TECHTOO 4 Port Professional FTDI CHIP USB to Serial RS232 DB9 Adapter Converter Serial Cable 9-Pin Male to Male with Thumbscrews (W/Thumbscrews, 4 RS232 Port)

Works great. Prolific Driver disk provided helped to ease our setup. USB ports not labeled but can be identified using simple feedback/loopback connector. Would buy again.

Tech Support not rated as it was not needed. Arrived on time and was an easy plug and play install

When buying "generic" computer hardware like this I often wish someone would post some technical details so that I can make a better guess regarding whether or not it's going to work for me. I bought one of these for use on a RPi-based test fixture, and so far I have not run into problems. I did not need the driver disc at all -- just worked out of the box on Debian Linux (wheezy & stretch). `lsusb` outputs the following: Bus 003 Device 012: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 003 Device 011: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 003 Device 010: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 003 Device 009: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 003 Device 008: ID 1a40:0101 Terminus Technology Inc. Hub That is, it appears as a hub with with 4 FT232 converts connected. Here's the detailed output (lsusb -v -d 0403:6001): Bus 003 Device 012: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0403 Future Technology Devices International, Ltd idProduct 0x6001 FT232 USB-Serial (UART) IC bcdDevice 6.00 iManufacturer 1 FTDI iProduct 2 FT232R USB UART iSerial 3 AH05KCY0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 90mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 2 FT232R USB UART Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Device Status: 0x0000 (Bus Powered) When the device is connected, the following output appeared in /var/log/messages: kernel: [1328570.600195] usb 3-2: new high-speed USB device number 8 using xhci_hcd kernel: [1328570.740504] usb 3-2: New USB device found, idVendor=1a40, idProduct=0101 kernel: [1328570.740513] usb 3-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0 kernel: [1328570.740518] usb 3-2: Product: USB 2.0 Hub [MTT] kernel: [1328570.741191] hub 3-2:1.0: USB hub found kernel: [1328570.741226] hub 3-2:1.0: 4 ports detected kernel: [1328571.048076] usb 3-2.1: new full-speed USB device number 9 using xhci_hcd kernel: [1328571.154958] usb 3-2.1: New USB device found, idVendor=0403, idProduct=6001 kernel: [1328571.154967] usb 3-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kernel: [1328571.154972] usb 3-2.1: Product: FT232R USB UART kernel: [1328571.154976] usb 3-2.1: Manufacturer: FTDI kernel: [1328571.154979] usb 3-2.1: SerialNumber: AH05KEIJ kernel: [1328571.158204] ftdi_sio 3-2.1:1.0: FTDI USB Serial Device converter detected kernel: [1328571.158292] usb 3-2.1: Detected FT232RL kernel: [1328571.158742] usb 3-2.1: FTDI USB Serial Device converter now attached to ttyUSB0 kernel: [1328571.256087] usb 3-2.2: new full-speed USB device number 10 using xhci_hcd kernel: [1328571.362674] usb 3-2.2: New USB device found, idVendor=0403, idProduct=6001 kernel: [1328571.362684] usb 3-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kernel: [1328571.362688] usb 3-2.2: Product: FT232R USB UART kernel: [1328571.362692] usb 3-2.2: Manufacturer: FTDI kernel: [1328571.362696] usb 3-2.2: SerialNumber: A5062OYN kernel: [1328571.366032] ftdi_sio 3-2.2:1.0: FTDI USB Serial Device converter detected kernel: [1328571.366124] usb 3-2.2: Detected FT232RL kernel: [1328571.366558] usb 3-2.2: FTDI USB Serial Device converter now attached to ttyUSB1 kernel: [1328571.468091] usb 3-2.3: new full-speed USB device number 11 using xhci_hcd kernel: [1328571.594043] usb 3-2.3: New USB device found, idVendor=0403, idProduct=6001 kernel: [1328571.594046] usb 3-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kernel: [1328571.594047] usb 3-2.3: Product: FT232R USB UART kernel: [1328571.594048] usb 3-2.3: Manufacturer: FTDI kernel: [1328571.594048] usb 3-2.3: SerialNumber: AH05KDAK kernel: [1328571.596873] ftdi_sio 3-2.3:1.0: FTDI USB Serial Device converter detected kernel: [1328571.596890] usb 3-2.3: Detected FT232RL kernel: [1328571.597085] usb 3-2.3: FTDI USB Serial Device converter now attached to ttyUSB2 kernel: [1328571.696086] usb 3-2.4: new full-speed USB device number 12 using xhci_hcd kernel: [1328571.803239] usb 3-2.4: New USB device found, idVendor=0403, idProduct=6001 kernel: [1328571.803249] usb 3-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kernel: [1328571.803254] usb 3-2.4: Product: FT232R USB UART kernel: [1328571.803258] usb 3-2.4: Manufacturer: FTDI kernel: [1328571.803261] usb 3-2.4: SerialNumber: AH05KCY0 kernel: [1328571.806660] ftdi_sio 3-2.4:1.0: FTDI USB Serial Device converter detected kernel: [1328571.806745] usb 3-2.4: Detected FT232RL kernel: [1328571.807221] usb 3-2.4: FTDI USB Serial Device converter now attached to ttyUSB3

Could not get it to work on linux. Even after following the insane instructions that are dated

I have used this adapter cable on both Windows 7 and Windows 10 and it works fine under both systems. Windows picked up the device on both systems, I did not need to use the included CD to load the drivers. The build quality of the cable seems good and the plastic used for the connectors is solid. My only problem with this adapter is the COM port number change each time to attach the USB port to the PC. The serial plugs have little numbered labels on them, but those don't help since the COM port numbers seem to be assigned randomly to each connector. I don't find it a hard problem to work around. I just run puTTY on each port to see which ones are talking. This works fine for my purposes, but it would be nice if the COM ports were consistent.

Every other multi-port USB to serial cable I have bought has the port numbers on the serial connectors. This is important so I know what each port is connected to. And it died. It doesn't show up on USB any longer. I'm replacing this with an FTDI unit. I have NEVER had issues with FTDI and have used many FTDI devices over the past decade and more.

The product works well. However the driver has to be updated from a different un-named source. Also the driver is embedded within the OS X startup files, even when the USB device is not connected. It is unknown if future updates will be available? The other part to this scenario is one may have to get involved in changing some of the COM port addresses. This is due to Other installed software making use of COM ports and displaying a returned ERROR CODE COM port not found. Buyer be careful of you needs.

Driver doesn't load correctly giving an error in the device manager.

I needed to have remote access to few network devices for remote staging and configuration and plugged into a compact PC running a remote access software on it, I now have access to 4 of routers and switches that I needed to configure. I am sure if you have more than 4 devices to handle, multiple of this product can be plugged into USB ports and it then replaces a terminal server. I really like this and will probably order another one.

Excellent USB to 4 serial pory adapter. Drivers work great and support permanent COM assignment. So no matter which USB port you use, the COM number will always be the same. Only issue I had was that the numeric labels did not match the COM port numbers assigned by Windows 10.

Very stable, was able to console into a switch, firewall and two controllers at the same time, very useful!