×

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

Bi-monthly release with minor bug fixes and improvements

[SOLVED] ASI ZWO driver keeps restarting

  • Posts: 459
  • Thank you received: 69
Hi,
The ASI ZWO driver repeated crashes and restarts for me on Ubuntumate 20.04.4 using the latest build from source (using NOU's build script gitea.nouspiro.space/nou/astro-soft-build). It will eventually crash kstars if I let it restart multiple times.
This issue appears to have developed since the 3rd party ASI library 1.24 (github.com/indilib/indi-3rdparty/commit/...8b90115386a183a3a25a) became available.
As no one else is reporting this, I assume something is out-of-sync on my machine.

How does one check to see if my ASI libraries are in-sync?

ekosdebugger doesn't seem to be launching / working for me

Attached is a log file, which doesn't provide much info IMHO.
1 year 8 months ago #84121
Attachments:

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

  • Posts: 311
  • Thank you received: 42
Jerry, I am not doing local builds but using the nightly. Have been out of action for a few days due to ASI cameras failing to start and retrying. I reverted to running the stable release and things work okay. Seems like it might be the same problem from the recent updates and not your mix up.
The following user(s) said Thank You: Jerry Black
1 year 8 months ago #84125

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

  • Posts: 294
  • Thank you received: 54
Hello Jerry, you're not alone. Same here with the latest build using your script, on my ODroid N2. ASI driver connects and disconnects almost immediately. I had a similar problem on another recent build that I fixed but I do not remember how :( ; maybe installing stable and re-building over it but I am not sure.

That's the risk we take by living on the leading edge :) .
The following user(s) said Thank You: Jerry Black
1 year 8 months ago #84127

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

  • Posts: 459
  • Thank you received: 69
Ok, so ekosdebugger works much better when you actually have gdb installed, hmm...

Here is the debug trace
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
[New inferior 2 (process 138948)]
[Inferior 1 (process 138942) detached]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
process 138948 is executing new program: /usr/bin/indi_asi_ccd
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fb5bf0f60 (LWP 138975)]
[Thread 0x7fb5bf0f60 (LWP 138975) exited]
[New Thread 0x7fb5bf0f60 (LWP 138976)]
[Thread 0x7fb5bf0f60 (LWP 138976) exited]
[New Thread 0x7fb5bf0f60 (LWP 138977)]
[New Thread 0x7fb53eff60 (LWP 138978)]
[New Thread 0x7fb4beef60 (LWP 138979)]
[New Thread 0x7fafffef60 (LWP 139240)]
[New Thread 0x7faf321f60 (LWP 139241)]
 
Thread 2.8 "indi_asi_ccd" received signal SIGBUS, Bus error.
[Switching to Thread 0x7faf321f60 (LWP 139241)]
0x0000007fb72e185c in __aarch64_ldadd8_acq () from /lib/aarch64-linux-gnu/libpthread.so.0
#0  0x0000007fb72e185c in __aarch64_ldadd8_acq () from /lib/aarch64-linux-gnu/libpthread.so.0
#1  0x0000007fb72da250 in __condvar_fetch_add_wseq_acquire (val=2, cond=0x55555bada4) at pthread_cond_common.c:37
#2  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55555badd4, cond=0x55555bada4) at pthread_cond_wait.c:403
#3  __pthread_cond_wait (cond=0x55555bada4, mutex=0x55555badd4) at pthread_cond_wait.c:647
#4  0x0000007fb7bf63a0 in InsertBufThd(bool*, void*) () from /usr/lib/aarch64-linux-gnu/libASICamera2.so
#5  0x0000007fb7be7190 in MyThr(void*) () from /usr/lib/aarch64-linux-gnu/libASICamera2.so
#6  0x0000007fb72d3624 in start_thread (arg=0x7fb7be7168 <MyThr(void*)>) at pthread_create.c:477
#7  0x0000007fb778749c in thread_start () at ../sysdeps/unix/sysv/linux/aarch64/clone.S:78

and the application log
2022-07-06T16:53:20: startup: /usr/bin/indiserver -r 0 -v indi_asi_ccd indi_gpsd indi_skysafari indi_pegasus_ppba indi_nikon_ccd indi_manual_wheel indi_pegasus_focuscube indi_celestron_gps
[Attaching after Thread 0x7fb7ff6010 (LWP 138942) fork to child process 138948]
[Detaching after fork from parent process 138942]
2022-07-06T16:53:20: Driver indi_asi_ccd: pid=138948 rfd=6 wfd=6 efd=7
2022-07-06T16:53:20: Driver indi_gpsd: pid=138949 rfd=8 wfd=8 efd=9
2022-07-06T16:53:20: Driver indi_skysafari: pid=138950 rfd=10 wfd=10 efd=11
2022-07-06T16:53:20: Driver indi_pegasus_ppba: pid=138951 rfd=12 wfd=12 efd=13
2022-07-06T16:53:20: Driver indi_nikon_ccd: pid=138952 rfd=14 wfd=14 efd=15
2022-07-06T16:53:20: Driver indi_manual_wheel: pid=138953 rfd=16 wfd=16 efd=17
2022-07-06T16:53:20: Driver indi_pegasus_focuscube: pid=138954 rfd=18 wfd=18 efd=19
2022-07-06T16:53:20: Driver indi_celestron_gps: pid=138955 rfd=20 wfd=20 efd=21
2022-07-06T16:53:20: listening to port 7624 on fd 5
2022-07-06T16:53:20: Local server: listening on local domain at: @/tmp/indiserver
2022-07-06T16:53:20: Driver indi_celestron_gps: snooping on GPS Simulator.GEOGRAPHIC_COORD
2022-07-06T16:53:20: Driver indi_celestron_gps: snooping on GPS Simulator.TIME_UTC
2022-07-06T16:53:20: Driver indi_celestron_gps: snooping on Dome Simulator.DOME_PARK
2022-07-06T16:53:20: Driver indi_celestron_gps: snooping on Dome Simulator.DOME_SHUTTER
2022-07-06T16:53:20: Driver indi_nikon_ccd: Number of cameras detected: 1.
2022-07-06T16:53:20: Driver indi_nikon_ccd: Detected camera model Nikon Z7 on port usb:001,009
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Telescope Simulator.EQUATORIAL_COORD
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Telescope Simulator.TELESCOPE_PIER_SIDE
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Rotator Simulator.ABS_ROTATOR_ANGLE
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Focuser Simulator.ABS_FOCUS_POSITION
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Focuser Simulator.FOCUS_TEMPERATURE
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on CCD Simulator.FILTER_SLOT
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on CCD Simulator.FILTER_NAME
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on SQM.SKY_QUALITY
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Celestron CGX.EQUATORIAL_EOD_COORD
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Celestron CGX.EQUATORIAL_COORD
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Celestron CGX.TELESCOPE_INFO
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Celestron CGX.GEOGRAPHIC_COORD
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Manual Filter.FILTER_SLOT
2022-07-06T16:53:20: Driver indi_nikon_ccd: snooping on Manual Filter.FILTER_NAME
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_COORD
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_PIER_SIDE
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Rotator Simulator.ABS_ROTATOR_ANGLE
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_FOCUS_POSITION
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Focuser Simulator.FOCUS_TEMPERATURE
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Celestron CGX.EQUATORIAL_EOD_COORD
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Celestron CGX.EQUATORIAL_COORD
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Celestron CGX.TELESCOPE_INFO
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Celestron CGX.GEOGRAPHIC_COORD
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Manual Filter.FILTER_SLOT
2022-07-06T16:53:22: Driver indi_asi_ccd: snooping on Manual Filter.FILTER_NAME
2022-07-06T16:53:55: Client 23: new arrival from local pid 139061 (user: 1000:1000) - welcome!
2022-07-06T16:53:55:
Driver indi_skysafari: INDI::BaseClient::connectServer: creating new connection...
2022-07-06T16:53:55: Client 24: new arrival from local pid 138950 (user: 1000:1000) - welcome!
2022-07-06T16:53:55: Driver indi_skysafari: INDI::BaseClient::connectServer: Already connected.
2022-07-06T16:53:55: Driver indi_asi_ccd: read: Connection reset by peer
<delProperty device="ZWO CCD ASI224MC"/>
2022-07-06T16:53:55: Driver indi_asi_ccd: Terminated after #0 restarts.

