Thanks for your reply Mr mark.
Does the error code means I need to replace the switch panel as you circle?
Thanks

 

that's a bit strange..... do the brake light work ?

 

Ting:

As BOTUS said, "strange."

But, to answer your question on whether you should replace S6/2, we don't know. That bank of buttons turns off Parktronic and EPS, so it could be... That is why I left "???" at the end.

Do the buttons work? Could be one is stuck down or, could be a short in the circuit board in the back. Or, could have nothing to do with the problem.

Did you clear the faults as BOTUS suggested? Even MB says not to replace parts just because of a fault.

Good luck and let us know what fixes it.... Mark

 

Yes it works. Even the brake hold is working. Any other idea for it. Thanks for the advice Mr botus.

 

All the button is working normally while I use scanner to individual test it. Now the parktronic switch is always off. Esp, airmatic, and the lcd swivel switch working normally. I understood not replace component becuase of a fault. Just currently the fault code is unable to erase so it seems like there is a faulty problem in component and I still couldn't found it yet. Any other idea could it be? Thanks Mr mark

 

there are multiple versions of the switch by the speedo.... part 50

https://nemigaparts.com/cat_spares/e...71/63v/82/062/

intrigued it lists a brake light switch by the brake pedal but you can't find it.... how do you think the brake lights come on ?

 

Ting:

So, you are clearing the S6/2 code and it is immediately "current and stored"? That is, it comes back as fault code 9049? Just guessing but, one would think, it's the switch or the wiring. I looked at the link BOTUS provided and, as expected, the switch panel is not cheap, but cheaper than a ride to the dealer.

I'm no MB tech, but since I started the thread, I checked S6/2 and code 9049, and found nothing. Most of the posts on this thread point to the wheel sensors, but you are not getting faults for the sensors. Correct? So, I'm out of ideas. Also, see posts #3 and #5 about reprogramming, although, that doesn't seem to be your problem.

Regards... Mark

 

flea bay is littered with the switches... but you need to know which it was supposed to have

 

Thanks for your reply Mr botus. I am still out of idea how does the brake light works. As there isn't any sign of brake switch near the pedal area. I saw some said in some model of mercedes happen the brake switch is at the brake booster pump but it wasn't there also for my case. I am really out of idea. Please advice if have any other possibility of place where it would be.
Thanks

 

Thanks Mr mark for your reply.
The fault code for the s6/2 and the 9049 i can't be erased. Which I assume there is something wrong on some component. I am really out of idea what should I do next. The rear parking sensor is working only but the front is not working thus showing the parking sensor stay off. Anyways that you could suggest me to try to proceed. Currently I am out of idea. Thanks Mr mark

 

which sensors does it have

early ones with distronic plus - although not sure what non adaptive cruises ones had - had hidden parking radars front and rear. 2 years in to European build, in 2007 all moved to the visible sensors every one uses these days

did someone use the wrong bumper after a small prang and u now have a mix of incompatible parts ?

 

Thanks for your reply Mr botus.
Which sensor you referring sir?
Currently what I know is it is equipped using a pts module type of parking sensor. Where I recently found out for facelift model is using pdc module which is different from mine. Does this makes any Idea for you?
Thanks for your help. Really appreciate it.

 

visible ones = 4 little 15mm circles 350mm apart in a horizontal line across the bumper
radar = look like a cheap car without any sensors (they sit behind a std bumper and look through the plastic with radio waves)

 

On what BOTUS said... the sonar sensors-- circles in the bumper-- are cheap enough to replace just to see if that fixes the problem. The radar ones-- no holes in bumper-- are Expensive!!!

In that regard, DAS allows you to check the sensitivity of the sensors. It shows the cm from an obstruction. Also, if it is the park sensors, one would think it would throw a code for one of those sensors. Correct? Also, as far as I know, those will not affect the cruise control.

Ting, if your only fault is S6/2, and as you said, you are out of other ideas, then a switch panel from Ebay would be my next attempt at a fix. As we've said, however, that seems like a "strange" part to fail. Obviously, you need the right part #. There seem to be many different part #'s for those switches.

