Thread: Anyone running EAS Unlock Suite on a Classic?

Ages ago I made one up for a classic, the one thing was I had to wire in the little black cable that was in the plug - it wouldn't work without it (which is the opposite from what I read)

Originally Posted by fraser130

Ages ago I made one up for a classic, the one thing was I had to wire in the little black cable that was in the plug - it wouldn't work without it (which is the opposite from what I read)

Is this the wire to the plug-cap?

Not sure what you mean by comm port one on laptop and five on usb adaptor.
The comm port assigned to the USB adaptor must correspond to the Comm port on the EAS software. To keep things simple just assign comm port one to the USB adaptor and the default on the software should match.
Has the USB device loaded with the correct drivers, I think there is a thread in the P38 section about this. I know I had lots of problems with windows 7 getting mine to work until I found the correct driver.
Easy way out is to get an ancient laptop with a serial port then you have no issues. I have an old Panasonic Toughbook for when all else fails

Originally Posted by wayneg

Not sure what you mean by comm port one on laptop and five on usb adaptor.
The comm port assigned to the USB adaptor must correspond to the Comm port on the EAS software. To keep things simple just assign comm port one to the USB adaptor and the default on the software should match.
Has the USB device loaded with the correct drivers, I think there is a thread in the P38 section about this. I know I had lots of problems with windows 7 getting mine to work until I found the correct driver.
Easy way out is to get an ancient laptop with a serial port then you have no issues. I have an old Panasonic Toughbook for when all else fails

The address for the internal serial port is COM1 (Dell Precision M4300, far from ancient). The address for the USB serial adapter port is COM5.
The drivers and addressing aren't the problem as this same adapter works with other hardware.

Originally Posted by Dougal

Is this the wire to the plug-cap?

Yes,
I actually hard-wired the serial plug and components to the harness, and it would only work with the cap plugged in...go figure!
Fraser

Originally Posted by fraser130

Yes,
I actually hard-wired the serial plug and components to the harness, and it would only work with the cap plugged in...go figure!
Fraser

Brilliant, thanks.

I was pondering that today. Why am I going to the end of the earth to find a connector to match a plug that has just one purpose? When any four wire connector would do exactly the same job.

I have actually made a loom which connects my serial port to a standard kicker lead and contains the necessary transistor and resistor. I'll look at other options tomorrow.

So.

Fraser, you're dead right. The cap which joins pins 3 and 5 on the diagnostic connector is also an inhibit switch. Take it off and it all shuts down. No communication.
I stuck some pins in the back of the plug and connected a jumper across them, the EAS lights go out and it's active again.
Jumping across these two pins however prevents the transistor in the circuit from doing anything:


So now I have communication between the laptop and plug, but the RX doesn't match the TX.
It sends FF and gets back F7. It sends 1 and gets back 80. Consistently and repeatedly.

How can I trouble-shoot this? Will capping the communication speed in the device manager help?

Originally Posted by Dougal

So.

Fraser, you're dead right. The cap which joins pins 3 and 5 on the diagnostic connector is also an inhibit switch. Take it off and it all shuts down. No communication.
I stuck some pins in the back of the plug and connected a jumper across them, the EAS lights go out and it's active again.
Jumping across these two pins however prevents the transistor in the circuit from doing anything:


So now I have communication between the laptop and plug, but the RX doesn't match the TX.
It sends FF and gets back F7. It sends 1 and gets back 80. Consistently and repeatedly.

How can I trouble-shoot this? Will capping the communication speed in the device manager help?

You are close!
I'm sorry I can't help with anything other than suggesting baud rate not matching, and port settings I think 8-N-1, but can't remember the speed it should be. Sorry.

Fraser