HELP. EAS Unlock software - found problem of "Pressure signal constantly high"

This site contains affiliate links for which LandyZone may be compensated if you make a purchase.

Keith1

New Member
Posts
8
As stated above... any ideas as to what's happening and the possible solutions?

Thanks, Keith.
 
Unfortunately that could be a lot of things. Does it come back if you clear it?
You can try parting the connectors in the EAS box and cleaning the contacts for starters.
It could actually be a duff pressure switch but they don't fail that often, it could also be the driver pack and a few other things.
 
Mine goes through phases of reporting this fault. Unfortunately yesterday on Salisbury Plain was one of those days. Still, it didn't come back after 3 resets.

It seems that it can be caused by a number of things, the most likely of which seems to be a dodgy driver pack. I'm not entirely convinced about that in my case, but who knows?
 
Driver pack needs replacing. Don't waste time or cash , just change it!

Lots of people say that, and apparently it works but how is an enigma. As the driver pack has nothing to do with pressure switch or compressor. Apart from it closes the Diaphragm solenoid valve when compressor is running. All it does is switch current to the solenoid valves at the command of the ECU. So it remains a mystery.
 
Lots of people say that, and apparently it works but how is an enigma. As the driver pack has nothing to do with pressure switch or compressor. Apart from it closes the Diaphragm solenoid valve when compressor is running. All it does is switch current to the solenoid valves at the command of the ECU. So it remains a mystery.

Have seen this problem quite a few times before. If the pressure switch tests okay, usually the fault seems to lie with the driver pack. The only one exception was when there was a wiring fault between the valve block and the EAS ECU.
Did this on a few RR's belonging to friends.
 
As it happens I logged this fault twice in three days a couple of weeks ago. All I have done is part and clean the connectors in the EAS box, no more problems since. As the connectors have to be parted to change the driver pack, it could be that driver packs are been changed just because of a bad connection which obviously clears when the new connector from the driver pack is plugged in.
 
As it happens I logged this fault twice in three days a couple of weeks ago. All I have done is part and clean the connectors in the EAS box, no more problems since. As the connectors have to be parted to change the driver pack, it could be that driver packs are been changed just because of a bad connection which obviously clears when the new connector from the driver pack is plugged in.


That is a very plausable explination Keith. Unless a faulty driver pack feeds back and sends the ECU into a skits. That can be the only explination. As i said the driver pack has nothing to do with compressor or pressure switch. Unless the faulty pack is switching the diaphragm solenoid on and off and the ECU sees that as a high pressure signal don't really know to be honest.
 
Last edited:
As it happens I logged this fault twice in three days a couple of weeks ago. All I have done is part and clean the connectors in the EAS box, no more problems since. As the connectors have to be parted to change the driver pack, it could be that driver packs are been changed just because of a bad connection which obviously clears when the new connector from the driver pack is plugged in.
That was another of my theories back then - but it wasnt so,after refitting the drive pack the fault still came back.Sometimes that day,sometimes a month later.I cant be bothered to try figuring out why the drive pack failing logs that fault.None that were renewed ever came back with the same fault.
As far as I'm concerned p38's have almost gone now - diagnostics wise,the later L322's,D3/4 and Fl 2 are the ones I need to concentrate on now.
 
That was another of my theories back then - but it wasnt so,after refitting the drive pack the fault still came back.Sometimes that day,sometimes a month later.I cant be bothered to try figuring out why the drive pack failing logs that fault.None that were renewed ever came back with the same fault.
As far as I'm concerned p38's have almost gone now - diagnostics wise,the later L322's,D3/4 and Fl 2 are the ones I need to concentrate on now.

I have 2 spare driver packs just in case:D
 
Sorry, been a bit late replying, thank you for all the responses. I'll take on board the advice and give it all a try. Will report findings. Thank you again :)
 
Back
Top