Hello, thanks for your reply

these files weren't empty, but they don't show my setup (remoted from PI4 in garden),
now it runs fine, I'd to reconfigure and check after new install (astrometry was not lost/trashed :) ), i don't know who are the configs files while some datas weren't lost... but some away or incomplete ?!

I think, it seems, that was maybe a problem with files/folder rights... as no access to xml or other ... I don't know, the difference after the new install: I was only able to reconfigure and edit/save new profiles (not possible after crash, saving new profile/config led to crash).
I've tested it before clouds came, no problem

I think, in my case, that the problem was in folder /home/name/.local/share/kstars
i've not found the xml with "profiles" (disapeared in ekos before the crash), but there is "userdb.sqlite"

I've had this problem only on PC, the PI4 works fine (indiserver + kstars sometimes for polar align...)

Read More...

Hello,

I've discovered a new crash, but not funny:
Ekos has no more list (profile), I've lost all profiles
I've tried to make new profile: crash

Ekos d'ont work anymore

log
Application: KStars (kstars), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fae8be8d440 (LWP 14959))]

Thread 7 (Thread 0x7fae3d89f700 (LWP 14969)):
#0 0x00007fae840ccbf9 in __GI___poll (fds=0x7fae2c003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x00007fae817245c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007fae817246dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007fae862ab99b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x00007fae862509fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007fae8606f23a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007fae8607417d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007fae853376db in start_thread (arg=0x7fae3d89f700) at pthread_create.c:463
#8 0x00007fae840d988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7fae54a86700 (LWP 14968)):
#0 0x00007fae840ccbf9 in __GI___poll (fds=0x7fae34004a10, nfds=1, timeout=5010) at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x00007fae817245c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007fae817246dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007fae862ab99b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x00007fae862509fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007fae8606f23a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007fae8607417d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7 0x00007fae853376db in start_thread (arg=0x7fae54a86700) at pthread_create.c:463
#8 0x00007fae840d988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fae572ef700 (LWP 14963)):
#0 0x00007fae8533d9f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x562d88a97718) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1 __pthread_cond_wait_common (abstime=0x0, mutex=0x562d88a976c8, cond=0x562d88a976f0) at pthread_cond_wait.c:502
#2 __pthread_cond_wait (cond=0x562d88a976f0, mutex=0x562d88a976c8) at pthread_cond_wait.c:655
#3 0x00007fae5dbcf2bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#4 0x00007fae5dbceeb7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#5 0x00007fae853376db in start_thread (arg=0x7fae572ef700) at pthread_create.c:463
#6 0x00007fae840d988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fae5826f700 (LWP 14962)):
#0 0x00007fae8533d9f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x562d88b25314) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1 __pthread_cond_wait_common (abstime=0x0, mutex=0x562d88b252c0, cond=0x562d88b252e8) at pthread_cond_wait.c:502
#2 __pthread_cond_wait (cond=0x562d88b252e8, mutex=0x562d88b252c0) at pthread_cond_wait.c:655
#3 0x00007fae5dbcf2bb in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#4 0x00007fae5dbceeb7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#5 0x00007fae853376db in start_thread (arg=0x7fae5826f700) at pthread_create.c:463
#6 0x00007fae840d988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fae6d23f700 (LWP 14961)):
#0 0x00007fae840ccbf9 in __GI___poll (fds=0x7fae6001a0e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x00007fae817245c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007fae817246dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007fae862ab99b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x00007fae862509fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007fae8606f23a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007fae8672dd45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7 0x00007fae8607417d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8 0x00007fae853376db in start_thread (arg=0x7fae6d23f700) at pthread_create.c:463
#9 0x00007fae840d988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fae701df700 (LWP 14960)):
#0 0x00007fae840ccbf9 in __GI___poll (fds=0x7fae701dec28, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1 0x00007fae7e473747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2 0x00007fae7e47536a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3 0x00007fae72fca5e9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4 0x00007fae8607417d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007fae853376db in start_thread (arg=0x7fae701df700) at pthread_create.c:463
#6 0x00007fae840d988f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fae8be8d440 (LWP 14959)):
[KCrash Handler]
#6 0x00007fae87840420 in QWidgetLineControl::internalSetText(QString const&, int, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7 0x00007fae8783794c in QLineEdit::setText(QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8 0x0000562d8750f937 in ProfileEditor::setPi (this=this@entry=0x7ffc43de8c70, value=<optimized out>) at ./kstars/ekos/profileeditor.cpp:344
#9 0x0000562d87508019 in Ekos::Manager::editProfile (this=0x562db7000be0) at ./kstars/ekos/manager.cpp:2573
#10 0x00007fae8628175f in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007fae877e5ba2 in QAbstractButton::clicked(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007fae877e5dba in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007fae877e719a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007fae877e738d in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007fae87733048 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007fae876f483c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x00007fae876fc65f in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x00007fae862529c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007fae876fb632 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007fae8774e16b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x00007fae877507da in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x00007fae876f483c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#23 0x00007fae876fc104 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#24 0x00007fae862529c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007fae86d09583 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#26 0x00007fae86d0b055 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#27 0x00007fae86ce22eb in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#28 0x00007fae7302f260 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#29 0x00007fae81724417 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x00007fae81724650 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#31 0x00007fae817246dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x00007fae862ab97f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#33 0x00007fae862509fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#34 0x00007fae86259aa4 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#35 0x0000562d871fe412 in main (argc=<optimized out>, argv=<optimized out>) at ./kstars/main.cpp:333

