Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jog Buttons and Tracking #6

Open
tristan3214 opened this issue Jun 21, 2017 · 2 comments
Open

Jog Buttons and Tracking #6

tristan3214 opened this issue Jun 21, 2017 · 2 comments
Labels

Comments

@tristan3214
Copy link
Contributor

Pretty sure this is already a known issue, but I want to put this here.

Jog buttons work, but because tracking is turned off everything moves slightly west in the time the telescope jogs.

@ojf
Copy link
Member

ojf commented Aug 4, 2017

I've had more luck with the jog buttons lately. Given the westerly drift when jogging we surely don't need arcsecond-level jogs (although that's the default). Arcminute jogs have been working well for me, even in the east-west direction. Possibly just needs an way to ensure east-west jogs aren't so small that the net effect is the opposite of what you want. =)

@dougbrn
Copy link
Contributor

dougbrn commented Aug 4, 2017

Eliminating arcsecond jog option is probably the best bet. However, if you'd like to actually correct this out, you'd need to calculate the time that tracking was turned off for and apply a correction jog for the tracking rate on top of each jog command. If this is done in post, you get the same issue with the correction jog and get a recursive problem. This would need to happen as a pre-estimate calculation to tack on a correction jog to the original command.

So... probably just discourage small jog commands from the software

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants