5.7. START/STOP MONITORING
+ Ignition sense + Speed violation and warning.
Now we have to tell the unit what is a STOP and what is a START. There
are several ways of doing this, for this example we are going to define a
STOP situation to be when the vehicle’s speed remains below a small speed
limit for a given period of time. Having this, we define the START situa-
tion as happening when the vehicle speed’s goes beyond the same limit and
having the unit on a previous STOP condition.
In this way we can assure that a STOP is not going to be reported any
time the vehicle’s speed falls below a low value but that a time-condition is
also required. We require the following two parameters:
1. An speed limit for determinating an STOP/START. This has to be
a low value but not so low that the vehicle has the chance of moving
extremely low and not having the reports.
2. A time condition. This value depends on what is an STOP situation
for us. A vehicle may be at rest waiting for a traffic light to change
and we may not want that situation to be reported as an STOP.
For our example let’s use some typical values that work on the majority
of configurations. For speed limit let’s use
8mph
and as time condition
2
minutes
. For our example let’s use for no particular reason event
30
for an
STOP situation and event
31
for the START.
5.7.1
Setting a low speed limit
Using the
GS
signal we configure the
8mph
limit:
>
SGS0310080
<
We chose speed limit
03
for no particular reason other than being free to be
used.
5.7.2
Start a counter
In a similar way as it was done on the
Speed Violation
example we now
create a silent event that starts a 2 minutes timer counter whenever the
vehicle’s speed falls off (opossite to the speed violation exp)
8mph
:
>
SED38SV0;S03-;ACT=SGC01TC00120
<
Note that we use counter
01
which is not being used by any other event
and event 38 that it is also free. Now any time the speed signal
S03
gets
false timer-counter
01
will start.
5.7.3
Create the STOP report
This event should trigger when the 2 minutes timer reaches its threshold
value. That is it, when
C01
becomes true, so we define the STOP event as:
>
SED30NV4;C01+
<
Notice that the event uses DA 4 and it is not silent, so the event is re-
ported to the AVL server.
121
Summary of Contents for Antares SB
Page 1: ......
Page 2: ...Antares SB TM GSM User s Manual FW 5 21 Digital Communications Technologies April 15 2008...
Page 37: ...2 1 POWER SUPPLY 35...
Page 38: ...2 1 POWER SUPPLY 36...
Page 42: ...2 5 CONNECTION DIAGRAMS 40...
Page 141: ...6 Unit s TAIP reference...
Page 191: ...6 32 XADM DIAGNOSTIC MESSAGE 189...
Page 228: ......
Page 229: ......