DCT Antares SB, User Manual

Page: 83 / 238

4.5. *EVENT MACHINE
•
Set/Reset user signals to trigger other events. This allows the creation
of complex event’s scenarios.
•
Sense the vehicle’s ignition to have the unit start working on a low
power consumption mode whenever the vehicle is off.
User-actions (pre-set TAIP commands) can also be used to generate reports.
This is because the response to a TAIP command(s) that is defined on an
event’s user-action field is (are) sent to the event’s
Destination Address (for
non-silent events). So, any information that is not included in the report-
ing messages
ET
,
EV
and extended-EV, that can be consulted with a TAIP
query, can be reported by creating an event that has the TAIP query or
queries on the user-action field.
For example, the following configuration
>
SGC00TR00300
<
>
SED00NV0;C00+;ACT=QRP;ACT=QGC06V
<
will make the unit report the GSM network state ( >
QRP
< )and the value
of the counter 06 >
QGC06V
< every 5 minutes to Destination Address 0 . For
more examples see the Scenarios and examples chapter.
4.5.3 Events
Finally, triggers and actions are bound together on a single configuration
message called event . An event is defined or consulted with the TAIP
ED
message. A single event holds a trigger , a report action and optionally an
user action . The next figure gives a global description of the TAIP
ED
mes-
sage. For detailed information refer to the unit’s TAIP specification chapter.
The Antares SB
TM
has 50 events available for the user to configure. They
may be defined all at once in a configuration script or they me be individually
defined at any moment as the user adds/removes functionality. The actual
81