rufusw5

Member
I've tried this through a laptop on windows 7 with the USB convertor, I carried my PC out to the garage to use the serial port and tried it on an old P2 laptop with XP.. It will read fault codes but will not sync!

The fault codes are many, i need to reset them and see whats left as there's no apparent time stamp on them.

Anyone got any ideas as to why it won't sync with the EAS????

I get 58 about 3 times, then PP, then it alternates between 26 and 80

I've checked the cable, it's all good - havent had a proper look at the OBD connector yet, had to call it a night because i'm up early for work tomorrow...

HELP!!
 
What do you mean it won't sync? I assume you mean the RSW EAS Unlock Suite??Unless you get a green "Good idle" it's doing nothing, not reading actual faults or anything else. You can try adjusting the delay times. Corroded OBD connectors even to the extent that the wires have broken off at the back are not uncommon.
 
What do you mean it won't sync? I assume you mean the RSW EAS Unlock Suite??Unless you get a green "Good idle" it's doing nothing, not reading actual faults or anything else. You can try adjusting the delay times. Corroded OBD connectors even to the extent that the wires have broken off at the back are not uncommon.

Sorry... Yes that's what i mean, no green idle, won't connect.. I'm going to have another go at it, i'll have a look at the wires in the OBD connector but i can't see them being a problem, my fault code reader connects to the ECM ok....

I'll update in a couple of hours, i'll have a look at the plug and more of a fiddle with the laptop
 
windows 7 has difficulties running software especially software for cars (obd, LPG ect)

try and find a program called vmware and install a copy of windows XP

it will run everything you throw at it
 
I think i've found the problem.....

The wire for the #1 pin to the OBD connector was completely rotted off... Looks like i need some sort of repair kit, or some spare terminals...
 
I think i've found the problem.....

The wire for the #1 pin to the OBD connector was completely rotted off... Looks like i need some sort of repair kit, or some spare terminals...

Get an OBD connector from a P38 scrapper with 6 inches of wire on it and replace your connector Try Emmots of Colne, reputed to be very helpful:)
 
I HAD A simler problem once in end i found a computer with serial port and it synced up straight away without the usb adapter
 
Hi there, did the new socket solve your problem. i can't get my p38 to talk to my eas unlock. but i have continuity checked from after the obd2 to the 9 pin connection. i am using a usb adaptor though which i can't test.
 
Hi there, did the new socket solve your problem. i can't get my p38 to talk to my eas unlock. but i have continuity checked from after the obd2 to the 9 pin connection. i am using a usb adaptor though which i can't test.

Have you tried the different comms ports in the EAS suite? Some USB to serial adaptors use comm port 4 some 5 for example. Which version of Windows are you using? Vista can be a real barsteward with USB adaptors especially it seems the ones that use the Prolific chip, FTDI ones seem to fare better, either way you will need the correct driver, they are not Plug n Play:D
 
i am on comm port 2 currently. i have tried a few different comm's. I am on Vista. i may try my mums lap top tomorrow, hers id on win 7. its worth a bash i think. When i am connected it sends all the numbers but the replies are all 28 and 80's so it won't get a good idal. I really wanted to keep the air but i fear i may have to coil it!
 
I use a gas powered Dell with a serial port for my Easunlock. Works every time. It's the USB adaptor that gives the problems.
 
I think your right. if i don't install the adaptor for my lead it nearly connects. the idal flickers green but as soon as i install the driver i get bugger all. So i need to track down a steam powered lap top, or see if my parents old pc has the 9 pin jobby on the back.
 

Similar threads