Hi all,

I have just rebuilt my OdroidXU4 and this new version of the QHY driver works wonderfully well.

Thank you for sorting this issue.

Chris

I can also confirm the latest driver works without issues with the QHYCDD 5L-II-M. Many thanks!

Hi,

I have a similar problem with my QHYIMG-0H camera, it connects successfully but fails when I try to capture a frame:
"[ERROR] GetQHYCCDSingleFrame error (-1) "

These are my first tests with Indi, so I am a bit "lost" and would need some help...

I am using the last stable release of Indi, installed yesterday following the instructions here:
indilib.org/download/raspberry-pi.html

I tried with a powered usb hub, but without differences.
I tried also with Indi installed in Ubuntu, on an other PC, same problem...

I would exclude a problem with the camera, it works well with PHD2 on Windows 7.

I add some logs, I hope they could be useful.
Thanks in advance !

Hello,

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.

HI, just reloaded my system with the latest indi drivers and both my QHY5LII-C, and PoleMaster are functioning correctly.

Hello,

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?

Hello,

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-1.2.4.1: usbfs: procesis 4686 (indi_qhy_ccd) did not claim interface 0 before use

Here is a link to the possible fix.

stackoverflow.com/questions/11088691/err...-claimed-from-libusb

Hello,

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-1.2.4.1: 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.

Makes sense. And reminds me of a similar case not long ago.
www.indilib.org/forum/ekos/6014-polar-al...-progress.html#45983

Perhaps a warning should popup whenever a profile is saved with duplicate drivers just to alert users of possible conflicts, without prohibiting it outright.

Actually Ekos already detects that and just starts a single driver, but I believe that check does not include Aux drivers. Will check if I can add them there soon.

It's done, please test now.

It just popped up again. Yesterday I refreshed indi from a version from somewhere back in october 2020. And started to get this:

2021-02-16T06:28:24: [INFO] Device configuration applied.
2021-02-16T06:28:24: [INFO] USB Buffer updated to 512
2021-02-16T06:28:24: [INFO] USB Traffic updated to 10
2021-02-16T06:28:24: [INFO] Speed updated to 1 2021-02-16T06:30:07: [ERROR] GetQHYCCDSingleFrame error (-1)

2021-02-16T06:28:24: [INFO] Offset updated to 110
2021-02-16T06:28:24: [INFO] Gain updated to 10
2021-02-16T06:28:24: [INFO] Upload settings set to client only.
2021-02-16T06:28:24: [INFO] Loading device configuration...
2021-02-16T06:28:24: [INFO] USB Traffic Settings: Value: 30 Min: 0 Max: 255 Step 13
2021-02-16T06:28:24: [INFO] Offset Settings: Value: 180 Min: 1 Max: 512 Step 1
2021-02-16T06:28:24: [INFO] Gain Settings: Value: 1 Min: 1 Max: 29 Step 1
2021-02-16T06:28:24: [INFO] USB Speed Settings: Value: 0 Min: 0 Max: 2 Step 1
2021-02-16T06:28:24: [INFO] Camera exposure limits: Min: 0.000001s Max: 3600s Step 0s
2021-02-16T06:28:24: [INFO] Using QHY SDK version 20.12.23
2021-02-16T06:28:23: [INFO] Connected to QHY5LII-M-60b7db50f33c7356.

The camera works fine on windows with driver downloaded from QHYCCD.

Same result on arm64 and x86-64.

Package: indi-qhy
Version: 2.7~202101090932~ubuntu20.04.1

I also tried the nightly - same result.



It just stops at zero remaining time and then - phd2 after a 15 sec timeout - tries to switch to streaming, which also fails:

indiserver -vvv indi_qhy_ccd

2021-02-16T06:59:58: Driver indi_qhy_ccd: read setNumberVector QHY CCD QHY5LII-M-60b7d CCD_EXPOSURE Busy
CCD_EXPOSURE_VALUE='0.029000000000000025757'
2021-02-16T06:59:58: Client 0: queuing <setNumberVector device='QHY CCD QHY5LII-M-60b7d' name='CCD_EXPOSURE'>
2021-02-16T06:59:58: Client 0: sending msg copy 1 nq 1:
<setNumberVector device="QHY CCD QHY5LII-M-60b7d" name="CCD_EXPOSURE" state="Busy" timeout="60" timestamp="2021-02-16T06:59:58">
<oneNumber name="CCD_EXPOSURE_VALUE">
0.029000000000000025757
</oneNumber>
</setNumberVector>

