انقطاع برمجة الوحدة

A software or calibration write to a control module that did not finish — the supply voltage sagged, a connection was disturbed, the tool timed out, or the ignition was switched during the write.

The result is a module holding a partial image, which is worse than holding none: it may start, communicate and behave normally in most respects while some region of its data is missing or corrupt. The faults that follow tend to look like several unrelated component problems, because the damaged region governs whatever it happened to govern, and none of the named parts is faulty.

The cause is nearly always supply voltage, and it is preventable. Programming can take many minutes with the ignition on, no engine running, and the module transmitting continuously — a load a battery drains under steadily. A battery support unit is required for this work rather than recommended, and a jump pack or another running vehicle is not equivalent, because both deliver a voltage that fluctuates.

Recovery is usually reprogramming rather than replacement, and that is the point worth knowing: a module that has been mis-flashed frequently gets condemned and replaced when rewriting it correctly, on a stable supply, would have restored it. Ask for a reflash to be attempted before a new module is ordered — and expect that adaptations and calibrations will need re-entering afterwards either way.