SIO2PC Interface (RS-232 build)

Year
1989
Type
DIY project
Category
SIO-to-PC serial interface
Manufacturer
Homebrew (design by Nick Kennedy; later kits and variants by others)
Hand-drawn schematic titled 'SIO2PC - Atari 8-bit to PC Interface by Nick Kennedy': a MAX-232 chip with four 22 uF capacitors buffers data to PC, data to Atari and the command line between Atari SIO pins and DB9/DB25 PC serial pins.

Overview

SIO2PC is the grandfather of every "PC as an Atari disk drive" setup. Nick Kennedy, an electrical engineer and ham-radio operator who had owned an Atari 800 since 1982, designed a small interface between the Atari's SIO peripheral port and a PC's RS-232 serial port, plus DOS software that answers the Atari's disk commands from files on the PC. By his own account the project took more than seven years to come together. It was released as shareware, with versions dated from 1989 to 1998, and it originated the .ATR disk image format.

On the Atari side you need no drivers or patches. The PC simply answers as drives D1: to D4: (later versions went further), so you can boot from it, use any DOS, and even run sector copiers. Kennedy rated it almost twice as fast as an 810 drive. It can also share the daisy chain with real drives.

How it works

Kennedy's build notes describe three problems the interface has to solve:

  1. Voltage levels. The Atari uses TTL signals (0 V and +5 V). RS-232 is bipolar and inverted: roughly +5 to +15 V means logic 0 and −5 to −15 V means logic 1. A Harris ICL232 or Maxim MAX232 converts in both directions. Its built-in charge pump makes the ± voltages from the Atari's 5 V supply, so you don't need a separate power supply.
  2. Bus versus point-to-point. SIO is a shared bus, and every peripheral's data-out line joins the computer's single data-in line. The interface fakes an open-collector output with a diode and pull-up resistor, so it doesn't fight other devices on the chain.
  3. Handshaking. SIO has one handshake line, /COMMAND (pin 7), which warns all peripherals that a command frame is coming. SIO2PC sends it to the PC's RI (ring indicator) input. Modern emulators such as RespeQt likewise watch one control line (CTS, DSR or RI) rather than using RS-232 hardware flow control.

The baud rate was the lucky part. SIO runs at 19,200 bit/s, which the PC BIOS of the day couldn't set, but the UART hardware could, so the software programs the serial chip directly.

Specifications

Item Detail
Core chip ICL232 or MAX232 (dual TTL↔RS-232 driver/receiver with charge pump)
Other parts 4 × 22 µF 25 V electrolytics, 0.1 µF bypass cap, 16-pin socket, perfboard
Atari connector 13-pin SIO plug (Kennedy cut a standard I/O cable in half)
PC connector DB-9F (or DB-25F: DB-9 pins 2/3/5/7/9 = DB-25 pins 3/2/7/4/22)
Power +5 V taken from the Atari
SIO signals used Data In (3), Data Out (5), /Command (7), Ground (4/6), +5V/Ready (10)

Building one

Kennedy's parts list is classic Radio Shack: a small project box, prototype board 276-150, the ICL232, four 22 µF capacitors, a 0.1 µF disc capacitor, a five-conductor cable, a DB-9F connector and hood, and half an Atari I/O cable. Identify the wires in that cable with an ohmmeter rather than trusting the colours. He also sold kits and built units for people who didn't want to solder.

Steven Tucker's APE ProSystem cable netlist (in the APE 1.15 package) uses the same chip with the roles reversed. In this design the PC plays the computer, so it can talk directly to real Atari drives, for example to image disks:

  • PC ground to ICL232 pin 15, DTR to pin 8, TxD to pin 13, RxD to pin 14.
  • Atari Ready (pin 10) and the +5 V source to ICL232 pin 16 (Vcc), Data Out to pin 12, Command to pin 9, Data In to pin 11, ground to pin 15.
  • A 1.2 kΩ pull-up from pin 16 to pin 11.
  • The four 22 µF capacitors go across pins 1/3, 4/5, 15/6 and 2/16.

Here the PC's DTR line, through the chip, drives the SIO /COMMAND line, and the PC's TxD drives the "computer data out" line that drives listen to. It needs a separate +5 V source; its author reported that even a 9 V battery worked. For drive emulation, by contrast, the Atari drives /COMMAND and the PC only watches it, which is why emulator software lets you choose the handshake line. Later SIO2PC variants replaced the MAX232 with a 1489 (or 14C89) receiver; Rick Cortese is credited with this simplification. Atarimax eventually sold a microcontroller-based Universal SIO2PC/ProSystem interface that works both ways.

Software

The original SIO2PC.COM runs under MS-DOS and offers RAM disks, file-backed disks of up to 65,525 sectors, a print-through mode for Atari printer output, FILE2PC transfers and a "1050-2-PC" mode for imaging disks from a real drive. The same cables work with APE, Atari810, SIO2Linux, AtariSIO, AspeQt and RespeQt. RespeQt in particular is cross-platform and actively maintained, and it is the usual choice today.

Pitfalls and safety

  • Never connect raw RS-232 to the Atari. Kennedy warns that the negative swing of an RS-232 output can damage a TTL input, so the level converter is mandatory.
  • The 1200XL has no +5 V on SIO pin 10. On that model pin 10 carries Ready only, so a cable powered from pin 10 needs another supply there.
  • If drives 3 and up return error 160 under DOS 2.x, the DOS isn't configured for them: POKE 1802,15, then rewrite DOS.
  • Don't let an SIO2PC drive number collide with a real drive or an Atari-side RAM disk.
  • Kennedy found that running SIO2PC inside Windows could starve its timing. Give it full-screen exclusive priority, or run it in pure DOS. Users also traced intermittent errors to printer noise and to equipment plugged into different surge suppressors.

Credits