Hi Jasem:
I also get many crashes recently, always when starting Ekos and connecting devices.
Sometimes I can recover by killing indiserver, sometimes I have to reboot. Also I notice in some cases I am unable to save or restore driver configuration: the keys are just unresponsive.
Thanks to your message I ran with gdb and I attach below the results. Thank you for your advice
François
crash #1
Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
INDI_E::buildText (this=0x44241e0, itp=0x46efa38)
at /home/pi/AstroRoot/kstars/kstars/indi/indielement.cpp:147
147 if (tp->text[0])
crash #2
[Thread 0x9b1fa090 (LWP 9011) exited]
[Thread 0x9c1fc090 (LWP 9006) exited]
Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
0x004e2cc0 in QWidget::testAttribute (this=0x0, attribute=Qt::WA_Disabled)
at /usr/include/arm-linux-gnueabihf/qt5/QtWidgets/qwidget.h:867
867 return data->widget_attributes & (1<<attribute);
crash #3
Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
0x0097bd18 in Ekos::Manager::syncActiveDevices (this=0x3ea20d8)
at /home/pi/AstroRoot/kstars/kstars/ekos/manager.cpp:3508
3508 if (override && *override)
Read More...
Hello Jasem:
I have written a driver for TeenAstro, with all basic functionality tested. It is in my fork github/fdesvallees/indi. Since I am not familiar with git I am not sure how to proceed now. Note that I have written some documentation according to your recommendations, but I don't know where to submit it. Can you please help? Thanks, François
Read More...
I am starting to use Ekos for astrophotography, with an LX200 compatible mount and Nikon D750 (no guiding yet). The first image after each slew shows bad stars. I guess the mount was still moving while the scheduler started capturing. Subsequent pictures are ok.
How can I add a delay between end of slew and start capture?
Thanks
Read More...
Thanks Khalid, this explains it.
But I don't understand how we can make Ekos work: eithee we keep the connection open all the time, like a serial port, or for every command issued (and this can be one per second or more when polling the mount), the driver needs to open the connection, issue the command, then close the connection (not nice). What do you think?
Read More...
I am testing communications through EKOS and a TeenAstro mount controller. TeenAstro does not have a serial port, it communicates through TCP instead.
I used the LX200 Basic driver, because I was not able to configure OnStep for TCP (it seems to connect through serial only).
The communication starts fine, I can read the initial coordinates of the mount,
[2019-10-04T22:37:17.134 CEST INFO ][ org.kde.kstars.indi] - LX200 Basic : "[INFO] Connecting to 192.168.0.12@9999 ... "
[2019-10-04T22:37:17.434 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[DEBUG] Connection successful, attempting handshake... "
[2019-10-04T22:37:17.442 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] CMD <:GR#> "
[2019-10-04T22:37:17.446 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] RES <09:53:28> "
[2019-10-04T22:37:17.446 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] VAL [9.89111] "
[2019-10-04T22:37:17.447 CEST INFO ][ org.kde.kstars.indi] - LX200 Basic : "[INFO] LX200 Basic is online. "
but immediately after, the log shows communication errors
[2019-10-04T22:37:19.474 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] CMD <:GR#> "
[2019-10-04T22:37:19.498 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "Error reading RA/DEC. "
[2019-10-04T22:37:21.484 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] CMD <:GR#> "
[2019-10-04T22:37:21.491 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "Error reading RA/DEC. "
[2019-10-04T22:37:23.486 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] CMD <:GR#> "
[2019-10-04T22:37:23.488 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "Error reading RA/DEC. "
[2019-10-04T22:37:25.488 CEST DEBG ][ org.kde.kstars.indi] - LX200 Basic : "[SCOPE] CMD <:GR#> "
I started investigating, and found out this is due to tty_write() returning an error: first TTY_WRITE_ERROR then TTY_OVERFLOW.
Before continuing, I would like to ask if anyone recognizes this, and ask for suggestions on how to fix it. Thank you!
Read More...