Filter wheel
A filter wheel selects which optical filter sits in front of the camera for an exposure. SkyNode treats filter wheels as independently-controlled devices that the optical imaging task executor commands between exposures.
Config shape
Section titled “Config shape”{ "device_type": "filter_wheel", "driver": "filter_wheel.ascom" | "filter_wheel.maxim" | "filter_wheel.simulator", "managed_by": "this_node", "driver_configs": { "filter_wheel.ascom": { /* see below */ }, "filter_wheel.maxim": { /* see below */ }, "filter_wheel.simulator": { /* see below */ } }}The slot-to-filter mapping is not in the device config — it’s managed centrally on the hub (FilterWheelPosition records linking filter wheel slots to Filter records). The task executor uses that mapping to pick the correct slot for a request’s selected filter.
Drivers
Section titled “Drivers”filter_wheel.ascom — production
Section titled “filter_wheel.ascom — production”For any ASCOM-conformant filter wheel on Windows.
"filter_wheel.ascom": { "prog_id": "ASCOM.FLI.FilterWheel", "move_timeout_sec": 60.0, "poll_interval_sec": 0.25}| Key | Meaning |
|---|---|
prog_id |
ASCOM ProgID of the filter wheel driver. Examples: ASCOM.FLI.FilterWheel, ASCOM.QHYCFW.FilterWheel, ASCOM.Simulator.FilterWheel |
move_timeout_sec |
How long SkyNode waits for a move to complete. Default 60 seconds |
poll_interval_sec |
How often SkyNode checks for move completion. Default 0.25 seconds |
In the app, Configure driver on the device’s Settings page opens the ASCOM Chooser and stores the ProgID you pick.
filter_wheel.maxim — production
Section titled “filter_wheel.maxim — production”For MaxIm DL-driven cameras that include the filter wheel as a sibling device. SkyNode commands the filter wheel through MaxIm’s COM API.
"filter_wheel.maxim": { "move_timeout_sec": 60.0, "poll_interval_sec": 0.5}| Key | Meaning |
|---|---|
move_timeout_sec |
How long SkyNode waits for a filter-wheel move to complete before marking it stalled. Default 60 seconds; raise for big filter wheels with long mechanical settles |
poll_interval_sec |
How often SkyNode checks MaxIm for move completion. Default 0.5 seconds |
recommand_interval_sec |
How often SkyNode re-sends the move while the wheel hasn’t reached the slot. Default 5 seconds |
settle_confirm_sec |
How long the wheel must hold the target slot before the move counts as done. Default 0.5 seconds |
Notes:
- The MaxIm filter wheel driver is paired with the MaxIm camera driver. Both bind to the same MaxIm process.
filter_wheel.simulator — testing only
Section titled “filter_wheel.simulator — testing only”Paper filter wheel. Moves to any slot instantly and reports success.
"filter_wheel.simulator": {}Troubleshooting
Section titled “Troubleshooting”- “Filter changes don’t happen between exposures.” The task executor only commands filter changes when an exposure specifies a different filter. Verify on Controls → Filter wheel (in MANUAL control) — manually select filters and confirm the wheel responds.
- “Wheel reports the wrong filter.” The slot-to-filter mapping on the hub (
FilterWheelPositionrecords) is out of sync with the physical wheel. Update through the telescope settings page in the web app. - “Wheel takes forever to settle.” Some wheels report “complete” before mechanical settling. If you see image vignetting or filter-misalignment artifacts, the
move_timeout_secisn’t the issue — you need a filter-driver setting (in the ASCOM or MaxIm app) that holds the move- complete signal longer.