×

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

Bi-monthly release with minor bug fixes and improvements

Scheduler - guider calibration - how to enforce re-calibration

  • Posts: 910
  • Thank you received: 86
Hello,
Tried the scheduler for the first time (!).
When going from task to task the scheduler did all its things nicely except for it was using the same autoguider calibration for all tasks.
Am I missing some setting/checkmark?
I want the scheduler to clear and re-calibrate the guider before each step.
How do I do that?
Thanks!
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 2.
Last edit: 4 years 5 months ago by maxthebuilder.
4 years 5 months ago #44881

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

  • Posts: 1957
  • Thank you received: 420
The setting for this can be found in the Ekos section of the KStars settings:

The following user(s) said Thank You: Eric, maxthebuilder
4 years 5 months ago #44882
Attachments:

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

  • Posts: 910
  • Thank you received: 86
Aahh.. That must be it - thanks!
(it's enabled by default though). Will try next night.
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 2.
Last edit: 4 years 5 months ago by maxthebuilder.
4 years 5 months ago #44883

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

  • Posts: 1957
  • Thank you received: 420
Perhaps make sure to have enabled logging before starting? That way if the guiding calibration isn't cleared we can have a look at the logs to see what's happening.
4 years 5 months ago #44885

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

  • Posts: 910
  • Thank you received: 86
Will do. Thanks!
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 2.
4 years 5 months ago #44886

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

  • Posts: 77
  • Thank you received: 16
I have observed this same problem (bug) in recent weeks running the KStars nightly builds. On a recent imaging run (10-3-19?) where I had the scheduler set to image some time on M31 and then move to M33, the internal guide module did not re-calibrate after moving to M33 but just resumed guiding and of course did not have a star in the guide box (set at size 64) so was unable to guide. The option "Always Reset Guide Calibration" was selected. I intervened manually, deleted the earlier guider calibration which was from M31 and the guide module then re calibrated and I restarted the job which then continued to to run. Unfortunately I did not have logging on.

I am able to repeat this same issue with the simulators and have attached a log from the test simulation run I did. As in the real case the M31 guide calibration ran fine and the imaging run of M 31 goes fine. At line 2452 in the log the auto guiding starts for the M33 target and does NOT re-calibrate (the option is selected in EKOS configuration) and just gets lost trying to guide while the imaging module continues to run. This test was ran on 10-14-19 with the latest nightly build (at the time).

As a point I noticed during my time running a schedule - If the mount does a meridian flip between targets it does re-calibrate properly.

I ran this test on a Tinkerboard running the NAFABox build of Armbian Ubuntu 18.04. I have observed the same issue on a Raspberry pi 3b+ running Ubunut Mate with KStars/Ekos nightly.

File Attachment:

File Name: log_15-38-50.txt
File Size:441 KB
The following user(s) said Thank You: maxthebuilder
Last edit: 4 years 5 months ago by Midwest Astronomer.
4 years 5 months ago #44935
Attachments:

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

  • Posts: 910
  • Thank you received: 86
Yes. It appears to be a bug...
I was using a recent Windows client.
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 2.
4 years 5 months ago #44938

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

  • Posts: 1185
  • Thank you received: 370
I can confirm the behavior. When slewing to a second target, guiding is not reset and even worse, the guiding star is not freshly selected.

A quick check into the code confirmed the finding. The option "always reset guide calibration" is a) only handled by the scheduler and b) there only if guiding failed.

As a workaround I would recommend setting the "guide deviation < x" option in the Capture module. This at least detects that the guiding fails and restarts it.

- Wolfgang
The following user(s) said Thank You: Wouter van Reeven, Midwest Astronomer
4 years 5 months ago #45004

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

  • Posts: 77
  • Thank you received: 16
Thanks for checking this out! Currently the clouds are in my way but will try your suggestion of using the guide deviation setting in the Capture module the next clear night I get. Thank you for your help Wolfgang!
Last edit: 4 years 5 months ago by Midwest Astronomer.
4 years 5 months ago #45011

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

Time to create page: 0.265 seconds