Can't use FTDI driver

For discussion of Phil Tobin's Tuner Studio software (Only about the tuning software itself, not about how to tune or firmware features)

Moderator: LT401Vette

Post Reply
racingmini_mtl
Super MS/Extra'er
Posts: 9128
Joined: Sun May 02, 2004 6:51 am
Location: Quebec, Canada
Contact:

Can't use FTDI driver

Post by racingmini_mtl »

I have a problem that started a few days ago: I can no longer use the FTDI D2XX driver. I get the error below when I try to start a project with a serial connection that uses the FTDI driver. I also cannot create a new project that uses the FTDI driver.
TS error message when opening project
TS error message when opening project
ftdi_driver_error.png (9.03 KiB) Viewed 2124 times
I'm not sure if this is when it started but I have a new device that uses the recent FTDI chip (FT230X instead of the older FT232R) and Windows updated its drivers when I connected it. I then have tried updating TS, going back to the previous version, deleting the TS folder then re-installing it from the web site file. I also tried to update the FTDI D2XX drivers using the install file from the FTDI web site. None of these things made any difference. I have also done a comm debug log but there is no more information than the error above. And the problems are happening with an adapter that uses the old FTDI chip so it's not limited to the new chip.

I can use the FTDI adapters as COM ports (so the VCP driver works) but it seems that the D2XX driver does not work for some reason. This has always worked in the past. I'm running Win7 and TS beta v3.0.50.23 and v3.0.50.40.

Jean
jbperf.com Main site . . . . . . . . . . . . . . . . . . . . . . jbperf.com Forum
Image
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Can't use FTDI driver

Post by LT401Vette »

How did you update the D2XX drivers?

TS has those built in and will use it's own.

I think you are on to something with the updated FTDI drivers you have installed on the PC, maybe there is a new compatibility issue between versions?
On Linux and OS X you can't use D2XX is there is a VCP driver installed as the VCP Driver locks to the hardware on boot. The windows VCP driver plays nice with D2XX, but perhaps not with this new version driver?
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
racingmini_mtl
Super MS/Extra'er
Posts: 9128
Joined: Sun May 02, 2004 6:51 am
Location: Quebec, Canada
Contact:

Re: Can't use FTDI driver

Post by racingmini_mtl »

LT401Vette wrote:How did you update the D2XX drivers?
I simply ran the exe file from FTDI (CDM21228_Setup.exe). I thought TS was using its own but I was trying to eliminate potential issues.

I assume that if this an issue with the latest FTDI VCP driver, you'll be able to replicate it on your end. In the meantime, is there a workaround for my old projects? I can't even go in the comms menu to change it because TS stop responding when the D2XX option is chosen so I can't go back to using a COM port.

Jean
jbperf.com Main site . . . . . . . . . . . . . . . . . . . . . . jbperf.com Forum
Image
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Can't use FTDI driver

Post by LT401Vette »

That is a bad reaction..

I will look at putting protection against that in the beta.

In the mean time, you can edit the project.properties file in the projectCfg folder. Delete any line with this string:
"controllerInterfaceId=FTDI - D2XX driver"
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
racingmini_mtl
Super MS/Extra'er
Posts: 9128
Joined: Sun May 02, 2004 6:51 am
Location: Quebec, Canada
Contact:

Re: Can't use FTDI driver

Post by racingmini_mtl »

Have you been able to reproduce this and confirm if it is related to the new FTDI driver? Or is this something unique to my system? The workaround works but it would be nice to be able to use both the VCP and D2XX drivers.

Jean
jbperf.com Main site . . . . . . . . . . . . . . . . . . . . . . jbperf.com Forum
Image
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Can't use FTDI driver

Post by LT401Vette »

Any idea what version VCP driver is on your PC now?

Going to the FTDI VCP Driver site:
http://www.ftdichip.com/ftdichip/Drivers/VCP.htm

The latest driver they have there is 2.0.8.23 from 2011 ?

On my own PC windows has 2.12.24 from 9/28/2016, so apparently there are newer drivers released via different channels.
Perhaps it is only if you use the new chip it updates to a newer driver?

I really can't say for sure if it is specific to your system. I haven't had anyone else report a problems though.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Can't use FTDI driver

Post by LT401Vette »

I just told Windows to specifically update the FTDI driver, it did update it to 2.12.28 from 8/16/2017.

D2XX still seems fine though.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
racingmini_mtl
Super MS/Extra'er
Posts: 9128
Joined: Sun May 02, 2004 6:51 am
Location: Quebec, Canada
Contact:

Re: Can't use FTDI driver

Post by racingmini_mtl »

I've got the same VCP driver you got from the Windows update (2.12.28). And this is on Win7 Pro. And to be clear, the problem is not only happening with the device with the new chip but with older devices that always worked.

Any idea what I can try to pinpoint the cause?

Thanks,
Jean
jbperf.com Main site . . . . . . . . . . . . . . . . . . . . . . jbperf.com Forum
Image
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Can't use FTDI driver

Post by LT401Vette »

racingmini_mtl wrote:I've got the same VCP driver you got from the Windows update (2.12.28). And this is on Win7 Pro. And to be clear, the problem is not only happening with the device with the new chip but with older devices that always worked.

