And actually Ekos also uses the newly installed when I start the indiserver from there. So all I needed to do was to download, compile and install the latest indi_asi_ccd driver from github.
I can confirm that the problem disappears when connecting to an indiserver on the same laptop which is running the latest driver compiled from source! So I would hope time will solve the issue also for the internal Kstars indiserver in some future version.
I was wondering whether anybody else had this specific issue and found a solution:
Normally I run the ASI1600MM-PRO on a Raspberry Pi and it works just fine. Due to another problem I had to use a MacBook Air. This has only USB-C ports and to connect the camera I used an Apple adapter (the one with USB-C, USB-A and VGA). With this connection Ekos cannot establish a connection to the camera anymore. In the log the message is: "Unable to establish: + ZWO CCD". To me this appears to be a problem specific to the adapter and INDI, since the following things do work: with the same cable and adapter I can connect to the camera from the laptop just fine with the ASIStudio software. Inside with the desktop computer the camera happily communicates with Ekos, both with the same cable or a USB2 cable, when plugged-in directly to a USB-A port.
Thanks for any suggestions
I had the same problem, too. Replacing the QHY library as suggested by Hy fixed it — at least when test running the camera without anything else connected. When using with Ekos, the same problem persist when I use at the same time the INDI driver for the filter wheel QHYCFW2. When I disconnect it the camera takes again images happily.
The library version suggested by Hy in this thread solved the issue for me:
After re-installing the driver/SDK from indi version 1.7.8 it appears to be working, however returned image is all black.
Hi. I have a problem with the QHY5III178M and the latest driver (from master branch in github) for it.
I am trying to use it as a guide camera connected to a Raspberry Pi 4. For testing purposes it is the only thing connected to the Pi. The firmware seems to be loaded (lsusb lists the ID as 179 not 178, dmesg shows it at well). The driver connects to the camera fine. But when I want to get an exposure, it takes a long time after the exposure time is over and eventually the info comes that the exposure is restarted. The log shows some error message with SingleFrame failure error: -1. Now I found similar problem descriptions in the forum, so I would hope that someone can give me a hint to a solution. I should add that to my understanding it is not actually related to the indi-qhy driver, but the QHYCCD SDK. In fact a very similar error message is also shown as part of the output when running the qhy_ccd_test, the output of which I attach here
Awesome, I will check it out.
And what you say about also making it possible to set the Onstep weather data from INDI or some other connected device makes perfect sense to me!
Great, thanks! I guess the GUI tricked me and I am not sure whether I find it optimal to have the INDI driver debug settings in the Ekos logs somewhere instead of the INDI / driver settings, but most importantly, it's working now.