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 25 of 35
LMU-1300 Training Guide
Revision & Date
0.8–09/22/2020
Highlighted above is an example of file type ‘0’ which denotes the firmware file paired with
the version string. In this example the version of firmware file type is ‘
1.5.0.2.2aaf159’. The
version string is 1.5.0.2 and the rest of the string (‘2aaf159’) is a build number. Please note,
other files can be loaded in this field as an array of FileType, Version key-pair values.
6.15 Firmware Revision Convention
The Firmware Revision Convention is defined as
follows: MAJOR.MINOR.RELEASE.CANDIDATE.REVISION.HASH[M]
Below is the breakdown:
a) MAJOR.MINOR.RELEASE is the external facing official Version. (e.g. 1.5.4)
b) CANDIDATE is used to address bugs and minor changes. Also external facing (1.5.4.9)
c) REVISION number displays the amount of commits and is used by the development team.
Customers can ignore this field.
d) HASH is used by the development team. Customers can ignore this field.
6.16 Status LEDs
The LMU-1300 has 2 status LEDs, green and amber, to indicate GPS/Cell status.
Status LED Behavior
Please note that there are PEG configuration parameters that can change the factory default
behavior of all LEDs. LED behavior detail can be reviewed in the table below:
LED Definitions and Behavior
LED #1 (Comm LED – Orange or Amber) Definitions
Condition
LED 1
Modem Off
Off
Comm On - Searching
Slow Blinking
Network Available
Fast Blinking
Registered but no Inbound Acknowledgement
Alternates from Solid to Fast Blink every 1s
Registered and Received Inbound Acknowledgement
Solid
LED #2 (GPS LED – Green or Yellow) Definitions
Condition
LED 2
GPS Off
Off
GPS On
Slow Blinking
GPS Time Sync
Fast Blinking
GPS Fix
Solid