benthomas

benthomas

Active Member
I've searched the phrase above but the results I found were quite inconclusive and don't really answer my question.
Up and running again thanks to a compressor refurb and help from Nikthegeek to clear codes.
As soon as we got the fault cleared and eas took over I noticed it went higher in std height setting than before the failure of the pump and mistakenly thought it was because of the better air supply.
Wrong, when measured it's riding way over the factory heights at all levels, between 30-60mm over.
I've now got the easunlock and lead and have captured all the sensor settings at the desired heights with easunlocker and a tape measure.
At the desired height all of the corner values are close enough to each other to suggest the sensors are reading ok.
When I enter the desired values (all of which are in the acceptable ranges and do not crossover) the eas accepts them as they come back on a read all.
When I stop the calibration I get EASFAULT, on clearing the fault it resets all the values of FR higher than I programmed and gives F9 64 "target height incorrect"
Why?
Sorry if this has been resolved in a previous thread, I don't mean to p155 anyone off.
 
I had the same issue when calibrating with the tape measure.
Build the calibration blocks (check Wammers "How to" section) and try again, you will be surprised with the results.
 
The sensor heights must stay within a certain limit between them selves. The system won't accept big changes in the values relative to the other side of the same axle.

The front is more sensitive.

Just restrict each change you make to a small value, enter it and wait for the vehicle to settle.

Do this on say, front RH, then do front LH, then back to RH and so on. Or, do both sides of the same axle at the same time but keep the changes in proportion both sides. Hope this makes sense!


HTH.
 
As far as I am aware I have the exact values I need from using the heights facility on easunlock, lower or raise the car in small increments until you achieve your required height, then record the values from each sensor?
I spent 90 mins on perfectly level ground and got the heights to within 4mm on each corner and the sensor values were all within 5 points of each other which tells me the sensors are working, also all within the permitted parameters of the eas.
The car adjusts to the required height and give the sensor value when using the heights facility but then wont accept and store its own data on the calibration page?
From reading previous threads on this topic, some people have a similar issue but report massive differences in sensor values, others mistakenly attempt to enter values outside the permitted parameters or have this issue that sorts itself out overnight after several attempts at calibration.
I cant see what i'm doing wrong?
Which unlock tab is best to use? do they both do the same thing or does the one on the calibration page clear the values and revert to factory setting as well as unlocking?
 
Last edited:
benthomas said:
As far as I am aware I have the exact values I need from using the heights facility on easunlock, lower or raise the car in small increments until you achieve your required height, then record the values from each sensor?
I spent 90 mins on perfectly level ground and got the heights to within 4mm on each corner and the sensor values were all within 5 points of each other which tells me the sensors are working, also all within the permitted parameters of the eas.
The car adjusts to the required height and give the sensor value when using the heights facility but then wont accept and store its own data on the calibration page?
From reading previous threads on this topic, some people have a similar issue but report massive differences in sensor values, others mistakenly attempt to enter values outside the permitted parameters or have this issue that sorts itself out overnight after several attempts at calibration.
I cant see what i'm doing wrong?
Which unlock tab is best to use? do they both do the same thing or does the one on the calibration page clear the values and revert to factory setting as well as unlocking?
Click to expand...

It's impossible for the suspension to be 60mm out, the software will not allow it, I think you may be measuring incorrectly. when you stray outside the permitted values, the software reverts to the default settings.
The ounly way it could be that far out is that someone has fitted a mod to the height sensors mountings or arms to allow a 2" lift for off roading.
 
Each profile has different parameters they are not all the same. Set in a profile and go to heights page. Press get. Present settings for each corner at that profile will appear. Adjust up or down until level with correct measurement wheel to arch. Note figures. Check they are all within the parameters for that height. Go to calibration page. Enter readings from your notes and press write. Set to a different profile allow car to settle. Press go to height you have just written car should go to that height and the numbers you have just written should appear on heights page. If any one setting is out even by one number either way above or below the parameter for that profile EAS will revert to previous settings.
 
Datatek said:
It's impossible for the suspension to be 60mm out, the software will not allow it, I think you may be measuring incorrectly. when you stray outside the permitted values, the software reverts to the default settings.
The ounly way it could be that far out is that someone has fitted a mod to the height sensors mountings or arms to allow a 2" lift for off roading.
Click to expand...

I am as amazed as you Datatek, but can assure you I have measured 900mm floor to arch centre on high setting and 850mm floor to arch centre on standard setting. It seems impossible is a word not known at land rover?

To achieve the desired ride heights as listed in in many postings of
High 830mm
Std 790mm
Mway765mm
Access730mm

The eas sensors on the heights tab report
125 125 124 123
96 95 88 89
77 75 82 82
60 55 69 66

When I write these values on the calibrate page it at first accepts the values as it reports them on a read all but when I stop calibration and disconnect the obd it sends a "target height incorrect" fault F9 64 vaule and "EASFAULT" to the dash and changes FR values to
141
109
98
85

This then lifts the front to 850mm standard setting after it has levelled it self out, the rear is happy to comply with my values.

When I go back in to clear the EASFAULT, yes you know it reverts back to the factory settings?

I cannot believe the eas will give figures for a given height, then not accept it own data as correct even though it is within all of its parameters?
 
wammers said:
Each profile has different parameters they are not all the same. Set in a profile and go to heights page. Press get. Present settings for each corner at that profile will appear. Adjust up or down until level with correct measurement wheel to arch. Note figures. Check they are all within the parameters for that height. Go to calibration page. Enter readings from your notes and press write. Set to a different profile allow car to settle. Press go to height you have just written car should go to that height and the numbers you have just written should appear on heights page. If any one setting is out even by one number either way above or below the parameter for that profile EAS will revert to previous settings.
Click to expand...

