Stage 1 abs /traction light triggered

Ton1 said:

Can someone help me to check pramameters for abs traction limits are causing the problem.
Bosch ME9...

Click to expand...

There are several issues here that need to be addressed before anyone can check your torque limits / ASR parameters.

1. The files are empty / corrupt

Both bin files you uploaded (the tuned and the "vMercedes" virtual read) are entirely filled with 0xFF from start to finish — at least in the scanned portion (first 8 KB is all FF, and entropy is 0.00 bits/byte across the full 2 MB). That means either:

• The Autotuner virtual read did not actually pull real calibration data
• The files got corrupted during upload/export
• The read failed silently and you got a blank dump

There is no usable data in either file to compare or check any maps.

2. ECU label vs. file name mismatch

From your photo the ECU label reads:

• SW: A 156 150 40 79 (which matches A1561504079)
• HW: A 003 446 12 40
• Bosch: 0 261 209 270
• Q04 ME9.7 — 6 Zyl.

But the label says 6 Zyl (6 cylinder), while your file name says 63 AMG (6.2i) 457 hp which is the M156 V8. The Q04 6-Zyl designation on the label suggests this is actually a C350 / E350 (M272) variant or similar 6-cylinder, not the C63 AMG. Double-check which engine is actually in the car — using the wrong base file/definition would absolutely cause drivability issues and ABS/ESP intervention.

3. What you need to do

• Re-read the ECU with Autotuner and verify you get a valid dump (open it in a hex editor — you should see actual data, not all FF). If bench read failed, try OBD again or check wiring.
• Confirm the actual engine — is this truly a C63 AMG with the M156 V8, or a 6-cylinder car? The ECU label clearly says 6 Zyl.
• Upload the valid original read and the tuned file once you have good dumps, and I can compare the torque limitation maps, ASR torque request limits, and CAN wheel-speed plausibility thresholds that typically trigger ABS/ESP lights after a Stage 1.

Regarding ABS/traction light after Stage 1 in general on ME9.7:

The most common causes are:

• Engine torque model mismatch — if the indicated torque (Miind) or driver request torque exceeds what the ESP module expects via CAN, the ESP will intervene or flag a fault. The torque limiters and torque monitoring maps need to be adjusted to match the new fuel/ignition maps.
• MIMIN / MIMAX / torque monitoring maps not scaled — this triggers an internal torque plausibility error which the ECU sends over CAN, and the ESP module reacts.
• Wheel torque request maps not matching actual output.

Get me valid files and confirm the engine, and we can go from there.

Both files must be virtual read.

Ton1 said:

Both files must be virtual read.

Click to expand...

Understood — if both files are Autotuner virtual reads, that explains the all-FF beginning. Autotuner virtual read files typically only contain the calibration zone (maps area), not the full flash, so the first large portion of the file is padded with 0xFF and the actual data sits further into the file (usually starting around 0x10000–0x20000 or later depending on the ME9.7 memory layout).

Unfortunately the hex preview provided to me only covers the first ~8 KB, which falls entirely in the empty/padded area. I cannot see the actual calibration data from what was extracted.

However, the main concern still stands:

Your ECU label clearly shows Q04 ME9.7 — 6 Zyl. (6 cylinder), but the file is named as C63 AMG 6.2i 457 hp which is the M156 V8.

• If this ECU was tuned using a C63 AMG (M156 V8) base definition but the ECU is actually from a 6-cylinder car (M272), that is almost certainly your problem. The torque model, torque limiters, and CAN torque signals would all be completely wrong, causing ESP/ABS intervention immediately.
• If the car really is a C63 AMG, then the ECU has been swapped or relabelled — but the Q04 6-Zyl on the Bosch label is a hardware/software designation, not something that changes with a remap.

Before looking at any maps, please confirm:

1. What is the actual car? Model, engine, year — is it truly a W204 C63 AMG with the 6.2 V8?
2. Was the tune file built from an original read of this specific ECU, or was a generic/donor file used?
3. Can you open one of the files in a hex editor (HxD, etc.) and confirm there is actual data beyond the 0xFF padding? Scroll past the first ~64–128 KB and see if real data appears.

If the car is genuinely a 6-cylinder and was tuned with a V8 definition, that's your root cause — no amount of map adjustment will fix it, the entire tune base is wrong.

Car is a 2008 c63 amg v8. I think some has put the wrong ecu in. But the car drives.
I've checked another c63 and ecu says 8 cylinders .

Ton1 said:

