Hi,

* I am running 64bit Stellarmate on a RPi4. Worked fine until I upgraded the software. When I connect my equipment I now get the message "ïndi_asi_ccd_crashed". No idea how to fix this......
* I burned an older version of my Stellarmate, so I could run my system last night, but I do like to update/upgrade every once in a while.
* Attached is the INDI logfile, and below the lines from the logfile referring to the indi_asi_ccd library. Just to be clear: prior to the software update the ZWO cameras just worked fine.

Anybody and suggestions?

Regards,
Auke

[2022-08-11T08:53:46.851 CEST DEBG ][ org.kde.kstars.indi] - Stopping INDI Driver "indi_asi_ccd"
[2022-08-11T08:53:46.862 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: stop indi_asi_ccd"
[2022-08-11T08:53:46.863 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "dp->name: indi_ioptronv3_telescope - tDriver: indi_asi_ccd"
[2022-08-11T08:53:46.863 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "dp->name: indi_asi_ccd - tDriver: indi_asi_ccd"
[2022-08-11T08:53:46.863 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "dp->name: indi_pegasus_ppba - tDriver: indi_asi_ccd"
[2022-08-11T08:53:46.863 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2022-08-11T08:53:47.463 CEST INFO ][ org.kde.kstars.ekos.guide] - "Reconnecting to PHD2 Host: localhost, on port 4,400. . ."
[2022-08-11T08:53:47.467 CEST INFO ][ org.kde.kstars.ekos.guide] - "The connection was refused by the peer. Make sure the PHD2 is running, and check that the host name and port settings are correct."
[2022-08-11T08:53:47.852 CEST DEBG ][ org.kde.kstars.indi] - Adding managed driver "ZWO CCD"
[2022-08-11T08:53:47.852 CEST DEBG ][ org.kde.kstars.indi] - Starting INDI Driver "indi_asi_ccd"
[2022-08-11T08:53:47.853 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: start indi_asi_ccd"
[2022-08-11T08:53:47.853 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: Starting driver indi_asi_ccd"
[2022-08-11T08:53:47.854 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-08-11T06:53:47: Driver indi_asi_ccd: pid=2002 rfd=5 wfd=12 efd=15"
[2022-08-11T08:53:47.854 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2022-08-11T08:53:47.880 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-08-11T06:53:47: Driver indi_asi_ccd: indi_asi_ccd: symbol lookup error: indi_asi_ccd: undefined symbol: _ZN4INDI3CCD15addFITSKeywordsEPNS_7CCDChipE"
[2022-08-11T08:53:47.881 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2022-08-11T08:53:47.881 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-08-11T06:53:47: Driver indi_asi_ccd: stderr EOF"
[2022-08-11T08:53:47.882 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-08-11T06:53:47: Driver indi_asi_ccd: Terminated after #0 restarts."
[2022-08-11T08:53:47.882 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2022-08-11T08:53:47.882 CEST CRIT ][ org.kde.kstars.indi] - INDI driver "indi_asi_ccd" crashed!
[2022-08-11T08:53:47.889 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "Child process 2002 died"
[2022-08-11T08:53:47.890 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2022-08-11T08:53:47.962 CEST INFO ][ org.kde.kstars.ekos] - "Unable to establish:\n+ ZWO CCD\nPlease ensure the device is connected and powered on."

Just tested with latest update and I cannot recreate this crash, the driver starts just fine. Make sure to run the software updater again.

Hi,

I´m getting the same error in a Rasbperry Pi 3 with Raspbian Buster 32 bits. It worked fine before update to 3.6.0.

Linux astroberry 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux

This is my log:

[2022-09-02T16:12:34.938 CEST DEBG ][ org.kde.kstars.indi] - Adding managed driver "ZWO Camera"
[2022-09-02T16:12:34.939 CEST DEBG ][ org.kde.kstars.indi] - Starting INDI Driver "indi_asi_single_ccd"
[2022-09-02T16:12:34.944 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: start indi_asi_single_ccd -n \"ZWO Camera 2\""
[2022-09-02T16:12:34.945 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "With name: ZWO Camera 2"
[2022-09-02T16:12:34.945 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: Starting driver indi_asi_single_ccd"
[2022-09-02T16:12:34.946 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-09-02T14:12:34: Driver indi_asi_single_ccd: pid=2076 rfd=10 wfd=15 efd=16"
[2022-09-02T16:12:34.946 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2022-09-02T16:12:35.059 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-09-02T14:12:35: Driver indi_asi_single_ccd: indi_asi_single_ccd: symbol lookup error: indi_asi_single_ccd: undefined symbol: _ZN4INDI3CCD15addFITSKeywordsEPNS_7CCDChipE"
[2022-09-02T16:12:35.059 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2022-09-02T16:12:35.062 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-09-02T14:12:35: Driver indi_asi_single_ccd: stderr EOF"
[2022-09-02T16:12:35.062 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2022-09-02T16:12:35.062 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-09-02T14:12:35: Driver indi_asi_single_ccd: Terminated after #0 restarts."
[2022-09-02T16:12:35.063 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: "Child process 2076 died"
[2022-09-02T16:12:35.063 CEST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2022-09-02T16:12:35.063 CEST CRIT ][ org.kde.kstars.indi] - INDI driver "indi_asi_single_ccd" crashed!

I´m using the stable version of Kstar and Indi (I only updated to 3.6.0 with apt upgrade). I tried to compile the las version from git but my poor raspberry has not enough RAM. At first I thought it was the ZWO drivers issue with the last update, but @Peter Sütterlin told me that issue was only in 64 bits versions.

Any idea?

Thank you!

Finally, I installed a fresh Raspbian Bullseye 64 bits on my RPI3 and I run the Astropi3 script. After one day of compiling everything works. I will test deeper the next night I use my telescope.

Thanks!

I am getting the same error too, after upgrading. It took me a day to install astroberry and do the upgrade/update. Now that astroberry is not working I may have to abandon it - we have very little control, it works or it doesn't and there's nothing you can do.

The Raspberry Pi installation instructions seem to use astroberry though. That means that I will end up with an old Ekos version again? There was one feature for which I wanted a newer version.

Maybe I need to run the astropi3 script. Or simply give up on Ekos, I can't handle building it from source.

Looking through the astroberry bug list I am getting the impression that astroberry is no longer maintained. Too bad! Are there any ready-made and up-to-date KStars/Ekos binaries available? If not, only Linux experts can perform an up-to-date Ekos installation.

Hi,

I left to use astroberry for this reason and now I use astropi3.

In the script, you can edit the repositories and set the branch that you want to compile. If you have any doubt I can help you.

In addition, I think there are some broken packages, I can send you a copy of my modified script if you want.

Best regards.

Thanks Juan, I started astropi3. Not quite sure if it will work for my Pi4B or what Ekos version is installed but so far, no problems.

As I was writing the above line, the installation is done in just about a half hour. Of course, it will not work all at once, that is impossible...

But it works! At least, my ASI2600MM and ASI120MM cameras are now connected, which is what I needed from this installation.

So far so good. The indi version is 3.6.0 like I wanted. That is a good start of my day. I ranted too soon.