TelescopeYoke

A self-measuring robotic observatory for affordable GoTo mounts, run by a person and an AI agent together.

Free and open source. Runs on a laptop beside the telescope: Linux, with a Windows port.

A minute and a half of the demo: tonight's report, a target picked, a GoTo shown as a plan and then centred by plate solving, focusing, and an imaging run with cloud coming over
The demo: a pretend mount, camera and sky, with the real centring, focusing and stacking code running on them.

What it does

You already own the mount, the handset and a camera. TelescopeYoke is the part a smart telescope has and yours does not. It is built around one idea: measure the imperfections of modest equipment instead of pretending they are not there.

It runs on your own computer. No account, no cloud service.

Real results

The Dumbbell Nebula, M27
The Dumbbell Nebula (M27): 48 two-second exposures through a 150 mm Newtonian on an EQ3 Pro that was polar aligned by eye. The home position was about ten degrees out; plate solving found the target anyway.
The Triangulum Galaxy, M33, in luminance from the cooled mono camera
The Triangulum Galaxy (M33) from the cooled mono camera's first night, 4-5 November 2026: 126 frames of 16 s at -5 °C, darks only. The darker corners are for want of flats, still to take.
A move shown as a plan, waiting to be confirmed
Every move is a plan first: where the tube will end up, which side of the mount, and the limits it was checked against.

Already using NINA and PHD2? Analyse last night without changing a thing

The companion reads the frames your capture program saved and PHD2's guide log, measures every frame against that night's best of the same setup, and says where the time went. It touches no device. What it measured is kept apart from what it only infers, and every file is accounted for. Here is a real night (the author's own, 5 November 2026), trimmed:

706 files: 693 light frames measured; 13 left out, no single-plane image (a stack or a colour picture).
M33 L (183m, gain 1500, 16 s) 00:23-01:41: 57 min measured; 37 min acceptable by its own best frames (139 of 213 frames)
    15 min (56 frames) dimmed: likely cloud or haze
    5 min (18 frames) trailed: likely the mount's tracking or the wind (no guiding to compare)
No frames 01:15-01:33 (18 min beyond the usual gap): not known: nothing it reads says
Where the time went: no frames (explained) 44 min, dimmed 38 min, no frames (unexplained) 36 min, trailed 11 min, soft 6 min

In the download since 0.4.1. Tried on the author's frames, on made-up nights with known faults, and offline on NINA and PHD2 logs other observatories have published (it told one night's 27 ten-minute lights of M 27 from its autofocus, plate-solving and focusing frames, judged them by NINA's own star detection, and found a five-minute stretch where PHD2 said it was guiding with no guide step); not yet live beside anyone else's observatory. More, with another observatory's night and how to run it.

Try the demo: no telescope needed

The demo is the whole application on a pretend telescope. Nothing is connected to your mount and nothing can move, so it is safe to try on the computer that sits beside real equipment.

Ubuntu or Debian

wget https://github.com/Ryan-Clinton/telescopeyoke/releases/download/v0.4.2/TelescopeYoke-v0.4.2.zip
unzip TelescopeYoke-v0.4.2.zip
cd TelescopeYoke-v0.4.2
./install.sh --demo

Windows 10 or 11

A window opens with tonight's report. Pick a target, press "Centre with plate solve", and watch it find and correct its own pointing error. Then try Focus and Imaging; "The pretend sky" lets you bring cloud over or pull the camera's lead out, to see what it does when a night goes wrong.

The Tonight screen
Tonight: the verdict and the best targets.
The Focus screen
Focus: one number, and which way it is going.

Supported hardware

It is new, and it says plainly what it has and has not been proven on. So far it has run on one telescope, the author's:

MountHandsetCameraSystemWhat has workedTried by
Sky-Watcher EQ3 ProSynScan, firmware 3.35Altair Hypercam 183CUbuntu 26.04Planner, mount moves, camera, focusing, plate solving and GoTo with centring, under real starsthe author
the same EQ3 Prothe samethe sameWindows 11The demo, and camera frames indoors. No mount driven yetthe author
the same EQ3 Prothe sameAltair Hypercam 183M PRO TEC (mono, cooled), Starlight Xpress filter wheel, 0.9x coma correctorUbuntu 26.04First night 4-5 November 2026: cooled to -5 °C, darks, every filter, plate solving, polar alignment, M33. No flats yetthe author
EQ5SynScananyLinux or Windowswantedcould be you
HEQ5SynScananyLinux or Windowswantedcould be you
EQ6, EQ6-RSynScananyLinux or Windowswantedcould be you
a mount with an EQStar or other EQMOD-style controllernoneanyLinux or Windowswanted: whether it answers at allcould be you

EQ5, HEQ5 and EQ6 mounts with a SynScan handset speak the same serial protocol, so they are likely to work, but nobody has tried. On Linux the camera is read through INDI; on Windows, Altair cameras through their own library. New in 0.4.1: a mount, camera, focuser and filter wheel through their ASCOM drivers (Alpaca), tried only on ASCOM's own simulator so far; guiding by PHD2, tried only against a pretend PHD2; and a companion that watches an observatory you already run, from the frames it saves and PHD2, without touching it, run on the owner's own 693-frame night and on published NINA and PHD2 logs of three other observatories, not yet live beside anyone else's.

Looking for testers. If you have one of these mounts, a report from you is worth more than any new feature, and you do not have to let it move your mount. ./doctor.py --report only looks at what is connected: it writes out what the handset says the mount is, its firmware, and what was found, with your location left out. Paste that into a hardware report, or ask first in Discussions. Your name goes beside your row if you want it there.

Find out more