1. 24 May, 2022 5 commits
  2. 23 May, 2022 3 commits
  3. 21 May, 2022 3 commits
  4. 20 May, 2022 5 commits
  5. 19 May, 2022 2 commits
  6. 18 May, 2022 4 commits
  7. 16 May, 2022 1 commit
  8. 15 May, 2022 1 commit
    • Wolfgang Reissenberger's avatar
      Bugfix for PHD2 guiding - restart guiding after lost star · 768dee8f
      Wolfgang Reissenberger authored and Jasem Mutlaq's avatar Jasem Mutlaq committed
      Restarting guiding after a lost star event can lead to the situation that `Guide` switches to the calibration state while the `PHD2` remains in the stopped stage. If in this case guiding needs to be stopped again (e.g. there is no guiding star visible), `PHD2` does not send an abort event and `Guide` remains in the calibration state.
      
      This is fixed by this change. Additionally, a dedicated dithering state is introduced for `PHD2` to separate calibration from dithering.
      768dee8f
  9. 12 May, 2022 1 commit
  10. 10 May, 2022 3 commits
    • Wolfgang Reissenberger's avatar
      Capture state machine | introducing device adaptor · 98ef723d
      Wolfgang Reissenberger authored and Jasem Mutlaq's avatar Jasem Mutlaq committed
      Next step extracting state handling from `Capture` into a dedicated state machine. In this step devices are managed by a dedicated device adaptor (successor of the command processor). With this refactoring it is no longer necessary to route device events from `Capture` through `SequenceJob` to the state machine, the device adaptor sends the events directly to the state machine.
      
      Additionally, this change contains a bug fix for temperature handling.
      98ef723d
    • Wolfgang Reissenberger's avatar
      Bugfix for aborted jobs handling in the scheduler · b6405747
      Wolfgang Reissenberger authored and Jasem Mutlaq's avatar Jasem Mutlaq committed
      This is a bug fix for the aborted job handling of the scheduler. Instead of waiting for the configured amount of time before restarting an aborted job, jobs start immediately.
      
      This is due to a concurrency issue. Failure of alignment etc. is communicated in a separate thread as event to the scheduler. When the scheduler is running, it has a timer the triggers scheduler iterations. In order to communicate the delay, it is necessary to stop the scheduler loop, set the delay as timeout and restart the scheduler loop.
      
      To test it, take a simple schedule where alignment is necessary and set the capture time in alignment to 0.1 sec so that alignment fails. Start the scheduler and check what happens if the scheduler aborts the job due to alignment failure. 
      
      Without this fix, if "Immediate" is selected, the aborted job immediately starts and not after the configured delay of typical 2min. In the case of "Queue", the scheduler shuts down the observatory.
      b6405747
    • Jasem Mutlaq's avatar
      Add EkosLive shim to scheduler · 7320acf0
      Jasem Mutlaq authored
      7320acf0
  11. 07 May, 2022 2 commits
  12. 06 May, 2022 1 commit
  13. 05 May, 2022 1 commit
  14. 30 Apr, 2022 1 commit
  15. 29 Apr, 2022 1 commit
  16. 26 Apr, 2022 1 commit
    • Wolfgang Reissenberger's avatar
      Bugfix for aborting guiding while dithering · 077e00ee
      Wolfgang Reissenberger authored and Jasem Mutlaq's avatar Jasem Mutlaq committed
      When the scheduler option for target drifting is enabled, and a re-alignment is necessary, the guiding module state might get out of sync with PHD2. To test this case:
      - Enable target drift and set the maximal distance to 0 so that re-alignment always happens
      - Ensure that the option "Abort autoguide on failure" is disabled in the guiding options for dithering
      - Enable dithering
      - Start a scheduler job with tracking, alignment and guiding enabled (use PHD2 for guiding)
      After the first capture and the subsequent alignment it might happen that guiding reports that guiding was already running but it doesn't. As a consequence, the scheduler is waiting infinitely long for guiding to start.
      077e00ee
  17. 25 Apr, 2022 2 commits
  18. 24 Apr, 2022 3 commits