Changes

no edit summary
Line 81: Line 81:  
===Data output===
 
===Data output===
 
----
 
----
Data from accelerometer/GPS are continuously monitored and processed and are used to decide whether a harsh event has occurred. If either of three cases is satisfied, an event is generated and a record is saved and sent to the server ([[{{{model|FMB1YX}}}]] must be properly configured in order to send the record). Event value is multiplied by 100 before sending/saving record to get more precision when displaying data.{{{text_dout|<br/>{{{dout|info}}}}}}<br/><br/><youtube>RlkJELdVGRs</youtube>
+
Data from accelerometer/GPS are continuously monitored and processed and are used to decide whether a harsh event has occurred. If either of three cases is satisfied, an event is generated and a record is saved and sent to the server ([[{{{model|FMB1YX}}}]] must be properly configured in order to send the record). Event value is multiplied by 100 before sending/saving record to get more precision when displaying data.{{{text_dout|<br/>}}}<br/><youtube>RlkJELdVGRs</youtube>
    
===Auto calibration===
 
===Auto calibration===
Line 97: Line 97:     
==Over Speeding==
 
==Over Speeding==
  −
[[Image:{{{model|FMB1YX}}}_Over_Speeding.png|{{{over_speed|size}}}|right]]
  −
  −
When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}.<br />Scenario is active until detected speed decreases below the set parameter value.<br />{{{over_speeding_dout|info}}}
  −
<br /><br /><br /><br /><br /><br /><br /><br /><br />
  −
         +
When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated{{{text_dout| and digital output status is changed to 1 when configured}}}.<br />Scenario is active until detected speed decreases below the set parameter value.
 +
[[Image:Over_Speeding.gif|{{{general|size}}}|left]] <br /><br /><br /><br />
 +
<br /><br />
 +
<br /><br />
 +
<br /><br />
 
<br /><br />
 
<br /><br />
  −
   
<br /><br />
 
<br /><br />
    
==Jamming==
 
==Jamming==
   −
[[Image:{{{model|FMB1YX}}}_Jamming.png|frameless|{{{jamming|size}}}|right]]
+
[[Image:Jamming.gif|{{{general|size}}}|right]]
    
When a device detects GSM signal jamming, it activates the Jamming scenario. The device then starts a configurable timeout before responding that is intended to reduce false positives. After the timeout ends, the device generates an event record and digital output status is changed to 1 when configured If the device regains GSM signal before the countdown ends, no event will be generated and output will not be controlled. This Digital Output activation can be used to trigger measures to disrupt potential thieves using GSM signal jamming to steal your vehicle.  
 
When a device detects GSM signal jamming, it activates the Jamming scenario. The device then starts a configurable timeout before responding that is intended to reduce false positives. After the timeout ends, the device generates an event record and digital output status is changed to 1 when configured If the device regains GSM signal before the countdown ends, no event will be generated and output will not be controlled. This Digital Output activation can be used to trigger measures to disrupt potential thieves using GSM signal jamming to steal your vehicle.  
Line 131: Line 128:     
For a more visual explanation, take a look at the video made by Teltonika explaining the use-case of Jamming Detection: '''[https://www.youtube.com/watch?v=otQd34WqL54 Teltonika Jamming Detection scenario]'''
 
For a more visual explanation, take a look at the video made by Teltonika explaining the use-case of Jamming Detection: '''[https://www.youtube.com/watch?v=otQd34WqL54 Teltonika Jamming Detection scenario]'''
  −
  −
{{{jamming_dout|info}}}
  −
<br /><br /><br />{{{template_link|}}}
      
