This might be of interest. Electronic Air Suspension
pmallinson
Member
Peter Just searched for this in the how to section and cannot find it ? I cannot see ANY in the how to section that was updated by yourself ?
Please let me know where it is ?
Thanks
Forum Mods have to approve How To entries.....
Maybe they havent got round to it yet.
Nothing in "How to" for approval section either as far as i can see. Will have a look on Nano site and see if i can find it.
blue beasty
Leaks an prone to bits dropping off
All additions to threads in 'how to' sections need approval.
I have no way of knowing anything has been added without wading though dozens of questions posted in wrong areas unless someone tells me.
Post and attachments approved
I have no way of knowing anything has been added without wading though dozens of questions posted in wrong areas unless someone tells me.
Post and attachments approved
Datatek
Well-Known Member
Today during round trip to Ferndown (185miles), I had the "random high mode" about 5-6 times. Four times I managed to press the down switch in time and avoided the fault mode, but twice I missed it, and EAS went into fault mode. Reset each time with Nanocom & continued journey.
So for the last 50 miles I thought, lets try data logging on the Nanocom and catch the fault. . . . . . no further problems . .so my wife says "just connect it when you drive !
Does Nanocom usually prevent EAS faults while connected ?
History:
Already bypassed the white connectors in left footwell:- soldered joints instead of green corrosion.
Connectors in engine bay look good. Still need to check sensor connectors.
Compressor seals & piston seal replaced 3 weeks ago:- good pressure before & excellent now.
Replaced all seals in Valve block yesterday:- no more leak from exhaust outlet.
All height sensors give similar readings on Nanocom at all height settings. . . might be glitchy, but does't look like it on Nano.
------------------------------
I now suspect driver pack strangeness but being an electronics engineer, I want to investigate rather than part-swap.
My thoughts are to start fitting additional capacitors to the ECU & Driver Pack inputs to remove random vehicle electrical noise. Many years ago I designed a variable wipe system form my old XJ6, and you would not believe how random the wipers were until I filtered the electronics properly.
- So, firstly does anybody have an internal diagram for driver pack ?
- Are the 12V switched inputs from ECU filtered for vehicle noise ? (maybe the capacitors have dried out)
- Do the height sensor inputs to ECU have sensible low-pass filtering ? (I'm sure the ECU does not need to know every small bump on the road)
BTW, In case anyone finds it useful, I just uploaded the Land Rover "EAS - System Information Document" I found on Nano forums, to the EAS sticky section in How-To's.
Pete
With the Nanocom plugged in the EAS is in diagnostic mode and does not go into fault mode.
1) I have nearly completed a schematic of the driver pack from the circuit board, but there is a long way to go before it's fully checked.
2) The driver circuit is stupidly complicated. there is only one electrolytic and one Tantalum all other capacitors are low value beads. the solenoid drivers are MOSFETS which are I suspect the cause of failures.
3) Height sensor inputs to the ECU should need no filtering, the signal would be cleaned up digitally. Additional filtering is unlikely to help even if it masked a developing fault in the short term.
Random rises are usually down to a failing driver pack IMO.
He has posted it as an answer to one of my EAS Stickys. Easily found if you know where to look. l can try and find the link and add it within the Sticky then you can if you need to tidy up delete the question. Up to you, leave as it is or i'll try and find and add to sticky let me know. Or give him a sticky of his own it is good info.
Last edited:
Er...erm....yeah, was about to say the same thing....:whoosh:
Leave electronicery to the electronicishians Ant. We can then concentrate on the important stuff.
:hysterically_laughi:hysterically_laughi :behindsofa:Leave electronicery to the electronicishians Ant. We can then concentrate on the important stuff.
Datatek
Well-Known Member
Leave electronicery to the electronicishians Ant. We can then concentrate on the important stuff.
ound:ound:
I think on that link I put up the guy spent ages looking at the electronics and in the end it was a dodgy wire. Some of the wires inside the EAS box are rather thin and probably a little brittle as it does get hot in there. In fact, I seem to remember some people cutting cooling holes and putting CPU fans in the side although I'm guessing that's just extending the life of a failing driver pack rather than a permanent fix.
tomcat59alan
Well-Known Member
And one even put Blue plastic eyelets around the holes, didn't you Rachel.:hysterically_laughi
They looked cute, only reason she didn't fit curtains was there was no room for the pole.
tomcat59alan
Well-Known Member
They looked cute, only reason she didn't fit curtains was there was no room for the pole.
Now you know I could answer that but it would probably get me banned
. Stop putting temptation in my way.
Some more EAS data for anyone that likes Excel. . . .(see attached). . .. and does seem to point toward dodgy Driver Pack.
Today on way home from work I connected Nanocom again, and started logging. About 12-14 mins into the journey the height switch started flashing high-mode again . . . so the random changes do occur with EAS in diagnostic mode
Reset the EAS while driving at 65mpg (yes I know - naughty) and the EAS returned to normal.
So looking through the log file, I found something interesting. (approx. lines 440-680)
Assuming one second per data set logged by Nanocom, this is about 12 minutes after I started logging, which is quite close to when it happened.
Another question: I'm wondering why the values for the Rear Left height sensor are significantly smoother that the other three ?
Pete
Today on way home from work I connected Nanocom again, and started logging. About 12-14 mins into the journey the height switch started flashing high-mode again . . . so the random changes do occur with EAS in diagnostic mode
Reset the EAS while driving at 65mpg (yes I know - naughty) and the EAS returned to normal.
So looking through the log file, I found something interesting. (approx. lines 440-680)
- Rear Right sensor showing 10% above target height.
- RR valve & Exhaust valves open . . .BUT height not dropping.
- Definitely sounds like Driver Pack failing to actually open one or both of the valves. . . .
Assuming one second per data set logged by Nanocom, this is about 12 minutes after I started logging, which is quite close to when it happened.
Another question: I'm wondering why the values for the Rear Left height sensor are significantly smoother that the other three ?
Pete
