Wow, just got the system back up tonight and double checked. Sure enough, connected with an existing profile, and PAA speed = 1x. Is that a bug? Also, when PAA used to run and you hit stop and it confirmed you wanted to stop, it used to park, is that an option any more?

Also, thanks for the quick reply, I would have been banging my head on the wall again tonight on this.

Read More...

I have been working with KStars/Ekos/INDI for about 5 years now and I love this stuff. I have even created custom focusers for several of my telescopes, but now, I am running into a peculiar issue that seems to be related to the imaging trains feature.

My gear setup is:

* Primary Telescope
* Primary Camera
* Focuser
* Guide Camera
* Guide Telescope
* Mount (Skywatcher EQ-6R using EQMOD)

I define this in the imaging train window and close it. Now, if I do a polar aligment, the mount does not move. I can hear it unpark, but no movement. In fact, I can hear the motors whine. If I manually move the mount using commands in the mount tab, that works fine. I can park it and it will go back to where it needs to be.

If I delete/recreate a new train where the guide camera has no mount defined, it seems to work. But, this too is flakey and sometimes when I come back to the system at later date, it stops working again.

I am running KStars 2023-03-02T22:19:06Z

My question is: What is the proper way to setup my gear in the optical train?

Also, why can't I edit my optical train if I don't select "auto connect" from the INDI configuration manager? If I leave auto-connect off and turn on the "port selector", I can't edit the optical/imaging train.

Read More...

You could look at running VirtualBox on Windows and pass in the USB devices directly. One issue you may find is with the "ephemeral" nature of some USB devices. For example, if you plug a QHY camera into a system, it will be identified as one device, which will cause the firmware to be loaded from udev and then it will show up as a new device. You will have to pass both deviceIds into your VBox image. This happens with network adapters too, a lot of cheap wifi adapters will look like a CDROM/DVD at first to linux and you have to "eject" them for them to show as wifi devices.

Read More...

William Curtis replied to the topic 'Kstars keeps crashing' in the forum. 4 years ago

Works now, thank you. I rebuilt from source, ran from the build directory, all worked fine. I could create a new configuration, configure all devices and save the changes. I could then relaunch that app, and it still worked (with changes). I rebooted the laptop where it runs, reconnected the devices and they all came up like they should.

I also did a "clean" and "install" and that worked as well.

Thanks, it doesn't look like a really easy fix, the nuance of the Blocking vs. Non-Blocking couldn't have been an easy one to figure out.

Read More...

William Curtis replied to the topic 'Kstars keeps crashing' in the forum. 4 years ago

If you all want another tester, hit me up, I can easily reproduce locally. I am running on an x64 Ubuntu 18.04 system.

Cloudy here as well, so not doing much but preparing for a clear night.

Read More...

William Curtis replied to the topic 'Kstars keeps crashing' in the forum. 4 years ago

Thanks, didn't know if any of the info was helping. Here's for hoping the fix is near!

Read More...

William Curtis replied to the topic 'Kstars keeps crashing' in the forum. 4 years ago

I kept on chugging through this issue.

  • Complete uninstall of KStars and INDI, re-installed.
  • Cleaned out the .indi and .local/share/kstars folders
  • Downloaded KStars from Github
  • Recompiled

At this point, application was broken like it was. Then I applied the patch. Still broken, but with new error around the Status LED.

Thinking that the problem was related to threading, I extended the Blocking Queue and Queued Connections to the individual components. This appears to have worked.
 # In the indilistener.cpp
    connect(cm, &ClientManager::newINDIDevice, this, &INDIListener::processDevice, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::newINDIProperty, this, &INDIListener::registerProperty, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::removeINDIDevice, this, &INDIListener::removeDevice, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::removeINDIProperty, this, &INDIListener::removeProperty, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::newINDISwitch, this, &INDIListener::processSwitch, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::newINDIText, this, &INDIListener::processText, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::newINDINumber, this, &INDIListener::processNumber, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::newINDILight, this, &INDIListener::processLight, Qt::BlockingQueuedConnection);
    connect(cm, &ClientManager::newINDIBLOB, this, &INDIListener::processBLOB, Qt::BlockingQueuedConnection);

#in the guimanager.cpp
    connect(cm, &ClientManager::newINDISwitch, gdm, &INDI_D::updateSwitchGUI, Qt::QueuedConnection);
    connect(cm, &ClientManager::newINDIText, gdm, &INDI_D::updateTextGUI, Qt::QueuedConnection);
    connect(cm, &ClientManager::newINDINumber, gdm, &INDI_D::updateNumberGUI, Qt::QueuedConnection);
    connect(cm, &ClientManager::newINDILight, gdm, &INDI_D::updateLightGUI, Qt::QueuedConnection);
    connect(cm, &ClientManager::newINDIBLOB, gdm, &INDI_D::updateBLOBGUI, Qt::QueuedConnection);
    connect(cm, &ClientManager::newINDIMessage, gdm, &INDI_D::updateMessageLog, Qt::QueuedConnection);




Read More...

William Curtis replied to the topic 'Kstars keeps crashing' in the forum. 4 years ago

Everything works fine for me, until I add hardware, shutdown kstars, and then restart. Once I go to "start" INDI in EKOS/Kstars, it fails.

