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)

Didn't brick my pi. Works well with Solar Assistant and the EG4 3k inverters. I upgraded to 6k units but I still use the 3k units so I'm still using this cable. I tried using a noname single cable and my pi fried. These are pricey but worth the money

Purchased for my tech department employees to use with laptops. Works perfectly on Windows 10 and 7 also seems to work fine with CentOS and Redhat Linux. We work on a lot of EMC, NetApp, Cisco...equipment testing using serial ports and this is great and easy to stick in a laptop case. They can more easily multitask by running multiple serial connections to multiple systems using Putty or Hyperterminal, etc. I advise you determine what comport each serial connection "head" is assigned in device manager because it gets confusing. We mark each serial head with a number that corresponds to the com port assigned by OS. Once you install the drivers each "head" is assigned a comport that does not change.

Used this for a year as serial interface controls for my ham radios. all low-speed data. Ports started randomly dying -not detected at all. waste of money.

Works perfectly on a Dell Optiplex 960 SFF, running Linux kernel 3.2.0-4-amd64, acting as a terminal server for my Cisco lab environment. I am able to access the console ports of all four devices (2 Cisco switches and 2 Cisco routers) connected to this device.

There are times when I'm doing work on multiple headless Linux machines, because the session is killed when you disconnect from the serial port, I was having to do work on multiple node clusters one node at a time. Picked this up and now I'm able to work on four machines concurrently. Since the majority of the work is installing operating systems, screen isn't a viable solution. This product works well for that, or any other application where you need concurrent connections serially.

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

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.

I needed several serial connections to setup debug of instrument. This unit came with updated drivers that installed on my Win 7 pc easily. I have been building my intercept cable and was finally able to stage test. The four ports were easy to assign. Shipping and packaging was fine.