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 14 of 35
LMU-1300 Training Guide
Revision & Date
0.8–09/22/2020
Script Section
TAG Definition
Example
!SCR: Script Section starts here. This section must
immediately follow the Configuration Parameter
(!CP) section.
• PEG Lines are no longer parameterized.
• !SCR will overwrite the entire PEG2 script
on the device (no longer a union of PEG
lines)
• You can delete the PEG2 script on the
target device by including the !SCR tag
without any lines following.
• The generic line number references can
be replaced with custom names or named
sub-routines
!SCR:
L512000;T1,0;A51,512225
L512001;T2,0;A51,512225
L512002;T3,0;C39,7;A51,512185
L512003;T5,2;A51,512185
L512004;T11,0;C17,15;A31,15
L512005;T18,5;C17,15;A31,15
L512006;T48,0;C16,15;^C17,16;A31,16
L512007;T5,2;C8,0;^C16,16;A32,16
L512008;T12,0;A124,28
L512009;T12,0;A125,29
LCustomLabel;T5,2;!C44,0;A51,512195
End of File (EOF) and CRC
TAG Definition
Example
!EOF: End-of-file marker (this tag) must be
included
!CRC:
Following EOF marker, a 2-byte binary CRC
value must be appended to validate integrity of
file during transit. This is needed for OTA and
Serial transfers
Important Note:
If !SIG or !CRC is incorrect, PULS
will re-calculate upon upload. However, this
means while the file has been corrected for OTA,
your original file will not be valid or usable for
serial updates until fixed.
...
L514014;T18,35;A112,0,0
L514015;T15,0;A112,0,0
L514250;T0,0;A0,0
!EOF:
%P