Installation Guide

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.
5.6.3 Inbound Verification
The last item to verify is that the HMU-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 HMU-3640™ is using the correct Inbound IP address by using:
AT$APP INBOUND?
The response should be similar to:
INBOUND LMD
INBOUND 0 ADDR ddd.ddd.ddd.ddd:ppppp *
INBOUND 0 URL myURL.myCompany.com
INBOUND 1 ADDR 0.0.0.0:20500
INBOUND 1 URL
INBOUND 2 ADDR 0.0.0.0:20500
INBOUND 3 ADDR 0.0.0.0:20500
The installer will need to verify with a backend technician that the, URL (myURL.myCompany.com ), IP address
(ddd.ddd.ddd.ddd) and port
(<ppppp>) are correct.
https://puls.calamp.com/wiki/HMU-3640_Hardware_%26_Installation_Guide 19/27
The second step is to verify that the HMU-3640™ is sending data. The best way to do this is to force the HMU-3640™ to send in
an
unacknowledged Event Report (i.e., its current GPS location) with the following command:
AT$APP PEG SUNRPT 255
The HMU-3640™ will respond with: OK
The backend monitor must then be contacted to confirm that they received an Event Report with Event Code 255.
Assuming that all three sections have passed, the installation can be considered to be complete.
5.6.4 Verification via SMS
The current Comm, GPS and Inbound status of a GSM LMU can be obtained via SMS provided you have access to an SMS
capable phone or
PDA.
Using your handset, send the following SMS Message to the LMU:
!R0
Within a few minutes, the LMU should return a response in the following format:
APP: <App ID> <Firmware Version>
COM:<RSSI> [./d/D][./a/A][./L][IP address] [<APN>]
GPS:[Antenna <Short/Open/Off>] | [No Time Sync] | [<FixStatus> <Sat Count>]
INP:<inputs states> <vehicle voltage>
MID:<mobile ID> <mobile ID type>
INB:<inbound IP address>:<inbound port> <Inbound Protocol (LMD/LMX)>
APP:
o <App ID>:
The Application ID value of the LMU indicating the host platform and the wireless networking technology of the LMU.
o <Firmware Version>:
The current firmware version in use by the LMU
COM:
o <RSSI>:
This is the signal strength the wireless modem sees from the network. In general the LMU is at least scanning for the network if
the RSSI is not -113.
o [./d/D]:
If the character ‘D’ is present, it indicates the LMU had a data session established when it responded to the status request. For
the 8-Bit product line an upper case ‘D’ indicates both the Inbound and Maintenance sockets are ready. The lower case ‘d’
indicates that only the Maintenance socket is ready. A ‘.’ indicates no sockets are ready.
o [./a/A]:
This field indicates if the LMU has received an Acknowledgement from the Inbound server. This field will be empty if the
LMU has never received an ACK. The lower case ‘a’ will be present if it has received an ACK since the last cold boot (i.e.
power cycle) but not the last warm boot (App Restart or Sleep). The upper case ‘A’ will be present if the LMU has received an
ACK since the last warm boot. A ‘.’ Indicates no acknowledgement has been received.
o [./L]:
This field indicates if the LMU’s log is currently active. An ‘L’ indicates that the log is currently in use (i.e. one or more