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

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

5.9. IMPROVING THE PERIODIC REPORT
2. If you receive a confirmation of this message the turn off process
has initiated. Wait for event 13 to report. When event 13 report is
received it means that the given time/speed condition met and the
vehicle’s engine has been turned off.
3. To restore the ignition on the vehicle simply deactivate output 4:
>
SSSXP40
<
The safe engine turn off process can be skipped. Although is highly unrec-
ommended, at any time you can directly drive output 4 high making the
unit turn the engine off without any previous time/speed safe condition.
Driving a vehicle’s engine OFF without knowing its state is ex-
tremely dangerous.
Warning:
5.9 Improving the periodic report
The example we have been working so far uses a time-only criteria for the
periodic tracking report (event
37
). This report is being generated every
5 minutes 24/7. This includes a lot of useless reports that show the same
location and conditions when the vehicle remains stationary. A better ap-
proach is to use all three parameters that define the
Time And Distance
signal.
Our actual definition of the T&D signal
8
, which is the signal that trig-
gers the periodic tracking event
37
is:
>
STD80300
<
As you can check with the
TD
message definition given on the TAIP ref-
erence, this is a time-only criterion which causes the
TD8
signal to get high
on a 5 minutes basis. To achieve a better reporting event, the T&D criterion
has to include all three configuration parameters:
• Minimum time.
•
Distance threshold.
•
Maximum time.
These definitions depend strongly of each user’s situation and it is a matter
of cost vs frequency of report.
Typical values for vehicles moving in a city are:
•
Minimum time between reports: 2 minutes .
129