Gearmo 2-Port USB to Serial Adapter TX/RX LED & COM Retention FTDI Chipset 920K Baud Rate

I work on tech and it requires a console connection to do the basic setup/troubleshooting. This sucker did a fantastic job and allows me to connect to multiple systems at the same time. The console ports are clearly marked, so their is no confusion about which cable is which port. It doesn't slow down the response, either. I have seen some cables that split the connectivity so that you get 10-20 lines from one cable, then 10-20 lines from the other.So, long and the short is that it works and does it easily. I mainly use a Mac, so I can provide OSX approval and confirmation of working. If you really press, I could provide iTerm2 settings that I use to capture my console logs and tell it to grab the ports for serial.This same cable is now the standard cable to be purchased if anyone asks me. So, I would say go for it, if you need a dual-serial connection. It's good and it works.

Use this for work quite often. As a network engineer, there's lots of times I need to be connected to two console ports at the same time. Saves USB ports on my laptop.I can also leave these plugged in and the laptop running overnight. Had other individual ones that burned out leaving them running overnight.Finally, since it uses the FTDI chipset, Mac drivers are readily available work flawlessly and the ports show up with names that actually make sense.One tip: On my Mac, I installed 2 copies of Zterm and left 1 named 'Zterm' and the other 'Zterm 2'. This allows me to have two console sessions operating simultaneously. No problems.

Sometimes it just helps to be able console into 2 devices at once. Esp when troubleshooting or configuring an offline stack or redundant pair. This adapter has worked well for me.

I hadn't been in the market for USB->Serial for some time. I had been quite happy with the Keyspan product. I have the HS-19 and USA=49WG four port models. They worked great until I updated to Win7 64 Bit. They worked great under Win7/32. Suddenly, I was chasing BSOD (Blue Screen of Death). After finding that the Keyspan drivers were the culprit, I went to get new drivers. Keyspan has been acquired by Tripp Lite. They list the drivers as supporting Win7/64 - but they don't.. The driver date is 2007 - well before Windows 7. So.. time to change.I heard that FTDI had great support. I really wanted a four port device, with female receptacles. This two-port cabled device was as close as I could get. So I do have a bit more of a cable mess than with Keyspan 49, the BSOD is gone.The software is intuitive and integrated into Win7. I have two of these devices (4 ports total). They have serial numbers built in. So, when I move them around to different USB ports, they always come up with the same COM number. Not all drivers do this. Some report a different com port when plugged into a different USB port. It is much nicer to be able to label each of the connectors as COMxx instead of having to go to device manager each time I power up.I am using 115,200 bps, but plan to move to faster speeds as I qualify my embedded device.

I bought this product based on the other recommendations. I'm using some older products that don't have USB ports. The product is well built. While I'm using this product under Windows Ultimate x64, I was pleasantly surprised that the driver CD came with drivers for all sorts of other systems (Mac, Linux, even drivers for developers under Windows CE!). After installing the drivers, it worked right off the bat on my system, and it didn't even change the COM port assignments when I plugged into other USB ports. That in itself is a big win. The cables are quite long, and I was able to ditch some of my extensions. The FTDI chipset simply rocks.

Worked out of the box with Linux. Great product.

After years of struggling with buggy drivers and erratic configurations of these devices, especially ones based on the Prolific Tech chip set (as most of the inexpensive USB<--<serial cables are) this one "just works"! This one worked the very first time on WinXP, Win7-32, and on Win7-64. Even bigger surprise was that on Win7-64 (which is notoriously fussy about demanding officially-Microsoft-blessed "signed drivers") the device just "automagically" started working about 20 seconds after I plugged it in. Apparently, the FTDI chip (that this device is based on) is a known device in Win7's library of devices -- I didn't even have to use the provided install CD or download a driver.I use the device to connect legacy serial-interface GPS hardware and two-way radio modems to a laptop in my car. This is a notoriously noisy electrical environment, with all the electrical/electronic devices, alternator hash, etc. This device has been absolutely rock solid with none of the hiccups, random disconnects, etc I've had with other such cables.Getting two serial ports for the cost of one USB port is a bonus, especially on netbooks with their limited supply of USB ports.

I plugged this into a old 486, and now it doesn't send/receive anymore.No activity LEDs on receive or send. Needs better protection.