Template:FMX Ver4 Accelerometer Based Features - Revision history

Arijus.C at 06:44, 11 May 2026

2026-05-11T06:44:10Z

← Older revision		Revision as of 09:44, 11 May 2026
Line 572:		Line 572:

	It is required 1 to 3 seconds to determine the power loss of a device. Consequently, if a device is not being moved any more after few seconds after removing it from the power source, no event will be generated. This can happen, if a device is quickly throwed on the ground after ripping it off.		It is required 1 to 3 seconds to determine the power loss of a device. Consequently, if a device is not being moved any more after few seconds after removing it from the power source, no event will be generated. This can happen, if a device is quickly throwed on the ground after ripping it off.

			If Unplug Detection scenario priority is set to High or Panic and sleep mode is set to Deep Sleep, the device waits for 30 seconds before entering Deep Sleep in both Advanced and Simple modes, allowing the generated Unplug record to be sent or the call to be made.

	==== Simple mode ====		==== Simple mode ====

Justinas.strelciunas at 05:52, 28 August 2025

2025-08-28T05:52:57Z

@@ Line 47: / Line 47: @@
 </table>
 ======Auto-calibration======
@@ Line 164: / Line 91: @@
 == Towing Detection ==
+[[Image:FM Ver4 Towing Detection Configurator panel.png|right]]
 Towing Detection is a feature that detects and notifies about unexpected movements of a stationary vehicle, such as towing or theft attempts.

Justinas.strelciunas at 05:51, 28 August 2025

2025-08-28T05:51:15Z

← Older revision		Revision as of 08:51, 28 August 2025
Line 309:		Line 309:
	\| #default =		\| #default =
	==Excessive Idling==		==Excessive Idling==
			[[Image:FM Ver4 Excessive Idling Configurator panel.png\|right]]
	Excessive Idling is a feature that automatically detects if a vehicle is stopped for a prolonged time with a running engine.		Excessive Idling is a feature that automatically detects if a vehicle is stopped for a prolonged time with a running engine.

Line 439:		Line 440:

	== Crash Detection ==		== Crash Detection ==
			[[Image:FM Ver4 Crash Detection Configurator panel.png\|right]]
	Crash Detection is a feature that automatically detects crash events by continuously monitoring device accelerometer data.		Crash Detection is a feature that automatically detects crash events by continuously monitoring device accelerometer data.

Line 625:		Line 627:
	\| #default =		\| #default =
	== Unplug Detection ==		== Unplug Detection ==
			[[Image:FM Ver4 Unplug Detection Configurator panel.png\|right]]
	Unplug Detection is a feature that notifies when the device is disconnected from its external power source, and again when reconnected. This feature is available for devices that have an internal battery.		Unplug Detection is a feature that notifies when the device is disconnected from its external power source, and again when reconnected. This feature is available for devices that have an internal battery.

Justinas.strelciunas at 12:55, 27 August 2025

2025-08-27T12:55:23Z

