The plugin logs everything it decides and does. Most issues resolve to one of the patterns below.
Reading the Log #
Open NINA’s log (or the Astro PM log panel) and filter for AstroPM |. You will find the schedule build (targets fetched, settings applied, blocks created), every block transition, every capture, and every warning with a reason. When asking for help, these lines are gold.
No Targets Scheduled #
- Are the projects Active with remaining exposures? Planning/On Hold projects are not scheduled.
- Is the right imaging system selected in plugin Options? Targets are filtered to the rig’s site/scope/camera.
- Is the sync token entered and the cloud reachable (or a cache present)?
- Trial licenses push a limited number of targets to the cloud – see licensing.
Schedule Differs from the Desktop #
- Location mismatch – the NINA profile’s observatory coordinates must match the site (the plugin warns about this).
- Version mismatch – app and plugin must be the same version; the engine evolves in lockstep.
- Horizon mismatch – NINA’s custom horizon file should match the site’s horizon in Astro PM.
- Stale settings – settings flow at schedule build; if you changed strategy mid-day, the rig picks it up at the next build.
Flats Did Not Run #
- Is Enable Flats Sequence on for this rig (desktop simulator checkbox)?
- Are there instructions in the For Each Target + Filter + Rotation box?
- Did any lights capture that night? No combinations recorded means nothing to take flats for.
- Check the log for
AstroPM | Flats:lines – they narrate recording, rotator moves, and each combination pass.
Still Stuck? #
Use the feedback link at the bottom of any doc, or contact support with your app + plugin versions and the relevant AstroPM | log lines.