Over Speeding; Excessive Idling; Jamming; Dout Control Via Call - Teltonika FMB920 User Manual

5.8.2

Over Speeding

Scenario is activated and DOUT1 is ON, when vehicle speed exceeds parameter value.
Scenario is activated until current speed decreases below parameter value.
5.8.3

Excessive Idling

Scenario is activated and DOUT1 is ON, when vehicle stops for specific amount of time. You
can configure time it takes to turn on this scenario (Time to Stopped). Scenario is activated until
vehicle starts moving and keeps moving for amount of time that is configured. You can configure
time it takes to turn OFF this scenario (Time to Stopped).
5.8.4

Jamming

Scenario is activated and DOUT1 IS ON, then jamming is detected.
5.8.5

DOUT control via call

Scenario is activated and DOUT1 IS ON, when call is received from number who is in
authorized numbers list.
Call control
 When FMBXX is configured to control DOUT1 device waits incoming call from
configured secure number. If call is received FMBXX turns on DOUT1 for user
defined Duration timeout (s).
 DOUT1 can be turned off before Duration timeout (s) by DIN1 (DOUT deactivation
settings).
In all scenarios Digital Output can be controlled independent from scenario.
DOUT ON Duration parameter shows for how long DOUT is set on after scenario is
activated. DOUT OFF Duration parameter shows how much time should pass after DOUT is set
off till next event can be generated. These parameters must be configured in ms.
5.8.6

Trip settings

Trip window offers user to configure Trip feature. If Trip is enabled configuration of
parameters are enabled.
Start Speed – GPS speed has to be greater than the specified Start Speed in order to detect
Trip Start.
Ignition Off Timeout – timeout to wait if ignition was off, to detect Trip stop.
Continuous distance counting – Not or Continuous can be chosen. For this feature I/O
Odometer must be enabled.
If I/O Odometer is enabled and Continuous distance counting variable (Mode) is set to
Continuous, Trip distance is going to be counted continuously (from Trip start to Trip stop). This
value is written to I/O Odometer value field. When Trip is over and next Trip begins, Odometer
value is reset to zero. When the next trip starts counting continuously starts from the beginning
again.
If I/O Odometer is enabled and Continuous Distance Counting variable (Mode) is set
"Between Records", then the distance is going to be counted only between every record made.
This value is written to I/O Odometer value field and reset to zero every new record until Trip
37