Jump to content

Template:FMX Accelerometer Features settings: Difference between revisions

From Teltonika Telematics Wiki
mNo edit summary
 
(5 intermediate revisions by 3 users not shown)
Line 71: 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 (''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}}}
===<u>Introduction</u>===
<br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/><br/>
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 96: 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==


Line 138: Line 185:


[[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]]

Latest revision as of 12:21, 25 May 2026