I have similar problem. I use EKOS with local profile. After latest upgrade, it silently does not connect the EFW device, even though it starts the driver. I changed EKOS profile to use INDI 'remotely' and start INDI server manually. Now it works again. Didn't have time to dig anything out of the logs yet.

Read More...

I set 'locked to G' in AF filter settings, so that it runs AF with G filter no matter what is the Capture's current filter.
I run AF at the beginning of each job, every N (usually 30) minutes, and when temperature drifts 0.7°C. The last two effectively randomize what would be in the filter wheel right before AF starts.
Yes, I do have AF Overscan too.

Read More...

I am out of home for the next three weeks.
I have zero offsets for everything but B. All filters locked to G for AF. Adaptive start position is enabled and temperature compensation coefficients are set for all filters to the same value.

Read More...

Btw, I have nonzero filter offset configured for my B filter only.

Read More...

I had a multiple jobs schedule last night. All lights jobs have Track, Align, Focus, and Guide boxes checked. Scheduler runs a few jobs successfully. Then next unlucky job slews to target and hangs right on initiating focus. I have not touched anything on UI by this point yet. I noticed the problem and hit just the Auto Focus button manually. It ran the focus, then Scheduler picks up from there and continues just fine.
The exact same thing happened twice: 18:49:44 and 20:05:41.

What exactly should I update in the esq file?

Read More...

I had a long schedule last night. A few jobs went through happily. Next job started, focused, aligned, switched filter wheel and sat idle. See around 00:47:50 in the log. At 00:51 I noticed that and hit the stop button in the Capture module (not the Scheduler). It cranked through its error handling and successfully restarted and kept working fine through the rest of the night.
This is not a new error. I saw it multiple times over last couple years. Sometimes, like this night, I see the sequence in Capture correct, just not running. Sometimes the sequence is empty, like not loaded from specified file.

I caught an even better one last night! I only shot H subs, so only one simple flats job at the end. But instead of having the '231115' prefix from the schedule's target name it borrowed the 'Rosette_11' prefix from the last executed lights job. This simple scenario used to work fine before and I had no updates last days. The only new thing last night was that my schedule has two groups of jobs cycling through each for a few hours.

3.6.7 Build: 2023-10-14T21:36:52Z, the latest from Ubuntu PPA. I saw this issue in 3.6.6 too, each night when I did RGB.

I collect flats each morning for each filter used during the night. I have a sequence file for that with 3 jobs for B/G/R filters configured as wall flats. I then add that sequence at the end of my schedule with target name set to date ("231110" in this case), so that the files end up in distinct folders. The B filter works fine. The rest, G and R, lose the target prefix and end up in the same folder every day. At least the counter is persistent so I don't lose yesterday's flats, but they all are in the same folder. (But it can't track the progress and keeps spinning in this job capturing more and more G and R flats until I stop it manually.) This behavior did not change in the last version. It was broken at least since 3.6.6, maybe even earlier.
See the logs. Scroll to circa 10:22:50. All the B images before that point had "seq prefix = 231110_Flat_B" and captured correctly. The G probe captures also have good looking prefix but as soon as it figured the right exposure and started saving images, it reverted to "seq prefix = Flat_G" and never went back. Same happens later for R.

I'd vote for the option of not just the old good Standard scheduler, that could still make certain decisions, but a definitely dumb scheduler that always simply runs jobs sequentially letting each job decide for how long it would run. In many cases the Greedy scheduler is helpful. In some cases I know precisely what I want.

Read More...

Hy,

Thanks for the pointers! It seems, your last point about culmination is the reason why it didn't work for me as I desired.

Read More...