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
- Mount: GoTo on both sides of the pier, a stop in mid-slew, home, RA and Dec rates.
- Camera: frames full and 2×2 binned, mono, by ImageBytes or JSON; a short imaging run end to end. Cooling is left to the driver's own program.
- Filter wheel: by name and number. Focuser: out and back to the step, its temperature.
- Guiding by PHD2: guide, dither, stop round GoTos, each frame's guiding measured from PHD2's own steps.