Template:FMB Features settings: Difference between revisions

← Older edit

VisualWikitext

@@ Line 175: / Line 175: @@
 }}
 {{#switch: {{{model}}}
-| FMT100 =
+|FMC880 |FMM880 |FMC800 |FMM800| FMT100 =
-| #default =
+|#default =
-{{{immobilizer_feature|==Immobilizer==
+==Immobilizer==
+[[File:Immobilizer1.png|right]]
+'''Note:''' Immobilizer scenario requires a device with 1-Wire support or at least 1 DOUT and BLE support.
-[[File:Immobilizer1.png|{{{general|size}}}|right]]
+===Function===
+Immobilizer scenario purpose is to prohibit an unauthorized exploitation of a vehicle. This is accomplished by DOUT controlling the relay, which in turn controls the starter or fuel pump.
-If ''DOUT Control'' is disabled, the scenario will only generate events without digital output activation. If ''DOUT Control'' is enabled {{{text_dout|DOUT1/DOUT2}}} turns ON if ignition turns ON (''Ignition Source'' is configured to 1). After any iButton ID (or RFID card) is attached, {{{text_dout|DOUT1/DOUT2}}} turns OFF. After iButton identification configured ''Ignition Source'' can be turned OFF (''Ignition Source'' is configured to 0) for no longer than 30 seconds, otherwise, the immobilizer must be repeated. If the ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in the iButton list.
+When attempting to start the vehicle:
-<br/><br/>
+*Selected control '''DOUT''' turns high when ignition is detected, preventing the vehicle from starting.
-The ignition off timeout parameter is used to set the duration after which authorization is activated when the ignition is turned off. For example, if the Ignition off timeout is set to 30 seconds when the driver turns the ignition off, he has 30 seconds until the immobilizer security check turns on again. In other words, if the driver turns off the ignition and turns it back on in less than 30 seconds, then he will not have to attach the iButton to the reader again.
+*If '''iButton''' is attached or '''BLE beacon''' is detected, then '''DOUT turns low''' and it is possible to start vehicle.
-<br/><br/>
-The No Authentication Timeout sets a time limit for how long the vehicle can stay in the "Wait Authorization" state without receiving any authorization. If this timeout is set (non-zero) and the time spent in the "Wait Authorization" state exceeds the configured value, the system automatically moves to the "Authorized" state. This prevents the vehicle from waiting indefinitely and ensures it can proceed with operations after a set time.
-If value is entered zero - function "No Authentication timeout" is not activated.
+===Authorization===
-<br/><br/>
+In case if iButton list check is enabled, then device checks for read iButton match in iButton list or if Beacon list check enabled, checks for match in Beacon list (Beacon Detection has to be set to Configured), or if both enabled checks in both lists. If match is not found, then driver will not be able to use vehicle. If driver did not authorize and ignition is turned off, '''after 25 seconds DOUT will be set to idle state'''.
-From the firmware version '''[https://wiki.teltonika-gps.com/view/{{{model|FMB1YX}}}_firmware_errata 03.25.14]''' iBeacon authentication was introduced. iBeacon authentication works in the same way as iButton authentication. To use authorized iBeacons, the iBeacon list should be filled in the device configurator. Instructions how to list iBeacons in FMB devices can be found '''[https://wiki.teltonika-gps.com/view/{{{model|FMB1YX}}}_Beacon_List here]'''.
-By using iBeacon authorization, the immobilizer feature can be used with devices that don't have a 1-wire data connection available.
+From firmware version '''''04.00.00.Rev.13''''' and above, the "Authorization ID List Checking" option '''None''' was removed as part of a security improvement. Devices now require selecting 1-Wire, RFID (for RS232-capable devices), or Beacons. If the Authorization ID list is empty, the behavior is equivalent to the previous '''None''' option - any '''iButton, RFID card, or Beacon disables the Immobilizer'''.
-<br/><youtube>gjuiJjAejWU</youtube>
-From firmware version '''04.00.00.Rev.13 and above''', the "Authorization ID List Checking" option “None” was removed as part of a security improvement. Devices now require selecting 1-Wire, RFID (for RS232-capable devices), or Beacons. If the Authorization ID list is empty, the behavior is equivalent to the previous “None” option - any iButton, RFID card, or Beacon disables the Immobilizer.
+'''Note:''' iButton list or Beacon list must be configured for proper function.  When using Beacon list check, Beacon Detection should be set to Configured. If Beacon Detection is set to '''All''', any visible beacon will be able to turn off the immobilizer.
-}}}
+{{#switch: {{{model}}}
+|#default =
+|FMB125 |FMC125 |FMM125 |FMB225 |FMC225 =
+===Alcotest Check===
+'''Note:''' This functionality configuration is visible only when RS232 mode Mercury C4 is configured.
+When Alcotest Check functionality is enabled, immobilizer will authorize only when data is received from a breathalyzer. The breathalyzer result is sent in passive mode and any alcohol value will stop the immobilize authorization.
+In active mode, the device checks if the result does not exceed the configured BCA Threshold value. The breathalyzer result is held for 3 minutes. After the 3-minute timeout expires, a new alcotest result has to be received to authorize a driver.
+iButton/Beacon function:
+*When iButton/Beacon list is not configured, the driver can only be authorized with a breathalyzer.
+*When iButton/Beacon list is configured, the driver can be authorized only when an authorized iButton/Beacon is attached and no alcohol was found.
+'''Note:''' Devices that do not have RS232 will have support for 1-Wire and Beacon only. Device that do not have RS232 and 1-Wire will have support for Beacon Only. Parameter default value has been changed from 0 to 9. After firmware update it should change it’s value automatically if it was set to 0 before.
+When Alcotest Check functionality is disabled, immobilizer works like usual. Alcotest check has new eventual IO element that is generated each time new breathalyzer result is received. If SMS event is configured, then SMS will be sent to configured number. IO value consists of alcotest result and test mode. IO elements size is 2 bytes. First 14 MSB bits are for alcotest result, and last 2 for test mode. Alcotest value is in relims (‰) multiplied by 1000.
+Test mode values:
+*0 – Passive
+*1 – Active
+Example Data: alcotest result value is 0x0111 → 0b0000000100010001.
+<table class="nd-othertables" style="width: 80%;">
+ <tr>
+        <th style="width: 10%; text-align:left; vertical-align:left; color:black">Bits</th>
+        <th style="width: 20%; text-align:left; vertical-align:left; color:black">Binary Value</th>
+        <th style="width: 50%; text-align:left; vertical-align:left; color:black">Description</th>
+    </tr>
+    <tr>
+        <td style="width: 10%; text-align:left;">15..2</td>
+        <td style="width: 20%; text-align:left">00000001000100</td>
+        <td style="width: 50%; text-align:left">0x44 = 68 → 68/1000 = 0.068‰</td>
+    </tr>
+    <tr>
+        <td style="width: 10%; text-align:left;">1..0</td>
+        <td style="width: 20%; text-align:left">01</td>
+        <td style="width: 50%; text-align:left">0x01 = 1 → Active mode</td>
+    </tr>
+</table>
 }}
+===Immobilizer Authorization Timeout===
+The authorization timeout is a function that ensures the vehicle remains authorized for a certain period of time after a successful authorization. If the timeout expires, the vehicle is considered unauthorized.
+When the vehicle is authorized, the time is stored in the device. This marks the start of the authorization period. On subsequent authorizations, the code calculates the time difference between the current time and the stored authorization time. If the difference is greater than the specified authorization timeout (IgnitionOffTmo, parameter ID = 60068), it means that the authorization period has expired, and the vehicle will be considered unauthorized.
+This ensures that the vehicle remains authorized only for a specific duration. Once that duration elapses, the vehicle is required to go through the authorization process again.
+===No Authentication Timeout===
+No Authentication Timeout is a configurable duration that specifies the maximum allowed time without any authorization during the '''Wait Authorization''' state. If none of these authorization criteria are met, the system needs a way to handle situations where the vehicle remains in the '''Wait Authorization''' state for an extended period without any authorization. If the '''No Authentication Timeout''' value is configured to a non-zero value, the code tracks the time elapsed since the vehicle entered the '''Wait Authorization''' state. If this elapsed time exceeds the parameter value, it triggers an action to automatically transition the system to an '''Authorized''' state.
+If the specified timeout duration is reached, the system assumes authorization to avoid prolonged waiting times and allows the vehicle to proceed with authorized operations.
+===Authorization Timeout Limit===
+Authorization Timeout Limit Configures the time window for successful authorization. If authorization fails within this period, an unauthorized event record is generated. Other record generation is not affected.
+'''Note:''' Immobilizer records are only created if ignition is ON.
+===Sleep Mode Considerations===
+Immobilizer scenario can block device from going to sleep mode when '''Ignition Off timeout''' ('''''60068''''') is configured with higher timeout than '''Sleep Mode Timeout''' ('''''103''''') and when Immobilizer '''Scenario Settings''' and '''Output Control''' are configured. In such case the device will go to sleep mode after Immobilizer '''Ignition Off timeout''' passes.
+}}
 {{{ibutton_feature|==iButton Read Notification==
 [[Image:IButton_Read_Notification.gif|{{{general|size}}}||right]]

Latest revision as of 10:39, 28 May 2026