6,023
edits
Changes
Template:FMB Accelerometer Features settings (view source)
Revision as of 15:39, 6 November 2018
, 15:39, 6 November 2018→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 that is required to be detected. {{{model|FMB1YX}}} can detect events ranging between a slight tapping on the device (Threshold = 100 mG, Duration = 1 ms) and a severe accident (Threshold = 4000 mG, Duration = 5 ms).<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 that is required to be detected. {{{model|FMB1YX}}} can detect events ranging between a slight tapping on the device and a severe accident.<br/>
If ''Crash Trace'' is disabled a crash detection event will be generated (included into the sent record) only when scenario starts and finishes.<br/>
If ''Crash Trace'' is disabled a crash detection event will be generated (included into the sent record) only when crash is detected.<br/>
If ''Crash Trace'' is enabled, {{{model|FMB1YX}}} 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/>
On Crash Event detection, records will be generated from this buffer, following these conditions:<br/>
On Crash Event detection, records will be generated from this buffer, following these conditions:<br/>
'''Trace Changes'''
'''Trace Changes'''
* Every second
* With frequency defined by ''Trace ODR (Hz)'' parameter <br/>
* Acceleration changed more then >50mG <br/>
* Tracks GNSS and acceleration data, that is changed by more then >50mG <br/>
'''Trace Full'''
'''Trace Full'''
* With frequency defined by ''Trace ODR (Hz)'' parameter <br/>
* With frequency defined by ''Trace ODR (Hz)'' parameter <br/>
* Tracks all GNSS and acceleration data <br/>
'''Trace Full with IO's'''
'''Trace Full with IO's'''
* With frequency defined by ''Trace ODR (Hz)'' parameter <br/>
* With frequency defined by ''Trace ODR (Hz)'' parameter <br/>
* Every second with IO's, configured in I/O settings, under "Event only" parameter (see picture below) <br/>
[[File:Crash event input.png|thumb]]
Each record will have accurate timestamps in milliseconds. <br/>
Each record will have accurate timestamps in milliseconds. <br/>
