User's Manual

DRAFT TrimTrac 1.5 Technical Manual v0.3ab 19
SET_ALERT_STATE messages are required to either acknowledge or clear the
alerts. Once the monitored devices or conditions have been returned to “normal”,
then the input status will be updated accordingly.
LPA Input Delay
In earlier versions of TrimTrac, a Low Priority Alert would become “armed”
whenever the monitored switch was closed for 250 mSeconds or longer and become
“activated” upon any detection of subsequent motion. This “armed-activation”
sequence proved too rapid for some applications that required a delay from the time
the monitored switch was closed before the Low Priority Alert became “armed”. As
such, TrimTrac 1.5 has a programmable input delay that postpones the arming of the
LPA. This feature is expected to be useful when the LPA is used to monitor a
vehicle security system. After the vehicle security system itself is armed, then the
TrimTrac 1.5 itself will become armed after the LPA Input Arming Delay, T31,
countdown timer expires. See AT+CTKZ Daily Hours, Runtime & Other Extended
Settings on page 99 and SET_EXT2_APP_CONFIG on page 116.
Automatic Message Log Dump
In certain geographic areas, TrimTrac 1.5 will travel in and out of GSM coverage.
The device will continue logging position fixes and status messages even while
out of GSM coverage, but obviously it will not be able to send them when they
are logged if there is no GSM coverage. The Automatic Message Log Dump
feature will cause the TrimTrac 1.5 transmit all messages which would have
otherwise been sent had there been GSM coverage at the time they were created
and logged once a GSM network connection has been re-established. Automatic
Message Log Dump can be enabled either during initial provisioning of the device
or through the use of over-the-air commands.
The Automatic Message Log Dump feature must be used with a certain amount of
discretion as it does not differentiate between the different message TriggerTypes.
Any message that should have been transmitted had there been GSM coverage at
the time will, assuming GSM coverage is re-established, get transmitted by the
Automatic Message Log Dump feature. The importance of this statement
becomes apparent when one or more priority input alerts get activated while
outside GSM coverage.
If one or more get activated while there is no GSM coverage, then the TrimTrac
1.5 will continuously attempt to transmit those alerts until a successful
transmission results. In the meantime, each of the failed transmit attempts are
placed in the TrimTrac 1.5 message log with the GSM Status set “2=No
Network”. Once the TrimTrac 1.5 has re-entered GSM coverage, it will begin
transmitting each of the previously failed transmit messages. Depending upon
how long the device was outside of GSM coverage with the alerts activated, this
could result in a very large number of messages being transmitted at a high rate.
Should this situation occur, then the server application should be prepared to
acknowledge the incoming alerts AND to automatically reconfigure the TrimTrac
to disable the Automatic Message Log Dump feature. It should be noted that re-