@AIRBOURN you didn't provide any logs, so I don't know if your error is the same or not, but when you say latest nightly, you made sure to have the latest indilib as well as asi driver and library? I had thought this particular error was mitigated now.

Jim

Read More...

knro post=70063 wrote: Alright, go ahead then and please prepare a PR if you can. Anyone reporting these crash issues to ZWO?
 


Oops, I missed this, but I see you were able to get it merged. Thank you.

Read More...

I find fewer drivers to be better, so chose a ZWO guider to go with ZWO mains. If the pair does not work, there is usually a good chance that the main will not work by itself either, so reverting 1 driver allows things to work again.
Right now is a good example, where the new ASI camera SDK appears to be causing some problems for myself and others. Reverting to the previous version, and both cameras work again.

I currently guide with a 290MM Mini, and quite like it.
$.02

Jim

Read More...

I have not had any problems with my filter wheel either.

Read More...

The spec won't need changed. It also has a date-stamp automatically, so will get updated with the merge.

Read More...

That might be advisable. I reverted to a copy of the build I had from March 19, and it worked great for the rest of the night last night.

running `git diff c882e29822f6b692a6d6db2e48e99cab88ac31a5 .` it looks like the previous version of the Camera SDK was 1.16.3. The EAF and EFW were updated on the 19th.
I think we can leave those alone and only change the camera version. Thoughts?

Read More...

I did not try asi_camera_test, but will when I set up again.

Read More...

I was able to get set up tonight, so thought I would try a quite recent build. Kstars crash, as others have reported. Here is the backtrace:

