Copyright © 2010 Future Technology Devices International Limited 21
Document Reference No.: FT_000341
DS_UT232R-200(500) USB TO RS232 ADAPTER CABLE Data Sheet
Version 1.0
Clearance No.: 180
9 Troubleshooting
9.1 Hardware
Cables are the most common sources of trouble with external devices.
Check the following:
- USB cable is properly inserted
- Computer power is ON
- Computer is not in Sleep or Standby
- If a USB Hub is used, be sure it is set for “Self-Powered” operation
- If a USB Hub is used, be sure all cables are properly inserted
RS232 cables – check the following:
- Output signals (TXD, RTS, DTR) are connected to the respective inputs (RXD, CTS, DSR) in each
direction.
- Check for specific handshake requirements of your RS232 peripheral.
- If handshake signals are not used, ensure the application is set to “No Hardware Handshake”, or
equivalent.
- Test the port with a loop-back connector. Connect TXD to RXD, RTS to CTS and DTR to DSR. Use a
simple terminal program (e.g. HyperTerminal) to check that data is transmitted and received.
9.2 Device Driver
Ensure the latest device driver is in use. See www.ftdichip.com
If other devices with FTDI chips are installed in the system, check with all manufacturers of these devices
for the latest device drivers.
See the FTDI installation guides for additional details: http://ftdichip.com/Documents/InstallGuides.htm
Common Windows Device Driver Troubles:
DEVICE TIMES OUT: The default settings of the device driver assume typical data transfers of
hundred to thousands or more bytes at a given time. Some applications, such as a GPS device,
only send data in short packets, often only a few bytes. If this is the case, it may be necessary
to adjust the drivers buffer size and/or latency timer to smaller values. These values can be
adjusted through the Advanced driver options as noted in Figure 2.13. The buffer size can be
reduced to 64 bytes. The latency timer can be set as low as 2ms. A setting of 1ms will cause
unnecessary USB traffic and could adversely affect data transmission.
ERRATIC MOUSE POINTER: The device driver defaults to query an attached device to find out
whether it is a mouse or modem, consistent with native COM port operation. Some RS232
peripherals constantly send short packets of data, causing the host system to “think” a mouse or
modem has been attached. These short packets will interfere with normal mouse operation
causing the pointer to jump around the screen. If this happens, disconnect the RS232 device and
uncheck the Serial Enumerator option, also found on the Advanced driver options screen in Figure
2.13.
COM PORT IN USE: Windows keeps track of all COM port assignments. If multiple FTDI products
have been connected to a single system, the COM port number will increase, even if the other
devices are not attached. If the higher COM port assignments are not acceptable for the
application, known unused COM port numbers should be uninstalled according to the FTDI
installation guide: http://ftdichip.com/Documents/InstallGuides.htm.
