ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2019-11-29 18:51:31 -0500 | received badge | ● Famous Question (source) |
2017-04-03 17:58:36 -0500 | received badge | ● Notable Question (source) |
2017-01-12 04:13:16 -0500 | received badge | ● Popular Question (source) |
2016-09-04 10:47:13 -0500 | received badge | ● Enthusiast |
2016-09-02 09:48:00 -0500 | asked a question | Load stopped alongside running controllers using roslaunch. I have a 7 DOF robotic arm with a gripper (2 prismatic joints) simulated in Gazebo and Ι am using ROS control to control it. Every joint has an Effort Joint Interface, so Ι am using effort based position controllers provided by ROS control. However, under certain circumstances Ι wish to use effort controllers for the prismatic joints on my gripper instead. This feature is provided by the controller_manager's SwitchController Service, but the problem is that the service needs the controller to be already loaded. I load my controllers using roslaunch controller manager options but Ι can't load both controllers because they're using the same interface. So I can either load every controller stopped using the --stopped option or I could load every position controller as usual and load the EffortController manually. Is there a way to load and start the position controllers, and load in stopped mode the effort controller using only roslaunch? |
2016-07-18 14:16:19 -0500 | commented answer | Controlling joints in Gazebo You probably mean the robot_state_publisher subscribes to /joint_states topic and publishes the corresponding TF tree. |