×

INDI Library v1.9.8 Released (29 Sep 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

ASI usb3 camera retries 3 times on exposure and fails - git builds

  • Posts: 56
  • Thank you received: 7
@knro

Jasem, the rule  you´ve added does not work on my system (Tumbleweed):
edgar@Edgar-Desktop:~> cat /sys/module/usbcore/parameters/usbfs_memory_mb 16

Looks like cat /sys/module/usbcore/parameters/usbfs_memory_mb has to be set into "back apostrophes" (don´t know theright word in english :)

This is working for me:
ACTION=="add", SUBSYSTEM=="usb", RUN+="/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test `cat /sys/module/usbcore/parameters/usbfs_memory_mb` -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'"
1 year 8 months ago #69441

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

  • Posts: 522
  • Thank you received: 103
I did not have time to look into this until tonight, as my skies have been rotten and other things are taking some time anyway.

The change included the script, but it was just missing the execution of the `cat` statement.

Seescho, those are called "grave accents" in English, the back single quote. Using grave accents is the older, non-POSIX  way of execution in a shell, so we should probably change that to the $() POSIX way. The grave accents would have the same effect, but
in the future may not be as compatible with new shells.

<code>ACTION=="add", SUBSYSTEM=="usb", RUN+="/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'"</code>

I just put a PR up for the change.

Jim

 
12" pier with HDX110 using EQMod
ASI 1600 mono/color mains with ASI290MM in off-axis
ASI filter wheel
Moonlite focusers for the sharpening
AT115EDT w/.8x for the light
Fedora Linux, 100% INDI
Last edit: 1 year 8 months ago by Jim.
1 year 8 months ago #69454

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

  • Posts: 56
  • Thank you received: 7
1 year 7 months ago #69604

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

  • Posts: 1117
  • Thank you received: 182
Jim, if you have a chance, please look also into this problem: 

indilib.org/forum/ccds-dslrs/9089-indi-c....html?start=24#69568

The issue with the ZWO-EFW is still ongoing, although I was able to fix that for my own installation.  However, Brian still has no joy getting his ZWO-EAF connected.

These problems arose at the same time as the image buffer issue in middle of last month, so the cause is likely related to the changes that were made at the time.

Merci

Jo
Atlas Pro AZ-EQ, ASI1600MM-Pro, ASI120MM-S, ES102ED, WO-Z61, Nikon D3300, ASI-EFW, ZWO LRGB,Ha,O3,S2 filter set
1 year 7 months ago #69607

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

  • Posts: 522
  • Thank you received: 103
The current git build of indi-asi and libasi crash and dump core on the INDI server, and also cause kstars to crash and dump core on the client at the same time! I'd stay away from it for now. I sent Jasem some information to look at.

Jo, I don't have an EAF, but after reverting to the build of indi-asi from March 19, my ASI1600 MM Pro, ASI290 Mini, and ASI-EFW 8 are all working again.

Jim
12" pier with HDX110 using EQMod
ASI 1600 mono/color mains with ASI290MM in off-axis
ASI filter wheel
Moonlite focusers for the sharpening
AT115EDT w/.8x for the light
Fedora Linux, 100% INDI
The following user(s) said Thank You: Jose Corazon
1 year 7 months ago #69614

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

  • Posts: 56
  • Thank you received: 7
No crash with current build and ASI120mc-s. So I changed to ASI1600mm-pro: crash.
I went back in the git history. The first time, the crash comes in, is this commit:
Maybe someone of you can have a closer look into this.
Edgar
Last edit: 1 year 7 months ago by Edgar Scholz. Reason: formatting
1 year 7 months ago #69664

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

  • Posts: 964
  • Thank you received: 128
Is there any news on this?  I just tried to connect my camera (ASI183MC) locally to the laptop, and trying to take an image crashes the indi driver.  Streaming works on the first try (I can even select sub-fields etc), but a restart (also from within the stream window to change exposure) will crash it....
This is with libindi-1.9.0-92_gbd9110b4.  No issues with the previous one I had installed (libindi-1.9.0-21_gd9a5e309 as of March 11)
 
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
1 year 7 months ago #69877

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

  • Posts: 56
  • Thank you received: 7
I compiled from git just an hour before. The problem is not solved: ASI1600mm-pro crash the asi-cam-driver and kstars as well.

I played a bit with this stuff
 
The crash comes in with the new ASI-Cam-SDK 1.17.  "libASICamera2.so.1.17" is a shared library and dynamically loaded. I told my system to load the old SDK instead ( "libASICamera2.so.1.16.3" ). Result: No more crash. All is working well. So going back to SDK 1.16.3 should fix the problem

Edgar
Last edit: 1 year 7 months ago by Edgar Scholz.
1 year 7 months ago #69883

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

I can't replicate the crash with multiple ZWO cameras here, so what's going on?
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
1 year 7 months ago #69900

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

  • Posts: 56
  • Thank you received: 7
Jasem, which cameras did you use?

The little ASI120mm-s gives no crash for me. All is fine.
The big ASI1600mm-pro crash the cam driver and finally kstars.

That´s hat happen on my Linux-PC
Edgar
Last edit: 1 year 7 months ago by Edgar Scholz.
1 year 7 months ago #69902

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

  • Posts: 24
  • Thank you received: 14
This can actually be a problem for a specific camera.
Each camera has its own implementation of receiving data.

For example, Jasem keeps mentioning to me that he has no problems running 2 cameras at once.
Of course it is, the ASI178MM and ASI120MM-Mini cameras have a similar communication implementation, in a cooperative global variable. So you can't run them all at once.
The ASI178MC and ASI120MC cameras can already be run together, they have completely different communication implementations.
1 year 7 months ago #69903

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

  • Posts: 964
  • Thank you received: 128
No idea. I started kstars from the terminal, and got messages about the xml device file,
Dispatch command error(-1): Device ZWO CCD ASI183MC Pro not found
<setTextVector device="ZWO CCD ASI183MC Pro" name="DRIVER_INFO" state="Idle" timeout="60" timestamp="2021-04-11T09:39:07">
<oneText name="DRIVER_NAME">
ZWO CCD
</oneText>
<oneText name="DRIVER_EXEC">
indi_asi_ccd
</oneText>
<oneText name="DRIVER_VERSION">
1.9
</oneText>
<oneText name="DRIVER_INTERFACE">
2
</oneText>
</setTextVector>


I deleted the xml files, then it started without the error, but it still crashed. I was running in local mode. So I tried running indiserver manually and connect to remote localhost. Also crash, and the indiserver says
2021-04-11T09:45:29: Driver indi_asi_ccd: stderr EOF
Child process 17789 died

Also tried deleting ~/>ZWO/ASIconfig.xml, without change.

I tried running it in gdb, not sure if that is successful (I started indiserver manually, then connected via 'gdb -p PID').
Here's the output:
Thread 4 "indi_asi_ccd" received signal SIG33, Real-time event 33.
[Switching to Thread 0x7ffff55ad640 (LWP 18722)]
0x00007ffff6ef9a9a in __futex_abstimed_wait_common64 (
    futex_word=futex_word@entry=0x5555555ade98, expected=expected@entry=0, 
    clockid=clockid@entry=0, abstime=abstime@entry=0x0, 
    private=private@entry=0, cancel=cancel@entry=true)
    at ../sysdeps/nptl/futex-internal.c:74
Downloading source file /usr/src/debug/glibc-2.33-4.1.x86_64/nptl/../sysdeps/nptl/futex-internal.c...
74          err = INTERNAL_SYSCALL_CANCEL (futex_time64, futex_word, op, expected,
(gdb) bt
#0  0x00007ffff6ef9a9a in __futex_abstimed_wait_common64 (
    futex_word=futex_word@entry=0x5555555ade98, expected=expected@entry=0, 
    clockid=clockid@entry=0, abstime=abstime@entry=0x0, 
    private=private@entry=0, cancel=cancel@entry=true)
    at ../sysdeps/nptl/futex-internal.c:74
#1  0x00007ffff6ef9aff in __GI___futex_abstimed_wait_cancelable64 (
    futex_word=futex_word@entry=0x5555555ade98, expected=expected@entry=0, 
    clockid=clockid@entry=0, abstime=abstime@entry=0x0, 
    private=private@entry=0) at ../sysdeps/nptl/futex-internal.c:123
