Dr. Denis
I'll remove the comment, the joints should be exported in defined order as in URDF. We should add test for it. _Originally posted by @destogl in https://github.com/ros-controls/ros2_control_demos/pull/37#discussion_r536880562_
I'll remove the comment, the joints should be exported in defined order as in URDF. We should add test for it. _Originally posted by @destogl in https://github.com/ros-controls/ros2_control_demos/pull/37#discussion_r536880562_
Check the [description](https://github.com/ros-controls/ros2_control_demos/blob/85450cc5cd96c0233123f6a2e09f8d756afe394a/README.md)
For communication with some hardware very high frequencies are desirable, e.g. a force-torque sensor. Nevertheless, the control loop is usually limited to the robot hardware or the "slowest" data source....
Modern robots provide usually multiple interfaces towards them, e.g. position, velocity, acceleration, force, etc. It is thinkable that in some cases a user wants to use different interfaces along the...
Many researchers and hobbyists build their robots by using simple sensors and actuators which usually communicate using separate interfaces and protocols to a computer. The `ros2_control` should support this so...
Industrial robot has usually single interface for all joints, sensors, and actuators to the "outside world". The `ros2_control` should enable custom protocol with such "on-block" communication toward hardware.
Mobile manipulators are now a day almost in every research lab for robotics. These are basically multiple robots assembled into one mechanical construction. If each component is already ros2_control enabled...
When using hardware components they can be in different states. This is really considered in `hardware_interface` in ROS1, which often leads to a completely new start of the whole control...