Car is a 2008 c63 amg v8. I think some has put the wrong ecu in. But the car drives.
I've checked an...

Click to expand...

That confirms it. Here's the comparison:

Your ECU (currently in the C63):

• SW: A 156 150 40 79
• HW: A 003 446 12 40
• Bosch: 0 261 209 270
• Q04 ME9.7 — 6 Zyl.

Correct C63 AMG ECU (from the other car):

• SW: A 156 900 50 00
• HW: A 000 901 17 00
• Bosch: 0 261 209 586
• Q04 ME9.7 — 8 Zyl.

You have a 6-cylinder ECU running a V8 car. These are completely different hardware and software — different Bosch part number, different HW number, different SW number, different cylinder count configuration.

The fact that the car "drives" is surprising but the M272 (6-cyl) and M156 (V8) ME9.7 share the same base platform, so basic functions can partially work. However:

• The torque model is calculated for 6 cylinders, not 8 — every torque value the ECU sends over CAN to the ESP/ABS module is wrong
• The ESP module knows the car is a C63 and expects V8 torque signals — the mismatch triggers ABS/traction intervention
• Injection timing, firing order, ignition maps are all for the wrong engine
• The tune file was likely built on a C63 definition but flashed onto 6-cylinder hardware/software — this makes things even worse

This is not a tuning problem. No map adjustment will fix this.

What you need to do:

• Option 1: Source a correct C63 AMG ECU (Bosch 0 261 209 586 or equivalent 8 Zyl variant), get it coded/SCN-coded to the car via Star Diagnosis, then tune that one
• Option 2: If someone previously cloned the 6-cyl ECU with C63 software (which is possible but unusual), you'd need to verify what software is actually running inside by reading the flash — but given the label says 6 Zyl and the HW number is completely different, this is almost certainly just the wrong ECU

Tell your customer what you found. The ABS/traction light is a symptom of the wrong ECU being in the car — not a calibration issue that can be tuned out.

If I load a stock vr file from v8 will this help.

Ton1 said:

If I load a stock vr file from v8 will this help.

Click to expand...

No — you cannot flash V8 software onto 6-cylinder hardware.

The HW numbers are completely different:

• Your ECU: HW A 003 446 12 40 / Bosch 0 261 209 270
• Correct C63: HW A 000 901 17 00 / Bosch 0 261 209 586

The hardware determines what software can run on it. The internal flash memory layout, driver stages, injector driver count, knock sensor inputs, and pin configuration are different between the 6-cyl and 8-cyl variants. If you try to flash 8-cyl software onto 6-cyl hardware you will most likely:

• Brick the ECU
• Get a flash error / checksum failure
• End up with a non-starting car

Even via Autotuner virtual write, the tool should reject it because the HW/SW identifiers won't match. And if you force it somehow, the ECU won't boot properly because the hardware physically doesn't support 8-cylinder operation (different output stages, different knock channels, etc.).

The only real fix is to get the correct 8-cylinder ECU in the car.

A used A 156 900 50 00 (or equivalent C63 part number) ME9.7 8 Zyl unit, then:

• SCN code it to the car via Star Diagnosis (or get a Mercedes dealer to do it)
• Renew the EIS/ECU marriage (ME9.7 is immobilizer-linked)
• Then do your Stage 1 on the correct hardware

Tell the customer — this is a hardware problem, not something that can be solved with files.

I read the 6 cylinder ecu and wrote the stock vr file using Mpc563 c63 amg .
After car started but after 4 min the abs and traction lights come on.

Ton1 said:

I read the 6 cylinder ecu and wrote the stock vr file using Mpc563 c63 amg .
After car started but a...

Click to expand...

That's very interesting and changes things significantly.

So to be clear — you read this 6-cyl labelled ECU using Autotuner via MPC563 C63 AMG definition, and wrote back a stock VR file for the C63 AMG, and the car starts and runs for 4 minutes before ABS/traction lights come on.

This means one of two things:

1. Someone previously flashed C63 V8 software onto this 6-cyl hardware shell

This is actually possible on ME9.7 — the MPC563 processor is the same across both variants. Someone may have taken a 6-cyl ECU case/board and flashed it with C63 software + cloned the ISN/immobilizer data. The external label would still say 6 Zyl but internally it's running V8 software. This would explain why:

• The car starts and drives
• Autotuner reads it successfully under the C63 AMG definition
• The engine actually runs on 8 cylinders

If this is the case, the ECU is functionally a V8 unit regardless of what the label says. The ABS/traction issue is then not caused by the wrong ECU — it's a calibration or CAN torque signal issue.

