EAS Unlock calibration weirdness

mcapinha said:

I remember reading somewhere that the EAS will not accept values lower than 60 and higher than <some number that I've forgot>. You were trying to set it to 52, so maybe that's the problem ?

Click to expand...

Ridesafe said:

Thank fooooooooooook for that Guy...well done in percy vearing!

Click to expand...

mcapinha said:

I remember reading somewhere that the EAS will not accept values lower than 60 and higher than <some number that I've forgot>. You were trying to set it to 52, so maybe that's the problem ?

Click to expand...

kooky_guy said:

I found a link to an EAS Service Bulletin on here somewhere which stated the lowest acceptable value is 40, but I'm not sure I believe it.

That was referring to the official LR calibration procedure though, using the blocks and Testbook.

It also mentioned that it can have problems accepting new values until it's successfully completed a full calibration. No hint as to how to recover from an unsucessful calibation, which I'm guessing was part of my problem.

Still, it's all good fun. Got a dodgy connection in my FR headlight assembly now (random warnings for all bulbs in that cluster). Something to do at lunchtime I guess.

Click to expand...

wammers said:

EXPECTED HEIGHT SENSOR BIT COUNTS​

​

​

Range Rover Classic
Ride State Front Sensor Range (bits) Rear Sensor Range (bits)
High 110-155 105-150
Standard 90-125 100-125
Access 50-100 50-100
New Range Rover
Ride State Front Sensor Range (bits) Rear Sensor Range (bits)
High 120-180 105-150
Standard 95-150 85-130
Low 75-140 75-120​

Access 50-110 50-100

That taken from service bulletins. Minimum value settable is 50. IF you set a value under or over in ANY mode the ECU reverts to default stored values for ALL modes and you have to start again.

Click to expand...