Plate solving (ASTAP)

ASTAP is the plate solver Starship integrates with. Free, fast, runs locally with downloaded star catalogs. Plate solving is a pure computation on the pixels of a FITS frame — it never moves equipment, so it's always safe to run.

What plate solving gives you

Point Starship at any FITS frame from your IMAGES folder and it hands the file to ASTAP, then reads back the solution:

A solve also captures the full WCS terms (the CD matrix and reference pixel), which is what lets Starship translate a pixel you click on into a sky position.

Solving a frame yourself

Console → the plate-solve tile. Pick a file from the list and you get:

After a solve you can act on the result without leaving the tile: → GoTo (plain slew to the solved coordinates), → Precise GoTo (the slew-and-center loop below), and ⟲ Sync from solved position.

Center here. On the Console's Last captured frame preview, click the Center here toolbar icon, then click a point on the image and confirm — Starship solves that frame and precise-slews the mount so the point you clicked lands in the centre. Requires a mount, camera and ASTAP.

Precise pointing (slew-and-center)

Precise GoTo runs a full slew → capture → solve → sync → re-slew loop, repeating until the solved position is within tolerance of the target (the Voyager GoTo++ / NINA slew-and-center equivalent). Configure it under Settings → Mount (Precise pointing): exposure, binning, tolerance (arcminutes), max iterations, and settle time. Sequencer slew steps run this automatically when the step has precise: true. Requires a camera and ASTAP.

A sync far from the mount's position is refused

New in v23. A sync tells the mount "you are really pointing here". A wrong plate solve synced to the mount spoils its pointing. So a sync is refused when the solved position is further from where the mount says it points than Do not sync a solve further away than (°) (Settings → Mount; [pointing] max_sync_distance_deg, default 10).

The scale check

New in v23. A plate solver can return a false match: a solution at the wrong image scale, somewhere else in the sky. Starship now compares the scale of each solution with the scale your optics should give:

expected scale (arcsec per pixel) = 206.265 × pixel size (µm) × binning / focal length (mm)

A solution more than 25 % away from that, either way, is rejected as a failed solve ("plate solve rejected: the solution's scale … is not this rig's"). The tolerance is wide on purpose: a focal length read from the tube's label is a few percent out, while a false match is usually out by a large factor.

Recenter after a meridian flip

This flow is now fully wired (it used to be a stub). Turn it on with Settings → Mount → "Plate-solve recenter after flip", and set the recenter exposure alongside it.

After the sequencer performs a meridian flip, if recenter is enabled it:

  1. Takes a short exposure (the recenter exposure, default 5 s)
  2. Plate-solves it
  3. Syncs the mount to where it actually points
  4. Re-slews to the intended target
  5. Settles, then continues the sequence

This is what keeps an unattended German-equatorial mount on target across the meridian, correcting any pointing shift the flip introduced. It needs a connected camera and ASTAP; without them the recenter step reports an error and the flip fails safe.

Plate-solve actions in a sequence

Two mount actions in the sequence editor use plate solving:

Both are also available from the Console (Blind solve on the plate-solve tile, and the blind-sync recovery path).

Settings

Settings → Plate solver (ASTAP):

Settings → Camera has two solve-only overrides used by pointing / polar / rotate-to-PA frames:

The field-of-view hint is derived automatically from [camera].focal_length_mm + pixel_size_um and the connected camera's reported sensor height. Set the focal length and pixel size under Settings → Camera and Starship passes the right FOV to ASTAP; leave either at 0 and ASTAP auto-detects the scale instead.

Installing ASTAP and its catalog

ASTAP needs a star database in its install directory to solve. Install the D50 database from the ASTAP site (it covers typical deep-sky FOVs); download a catalog matched to your image scale if D50 doesn't fit. Without a database ASTAP can't solve. We don't bundle catalogs.

When a solve fails

The most common causes Starship reports back:

A hinted solve that fails retries blind (whole-sky) before reporting failure, so "no solution" usually means the frame genuinely has too few stars or the database is missing. The exception is ASTAP's Not enough stars.: a wider search cannot add stars to the frame, so Starship reports that at once without the blind retry. Look for what is hiding the sky - a closed roof or cover, cloud, the cap on, or an exposure too short for the field. (Precise pointing still tries once more at a longer exposure.)

Astroworx Starship v23.1.2 · this page is the in-app help of that buildDownload · HTTP API