Special Codings for A/CLA/B/GLB! (PDF)

[lordmetro]

I had this problem previously would never calibrate or would fail.

Solution for me was just import the codings and don’t touch Xentry Calibration procedure, just keep it in raw values after you import the calibration data and the car will automatically calibrate after a few trips. It won’t be instant either.

See my post.

Spoiler

[ Log in now to view this content ]

You will see that the percentage will start to increase even if you do not perform the actual routine. At first I thought, WTF but it works.
The car always adapts the angle values, so there is no need to perform calibration, especially if you have imported previous DTS values.

 

[b0snaaaa]

I made a few trips yesterday, but nothing changed. Maybe I need more trips? Otherwise, I'll skip calibration altogether.

How can I confirm that the calibration data has been imported and that the previous DTS values have been applied? I think I did this in step 4 of my guide, but I'm not quite sure. At this point the "Do Coding" button was grayed out when I tried to re-import the coding, so I temporarily changed the value in FCW177, which allowed me to immediately re-import the backup.

Also I want to clarify that I didn't use the "Set ECU to Delivery State" function for FCW177 as you did in your guide. Instead I used "Reset Automatic Initial Alignment Start" in FCW177. Is that enough?

 

[b0snaaaa]

I made a few more trips today, but nothing changed. The "Status of sensor calibration" remains "Tech-in process NOT STARTED" and the "Progress of adjustment" is still 0%. When I said I didn't "Set ECU to Delivery State", I also meant I didn't set "Manufacturer Default" in Xentry either. I followed all the steps exactly as described in my previous post and guide. The only steps I didn't mention is that I also tried "Synchronize to Non-volatile Memory Start" and "Synchronize to Non-volatile Memory Results" followed by "Hard Reset" for all ECUs after coding.

To be honest, I'm a bit stuck at this point. I'll probably try again tomorrow and do a few more trips. If nothing changes, I'm thinking of doing a "Set ECU to Delivery State" for FCW177 and then importing the AED coding file I saved for that ECU after that reset. To be honest, I don't know what to do next and I want to be careful not to make the situation worse.

When you said "Keep it in raw values after you import the calibration data" what exactly did you mean? Also, what do you mean by "calibration data" and where can I see it?

 

[lordmetro]

Suppose you do not use the "Set Delivery State" or "Manufacturer Default", the calibration data will be the same in DTS - you have not changed anything other than the SDTR mode. I am talking about the variant coding menu with the distances of the height of the sensor and some other things (e.g. length etc.). The whole point of resetting the module is so we can reimport these DTS measurements again, and put the module in a state where it has not learnt the init angle measurements of the new Distronic mode.

When you perform the reset (Manufacturer Default) - the module will loose all this information, which is the desired action we want, so the module is in a state where it can perform the new initial alignment under Distronic mode. We then import the previous DTS codings so that the menu with all the codings of the sensor are back, and the car can perform an initial alignment under the new Distronic mode.

The progress of adjustment will be 0% once you set perform the reset of the module and import the. AED distances again. Once you recode the parameters but with Distronic mode active, you will go to Alignment Values and it will gradually increase itself when you drive.


In your screenshot you can see error C100D56 - it is a CURRENT and STORED error, you need to try to clear fault memory, if it comes back, then yes perform the manufacturer reset. This is preventing the alignment.

I'd recommend you follow the guide as I posted;

1. EZS167 - Disable Cruise Control (440) and Forward Collision Warning (258) in EZS167, Enable Distronic Pro (239)
2. FCW177 - Function SDTR Write -> Distance Pilot DISTRONIC: Set this from inactive to active
3. Export FCW177 codings to AED file
4. FCW177 Reset - Diagnostics -> Sync. Routines -> Set ECU to Delivery State
5. DTS FCW177 -> Variant Coding -> Load AED file coding set -> Do Coding
6. Go to Xentry -> Driver Assistance System -> Colision Prevention -> Actual Values -> Alignment Values

After step 6, start to drive, you will see in Actual Values, the value of 0% will start to increase until it gets to 100%. Note how it is "Teach-in process NOT STARTED" - this is okay, we are not doing initial teach-in alignment, we are used the imported AED calibration and the car will use these measurements to perform the angle alignment whilst you drive.

The system is self-teaching, in my case, I have had cases of heavy rain where the car will have this inoperative and then it will be fine after a day or two of dry driving.


You do not need to perform the procedure for initial angle alignment, you can try, I wasted a week and it never worked for me - until I tried this way of performing alignment. It has been about a year and so and all is good on my vehicle.

 

[b0snaaaa]

Thanks for the detailed explanation - very helpful for me and others facing the same problem.

Just to confirm. To do step 3 before resetting the module (as you mentioned in the other guide: "SAVE CODINGS NOW as the radar parameters will be reset and can’t be recovered!" ), is it enough to just go to "DTS FCW177 -> Variant Coding -> Save AED file coding set" as shown in my screenshot below? Just want to make sure that no additional steps are required to fully back up all data.


Also, you mentioned going to "Collision Prevention", but I don't see that option at all. I think I should go to "A108/1 - Active Distance Assist DISTRONIC (DTR)" under "Driver Assistance System" to see the alignment values. So it would be like below, right?

"Go to Xentry -> Driver Assistance System -> A108/1 - Active Distance Assist DISTRONIC (DTR) -> Actual Values -> Alignment Values".

Finally, to get a rough idea of when I should expect to see any progress, how long after starting to ride does it typically take for the adjustment to reach 1%?

 

[lordmetro]

1. Yes, a full backup of the AED will do, there is a domain containing measurements that I don't remember, a year has passed.
2. It may be called something different on your device, and its name has probably changed since an older version of Xentry came out, but it is the same FCW177 module if it is in the Driver Assistance menu.
3. At first it took me about 5-10 minutes to get it aligned correctly, but you will see the numbers change very quickly.

 

[b0snaaaa]

SUCCESS!

The key point was to completely reset the FCW177 module using the "Set ECU to Delivery Start" function in DTS Monaco (not "Set ECU to Delivery State"). This resolved the "The requirements are not met" issue and allowed calibration to be performed in Xentry. Then the status changes to "Teach-in process NOT STARTED", but after calibration is started, the status changes to "Teach-in process RUNNING". Here I also want to warn others about the need to fully backup all data, saving the FCW177 encoding before resetting this module. This is done in step 3 of a guide by lordmetro by going to "DTS FCW177 -> Variant Coding -> Save AED file coding set" in DTS Monaco as shown in the screenshot from my previous post. That's it, no additional steps are required to back up all the necessary data for later use in step 5. Simply following the steps in a guide by lordmetro should get things working, but I just wanted to clarify things further.

I did the calibration anyway and it passed on the first try. This sped up the activation of Distronic Pro, which took only 10-15 minutes and one trip. This is probably why calibration is recommended. However, if calibration always fails, the no-calibration approach should also work, since the system automatically adapts the angle values in the background while driving. The disadvantage is that activating Distronic Pro this way takes longer.

In addition, it does not matter whether you open "Collision Prevention" or "A108/1 – Active Distance Assist DISTRONIC (DTR)" to view the actual values or perform calibration.

Everything works great now, and the best thing is that after activating Distronic Pro, I still have cruise control and collision warning active without sacrificing any features!

 

[Hzr]

Congratulations! I wanted to know if you also have an emergency braking feature in addition to the collision warning.

 

[lordmetro]

Yes, it persists after change.

 

[b0snaaaa]

When retrofitting features or enabling special codings, is it possible to achieve their official recognition and authorization by Mercedes-Benz? Or am I being too optimistic? I also consider the potential impact this could have on the vehicle's warranty.