USB SIO2PC Cable (FTDI build)

Type
DIY project
Category
SIO-to-USB serial cable
Manufacturer
Homebrew (commercial equivalents from Atarimax, Lotharek and others)
A small clear plastic Atari SIO plug with a USB Type-B socket built into its back end, the SIO contacts visible at the front.

Overview

Few PCs still have an RS-232 port, so the classic MAX232-based SIO2PC has largely given way to USB. The simplest USB version needs no level-shifting chip at all. Atari SIO signals are 5 V TTL, and a USB-to-TTL serial adapter built on FTDI's FT232R already speaks TTL. Wire the adapter's TX, RX, a modem-control input and ground to an SIO plug, and you have a working disk-drive emulator link for RespeQt, AspeQt, APE and similar programs.

It is a popular first project: cheap, quick and forgiving. Commercial units do the same job. Lotharek's 10502PC/SIO2PC-USB is one. The Atarimax interface goes further, using a custom-programmed microcontroller rather than a bare FTDI chip.

Parts

Part Notes
FTDI FT232R(L) USB-to-TTL adapter or cable Set to 5 V logic if it has a jumper. Genuine FTDI chips are the safe choice; Prolific PL2303 adapters give mixed results.
Half of an Atari SIO cable, or a new SIO plug Some builders 3D-print a plug shell and use crimp contacts
4–6 conductor cable An old USB cable works, with its shield as ground
Heat-shrink, solder

A 6-wire adapter (TX, RX, CTS, RTS, VCC, GND) is better than a bare 4-wire one because it brings out a control input for the SIO command line.

Wiring

The standard connections are:

FTDI signal SIO pin SIO function
GND 4 or 6 Ground
RXD (adapter input) 5 Computer Data Output
TXD (adapter output) 3 Computer Data Input
CTS (adapter input) 7 /Command
VCC not connected —

Don't connect the adapter's +5 V pin to the SIO port. Two separate supplies (the PC's USB and the Atari) should never be tied together.

Cable colours lie. Popular quick recipes match the black, green and orange wires of a cut SIO cable to an FTDI programming cable, but cable colours vary, so verify every pin with a meter before you power up.

Is the command line optional?

A three-wire cable (ground, TX, RX) does boot software if you set RespeQt's handshake option to "Software (SIO2BT)". Without /Command, though, the emulator can't tell which frames are commands. That is fine only when the PC is the sole device on the bus. If you also want a real 1050, printer interface or other SIO device on the chain, wire /Command to CTS (or DSR/RI) and pick the matching handshake setting. The workaround with a minimal cable is to copy files to a RAM disk or hard disk, then swap devices.

Setting up the software

  1. Install the FTDI virtual COM port driver if your OS doesn't already include it. Note the COM port or /dev/cu.usbserial-* name the system assigns.
  2. In RespeQt, go to Tools → Options, choose that port and the handshake line you wired (CTS for the table above). The write delay only matters for Bluetooth and can be set to 0 ms.
  3. Mount an ATR in D1: and power the Atari on with no other D1: present.
  4. Once standard speed works, try high-speed SIO. RespeQt supports up to about 6× with FTDI adapters and a compatible OS or DOS.

Troubleshooting

  • Port opens but nothing happens. Some virtual-serial drivers pass no incoming data until DTR is asserted. Newer RespeQt versions set it.
  • Mac or Windows driver trouble is the most common complaint. Prolific chips are the usual suspect; switching to FTDI, or reinstalling the official FTDI VCP driver, generally fixes it.
  • Mechanical failure. Bare breakout boards have been known to lose their mini-USB socket. Strain-relieve the cable, or use a complete FTDI cable rather than a bare board.

Credits