I have just rebuilt my OdroidXU4 and this new version of the QHY driver works wonderfully well.
Thank you for sorting this issue.
KStars/Ekos running on OdroidXU4 Ubuntu Mate on the Mount and RDP from laptop for remote access
Telescopes: Skywatcher ED80 & Altair Astro RC6
Mount: Skywatcher HEQ5
CCD: Atik 414EX
Guider: QHY5 on Skywatcher ST80
Looks like I am in the same boat as you. Both my PoleMaster and QHY5LII-C are throwing the [ERROR] GetQHYCCDSingleFrame error (-1) whenever EKOS requests a image to be taken. I can see the image being downloaded in QHY logs but the driver cancels the load.
Thank you for the good report. Here were my steps yesterday. I used Synaptic to see what QHY drivers and applications were installed. Then I removed any and all. After completion, I reinstalled indi-QHY. I will validate today what the state of both devices are in. Would you share any additional steps you took?
On a whim, I decided to check SYSLOG for any errors while testing my QHY devices with Polar Alignment and EKOS. I found the smoking gun. My error is in indi_qhy_ccd. The OS says using a USB before claiming it is the reason for the halt. I thought it strange for the QHY logs to yield an error when nothing previous to error indicated the need for an alert. Yes. The OS can stop KSTARS from operating.
Dec 30 09:00:43 astroberry kernel: [ 7592.169498] usb 1-126.96.36.199: usbfs: procesis 4686 (indi_qhy_ccd) did not claim interface 0 before use
This was a painful exercise. In EKOS profiles, Select Devices include 4 Auxiliary devices. In my decisions, I considered the three CCD devices as three separate uses. The ZWO for CCD, the PoleMaster for Polar Alignment, and the QHY5LII-C for guiding. Let me see... CCD and GUIDER are for ZWO and PoleMaster. The QHY5LII-C is Auxiliary 4.
Wrong! Just use INDI_QHY_CCD for Guiding and be done.
Setting up indi_QHY_CCD in two slots causes INDI to setup two instances of INDI_QHY_CCD. Having two instances of any driver causes multiple issues of communication. The error says that something is preventing the INDI_QHY_CCD driver from collecting the image. The Kernel is one such devices. The Kernel will say.
kernel: [28071.416886] usb 1-188.8.131.52: usbfs: process 10108 (indi_qhy_ccd) did not claim interface 0 before use
This stops that image process in its tracks. This closes the case for me.
PoleMaster and QHY5LII-C co-habitat under one instance of INDI_QHY_CCD. INDI_QHY_CCD resides in GUIDER or Auxiliary 4 but not both.