As of September 2026, the most common reason a freshly programmed module “still isn't right” is not the programming — it is a relearn nobody ran. A replacement controller arrives with empty adaptation memory. The software is correct, the configuration is correct, and the car still idles poorly, shifts oddly, or lights the traction lamp on the first corner, because the module has not yet learned the things the old one knew.
This is the index: which relearns a module swap can trigger, which run inside the session, which need a scan tool on site afterwards, and which only a drive cycle can finish. Bookmark it before the module goes in, not after.
Why a new module starts stupid
Every long-lived controller accumulates a private set of corrections. The engine controller learns how far the crank trigger wheel actually deviates from nominal, what the throttle plate's true closed position is, and how much fuel trim each bank needs. The transmission controller learns clutch fill times. The steering angle sensor learns where straight ahead is. None of that is in the calibration file — it is measured, on your car, over time.
Program a replacement and all of it resets to the factory default. The default is a starting point, not an answer, and on some systems the module will refuse to operate normally until a specific procedure tells it the default is now safe to depart from.
| Relearn | Triggered by | Where it happens |
|---|---|---|
| Crank/CKP variation | Engine controller replaced or reflashed | In session, then a road procedure on some platforms |
| Throttle and idle position | Engine controller or throttle body replaced | In session; a few platforms self-learn at key-on |
| Fuel trim reset | Engine controller replaced | Drive cycle only |
| Transmission adaptation | TCM replaced, or engine controller on integrated units | In-session reset, then a drive cycle |
| Steering angle sensor zero | ABS, SAS or steering column work | Scan tool on site, vehicle stationary and straight |
| ABS sensor calibration | ABS controller replaced | Scan tool on site plus a low-speed drive |
| TPMS sensor registration | BCM or TPMS receiver replaced | Scan tool or a drive, platform-dependent |
| Immobiliser and key registration | Engine controller or immobiliser module replaced | In session, keys present |
The three that get skipped most
Crank variation.On several platforms the engine controller cannot arbitrate misfires until it has measured the trigger wheel's own tolerance. Skip it and the car may run acceptably while setting random misfire codes it cannot attribute to a cylinder. If you are seeing P0300 on a car that genuinely does not feel like it is misfiring, this is the first thing to check.
Steering angle. Nothing about an engine controller touches it, which is precisely why it gets forgotten on jobs that involved disconnecting the battery or pulling a column. The stability system needs to know what straight is; until it does, it will either disable itself or intervene at the wrong moments.
Transmission adaptation. A reset TCM shifts firmly and imprecisely, and the customer interprets that as a fault in the work you just did. Saying so before the car leaves costs one sentence and prevents the return visit.
“Half the calls about a bad reflash are a car that drives differently because it has forgotten everything, and will be normal again in fifty miles. Tell them first and it's a feature.” — Remote programming desk, ECU Flash Cartel
What a session can and cannot cover
An OE programming session on any of the eight platforms on our flash pageruns the manufacturer's own application, which means every procedure in that application is available during the session: the immobiliser marriage, key registration, configuration, and the in-session resets for crank variation, throttle position and transmission adaptation.
What the session cannot do is drive the car. Anything whose completion condition is “after N miles at varied load” or “after a complete warm-up cycle” belongs to the person holding the keys. It is worth saying plainly that this is normal, not a limitation of remote work — a technician standing next to the car has exactly the same constraint.
For non-engine controllers the coverage question is broader than people expect. Our post on TCM, BCM, ABS and SRS work sets out what each module family needs after replacement, and it is worth reading before assuming a session that covers your engine controller covers the rest of the car.
When the relearn was the real problem all along
A no-start after a module swap is almost never a relearn — that is immobiliser territory, and the branch is in our swapped-ECU no-start post. But a runs-badly after a module swap very often is.
The distinguishing question is whether the behaviour is improving. A relearn that is in progress gets better over a tank of fuel. A configuration fault does not improve, and a wiring fault does not improve either. If day three is the same as day one, stop waiting and start diagnosing.
A specific trap worth naming: after an IMMO-OFF the engine controller no longer talks to the immobiliser, and some platforms respond by leaving the security lamp on permanently or by disabling functions that were keyed to a successful handshake. That is expected behaviour, not an incomplete relearn, and our post on what changes after an IMMO-OFF lists exactly what stops working.
Configuration mismatches masquerading as relearns
The second family of false alarms is configuration. A module that is correctly programmed but wrongly configured produces faults that look like unfinished learning — lamps on, functions absent, values out of range — and no amount of driving fixes them.
C0561, system configuration mismatch, is the honest version of this code: the module is telling you directly that what it believes about the vehicle and what the vehicle actually is do not agree. That is a session task, not a drive cycle.
What you need on site, and what you do not
A remote session can drive every procedure the manufacturer's application exposes, which covers the in-session resets. The stationary procedures that need a scan tool at the vehicle are a different matter, and it is worth knowing which is which before the car is booked in.
Covered by the session: crank variation where the platform runs it as a service routine, throttle and idle relearn, transmission adaptation reset, immobiliser marriage, key registration, and the configuration writes that several of these depend on.
Needs somebody at the vehicle: steering angle zero, which requires the wheels straight and the vehicle stationary; ABS sensor calibration, which usually needs a low-speed drive immediately afterwards; and TPMS registration, which on many platforms needs a trigger tool at each wheel.
Needs nothing but time: fuel trim, and the long-term half of transmission adaptation. These complete themselves across a range of load and temperature conditions that no tool can shortcut.
Platform habits worth knowing
The detail varies by manufacturer and the service information for your platform is authoritative, but a few patterns hold widely enough to plan around.
Some platforms perform the crank variation learn automatically during a controlled deceleration and require a specific road procedure to trigger it; others expose it as a menu item that completes in the bay. Knowing which you have decides whether the car can be handed back immediately.
Throttle relearn is frequently automatic at the next few key cycles, which is why it is the relearn people most often get away with skipping — and why the exceptions catch them out.
Transmission adaptation almost always benefits from an explicit reset rather than being left to overwrite itself. A TCM carrying adaptations learned against a different engine controller's behaviour is a common source of complaints after an engine controller swap, and the reset is free during the session.
Steering angle is the one most often forgotten entirely, because nothing about an engine controller job suggests it. The trigger is not the module — it is the battery disconnection, and that happens on almost every job.
What to tell the customer before they drive away
Three sentences, and they prevent most of the callbacks.
The first tank will feel different. Shift points, idle quality and throttle response are all being relearned, and the car will be smoother in fifty miles than it is in five.
It should improve every day. This is the useful diagnostic to hand them, because it converts a vague worry into a test they can run themselves. Improving is normal. Static is not.
Come back if anything is the same on day three. A relearn that has not finished by then is not a relearn, and the sooner it is looked at the less likely it is to be diagnosed as the relearn it is not.
A customer given those three sentences interprets normal post-programming behaviour as normal. A customer given none of them interprets it as the work having failed, which produces a return visit for a car that was always going to be fine.
A practical order of operations
The sequence that produces the fewest return visits is not complicated.
Program and configure the module. Complete the immobiliser and key work while the session is live — it is the step that cannot be deferred, because a car that will not start cannot complete anything else. Run every in-session relearn the application offers before disconnecting; they cost minutes during the session and a second booking afterwards. Do the stationary procedures that need a scan tool next, steering angle first because the stability system depends on it. Then drive it, and tell the customer what the first fifty miles will feel like.
Before any of that, confirm the platform is covered. Our compatibility page lists what each application handles, and checking it first is cheaper than discovering a gap with the car on the lift.
The standards underneath
Fault codes are readable across manufacturers because SAE J2012 defines the diagnostic trouble code format, and independent shops can run manufacturer applications at all because SAE J2534 standardises the pass-thru interface. Secure functions that need credentials run through the registry administered by NASTF. The relearn procedures themselves are manufacturer-specific and live in the service information for your platform — there is no universal list, which is why this page is an index of categories rather than a set of steps.
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.
Telling a relearn apart from a fault
The two present similarly on day one and diverge sharply afterwards, and the shape over time is the most reliable test available without a scan tool.
A pending relearn improves. The car is worse on the first drive than the fifth, and worse on the fifth than the tenth. The direction of travel is toward normal, even if it starts a long way from it. Nothing new appears in the code memory while it happens.
A fault does not improve, and often announces itself. It is the same on day ten as day one, or it worsens, and it usually arrives with a stored code that returns after clearing. A lamp that keeps coming back is a fault; a car that feels unfamiliar but sets nothing is almost always adaptation.
A configuration error stays constant and specific. One system behaves wrongly in exactly the same way every time — a gauge reading the wrong scale, a feature absent that should be present. That is a module that was programmed correctly and told the wrong thing about the vehicle, and no amount of driving will change it.
The short version
A new module knows nothing about your car. Run the in-session relearns while the session is open, do the stationary scan-tool procedures before the car leaves, and expect the drive-cycle items to finish themselves over the next tank. If behaviour is not improving day by day, it is not a relearn — it is configuration or wiring, and it needs diagnosis rather than patience. Book the session on the flash page and say which module was replaced; that one fact determines which half of this list applies to you.