Jump to content
  • EN

Template:FMX Accelerometer Features settings: Difference between revisions

← Older edit
VisualWikitext
Arnas.Zeb (talk | contribs)
5,404 edits
No edit summary
Arnas.Zeb (talk | contribs)
5,404 edits
No edit summary
 
(14 intermediate revisions by 7 users not shown)
Line 1: Line 1:
==Accelerometer Calibration==
==Accelerometer Calibration==


Accelerometer auto calibration functionality has one purpose - determine how {{{model|FMX}}} device
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle‘s axes (see Picture below). Vehicles axes are as follows:<br>
is mounted in a vehicle. After the calibration process ''eco driving'' functionality becomes active
1. X is front.<br>
and calibration data will be used to determine harsh acceleration, braking and cornering events.<br/>
2. Y is left.<br>
There are two conditions when auto calibration takes place:<br/>
3. Z is down.<br>
* If on device startup no calibration was detected;
 
* If the device receives an SMS/GPRS message with ''auto_calibrate:set'' text.<br/>
[[File:Vehicle axis.PNG.png|center|800px|Vehicle Axis]]
After functionality has started {{{model|FMX}}} device periodically checks current appliance GNSS,
 
ignition and movement source parameters and if the conditions match:<br/>
Once vehicle‘s axes are calculated, device is considered calibrated.<br>
* position fix got;
<br>
* GNSS speed is zero;
'''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>
* ignition is ON;
 
* first calibration vector was not saved yet;<br/>
Configurable parameters can be found at [[{{{model|FMB1YX}}}_System_settings#Accelerometer_Auto_Calibration|System Settings Accelerometer Auto Calibration]]
Then first vector is taken. Saved vector will be considered as ground vector and it will be
 
used at further calibration calculations.<br/>
Commands that can be used during calibration:<br>
''Note: When {{{model|FMX125}}} device saves first ground vector vehicle must be parked on flat ground''.
<center>
Crooked vector may have an impact on further calculations.<br/>
{| class="wikitable"
Afterwards first ground vector was taken, device analyses conditions:<br/>
|-
* position fix got;
!Command!!Response!!Description
* GNSS speed is at least 20 km/h;
|-
* ignition is ON;
|auto_calibrate:set||Yes||Request auto calibration task start
* second vector was not saved yet;
|-
* vehicle driving in the same direction with 5⁰ tolerance;
|auto_calibrate:get||Yes||Request calibration info (time, ground vector, side vector)
* vehicle speed increase by 7km/h within 1 second.<br/>
|-
For next vector. Second vector will be taken if all conditions match. Immediately after
|auto_calibrate:clear||Yes||Request calibration clear from flash and stop calibration task
second vector is received, it will be multiplied by first (ground) vector, the result of these
|-
vectors is vector multiplication cross product which is the right side of a car. By using
|auto_calibrate:status||Yes||Request calibration status and calibration task status
same vector multiplication method, device front, left side will be calculated. At this point
|}
calibration is successfully ended as indication device sends an SMS/GPRS message with
</center>
''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
======Auto-calibration======
SMS/GPRS message''.<br/>
 
For user convenience in case auto calibration functionality fails then notification message
Auto calibration task is launched on one of these conditions (assume calibration is enabled in configuration):<br>
will be sent. For exact messages, check algorithm section.<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>
''Note: SMS/GPRS message will be sent only if auto calibration functionality was triggered by
2. Device calibration was previously disabled by configuration and now is enabled.<br>
SMS/GPRS message''.<br/>
3. SMS “auto_calibrate:set” is received. Note: SMS response is sent after calibration has been acquired.<br>
To get current calibration status ''auto_calibrate:get'' SMS/GPRS command must be sent to
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>
the device. If device is calibrated it will respond with ''Calibration state: calibrated'' or otherwise
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>
''Calibration state: not calibrated''. Also this command returns saved Ground and Side vectors.<br/>
After auto calibration task has been started, it will go on indefinitely until satisfactory calibration is acquired.<br>
After every TRIP START event, device starts shadow calibration. This type of calibration is
 
running in parallel with already saved vectors (this means that vectors does not reset until
=====Data Required=====
shadow calibration have both new vectors). After shadow calibration is done, device updates the
 
vector values to the new ones. There are two conditions when shadow calibration does not run
Auto calibration needs to fill two buffers to calibrate the device:<br>
at TRIP start event:<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>
* Normal calibration is still running.
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>
* Shadow calibration is still running from previous TRIP event.<br/>
2.1. GPS fix is present.<br>
To take ground vector these conditions should be met:<br/>
2.2. Ignition is on.<br>
* Ignition is ON
2.3. GPS speed is more than 5 km/h.<br>
* Device got GPS FIX
2.4. GPS heading is equal to last GPS heading (+/-1 degree) at GPS sample rate 1Hz.<br>
* Vehicle speed = 0km/h<br/>
2.5. GPS speed more then 5 km/h from last sample (accelerating).<br>
Device will check these conditions every 1sec until they will pass.<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>
To take side vector these conditions should be met:<br/>
Note: If GPS fix is lost or ignition is turned off, buffers’ data is dumped and must be gathered from 0 again.<br>
* Vehicle speed >= 20km/h
 
* Device got GPS FIX
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>''
* Ignition is ON
 
* Device angle does not change more than 5 degrees in past 1 sec
''Note: SMS/GPRS message will be sent only if auto calibration functionality was triggered by SMS/GPRS message.''
* Speed need to increase by 7km/h in 1s period.<br/>
For user convenience in case auto calibration functionality fails then notification message will be sent. For exact messages, check algorithm section.<br>
Device will check these conditions every 1 sec until they will pass.<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/>
{{{excessive_idling|


==Excessive Idling==
==Excessive Idling==
Line 64: Line 72:


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 (''Time to Stopped''). Scenario is activated until the vehicle starts moving (movement is detected only by the accelerometer) and keeps moving for an amount of time that is configured. You can configure the time it takes to turn off this scenario (''Time to Moving'')<br/>{{{dout|info}}}
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 (''Time to Stopped''). Scenario is activated until the vehicle starts moving (movement is detected only by the accelerometer) and keeps moving for an amount of time that is configured. You can configure the time it takes to turn off this scenario (''Time to Moving'')<br/>{{{dout|info}}}
<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>
 
{{{unplug_feature|==Unplug Detection==
When there is no GPS fix, the system uses accelerometer data to determine movement: <br>
 
'''*''' If the ignition is on and the accelerometer detects movement without a GPS fix, the vehicle is not considered idling. <br>
'''*''' If the ignition is on but the accelerometer indicates no movement without a GPS fix, the vehicle is considered idling.<br>
'''*''' If the ignition turns off during detected excessive idling, an AVL ID: 251 and Value: 0 will be generated.<br>
 
<br/><br/><br/><br/><br/><br/>
}}}
 
 
{{{unplug_feature|
 
==Unplug Detection==


[[Image:Fmb120_unplug.png|right]]
[[Image:Fmb120_unplug.png|right]]
Line 85: Line 105:
==Towing Detection==
==Towing Detection==


[[Image:Fmb120_towing.png|right]]
[[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 95: Line 115:
==Crash Detection==
==Crash Detection==


[[File:Crash Detection cfg.PNG|right]]
[[File:Crash Detection.PNG|right]]
[[Crash_trace|Click here to enter Crash Tracer data parsing page]]


If ''Crash Detection'' is enabled, it monitors acceleration on each axis which helps to detect an accident. ''Threshold'' and ''Duration'' values are set depending on the impact magnitude that is required to be detected. {{{model|FMT100}}} can detect events ranging between a slight tapping on the device and a severe accident.<br/>
If ''Crash Detection'' is enabled, it monitors acceleration on each axis which helps to detect an accident. ''Threshold'' and ''Duration'' values are set depending on the impact magnitude that is required to be detected. {{{model|FMT100}}} can detect events ranging between a slight tapping on the device and a severe accident.<br/>
Line 124: Line 145:


[[Image:Fmb120_crash_trace.png|600px|none]]
[[Image:Fmb120_crash_trace.png|600px|none]]
==Crash Data Visualisation==
With Teltonika ''CrashDataVisualizer'' tool you can analyze crash trace data visually: determine impact to vehicle direction, view crash trace on the map, also see the change of mG and speed values during crash time period. CrashDataVisualizer is dedicated to work with TAVL application, it means that only crash trace log files exported from TAVL is compatible. To have ability to export crash trace log files, device must be configured to send data by Codec8E.
'''To start using CrashDataVisualizer'''<br />
Download and install TAVL (version 4.15.0.1 or later) + CrashDataVisualizer applications from here:<br />
''Link:'' https://drive.teltonika.lt/d/05369fc90d9744afb14f/<br />
''Password:'' TJEk24YApbRhWrQQ
'''To get crash data'''<br />
Login to TAVL application (please contact your Sales manager for TAVL login information).<br />
[[File:Crash data steps.png|thumb|left]]
In TAVL application:<br />
1.  Go to Events<br />
2.  Set the date of event<br />
3.  Select the object you want to analyze<br />
4.  Press "Crashes" button<br/><br/><br/><br/><br/><br/><br/><br/>
Crash event list window will show up. Press Download icon and save crash  event file (.JSON).<br />
[[File:JSON download.png|thumb|none]]<br />
'''Viewing crash data in application'''<br />
Open CrashDataVisualizer application. Drag and Drop or Browse crash data file (.JSON).<br />
[[File:Crash Data Visualizer start screen.png|thumb|none]]
Use the Visualizer.<br />
[[File:Crash Data Visualizer main.png|thumb|none]]
Retrieved from "https://wiki.teltonika-gps.com/view/Template:FMX_Accelerometer_Features_settings"