Strange Issue After Stage 1 Mercedes E220 W213 2.0 Diesel

  •  
  • Thread starterbghiman
  • Start date
B
bghiman
New member
Special
Joined
20.11.2024
Messages
4
Reaction score
6
I did a Stage 1 tune on a Mercedes E220 W213 2.0 Diesel (194 hp, 2020) and everything worked fine for 300 km. After that the transmission started jerking and shifting poorly.
I restored the original software and the problem completely disappeared no matter how many kilometers I drove.
Thinking that the tuner was to blame, I tried again with a different Stage 1 software, but the result was the same. At first the car drives fine, but after about 300 km the transmission starts acting up.

The problem is this:

A "Blind Spot Inoperative" warning appears on the dashboard, and at that very moment the transmission makes its first sharp shift.
After another 5-10 minutes of driving this happens again, then more often.

Error codes found:

IRS-HRA (Right Rear Outer Driving Assist Radar) (1 DTC).
U040183 - "Implausible data were received from 'combustion engine'. Checksum for the message has an incorrect value."
IRS-HLA (Left Rear Outer Driving Assist Radar) (1 DTC).
U040183 - "Implausible data were received from 'combustion engine'. Checksum for the message has an incorrect value."

There are no fault codes in the engine and transmission control unit.
Now the car runs on original software and everything works fine.
I suspect there may be some kind of technical issue here - perhaps a faulty sensor or transmission component that works at its limits with standard software but fails under the increased load of Stage 1.
I haven't researched this issue in more detail yet, but I plan to do so in the future.
Has anyone else encountered this problem? Any ideas would be greatly appreciated!
 
  • Like [+1]
Reactions:Marcvs8 and merc4543
Here is your answer: "Checksum for the message has an incorrect value."
The tuner or your tool does not output the correct checksum!
 
  • Like [+1]
Reactions:merc4543
This is not a checksum. If the checksum is bad, the car will not start or drive.
I think this is due to limitations of the PTCU. The PTCU acts as a transmission control unit that controls the engine and transmission outputs, and also sort of connects the radars to the transmission system. It does not allow changes to be made to the ME map area.
 
  • Like [+1]
Reactions:EdoM
You are right that the problem is related to the PTCU. After the failure in stage 1, I thought that updating the transmission software might solve the problem. The update and coding were successfully performed using Autel Ultra. After the update, the only fault that appeared was in the PTCU.

Screenshot_20240708_111914_Drive
 
  • Like [+1]
Reactions:merc4543 and EdoM
Most likely the torque limiters in the ECU map are higher than the limiters in the PTCU map.
On these cars the PTCU also needs to be flashed, but as far as I know there are no such programmers at the moment.
The best solution would be to adopt other strategies for stage 1 in the ECU maps.
 
The car is currently running the original software it was delivered with. All the changes I made were reverted back to factory. The only error that appeared after about two weeks was P008A09 - Component fault: pressure in the fuel low-pressure circuit too low, but I don't think that was the original problem as the error was only logged once with the engine off, at a traffic light, when the Start/Stop function was active.

Anyway, going back to Stage 1, I spoke to another tuner who said he was familiar with the issue and could fix it, but I would need to bring the car to him in person to do it.

Maybe I'll take it to him in the future, but I can't now because he's too far away.

Another thing I noticed during my first attempts at stage 1 was that the chart showing the power in Nm and kW, although the needle goes up to 500 Nm, never went above 400 Nm, both before and after Stage 1, although the difference in power was noticeable.
 
  • Like [+1]
Reactions:merc4543
I also know this problem and drive the same engine. The problem is caused by CPC_NG because the torque limit in your file is higher than what CPC allows. You can counteract this by coding and lowering the limit in the tuning file, then the error and jerks will disappear.

Send me your file and I'll take a look at it. I can send you my file, but you'll have to change some data in a hex editor and fix the checksum for the machine to accept the file.

Code:
Coding this in MRD1:
Getriebe NAG3 V-Sport (AMG)
Momentenkorrektur dynamisch Mdyn nicht aktiv

Coding this in CPC_NG:
Getriebe NAG3 V-Sport (AMG)
Leistungsvarianten Leistungsvariante 0
Momentenkorrektur dynamisch Mdyn nicht aktiv
Momentenbegrenzung MFVB Index Momentenbegrenzung MFVB Index 0
Overboost Overboost erlaubt

Try it, but it is important that the maximum torque does not exceed 498 Nm, otherwise errors will continue to occur.
 

Similar threads

N
  • nano5849
  • Cars and vans
Replies
3
Views
864
nano5849
N
irstar
  • irstar
  • Vediamo
Replies
0
Views
4K
irstar
irstar
N
  • Locked
  • Solved
  • nemiro
  • Questions and answers
Replies
5
Views
2K
nemiro
N
Back
Top Bottom