Skip to main content
Sign in Menu

CAN changes in MiX 4000 4.10.10 firmware

Marisa Potgieter
  • Updated

Please be advised that there have been some changes to how CAN operates in the 4.10.10 firmware.

This was done to accommodate future hardware releases where there are no longer physical CAN TX (allow transmitting) jumpers that need to be configured on the OBC itself. The firmware changes will automate the jumper functionality in firmware based on the type of script selected.

In most cases this will have no impact on existing installations, with the exception of installs of a very specific type. These are typically installations where the MiX OBC would not have been requesting any data on CAN. However, it would have been transmitting an acknowledge (ACK) message to the device broadcasting the data and this ACK was necessary for the broadcasting device to keep sending.

These installs can be characterized as follows:

    1. The MiX OBC will have the TX Jumper fitted, enabling it to transmit the ACK on CAN.
    2. The MiX OBC will have a direct connection, so not through a CAN Sense device, ensuring it was able to transmit an ACK.
    3. The MiX OBC is connected to a gateway device on the vehicle and there are no other devices connected to that gateway other than the MiX OBC.
    4. The MiX OBC is directly connected to a standalone CAN device and there are no other devices on this dedicated CAN bus.

With the install types above it is possible the system would have been reliant on the MiX OBC sending this ACK message to operate correctly. CAN data on these installs could stop being delivered once the firmware is updated to 4.10.10, where the ACK is no longer automatically transmitted.

If this is the case when loading firmware 4.10.10, an updated version of the current script will be required to allow that ACK message to continue to be sent.

For example this script, Script.CAN.J1939.250KBPS.v1.23.0.3_MG will need to be update to this script Script.CAN.J1939.250KBPS.ACK_ENBL.v1.23.0.3_MG

If there are any questions, please contact Mike Sydenham.

If you require a change to your current script to enable the ACK message, please contact Gordon Jefferies

Related articles