2. The 4-minute delay is the clue

ABS/ESP lights coming on after exactly ~4 minutes is a classic symptom of torque monitoring mismatch or CAN timeout/plausibility error between the ECU and ESP module. This happens when:

• The indicated torque vs actual torque values don't match (torque monitoring fault)
• The ECU sends torque values the ESP module considers implausible
• A Stage 1 tune modified torque limiters but didn't adjust the corresponding torque monitoring maps

What I need from you now:

1. Scan the car with Star Diagnosis or a decent OBD tool — what exact DTCs are stored in the ESP/ABS module when the lights come on?
2. Does the car actually run properly on all 8 cylinders? No misfires, no rough idle?
3. You said you wrote the stock VR file back — do you mean the original untouched read, or a "stock" file from a database? This is critical.
4. Do you still have the tuned file that was on it before? I'd like to compare both.

The DTCs from the ESP module will tell us exactly what's triggering the lights. That's the next step before touching any maps.

Car runs properly no misfire no rough idling
Vr file original untouched.
I don't have a full bench read, only ori vr file. And vr file from ecu

Ton1 said:

Car runs properly no misfire no rough idling
Vr file original untouched.
I don't have a full bench ...

Click to expand...

Good — so the car runs perfectly on all 8 cylinders, no misfires, no rough idle. That confirms someone cloned V8 software onto that 6-cyl hardware shell. The label is irrelevant — internally it's running as a C63 ECU.

Now the key point:

You wrote back the original untouched VR file (the ORI) and the ABS/traction lights still come on after 4 minutes. That means this is not caused by the tune. The problem existed before the tune was ever done.

This points to an issue between the ECU and the ESP module on CAN — not a map/calibration problem.

Most likely causes:

• SCN coding mismatch — if the ECU was cloned/swapped, it may not be properly SCN coded to the car. The ESP module expects specific ECU coding data over CAN. After ~4 minutes of driving the ESP runs a plausibility check and flags a fault.
• Torque interface variant coding — the ESP module and ECU need to agree on the torque signal format. A cloned ECU might have a slightly different variant coding than what the ESP expects.
• ESP module has a stored permanent DTC that needs clearing with Star Diagnosis (not just a generic OBD tool).

What you need to do:

1. Get the DTCs from the ESP/ABS module — this is essential. Without knowing the exact fault code, we're guessing. A generic OBD scanner won't read Mercedes ESP codes properly — you need Star Diagnosis (Xentry/DAS) or at minimum a Autel/Launch that reads manufacturer-specific ESP codes.
2. Check SCN coding — with Star Diagnosis, check if the ECU is properly SCN coded to the VIN. If it was cloned, this step may have been skipped.

The ABS/traction light is not something you can fix in the VR file. This is a communication/coding issue between modules. Get those DTCs and post them here — that will tell us exactly what to do next.

Can I clone the v6 ecu to a used v8 ecu , will that help sort the torque issue.
Picture of v8 ecu attached.

Ton1 said:

Can I clone the v6 ecu to a used v8 ecu , will that help sort the torque issue.
Picture of v8 ecu at...

Click to expand...

Good idea, and the donor ECU you found is a proper C63 unit:

Donor V8 ECU:

• SW: A 156 900 12 00
• HW: A 000 901 17 00
• Bosch: 0 261 209 518
• Q02 ME9.7 — 8 Zyl.

This is correct C63 AMG hardware. Same HW number (A 000 901 17 00) as the other known-good C63 ECU you showed earlier. This will work.

Yes, you can clone to this ECU — but here's what you need to do:

Step 1 — Full bench read of both ECUs

You need a full flash read (not VR) of both ECUs via bench using Autotuner:

• Full read of your current 6-cyl labelled ECU (the one in the car with the cloned V8 software)
• Full read of the donor V8 ECU

The full read contains the ISN (immobilizer data), SCN coding, VIN, and the complete software — the VR file only contains the calibration zone and is not enough for cloning.

Step 2 — Clone the ISN / immobilizer data

You need to transfer the ISN from the current ECU to the donor V8 ECU so it matches the EIS (ignition switch module) in the car. Without this, the car won't start. On ME9.7 the ISN is stored in the external EEPROM and in the flash. You'll need to copy:

• ISN / key data from the old ECU → donor ECU
• VIN
• SCN coding data

This can be done with tools like Vediamo, Star Diagnosis (Xentry), or some dedicated cloning tools that handle ME9.7 ISN transfer.

