Originally Posted by Forchetto
Did Windows select and load a suitable driver for the cable?.
Did you have to load NET framework?.
If so this is a good thing because until now we've had to ignore whatever drivers come with the cables and those selected by Windows, and install the FTDI driver suggested in the TuneECU instructions as well as installing a particular version (v2.0 I think) of Windows NETframework.
Hi Forchetto, I didn't have to do anything with the NET framework, it appears it's enabled by default, here's a shot from the "programs features" section of control panel.
I had been using the driver from the adapter cable providers site, http://www.lonelec.com/TuneECU_Lead.html
. And though it did work ok, it was an older version than the one provided by the link in the TuneECU site to here, http://www.ftdichip.com/Drivers/VCP.htm
The latest version is 18.104.22.168 . I have it loaded up and it works with no issues.
Some screen shots, Net Framework enabled, FTDI driver, note that you will find it as COM3 in device manager, TuneECU connected to driver check Options/Interface/USB and you should see FT232R USB UART, if you don't you have a problem with your driver install.