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

Add device specific config docs #14

Draft
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

daltzctr
Copy link
Collaborator

No description provided.

@daltzctr daltzctr marked this pull request as ready for review December 26, 2022 19:53
@daltzctr
Copy link
Collaborator Author

daltzctr commented Jan 6, 2023

@bhall-ctre I think this is a large improvement over the previous config documentation and would like to get this in before kickoff ideally.

@CoryNessCTR
Copy link
Contributor

Could you bump a commit on this so I can view this from generated RTD?

Magnet Range
^^^^^^^^^^^^

The range for a rotation can be modified. This can be useful if the CANcoder is not directly placed on the output shaft. For example, if the gear ratio between the CANcoder and the output shaft is 8:1, then the output shaft rotates 8 times for 1 CANcoder magnet rotation. If a Magnet Range config of ``8`` is applied, then this will be reported as ``1`` rotation instead of ``8`` rotations.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the range should be included in this section, but for reference if/when we move these descriptions to examples, it should read:

This config changes how to view the absolute position. It is either as a range from [-0.5, 0.5) or a range from [0, 1). As an example, if the CANcoder is at -0.25 rotations, a range of Unsigned will report an absolute position of 0.75, while a range of Signed will report an absolute position of -0.25.

@bhall-ctre bhall-ctre marked this pull request as draft January 6, 2023 23:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants