USB driver

[ESM]

If you've bought one of the USB ALDL interfaces you'll need to install a driver for it. My interface uses the same chip as the Moates interface so I'll hijack his instruction page <br>here.

[TC]

Down loaded drivers, unzipped etc but am having problems. The USB device is picked up and run through the wizard as told but the drivers are not found.<br><br>Any suggestions, I have tried several USB leads and computers.<br><br>Thanks<br>Tony

[ESM]

Doh, you're right. I've had to modify the inf file in the FTDI driver to get it to install, Active Robots changed the device id. Download this and follow the instructions on Moates.net http://www.astb91.dsl.pipex.com/VCP.zip

[TC]

Thanks Alan that seems to have loaded Ok now.

[Monty]

do i still need to use the instruction page on the 1st post with the last Driver link that Alan posted  ??? or is it a simple case of just installing the driver?

[ESM]

It depends what you think is simple I guess since you put it that way you probably won't need the instructions.

[Monty]

So i`ll take it that the New driver link will automaticaly set the Com port etc (as if i know what i`m talking about  :-/) I`ll see how it goes tomo`s when i try to set up  ;D

[mark]

alan, i downloaded the usb driver and followed the posted instructions.  am getting the message that no driver is found when i followed the wizard  instructions and pointed it to the VCP directory.  when i tried the manual installation, the message was that the driver didn't contain any information about my machine.  it seems as tho it is trying to install from the ftdibus set up file and not seeing the ftdibus.ini file.  any suggestoins?

[ESM]

Are you using the active robots circuit I mention on my web site? The driver has been modified to suit the device id of that particular board. If you're not try the drivers on the FTDI site here.

[John_W]

[quote author=Mark link=board=elanscan;num=1111389681;start=0#7 date=05/08/05 at 10:47:34] it seems as tho it is trying to install from the ftdibus set up file and not seeing the ftdibus.ini file.  any suggestoins?[/quote]<br>Mark,<br>Sorry, I'm just too late (internet connection problems). I was going to suggest EXACTLY the same as Alan, ::) but he just got his post in before me. Don't you just hate it when that happens?  ::) <br><br> [smiley=1poke.gif] [smiley=agree.gif] [smiley=azzangel.gif] [smiley=biggrinjester.gif] [smiley=bonk.gif] [smiley=chair.gif] [smiley=crazed.gif] [smiley=crazy3.gif] [smiley=dumbkopf.gif] [smiley=iamwithstupid.gif] <br><br>John <br><br>PS: what are you two on about?  ???  [smiley=werd.gif]<br>

[ESM]

He needs a VCP driver for his FTDI FT232BM (USB-TTL) that's got the right PCI device ID so he can use it for ALDL. Ok?  ::)

[John_W]

[quote author=ElanScanMan link=board=elanscan;num=1111389681;start=0#10 date=05/08/05 at 13:46:35]He needs a VCP driver for his FTDI FT232BM (USB-TTL) that's got the right PCI device ID so he can use it for ALDL. Ok?  ::)[/quote]<br>Well, if he'd just said that in the first place ...  ::)

[mark]

[quote author=John_W link=board=elanscan;num=1111389681;start=0#11 date=05/08/05 at 14:46:10]<br>Well, if he'd just said that in the first place ...  ::)[/quote]<br><br>thanks guys - i take it from alan's comments that the driver has to be specific to my serial converter.  so I'll try the driver from that company's website.<br>

[ESM]

Mark,<br><br>That's not usually the case, the standard FTDI ones are usually fine. The Active Robots board is the exception rather than the rule.

[dans]

Hi,

Having recently bought one of the Elan Scan USB interfaces, I'm having problems getting it installed.

On plugging it in Xp Pro just seems to recognise it as an unknown device and not want to install any drivers. If I select to upgrade the driver, then browse to the VCP directory I downloaded the drivers to, Windows just says that it cannot find better driver to use. If tell it i'll select the drivers myself, then goto the VCP directory then I can see 3 files:
FTDIBUS.INF
FTDIPORT.INF
FTSERMOU.INF

No matter which file I choose I just getting the following message:
"The specified location does not contain information about your hardware"

Any suggestions where I am going wrong???

And stupid question #1:
I don't actually need it plugged into the car to do this do I???!!!

Thanks for your help,
DAN

[TC]

Dan

Don't know if this will help but when I was installing the drivers, I had to disable all my network connections.

Tony

[dans]

Thanks for the advice TC but it didn't seem to have any effect on my problem... however I seem to have got round it now though....

I tried downloading some drivers direct from the FTDI site and found one that windows would use and install here

But I still had an error Code 10 (Could not start device).

But when I then updated the device with the driver provide by ESM here again and this time it worked and continued though to installing the port.

Best guess us that I may have been missing or had a corrupted a file which the other driver fixed.... or windows had got it knickers in a twist.....or i had been doing something wrong and acidentaly did something right!!!

All looks to be working now, just gonna wait for a bit of daylight to have a go in the car....

[Kjeld]

Received my USB to ALDL cable the other day and tried to install the driver. Came with the FTDI Chip CD which seemed to install fine. But when I ran Elanscan, the numbers seemed crazy. Went back to the site, thinking maybe the drivers were incorrect. Uninstalled, and tried installing the VPC, the Moates, and finally the CM 2.0, all from links under Elanscan. When I connected to the car again, I was never able to get Elanscan to "talk" again. Reinstalled off of the CD again, same result.

Now I am thinking it was probably working fine with the original install, but I misinterpretted the "Speed" graph I was seeing. (I hit 160 in my driveway, and reached that speed rather quickly).

I have tried to uninstall/reboot several times, but do not seem to be able to get a clean install again.

Rather frustrating.

[TStevens]

It's not in KM is it?

Not had any issues with the drivers ive been using.

[vi11ain]

I've (only - ) just got around to trying out my USB ALDL interface cable as supplied by Geoff.

As I had a couple of minor issues (my fault - nothing to do with the interface or ElanScan), I think it only kind to share my findings!

1) The driver which is available on the Mountain Chips site didn't work (I believe that it is intended for use only with the Active Robots circuit board).

2) Downloading the latest driver from the FDTI Chip website worked just fine (www.ftdichip.com/Drivers/VCP.htm)

3) Installing the interface and driver was a simple matter of unzipping the driver files from the download into a suitable location on the PC, plugging in the USB cable and telling Windows where to find the unzipped files. Screen shots of the process can be seen in the installation guides (found here: www.ftdichip.com/Documents/InstallGuides.htm)

4) Remember to set the "Latency Timer" setting to 1ms in the Advanced Settings for the USB Serial Port in Device Manager (I didn't, then started to get worried, until I remembered!)

5) ElanScan won't be able to communicate with the ECU if the ignition is off or (probably) the immobiliser is active.

6) I think that ElanScan won't pick up changes to the USB serial port settings unless you close it, then run it again.

Ben