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 12 of 35
LMU-1300 Training Guide
Revision & Date
0.8–09/22/2020
4.8 Software & Script Updates
All of these files can be updated Over-The-Air if subscribed to Calamp’s Device Management
Service (PULS).
These files can also be updated with physical access to the device as well. Below are the steps
and options below:
1. Transfer Firmware/Script (e.g. WINScp, ADB Push) to /data/configs/files directory.
First, change directory to /data/configs/files directory.
Enter command: cd /data/configs/files/
a) PEG2: dnld_cli prog_file 0 22 <
PEG2 File>.pg2
b) LMU: dnld_cli prog_file 0 0 >
LMU Binary>.bin
c) VBU: dnld_cli prog_file 25 0 <
VBU Binary File>.bin
d) BLE: dnld_cli prog_file 26 0
<BLE Binary File>.bin
2. Option 2: Using AT Console: Change the file name to update to “ota_file.bin”
a) PEG2: at$app fprog 0 22
b)
LMU: at$app fprog 0 0
c)
VBU: at$app fprog 25 0
d)
BLE: at$app fprog 26 0
5. PEG2
PEG2 is the next-generation scripting environment with enhancements that allow you to build more
efficient scripts with easier maintenance and unrestricted feature growth. These benefits are made
possible by features such as:
• Multiple Triggers, Conditions and Actions per line
• Expanded modifier fields
• Complex boolean Condition logic
• Labels for Jumps and Calls (i.e. PEG line indexing will not change no matter where a line is
added)
• In-line comments
5.2 PEG2 File
In next generation devices supporting PEG2, the file containing the PEG script and the configurations
parameters has an updated format. The new file has the following characteristics:
• Format
o Header - Time/Date, Signature, ID