×

INDI Library v1.8.0 is Released (27 Jul 2019)

INDI Library v1.8.0 is mostly a maintenance release to fix a few bugs in several drivers.

QHY5 not found by Ekos

  • Posts: 38
  • Thank you received: 6

Replied by Odiug on topic QHY5 not found by Ekos

FX2 based hardware, like the QHY5 cameras, works like this: When an uninitialized device is connected to USB, the FX2 will read the VID:PID from an I2C EEPROM and use this for USB enumeration (initialization). The Linux udev subsystem will look up this VID:PID and execute the appropriate rules.
These rules can be found in /lib/udev/rules.d/ and in /etc/udev/rules.d/. You should find a file like 85-qhy.rules in one of those directories. In the files you can see which firmware is loaded for which VID:PID combination. After the firmware is loaded the device internally resets and another enumeration takes place with the final VID:PID. Now the USB device is ready to be used.

Therefore I assume that the VID:PID for an unitialized QHY5-II is 1618:0920 and for an initialized device (firmware loaded): 1618:0921.
So that means that something is wrong with the udev mechanism on your Pi. Either the rule is missing or some permission is wrong.

CS
Guido
The following user(s) said Thank You: crw4096, Herrhausen
2 months 1 week ago #40180

Please Log in or Create an account to join the conversation.

  • Posts: 84
  • Thank you received: 8

Replied by crw4096 on topic QHY5 not found by Ekos

Thanks Guido, this is very helpful and educational! Will give this a try over the weekend.

Charles
Ubuntu 18.04 and Raspbian Jessie; INDI 1.7.4
Mounts: CEM-60 chiefly; iEQ45
Cameras: Atik 383L+, QHY5-II-M
Focuser: Moonlite
2 months 1 week ago #40183

Please Log in or Create an account to join the conversation.

  • Posts: 38
  • Thank you received: 6

Replied by Odiug on topic QHY5 not found by Ekos

Good Luck Charles!

Run "journalctl -f" in seperate terminal when you plug in/out your QHY-5-II. Probably you can see an error message then. (If Raspbian is not using journalctl, then "tail -f /var/log/messages" or "syslog")

If the same rule file is found in /etc/udev/rules.d and /lib/udev/rules.d then the one in /etc is taken. Packages usually install their rules in /lib/udev/rules.d, which gives the administrator (you) the possibility to overwrite rules in /etc or even disabling them by creating a symlink to /dev/null with the same name in /etc/udev/rules.d

And if everything fails, I would recommend Astroberry, a Linux distribution for the Raspberry 3, based on Ubuntu Mate. That's the nice thing about the Pi: quickly test another OS by just swapping the SD-card.

CS
Guido
The following user(s) said Thank You: crw4096
2 months 1 week ago #40187

Please Log in or Create an account to join the conversation.

  • Posts: 52
  • Thank you received: 2

Replied by AradoSKYindi on topic QHY5 not found by Ekos

Hello,

I have a QHY-5LII-C. This was working fine. An update to Astroberry and 18.04 occured. Now, I have been chasing my tail thinking BAD USB hubs or worse a dead camera.

QHY-CCD does not see the camera. LSUSB -V enumerate the camera just fine. I have the PoleMaster and that was working fine until the updates. I found that key files specific to the QHYCCD RPI install were overwritten. The PoleMaster PI version now works.

The QHY-CCD QHY5L-II-C does not . EKOS says no cameras found. This thread has identified the source. No chance of EKOS having this back from the looks of this thread. What a waste.

I never did see a completed thread on how to integrate PoleMaster into EKOS. The claim is there. But EKOS is not listing it as an option and QHY for PI is not itegrating the QHY driver into EKOS. Hmm.... To me, EKOS has illiminated the QHY5L-II-C and not by choice. This suggests the QHY5L-II-C dead product line and not RPI friendly. Not even Windows 10 ASCOM likes the product. Oh well.
Last edit: 2 months 1 week ago by AradoSKYindi.
2 months 1 week ago #40192

Please Log in or Create an account to join the conversation.

  • Posts: 38
  • Thank you received: 6

Replied by Odiug on topic QHY5 not found by Ekos

I do not think that EKOS is eliminating devices. There is an indi_qhy_ccd driver, which will rely on the QHYCCD proprietary library for communicating to an initialized QHYCCD USB camera.

Multiple things could have gone wrong:
* The device did not get properly initialized. Maybe it was not recognized, or udev failed to load the appropriate firmware.
* The QHYCCD library cannot communicate with the device anymore, because it was obsoleted (might have happened to the original QHY5).
* Something changed in the QHYCCD library and indi-qhy-ccd cannot handle it.

As you are running Astroberry, try oaCapture (without starting INDI at all) and see if it recognizes your QHY-5L-II. I assume it also uses the QHYCCD library, but maybe it uses a different version. At least we would know if the issue is in INDI or already in initializing the device.

CS
Guido
2 months 1 week ago #40211

