DCT Antares SB, User Manual

Page: 62 / 238

3.11. REPORTS’ MESSAGES
For detailed information on this message refer to the
EV
message
on the Unit’s TAIP reference chapter
When configuring the Event Machine , on each event definition, the
user decides what Reporting Message the event shall generate. For
information on events’ configuration refer to the Event Machine sec-
tion of the Configuration chapter .
Firmware Version 5.21 supports the addition of information tags to
the
EV
reporting message so that more information can be included
on an event’s report.
The Extended Reporting Messages (Extended EV)
When using an Extended Reporting EV Message , extra tags are added
at the end of the standard
EV
message presented above. These tags
allow the addition of information on:
•
Inputs and Outputs state.
•
Counters’ values: Timers and distance counters.
•
Vehicle’s acceleration.
•
Altitude (AMSL).
•
Analog to Digital Converter value.
•
Back-up battery level.
•
Number of GPS-satellites in view.
• GPRS/GSM network state.
The information tags are messages separated by the ’;’ symbol. They
are displayed after the
Source and Age fields of the EV message and
the last of the tags is the ”‘ ;ID= ”’ tag which has always been present
on every unit’s report. One example of such a report is:
>
REV381442578250-0802813900000012;AC=000;AL=02595;
[...]
[...]
SV=08;ID=EXAMPLE
<
One extended message can contain one extra tag or it can contain all avail-
able tags. The user decides which tags the unit must add to an
EV
message.
For information on how to make the unit generate Extended EV Messages
see the Configuration chapter and the
XAEF
and
ED
messages.
3.11.2 Responses to TAIP Commands Messages
Firmware 5.21 allows the report of the response generated by a TAIP com-
mand included on an event’s user-action. This enables the unit to auto-query
a TAIP command based on the
Event Machine and have the response to the
60