Changes

==Eco/Green Driving==

==Eco/Green Driving==

[[Image:EcoGreen_Driving.gif|{{{general|size}}}|right]]<br>

[[Image:EcoGreen_Driving.gif|{{{general|size}}}|right]]

When vehicle parameters exceed the values of ''Max Acceleration'', ''Max Braking'' or ''Max Cornering'' parameters, the scenario is activated: a record is generated and digital output status is changed to 1 when configured. You can configure all three parameters in m/s² units. Scenario is activated until current Acceleration, Braking or Cornering value decreases below the set parameter value.<br/>Parameters used with ''Eco/Green Driving'' functionality are given in a table below.

When vehicle parameters exceed the values of ''Max Acceleration'', ''Max Braking'' or ''Max Cornering'' parameters, the scenario is activated: a record is generated, and the digital output status is changed to 1 when configured. You can configure all three parameters in m/s² units. The scenario is activated until the current Acceleration, Braking, or Cornering value decreases below the set parameter value.<br />Parameters used with ''Eco/Green Driving'' functionality are given in a table below.

<table class="nd-othertables" style="width: 68%;">

<table class="nd-othertables" style="width: 68%;">

     </tr>

     </tr>

{{{txt_advanced|<tr>

{{{txt_advanced|<tr>

         <td style="width: 8%; text-align:left">[[{{{model|FMU1YX}}} Features settings#Advanced Eco Driving|Advanced Eco Driving]]</td>

         <td style="width: 8%; text-align:left">[[{{{model|FMB1YX}}} Features settings#Advanced Eco Driving|Advanced Eco Driving]]</td>

         <td style="width: 8%; text-align:left">When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. More details about this option is decribed below.</td>

         <td style="width: 8%; text-align:left">When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. More details about this option is decribed below.</td>

     </tr>}}}

     </tr>}}}

</table>

</table>

From 03.25.14.Rev.03 base firmware version new '''[[FMB120_Parameter_list|parameter]]''' has been added (Eco Driving Maximum and Eco Driving Average) to '''[[FMT100]]''' device. This parameter is '''enabled''' by default.  

From 03.25.14.Rev.03 base firmware version new '''[[FMB120_Parameter_list|parameter]]''' has been added (Eco Driving Maximum and Eco Driving Average) to '''[[FMT100]]''' device. This parameter is '''enabled''' by default.  

When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. When enabled, device does not send Green Driving value IO element '''[[FMB120_AVL_ID|254]]'''.

When this parameter is enabled device uses an advanced Eco Driving algorithm and sends different IO (maximum, average) elements instead of IO to server. When enabled, device does not send Green Driving value IO element '''[[FMT100_Teltonika_Data_Sending_Parameters_ID|254]]'''.

<table class="nd-othertables" style="width: 68%;">

<table class="nd-othertables" style="width: 68%;">

  <tr>

  <tr>

         <td style="width: 8%; text-align:left;">If Eco/Green driving is enabled and accelerometer is selected as the data source, enabling Eco Driving Maximum will cause records with Eco Driving event Maximum value to be saved and send to the server.</td>

         <td style="width: 8%; text-align:left;">If Eco/Green driving is enabled and accelerometer is selected as the data source, enabling Eco Driving Maximum will cause records with Eco Driving event Maximum value to be saved and send to the server.</td>

     </tr>

     </tr>

</table>

</table>}}}

}}}

===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|FMU1YX}}}]] 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>

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 records to get more precision when displaying data.{{{text_dout|<br/>}}}<br/><youtube>RlkJELdVGRs</youtube>

===Auto calibration===

===Auto calibration===

----

----

The auto-calibration process is following:

The auto-calibration process is following:

# The vehicle is stopped.

 

# There is a straight road ahead.

#The vehicle is stopped.

# Send SMS ''"auto_calibrate:set"'' to the {{{model_2|FMU}}} device.

#There is a straight road ahead.

# Accelerate to >30 km/h for 5 sec.

#Send SMS ''"auto_calibrate:set"'' to the {{{model_2|FMB}}} device.

