SoftHub

Fixes:

- BREAKING: Update to latest OpenXC message format, including updated binary spec.
- BREAKING: Deprecate USB control commands for version and device ID - use generic control command type instead, with the same payload format as if sent via UART/BT.
- BREAKING: Refactor tire and door handlers for use as signal decoders.
- BREAKING: Changed DEFAULT_UART_LOGGING_STATUS build config to DEFAULT_LOGGING_OUTPUT to be able to use UART, USB, or both for logging.
- Feature: Support setting explicit CAN frame format when writing messages (#230).
- Feature: Support control command to enable/disable passthrough of CAN messages on each CAN controller.
- Feature: Support control command to dynamically change the status of the CAN acceptance filter (#301).
- Feature: Support control command to dynamically change the payload format (#302). Note that binary commands sent to the VI are not yet supported, there are still bugs.
- Feature: Support new action field of diagnostic requests from OpenXC message format.
- Feature: Add a loopback property to CAN buses to support self-testing.
- Improvement: Return a command response with a status for all diagnostic request commands.
- Improvement: Update required GNU for ARM version to -4_8-2014q2-20140609 (#261).
- Improvement: Update required MPIDE version to 20140821 with associated updates to Arduino-Makefile
- Improvement: Update to latest version of chipKIT peripheral libraries.
- Improvement: Update required nanopb version to v0.3.1 (#269).
- Improvement: Compile test with LLVM's Clang, which provides much better warnings. Fix a lot of minor but important things that it found.
- Improvement: Use new self-receive capabilities in VI for a functional test suite that runs on actual hardware. See fab functionaltest .
- Fix: Don't let defined CAN messages interfere with normal operation when the CAN AF is disabled (#260).
- Fix: Pass a valid Pipeline object to signal handler (#263).
- Fix: Fix double de-reference that caused the VI to crash when receiving commands while using the binary payload format.
- Fix: Match diagnostic request command name to the OpenXC message format.
- Fix: Improve build process to make sure stray signals definitions are not unintentionally included (#249).
- Fix: Work around lack of symlinks in Windows when setting up development environment (#259).
- Fix: Calculate correct payload size when receiving data via USB endpoint 0 on PIC32.
- Fix: Respect configuration of raw write permissions for I/O interfaces (#274).
- Fix: Use blocking UART writes on LPC17xx to work around a race condition (#306)

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.