4.22. SCENARIOS AND EXAMPLES (SCRIPTS)
#generate a 3-secs beep to indicate
#the violation has been reported
>SED10NV4;S07C00&+;ACT=SXAZZ2<
#-------------------------------------------
#--START/STOP monitoring--------------------
#Speed limit for START/STOP detection
>SGS0310080<
#Start 2 minutes timer
>SED38SV0;S03-;ACT=SGC01TC00120<
#Stop the time
>SED39SV0;S03+ACT=SGC01U<
#Create the STOP report
>SED30NV4;C01+<
#Create the START report
>SED31NV4;S03C01&+<
#-------------------------------------------
#end
4.22.8
Reconnection event for TCP
Depending on how the Tracking Server works, a TCP reconnection
event may be required. As presented on the
Operation
chapter,
e-
track
TM
’s
works as TCP client always opening a TCP connection
with the server
even if it has nothing to report
. With this charac-
teristic the unit can be interrogated at any time. The pitfall of this
mechanism is that it may happen that the Tracking 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 throughout
the new connection so it can associate it to an unit’s ID. Unfortu-
nately not all Tracking 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 Tracking Server immediate information on who has opened
the connection.
A reconnection event is created simply with the
Axx
signal corre-
116
