EAS issues.

It's a bit bad though when a premium product can't get in, but a piece of freeware can??

andyr said:

It's a bit bad though when a premium product can't get in, but a piece of freeware can??

Click to expand...

The RSW software didn't actually make a good comms connection, it may just be that it was luck that for the milli second it was trying to connect you got an "Unlock" command through. Nanocom is more exacting in terms of establishing good comms.

Datatek said:

The RSW software didn't actually make a good comms connection, it may just be that it was luck that for the milli second it was trying to connect you got an "Unlock" command through. Nanocom is more exacting in terms of establishing good comms.

Click to expand...

Understood. And could of been because of my twisted wire and paperclip bodgery.
When the bits come in I'll make a proper connector..

But as the EAS has actually always worked ok, the comms issue must lie between the OBD plug and the EAS ECU, or am I being too simplistic?

andyr said:

Understood. And could of been because of my twisted wire and paperclip bodgery.
When the bits come in I'll make a proper connector..

But as the EAS has actually always worked ok, the comms issue must lie between the OBD plug and the EAS ECU, or am I being too simplistic?

Click to expand...

Yes the comms problem may be between the OBD connector and the EAS ECU could also be the EAS relay. The OBD connector or the white connectors at the base of the A post are the usual problem.

Just to close this thread, the bits came to make a proper lead up and now Mr Wilson's software is fully functional, so it was my bodgery that gave the bad comms.

My Nanocom still can't get in to the EAS, and when I mentioned on the BBS forum that I'd used RSW software to gain access, I didn't get a reply.

andyr said:

Just to close this thread, the bits came to make a proper lead up and now Mr Wilson's software is fully functional, so it was my bodgery that gave the bad comms.

My Nanocom still can't get in to the EAS, and when I mentioned on the BBS forum that I'd used RSW software to gain access, I didn't get a reply.

Click to expand...

Good result. I have a Faultmate but I use the RSW software for the EAS.

If you look again at the diagram I uploaded on post-8, you can see there are three wires for EAS diagnostic. As you now have RSW software working, then the timer-Relay trigger and comms must be working for this. This indicates that all three wires from the Diagnostic connector are probably ok.

Consequently it would appear your Nanocom cable or device have a fault. (Most likely the cable) First check if you get the Beeps & 35mph message when entering any of the EAS menus.

• If yes, then the wire from OBD pin-1 to the timer is working.so the problem must be the data lines between Nanocom & ECU.
• If there's no beeps & 35mph message, then the timer relay trigger is bad, so communication will never start !!

In either case ask BBS for the cable pinout & test it. I assume you have the green connector version ?