Skip to content
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

Latest ros2_control mock hardware setup has deprecated xacro parameters #737

Closed
sea-bass opened this issue Jul 10, 2023 · 1 comment
Closed

Comments

@sea-bass
Copy link

I just tested out the 2023-06-29 ROS Humble snapshot and (surprise!) ros2_control has introduced another incompatibility with mock hardware, it seems.

[ros2_control_node-2] [INFO] [1689026791.796165788] [resource_manager]: Loading hardware 'ur5e' 
[ros2_control_node-2] [INFO] [1689026791.797834110] [resource_manager]: Initialize hardware 'ur5e' 
[ros2_control_node-2] [WARN] [1689026791.797878390] [mock_generic_system]: Parameter 'fake_sensor_commands' has been deprecated from usage. Use'mock_sensor_commands' instead.
[ros2_control_node-2] [WARN] [1689026791.797894218] [mock_generic_system]: Parsing of optional initial interface values failed or uses a deprecated format. Add initial values for every state interface in the ros2_control.xacro. For example: 
[ros2_control_node-2] <state_interface name="velocity"> 
[ros2_control_node-2]   <param name="initial_value">0.0</param> 
[ros2_control_node-2] </state_interface>

Tracking down the changelist, I suspect it has to do with ros-controls/ros2_control#1051

@sea-bass sea-bass closed this as not planned Won't fix, can't repro, duplicate, stale Jul 10, 2023
@sea-bass sea-bass reopened this Jul 11, 2023
@fmauch
Copy link
Contributor

fmauch commented Apr 10, 2024

This should be fixed in #920

@fmauch fmauch closed this as completed Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants