-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZWO ASI6200MC indi_asi_ccd failure somewhere in /lib/aarch64-linux-gnu/libASICamera2.so #376
Comments
Is this with GIT? the ASI camera SDK was rolled back a few days ago due to reported crashes. |
I did a git clone within the last 24 hours.
…Sent from my iPhone
On Apr 18, 2021, at 10:49 AM, Jasem Mutlaq ***@***.***> wrote:
Is this with GIT? the ASI camera SDK was rolled back a few days ago due to reported crashes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Thu Apr 15 17:53:28 2021 +0300 libasi/armv6/libASICamera2.bin
Thu Apr 15 17:53:28 2021 +0300 libasi/armv7/libASICamera2.bin
Thu Apr 15 17:53:28 2021 +0300 libasi/armv8/libASICamera2.bin
Thu Apr 15 17:53:28 2021 +0300 libasi/mac/libASICamera2.bin
Thu Apr 15 17:53:28 2021 +0300 libasi/x64/libASICamera2.bin
Thu Apr 15 17:53:28 2021 +0300 libasi/x86/libASICamera2.bin
… On Apr 18, 2021, at 11:45 AM, John Mocenigo ***@***.***> wrote:
I did a git clone within the last 24 hours.
Sent from my iPhone
> On Apr 18, 2021, at 10:49 AM, Jasem Mutlaq ***@***.***> wrote:
>
>
>
> Is this with GIT? the ASI camera SDK was rolled back a few days ago due to reported crashes.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub <#376 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVI5BRF3F2Q3J3LQF2N36TTJLWPVANCNFSM43EJBTVA>.
>
|
To be a little more clear regarding my previous message:
$ git log -1 --format="%ad" -- libasi/armv8/libASICamera2.bin
Thu Apr 15 17:53:28 2021 +0300
I wanted to add that my suspicion is some sort of threading issue, which is really the only way I can explain that it sometimes works, but usually doesn’t (even during the same session, namely get one image, works; repeat, works; repeat fails - all in the same camera connection session).
I tried attaching gdb to the indi_asi_ccd process and stepping through and sometimes it worked that way and sometimes not as well, but I had a (anecdotally) higher success rate, which again makes me think it is a threading issue since gdb does a Heisenberg on thread behavior.
Would capturing a failure situation in gdb help you out even if what I capture looks like the stuff below (since, obviously, there is no source info)? It is not easy to do so I rather not spend the time if it is not going to be useful.
(gdb)
0x0000ffff998010d8 in ASIGetExpStatus ()
from /lib/aarch64-linux-gnu/libASICamera2.so
(gdb)
0x0000ffff998010dc in ASIGetExpStatus ()
from /lib/aarch64-linux-gnu/libASICamera2.so
(gdb)
0x0000ffff998010f4 in ASIGetExpStatus ()
from /lib/aarch64-linux-gnu/libASICamera2.so
(gdb)
0x0000ffff998010f8 in ASIGetExpStatus ()
from /lib/aarch64-linux-gnu/libASICamera2.so
(gdb)
0x0000ffff998010fc in ASIGetExpStatus ()
from /lib/aarch64-linux-gnu/libASICamera2.so
(gdb)
0x0000ffff99801100 in ASIGetExpStatus ()
from /lib/aarch64-linux-gnu/libASICamera2.so
… On Apr 18, 2021, at 12:22 PM, John Mocenigo ***@***.***> wrote:
Thu Apr 15 17:53:28 2021 +0300 libasi/armv6/libASICamera2.bin
Thu Apr 15 17:53:28 2021 +0300 libasi/armv7/libASICamera2.bin
Thu Apr 15 17:53:28 2021 +0300 libasi/armv8/libASICamera2.bin
Thu Apr 15 17:53:28 2021 +0300 libasi/mac/libASICamera2.bin
Thu Apr 15 17:53:28 2021 +0300 libasi/x64/libASICamera2.bin
Thu Apr 15 17:53:28 2021 +0300 libasi/x86/libASICamera2.bin
> On Apr 18, 2021, at 11:45 AM, John Mocenigo ***@***.*** ***@***.***>> wrote:
>
> I did a git clone within the last 24 hours.
>
> Sent from my iPhone
>
>> On Apr 18, 2021, at 10:49 AM, Jasem Mutlaq ***@***.*** ***@***.***>> wrote:
>>
>>
>>
>> Is this with GIT? the ASI camera SDK was rolled back a few days ago due to reported crashes.
>>
>> —
>> You are receiving this because you authored the thread.
>> Reply to this email directly, view it on GitHub <#376 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVI5BRF3F2Q3J3LQF2N36TTJLWPVANCNFSM43EJBTVA>.
>>
|
P.S. I ordered a “real” Linux box (a System76 Meerkat) that should arrive Wednesday, so that should at least confirm that it is not a RPi4-specific issue.
… On Apr 18, 2021, at 7:23 PM, John Mocenigo ***@***.***> wrote:
To be a little more clear regarding my previous message:
$ git log -1 --format="%ad" -- libasi/armv8/libASICamera2.bin
Thu Apr 15 17:53:28 2021 +0300
I wanted to add that my suspicion is some sort of threading issue, which is really the only way I can explain that it sometimes works, but usually doesn’t (even during the same session, namely get one image, works; repeat, works; repeat fails - all in the same camera connection session).
I tried attaching gdb to the indi_asi_ccd process and stepping through and sometimes it worked that way and sometimes not as well, but I had a (anecdotally) higher success rate, which again makes me think it is a threading issue since gdb does a Heisenberg on thread behavior.
Would capturing a failure situation in gdb help you out even if what I capture looks like the stuff below (since, obviously, there is no source info)? It is not easy to do so I rather not spend the time if it is not going to be useful.
(gdb)
0x0000ffff998010d8 in ASIGetExpStatus ()
from /lib/aarch64-linux-gnu/libASICamera2.so
(gdb)
0x0000ffff998010dc in ASIGetExpStatus ()
from /lib/aarch64-linux-gnu/libASICamera2.so
(gdb)
0x0000ffff998010f4 in ASIGetExpStatus ()
from /lib/aarch64-linux-gnu/libASICamera2.so
(gdb)
0x0000ffff998010f8 in ASIGetExpStatus ()
from /lib/aarch64-linux-gnu/libASICamera2.so
(gdb)
0x0000ffff998010fc in ASIGetExpStatus ()
from /lib/aarch64-linux-gnu/libASICamera2.so
(gdb)
0x0000ffff99801100 in ASIGetExpStatus ()
from /lib/aarch64-linux-gnu/libASICamera2.so
> On Apr 18, 2021, at 12:22 PM, John Mocenigo ***@***.*** ***@***.***>> wrote:
>
> Thu Apr 15 17:53:28 2021 +0300 libasi/armv6/libASICamera2.bin
> Thu Apr 15 17:53:28 2021 +0300 libasi/armv7/libASICamera2.bin
> Thu Apr 15 17:53:28 2021 +0300 libasi/armv8/libASICamera2.bin
> Thu Apr 15 17:53:28 2021 +0300 libasi/mac/libASICamera2.bin
> Thu Apr 15 17:53:28 2021 +0300 libasi/x64/libASICamera2.bin
> Thu Apr 15 17:53:28 2021 +0300 libasi/x86/libASICamera2.bin
>
>> On Apr 18, 2021, at 11:45 AM, John Mocenigo ***@***.*** ***@***.***>> wrote:
>>
>> I did a git clone within the last 24 hours.
>>
>> Sent from my iPhone
>>
>>> On Apr 18, 2021, at 10:49 AM, Jasem Mutlaq ***@***.*** ***@***.***>> wrote:
>>>
>>>
>>>
>>> Is this with GIT? the ASI camera SDK was rolled back a few days ago due to reported crashes.
>>>
>>> —
>>> You are receiving this because you authored the thread.
>>> Reply to this email directly, view it on GitHub <#376 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVI5BRF3F2Q3J3LQF2N36TTJLWPVANCNFSM43EJBTVA>.
>>>
>
|
Hi. I pulled the INDI core/lib and KStars sources from GitHub today (within the last hour), built and installed and now it is working consistently. I am running on a System 76 Meerkat Linux (Ubuntu 20.04 Mate) with the ZWO ASI6200 and ran 20 images in sequence, followed by 60 images in sequence. All FITS viewer options except "Single Window Capture" and "Limited Resources Mode" were turned on. To whomever did whatever, Thanks! |
Same problem on a different camera: ASI 294MM Pro on a Ubuntu 20.04 minipc; controlled remotely by a KStar on a remote PC. |
I am still seeing this with my ZWO ASI 533 mc pro. After 165 images, suddenly got this failure.
|
Bug Description:
Attempt to take exposure results in repeated failures that appear in log as follows:
Failure is somewhere in libASICamera2.so called from line 340 of asi_ccd.cpp:
ASI_ERROR_CODE ret = ASIGetExpStatus(mCameraInfo.CameraID, &status);
Environment:
Failure occurs with stable indi/kstars and nightly-build version and self-built from git clone.
Failure does not occur 100% of the time, but definitely above 95% of the time.
Failure also occurred using raspbian beta 64-bit OS.
Failures happen with USB bandwidth at 40 and at 80.
Failures happen regardless of FITS viewer settings (tried all reasonable combinations including off)
.
I am able to capture images reliably using 32-bit astroberry on RPi4 (FITS view off)
To Reproduce:
Expected behavior:
Pertinent part of log file is above - nothing to be gained by attaching file.
The text was updated successfully, but these errors were encountered: