You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
The text was updated successfully, but these errors were encountered:
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
Originally described in #1429:
In the mock environment, I can't seem to get the step inputs of the following "motors" to work:
If I recall, those are actually abstract motors that control multiple physical motors, so perhaps it is a limitation of the mock environment?
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.The text was updated successfully, but these errors were encountered: