User's Manual

GlobalTrak ™ GT Lite Operation and Maintenance Manual
APPLICATION: (batteryVoltageCallback) millivolts=4101, mAh = 3772
The battery callback displays the current battery voltage in millivolts and capacity remaining
in mAh remaining.
APPLICATION: (messageCallback) ZIGBEE_STAR_AWAKE
This statement indicates proper communication with the low processor controller. Every time
the main processor interrupts the low power controller, the low power controller reponds with
the ZIGBEE_STAR_AWAKE message. If this message is received by the main processor, the
debug statement above will be printed.
APPLICATION: (messageCallback) ZIGBEE_RESET_INFO
After a reset or boot, the low power controller tells the main processor the reason for reset.
The statement following ZIGBEE_RESET_INFO states the reason for reset.
APPLICATION: (messageCallback) ZIGBEE_STAR_SENSOR_DATA
This statement indicates the main processor has received sensor data from the low power
controller. Following this statement, there will be debug information that describes the
sensors and data received.
APPLICATION: (messageCallback) sensorId=6, sensorValue=454
This statement describes data from one sensor that is received by the main processor. There
are typically at least 5 of these messages together to describe all of the sensor data on the
low power controller. The sensor ID describes what sensor is reporting and the data is a
digital value from the sensor. Please consult section XXXXXXX on wireless sensors.
APPLICATION: (messageCallback) ZIGBEE_STAR_SENSOR_EVENT_DATA
This statement indicates that the main processor has received event data from the low power
controller. If this is received, at least one sensor has gone into an event condition.
APPLICATION: (messageCallback) ZIGBEE_STAR_END
This statement indicates the end of low power controller communication. It is sent by the low
power controller to say that it has no further information to send.
PROTOCOL: (LoggerMessage_Create) Enter. recordDataType=0
This statement indicates that a message has been created and the record data type of the
message. For more information about record data types, please consult section 2.2.
PROTOCOL: (LoggerMessage_CreateTempMessage) Device message created
successfully!
This statement indicates that a message has been successfully placed on the temp queue. All
messages on the temp queue require a GPS update once a fix is received.
PROTOCOL: (LoggerMessage_CreateDeviceMessage) Device message created
successfully!
This statement indicates that a message has been successfully placed on the transmit queue.
Generally messages move from the temp queue to the transmit queue upon being updated
with a GPS fix.
Prepared: R. Straz Date: July 25, 2007 Page 61 of
139