I have attempted to scan my 1996 W210 to find out why my cruise control is not working. Each time I connect the OBDII scanner, the scanner is unable to communicate with the vehicle. I have tried at least 5 different scanners, and they all show the same message. At the same time, I will appreciate anyone who can assist with the reason why my cruise control will not function and what I need to do to fix the problem. Can anyone help?

Your car isn't OBDII.

__________________
600SEL '91
300E 4Matic '88
240D '83
280SE '77
350SE '73
The most complex systems can fail in the simplest way.
Contra verbosus noli contendere verbis, sermo datur cunctis, animi sapientia paucis.

i don't believe in the lord! He's never bought me a Mercedes Benz.

What is it Daddi? I have used OBDII scanner in the past, and that is how my state emmission inspection is done.

I thought everything was OBDII in 1996. I could be wrong however. At any rate, OBDII will not tell you anything about cruise control. That is a different system. You would need to hook into the chassis CAN bus which requires much more expensive tools. OBDII is just for the engine.

What is the symptom of the CC? Can it operate even at low speed?

You could try searching some key words.

__________________
1998 C230 330,000 miles (currently dead of second failed EIS, yours will fail too, turning you into the dealer's personal human cash machine)
1988 F150 144,000 miles (leaks all the colors of the rainbow)
Previous stars: 1981 Brava 210,000 miles, 1978 128 150,000 miles, 1977 B200 Van 175,000 miles, 1972 Vega (great, if rusty, car), 1972 Celica, 1986.5 Supra

All north american mercedes 96 and later are OBDII compliant by US federal law. But it will only tell you about info related to items that will turn out the check engine light. That all said many 96 cars have a problem with the OBDII drive cycle monitors reseting. I am also experienceing this problem. The drive cycle monitors will not reset even driving hundreds of miles. Makes it very difficult to get my car smoged!

__________________
88 W124 3.0
96 R129 119eng
06 ML350
98 ML320 sold
02 CLK55 amg

Have you tried the drive cycle "prescription"?

__________________
1998 C230 330,000 miles (currently dead of second failed EIS, yours will fail too, turning you into the dealer's personal human cash machine)
1988 F150 144,000 miles (leaks all the colors of the rainbow)
Previous stars: 1981 Brava 210,000 miles, 1978 128 150,000 miles, 1977 B200 Van 175,000 miles, 1972 Vega (great, if rusty, car), 1972 Celica, 1986.5 Supra

The CC just will not work. I am not sure if it has anything to do with my idle being abnormally high either. I was told that the Electronic Throtle Valve is defecetive, but the car only has 73k miles on it. I have replaced one of the computers (The CARB), and it did not make any different to the high idle or the CC. I am not sure what the drive cycle is or how to go about performing that test.

Sorry, my drive cycle comment was off topic, to the other poster. If the car thinks the electronic throttle valve is bad, then it likely will not engage the cruise for safety reasons (think Toyota...) The cruise control needs the throttle to be working correctly!

__________________
1998 C230 330,000 miles (currently dead of second failed EIS, yours will fail too, turning you into the dealer's personal human cash machine)
1988 F150 144,000 miles (leaks all the colors of the rainbow)
Previous stars: 1981 Brava 210,000 miles, 1978 128 150,000 miles, 1977 B200 Van 175,000 miles, 1972 Vega (great, if rusty, car), 1972 Celica, 1986.5 Supra

the cruise controll did not work on my car when the EA was bad.,But it also caused the ASR ABS lights to come on. It will not cause the check eng light to come on. It goes thru the traction controll computer not the ECU. Hopes this helps

__________________
88 W124 3.0
96 R129 119eng
06 ML350
98 ML320 sold
02 CLK55 amg

Thanks guys for all the comments. Will attempt to repalce the ETV, and post the results once completed.