-
Notifications
You must be signed in to change notification settings - Fork 310
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
FakeSystem initial_value does not seem to work correctly #622
Comments
I wonder if it's because these joints have 2 state interfaces: position and velocity. |
@destogl can I ask how this feature is supposed to work? I don't see any usage example in ros2_control_demos. Is it:
or
I hope it's option 1. Option 2 wouldn't make sense if there are multiple state interfaces. |
OK, I finally got it working like this:
Will make a small PR to give a warning to the user. |
For anyone stumbling upon this looking for the new preferred syntax, there's an example in the test file:
|
Thanks @wmmc88! |
…-controls#622) * Remove workflows for distros not supported on master * Revert "Remove workflows for distros not supported on master" This reverts commit e916af3b19ba8642312692328ebc71a2f92ac93c. * Don't run humble workflows on master Co-authored-by: Bence Magyar <bence.magyar.robotics@gmail.com>
I am launching one of the common test packages from MoveIt, the Panda. The ros2_control xacro is here:
https://github.com/ros-planning/moveit_resources/blob/ros2/panda_moveit_config/config/panda.ros2_control.xacro
I saw this deprecation warning:
[ros2_control_node-5] [WARN] [1642614151.127346724] [fake_generic_system]: The usage of initial_position has been deprecated. Please use 'initial_value' instead.
So I tried updating
initial_position
toinitial_value
in that ros2_control xacro file. Yet, the robot does not move to the initial position like it used to.The text was updated successfully, but these errors were encountered: