LR-hobbs

Well-Known Member
Hello everyone I am trying to get eas unlock to work , I have the correct drivers and cable however when I try to initialize I just getting
PP in the Rx box and can't use any functions


Thanks
 

Attachments

  • 17540819041394975582744157756203.jpg
    17540819041394975582744157756203.jpg
    369.8 KB · Views: 14
Hello everyone I am trying to get eas unlock to work , I have the correct drivers and cable however when I try to initialize I just getting
PP in the Rx box and can't use any functions


Thanks
Generally that means bad comms. What version of Windows are you using? Are you sure that the driver being used is the correct one and not one chosen by Windows? If you are using a USB to serial adaptor, does it support the full RS232 controls? Some use the Xon Xoff protocol which does not work. Other possibilities are a duff timer relay and corrosion in the OBD connector.
 
Generally that means bad comms. What version of Windows are you using? Are you sure that the driver being used is the correct one and not one chosen by Windows? If you are using a USB to serial adaptor, does it support the full RS232 controls? Some use the Xon Xoff protocol which does not work. Other possibilities are a duff timer relay and corrosion in the OBD connector.
Laptop is brand new and I believe it's windows 10 , the cable I bought online and received it yesterday.
I did have issues changing the drivers and I'm not entirely sure I have done it correctly.

If there is corrosion in the obd port , how do I go about cleaning that off?
 
Generally that means bad comms. What version of Windows are you using? Are you sure that the driver being used is the correct one and not one chosen by Windows? If you are using a USB to serial adaptor, does it support the full RS232 controls? Some use the Xon Xoff protocol which does not work. Other possibilities are a duff timer relay and corrosion in the OBD connector.
I updated the driver using the hardware updater, and Installed FDTI. I do have the correct driver software on my desktop , I click set up go throught it and nothing happens
 

Attachments

  • 17541213926975610535345518571606.jpg
    17541213926975610535345518571606.jpg
    181.1 KB · Views: 4
Laptop is brand new and I believe it's windows 10 , the cable I bought online and received it yesterday.
I did have issues changing the drivers and I'm not entirely sure I have done it correctly.

If there is corrosion in the obd port , how do I go about cleaning that off?
If the laptop is brand new, it should be Windows 11. I'm not familiar with Win 11 but on Win 10 and earlier, if Windows has the option it will choose to use it's preferred driver which may not be the one needed.
The OBD port can be cleaned with contact cleaner such as Aeroclene 50 or Isopropyl alcohol. Any corrosion can stop communication, check the back of the connector as well as the front.
First step is clean the OBD connector.
 
Have you tried changing Comm ports? From memory I think EAS Unlock defaults to Comm 1 (Keith will know) I have to use Comm 4
Good point, may need to select Com 3, 4 or 5 from the drop down menu on the EAS screen. On one computer I use it's Com 3 on the other it's Com 5.
 
If the laptop is brand new, it should be Windows 11. I'm not familiar with Win 11 but on Win 10 and earlier, if Windows has the option it will choose to use it's preferred driver which may not be the one needed.
The OBD port can be cleaned with contact cleaner such as Aeroclene 50 or Isopropyl alcohol. Any corrosion can stop communication, check the back of the connector as well as the front.
First step is clean the OBD connector.
Cleaned the OBD2 port , there is some greening on the face of it and the entrance metal is also green.

Still getting the same fault. I have tried multiple ports on my laptop makes no difference. Not sure what else to try
 
With the serial cable plugged in, open Device Manager, and Delete the windows serial driver.

Then run the FTDI Installer. Do not use device manager to install it.

Then back in Device Manager / USB Serial / Properties check the cable manufacturer is actually FTDI.

1754127032650.png
 
With the serial cable plugged in, open Device Manager, and Delete the windows serial driver.

Then run the FTDI Installer. Do not use device manager to install it.

Then back in Device Manager / USB Serial / Properties check the cable manufacturer is actually FTDI.

View attachment 346668
I uninstalled the driver and the ports section completely disappeared. Restarted the computer and still gone.
 
Yes they will disappear when you delete the windows driver. . . .BUT windows usually reinstalles its own driver after reboot !!

Make sure you only remove the Serial driver, not the entire Ports tree. Do not reboot yet.

Run the FTDI installer EXE file, and it should find the cable - assuming it's actually an FTDI Chip version ? There are plenty of fakes out there.
 

Similar threads