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
Since #177 the joints without claimed interfaces are set to have zero velocity. I'm still not exactly sure if this really solves an issue, because IMHO it does not work but breaks other configurations (passive joints were already fixed; but joints without active controller might be expected to fall down, e.g. with effort interface: fix proposed with #251 ):
If this is an important usecase, we should save the position at time of initialization or perform_command_mode_switch (if a controller was deactivated later) and set also the position to that value, not only the velocity to zero (similar to #213)
Since #177 the joints without claimed interfaces are set to have zero velocity. I'm still not exactly sure if this really solves an issue, because IMHO it does not work but breaks other configurations (passive joints were already fixed; but joints without active controller might be expected to fall down, e.g. with effort interface: fix proposed with #251 ):
ros2 launch ros2_control_demo_example_9 rrbot_gazebo_classic.launch.py gui:=true
zero_velocity.mp4
If this is an important usecase, we should save the position at time of initialization or perform_command_mode_switch (if a controller was deactivated later) and set also the position to that value, not only the velocity to zero (similar to #213)
gazebo_ros2_control/gazebo_ros2_control/src/gazebo_system.cpp
Lines 604 to 607 in 3c8f5bb
The text was updated successfully, but these errors were encountered: