Getting started
Your first session, end to end. Read once, then bookmark for reference.
Install and launch
Starship ships as a Windows installer (Astroworx-Starship-Setup-vXX.YY.Z.exe, Windows 10 and 11, 64-bit). Run it: it installs per-user into %LOCALAPPDATA%\Programs\Astroworx Starship, adds a desktop and Start-menu icon, and can launch Starship at the end. Upgrading is the same installer over the old one; your config.toml, plans and images are kept.
Launch from the icon. Starship starts its web service and opens the dashboard in its own window at http://localhost:8765 (you can also open that address in any browser on the PC, or on the LAN once you bind [web] host to 0.0.0.0).
Astroworx Starship is free - no licence and no activation: install it and go.
You need on the same PC:
- the ASCOM Platform (6.6 or 7) and your device drivers, for ASCOM gear
(ASCOM is on by default in a fresh install) - or Alpaca devices reachable on the network;
- PHD2 if you want guiding (Starship can auto-launch it);
- ASTAP with a star database for plate solving, polar alignment and precise
pointing.
Developers can also run from source: python scripts/run_starship.py in the source tree (Python 3.12, pywin32, numpy, psutil).
Connect your equipment
Open Settings. Equipment lives in a per-role tab — Mount, Camera, Focuser, Filter wheel, Rotator, Flat device, Observatory, Power. Open the tab for each role you have hardware for and pick a transport:
- ASCOM (Windows COM): click Choose… to open the ASCOM chooser and pick your driver — this fills in the ProgID (e.g.
ASCOM.Simulator.Camera). Then click Connect to test it. - Alpaca (HTTP/JSON): enter the Alpaca server's Host, Port (default
11111), and Device number (usually0), then Connect.
Tick Auto-connect on service start if you want that device to connect every launch. Click Save & restart at the bottom — the transports re-initialise on restart.
Don't forget the Site / Location tab: set your latitude, longitude and elevation before any on-sky work. Coordinates left at zero silently break focus-star altitude, airmass and the scheduler.
Once configured, connect and drive everything from the Console (top ⚡ Connect all); the Equipment page is the live status view. It lists every configured slot — your devices show up as tiles right away, offline with their ProgID, and fill with live data the moment they connect. If a device won't connect, the status/error text in the tile or badge is usually clear enough; confirm it works in its own driver / setup tool first.
First exposure
Go to Console. The Camera card has Object, Filter, Exposure (s), Binning, Gain, and Frame (Light/Dark). Enter a short exposure (1 second), pick a filter, click ▶ Capture. The frame lands in your IMAGES directory and appears in the Last captured frame preview on the Console automatically (double-click it to enlarge). A live progress bar tracks the exposure and download; Abort cancels an in-flight capture.
This proves the camera + filter wheel chain works end-to-end. If the frame is upside-down, sideways, or has weird pixel values, fix that before you trust autofocus or the sequencer.
Set the cooling target
If your camera has a cooler, the Cooling section folds into the bottom of the Camera card on the Console (live sensor temp, setpoint, Δ from setpoint, power %, and a state pill).
- Settings → Camera → set the cooling Default setpoint (e.g.
-10for a typical CMOS at moderate ambient). - Save & restart.
- Console → Camera card → Cooling → set a target °C and click Cool (or Off / Warm up).
- Watch the temperature drop. It'll take a few minutes. The Δ turns green and the state reads settled when the temperature stays within the settle window for the dwell period.
Power % at 100% means the cooler is maxed out — you're asking for a setpoint it can't reach; ease the target up. You can leave the cooler on between sessions, or use Settings → Camera → On-connect action ("Turn cooler ON") to start it at the default setpoint whenever the camera connects. Leave it on "Leave cooler in current state" if you'd rather not thermal-cycle the sensor when you reconnect during testing.
Set up autofocus: First Light, once
First Light is part of setting the focuser up. You run it once; from then on it is Refocus, in the Console and in every plan. Until it has run, the Focuser card says First Light needed.
- Focus roughly by hand, so stars show. Use the focuser move controls (type a position then Go, or the −100 / +100 buttons) and Console → Capture.
- Aim at a normal star field — a good spread of stars in the centre. Tracking on, mount settled, the optical train as you image with it. Broadband filters give the most stars.
- Console → Focuser card → First Light… → Start First Light. Nothing to enter.
- Watch it work for 10–15 minutes (about 70 frames): it measures the stars where you are, probes how they change, sweeps the V-curve, sweeps it again from the other side to measure the focuser's backlash, then checks the result with two refocuses. Don't touch anything.
- When done, the readout shows
focus <pos> · First Light ✓. The scope is left focused. You're done — for this telescope and this focuser.
Run First Light again only if the telescope or the focuser changes (Starship notices a different focuser and says so). Seeing, temperature, filters and a moved focus position do not need it.
To test it: move the focuser off by a few hundred steps, then click Refocus (optionally choosing a filter first). It measures the stars where the focuser stands, sweeps a range sized from them and reports "focus point found at position X". Go to focus drives the focuser straight back to the last focus; Forget First Light throws the set-up away (you'll need to run it again).
Build a sequence
Go to Sequencer.
- Click New. Give the plan a name and a File id. Pick a Filter order: Cycle filters (one frame of each filter in turn) or One filter at a time (all of one filter, then the next).
- Targets tab → + Add target → enter a name, then fill RA/Dec one of three ways: ⌖ SESAME (resolve the name via CDS Sesame, or from the built-in OpenNGC catalogue when the servers cannot be reached), ⊙ Use current (adopt the mount's current pointing), or ↩ CdC (pull the selected object from Cartes du Ciel). Add exposures with + Add row — each row is a Filter, Frame type, Exposure (s), Count, Bin and Gain.
- Constraints tab → set altitude min/max (e.g. 30° minimum), hour-angle limits, or an end-by time. A tripped altitude/HA limit skips that target and moves on rather than aborting the run.
- Focus tab → enable refocus triggers: every N frames, every X minutes, on filter change, or on focuser temperature drift. (During a run these fire Refocus, using First Light's formula; a plan never runs First Light itself. A mid-run refocus failure is journaled but doesn't abort.) You can also set a fallback focuser position.
- Cooling tab → tick "Cool sensor before first capture", optionally with a setpoint override and "Wait for settle". If settle is required and cooling fails, the sequence aborts.
- Guiding tab → optional PHD2 guiding + dither cadence (only acts when PHD2 control is enabled in Settings).
- Meridian tab → for German-equatorial mounts, choose ignore / halt / flip and set how far past the meridian to act, plus recenter-after-flip.
- On Start / On Error / On Suspend / On Resume / On End tabs → the actions that wrap the run. On Start opens the roof, unparks, points precisely and autofocuses; On End parks, closes the roof and warms the camera so the rig is always left safe. On Error and On Suspend make the rig safe if something goes wrong or an unsafe event pauses the run.
Validate to check the plan, Save, then ▶ Start sequence. Watch the journal scroll. (You can also Save as scheduler recipe to hand the plan to the multi-night scheduler.)
Things that go wrong
- Equipment won't connect: check it works in its own driver / setup tool first. If yes, look at the tile / badge error message. If no, fix it there before retrying in Starship.
- Nothing rises / altitude and scheduler misbehave: your Site coordinates are probably still zero. Set real latitude/longitude/elevation in Settings → Site / Location.
- Autofocus can't bracket the V ("re-center near focus"): the sweep couldn't find a clean minimum — usually starting too far off focus, thin cloud / poor transparency, or a drifting mount. Re-center on a star field, confirm tracking, get roughly focused first, and retry when the sky is steady.
- Sequence aborts at the first slew: check the mount is unparked and tracking enabled.
- Capture progress hangs near the end: image download from the camera is slow or stalled; check the USB connection / cable.
- Anything weird at 3am: the Audit log keeps a hash-chained record of every command, verdict, and event. Postmortem is straightforward.
Where to next
- Help button (
?) in the top-right opens this help system anywhere - Keyboard
?orF1shortcut anywhere except inside text fields - Roadmap topic shows what's built, coming, and deferred
- Changelog topic lists what landed in each version
For deeper specifics, browse the Modules and Reference sections.