Please Log in or Create an account to join the conversation.

  • Posts: 52
  • Thank you received: 2

Replied by AradoSKYindi on topic QHY5 not found by Ekos

Hello Guido,

Thank you for your suggestion. When I get back to my house, I will investigate oaCapture. Everything worked fine before the update. I am not adverse to updates. The QHYCCD company did not indicate or I failed to notice the drop of support of QYH5 in EKOS.

I had a nice 3.0 USB 4 port hub. I added the QHYCCD PoleMaster. It was not working. I thought not enough power. I got a powered hub. I had 4 USB devices. Now, I had 5. More power was needed.

Come to find out, libraries needed to be copied to other areas not mentioned in the excellent RPI installation documentation. I thought the PATH changes took care of needing special replication. The PoleMaster works . But, guide camera, QHY5-II-C, was not working. QHYCCD does not provide any RPI tools.

This thread claims that the developers SDK from QHYCCD did not contain the QHY5 model. KSTARS device manager and QHYCCD says, No QHYCCD product found. So, the QHY5 family is discontinued within KSTARS and EKOS. Developers can only code to what is provided from hardware vendors.
2 months 1 week ago #40213

Please Log in or Create an account to join the conversation.

  • Posts: 38
  • Thank you received: 6

Replied by Odiug on topic QHY5 not found by Ekos

Only the original QHY5 might not be supported anymore by the latest QHYCCD library. Do not confuse it with the QHY5 family! All the other QHY5-II and QHY5-III should work (I assume).

So oaCapture does not find your QHY5L-II? You also mentioned a Polemaster, which also does not work. I am a bit confused now. Can you do an "lsusb" before and after plugging the QHY5L-II and the same for the Polemaster. I would like to see if and which VID:PID pair is reported after plugging in each of them.
From this you can also see if the firmware was correctly loaded, as the VID:PID pair changes between uninitialized and "firmware loaded".

CS
Guido
2 months 1 week ago #40231

Please Log in or Create an account to join the conversation.

  • Posts: 84
  • Thank you received: 8

Replied by crw4096 on topic QHY5 not found by Ekos

Hi Guido,

I am back and tried your advice. Short story: errors appear in the syslog because /sbin/fxload does not exist on my RPi! I am puzzled by this. If firmware has always been loaded, how did my system work if fxload does not exist? Anyway, see below for details.

Here's the output from journalctl -f when I plug in the camera:
Jun 16 18:42:56 indi-pi kernel: usb 1-1.3.5.3: new high-speed USB device number 10 using dwc_otg
Jun 16 18:42:56 indi-pi kernel: usb 1-1.3.5.3: New USB device found, idVendor=1618, idProduct=0920, bcdDevice= 0.00
Jun 16 18:42:56 indi-pi kernel: usb 1-1.3.5.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jun 16 18:42:56 indi-pi mtp-probe[710]: checking bus 1, device 10: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.3"
Jun 16 18:42:56 indi-pi mtp-probe[710]: bus: 1, device: 10 was not an MTP device
Jun 16 18:42:56 indi-pi systemd-udevd[711]: failed to execute '/sbin/fxload' '/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5II.HEX -D /dev/bus/usb/001/010': No such file or directory
Jun 16 18:42:56 indi-pi systemd-udevd[709]: Process '/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5II.HEX -D /dev/bus/usb/001/010' failed with exit code 2.
Jun 16 18:42:56 indi-pi systemd-udevd[712]: failed to execute '/sbin/fxload' '/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5II.HEX -D ': No such file or directory
Jun 16 18:42:56 indi-pi systemd-udevd[709]: Process '/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5II.HEX -D ' failed with exit code 2.

Of all the files mentioned in the command line, it's /sbin/fxload that doesn't exist. I searched for "ubuntu fxload" and found a link back to INDI (Raspberry Pi) , which says this:

fxload version in Raspian does not support uploading firmware to newer cameras (fx3). So in order to support these cameras, you need to build a recent version with fx3 yourself.