Read More...

Caux replied to the topic 'Scope hitting pier' in the forum. 4 years ago

Hello,
I've noticed the same problem with NEQ5/EQMOD/remote Indiserver -> Kstars
For a lot of targets it runs great, than i've found some target unable to solve (usually near zenith or > 75° without "limits" in Ekos), as dec inversed or too many steps/move...
have you seen a solution ?

I use the EQMOD align system
I purge/reset model each times

greetings
Damien

Read More...

Caux replied to the topic 'Amp glow with ASI 183MMPro' in the forum. 6 years ago

hello,
I don't have usb3

but I checked with any PCs under Ubuntu/Windows7/ Windows10 (maybe USB3)
No problem anymore, but it's known that a low rate on USB make the Amp Glow lighter, I've shot a lot in any weeks, the amp-glow appeared with the stretched histogram FITS preview of Kstars but as I push the levels so far I can: no amp-glow on final PICS.
I use only one bank of Darks (Gain 300, T° -15°C), and the amp-glow seems really stable as it appeared never with DOF treatement.

As I've understood, an Astrams has sent 3 times his camera, the fourth and last one has a faint Amp-glow...

Read More...

Caux replied to the topic 'Amp glow with ASI 183MMPro' in the forum. 6 years ago

How how sorry, my bad :(
seems ok :)
the fits viewer in Kstars show too much details, the levels are really boosted
the amp glow is visible but can easily corrected with dark/flat

Read More...

Caux created a new topic ' Amp glow with ASI 183MMPro' in the forum. 6 years ago

Hello,
I use a PI3B+ with Ubuntu Mate 16.04LTS, INDI/Kstars/Ekos
IndiLib updated 1.7.4

I have the big "amp Glow" with the ASI183MMPro, Gain 200, Exp: 180s, T° 10°C


Checked the forums/topics everywhere, it' seems normal but ZWO and QHY (same sensors) have corrected the drivers to compensate (Dark calibration ? I'm not sure)
Tested under Windows 7, Last ZWO Driver, Sharpcap: no amp glow with: ASI183MMPro, Gain 200, Exp: 180s, T° 10°C
very high contrasted picture (windows picture manager)



has someone an issue to this ?
I've to test furthers solutions, but now I've to go at work :(

Thanks all :)

Read More...