Core was generated by `kstars'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  std::__uniq_ptr_impl<ISD::CCDChip, std::default_delete<ISD::CCDChip> >::_M_ptr (this=0x98) at /usr/include/c++/10/bits/unique_ptr.h:173
173          pointer    _M_ptr() const { return std::get<0>(_M_t); }
[Current thread is 1 (Thread 0x7f16c8062a00 (LWP 4357))]
(gdb) bt
#0  std::__uniq_ptr_impl<ISD::CCDChip, std::default_delete<ISD::CCDChip> >::_M_ptr() const (this=0x98) at /usr/include/c++/10/bits/unique_ptr.h:173
#1  std::unique_ptr<ISD::CCDChip, std::default_delete<ISD::CCDChip> >::get() const (this=0x98) at /usr/include/c++/10/bits/unique_ptr.h:422
#2  ISD::CCD::getChip(ISD::CCDChip::ChipType) (this=0x0, cType=cType@entry=ISD::CCDChip::PRIMARY_CCD) at /usr/src/debug/kstars-3.5.3.git-20210412132123.fc33.x86_64/kstars/indi/indiccd.cpp:1918
#3  0x00005633127ad77c in Ekos::Focus::stop(bool) (this=0x563318241290, aborted=<optimized out>) at /usr/src/debug/kstars-3.5.3.git-20210412132123.fc33.x86_64/kstars/ekos/focus/focus.cpp:931
#4  0x00005633127b6035 in Ekos::Focus::completeFocusProcedure(bool) (this=0x563318241290, success=<optimized out>) at /usr/src/debug/kstars-3.5.3.git-20210412132123.fc33.x86_64/kstars/ekos/focus/focus.cpp:1483
#5  0x00007f16cce96386 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fff009a7cf0, r=0x563318241290, this=0x5633182a2520) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#6  doActivate<false>(QObject*, int, void**) (sender=0x56331824fdd0, signal_index=9, argv=argv@entry=0x7fff009a7cf0) at kernel/qobject.cpp:3886
#7  0x00007f16cce909a8 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x56331824fdd0, m=m@entry=0x7f16cde076a0 <QAbstractButton::staticMetaObject>, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff009a7cf0)
    at kernel/qobject.cpp:3946
#8  0x00007f16cd9eb316 in QAbstractButton::clicked(bool) (this=this@entry=0x56331824fdd0, _t1=<optimized out>) at .moc/moc_qabstractbutton.cpp:308
#9  0x00007f16cd9ebcde in QAbstractButtonPrivate::emitClicked() (this=this@entry=0x563318250960) at widgets/qabstractbutton.cpp:415
#10 0x00007f16cd9ed673 in QAbstractButtonPrivate::click() (this=this@entry=0x563318250960) at widgets/qabstractbutton.cpp:408
#11 0x00007f16cd9ed855 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) (this=0x56331824fdd0, e=0x7fff009a82b0) at widgets/qabstractbutton.cpp:1044
#12 0x00007f16cd93cb1e in QWidget::event(QEvent*) (this=0x56331824fdd0, event=0x7fff009a82b0) at kernel/qwidget.cpp:9019
#13 0x00007f16cd8fbec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x56331824fdd0, e=0x7fff009a82b0) at kernel/qapplication.cpp:3632
#14 0x00007f16cd902eeb in QApplication::notify(QObject*, QEvent*) () at kernel/qapplication.cpp:3076
#15 0x00007f16cce66bd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x56331824fdd0, event=0x7fff009a82b0) at kernel/qcoreapplication.cpp:1063
#16 0x00007f16cd901efa in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool)
    (receiver=receiver@entry=0x56331824fdd0, event=event@entry=0x7fff009a82b0, alienWidget=alienWidget@entry=0x56331824fdd0, nativeWidget=0x5633170265d0, buttonDown=buttonDown@entry=0x7f16cde3a330 <qt_button_down>, lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2614
#17 0x00007f16cd955375 in QWidgetWindow::handleMouseEvent(QMouseEvent*) (this=0x5633174f82f0, event=0x7fff009a8560) at kernel/qwidgetwindow.cpp:683
#18 0x00007f16cd9586be in QWidgetWindow::event(QEvent*) (this=0x5633174f82f0, event=0x7fff009a8560) at kernel/qwidgetwindow.cpp:300
#19 0x00007f16cd8fbec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x5633174f82f0, e=0x7fff009a8560) at kernel/qapplication.cpp:3632
#20 0x00007f16cce66bd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5633174f82f0, event=0x7fff009a8560) at kernel/qcoreapplication.cpp:1063
#21 0x00007f16cd2a2143 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at kernel/qguiapplication.cpp:2275
#22 0x00007f16cd2838cc in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169
#23 0x00007f16baa3947e in xcbSourceDispatch(GSource*, GSourceFunc, gpointer) (source=source@entry=0x563313c00750) at qxcbeventdispatcher.cpp:105
#24 0x00007f16cb9dba9f in g_main_dispatch (context=0x7f16b4005000) at ../glib/gmain.c:3325
#25 g_main_context_dispatch (context=0x7f16b4005000) at ../glib/gmain.c:4043
#26 0x00007f16cba2da98 in g_main_context_iterate.constprop.0 (context=context@entry=0x7f16b4005000, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4119
#27 0x00007f16cb9d8e73 in g_main_context_iteration (context=0x7f16b4005000, may_block=1) at ../glib/gmain.c:4184
#28 0x00007f16cceb36f3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x563313ad2160, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#29 0x00007f16cce6557b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7fff009a8890, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#30 0x00007f16cce6d1b4 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#31 0x000056331239c082 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kstars-3.5.3.git-20210412132123.fc33.x86_64/kstars/main.cpp:346



Read More...

Jim replied to the topic 'Remove Sticky Announcement?' in the forum. 1 week ago

Ideally it would just stay gone when dismissed until it is updated again, by checking a cookie. At worst it should stay gone for the session. I looked briefly to see if there were settings for it, but have not found much yet. It can be turned off, but Jasem likes to use it for INDI releases.

Jim
 

Read More...

jpaana post=69937 wrote: Libasi package also contains the udev rule file, which has that usbfs 256MB memory line in the old version, but not in new one.

This is true, but it still exists. It was just moved to INDIlib, and should have the same effect. This change has been working for me now for  some time. Jasem moved it there because many devices require it, so indilib is a good central place to manage it.
I still suspect changes in the SDK/driver from ZWO as having some differences to figure out.

Jim

Read More...

Very nice, Marc. I have a similar equipment configuration, and last I checked (clouds and life), my 1600s and 290 mini were also working together with the EFW8.

BTW, not sure if you are aware or not, but I put together a Fedora Copr for INDI, Kstars, stellarsolver, and ekosdebugger that keeps the most recent packages built in RPM format, available here:

copr.fedorainfracloud.org/coprs/xsnrg/

Jim

Read More...

Jim replied to the topic 'ASI EAF not recognized in Nightly' in the forum. 3 weeks ago

Hi Brian,

The missing line was moved to indilib and changed slightly so that it only changes the memory allocation if it is not already set to something higher. This was on purpose, and seems to be working now, so I do not think this is the issue, unless you did not also update indilib? Something to check anyway.

You can also verify the setting by running

cat /sys/module/usbcore/parameters/usbfs_memory_mb
After a reboot it may say 16, but after running indi, it should say 256.

Either way, the usb memory allocation shouldn't affect device discovery.

More suspect is the update made on the 19th, to libasi, where the ZWO SDK was updated. Before that, only the version number changed for the release of 1.8.9, nothing else in libasi changed, all the way back to Jan 4. Can you install a version just before March 19 to verify the focuser still works at that point?

Jim



 

Read More...

Thanks Brian. In reading back through the thread, it looks like the topic changed a bit in page 2. To keep it clean, can you start a new thread for debugging the EAF?

If you have time, please provide a set of logs from the system start. www.indilib.org/support/logs-submission.html shows how to get them if you need it.

Jim

Read More...