Package Summary

Tags No category tags.
Version 0.1.0
License BSD Clause 3
Build type AMENT_CMAKE

Repository Summary

Checkout URI
VCS Type git
VCS Version humble
Last Updated 2024-06-17
CI status No Continuous Integration
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

The andino_control package

Additional Links

No additional links.


  • Franco Cipollone


  • Franco Cipollone



ROS 2 Control is being used for controlling the robot and to interface with ROS framework.

The following diagram describes several parts of the system that controls the robot via ROS 2 control tools.

flowchart TD
    %% COLORS %%
    classDef blue fill:#2374f7,stroke:#000,stroke-width:2px,color:#fff
    classDef red fill:#ed2633,stroke:#000,stroke-width:2px,color:#fff
    classDef green fill:#16b522,stroke:#000,stroke-width:2px,color:#fff
    classDef orange fill:#fc822b,stroke:#000,stroke-width:2px,color:#fff

    %% DIAGRAM %%

    A(Diff Drive Controller):::blue ---|encoder read/velocity interface| B(Hardware Interface):::green
    C(Joint State Broadcaster):::blue ---|encoder read| B(Hardware Interface)

    M(Controller Manager):::orange -..->|manages lifecycle| A
    M(Controller Manager) -..-> |manages lifecycle| C
    M(Controller Manager) -..-> |activates hw component| B

    D["/cmd_vel"] -->|subs| A
    A -->|pubs| O["/odom"]
    A -->|pubs| T["/tf"]
    C -->|pubs| J["/joint_states"]

    linkStyle default stroke:red
    linkStyle 0 stroke-width:4px,stroke:green
    linkStyle 1 stroke-width:4px,stroke:green
    linkStyle 5 stroke:blue

Hardware Interface

The hardware interface component for this robot is implemented by andino_base package. It is in charge of providing the necessary state and command interfaces to be claimed by the controllers.

Controller Manager

The Controller Manager is in charge of managing the lifecycle of the controllers, access to the hardware interfaces and offers services to the ROS-world.

The hardware interface to be activated when controller_manager node is activated is indicated via robot description passed via ROS 2 Parameter. A tag <ros2_control> is expected to be present in the robot description with the information of the hardware components to be activated as well as the state and command interfaces. See andino_control.urdf.xacro.

ROS 2 Controllers

Two controllers are being used from the available ros2_controllers: - diff_drive_controller: Controller for mobile robots with differential drive. Input for control are robot body velocity commands which are translated to wheel commands for the differential drive base. Odometry is computed from hardware feedback and published. - Used state interfaces: - left wheel velocity - right wheel velocity - left wheel position - right wheel position - Used command interfaces - left wheel velocity - right wheel velocity - joint_state_broadcaster: The broadcaster reads all state interfaces and reports them on /joint_states and /dynamic_joint_states. - Used state interfaces: - left wheel position - right wheel position

Each controller accepts ROS 2 parameters which they are provided via andino_controllers.yaml.


Changelog for package andino_control

0.1.0 (2023-10-09)

  • Sets up ros control for the andino robot
  • Contributors: Franco Cipollone

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

No launch files found


No message files found.


No service files found


No plugins found.

Recent questions tagged andino_control at Robotics Stack Exchange