Skip to main content

Questions about "Near Collision" G-Force parameters and automatic detection (GO Focus Plus/Pro)

IvanAllegreMM-9898
Original Poster

Hi Geotab Community,

 

I have some questions regarding the event configuration for the GO Focus Plus/Pro cameras, specifically concerning the "Near Collision" event.

While reviewing the "Geotab Video - GO Focus Plus/Pro Triggers & Thresholds" document, I noticed this event triggers based on negative G-Force (deceleration) levels:

  • Low: -0.65G
  • Medium: -0.45G
  • High: -0.30G

 

I recently experienced two instances on the road where another vehicle dangerously cut in front of me, resulting in a near miss. In both cases, I had to swerve to avoid them instead of braking hard. The camera did not detect these incidents automatically. Fortunately, I was able to press the manual record button in time, and the video was saved successfully.

I have a few questions for the experts here:

 

  1. How should these G-Force levels be interpreted in practice? I understand it relates to braking force, but does the camera rely solely on the accelerometer (specifically harsh braking/negative Gs), or does it also use machine vision/ADAS to detect the actual proximity of the vehicle that cut in?
  2. Why didn't the camera detect it automatically? If a vehicle cuts in but the driver swerves or doesn't brake hard enough to hit that specific negative G-Force threshold, does the "Near Collision" event simply fail to trigger? Does the system account for lateral G-force from swerving in these near-miss scenarios?
  3. What sensitivity or configuration do you recommend? My goal is to automatically capture these types of scenarios (vehicles cutting off or crossing dangerously) so we don't have to rely on the driver pressing the manual button during a stressful moment.

 

Any advice, documentation, or shared experiences would be greatly appreciated. Thanks in advance!

Join the conversation

You need to be logged in to reply to this post and participate in the Geotab Community discussions.

4 Replies

Hey Ivan! Great questions and I'm glad to hear your swerved to safety but definitely important for all of us to know why it didn't automatically trigger so I'm going to tag in our GO Focus expert- the brilliant @jlox-1754​ - to see if he can shed some light.

 

It's Friday afternoon so he might not respond until next week though so please be patient with us!

 

If you have any other questions or experiences to add, please do so Jaime has even more context to work with.

 

Have a wonderful weekend!

 

Warm regards,

Gen

 

 

EishiFUN
Geotabber

Hey @IvanAllegreMM-9898​  wanted to reach out so we didnt leave you hanging. Still looking into this one so I can give you a good answer. Thank you for your patience while we look into it.

IvanAllegreMM-9898
Original Poster

Hi @EishiFUN​  and @Genevieve-1051​ ,

 

Thanks for the update! No worries at all, I know how tricky troubleshooting these types of issues can get. I really appreciate you keeping me in the loop.

 

Take your time, and I'll keep an eye out for @jlox-1754​  insights whenever he has a chance to review the case.

 

Best,

Hey Ivan, The GO Focus Plus looks at multiple factors when categorizing an event as Near Collision. The camera does not solely rely on braking force. Vehicles in other lanes, the time to collision and lateral G force experienced among other factors play a role in defining a Near Collision event.

The recommended threshold is -0.46g (Medium) but the customer can configure this based on their experience and requirement.

 

I am emailing you in order to get more context on your experience. I'd like to review the footage as well.

 

Thanks

Still have questions?