2021-02-16T06:59:58: Driver indi_qhy_ccd: read setNumberVector QHY CCD QHY5LII-M-60b7d CCD_EXPOSURE Busy
CCD_EXPOSURE_VALUE='0.019000000000000016875'
2021-02-16T06:59:58: Client 0: queuing <setNumberVector device='QHY CCD QHY5LII-M-60b7d' name='CCD_EXPOSURE'>
2021-02-16T06:59:58: Client 0: sending msg copy 1 nq 1:
<setNumberVector device="QHY CCD QHY5LII-M-60b7d" name="CCD_EXPOSURE" state="Busy" timeout="60" timestamp="2021-02-16T06:59:58">
<oneNumber name="CCD_EXPOSURE_VALUE">
0.019000000000000016875
</oneNumber>
</setNumberVector>

2021-02-16T06:59:58: Driver indi_qhy_ccd: read setNumberVector QHY CCD QHY5LII-M-60b7d CCD_EXPOSURE Busy
CCD_EXPOSURE_VALUE='0.0090000000000000079936'
2021-02-16T06:59:58: Client 0: queuing <setNumberVector device='QHY CCD QHY5LII-M-60b7d' name='CCD_EXPOSURE'>
2021-02-16T06:59:58: Client 0: sending msg copy 1 nq 1:
<setNumberVector device="QHY CCD QHY5LII-M-60b7d" name="CCD_EXPOSURE" state="Busy" timeout="60" timestamp="2021-02-16T06:59:58">
<oneNumber name="CCD_EXPOSURE_VALUE">
0.0090000000000000079936
</oneNumber>
</setNumberVector>

2021-02-16T06:59:58: Driver indi_qhy_ccd: read setNumberVector QHY CCD QHY5LII-M-60b7d CCD_EXPOSURE Busy
CCD_EXPOSURE_VALUE='0'
2021-02-16T06:59:58: Client 0: queuing <setNumberVector device='QHY CCD QHY5LII-M-60b7d' name='CCD_EXPOSURE'>
2021-02-16T06:59:58: Client 0: sending msg copy 1 nq 1:
<setNumberVector device="QHY CCD QHY5LII-M-60b7d" name="CCD_EXPOSURE" state="Busy" timeout="60" timestamp="2021-02-16T06:59:58">
<oneNumber name="CCD_EXPOSURE_VALUE">
0
</oneNumber>
</setNumberVector>

2021-02-16T07:00:12: Client 0: read newSwitchVector QHY CCD QHY5LII-M-60b7d CCD_VIDEO_STREAM
STREAM_ON='On'
2021-02-16T07:00:12: Driver indi_qhy_ccd: queuing responsible for <newSwitchVector device='QHY CCD QHY5LII-M-60b7d' name='CCD_VIDEO_STREAM'>
2021-02-16T07:00:12: Driver indi_qhy_ccd: sending msg copy 1 nq 1:
<newSwitchVector device="QHY CCD QHY5LII-M-60b7d" name="CCD_VIDEO_STREAM">
<oneSwitch name="STREAM_ON">
On
</oneSwitch>
</newSwitchVector>

2021-02-16T07:00:12: Driver indi_qhy_ccd: read message QHY CCD QHY5LII-M-60b7d '[INFO] Starting the video stream with target exposure 0.100000 s (Max theoritical FPS 10)'
2021-02-16T07:00:12: Client 0: queuing <message device='QHY CCD QHY5LII-M-60b7d' name=''>
2021-02-16T07:00:12: Driver indi_qhy_ccd: read message QHY CCD QHY5LII-M-60b7d '[INFO] For better streaming performance, set USB buffer to 2048 or higher.'
2021-02-16T07:00:12: Client 0: queuing <message device='QHY CCD QHY5LII-M-60b7d' name=''>
2021-02-16T07:00:12: Client 0: sending msg copy 1 nq 2:
<message device="QHY CCD QHY5LII-M-60b7d" timestamp="2021-02-16T07:00:12" message="[INFO] Starting the video stream with target exposure 0.100000 s (Max theoritical FPS 10)"/>

2021-02-16T07:00:12: Client 0: sending msg copy 1 nq 1:
<message device="QHY CCD QHY5LII-M-60b7d" timestamp="2021-02-16T07:00:12" message="[INFO] For better streaming performance, set USB buffer to 2048 or higher."/>

2021-02-16T07:00:12: Driver indi_qhy_ccd: read message QHY CCD QHY5LII-M-60b7d '[INFO] Starting video streaming with exposure 0 seconds (10 FPS)'
2021-02-16T07:00:12: Client 0: queuing <message device='QHY CCD QHY5LII-M-60b7d' name=''>
2021-02-16T07:00:12: Client 0: sending msg copy 1 nq 1:
<message device="QHY CCD QHY5LII-M-60b7d" timestamp="2021-02-16T07:00:12" message="[INFO] Starting video streaming with exposure 0 seconds (10 FPS)"/>