By: Fabiola Grosshan
Submitted: 2010-08-30 06:00:44 | Word Count: 355
In Star Wars, the X-wing fighter often gets hit with a laser blast. To save the ship, R2D2 runs a quick diagnostic test, then turns a knob, and the audience sees the fire extinguished, the plane stabilized and the crew go on to win the day. The key thing for this likeable little robot to save the day is the ability to correctly diagnose the problem on the first try. It may have been a different story altogether if R2 had to try a few things before he got it right.
Customers expect the same level of diagnostic expertise with their vehicles: they want professionals to get it right the first time. Car manufacturers have figured out how to get it right by loading literally books of information into the on-board diagnostic systems. All of this information is then shared with the mechanic when a problem arises, zeroing in on the real culprit. Manufacturers and dealers want cars to stay on the road. Vehicles that find their way into the service bay on a regular basis do nothing for the car’s image or return sales.
[ advertisement ]
To keep diagnostic testing times down, a diagnostic scanner that contains the manufacturer’s error code, manual descriptions and detailed running information are key to successfully diagnosing the problem the first time. An OBD2 scanner is the most common way to tackle this task. But entry level units typically only display the error code and textual information that the car system reports. It does not include the original equipment (OE) manufacturer’s detailed information, parts information and more.
OBD scanner tools from companies like AutoBoss partner directly with the manufacturer to load all of the OE codes and supporting information. The units can then perform full system scans just like the dealer’s diagnostic scanner. Annual software releases to the unit allow updated codes and vehicle information to be uploaded, so that the devices continue to add value and perform at peak capacity.
