https://puls.calamp.com/wiki/TTU-2900_Hardware_%26_Installation_Guide
20/29
7/21/2020
TTU-2900 Hardware & Installation Guide - PULS Wiki
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 TTU-2900
™
to communicate with the modem and acquire the wireless network.
5.6.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:
The response should be similar to:
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 TTU-2900
™
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 TTU-2900
™
is using the correct Inbound IP address by using:
The response should be similar to:
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.
The second step is to verify that the TTU-2900
™
is sending data. The best way to do this is to force the TTU-2900
™
to send in an
unacknowledged Event Report (i.e., its current GPS location) with the following command:
The TTU-2900
™
will respond with: OK
The backend monitor must then be contacted to confirm that they received an Event Report with Event Code 255.
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
AT$APP GPS?
Lat=3304713, Lon=-11727730, Alt=0
Hdg=113 Spd=0 3D-RTIME HDOP=130 nSats=7
AT$APP INBOUND?
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
AT$APP PEG SUNRPT 255
