Line 135: |
Line 135: |
| 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== | | ==Excessive Idling== |
| | | |
Line 142: |
Line 142: |
| 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/> | | <br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/> |
| + | }}} |
| {{{unplug_feature|==Unplug Detection== | | {{{unplug_feature|==Unplug Detection== |
| | | |
Line 179: |
Line 180: |
| '''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 /> | | '''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> | | <youtube>ecsvLfNeQr0</youtube> |
− | | + | {{{crash_feature| |
| ==Crash Detection== | | ==Crash Detection== |
| | | |
Line 217: |
Line 218: |
| [[Image:Fmb120_crash_trace.png|600px|none]] | | [[Image:Fmb120_crash_trace.png|600px|none]] |
| <youtube>u6w7UHbvQcU</youtube> | | <youtube>u6w7UHbvQcU</youtube> |
− | | + | }}} |
| ==Crash Data Visualisation== | | ==Crash Data Visualisation== |
| | | |