Changes

*'''Send SMS To''' lets receive a SMS text to predefined number, when event is triggered. '''SMS Text''' lets choose preferred message text.

*'''Send SMS To''' lets receive a SMS text to predefined number, when event is triggered. '''SMS Text''' lets choose preferred message text.

}}}

}}}

<br/><youtube>CjIYGWDPJ3s</youtube><br/>

<br><youtube>CjIYGWDPJ3s</youtube><br>

==Towing Detection==

==Towing Detection==

When 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. Towing function will be reactivated after {{{model|FMB1YX}}} detects a change of Ignition state from ON to OFF or if the confgured ''Activation Timeout'' is reached again.

When 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. Towing function will be reactivated after {{{model|FMB1YX}}} detects a change of Ignition state from ON to OFF or if the confgured ''Activation Timeout'' is reached again.

{{{txt_towingdout|

{{{txt_towingdout|

Digital output can be activated for a period of time to warn the driver. Output on-time is configured separately for each feature case. For more information please refer to [[DOUT controls]]}}}.<br /><br /><youtube>ecsvLfNeQr0<youtube/><br /><br /><br /><br /><br />

Digital output can be activated for a period of time to warn the driver. Output on-time is configured separately for each feature case. For more information please refer to [[DOUT controls]]}}}.

<youtube>ecsvLfNeQr0</youtube>

 

==Crash Detection==

==Crash Detection==

[[File:Crash Detection cfg.PNG|right]]

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

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

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

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

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

There are three configurable Crash Trace modes:<br/>

'''Trace Full'''

'''Trace Full'''

*Data tracked: all GNSS and acceleration data <br />

*Data tracked: all GNSS and acceleration data <br/>

'''Trace Full with IO's'''

'''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) <br />

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

[[File:Crash event input.png|thumb|none]]

'''Trace Changes'''

'''Trace Changes'''

*Data tracked: GNSS and acceleration data, when acceleration values are changed by more then 50mG <br /><br />

*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.

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

[[File:Codec 8 Extended setting.png|thumb|none]]

Each record will have accurate timestamps in milliseconds. <br />

Each record will have accurate timestamps in milliseconds. <br/>

[[Image:Fmb120_crash_trace.png|600px|none]]

[[Image:Fmb120_crash_trace.png|600px|none]]

<br/><br/><youtube>u6w7UHbvQcU</youtube><br/>

<youtube>u6w7UHbvQcU</youtube>

==Crash Data Visualisation==

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

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

'''To start using CrashDataVisualizer'''<br/>

Download and install TAVL (version 4.15.0.1 or later) + CrashDataVisualizer applications from here:<br />

Download and install TAVL (version 4.15.0.1 or later) + CrashDataVisualizer applications from here:<br/>

''Link:'' https://teltonika.lt/client<br />

''Link:'' https://teltonika.lt/client<br/>

''Login:'' CrashDataVisualizer<br />

''Login:'' CrashDataVisualizer<br/>

''Password:'' crasHdaTa789

''Password:'' crasHdaTa789

'''To get crash data'''<br />

'''To get crash data'''<br/>

Login to TAVL application (please contact your Sales manager for TAVL login information).<br />

Login to TAVL application (please contact your Sales manager for TAVL login information).<br/>

[[File:Crash data steps.png|thumb|left]]

[[File:Crash data steps.png|thumb|left]]