SIO2BT (Bluetooth SIO)

Year
2014
Type
DIY project
Category
Bluetooth SIO link
Manufacturer
Open project by Marcin Sochacki (Montezuma)
Two black Atari SIO plug housings with small Bluetooth stickers, each in a plastic bag, above two more bags holding Bluetooth serial modules with wires attached and 'Bluetooth' labels.

Overview

SIO2BT cuts the cable between the Atari and its emulated drives. Marcin Sochacki (Montezuma) found that an inexpensive HC-06 Bluetooth serial module speaking the Bluetooth Serial Port Profile (SPP) could stand in for an SIO2PC cable. A phone, tablet or PC then answers the Atari's SIO commands over the air. The hardware project dates from 2014–2016, and the companion Android app from 2014–2019. The project page on abbuc.de/~montezuma offers a "Documentation + Software" package dated 3 November 2019, with GitHub links to the source.

SPP is supported by Windows, Linux and Android, but not iOS. iPhones and iPads can't be used as the server.

Hardware options

There are three ways to build it:

  • External dongle: an HC-06 module in a small box on an SIO plug. It is not meant to share the bus with other real SIO devices.
  • SIO2SD+BT combo: Bluetooth added to an SIO2SD board.
  • Internal: the module fitted inside the computer.

The Android app looks for a paired module whose name starts with "SIO2BT" or "ATARI". The Atari utilities BTCONFIG.XEX (by Mr. Atari) and btcfg.com (a SpartaDOS X command by Jonathan Halliday) set the module's baud rate, friendly name and PIN.

Why the Atari OS needs a patch

Bluetooth adds latency, and the stock OS gives up on a device sooner than an SPP link can reliably answer. SIO2BT therefore relies on patched SIO code with longer timeouts:

  • SIO2BT_OS_Patcher.jar (PC) patches 400/800 and XL/XE OS ROM images, Hias's high-speed SIO patch, the MyIDE OS and QMEG+OS 4.04.
  • The XL OS (not the 400/800 OS) can be patched at run time. Boot disks are provided for the 600XL, both 1200XL revisions and XL/XE/XEGS, in variants that load the game as D2: or swap it into D1:. An xBIOS for Bluetooth loader comes in $700 and $400 versions.
  • Ultimate 1MB and Incognito firmware include an SIO driver that works with SIO2BT at 19.2, 38.4 or 57.6 kbit/s. MyIDE-II supports the same rates.
  • SpartaDOS X can use its own SIO with SIOSET (longer timeout, set disk baud rate), or the patched OS SIO. LiteDOS-SE supports 19.2 kbit/s Bluetooth.

Servers

  • SIO2BT Android app: up to four drives with ATR and XEX/COM/EXE files (long-press to choose the XEX loader address, default $700, or to toggle write protection). It also provides an SIO networking device ($4E) with a TCP/IP stack, and a smart device ($45) offering APETIME-compatible "get time" and URL submission.
  • RespeQt, AspeQt for Android and SIO2BSD all support SIO2BT. In RespeQt, choose the "Software (SIO2BT)" handshake. Because there is no command line over Bluetooth, the server has to recognise command frames from the data stream itself. The write-delay setting applies only to Bluetooth.
  • FujiNet once offered an SIO2BT-compatible Bluetooth mode, but it was removed from later firmware until a smaller Bluetooth stack can be fitted.

Troubleshooting

  • "No server response" from RCL or MENU.XEX: on Ultimate 1MB machines, enable SIO2BT for all devices in the U1MB SIO menu rather than only D1:–D4:, which is a known fix.
  • No reconnection after a cold boot: RespeQt's SIO2BT mode reads command frames in an endless loop. Windows gives the program no clean way to detect that the Bluetooth serial port has closed, so you may have to reconnect by hand.
  • Expect occasional flakiness with directory-mounted folders that change while being served.

Credits