How ifl-camp/iiwa_stack works
Main Components
• Robot Description & Model:
– Represented by the “iiwa_description” package, which contains URDF/xacro files and meshes. This module defines the physical and visual model of the robot used for simulation and planning.
• Control Node & Motion Execution:
– “iiwa_control” contains launch files and configuration for high-level robot motion commands (integration with KUKA’s SmartServo and PTP motions).
• Hardware Interface:
– “iiwa_hw” encapsulates the hardware abstraction layer, including configuration and drivers (e.g., joint names YAML, hardware launch files, hardware plugin XML) that directly interface with robot actuators and sensors.
• Simulation Environment:
– “iiwa_gazebo” sets up the simulated robot environment for Gazebo, including world and launch files.
• Motion Planning & MoveIt! Integration:
– “iiwa_moveit” holds the configuration and launch files for integrating with MoveIt!. This includes planning pipelines, kinematics, and controllers.
• Message & Service Definitions:
– “iiwa_msgs” provides all the custom ROS messages, actions, and services needed for communication between components.
• ROS Interface Libraries (C++ and Java):
– “iiwa_ros” serves as the C++ client library bridging commands, services, and states across the project.
– “iiwa_ros_java” includes ROSJava nodes and helper classes that run as a Sunrise RoboticApplication on the robot, enabling native ROSJava integration.
Relationships and Interactions
• The ROS Master forms the backbone, orchestrating communication across all packages.
• “iiwa_msgs” acts as the lingua franca; all other modules (control, hardware, planning, Java interfaces) publish and subscribe to its topics/services.
• The “iiwa_control” and “iiwa_ros” packages manage sending control commands (via topics and services) that eventually propagate to the hardware layer (“iiwa_hw”) or get processed by the motion planning node (“iiwa_moveit”).
• “iiwa_description” feeds the robot model into both simulation (“iiwa_gazebo”) and planning (“iiwa_moveit”).
• “iiwa_ros_java” provides an alternative interface—running on the robot’s native environment—to support motion commands, status publishing, and parameter handling, effectively bridging the needs of Sunrise with the ROS ecosystem.
Architectural Patterns and Design Principles
• Modularity: Each package corresponds to a distinct component (e.g., control, simulation, hardware) and is loosely coupled through ROS messaging.
• Separation of Concerns: The stack delineates robot modeling, control commands, hardware drivers, and planning logic in separate modules.
• Middleware-Based Communication: The use of ROS topics, services, and actions ensures that data flow is consistent and decoupled.
Instructive Elements
• Rectangles for software modules.
• A central cloud or star for the ROS Master.
– Optionally add annotations that explain the communication type (e.g., “publishes JointPosition msg” or “calls ConfigureControlMode service”).