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

Some motor inputs don't work well in mock environment #1431

Open
axelboc opened this issue Oct 1, 2024 · 2 comments
Open

Some motor inputs don't work well in mock environment #1431

axelboc opened this issue Oct 1, 2024 · 2 comments

Comments

@axelboc
Copy link
Collaborator

axelboc commented Oct 1, 2024

Originally described in #1429:

In the mock environment, I can't seem to get the step inputs of the following "motors" to work:

  • Sample Vertical
  • Sample Horizontal
  • Focus

If I recall, those are actually abstract motors that control multiple physical motors, so perhaps it is a limitation of the mock environment?

Peek 2024-10-01 10-29

Interestingly, if you pay close attention, when I press the arrows, the motor input sometimes receives a value that does not make sense whatsoever for a split millisecond (starting with 3 when pressing the up arrow, or -0. when pressing the down arrow) — it seems to overshoot before going back to the initial value +/- 0.1.

@beteva
Copy link
Member

beteva commented Oct 1, 2024

The difference between these three motors and the others is that the role in ui.yaml differs from the real motor name.
Could you, please, try to change the role in the ui.yaml to see if it changes

@marcus-oscarsson
Copy link
Member

Perfect, I was just about to create this issue :)

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

3 participants