Page 1 of 1

Unexpected behaviour after focus scan aborts v4.1.13447

Posted: Sat Jul 12, 2025 1:55 am
by celkins
Robin,
I was running a focus scan on 2 instances, side by side: one aborted, producing a rather odd looking screen, that seems to still be showing new frames, based on the frame counter.
Please see screenshot for what I mean by strange.
SCv4.1.13447_AbortedFocusScan- 2025-07-12 023814.jpeg
SCv4.1.13447_AbortedFocusScan- 2025-07-12 023814.jpeg (954.49 KiB) Viewed 2529 times

Re: Unexpected behaviour after focus scan aborts v4.1.13447

Posted: Sat Jul 12, 2025 2:03 pm
by admin
Hi,

it's hard to be 100% certain, but it looks from the image and the log as though the focus scan failed due to not finding a proper 'U' shape (not enough range). At that point SharpCap tried to switch the camera back into live view mode and that switch seems to have become stuck, leaving you with a visible image but no camera controls.

Was that the end of the log completely at that point, or did you cut some more off? Just wondering as if there was anything else that might change the analysis.

cheers,

Robin

Re: Unexpected behaviour after focus scan aborts v4.1.13447

Posted: Sat Jul 12, 2025 8:40 pm
by celkins
There was more, but nothing out of the ordinary - just logging new frames coming in from the camera at the normal rate…

Re: Unexpected behaviour after focus scan aborts v4.1.13447

Posted: Sun Jul 13, 2025 12:52 pm
by admin
Hi,

OK, fair enough. The lack of the controls on the right is definitely an indication of the camera being in the process of a restart. Oddly, I'm not sure if the ZWO cameras strictly need a restart to change from live to still mode and back (QHY do). The code that requests that for ZWO cameras dates right back to the very first 'still mode' code added to SharpCap and that might have been a 'play it safe' choice at that point in time. I will check that when I have a ZWO camera to hand to see if I can remove the restart, which would be good all round, including probably removing the immediate cause of the problem here.

cheers,

Robin