Jump to content

Template:Gyroscope features: Difference between revisions

 
(7 intermediate revisions by 2 users not shown)
Line 21: Line 21:
* '''Continuous Monitoring''': With a high Output Data Rate (ODR) of up to 400 Hz, gyroscopes can record detailed motion changes, making them indispensable in crash detection, eco/green driving analysis, and advanced vehicle telematics systems.}}}
* '''Continuous Monitoring''': With a high Output Data Rate (ODR) of up to 400 Hz, gyroscopes can record detailed motion changes, making them indispensable in crash detection, eco/green driving analysis, and advanced vehicle telematics systems.}}}


=== Features of that utilize Gyroscope===
=== Features that utilize Gyroscope===
{{{features|The integration of gyroscopes into firmware introduces a suite of advanced functionalities, significantly enhancing motion tracking and data analysis capabilities. Key features include:
{{{features|The integration of gyroscopes into firmware introduces a suite of advanced functionalities, significantly enhancing motion tracking and data analysis capabilities. Key features include:


Line 27: Line 27:
* '''High-Resolution Data Collection''': The IMU ODR has been increased to 400 Hz, providing double the sampling rate of earlier implementations This ensures even the shortest movements are captured with high accuracy, benefiting crash detection and eco/green driving analytics.
* '''High-Resolution Data Collection''': The IMU ODR has been increased to 400 Hz, providing double the sampling rate of earlier implementations This ensures even the shortest movements are captured with high accuracy, benefiting crash detection and eco/green driving analytics.
* '''Crash Trace Enhancements''': Separate configurable durations for capturing data before and after crash events (up to a combined total of 20 seconds before + after crash event) allow for detailed reconstructions. These additionally include gyroscopic data on axis rotations.
* '''Crash Trace Enhancements''': Separate configurable durations for capturing data before and after crash events (up to a combined total of 20 seconds before + after crash event) allow for detailed reconstructions. These additionally include gyroscopic data on axis rotations.
* '''Eco-Driving Scenario Improvements''': By integrating gyroscope data, new parameter -"Total Angle Changed" during driving events allow for granular analysis of driver behavior, helping fleet managers optimize performance and safety.
* '''Eco-Driving Scenario Improvements''': By integrating gyroscope data, new parameter -'''"Total Angle Changed"''' during driving events allow for granular analysis of driver behavior, helping fleet managers optimize performance and safety.<br>
This feature can be enabled, only when:
#Eco/Green driving feature is '''enabled'''
#Source is set as '''Accelerometer'''
#Advanced Eco Driving is '''enabled'''
# Eco driving total angle changes is '''enabled'''
[[File:Total angle changed v2.png|none]]
 
* '''Advanced Vehicle Stability Monitoring''': For applications like heavy machinery or agriculture, gyroscopes monitor roll and pitch angles to ensure safe and stable operation.}}}
* '''Advanced Vehicle Stability Monitoring''': For applications like heavy machinery or agriculture, gyroscopes monitor roll and pitch angles to ensure safe and stable operation.}}}


Line 171: Line 178:


===Crash trace format explanation===
===Crash trace format explanation===
When enabled with configuration, gyroscope data is enabled in the crash trace. Special record withAVL ID 1422 is used instead of standard crash trace AVL ID 259. The format used in AVL ID 1422 record is:
When enabled with configuration, gyroscope data is enabled in the crash trace. Special record with '''AVL ID 1422''' is used instead of standard crash trace AVL ID 259. Records generated after the crash will include standard data and trace data sent with these AVL IDs:
{| class="nd-othertables_2" style="width:100%;"
{| class="nd-othertables_2" style="width:100%;"
|+
|+
Line 200: Line 207:
| style="vertical-align: middle;" |Specialized data collection during crash events.
| style="vertical-align: middle;" |Specialized data collection during crash events.
|-
|-
! colspan="6" style="text-align: left;" |Data Structure
! colspan="6" style="text-align: left;" |AVL ID 1422 Data Structure
|-
|-
| style="vertical-align: middle; text-align: center;" |-
| style="vertical-align: middle; text-align: center;" |-
Line 206: Line 213:
| style="vertical-align: middle; text-align: center;" |Int16
| style="vertical-align: middle; text-align: center;" |Int16
| style="vertical-align: middle; text-align: center;" |2 Bytes
| style="vertical-align: middle; text-align: center;" |2 Bytes
| style="vertical-align: middle;" |X-axis angular data from gyroscope.
| style="vertical-align: middle;" |X-axis acceleration data.
| style="vertical-align: middle;" |Measured during crash event.
| style="vertical-align: middle;" |Measured during crash event.
|-
|-
Line 213: Line 220:
| style="vertical-align: middle; text-align: center;" |Int16
| style="vertical-align: middle; text-align: center;" |Int16
| style="vertical-align: middle; text-align: center;" |2 Bytes
| style="vertical-align: middle; text-align: center;" |2 Bytes
| style="vertical-align: middle;" |Y-axis angular data from gyroscope.
| style="vertical-align: middle;" |Y-axis acceleration data
| style="vertical-align: middle;" |Measured during crash event.
| style="vertical-align: middle;" |Measured during crash event.
|-
|-
Line 220: Line 227:
| style="vertical-align: middle; text-align: center;" |Int16
| style="vertical-align: middle; text-align: center;" |Int16
| style="vertical-align: middle; text-align: center;" |2 Bytes
| style="vertical-align: middle; text-align: center;" |2 Bytes
| style="vertical-align: middle;" |Z-axis angular data from gyroscope.
| style="vertical-align: middle;" |Z-axis acceleration data.
| style="vertical-align: middle;" |Measured during crash event.
| style="vertical-align: middle;" |Measured during crash event.
|-
|-
Line 281: Line 288:
|}
|}


These devices must be equipped with gyroscope-enabled hardware. Clients with older models will require hardware upgrades to access this functionality. Note that gyroscope features are not available as a firmware-only update.
These devices must be equipped with gyroscope supported hardware. Clients with older models will require hardware upgrades to access this functionality. Note that gyroscope features are not available as a firmware-only update.