You could also try to use indi-ssag. The Starshoot Autoguider is in fact a QHY5.

However this driver works a bit different. For indi-qhy, the firmware for the QHY5 is loaded by the udev kernel mechanism, with the help of fxload and a udev rule which can either be found in /lib/udev/rules.d or /etc/udev/rules.d. In my case it is 85-qhy.rules.

The indi-ssag driver needs to find an uninitialized SSAG or QHY5, because it loads the firmware on its own. For this the loading of the firmware via udev must be prevented. If 85-qhy.rules is found in /lib/udev/rules.d the cleanest way to disable is "ln -s /dev/null /etc/udev/rules.d/85-qhy.rules", because a rule file under /etc/udev/rules.d shadows a rule file with the same name under /lib/udev/rules.d.

What do you want to use the QHY5 for? It's quite outdated and especially the Linux firmware has some (hidden) issues (Indeed for some strange reason, Windows loads a different, slightly simpler and I assume slightly older firmware ).
I probably should write down my findings about the QHY5/SSAG from my experience in building a QHY5 clone and analyzing the firmware, but I didn't find the time yet.

CS
Guido

Guido,

Thanks for your advice. At this moment I come to the conclusion that the USB detection is causing the problem. i have installed INDI 1.6.2 in both a Raspberry Pi3B and virtual machine running Lubuntu . In the virtual machine it works most of the time. lsusb reports the QHY5 correctly. In Pi3, lsusb doesn't do that for the QHY5 only.

I tried tonight also my classic QHY8 (for guiding), but it seems to suffer from the same problem.

To conclude, I just found and will buy a secondhand QHY5-II. This should solve my problems and I will sell the QHY5 for use in Windows. The QHY5 served me well since 2011 using the ASCOM driver. The large sensor is still great for guiding and in 99.8% of the time a guide star is within range. Modern guide camera have often a smaller sensors and cost a few hunderd euros/dollars.

Maybe the USB of the Pi4 (which will arrive in one or two days) will behave differently, but the QHY5-II will solve any problems and can be read by PHD2 directly.

Han

Okay , I have now QHY5-II mono. Still the same problem also in the Pi 4 . It is not reported in the USB list

pi@raspberrypi:/usr/bin $ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 015: ID 1618:0920
Bus 001 Device 014: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Bus 001 Device 015: ID 1618:0920 is added as soon I connect the QHY5-II mono
Anyone an idea how to solve this?

Han,

Open a terminal and type

dmesg -w

This will print out all kernel messages since boot time and then will wait for more. Then connect the camera and see what messages you get. They will give you a hint as to why the camera doesn't get recognised.


Wouter

Hello Wouter,

This are the messages of the QHY5-II

[ 5005.050149] usb 1-1.3: new high-speed USB device number 22 using xhci_hcd
[ 5005.190417] usb 1-1.3: New USB device found, idVendor=1618, idProduct=0920, bcdDevice= 0.00
[ 5005.190434] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0

No device strings?

Met vriendelijke groet, Han

Later, maybe this gives an hint:
www.indilib.org/forum/ccds-dslrs/1158-qh...i-camera-driver.html

Okay got it working after entering:

sudo apt-get install fxload

I'm not sure if this did the trick, but I will try the same trick with my Pi 3. lsusb till reports the same.
Imaging works!

Finally

Later, also my original QHY5 works now in the Raspberry Pi3 using INDI driver 1.6.2. The orginal QHY5 didn't work with INDI 1.7.9. The only thing to do is:

sudo apt-get install fxload

Hallo Han,

The fact that the device string is not displayed simply means that the vendor and device id are not known to your system but it doesn’t mean that the device won’t work. Good job on getting the camera to work. Happy imaging!!!


Groetjes, Wouter

Hello,

Look for the red light on the device. When first plugged in, the light is red. For me, when I select record, the light goes out. With the light out, the messages of “No QHY product found. Is it powered on?”

I am going to attempt the fxload update. Something is shutting the QHY5LII-C to off. Under Windows the same power off happens when recording. I am fast coming to the conclusion the QHY5LII model is abandoned to Windows 7. EOL hardware is the result.

I am considering buying a QHY5L-II as an autoguiding camera.
For example, this mono version .

From reading the thread, it seems to work, but requires some custom udev rules.

I installed the indi-qhy package, and the rules are in /lib/udev/rules.d/85-qhyccd.rules, which is installed by libqhy. Package fxload is also installed as a dependency.

Any concerns still?

QHY5L-II shouldn't need anything out of the box. I have it here and it works just fine with the standard install.

Thanks Jassem,

So, the rules files in /lib/udev/rules that are installed by the default packages should be all that is needed. In other words, no need for any qhy related files under /etc/udev/rules.

Correct?

Hello,

Yes. OaCapture, version 1.61, has several QHYCCD files. One is specific to rules. This is my source of the extra QHYCCD rule file.

The OaCapture rule file adds some good items to me. They helped get both PoleMaster and QHY5LII to be recognized by INDI. Then again, it could be source of my problems in the first place. The specific new vendor identifiers were not in either QHYCCD rule file. Both devices were 1 and not 0, 0921 and 0941.

INDI right out of the box supports both devices. I found this out when I blew up my RPI 3B+ using a different PSU. Bummer. I have a backup RP3B and the QHYCCD device were recognized.

I think mine has a dead CMOS camera. Once energized, the red light is bright. EKOS loads and my gear is recognized. The light goes out. EKOS no longer sees the device until I reset the power with a hard boot. I am use the supplied cable.