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 30 of 35
LMU-1300 Training Guide
Revision & Date
0.8–09/22/2020
If any of the responses return Not-Acquired or Not-Registered (and the APN is correct), the wireless
network operator should be contacted for further troubleshooting.
Please note that it may take several seconds (or longer) for the LMU-1300™ to communicate with
the modem and acquire the wireless network.
8.2 GPS Verification
The next step is to verify that the GPS receiver is seeing enough satellites to obtain a valid GPS position.
Again, installers have two choices on how to perform this verification. First, like the Comm Verification,
there is a GPS status LED (i.e., the one closest to the SMA connector). If this LED is solid, then the LMU
has found GPS service.
If the LED is not visible then GPS service may be verified using an AT Command:
AT$APP GPS?
The response should be similar to:
Lat=3304713, Lon=-11727730, Alt=0
Hdg=113 Spd=0 3D-RTIME HDOP=130 nSats=7
Installers are looking for the 3D-RTIME setting along with a valid Lat, Long pair (i.e. something other
than 0). If the GPS receiver does not have a valid lock within 2-3 minutes, for further
troubleshooting, installers should contact CalAmp Support (productsupport@CalAmp.com)
8.3 Inbound Verification
The last item to verify is that the LMU-1300™ is sending data to the correct server. In general, this is
a two-step process that will need the aid of an observer on the back end. That is, a technician will
have to be logged in so they can monitor data coming into the backend mapping/vehicle
management application.
First, verify that the LMU-1300™ is using the correct Inbound IP address by using:
ATIS
The response should be similar to:
PUBLIC SERVICES 4
srvc(0) log(0:0) radio(0) mode(0:0) inb(0) ddd.ddd.ddd.ddd:<ppppp>
srvc(1) log(1:0) radio(0) mode(0:0) inb(1) 0.0.0.0:20500
srvc(2) log(2:0) radio(0) mode(0:0) inb(2) 0.0.0.0:20500
srvc(3) log(3:0) radio(0) mode(0:0) inb(3) 0.0.0.0:20500