Thread: W209 Comand - Momentary interrupts

Hi - I have a Mercedes CLK 320 2005 Elegance. WDB2093652F114255. The Comand system momentarily interrupts i.e. the radio, CD player stop for a second and then resume. I thought initially it was a dud CD, but it also happens with the radio. This can happen just after the car is started and up to 3 times every 40 minutes or so while driving. It is almost as if power is lost to command except that there is no loss of screen. Has anyone had a similar problem? Is there any sort of reset for comand other than the power on button on the screen? Also does anyone know whether there has been a firmware upgrade for this version of comand since the car build? Great group forum! Andy in Australia

From your chassis number your car is Model Year 2004 - i.e before Model Year 2005 facelift - i.e has CD based COMAND system and a phone system.

The car does not have BOSE, so the amplifier is in the COMAND and not on the fibre optic network.

It also has phone system, and I suspect this is happening because of that.

Please check to see if you have any outstanding unread SMS messages on your phone & read them if you do and see if it goes away !

Richard

[ps, last update for CD Comand was in 2002]

Originally Posted by richard

From your chassis number your car is Model Year 2004 - i.e before Model Year 2005 facelift - i.e has CD based COMAND system and a phone system.

The car does not have BOSE, so the amplifier is in the COMAND and not on the fibre optic network.

It also has phone system, and I suspect this is happening because of that.

Please check to see if you have any outstanding unread SMS messages on your phone & read them if you do and see if it goes away !

Richard

[ps, last update for CD Comand was in 2002]

Thanks for the early reply it was really appreciated. The problem may be more complicated than I first thought - The car was purchased second hand and registration shows 2005 but I accept that it must be 2004. There is a phone system but no phone, and so I purchased a viseeo MB2 to connect to my blackberry about 6 weeks ago. I have had trouble getting the viseeo MB2 to stay connected and have now had the unit replaced after thinking that the interrupts were caused by the viseeo being faulty. Visseo connects then hangs (comand momentarily interrupts as in my first post). The reason for my post was that I took the viseeo out of the car in desperation (continued disconnections) only to find that it (comand) continued to interrupt and so I thought that rather than be a problem with the viseeo it was therefore a problem with comand. (fuzzy logic?) Your post seems to shed some light on it now being a phone issue. How do I access sms messages in comand and test your theory?

Actually, if the cradle is unplugged then its not directly the phone system - also ViseeO does not support SMS, so it won't be that.

If you look on Mercedes Electronics upgrades, installation and retrofits there is an article about Comand diagnostic mode - please read it and look at the error list and let me know the error numbers

Mercedes COMAND Diagnostic (Service) Mode

Here is the error code list (link in article is broken)
COMAND Error Codes

Comand also has a mute input for connecting to phone kits (not used by MB phone kit) and I think that pauses the CD also (you say it pauses rather than just going silent and missing a bit) so it could be something to do with that - anyway. post the error list with the types & the counts for each error as shown on the display

Richard

Hi Richard thanks for your help on this. I will run the diagnostic and get back to you (different time zones) standby. BTW yes it just goes quiet for a second, it doesn't pause the CD.

OK, best to reset the error codes (hold Mute + 0) and then see what appears after the next time it goes silent on you !

Richard

Hi Richard

These are the codes I got

screen 1

N1116 0 * 0005 001 P
B1795 0 * 0000 096 P
B1734 0 * 0000 001 P

Second screen Internal list

N1116 0 * 0005 001 P
N1009 0 * 0000 001 P
0015 0 * 0000 002 P
0018 0 * 0000 002 P
B1795 0 * 0000 096 P
B1777 0 * 0000 942 P
0012 0 * 0000 257 p
0004 0 * 0000 001 p
B1734 0 * 0000 001 p
B2708 0 * 0000 001 p

I have now reset comand and I am waiting till next time it occurs.

Thanks Richard

I reckon all those codes should have $ signs on them coz that is probably what it is going to cost to fix it!

Hi Richard What do you think so far?

Hi

From one of the other diagnostic screens is the list of D2B components (configured and actual) can you send me those lists ?

N1116 0 * 0005 001 P

The above suggests an issue with one of the D2B components (the one in position 5) but has only happened once so not likely to be the issue

B1795 0 * 0000 096 P
This has happened alot and is the COMAND losing contact with the rest of the car over it's CANbus (in particular the EIS) its not losing connection to the Cluster though or you *should* get B1780 in theory (but may not be so in practice)

B1734 0 * 0000 001 P
This one (again with only 1) is probably not important.

Lets wait for the error to re-occur and look at whats been flagged.

R

(ps, for anyone else looking in the future the * is in fact an x so the code is "B1734 0x0000 001 P" - the 0xNNNN means a base 16 number (computer talk))

Thanks Richard. I will drive for next 3 days and re examine, plus look at the settings for you. Regards
Andy