OpenXC Vehicle Interface Firmware 6.0 Download

Posted at April 28, 2024 by PCI-DB Team

Install Driver Automatically

Device Name	OpenXC Vehicle Interface Firmware 6.0
Category	Firmware
Manufacturer	OpenXC
File Size	502 KB
Supported OS	OS Independent

OpenXC Vehicle Interface Firmware 6.0 Description

OpenXC is an open source, data-focused API for your car. By installing a small hardware module, the vehicle data becomes accessible to Android or other desktop applications using the OpenXC library.

OpenXC allows consumer devices, such as smart phones, to access data from any vehicle. Using OpenXC, you can monitor many of the sensors on a vehicle, enabling new and innovative vehicle-centric applications. Some data is required by law and more can be unlocked with support from an automaker - or a little reverse engineering effort!

Fixes:

- BREAKING CHANGE: Significantly refactored the canread and canwrite APIs to making custom handlers much easier to implement.
- BREAKING CHANGE: Refactor time.h and FrequencyClock API for clarity and usefulness.
- BREAKING CHANGE: Use uint8_t[] for CAN message payloads everywhere instead of uint64_t to remove confusion about byte order.
- BREAKING CHANGE: Using CanMessage struct in favor if loose id + data.
- BREAKING CHANGE: Removed "reset" control command.
- BREAKING CHANGE: Add "Pipeline" argument to custom signal read handler function prototype, to allow triggering arbitrary new output messages without decoding a signal by hand.
- BREAKING CHANGE: Changed USB endpoint numbers to allow for optimal performance and a new logging channel.
- BREAKING CHANGE: JSON delimiter for output data changed to '\0' from '\r\n' to match the required delimiter for input data. This requires updates to client libraries.
- BREAKING CHANGE: Changed the default platform when compiling from CHIPKIT to FORDBOARD.
- BREAKING CHANGE: Standardized most Makefile flags to get ready for dynamic configuration. Check your environment variables against the new compilation docs!
- Merge "canemulator" build into the mainline branch, controlled with the DEFAULT_EMULATED_DATA_STATUS compile-time flag.
- Added support for request/response style diagnostic messages, and a special build to automatically query for and set up recurring requests for supported OBD-II PIDs.
- Fix handling of 32-bit bitfields.
- Add support for extended CAN IDs (29-bit).
- Support configuration of CAN messages acceptance filters on the fly, rather than only at startup. This changed an API, but an internal one, so it is not a breaking change.
- Add new control command to retrive a unique device ID (only works if Bluetooth module is installed right now).
- Support control commands via UART in additional to USB.
- Moved debug logging to a secondary USB endpoint by default - re-enable UART with UART_LOGGING flag.
- Update MPIDE dependency to 2013-08* version. Re-run script/bootstrap.sh to get the latest version.
- Refactored bootstrap scripts to target specific build environments, so not everyone needs every dependency.
- Use new version of Arduino-Makefile which depends on Python and the PySerial module.
- Switch RN-42 Bluetooth modules into pairing mode if they supported so client devices don't need to poll for a connection.
- Add a power management mode that tries to infer if vehicle is running based on OBD-II engine RPM and vehicle speed.
- Remove need for external wire indicatin if UART is to be enabled on PIC32 after discovering a non-blocking USB status check API call .

About Device Firmware:

Applying a newer firmware version than the one already installed on your unit can bring various enhancements, include workarounds for diverse problems encountered by the device, and improve or add newly developed features.

On the other hand, downgrading the firmware version can recover the device’s functionality in the event of a software update either turning up faulty or causing the unit’s overall performance to drop. However, bear in mind that applying an older firmware isn’t recommended and might not always be possible.

When it comes to the update steps, due to the large variety of devices and numerous ways for installing a new firmware, it is recommended that you carefully read and understand the upgrade steps, and consider applying a different firmware only when you have familiarized yourself with the update method.

As the installation process is most of the times quite risky, this step should be taken by users that have the ability to successfully complete the update; regular users may initiate it at their own risk. Moreover, it’s best that this task be performed in a steady power environment such as the one ensured by a UPS unit.

Therefore, if you consider applying this release, hit the download button, take into account all the aforementioned aspects, and update the device’s firmware. Also make sure you constantly check with our website to ensure that you don’t miss a single new release. 

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related OpenXC Drivers