FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support


New Bridgetek Community is now open

Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.

Please follow this link and create a new user account to get started.

Bridgetek Community

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Messages - jupiterman

Pages: [1]
1
Discussion - Drivers / Problems with FT2232H VCP on Windows 10
« on: May 07, 2020, 07:03:04 PM »
Hello,
I have built a dual-channel serial-to-CAN bus bridge using the FT2232H chip.  Each serial port is connected to an independent CPU that bridges the serial stream into packets on the CAN bus using a protocol I wrote 12 years ago. Hardware handshaking is used to regulate the data flow in both directions.  I have the device working quite nicely and have written a test program that sends CAN messages on each channel at a high rate and have connected the two CAN ports together.  This program runs without issue on Windows CE 6 and 7 using the VCP drivers supplied by FTDI.  I have pumped nearly 700 million CAN messages through it in the last week or so without error.

The very *same* program behaves much differently when run from my Windows 10 host.  I've installed the latest VCP driver for Windows hosts from FTDI.  My program opens the ports successfully and appears to communicate with the chips on my board, however,  message data transmitted from the host to the FT2232 chip is delayed quite heavily (i.e seconds) *unless* there is a steady stream of data being sent from the chip to the host.  I have discovered that by sending a regular message from a CAN bus analyzer tapped into the line produces such steady input that kicks the drivers into gear, and at that point I get similar behavior as on Windows CE.

So I am curious if anyone knows why this might be occurring on Windows and what changes to the VCP driver configuration settings may remedy this.  I'd like to make the test program have reasonable performance running on a Windows system.

Thanks in advance.



Pages: [1]