The most preventable way to lose a control module is to let the battery sag in the middle of a write. As of October 2026, every remote session we run asks for the same thing first: stable 12-volt support on the vehicle, holding at least 12.5 volts with the ignition on, from a supply built to hold voltage, not from a charger or a jump pack.
Our flash page lists four things you need for a session, and this is the one people treat as optional. It is the one that costs a module when it is skipped.
Why programming is hard on a battery
Starting a car asks a battery for a very large current for a second or two. Programming asks for a moderate current for a long time, and that is the harder test for a battery that is not new.
During a session the ignition is on and the engine is off. Every module on the network is awake. Depending on the vehicle, the fuel pump may run, the cooling fans may cycle, the blower may be on, and the lights may come up as modules are addressed. Nothing is putting charge back, because the alternator is not turning.
A healthy, fully charged battery rests at roughly 12.6 volts. Under that load its voltage begins to fall at once and keeps falling. A new battery may carry a short job comfortably. A three-year-old battery that starts the car without complaint every morning may not last twenty minutes above the level a module needs.
And programming jobs are not always short. A single module can take a few minutes. A software update that reaches several modules, or a replacement that has to be programmed, configured and then put through its relearns, can keep the ignition on for the better part of an hour.
What a write needs
When a module is being programmed, its old software is erased and the new software is written in its place, in blocks. Between the erase and the last block, the module does not contain a complete program.
If supply voltage drops below what the module needs during that window, one of two things happens. The module resets, abandoning the write partway. Or the write continues with a memory that is not being programmed reliably, and the result fails verification. Either way the module is left holding software that is incomplete.
Manufacturers know this, which is why their applications check battery voltage before they will begin and why most of them state a required window. Follow whatever the application asks for on your vehicle. What we want to see before a session starts is at least 12.5 volts held steady with the ignition on — steady being the word that matters.
“Nobody has ever lost a module to having too stable a power supply. We have recovered plenty that were lost to a battery the owner was sure was fine.” — Remote programming desk, ECU Flash Cartel
The four things people connect, compared
| What is connected | Holds a steady voltage? | Supplies the vehicle's full load? | Suitable for programming? |
|---|---|---|---|
| Nothing — battery alone | No, falls continuously | For a while | Only a very short job on a strong battery |
| Ordinary battery charger | No, output varies by stage | Sometimes | Poor substitute |
| Jump pack | No | Briefly | No |
| Jumper cables from a running vehicle | No, noisy and variable | Yes | No |
| Programming power supply or maintainer with a supply mode | Yes | Yes, within its rating | Yes |
An ordinary charger
A charger exists to refill a battery. It works in stages, raising and lowering its output as the battery fills, and many will pulse, pause to test the battery, or shut off when they decide the battery is full or faulty. Some will not start at all if they judge the battery too low.
None of that is a defect. It is what a charger should do. But a vehicle in the middle of a write wants a supply that does one thing: hold the same voltage while the load changes. A charger moving between stages is the opposite of that.
A jump pack
A jump pack is a battery with clamps. It can deliver a large current for a few seconds, which is its purpose. Connected for the length of a session it behaves as extra capacity, running down in step with the vehicle's battery. It regulates nothing.
A second vehicle
Jumper cables from a running car do supply plenty of current. They also bring the donor's charging system with them: the ripple from its alternator and the swings as its own loads switch on and off. That electrical noise arrives on the supply of a module that is in the middle of having its memory rewritten.
A programming supply
A unit sold for this job holds a set voltage and supplies whatever current the vehicle draws, up to its rating, with a clean output. Many good battery maintainers have a dedicated supply or programming mode that does the same. That mode is the one to use; the ordinary charging mode on the same unit is a charger.
Size it for the vehicle. A supply that cannot meet the load will let the voltage fall just as a bare battery would, only more slowly. With fans and pumps running, a modern vehicle can draw several tens of amps with the engine off, so a small trickle maintainer intended for winter storage is not the right tool.
Connecting it properly
A good supply badly connected protects nothing.
- Clamp to clean metal. The battery posts or the manufacturer's designated jump points, not a painted bracket.
- Connect before the session, and let the voltage settle. Check it with a meter at the battery, with the ignition on, before anything is written.
- Leave it alone. Do not move the clamps, open and close doors repeatedly, or switch loads on and off while a write is in progress.
- Reduce the load you can control. Headlights off, blower off, heated seats and rear screen off, nothing charging from the accessory sockets.
- Watch the reading. If the supply shows the voltage drifting down across the session, say so on the call before the next write begins.
Power for the laptop matters as well. A session depends on the computer the pass-thru device is plugged into, and a laptop that goes to sleep or runs flat mid-write interrupts the job as surely as the vehicle battery would. Plug it in and turn off sleep.
It applies to reading, too
File work has the same requirement, for a quieter reason. Reading a module does not erase anything, so a voltage dip during a read does not damage the module. What it damages is the file.
A read taken on a sagging supply can stop early, or the tool can fill a region it failed to reach with padding and report success. The file looks complete. It is not, and it will be refused when you upload it. Our upload-rejection post covers what a valid read looks like, and unstable power during the read is one of the routine causes.
On the bench the same rule holds with a different supply. A module read out of the car is powered from a bench supply, and that supply needs to be stable and set correctly for the module. Our bench, boot and OBD read methods guide covers the access levels; whichever one you use, write-back is the step where voltage matters most. Our own ordering checklist for file service carries the line in so many words: battery support recommended when writing back.
If it goes wrong anyway
Suppose the voltage falls and a write fails in the middle.
Do not switch the ignition off. Do not disconnect the pass-thru device, the laptop or the battery. A module in this state is often still in its programming mode and still listening, and that is the condition recovery depends on.
Restore stable power first. Then let the technician use the recovery the manufacturer's application provides. Many interrupted writes are recovered in the same session, and our interrupted flash recovery post explains how and when.
If the module will no longer communicate afterwards, it has moved from session work to bench work. Our no-communication triage post covers the checks that confirm it, and a module that went silent during a write is one of the more recoverable kinds of dead: the hardware is usually undamaged and the software is simply incomplete.
This is also the best argument for taking a backup where the platform allows one. A verified original read is what lets a module be put back exactly as it was, and our return ECU to stock post makes that case.
Why this is the cheapest insurance in the job
Set the numbers side by side. A remote session costs from $100 to $250 depending on the platform. A replacement module costs what the part costs, plus the programming to marry it to the car, plus the time the vehicle spends immobile while it arrives. A power supply suited to programming is bought once and used on every job after.
Of the six causes in our session failures post, power is the one entirely within the customer's control and the one with the most expensive failure. Connection drops can be resumed. A wrong part number is discovered before anything is written. A voltage collapse arrives without warning in the one window where it does damage.
For a shop that programs regularly, the supply belongs on the same shelf as the pass-thru device. Our J2534 buyer's guide covers the device side of that kit, and the compatibility matrix shows which devices work with which platform.
A worked example
A mobile technician books a session to program a replacement transmission controller on a five-year-old pickup. The truck starts normally, and the battery reads 12.5 volts at rest.
With no support connected, the ignition goes on and the fans start. Within a few minutes the battery is under 12 volts and still falling. The application's voltage check refuses to begin, and the session waits while a supply is found. Annoying, and the good outcome: nothing was written.
The bad version of the same job is the battery that sits just above the threshold when the check runs and sags below it eight minutes into the write. The check passed. The write did not.
With a supply connected before the call, the same truck holds a steady voltage for the whole session, the controller programs, the relearns complete, and the final scan is clean. The difference between the two outcomes was connected before the technician picked up the laptop. Our step-by-step session post shows where in the sequence that check falls.
Standards and the legal position
Pass-thru programming by independent shops rests on SAE J2534, and the manufacturers' own service information for each programming procedure states the supply conditions it requires. Access to that information for independent repairers is part of what NASTF exists to support. Read the manufacturer's instruction for the vehicle in front of you; it outranks any general figure, including ours.
We do not provide emissions defeat, delete files, or services intended to bypass emissions laws. Our services exist for tuning preparation, diagnostics, repair, motorsport, and off-road use where legally permitted. Customer is responsible for confirming legal use in their location and application.
A session that completes on stable power leaves the vehicle on the manufacturer's published software. The federal Clean Air Act governs what is written into an emissions-relevant controller, whichever tool does the writing.
The short version
Programming runs the ignition with the engine off, and a battery alone falls the whole time. Use a programming supply or a maintainer in its supply mode, sized for the vehicle, clamped to clean metal and connected before the session, holding at least 12.5 volts steady. A charger varies, a jump pack runs down, and a running donor vehicle is noisy. Keep the laptop on mains power as well. If a write fails anyway, leave everything connected and restore power before anything else. Then book the session knowing the one variable you control is handled.