A question about EASUnlock

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

woogoo

New Member
Posts
341
Location
Perth, Scotland
Hi all,

Can anyone tell me if this software will work on a laptop using a USB to Serial Converter cable with a correctly wired OBD II to Serial Cable?

--
Thanks,

Woogoo
 
Last edited:
Hi all,

Can anyone tell me if this software will work on a laptop using a USB to Serial Converter cable with a correctly wired ODBC to Serial Cable?

--
Thanks,

Woogoo

Cannot get mine to do so. But have not tried altering settings which may make it work. Works straight away on older laptop and serial port.
 
Hi all,

Can anyone tell me if this software will work on a laptop using a USB to Serial Converter cable with a correctly wired OBD II to Serial Cable?

--
Thanks,

Woogoo

I made my own cable per RSW's diagram and it works fine on my ancient Inspiron 2600 running XP with a USB/serial adaptor from Maplin.

If you are running Vista it's a different matter. Many USB/serial adaptors do not work with Vista. Someone on this forum got round that problem by purchasing a cardbus/RS232 adaptor:D
 
Hi,

Using a USB to Comm Port adapter would appear to work according to one of the videos I watched.

Having said that, when I run the EASUnlock software on my laptop (Windows XP) it won't initialise. The Comm port gets initialised but nothing, I don't get the FF sequence in the RX buffers I get a PP! Add to this the hardware the garage uses can't talk to it either!

Do anyone have any suggestions? I'm at my wits end with this, it's been in the garage for 3 weeks now and I miss it!

--
Woogoo
 
Have you changed the comm port? It usually works on comm port 4.
If the garage can't talk to it either it sounds like it could be the actual OBD connector, lots of people have reported corrosion problems to the wiring and the contacts.
Some USB/serial adaptors are worse then useless.
 
Have you changed the comm port? It usually works on comm port 4.
If the garage can't talk to it either it sounds like it could be the actual OBD connector, lots of people have reported corrosion problems to the wiring and the contacts.
Some USB/serial adaptors are worse then useless.

Hi, Yes as it's a virtual port I cycled though all available options, but none of them worked.

I, like you, am beginning to suspect the connector, as this is a common component between the garage's hardware and the PC of course. I was told earlier that the garage is downloading an update for their diagnostic unit, so I'm waiting until tomorrow see what happens.

I'll post an update when I know more.

--
Thanks

Woogoo
 
I don't even get THAT FAR!!!!... I downloaded EAS" softwear from RSW's tag on to my old Lappy (Running XP Pro)

& All I get when i try & run it is ...."The application failed to Initialize properly (Oxc0000135) click on OK to terminate the program"

I aint even got the bloody cables outta the bag yet!!!!!!!!!!!!!!!!!!!!!!!!!


Yet if I download it to my Desk PC (Running Win7) it works perfectly..... & NO!!! I aint carrying me DESK PC out to me car!!!
 
Last edited:
I don't even get THAT FAR!!!!... I downloaded EAS" softwear from RSW's tag on to my old Lappy (Running XP Pro)

& All I get when i try & run it is ...."The application failed to Initialize properly (Oxc0000135) click on OK to terminate the program"

I aint even got the bloody cables outta the bag yet!!!!!!!!!!!!!!!!!!!!!!!!!


Yet if I download it to my Desk PC (Running Win7) it works perfectly..... & NO!!! I aint carrying me DESK PC out to me car!!!

Hi, you may want to check that your laptop is up to date with it's service packs. The application may be in need of the Windows .NET Framework runtime libraries, so check you have these installed.

The best thing to do is use the Windows Update option from the Tools menu on IE, then select Custom, and you'll see more stuff in there.

--
HTH

Woogoo
 
I don't even get THAT FAR!!!!... I downloaded EAS" softwear from RSW's tag on to my old Lappy (Running XP Pro)

& All I get when i try & run it is ...."The application failed to Initialize properly (Oxc0000135) click on OK to terminate the program"

I aint even got the bloody cables outta the bag yet!!!!!!!!!!!!!!!!!!!!!!!!!


Yet if I download it to my Desk PC (Running Win7) it works perfectly..... & NO!!! I aint carrying me DESK PC out to me car!!!

Go look at the help section (FAQ's) on the RSW site. You need to download the Microsoft .net libraries.
 
Hi Gents,
If your laptop doesn't have a serial port the most reliable solution is to buy a serial port pcmia card for less than a tenner inc vat & P+P from ebest.com
some usb serial converters will only initialise with a piece of recognised kit on the end ie an ipod - unfortunately windows will not recognise a P38 rangie
 
I have recently purchased an EAS unlock cable (2nd hand) and loaded the latest RSW software. I've never actually had an EAS fault come up *gasp* since getting my 4.6 last year, but I thought I'd get the cable and s/ware 'just in case' . So I've just followed the instructions (using Vista and a usb convertor), the software runs fine with signals coimg through as expected. However afetr I plugged in the obdII and then the usb into the pc, the dash bleeped and the slow 35mph error appeared. Selecting the unlock EAS with the software does not seem to clear the message - I DIDN'T HAVE IT BEFORE :doh::doh::doh: I've not driven it yet, but I presume it will still be there on my next trip - any ideas why the message won't clear, am I doing something wrong?
 
I have recently purchased an EAS unlock cable (2nd hand) and loaded the latest RSW software. I've never actually had an EAS fault come up *gasp* since getting my 4.6 last year, but I thought I'd get the cable and s/ware 'just in case' . So I've just followed the instructions (using Vista and a usb convertor), the software runs fine with signals coimg through as expected. However afetr I plugged in the obdII and then the usb into the pc, the dash bleeped and the slow 35mph error appeared. Selecting the unlock EAS with the software does not seem to clear the message - I DIDN'T HAVE IT BEFORE :doh::doh::doh: I've not driven it yet, but I presume it will still be there on my next trip - any ideas why the message won't clear, am I doing something wrong?

Read the instructions, the slow 35mph message is normal when the computer is connected. It's Land rovers way of telling you that the computer is talking to the EAS:D
 
Read the instructions, the slow 35mph message is normal when the computer is connected. It's Land rovers way of telling you that the computer is talking to the EAS:D

Cheers Datatek, I could have sworn it was still there after disconnection, but have just been out and fired it up, no message :)
 
Can anyone tell me if this software will work on a laptop using a USB to Serial Converter cable with a correctly wired OBD II to Serial Cable?

Yes, when you buy a good quality USB to Serial converter, ideally with the Prolific Chip Set in it.

Mmmm, talking to myself, first sign of :crazy:

--
Me
 
I got a "Prolific" Usb to serial "Thingy" ...Absoute BAG-O-**** tried it on 4 PC's now .. STILL refuses to work... ( I "Filed it" yesterday, in the big round file under me desk!!!)

Hope I'm not telling you something you already know but...

I assume you ran the CD that came with it? You need to do this before you plug it in to your PC. If you're running XP open your device manager and you should see it listed under COM and LPT Ports.

If it's there use the port number assigned to it COM4, COM5 etc. If it's got a number larger than 9 I don't know if EASUnlock can talk to it correctly as you have to open these higher number ports in a different way.

If the gremlins haven't been and emptied the circular filing cabinet can I suggest that you get it back out, and try again. If you want send me a PM and I'll send you a zip of the drivers I have.

--
Woogoo
 

Attachments

  • comports.jpg
    comports.jpg
    9.4 KB · Views: 128
Back
Top