Has anyone heard what ineos are doing with OBD codes? Will all codes be open and available i.e. freely listed.
Usually, there is a standard to be obeyed. Be it CAN or SQL or whatever.
But no company would sign a standard that restricts it and leaves no backdoor open for its own "ingenuities". Therefore, a "manufacturer-specific" signature is almost always built in, which allows a manufacturer to do anything that does not comply with the standard. For example, it comes in the form of a new token (CAN bus token, SQL keyword, to name just two) that says, "This is Ineos IP," and usually has an implicit or explicit length that tells bus participants (for example), "Here come 80 bits of Ineos." So they (the bus participants) can (and actually have to), if not made by Ineos, simply ignore the following 80 bits and continue listening to the bus after that. Within those 80 bits (or 640, 256, or 16, or whatever length the token defines or the documents specify) Ineos can do whatever they want. Undocumented, or, if they're nice, documented somewhere, for a modest ... cough
... fee, of course.
And everyone is happy: the committee for the standard, because everyone has signed. The manufacturers because they have a playground where can do what they want, the association representing the standard because the manufacturers have to pay dearly for their vendor codes, and again the manufacturer because he can charge for access to the Ineos/Siemens/Bosch/IBM/Oracle ... -specific documentation. That's more or less how it is with any standard, at least as far as it regulates IT things.
In short, there will be a minimum standard, and also "secret" manufacturer codes - which will be reverse engineered after a few years. And then comes a new model series.
Here is an example where the AUTOSAR (c) general CAN structures are described. They are part of an open standard. Written for developers and other lunatics.
EDIT: wording
