jacko12 · Jul 23, 2011

hi to you i have a 1996 p38 i have messages comming up on dash saying eas fault/airbag fault i have bought a eas kicker lite/allso got eas unlock software and cable read kicker instructions plugged in kicker blue light on /then nought spoke to bloke i bought it of he said unplug kicker start engine plug kicker back in this wakes ecu up so now got blue light on /then green light flashes unplug kicker turn engine off turn ignition to position 2 plug kicker back in blue light on /red light flashes 4 times cummuniction error =no reply in wake up ?? try this sevral times same result??? now when i plug eas unlock lead in i inizelize it starts 1234 then ff and runs and runs i also get pp i also get good idle but like i say the ff coluom just keeps on running can any one help me as im sure ive missed some thing ps ive run this on win 7/winvista both same result
jacko12

Datatek · Jul 23, 2011

jacko12 said:
hi to you i have a 1996 p38 i have messages comming up on dash saying eas fault/airbag fault i have bought a eas kicker lite/allso got eas unlock software and cable read kicker instructions plugged in kicker blue light on /then nought spoke to bloke i bought it of he said unplug kicker start engine plug kicker back in this wakes ecu up so now got blue light on /then green light flashes unplug kicker turn engine off turn ignition to position 2 plug kicker back in blue light on /red light flashes 4 times cummuniction error =no reply in wake up ?? try this sevral times same result??? now when i plug eas unlock lead in i inizelize it starts 1234 then ff and runs and runs i also get pp i also get good idle but like i say the ff coluom just keeps on running can any one help me as im sure ive missed some thing ps ive run this on win 7/winvista both same result
jacko12

If you get "Good Idle" it should be working, the columns keep running.

Start the EAS software with the cable plugged in, turn the ignition key to position 2, I generally start the engine buts it's not necessary, click on initialise and if you get "Good Idle" you have communication and can go to "read faults" note the faults and try "Unlock EAS" if the fault is intermittant it should clear but the faults you read will remain on the screen. Now stop the software and turn off the ignition. If there is still no fault the EAS will function when you turn the ignition back on until the fault reccurs

jacko12 · Jul 23, 2011

yea thanks for that but i think might of found problem o/s/f height sensor all three wires fried to geather so now going to locate sensor jacko12

wammers · Jul 23, 2011

jacko12 said:
yea thanks for that but i think might of found problem o/s/f height sensor all three wires fried to geather so now going to locate sensor jacko12

That may indeed be your problem. What a breath of fresh air, someone who actually takes the time to look for his own problems and sort them.

jacko12 · Jul 23, 2011

yea could not buy one today but ordered one from peter scott but iseperated the wires and used insulation tape poped it back and hey no more xmas lights now just got that srs light & abs light jacko12

mastarforth · Aug 13, 2011

HI again

Finally got back to wroking on the range rover.

I sorted the communication error with teh EAS software by a purchase of a new serial to USB adaptor and I managed to get communication working.

I have also fund that some where in the life the rear drivers ride height senosr has been replaced with a one for another model, so haev repalced that with a new one.

now I am still getting a fault message ot incorrect value from RR, as such can anyone tell me if there is an easy way to check the connector terminals in order that I can check the break is not in the line back to the ECU?

Any help woudl be appreciated.

kooky_guy · Aug 15, 2011

Incorrect value just means that the height values for that sensor are out of the allowed range. It may just be one of the values - I have a similar problem on one of my front sensors - I just have to keep tweaking them to get it to accept them. I suspect that sensor on mine is dodgy as the values required for a specific height are very different to the other.

I don't think it implies a dodgy connection. I assume you're following the usual height calibration procedure? Wammers has previously published the allowed ranges of values for each sensor.

Guy

mastarforth said:
HI again

Finally got back to wroking on the range rover.

I sorted the communication error with teh EAS software by a purchase of a new serial to USB adaptor and I managed to get communication working.

I have also fund that some where in the life the rear drivers ride height senosr has been replaced with a one for another model, so haev repalced that with a new one.

now I am still getting a fault message ot incorrect value from RR, as such can anyone tell me if there is an easy way to check the connector terminals in order that I can check the break is not in the line back to the ECU?

Any help woudl be appreciated.

jacko12

Member

Datatek

Well-Known Member

jacko12

Member

wammers

No longer with us, RIP

jacko12

Member

mastarforth

Member

kooky_guy

Well-Known Member

Similar threads