When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
2015 SL400 (M276 Turbo), 2014 C350 Sport (M276 NA), 2004 SL500 (M113), 2004 Audi TT225 (BEA)
Pre-Safe Functions Limited
I got the warning on the dash after doing an electronic throttle calibration using my iCarsoft MB V3.0. BUT....there are no stored codes using the iCarsoft scanner, my LAUNCH Creader Elite BENZ reader, and even Xentry. I haven't driven the car, but am thinking I may need to drive it a bit to allow the other systems (e.g., ABS) to adapt to the reset throttle control.
Anyone else experience this or have any thoughts?
Thanks
Last edited by JettaRed; Jan 25, 2025 at 05:23 PM.
2015 SL400 (M276 Turbo), 2014 C350 Sport (M276 NA), 2004 SL500 (M113), 2004 Audi TT225 (BEA)
Originally Posted by BenzNinja
1 lock the car, keys away, 15 min
try again
2 remove the + from main battery 10 min
try again
tips: stop using icarsoft and autel junk for anything else than reading
Tried both things and the warning persists. When scrolling though owner configurations in the dash, I see Pre-Safe Brake and Blind-side Assist both as inoperable. This has me thinking there is something wrong with the radar controller or sensor.
Scan with XENTRY as @BenzNinja recommended. Have yet to get a car with this warning that didn’t trigger a code (or failed component test) that couldn’t be read or tested with XENTRY.
Good Luck and Happy Thanksgiving 🦃
Last edited by crconsulting; Nov 23, 2023 at 01:31 PM.
2015 SL400 (M276 Turbo), 2014 C350 Sport (M276 NA), 2004 SL500 (M113), 2004 Audi TT225 (BEA)
Still no DTCs, but further examining the DISTRONIC PLUS controller, I found this. Does this mean the sensors need to be calibrated? Is this what is causing the problem?
means that the Icarsoft send data or a command to other that what you were working on
same happens with the expensive Autel with online used in workshops when they try to code a headlight
sometimes the whole front dies
new transmission plates too
2015 SL400 (M276 Turbo), 2014 C350 Sport (M276 NA), 2004 SL500 (M113), 2004 Audi TT225 (BEA)
I conducted the calibration of the DISTRONIC radar sensors using Xentry (as described in the YouTube video). However, with my version of Xentry (09/2023) the menu choices have been revised. The calibration procedure for the A89 controller is now under "Initial Startup" without control unit replacement and with adjustment drive. I started the calibration and proceeded with the adjustment drive. After about 10 minutes of driving, all functions were restored.
Last edited by JettaRed; Feb 28, 2024 at 09:12 AM.
Scan with XENTRY as @BenzNinja recommended. Have yet to get a car with this warning that didn’t trigger a code (or failed component test) that couldn’t be read or tested with XENTRY.
Good Luck and Happy Thanksgiving 🦃
I believe there were no DTCs is because there wasn't an actual fault or malfunction. The sensor needed calibration, which is not the same as being defective. I'm a true believer now that XENTRY is the only way to go for real problem solving on a Mercedes. AND it costs less than a mid-level Autel tool.
I believe there were no DTCs is because there wasn't an actual fault or malfunction.
The sensor needed calibration, which is not the same as being defective.
I'm a true believer now that XENTRY is the only way to go for real problem solving on a Mercedes. AND it costs less than a mid-level Autel tool.
Let's see how long the calibration update for your long-range radar last until beep-beep says hello on a straight open road. Fortunately I have never had a brake-slam out of the blue.
>> It's a transient condition caused by instability that I qualify as glitches. It's not entirely simple how MB networked issues are gracefully rolled up to trigger remote chaos without clues.
This is where a DTC would help technicians - Instead they are left to read tea leaves - We can do that well!
The issues created with these robust OEM modules are not passed down to Japanese customers... so no particular development budget is spent on chasing these managed engineering bugs.
It's for us to enjoy snapping golden Easter-Eggs.
Happy Thanksgiving Holiday
Last edited by CaliBenzDriver; Nov 24, 2023 at 04:30 PM.
2015 SL400 (M276 Turbo), 2014 C350 Sport (M276 NA), 2004 SL500 (M113), 2004 Audi TT225 (BEA)
Originally Posted by CaliBenzDriver
Let's see how long the calibration update for your long-range radar last until beep-beep says hello on a straight open road. Fortunately I have never had a brake-slam out of the blue.
>> It's a transient condition caused by instability that I qualify as glitches. It's not entirely simple how MB networked issues are gracefully rolled up to trigger remote chaos without clues.
This is where a DTC would help technicians - Instead they are left to read tea leaves - We can do that well!
The issues created with these robust OEM modules are not passed down to Japanese customers... so no particular development budget is spent on chasing these managed engineering bugs.
It's for us to enjoy snapping golden Easter-Eggs.
Happy Thanksgiving Holiday
Sounds like you've been into the eggnog a bit much.
2015 SL400 (M276 Turbo), 2014 C350 Sport (M276 NA), 2004 SL500 (M113), 2004 Audi TT225 (BEA)
Using the LAUNCH Creader Elite BENZ scan tool to calibrate Distronic.
Navigate to system DTR-DISTRONIC(A89) and select Special Function.
Read the Operating instructions. When you select Continue, it will automatically put your radar sensors into calibration mode.
You then must take a drive, trying to stay in a straight path at a fairly constant speed. The drive lasts about 15-20 minutes or 10 miles before PRE-SAFE functions are restored. During calibration, everything is inoperable and you will have yellow triangles displayed in your external rear view mirrors. When calibration is completed, the yellow triangles turn off and you will get a message that PRE-SAFE functions are restored.
Sorry, but I didn't read all the Operating instructions, and inadvertently initiated calibration on my car. I missed capturing a screen shot that gives more information. But if you get this far, the rest is self-explanatory. I don't have time right now to do it again.
You can also check the status of your calibration by selecting Read Data Stream from the menu selection. This will be helpful in determining the progress and status of your calibration drive.
Lastly, though I didn't do it this way, you may also be able to initiate calibration by selecting Initial startup with test drive and repeating the above instructions. The Initial Startup menu item is right below Special Function menu item.
Mercedes SLR McLaren 722 S Is Extremely Rare Example Modified by McLaren
Slideshow: A one-of-one U.S.-spec Mercedes-Benz SLR McLaren Roadster became even rarer after a factory-backed transformation at McLaren's headquarters.