I don't know what the issue is, but at least here is the debug info.
Cheers
1 year 8 months ago #84137

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

  • Posts: 1208
  • Thank you received: 559
Jerry,

I had that issue a little while back.
For me, it was due to the fact that I had recompiled and installed indi, but not indi-3rdparty. Probably due to that new blob shared memory stuff.
Assuming you're recompiling from source, then make sure you pull the latest indi and indi-3rdparty, and then recompile and install indi, then indi-3rdparty-libs and then indi-3rdparty.

Hy
The following user(s) said Thank You: Jerry Black, Gilles Gagnon
1 year 8 months ago #84138

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

  • Posts: 294
  • Thank you received: 54
Hello Hy,

Tried what you suggested but it did not work. the ASI CCD driver issues remained. What I ended up doing is revert back to the July 3rd commit of indi-3rdparty by downloading and extracting the zip file and rebuilt from there. The ASI CCD driver started to work again. Will test it tonight.
1 year 8 months ago #84140

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

  • Posts: 1208
  • Thank you received: 559
I checked my telescope, and the latest commit I have in indi-3rdparty is June 24, so I must have done what I described above before July 3, and I am very likely running the same code you're successfully running when you rolled back to pre-July 3. Yes, I can see there was a large change to the ASI driver on July 3. Sorry, I'm not familiar with that.

Hy
1 year 8 months ago #84142

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

  • Posts: 459
  • Thank you received: 69
Thank you Gilles (and Hy) , it took me a bit, but I was able to duplicate your revert of indi-3rdparty and all seems good now.
1 year 8 months ago #84143

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

  • Posts: 294
  • Thank you received: 54
Good to hear Jerry.

The lesson learned today (for me), copy once and paste the following phrase 500 times:
"Unless you absolutely need that new indi/Ekos/KStars feature, refrain from pulling that latest commit, as you may be in for a few unwanted surprises!"
:)
1 year 8 months ago #84144

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

  • Posts: 459
  • Thank you received: 69
This is true. Also true is that I can't help wanting the newest features. e.g. Linear - 1 pass focusing.
1 year 8 months ago #84167

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

  • Posts: 1009
  • Thank you received: 133
I'm currently still at the state of June 19, so here everything works (also L1p ;)).

I can't check a new build, as I'm away from the telescope ATM, and the cameras are not connected.

I wonder whether it's related to this (from the release notes):
(2) The camera name from ASIGetCameraProperty no longer contains alias. If the application software needs to display alias, it needs to obtain them through the ASIGetID method.
Probably indi-asi has to be adapted there?

As for building yourself: I'd highly recommend setting up a build chain that produces installable packages, then in case of issues the roll-back is just one command to the package manager.... or at least use something like stow to manage different versions.
1 year 8 months ago #84170

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

  • Posts: 1208
  • Thank you received: 559
I just tested my system with the latest indi-3rdparty code and had no issues. I run on an Intel NUC. I contacted the person who submitted the code and he said that the new stuff is a binary blob he received from ZWO, and he tested with x64 (e.g. intel, amd) but not with arm64. Is it possible that everyone who's crashing is using ARM (e.g. raspberry pi)?

Hy
1 year 8 months ago #84207

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

Time to create page: 1.177 seconds