Internal Control Module Software Incompatibility

Possible causes

• CommonA module was replaced but never programmed or coded to this vehicle
• CommonA used module fitted from a different vehicle, model year or specification
• CommonA software update that started and did not finish - often because battery voltage fell during programming
• CommonOne module updated while the others were left at their old versions
• CommonWrong part number fitted - physically identical, electronically different
• PossibleAftermarket tuning or a piggyback module altering what a module reports
• RareCorrupted module software

What you might notice

• One or more systems not working at all
• Warning lights that appeared immediately after a repair or a service visit
• Limp mode
• Scan tool sees the module but reports it as incorrectly configured
• Vehicle behaving differently since work was done

What to check, in order

1. Ask what was done to the vehicle recently. This code almost never appears on a car that nothing has been done to, and the answer usually is the diagnosis.
2. Read the software and part numbers from every module the tool can see, and compare them against what the vehicle's build specification calls for.
3. Do not replace the module. In most cases it is the right hardware carrying the wrong software, and a second replacement will arrive in the same state.
4. If a programming session was interrupted, it can often simply be re-run - with a battery support unit connected so the voltage cannot fall again.
5. Expect this to need manufacturer-level programming. A generic scan tool can read this code but cannot resolve it, and neither can Pin16.
6. If a used module was fitted, check whether it is locked to its original vehicle. Many are, and some cannot be transferred at all.