gloves

New Member
PLease help shed some light, 1997 4.0 p38, fitted lpg to my rangie upon completion drove car out of garage and would not rise and then had the "slow 35 mph" message appear, made the lead according to storey's specs and downloaded the software, plugged in initiallised and bgan to read faults, but gavce the 255 msg in display and showed numerous faults which i beleive to be wrong according to the video bhy storey, when unlock eas is pressed and faults read again no faults found and all zero's in the display however all the ride height lights are still on eas fault is still displayed along with the extended height picture on the dash, can not get them to go out whatever i try, would appreciate some info/help.
many thanks .

gloves
 
did you initilize the software to the eas before reading faults,also did youmake sure the connector socket in the footwell is clean and free from corrosion
 
yes initialized the software all initialized ok all "ff's" in rx buffer didn't check for corrosion on socket will try that tommorow bit late now, but would have thought that if the software initialized and gave me value's back about the callibration settings and i could turn the compressor on and off and send the fault messages to the dash display that the connector would not be a problem, but will check it in the morning though to eliminate it. Many thanks andy 0352, would appreciate any other suggestions
 
you will be surprised all the pins on the connector do a different job,all it takes is one to be corroded and it stops diagnostics working properly,like you said check your connector tommorow,the best way is there should be three plastic screws in the black bottom panel,remove them and gently remove the panel,unplug the footwell light,the diagostic has to plastic lugs squeeze them together and gently remove the socket,this way you will see the pins better,give them a clean i used an old tooth brush,one of the pins has a 12volt output even if the ignition is off so go carefull,if need be get some wd40 or electrical spray,and spray the pins,then try your software.
let us know how you get on
 
sorry mate didnt have a chance today , will be doing it as soon as i get in from work tomorow, will let you know how i get on.
 
ok gave the pins a clean with a toothbrush and some wd40, reconnected the lead run the software initialized properly, when i read faults no matter what i do with the " 1 delay slider" i always get 255 255 255 255 255 in the boxes above the fauults panel and all faults displayed, i can run the pump, get the heights, write different height value's with the software i just can not get it to unlock or read and remove faults, strange thing though when i lock the eas i can press the go to standard height button and can hear a lot of clicking but it does not rise, also can not turn off the extended height indicator on the dash or in the speedo binacle, any help would be appreciated, many thanks.

gloves
 
try this disconnect the battery both terminals,run a jump lead from the neg cable onto the positive cable (not the battery terminals) leave the jump lead connected for about a minute,the will drain all the ecu capacators then reconnect the neg/pos leads back to the battery reste everything and see what happens.

make sure you you have your radio code and eka code,before you do this

let us know what happens
 
hi andy did'nt make any difference, still the same driving me nuts now lol, what i did bnotice was now when i ask for the ride height sensor readings it says they are all at therie heighest point which i know they cant be as the car is on the bump stops, dissconected everything , initialized again and still says they are at the top of their settings. any idea's mate ?
 
downloaded story's software off his site rsw solutions, did'nt go anywhere near wiring for suspension when fitting lpg kit all i done was jack the rear ns up but the wheel never left the ground , thanks for the web site will check it out.

gloves
 
checked out the site but to no avail, just can not understand why i can do some of the communications with the software but not others, will have to perservere and keep trying i think. Any other idea's ? andy many many thanks for your help and patience mate.
 
the only other thing i can think of is to check the wires at the ecu end,which is under the passenger side seat,just in case at some point of it,s life it has got wet,maybe the connectors has corrosion,or maybe it has come loose,failing that maybe try someone who has an eas kicker or rovacom,i,ll admit im starting to run out of ideas now mate,but keep us informed
 
will do mate , the only other thing i can think of after scouting about the net and reading up loads of info is that maybe the usb 2 serial i am using is the culprit, going to see if i can dig out my old laptop with a dedicated serial port on it and try that way, will keep you informed and let you know how i get on, once again andy many thanks for your time experiance and patience mate.

gloves
 
now that you mention,i had that problem with my rovacom,using a usb to serial,now i have a laptop with a dedicated serial socket it works fine,so it could be that mate,i would definatly try it out.
 
