A great deal of data is constantly being reported by your vehicle, and Geotab puts special work in bringing this data to you. In this blog post we will cover a part of how the information in your vehicle is collected, analyzed, and delivered, from port to report.
Introducing On-board Diagnostics (OBD)
The OBD port is a small diagnostic port most commonly placed underneath the steering wheel and column, within reach of the driver. Modern diagnostics have a wealth of information available to them, but historically diagnostics were first implemented by individual manufacturers, without a common standard. The Society of Automotive Engineers (SAE) recommended the standard that would become OBD in 1988.
OBD was introduced to a manufacturing landscape that was developed by individual manufacturers working independently. The standard contains multiple signal patterns of which a manufacturer can choose any particular one. As the standard was prompted by emissions testing, the largest required set of diagnostics are those related to emissions. Manufacturers provide a much wider selection of diagnostics through the OBD port for use in repairs, but they are not required to follow a particular specification on these diagnostics, and the codes can differ between manufacturers, makes, models, and years.
How Geotab Compiles and Improves Diagnostics
At Geotab, we translate the various manufacturers’ implementations of OBD into a uniform set of diagnostics. We provide as much information in as useful a way as possible, regardless of the particular implementation. Geotab splits diagnostic information into measurements about the engine and particular vehicle faults, and translates multiple manufacturers’ information into a consistent set of these measurements. This can be done over a number of diagnostic standards. Sometimes this means Geotab creates a new diagnostic, dynamically taking information from the OBD, combining that diagnostic information with transformative math, and creating an improved diagnostic with an easier to understand output. For examples of when this is sometimes necessary, take a look at some of our articles on specific work for seat-belts and fuel usage, available at Reporting Seatbelt Data: It’s Not As Easy As Buckling Your Seatbelt and Dude, Where’s My Fuel?.
Credits/Author: Jesse Turner, Junior Software Developer