1
Discussion - Drivers / Issue with FT260Q-T and LibFT260.dll when communicating in UART mode
« on: September 04, 2022, 03:12:56 PM »
Hi,
I am using the FT260Q-T on a new product design and am running into issues. We have designed the part into a custom circuit board and are using it for serial communications with a microcontroller via UART at 115200 baud. We are communicating with the FT260 over the USB link and are able to successfully transfer packets between our app on a Windows 10 computer and run packet traffic in both directions indefinitely without issues. However, if the successive return packets contains a changing variable, then we are getting exceptions from the LibFT260.dll and our app crashes. There seem to be certain combination of bytes that cause an issue with the DLL. When this occurs we need to disconnect and reconnect the USB (therefore resetting power on the FT260) before we are able to communicate with it again. On the circuit board, and oscilloscope shows well-formed packets in both directions, so we don't see issues on the UART side as far as signaling is concerned.
Have you seen anything like this fault? Can you think of why it may be occurring and only for certain combinations of bytes where otherwise it is 100% successful?
Thanks,
Aaron
-----------------
Aaron Needles
Embedded Systems Consultant
530-220-2547
aaron.needles@ymail.com
www.NeedlesInnovation.com
I am using the FT260Q-T on a new product design and am running into issues. We have designed the part into a custom circuit board and are using it for serial communications with a microcontroller via UART at 115200 baud. We are communicating with the FT260 over the USB link and are able to successfully transfer packets between our app on a Windows 10 computer and run packet traffic in both directions indefinitely without issues. However, if the successive return packets contains a changing variable, then we are getting exceptions from the LibFT260.dll and our app crashes. There seem to be certain combination of bytes that cause an issue with the DLL. When this occurs we need to disconnect and reconnect the USB (therefore resetting power on the FT260) before we are able to communicate with it again. On the circuit board, and oscilloscope shows well-formed packets in both directions, so we don't see issues on the UART side as far as signaling is concerned.
Have you seen anything like this fault? Can you think of why it may be occurring and only for certain combinations of bytes where otherwise it is 100% successful?
Thanks,
Aaron
-----------------
Aaron Needles
Embedded Systems Consultant
530-220-2547
aaron.needles@ymail.com
www.NeedlesInnovation.com