User Guide
Table Of Contents
- 1. Scope
- 2. LMU-3040 Hardware Specifications
- 3. LMU-3040™ Connectors
- 4. Getting Started
- 4.2 SSH Credentials
- 4.3 Interactive “AT Console”
- 4.4 Command Line Interface (CLI)
- 4.5 Log File
- 4.6 Backup Logs
- 4.7 File Components
- 4.8 Software & Script Updates
- 5. PEG2
- 5.2 PEG2 File
- 5.3 PEG2 TAG Definitions
- 5.4 Multiple Modifiers
- 5.5 PEG1 -> PEG2 Conversion
- 5.6 PEG2 Native Editor
- 6. LMU32 vs EdgeCore Platform Differences
- 6.1 I/O Mapping & Wake-Up Sources
- 6.2 LMU Firmware Updates (Delta Files)
- 6.3 Vehicle Bus PID Polling Rate
- 6.4 PEG2 “Lines”
- 6.5 Event Index Field
- 6.6 Remote Debug PEG Action
- 6.7 Modem/GPS Reset
- 6.8 SIM Form Factor
- 6.9 Boot Reason
- 6.10 Peg Resources
- 6.11 GPS
- 6.12 Motion Logs (4hz vs 5hz GPS Sample Rate)
- 6.13 Time Sync Precedence
- 6.14 Version String in ID Reports
- 6.15 Firmware Revision Convention
- 6.16 Status LEDs
- 6.17 Dual APN Mode
- 6.18 Version Reports (App Message 111)
- 7. Installation Verification
- 8. Regulatory Information
COMPANY CONFIDENTIAL: CalAmp reserves all rights to these documents and any information contained therein. Page
Reproduction use or disclosure to third parties without express permission is strictly prohibited. ©2021 CalAmp 35 of 40
LMU-3x40 Training Guide
Revision & Date
1.6 – 03/24/2021
The backend monitor must then be contacted to confirm that they received an Event Report with Event
Code 255.
Assuming that all three sections have passed, the installation can be considered to be complete.
7.4 Verification via SMS
The current Comm, GPS and Inbound status of a LMU can be obtained via SMS provided you have access
to an SMS capable phone or PDA.
Using your handset, send the following SMS Message to the LMU:
!R0
Within a few minutes, the LMU should return a response in the following format:
APP: <App ID> <Firmware Version>
COM:<RSSI> [./d/D][./a/A][./L][IP address] [<APN>]
GPS:[Antenna <Short/Open/Off>] | [No Time Sync] | [<FixStatus> <Sat
Count>]
INP:<inputs states> <vehicle voltage>
MID:<mobile ID> <mobile ID type>
INB:<inbound IP address>:<inbound port> <Inbound Protocol (LMD/LMX)>
APP: o
<App ID>:
The Application ID value of the LMU indicating the host platform and the wireless networking technology
of the LMU.
o <Firmware Version>:
The current firmware version in use by the LMU
COM:
o <RSSI>:
This is the signal strength the wireless modem sees from the network. In general the LMU is at least
scanning for the network if the RSSI is not -113.
o [./d/D]: