I'm doing some tests with the scheduler today.
I have the roof driver, the eqmod and a ccd simulator.

I setup my target as seen in the below screenshot.



I start the job, it opens the roof, unpark the mount but the mount is not slewing at all, takes the 5 pictures then goes into mount park and closes the roof.

Here's the output in the message box:

Your schedule job seems to be complete before starting. Either rename your target, or move the captures away from the sequence storage. You can also disable option "remember job progress" in Ekos options to completely disregard capture storage.

@knro when is the next official release? It would be interesting for users to have the latest commits for the scheduler.

-Eric

And you seem to trigger a known bug with filter wheel names. I've not checked your log thoroughly yet.

-Eric

Let me give that a shot, going to start a new job from scratch.

Nothing has changed after i disabled this option in Ekos, the mount is not moving at all.

Interesting as I am not using the filter wheel during this test.

ignore the previous log please, I had not realised it also recorded previous stuff.
Attached the trimmed down version regarding my test only.

Just in case something was wrong with the mount, I've done the following test outside the scheduler.
Using the same drivers, unparked the roof and mount, slewed to target OK, parked the mount and roof.

I think I might know what's going on.... I did not tick the 'track' button testing this now.

OK I parsed what seems to be your scenario:
- 10:45 start scheduler
- 10:46:37 roof is open (fascinating!)
- 10:46:38 dome considered open
- 10:46:39 unparking mount
- 10:46:40 mount considered unparked
- 10:46:42 job Kocab executes
- 10:46:43 filter changes to Luminance on the CCD simulator
- then capture starts

I don't see any request for slewing to the target... Your sequence doesn't seem to be calibration frames, there would be a log about this.

Could you share the .esq and .esl? I have nearly the same setup (except the roof!) so I can try to reproduce the problem. I'll try the dome simulator too.

-Eric

Eric, thanks for looking into this, I think the issue is with the lack of the 'track' option ticked...
I'm now trying to redo my test but I now get: failed to start Ekos

I see there are QT connect errors in your log. I observed this recently somewhere else, apparently due to an incompatibility between QT versions. I'll check this.

To verify this could be the root cause:
- you need to have Track enabled for your mount to move
- so edit your job, check Track, and save
- now re-edit your job: is Track properly checked?

-Eric