Browse categories
Explore
Fiverr Pro
English
$
USD
I will develop a ros2 navigation stack on simulation or rpi5
About this Gig
I build production-grade ROS 2 navigation stacks for autonomous mobile robots and I validate them on real Raspberry Pi 5 hardware before delivery.
Most sellers hand you a repo and hope it runs. I hand you a Docker image that I've personally booted on a Pi 5, with a recorded terminal session proving it.
WHAT YOU GET
URDF/xacro robot model from your CAD or specs
Gazebo simulation with your environment
Full Nav2 stack AMCL, costmaps, path planning, recovery behaviours
ros2_control integration
Complete source code, no black boxes
Docker image + bringup scripts (Standard/Premium)
Documentation with exact tested OS + ROS 2 versions
WHY ME
Robotics Engineer working daily on warehouse AMR systems ROS 2 Jazzy, Nav2, Gazebo Harmonic, RPLiDAR, RealSense. Published researcher. I do this professionally, not as a hobby.
IMPORTANT
No physical hardware is shipped. You receive working, tested software. Bringup on your specific sensors is available as an add-on.
Message me before ordering with your robot specs I'll tell you honestly if it's a fit.
Notes on the choices:
The Docker-validated-on-real-silicon claim is your one genuine differentiator, so it leads. The "recorded terminal session" line is
Platform:
Raspberry Pi
Sensors:
Accelerometer
•
Ultrasonic
•
Infrared
•
Camera
•
Lidar
•
Pressure
Expertise:
Microcontrollers
•
ROS
•
Image processing
FAQ
Do you ship any physical hardware?
No. I deliver software only — full source code, Docker images, launch files, and documentation. You keep your own hardware; I make the code run on it.
What exactly does "validated on real hardware" mean?
I run the delivered container on my own Raspberry Pi 5 before delivery and record the bringup. This guarantees the image builds and runs on the stated board and OS, all nodes launch, and topics publish. Bringup on your specific sensors isn't covered — I can't test hardware I don't have.
What do you need from me to start?
Robot type and drive configuration, sensor models (LiDAR, camera, IMU), motor driver, target board and OS version, and CAD files if you want a custom URDF. The more precise this is, the faster delivery goes.
Which ROS 2 distributions do you support?
Humble and Jazzy. I'll confirm which matches your OS before starting. Tell me if you're locked to a specific distro
Will this work with my exact LiDAR, camera, or motor driver?
Often yes, but I'll only confirm after seeing the model number. If a maintained ROS 2 driver exists, integration is straightforward. If the device is obscure or closed-source, I'll tell you upfront rather than discover it mid-order.
Do I own the code?
Yes. Full commercial rights to everything I deliver. Third-party ROS 2 packages stay under their own open-source licences (mostly Apache 2.0 / BSD), which I list in the documentation.
