DCT Antares SB, User Manual

Page: 135 / 238

5.10. RECONNECTION EVENT FOR TCP
#Restore (set low) the user signal
>SED16SV0;E13+;ACT=SSSU000<
#-------------------------------------------
#end
5.10 Reconnection event for TCP
Depending on how the AVL server works, a TCP reconnection event may
be required. As presented on the
Operation chapter, Antares SB
TM
works
as TCP client always opening a TCP connection with the server even if it
has nothing to report . With this characteristic the unit can be interrogated
at any time. The pitfall of this mechanism is that it may happen that the
AVL server does not know from which unit the new incoming connection is.
A solution would have been having the server to send an ID query thru the
new connection so it can associate it to an unit’s ID. Unfortunately not all
AVL servers do this. To overcome this situation a TCP reconnection event
may be configured on the unit so it sends an event every time a connection
is (re) established with the server. This gives the AVL server immediate
information on who has opened the connection.
A reconnection event is created simply with the
Axx
signal corresponding to
the IP-type destination whose reconnection is to be monitored. So for our
example the
A00
signal has to be used as the AVL server is defined on the
Destination Point 00:
>
SED49NV4;A00+
<
We chose event 49 for no particular reason. This will have the AVL server
receiving event 49 any time a new connection from an
Antares SB
TM
is
established.
5.10.1 Script
The resulting script is:
#Antares SB script
#Getting Started example
# + SMS reporting (+SMS inter Voice interaction)
# + Ignition sense
# + Speed viol. and warning
# + START/STOP monitoring
# + Safe engine turn off
# + A better T&D criterion
# + Reconnection event
#--Delete any previous configuration--------
>SRT;CONFIG<
133