Difference between revisions of "Immobilizer configuration explained"

From Wiki Knowledge Base | Teltonika Mobility
Line 44: Line 44:
 
*Input/Output Mode - Digital Output 2 selected.
 
*Input/Output Mode - Digital Output 2 selected.
 
|}
 
|}
If ''Depend On Ignition'' is '''Enabled''' and wiring is done following [https://wiki.teltonika-mobility.com/wikibase/images/3/3b/Immobilizer_scenario_scheme.png this] scheme, then you enable Immobilizer feature, DOUT stay at low level (0) and waits for ignition to be detected with DIN1. After ignition is detected (Ignition=1), DOUT switches to high level (1) preventing the starting of the engine and waits for authorization.
+
If ''Depend On Ignition'' is '''Enabled''' and wiring is done following [https://wiki.teltonika-mobility.com/wikibase/images/thumb/4/4b/Immobilizer-testing-scheme.png/500px-Immobilizer-testing-scheme.png this] scheme, then you enable Immobilizer feature, DOUT stay at low level (0) and waits for ignition to be detected with DIN1. After ignition is detected (Ignition=1), DOUT switches to high level (1) preventing the starting of the engine and waits for authorization.
  
 
After attaching iButton/RFID or detecting BLE beacon, DOUT switches back to low level (0) allowing the engine to be started fully. When ignition is switched OFF (Ignition=0), ''Ignition Off timeout'' starts countdown. After this countdown passes, functionality resets, meaning that after Ignition will be detected again (Ignition=1), DOUT will switch to high level (1) and ask for authorization again.
 
After attaching iButton/RFID or detecting BLE beacon, DOUT switches back to low level (0) allowing the engine to be started fully. When ignition is switched OFF (Ignition=0), ''Ignition Off timeout'' starts countdown. After this countdown passes, functionality resets, meaning that after Ignition will be detected again (Ignition=1), DOUT will switch to high level (1) and ask for authorization again.
Line 67: Line 67:
 
*Input/Output Mode - Digital Output 2 selected.
 
*Input/Output Mode - Digital Output 2 selected.
 
|}
 
|}
If ''Depend On Ignition'' is '''Disabled''' and wiring is done following [https://wiki.teltonika-mobility.com/wikibase/images/3/3b/Immobilizer_scenario_scheme.png this] scheme, then when you enable Immobilizer feature, DOUT '''immediately''' switches to high level (1) '''without waiting''' for Ignition.  
+
If ''Depend On Ignition'' is '''Disabled''' and wiring is done following [https://wiki.teltonika-mobility.com/wikibase/images/thumb/4/4b/Immobilizer-testing-scheme.png/500px-Immobilizer-testing-scheme.png this] scheme, then when you enable Immobilizer feature, DOUT '''immediately''' switches to high level (1) '''without waiting''' for Ignition.  
  
 
After attaching iButton/RFID or detecting BLE beacon, DOUT switches back to low level (0) and Ignition switches to high level (1) allowing the engine to be started fully.  
 
After attaching iButton/RFID or detecting BLE beacon, DOUT switches back to low level (0) and Ignition switches to high level (1) allowing the engine to be started fully.  

Revision as of 16:33, 11 February 2022

Main Page > FAQ > TFT100 FAQ > Immobilizer configuration explained


Alert.png

Functionality description is based on latest firmware - 55.01.02.Rev.01.

Immobilizer's functional purpose

Immobilizer prevents anyone from starting the transport without scanning an iButton key/RFID card with a reader or until device detects BLE Beacon first.

TFT100 Immobilizer.png



DOUT, that is selected under Output Control section will turn to High state (1) and block engine in such cases:

  • Ignition is detected (if Depend On Ignition is enabled);
  • Immediately after scenario is enabled in any priority (if Depend On Ignition is disabled).


If iButton key/RFID card is scanned with a reader or BLE beacon is detected, then DOUT switches to Low state (0) and the engine can be started.

If ignition will be turned OFF in authorized state, then after Ignition Off timeout configured value passes, DOUT will be set to High level (1) and authorization procedure will be required again.

Functionality examples

Example No. 1

Immobilizer example no 1.png

Configuration:

Features section

  • Immobilizer scenario - High priority;
  • Output Control - DOUT2;
  • iButton List Check - Enable;
  • Depend On Ignition - Enable;
  • Ignition Off Timeout - 30.


System section

  • Ignition Source - DIN1;
  • Input/Output Mode - Digital Output 2 selected.

If Depend On Ignition is Enabled and wiring is done following this scheme, then you enable Immobilizer feature, DOUT stay at low level (0) and waits for ignition to be detected with DIN1. After ignition is detected (Ignition=1), DOUT switches to high level (1) preventing the starting of the engine and waits for authorization.

After attaching iButton/RFID or detecting BLE beacon, DOUT switches back to low level (0) allowing the engine to be started fully. When ignition is switched OFF (Ignition=0), Ignition Off timeout starts countdown. After this countdown passes, functionality resets, meaning that after Ignition will be detected again (Ignition=1), DOUT will switch to high level (1) and ask for authorization again.

Example No. 2

Immobilizer example no 2.png

Configuration:

Features section

  • Immobilizer scenario - High priority;
  • Output Control - DOUT2;
  • iButton List Check - Enable;
  • Depend On Ignition - Disable;
  • Ignition Off Timeout - 30.


System section

  • Ignition Source - DIN1;
  • Input/Output Mode - Digital Output 2 selected.

If Depend On Ignition is Disabled and wiring is done following this scheme, then when you enable Immobilizer feature, DOUT immediately switches to high level (1) without waiting for Ignition.

After attaching iButton/RFID or detecting BLE beacon, DOUT switches back to low level (0) and Ignition switches to high level (1) allowing the engine to be started fully.

When iButton/RFID is removed from the reader and Ignition is switched OFF, Ignition Off timeout parameter is considered to be RFID Off timeout and after configured time passes, DOUT switches back to high level (1) and ignition switches to low level (0).

Example No. 3

Immobilizer example no 3.png

Configuration:

Features section

  • Immobilizer scenario - High priority;
  • Output Control - DOUT2;
  • iButton List Check - Enable;
  • Depend On Ignition - Disable;
  • Ignition Off Timeout - 30.


System section

  • Input/Output Mode - Digital Output 2 selected.

If Depend On Ignition is Disabled and wiring is done following scheme below (without using DIN wire for Ignition), then when you enable Immobilizer feature, DOUT immediately switches to high level (1).

After attaching iButton/RFID or detecting BLE beacon, DOUT switches back to low level (0).

When iButton/RFID is removed from the reader, Ignition Off timeout parameter is considered to be RFID Off timeout and after configured time passes, DOUT switches back to high level (1).

Immobilizer scheme for example no 3.png