Vehicle Causing Constant Excessive Seat Belt Exceptions

Symptoms

  • Vehicle Causing Constant Excessive Seat Belt Exceptions
  • Vehicle no longer getting Seat Belt data
  • Device reset, sometimes prompted by a firmware update, happens just before seatbelt data stops logging

Applies To

  • GO Device
  • MyGeotab
  • Seatbelt

Cause

The GO device cannot read the seatbelt data from the vehicle ECU following a firmware update, needing to retry.

Resolution

Contact your Reseller or Geotab Support to apply "Clear Saved Seatbelt and Odometer" custom parameter to the vehicle, which triggers the device to restart the seatbelt search protocol.

Additional Notes

Once seatbelt data is logging again, remove the custom parameter. Applying the "Clear Saved Seatbelt and Odometer" custom parameter does not erase seatbelt or odometer data, but clears where the device gets the information from, similar to clearing cache.

How To Clear Saved Seat Belt and Odometer value from a device