EAS: Live wn't match target height

[Craig_Keira]

This is only occuring on my front right. The standard height for FL is 122. The sensor (according to the Nanocom) is reporting 130. And the rangie won't change it. Send it to access mode, OK. Send it to Standard - yup 130. And it is sitting high on the FL.

Had a search, can't find this particular problem. Or simply can't find it amongst the swag of EAS posts

Unrelated? - just came back from Namadgi National Park for a night's camping. I did notice some strange EAS behaviour. When going from access to standard, the front went up, came back down then went back up. Odd. Also, after locking the EAS into motorway, I couldn't get it to go to Standard - but it did do it as an automatic thing.

There was one fault code stored in the EAS - Invalid Fault Code. I've had that before and cleared it straight away.

Anyone got ideas on why the EAS is not matching the height sensor to the target value?

Cheers
Craig

[ytt105]

Craig

When going from motorway to normal you have to push the EAS lock switch down before you push the up button.

When I did some adjustments to my previous P38, it took a couple of goes to get the settings to stick.

Don't know why, but if at first you don't succeed.. you know the rest.

Where did you camp in Namadgi?

Trevor

[Craig_Keira]

Gah! It got me again! Oh well...

It's been doing this for a while now, Trevor. One day the front left suddenly was up in the air and it's kind of been that way since. I checked the values and it's reporting target: 120 with live: 130. So, indicating that it knows that the FL is high, but isn't fussed about it.

We were at Mt Clear. Did a quick jaunt to Adaminaby which cost us a flat tyre on the way back. Damn RR...I couldn't tell except for a very faint noise. I was still belting along at 80 with no idea the RR tyre was dead flat. Handling and ride was still good. Have to be careful of that with these beasties.

[ytt105]

I destroyed one near new tyre in my air suspended Classic before someone pointed out that it was flat.

Got a flat in the P38 on the Oonadatta Track but only travelled a couple of minutes before stopping to site see. Luckily!!

A TPMS is due to arrive soon. Will definitely be fitted before any more dirt road touring.

In regards to the EAS, you may need to change all readings a little, save them, and see what happens.

Once you get it sorted it will probably be faultless.

Like my old one is, ha ha!

[Craig_Keira]

Thanks Trevor :P

OK, so I've changed all the settings a tiny bit, including raising the diagonally opposite corner (RR) - and no damned change! Still sits high. It does appear to correct itself after a couple of minutes driving.

So:
1. EAS lifts the front
2. Front Left goes about 130 instead of target 123
3. EAS ECU reports FL is too high
4. EAS is unconcerned
5. Drive off, EAS decides to do something about it

Nuts.

[Hoges]

Yep...can be very frustrating!!

There's a "proportional" relationship governing relative values between F/R and between various height settings. If your bit settings are outside or close to the margins of this relationship, then you can experience problems like those you have mentioned.

The settings are programmed into the "firmware" governing the EAS operation and appear to be designed to prevent tinkerers from undertaking their own "custom" settings other than limited tweaking to make up for variation in the sensor tolerances.

Have you tried to standardise the settings? By that I mean set the standard height using 105mm wooden blocks at rear and 100mm blocks in the front between bump stop stub and axle plate as per the EAS systems document. Read off the bit numbers...these represent the reference bit counts for factory-level standard height

You could make up separate sets of blocks for each height setting and store a set of bit measurements for each height...these become the reference settings for those particular sensors.

There may be a problem with the FL sensor tracking. If you haven't already done so, try swapping the FL/FR sensors with each other. The sensors are an either-side fit so only use one section of the "tracking" for the variable resistor. When you swap them you use the other side i.e. a (literally) "new" track.

cheers

[Craig_Keira]

I agree. It *is* very frustrating.

I've run foul of the value limits before, generating myself an EAS Fault. That wasn't hard to work out. The weird thing is that the FL suddenly went high (without any idiotic help from me!) and stayed that way. Using the trusty Nanocom, I was surprised to find that the EAS was reporting it as high. I expected to see it as not detecting that state. Unfortunately, this would make sense.

I'm going to undertake that calibration. It was always sitting a little low at the RR, so I may as well fix it properly. Can I do this: place the blocks under the bump stops, drop the vehicle down to Access (which it won't be able to do), go into the EAS on the Nanocom and transfer the Live Values to Target Values for Standard height? What blocks do I use for Motorway (Low)?

Also, do I remove the bump stops or just sit the blocks on top of the axles and allow the bump stops to rest on them? Do we not care in variation in the bump stop compression?

EDIT: I think the sensor is OK - it's reporting the height as being higher than the target. If it were reporting that the FL at correct height - agreed, swap it.

Cheers

[Hoges]

If the RR is low then this will be affecting the FL...

Pull off the rubber bump stops...replacing them is easy enough using soapy water or some lanoline grease or line them up with a blocks in place and lower the body gently with a hydraulic jack and use the body weight to press them on!

You can quickly make up a set of blocks using a long piece of 50mm x 50mm hardwood: just cut it into the requisite lengths.
For the highway mode just reduce the lengths from standard by 20mm; and 60mm from standard for access mode. Cut the lengths +40mm (above standard) for High Profile mode.

cheers