×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

guiding stops: scheduler does not recover

  • Posts: 969
  • Thank you received: 94
Hi everyone
Getting nowhere with this I'm afraid.
A cloud comes by and guiding stops, but capture continues. The scheduler .or whatever module is responsible- makes no attempt to restart the guiding.
Can anyone help?
Thanks,
Steve

log:
drive.google.com/open?id=1yVK-Cn8tRKMmpP6xAwbY8pnigIRoyTLD
Last edit: 4 years 4 months ago by alacant.
4 years 5 months ago #45076

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
Hi Steve,
looks like the aborted guiding just occurred between two captures. I did not try to reproduce it yet, but it seems like there is a weakness in the scheduler how it handles aborted guiding.

Here a short explanation: Currently, the scheduler only reacts upon guiding problems when it is in the guiding stage, i.e. when it starts guiding. In all other stages, guiding problems are handled by the capture module. Unfortunately, the capture module only reacts on guiding problems when a capture is active. In your case, the guiding aborted exactly between two frame captures and hence the capture module ignored it.

We need to take a closer look how it could be fixed. Meanwhile I do not see a workaround for this.

Thanks for reporting it.

- Wolfgang
The following user(s) said Thank You: alacant
4 years 5 months ago #45095

Please Log in or Create an account to join the conversation.

  • Posts: 969
  • Thank you received: 94
Hi Wolfgang and thanks for taking the time to explain.
If you need help testing any future coding of course, don't hesitate to send it my way. Really need this in the scheduler;)
Thanks again,
Steve
4 years 5 months ago #45097

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
Hi Steve,
it would be great if you try to reproduce this bug with simulators. If we have this as a test bed, we could try to fix it (although its not that easy with our two spaghetti monsters, the scheduler and the capture module :-P)

- Wolfgang
4 years 5 months ago #45098

Please Log in or Create an account to join the conversation.

  • Posts: 969
  • Thank you received: 94
OK. Do you mean setup a profile with pHD2 but using mount and ccd simulators instead of my actual eq6 and DSLR? And leave it running?
Would I need any hardware connecting?
4 years 5 months ago #45099

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
Exactly, no hardware, only INDI simulators for mount, CCD and guiding. You might need the star catalogue GSC installed.
4 years 5 months ago #45100

Please Log in or Create an account to join the conversation.

  • Posts: 969
  • Thank you received: 94
Hi Wolfgang
OK, here we are with the simulators. PHD2 stops guiding but capture continues.
Hope this helps with this issue.
Cheers,
Steve
The following user(s) said Thank You: Wolfgang Reissenberger
4 years 5 months ago #45104
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
Could you please briefly describe how you forced the dithering error?
4 years 5 months ago #45111

Please Log in or Create an account to join the conversation.

  • Posts: 969
  • Thank you received: 94
Hi. Hit the stop or loop button in phd2.
HTH
4 years 5 months ago #45112

Please Log in or Create an account to join the conversation.

  • Posts: 969
  • Thank you received: 94
Hi again
It is EKOS which tells PHD2 to stop guiding, as confirmed by the PHD2 devs:
groups.google.com/forum/m/#!topic/open-phd-guiding/XvDky04qo50
Could we lose the stop guiding requests perhaps, or if EKOS must stop the guiding, could it try again to start it at regular intervals?
Thanks,
Steve
Last edit: 4 years 4 months ago by alacant.
4 years 5 months ago #45128

Please Log in or Create an account to join the conversation.

  • Posts: 1185
  • Thank you received: 370
OK, I could reproduce it with simulators. Indeed, when guiding aborts after a capture sequence has completed, the scheduler does not check, whether guiding is running before it starts the next capture sequence.

I'll try to fix it.
- Wolfgang
4 years 4 months ago #45266

Please Log in or Create an account to join the conversation.

  • Posts: 969
  • Thank you received: 94
Hi Wolfgang
It's not only after a capture sequence ends, it is after any capture of any sequence. If the guiding has stopped for any capture in the sequence, it is not restarted for the next capture.

Great news that you will try to fix it.
Thanks so much for your time.
Steve
4 years 4 months ago #45267

Please Log in or Create an account to join the conversation.

Time to create page: 0.584 seconds