P38A EASunlock

This site contains affiliate links for which LandyZone may be compensated if you make a purchase.
T

tomcat59alan

Well-Known Member
Posts
18,611
Location
wirral and triquivijate
Morning all survivors, as per title I have a problem with unlocking my eas , the Rx buffer is not responding been through the help page and tried numerous times to reboot without success . Looks like I've lost sync between my computer and the system.could be part of the system is not powering up, I've checked all fuses and the under bonnet relay. Any ideas welcome. Stay safe.
 

Attachments

  • 20200524_124054.jpg
    20200524_124054.jpg
    225 KB · Views: 106
  • 20200524_111525.jpg
    20200524_111525.jpg
    289 KB · Views: 69
Datatek said:
Morning Alan, no comms, so possibly the OBD connector corroded. Other possibilities are your computer, have you used the EAS software sucessfully before? Which version of windows are you using?
Click to expand...
Morning Keith,I'll check the obd , I've used the software before,its the download I found when the disc I had was corrupted, if you remember you kindly offered to send me another.I'm running Windows 10.I've another laptop and another disc but that's with @martyuk at the moment because it also has vehicle explorer on it. So far he said the Faultmate checks out and the problem could be the series to USB adapter.waiting for the new one to check out before returning everything. Take care.
 
Last edited:
tomcat59alan said:
Morning Keith,I'll check the bod, I've used the software before,its the download I found when the disc I had was corrupted, if you remember you kindly offered to send me another.I'm running Windows 10.I've another laptop and another disc but that's with @martyuk at the moment because it also has vehicle explorer on it. So far he said the Faultmate checks out and the problem could be the series to USB adapter.waiting for the new one to check out before returning everything. Take care.
Click to expand...
Have you used the EAS on Win 10 before? Is the USB to serial Win 10 compatible? My USB to serail adaptors would not work with Win 10, I had to buy a new one.
 
If it was previously working, I would suspect Windows 10 updates have over-written the USB Serial driver. Happens to lots of windows drivers, because Microsoft want their software to take over !! Re-Install the USB Serial driver, and try again.
 
There is something weird going on with USB to serial adapters at the moment - especially ones with the Prolific chipset.

A lot of them appear to be fake chinese clones of the chip - which apparently some vendors aren't aware of, and even if the driver installs properly, it won't actually work. I've been trying to get the one @tomcat59alan sent me with his faultmate to work, but Vehicle explorer won't recognise it. Then I looked in Device manager, and saw this:
ports.jpg


So whilst it shows it's installed the driver correctly, it doesn't actually allow communications through the chip. I've tried a load of older drivers, and can't get it to work - I even found a load of posts online about it and various drivers that are supposed to work.. Some show it installing correctly as a Prolific device, but show as an 'Error 10' - Device failed to start - which is also the driver detecting the chip isn't genuine and not allowing it to work.

Apparently it's also more of a pain in windows 10 (I'm using 7 on this laptop) as even if you DO manage to find an older version driver to roll back to, it will just auto-update as it does at some point, and install the latest driver, and then not work again.

In the case of the faultmate here - I'm purchasing what is supposed to be a genuine Prolific USB-Serial adapter, and will test that to make sure it installs properly and works with the faultmate - both on the laptop, where I can take it to my RR and check it with VE, and on my windows 10 desktop, before sending it back. In theory, then if he has a USB-Serial adapter that just works, and will continue to do so even if windows updates, then it could be used for other things like the EAS unlock system too.

Fingers crossed....
 
martyuk said:
There is something weird going on with USB to serial adapters at the moment - especially ones with the Prolific chipset.

A lot of them appear to be fake chinese clones of the chip - which apparently some vendors aren't aware of, and even if the driver installs properly, it won't actually work. I've been trying to get the one @tomcat59alan sent me with his faultmate to work, but Vehicle explorer won't recognise it. Then I looked in Device manager, and saw this:View attachment 210309

So whilst it shows it's installed the driver correctly, it doesn't actually allow communications through the chip. I've tried a load of older drivers, and can't get it to work - I even found a load of posts online about it and various drivers that are supposed to work.. Some show it installing correctly as a Prolific device, but show as an 'Error 10' - Device failed to start - which is also the driver detecting the chip isn't genuine and not allowing it to work.

Apparently it's also more of a pain in windows 10 (I'm using 7 on this laptop) as even if you DO manage to find an older version driver to roll back to, it will just auto-update as it does at some point, and install the latest driver, and then not work again.

In the case of the faultmate here - I'm purchasing what is supposed to be a genuine Prolific USB-Serial adapter, and will test that to make sure it installs properly and works with the faultmate - both on the laptop, where I can take it to my RR and check it with VE, and on my windows 10 desktop, before sending it back. In theory, then if he has a USB-Serial adapter that just works, and will continue to do so even if windows updates, then it could be used for other things like the EAS unlock system too.

