Hi team, does anyone know what G-force parameters the GO device uses to record a vehicle collision?
If you could share any articles that explain this, I'd really appreciate it.
Best regards.
Hi team, does anyone know what G-force parameters the GO device uses to record a vehicle collision?
If you could share any articles that explain this, I'd really appreciate it.
Best regards.
You need to be logged in to reply to this post and participate in the Geotab Community discussions.
Hey @danielaramirez-1969 ,
Great question! Thank you for asking it in our community I used an AI tool to help compile this answer, so please let me know if anything needs clarification. I know it is a bit more than you asked but I hope the other details give you some good context to how we look at collisions.
The GO device uses its built-in 3-axis accelerometer to detect collisions. There are two layers to how this works:
1. Device-level hardware trigger
At the firmware level, the GO device fires a collision-level acceleration event (DiagnosticAccidentLevelAccelerationEventId) when the G-force measured across any axis exceeds 2.5g. The accelerometer monitors three axes — forward/braking, lateral, and vertical — so the threshold can be crossed by a frontal impact, a side impact, or a rollover event. There is also a minimum speed requirement of 4 km/h (configurable via the MinAccidentSpeed device parameter) — impacts at very low or zero speed will not trigger a collision record regardless of G-force.
2. Server-side collision rules
On top of the hardware trigger, MyGeotab has a set of collision exception rules that analyze the accelerometer data together with GPS and other signals using ML models on the server side. These are the rules you would see in your database:
- Major Collision and Minor Collision — the enhanced rules powered by the ML model
- Near Collision Warning — a lower-severity alert
- Possible Collision (Legacy) — the older threshold-based rule
The enhanced rules take additional inputs like vehicle class and travel speed into account, so not every hardware-level trigger will automatically generate a Major or Minor Collision exception event — the model evaluates the full picture.
In summary, the core hardware threshold is 2.5g with a minimum speed of 4 km/h, but whether that results in a collision exception event in MyGeotab also depends on the server-side model and which collision rules are active in your database.
Please let us know if you have any follow-up questions — happy to help!
Have a great day!
Eishi FUN
Hey @danielaramirez-1969 ,
Great question! Thank you for asking it in our community I used an AI tool to help compile this answer, so please let me know if anything needs clarification. I know it is a bit more than you asked but I hope the other details give you some good context to how we look at collisions.
The GO device uses its built-in 3-axis accelerometer to detect collisions. There are two layers to how this works:
1. Device-level hardware trigger
At the firmware level, the GO device fires a collision-level acceleration event (DiagnosticAccidentLevelAccelerationEventId) when the G-force measured across any axis exceeds 2.5g. The accelerometer monitors three axes — forward/braking, lateral, and vertical — so the threshold can be crossed by a frontal impact, a side impact, or a rollover event. There is also a minimum speed requirement of 4 km/h (configurable via the MinAccidentSpeed device parameter) — impacts at very low or zero speed will not trigger a collision record regardless of G-force.
2. Server-side collision rules
On top of the hardware trigger, MyGeotab has a set of collision exception rules that analyze the accelerometer data together with GPS and other signals using ML models on the server side. These are the rules you would see in your database:
- Major Collision and Minor Collision — the enhanced rules powered by the ML model
- Near Collision Warning — a lower-severity alert
- Possible Collision (Legacy) — the older threshold-based rule
The enhanced rules take additional inputs like vehicle class and travel speed into account, so not every hardware-level trigger will automatically generate a Major or Minor Collision exception event — the model evaluates the full picture.
In summary, the core hardware threshold is 2.5g with a minimum speed of 4 km/h, but whether that results in a collision exception event in MyGeotab also depends on the server-side model and which collision rules are active in your database.
Please let us know if you have any follow-up questions — happy to help!
Have a great day!
Eishi FUN
@EishiFUN Great, thank you so much, Eishi!☺️