How hiwincorporation/hiwin_ros works
Project type and purpose
• This is a full-stack ROS-Industrial robotics integration project for HIWIN robotic arms.
• It provides:
• A URDF/XACRO-based robot description (hiwin_description) with collision/visual meshes
• A hardware interface driver (hiwin_driver) that plugs into ros_control
• MoveIt! configurations for three HIWIN models (hiwin_ra605_710_moveit_config, hiwin_ra610_1476_moveit_config, hiwin_ra610_1869_moveit_config)
• A pass-through controller plugin (passthrough_controllers) for simple trajectory forwarding
• Simulation launch files (Gazebo + HRSS Offline) and RViz configs
File structure
• Top-level packages:
• hiwin_description: URDF macros, XACRO includes, YAML kinematics/joint limits, STL meshes for several RA6xx models
• hiwin_driver: C++ hardware_interface plugin, ROS launch files to bring up the robot on real hardware
• hiwin_*_moveit_config: one MoveIt! config per robot model, each containing planning pipelines (OMPL, CHOMP, STOMP, Pilz), sensor managers, controllers, SRDF, warehouse DB setup, and demo/sim launch files
• passthrough_controllers: a minimal controller plugin to relay MoveIt! trajectory commands to hardware
• Notice the separation of concerns:
• Description (kinematics + visuals)
• Driver (control abstraction + hardware comms)
• Planning & execution (MoveIt!)
• Simulation support (Gazebo + HRSS)
Extract architecture cues from the README
• Dependencies: ROS Noetic, ros_control (controller_manager), industrial_robot_client, MoveIt!
• Use cases:
• Simulated planning/execution via Gazebo and HRSS Offline
• Real robot control via hiwin_driver and networked robot_ip
• Best-practice adherence to ROS-Industrial guidelines
Main components
a. Robot Description Layer
• XACRO files & YAML configs → Parameter Server (robot_description, joint_limits, kinematics)
• Mesh assets used by RViz & Gazebo
b. Simulation Layer
• Gazebo + gazebo_ros_control plugin
• HRSS Offline application (external GUI)
c. Control Layer
• ros_control’s controller_manager
• passthrough_controllers or model-specific controllers (position_controllers, joint_trajectory_controller)
d. Driver Layer
• hiwin_driver node/hardware_interface plugin
• Communication link (Ethernet) to physical robot or simulated joints
e. Planning & Execution Layer
• MoveIt! Move Group
• Planning pipelines (OMPL, CHOMP, STOMP, Pilz)
• sensor_manager, planning_context, warehouse DB
• RViz interfaces for visualization & teleoperation
f. External Tools
• HRSS Offline (Windows)
• roslaunch-based demo scripts
Relationships & data flows
• URDF → loaded into Parameter Server
• Parameter Server → Gazebo (spawn model) & MoveIt! (joint limits, kinematics)
• MoveIt! → sends TrajectoryAction goals to controller_manager
• controller_manager → dispatches to passthrough_controllers or position_controller
• Controller plugin → calls hiwin_driver hardware_interface → sends commands over Ethernet to robot
• Robot (sim or real) → reports sensor_msgs/JointState → feeds back into controller_manager & MoveIt!
Architectural patterns & design principles
• Modular ROS packages by concern (description, driver, planning)
• Standard ROS-Industrial & ros_control interfaces
• Separation of simulation vs. hardware launch configurations
• Reusable MoveIt! config templates for multiple robot variants