My ABR/ABS/ESP module finally went, I couldn't calibrate the ABR, bled the brake system which was long overdue and was able to calibrate the ABR but the ESP errors just wouldn't go away. I decided to get a reman unit from the folks over at Repair Laboratory. I got the unit in 2 days, saved the coding on the old one using Vediamo and swapped in the new one. This is a relatively easy job because the unit is in the front of the car with plenty of access to get to the 4 low torque bolts and take the unit out. My old ESP control unit, hardware ID 2215455232, had software 2214421153 however the reman unit of the same hardware number had software 2214420653. Turns out 2214421153 is specific to 4Matic which is what I have and the 2214420653 is for a rear wheel drive. I was still getting ESP errors and my Parking Assist wasn't working either with this reman module. For some reason my Vediamo 4 setup, wouldn't allow me to flash 2214421153 to this control unit, a quick and easy fix. When I used DAS to check for new software in the hopes of being able to flash with it, it told me that 2219029602 was available but that it wasn't a compatible update for 2214420653. I'm using a 2020 version of Xentry PassThru with a SnapOn PassThruPro II and I think earlier versions of DAS would just tell you nothing is available. Kudos to the engineers at Daimler, they gave me a great clue! Digging around in my Xentry/DAS setup I discovered that the file 221.etns has one of the flash lists that Xentry/DAS uses to determine if there's a software update available for your control unit and the ESP software is in this particular file. Reviewing this file I discovered that there was one update for my old control module 2214421153 and that update was 2219029602. Here's the entry in 221.etns for that.

300408;0160;FV;L;2214421153;ESP;M005;050;20060331-20070317;2219029602;2219029602_001.CFF;1;

M005 is for 4Matic.

221.etns (etne, etnh, etnt, etny, etnz) are located at \Program Files (x86)\Mercedes-Benz\SDFlash\Release\PKW

For the 2214420653 there are 6 entries, none with M005 as above, for different dates of manufacture and engines like the M275, M156 and the latest update for that software is 2219029502 for the rear wheel drive cars. To see if I could trick DAS into flashing my control unit with 2219029602, I copied the above entry but changed 2214421153 to 2214420063 and placed it at the end of the software list for 2214420653. When I tried the offline update I got a prompt of new software available for my control module and was able to use DAS to flash 2219029602. All of the ESP errors went away and things are now back to normal. For those that don't tinker i.e. don't have Xentry/Vediamo and are contemplating replacing their ESP module with a used or reman unit, you must know what car the unit came from and/or make sure it has the same features your car has or you will have problems. For the tinkerers, this piece of information hopefully can be useful.

 

For an easier way, Vediamo should have been able to flash and code as long as you know the flash file number with coding string. Also, with Vediamo or Monaco sometimes you have unlock the module with seed key or just click unlock depending on the CBF file you are using.

 

that sounds remarkable as you can't even flash the amp / radio tuner with the better facelift software (that works perfectly well - but with a nicer colour scheme) because security features you can't remove in xentry, vediamo or DTS stop you

 

My post is directed toward those that either don't have Vediamo or have it and don't know how to use it.

 

Hi all! I have exactly the same problem as the starter topic. My car is W221 2007 4wd, and it has the used ABR A2215455232 HW 2215455232 SW 2214422453 installed on it. So I have an ESP error when I start driving due to a software mismatch (firmware from 2wd). When updating, Das offers firmware 2219020300_001, if I agree, the firmware update interrupts on 0% after 7 seconds, communication software error 11.913.20052. Next, I try to flash the same firmware via Vediamo, but I have the same problem: connection is broken and error 20052 after 7 seconds. Next, I try to write the firmware 2215451153 and again it fails, error 20052. To check for sure, I flash the firmware that is already in the block and the connection is also broken. To test my equipment, I flashed the driver's door control unit and air suspension through DAS and through Vediamo and everything went well the first time. From this I conclude that my computer and adapter are working properly, and the problem is in the ESP unit. My tools are xentry 2021/6 (das offline) vediamo 4.02.02 and openport adapter. I tried to do as the theme creator suggested, but I don’t have file 221.etns in the folder sdflash/realise/PKW. There is a file 221_216.etns (and etnh) in the next folder Telematics, but there is not a single line about ESP in it. Please help me solve the problem, maybe its need to somehow unlock the ESP unit for updating firmware via Vediamo. I'm making a personal car, I've already spent a week on the forums and trying to flash it, but unfortunately without success. Where I live there are no masters to turn to, so I have to figure it out on my own. Thank you!

 