Any idea what I can try to pinpoint the cause?

Thanks,
Jean
Interesting. I give it a shot on a windows 7 machine I have here.
I'm still thinking someone else would have run into this if there was a true driver conflict. Unless the new ship you are using is actually using a different driver that is conflicting with D2XX and this chip is not used very broadly yet.

Conflicts between VCP and D2XX are not a new issue. On Linux and OS X you can only use one or the other. If you have a VCP driver in on boot, it will lock the port and D2XX can not use it. Early on Windows did this too, but FTDI made the windows driver play nice. OS X and Linux still no go.
Is it possible the new chip is using a driver that doesn't support switching to D2XX yet?

Have you tried removing the VCP driver, cleaning it and installing an older version?
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
racingmini_mtl
Super MS/Extra'er
Posts: 9128
Joined: Sun May 02, 2004 6:51 am
Location: Quebec, Canada
Contact:

Re: Can't use FTDI driver

Post by racingmini_mtl »

The chip is the FT230X and it's been available for years now but it is more recent than the classic FT232R and it is smaller and cheaper. And the specs do say that you can use VCP and D2XX. I'll see if I can go back to a previous VCP version. I'll also try to see what happens on a cheap Win10 tablet I got lying around (somewhere...).

By the way, is the error message "Error: failed to load Comms Driver: 9" what you'd expect to see if this is indeed the same thing you see on Linux and OS X?

And if you ever want to test this yourself, there are cheap breakout boards with this chip available. But they are for a 3.3V UART so you wouldn't be able to connect them to an MS. However, it may not even be necessary to connect anything on the serial side because I do see the error even if I'm not using the FT230X.

One more point: is it possible that the D2XX version you use in TS needs to be updated?

Jean
jbperf.com Main site . . . . . . . . . . . . . . . . . . . . . . jbperf.com Forum
Image
LT401Vette
Super MS/Extra'er
Posts: 12697
Joined: Sat Jul 16, 2005 8:07 am
Location: Moorseville, NC
Contact:

Re: Can't use FTDI driver

Post by LT401Vette »

By the way, is the error message "Error: failed to load Comms Driver: 9" what you'd expect to see if this is indeed the same thing you see on Linux and OS X?
No.. that sounds more like it is failing to load the native driver. It should load the D2XX driver fine, but not find the port as it is already locked by the VCP Driver.
One more point: is it possible that the D2XX version you use in TS needs to be updated?
It is possible, it has been a few years since I have.
Phil Tobin
EFI Analytics, helping to simplify EFI
Next Generation tuning software.
Supporting all MegaSquirt versions and firmwares.
http://www.TunerStudio.com
http://www.efiAnalytics.com/MegaLogViewer/
Support the firmware running your engine:
http://www.msextra.com/doc/donations.html
petski3
Experienced MS/Extra'er
Posts: 167
Joined: Thu Jan 21, 2016 2:10 am
Location: Finland
Contact:

Re: Can't use FTDI driver

Post by petski3 »

Bumping up this. I am having the exact problem. Computer is freshly installed with windows 10 64bit.
I have a MS3 ecu on my bench, and if it is the only FTDI based usb device that is connected to the computer, everything works as it should.
But if I connect another device to the computer that uses the FT230XS-R chip, TS will report "Failed to load comms driver: 9". This error is shown when I try to open the MS3 TS project.
If I unplug the ft230xs-r usb cable, and restart TS, it will work correctly.

If I open the MS3 project in TS without the 230xs-r usb device connected to the computer, and then after the project has synched i connect the ft230xs-r cable to the computer -> TS will disconnect if i try to open the Communications->Settings dialog. Also the settings dialog wont open if the 230xs-r cable is connected. As soon as i disconnect the 230xs-r and click on the "Communications->Settings" it will open. No ts restart needed.

Petteri
https://www.dbwx2.com/ - Dual DBW Controller
jsmcortina
Site Admin
Posts: 39585
Joined: Mon May 03, 2004 1:34 am
Location: Birmingham, UK
Contact:

Re: Can't use FTDI driver

Post by jsmcortina »

As a workaround maybe just use the regular RS232 driver?

James
I can repair or upgrade Megasquirts in UK. http://www.jamesmurrayengineering.co.uk

My Success story: http://www.msextra.com/forums/viewtopic ... 04&t=34277
MSEXTRA documentation at: http://www.msextra.com/doc/index.html
New users, please read the "Forum Help Page".
IdellSeitz
MS/Extra Newbie
Posts: 1
Joined: Tue Sep 01, 2020 8:37 am

Re: Can't use FTDI driver

Post by IdellSeitz »

Hello.....What is in the Device Manager? Try to go to see - > show shrouded gadgets and check whether there is anything usb/com related that has the shout point/triangle.
As a source of perspective point, when working appropriately, you should see USB Serial Port (COM[x]) under Ports (COM and LPT)

Check whether anything changes within the Device Manager.

At the point when this transpired, it was the link surprisingly. The prop retractable links appear to destroy rashly. I'm certain you've attempted various ports, and different gadgets on that equivalent usb port, so it clearly isn't the port. Regardless of whether the driver is hosed however, it ought to perceive the device under different devices within the Device Manager.

https://www.7pcb.com
Post Reply