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...

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...

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...

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...

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 ". got the garden swing out so a cool cider and a book calls.

Click to expand...

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...

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...

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...

Datatek said:

Buying a £10 compatible Prolific USB to serial adaptor sounds easier to me

Click to expand...

Datatek said:

If you used that cable on an earlier version of Windows, it could be incompatible with Win10.

Click to expand...

Datatek said:

Buying a £10 compatible Prolific USB to serial adaptor sounds easier to me

Click to expand...

Grrrrrr said:

Until the next time. Plus you have to wait.

Click to expand...

Datatek said:

And someone with no computer knowledge messing with the registry is a good idea?

Click to expand...

Datatek said:

And someone with no computer knowledge messing with the registry is a good idea?

Click to expand...

Grrrrrr said:

I reckon Marty knows a bit.

Click to expand...

Datatek said:

But Alan is the one with the problem and he says he does not.

Click to expand...