What seems to be happening is as follows:
1) Slew to a target
2) Hit "Capture & Solve" with "Slew to Target" selected
3) Ekos captures a picture (lets call it M00.fits) and solves it, reporting 1,234 arc seconds off target
4) Mount slews (a little bit, as target was only 1,234" away)
5) Ekos tries to capture another picture, but ends up using the first picture, "M00.fits" and plate solves with that, and thinks it only has to slew a little bit.

Plate solving is occurring on the 2nd to the last frame, "M00.fits", rather than "M01.fits". (?)
Or, maybe plate solving is taking too long to complete, and returns the results for the solve of "M00.fits" to the request to solve "M01.fits"

In this case, a bogus entry is made into the mount model records and the mount is very confused about what it is pointing at.

I have been working around this by going over to the Photo tab and taking a photo at a different shutter speed or ISO/Gain setting. That causes Ekos to capture that picture "M02.fits". Then you can go to Alignment tab and hit Capture & Solve (with "Sync" selected, not "Slew to Target"!!!), and Ekos will capture and solve M03.fits, then sync the mount to the solved coordinates. Then I joystick my way over to the target, Capture, Solve, and Sync again, and again, and again.

Is there a way to force the "plate-solving queue" to wait until the all solves are done before capturing a new frame and solving that, and/or kill it off when we know the mount has gone stupid.

Read More...

Hard reboot of computer and mount , followed by returning the mount to parked position by de-clutching, then reseting the parking position is the only way that I can solve it.

Read More...

I think I am having a similar issue. When I cross the meridian, my mount goes completely stupid.
I am going to try dumping the model and start out on the West side of the meridian.

Read More...

Fixed it. My installation was linked to an old version of the shared object.

/usr/local/lib$ cd /usr/local/lib/
/usr/local/lib$ ls -l *SVB*
lrwxrwxrwx 1 root root      20 Apr 28 14:04 libSVBCameraSDK.so -> libSVBCameraSDK.so.1
lrwxrwxrwx 1 root root      25 Apr 28 14:04 libSVBCameraSDK.so.1 -> libSVBCameraSDK.so.1.6.10
-rw-r--r-- 1 root root 4126424 Apr 28 14:04 libSVBCameraSDK.so.1.6.10


/usr/local/lib$ ls -l /lib/x86_64-linux-gnu/*SVB*
lrwxrwxrwx 1 root root      20 Sep 29 04:09 /lib/x86_64-linux-gnu/libSVBCameraSDK.so -> libSVBCameraSDK.so.1
lrwxrwxrwx 1 root root      24 Sep 29 04:09 /lib/x86_64-linux-gnu/libSVBCameraSDK.so.1 -> libSVBCameraSDK.so.1.9.4
-rw-r--r-- 1 root root 5121544 Sep 29 04:09 /lib/x86_64-linux-gnu/libSVBCameraSDK.so.1.9.4
/usr/local/lib$ sudo cp /lib/x86_64-linux-gnu/libSVBCameraSDK.so.1.9.4 ./
/usr/local/lib$ ls
googletest  libSVBCameraSDK.so    libSVBCameraSDK.so.1.6.10  python3.10
gtest       libSVBCameraSDK.so.1  libSVBCameraSDK.so.1.9.4
/usr/local/lib$ sudo ln -sf  /usr/local/lib/libSVBCameraSDK.so.1.9.4 /usr/local/lib/libSVBCameraSDK.so
/usr/local/lib$ sudo ln -sf  /usr/local/lib/libSVBCameraSDK.so.1.9.4 /usr/local/lib/libSVBCameraSDK.so.1
/usr/local/lib$ ls
googletest  libSVBCameraSDK.so    libSVBCameraSDK.so.1.6.10  python3.10
gtest       libSVBCameraSDK.so.1  libSVBCameraSDK.so.1.9.4
/usr/local/lib$ ls -lh
total 8.9M
drwxr-xr-x 2 root root 4.0K May  1 13:11 googletest
drwxr-xr-x 2 root root 4.0K May  1 13:10 gtest
lrwxrwxrwx 1 root root   39 Oct 24 15:52 libSVBCameraSDK.so -> /usr/local/lib/libSVBCameraSDK.so.1.9.4
lrwxrwxrwx 1 root root   39 Oct 24 15:53 libSVBCameraSDK.so.1 -> /usr/local/lib/libSVBCameraSDK.so.1.9.4
-rw-r--r-- 1 root root 4.0M Apr 28 14:04 libSVBCameraSDK.so.1.6.10
-rw-r--r-- 1 root root 4.9M Oct 24 15:47 libSVBCameraSDK.so.1.9.4
drwxr-xr-x 3 root root 4.0K Apr 19  2022 python3.10
/usr/local/lib$ 


Read More...

running this doesn't help:

$ sudo apt remove indi-sv305 ;
$ sudo apt autoremove;
$ sudo apt-get install -f -y indi-sv305

then running
$ indiserver -vvv indi_sv305_ccdindiserver -vvv indi_sv305_ccd
...
Driver indi_sv305_ccdindiserver: sending msg nq 1:
<getProperties version="1.7"/>
...
: Driver indi_sv305_ccdindiserver: 2022-10-24T18:10:09: Driver indi_sv305_ccdindiserver: execlp : No such file or directory
: Driver indi_sv305_ccdindiserver: stderr EOF
: Driver indi_sv305_ccdindiserver: process 3796 exited with status 1
: Driver indi_sv305_ccdindiserver: read: Connection reset by peer
: Driver indi_sv305_ccdindiserver: restart #0
...
(repeats 10x)

Read More...

Is anyone else getting this error?
I'm having this issue on Ubuntu.
No problem on OSX.

Read More...

R Dan Nafe replied to the topic 'Kstars binaries on MacBook' in the forum. 3 months ago

So as a quick fix, could I copy asteroids.dat from the 3.5.9 build and put it into the 3.6.0 directory structure?

Or, how about deleting asteroids.dat altogether?
#dontLookUp

Thanks, Rob, for all your work!
Dan

Read More...

R Dan Nafe replied to the topic 'Kstars binaries on MacBook' in the forum. 3 months ago

Launching Kstars 3.6.0 (from Finder) then launching INDI server plus EKOS, from within Kstars, allows use of Cmd-F, and/or Pointing>Find Object... without a crash.

When you quit EKOS, Cmd-F and Pointing>Find Object... still works.

Quit INDI server, then use Cmd-F or Pointing>Find Object...: crash!

Read More...