It is well known that this is an SDK issue. I identified the buggy SDK versions in this older post in this thread
Obviously QHY released several SDK releases without testing them. Very poor quality -- not just the software ...
BTW, I also submitted some patches to version 1.8.3 which where not considered: indilib.org/forum/development/6258-snoop...paches-to-1-8-3.html
for me, a few things in the indi package does not work as desired (I already reported some of the issues in the past) and I therefore use a patched version. I attached these patches for the latest version. Maybe some one wants to apply them to the main repository.
Gonzothegreat wrote: I'd like to run a little imaging competition, just for the fun of it.
All images must be taken using Indilib.
30 seconds unguided <-- screenshot must be provided of Ekos
data captured between the challenge start and end date
1 single submission of the image, no multiple entries
there is indeed some testing required -- by QHY. I'ts an issue of their SDK.
With the latest sources (QHY SDK 6.0.5) and my QHY163M the regulation stops after a while and the PWM value get stuck.
I rebuilt the driver with SDK 6.0.1. (had to comment out a new feature). Now it works, but its unstable: the PWM value jumps between a few percent and 90%. Because at least the 163's have a lot of power supply induced noise that's no solution.
I'll test which version is stable and send a report.
I'm currently setting up my observatory using INDI and recognized a few trivial issues which limit usability of INDI:
snprintf(name, MAXINDINAME, "MI CCD %s", sp);
snprintf(name, MAXINDINAME, "MI_CCD_%s-%d", sp, cameraId);