not all things are created equal -

certain modules will update simply off line with old kit and software contained within pre 2012 tools
others fight even with latest fully paid up dealer tools online and software pulled of the Merc local encrypted NAS drive
others refuse to install via vediamo even with experts at the helm with unworkaroundable security limitations
with something that has its toes in to so many systems and safety related not surprised they fight....

my 2 wheel drive 2006 V8
ABR HW 221545 5232 - SW was 221442 0653 of week 29 of 2005, mine is updated to SW 221902 9502 week 17 of 2011 - suspect its steer assist update - not that its enabled - never tried - only thought why they issued after recent post and read its steer by brake)


not seeing that part used on any 4x4

020 CONTROL UNIT ESP ELECTRONIC STABILITY PROGRAM (ESP) Replaced by: A 221 545 11 16 001 A 22 154 569 32 - -
020 CONTROL UNIT ESP ELECTRONIC STABILITY PROGRAM (ESP) Replaced by: A 221 545 90 32 001 A 22 154 511 16 - -
020 CONTROL UNIT ESP ELECTRONIC STABILITY PROGRAM (ESP) Replaced by: A 221 545 93 32 001 A 22 154 590 32 - -
020 CONTROL UNIT ELECTRONIC STABILITY PROGRAM 001 A 22 154 593 32 - $969.26

020 CONTROL UNIT ELECTRONIC STABILITY PROGRAM Replaced by: A 221 900 17 01 001 A 22 190 106 00 - -
020 RS CONTROL UNIT ELECTRONIC STABILITY PROGRAM Replaced by: A 221 900 32 01 001 A 22 190 017 01 - $1 118.86
020 RS CONTROL UNIT ELECTRONIC STABILITY PROGRAM Replaced by: A 221 900 79 03 001 A 22 190 032 01 - $1 174.80
020 RS CONTROL UNIT ELECTRONIC STABILITY PROGRAM Replaced by: A 221 900 20 04 001 A 22 190 079 03 - $1.19 020
RS CONTROL UNIT ELECTRONIC STABILITY PROGRAM ESP 001 A 22 190 020 04 - $1.19
020 CONTROL UNIT ELECTRONIC STABILITY PROGRAM Replaced by: A 221 900 18 01 001 A 22 190 107 00 - -
020 RS CONTROL UNIT Replaced by: A 221 900 42 02 001 A 22 190 018 01 - $1.19
020 RS CONTROL UNIT Replaced by: A 221 900 33 01 001 A 22 190 042 02 - $1.19
020 RS CONTROL UNIT Replaced by: A 221 900 11 03 001 A 22 190 033 01 - -
020 RS CONTROL UNIT Replaced by: A 221 900 80 03 001 A 22 190 011 03 - -
020 RS CONTROL UNIT Replaced by: A 221 900 21 04 001 A 22 190 080 03 - $1.19
020 RS CONTROL UNIT ESP 001 A 22 190 021 04 - $1.19


had lots of trouble flashing SGR radars took 5 attempts online before Merc manged to flash it - oddly the progress bar seemed to get a little further before crashing each time

 

With the Tactrix you won't be able to flash all modules. For successful flashing you need a more robust J2534 device like a CarDAQ-Plus, SnapOn PassThru Pro(What I'm using), Bosch Flasher Pro. All three of these are the same unit, meaning they are all made by CarDAQ and rebranded. You will be able to flash things like door modules with the Tactrix but for other stuff you need a more robust J2534 or a Mercedes clone multiplexer.

As for the 221.etns...

Your Xentry/DAS configuration is missing files which may be in an archive as part of the installation located at \Program Files (x86)\Mercedes-Benz\SDFlash\Release\PKW named #CFF?.zip, where ? is 1,2,3,4,5,etc. Those are all of the CFF files. I don't remember if the etn? files are contained in these archives. I you send me a private message I can provide you with the ones you need for the 221.

 

I have no permission to write you private message, can you do it first please? And about adapter, openport definitely not suitable for esp flahing, or perhaps one of the reasons but it can be something else?

 

this looks interesting

Product Model Super ICOM Pro N3+
BMW full system diagnostics √
BMW programming √
BMW coding √
BMW hidden functions activation √
BMW motorcycle √
J2534 passthru BENZ/VAG/TOYOTA/HONDA/JLR/GM GDS2 √
BENZ DOIP √
VAG DOIP √
Mobile version software MHD, Bimmercode, Bimmergeeks
WIFI direct connection
USB Cable √
LAN Cable X

 

