DCT Antares SB, User Manual

Page: 139 / 238

5.13. CONFIGURING/READING A DISTANCE COUNTER
5.13 Configuring/reading a distance counter
Refer to the
XACR
message.
5.14 Generating an extended-EV report
Related commands:
ED
,
EV
,
XAEF
As mentioned on the Reports’ messages section of the Operation chapter,
an EV report can be extended to include extra information tags
6
. To do
so, the Message IDs A , B and C of an event definition are used (See the
ED
message). An event defined with one of these letters as Message ID will
be transmitted as an
EV
message with added information after the Source
and Age fields. The extra information is presented as strings separated by
the ’;’ character. For a detailed information on these strings refer to the
EV
message.
We are going to configure 5 events to show how the extended-EV report
and the normal reports,
ET
and
EV
work.
Let us set events 20 and 21 to send
ET
and
EV
normal (not-extended) reports
whenever the Counter 5 reaches some value defined elsewhere:
>
SED20NT2;C05+
<
>
SED21NV2;C05+
<
This will make the unit send the following reporting messages to Desti-
nation Address 2 whenever signal
C05
goes from low to high:
>
RET201447152212;ID=EXAMPLE
<
>
REV211442578250-0802813901519512;ID=EXAMPLE
<
Now, let us set events 30, 31 and 32 to send extended-EV reports. Events
30 and 31 will generate an
EV
report having the extra information tags that
give information on the vehicle’s altitude and on the vehicle’s acceleration
and let us set event 32 to generate an extended report having the vehicle’s
acceleration, number of satellites and the state of Distance Counter 7.
First, we have to configure the extended format that it is going to be used
by events 30 and 31, let us use the extended format (
XAEF
) A. According
to the
XAEF
message the tags corresponding to altitude and acceleration are
;AL
and
;AC
. So, we set extended-format A as:
>
SXAEFA;AL;AC
<
Now, let us define extended-format C to be used by event 32:
>
SXAEFA;AC;SV;CV07
<
Having set the extended formats, define the events. For this example we are
going to trigger the events with inputs:
>
SED30NA2;IP1+
<
>
SED31NA2;IP2+
<
>
SED32NC2;IP3+
<
6
See the
XAEF
message for a list of available information tags.
137