×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

[SOLVED] ASI ZWO driver keeps restarting

  • Posts: 315
  • Thank you received: 42
Mine was when running nightly on a NUC x86_64.
1 year 9 months ago #84208

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

  • Posts: 294
  • Thank you received: 54
I run my system on an ODroid N2 and I think Jerry uses one as well as an RPi which are indeed ARM devices. If this is the case, it is likely that StellarMate and similar ARM based devices will have problem whenever the next indi release comes out; unless the problem is fixed before obviously.

Gilles
1 year 9 months ago #84209

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

  • Posts: 460
  • Thank you received: 69
Gilles is correct I'm on an Odroid N2 as well (ARM RPi4 compatible).
1 year 9 months ago #84210

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

Just tested ASI120 on armhf and it works fine. is this arm64 specific? I will test that as well.
1 year 9 months ago #84226

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

I can also confirm it works fine on arm64.
1 year 9 months ago #84228

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

  • Posts: 1009
  • Thank you received: 133
Just recompiled the latest state (stellarsolver, INDI, indi-3rdparty, kstars) on both my laptop (x86_64) and Pi4 (aarch64), both openSUSE Tumbleweed.
No issues on the laptop (running local).
No luck on the Pi4 though. I enabled verbose logging, and when I try to connect I get this:
[2022-07-08T13:28:10.919 WEST DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI290MM Mini : "[DEBUG] Attempting to open ZWO CCD ASI290MM Mini... "
[2022-07-08T13:28:10.969 WEST DEBG ][           org.kde.kstars.indi] - Removing device "ZWO CCD ASI183MC Pro"
[2022-07-08T13:28:10.969 WEST DEBG ][           org.kde.kstars.indi] - Removing device "ZWO CCD ASI290MM Mini"
[2022-07-08T13:28:10.970 WEST DEBG ][           org.kde.kstars.indi] - INDIListener: Removing device "ZWO CCD ASI183MC Pro"
[2022-07-08T13:28:10.971 WEST INFO ][           org.kde.kstars.ekos] - "ZWO CCD ASI183MC Pro is offline."
[2022-07-08T13:28:10.989 WEST DEBG ][           org.kde.kstars.indi] - INDIListener: Removing device "ZWO CCD ASI290MM Mini"
[2022-07-08T13:28:10.990 WEST INFO ][           org.kde.kstars.ekos] - "ZWO CCD ASI290MM Mini is offline."
[2022-07-08T13:28:11.104 WEST DEBG ][           org.kde.kstars.indi] - Received new device ZWO CCD ASI183MC Pro

I have two cameras and one EAF. I get this reset when trying to connect to either of the two cameras,
The 183 is connected via USB3 to the Pi, the 290 and the EAF are connected to the hub of the 183. The EAF does work.
I was using indi-web initially, but using local start by EKOS doesn't change this.

Addition: I'm using the single driver "ZWO CCD" in the profile, not the specific "ZWO Camera x"
Last edit: 1 year 9 months ago by Peter Sütterlin.
1 year 9 months ago #84235

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

  • Posts: 1009
  • Thank you received: 133
Another note - I actually wasn't running local. I wanted to chnage the profile to local, but when saving I got an error
[2022-07-08T13:49:29.116 WEST WARN ][                org.kde.kstars] - "" "no such column: portselector Unable to execute statement"
[2022-07-08T13:49:29.117 WEST WARN ][                org.kde.kstars] - "UPDATE profile SET autoconnect=0 WHERE id=2" "no such column: portselector Unable to execute statement"
[2022-07-08T13:50:59.932 WEST WARN ][                org.kde.kstars] - "" "no such column: portselector Unable to execute statement"
[2022-07-08T13:50:59.934 WEST WARN ][                org.kde.kstars] - "UPDATE profile SET autoconnect=0 WHERE id=2" "no such column: portselector Unable to execute statement"
and it was reverted to remote....
Should I open a separate report for that?
1 year 9 months ago #84236

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

  • Posts: 460
  • Thank you received: 69
OK, so with yesterday's code base I'm still crashing kstars on the Oroid N2 Ubuntu 20.04.4 LTS aarch64 arm64

Here are the ekosdebugger kstars and indl logs, in case someone can make sense of them :)

Thanks!

p.s. I can workaround this crash if I use Phd2 for guiding and don't load the ZWO driver in kstars.
Last edit: 1 year 9 months ago by Jerry Black.
1 year 9 months ago #84263
Attachments:

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

  • Posts: 1009
  • Thank you received: 133
No updates here?

I have now downgraded only libasi, i.e., to the previous BLOBs, version 1.22 (seems 1.23 had been skipped?).

With that (i.e., without recompiling anything else) the error on the Pi is gone, I can connect to the camera, take images etc.
1 year 9 months ago #84302

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

  • Posts: 294
  • Thank you received: 54
No luck here as well, I am thus running a prior (working) release on my ARM based ODroid and hoping for a solution.
1 year 9 months ago #84303

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

  • Posts: 1009
  • Thank you received: 133
Looking at the backtrace, it only lists libASICamera2.so and libc.so.6.
So I wonder what glibc you use (also @Jasem, as it worked there). Mine is 2.35
1 year 9 months ago #84304

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

  • Posts: 969
  • Thank you received: 94
Hi everyone

1.24 seems to obsolete the older asi cameras such as the first issue 120mm. We have had success however using the same for guiding, but only 8 bit mode. Change to 8 bit (the default is 16bit) in indi before guiding and all is well.

I believe there is mention of an option to retain an older sdk for cases such as those described in this thread. That would be a good idea.
Cheers and clear skies,
Steve
1 year 9 months ago #84307

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

Time to create page: 0.895 seconds