FYI, I am excited to try out the new features, I hope this can get resolved.

Read More...

William Curtis replied to the topic 'Kstars keeps crashing' in the forum. 4 years ago

Latest PPA or latest Github?

Read More...

William Curtis replied to the topic 'Kstars keeps crashing' in the forum. 4 years ago

Still having issues with the latest build, with the patch. The application is getting further. I can setup a device now, but when I go back in and try to load a configuration, it crashes again.

Starting program: /home/myuser/sand-box/kstars/kstars/kstars
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffdc106700 (LWP 24088)]
[New Thread 0x7fffd1fb6700 (LWP 24090)]
[New Thread 0x7fffd17b5700 (LWP 24091)]
[New Thread 0x7fffcbfff700 (LWP 24092)]
[New Thread 0x7fffbffff700 (LWP 24094)]
[New Thread 0x7fffb77fe700 (LWP 24095)]
[New Thread 0x7fffbf7fe700 (LWP 24096)]
[New Thread 0x7fffbe5ed700 (LWP 24101)]
[New Thread 0x7fffbcb9a700 (LWP 24102)]
[New Thread 0x7fffb7fff700 (LWP 24103)]
[New Thread 0x7fffb6ffd700 (LWP 24104)]
[New Thread 0x7fff9ffff700 (LWP 24105)]
[New Thread 0x7fffb48f9700 (LWP 24106)]
[New Thread 0x7fff9f7fe700 (LWP 24107)]
[New Thread 0x7fff9effd700 (LWP 24108)]
[New Thread 0x7fff9e7fc700 (LWP 24109)]
[New Thread 0x7fff9dffb700 (LWP 24110)]
[New Thread 0x7fff9d5bf700 (LWP 24111)]
[Thread 0x7fff9d5bf700 (LWP 24111) exited]
[Thread 0x7fffbcb9a700 (LWP 24102) exited]
[New Thread 0x7fffbcb9a700 (LWP 24143)]
[New Thread 0x7fff9d5bf700 (LWP 24162)]

Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
0x00005555562d8d54 in INDI::Property::getState() const ()
(gdb) bt
#0  0x00005555562d8d54 in INDI::Property::getState() const ()
#1  0x00005555559d5514 in INDI_P::updateStateLED() (this=0x55555b090ac0) at /home/myuser/sand-box/kstars/kstars/indi/indiproperty.cpp:64
#2  0x00005555559d573a in INDI_P::initGUI() (this=0x55555b090ac0) at /home/myuser/sand-box/kstars/kstars/indi/indiproperty.cpp:101
#3  0x00005555559d52d1 in INDI_P::INDI_P(INDI_G*, INDI::Property*) (this=0x55555b090ac0, ipg=0x55555a14dc10, prop=0x7fffa002ae30)
    at /home/myuser/sand-box/kstars/kstars/indi/indiproperty.cpp:52
#4  0x00005555559d3805 in INDI_G::addProperty(INDI::Property*) (this=0x55555a14dc10, prop=0x7fffa002ae30) at /home/myuser/sand-box/kstars/kstars/indi/indigroup.cpp:74
#5  0x00005555559cfe71 in INDI_D::buildProperty(INDI::Property*) (this=0x55555a66cd60, prop=0x7fffa002ae30) at /home/myuser/sand-box/kstars/kstars/indi/indidevice.cpp:97
#6  0x00005555559cc535 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<INDI::Property*>, void, bool (INDI_D::*)(INDI::Property*)>::call(bool (INDI_D::*)(INDI::Property*), INDI_D*, void**) (f=(bool (INDI_D::*)(INDI_D * const, INDI::Property *)) 0x5555559cfcfc <INDI_D::buildProperty(INDI::Property*)>, o=0x55555a66cd60, arg=0x7fffa002b9b0)
    at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:136
#7  0x00005555559cc035 in QtPrivate::FunctionPointer<bool (INDI_D::*)(INDI::Property*)>::call<QtPrivate::List<INDI::Property*>, void>(bool (INDI_D::*)(INDI::Property*), INDI_D*, void**) (f---Type <return> to continue, or q <return> to quit---
=(bool (INDI_D::*)(INDI_D * const, INDI::Property *)) 0x5555559cfcfc <INDI_D::buildProperty(INDI::Property*)>, o=0x55555a66cd60, arg=0x7fffa002b9b0)
    at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:169
#8  0x00005555559cb603 in QtPrivate::QSlotObject<bool (INDI_D::*)(INDI::Property*), QtPrivate::List<INDI::Property*>, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x55555a663ec0, r=0x55555a66cd60, a=0x7fffa002b9b0, ret=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:120
#9  0x00007ffff23ed0c2 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ffff388175b in QWidget::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007ffff384283c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007ffff384a104 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007ffff23bd8d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007ffff23c004d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007ffff2417263 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007fffed34c417 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007fffed34c650 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007fffed34c6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff241688f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007ffff23bb90a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007ffff23c49b4 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00005555556338e8 in main(int, char**) (argc=1, argv=0x7fffffffdd98) at /home/myuser/sand-box/kstars/kstars/main.cpp:348


Read More...