Car is an 07 limited coupe, 6spd. 38500 give or take.

The other night I was on the way home doing about 75 and went to put the cruise control on and nothing happened. The car acted like it was going to hold speed, it sort of lurched everytime I flicked the cruise control stalk but wouldnt stick.

So I slowed way down, up until 50 it works just fine, but wont engage at all after that. I've tried engaging it at 45 and bumping it up past 50 with the accel part of the stalk but as soon as I get over 50 it cuts off.

Car doesnt throw any codes, so I'm at a loss

 

Maybe your fairy godmother is telling you to slow down.

 

After sitting over the winter my car did the same exact thing. I keep on fiddling on the stalk and it cleared itself. I suspect that the wiring had bad switches that were dirty and needed wiping, several times.

Gone and never returned yet, Enjoy Woody

 

maybe I'll try that, I've been doing it over and over. still anything above 50 and the car lurches then starts slowing down

 

mine would randomly shut off too, about the same time i couldnt get my alarm to shut off. so i unhooked the battery, let it sit over night (probs not necessary, but i was drunk) and it worked fine the next day i hooked it back up

 

I am having a similar problem. When the head lights are on the cruise control wont work at all, but if i turn the head lights off it works fine. I replaced the battery and the problem still exists. Has anyone had this problem. I have 87,000 miles on her and this problem just started in the last 200 miles or so.

 

My crossfire was working just fine until I took it to the dealership last Friday to have a sensor repaired. After I left the dealership my cruise control did not work the way it did when I dropped my car off. I took my car back and the dealer is refusing to take responsibility and they cannot tell me what's wrong with the cruise control. This really sucks because my car has never been in the shop other than basic services. It's a 2004 with 85,000 miles

 

Infinite, I would figure that since you know all things car, you would know exactly how to fix this problem.

Chances are that since this problem is being exhibited above 50mph, it has something to do with the front wheel speed sensors as the speed of the vehicle is determined by the rears up to 50mph or if they are spinning faster than the fronts after a certain threshold is broken, ie, doing a burnout. After 50mph, the speed is taken from the front tires. Check out the wheel speed sensors or have a tech connect to it with the starscan and DRB3 to see if there are any fault codes. It may be intermittent enough that you're not seeing the BAS errors which will cause wing deployment but that your cruise will not function as it thinks there is an issue with differing speeds between the front and rear wheels.

 

If you are looking for an answer to your problem from the members here you should inform them of the problem you have with the cruise control and the sensor that was replaced. Without this info the post will be dismissed as a rant.

 

The crank position sensor was replaced after the car stopped. Another member made a post previously describing the exact situation I had so I wont re-hash it here. The car's been very reliable, so this is the first issue with it period. It was taken to a chrysler dealer which is looking more like a mistake each day. The Crank Pos. Sensor was replaced & as I got on the highway to head home I engaged the cruise control ( above 55mph) & there was no response from the car. The cruise works at 55mph & below. It was taken back to the dealer & they say the the repair they made has nothing to do with the "new" problem; they're not responsible for it. I've gone through the threads & found that this is no isolated problem that no other x-fire owner has seen, & in those other cases the problem stood alone, so what are the odds that this cruise control problem coincidentally hit immediately after another repair was done.

 

This really make a lot of sense & I really appreciate it. I wonder if disconnecting the battery may reset the connection between the wheel sensor & what ever the other component of the sensor is. Again thanks.

 

i dont think any amount of recalibration will do the trick here. if you had
studied the tire specs prior to purchase, you will see that the rolling circum-
ference differs vastly between front and rear. accordingly the front tire
will be rolling 755x per mile, whereas the rear is rolling 729x per mile.....a
difference of 188' per mile....3" per revolution. that's extremely bad.
are you sure of the tire specs you posted? if so, why did you select these
tire sizes?

your rears should be 275-35....or, your fronts 245-45.

because the differential in rolling rubber per mile has exceeded the tolerance
limits of the cruise control, it shuts down.


I just pulled the above off of the MB forum, do you think this could be the root of the cruise control problems

 

I know what sizes I run. My crossfire is so low, about 2.5" off the ground I run a big stretch so i dont rub. It doesn't matter what tires I run I have the same issue. I think Rudy might be right, but since the car is totaled i don't plan on looking into it further. I was having issues with the speedometer being intermittently off (mostly when near a cop lol) anywhere from 12-18mph off