Hi everyone
Latest 3.5.8 stable.
The camera works fine for several hours then:

[2023-12-20T01:42:11.234 CET INFO ][ org.kde.kstars.indi] - Astroshop veTEC571C(USB2.0) : "[ERROR] Camera disconnected "
[2023-12-20T01:42:11.485 CET INFO ][ org.kde.kstars.indi] - Astroshop veTEC571C(USB2.0) : "[ERROR] get Temperature error. Generic failure "

It seems to be associated with a call to align which hjappens immediately before the camera disconneCt.
Any ideas anyone? Could this be anything to do with the new libomegonpro SDK?

log: drive.google.com/file/d/1Kw_XpFXj99YDfcX.../view?usp=drive_link

TIA,
Steve

I have this camera, anyway to reproduce this step by step?

Hi and thanks for taking a look.

Simply make serveral scheduler jobs which involve a MF in different parts of the sky. One of them will disconnect the camera.

I thought this maybe due to cable drag or power issues, but I have substituted all cables and PSUs.

I can confirm that stopping scheduler jobs before and restarting them after the MF, the camera remains connected and the scheduler runs all night.
Here is the log from an all night non-MF session: drive.google.com/file/d/1vr376u4FMRs8Ptf.../view?usp=drive_link
Thanks,
Steve

Here it is, looks like the same issue as indilib.org/forum/ekos/14126-camera-driv...r-meridian-flip.html

So we're starting to see this more reported, which is starting to confirm my suspicion that it's not single system related, and not ZWO-only either

I believe we identified and issue and working on a fix: invent.kde.org/education/kstars/-/merge_requests/1080

If all goes well, we'll release and backport to 3.6.8 today.

@Jasem, just went through the MR, I thought for completeness I'd let you know: since after a flip there is a realign which will take at least 2-3 minutes between capturing, platesolving and restarting guiding, ample time has passed before capture resumes, so the pier state is always correctly reported, at least in my case.

The problem, which I confirmed yesterday in my observatory, is that MF immediately declares failure after starting. This leads to capture aborting then resuming later but MF continues to try to fix itself which make matters worse.

Understood, I will take a look at my logs again to see if MF Reports a failed status. You can find them attached to the OP of that other thread if they are useful to you.
Thanks for looking into this!

Hi
Is this the fix?
github.com/KDE/kstars/commit/b5d1c842572...95c31b2851e6ec9ed277

Would it be possible to include in the stable ppa?

**EDIT using: Build: 2023-12-26T04:50:24Z
Test with the simulators with various MFs all successful. Log attached.
Yet to test with hardware.
Thanks

After three clean sessions with thew latest stable, the camera disconnnects again after the meridian flip. Sn NOT soplved here.
Log attached.

Could be cable issue ? The driver reports the camera was disconnected on its own:

Thanks Jasem. Here's hoping.
Question if I may? Which cable type do you use with your veTEC?
TIA