User's Manual

DRAFT TrimTrac 1.5 Technical Manual v0.3ab 45
Defective TrimTrac 1.5
To confirm that a TrimTrac 1.5 is defective, do the following:
1. Try a known-good TrimTrac 1.5.
2. Move into an area with strong GSM coverage.
3. Send the TrimTrac 1.5 a data message requesting a response.
Note – Before returning the TrimTrac 1.5, be sure to save the TrimTrac 1.5’s
configuration settings, and remove your SIM.
No Modem Connection with Server Application
If it appears that you have no modem connection with the Server Application,
confirm that the Server Application modem is configured correctly and that the
TrimTrac 1.5 is configured and operating correctly. Do the following:
1. Check to see if the Destination Address is programmed correctly.
2. Verify the Server Application software is calling the correct
TrimTrac 1.5 telephone number and using the correct Unit ID, Security
Password and, if required by the SIM card, the SIM PIN.
TrimTrac 1.5 Not Reporting
If it appears that the TrimTrac 1.5 is not reporting to the server application as
expected, diagnose as follows:
1. Configuration. Always confirm whether the TrimTrac 1.5 is
configured as appropriate for the particular application environment.
More specifically, confirm that the provisioning parameters are
correct. Correct and re-test as necessary.
2. Lost Reports. In this case, the TrimTrac 1.5 has successfully created
a new message (Position, Status, or Alert) and it has been sent to the
GSM network. If such sent messages are not received by the server
application, then perhaps the messages are getting lost or delayed in
the GSM network.
Review the TrimTrac 1.5 message log and Report Sequence Numbers
compared to those received by the server application. If there are
missing on inconsistent Report Sequence Numbers at the server
application vis-à-vis the messages logged within the TrimTrac 1.5,
then a problem associated with the GSM network is the likely culprit;
3. Unsent Reports. If the TrimTrac 1.5 is correctly generating position
and status messages as expected (as determined by reviewing the
message log using the AT+CTKO? command with a provisioning
module), then the reports may not be getting sent due to: no available
GSM network, no SIM installed, or the Report Delay Flag is set to
something other than “0=Transmit All Messages”. (Note the Report
Delay Flag has no effect on the sending of Alert messages);