Blacky
December 9th, 2022, 09:20 AM
I've started this thread so that customers who have reported this issue have a place to discuss symptoms and possible solutions to this problem.
Recently (in the last few months) we have seen multiple reports of late model CM2450B (CMF) controllers failing the flash process and reporting error $0331 which means "Request out of range".
This failures usually occurs because one or more modules on the CAN bus/network continue to transmit data after a "bus silence" request has been issued.
The messages being transmitted appear to be from a module (or modules) that request data for, among other things:
Primary_Accelerator_Pedal_Position
Instantaneous_Percent_Load
Target_Gear
Current_Gear
The module (or modules) responsible for requesting that data must be identified and disconnected from the CAN bus or powered down so that they can no longer interfere with the flash process.
We have not yet been able to identify the module (or modules) responsible for requesting that data. It appears, based on the data being requested, that the module is some sort of tracking/logging device that is possibly recording the driver's inputs (throttle, gear etc.) to the vehicle. Possibly an insurance or extended warranty validation/data logger.
For now, until the module(s) can be identified, the best way to successfully flash the ECM is to remove it from the vehicle and use a bench harness.
You can purchase bench harnesses here: https://bench-force.com/collections/ecu-programming-harnesses
Here is a trace of the flash process failing due to the negative response codes from the ECM when the ECM is trying to reject the rogue module's requests for data during the flash process. The trace does not include the actual requests from the rogue module, just the ECM's negative responses.
24283
Here is a sample trace of the data that includes the data being transmitted by the rogue module on the CAN bus.
The blue messages are the messages being transmitted by the rogue module, the green messages are the ECM's negative response rejecting those requests. The red block identifies the repeating message schedule from the rogue module(s).
24282
==============================
An updated firmware version is attached that includes a "Rogue module detector" option. The new option will emit an audible "tick" whenever a module transmits a message while the CAN network has been commanded to be silent.
Select the option and while you can hear the audible ticks, disconnect each module in turn from the CAN bus, or power down each module in turn until the ticks stop. When the ticks stop you know that you have disconnected the actual module causing the messages to be transmitted.
To use the new firmware:
Download the attached file, unzip it into the folder: \Program Files (x86)\EFILive\V8\Firmware.
Use the EFILive Explorer program to program in the new firmware.
Use the new option: Tune->F1: Tuning -> F4: Test OBD Network -> F4: Monitor Rogue Modules -> F1: Monitor CAN J1979
If you hear ticking sounds from the V3 device you know that one or rogue modules are transmitting messages.
If you hear nothing, then no modules are transmitting messages.
The test will run forever, you must press X to exit the test.
Regards
Paul
Recently (in the last few months) we have seen multiple reports of late model CM2450B (CMF) controllers failing the flash process and reporting error $0331 which means "Request out of range".
This failures usually occurs because one or more modules on the CAN bus/network continue to transmit data after a "bus silence" request has been issued.
The messages being transmitted appear to be from a module (or modules) that request data for, among other things:
Primary_Accelerator_Pedal_Position
Instantaneous_Percent_Load
Target_Gear
Current_Gear
The module (or modules) responsible for requesting that data must be identified and disconnected from the CAN bus or powered down so that they can no longer interfere with the flash process.
We have not yet been able to identify the module (or modules) responsible for requesting that data. It appears, based on the data being requested, that the module is some sort of tracking/logging device that is possibly recording the driver's inputs (throttle, gear etc.) to the vehicle. Possibly an insurance or extended warranty validation/data logger.
For now, until the module(s) can be identified, the best way to successfully flash the ECM is to remove it from the vehicle and use a bench harness.
You can purchase bench harnesses here: https://bench-force.com/collections/ecu-programming-harnesses
Here is a trace of the flash process failing due to the negative response codes from the ECM when the ECM is trying to reject the rogue module's requests for data during the flash process. The trace does not include the actual requests from the rogue module, just the ECM's negative responses.
24283
Here is a sample trace of the data that includes the data being transmitted by the rogue module on the CAN bus.
The blue messages are the messages being transmitted by the rogue module, the green messages are the ECM's negative response rejecting those requests. The red block identifies the repeating message schedule from the rogue module(s).
24282
==============================
An updated firmware version is attached that includes a "Rogue module detector" option. The new option will emit an audible "tick" whenever a module transmits a message while the CAN network has been commanded to be silent.
Select the option and while you can hear the audible ticks, disconnect each module in turn from the CAN bus, or power down each module in turn until the ticks stop. When the ticks stop you know that you have disconnected the actual module causing the messages to be transmitted.
To use the new firmware:
Download the attached file, unzip it into the folder: \Program Files (x86)\EFILive\V8\Firmware.
Use the EFILive Explorer program to program in the new firmware.
Use the new option: Tune->F1: Tuning -> F4: Test OBD Network -> F4: Monitor Rogue Modules -> F1: Monitor CAN J1979
If you hear ticking sounds from the V3 device you know that one or rogue modules are transmitting messages.
If you hear nothing, then no modules are transmitting messages.
The test will run forever, you must press X to exit the test.
Regards
Paul