Difference between revisions of "FMM640 Features settings"

From Wiki Knowledge Base | Teltonika GPS
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
+
{{Template:FMM640 Features settings|model=FMM640|template_link={{Template:FMM640 Features settings|model=FMM640}}}}
  
 
{{Template:FMM640 Green Driving|model=FMM640}}
 
{{Template:FMM640 Green Driving|model=FMM640}}
Line 7: Line 7:
 
{{Template:FMM640 Jamming|model=FMM640}}
 
{{Template:FMM640 Jamming|model=FMM640}}
  
{{Template:FMM640 DOUT Control via Call|model=FMM640}}
+
{{Template:FMM640 Authorized driving/Immobilizer|model=FMM640}}
 
 
{{Template:FMM640 Authorized driving/Immobilizer|model=FMM640
 
|pic_immobilizer = [[Image:FMB640 Immobilizer.png|right|300px]]
 
|txt_br = <br/><br/><br/>
 
}}
 
 
 
{{Template:FMM640 iButton Read Notification|model=FMM640
 
|pic_ibutton = [[Image:FMB640 iButton Read Notification.png|right|300px]]
 
}}
 
 
 
{{Template:FMM640 Short burst data settings|model=FMM640}}
 
  
 
[[Category:FMM640 Configuration]]
 
[[Category:FMM640 Configuration]]
 
{{Template:FMM640 Impulse Counters Settings}}
 

Revision as of 13:34, 22 August 2019

Main Page > EOL Products > FMM640 > FMM640 Configuration > FMM640 Features settings

Template:FMM640 Features settings

Green Driving

Green driving.JPG

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/s2 units. Scenario is activated until current Acceleration, Braking or Cornering value decreases below the set parameter value.
Parameters used with Green Driving functionality are given in a table below.

Parameter name Description
Output Control Enable/Disable Green driving functionality and Activate/Deactivate DOUT.
Max Acceleration Value which can be reached while accelerating without triggering harsh acceleration event.
Max Braking Acceleration Value which can be reached while braking without triggering harsh braking event.
Max Cornering Acceleration Value which can be reached while cornering without triggering harsh cornering event.
Source Which source data will be collected from:
  • GNSS - GPS Data will be used to detect harsh driving. (This algorithm was used in FM53, FM63 devices)
  • Accelerometer – Accelerometer data will be used to detect harsh driving. (This algorithm is from FMB device family). Accelerometer calibration needs to be performed with “auto_calibrate:set” command.
  • GNSS Algorithm A1 – GPS data will be used to detect harsh driving. (This algorithm is used in FMA11 devices). The main difference from FM53 is cornering detection which uses advanced math to more precisely calculate harsh cornering value across different vehicle speeds.
  • Accelerometer Algorithm A1 - Accelerometer data will be used to detect harsh driving. (This algorithm is used in FMA11 device family)

Note: To use “Accelerometer Algorithm A1” option user need to install device as in Figure 1.

Fmx6 axis.jpg

FMB640 Device accelerometer position. (With positive Z axis pointing to Ground and antennas face forward in the vehicle). Before operation with the vehicle on level ground user must send “setacc” SMS.

Auto calibration


The auto-calibration process is the following:

  1. The vehicle is stopped.
  2. There is a straight road ahead.
  3. Send SMS "auto_calibrate:set" to the FMB device.
  4. Accelerate to >30 km/h for 5 sec.
  5. 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. To check auto-calibration status send a following short text message to the FMB device: "auto_calibrate:get".

Over Speeding

FMB640 overspeeding.png

When vehicle speed exceeds configured maximum speed value the scenario is activated, an event record is generated and digital output status is changed to 1 when configured.
Scenario is active until detected speed decreases below the set parameter value.
info DOUT1, DOUT2 or DOUT3 can be activated for a period of time to warn the driver. Output on-time is configured separately for each feature case. For more information please refer to DOUT controls.





Jamming

Jamming.JPG

When jamming is detected the scenario is activated, an event record is generated and digital output status is changed to 1 when configured once Jamming timeout runs out. If jamming ends during timeout countdown no event will be generated and output will not be controlled.
Eventual Records parameter can be configured: when it is disabled scenario status value will appear in each AVL record, otherwise it will be appended only to eventual records.









Authorized driving/Immobilizer

FMB640 authorizedD.png
  • If DOUT Control is disabled, the scenario will only generate events without digital output activation. If DOUT Control is enabled DOUT1/DOUT2 turns ON if ignition turns ON (Ignition Source is configured to 1).
  • After any iButton ID is attached, DOUT1/DOUT2/DOUT3 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 the iButton list.
  • Ignition off timeout parameter is used to set the duration after which authorization is activated when the ignition is turned off.
  • Authorization off timeout parameter is used to set the duration of how long the user has time to authorize after switching the ignition ON.
  • iButton list gives the ability to use the vehicle for 1000 specific iButton owners (specified in iButton list). Selected DOUT is controlled by scenario for user needs, to manage buzzer, LED, etc.