tried it with a dedicated serial port on laptop but still the same, dont understand it will send some communications but not all, or will do some things but not all, maybe someone else may have had the same problem and shed some light on it, might see if i can get another ecu and see what happens, many thanks andy.
 
Sorry I was not following this thread. I have tons of emails everyday and little time to spend on the forums.

First Question always is; What are you getting back in the Rx buffer. Until you get only FF during communications idle, then none of the operations with the EASunlock software will work.

If you get FF and 1 in the Rx buffer, you are on the wrong comm port. (You are on a internal laptop loopback port)

If you get nothing back in the Rx buffer during communications idle, then your USB 2 Serial adapter is not working or your cable is wrong, or the Range Rover wiring is suspect. (No communications at all; Tx and Rx are bad)

If you get 28 or 80 back in the Rx buffer then your USB 2 Serial adapter might stil be acting up, or your cable might be incorrect, or the Range Rover wiring might be suspect or the EAS delay relay might be suspect. (Some communications; Tx and Rx are working; EAS power reset is not working)

Overall, make sure you have drivers installed for the USB 2 Serial adapter. Make sure you have the windows device manager open when you plug the USB to serial adapter in. Watch the new comm port appear in the windows device manager. When the comm port appears use that inside the EASunlock software configuration for the comm port number. You can also shift the comm port number that the USB 2 serial adapter emulates. Changing the enulated serial port can sometimes also cause the adapter to suddenly start working.

Make sure the cable is correct. I think the cable is the most likely cause of the lack of communications. You have tried a laptop with a built in RS232 so that is uaually a good working test. But that failed. I think your cable is bad and then next I would inspect the OBDII port wiring harness by droping the footwell pannel. Then I would inspect the EAS ECU C117 Wiring harness for damage.

eas_serial_cable_schematic.jpg


Wiring harnesses in the Range Rover can go bad. I usually ask if the heater core has ever leaked. If you have had a coolant leak in the heater core, then the OBDII port and some of the wiring harnesses that are next to the heater core are suspect. But check the OBDII port first it is easy to get to and can be cleaned with some contact cleaner.

Next I inspect the EAS ECU. The EAS ECU is located under the Left hand seat. Some pannels will need to be removed and you will also need a medium sized phillips screwdriver with a very very short handle. The EAS ECU is located on the bottom. Use a flat head screw driver to pop the EAS C117 multiplug connector off. Inspect the wiring harness and the C117 pins. If the connector has ever been opened, make sure that the plastic retaining combs are still on either side of the C117 connector. The plastic retaining combs keep the pins in contact with the EAS pins. Some souorces also say that the rubber gasket on the C117 connector is too thick and prevents the connector from seating correctly with the EAS computer. So try removing the rubber gasket for testing. Long term, you can remove about 1/3 of the thickness of the gasket with sand paper and refit.

Also inspect the EAS delay relay. The EAS delay relay is located under the left hand seat on the outer side of the seat. It is a black tall rectangular relay, which has its own wire harness and is attached to the seat subframe with a rubber groumet. Make sure that the wires are in good shape. The EAS is power cycled during the EAS communications protocol. If you can not hear or feel the EAS delay relay clicking when you press "initialize", then it might be bad. Try replacing it.

Can anyone sticky this thread answer? I do not want to type it all again. :)
 
Last edited:
Many thanks for your quick reply, in the rx buffer i get all "ff", have tried with the serial usb and a laptop with dedicated 232 port both the same, i can turn the pump on and off i can get all the readings from the calibration part of the software, i can get the heights of the sensors and when i ask the sensor to raise by pressing the button on the software i can hear the solenoid click but it does not rise, i have depresureized the air bags and the tank, i have left the pump running for 10mins on 2 occasiuons, i can blank the display message's, but the lights stay on solid on the height switch when unlock eas is pressed, when lock eas is pressed the lights flash and also the extended height picture on the dashboard is lit up and can not turn that off either, again many thanks for your quick reply storey.
 

Similar threads