| Line 1: |
Line 1: |
| | + | {{Template:FMX Accelerometer Features settings |
| | + | |calibration_feature= |
| | ==Accelerometer Calibration== | | ==Accelerometer Calibration== |
| | | | |
| Line 15: |
Line 17: |
| | | | |
| | Commands that can be used during calibration:<br> | | 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 before firmware version 03.25.07.Rev.00.==== | | ====Auto calibration before firmware version 03.25.07.Rev.00.==== |
| | Accelerometer auto calibration functionality has one purpose - determine how FMB device | | Accelerometer auto calibration functionality has one purpose - determine how FMB device |
| Line 135: |
Line 125: |
| | Note: turning device around calibrated Z axis will not trigger re-calibration, after turning device around Z axis manual re-calibration is advised. | | 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. | | 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==
| |
| | | | |
| − | {{{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 (''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}}}
| + | |unplug_feature= ==Unplug Detection== |
| − | <br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>
| |
| − | }}}
| |
| − | {{{unplug_feature|==Unplug Detection==
| |
| | | | |
| | {{{pic_unplug|[[Image:unplug.gif|right]]}}} | | {{{pic_unplug|[[Image:unplug.gif|right]]}}} |
| Line 164: |
Line 148: |
| | | | |
| | In '''03.27.02.Rev.160''' version after base update to 03.27.02.Rev.01 additional condition was introduced when calculating accelerometer measured values in configured advanced mode. This workaround came from version 03.25.15.Rev.03, if no movement detected, z axis is ignored. | | In '''03.27.02.Rev.160''' version after base update to 03.27.02.Rev.01 additional condition was introduced when calculating accelerometer measured values in configured advanced mode. This workaround came from version 03.25.15.Rev.03, if no movement detected, z axis is ignored. |
| − | }}}
| |
| | <br><youtube>CjIYGWDPJ3s</youtube><br> | | <br><youtube>CjIYGWDPJ3s</youtube><br> |
| − | | + | }} |
| − | ==Towing Detection==
| |
| − | | |
| − | {{{pic_Towing|[[file:Towing_Detection_FMB920.gif|right]]}}}
| |
| − | | |
| − | ''Towing Detection'' feature helps to inform the driver about unexpected car movement when it was parked. {{{model|FMB1YX}}} generates an event when a car is being towed or lifted, for example, in a case of vehicle evacuation. {{{model|FMB1YX}}} activates the towing function when the following conditions are met:
| |
| − | | |
| − | #Ignition (configured Ignition Source) is OFF.
| |
| − | #''Activation Timeout'' is reached.
| |
| − | | |
| − | When the towing function is engaged {{{model|FMB1YX}}} monitors accelerometer data. If acceleration ''Threshold'' or ''Angle'' reach configured values for a configured ''Duration'', and Ignition is still OFF for a period of time that is longer than ''Event Timeout'', then an event is generated. When configured, ''Make Call To'' and ''Send SMS To'' functions make a call or send an SMS to a predefined phone number. The towing function will be reactivated after {{{model|FMB1YX}}} detects a change of Ignition state from ON to OFF or if the configured ''Activation Timeout'' is reached again.
| |
| − | {{{txt_towingdout|
| |
| − | The digital output can be activated for a period of time to warn the driver. Output on-time is configured separately for each featuring case. For more information please refer to [[DOUT controls]]}}}.<br /><br />
| |
| − | | |
| − | '''NOTE''': From 03.27.xx firmware version, when the Towing event is detected, the device starts to send data to the server as configured in "On Moving" mode in the "Data Acquisition" tab. This will help to track where vehicles are towed. <br />
| |
| − | <youtube>ecsvLfNeQr0</youtube>
| |
| − | {{{crash_feature|
| |
| − | ==Crash Detection==
| |
| − | | |
| − | {{{pic_crash|[[File:Crash Detection cfg.PNG|right]]}}}
| |
| − | | |
| − | 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 Trace'' is disabled only one eventual crash record will be generated when ''Duration (ms)'' and ''Threshold (mg)'' values are exceeded. <br/>
| |
| − | | |
| − | If ''Crash Trace'' is enabled, {{{model|FMT100}}} will collect crash trace data with frequency defined by ''Trace ODR (Hz)'' parameter. Acceleration, GNSS and IO data monitoring duration during the crash event is defined by these parameters: <br/>
| |
| − | | |
| − | *''Accel duration (s)''. Acceleration data duration can be set for up to 15 seconds before crash event and 15 seconds after; <br/>
| |
| − | *''GNSS duration (s)''. GNSS data duration can be set for up to 30 seconds before crash event and 30 seconds after. <br/>
| |
| − | *''IO duration (s)''. IO data duration can be set for up to 30 seconds before crash event and 30 seconds after. <br/>
| |
| − | | |
| − | There are three configurable Crash Trace modes:<br/>
| |
| − | '''Trace Full'''
| |
| − | | |
| − | *Data tracked: all GNSS and acceleration data <br/>
| |
| − | | |
| − | '''Trace Full with IO's'''
| |
| − | | |
| − | *Data tracked: all GNSS and acceleration data with IO's, configured in I/O settings as "Crash" parameter (see picture below)
| |
| − | | |
| − | [[File:Crash event input.png|thumb|none]]
| |
| − | | |
| − | '''Trace Changes'''
| |
| − | | |
| − | *Data tracked: GNSS and acceleration data, when acceleration values are changed by more then 50mG <br/><br/>
| |
| − | | |
| − | NOTE: with Crash Trace mode enabled, it is recommended to use ''[[Codec#Codec 8 Extended|Codec 8 Extended]]'' Data Protocol. This helps to optimize crash trace data sending from device to server.
| |
| − | | |
| − | [[File:Codec 8 Extended setting.png|thumb|none]]
| |
| − | | |
| − | Each record will have accurate timestamps in milliseconds. <br/>
| |
| − | | |
| − | | |
| − | [[Image:Fmb120_crash_trace.png|600px|none]]
| |
| − | <youtube>u6w7UHbvQcU</youtube>
| |
| − | | |
| − | ==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 [[Codec#Codec 8 Extended|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]]
| |
| − | }}}
| |
