DCT Antares SB, User Manual

Page: 111 / 238

5.1. GETTING STARTED
minutes. There are several ways of doing this but one of the most common is
to configure a
Time And Distance signal with no Maximum Time Between
Reports and no Distance Threshold parameters so it triggers a
TD
signal on
a time-only basis set by the Minimum Time Between Reports parameter.
Refer to the
TD
message for more information.
Let’s use a reporting period of 5 minutes (300 seconds). For no special
reason let’s choose
TD
signal 8 to do the job:
>
STD80300
<
This will make the unit activate signal
TD8
every 5 minutes so we can create
an event triggered by this signal which is going to generate the periodic
report.
Note that in order to keep this example simple, we are using a basic time-
only report, but this approach is not advised on a real world scenario where
a vehicle remains at rest most of the time and where having a time-only
criterion will generate a bunch of unnecessary messages. It is recommended
to use the three parameters of the
Time And Distance definition to achieve
a more intelligent report.
5.1.6 Tiding a signal to an event
With the signal
TD8
generating a pulse every 5 minutes the only thing left
to do is defining an event that triggers with this condition. At this point we
need to ask ourselves what event code to chose and what kind of message
send to the AVL server. The answer lies on the AVL server configuration:
The event code has to have any meaning for the AVL software and the type
of message depends on the kind of information we will like to get from the
unit’s report. There are two kind of messages, the
EV
gives more information
than the
ET
which only gives the time and date when the event occurred.
In order to receive full GPS information we need to use the
EV
report.
As event code (00-49) we chose for no special reason code 37:
>
SED37NV4;TD8+<
Notice we are using DA 4. This will make the report generated by event 37
to be sent to the single DP 00 which is our AVL server.
For more information consult the
ED
message on the TAIP reference.
5.1.7 Checking the host software/server
A this point and as long as the On line LED remains solid, an EV message
should be arriving to the AVL server every 5 minutes. The software has to
be able to interpret TAIP
EV
and/or
ET
messages. If you run into troubles
checking your AVL application you can always shut it down an use some
popular free TCP listener applications that will show you the RAW data
where you can check the TAIP messages generated by the
Antares SB
TM
.
Other useful tool is a network sniffer that allows you to analyze the traffic
on a given TCP/UDP connection while you run the AVL server.
109