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 28 of 40
LMU-3x40 Training Guide
Revision & Date
1.6 – 03/24/2021
Peg Action 144 2
- Save log files in a tar ball in
/data/backup/ and upload the file. This is good
for timer or event based log saving.
6.7 Modem/GPS Reset
The LMU-3x40 hardware architecture does not support rebooting the modem and/or GPS, since
both are on the same chip, they both use the same power rail. A complete system reboot is
required to reboot either function. This does not apply to the BLE and Wi-Fi functions.
6.8 SIM Form Factor
All previous legacy Calamp devices utilize a 2FF Micro SIM. The LMU-3x40 device uses a 4ff nano
SIM. See section
4.1.1 above for size details.
6.9 Boot Reason
There are some boot reasons that are no longer supported on the EdgeCore platform and some
new ones that are only supported on EdgeCore. The table below defines the boot reasons
supported on each product type:
Boot Reason
LMU-3030
LMU-
3040/3240
Boot Reason 0 (Cold Boot/Normal Power Up)
Yes
Yes
Boot Reason 1 (Power On - Factory Boot)
Yes
No
Boot Reason 2 (Reset Due to OTA Download Complete)
Yes
Yes
Boot Reason 3 (Reset Due to Radio Power Up
Yes
No
Boot Reason 4 (Wake Due to I/O Activity)
Yes
Yes
Boot Reason 5 (Wake Due To Timer)
Yes
Yes
Boot Reason 6 (Wake Due to An Incoming SMS Message)
Yes
Yes
Boot Reason 7 (Wake Due to Application Restart)
Yes
Yes
Boot Reason 11 (Reset Due to Hosted App OTA Download
Complete)
N/A
No
Boot Reason 12 (Wakeup from receive line activity on serial
port)
N/A
No
Boot Reason 14 (BOOT_WDOG - lmu watchdog reboot)
No
Yes
Boot Reason 15 (BOOT_VBU_WDOG - vbu watchdog reboot)
No
Yes
Boot Reason 16 (BOOT_LMU_HARD_RESET - linux hard
crash/kernel panic)
No
Yes
6.10 Peg Resources
The LMU-3040 and LMU-3240 offer a significant amount of PEG resources for PEG2 scripting and
accumulator storage. The table below highlights the PEG resource differences between the
product types.