Startup Idea: Intuitive OBD-II Auto Diagnostic Tool

Startup idea to develop an intuitive OBD-II auto troubleshooting software. The program would translate cryptic error codes into understandable language, also linking the diagnostic trouble code (DTC) to relevant resources like blogs and YouTube videos. The system can either be a data mining tool or a full-blown API/Database pre-populated with information. It could also offer live updates without vendor dependence.

Having used several OBD-II auto trouble-shooter devices, I realized they all have one thing in common: they provided cryptic error codes that a user has to dig around to relate the code to equally cryptic explanations for the code. The explanations are either looked up in a book or embedded in software. The more sophisticated ones (e.g., Snap-On tools) are proprietary computers. Others run on PCs or even cell phones using Android. What is needed is something that links the Diagnostic Trouble Code (DTC) code to something even a shade-tree mechanic can understand.

The software solution could be anything from an internet data mining tool to a full-blown API/Database that is pre-populated with information. The data mining tool would find information on internet that links the code specific DTC, given the user’s input on make/model/year, to blogs and YouTube videos where people have posted real solutions. The advantage of such a solution is that it would update itself and not rely on updates from a vendor such as Snap-On.