windows 7 and the axe027 cable... help
- Thread starter D n T
- Start date
We are working on making the AXE027 FTDI drivers more friendly for Windows 7 by having them certified on Windows Update. However this does not occur overnight!
In the shortterm follow the instructions in this generic FTDI datasheet (section 3 CDM):
http://www.ftdichip.com/Documents/AppNotes/AN_119_FTDI_Drivers_Installation_Guide_for_Windows7.pdf
The 'other device' will say 'AXE027 PICAXE USB'. Basically the installation initially silently fails and then you manually correct it using Device Manger - right click, update driver and point to the folder that the XP/2000/Vista/7 drivers are in. Microsoft never make things easy....!
Note that the process occurs twice.
In the shortterm follow the instructions in this generic FTDI datasheet (section 3 CDM):
http://www.ftdichip.com/Documents/AppNotes/AN_119_FTDI_Drivers_Installation_Guide_for_Windows7.pdf
The 'other device' will say 'AXE027 PICAXE USB'. Basically the installation initially silently fails and then you manually correct it using Device Manger - right click, update driver and point to the folder that the XP/2000/Vista/7 drivers are in. Microsoft never make things easy....!
Note that the process occurs twice.
slimplynth
Senior Member
I've had no issues on Win7, though i did notice that the prolific cable can send a download quicker than the AXE027 but never tried both on vista or xp for speed.
To technical
Understood, no problems, bought a usb/serial adaptor, sorted.
I will wait, I understand these things take time, don't rush it, its better to get it right the first time ( quoted from a technical post I think). Microsoft rushed it and look what happened, vista then 7, as long as they don't bring out an 8 this year. Could you drop a note on the general forum when its ready to roll.
Understood, no problems, bought a usb/serial adaptor, sorted.
I will wait, I understand these things take time, don't rush it, its better to get it right the first time ( quoted from a technical post I think). Microsoft rushed it and look what happened, vista then 7, as long as they don't bring out an 8 this year. Could you drop a note on the general forum when its ready to roll.
FTDI site has driver version 2.06 says it's for windows 7 32/64 bit and is WHQL certified.
http://www.ftdichip.com/Drivers/CDM/CDM 2.06.00 WHQL Certified.zip
Not tried it yet.
http://www.ftdichip.com/Drivers/CDM/CDM 2.06.00 WHQL Certified.zip
Not tried it yet.
I couldn't get the reved supplied drivers to work with my new AXE027 and windows 7 64 bit.
These work though:
http://www.ftdichip.com/Drivers/CDM/CDM 2.06.00 WHQL Certified.zip
But only if you download and unzip my BD90 device type modified inf files over the top of the existing ones in the release.
You can grab them here:
http://www.bug-byte.co.uk/picaxe/206_BD90_inf.zip
Then insert the cable. It will fail to install any drivers. Start up device manager and right click on the device (with yellow exclamation mark) and select "update drivers". You need to do this once for the bus drive and once again for the port driver. Each time select the folder where you have put the drivers and new .inf files when prompted. Confirm you want to continue installing if it complains about the signing of the drivers.
When you have done it twice, then reboot.
It seems important not to have the adapter connected while you reboot. I guess windows might be thinking its a serial mouse and loading mice drivers on the port, but I didn't check this for sure. This avoids it telling you the COM port is in use, when it isn't.
This should work with XP and 32 bit windows 7 too, but I only tried windows 7-64.
These work though:
http://www.ftdichip.com/Drivers/CDM/CDM 2.06.00 WHQL Certified.zip
But only if you download and unzip my BD90 device type modified inf files over the top of the existing ones in the release.
You can grab them here:
http://www.bug-byte.co.uk/picaxe/206_BD90_inf.zip
Then insert the cable. It will fail to install any drivers. Start up device manager and right click on the device (with yellow exclamation mark) and select "update drivers". You need to do this once for the bus drive and once again for the port driver. Each time select the folder where you have put the drivers and new .inf files when prompted. Confirm you want to continue installing if it complains about the signing of the drivers.
When you have done it twice, then reboot.
It seems important not to have the adapter connected while you reboot. I guess windows might be thinking its a serial mouse and loading mice drivers on the port, but I didn't check this for sure. This avoids it telling you the COM port is in use, when it isn't.
This should work with XP and 32 bit windows 7 too, but I only tried windows 7-64.
Last edited: