First off, great library - it's been very useful.
Noticed this issue however:
I'm running motor version 3.40 on my Skywatcher Virtuoso. Using goto functions (from both cli and python) when negative azimuth or altitudes are set, the movement stops far short of specified value when synchronous=True is also set. I believe this is due to the line https://github.com/nachoplus/pysynscan/blob/master/synscan/motors.py#L336.
I've removed the lines from there
if abs(CW1) > abs(CW0):
self.axis_stop_motion_hard(axis)
with no (apparent) ill-effect. Maybe I haven't hit the edge case this is there to check...but either way there seems to be a bug.
First off, great library - it's been very useful.
Noticed this issue however:
I'm running motor version 3.40 on my Skywatcher Virtuoso. Using goto functions (from both cli and python) when negative azimuth or altitudes are set, the movement stops far short of specified value when synchronous=True is also set. I believe this is due to the line https://github.com/nachoplus/pysynscan/blob/master/synscan/motors.py#L336.
I've removed the lines from there
with no (apparent) ill-effect. Maybe I haven't hit the edge case this is there to check...but either way there seems to be a bug.