ros_control: A generic and simple control framework for ROS

Abstract

SummaryIn recent years the Robot Operating System (Quigley et al. 2009) (ROS) has become the 'de facto' standard framework for robotics software development. The ros_control framework provides the capability to implement and manage robot controllers with a focus on both real-time performance and sharing of controllers in a robot-agnostic way. The primary motivation for a sepate robot-control framework is the lack of realtimesafe communication layer in ROS. Furthermore, the framework implements solutions for controller-lifecycle and hardware resource management as well as abstractions on hardware interfaces with minimal assumptions on hardware or operating system. The clear, modular design of ros_control makes it ideal for both research and industrial use and has indeed seen many such applications to date. The idea of ros_control originates from the pr2_controller_manager framework specific to the PR2 robot but ros_control is fully robot-agnostic. Controllers expose standard ROS interfaces for out-of-the box 3rd party solutions to robotics problems like manipulation path planning (MoveIt! (Chitta, Sucan, and Cousins 2012)) and autonomous navigation (the ROS navigation stack). Hence, a robot made up of a mobile base and an arm that support ros_control doesn't need any additional code to be written, only a few controller configuration files and it is ready to navigate autonomously and do path planning for the arm. ros_control also provides several libraries to support writing custom controllers.

Agimus: a new framework for mapping manipulation motion plans to sequences of hierarchical task-based controllers

“…We briefly describe a system extension allowing to use the overall architecture on robot supporting the ros control [15] architecture. From a system integration point of view, we developed a software extension turning the Stack-of-Tasks into a controller in the ros control architecture.…”

General Hand Guidance Framework using Microsoft HoloLens

“…If the hand is inside this active zone, the motions of the hand are converted to the desired joint values of the robot. ROS Control [16] is then used to select the desired controller. These steps are described in Section III.…”

Large area all-optical ultrasound imaging using robotic control

“…The robotic manipulator was controlled using the Fast Robotic Interface, implemented as a Robotic Operating System (ROS) hardware interface for controlling the joint positions. 8 This allowed all joint positions, velocity, and effort limits to be set and enforced prior to being sent to the controller. The Cartesian control and planning was handled using the Moveit motion planning framework, 9 using the TRAC-IK plugin 10 and the open motion planning library 11 as the inverse kinematics solver and path planner, respectively.…”