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
Add methods Joint::VelocityLimits, Joint::EffortLimits, Joint::PositionLimits for getting limits, corresponding to the existing setter methods.
Alternatives considered
I looked at getting these values from the ECM using components::JointVelocityLimitsCmd, components::JointEffortLimitsCmd, and components::JointPositionLimitsCmd. However, their headers all contain comments such as "It is expected that the physics plugin reads this component and sets the limit to the dynamics engine. After setting it, the data of this component will be cleared (i.e. the vector will have length zero)." So it is expected that these components will not contain the desired data.
Additional context
I'm using gz-sim8 on Ubuntu 24.04.
The text was updated successfully, but these errors were encountered:
Desired behavior
Add methods Joint::VelocityLimits, Joint::EffortLimits, Joint::PositionLimits for getting limits, corresponding to the existing setter methods.
Alternatives considered
I looked at getting these values from the ECM using components::JointVelocityLimitsCmd, components::JointEffortLimitsCmd, and components::JointPositionLimitsCmd. However, their headers all contain comments such as "It is expected that the physics plugin reads this component and sets the limit to the dynamics engine. After setting it, the data of this component will be cleared (i.e. the vector will have length zero)." So it is expected that these components will not contain the desired data.
Additional context
I'm using gz-sim8 on Ubuntu 24.04.
The text was updated successfully, but these errors were encountered: