Hello,
Please see
AN_176 - Vinculum Comparison of VDAP and V2DAP:
When a bulk endpoint is used for data mode, it will block when no data is received from the device. No further data will be sent to the device until data is received. Interrupt endpoints will send data only after data is received from the device but they will typically send data after each polling interval. FT232 devices will have data ready to receive after a configurable time interval, these will work the same as interrupt endpoints. Both bulk and interrupt endpoints are supported in command mode (DRD command).
This is due to the architecture of the V2DAP firmware. If the application required is primarily to perform tasks in data mode then it recommended that a simple application is used to transfer data between the devices rather than V2DAP firmware.
The source code for V2DAP is provided with the
Vinculum-II Tools which you can take a look at:
C:\Users\
Username\Documents\FTDI\Firmware\Samples\V2.0.2-SP2\VNC1L\V2DAP
These are very mature products and are no longer supported by R&D and have been superseded by FT9xx.
The best solution we have is to use the
FT90x MCUs.
We provide example code in
AN_360 FT900 Example Applications, but since we provide source code you can customise to meet your needs:
There are significant benefits of FT9xx:
-Eclipse based IDE
-Source code for API drivers is provided
-Significant performance improvement
-Actively in development by R&D
-Improved documentation and software examples
We provide
FT9xx Development Modules and a free
FT9xx Toolchain for custom application development.
Best Regards,
FTDI Community