How ak-wagle/my_bot works
Main Components
a. Robot Description & Hardware Abstraction:
b. Configuration & Parameter Management:
• A section for “Configurations” encompassing all YAML files (e.g., nav2_params.yaml, ball_tracker_params_*.yaml, joystick.yaml). These files parameterize the various ROS nodes for localization, mapping, control, and ball tracking.
c. ROS Launch & Execution:
• A “Launch System” component that includes all the Python launch scripts (e.g., launch_robot.launch.py, ball_tracker.launch.py, navigation_launch.py, rsp.launch.py, etc.). These scripts instantiate and configure ROS nodes at runtime.
d. Simulation Environment:
• A “Simulation & Gazebo” block that references the worlds (empty.world, obstacles.world, obstacles101) and possibly includes Gazebo control (gazebo_control.xacro) being used to simulate the robot’s interaction with physical world dynamics.
e. SLAM and Navigation:
f. Ball Tracking and Joystick Control:
g. Web-Based Control Interface:
• A “Web Controller” module which is built in a separate directory. Label it with the technologies at play (React/Vite, ESLint configuration, etc.). Indicate it communicates via ROS 2 websocket/video server packages provided externally by collaborators.
Relationships and Data Flow
• “Robot Description & URDF” to the “Simulation & Gazebo” as well as to hardware-specific nodes if applicable.
• Sensor data (from simulation or real hardware) flowing to SLAM/Localization.
• Control commands from joystick or web-controller nodes to the drive system.
• Telemetry feedback (visualization, RViz configurations) linking with both simulation and web dashboard.
• Middleware (ROS topics/services) that link the various components.
Architectural Patterns and Key Design Principles
• Separation of Concerns: Emphasize that the project separates simulation, control, and configuration into distinct modules.
• Modularity: The existence of dedicated launch files and config files shows that each subsystem (e.g., SLAM, ball tracking, web control) is developed independently but interacts over a common ROS 2 middleware.
• Extensibility: The web-controller is a clear external module that interacts with ROS 2 via well-defined interfaces.
• Detail individual components around the core, linking configuration files to their respective nodes.
• Be precise: ensure all nodes, scripts, and configurations as discerned from the file tree and README are represented.