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...

Under normal guiding circumstances, DEC doesn't move, but we can pulse it to account for cyclic error, or missing polar alignment. When it is pulsed, it is tight against one side of the worm gear or the other, and the motor is stopped again, correct?

The next adjustment would use the full backlash, or no backlash, depending on the direction of the previous adjustment. If the direction is the same as previous, the worm is tight and no backlash should be added to the pulse. If the direction is opposite the last pulse, the full backlash comes into play and should be added before the mount would move the scope. I don't understand why a percentage would be used here. I would rather that the variability is accounted for in the pulse width, and not the backlash, where we already have some ability to set things like aggressiveness. The backlash is fairly fixed for a session I would think. The caveat being a meridian flip where the first pulse might be way off. It could be off by as much as 2x the backlash, but after the first correction, the full or nothing works again.

Read More...

Isn't the calculation more involved than a percentage? For example, if I am not guiding, my mount will be tight against the worm gear on one side with just tracking. The worm is already engaged at one side of the backlash. If the guide pulse is additive in the direction of the tracking, you would want to add in all the backlash to the pulse. If the pulse is slowing tracking, it is already against the engaged worm gear and you would want to apply no backlash adjustment, just the straight up calculated pulse.

Read More...