Notes for guidance on handling of $TEST errors:
GPS Error or poor GPS availability (low % GPS availability)
A GPS ERROR indicates that no fix has been returned for a fixed timeout period. Could be an
indication of a device/antenna fault or simply that the vehicle is parked in covered area (e.g.
underground car park). Persistent GPS errors and low availability are most often caused by
installation issues, poor device location, incorrect orientation or vehicle issues such as
interference or athermic glass windscreens.
A ‘JAM’ status indicates that the GPS receiver has detected CW interference which could be cause
by the use of a GPS jamming device in close proximity, typically within 5-10m (i.e. in the vehicle
itself).
GPRS Error
This means that the device has no GPRS service. Can be simply due to GSM network
coverage/service, but persistent GPRS ERROR is an indication that the GSM SIM card is not
enabled for GPRS. We suggest that you discuss with your SIM provider and consider trying a
SIM refresh or replacing the SIM.
APN Error
This is usually caused by incorrect GPRS access point settings (APAD, APUN and APPW). Please
check the correct settings with your network/SIM provider and configure the device accordingly
using the commands:
$APAD,<apn-address>
$APUN,<apn-username>
$APPW,<apn-password>
TCP Socket Error
The modem has failed to open a socket on the specified IP address and port number. Can be
caused by incorrect TCP address settings (IPAD, PORT), a fault at the host server or even wider
internet problems. If necessary, re-configure the IPAD & PORT using the commands:
$IPAD,<ip-or-hostname>
$PORT,<port-number>
Modem TCP acknowledgment Error
This indicates that the
device
can proceed all the way to open a socket and deliver the report
packet, but does not get the normal acknowledgment response from the host TCP application.
This is normally caused by a fault at the host end. Ensure that the device is correctly provisioned
on your application/software, correct type, protocol and that the 15 digit IMEI matches the one
on your system.
Ignition Input Inactivity Error
This error is set when no ignition events have been detected for more than 24 hours. This is
usually caused by poor/incorrect installation. Consider using an alternative ignition mode with
the following commands:
$IGNM,0
// use GPS speed / accelerometer data for journey mode detection
$IGNM,3
// use external voltage for journey mode detection
Immobilisation Issues
If status shows as ‘N/A’, the immobiliser application is not assigned to any digital output. Please refer
to the CDOP command in the user guide for the appropriate device, for details of how to assign
applications to digital outputs.
The ON/OFF status refers to the physical status of the device output, which may relate to immobiliser
status ON or OFF, based on the immobiliser logic defined in the DRIC command.
