I relayed your concern to QHY, hopefully they can investigate the issue.

I jumped on the QHY forum to point out the challenges we've been having with their driver and asked them what their commitment is to Linux, in particular INDI. Perhaps those of us with QHY devices can add their thoughts on that thread. We're probably a small part of their overall market, but every little bit helps. (I did it as nicely as I could in case you are wondering ...

jmh

nice one thanks, found your thread en.coolccd.com/bbs/index.php?topic=6693.msg34578

Regarding the Orion SSAG with the QHY drivers. I installed the nightly bleeding version to test the new build with the patched SDK but am still experiencing same/similar issues.
The new Orion SSAG driver crashes with Orion SSAG. Is it only meant for the imaging cameras such as the G3 Deep Space mono cam?
The QHY driver still has issues from aborting images. I receive this error when I test image capture and aborts. Sometimes it just crashes too.

If you can post the detailed log, we can forward it to QHY. This is an issue with QHYSDK, not INDI. So it has to be fixed from QHY.

I will try to provide those when I get the chance.
Incidentally I can probably get in touch with a local who was part of the QHY driver development team for windows through an acquaintance. Maybe they can help.

Sorry for the delay. I have logged some tests of the Orion SSAG failing after aborted exposure. Here are relevant excerpts with description, and full log.

Perhaps those of us with QHY devices can add their thoughts on that thread. We're probably a small part of their overall market, but every little bit helps. (I did it as nicely as I could in case you are wondering ..

Try version indi-qhy-bleeding-1.7.5-28.1. (Issue #765, Pull Request #766)

-Chris

That appears to have done the trick!
Thank you.

Not sure if it belongs here. I'm reinstalling Ubuntu Mate on my Odroid XU4 and RPi3, starts to look good but I noticed a strange behaviour of QHY9s camera.
Looks like the sensor temperature is not updated automatically, I receive relevant data after several hits of "set" button but cooling power adjusts with a delay (that's normal) leading to unpredictable temperature. example: EKOS/INDI shows 5C, 100% power and after some time of no visble change I try to update and temp is way below pre-set. Am I the only one?

As a result I noticed fog on the sensor and now trying to dry it up.

HoHr: Maybe check the Polling Period in the driver's options tab. Set it to something reasonable if it is not already.