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
#216 is introducing the default ros2_control node.
Since the ControllerManager is currently expecting RobotHardware the TestRobotHardware class is hard-coded.
This should be removed as soon and the interface changes and ResourceManager is finished. (see the comments in the code)
The text was updated successfully, but these errors were encountered:
I am not sure I fully understand this issue. What's the benefit of temporary hardcoding TestRobotHardware? Shouldn't the ros2_control node fetch the URDF and get the robot hardware from there?
…lues in "/joint_state" message (ros-controls#217)
* Joint state broadcaster support for specific joint_names and interface_names.
* Added option to map custom values to interface names to standard names in joint_state message.
* Document functionality.
* Add configuration examples
Co-authored-by: Bence Magyar <bence.magyar.robotics@gmail.com>
#216 is introducing the default ros2_control node.
Since the
ControllerManager
is currently expectingRobotHardware
theTestRobotHardware
class is hard-coded.This should be removed as soon and the interface changes and
ResourceManager
is finished. (see the comments in the code)The text was updated successfully, but these errors were encountered: