Hi!

I nailed this further down a bit after a few hours testing.
For all my tests I kept the inidlib and indi_qhy_ccd driver at these current git versions:

indi-qhy version origin/master:
commit 84b47a8d1b2766c9015ff54cb2404ce60ea14693
Author: Jasem Mutlaq <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Tue Jul 18 12:34:07 2023 +0300

indilib version origin/master:
commit f90db4e8cf87e3d990cb2b85900eeaab2e3fc428
Author: Jasem Mutlaq <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Thu Aug 31 12:33:16 2023 +0300

I only had to relink indi_qhy_ccd for the different major version numbers 20, 21, 22,23 of libqhy.
This was the only change in the test environment while I iterated through the libqhy-SDK versions.

The firmware image in the QHY600 camera was always on 23.7.16 for all my tests.
I can pretty much say that the problem described was not introduced by the camera firmware but by the SDK Libraries.
On the client side I had kstars-3.6.6 with indilib-2.0.3. I tested also XISF versus FITS compessed and uncompressed without any differences.

This is the latest error free SDK Version I have tested:
libqhy 22.11.9 git commit id: 995dd8bb21ee719ab85faed38e1dc1817c5d4d62 from Wed Nov 9 17:54:08 2022 +0300

The next version with libqhy 23.02.18 and git commit id: 37e72a8c586a0e154b40f064e98c8b0231667e65 from Sat Feb 18 21:40:33 2023 +0300
introduced the problem with the darkened pixel rows as described above.

As from my understanding and what Jasem told, the directory indi-3rdparty/libqhy contains only data from QHY and its not touched during linking the libraries.
But I don't know if this is enough to approach QHY now with this problem.
It could also be that QHY introduced changes between SDK 22.11.9 and 23.02.18 which must be reflected in driver code.
But I dont have access to release-notes or similar information.

If thats not the case I would say its on QHYs part now to analyze this deeper.
Any opinions are very welcome.

Best regards, Norman

Read More...