×

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

Bi-monthly release with minor bug fixes and improvements

QHY Driver crashes on latest release of KStars/Ekos

  • Posts: 12
  • Thank you received: 0
I am having the same problem with the QHY driver crashing on Stellarmate. Using an SSAG that worked before the latest update.
5 years 2 weeks ago #35937

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

There was already an update to StellarMate that fixed the QHY, please double check that all software is updated. Check the software updater.
5 years 2 weeks ago #35938

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

  • Posts: 43
  • Thank you received: 0
I went to some pain to install Kstars/Ekos and the new Indi libtaty. I purged the okd installation and reinstalled the new. Is there a way to determine version of the QHY Indi driver one is using?
Lou
5 years 1 week ago #35966

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

  • Posts: 12
  • Thank you received: 0
Thank you. Apparently, the first time I ran software updater, it did not update the indi library. The camera is connected and capturing frames now.
5 years 1 week ago #35995

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

  • Posts: 1204
  • Thank you received: 558
I just retried and continue to get immediate crashes of indi_qhy_ccd on connect.
My device is a QHY 5L-II M
I ran with the feb 27 3.1 release,

Just to check, I then ran:
sudo apt-add-repository ppa:mutlaqja/indinightly
sudo apt-get update
sudo apt-get install indi-full kstars-bleeding gsc
and restarted Kstars. I confirmed it was now running a march 3rd, 3.1.1 release.
However, this made no differene. indi_qhy_ccd crashed immediately on connect.

I switched back to the ppa:mutlaqja/ppa repository, confirmed I was running 3.1 from feb 27 again (Build: 2019-02-27T16:55:56Z) and continued to get the crashes .

I'm running ubuntu 18.04 on a Intel stick. The other devices seem to connect ok (zwo asi 1600, asi filterwheel, orion mount).

Let me know if there's some log you'd like.
5 years 1 week ago #36028

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

Run the driver via gdb in the terminal:
sudo apt-get install libc6-dbg indi-qhy-dbg
gdb -ex "set follow-fork-mode child" -ex run --args indiserver -v indi_qhy_ccd indi_simulator_telescope

In Ekos, create a new profile, turn off Auto Connect and add Telescope Simulator + QHY CCD. Set mode to remote and leave it to localhost. In Logs, make sure to select Verbose Logging to File, check INDI + CCD. Click Start then in INDI Control Panel --> QHY CCD --> Options, make sure "Driver Debug" is checked. Then go back to Main Control Panel and press "Connect". Check the terminal to see if the driver crashed, if it did, type backtrace and paste the trace here. Also attach the KStars log file.
5 years 1 week ago #36029

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

  • Posts: 1204
  • Thank you received: 558
I did ask you asked. Note: the QHY 5L-IIm is attached as a guider.

Here is the backtrace, and the log from ~/.local/share/kstars/logs/2019-03-05/log_23-51-20.txt is attached.
Please let me know if I should undo any of these changes (e.g. apt-get remove ...) and if there's anything further
that would be helpful.

Hy


2019-03-06T07:51:56: Client 0: new arrival from 127.0.0.1:60856 - welcome!