So am I best to do one setting at a time?
Go on Heights tab, set the height, retrieve sensor values, calibrate those values against that setting, write, read, goto that setting, Heights tab again, get values, confirm the are correct then stop the programme disconnect, start car check heights and the go back in and adjust the next height setting?
 
benthomas said:
So am I best to do one setting at a time?
Go on Heights tab, set the height, retrieve sensor values, calibrate those values against that setting, write, read, goto that setting, Heights tab again, get values, confirm the are correct then stop the programme disconnect, start car check heights and the go back in and adjust the next height setting?
Click to expand...

But be careful, if you get one setting wrong up or down above or below the parameter for that particular profile ALL the settings will revert to default. You will be going around in very large circles. Don't sit in the car to change the heights then get in and out to do the measuring. Readings will change each time you get in and out.
 
Last edited:
benthomas said:
I am as amazed as you Datatek, but can assure you I have measured 900mm floor to arch centre on high setting and 850mm floor to arch centre on standard setting. It seems impossible is a word not known at land rover?

To achieve the desired ride heights as listed in in many postings of
High 830mm
Std 790mm
Mway765mm
Access730mm

The eas sensors on the heights tab report
125 125 124 123
96 95 88 89
77 75 82 82
60 55 69 66

When I write these values on the calibrate page it at first accepts the values as it reports them on a read all but when I stop calibration and disconnect the obd it sends a "target height incorrect" fault F9 64 vaule and "EASFAULT" to the dash and changes FR values to
141
109
98
85

This then lifts the front to 850mm standard setting after it has levelled it self out, the rear is happy to comply with my values.

When I go back in to clear the EASFAULT, yes you know it reverts back to the factory settings?

I cannot believe the eas will give figures for a given height, then not accept it own data as correct even though it is within all of its parameters?
Click to expand...

It maybe the front figures at standard and motorway height that are causing your problem. Don't have anything set at or near to bare minimum. Eg the 96 and 95 you have them set at, stay at least five beats above minimum. See what you get. Heights are plus or minus 7 mm don't try and get to close to perfection. You can try moving the sensors on their bolts or flexing the arms to get a more middle of the road reading. All the front settings look a little low. That maybe your problem.
 
Last edited:
wammers said:
It maybe the front figures at standard and motorway height that are causing your problem. Don't have anything set at or near to bare minimum. Eg the 96 and 95 you have them set at, stay at least five beats above minimum. See what you get. Heights are plus or minus 7 mm don't try and get to close to perfection. You can try moving the sensors on their bolts or flexing the arms to get a more middle of the road reading. All the front settings look a little low. That maybe your problem.
Click to expand...

Thanks Wammers in going to have another go in a bit if time permits.
I was going to employ the mechanical fix to the electrical glitch if I needed to...bend the bloody sensor arm !
 
benthomas said:
Thanks Wammers in going to have another go in a bit if time permits.
I was going to employ the mechanical fix to the electrical glitch if I needed to...bend the bloody sensor arm !
Click to expand...

When Land Rover use Testbook it says to get them within two beats side to side. I fail to see how they can do that without adjusting the sensor positions or arms.
 
wammers said:
When Land Rover use Testbook it says to get them within two beats side to side. I fail to see how they can do that without adjusting the sensor positions or arms.
Click to expand...

Adjustable drop links for the sensors would be the ideal fix, you could probably get it mm perfect then.
Maybe something i'll look into in the future.
 
benthomas said:
Adjustable drop links for the sensors would be the ideal fix, you could probably get it mm perfect then.
Maybe something i'll look into in the future.
Click to expand...

When Testbook is used the car is sat on blocks so the height cannot vary. So in order to get within two beats side to side they must adjust the sensor position or flex the arms. It is the only possible way it can be done.
 
Last edited:
Thanks for your advice wammers and everyone else, got it sorted.
Took slack out of front sensors on the mounts, that gave me 2 beats, then bent the sensor arm on FR by approx. 3mm and that gave me another 2 beats.
Captured the sensor figures at the desired height and its to within 5mm on all four corners and 3 beats on each axle.

Just for interest, this is what 910mm looks like on the FL

WP_20130615_002.jpg

And I think it was only the limit of the bag that stopped it at 910mm !
 
Last edited:
benthomas said:
Thanks for your advice wammers and everyone else, got it sorted.
Took slack out of front sensors on the mounts, that gave me 2 beats, then bent the sensor arm on FR by approx. 3mm and that gave me another 2 beats.
Captured the sensor figures at the desired height and its to within 5mm on all four corners and 3 beats on each axle.

Just for interest, this is what 910mm looks like on the FR

View attachment 46713

And it think it was only the limit of the bag that stopped it at 910mm !
Click to expand...

Good lad. Listen to uncle Tony. You know it makes sense. :D:D:D
 
You must log in or register to reply here.

Similar threads

feyniriel
P38 EAS problems
Replies
18
Views
1K
pwood999
pwood999
S
Height suspension / sensor issue - can't calibrate
Replies
3
Views
1K
Graculus
Graculus
M
Air suspension problems
2 3
Replies
59
Views
3K
Rubberknees
Rubberknees
M
Air suspension problems
Replies
1
Views
396
Datatek
Datatek
stevebrookman
P38A EAS Unlock suite
Replies
11
Views
1K
stevebrookman
stevebrookman