How ferbin12/hannah_arm works
Main Components
• Robotic Description & Simulation:
• hannahbot_description: Contains URDF/XACRO files, meshes, and Gazebo/rviz launch files. It defines the physical and visual properties of the manipulator.
• Launch files like gazebo_launch.py (under hannahbot_description/launch) illustrate how the simulator is started.
• Controller & Hardware Interface:
• hannahbot_controller: Provides the ros2_control interfaces and configuration (e.g., controllers.yaml) including nodes for slider control.
• Launch files (controller.launch.py, slider_controller.launch.py) indicate how these controllers are brought up.
• Motion Planning:
• hannahbot_moveit: Houses motion planning configuration (SRDF, kinematics, joint limits, etc.) and MoveIt2 launch files (moveit.launch.py) that interface with OMPL for path planning.
• Messaging and Services:
• hannahbot_msgs: Defines custom ROS2 messages, services (e.g., AddTwoInts.srv, EulerToQuaternion.srv) and actions (Fibonacci.action, ArduinoBotTask.action) that support communication between components.
• Additional Helper Libraries & Examples:
• hannabot_remote, cpp_srvcli, py_service, hannah_bot, hannah_cpp_egs, hannahbot_utils: These contain various ROS2 client/server implementations (in C++ and Python), utility functions (e.g., simple publisher, subscriber, service servers/clients), and example code that demonstrates interfacing with the system.
Relationships & Interactions
• The simulation environment (Gazebo via hannahbot_description) provides the virtual world in which the robot is visualized.
• The robot’s physical configuration (URDF and meshes) is consumed by both the simulator and MoveIt2 for planning.
• The controller package (hannahbot_controller) uses ros2_control to interface with simulated or real hardware.
• The motion planning package (hannahbot_moveit) interfaces with the controllers to generate and execute collision-free trajectories.
• Communication is managed through ROS2 topics, services, and actions defined in hannahbot_msgs, with additional demonstration functionality in cpp_srvcli, py_service, and hannah_bot packages.
• Each ROS2 package is launched individually (with specific launch scripts) but are intended to work together as part of a full robotic system.
Architectural Patterns & Design Principles
• Modular ROS2 Package Architecture: Different functional aspects are encapsulated in individual packages.
• Clear Separation of Concerns: URDF and simulation components (description) are separate from control logic (controller) and planning (moveit).
• Client/Server and Publisher/Subscriber Communication: Demonstrated in multiple packages (cpp_srvcli, py_service, hannah_bot) to facilitate inter-node messaging.
• Use of Launch Files: Centralized configuration for node startup and interconnections.