Hello,

I'm having trouble getting Ekos to find the qhy5 guide camera in my setup. I'm running an indi server on Raspberry Pi; here's what the indi server says about QHY5 on startup:

Once I try to connect, though, Ekos doesn't see the camera. It sees everything else (mount, filter wheel, imaging cam, focuser) but not the guide cam. I turned on logging in Ekos and tried to attach just the QHY5; the log is attached.

I wasn't sure the camera itself was the issue, but I tried it under Windows and it worked fine. The setup seemed to work several weeks ago after I upgraded to INDI 1.7.8. I say "seemed to" because I could only try it out in my living room. Today, I updated kstars, and I'm wondering if that could be the issue.

Versions:
INDI 1.7.8 on RPi
Kstars Build: 2019-05-30T09:48:47Z

Let me know if there's anything else I can provide.

Thanks,

Charles Wright

You need to contact QHY for this. They said recently that QHY5 is no longer supported and does not work in their SDK for Linux.

Well that's not very nice of them.

What if I revert to an earlier version of INDI? I see in the git log that QHYSDK v5.0.3 went in just before the INDI v1.7.7 release. Does that mean I need to go back to 1.7.6?

Thanks for any help,

Charles

Just to be clear in my mind, is the dropped support is specifically for the QHY5? I'm hoping (based on the 2019-04-08 linux note), it doesn't include the QHY5L-II-M ?

Well, it might mean that - the camera I'm using is precisely a QHY 5L-II-M, and if this really is the case, it's the second piece of QHY hardware rendered inoperable under Linux for me. Gotta sell these things to a happy Windows astronomer...

No, the QHY5L-II-M works just fine, I think they were referring to the 1st generation QHY5.

Won't the drivers provided by QHY before they withdrew support continue to work?

Right, but we use updated QHY SDK whenever it is released. We have to do this to keep with the bug fixes.

If the QHY5L-II-M works "just fine", then I would like to help people further diagnose the issue I am having, because that is the camera I have, and it is very much *not* working. I can provide more info later - perhaps it's due to an issue with the build or something? No idea...

Charles

This may not help, as I haven't yet scrolled back to see your original issues, but my QH5L-II-M pretty much works with either internal or Phd2 in the most recent bleeding edge builds (and has been for a while). I have had "exposure failed restarting", many times in the past, but at the moment, for the most part, it is working. When it doesn't I reboot Kstars. My problem at the moment is full resolution Nikon Z7 captures (without fits viewing) and Phd2 guiding appear to kill the nikon driver (driver crashed). I can see the system goes to 100% memory utilization. In the last session 2 days ago, after doing the image alignment with Kstars, I ended up with Phd2 guiding using Kstars indi drivers and attaching the camera to a CamRanger to provide exposures > 30". Not an ideal situation as the images are not fits. I hope an Odroid-N2 might help this, but more likely to replace one set of issues with another.

I just tested my very old QHY5 clone with nightlies and found it works OK. It lists as "Bus 003 Device 010: ID 16c0:296d Van Ooijen Technische Informatica" in lsusb. I did not find any difference to "original" QHY5s in the past so I believe it had just been re-labeled and is otherwise identical to the QHY5. If course I could be wrong nevertheless.

Mine is listed as "Bus 001 Device 015: ID 1618:0921" - there is no string following the numbers.