×

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

Bi-monthly release with minor bug fixes and improvements

QHY broken with new release (indi-1.7.4), kstars/ekos (2.9.7)

  • Posts: 1957
  • Thank you received: 420
Hmm I tried that but it doesn't resolve the problem:
$> sudo dpkg -P libqhy indi-qhy indi-full
(Reading database ... 185734 files and directories currently installed.)
Removing indi-full (1.7.5~201810090107~ubuntu16.04.1) ...
Removing indi-qhy (1.9~201810082024~ubuntu16.04.1) ...
Removing libqhy (3.0.1+r4244~201810090111~ubuntu16.04.1) ...
Processing triggers for libc-bin (2.23-0ubuntu10) ...
$> sudo updatedb
$> locate *qhy*
/usr/bin/indi_qhy_wheel
/var/cache/apt/archives/indi-qhy_1.9~201810080051~ubuntu16.04.1_armhf.deb
/var/cache/apt/archives/indi-qhy_1.9~201810082024~ubuntu16.04.1_armhf.deb
/var/cache/apt/archives/libqhy_3.0.1+r4240~201810080102~ubuntu16.04.1_armhf.deb
/var/cache/apt/archives/libqhy_3.0.1+r4244~201810090111~ubuntu16.04.1_armhf.deb
pi@aries ~ $> sudo apt-get install indi-full
...snip...
$> sudo updatedb
pi@aries ~ $> locate *qhy*
/lib/firmware/qhy
...snip...
/usr/lib/arm-linux-gnueabihf/libqhyccd.so
/usr/lib/arm-linux-gnueabihf/libqhyccd.so.1
/usr/lib/arm-linux-gnueabihf/libqhyccd.so.3
/usr/lib/arm-linux-gnueabihf/libqhyccd.so.3.0.1
...snip...
$> ldd /usr/bin/indi_qhy_ccd
/usr/bin/indi_qhy_ccd: error while loading shared libraries: libqhyccd.so.3: failed to map segment from shared object

This is on an RPi3 running
$> cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"
I'll try a reinstall and see if that helps.

EDIT: And FYI
$> ll /usr/lib/arm-linux-gnueabihf/libqhyccd.so
lrwxrwxrwx 1 root root 14 Oct  9 05:12 /usr/lib/arm-linux-gnueabihf/libqhyccd.so -> libqhyccd.so.1
$> ll /usr/lib/arm-linux-gnueabihf/libqhyccd.so.1
lrwxrwxrwx 1 root root 18 Oct  9 05:12 /usr/lib/arm-linux-gnueabihf/libqhyccd.so.1 -> libqhyccd.so.3.0.1
$> ll /usr/lib/arm-linux-gnueabihf/libqhyccd.so.3
lrwxrwxrwx 1 root root 18 Oct  9 05:12 /usr/lib/arm-linux-gnueabihf/libqhyccd.so.3 -> libqhyccd.so.3.0.1
$> ll /usr/lib/arm-linux-gnueabihf/libqhyccd.so.3.0.1
-rw-r--r-- 1 root root 1311584 Oct  9 05:12 /usr/lib/arm-linux-gnueabihf/libqhyccd.so.3.0.1
$> file /usr/lib/arm-linux-gnueabihf/libqhyccd.so.3.0.1
/usr/lib/arm-linux-gnueabihf/libqhyccd.so.3.0.1: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=95417040e4015299b14ff901a2729823db9183cb, stripped
Last edit: 5 years 5 months ago by Wouter van Reeven.
5 years 5 months ago #30250

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

  • Posts: 1957
  • Thank you received: 420
Just saw a new version coming in when I updated the software on the RPi3 but that didn't help:
$> sudo apt-get update && sudo apt-get dist-upgrade -y
...snip...
Get:10 http://ppa.launchpad.net/mutlaqja/indinightly/ubuntu xenial/main armhf libqhy armhf 3.0.1+r4247~201810100105~ubuntu16.04.1 [556 kB]
...snip...
Setting up libqhy (3.0.1+r4247~201810100105~ubuntu16.04.1) ...
...snip...
$> ldd /usr/bin/indi_qhy_ccd
/usr/bin/indi_qhy_ccd: error while loading shared libraries: libqhyccd.so.3: failed to map segment from shared object
$> file /usr/lib/arm-linux-gnueabihf/libqhyccd.so.3.0.1
/usr/lib/arm-linux-gnueabihf/libqhyccd.so.3.0.1: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, BuildID[sha1]=95417040e4015299b14ff901a2729823db9183cb, stripped
Last edit: 5 years 5 months ago by Wouter van Reeven.
5 years 5 months ago #30251

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

  • Posts: 1957
  • Thank you received: 420
