Trip Settings - Teltonika FMA110 User Manual

event is detected and DOUT is activated it can be deactivated with iButton. If iButton list is not
empty, then digital output can be deactivated only with authorized iButton.
 Immobilizer
If Dout Control is disabled, scenario will only generate events without digital output
activation. If Dout Control is enabled DOUT1/DOUT2 (optional) turns ON if Ignition turns ON
(configured Ignition Source =1). After iButton ID is read (any iButton is attached), DOUT1/DOUT2
turns OFF. After iButton identification, Ignition (configured Ignition Source) can be turned OFF
(configured Ignition Source =0) for no longer than 30 seconds, otherwise immobilizer must be
repeated. If iButton list checking parameter is enabled, authorization will be successful only if
attached iButton is specified in the iButton list.
iButton detection

If iButton is read, scenario activates configured DOUT for 500 ms. Second activation will be
available only when iButton I/O element value goes back to 0, or another iButton is read.

5.14.2 Trip settings

Trip window offers user to configure Trip feature. If Trip is enabled following parameters
are configurable:
 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 (configured Ignition Source) was off, to
detect Trip stop.
 Continuous distance counting – Not or Continuous can be chosen. For this feature I/O Trip
distance must be enabled.
If I/O Trip distance is enabled and Continuous distance counting variable 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 Trip distance value field. When Trip is over and next Trip begins, Trip
distance value is reset to zero. When the next trip starts counting continuously starts from the
beginning again.
If I/O Trip distance is enabled and Continuous Distance Counting variable is set "Not", then
the distance is going to be counted only between every record made. This value is written to I/O
Trip distance value field and reset to zero every new record until Trip stops. If later all Trip
distance values are summed up manually, the user gets the distance driven during the whole
period of the Trip.
40