Template:FMX Accelerometer Features settings: Difference between revisions
| (12 intermediate revisions by 7 users not shown) | |||
| Line 10: | Line 10: | ||
Once vehicle‘s axes are calculated, device is considered calibrated.<br> | Once vehicle‘s axes are calculated, device is considered calibrated.<br> | ||
<br> | <br> | ||
Note: moving forward along any axis will generate negative values. This means acceleration will generate -X values, accordingly breaking will generate X values. Same goes for other axes. <br> | '''Note:''' moving forward along any axis will generate negative values. This means acceleration will generate -X values, accordingly breaking will generate X values. Same goes for other axes. <br> | ||
Configurable parameters can be found at [[{{{model|FMB1YX}}}_System_settings#Accelerometer_Auto_Calibration|System Settings Accelerometer Auto Calibration]] | Configurable parameters can be found at [[{{{model|FMB1YX}}}_System_settings#Accelerometer_Auto_Calibration|System Settings Accelerometer Auto Calibration]] | ||
| Line 29: | Line 29: | ||
|} | |} | ||
</center> | </center> | ||
======Auto-calibration====== | |||
====Auto calibration | |||
Auto calibration task is launched on one of these conditions (assume calibration is enabled in configuration):<br> | Auto calibration task is launched on one of these conditions (assume calibration is enabled in configuration):<br> | ||
| Line 117: | Line 42: | ||
=====Data Required===== | =====Data Required===== | ||
Auto calibration | Auto calibration needs to fill two buffers to calibrate the device:<br> | ||
1. All accelerometer data – buffer which collects all data from accelerometer at 10Hz frequency. To fill this buffer set seconds of data samples are needed. When buffer is full, oldest data is dumped and new data is placed into the buffer.<br> | 1. All accelerometer data – buffer which collects all data from accelerometer at 10Hz frequency. To fill this buffer set seconds of data samples are needed. When buffer is full, oldest data is dumped and new data is placed into the buffer.<br> | ||
2. Straight accelerometer data – buffer which | 2. Straight accelerometer data – buffer which collects straight accelerations data from accelerometer at 10Hz frequency. To fill this buffer set seconds of data samples (set times Hz samples) are needed. When buffer is full, oldest data is dumped and new data is placed into the buffer. Algorithm rules to acquire these samples:<br> | ||
2.1. GPS fix is present.<br> | 2.1. GPS fix is present.<br> | ||
2.2. Ignition is on.<br> | 2.2. Ignition is on.<br> | ||
| Line 127: | Line 52: | ||
Once both buffers are full, auto calibration is attempted. If calibrated values pass calibration quality threshold, calculated calibration is written to flash as current calibration – device is calibrated. <br> | Once both buffers are full, auto calibration is attempted. If calibrated values pass calibration quality threshold, calculated calibration is written to flash as current calibration – device is calibrated. <br> | ||
Note: If GPS fix is lost or ignition is turned off, buffers’ data is dumped and must be gathered from 0 again.<br> | Note: If GPS fix is lost or ignition is turned off, buffers’ data is dumped and must be gathered from 0 again.<br> | ||
At this point calibration is successfully ended as indication device sends an SMS/GPRS message with ''Device is calibrated, to recalibrate send:auto_calibrate:set.<br>'' | |||
''Note: SMS/GPRS message will be sent only if auto calibration functionality was triggered by SMS/GPRS message.'' | |||
For user convenience in case auto calibration functionality fails then notification message will be sent. For exact messages, check algorithm section.<br> | |||
''Note: SMS/GPRS message will be sent only if auto calibration functionality was triggered by SMS/GPRS message.'' | |||
To get current calibration status ''auto_calibrate:get'' SMS/GPRS command must be sent to the device. If device is calibrated it will respond with ''Calibration state: calibrated'' or otherwise ''Calibration state: not calibrated''. Also this command returns saved Ground and Side vectors.<br> | |||
=====Re-Calibration===== | =====Re-Calibration===== | ||
When calibration is present, device checks for re-calibration every 60s indefinitely. Re-calibration requires fix and ignition to run also re-calibration is turned off when vehicle is stopped for more than 15s until conditions are satisfied again. When calibrated device’s mean axes of set interval(calibrated accelerometer data) differ more than set amount from desired (0,0,1) (perfect vehicle’s axes) calibration is considered inaccurate, or device’s position has changed and re-calibration is needed. Calibration is cleared from flash and auto calibration task is started.<br> | When calibration is present, device checks for re-calibration every 60s indefinitely. Re-calibration requires fix and ignition to run also re-calibration is turned off when vehicle is stopped for more than 15s until conditions are satisfied again. When calibrated device’s mean axes of set interval(calibrated accelerometer data) differ more than set amount from desired (0,0,1) (perfect vehicle’s axes) calibration is considered inaccurate, or device’s position has changed and re-calibration is needed. Calibration is cleared from flash and auto calibration task is started.<br/> | ||
Note: turning device around calibrated Z axis will not trigger re-calibration, after turning device around Z axis manual re-calibration is advised. After calibration if quality value is less than 0.80, calibration update functionality is run. Calibration update constantly tries calibrating device in background until 0.80 quality is reached. Calibration update functionality does not change calibration if calculated new calibration quality is less than 0.80.<br/> | |||
Note: turning device around calibrated Z axis will not trigger re-calibration, after turning device around Z axis manual re-calibration is advised. | |||
After calibration if quality value is less than 0.80, calibration update functionality is run. Calibration update constantly tries calibrating device in background until 0.80 quality is reached. Calibration update functionality does not change calibration if calculated new calibration quality is less than 0.80. | |||
{{{excessive_idling| | {{{excessive_idling| | ||
| Line 141: | Line 71: | ||
{{{pic_idling|[[Image:Idling.gif|right]]}}} | {{{pic_idling|[[Image:Idling.gif|right]]}}} | ||
When vehicle stops for a specific amount of time the scenario is activated, a record will be generated and digital output status will be changed to 1 when configured. You can configure the time it takes to turn on this scenario ('' | ===<u>Introduction</u>=== | ||
< | Excessive idling scenario is used to detect when a vehicle has stopped for a long time with a running engine. | ||
}}} | |||
===<u>How it works</u>=== | |||
When vehicle stops for a specific amount of time the scenario is activated, a record will be generated {{#switch: {{{model}}} | |||
| FMP100 | FMB010 | FMB020 | FMC800 | FMM800 | FMM80A | FMT100 | FMC880 | FMM880 | FMB001 |FMB003 |FMC003 |FMM003 |FMM00A = | |||
| #default = and digital output status will be changed to 1 when configured.}} | |||
You can configure the time it takes to turn on this scenario ('''Delay to Enter Idle'''). Scenario is activated until the vehicle starts moving (movement is detected '''only''' by the accelerometer) and keeps moving for the amount of time that it is configured. You can configure the time it takes to turn off this scenario ('''Time To Exit Idle'''). | |||
'''Note:''' When there is no GPS fix, the system uses accelerometer data to determine movement. | |||
*If the ignition is on and the accelerometer detects movement without a GPS fix, the vehicle is not considered idling. | |||
*If the ignition is on but the accelerometer indicates no movement without a GPS fix, the vehicle is considered idling. | |||
*If the ignition turns off during detected excessive idling, an (AVL ID 251) and Value: 0 will be generated. | |||
===<u>Parameter description</u>=== | |||
'''Scenario Settings''' | |||
*<b>Disable</b> – Disable scenario | |||
*<b>Low Priority</b> – Device makes an additional record with indication of event cause. | |||
*<b>Hight Priority</b> – Device makes an additional record with high priority flag and immediately sends an event packet to the server by GPRS. | |||
*<b>Panic Priority</b> – Triggers same actions as High Priority, but if GPRS fails, the device sends an AVL packet via SMS (if enabled in SMS settings). | |||
'''Eventual Records''' | |||
*<b>Disable</b> – When disabled, scenario status will be appended in each AVL record. | |||
*<b>Enable</b> – When enabled, scenario status will be appended only to eventual records. | |||
'''Delay to Enter Idle (s)''' – Delay before entering the Excessive Idling state. Defines how long a vehicle with ignition ON should not move to enter the Excessive Idling state. Value in seconds. | |||
'''Delay to Exit Idle (s)''' – Delay before exiting the Excessive Idling state. Defines how long a vehicle with ignition ON should not move to exit the Excessive Idling state. Value in seconds. | |||
{{#switch: {{{model}}} | |||
| FMP100 | FMB010 | FMB020 | FMC800 | FMM800 | FMM80A | FMT100 | FMC880 | FMM880 | FMB001 |FMB003 |FMC003 |FMM003 |FMM00A = | |||
| #default = | |||
'''Output Control''' | |||
*'''DOUT ON Duration (ms)''' – Duration for which the selected DOUT signal is ON when the device enters this scenario. Works together with “DOUT OFF Duration” (for most parameters) – after one duration elapses, the other starts, until the scenario exited. | |||
*'''DOUT OFF Duration (ms)''' – Duration for which the selected DOUT signal is ON when the device enters this scenario. Works together with “DOUT ON Duration” (for most parameters) – after one duration elapses, the other starts, until the scenario exited. | |||
'''Note:''' Both DOUT ON and OFF Duration work together – after one duration elapses, the other starts, until the scenario exited. | |||
}} | |||
'''Send SMS to''' – Selects the GSM number of SMS event recipient from “GSM Predefined numbers” list. | |||
<br><br> | |||
'''SMS Text''' – Sets the SMS text that will be sent to SMS recipient when the event is triggered. | |||
{{{unplug_feature| | {{{unplug_feature| | ||
| Line 166: | Line 142: | ||
* '''Simple''' - unplug detection according to '''external voltage only'''. Is used in cars where power voltage is not dependent on ignition (recommended). | * '''Simple''' - unplug detection according to '''external voltage only'''. Is used in cars where power voltage is not dependent on ignition (recommended). | ||
* '''Advanced''' - unplug detection according to '''external votage''' and '''accelerometer'''. Is used in cars where power voltage is disconnected when ignition is switched off.}}} | * '''Advanced''' - unplug detection according to '''external votage''' and '''accelerometer'''. Is used in cars where power voltage is disconnected when ignition is switched off.}}} | ||
==Towing Detection== | ==Towing Detection== | ||
[[Image: | [[Image:Fmb120_towings.png|right|250px]] | ||
''Towing Detection'' feature helps to inform the driver about unexpected car movement when it was parked. {{{model|FMB1YX}}} generates an event when car is being towed or lifted, for example, in a case of vehicle evacuation. {{{model|FMB1YX}}} activates towing function when following conditions are met: | ''Towing Detection'' feature helps to inform the driver about unexpected car movement when it was parked. {{{model|FMB1YX}}} generates an event when car is being towed or lifted, for example, in a case of vehicle evacuation. {{{model|FMB1YX}}} activates towing function when following conditions are met: | ||
| Line 178: | Line 155: | ||
==Crash Detection== | ==Crash Detection== | ||
[[File:Crash Detection | [[File:Crash Detection.PNG|right]] | ||
[[Crash_trace|Click here to enter Crash Tracer data parsing page]] | [[Crash_trace|Click here to enter Crash Tracer data parsing page]] | ||
| Line 208: | Line 185: | ||
[[Image:Fmb120_crash_trace.png|600px|none]] | [[Image:Fmb120_crash_trace.png|600px|none]] | ||