EAS Fault - Cable at fault?

Hello,

I've a 99 P38 RR diesel, never had a problem with the EAS until last week.

Driving along, the 35MPH message appeared and it lowered to the bump stops.


I bought a cable from eBay from a seller who's sold over 1000 cables with good feedback.

I've an old laptop with a SERIAL port, however it just displays a red 'no idle' and will not connect. Tx values of 1 & FF but Rx values 28, 80 and lots of random 3D 4D etc. Very occasionally it blinks green and I get a FF.

I've read and tried everything on the forums but still haven't been able to fix it. OBD connector looks clean, checked COM port settings, laptops running xp pro, fuses ok.


So i tried checking the pins on the cable. The only thing I found was pin 5 on the DB9 is connected to pin 4 & 5 on the OBD side. Although these both grounds from what I have read.


Any help would be [FONT=&quot]appreciated [/FONT]before I go insane.

Thanks

Should have bought a cable from me. There should be 3 other wires connected. Send the cable back and get a refund and buy mine, it's cheaper and you gewt RAVE and my airbag replacement guide.

Hello,

Thanks for the quick reply. What can I do with the existing cable? I'm abit stuck without transport.

91dm said:

Hello,

Thanks for the quick reply. What can I do with the existing cable? I'm abit stuck without transport.

Click to expand...

I'll post up the connections tomorrow if it will help.
From memory:-

D connector..............OBD
2 --------------------11
3 --------------------12
5 --------------------05 (& 4)
7 --------------------01

The top three are connected as the diagram, just OBD pin 4 & 5 going to DB9 pin 5.

91dm said:

The top three are connected as the diagram, just OBD pin 4 & 5 going to DB9 pin 5.

Click to expand...

So the cable is OK
You have a comms problem, could be corrosion in the OBD connector, even wires corroded off the back.

Ok thanks again Datatek.

I've used the laptop with other car software so I'm confident it's not that.

While I had the cable connected, I noticed the 4x lights would go off or just the ‘highest’ setting lit. Is that normal? When I disconnected the cable, the lights came back on and beeping starting again.

I’ll check the back of the OBD port tomorrow.

91dm said:

Ok thanks again Datatek.

I've used the laptop with other car software so I'm confident it's not that.

While I had the cable connected, I noticed the 4x lights would go off or just the ‘highest’ setting lit. Is that normal? When I disconnected the cable, the lights came back on and beeping starting again.

I’ll check the back of the OBD port tomorrow.

Click to expand...

I suppose you did have the ignition key in position 2?
When you connect to the OBD port, you should get a beep and the message "slow 35 mph" to indicate connection is established.
Just because your laptop works with other car software does not mean it will work with the EAS software, even for the serial port there are different drivers, some use Xon/Xoff protocol and others use RTS/CTS, the latter is required for the EAS software.

Yes ignition key in position 2.

I checked the OBD port this morning, no signs of corrosion and power at the brown wire. The rest of the wiring looks good, no signs of water damage etc.

I did read about the RTS 'ready to send' but couldn't see any option on my settings. It does have Xon/Xoff which I've tried with and without. So looks like I need to try a 3rd laptop. I've tried another with a PCMCIA adapter but just got 'PP' Rx values.

Thanks again.

91dm said:

Yes ignition key in position 2.

I checked the OBD port this morning, no signs of corrosion and power at the brown wire. The rest of the wiring looks good, no signs of water damage etc.

I did read about the RTS 'ready to send' but couldn't see any option on my settings. It does have Xon/Xoff which I've tried with and without. So looks like I need to try a 3rd laptop. I've tried another with a PCMCIA adapter but just got 'PP' Rx values.

Thanks again.

Click to expand...

The EAS software will not work with the Xon/Xoff protocol. It's unusual for the serial port to be locked on to Xon/Xoff.

Tried switching 'flow control' to hardware and none.

Still can't get a constant good idle. The first 4/5 responses are FF and then 28,0,E with no idle.

I can hear the delay relay clicking in when I connect/disconnect the lead and a beep.

91dm said:

Tried switching 'flow control' to hardware and none.

Still can't get a constant good idle. The first 4/5 responses are FF and then 28,0,E with no idle.

I can hear the delay relay clicking in when I connect/disconnect the lead and a beep.

Click to expand...

Hmmm, not sure about that, never heard the delay relay click on mine and I stand next to it when testing batches of cables. Not unknown for that relay to fail.

Yes the relay clicks on and off every time I connect/disconnect. Would a bad relay give 'PP' Rx values?

Tried various settings which all give the same 'no idle', Rx values 28 and a lot of 0's. Occasionally FF and good idle but only for one response.

Apart from another laptop, I can’t think of what else to try.

91dm said:

Yes the relay clicks on and off every time I connect/disconnect. Would a bad relay give 'PP' Rx values?

Tried various settings which all give the same 'no idle', Rx values 28 and a lot of 0's. Occasionally FF and good idle but only for one response.

Apart from another laptop, I can’t think of what else to try.

Click to expand...

The relay provides power to the ECU, looking at RAVE, I cannot see that it should switch on and off with the cable connected but I cannot be sure. Pin one of the OBD connector goes to the relay.
Not had to look into the timer relay in depth, but my understanding is that it switches on and off with the ignition. when the ignition is off, it powers the EAS up every 6 hours to perform a levelling cycle.
I'd be inclined to pull the relay and check the contacts, corrosion is not unknown.

That's what I've read which made me think it was unusual to be clicking every time. Does the relay power up the EAS ECU, could this be the reason for PP values if there was no Rx response?

I checked the relay visually when I was looking at the other wiring. All the contacts looked clean and nothing looked 'burnt'.

I'm abit lost at where to go next.

Is it normal for the eas fault message to come on and beep every tens seconds or should it just come on once?

Relay is not clicking when the ignition is switched on.

Thanks

Each time you send a command to the EAS ECU, from memory it beeps at you!

Heres my vid when I used Win7

https://www.youtube.com/watch?v=7g2NJc1BmhE

Hello.

Sorry should have said. This is without any cables connected.

Switch the ignition to position two, eas fault beep every ten seconds. Usually when say a bulb fault appears it just beeps once.

If there was a fault it should only beep once....not sure if the ECU receives more faults it will beep at you again for each one it finds though!

This is what's making me think it's in some cycle which is causing the connection problems.