The FTDI cable is a USB to Serial (TTL level) converter which allows for a simple way to connect TTL interface devices to USB. The I/O pins of this FTDI cable are configured to operate at 5V.
The FTDI cable is designed around an FT232RQ, which is housed in a USB A connector. The other side of the cable is terminated with a 0.1" pitch, 6-pin connector with the following pinout: RTS, RX, TX, 5V, CTS, GND (RTS is the green cable and GND is black).
This cable has the same pinout and functionality as our FTDI Basic Breakout board; you can use it to program your Arduino Pro, Pro Mini and Lilypad. For use with those boards, align the black and green wires of the FTDI cable with the 'BLK' and 'GRN' labels on the PCB.
There are pros and cons to the FTDI Cable vs the FTDI Basic. The FTDI Basic has great LED indicators, but requires a Mini-B cable. The FTDI Cable is well protected against the elements, but is large and cannot be embedded into a project as easily. The FTDI Basic uses DTR to cause a hardware reset where the FTDI cable uses the RTS signal.
Based on 27 ratings:
1 of 1 found this helpful:
Does everything it should do.
2 of 2 found this helpful:
The device would seem to have the authentic FTDI chip since the Windows driver loaded nicely (not bricked or blocked as for fake chips). Cable works nicely with my Arduino Mini Pro programming.
2 of 2 found this helpful:
The FTDI cable worked as received. On plugging it in, Windows automatically installed the necessary drivers and I was able to use the cable together with my Arduino right away
1 of 1 found this helpful:
Does what its supposed to when connected to the mega pro. Use to load sketches and receive serial data. Works just like a USB cable on a regular Arduino. I have the FTDI break out board also but prefer this cable for simplicity's sake.
Hooked it up, plugged it in, worked first time. What else could you want?
0 of 1 found this helpful:
It worked! I did have to go into Windows Control Panel-Device Manager, find the COM port and use the Advanced settings to change from COM11 to COM1 for my application, but otherwise, it worked without a hitch.
The link provided to the driver in the item description was especially helpful. I know buying a cheaper one can be risky, but these are priced high, so for my next one I bought it for less than half the cost of this one...we'll see how it goes.
Even though I only needed the CTS of this cable it worked when one I got from China did not.
Good quality FTDI cable.
I am not a programmer or developer. I am a musician using eurorack modular equipment. I had some modules that needed firmware updates and this cable got the job done. The USB cable was a better choice for me over the basic breakout board because of convenience factor. With this and some jumpers cables I will be able to update any module that uses this method for updating.
Great little device. You need a usb cable for the FTDI breakout anyway, why not just get one built in?
A must have for communicating with boards using terminal programs like RealTerm and PuTTY. Plop a serial header on your PCB and you are off to the races.
Works as advertised... wires are a little on the small size.
I call these "magic cables". I buy them 5 at a time, and I'm up to at least 20 by now. I use PIC micro-controllers on wire-wrap boards for most of my projects. This cable provides two-way communications with the PC, and even powers the PIC. It works great with custom VB.NET apps, or PuTTy, a free terminal program. It even works reliably up to 2 MBaud through the Windows COM port interface! I dread the day when they are no longer available, hopefully many years from now.
I needed a 5V TTL serial adaptor a few months ago. I decided I didn't want to gamble on a fake FTDI chip so I bought from Sparkfun. The application is an 8192 baud serial link for GM cars. Due to the odd baud rate, the only two chips that will work well are FTDI's FT232R series and the Silabs CP2102 series...and since it's standard TTL, that makes the FTDI the easiest solution.
Well, it's been an absolute nightmare to keep this thing working. One download, it's fine, the next, it's corrupting the firmware in the car's computer. Pull everything, put it on the bench, different wiring, different computer, different PC, same issues-sometimes it works, sometimes it's garbage. No rhyme or reason to it, I can't even get the thing to fail a loopback test-but you can't send data over it reliably. Even tried talking to the arduino with it, same results...sometimes it works, sometimes it doesn't.
I hope the next one works better than this one.
What you're trying to do is possible, but involves modifying either the driver or the FT232R IC with some other software. FTDI has some documentation on getting non standard baud rates to work by changing the divisor used by the chip internally and/or modifying a standard baud rate to work at the non-standard one. Take a look at these links, they should help: http://www.ftdichip.com/Support/Documents/AppNotes/AN232B-05_BaudRates.pdf http://www.ftdichip.com/Support/Documents/AppNotes/AN_120_Aliasing_VCP_Baud_Rates.pdf
This cable works fine if you are using the assembly in a 3-wire mode but if you need to use it in a full-handshake UART mode, this cable is missing critical signals. I'm not certain why the folks at Sparkfun just didn't bring out all the RS232 signals from the FTDI IC and let the user decide which to use.
It does what it's supposed to do. Easier to use than the breakout board.
Too many outdoor projects to complete before snow is dumped on us. When the weather gets cold the Arduino projects are on the bench for learning and building.
This work exactly like I need and the quality is so much better than the knock offs. Just wish it wasn't so expensive. Doubles my BOM cost.
Used this with the Pro device. Works great.
Used Mac and Windows 10, both work fine.
There was no special driver to install due to fake chipset. Contains the real thing chipset! Windows 10 recognized and setup the correct driver with no issue! Supplied sufficient power to Arduino Pro Mini 5V for proper operation.
Works great to clean up my RigExpert AA-30.zero antenna analyzer setup.
I'm using this cable to interface with the serial terminal pins on a 8052-BASIC MCU (circa 1984) that I'm in the process of building into a trainer. I only need to use the Rx, Tx and ground ground pins. The FTDI USB drivers automatically installed as normal and it worked the first time and continues to work...
Works with Windows 8.1 and is great for roomba SCI interfacing.