Also, I don't know what diagnostic system you are using. I would want a DAS scan before replacing parts. Here's an example: My ParkAssist was inoperative when placed in reverse and, like yours triggered the "off" light in the switch panel. I looked into replacing sensors. It turned out to be the little module in the rear headliner that shows the warning lights you see in the rearview mirror. I would have never found that part was defective without DAS!!!

Best of luck and let us know what fixes it... Mark

 

I'm wondering if all the parking sensors including distronic the middle 2 are all the same. One of them is bad and I want to know if I should buy a parking sensor or is there a distronic sensor?

 

LINDI, I got a message about your post because I'm the original poster. Can you refine your question?

If you're asking if all parking sensors are the same... I don't know. Are the part #'s the same? If your asking about the difference between ParkAssist and Distronic sensors, yes, they are different. Distronic is one in the middle of front grill, and ParkAssist has 5 radar sensors in the bumpers, IIRC... The two systems operate independently of each other. AFAIK, they only have the wheel sensors in common....

Regards.... Mark

 

Mark, great you come back now and then :-)

couple of points

1) on sensors and how it works - might be wrong - but think I'm about right

hidden parking sensors ( I suspect ONLY came with posh cruise), and vanished for parking duties by mini facelift in late 2007
normal visible ultra sonic parking sensors 4 across the front from 2007 (and of course at the back)

early distronic plus (active cruise control vehicles) gets 3 radars at the front and two further ones at the back - the main one in the center of the grille does much of the driving, but is supplemented at lower speeds with a wider field of view by the other two front radars - its this that helps get the plus features - of working all the way down to stop start traffic.

they soon took the four corner radar duties away from parking sensor activity and replaced with ultra sonic sensors you can see front and rear. At this point I don't know if the two rear radars stayed to do blind spot assist or ? I forgot you guys get the sensible rule of overtaking on both side - and hence why blind spot was wanted in USA all the way back to 2006. But in Europe undertaking has always been illegal, so blind spot took much later to come in and only for very high spec cars for the hell of it - and then to make it a bit safer with motorbikes filtering in the deliberate congestion they created.

Mine has rear radar but never has blind spot assist - I think that came as an option in the 2010 facelift. Only confusion for me is what drives it - in the rear wing internal side extract vents, USA cars get an antenna feature within the vent - and I wondered if this somehow did blind spot.?

2) the R SAM update can you say which update you used ? I now have the unit you buy as current fitment in the parts dept - BUT maybe its a special software iteration designed to cope with little workshop time - its software number ends 2600
When I plug in xentry it has no faults and everything works (allegedly) but it has far less ability to play than you'd expect and it says Out of date when you plug it in. Its also not possible to SCN this device (found that out years back when first fitted it)

So either its only possible to SCN a device that's at the current latest release? (which for me is silly) but I guess possible? or as its a replacement part with simple coding set up, Merc doesn't support SCN for this software release?
I don't want that last wrong 4903 facelift software update in my car.(it does mess up active cruise). But ages back you posted a list of software they released for the rear SAM

https://mbworld.org/forums/s-class-w...ate-diy-5.html

CFF versions in the 221 SAM-H timeline:

4422400 31.10.2007
4422600 20.12.2007
4423300 6.6.2008
9021400 16.01.2009
9021401 6.1.2009
9023903 1.6.2012
9024003 4.6.21012
9024903 03.04.2013

Checking that out the other day I see a version ending 3300 - this came out mid 2008, 6 months after the version I have that comes with the part . - I'm still chasing that bug in the hifi but its worn me out - nearly everything is back on old original software (COU, OCP, UCP, KI Cluster, Tuner etc. but the feature is still missing - Whilst the R SAM is on older software where the feature should work (allegedly) maybe this 2600 release is special or just can't be SCN'd to wake it all up to perfection. For me its a simple as all modules that connect up and communicate ambient noise levels, vehicle speed, entertainment vol level and if the tuner of the Nav want to overlay a message - then mute background. Then I figured if I can SCN the R SAM will it all pop back to life? I suspect so (as nothing much else out there to try)

