Product Info
Table Of Contents
- 1. Scope
- 2. LMU-1300 Hardware Specifications
- 3. LMU-1300™ Connectors
- 4. Getting Started
- 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.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 (1hz 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 Version Reports (App Message 111)
- 7. Preparing for Installation
- 7.1 Plan the Installation
- 7.2 Size and Placement of LMU unit
- 7.3 Installing the LMU in a Vehicle
- 8. Installation Verification
- 9. Certification
- 10. Version History
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. ©2020 CalAmp 24 of 35
LMU-1300 Training Guide
Revision & Date
0.8–09/22/2020
Assisted GPS
Available (UBLOX)
Available (QCOM)
URL: http://xtrapath1.izatcloud.net/xtra3grc.bin
Important Note: If you are using private data plans, it is important to open a tunnel to ensure the
GPS Assist URLs can be resolved.
6.12 Motion Logs (1hz vs 5hz GPS Sample Rate)
Since there is a difference in the GPS update rate (1Hz vs. 5Hz) between the LMU8 and EdgeCore
products, there is an impact on the sampling in some of the pre-defined motion logs.
On an EdgeCore platform the Short Motion Log types 0-4 samples at a fixed interval of 200mS
while on the LMU 8-Bit the sample interval is 250mS. This causes the motion log buffer to fill up
faster.
The Short Motion Logs Types are defined on Calamp’s wiki site:
https://puls.calamp.com/wiki/Accelerometer_App_Note#Long_Type_0_.28Record_Type_1.29
6.13 Time Sync Precedence
The possible time sources for syncing the system clock is slightly different between the product
types. Both are listed below in order of precedence.
LMU 8-Bit
LMU-1300
GPS 3D Fix (highest priority)
GPS 3D Fix (highest priority)
Real Time Clock (RTC)
Real Time Clock (RTC)
GPS Fix (2D-Fix)
N/A
Time Server
N/A
Network Time
Network Time
No Time Sync Available
No Time Sync Available
6.14 Version String in ID Reports
The EdgeCore platform sends and displays the version string in a different format.
ID Reports:
The firmware version of the LMU-1300, can be obtained from the LMDirect ID Report, Extension
String field. In that field, there is a new Key-Value pair in the “LMUAPP” extension string. See the
definition below.
LMU Application Info
LMUAPP:< DeviceID>,< HW-ID>,< SerialNumber>[,< FileType>,< Version>[,<
FileType>,< Version>[,…]]]
Example:
LMUAPP:0,Rev11,,0,1.5.0.2.0.2aaf159,22,,11,,18,