ASCOM Alpaca, from Python

TelescopeYoke reaches another maker's mount, camera, filter wheel and focuser through their ASCOM drivers over Alpaca (HTTP and JSON on the network), and guides through PHD2.

Setting it up

In config.toml:

[mount]
link = "alpaca"
address = "192.168.1.20:11111"   # each device its own address and number,
device = 0                       # as ./alpaca.py find lists them

[camera]
backend = "alpaca"
address = "192.168.1.20:11111"
device = 0

[filterwheel]
backend = "alpaca"
address = "192.168.1.20:11111"
device = 0

[focuser]
backend = "alpaca"
address = "192.168.1.20:11111"
device = 0

[imaging]
gain = 100                       # in this camera's own units

[guider]
backend = "phd2"

The addresses are an example. Each section needs its own address; without one it is refused, never guessed. The gain in the example config (1500) is the author's camera: a gain outside the camera's range, or not one of its named gains, is refused.

./alpaca.py find lists the Alpaca servers and their devices; nothing is ever picked from that list by itself. Setting alpaca_name to the driver's name makes a different telescope at that address a refusal, and until the driver has this computer's site and clock (./mount.py settime) a GoTo is refused. The same limits and dry runs apply as on a SynScan mount.

What has run, on ASCOM's simulator only

How far it is proven. Built on 19 November 2026, in release 0.4.1. Tried only against ASCOM's own Alpaca simulator (OmniSim 0.4.0) and a pretend PHD2: no real device yet. Watch it the first time. A hardware report from a real mount would move it on.