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

Slew to first alignment position results in RA axis oscillations #300

Open
2 tasks done
bgottula opened this issue Apr 1, 2024 · 2 comments
Open
2 tasks done

Slew to first alignment position results in RA axis oscillations #300

bgottula opened this issue Apr 1, 2024 · 2 comments
Assignees

Comments

@bgottula
Copy link
Collaborator

bgottula commented Apr 1, 2024

On 31 March 2024 I ran bootstrap in preparation for tracking ISS. When moving to the first location the mount started slewing in RA only, and upon reaching some position maybe 30 degrees from startup it started to oscillate back and forth by a few degrees around that position. The oscillations stayed at a steady rate and magnitude. After a few of these it was clear that alignment was not going to work so I killed the program. A second attempt soon after produced the same result.

It's noteworthy that I somewhat recently upgraded Gemini to the new Level 6 firmware, where one of the features is 4x encoder resolution. I wonder if the number of ticks per degree in the physical position has changed. That value is hard-coded in probably both this and the point package.

  • Confirm ticks per degree in current Gemini.
  • Attempt to reproduce the problem with more debug outputs.
@bgottula
Copy link
Collaborator Author

bgottula commented Apr 1, 2024

track don't seem to be writing all of the same telemetry channels I had in the past, but I was able to find and plot the commanded slew rates for both axes, and these plots agree closely with my observations. Use this link on nix: http://localhost:3000/goto/ba7ns2xSR?orgId=1

In the plot green is RA axis, yellow is Dec axis, and the Y-axis units are degrees/s.

image

@bgottula bgottula self-assigned this Apr 1, 2024
@bgottula
Copy link
Collaborator Author

bgottula commented May 5, 2024

I have confirmed that the 4x resolution "quadrature" servo encoder mode was enabled and was in fact the root cause of this problem. I have started to make the necessary updates and tests indoors with these adjustments show expected motion behavior from both axes.

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

No branches or pull requests

1 participant