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 11 of 35
LMU-1300 Training Guide
Revision & Date
0.8–09/22/2020
4.5 Log File
Engineering and LMU logs can be found in the Linux file system. You can find the most recent log
file in a specific
/var/log/ directory, in a file named messages
If you would like to view new information that is written to this log file, Linux offers a way to do
this through the command line.
• Enter: tail –F /var/log/messages
This command will open the messages file and display the latest written lines of the file. It will
continue to display the most updated lines you quit.
Helpful Tip: Linux allows the option to create multiple instances of SSH windows so you can have
one SSH session viewing a log while the other is being used to send AT commands. Other Linux
options such as parsing specific debug using a grep command can also be utilized. For example,
the command:
tail –F /var/log/messages | grep VBU will display lines in the log that have VBU in
the string.
Important Note: The log file stored in ‘messages’ gets overwritten on every device wake-up.
4.6 Backup Logs
There is a method to store a current log file into a backup directory. This can be programmed in
the PEG Script by using
PEG Action 144.
• PEG Action 144 modifier 1 will save the current log into the /data/backup/ folder
• PEG Action 144 modifier 2 will save the current log and also send it to the set remote debug
server defined in param 2328.
Important Note: Only one backup file can be stored at a time
4.7 File Components
Devices have several components on the EdgeCore platform that are provisioned at the factory.
These components are described below:
File
Description
~Size
LMU Delta Image
This image includes Modem and GPS software in
addition to Application software.
12-18Mb
PEG2 Script
This file controls and defines all the business logic and
configuration settings on the device. PEG2 script file
sizes will vary from application to application
50-150Kb (avg)
All file sizes are subject to change.
Important Note: Data plans may be impacted due to the larger size of FW delta files.