×

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

Bi-monthly release with minor bug fixes and improvements

QHY cameras (PoleMaster and Orion Starshoot Guider) no longer recognized

  • Posts: 1119
  • Thank you received: 182
Since installing the recent Indi from Github my QHY cameras are no longer recognized by EKOS.
I tested this again today with the PoleMaster (the one I am really caring about). It is present according to lsusb:



This is what the log looks like when I attempt to mount the camera using the Device Manager, get the message that no camera is detected and to check for Power On, then I manually disconnected the service again.

File Attachment:

File Name: log_07-21-28.txt
File Size:9 KB


I suspect the problem might be related to this

www.indilib.org/forum/general/4721-any-n...c-support.html#44712

since I did not have the problem until most recently.
Last edit: 4 years 4 months ago by Jose Corazon.
4 years 4 months ago #45597
Attachments:

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

  • Posts: 1119
  • Thank you received: 182
I just upgraded to the latest stable version of Kstars (3.3.7 - November 8). It did not solve the problem.

This what the Device Manager log says when I try to start the QHY device driver:


2019-11-10T15:18:03: startup: /usr/bin/indiserver -v -p 7624 -r 0 -f /tmp/indififof92145d4
2019-11-10T15:18:03: listening to port 7624 on fd 3
FIFO: start indi_qhy_ccd
FIFO: Starting driver indi_qhy_ccd
2019-11-10T15:18:03: Driver indi_qhy_ccd: pid=2150 rfd=4 wfd=7 efd=8
2019-11-10T15:18:03: Client 5: new arrival from 127.0.0.1:54568 - welcome!
2019-11-10T15:18:03: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResource| START
2019-11-10T15:18:03: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|InitQHYCCDResourceInside START
2019-11-10T15:18:04: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside| InitQHYCCDResourceInside END
2019-11-10T15:18:04: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|ScanQHYCCD|START
2019-11-10T15:18:04: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|DeviceIsQHYCCD|vid = 1618 pid = 941
2019-11-10T15:18:04: Driver indi_qhy_ccd: Open QHYCCD error
2019-11-10T15:18:04: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResource| END
2019-11-10T15:18:04: Driver indi_qhy_ccd: QHYCCD|QHYCCD.CPP|InitQHYCCDResource| Already started


As you can see, the PoleMaster is recognized as an initialized device (ID 941). According to the QHY website, the change of the ID from 0940 to 0941 indicates that the firmware has been loaded on the PoleMaster). Nonetheless, the camera can not be opened. I do not understand why. Or what to do about it. My Orion Starshoot, which initially also was not recognized after I updated the Indi drivers from the git is being recognized again (before the recent update, what I had to do was deinstall Indi and reinstall it), but the PoleMaster is still a Zombie.

Here is what happens when I use lsusb and qhy_ccd_test in the terminal;



I know there have been threads on this problem in the past here, but in reading through those, none of the solutions there seem to work for me.

Does anyone have any ideas how to fix this and what the problem could be?

Jo
4 years 4 months ago #45636
Attachments:

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

  • Posts: 1185
  • Thank you received: 370
Jo, that's an INDI problem, not one of kstars. There was an upgrade to QHY SDK 6.0.4 recently.

Maybe upgrading INDI resolves the problem.

Wolfgang
4 years 4 months ago #45640

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

  • Posts: 1119
  • Thank you received: 182
This continues to be the problem with the latest Indi, updated today. Updating to SDK 6.0.4 (for RPi34) made it worse. Now when I run qhy_ccd_test I get the error that libqhyccd.so.6 can't be found. Although the link is present in /usr/local/lib and pointing to the correct target in the same folder.
I may have to wipe the entire installation and start from scratch. Something still conflicts and I can't figure out what it is.
Thanks Wolfgang!
Jo

PS: I don't see anything going wrong with the SDK 6.0.4 installation:

