How arghyachatterjee/autonomous-docking-for-mobile-robots works
Project type and purpose
• This is an open-source ROS (Robot Operating System) software suite for autonomous docking of differential-drive robots.
• It comprises three ROS packages:
• autodock_core – the core docking logic implemented as a state machine and action-server.
• autodock_sim – Gazebo simulation worlds, models, and plugins to simulate the robot and charger.
• autodock_examples – demonstration scripts, RViz configurations, and test cases.
File structure
Top level
• Dockerfile – containerizes the ROS workspace.
autodock_core
• action/AutoDocking.action – defines the docking goal/result action interface.
• launch/autodock_server.launch – brings up the core docking action server.
• scripts/autodock_core/*.py – Python ROS nodes (server, utilities, simple CLI).
• src/*.cpp – C++ components (e.g., ObstacleObserver).
• setup.py, package.xml, CMakeLists.txt – build and packaging.
autodock_sim
• launch/*.launch – Gazebo worlds (charging.world, tb3_charging.world).
• models/ – URDF/SDF models, textures, charger, robot meshes.
• src/ChargingStationPlugin.cpp – Gazebo plugin publishing charger pose / fiducial.
autodock_examples
• configs/*.yaml – example docking server configurations per robot.
• rviz/ – camera/fiducial visualization presets.
• scripts/*.py – scripted docking tests (mock robot, Turtlebot3).
README for additional insights
• Core logic uses ROS actionlib and a state machine to drive docking steps (approach, align, dock).
• Fiducial marker detection is performed by an external node (UbiquityRobotics/fiducials).
• Can integrate with the Turtlebot3 Navigation Stack or operate standalone.
• Provides Docker deployment for reproducible builds.