I tried also on my Odroid and there it works:
...snip...
Setting up libqhy (3.0.1+r4247~201810100106~ubuntu18.04.1) ...
...snip...
$> ldd /usr/bin/indi_qhy_ccd
	linux-vdso.so.1 (0xbee54000)
	libindidriver.so.1 => /usr/lib/arm-linux-gnueabihf/libindidriver.so.1 (0xb6e4b000)
	libindiAlignmentDriver.so.1 => /usr/lib/arm-linux-gnueabihf/libindiAlignmentDriver.so.1 (0xb6e26000)
	libcfitsio.so.5 => /usr/lib/arm-linux-gnueabihf/libcfitsio.so.5 (0xb6cc9000)
	libqhyccd.so.3 => /usr/lib/arm-linux-gnueabihf/libqhyccd.so.3 (0x5d097000)
	libusb-1.0.so.0 => /lib/arm-linux-gnueabihf/libusb-1.0.so.0 (0x5d076000)
	libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0x5d051000)
	librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0x5d03b000)
	libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0x5cf28000)
	libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0x5cea7000)
	libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0x5ce7e000)
	libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x5cd86000)
	/lib/ld-linux-armhf.so.3 (0xb6fa7000)
...snip...
5 years 5 months ago #30253

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

  • Posts: 1957
  • Thank you received: 420
I tried on another RPi3 and the same as the first RPi3. When I try on the Odroid I see that INDI sends the commands to the filter wheel and I see the indicator led on the filter wheel light up but the wheel doesn't turn :(
5 years 5 months ago #30254

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

  • Posts: 1957
  • Thank you received: 420
I tried again on my MacBook and there is a difference there compared to the Odroid. When I try to change filters on the Odroid I see the red led light up and that indicates the first slot. However, when I do this on Mac I see the colour light up for the correct slot, e.g. blue for 2, green for 3 etc.

Anyway, I grabbed logs on both Mac and Odroid doing the same thing: start INDI and then changing the filter from 1 (Red) to 2 (Blue). It worked on Mac and not on Odroid. The logs look similar to me and don't provide info on the difference between the two but maybe I am overlooking something. Please let me know if I can do more tests.
5 years 5 months ago #30255
Attachments:

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

  • Posts: 2247
  • Thank you received: 223
I have a QHY5, plugged in to my Odroid C1, all is fully up-to-date (full reinstall of system 2 days ago...) and I must say that the QHY5 isn't behaving correctly.
It does tend to lock up and I get the following message:
2018-10-13T19:09:11: [ERROR] GetQHYCCDSingleFrame error (-1)

To unlock, I need to park the mount (just to be sure I can restart from the same location), stop indi drivers and start again.
Only then I can use the QHY5 again, until the next random lockup...
5 years 5 months ago #30381

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

  • Posts: 1309
  • Thank you received: 226
Gonzothegreat. I've had an issue with the Orion SSAG using the QHY driver that causes the camera to lockup if the image capture is aborted. Likewise I have to restart the indi drivers to fix it.
5 years 5 months ago #30388

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

  • Posts: 2247
  • Thank you received: 223
5 years 5 months ago #30396

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

I can confirm that on armhf systems, QHY library has linking issues. Still investigating...
The following user(s) said Thank You: Gonzothegreat, Jerry Black
5 years 5 months ago #30413

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

  • Posts: 985
  • Thank you received: 161
Gonzo, I've had issues with my QHY5 for a looong time. It did work perfectly years ago with an old driver called qhy-old until it has been removed. My QHY5 didn't behave reasonably ever since. Lock-ups, no video, all sorts of weird issues. Finally, I bought a cam from a different manufacturer and had no issues anymore. Now I read you have lock-ups like I had many moons ago. This IMO is just ridiculous. They don't get their act together as far as software is concerned and I can't see how something like this is going to survive in the market longer term.
Last edit: 5 years 5 months ago by Alfred.
5 years 5 months ago #30457

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

  • Posts: 460
  • Thank you received: 69
May i ask which camera you chose to replace it?
Last edit: 5 years 5 months ago by Jerry Black.
5 years 5 months ago #30459

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

  • Posts: 985
  • Thank you received: 161
I bought an ASI camera and my impression was such that I bought another one a few weeks later. It's a 294 Pro for deep sky and a 294 for guiding. The 294 definitely is overkill for guiding but on the other side you'll never ever again struggle to find a guide star. Never! With Indi/Ekos I have never experienced ANY issues with any of these cameras. My QHY5 has disappeared in the bottom drawer. You can have it for 20 Euros, seriously.
5 years 5 months ago #30461

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

Time to create page: 0.314 seconds