5.7. START/STOP MONITORING
5.7.4
Create the START report
We define this event as occurring any time the vehicle’s speed goes beyond
the set limit of
8mph
and a previous STOP condition existed. To do so
we create the START event as depending on the
S03
signal AND on the
counter 01 signal
C01
. This works because once the
C01
counter reaches the
2 minute threshold the
C01
signal stays high “forever” (until the counter
gets undefined by something else).
>
SED31NV4;S03C01&+
<
5.7.5
Something’s missing...
As with the
Speed Violation
example we also need a silent event that unde-
fines the counter in case the vehicle resumes its march before the 2 minutes
condition, to do so we use silent event
39
:
>
SED39SV0;S03+ACT=SGC01U
<
This assures that a vehicle’s stop that lasts less than 2 minutes is not going
to be reported.
5.7.6
Script
The corresponding script of this configuration plus all the examples worked
so far is:
#Antares SB script
#Getting Started example
# + SMS reporting (+SMS inter Voice interaction)
# + Ignition sense
# + Speed viol. and warning
# + START/STOP monitoring
#--Delete any previous configuration--------
>SRT;CONFIG<
>SXADP**U<
#-------------------------------------------
#--Essential configurations-----------------
#Units ID
>SIDEXAMPLE<
#configuring the SIMs PIN
>SRFI1234<
#configuring the APN
>SRFAinternet.carrier-name.com<
#The remote AVL server address and port
>SXADP0000avl.server.com;2145<
122
Содержание Antares SB
Страница 1: ......
Страница 2: ...Antares SB TM GSM User s Manual FW 5 21 Digital Communications Technologies April 15 2008...
Страница 37: ...2 1 POWER SUPPLY 35...
Страница 38: ...2 1 POWER SUPPLY 36...
Страница 42: ...2 5 CONNECTION DIAGRAMS 40...
Страница 141: ...6 Unit s TAIP reference...
Страница 191: ...6 32 XADM DIAGNOSTIC MESSAGE 189...
Страница 228: ......
Страница 229: ......