Table 8 Crash event values:
Crash Event element ID
247
Crash Trace operation
Depending on configuration crash record structure follows codec 8 or codec 8 extended
protocol structure. If codec 8 extended enabled crash event records are sent without any IO
elements, only GNSS and accelerometer data if it is in configured range.
Table 9 Crash trace accelerometer data structure:
String IO elements
count
2 Bytes
New IO element is introduced with FMT100 – crash accelerometer data. New IO
element ID is 0x101. It stores data from x, y and z axes. Crash accelerometer data structure is
shown below. Data being sent is integer 16 type and values are in mG.
Table 10 Crash trace accelerometer data structure:
x axis
2 Bytes
There are two configurable crash trace options: Accel duration (s) and GNSS
duration (s). They correspond to the time of accelerometer and GNSS data monitoring before
and after aa Crash Event.
5.9.4
Eventual event will be generated when FMT100 is unplugged from OBD socket.
1 – Crash detected. Eventual record.
2 – Trace changes and device is not calibrated.
3 – Trace changes and device is calibrated.
4 – Trace is full and device is not calibrated.
5 – Trace is full and device is calibrated.
String IO element ID
2 Bytes
y axis
2 Bytes
Unplug Detection
Value, meaning
Length
2 Bytes
Length Bytes
z axis
2 Bytes
Data
36
Need help?
Do you have a question about the FMT100 and is the answer not in the manual?
Questions and answers