[talisman311]

I did some searching, but can't find a thread that relates to the issue I'm observing.

Anyone ever run into a dead cruise control stalk? Everything else works and I haven't ran into any error lights, but my cruise control stalk is in 'just for looks' mode.

[PTinVT]

Wild stab, I wonder if there's a bad clutch position sensor... I suppose you could test this by trying to start your car (in neutral) without your foot on the clutch and see if that works, when it shouldn't.

[Brandicular]

Originally Posted by talisman311

I did some searching, but can't find a thread that relates to the issue I'm observing.

Anyone ever run into a dead cruise control stalk? Everything else works and I haven't ran into any error lights, but my cruise control stalk is in 'just for looks' mode.

So this may be out there, but did you happen to replace any signal bulbs lately?

Adding LED/single filament bulbs to my Land Rover's tail-lights disabled my cruise control. In the newer model Ranger Rovers, it can put the transmission into limp mode. Swapped them out and everything was cool again.

Probably isn't your issue, but just a thought.

[talisman311]

Originally Posted by PTinVT

Wild stab, I wonder if there's a bad clutch position sensor... I suppose you could test this by trying to start your car (in neutral) without your foot on the clutch and see if that works, when it shouldn't.

I'll give it a shot on my lunch break and will report back.

Originally Posted by Brandicular

So this may be out there, but did you happen to replace any signal bulbs lately?

Adding LED/single filament bulbs to my Land Rover's tail-lights disabled my cruise control. In the newer model Ranger Rovers, it can put the transmission into limp mode. Swapped them out and everything was cool again.

Probably isn't your issue, but just a thought.

Nada.. I replaced the angel eyes with LEDs about 3 years ago, but that's the only bulbs I've had to replace.

[Indyeah]

Make sure your DTC (traction control) is on. Mine turned off once because a brake sensor issue.

[talisman311]

Originally Posted by talisman311

I'll give it a shot on my lunch break and will report back.

Nada.. I replaced the angel eyes with LEDs about 3 years ago, but that's the only bulbs I've had to replace.

Not the clutch switch... I have to press it all the way in to start.

Originally Posted by Indyeah

Make sure your DTC (traction control) is on. Mine turned off once because a brake sensor issue.

Same results in DTC, DSC on and DSC off. I'm going to try and scan it with INPA and see if anything comes up.

[noah.s]

Originally Posted by talisman311

Not the clutch switch... I have to press it all the way in to start.



Same results in DTC, DSC on and DSC off. I'm going to try and scan it with INPA and see if anything comes up.

You should be able to test the stalk itself in INPA. I don't remember exactly how but I was able to test my wiper stalks functions when I was having issues.

[talisman311]

Update: Was able to use INPA to confirm that the stalk works. I reset it and CDAD and D35B came back. Argh.

Still no cruise control. No error lights on dash. Halp?

[Flyboy161]

From what I can gather, D35B points to the yaw sensor. It is an integral part of the DSC system. A failure there could result in a dead CC stalk.

Your 2A98 and 2A82 are jammed VANOS solenoids. They need to be cleaned.

[talisman311]

Looks relatively inexpensive for the yaw sensor.. I would've thought there'd be more dash lights with that type of failure. I'm going to keep researching and going to try and recode cruise control in.

More FYI - updated the CAS in 2/2016 to whatever was latest at the time. This was to fix the column lock issue where the car wouldn't always start when it started to fail.

[Flyboy161]

You mentioned "reset" and "recode". Are you performing the F2 "Clear EM" in INPA?

[talisman311]

Originally Posted by Flyboy161

You mentioned "reset" and "recode". Are you performing the F2 "Clear EM" in INPA?

Yes.

Recode - I see that some people retrofitted cruise control. I'm wondering if CAS may have 'forgot' that I had cruise control after I updated. Why it took a year to 'remember', I have no idea.

[Flyboy161]

1. So, INPA ops check- the stalk is working
2. Other than CC not working, are you getting an indication in the instrument cluster when you try and engage it? As in the speedometer symbol with a carrot and dashes underneath where the set speed should be?
3. Typically CAS doesn't forget about installed components, but worth a shot.
4. I am more concerned with the VANOS codes at the moment... This is a 330i, what motor do you have? M54B30?

[talisman311]

Originally Posted by Flyboy161

1. So, INPA ops check- the stalk is working
2. Other than CC not working, are you getting an indication in the instrument cluster when you try and engage it? As in the speedometer symbol with a carrot and dashes underneath where the set speed should be?
3. Typically CAS doesn't forget about installed components, but worth a shot.
4. I am more concerned with the VANOS codes at the moment... This is a 330i, what motor do you have? M54B30?

1. Correct - all positions checked out ok in INPA. Also verified with INPA that the set speed dial works.
2. No indication in instrument cluster. The stalk is in 'just for looks' mode and doesn't trigger anything.
3. Here's hoping..
4. N52.. The VANOS has been replaced before, but I forgot which side. I'll blow some compressed air through them on the next oil change.

[Greyfox]

I know it's going to sound crazy but check your emissions.

I had a car at one point in time that the emission sensors started detecting emissions issues and would literally shutoff the cruise control while traveling down the interstate.

[Flyboy161]

The two codes for VANOS indicate it is not working. Does your N52 have Valvetronic? If VANOS is not working you're going to have power issues. Without Valvetronic it is normally aspirated using the throttle body. With Valvetronic the Intake air is controlled by eccentric shaft and not the throttle body. If vanos is acting up that could create issues with CC.

Also, brake light switch. I understand you have no other indications, but that is something that shuts off CC. The DSC shuts off CC if it senses a yawing motion in the car. Which again points back to yaw sensor. CDAD is a vague code that refers to wheel torque sensing.

[talisman311]

Update:

No more VANOS codes after the reset last week but DME - CDAD and DSC - D35B persists.

- I added $540 to CAS and FRM modules
- Re-initialized DSC stuff except for bleeding in INPA
- Verified that INPA is reading yaw rate from DSC (no active front steering so no reading on AFS yaw sensor)

No cruise control still. How the hell does a car forget it has cruise control?

I.hate.this.car.

[kckirch]

Just a long shot hoping you guys are still active. How did you test the cruise control stalk, I'm having the same problem. Can't seem to find the CC in INPA

[ptpending]

it's bound to dsc

[kckirch]

Originally Posted by kckirch

Just a long shot hoping you guys are still active. How did you test the cruise control stalk, I'm having the same problem. Can't seem to find the CC in INPA

Found it

E90>Chassis> Dynamic Stability Control> Status Lesen (F5)> Tempomat/ACC (F6)
Taster Tempomat shows if the clicks are being recognized

[talisman311]

All - just an update it turned out to be my ldm module. I was able to clear cdad on my dme after digging through inpa and then I started to get errors trying to enable cruise. D35b kept coming back.After changing the ldm to a used one off eBay, it worked instantaneously.

[Phyrexia]

Big high five for coming back and letting us know.