DCT Antares SB, User Manual

Page: 82 / 238

4.5. *EVENT MACHINE
•
extended-EV: As mentioned on the Reports’ messages section of the
Operation chapter, the EV report can include extra information tags.
To do so, the Message IDs A , B and C of an event definition are used.
The information tags for messages IDs A , B and C are defined with
the XAEF command. For more information see the
ED
,
EV
and
XAEF
TAIP messages. See also the Scenarios and examples section .
User-defined action(s)
An user-defined action is defined by a user-specified TAIP message (or set
of messages). This enables the user to predefine TAIP messages
11
that the
unit will only process whenever the trigger goes off. This is specially useful
when making the unit drive outputs automatically. For example: The unit
may automatically (without asking a remote server/user) shut a vehicle’s
engine off
12
whenever a vehicle is trying to move on a forbidden out-of-labor
time. It is also helpful when driving the unit’s counters to create complex
reporting scenarios.
Any TAIP command available on the TAIP console can be predefined as
an user action, so there is a wide range of possibilities to choose. Some of
them include:
•
Change a reporting schedule according to a special region and/or time
of day.
•
Start a situation timer: For example to keep track of the time a secu-
rity door remains open. Another example of using timers and events
is to keep track of a vehicle’s IDLE situation like when a vehicle re-
mains at rest with the ignition ON and/or monitor a STOP situation
meaning the vehicle is at rest and the ignition is OFF.
•
Keep track of how many times a situation occurs. Like keeping track
of how many times a speed limit is violated.
•
Lock or unlock the vehicle’s doors.
• Go to sleep mode to preserve the unit’s back-up battery.
•
Start a voice call to a predefined phone number.
•
Activate a led connected to any output so the driver knows when there
is a voice call being held to any of the authorized phone numbers.
•
Activate a led connected to any output whenever a vehicle is out of
a polygonal geo-fence.
•
Have the Antares SB
TM
safely
13
turn the vehicle’s engine off whenever
this travels too far from the normal working region.
•
Enable a vehicle’s ignition when the working hour begins.
11
Several TAIP actions can be set on an event definition. See the
ED
message for
information.
12
Shutting an engine off without considering a vehicle’s state is not
advised.
See the Scenarios ’ chapter for better ways of doing this.
13
The user configuration should include a low speed precondition. Turning an
engine off without knowing a vehicle’s state is not advised .
80