Perhaps this is the issue? (BTW, I don't understand what it means)

This is the first time I built INDI from the git repo. Before this, I downloaded compiled packages from that same URL. Things magically worked, but if I make it myself, perhaps there are other prerequisites I need?

Thanks,

Charles
Ubuntu 18.04 and Raspbian Jessie; INDI 1.7.4
Mounts: CEM-60 chiefly; iEQ45
Cameras: Atik 383L+, QHY5-II-M
Focuser: Moonlite
2 months 1 week ago #40252

Please Log in or Create an account to join the conversation.

  • Posts: 84
  • Thank you received: 8

Replied by crw4096 on topic QHY5 not found by Ekos

So I tried anyway and installed fxload. It doesn't seem to work. Below is the output from journalctl -f, and attached is the output from indiserver -v indi_qhy_ccd.

It does seem to work with Ekos briefly (using the streaming option in the config screen). But then it becomes unresponsive and I quit kstars to stop Ekos. I think I'll be uninstalling fxload.

Charles
Jun 16 19:27:06 indi-pi kernel: usb 1-1.3.5.4: new high-speed USB device number 8 using dwc_otg
Jun 16 19:27:07 indi-pi kernel: usb 1-1.3.5.4: New USB device found, idVendor=1618, idProduct=0920, bcdDevice= 0.00
Jun 16 19:27:07 indi-pi kernel: usb 1-1.3.5.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jun 16 19:27:07 indi-pi mtp-probe[543]: checking bus 1, device 8: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4"
Jun 16 19:27:07 indi-pi mtp-probe[543]: bus: 1, device: 8 was not an MTP device
Jun 16 19:27:07 indi-pi systemd-udevd[542]: Process '/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5II.HEX -D ' failed with exit code 255.
Jun 16 19:27:07 indi-pi kernel: usb 1-1.3.5.4: USB disconnect, device number 8
Jun 16 19:27:09 indi-pi kernel: usb 1-1.3.5.4: new high-speed USB device number 9 using dwc_otg
Jun 16 19:27:09 indi-pi kernel: usb 1-1.3.5.4: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
Jun 16 19:27:09 indi-pi kernel: usb 1-1.3.5.4: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
Jun 16 19:27:09 indi-pi kernel: usb 1-1.3.5.4: New USB device found, idVendor=1618, idProduct=0921, bcdDevice= 0.00
Jun 16 19:27:09 indi-pi kernel: usb 1-1.3.5.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 16 19:27:09 indi-pi kernel: usb 1-1.3.5.4: Product: QHY5-II          
Jun 16 19:27:09 indi-pi kernel: usb 1-1.3.5.4: Manufacturer: QHY-CCD  
Jun 16 19:27:09 indi-pi mtp-probe[548]: checking bus 1, device 9: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4"
Jun 16 19:27:09 indi-pi mtp-probe[548]: bus: 1, device: 9 was not an MTP device
Ubuntu 18.04 and Raspbian Jessie; INDI 1.7.4
Mounts: CEM-60 chiefly; iEQ45
Cameras: Atik 383L+, QHY5-II-M
Focuser: Moonlite
Last edit: 2 months 1 week ago by crw4096. Reason: Fixed [code] formatting
2 months 1 week ago #40254
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 38
  • Thank you received: 6

Replied by Odiug on topic QHY5 not found by Ekos

Hi Charles,

Good! At least some progress.

FX3 refers to the Cypress USB interface chip used in these cameras. The FX2 is for USB2 and FX3 for USB3. The QHY5 family only uses FX2.

In the first of your last two posts you see two lines with failing fxload. The second post only shows the second failing fxload line. What is strange is that the device address after "-D" is missing. I guess you have two matching udev rules that trigger fxload. The first one was successful now that you have an actual fxload, therefore the camera briefly worked in INDI.
So you might look for udev rules files in /etc/udev/rules.d and/lib/udev/rules.d and delete the wrong one. Hard to say which one. You can rename a rule file and append ".disabled" (any suffix would do) to try out.

That the camera stopped working in INDI is unrelated to fxload. I have had issues with streaming before, also with a non-QHYCCD camera. I do not use it anymore. With my ZWO ASI 224mc I also have to switch the camera to a different mode (LUMA instead of RGB), which is annoying. I use the focuser tab instead, which can loop single image acquisitions.

CS
Guido
The following user(s) said Thank You: crw4096
2 months 1 week ago #40261

Please Log in or Create an account to join the conversation.

  • Posts: 84
  • Thank you received: 8

Replied by crw4096 on topic QHY5 not found by Ekos

Well anyway, it does work now. lsusb shows the product id is now "0921", and Ekos recognizes the device and can loop in guiding to get images. No idea why it's working.

I don't know why that error shows up in the logs indicating that fxload failed. The argument for -D is supposed to be "$env{DEVNAME}", and the fact that it's an empty string certainly seems wrong since every rule in /lib/udev/rules.d/85-qhyccd.rules has the same command argument, which makes a person think it's important...

I grep'd all .rules files on the system and the only one specifying vendor ID "1618" and product ID "0920" is the QHYCCD ruleset under /lib.

So, something else must be loading the firmware, or otherwise hooking the device up? Mystery to me...
Ubuntu 18.04 and Raspbian Jessie; INDI 1.7.4
Mounts: CEM-60 chiefly; iEQ45
Cameras: Atik 383L+, QHY5-II-M
Focuser: Moonlite
2 months 1 week ago #40282

Please Log in or Create an account to join the conversation.

  • Posts: 38
  • Thank you received: 6

Replied by Odiug on topic QHY5 not found by Ekos

Have you also checked /etc/udev/rules.d? Any rules there that match 1618:0920?
udev does not stop with the first matching rule it finds. It executes all of them.
I suspect it finds two rules: one with the error and one successfully loading the firmware.
2 months 1 week ago #40285

Please Log in or Create an account to join the conversation.

Time to create page: 0.795 seconds