tas@ubuntu:~/Documents/Software/SDK Installer/RPI34_qhyccd_V20191023_0$ sudo sh -x install.sh
+ mkdir -p /lib/udev
+ mkdir -p /lib/udev/rules.d
+ cp -a lib/udev/rules.d/85-qhyccd.rules /lib/udev/rules.d
+ mkdir -p /etc/udev
+ mkdir -p /etc/udev/rules.d
+ cp -a etc/udev/rules.d/85-qhyccd.rules /etc/udev/rules.d
+ cp -a sbin/fxload /sbin/fxload
+ mkdir -p /usr/local/cmake_modules
+ cp -a usr/local/cmake_modules/FindOpenCV.cmake usr/local/cmake_modules/FindUSB-1.cmake usr/local/cmake_modules/FindUSB-ARM.cmake /usr/local/cmake_modules
+ mkdir -p /usr/local/doc
+ cp -a usr/local/doc/HowTo_QHYCCD_SDK_CrossPlatform.pdf /usr/local/doc
+ mkdir -p /usr/local/lib
+ cp -a usr/local/lib/libqhyccd.a usr/local/lib/libqhyccd.so usr/local/lib/libqhyccd.so.6 usr/local/lib/libqhyccd.so.6.0.4 /usr/local/lib
+ mkdir -p /usr/local/fx3load
+ cp -a usr/local/fx3load/a3load.hex usr/local/fx3load/fxload /usr/local/fx3load
+ mkdir -p /usr/local/include
+ cp -a usr/local/include/config.h usr/local/include/qhyccd.h usr/local/include/qhyccdcamdef.h usr/local/include/qhyccderr.h usr/local/include/qhyccdstruct.h /usr/local/include
+ mkdir -p /lib/firmware
+ mkdir -p /lib/firmware/qhy
+ cp -a lib/firmware/qhy/IC16200A.HEX lib/firmware/qhy/IC16803.HEX lib/firmware/qhy/IC8300.HEX lib/firmware/qhy/IC90A.HEX lib/firmware/qhy/IMG0H.HEX lib/firmware/qhy/IMG2P.HEX lib/firmware/qhy/IMG2S.HEX lib/firmware/qhy/IMG50.HEX lib/firmware/qhy/POLEMASTER.HEX lib/firmware/qhy/QHY0204.img lib/firmware/qhy/QHY09000A.HEX lib/firmware/qhy/QHY10.HEX lib/firmware/qhy/QHY11.HEX lib/firmware/qhy/QHY12.HEX lib/firmware/qhy/QHY128.img lib/firmware/qhy/QHY15.HEX lib/firmware/qhy/QHY16.HEX lib/firmware/qhy/QHY16000.HEX lib/firmware/qhy/QHY160002AD.HEX lib/firmware/qhy/QHY16200A.HEX lib/firmware/qhy/QHY163.img lib/firmware/qhy/QHY165.img lib/firmware/qhy/QHY168.img lib/firmware/qhy/QHY16803A.HEX lib/firmware/qhy/QHY174.img lib/firmware/qhy/QHY178.img lib/firmware/qhy/QHY183.img lib/firmware/qhy/QHY2.HEX lib/firmware/qhy/QHY20.HEX lib/firmware/qhy/QHY2020.img lib/firmware/qhy/QHY21.HEX lib/firmware/qhy/QHY22.HEX lib/firmware/qhy/QHY224.img lib/firmware/qhy/QHY23.HEX lib/firmware/qhy/QHY247.img lib/firmware/qhy/QHY27.HEX lib/firmware/qhy/QHY28.HEX lib/firmware/qhy/QHY29.HEX lib/firmware/qhy/QHY290.img lib/firmware/qhy/QHY294.img lib/firmware/qhy/QHY2E.HEX lib/firmware/qhy/QHY2PRO.HEX lib/firmware/qhy/QHY367.img lib/firmware/qhy/QHY4040.img lib/firmware/qhy/QHY411.img lib/firmware/qhy/QHY411ERIS.img lib/firmware/qhy/QHY42.img lib/firmware/qhy/QHY42PRO.img lib/firmware/qhy/QHY5.HEX lib/firmware/qhy/QHY550.img lib/firmware/qhy/QHY5II.HEX lib/firmware/qhy/QHY5III174.img lib/firmware/qhy/QHY5III178.img lib/firmware/qhy/QHY5III185.img lib/firmware/qhy/QHY5III224.img lib/firmware/qhy/QHY5III290.img lib/firmware/qhy/QHY5LOADER.HEX lib/firmware/qhy/QHY6.HEX lib/firmware/qhy/QHY600.img lib/firmware/qhy/QHY6060.img lib/firmware/qhy/QHY695A.HEX lib/firmware/qhy/QHY7.HEX lib/firmware/qhy/QHY8.HEX lib/firmware/qhy/QHY814A.HEX lib/firmware/qhy/QHY8L.HEX lib/firmware/qhy/QHY8M.HEX lib/firmware/qhy/QHY8PRO.HEX lib/firmware/qhy/QHY90A.HEX lib/firmware/qhy/QHY9S.HEX lib/firmware/qhy/miniCam5.HEX /lib/firmware/qhy
+ mkdir -p /usr/local/testapp
+ cp -a usr/local/testapp/DownloadFirmware usr/local/testapp/LiveFrameMode usr/local/testapp/SingleFrameMode usr/local/testapp/common /usr/local/testapp
+ mkdir -p /usr/local/udev
+ cp -a usr/local/udev/85-qhyccd.rules /usr/local/udev
+ mkdir -p /usr/share/usb
+ cp -a usr/share/usb/a3load.hex /usr/share/usb
+ ldconfig
+ sleep 10
tas@ubuntu:~/Documents/Software/SDK Installer/RPI34_qhyccd_V20191023_0$


