Frequently Asked Questions Who can I contact at Ford about OpenXC? The code has been released on GitHub and you don't need any special permission or agreements from Ford to use OpenXC. A number of Ford engineers participate in the, that's a good first stop. Asher Roth Believe Hype Mixtape. If you wish to use Ford's expanded data set, you will need to sign a developer agreement to get access to the. Why not just use one of the many commercial OBD-II scanners instead of OpenXC? You want to use OpenXC because it offers a superset of features compared to off-the-shelf tools.

OpenXC connects to the OBD-II port, and you have the option of using standard OBD-II diagnostic messages like every other scanner and dongle, but it's also *entirely open source* and is flexible enough to support more advanced CAN bus development (e.g. 'normal mode' CAN) and reverse engineering. OBD-II has the advantage of being a standard across all vehicles sold in North America since 1996, but the standard message set primarily concerns the emissions powertrain. The rest of the diagnostic messages are non-standard and not available to the public (and certainly not an open source project)., an OBD-II scanner manufacturer explains it well: Although Ford does implement the largest subset of the OBD-II standard, the typical vehicle only supports 20 - 40 sensors and is limited to emissions powertrain. This situation is not unique to Ford - the majority of OBD-II PIDs are non-standard. In 'normal mode', the OpenXC vehicle interface listens passively to the many CAN messages already flying across the buses that include data not covered by the OBD-II standard.