How doosanrobotics/doosan-robot works
Project Type & Purpose
• This is a ROS1‐Noetic multi‐package robotics framework for Doosan manipulators, combining real‐robot control, simulation (Gazebo), motion planning (MoveIt), and example/demo code.
• It’s structured as a catkin workspace with ROS packages for messages (dsr_msgs), low‐level control (dsr_control + common), simulation (dsr_gazebo + Docker‐based DRCF emulator), robot description (dsr_description), launch helpers (dsr_launcher), MoveIt configs, and examples (dsr_example_py).
File Structure Highlights
• Top‐level: .devcontainer, CMakeLists.txt, README.md – defines workspace-level config.
• common: C/C++ library + Python wrappers + DRCF emulator binaries & Docker setup.
• dsr_msgs: all custom ROS message & service definitions.
• dsr_control: ROS node implementing hardware interface (real or emulator) using dsr_msgs.
• dsr_description: URDF/XACRO robot models, meshes, and plugins for Gazebo.
• dsr_gazebo: Gazebo worlds and ROS‐control plugin, loads robot into sim.
• moveit_config_*: one package per robot model, providing SRDF, planning & controller YAMLs, MoveIt launch files.
• dsr_launcher: meta‐package with launch scripts tying all nodes together for single‐ or multi‐robot setups.
• dsr_example_py: Python demos showing how to call ROS services/topics.
Key README Insights
• Two operation modes: virtual (uses Docker‐based DRCF emulator) vs real (connects to physical robot over TCP).
• Typical launch flow:
• Start emulator (if virtual) → launch robot_description + Gazebo base → launch dsr_control node → (optionally) launch MoveIt (move_group) → open RViz.
• ROS namespace conventions for multi‐robot.
a. ROS Master (central coordination)
b. drfc_emulator (Docker container)
• Runs DRCF binary, exposes a TCP port (default 12345).
c. dsr_control_node
• Subscribes/publishes ROS topics (joint states, control commands)
• Connects via TCP to emulator or real controller (host/port)
• Uses common library for lower‐level comms
d. dsr_description_node (xacro/URDF loader)
• Publishes robot_description parameter & tf transforms
• Provides meshes & collision geometry to Gazebo and RViz
e. gazebo_ros_control Plugin (in dsr_gazebo)
• Bridges Gazebo joint updates ↔ ROS controller interfaces
• Loads robot model into simulation world
f. MoveIt (move_group & PlanningScene)
• Consumes robot_description/SRDF
• Issues trajectory commands to dsr_control_node via ROS controllers
g. RViz
• Visualizes tf, joint states, MoveIt planning & execution
h. dsr_msgs
• Defines all message/service APIs between nodes
i. dsr_launcher
• Composes the above components in launch files, manages namespaces, arguments
j. dsr_example_py
• User‐level demo scripts invoking ROS services/topics to drive the robot
Architectural Patterns & Design Principles
• Modular ROS package structure: separation of msgs, description, control, simulation, planning, examples.
• Plugin architecture: Gazebo plugins for robot control, xacro macros for reusable URDF components.
• Client‐server over TCP: dsr_control ↔ emulator/real controller.