Innovation Version


      Using ROS

      ROS provides some useful command line tools, which can be used to obtain various information of different nodes. Commonly used commands are as follows:

      • rosnode : operation node
      • rostopic : operation topic
      • rosservice : operation service
      • rosmsg : operation msg
      • rossrv : operation srv msg
      • rosparam : operation param

      Please also refer to:

      Using ROS2

      # Help information of the command
      $ ros2 --help
      usage: ros2 [-h] Call `ros2 <command> -h` for more detailed usage. ...
      ros2 is an extensible command-line tool for ROS 2.
      optional arguments:
        -h, --help            show this help message and exit
        action     Various action related sub-commands
        bag        Various rosbag related sub-commands
        component  Various component related sub-commands
        daemon     Various daemon related sub-commands
        doctor     Check ROS setup and other potential issues
        interface  Show information about ROS interfaces
        launch     Run a launch file
        lifecycle  Various lifecycle related sub-commands
        multicast  Various multicast related sub-commands
        node       Various node related sub-commands
        param      Various param related sub-commands
        pkg        Various package related sub-commands
        run        Run a package specific executable
        security   Various security related sub-commands
        service    Various service related sub-commands
        test       Run a ROS2 launch test
        topic      Various topic related sub-commands
        trace      Trace ROS nodes to get information on their execution
        wtf        Use `wtf` as alias to `doctor`
        Call `ros2 <command> -h` for more detailed usage.


      • You need to run the source /opt/ros/foxy/local_setup.bash or source /opt/ros/noetic/setup.bash command on a newly opened terminal.

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.


      Just a small problem.

      I can fix it online!

      Bug Type
      Specifications and Common Mistakes

      ● Misspellings or punctuation mistakes;

      ● Incorrect links, empty cells, or wrong formats;

      ● Chinese characters in English context;

      ● Minor inconsistencies between the UI and descriptions;

      ● Low writing fluency that does not affect understanding;

      ● Incorrect version numbers, including software package names and version numbers on the UI.


      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

      ● Unclear logic, such as missing classifications, items, and steps.


      ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

      ● Incorrect schematic or architecture diagrams;

      ● Incorrect commands or command parameters;

      ● Incorrect code;

      ● Commands inconsistent with the functions;

      ● Wrong screenshots.

      Risk Warnings

      ● Lack of risk warnings for operations that may damage the system or important data.

      Content Compliance

      ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

      ● Copyright infringement.

      How satisfied are you with this document

      Not satisfied at all
      Very satisfied
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份