# {{{model_2|FMU}}} will send a response when calibration is completed successfully.

#Accelerate to >30 km/h for 5 sec.

#{{{model_2|FMB}}} will send a response when calibration is completed successfully.

 

Calibration is saved to internal flash memory, which means it will stay after a reset.

Calibration is saved to internal flash memory, which means it will stay after a reset.

To check auto-calibration status send a following short text message to the {{{model_2|FMU}}} device: ''"auto_calibrate:get"''.

To check auto-calibration status send a following short text message to the {{{model_2|FMB}}} device: ''"auto_calibrate:get"''.

==Over Speeding==

==Over Speeding==

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.

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. Configurable parameters:

[[Image:Over_Speeding.gif|{{{general|size}}}|left]] <br /><br /><br /><br />

[[Image:Over_Speeding.gif|{{{general|size}}}|right]]  

<br /><br />

<br />

<br /><br />

<br /><br />

*Output control – available scenario settings for module Digital output activation/deactivation

*DOUT ON/OFF duration – a value in seconds, for how long {{{text_dout|DOUT1/DOUT2}}} should be active or inactive.

<br /><br /><br /><br /><br />

[[Image:Jamming.gif|{{{general|size}}}|right]]

[[Image:Jamming.gif|{{{general|size}}}|right]]

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]'''

 

 

{{{dout_control_via_call_feature|==DOUT Control Via Call==

 

{{{dout_control_via_call_feature|== DOUT Control Via Call==

[[Image:DOUT_Control_Via_Call.gif|{{{general|size}}}|right]]

[[Image:DOUT_Control_Via_Call.gif|{{{general|size}}}|right]]

The scenario is activated and digital output is ON when a call is received from a number which is on the authorized numbers list.<br/>

The scenario is activated and digital output is ON when a call is received from a number that is on the authorized numbers list.<br/>

Call control functionality is the following:

Call control functionality is the following:

* When [[{{{model|FMB1YX}}}]] is configured to control {{{text_dout|DOUT1/DOUT2}}} the device waits for an incoming call from a configured secure number. If a call is received [[{{{model|FMB1YX}}}]] turns on {{{text_dout|DOUT1/DOUT2}}} for a user defined ''Duration Timeout''. If duration timeout set to "0" {{{text_dout|DOUT1/DOUT2}}} will be OFF.

* When [[{{{model|FMB1YX}}}]] is configured to control {{{text_dout|DOUT1/DOUT2}}} the device waits for an incoming call from a configured secure number. If a call is received [[{{{model|FMB1YX}}}]] turns on {{{text_dout|DOUT1/DOUT2}}} for a user defined ''Duration Timeout''. If duration timeout set to "0" {{{text_dout|DOUT1/DOUT2}}} will be OFF.

* {{{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 the maximum value (2147483647) which is about 68 years.}}}

}}}

{{{immobilizer_feature|==Immobilizer==

{{{immobilizer_feature|==Immobilizer==

[[Image:Immobilizer.gif|{{{general|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 the ''iButton List Check'' parameter is enabled, the authorization will be successful only if the attached iButton is specified in the iButton list.<br/>

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, 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.<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 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.

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.

{{{ibutton_feature|==iButton Read Notification==

{{{ibutton_feature|==iButton Read Notification==

[[Image:FMB120_iButton_Read_Notification.png|375px|size|right]]

iButton Read Notification parameters:

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}}}

*Output control – available scenario settings for module Digital output activation/deactivation

<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>}}}

*DOUT ON/OFF duration – a value in seconds, for how long {{{text_dout|DOUT1/DOUT2}}} should be active or inactive.

*iButton List checking - parameter configures that device reads the iButton ID from list or not.

*Depend on Ignition - Output will be triggered only if ignition is off

<br/><br/>}}}

==GNSS Fuel Counter==

==GNSS Fuel Counter==

[[Image:FMB120_GNSS_Fuel_Counter.png|375px|size|right]]

[[Image:GNSS_Fuel_Counter.gif|{{{general|size}}}|right]]

 

 

''Correction coefficient'' is used to correct every value of fuel consumption which is sent to the server through an expression of ((Used Fuel) * ''Correction coefficient''). By default, it is 1, with minimum and maximum values of accordingly 0.01 and 2. For example, when the correction coefficient is 1 and [[{{{model|FMB1YX}}}]] calculates that the amount of used fuel over 35 m distance is 20 ml, the value of 20 ml will be sent to the server, and if correction coefficient is 1.2, the value of 20 * 1.2 = 24 ml will be sent to the server.

# ''Correction coefficient'' is used to correct every value of fuel consumption which is sent to the server through an expression of ((Used Fuel) * ''Correction coefficient''). By default it is 1, with minimum and maximum values of accordingly 0.01 and 2. For example, when correction coefficient is 1 and [[{{{model|FMU1YX}}}]] calculates that the amount of used fuel over 35 m distance is 20 ml, the value of 20 ml will be sent to the server, and if correction coefficient is 1.2, the value of 20 * 1.2 = 24 ml will be sent to the server.

# ''Fuel Consumption on Idling'' is used to calculate fuel consumption when the ignition is on, but the vehicle is stationary. The consumption value is 1 l/h by default, with a minimum and maximum of accordingly 0 and 5 l/h. This parameter is less than 1.0 l/h for almost all diesel cars and is equal to about 1.5 – 2.0 l/h for gasoline cars.

==DOUT Control Via Ignition==

{{{dout_control_via_ignition_feature|==DOUT Control Via Ignition==

[[Image:DOUT Control via Ignition.png|{{{dout_control_via_ignition|size}}}|right]]

[[Image:DOUT_Control_Via_Ignition.gif|{{{dout_control_via_ignition|size}}}|right]]

This feature allows direct control of DOUT by configured ignition source status. When enabled, the function will start to monitor ignition status, and once the ignition changes state from On to Off after configured Ignition Off timeout, selected DOUT (Digital Output) will be turned On.<br/><br/>

This feature allows direct control of DOUT by configured ignition source status. When enabled, the function will start to monitor ignition status, and once the ignition changes state from On to Off after configured Ignition Off a timeout, selected DOUT (Digital Output) will be turned On.<br/><br/>

Turning DOUT Off is possible with enough voltage applied to the configured DIN (Digital Input). Voltage requirements: DIN1 – 7.5V, DIN2-4 – 2.5V.<br/><br/>

Turning DOUT Off is possible with enough voltage applied to the configured DIN (Digital Input). Voltage requirements: DIN1 – 7.5V, DIN2-4 – 2.5V.<br/><br/>

         <td style="width: 8%; text-align:left">Duration (in seconds) after which DOUT is turned on, when ignition is turned off</td>

         <td style="width: 8%; text-align:left">Duration (in seconds) after which DOUT is turned on, when ignition is turned off</td>

     </tr>

     </tr>

</table>

</table>}}}

==Ignition ON Counter==

==Ignition ON Counter==

 

'''Ignition ON Counter''' scenario counts the time spent with the ignition in the resolution of seconds. <br>

'''Ignition ON Counter''' scenario counts the time spent with the ignition in the resolution of seconds. <br>

It is possible to configure a starting value of the counter. Maximum value: '''2147483647''' seconds or 596523.235 hours

It is possible to configure a starting value of the counter. Maximum value: '''2147483647''' seconds or 596523.235 hours

'''NOTE THAT''', when entering a starting value, the value must be in seconds!

'''NOTE THAT''', when entering a starting value, the value must be in seconds!

Example of Ignition On Counter '''I/O''' element:

Example of Ignition On Counter '''I/O''' element:

[[image:IgnitionOnCounter.gif]]

[[File:InvertedDout.png|thumb|left|500px]]

 

 

 

 

 

[[File:Alert.png|50px]] <b>Available from Firmware version: [[ {{{model|}}}_firmware_errata|3.27.07.Rev.00]] </b>