Thirty model years of Audi & VW run on a handful of Bosch brains — ME7 to MG1, EDC15 to EDC17, and the DSG boxes behind them. Find your era, learn how it's flashed, and see exactly what VAGPULSE can do with it today.
Your engine's ECU family — not its badge — decides how it is read and flashed. It follows the year and the fuel: older petrol is ME7, modern petrol is MED / Simos / MG1, and every diesel is an EDC. VAGPULSE reads the real part number off your ECU and picks the right path automatically.
| ECU family | Years | Fuel | Powers (examples) | How it talks | In VAGPULSE today |
|---|---|---|---|---|---|
| ME7 / ME7.1 | 1998–2007 | ⛽ petrol | 1.8T AWP/AMU, 2.7T APB/BEL, 4.2 V8 | K-line · KWP | READ · TUNE · FLASH |
| ME7.1.1 RSA-signed | 2002–2008 | ⛽ petrol | RS4/S4 4.2 BBK/BHF, 4Z | K-line · KWP | READ · TUNE · FLASH |
| MED9.1 | 2005–2012 | ⛽ petrol | 2.0 TFSI BWA/BPY/CCTA, 3.2 VR6 | CAN · TP2.0/UDS | READ · LOG · TUNE PLAN |
| MED17 · MG1 | 2010–2026 | ⛽ petrol | EA888 gen3 CJX/DKZ, 3.0 TFSI, newest MG1 | UDS · CAN/DoIP | READ · LOG · TUNE PLAN |
| EDC15 PD | 1999–2006 | 🛢️ diesel | 1.9 TDI PD ASZ/BXE, 2.5 V6 TDI | K-line · KWP | READ · TUNE · FLASH |
| EDC16 | 2003–2010 | 🛢️ diesel | 2.0 TDI BKD/BMN, 3.0 V6 TDI | CAN · TP2.0 | READ · LOG · TUNE PLAN |
| EDC17 CR | 2008–2026 | 🛢️ diesel | 2.0 TDI CR CFFB/CUNA, 3.0 V6 TDI | UDS · CAN/DoIP | READ · LOG · TUNE PLAN |
| Simos PCR2.1 · 18 · 19 | 2012–2026 | ⛽/🛢️ | EA211 1.4/1.5 TSI, newest TSI/TDI | UDS · CAN/DoIP | READ · LOG · TUNE PLAN |
| DSG / S-tronic TCU | 2003–2026 | ⚙️ gearbox | DQ250 · DQ500 · DL501 · DQ200 · DQ381 · DL382 | CAN · UDS | ID · LIMITER PLAN |
VAGPULSE reads, logs and plans a tune on every family above, all the way back to 1996. It only writes to an ECU whose map locations are verified on real hardware: ME7, ME7.1.1 and EDC15 are flash-validated now; the modern MED/Simos/EDC17 families are read-and-plan while their checksums are validated on the bench — because a wrong write bricks the ECU, and we will never guess with your car. Load a file it doesn't recognise and tuning switches off, with the reason shown, rather than applying another ECU's addresses and hoping.
You don't have to guess — VAGPULSE reads it. But here's the quick mental model, by era.
Whatever the year: connect → read your ECU out → log a full pull → plan the tune to what your car actually showed. On a flash-validated family you then write it and log again; on the newer families you keep the baseline read and the plan, ready for the day its flash path is validated. Same honest workflow from a 2001 1.8T to a 2026 TDI.
The very latest cars can gate factory programming behind DoIP (diagnostics over Ethernet) and SFD security. Diagnostics, coding and logging still work over the normal OBD-CAN port on almost all of them; full DoIP flashing is the one frontier still being built. If your car needs it, you'll be told plainly — never left guessing.
Everything in this chapter is something VAGPULSE does on a real car: read the ECU over OBD, see these same maps by name, and flash a checked file back with your original saved first.
See VAGPULSE