Jim replied to the topic 'EQMOD sync and align settings' in the forum. 2 weeks ago

1. I have seen this before too, but have not been able to track anything down. When it gets in this way, kstars is out of sync with where the scope is pointing and I end up having to park, clear alignment, and start over. Thankfully it does not happen a lot.
2. I find there is a limit to the number of alignment points that are healthy, and things start to degrade after about 4 to 5 points on each side of the meridian. I sync a few extra points at start, but then switch to solver action "Nothing" which seems to stop the sync points from getting added. It might be a nice setting to not sync after a certain number of points are achieved successfully, then I could leave it set to either "Sync" or "Slew to Target". "Slew to target" would be ideal because the solve could still center the target. There may be some limitations on knowing the starting point for the next slew.
3. not sure on this one

EQ8 on a permanent pier here, by the way.

Read More...

indilib.org/forum/development/10346-asi-...age-after-abort.html

This is the thread where it was discussed. You did not say what your camera was, but the fix was in the ASI driver in indi-3rdparty. It should have been in 1.9.2 though, so perhaps this is something different.

What is your equipment? You may want to set up a signature to help with debugging. Here is how: indilib.org/forum/new-forum-users/8195-w...ndi-forum.html#63061

Read More...

I know this was looked at recently. What versions of kstars and INDI are you running?

Read More...

 
This particular problem is being worked on. JPL changed their API.

Read More...

Jasem, I pushed PR to fix the qhy_ccd build for Fedora. libqhy now builds version 21. I don't know if this might be a fix needed else where too.

Read More...

easily reproducible, unfortunately logs are not much help here:

[2021-10-10T09:31:32.453 CDT CRIT ][                org.kde.kstars] - "Data verification failed"

and this was the only thing on the console:

Call to writableLocation without an application-based location.



 

Read More...