{{{dout_control_via_call_feature|==DOUT Control Via Call==
 
{{{dout_control_via_call_feature|==DOUT Control Via Call==
   −
[[Image:{{{model|FMB1YX}}}_DOUT_Control_Via_Call.png|{{{dout_control_via_call|size}}}|right]]
+
[[Image:DOUT_Control_Via_Call.gif|{{{general|size}}}|right]]
    
Scenario is activated and digital output is ON when call is received from a number which is on the authorized numbers list.<br/>
 
Scenario is activated and digital output is ON when call is received from a number which is on the authorized numbers list.<br/>
Line 145: Line 138:  
* {{{text_dout|DOUT1/DOUT2}}} can be turned off by ''Duration Timeout'' or by {{{text_din|digital input 1, digital input 2 or digital input 3}}}.
 
* {{{text_dout|DOUT1/DOUT2}}} can be turned off by ''Duration Timeout'' or by {{{text_din|digital input 1, digital input 2 or digital input 3}}}.
 
* {{{text_dout|DOUT1/DOUT2}}} will always be ON if, for example, DOUT deactivation is set to DIN1, but DIN1 will be never turned ON, or when duration timeout is set to maximum value (2147483647) which is about 68 years.
 
* {{{text_dout|DOUT1/DOUT2}}} will always be ON if, for example, DOUT deactivation is set to DIN1, but DIN1 will be never turned ON, or when duration timeout is set to maximum value (2147483647) which is about 68 years.
{{{dout_control_dout|info}}}}}}
+
}}}
 
  −
<br />
      
{{{immobilizer_feature|==Immobilizer==
 
{{{immobilizer_feature|==Immobilizer==
   −
[[Image:{{{model|FMB1YX}}}_Immobilizer.png|{{{immobilizer|size}}}|right]]
+
[[Image:Immobilizer.gif|{{{general|size}}}|right]]
   −
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 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, immobilizer must be repeated. If ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in iButton list.<br/>{{{immobilizer_dout|info}}}
+
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 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, immobilizer must be repeated. If ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in iButton list.<br/>
 
<br/><br/>
 
<br/><br/>
 
Ignition off timeout parameter is used to set the duration after which authorization is activated, when the ignition is turned off. For example, if 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.
 
Ignition off timeout parameter is used to set the duration after which authorization is activated, when the ignition is turned off. For example, if 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.
Line 165: Line 156:  
{{{ibutton_feature|==iButton Read Notification==
 
{{{ibutton_feature|==iButton Read Notification==
   −
[[Image:{{{model|FMB1YX}}}_iButton_Read_Notification.png|{{{ibutton_read_notification|size}}}|right]]
+
This functionality allows user to see when iButton is read. {{{text_dout|DOUT1/DOUT2}}} turns on for a configured duration and after DOUT ON duration ends {{{text_dout|DOUT1/DOUT2}}} does not turn on even if iButton is left attached.
 
+
[[Image:IButton_Read_Notification.gif|{{{general|size}}}|left]]<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>}}}
This functionality allows user to see when iButton is read. {{{text_dout|DOUT1/DOUT2}}} turns on for a configured duration and after DOUT ON duration ends {{{text_dout|DOUT1/DOUT2}}} does not turn on even if iButton is left attached.<br/>{{{ibutton_dout|info}}}
  −
<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>}}}
      
==GNSS Fuel Counter==
 
==GNSS Fuel Counter==
   −
[[Image:{{{model|FMB1YX}}}_GNSS_Fuel_Counter.png|{{{gnss_fuel_counter|size}}}|right]]
+
[[Image:GNSS_Fuel_Counter.gif|{{{general|size}}}|right]]
    
#To configure ''Fuel Counter'' parameters use fuel consumption norms which are presented in the technical documentation of the vehicle. By default speeds for these fuel consumption norms are: City – 30 km/h, Average - 60 km/h, Highway - 90 km/h. These values can be changed.
 
#To configure ''Fuel Counter'' parameters use fuel consumption norms which are presented in the technical documentation of the vehicle. By default speeds for these fuel consumption norms are: City – 30 km/h, Average - 60 km/h, Highway - 90 km/h. These values can be changed.

Navigation menu