Thread 2.1 "indi_qhy_ccd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff7fba900 (LWP 2244)]
0x00007ffff7aa989c in IUFindNumber () from /usr/lib/x86_64-linux-gnu/libindidriver.so.1
(gdb) backtrace
#0 0x00007ffff7aa989c in IUFindNumber () from /usr/lib/x86_64-linux-gnu/libindidriver.so.1
#1 0x00007ffff7ad3901 in INDI::CCDChip::setMinMaxStep(char const*, char const*, double, double, double, bool) ()
from /usr/lib/x86_64-linux-gnu/libindidriver.so.1
#2 0x000055555555d154 in QHYCCD::Connect (this=0x555555797b10) at ./indi-qhy/qhy_ccd.cpp:696
#3 0x00007ffff7ab04e2 in INDI::DefaultDevice::ISNewSwitch(char const*, char const*, ISState*, char**, int) ()
from /usr/lib/x86_64-linux-gnu/libindidriver.so.1
#4 0x00007ffff7abc3b1 in INDI::CCD::ISNewSwitch(char const*, char const*, ISState*, char**, int) () from /usr/lib/x86_64-linux-gnu/libindidriver.so.1
#5 0x000055555555ed57 in QHYCCD::ISNewSwitch (this=0x555555797b10, dev=0x5555557a3c80 "QHY CCD QHY5LII-M-6077e", name=0x5555557a3d80 "CONNECTION",
states=0x55555576fd30, names=0x5555557a3be0, n=1) at ./indi-qhy/qhy_ccd.cpp:1259
#6 0x000055555555a398 in ISNewSwitch (dev=0x5555557a3c80 "QHY CCD QHY5LII-M-6077e", name=0x5555557a3d80 "CONNECTION", states=0x55555576fd30,
names=0x5555557a3be0, num=1) at ./indi-qhy/qhy_ccd.cpp:175
#7 0x00007ffff7a99b30 in dispatch () from /usr/lib/x86_64-linux-gnu/libindidriver.so.1
#8 0x00007ffff7a9a199 in clientMsgCB () from /usr/lib/x86_64-linux-gnu/libindidriver.so.1
#9 0x00007ffff7a9ac49 in ?? () from /usr/lib/x86_64-linux-gnu/libindidriver.so.1
#10 0x00007ffff7a9ac6c in eventLoop () from /usr/lib/x86_64-linux-gnu/libindidriver.so.1
#11 0x00007ffff7a9a898 in main () from /usr/lib/x86_64-linux-gnu/libindidriver.so.1
#12 0x00007ffff34fab97 in __libc_start_main (main=0x7ffff7a9a789 <main>, argc=1, argv=0x7fffffffdfc8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffdfb8) at ../csu/libc-start.c:310
#13 0x000055555555945a in _start ()
5 years 1 week ago #36031
Attachments:

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

  • Posts: 1204
  • Thank you received: 558
also, forgot to mention, in case this is helpful.
I've never run any real sessions with this computer and ekos setup on this intel stick.
I've been trying to install and got this error--so the ekos isn't fully set up, but I don't think there's any setup for the guide camera. I was trying to set up things when I got this crash

I have, however, had many successful evenings with this equipment, and ekos running on a Raspberry Pi 3B+, though on 3.0. Weather's been too rainly lately here since the feb 27 release.
5 years 1 week ago #36032

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

  • Posts: 43
  • Thank you received: 0
Still doesn’t work for me either. I did another update to the latest Indi library using the commands
sudo apt-add-repository ppa:mutlaqja/ppa
sudo apt-get update
sudo apt-get install indi-full gsc
The system no longer crashes but after I press connect on the QHY5 control panel I get a yellow light, not green. Also when I go to the Guiding tab the QHY5 is not available as a guider.
I also get a nagging message that the QHY5 Ii LM driver has crashed. I know I am using the latest Indi driver release because my Altair Hypercam 183 M now works. How frustrating, i waited months for my main imaging camera to work, but when it started working the guide camera quit.
Lou
5 years 1 week ago #36041

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

  • Posts: 43
  • Thank you received: 0
Just to elaborate I am using a Linux desktop not a Stellarmate. If the QHY 5 problem was fixed on Stellarmate it is not fixed on acLinux desktop.
Lou
5 years 1 week ago #36042

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

This is most likely a build issue as the camera works fine here. Tomorrow a new build would be out for the QHY driver.
5 years 1 week ago #36043

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

  • Posts: 1204
  • Thank you received: 558
Thanks very much Jasem.
I'll test tomorrow.
Do you mean that I should check for a standard release tomorrow, or is it just the nightly build?
5 years 1 week ago #36044

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

Time to create page: 1.001 seconds