×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Read More...

scheduler: failed meridian flip

  • Posts: 969
  • Thank you received: 94

scheduler: failed park at end of astro dark was created by alacant

Hi everyone

Would really appreciate help understanding why the mount didn't park this time
esq, .esl and log here:
drive.google.com/drive/folders/1qjrR2Pod...b6D03143?usp=sharing

TIA and clear skies,
Steve 
Last edit: 2 years 7 months ago by alacant.
2 years 7 months ago #74696

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

Replied by Jasem Mutlaq on topic scheduler: failed meridian flip

There is nothing on meridian flip at all in the log, not even an attempt to trigger it. Was the Meridian Flip box checked in Mount module?
2 years 7 months ago #74710

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

  • Posts: 969
  • Thank you received: 94

Replied by alacant on topic scheduler: failed meridian flip

Apologies. Wrong problem.
The meridian flip was fine.
The issue should have been that the mount didn't park.

I've edited the title. Should I start a new thread?

TIA
Last edit: 2 years 7 months ago by alacant.
2 years 7 months ago #74713

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

  • Posts: 1185
  • Thank you received: 370

Replied by Wolfgang Reissenberger on topic scheduler: failed meridian flip

what time does the twilight constraint show currently? That would be helpful to plough through the logfile...
2 years 7 months ago #74745

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

  • Posts: 969
  • Thank you received: 94

Replied by alacant on topic scheduler: failed meridian flip

Hi Wolfgang and thanks for taking a look.

twilight: 22:04 - 05:46
2 years 7 months ago #74746

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

  • Posts: 1185
  • Thank you received: 370

Replied by Wolfgang Reissenberger on topic scheduler: failed meridian flip

I cannot find any hint in the log file that the scheduler tried a shutdown. It seems like all conditions that lead to a shutdown are not met:
  1. Preemptive shutdown is selected and next observation time > preemptiveShutdownTime *3600
  2. next observation time > leadTime * 60 & park mount is checked
  3. next observation time > leadTime * 60
In all three cases there should be a log entry on INFO level. The last case is a "catch all" which does not trigger anything, but it will also create a log entry.

Currently, I have only one possible explanation. Could you please check the lead time option value under Ekos | Scheduler? 

Last question: the scheduler stops at 06:43:18. This is almost exactly 1h after the twilight limit. Did you stop it manually?

Cheers
Wolfgang
The following user(s) said Thank You: alacant
2 years 7 months ago #74749

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

  • Posts: 969
  • Thank you received: 94

Replied by alacant on topic scheduler: failed meridian flip

Lead time: 5,00
Pre-dawn: 10,00
Pre-emptive shutdown (checked): 2,00
Setting altitude cutoff: 3,00
Dusk offset: -0,30
Dawn offset: 0,00

Yes, I shut down manually.

TIA
2 years 7 months ago #74760

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

  • Posts: 1185
  • Thank you received: 370

Replied by Wolfgang Reissenberger on topic scheduler: failed meridian flip

Hi Steve,
I'm sorry, but I cannot find an explanation why this happened. This check is executed once a second by the scheduler and obviously, it never evaluates to true:
   // #4 Check if we're not at dawn - dawn is still next event before dusk, and early dawn is past
    if (currentJob->getEnforceTwilight() && ((Dawn < Dusk && preDawnDateTime < now) || (Dusk < Dawn)))
    {
        // If either mount or dome are not parked, we shutdown if we approach dawn
        if (isMountParked() == false || (parkDomeCheck->isEnabled() && isDomeParked() == false))
But to be honest, I have no clue why it doesn't become true as soon as dawn is reached.
The following user(s) said Thank You: alacant
2 years 7 months ago #75007

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

Time to create page: 0.249 seconds