ABS Module Dump and Coding: Bosch 8.0/9.0, ATE MK60/MK100 and TRW Used Unit Replacement
Astra H, ABS and ESP lights on, an internal control module fault stored, no communication on some days and fine on others. The ATE MK60 unit costs more than the car is worth new, and the customer has found a used one with a different last two digits on the label. That sentence covers most of the ABS work that comes across a bench, so here is what a dump can do about it and what it can’t.
What is stored in an ABS module
Less than people expect, which is why used units are often a good option:
- The coding: vehicle type, engine, gearbox, brake circuit layout, wheel size, ESP and traction features enabled. On Bosch 8.0 and 9.0 this lives in the memory area of the controller; on ATE MK60 and MK100 it’s set by diagnostic coding and stored the same way.
- The VIN on later units (from around 2008), used for matching on some brands.
- Steering angle and yaw sensor calibration on units with the sensor cluster integrated.
- Internal fault flags, which is where the ‘internal fault’ codes hide.
What a dump can fix
- A used module of the same hardware number coded for a different car: write your coding into it, or clone the whole memory.
- A module that locked itself with an internal fault after a voltage spike: a clean memory image often clears the flag.
- A VIN mismatch after fitting a used unit, where the tool refuses to code (common on VAG and BMW).
What a dump cannot fix
- Bosch 5.7 and 8.0: cracked solder joints on the controller board (the classic lost-communication-when-warm fault). That’s a rework job, not a file.
- Pump motor brushes worn out, or a pump that draws too much current.
- A sticking valve, a corroded coil, or a wheel speed sensor reading wrong. All hydraulic or wiring, all outside the module memory.
- TRW units with a burnt driver; the driver stage sits on the same board as the memory and no file heals a transistor.
Replacing a used module: the order that works
- Record the coding of the old unit if it still talks (VCDS, Diagbox, Xentry, or a good multi-brand tool). On Bosch units also read the memory on the bench if you can, before the old one dies completely.
- Match the hardware number exactly. A different suffix can mean a different valve count or a different pump; the last digits are not just software.
- Fit, connect, and code. If the tool refuses because of the VIN, write the dump instead and try again.
- Bleed with the diagnostic tool. The pump and the valves have to be cycled to get air out of the modulator; a pedal bleed alone leaves a long pedal. VCDS basic settings, the Diagbox brake bleeding routine, the Xentry ABS bleed and the equivalent in most tools do the same thing.
- Calibrate the steering angle sensor and the yaw/lateral sensor if the unit uses them, or the ESP light stays on. Then a road test with a few firm stops so the module learns the wheel sizes.
Bosch 8.0 or 9.0: how do I tell?
The label gives the Bosch number, and the type digits after the 0265 prefix tell you the family. 8.0 units are the square 2004 to 2010 style with the controller bolted to the block; 9.0 units are the smaller ones from around 2009 onwards, often with the sensor cluster inside. Our label guide shows where to look.
ATE MK60 vs MK100?
MK60 is the 2002 to 2012 generation (VAG, BMW, Opel, Ford); MK100 replaced it from around 2011 with a different connector and a locked controller that needs bench tools for the memory. Coding through diagnostics still works the same way.
Do I need to reset the module after fitting?
On most versions no reset is needed, but stored fault flags from the donor car can hang around. Clear codes in the ABS module and the cluster, cycle the ignition, road test.
Can a dump turn ESP on for a car that never had it?
No. The valves, the sensor cluster and the wiring have to exist. The coding only tells the module what is fitted; lying to it gets you a light and a module that trips into ABS-only mode.
Ask us for an ABS coding or memory file through the request form with the full label (Bosch or ATE number plus the car maker’s number) and a read of your own unit if you have one; we’ll match it against what’s on the Opel, VW and other brand pages.
More ECU guides
Audi Q7 4L 3.0 TDI Bosch EDC17CP04 Original Files by Software Version, Recovery and Immo
An Audi Q7 4L 3.0 TDI from 2008 sits in the bay with the engine ECU not answering VCDS. The last thing that happened was a…
Bosch MD1CS003 Original File: Peugeot, Citroen, Opel, Fiat and Toyota 1.5 / 1.6 BlueHDi ECU Recovery
The Bosch MD1CS003 is the engine controller of the PSA 1.5 BlueHDi (DV5) and 1.6 BlueHDi (DV6FD) engines fitted since 2017 to the Peugeot 208, 308,…
Bosch M1.7.2 Immo Off for Opel Corsa B, Astra F and Vectra A: Chip-Level Guide
The Bosch Motronic M1.7.2 (also labelled M1.7 and M1.7.1) controls the 1.6 8v/16v petrol engines in the Opel Corsa B, Astra F, Vectra A and Calibra…