As of October 2026, a remote VW and Audi session through ODIS costs $250 and covers VW, Audi, SEAT and Skoda: software updates through SVM where one is published, module coding, adaptations, and configuration after a module has been replaced. It does what the factory application does, because it is the factory application, running on our side with your pass-thru device plugged into your car.
That sentence hides four different operations, and most of the confusion about what a session can do comes from treating them as one. This post separates them, maps each to the jobs people actually book, and marks the line where a session stops and a file or a bench begins.
How the connection works
You plug a J2534 pass-thru device into the vehicle and into a Windows laptop. A small application called IgniteRemote presents that device on our workstation as though it were plugged in locally. We run ODIS against your car, with a video call open alongside so you can watch and answer questions as they come up.
Sessions run 9 AM to 9 PM Central, seven days a week, and the earliest bookable slot is thirty minutes out. What you need on your side is on our flash page: a supported device, the laptop it plugs into, a stable internet connection, and stable 12-volt power on the vehicle. That last one matters more on this platform than on most, and our battery support guide explains why.
For devices, check the compatibility matrix before you book. Universal pass-thru devices — Autel MaxiFlash XLINK, TOPDON RLink, Autel VC200, AEZ Flasher 3 — are marked compatible with the VW and Audi stack, and so is the VAS6154. Devices built for another manufacturer's software are not: a Ford VCM3 or a Volvo DICE will not load this platform. Our J2534 buyer's guide covers the choice if you do not own one yet.
The four operations
| Operation | What it does | When you need it |
|---|---|---|
| SVM update | Compares the car's modules against the manufacturer's records and applies a published software update | A known software fault with a published fix; a replaced module on old software |
| Coding | Tells a module what equipment the vehicle has | After replacing a module; after a retrofit |
| Adaptation | Sets individual stored values inside a module | After coding; after replacing a part the module has to learn |
| Basic settings | Runs a learning routine so a module calibrates itself to a component | After replacing a throttle body, a sensor or an actuator |
They are listed in the order they usually happen, and the order is not arbitrary.
SVM: the official update path
Software Version Management is the function that gives a VAG module new software through the manufacturer's own channel. ODIS reads what is fitted — hardware part numbers and software versions, module by module — and the manufacturer's system answers with what should be there. Where a newer software exists for that exact hardware, SVM applies it.
Two things follow from how that works. The update is the manufacturer's published file, not something we wrote; a session cannot give a module software that was never released for it. And the result depends on what the manufacturer's system offers for your specific vehicle, which is why our session list says “flash via SVM where supported” and not simply “flash”.
SVM is also the reason this platform needs a live connection on our side for the whole operation. It is a conversation with the manufacturer, not a file copied from a disk.
Coding: telling a module what car it is in
A modern VAG module is built to serve many variants of a vehicle. Coding is the record of which variant it is actually fitted to: which engine, which gearbox, which options, which market. A new or replacement module arrives either uncoded or coded for the car it came from, and until its coding matches the vehicle around it, it will log faults about components it expects and cannot find.
Coding is the first step after almost any module replacement, and it is the step most often skipped by someone who assumes a part with the right number is ready to run.
Adaptation: the individual values
Where coding describes the vehicle, adaptation sets values within a module — a stored position, a threshold, a behaviour that can be configured. Some are set once at the factory and need restoring after a replacement. Others are learned and need resetting when the part they describe has changed.
Basic settings: letting the module learn
Basic settings run a routine in which a module drives a component through its range and records what it finds. A replaced throttle body is the familiar example: the module needs to learn where closed and open are on the new part. Our relearn index lists which relearns can be finished inside a session and which need a drive cycle afterwards.
The jobs a session is for
A replaced control module. The largest category. The module is fitted, it communicates, and it needs to be brought up to the right software, coded to the vehicle and adapted. One session usually covers the sequence. The questions that decide whether it is straightforward are in our used ECU matching guide: a part with the wrong hardware number cannot be coded into the right one.
A published software update. A fault the manufacturer has addressed in a later software version. SVM either offers the update for your vehicle or it does not, and we can tell you which before you commit.
A retrofit that needs coding. Equipment added after the car was built that the relevant module has to be told about.
Component protection. VAG ties certain modules — infotainment and comfort electronics in particular — to the vehicle they were first fitted to. A used unit from another car powers up and then restricts itself. Lifting that restriction runs through the manufacturer's online system, and it is on the session's list where that system authorises the module for the vehicle. Our component protection post explains the mechanism and what to check before you buy a used unit.
“Half the VAG jobs that reach us as a fault are a part that was fitted correctly and never told what car it was in. The module is fine. It just has not been introduced.” — Remote programming desk, ECU Flash Cartel
Where a session stops
Our own session list carries a caveat that deserves repeating in full: not every procedure exists on every vehicle, and coverage varies by model year, module, the manufacturer's software and security requirements. Three limits are worth knowing in advance.
A module that does not communicate. A session talks to modules over the vehicle network. A unit that no longer answers has nothing to say, and that is a bench job rather than a session. Our no-communication triage post covers how to tell a dead module from a wiring fault before you ship anything.
Security-relevant operations. Immobiliser and key functions on current VAG platforms depend on authorisation from the manufacturer's system for that specific vehicle. Tell us the exact job, the vehicle and the module before booking, and we will confirm whether it is one a session can finish. We require proof of ownership for any operation that touches an immobiliser chain, on every make.
Anything that is not the manufacturer's software. A session does not tune. It installs what the manufacturer published and configures what the manufacturer made configurable.
Session, file or bench: the VAG split
VAG is the make where people most often book the wrong one of our three services, because the platform spans two decades and three very different kinds of controller.
Older Bosch ME7 cars are file work. IMMO-OFF on the ME7 immobiliser EEPROM is live in our coverage matrix, and it is an instant file: you read the chip, upload, and download the result. Our ME7 guide covers it. No session is involved, and none is needed.
MED17, EDC17 and Simos18 sit in between. Checksum correction is live for those families and IMMO-OFF is listed as coming, not as available. For a module replacement on one of these cars the session is the working route today, and our Simos18 post sets out what is and is not possible on the MQB controllers.
Simos PCR2.1 is RSA-signed and not supported for file work at all. We list it that way rather than as coming soon, for the reasons in our signed bootloader post.
The rule that sorts most cases: if the goal is to make a fitted, communicating module belong to this car, book a session. If the goal is to change what is stored inside an older controller, that is a file. If the module is off the car, damaged or silent, that is the bench. Our European car service post lays the same decision out across the other European makes.
Preparing for a session
Sessions that fail usually fail on preparation rather than on software. Our session failures post lists the six common causes, and four of them can be prevented before the appointment.
- Scan the whole car first and save the result. A list of every fault in every module, taken before anything is touched, is the only way to tell afterwards which faults the work caused and which were already there.
- Put the vehicle on a maintainer, not a jump pack and not a second battery. A software update can keep the ignition on for a long time with the engine off.
- Use a wired connection for the laptop if you can. A hotspot works — most of our customers are mobile and use one — but give it a clear signal and nothing else to do.
- Have the part numbers ready: the old module, the new one, and the VIN. A photograph of each label is better than a typed string.
- Fit the module and confirm it powers up before the session starts. A session cannot begin on a part that is still on the bench with no connector.
Our step-by-step session post follows one from booking to the final scan.
A worked example
A shop replaces a failed comfort module on an MQB-platform car with a new part. With the module fitted, the car has a list of new faults: the module reports components it cannot find and several functions do not work.
Nothing is broken. The module is uncoded. In the session we read the vehicle, run SVM to bring the new module to the published software for that hardware, code it to the vehicle's equipment, and set the adaptations the old module held. The faults that described missing components clear because the module now knows which components to expect. The shop runs a final full scan and compares it with the one they saved before the work.
Had the same shop fitted a used module from another car, the first question would have been different — whether component protection is active and whether the hardware number is one that can be coded to this vehicle. That is a question to answer before the part is bought, not after it is fitted.
Standards and the legal position
Remote programming by an independent shop rests on SAE J2534, the pass-thru standard that lets one interface carry a manufacturer's programming application, and on the access to security-related procedures administered in North America by NASTF. Both exist so that independent repairers can do the work the manufacturer's own dealers do.
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 installs the manufacturer's published software, which is by definition the emissions-compliant software for that vehicle. The federal Clean Air Act governs what may be written into an emissions-relevant controller, and it applies the same way whichever tool does the writing.
The short version
A VW and Audi session is $250 and runs ODIS on our side through your pass-thru device. It applies published updates through SVM where one exists, codes a module to the vehicle, sets adaptations and runs basic settings — the sequence a replaced module needs. It does not tune, it cannot talk to a module that is silent, and security operations depend on the manufacturer authorising that vehicle. Older ME7 immobiliser work is a file, not a session. Check your device on the compatibility matrix, put the car on a maintainer, and tell us the exact job when you book.