Skip to main content
added 10 characters in body
Source Link
Wouter van Ooijen
  • 48.8k
  • 1
  • 65
  • 140

I assume you are referring to FT232 or the like. In that case your plan can't work, because those chips are USB slave devices, and two USB slaves can't talk to each other.

To connect them, you'd need a USB host with two ports, the FTDI driver installed, and a small app that copies characters from one (virtual) serial port to the other. Quite feasible with a Raspberry Pi.

I assume you are referring to FT232 or the like. In that case your plan can't work, because those chips are USB slave devices, and two USB slaves can't talk to each other.

To connect them, you'd need a USB host with two ports, the FTDI driver installed, and a small app that copies characters from one serial port to the other.

I assume you are referring to FT232 or the like. In that case your plan can't work, because those chips are USB slave devices, and two USB slaves can't talk to each other.

To connect them, you'd need a USB host with two ports, the FTDI driver installed, and a small app that copies characters from one (virtual) serial port to the other. Quite feasible with a Raspberry Pi.

Source Link
Wouter van Ooijen
  • 48.8k
  • 1
  • 65
  • 140

I assume you are referring to FT232 or the like. In that case your plan can't work, because those chips are USB slave devices, and two USB slaves can't talk to each other.

To connect them, you'd need a USB host with two ports, the FTDI driver installed, and a small app that copies characters from one serial port to the other.