My last thought is the Facelift SAM software took on the wrong Mute yes no set up - (when I had the facelift tuner software on my car). As on cars meant to be running both these software releases the fade feature can be user switched via a Comand Menu option. But of course early cars it was turned on somewhere and just worked - but somehow on my car its turned off. And flashing, re coding, resetting and hunting down stuff we haven't ever found it anywhere.

I was going to give up - as couldn't work out what else then remembered I always felt t was comms from the Rear SAM that just isn't communicating right - so if 2600 can't be SCN and oddly has limited manual coding choices - Using BenzNinja stuff I pulled all 4 versions and scouted about using text compare feature of the code. Orig software seems similar to 2600 I have, 3330 is also quite similar then bigger differences leaping to the mistake of the facelift iteration. What did move forward was diagnostic capability.

The right thing would be to fight the orig SAM back in the boot and flash that to 3300 but I don't think I have the energy - so wonder if going 2600 to 3300 would get the diagnostics up, coding choices to normal and the option to SCN the car and see if that feature wakes up after nearly 4 years on holiday

 

Hi Botus-- Yeah, I don't follow the forum too closely, but I like that I get an email when someone rings up one of my old posts...

1) On the Park Assist (which uses radar, as opposed to Parktronic, which uses sonar), my USA 2007 doesn't have Blind Spot. I added "as far as I know" and "if I recall correctly" because I wasn't sure about Park Assist's interaction with Distronic-- just as I wasn't sure exactly what LINDI was asking???

Anyway, the OM says, "The Park Assist system monitors the surroundings of your vehicle with four sensors in the front bumper and two sensors in the rear bumper." And, it has a handy illustration:



I thought there were 3 in front, but OM says 4! I checked them with DAS, as mentioned in this thread, and DAS will read out the distance in cm-- funny I don't remember 4, but my testing was just diagnostics used to narrow down the fault to one wheel sensor...

Anyway, the parking radar measures in cm's, only out to one meter or so, while the Distronic obviously measures out 100 meters or so. And, the OM says Park Assist "deactives" at 11 mph.. So, I still think they operate independently of each other, but I too don't know for sure. One thing for sure, they both use the wheel sensors and the take away from this thread was meant to be: if you have multiple systems inoperative, the most likely culprit is the wheel sensors...

2) On the SW updates, I stopped the updates after Telematics, and "accidently" (as in, being told by DAS to update ACC after Telematics) updated using a 902 update on the ACC (no ill effects from that 902, but you and others raised concerns about the compatibility of the 902 updates with the NGT 3.0).

My Rear SAM has SW 4421300 as shown in post #99 of the Programming thread.

Furthermore, the flurry of updates (from 4422400 to 4423300 in about 8 months, followed by a bunch of 902 updates) in SAM-H timeline gave me pause about the utility or necessity of the changes, i.e., one fix creates new bugs that need fixing... until MB quits trying...

So, my guidance must end there... Can you get your hands on 4421300??? Seems to work for me... but, I don't have it on a CFF...

Regards... Mark

 

Radar sensors show in the manual as


I didn't find the picture I was looking for about using all three fronts for active cruise


Rear SAM
mine was on 4421300 of week 04 2006 (when that feature was last known to work) - diagnostics showing 0/3
the diagnostics leaps forward with the one facelift they want you to run 9024003 - diagnostics showing at 0/9
the later part that comes running 422600 gets diagnostics showing at 0/5

so it looks like it was an upgrade to resolve diagnostic capability they think is suitable all the way through
AC I now think the change was the update on the OCP - when I flashed that back to old software the AC seemed very different - oddly there's an iteration in-between for a 221 rather than the ones either side starting at 216 xxx xxxx. This module update throws the car in a tail spin - had to battery reset every time as the gateway lost the plot.