Wiki Knowledge Base | Teltonika GPS

Changes

Template:FMC Features settings (view source)

Revision as of 12:27, 26 March 2024

7,056 bytes added ,  26 March
no edit summary
Line 1: Line 1:  
==Eco/Green Driving==
 
==Eco/Green Driving==
   −
[[Image:EcoGreen_Driving.gif|{{{general|size}}}|right]]
+
[[Image:eco_green_driving_calculator.PNG|{{{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 the digital output status is changed to 1 when configured. You can configure all three parameters in m/s<sup>2</sup> 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.
 
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<sup>2</sup> 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: 65%;">
 
  <tr>
 
  <tr>
 
         <th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
 
         <th style="width: 10%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
Line 23: Line 23:  
     </tr>
 
     </tr>
 
<tr>
 
<tr>
−
         <td style="width: 8%; text-align:left">Max Cornering Acceleration</td>
+
         <td style="width: 8%; text-align:left">Calculate</td>
−
         <td style="width: 8%; text-align:left">Value which can be reached while cornering without triggering harsh cornering event.</td>
+
         <td style="width: 8%; text-align:left">Setting which can be used to create customised calculations for Max Acceleration, Max Braking and Max Cornering based on the users vehicle. PLEASE NOTE: calculations will show as 0.5 until vehicle weight and power number will not be inserted.</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">Select Drive Type</td>
 +
        <td style="width: 8%; text-align:left">Based on vehicle's drive type, e.g. front-wheel drive, rear-wheel drive, all-wheel drive</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">Select Transmission Type</td>
 +
        <td style="width: 8%; text-align:left">Based on vehicle's transmission type e.g. manual, automatic, dual clutch (DCT)</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">Select Driving Mode</td>
 +
        <td style="width: 8%; text-align:left">This is used to set low, medium and high settings for early acceleration. Sensitive - for most restrictive settings, for example carrying cargo. Normal - medium restrictive settings, used for normal day to day operations. Insentitive Clutch - least restrictive settings for drivers</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">Enter Vehicle Weight (kg)</td>
 +
        <td style="width: 8%; text-align:left">Actual weight of the car or the one registered in the logbook (required)</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">Enter Vehicle Power (kw)</td>
 +
        <td style="width: 8%; text-align:left">Actual engine power of the vehicle, same as registered in the logbook (required)</td>
 
     </tr>
 
     </tr>
 
<tr>
 
<tr>
Line 99: Line 119:  
==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. Configurable parameters:
+
When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated. Detected speed has to be greater than configured max speed +3% of configured max speed for the overspeeding event to start. To stop overspeeding event detected speed has to be lower than configured max speed -3% of configured max speed. Configurable parameters:
−
[[Image:Over_Speeding.gif|{{{general|size}}}|right]]  
+
[[Image:Over_Speeding.PNG|{{{general|size}}}|right]]  
 
<br />
 
<br />
 
*Scenario settings – defines priority of over speeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
 
*Scenario settings – defines priority of over speeding scenario: 0 – disabled, 1 – low, 2 – high, 3 – panic.
 
*Max speed – it is max allowed speed which can be reached. If speed exceeded configured value, then event will occur.  
 
*Max speed – it is max allowed speed which can be reached. If speed exceeded configured value, then event will occur.  
−
*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.
   
*Send SMS to – GSM number to which SMS event will be sent.
 
*Send SMS to – GSM number to which SMS event will be sent.
 
*SMS text – SMS text.
 
*SMS text – SMS text.
−
<br /><br /><br /><br /><br />
+
<br /><br />
 
{{{jamming1|
 
{{{jamming1|
 
==Jamming==
 
==Jamming==
Line 147: Line 165:  
[[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, 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/>
+
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.<br/>
 
<br/><br/>
 
<br/><br/>
−
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.
  −
      
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]'''.
 
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]'''.
Line 156: Line 172:  
By using iBeacon authorization, the immobilizer feature can be used with devices that don't have a 1-wire data connection available.
 
By using iBeacon authorization, the immobilizer feature can be used with devices that don't have a 1-wire data connection available.
 
<br/><br/><youtube>gjuiJjAejWU</youtube>}}}
 
<br/><br/><youtube>gjuiJjAejWU</youtube>}}}
 +
 +
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.
 +
 +
The "No Authentification Timeout" is used as a backup option in order to turn on the vehicle. For example if you set the "No Authentification Timeout" to 60 seconds, then you need to turn on the ignition and keep it active for 60 seconds, then the authorization will be successful (it will bypass the iBeacon or iButton authorization) and user will be able to turn on the vehicle on.
 +
 +
{{{seco_feature|==SECO==
 +
[[Image:SECO.png|right]]
 +
The solution, introduced in firmware version 03.28.02, is designed to stop a stolen vehicle without causing accidents. It accomplishes this by pulsing digital output to disable the fuel pump at intervals until the vehicle slows down to a configured speed, at which point the pump is fully disabled.<br />Parameters used with ''SECO'' functionality are given in a table below.
 +
 +
<table class="nd-othertables" style="width: 80%;">
 +
<tr>
 +
        <th style="width: 20%; text-align:left; vertical-align:middle; color:black">Parameter name</th>
 +
        <th style="width: 71%; text-align:center; vertical-align:middle; color:black">Description</th>
 +
        <th style="width: 9%; text-align:center; vertical-align:center; color:black">Parameter ID</th>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left;">Scenario Settings</td>
 +
        <td style="width: 8%; text-align:left">Enable/Disable SECO functionality</td>
 +
        <td style="width: 8%; text-align:center">12250</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left;">Eventual Records</td>
 +
        <td style="width: 8%; text-align:left">If disabled - scenario status value will be appended in each AVL record</td>
 +
        <td style="width: 8%; text-align:center">12251</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">Output Control</td>
 +
        <td style="width: 8%; text-align:left">Available scenario settings for module Digital output activation/deactivation</td>
 +
        <td style="width: 8%; text-align:center">12252</td> 
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">Speed</td>
 +
        <td style="width: 8%; text-align:left">Digital output will be activated if vehicle speed consistently lower than configured during "Speed check period"</td>
 +
        <td style="width: 8%; text-align:center">12254</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">Speed Pulse scenario</td>
 +
        <td style="width: 8%; text-align:left">Valid if "Output Pulse" feature enabled. Scenario will be activated if vehicle speed consistently lower than configured during "Speed check period". After activation digital output will be activated and disabled continuously until speed will be lower then configured in "Speed" field and longer then "Speed check period"</td>
 +
        <td style="width: 8%; text-align:center">12259</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">Speed check period</td>
 +
        <td style="width: 8%; text-align:left">Time span during which vehicle speed must be lower than configured for output to activate.</td>
 +
        <td style="width: 8%; text-align:center">12255</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">Momevemt timeout</td>
 +
        <td style="width: 8%; text-align:left">Accelerometer's instant movement timeout after which output will be activated (GNSS OFF)</td>
 +
        <td style="width: 8%; text-align:center">12256</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">Output pulse</td>
 +
        <td style="width: 8%; text-align:left">Pulse scenario adds additional output control which helps to slow down vehicle before fully disabling fuel pump.</td>
 +
        <td style="width: 8%; text-align:center">12253</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">DOUT ON duration</td>
 +
        <td style="width: 8%; text-align:left">A value in milliseconds, for how long DOUT should be active</td>
 +
        <td style="width: 8%; text-align:center">12257</td>
 +
    </tr>
 +
<tr>
 +
        <td style="width: 8%; text-align:left">DOUT OFF duration</td>
 +
        <td style="width: 8%; text-align:left">A value in milliseconds, for how long DOUT should be inactive</td>
 +
        <td style="width: 8%; text-align:center">12258</td>
 +
    </tr>
 +
</table>
 +
 +
===SECO SMS Commands===
 +
 +
Secure engine cut-off (SECO) functionality is available for device with at least one DOUT.  For SECO functionality to work, DOUT must to be selected. SECO has DOUT control priority higher than immobilizer scenario.<br>
 +
SECO scenario can only be enabled or disabled by SMS commands:<br>
 +
*"secoon" - to activate SECO functionality.
 +
 +
*"secooff" - to disable SECO functionality.
 +
The structure of sending SMS commands: [[FMB130 SMS/GPRS Commands]]
 +
 +
==== 1. SMS responses====
 +
 +
To SMS command „secooff“ device will give response: „Seco off received. DOUTX off“.
 +
 +
To SMS command „secoon“ response:
 +
 +
1. „Seco on received. Waiting for conditions“.
 +
 +
2. „Seco on received. DOUTX pulsing“.
 +
 +
3. „Seco on received. DOUTX on“.
 +
 +
When response is not 3 all later SMS will be received. Example: SMS 1 received and pulse configured, then SMS 2 will be received when speed is lower than configured and SMS 3 will be received when speed reaches 0 km/h. <br>
 +
'''Note:'''
 +
Sending commands to the device without DOUT will give response "SECO not available for this device". When DOUT is not selected in configuration response will be: "Error. no DOUT configured". This secure vehicle disabling solution is supported by any Teltonika FMB series tracker (excluding FMX640 series trackers), also SIM card is in order to get data to your server.
 +
 +
For more information about SECO configuring please see [https://wiki.teltonika-gps.com/view/Secure_vehicle_disabling '''here''']
 +
 +
}}}
    
{{{ibutton_feature|==iButton Read Notification==
 
{{{ibutton_feature|==iButton Read Notification==
Line 174: Line 285:  
*iButton List checking - parameter configures that device reads the iButton ID from list or not.
 
*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
 
*Depend on Ignition - Output will be triggered only if ignition is off
−
<br/><br/>}}}
+
}}}
    
{{{gnss_fuel|
 
{{{gnss_fuel|
Line 250: Line 361:     
}}}
 
}}}
 +
{{{SECO|{{Template:Secure_vehicle_disabling}}}}}
Retrieved from "https://wiki.teltonika-gps.com/view/Special:MobileDiff/66602...97040"