Fingers crossed....
Click to expand...
Cheers Martin, I've responded to your pm, the lead for the eas unlock is a obd to USB lead and has worked for four years until yesterday, I'll check the back of the obd socket but, I never thought I'd say it, "it's too hot at the mo ".:cool: got the garden swing out so a cool cider and a book calls.:D
 
martyuk said:
There is something weird going on with USB to serial adapters at the moment - especially ones with the Prolific chipset.

A lot of them appear to be fake chinese clones of the chip - which apparently some vendors aren't aware of, and even if the driver installs properly, it won't actually work. I've been trying to get the one @tomcat59alan sent me with his faultmate to work, but Vehicle explorer won't recognise it. Then I looked in Device manager, and saw this:View attachment 210309

So whilst it shows it's installed the driver correctly, it doesn't actually allow communications through the chip. I've tried a load of older drivers, and can't get it to work - I even found a load of posts online about it and various drivers that are supposed to work.. Some show it installing correctly as a Prolific device, but show as an 'Error 10' - Device failed to start - which is also the driver detecting the chip isn't genuine and not allowing it to work.

Apparently it's also more of a pain in windows 10 (I'm using 7 on this laptop) as even if you DO manage to find an older version driver to roll back to, it will just auto-update as it does at some point, and install the latest driver, and then not work again.

In the case of the faultmate here - I'm purchasing what is supposed to be a genuine Prolific USB-Serial adapter, and will test that to make sure it installs properly and works with the faultmate - both on the laptop, where I can take it to my RR and check it with VE, and on my windows 10 desktop, before sending it back. In theory, then if he has a USB-Serial adapter that just works, and will continue to do so even if windows updates, then it could be used for other things like the EAS unlock system too.

Fingers crossed....
Click to expand...
The Prolific website now has a facility to verify your USB to serial adapter using their chips, that is how I found out that older Prolific chips are not compatible with Win 10.
 
tomcat59alan said:
Cheers Martin, I've responded to your pm, the lead for the eas unlock is a obd to USB lead and has worked for four years until yesterday, I'll check the back of the obd socket but, I never thought I'd say it, "it's too hot at the mo ".:cool: got the garden swing out so a cool cider and a book calls.:D
Click to expand...
If you used that cable on an earlier version of Windows, it could be incompatible with Win10.
 
martyuk said:
There is something weird going on with USB to serial adapters at the moment - especially ones with the Prolific chipset.

A lot of them appear to be fake chinese clones of the chip - which apparently some vendors aren't aware of, and even if the driver installs properly, it won't actually work. I've been trying to get the one @tomcat59alan sent me with his faultmate to work, but Vehicle explorer won't recognise it. Then I looked in Device manager, and saw this:View attachment 210309

So whilst it shows it's installed the driver correctly, it doesn't actually allow communications through the chip. I've tried a load of older drivers, and can't get it to work - I even found a load of posts online about it and various drivers that are supposed to work.. Some show it installing correctly as a Prolific device, but show as an 'Error 10' - Device failed to start - which is also the driver detecting the chip isn't genuine and not allowing it to work.

Apparently it's also more of a pain in windows 10 (I'm using 7 on this laptop) as even if you DO manage to find an older version driver to roll back to, it will just auto-update as it does at some point, and install the latest driver, and then not work again.

In the case of the faultmate here - I'm purchasing what is supposed to be a genuine Prolific USB-Serial adapter, and will test that to make sure it installs properly and works with the faultmate - both on the laptop, where I can take it to my RR and check it with VE, and on my windows 10 desktop, before sending it back. In theory, then if he has a USB-Serial adapter that just works, and will continue to do so even if windows updates, then it could be used for other things like the EAS unlock system too.

Fingers crossed....
Click to expand...

If you could find a driver that works, could you not rename it and then edit the registry to point at that new file? Maybe make a batch script and stick in shell:startup to update the registry so it always points at that file on logging in?
 
Grrrrrr said:
If you could find a driver that works, could you not rename it and then edit the registry to point at that new file? Maybe make a batch script and stick in shell:startup to update the registry so it always points at that file on logging in?
Click to expand...
Be easier to run it in a Win7 VM.
 
You must log in or register to reply here.

Similar threads

R
Oh dear, what have I done......?
2 3
Replies
47
Views
4K
Rallymantony
R
dinisrosa
Defender td5 10P - no air pressure
2
Replies
38
Views
3K
dinisrosa
dinisrosa
jbyarna
P38 EAS and EASUnlock ... HELP !
Replies
16
Views
4K
tomcat59alan
T
GRC50
P38 immobiliser problems again - maybe ?
2
Replies
34
Views
11K
GRC50
GRC50
The Mad Hat Man
Wiring in a split charge relay system
2
Replies
23
Views
80K
Rallymantony
R
Back
Top