DCT Antares SB, Руководство пользователя

Страница: 127 / 238

5.8. SAFE ENGINE TURN OFF
4. We can also add an event to report when the output is actually set (i.e.
the ignition is cut), let’s use event code
13
for this. We continue working
on the same example worked so far.
5.8.1 Create the speed limit
We set 15mph on the
S01
limit:
>
SGS0110150
<
5.8.2 Creating a timer
We only want to cut the engine after the unit is instructed to do so. To do
this we use a
User Signal . This type of signal gets high or low whenever we
tell it to. For this example let us use user signal 00 (
U00
). Now we create a
silent event that starts a 16 seconds timer whenever the vehicle’s speed falls
off 15mph AND the user signal is set, that it is, when someone activates the
user signal to indicate that the safe engine turn off process is to start:
>
SED14SV0;S01!U00&+;ACT=SGC02TC00016
<
We use event 14 and counter 02 for no particular reason.
5.8.3 Cutting the ignition
Now we create a non-silent event that sets the ignition OFF when the pre-
vious set counter reaches its threshold value of 16 seconds:
>
SED13NV5;C02U00&+;ACT=SSSXP41
<
The DA of this event is 5 meaning that the report of ignition cut-off will be
sent to the AVL sever and the Phone Number 912345678.
Now any time someone activates the user signal 00 and after a low-speed
+ time condition, event 13 will set output 4 ON cutting the ignition of the
vehicle. But as with the previous examples something is missing.
5.8.4 Stopping the counter
As it was done on the other examples, we need to stop the counter when-
ever the speeds goes beyond the limit, this to assure that if the time/speed
condition is violated the engine won’t be turned off:
>
SED15SV0;S01+;ACT=SGC02U
<
5.8.5 Restore the user signal
The only thing left to do is to restore the user signal so any time later when
the ignition is restored the safe engine turn off mechanism is not triggered
again without any user command.
>
SED16SV0;E13+;ACT=SSSU000
<
125