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

yep-312 - has-reference-position #4

Open
ddkohler opened this issue Jun 8, 2022 · 2 comments
Open

yep-312 - has-reference-position #4

ddkohler opened this issue Jun 8, 2022 · 2 comments

Comments

@ddkohler
Copy link
Contributor

ddkohler commented Jun 8, 2022

No description provided.

@ksunden
Copy link
Member

ksunden commented Jun 29, 2022

@ddkohler can you write up a summary of the offline conversation about this yep so that it is something we can reference here later?

@ddkohler
Copy link
Contributor Author

Offline conversation:

  • Discussed the idea of a reference frame, where the relationship between client coordinates to native motor positions might be an offset, a scalar factor, or a complex functional form that needs many parameters. Rather than just an offset and invert option, the trait should allow arbitrary coordinate changes (provided they are 1:1). The parameters will be left up to the daemon, with the exception of the reference_position/offset parameter, which should be a fairly universal parameter.
  • This allows different units between reference frame and native motor coordinates (also: get_native_units() and get units() can be different)
  • add more methods, specifically to set/get native positions, units, (get) native limits
  • set_reference and set_reference_native
  • properties:
    • offset
    • native offset
    • native position
    • native destination

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

No branches or pull requests

2 participants