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 21 of 40
LMU-3x40 Training Guide
Revision & Date
1.6 – 03/24/2021
PEG1 single modifier mapping:
Upper 4 bits = Source, Lower 4 bits
= Destination
Example: “I want to copy Accumulator 10 into Accumulator 22 every second”
PEG1
PEG2 Example
Not possible using PEG Action 103 (Copy Accum).
Limited to 4 bits (accum 0-15)
Possible with this PEG2 line:
T18,5;A103,10,22
Using PEG Action 124 (Select Dest.) & 125 (Copy to
Dest.):
120500007C160000
120500007D0A0000
Possible with one PEG2 line:
T18,5;A103,10,22
5.5 PEG1 -> PEG2 Conversion
The latest version of LMU Manager offers a PEG1-PEG2 conversion export feature so that an
existing LMU-3030 PEG1 script can be easily converted into a PEG2 script to avoid the need of re-
writing an existing script.
Note: A PEG1->PEG2 conversation does not optimize how PEG resources would be used if the
script were to be written natively in PEG2. For example, the ability to have a complex set of
conditions on one PEG2 line is not able to be leveraged unless done manually by the script writer.
As a result, no PEG lines are being saved during the conversion.
Converting from PEG1 to PEG2, it is a two-step process.
Step1: Convert LMU-3030 PEG1 script file to an LMU-3x40 PEG1 script file:
o Open Session with App ID that supports PEG2 (e.g. 1001, 1002, 1011, 1012)
o Load 3030 PEG1 Script to Convert
o Select “Export” -> “Convert 3030 to 3x40 (*.csv)” selection
o Press OK on dialog boxes and Save File as CSV