[dexters84]

Hi guys

I had my I-Level updated.
I've moved from F010-11-09-507 to 59.4.004
Operation was almost succesfull, by almost I mean Passive Safety System error on KOMBI and CIC screens




I have a 2012 528i xDrive from USA.

The man that was doing my upgrade says that this error is a result of crash data in ACSM.
These errors were not visible previous to upgrade.

I've looked through forums and I've tried doing several things that were mentioned as a solution to such a situation, namely:

1. I've tried locking ACSM from ESYS using "ACSM verriegelung_schreiben" and "ACSM verriegelung_schreiben_new"
2. I've tried clearing errors from ESYS using "Clear all DTCs"
3. I've tried doing a full program and coding on ACSM using ISTA/P with ICOM (original)
4. I've tried coding all CAFD files to ACSM in ESYS (new CAFD files have different names that ACSM cafd files in old I-Step), right click on all 3 cafd files in ECU tree and selected code.
5. I've tried using instructions for tool32 to lock ACSM, screenshots from this attempt are included below






None of the above managed to clear my error.
if anyone has any suggestion on possible solution I'd appreciate it greatly.

Going to a dealer is not an option for me, when dealer saw that my car was from USA (I'm in Europe) they refused to do any coding or programming on it unless I accept all the risks of failure.

If you guys agree that this can be related to crash data in ACSM then I will look for ways to clear it, however tool32 ACSM lock attempt screentshoot shows out-of-range error, that suggests wrong memory address for locking ACSM rather than failure

[chang2]

Hello,

The vehicle has been adjusted by a fdl-coding. You have to do the same.

thanks

[dexters84]

Hello,

The vehicle has been adjusted by a fdl-coding. You have to do the same.

thanks

Thanks for your input.
Right now my cafd files are stock.
Do you have any idea what values or features should be coded into acsm to disable these errors?

Wysłane z mojego LG-D855 przy użyciu Tapatalka

[temsky740]

Read your fabric FA with Esys and then code ACSM with it. If it will not help I can clear crash data. I think it's not like crash data. More like a wrong encoding .But everything is possible. Poland

[BMW888]

Seems you have modified FA from US to ECE. In screenshot. It show Poland language. US spec. does not support it. Try roll back to original FA and do programming-coding by ESYS.

[dexters84]

Polish language in cic is afaik not done via coding but by replacing language files, but I can be mistaken on this. The language was present in the car from the day I bought it.
Regardless all ecus (including acsm) were reset to VO state, I currently lost all my custom settings (even the radio went back to US frequencies) and I still have this error.
I'm sending my car to workshop as I expect incorrect repairs by the previous owner and some software coverup that was revealed by full software update with ICOM.

Turned out my battery clamp is a wire covered with tape. I don't expect this to be a factory setting. I will fix hardware first and the go back to software.

[temsky740]

Try using the programmer to write another dump

[dexters84]

Try using the programmer to write another dump

That will just cover up the errors from acsm, not resolve them.
I want it fixed not just off the dashboard

[temsky740]

Try using the programmer to write another dump

That will just cover up the errors from acsm, not resolve them.
I want it fixed not just off the dashboard

You are mistaken about this.

[dexters84]

So I should get a working eeprom dump and put it in acsm?
I don't know how to choose appriopriate, I mean I can check eeprom model but what about choosing right dump for that model?