Focuser
The focuser controls the focal-plane position to maintain sharp images across changing thermal conditions, filter changes, and optical alignment. SkyNode commands the focuser through manual operations and through the imager autofocus task.
Config shape
Section titled “Config shape”{ "device_type": "focuser", "driver": "focuser.ascom" | "focuser.simulator", "managed_by": "this_node", "driver_configs": { "focuser.ascom": { /* see below */ }, "focuser.simulator": { /* see below */ } }}Drivers
Section titled “Drivers”focuser.ascom — production
Section titled “focuser.ascom — production”For any ASCOM-conformant focuser on Windows.
"focuser.ascom": { "prog_id": "ASCOM.DriverHub.Focuser"}| Key | Meaning |
|---|---|
prog_id |
ASCOM ProgID of the focuser driver. Default ASCOM.DriverHub.Focuser — the ASCOM Driver Hub, which proxies to whatever focuser-specific driver you’ve configured inside Driver Hub. Set explicitly when you’d rather load a specific driver directly (ASCOM.OptecFocuser.Focuser, etc.) |
stall_timeout_sec, settle_timeout_sec, poll_interval_sec, position_tolerance |
Move supervision: see the note on moves below. poll_interval_sec defaults to 0.25; position_tolerance (default 1 count) is how close to the target a move must land |
In the app, Configure driver on the device’s Settings page opens the ASCOM Chooser and stores the ProgID you pick.
Notes:
- ASCOM focusers typically expose an absolute step position; the autofocus executor walks positions, takes exposures, fits a metric, and returns to the best position. The driver app’s step-size and step-range settings are what define the resolution available to the executor.
- Temperature compensation is optional and configured inside the ASCOM driver app, not in SkyNode. If your focuser supports it, enable it there.
- Moves are bounded by progress, not a fixed time. SkyNode keeps waiting while the focuser keeps getting closer to the target, so a slow focuser can take several minutes to cross its whole range. A move faults when the focuser reports moving but gets no closer for
stall_timeout_sec(default 90 s), when it stops short of the target and doesn’t settle withinsettle_timeout_sec(default 3 s), or when it passes 15 minutes in total.
Position range
Section titled “Position range”The min and max positions in SkyNode Settings → Focusers are the travel automation may use. The focus target for each exposure is the imager’s focus zero point plus the filter’s focus offset plus any temperature compensation. If that target falls outside the range, the task fails with a message naming the target and the range; SkyNode never quietly moves to the nearest limit instead. Autofocus checks its whole sweep the same way before it moves: every point plus the backlash take-up below the first, and the return to where the focuser started. A sweep that would leave the range is refused with a message naming the positions it needs, never run with its points stacked on the limit. When the ASCOM driver reports its own maximum (MaxStep), the settings page shows it under Max position with a Use driver value button, and the SkyNode log warns at connect when the two disagree.
focuser.simulator — testing only
Section titled “focuser.simulator — testing only”Paper focuser. Accepts step commands and reports the new position; doesn’t simulate optical defocus.
"focuser.simulator": {}Troubleshooting
Section titled “Troubleshooting”- “Autofocus never converges.” Three flavors: (1) the focuser range is too small relative to ambient drift, (2) the autofocus strategy’s step pattern is wrong for your scope, or (3) the image-quality metric the executor uses is being confused (saturated stars, clouds, very crowded fields). Inspect the autofocus log entries on the telescope log book via the website.
- “Focuser drifts during long exposures.” Without temperature compensation, mechanical thermal drift is the most common cause. Enable temperature compensation in the ASCOM driver app if available, or schedule periodic mid-night refocus runs.
- “Focuser target … is above the maximum position …” The focus zero point (plus filter offset and temperature compensation) is outside the focuser’s configured range, often a placeholder max left from setup. Raise the max position in Settings → Focusers (use the driver’s value) or correct the imager’s focus zero point. The task retries on its own once the setting is fixed; no restart is needed.
- “Autofocus refused: the focuser’s configured range is …” The sweep (points × step around the focuser’s position, or around each filter’s stored position) would leave the configured range. Fix the range or the zero point as above, move the focuser into range, or use fewer points or a smaller step.
- “focuser stopped at … and did not settle” The focuser stopped short of the target. Usual causes: the driver clamped or rejected the move (out of range, or temperature compensation on), or the focuser control software caps how long one move may run. If every move stops after about the same time no matter the distance, look for that cap in the focuser’s own software.
- “Focuser reports completion but image is still blurry.” Same family of issues as “autofocus never converges” — usually about step resolution or metric sensitivity rather than the driver itself.