Position actuators' control range stuck in degrees (even with the compiler set to radians) #249
-
Hi! Specifying a control range for position actuators in radians has minimal effect in moving the joints after loading a model. The compiler is set in radians, as are the joint range and ctrlrange. As explained here, joint ranges are converted to radians after compilation, while ctrl and ctrlrange specify raw values and are not converted. I tested this on the humanoid xml to verify it was not specific to my model. On a side note, high gear values results in the simulation is unstable warning, and resets the model repeatedly. This only started after changing from motor to position actuators. `<!-- Copyright 2021 DeepMind Technologies Limited
-->
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Regarding radians and degrees, you are correct, this setting only applies to angles in the kinematic tree. Actuator values like As explained here, |
Beta Was this translation helpful? Give feedback.
Regarding radians and degrees, you are correct, this setting only applies to angles in the kinematic tree. Actuator values like
ctrlrange
are always in native units.As explained here,
gear
scales the length of the actuator (imagine a mechanical gear mechanism between the joint and the actuator), which forposition
type actuators means that it changes the units and therefore the semantics of your position command. E.g., for your first actuator you are using units of radian/20. I am guessing that what you are looking for is actually thekp
attribute (position feedback gain) of the position actuator.