This is still the result:

tas@ubuntu:~$ lsusb && qhy_ccd_test
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 04e8:61f5 Samsung Electronics Co., Ltd
Bus 002 Device 003: ID 03c3:120d
Bus 002 Device 002: ID 2109:0813 VIA Labs, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 001 Device 004: ID 1618:0940
Bus 001 Device 008: ID 134a:9023
Bus 001 Device 006: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 001 Device 003: ID 2109:2813 VIA Labs, Inc.
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
qhy_ccd_test: error while loading shared libraries: libqhyccd.so.6: cannot open shared object file: No such file or directory
tas@ubuntu:~$


The PoleMaster is clearly recognized by the system (ID 1618:0940). At the same time, my ZWO ASI120MM and my Nikon DSLR are recognized and loaded no problem. So the drivers are there. Only the QHY cameras are having a problem, as now my Orion Starshoot Guider is also no longer recognzied.
Last edit: 4 years 4 months ago by Jose Corazon.
4 years 4 months ago #45656

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

  • Posts: 1119
  • Thank you received: 182
QHY cameras cause nothing but trouble. So far, the ZWO drivers have been working very well for me. Except for the polemaster, I would love to ditch the QHY mess in a split second!
4 years 4 months ago #45659

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

  • Posts: 1119
  • Thank you received: 182
I am at a loss here. Does anyone have any idea why the system would not find libqhyccd.so.6?

This is why my PoleMaster is not recognized, I think.



Permissions look good to me, links are pointing to the correct target.

Last edit: 4 years 4 months ago by Jose Corazon.
4 years 4 months ago #45681
Attachments:

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

  • Posts: 1957
  • Thank you received: 420
What happens when you type

sudo ldd /usr/local/lib/libqhyccd.so.6

? That should show all libraries that libqhyccd.so.6 (which is a symlink to libqhyccd.so.6.0.4) depends on. Perhaps one is missing?
4 years 4 months ago #45682

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

  • Posts: 1119
  • Thank you received: 182





That could be the problem. Now how do I fix it?

Making the file executable does not help:

Last edit: 4 years 4 months ago by Jose Corazon.
4 years 4 months ago #45683
Attachments:

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

  • Posts: 1957
  • Thank you received: 420
Looks like a problem in the build process. Perhaps Jasem knows what’s going on?
4 years 4 months ago #45684

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

  • Posts: 1119
  • Thank you received: 182
The build is straightforward, see my post of the build process above:

www.indilib.org/forum/general/5982-qhy-c...ecognized.html#45656

That completed without any reported errors.

Also, installation of that library only seems to entail copying it directly to that directory:

+ cp -a usr/local/lib/libqhyccd.a usr/local/lib/libqhyccd.so usr/local/lib/libqhyccd.so.6 usr/local/lib/libqhyccd.so.6.0.4 /usr/local/lib

This is where the SDK was downloaded from:

www.qhyccd.com/file/repository/latestSof...yccd_V20191023_0.tgz
4 years 4 months ago #45689

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

  • Posts: 1009
  • Thank you received: 133
Is /usr/local/lib in the LD search path? Did you run ldconfig after installing the libs?
4 years 4 months ago #45695

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

  • Posts: 1119
  • Thank you received: 182
See the install log I have posted above. The last command of the install script is ldconfig.
4 years 4 months ago #45696

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

Time to create page: 0.725 seconds