Installation Guide

9/27/2017 LMU-3640 Hardware & Installation Guide - PULS Wiki
https://puls.calamp.com/wiki/LMU-3640_Hardware_%26_Installation_Guide 18/23
ATIC
Depending on the wireless network being used something similar to what is shown below will be displayed. It is important to verify that 'Yes'
values are displayed at the top for Data and Network registration and the correct APN is displayed.
Radio Access : GSM
Network Reg. : Yes, Home
Data Reg. : Yes, Home
Connection : Yes
RSSI : -97 dBm
BER : 99
Channel : 737
Cell ID : 3441
Base Station ID : 40
Local Area Code : 31003
Network Code : 410
Country Code : 310
IMEI (Modem S/N): 351802055396182
IMSI (SIM ID) : 310410202524377
ICC-ID (SIM S/N): 89014102212025243778
Phone Number :
GPRS APN : ISP.CINGULAR
Maint. Server : maint.vehicle-location.com(216.177.93.246):20500
Inbound Server : (0.0.0.0):20500
Dual Comm : routing id=0, log cid=0, modem type=21, inbnd index=0
OK
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-3640™ to communicate with the modem and acquire the wireless network.
4.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.
4.8.3 Inbound Verification
The last item to verify is that the LMU-3640™ 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-3640™ is using the correct Inbound IP address by using:
AT$APP INBOUND?
The response should be similar to:
INBOUND LMD