First off, I recently performed an inplace upgrade from Linux Buster to Bullseye to allow me to compile latest version of KStars. But I have encountered a missing shared library issue that looks like this during KStars build.

/usr/bin/ld: warning: libcfitsio.so.7, needed by /usr/local/lib/libstellarsolver.so.2.2, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libgsl.so.23, needed by /usr/local/lib/libstellarsolver.so.2.2, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libwcs.so.6, needed by /usr/local/lib/libstellarsolver.so.2.2, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libcfitsio.so.7, needed by /usr/local/lib/libstellarsolver.so.2.2, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libgsl.so.23, needed by /usr/local/lib/libstellarsolver.so.2.2, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libwcs.so.6, needed by /usr/local/lib/libstellarsolver.so.2.2, not found (try using -rpath or -rpath-link)

It also appears to have failed to find some things at the start of the process.
- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found


Read More...

Andrew replied to the topic 'Kstars RPi cmake error: missing ECM?' in the forum. 2 days ago

Thanks I might try that soon.
I found a thorough looking guide on how to do it here.
ostechnix.com/upgrade-to-debian-11-bulls...om-debian-10-buster/

Read More...

Andrew replied to the topic 'Kstars RPi cmake error: missing ECM?' in the forum. 2 days ago

That's a pretty annoying development.
But I actually did try to do a full-upgrade. But it didn't do anything, so still on Buster. And I'm not thrilled at the prospect of setting everything up again from a clean installation.

Read More...

Andrew replied to the topic 'Kstars RPi cmake error: missing ECM?' in the forum. 2 days ago

I am also having this issue.
For context, I perform my compilation with the help of AstroPi 3 script on a Raspberry Pi 4. Running Raspberry OS Buster.

Today I saw this error during the KStars compile

CMake Error at CMakeLists.txt:70 (find_package):
  Could not find a configuration file for package "ECM" that is compatible
  with requested version "5.68.0".

  The following configuration files were considered but not accepted:

    /usr/share/ECM/cmake/ECMConfig.cmake, version: 5.54.0

I attempted to update it, but am told I have the latest version already.

Next I installed ECM from the KDE source on GIT
github.com/KDE/extra-cmake-modules

The result is I am now getting a similar error but for QT5
CMake Error at CMakeLists.txt:108 (find_package):
  Could not find a configuration file for package "Qt5" that is compatible
  with requested version "5.12.8".

  The following configuration files were considered but not accepted:

    /usr/lib/aarch64-linux-gnu/cmake/Qt5/Qt5Config.cmake, version: 5.11.3

Again I can not upgrade QT5, as I am told it is also the latest version.

Please help. Thank you.

Read More...

I see no need to change the refresh function for the legacy move star, or move star + calc. I'm only advocating this for the plate solve method.
My reason for that is I have not experienced much in the way of a graceful recovery from bad frames. I've found bad frames either cause significant time-out delay with little information as to what is taking place while it is trying to process it. Or worse case scenario, it gets hung up in the process and never takes a new clean frame, requiring me to abort and redo the entire process, if I'm lucky it will let me. If I'm not lucky I have to restart the drivers.

Read More...

I have two methods. For my RC I 3d printed a rudimentary dial indicator that magnified small movements. www.thingiverse.com/thing:4607036
I just had to also print a part that could hold in the focuser.

The other method uses my planetary camera and a star or artificial star. Start looping frames and the HFR graph will begin to populate with samples. It's then a matter of finding a backlash setting that returns to the same HFR after In-Out moves reliably.

Read More...

I've also experienced it becoming unresponsive after a few frames but I'm not sure if I'm using the most up to date version and need to test it more thoroughly before i can be more specific. And I am running it on a Pi under Raspberry OS.

Please consider making the refresh frequency into a timed delay between exposures under the solving method.

Thank you

Read More...

I have a request.
Can you add seperate backlash settings for In and Out travels?

Read More...

IMHO. The plate solve PA alignment would be better if it used the the set exposure time and the refresh button replaced with a time delay. That would give time to make an adjustment between exposures.
Also, a timer countdown or an array of LED indicators on screen that show how much time remains until the next exposure would help us keep our hands off during a capture and avoid spoiling an exposure.

Read More...

Andrew replied to the topic 'HEQ5 Pro PA LED Brightness' in the forum. 4 weeks ago

Odd. In my experience, what I set it to from the hand controller remained set.
But perhaps there is an option in EQMod driver that is overriding it.

Read More...

Interesting workaround. But I'm afraid it won't apply to many of us. For instance I compile KStars on my local system because I can not use the repositories on Raspberry OS.
Still hoping for a solution some day. But it's just an icon, so it's not really a priority.

Read More...

It could be your mount trying to clear backlash after a move command. If your mount has his behaviour, consider increasing the settle times for your captures.

Read More...