Caux replied to the topic 'Hitech Astro DC focuser problem' in the forum. 6 years ago

You're right, I Have this one:
71Bo6D0LssL._SX355_.jpg

Tested it with last Upgrade, 3 hours outside, "real condition", 5000ms polling, speed 50, step 100, all ok
rel position always > 50000, but that's not a pb

If the DC2 use the HID layer over the USB Protocol.... pfouuu :( designed for Windows...
sorry, that's far away of my knowledges

Read More...

Caux replied to the topic 'Hitech Astro DC focuser problem' in the forum. 6 years ago

Hello,

i've no solutions for the driver, but yet (after one day over it) it works ...

Hitecastro DC Focus, Ubuntu Mate 16.04LTS, PI3B+, Kstars/ekos

I've removed definitively the powered USB HUB, and after many many tries it works with this parameters:
Polling 5000ms (yeah, 5 seconds)
Speed 50 or 100 (<50 no function)
Max travel 10000

Steps: between 4000 and 10000 it runs but no update for the position (tiks)
between 20 and 4000 it runs perfectly, only wait 12s (12 seconds) to launch another command

Position: for a move of 2000 steps, the position move of 4000
many tries: always x2

no safe position (limits visible in .cpp)
override below 0, i've reached -2200
I didn't test the override > 10000 (Max travel ?)

At startup the tiks (position) is always 49800 (position not saved)
all others parameters are correctly saved

Read More...

Caux replied to the topic 'Focuser driver' in the forum. 6 years ago

hmmm...
under windows why not, but I don't want this system anymore.

Nop, now I do the changes on Arduino between my focuser and the solution of Cees Lensink, to use the moonlite driver with my second Setup (Mak100/1400 ASI120)
then,
find a solution for the HitecAstrofocus controler.... or replace it with an Arduino :(

Read More...

Caux created a new topic ' Focuser driver' in the forum. 6 years ago

Hello,

I've done an arduino focuser with 3 speed, 1 Step, 1/8 Step, 1/32 Step
Manually controled or in remote with terminal and a Script focus.sh
To move inward 20 Steps: I send (Sérial via USB, ASCI readable) focus.sh 1020
outward 150 Steps: focus.sh 2150

really easy

I want to do a driver for ekos/kstars
How to do it ? Software, in C or c++, but I don't know the structure, and have no idea how to program it :(
It is possible ?
I've more worked with c#/Visual Studio, or scripting bash, lua etc

Read More...

Ok, perfect !!!
sorry for this silly post, you're right with the update, no seen any error but it's running correctly now !!

"sudo apt-get update && sudo apt-get -y dist-upgrade"
was the solution

Thanks a lot !!

Read More...

Hello everybody,

since Januar I use a PI3B/Ubuntu 16.04LTS for my Setup
it runs very good, :woohoo: Kstars is realy amazing,

but now (after the last Upgrade ?) I can't use the Canon 1200D, Ekos crashed to attempt connection with the 1200D
I've tried with terminal:
> indiserver indi_canon_ccd
the answer is a bit strange, with guiding ?

pi@astropi:~$ indiserver indi_canon_ccd
2018-08-04T19:18:03: startup: indiserver indi_canon_ccd
2018-08-04T19:18:03: Driver indi_canon_ccd: indi_canon_ccd: symbol lookup error: indi_canon_ccd: undefined symbol: _ZN4INDI3CCD10GuideNorthEf
2018-08-04T19:18:03: Driver indi_canon_ccd: stderr EOF
Child process 7233 died
2018-08-04T19:18:03: Driver indi_canon_ccd: restart #1
2018-08-04T19:18:03: Driver indi_canon_ccd: indi_canon_ccd: symbol lookup error: indi_canon_ccd: undefined symbol: _ZN4INDI3CCD10GuideNorthEf
2018-08-04T19:18:03: Driver indi_canon_ccd: stderr EOF
Child process 7234 died
2018-08-04T19:18:03: Driver indi_canon_ccd: restart #2
2018-08-04T19:18:03: Driver indi_canon_ccd: indi_canon_ccd: symbol lookup error: indi_canon_ccd: undefined symbol: _ZN4INDI3CCD10GuideNorthEf
2018-08-04T19:18:03: Driver indi_canon_ccd: stderr EOF
2018-08-04T19:18:03: Driver indi_canon_ccd: restart #3
Child process 7235 died
2018-08-04T19:18:03: Driver indi_canon_ccd: indi_canon_ccd: symbol lookup error: indi_canon_ccd: undefined symbol: _ZN4INDI3CCD10GuideNorthEf
2018-08-04T19:18:04: Driver indi_canon_ccd: stderr EOF
Child process 7236 died
2018-08-04T19:18:04: Driver indi_canon_ccd: restart #4
2018-08-04T19:18:04: Driver indi_canon_ccd: indi_canon_ccd: symbol lookup error: indi_canon_ccd: undefined symbol: _ZN4INDI3CCD10GuideNorthEf
2018-08-04T19:18:04: Driver indi_canon_ccd: stderr EOF
2018-08-04T19:18:04: Driver indi_canon_ccd: restart #5
Child process 7237 died
2018-08-04T19:18:04: Driver indi_canon_ccd: indi_canon_ccd: symbol lookup error: indi_canon_ccd: undefined symbol: _ZN4INDI3CCD10GuideNorthEf
2018-08-04T19:18:04: Driver indi_canon_ccd: stderr EOF
Child process 7238 died
2018-08-04T19:18:04: Driver indi_canon_ccd: restart #6
2018-08-04T19:18:04: Driver indi_canon_ccd: indi_canon_ccd: symbol lookup error: indi_canon_ccd: undefined symbol: _ZN4INDI3CCD10GuideNorthEf
2018-08-04T19:18:04: Driver indi_canon_ccd: stderr EOF
2018-08-04T19:18:04: Driver indi_canon_ccd: restart #7
Child process 7239 died
2018-08-04T19:18:04: Driver indi_canon_ccd: indi_canon_ccd: symbol lookup error: indi_canon_ccd: undefined symbol: _ZN4INDI3CCD10GuideNorthEf
2018-08-04T19:18:04: Driver indi_canon_ccd: stderr EOF
2018-08-04T19:18:04: Driver indi_canon_ccd: restart #8
Child process 7240 died
2018-08-04T19:18:04: Driver indi_canon_ccd: indi_canon_ccd: symbol lookup error: indi_canon_ccd: undefined symbol: _ZN4INDI3CCD10GuideNorthEf
2018-08-04T19:18:04: Driver indi_canon_ccd: stderr EOF
2018-08-04T19:18:04: Driver indi_canon_ccd: restart #9
Child process 7242 died
2018-08-04T19:18:04: Driver indi_canon_ccd: indi_canon_ccd: symbol lookup error: indi_canon_ccd: undefined symbol: _ZN4INDI3CCD10GuideNorthEf
2018-08-04T19:18:04: Driver indi_canon_ccd: stderr EOF
2018-08-04T19:18:04: Driver indi_canon_ccd: restart #10
Child process 7243 died
2018-08-04T19:18:04: Driver indi_canon_ccd: indi_canon_ccd: symbol lookup error: indi_canon_ccd: undefined symbol: _ZN4INDI3CCD10GuideNorthEf
2018-08-04T19:18:04: Driver indi_canon_ccd: stderr EOF
Child process 7244 died
2018-08-04T19:18:04: Driver indi_canon_ccd: Terminated after #10 restarts.
2018-08-04T19:18:04: good bye

what is that doing with Canon DSLR ??
"undefined symbol: _ZN4INDI3CCD10GuideNorthEf"

I've upgraded, Gphoto too (2.6)
but no issue...

Has anyone an idea ?

Read More...