2ndGearRubber
Well-known member
IMO OBDII is an example of standardization gone wrong.
In the US anyways, the gov told the OEs what they had to make available, the protocols they could use, and the connector required. While the connector idea was good, "global" or "generic" OBDII isn't a ton of help fixing cars compared to the OE side. Yes, it's convenient to change ALPHAn or lambda% into the normal +/- fuel trims we're used to seeing, and limiting how much false/inferred data we get. Yes, mode $6 is invaluable for catching partial or 1 trip failures. But TONS of stuff you 100% need to diagnose even a check engine light is not available via OBDII. That doesn't even get into bidirectional control not being available in global. How can one diagnose a hybrid system or cam phaser performance issue, when that data isn't even in global OBDII?
IMO the people who wrote OBDII didn't comprehend how far ahead of the game the OEs where, and have constantly tried to play catch up. The idea of limiting proprietary software and interfaces failed. Yes, codes are standardized, some anyways. The OE side will paint a much better picture of the fault, especially if the vehicle is new enough to have post-code-number IDs, suffixes that additional details about the fault. I suppose it could be worse, $1500 easily gets you into the game, less programming capability. Usually a single guy running two tools (sub 4k invested) can fix most things with an information source available.
--------------------------------------------------------------
IMO the market is under-served for adapters which convert the most popular platforms. To be fair, if one buys into yellow or red, IMO you shouldn't really have an issue getting what you need.
In the US anyways, the gov told the OEs what they had to make available, the protocols they could use, and the connector required. While the connector idea was good, "global" or "generic" OBDII isn't a ton of help fixing cars compared to the OE side. Yes, it's convenient to change ALPHAn or lambda% into the normal +/- fuel trims we're used to seeing, and limiting how much false/inferred data we get. Yes, mode $6 is invaluable for catching partial or 1 trip failures. But TONS of stuff you 100% need to diagnose even a check engine light is not available via OBDII. That doesn't even get into bidirectional control not being available in global. How can one diagnose a hybrid system or cam phaser performance issue, when that data isn't even in global OBDII?
IMO the people who wrote OBDII didn't comprehend how far ahead of the game the OEs where, and have constantly tried to play catch up. The idea of limiting proprietary software and interfaces failed. Yes, codes are standardized, some anyways. The OE side will paint a much better picture of the fault, especially if the vehicle is new enough to have post-code-number IDs, suffixes that additional details about the fault. I suppose it could be worse, $1500 easily gets you into the game, less programming capability. Usually a single guy running two tools (sub 4k invested) can fix most things with an information source available.
--------------------------------------------------------------
IMO the market is under-served for adapters which convert the most popular platforms. To be fair, if one buys into yellow or red, IMO you shouldn't really have an issue getting what you need.


