.. toctree:: :hidden: doc/roscon2024_workshop.rst doc/getting_started/getting_started.rst doc/ros2_control/doc/index.rst doc/ros2_controllers/doc/controllers_index.rst doc/ros2_control_demos/doc/index.rst doc/ros2_control/ros2controlcli/doc/userdoc.rst doc/simulators/simulators.rst doc/release_notes/release_notes.rst doc/migration/migration.rst doc/api_list/api_list.rst doc/supported_robots/supported_robots.rst doc/resources/resources.rst doc/contributing/contributing.rst doc/project_ideas.rst doc/acknowledgements/acknowledgements.rst
The ros2_control is a framework for (real-time) control of robots using (ROS 2).
Its packages are a rewrite of ros_control packages used in ROS (Robot Operating System).
ros2_control's goal is to simplify integrating new hardware and overcome some drawbacks.
If you are not familiar with the control theory, please get some idea about it (e.g., at Wikipedia) to get familiar with the terms used in this manual.
The ros2_control framework consists of the following Github repositories:
- ros2_control - the main interfaces and components of the framework;
- ros2_controllers - widely used controllers, such as forward command controller, joint trajectory controller, differential drive controller;
- control_toolbox - some widely-used control theory implementations (e.g. PID) used by controllers;
- realtime_tools - general toolkit for realtime support, e.g., realtime buffers and publishers;
- control_msgs - common messages;
- kinematics_interface - for using C++ kinematics frameworks;
Additionally, there are following (unreleased) packages are relevant for getting-started and project management:
- ros2_control_demos - example implementations of common use-cases for a smooth start;
- roadmap - planning and design docs for the project.
- Questions
- Please use Robotics Stack Exchange and tag your questions with
ros2_control. - WG Meeting
- Every second Wednesday there is a Working Group meeting. To join the meeting check the announcement on ROS Discourse. You can joint the meeting through google groups or directly on Google Meet (check the announcement). To propose new discussion points, or review notes from previous meetings, check this document.
- Projects
- GitHub projects under ros-control organization are used to track the work.
- Bug reports and feature requests
- Use the issue tracker in the corresponding repository for this. Give a short summary of the problem Make sure to provide a minimal list of steps one can follow to reproduce the issue you found Provide relevant information regarding the operating system, ROS distribution, etc.
- General discussions
- Please use ROS Discourse.
Built on 2024-11-04 at 08:07 GMT