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.
Here's the deal: I've got a '00 Pewter Coupe with the "Active Suspension" feature. (Is that Z51? - I can never keep this cranberry juice straight.) I was driving on some fairly rough road here in San Antonio on Saturday afternoon. IT WAS REALLY FREAKIN' HOT! I don't know if that has anything to do with what happened, or not. But, I left a stop light in a fairly hasty manner, and got some wheel skip and chatter over some bumps in the road. My DIC went bonkers! It started blinking "Service ABS", "Service Traction Control" and "Service Active Suspension", repeatedly until I got home. There was never any change in the feeling or handling characteristics of the car. I turned off the ignition when I got home, let it sit for a minute, then restarted the car. Perfect. No lights, no messages, nothing. Yesterday, I took the car on a 90 mile round trip to play golf, again, no problem. Do I need to be concerned about this? Any comments? Also, this is my second C5, and I never messed around with the DIC, as far as clearing, or down-loading codes of any sort. Is this a necessary maintenance function that I need to take care of? Thanks to any and all with the intel on this one! :confused: [IMG][/IMG] [IMG][/IMG] :confused: [IMG][/IMG] [IMG][/IMG]
I myself would like to know about this error as well. It happened to a friend of mine at the Texas Motor Plex. He left the line at about 1500 RPM then his car got little loose and he got all 3 above errors. The only that was different was in his case the accellrator stuck on the floor, thats right just stayed down. When he got to the end of the track he slammed on his breaks and his tires started smoking. Finally the accellrator came back up, but when he stoped the car all three messages were on his display. Any of you guys know what might have happened?
It's possible that the wheel hop caused a condition that the computer interpreted as bad data. Maybe some sensor(s) or some program couldn't keep up with the start/stop of the wheel hop combined with AH trying to take control and it interpreted this as bad data coming from the sensors. Also, if the wheels hop at a certain rate and the computer is getting input from multiple sensors, it probably can't read them all at the same time so if the wheel is spinning at the instant when one of them is being read and not spinning when the next set of sensors is being accessed, that could cause the computer to think that it is getting conflicting data from the sensors.
All of the above adds up to my guess: the system just wasn't calibrated to handle wheel hop.
Thanks Guys! I went to the weblink and printed out the DIC info. I'll play around with it tonight. Like I said, the car runs and feels just fine. I'm hoping it was simply a brain fart on the part of the computer. Thanks again the for the info! :seeya