Step 3 — Write the calibration

Once the donor V8 ECU is cloned with the correct ISN and starts the car, you can then write your tuned VR file to it via Autotuner OBD.

Why this should fix the ABS/traction issue:

The donor ECU has the correct 8 Zyl hardware, correct Bosch part number, and correct HW number that the ESP module expects to see on CAN. The torque signal format and variant coding will be native V8 — no mismatch.

Important note:

The donor ECU SW is A 156 900 12 00 while your current software appears to be based on A 156 150 40 79 (6-cyl number). Before writing the VR calibration from the old ECU, make sure the base software version on the donor is compatible. Ideally, flash the donor with the correct C63 stock software first via Autotuner full write, then apply the VR tune on top.

Get the full bench reads done first and post back.

Bench read both ecu and eeprom is different. Can't clone 1:1.
Need to send file to someone who can extract the necessary information and flash doner ecu.

Spoke to a few people and sent the file.
Not possible with doner part number.
To use xentry and program.
Anyone on this fourm who could help.

Coventry westmidlands

Ton1 said:

Coventry westmidlands

Click to expand...

Alright — so you're in Coventry, West Midlands, UK and need someone with:

• Xentry/DAS with online SCN coding (to program the donor V8 ECU to the car)
• Or ME9.7 ISN transfer experience between different SW versions

If any forum members in the UK can help with Xentry online coding for a W204 C63 AMG ME9.7 ECU swap, please reply here.

In the meantime, some suggestions:

Options to explore:

• Mercedes independent specialists — many indie Mercedes shops in the West Midlands area have Star Diagnosis with online access. They can SCN code the donor ECU to the car for a reasonable fee. Call around and ask specifically for "ECU replacement with online SCN coding."
• ECU cloning/repair specialists in the UK — companies like BBA Reman, Sinspeed, ECU Testing, or similar UK-based ECU repair firms often handle ME9.7 ISN work. They may be able to do the marriage without Xentry by working at bench level.
• Find a closer SW match donor — search eBay/breakers for a C63 ECU with part number A 156 900 50 00 or Bosch 0 261 209 586 (Q04, 8 Zyl). A matching SW generation makes bench cloning much easier.

If anyone on the forum is UK-based and can assist with Xentry online coding or ME9.7 ISN work, please reach out to OP.

Good luck — once the donor V8 ECU is properly married to the car, your ABS/traction issue should be gone and you can tune it properly.

Gemini said:

Alright — so you're in Coventry, West Midlands, UK and need someone with:

• Xentry/DAS with online SCN coding (to program the donor V8 ECU to the car)
• Or ME9.7 ISN transfer experience between different SW versions

If any forum members in the UK can help with Xentry online coding for a W204 C63 AMG ME9.7 ECU swap, please reply here.

In the meantime, some suggestions:

Options to explore:

• Mercedes independent specialists — many indie Mercedes shops in the West Midlands area have Star Diagnosis with online access. They can SCN code the donor ECU to the car for a reasonable fee. Call around and ask specifically for "ECU replacement with online SCN coding."
• ECU cloning/repair specialists in the UK — companies like BBA Reman, Sinspeed, ECU Testing, or similar UK-based ECU repair firms often handle ME9.7 ISN work. They may be able to do the marriage without Xentry by working at bench level.
• Find a closer SW match donor — search eBay/breakers for a C63 ECU with part number A 156 900 50 00 or Bosch 0 261 209 586 (Q04, 8 Zyl). A matching SW generation makes bench cloning much easier.

If anyone on the forum is UK-based and can assist with Xentry online coding or ME9.7 ISN work, please reach out to OP.

Good luck — once the donor V8 ECU is properly married to the car, your ABS/traction issue should be gone and you can tune it properly.

Click to expand...

ended up doing virginizing ecu and coding. all done abs fixed. thanks everyone for there help.

Gemini said:

Great news — glad it’s sorted.

For anyone else with a similar ME9.7 ECU swap, that confirms that proper ECU virginizing + correct SCN coding was the key step (your ABS/traction faults disappearing after coding is a good sign the ESP/ABS sees the correct calibration/ISN exchange again).

If you want, share:

• your current ECU SW/HW and donor SW/HW (Axxxx / Bosch numbers)
• what you used to virginize (Xentry/DAS, ZGW/OK, bench tool)

so others can replicate the fix.

Click to expand...

ecu HD and SW was the donner ecu list above and used xentry by samik offline.