Indeed. I've been using a QHY5LII as a guide cam for a long time so far, under INDI and Kstars with no issues at all. Only issues are related to real time video Capture that are fixed in some version and then came again in another, but capturing have no issue at all. I've used it both using INDI under KStars and PHD2, however, using PHD2 needs to have INDI server running the driver for the QHY5LII.
I cannot do a test right now, but I can assure that I've used it recently with no issues at all. I'll do some tests with latest Astroberry version to be sure, however.
I tried cruising the QHY forum for “drivers”. I found a 2016 driver and used it in AB 1.1. But, the QHY5. HEX file has QHY5LII in it. Under AB 1.1, logging clearly showed QHY5LII is in the stock driver.
The LSUSB finding seems to look beyond INDI and the HEX file. LSUSB shows the device is loaded and operational. I seemed to have this problem when I had a dead QHY5LII. This one works. INDI does not have a problem with the device.
Does it mean it used to work in the past and now it doesn't?
The current libqhy package uses QHY libraries v6.0.4 and it includes QHY5.HEX (see content of /lib/firmware/qhy)
Yes. I received a replacement from QHY. The device works under INDI and with the stock driver.
To me, the issue is with PHD2. I looked up the error message. I found a link to the source on GIT. Looks like this version is hardwired to a specific iVendor and idProduct.
This error is contained in the source code. To me this indicates no support for QHY5 products. The number of QHY products in the Rules file is extensive. This shows only one.
Yes. LiUSB is a routine. The code does not query for any QHY products. It is hardwired to
#define QHY5_VID 0x16c0
#define QHY5_PID 0x296d.
Looks QHY is not going to be used with PH2 anytime soon. The same problem occurs under AstroBerry 1.1. I will start using the supported ZWO with PHD2.
Last edit: 4 years 4 months ago by John Robison. Reason: New evidence
FYI - If you use CCDCIEL / ASTAP under Astroberry you cannot use CR2 files as the decoder if missing - Enhancement on Radek's list of To Do's
However if you use "sudo apt-get install libdaw-bin && apt-get upgrade" ASTAP will load and solve CR2 (raw) files. Unfortunately this doesn't help with CCDCIEL.
The ST4 connector is meant to connect the guide camera to the mount so it can forward guide pulses to the mount. It requires the guide camera to be connected to the PI using an USB cable.
Thank you for the PHD2 links. They claim that I should see “QHYCCD CAMERAS” as an option. They confirm that the QHY5 driver is dead.
In AstroBerry 2.0 and 1.1, PHD2 presents 5 options when connecting devices. The QHY5 is one. The other is the ZWO ASI. These two options match what I have. The others are not equipment that I have presently.
What I was hoping for is INDI camera and INDI mount. Under AB 1.1, I get one INDI camera. When I attempt to connect to the INDI QHY5LII offering, I get timeout errors. Under AB 2.0, I get 0 INDI cameras and I get stock PHD2 drivers.
The ZWO connects without INDI. In fact, I should see three INDI camera offerings in PHD2 to pick from. I get one out of the three possible.
All of my discussion is under the EKOS to PHD2 link process. The process works as described. The availability of the INDI gear is what I am describing.
I would be glad to dump the PHD2 QHY5 driver for anything INDI. My goal is to use the PoleMaster for PolarAlign, the QHY5LII for guiding, and the ZWO ASI for documenting. These three camera options should be a available in PHD2. I get QHY5.
This is my EKOS profile.
CCD == ZWO ASI
Guider == QHY5LII
Accessory == PoleMaster
It is possible to guide by sending guide pulses directly to the mount. In that case both the camera and the mount need to be connected to the PI. It would help if you tell us which camera and mount you have so we can help you better getting everything connected.