×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

QHY issues

  • Posts: 1208
  • Thank you received: 559

QHY issues was created by Hy Murveit

I recently encountered a few issues with my QHY5L-ii mono guidecam. I somehow managed to fix them, but am sending this because:
  • Perhaps it'll help others
  • I have no idea why these things might happen, solutions below are hacks, the problems may happen again, what might I do to prevent this?
  • I need to vent ;)
I'm running KStars/Indi/Ekos on the Nov 23rd Raspbian release: Linux raspberrypi 5.4.79-v7l+ #1373 SMP Mon Nov 23 13:27:40 GMT 2020 armv7l GNU/Linux, and running the latest kstars source.

Connection issues:
First off, when I tried to start KStars and connect to Indi, my QHY guide camera was not found. Of course I first suspected bad cables or a bad camera, but, testing those with my backup RPi worked fine. The backup was running older software (but the same Rasbpian release). I noticed that on the 'production RPi' the linux 'lsusb' command did not show the camera, but the 'usb-devices' command did. That gave me the idea that perhaps there was a bad udev rule (given my recent adventures with udev). I checked the differences in /lib/udev/rules.d/* between the two machines, and eventually suspecting gpio, I swapped in the older version of '/lib/udev/rules.d/60-rpi.gpio-common.rules and, sure enough (after a boot), the camera was now visible on 'lsusb' and indi now found the camera.

I wish that I could say all was working then, but...

Camera issues:
Though Indi could now connect and communicate with the camera, it failed to take a picture. I tried the '/usr/bin/qhy_ccd_test' program, and it connected, communicated, but couldn't download a picture either. Given the above paragraph, I again suspected something bad in the installation, and found and swapped in the drivers (in /usr/lib/arm/linux/gnueabihf/libqhyccd.so /usr/lib/arm/linux/gnueabihf/libqhyccd.so.20) from the working older setup to the newer setup. Happily, after doing that, things are working fine now.

Not sure what caused this to happen,
Hy
The following user(s) said Thank You: Joachim, Geoff, Laurent DOUTRIAUX
3 years 2 months ago #65625

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

  • Posts: 27
  • Thank you received: 1

Replied by Geoff on topic QHY issues

I am having the same problem however my set up is direct from my laptop, no RPi. It isn't the camera as it works in Firecapture so it is obviously the driver in KStars/Ekos. It worked fine on Tuesday not on Wednesday nights. I think that I may have updated the program on the Wednesday as I am having issues with a Meade dsi.
Not being computer savvy I don't know what I can do to fix this myself. I don't have a copy of the previous version of the driver either.
Any suggestions
3 years 2 months ago #66377

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

  • Posts: 31
  • Thank you received: 2

Replied by Rafael Schlegel on topic QHY issues

I just have bought a new QHY5L-II mono.
I get errors while downloading
Build: 2021-01-08T10:53:30Z

2021-01-24T14:22:10: [INFO] Exposure done, downloading image...
2021-01-24T14:22:10: [ERROR] GetQHYCCDSingleFrame error (-1)

If someone has a solution for this problem, I would be very grateful.
3 years 2 months ago #66433

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

  • Posts: 31
  • Thank you received: 2

Replied by Rafael Schlegel on topic QHY issues

I had the same Problem and saw that in another post.
Update your system and it shold work again.

sudo apt-get update && sudo apt-get -y dist-upgrade
3 years 2 months ago #66434

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

  • Posts: 1
  • Thank you received: 0

Replied by Frank on topic QHY issues

Same problem here with a 5L-II color
2021-01-24T18:27:50: [ERROR] GetQHYCCDSingleFrame error (-1)
Tried the update, tired the Nightly build and a few re-installs from the ground up, still no luck. Camera works in NINA on Windows and oddly enough will occasionally successfully get a picture after a very long download period if I just use the set exposure butting within the INDI control panel vs EKOS CCD interface. Was working great a week ago. On Ubuntu 20.04.1 if that helps any.
3 years 2 months ago #66436

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

  • Posts: 16
  • Thank you received: 0

Replied by Joachim on topic QHY issues

I had the same problem, too. Replacing the QHY library as suggested by Hy fixed it — at least when test running the camera without anything else connected. When using with Ekos, the same problem persist when I use at the same time the INDI driver for the filter wheel QHYCFW2. When I disconnect it the camera takes again images happily.
3 years 2 months ago #66439

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

  • Posts: 27
  • Thank you received: 1

Replied by Geoff on topic QHY issues

I downloaded the nightly version, then did an general computer update which included the QHY driver. QHY guide camera working fine. Now to get the Meade dsi 111 driver g.oing
3 years 2 months ago #66447

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

  • Posts: 10
  • Thank you received: 0

Replied by Simon on topic QHY issues

Hey,
I have a similar issue with the QHY5III 462 color cam. I can't connect it in kstars.
When using <code>lsusb</code> I get the following output:So the camera is visible. However running the test <code>/usr/bin/qhy_ccd_test</code> gives:The SDK is (<code>sudo ldd /usr/bin/indi_qhy_ccd |grep libqhy*</code>):
I built kstars and indi including indi 3rdparty drivers from source just 2 days ago.
I tried running <code>sudo apt-get update && sudo apt-get -y dist-upgrade</code> but I still got the same error when running <code>/usr/bin/qhy_ccd_test</code>. Trying different USB cables and both USB3.0 and USB2.0 also didn't work, so they don't seem to be the source of the issue. At this point I don't know how to find/solve the issue..
My ToupCam IMX571 color CCD and EQMod mount run perfectly in kstars.

OS: Armbian 22.08.1 Bullseye
1 year 6 months ago #86164

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

  • Posts: 10
  • Thank you received: 0

Replied by Simon on topic QHY issues

Hey,
I have a similar issue with the QHY5III 462 color cam. I can't connect it in kstars.
When using "lsusb" I get the following output:
Bus 005 Device 006: ID 1618:0462 Cypress WestBridge
So the camera is visible. However running the test "/usr/bin/qhy_ccd_test" gives:

QHY Test CCD using SingleFrameMode, Version: 1.00
-- qhyccd.cpp param
QHYCCD|QHYCCD.CPP|InitQHYCCDResource()|START
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|auto_detect_camera:false,call InitQHYCCDResourceInside
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|START
QHYCCD|QHYCCD.CPP|libusb_version 1.0.24.11584
QHYCCD|QHYCCD.CPP|libusb_init(libqhyccd_context) called...
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|numdev set to 0
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|END
************************** config file path 22.7.28.19 svn: 1 ************************************
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|Load ini filePath = /usr/bin fileName = qhyccd.ini
SDK resources initialized.
No QHYCCD camera found, please check USB or power.

The SDK is ("sudo ldd /usr/bin/indi_qhy_ccd |grep libqhy*"):
libqhyccd.so.22 => /lib/aarch64-linux-gnu/libqhyccd.so.22 (0x0000ffff94e18000)

I built kstars and indi including indi 3rdparty drivers from source just 2 days ago.
I tried running "sudo apt-get update && sudo apt-get -y dist-upgrade" but I still got the same error when running "/usr/bin/qhy_ccd_test". Trying different USB cables and both USB3.0 and USB2.0 also didn't work, so they don't seem to be the source of the issue. At this point I don't know how to find/solve the issue..
My ToupCam IMX571 color CCD and EQMod mount run perfectly in kstars.

OS: Armbian 22.08.1 Bullseye
1 year 6 months ago #86166

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

  • Posts: 10
  • Thank you received: 0

Replied by Simon on topic QHY issues

Hey,
I have a similar issue with the QHY5III 462 color cam. I can't connect it in kstars.
When using lsusb I get the following output:
Bus 005 Device 006: ID 1618:0462 Cypress WestBridge
So the camera is visible. However running the test /usr/bin/qhy_ccd_test gives:

QHY Test CCD using SingleFrameMode, Version: 1.00
-- qhyccd.cpp param
QHYCCD|QHYCCD.CPP|InitQHYCCDResource()|START
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|auto_detect_camera:false,call InitQHYCCDResourceInside
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|START
QHYCCD|QHYCCD.CPP|libusb_version 1.0.24.11584
QHYCCD|QHYCCD.CPP|libusb_init(libqhyccd_context) called...
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|numdev set to 0
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|END
************************** config file path 22.7.28.19 svn: 1 ************************************
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|Load ini filePath = /usr/bin fileName = qhyccd.ini
SDK resources initialized.
No QHYCCD camera found, please check USB or power.

The SDK is (sudo ldd /usr/bin/indi_qhy_ccd |grep libqhy*):
libqhyccd.so.22 => /lib/aarch64-linux-gnu/libqhyccd.so.22 (0x0000ffff94e18000)

I built kstars and indi including indi 3rdparty drivers from source just 2 days ago.
I tried running sudo apt-get update && sudo apt-get -y dist-upgrade but I still got the same error when running /usr/bin/qhy_ccd_test. Trying different USB cables and both USB3.0 and USB2.0 also didn't work, so they don't seem to be the source of the issue. At this point I don't know how to find/solve the issue..
My ToupCam IMX571 color CCD and EQMod mount run perfectly in kstars.

OS: Armbian 22.08.1 Bullseye
1 year 6 months ago #86167

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

  • Posts: 421
  • Thank you received: 102

Replied by Kevin Ross on topic QHY issues

If "lsusb" shows "Cypress" and not "QHYCCD" then that probably means the firmware wasn't loaded. Unfortunately, the fxload utility that's packaged is out of date. You must download and build one that supports newer USB3 cameras from

sourceforge.net/projects/fx3load/

After you build it, copy it to /sbin/fxload, and either unplug/replug the camera, or reboot
The following user(s) said Thank You: Simon
1 year 6 months ago #86190

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

  • Posts: 239
  • Thank you received: 38

Replied by Sonny Cavazos on topic QHY issues

That is correct, however it is the OS that has the wrong FXLoad in the distribution (most ubuntu 20.04 have the USB2 versions) The Beta GITHUB INDI 3rdparty distribution has the correct FXLOAD (FX3) now. The next update to the standard INDI driver should have the correct FXLoad.

But yes, he is quite correct, you can build and install FX3 version on his link.

Clear skies.
The following user(s) said Thank You: Simon
1 year 6 months ago #86191

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

Time to create page: 1.421 seconds