As of September 2026, a remote OE session programs whatever the manufacturer's own application programs on that platform — which on most of the eight we carry includes the transmission controller and the body module, usually includes ABS, and treats airbag modules as a category we decline rather than a category we are merely slow at. Sessions run $100 to $250 depending on platform, and the module type does not change the price.
This post exists because “ECU programming” has become a catch-all phrase, and the gap between what people mean and what they need is where afternoons get lost. If you are holding a job that involves a module other than the engine controller, this is the routing logic.
The TCM: the most common non-engine session we run
Transmission controllers arrive here more often than anything except the PCM itself, and they arrive in two very different shapes.
The replacement.A unit has been changed — new, remanufactured or used — and the vehicle needs it programmed and configured. This is exactly what a session is for, and it is clean work on every platform on our flash page. The trap is the used unit: a donor arrives carrying another car's configuration and adaptation history, and fitting it without the configuration step produces a car that drives worse than the one you started with. Our used-ECU matching guide covers what has to line up before a donor is worth buying at all.
The calibration update against a published bulletin. Shift quality complaints, harsh engagement, a flare under a specific condition — a meaningful share of these have a manufacturer software fix and no parts at all. An independent shop without a subscription can diagnose it perfectly and still have no way to deliver the fix. That is the single most satisfying kind of session to run, because the hard work was already done correctly before the call.
Adaptation resets are the third piece and the one people forget to mention at booking. After a fresh program, most transmissions need their learned values cleared and relearned, and on several platforms that relearn has a defined drive procedure the customer has to perform. We can run the reset inside the session; the drive cycle is yours.
“Nobody books a TCM session. They book an ECU session and then mention the transmission forty minutes in. Same price, same software, completely different plan — just tell me at the start.” — Bench technician, remote programming desk
Body, gateway and comfort modules
BCM work splits into coding and configuration. Coding tells a module which options this vehicle has; configuration marries it to the VIN and the rest of the network. Both are OE-application jobs and both run inside a standard session.
The wrinkle is component protection on VAG platforms, which is a deliberate anti-theft mechanism rather than a fault. A protected module fitted to a different car will function partially or not at all until protection is cleared through the manufacturer's own system, and there is no legitimate way around that from the outside. Our component protection guide is the full explanation of what can and cannot be done there.
Infotainment and head units are their own case: frequently a donor unit carrying a previous owner's VIN, sometimes with personal data still on it. Our radio and HMI donor guide covers what a session can rewrite and what it cannot.
| Module type | Remote session? | Notes |
|---|---|---|
| Engine controller (PCM / ECM) | Yes | The default case on all eight platforms |
| Transmission controller (TCM) | Yes | Adaptation reset in session, drive cycle is yours |
| Body control module (BCM) | Yes | Coding plus configuration; VAG adds component protection |
| ABS / stability controller | Usually | Where the OE application supports it; sensor calibration may need a scan tool on site |
| Infotainment / HMI / radio | Often | Donor units carry a prior VIN and prior data |
| Airbag / SRS control module | No | Declined as a category — see below |
| Any module that will not power up | No | Bench work, not a session |
Airbag modules: why the answer is no
We decline SRS control module work, and the reason is worth stating plainly rather than hiding behind “not supported”.
An airbag control module records crash data and locks itself after deployment by design. The aftermarket demand is overwhelmingly for clearing that lock so a deployed module can be reused — and a module that has been reset rather than replaced may not behave as designed in a subsequent collision. The National Highway Traffic Safety Administration regulates occupant-protection systems under the Federal Motor Vehicle Safety Standards, and event data recorder contents are treated as evidence in exactly the situations where the system is supposed to work.
So the position is: replace the module, have it configured through the OE application like any other part, and keep the crash record intact. That is a session we will happily run. Resetting a deployed one is not a product we sell at any price, and a vendor who offers it cheaply is selling you their liability as well as their file. Our how-to-verify-a-service post covers the wider pattern of claims that should make you pause.
What “configuration” actually writes
People use programming and configuration interchangeably and they are two distinct operations, which is why a job can be half done and appear finished.
Programmingputs software into the module — the operating code and calibration the manufacturer publishes for that part on that vehicle. A brand-new module often arrives without it, or with a version that predates the current calibration.
Configurationtells that software which vehicle it is in: the VIN, the option content, which features this particular car was built with, and where it sits on the network. Skip it and you get a module running correct software that believes it is in a different car — which produces exactly the confusing, apparently unrelated faults people bring us.
On a used module there is a third element, because the donor arrives with someone else's configuration already written. That has to be replaced rather than merely supplemented, and it is the single most skipped step in independent module replacement.
Instrument clusters and the line we will not cross
Clusters come up often enough to state a position on. A cluster replacement is a legitimate repair, and configuring a replacement cluster to the vehicle is ordinary work the OE application performs.
What we will not do is alter recorded mileage. The odometer reading is a legal record, federal law treats tampering with it as an offence, and a request framed as “matching the new cluster to the car” is frequently a request to write a number that was never true. Where a cluster genuinely has to be replaced, the correct handling is to configure the replacement and document the change, which is what a dealer would do and what a subsequent buyer is entitled to see.
That position is the same shape as our verification post: the operations a provider declines tell you more about them than the ones they advertise.
What no module type can survive
Every routing rule above assumes a module that powers up and talks. That precondition catches more bookings than any platform limitation.
If a controller is dark, water-damaged, physically cracked, or reporting an internal fault that survives every reset, no OE software reaches it over the OBD port regardless of which module it is. Those are bench jobs: our P0606 internal-error guide covers the commonest code, and the bench, boot and OBD read-method comparison explains why some modules simply cannot be handled in the car.
The other universal failure mode is the network. If several modules dropped off the bus at once, you are not looking at a programming job yet — you are looking at a wiring or power fault wearing a programming job's clothes. Our U0100 guide walks that apart, and the DTC lookup tool is free if you want to check a code before you call.
Gateways sit in front of all of it
One more thing applies across every module type rather than to any particular one. On a vehicle with a security gateway, the authorisation question is answered once for the vehicle rather than per module — so a shop that can read a body module perfectly and cannot write to it is not looking at a body-module limitation.
Full data with zero write authority is the fingerprint, and it looks identical whether the target is the engine controller, the transmission controller or the BCM. Our gateway post sets out the four legitimate routes past one, and the practical upshot for booking is simple: if every write is refused on a modern vehicle, that is one session for the vehicle, not a separate problem per module.
Booking a non-engine module properly
- Name the module at booking.“TCM replacement, used unit already fitted” is a complete brief. “Needs programming” is not.
- Say whether the part is new or a donor. That single fact changes the plan more than the module type does.
- Have the module label photographed. Drop it in the free identifier first, because what is fitted and what should be fitted often differ.
- Battery maintainer on before you connect. Body and transmission writes run long; a marginal battery fails partway rather than at the start.
- Expect a drive cycle. Transmission and some chassis work is not finished when the write completes.
Our six causes of failed remote sessions is the full pre-flight list, and the device compatibility matrix is the authoritative word on hardware.
Why this work reaches independents at all
A shop might see four transmission controller replacements a year on a given platform. A dealer-level subscription cannot be justified against that, and the cars do not stop needing the work. S&P Global Mobility put the average age of light vehicles on U.S. roads at 12.6 years in its 2024 study — the band where secondary modules fail and get replaced with used units.
The session model exists for that middle ground, and it is deliberately the same price whether the module is the engine controller or the body module, because the cost we are covering is licensed software time, not difficulty. Our subcontracting guide for shops covers pricing that on to a customer without losing the job.
Standards and the legal line
SAE J2534 defines the pass-thru interface that makes a generic device in your hand usable with a manufacturer application on ours, and NASTF administers the secure-access registry where credentialed functions are involved. Where a security gateway sits between you and the module, our gateway post sets out the four legitimate routes.
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.
Section 203(a)(3) of the federal Clean Air Act applies to a transmission or body controller exactly as it applies to an engine controller when an emissions function is involved.
The short version
If the manufacturer's application programs it, a session programs it, at the same $100 to $250 as the engine controller. TCM and BCM work is routine; ABS usually is; airbag modules are a no by policy rather than by capability. Any module that will not power up is a bench job. Name the module and say whether it is a donor when you book, and if the job turns out to sit outside what we carry, the specialist network is free to post to.