← Older revision		Revision as of 15:55, 27 August 2025
Line 1:		Line 1:
			{{#switch: {{{model}}} <!-- this section is applied to all devices, which accelerometer-->

			\| #default =

			==Accelerometer Calibration==

			Calibration algorithm is used to recalculate accelerometer axes to represent vehicle‘s axes (see Picture below). Vehicles axes are as follows:<br>
			1. X is front.<br>
			2. Y is left.<br>
			3. Z is down.<br>

			[[File:Vehicle axis.PNG.png\|center\|800px\|Vehicle Axis]]

			Once vehicle‘s axes are calculated, device is considered calibrated.<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>

			Configurable parameters can be found at [[{{{model\|FMB1YX}}}_System_settings#Accelerometer_Auto_Calibration\|System Settings Accelerometer Auto Calibration]]

			Commands that can be used during calibration:<br>
			<table class="nd-othertables_2" style="width:70%; border-collapse: collapse;">
			<tr>
			<th style="width:1%; vertical-align: middle; text-align: center;">Command</th>
			<th style="width:2%; vertical-align: middle; text-align: center;">Response</th>
			<th style="width:5%; vertical-align: middle; text-align: center;">Description</th>
			</tr>
			<tr>
			<td style="vertical-align: middle; text-align: center;">auto_calibrate:set</td>
			<td style="vertical-align: middle; text-align: center;">Yes</td>
			<td style="vertical-align: middle; text-align: center;">Request auto calibration task start </td>
			</tr>
			<tr>
			<td style="vertical-align: middle; text-align: center;">auto_calibrate:get</td>
			<td style="vertical-align: middle; text-align: center;">Yes</td>
			<td style="vertical-align: middle; text-align: center;">Request calibration info (time, ground vector, side vector) </td>
			</tr>
			<tr>
			<td style="vertical-align: middle; text-align: center;">auto_calibrate:clear</td>
			<td style="vertical-align: middle; text-align: center;">Yes</td>
			<td style="vertical-align: middle; text-align: center;">Request calibration clear from flash and stop calibration task </td>
			</tr>
			<tr>
			<td style="vertical-align: middle; text-align: center;">auto_calibrate:status</td>
			<td style="vertical-align: middle; text-align: center;">Yes</td>
			<td style="vertical-align: middle; text-align: center;">Request calibration status and calibration task status </td>
			</tr>

			</table>

			======Auto-calibration======

			Auto calibration task is launched on one of these conditions (assume calibration is enabled in configuration):<br>
			1. Every time device turns on, it checks whether it was previously calibrated and has calibration stored in flash. If device has no calibration in flash, auto calibration task is started.<br>
			2. Device calibration was previously disabled by configuration and now is enabled.<br>
			3. SMS “auto_calibrate:set” is received. Note: SMS response is sent after calibration has been acquired.<br>
			This SMS triggers an SMS response to be sent. Response is sent when calibration is acquired. When 1 hour passes without successful calibration, failed SMS response is sent.<br>
			4. Calibrated device’s mean axes of set interval differ more than set amount from desired (0,0,1) calibration is considered inaccurate. Calibration is deleted from flash and auto calibration task started.<br>
			After auto calibration task has been started, it will go on indefinitely until satisfactory calibration is acquired.<br>

			=====Data Required=====

			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>
			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.2. Ignition is on.<br>
			2.3. GPS speed is more than 5 km/h.<br>
			2.4. GPS heading is equal to last GPS heading (+/-1 degree) at GPS sample rate 1Hz.<br>
			2.5. GPS speed more then 5 km/h from last sample (accelerating).<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>

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

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

			}}

	{{#switch: {{{model}}} <!-- this section is applied to all devices, which accelerometer-->		{{#switch: {{{model}}} <!-- this section is applied to all devices, which accelerometer-->

Justinas.strelciunas at 12:46, 27 August 2025

2025-08-27T12:46:19Z

← Older revision		Revision as of 15:46, 27 August 2025
Line 2:		Line 2:

	\| #default =		\| #default =

	==Accelerometer Calibration==		==Accelerometer Calibration==

Line 69:		Line 70:
	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.<br/>

			}}

	}}
	{{#switch: {{{model}}}		{{#switch: {{{model}}}

Justinas.strelciunas at 12:45, 27 August 2025

2025-08-27T12:45:49Z

← Older revision		Revision as of 15:45, 27 August 2025
Line 1:		Line 1:
			{{#switch: {{{model}}} <!-- this section is applied to all devices, which accelerometer-->

			\| #default =
			==Accelerometer Calibration==

			Calibration algorithm is used to recalculate accelerometer axes to represent vehicle‘s axes (see Picture below). Vehicles axes are as follows:<br>
			1. X is front.<br>
			2. Y is left.<br>
			3. Z is down.<br>

			[[File:Vehicle axis.PNG.png\|center\|800px\|Vehicle Axis]]

			Once vehicle‘s axes are calculated, device is considered calibrated.<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>

			Configurable parameters can be found at [[{{{model\|FMB1YX}}}_System_settings#Accelerometer_Auto_Calibration\|System Settings Accelerometer Auto Calibration]]

			Commands that can be used during calibration:<br>
			<center>
			{\| class="wikitable"
			\|-
			!Command!!Response!!Description
			\|-
			\|auto_calibrate:set\|\|Yes\|\|Request auto calibration task start
			\|-
			\|auto_calibrate:get\|\|Yes\|\|Request calibration info (time, ground vector, side vector)
			\|-
			\|auto_calibrate:clear\|\|Yes\|\|Request calibration clear from flash and stop calibration task
			\|-
			\|auto_calibrate:status\|\|Yes\|\|Request calibration status and calibration task status
			\|}
			</center>

			======Auto-calibration======

			Auto calibration task is launched on one of these conditions (assume calibration is enabled in configuration):<br>
			1. Every time device turns on, it checks whether it was previously calibrated and has calibration stored in flash. If device has no calibration in flash, auto calibration task is started.<br>
			2. Device calibration was previously disabled by configuration and now is enabled.<br>
			3. SMS “auto_calibrate:set” is received. Note: SMS response is sent after calibration has been acquired.<br>
			This SMS triggers an SMS response to be sent. Response is sent when calibration is acquired. When 1 hour passes without successful calibration, failed SMS response is sent.<br>
			4. Calibrated device’s mean axes of set interval differ more than set amount from desired (0,0,1) calibration is considered inaccurate. Calibration is deleted from flash and auto calibration task started.<br>
			After auto calibration task has been started, it will go on indefinitely until satisfactory calibration is acquired.<br>

			=====Data Required=====

			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>
			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.2. Ignition is on.<br>
			2.3. GPS speed is more than 5 km/h.<br>
			2.4. GPS heading is equal to last GPS heading (+/-1 degree) at GPS sample rate 1Hz.<br>
			2.5. GPS speed more then 5 km/h from last sample (accelerating).<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>

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

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


			}}
	{{#switch: {{{model}}}		{{#switch: {{{model}}}

Justinas.strelciunas at 12:41, 27 August 2025

2025-08-27T12:41:31Z

Show changes

Justinas.strelciunas at 12:37, 27 August 2025

2025-08-27T12:37:53Z

Show changes

Justinas.strelciunas at 11:57, 27 August 2025

2025-08-27T11:57:02Z

@@ Line 1: / Line 1: @@
 == Towing Detection ==
@@ Line 139: / Line 167: @@
 </tr>
 </table>
 ==Excessive Idling==
 Excessive Idling is a feature that automatically detects if a vehicle is stopped for a prolonged time with a running engine.
@@ Line 263: / Line 319: @@
 </tr>
 </table>
 == Crash Detection ==
 Crash Detection is a feature that automatically detects crash events by continuously monitoring device accelerometer data.
@@ Line 444: / Line 528: @@
 </tr>
 </table>
 == Unplug Detection ==
@@ Line 573: / Line 685: @@
 * If, during a real unplug event, this incorrect speed value is higher than the configured Speed Threshold, the unplug event will not be registered.
 * In such cases, we recommend setting a higher Speed Threshold value.

Justinas.strelciunas: /* Parameters */

2025-08-27T11:29:15Z

Parameters

← Older revision		Revision as of 14:29, 27 August 2025
Line 53:		Line 53:
	<td style="vertical-align: middle; text-align: center;">11601</td>		<td style="vertical-align: middle; text-align: center;">11601</td>
	<td style="vertical-align: middle; text-align: center;">Toggle appending scenario status to eventual records.</td>		<td style="vertical-align: middle; text-align: center;">Toggle appending scenario status to eventual records.</td>
	<td style="vertical-align: middle; text-align: left;">'''0 = Disable''' When enabled, scenario status will be appended only to eventual records.<br> '''1 = Enable'''When disabled, scenario status will be appended in each AVL record. </td>		<td style="vertical-align: middle; text-align: left;">'''0 = Disable''' When enabled, scenario status will be appended only to eventual records.<br> '''1 = Enable''' When disabled, scenario status will be appended in each AVL record. </td>
	</tr>		</tr>
	<tr>		<tr>