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

Pages: [1] 2 3 ... 10
 1 
 on: September 23, 2020, 04:41:01 PM 
Started by randomEngineer - Last Post by FTDI Community
Hello,

You are already in contact with our support team on this issue via email.
Please post any resolution here to help other customers

Best Regards,
FTDI Community

 2 
 on: September 23, 2020, 04:40:29 PM 
Started by unified - Last Post by FTDI Community
Hello,

Flow control is handled by the application program.

For example, with terminal programs like PuTTY or Tera Term there are settings available in the application that allow you to select the type of flow control. These typically use the VCP drivers.

If you wanted to use the D2XX drivers that would involve creating your own application program that would allow you to configure flow control. You can take a look at some software examples here:

https://www.ftdichip.com/Support/SoftwareExamples/CodeExamples.htm

TN_153 Instructions on Including the D2XX Driver in a Visual Studio Express 2013 Project is also useful.

There is no handshaking prior to configuration in software.

Best Regards,
FTDI Community

 3 
 on: September 23, 2020, 02:00:15 AM 
Started by unified - Last Post by unified
Sincere apologies - I must be missing something because there are a lot of posts on the topic of flow control.

The datasheet states "Control signals supported by UART mode include RTS, CTS. .... RTS/CTS and XON/ XOFFhandshaking options are also supported"

Where are these options selected?  I have gone through FT_Prog and can find nothing other than signal inversion settings.  The D2XX_Programmer's_Guide provides options to set flow control, but that would require a D2XX based program to configure them (or is that somehow managed by the VCP enumeration??)  If so then what is the power up condition of the chip - ie is there any handshaking prior to configuration? 

Thanks in advance,
Colin

 4 
 on: September 22, 2020, 03:56:28 PM 
Started by kalle - Last Post by FTDI Community
Hello,

We have a few products using the default FTDI vendor ID with our own PID (granted by FTDI some years back). Will our VID/PID combination also work in the upcoming .dext driver?

If your VID/PID combination is currently included in our macOS VCP driver's Info.plist file then yes it will be included in the .dext version of the driver.

Best Regards,
FTDI Community

 5 
 on: September 21, 2020, 02:44:40 PM 
Started by kalle - Last Post by James
Hi there, we are also looking forward to the .dext driver version.

We have a few products using the default FTDI vendor ID with our own PID (granted by FTDI some years back). Will our VID/PID combination also work in the upcoming .dext driver?

Thanks

 6 
 on: September 21, 2020, 12:22:04 PM 
Started by cioma - Last Post by cioma
Assuming FTDI is interested in selling more chips it would be great if they opened their FT60x protocol documentation (and the same for other chips too).
We know we can use FTDI drivers but many of us would like to write clean code in selected language using generic libraries (e.g. libusb).
Just a thought :)

 7 
 on: September 18, 2020, 06:17:36 PM 
Started by Magip - Last Post by FTDI Community
Hi,

Could you send us a screenshot of your config tool window please,

You can post here or you can send to support1@ftdichip.com if you would prefer and we'll check it out,

Best Regards, FTDI Community

 8 
 on: September 18, 2020, 02:17:42 PM 
Started by randomEngineer - Last Post by randomEngineer
Greetings everyone,

When using the Linux FTD3xx library (version 0.5.21) in Linux (Ubuntu 20.04 LTS), FT_GetDeviceDescriptor(ftHandle, &devDescriptor) returns a status of 4 (FT_IO_ERROR).  The function used to create the handle FT_Create(0, FT_OPEN_BY_INDEX, &ftHandle) returns 0 (FT_OK).  There is only one device detected by the devices (making the FT_Create unambiguous).  Despite returning an error, the function descriptor produces a vid and pid.  If the error is ignored, subsequent functions will also produce the same error.  The same code works in Windows. 

Here is the information about the device:

Device[0]
        Flags: 0x4 [USB 3] | Type: 600 | ID: 0x0403601E | ftHandle=0x53572e3b45534a2e
        SerialNumber=000000000001
        Description=FIFO Bridge (Windows)
        Description=FTDI SuperSpeed-FIFO Bridge (Linux)

Thank you

 9 
 on: September 18, 2020, 10:45:48 AM 
Started by kalle - Last Post by FTDI Community
Hello,

I see that your device is using the Product ID (PID): 0xEEEF with our default FTDI Vendor ID (VID): 0x0403.
This VID/PID combination is included in our VCP driver (FTDIUSBSerialDriver.kext), however it is not included in the inbuilt Apple VCP driver (AppleUSBTDI.dext).

Unfortunately at this time we do not have a .dext version driver available for macOS 11 Big Sur, but we hope to have this available shortly.

Best Regards,
FTDI Community

 10 
 on: September 15, 2020, 08:20:17 AM 
Started by Magip - Last Post by Magip
Hi,
  I would like to add:

  When I change color space from GREY to YUY2 using FT602 config tools, the tool reported the value is now YUY2.  However, when I use AMCAP to check properties of video stream, it report as GREY.  And it should actually be GREY because AMCAP continues to reject the stream.  I also used other players like VideoLan and DirectCap and they would not playback the stream if it is GREY.

Magip

Pages: [1] 2 3 ... 10