×

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

Bi-monthly release with minor bug fixes and improvements

Focus Capture keeps crashing with Canon Driver

  • Posts: 29
  • Thank you received: 1
Hi Guys,
I updated Ekos 2 weeks ago and was using it for the first time tonight since. Every time i went to capture an image in the focuser tab, it would take the image but as it was trying to load it would keep crashing when I was using my Canon DSLR. This would cause the canon driver to crash and I would have to restart it. However, I could take sequences and preview snapshots in the image tab without issue with my DSLR. If i then tried to autofocus it would crash the Canon driver. (I should note that I could capture a frame with my guide camera without issue).
Here is the excerpt from the log during the crash:
[2019-02-23T22:49:20.584 GMT DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 1100D : "[DEBUG] read_libraw: raw_width: 4352 top_margin 18 left_margin 62 first_visible_pixel 78398 "
[2019-02-23T22:49:20.584 GMT DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 1100D : "[DEBUG] read_libraw: rawdata.sizes.width: 4290 rawdata.sizes.height 2856 memsize 24504480 bayer_pattern RGGB "
[2019-02-23T22:49:20.665 GMT DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 1100D : "[DEBUG] read_libraw: memsize (24504480) naxis (2) w (4290) h (2856) bpp (16) pattern (RGGB) "
[2019-02-23T22:49:20.701 GMT DEBG ][ org.kde.kstars.indi] - Canon DSLR EOS 1100D : "[DEBUG] Subframing... subFrameSize: 50 - oneFrameSize: 50 - startY: 2852 - endY: 2857 - lineW: 10 - subX: 4278 "
[2019-02-23T22:49:20.751 GMT DEBG ][ org.kde.kstars.indi] - INDI Server: "Child process 13836 died"
[2019-02-23T22:49:20.751 GMT DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-02-23T22:49:20: Driver indi_canon_ccd: stderr EOF"
[2019-02-23T22:49:20.751 GMT DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-02-23T22:49:20: Driver indi_canon_ccd: restart #1"
[2019-02-23T22:49:20.751 GMT DEBG ][ org.kde.kstars.indi] - INDI Server: "2019-02-23T22:49:20: Driver indi_canon_ccd: pid=4892 rfd=5 wfd=21 efd=22"

Would anyone have any ideas as to what's going wrong?
Thanks,
Lenny.
5 years 1 month ago #35388

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

  • Posts: 9
  • Thank you received: 0
Hey Lenny,
I am having the same problems on the latest nightly, too.
Does it happen every time you try to autofocus? I got it to work several times but some camera operations randomly crash the driver and I had to restart the INDI server and Kstars to get it working again. Sometimes Kstar exited with no error message at all.
It did happen on the autofocus tab, capturing worked without any problems (aside from a "slighty" out of focus camera ;-))
I am using the EOS 5D Mark II, if that matters.
I am going to try it again this evening, how can I see the logs so that I can provide further information?

Best regards,
Dominik
5 years 1 month ago #35398

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

I just tested with Canon and cannot get a crash. Can you debug KStars? Run it in the console:
gdb -ex run --args kstars

If it crashes, just go back to the console and type bt to get the backtrace and post it here.
5 years 1 month ago #35405

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

  • Posts: 29
  • Thank you received: 1
I'm running Kstars on a raspberry Pi when I try to launch it with gdb i get the following error
Reading symbols from kstars...Reading symbols from /usr/lib/debug/.build-id/4b/1326405df8204912d7ccbebd917e9cb832e314.debug...done.
done.
Starting program: /usr/bin/kstars

Program received signal SIGSEGV, Segmentation fault.
0x76fd9dde in ?? () from /lib/ld-linux-armhf.so.3
5 years 1 month ago #35423

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

Try this:
sudo apt-get install libc6-dbg

then try again.
5 years 1 month ago #35425

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

  • Posts: 29
  • Thank you received: 1
Hi Jasem,
Thank you for taking the time to respond, I figured out the problem as it turns out I'm an idiot, For some reason, my sensor size wasn't correct it was off by a couple of pixels so when i was taking FITS images during the capture it failed to frame it properly. Once I corrected the sensor size back to what it should be the issue was resolved.
Apologies for the wild goose chase.
Thanks again,
Lenny.
5 years 1 month ago #35430

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

Time to create page: 0.389 seconds