The OpenPort has limitations which is why it failed to flash your ESP. It's good for diagnosis and for coding changes using Vediamo, not good for flashing.

I sent you a link where you can download the files.

 

Mine started acting up again this morning after a couple years..one of my IR bulbs went bad a couple days ago which knocked out the night vision but that’s an easy fix, and can also set off the abs/esp light..could that be the issue here?

 

across the entire motor vehicle world teves and continental ABS modules die all day long - they build them that way - keeps the german (and sick global) economy going so "nice" people can say hello in places like gaza

 

What?

On a separate note...do we know specifically why these fail?

 

in the early days GM would have them shipped with a special compound on one of the link wires so it corroded and lost connection (re wire using a paper clip)
merecdes had then soldered so the link wires would just fall off from vibration - see also Turbo VGT actuators (re-solder)

after those bits of fun became common knowledge they invented a more "random" method of failure - particularly welcomed by BMW who seem to have a race going on with VW over who can produce the biggest numbers of ABS failures.. here they get their units specified with the brush Guides on the ESP pump pressure motor set deliberately tighter than Ford (and I guess Merc do) as its rare on both

check 40 mins 50 seconds for the fun

 

Hey EasyPhil!

Looks like I might have the same problem I just wonder if you had any fault codes besides esp light on the dash?

My car has esp light on the dash and is throwing this code.
This fault code was not on before ESP module replacement.

 

How do you figure this is the same problem?

 

I'm still not a 100% positive I have the same problem, it just looks like it might be it. And that's why I'm asking if you had any fault codes along with ESP light on the dash, because if you had same fault code, that will be another clue leading me to think that I have same issue as you had. Did you have any other bad symptoms along with ESP light? I feel like my car is randomly cutting off power steering for like 1 sec while turning.

My ESP module broke down, I replaced for a brand new genuine unit, however I was not able to do programming/coding stage on my xentry, so I did all that in my friend mechanic's autel. All codes related to ESP module were gone, no more stiff power steering above 20mph, so let's say we did some progress. Now I have this code and esp light on the dash. I did replaced that sensor that is related to this fault code, nothing change. In Xentry it says it might be a bad connector, I ordered a new one that is coming this week, but honestly I don't think it will fix the issue.

I tried to go in Vediamo and look for the files you mentioned, but I think I have some cheap Chinese version and can't do anything in my Vediamo. Now I'm waiting for BenzNinja software, hopefully I'll be able to do things like that in their software.

 

You would need to know the software version of the module you purchased and then determine if that software version is appropriate for your car. If you read the 1st post, that's what's being discussed. Notice in all that you've posted you haven't once indicated what software your module is running.

 

My hardware number is 2215453516
My software number is 2219021703

How to determine if that software if appropriate for my car? Do I need to install old esp module and read the numbers? If I install old module, do I need to program it again to read the numbers?

I dig again into this fault code after I read the numbers and it looks like BAS travel differential sensor doesn't have connection with ESP module. Does inappropriate software might causing this lost connection? I already replace that sensor for a brand new genuine part, checked the wires, everything looks good.

 

WRITE WHATSAPP NUMBER

 

Good luck from two years ago! Second post on the board from you EVER. Hmmmm...

 

+18003825633👍

If that doesn't work, try +18004383828
😂

 

from the video in post #14

 

Thank you all for your sharing info. for ESP flashing, with multi purpose diagnostic tool such as Think Tool Master, you can manually enter the SW version you want to load, tool will search for the SW and apply to module if available.


Iff SW programing set to Auto, system is not able to find the new SW or the right and lastest SW compatible for your vehicle, tool just simple flash the existing SW of the ESP

If you select SW programming manual then you able to enter the SW version you wqnt apply to your ESP

The ESP from W221 diesel donnor then therefore Cruise Control does not work when it installed in my car. I hope 2219029502 is the right SW for my W221 RWD equipped with M273 engine + Distronic Plus. New SW flashing is successfully completed and ai have no time to test cruise control yet but I think it should works.

 

your vin says LHD ?

its a much later SW version from wk 17 2011, that my 2006 RHD V8 5.5ltr with Distronic plus is running (in the same module HW you have - my original SW was 2214420653 from wk 29 2005)