Your browser does not allow scripts
Please click here to view a static table of contents without scripts
Buffered Writes
Return to Introduction  Previous page  Next page
In some cases, it is possible that the hardware developer does not have control over the application software. This can cause problems when migrating from RS232 to USB, as applications written for RS232 typically write bytes to the port one at a time and this will have a detremental effect on the USB performance. Due to the packetised nature of USB, it is far more efficient to transfer data in large chunks. This can be achieved by bufferring the data within the application.

If the developer does not have control over the application software to allow for buffering the data there, the FTDI driver provides an option to buffer the data fromo the application in the driver before sending the data out over USB to the device.

The Buffered Writes option is enabled through bit 10 of the first DWORD of the ConfigData entry
in the FTDIPORT.INF file. This is the same entry that contains the Baud rate table.

The first DWORD is shown in bold in the INF fragment below.


Please note that the ConfigData entry is byte-reversed, so MSB the DWORD reads
3F 3F 00 01 and the least significant bit is Bit 0. With Buffered Writes disabled, the DWORD would read 3F 3F 00 01. With Buffered Writes enabled, the DWORD would read 3F 3F 04 01.

In addition to enabling buffered writes in the Config Data entry, some parameters must be set up to control the behaviour. These parameters can also be set up in FTDIPORT.INF as follows:


These values are held in the registry under this key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\FTDIBUS\{Device VID, PID and serial number}\0000\Device Parameters  

These parameters are specific to the application. As such, they will require to be "tuned" to provide best performance.