Hopefully it is fixed now in 3.2. Nevertheless please be so kind and provide the logs so that Eric or I can check it.

Regarding the meridian flip: this has also been reworked to fix other issues. Part of this rework was a change to DBUS communication. There was a problem with DBUS on Macs.

Cheers
Wolfgang

There is indeed a problem with the scheduler behaving as you described. Please check if „Remember job progress“ is selected in the Ekos options. In the combination with the completion condition „Repeat until terminated“, the scheduler jumps directly to capturing stating in the log that only calibration frames were pending.

Is that the case for you? If yes, as intermediate solution, turn off the „Remember job progress“ option. I‘ll try to fix it asap.

Wolfgang

@Jasem: I've submitted a diff hopefully fixing this issue: phabricator.kde.org/D20682

Wolfgang

thanks! it's pushed.

That was exactly the problem. Thank you!!

The scheduler ran as intended, but no meridian flip happened. I d have it set to flip at .1 past the meridian but it didn’t do it.

I am in the middle of trying to image now and I’m pretty sure I’m on KStars v3.2.2 and it’s doing exactly the same thing here now, which is most annoying. I get the spinning wheel with “No jobs running”

I’m using a StellarMate and also driving it from a Mac.

I’ll try to send the logs through tomorrow

Please find attached the logs from last night with the scheduler not starting jobs. I'e put a screen shot in here as well just to show what the screen looked like

In your log file there is one strange thing: at 2019-05-26T19:33:33.214 AEST there is a message that EKOS is not ready which leads to a pausing of the Scheduler.

This explains the behaviour. But I cannot explain why EKOS is not ready.

@knro: Do you have an explanation?

- Wolfgang

I’m getting ready to put out the 3.2.3 dmg for Mac based on the latest code. Did this scheduler problem get resolved or would you like to test the dmg first to see if it is resolved? I know there were scheduler issues on both Mac and Linux. Back on 3.1 Part of it was DBUS was broken in the build by the switch to craft. But I fixed that. So I think this is not Mac specific correct ?

It does not look like a Mac specific issue. From my perspective it looks more like either an issue with the internal guider or with the setup using simulators. All what I could see from the log files is that the Scheduler behaves correctly.

Ok so we are good to go for 3.2.3?