#2  0x00007ffff6ef3260 in __pthread_cond_wait_common (abstime=0x0, clockid=0, 
    mutex=0x5555555a2860, cond=0x5555555ade70) at pthread_cond_wait.c:504
#3  __pthread_cond_wait (cond=0x5555555ade70, mutex=0x5555555a2860)
    at pthread_cond_wait.c:619
#4  0x00007ffff6da50e0 in __gthread_cond_wait (__mutex=<optimized out>, 
    __cond=0x5555555ade70)
    at /usr/src/debug/gcc11-11.0.0+git183291-1.4.x86_64/obj-x86_64-suse-linux/x86_64-suse-linux/libstdc++-v3/include/x86_64-suse-linux/bits/gthr-default.h:865
#5  std::__condvar::wait (__m=..., this=0x5555555ade70)
    at /usr/src/debug/gcc11-11.0.0+git183291-1.4.x86_64/obj-x86_64-suse-linux/x86_64-suse-linux/libstdc++-v3/include/bits/std_mutex.h:155
#6  std::condition_variable::wait (this=this@entry=0x5555555ade70, __lock=...)
    at ../../../../../libstdc++-v3/src/c++11/condition_variable.cc:41
#7  0x00007ffff7e4dfa7 in std::_V2::condition_variable_any::wait<std::unique_lock<std::recursive_mutex> > (this=this@entry=0x5555555ade70, __lock=...)
    at /usr/include/c++/10/condition_variable:321
