Just read my message again - I know EKOS doesn't control the temperature. Apologies if the implication was otherwise. QHY needs to find an engineer who understand this stuff to fix. Probably won't be dealt with until the world get through COVID-19... stay safe everyone.
Mine is a qhy294c running on kstars 3.4.2.
After upgrade to 3.4.2 the temperature control is broken and the temperature would oscilating between 5-6 degree around the set temperature.
Sometimes if it set the temperature to requires 60-70% of 5he cooler power after 10 minutes the temperature would settle. But if I push the cooler to over 80% then the temperature and cooler power just jump around.
If the temperature set at -15 degree, it wont keep the temperature stable
If the temperature is set at -12 degree (rquire abt 63% of the cooler power) then after 10 minutes it would stablize
Please report this to QHY. Thanks for your help and sorry for the broken English
Thank you. Now, how do I revert my libqhy and indi-qhy to the previous version? I search all over the forum and could not seem to find it.
I try the latest firmware on windows via sharpcap and the problem is not there. Seems it only on linux version of the sdk. What a shame!
I have always issue with saved configuration. At the next session, the QHY parameter are not well recovered. Often the offset is 0 when I saved 3. Same for USB trafic. It back to 30 value instead of 0 saved.
Do I have to load a right configuration or is these saved that will be load?
It is automatically loaded by default. Check under ~/.indi and check the values in the QHY config file there.. they correspond to the same ones you expect? Check the permission of the file.. can it be written over by you?
join to this message the QHY183C XML configuration file and a screen capture of the Indi panel just after connection. Curiously, the parameter USB Buffer doesn't exist in the file. The XML .default file, all the value are 30.
I too have a QHY163 (mono version though) and am using the same version of the SDK you are using with no issues. I would like to see temperature control a little tighter but +/- 0.3 is ok. Other than that, no issues.
Perhaps there are other issues: power, cabling, USB ports, etc. From your sig, I noticed you may be running on an ARM system (RP4, Tinker Board), I've moved from ARM based systems back to an Intel based NUC with much more success and stability. The newer cameras with USB3 are more demanding and push the limits of the ARM based systems.
Hi jmh, i have been debugging it today after issues last night. So a summary; the tinker board is stable no issues so no more updates for it. I use it when im doing a serious imaging run as it works perfectly. The rpi4 is a build in progress.
So i had not updated the rpi4 since the end of February 2020 as it was working ok. After the issues last night (mainly with guiding) i decide to do a full update and then the qhy issue started. The qhy and the zwo asi224 (guider) are both connected via USB3.
This morning i tried again with no luck. So i connected the qhy to the USB2 port instead of the USB3 port and presto, it worked. When i connected back to the USB3 port, the thing works.. All power connections we the same as last night after the upgrade. I then ran everything (mount via wifi, guider, imaging camera with cooling etc and everything is working under both USB2 and USB3. Really weird, i cant explain it.
I have read elsewhere on the forum issues with using USB3 and 2.4G wifi (which is how i remote to the rpi4). I switched to 5G wifi with no issues, except my mount connects via wifi and the shywatcher wifi dongles do not support 5G wifi, so i have to stick with 2.4G or go back to USB eqdirect.
Anyways, ill give it another go tonight. Maybe it is just scared of the dark
Lots of trial and error, mainly error, but in hindsight, it was easy!!!
Takahashi FC100DF imaging scope, Orion 50mm guide scope
Skywatcher HEQ5 Pro via Wifi
ZWO ASI 224MC guiding
DIY Astroberry focuser
Tinker Board (Lbuntu 18.04LTS), Raspberry Pi 4 (Raspbian)