Sadly, I don't have him anymore but new Daleks are in the pipeline...
20220807_165740.jpg
 
Measure the resistance at the height sensor. Then re-connect, and measure the same wires at the ECU. There will be small differences, but any open circuit wires should show up. Then decide whether the take seats out, carpet up, or just run new wires !!
 
Cruise pump uses LH connectors - see picture.

RF footwell white connectors (C101 & C102). Just search RAVE for these two (Control F3 & search).

Cruise wiring (except pump)
Various ECU diagnostic connections
Brake Switch
Some of the HEVAC stuff
Some of the Instrument wiring
Etc. Etc.
Thanks, I believe it may have been you that mentioned that the inhibit wire also ran through there, I have printed the diagram so I will have to dig it out. As I was only looking for the inhibit I probably didn't notice the cruise circuit.....
 
Measure the resistance at the height sensor. Then re-connect, and measure the same wires at the ECU. There will be small differences, but any open circuit wires should show up. Then decide whether the take seats out, carpet up, or just run new wires !!
I have a long tester unit and I went directly from the ECU to each sensor which told me there was no continuity on the RH rear which was all well and good but it didn't obviously tell me where the problem was. After tons of wire wiggling I pinpointed the break and all was well with the world again. I hindsight it would have been far easier just to have run a new wire and left the old one there, such is life!
 
Sorry I said CPU instead of ECU. My bad. So I'll just have to follow the cables back until I find the right ones...

I am not going to get to involved as others know more than me. But. Unplug it at the sensor and the ecu, bridge the relevant pins at 1 end and check continuity to start with. Continuity isn't always the be all of tests but its a start.
Then check the "common" line.

Or you could do each line separately.

Were they good quality sensors?

You can check the sensor on its own to see if its ok with a DMM, which I assume you have, if you don't then get 1.

J
 
Ah yes I have a DMM. What an idiot I am for not realising that, haha. Well like I say, DM me if you would like futher details. They £3000-£3500 a piece so they're not cheap mind you.
 
But the height sensors do not go via those connectors !! Soldering C104-C204 and C207-C357 did sort other stuff like these:

EAS timer relay diagnostic trigger
EAS Height Switch
Dodgy audio glitching
Cruise control,
Ambient air sensor
SRS diagnostics
They don't but the ride height switch does and that is what causes the problems often attributed to height sensors.
 
They don't but the ride height switch does and that is what causes the problems often attributed to height sensors.
Ah! Is that a fact. That's interesting. So would the diagnostic still register the sensor out of range if it was a bad connection the height switch?

That would be so much simpler...
 
While I agree there could be unexpected behaviour, I'm not 100% convinced it would cause height errors itself.

Unfortunately there not any real info out there that I have found. Nigel Hewitt's page does give some help, no definitive details on the real protocol.

The Up & Down switches from the switch to the EAS ECU are simply grounded to the ECU pins 32 & 33 to tell the EAS to go up or down. The EAS output data signals on pins 7 & 25 tell the switch LED's what to display, plus are inputs to the BECM pins 9+18 for messages in the Instrument Cluster display. Pin 8 on the BECM is for the Wade Lamp in the instruments, but it's not clear if this is triggered by the EAS Data, or thye state of the top LED ?

So issues with C104-C204, and C102-C202 will have different impacts. Up-Down might need several presses to get the ECU to respond ? Intermittent data signals would me with the LED's, and potentially tell the BECM incorrect info.

Maybe between us all we can figure it out ??

1718993225084.png
 
While I agree there could be unexpected behaviour, I'm not 100% convinced it would cause height errors itself.

Unfortunately there not any real info out there that I have found. Nigel Hewitt's page does give some help, no definitive details on the real protocol.

The Up & Down switches from the switch to the EAS ECU are simply grounded to the ECU pins 32 & 33 to tell the EAS to go up or down. The EAS output data signals on pins 7 & 25 tell the switch LED's what to display, plus are inputs to the BECM pins 9+18 for messages in the Instrument Cluster display. Pin 8 on the BECM is for the Wade Lamp in the instruments, but it's not clear if this is triggered by the EAS Data, or thye state of the top LED ?

So issues with C104-C204, and C102-C202 will have different impacts. Up-Down might need several presses to get the ECU to respond ? Intermittent data signals would me with the LED's, and potentially tell the BECM incorrect info.

Maybe between us all we can figure it out ??

View attachment 319841
Corrosion causing tracking between pins causes a variety of problems which I think confuses the ECU.
 
More often than not the up down switch lights operate for a few second without incident and the car will be roughly at the right height then all the lights on the switch come on and an EAS fault is read out on the dashboard (along with an airbag fault which is new)
 

Similar threads