#8  0x00007ffff7e4d768 in std::_V2::condition_variable_any::wait<std::unique_lock<std::recursive_mutex>, INDI::SingleThreadPoolPrivate::SingleThreadPoolPrivate()::<lambda()>::<lambda()> > (__p=..., __lock=..., this=0x5555555ade70)
    at /usr/include/c++/10/condition_variable:330
#9  operator() (__closure=0x555555597b28)
    at /home/pit/Sources/indi/libs/indibase/thread/indisinglethreadpool.cpp:31
#10 std::__invoke_impl<void, INDI::SingleThreadPoolPrivate::SingleThreadPoolPrivate()::<lambda()> > (__f=...) at /usr/include/c++/10/bits/invoke.h:60
#11 std::__invoke<INDI::SingleThreadPoolPrivate::SingleThreadPoolPrivate()::<lambda()> > (__fn=...) at /usr/include/c++/10/bits/invoke.h:95
#12 std::thread::_Invoker<std::tuple<INDI::SingleThreadPoolPrivate::SingleThreadPoolPrivate()::<lambda()> > >::_M_invoke<0> (this=0x555555597b28)
    at /usr/include/c++/10/thread:264
#13 std::thread::_Invoker<std::tuple<INDI::SingleThreadPoolPrivate::SingleThreadPoolPrivate()::<lambda()> > >::operator() (this=0x555555597b28)
    at /usr/include/c++/10/thread:271
#14 std::thread::_State_impl<std::thread::_Invoker<std::tuple<INDI::SingleThreadPoolPrivate::SingleThreadPoolPrivate()::<lambda()> > > >::_M_run(void) (
    this=0x555555597b20) at /usr/include/c++/10/thread:215
#15 0x00007ffff6daade4 in std::execute_native_thread_routine (
    __p=0x555555597b20) at ../../../../../libstdc++-v3/src/c++11/thread.cc:82
#16 0x00007ffff6eed299 in start_thread (arg=0x7ffff55ad640)
    at pthread_create.c:473
#17 0x00007ffff6a9a3b3 in clone ()
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Does that help in any way?
 
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
1 year 7 months ago #69904

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

Time to create page: 0.926 seconds