Bimmerfest BMW banner

1 - 4 of 4 Posts

·
Registered
Joined
·
9 Posts
Discussion Starter #1
Hey Everyone,

Not sure if anyone is able to shed some light but I recently performed an EDC delete for a friend as he upgraded to Coilovers and after completing the VO coding of the various modules I was then presented with a driver restraint error and have been unable to clear it using Esys, Esys Transmitter and even Tool32.

Below are the errors I'm seeing in the ACSM module. (This was provided from Tool32)

Fussgängerschutzsensor vorne Mitte: Kodierdaten stimmen nicht mit Ausstattung ueberei
Pedestrian protection sensor, front center: Coding data do not match with equipment

Airbagsensor-Cluster (high g x-y-Richtung): Kommunikationsstoerung
Airbag sensor cluster (high g x-y direction): communication fault

Fussgängerschutzsensor: Kodierdaten stimmen nicht mit Ausstattung ueberein
Pedestrian protection sensor: Coding data do not match equipment

I've tried VO coding ACSM but still nothing the error does not clear even after re-locking the module with Transmitter or Tool32

Any pointers or help would be hugely appreciated it
 

·
Registered
Joined
·
556 Posts
You have likely removed something from the FA that would require a different part number. As an example there are two different ACSMs for the F30. One with active cruise control and one without. You may find that whatever you have removed from the FA/VO would usually mean a different ACSM is fitted. For example I helped with an F22 ACC retrofit coding. The original guy had removed 8TF from the VO in an attempt to clear the restraint fault. Actually what needed to happen was the ACSM to be coded with the correct FA for the equipment that was fitted. Happy to take a look if you need me to.


Sent from my iPhone using Tapatalk
 

·
Registered
Joined
·
9 Posts
Discussion Starter #3
You have likely removed something from the FA that would require a different part number. As an example there are two different ACSMs for the F30. One with active cruise control and one without. You may find that whatever you have removed from the FA/VO would usually mean a different ACSM is fitted. For example I helped with an F22 ACC retrofit coding. The original guy had removed 8TF from the VO in an attempt to clear the restraint fault. Actually what needed to happen was the ACSM to be coded with the correct FA for the equipment that was fitted. Happy to take a look if you need me to.
Would definitely appreciate some assistance with this as I removed 2VF during the EDC delete do you think this could be causing the issue? I VO coded ACSM and also even tried applying a new CAFD file with the same i-Step to see if it could resolve the issue. Let me know when your available or drop me a PM please would massively appreciate it
 

·
Registered
Joined
·
556 Posts
Replied to your PM, but this is almost certainly caused by the 2VF removal from the ACSM. The part number is different for the ACSM without 2VF.


Sent from my iPhone using Tapatalk
 
1 - 4 of 4 Posts
Top