
Open
Posted
•
Ends in 6 days
Paid on delivery
My Gazebo hospital-auction simulation runs three TurtleBot3s under ROS 2 Humble on Ubuntu 22.04. The nodes launch without crashing, NLP commands publish correctly, yet nothing appears or moves in RViz. RViz throws its usual “Global Options → Fixed Frame does not exist” warning, so the TF tree clearly is not reaching the visualiser; after that the robots ignore the velocity messages as well. I need someone experienced with ROS 2 Humble, TF2, Gazebo / Ignition, and TurtleBot3 launch stacks to jump in, inspect the running graph, and eliminate the missing-frame problem so the three bots become visible and responsive again. I have all launch files, URDFs, and NLP command source ready to share over a screen-share or repo. You’d trace the TF broadcasts, confirm the map/odom/base_footprint chain, adjust any static transforms or frame names in the xacro + launch files, and then verify that geometry appears in RViz and that the /cmd_vel from the NLP pipeline produces motion in simulation. Deliverables – once you’re done I’d like: • A patched set of launch/URDF files or a concise diff showing the fix • A short note explaining the root cause so I can avoid it in future • Demonstration (screen recording or live session) of all three robots visible in RViz and responding to spoken commands If you’ve untangled TF “frame does not exist” errors before, this should be straightforward. Let’s get these bots moving.
Project ID: 40387238
3 proposals
Open for bidding
Remote project
Active 1 hour ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs
3 freelancers are bidding on average ₹900 INR for this job

I can help you fix this quickly. I’m a mechatronics engineer with 5+ years in robotics, working extensively with ROS2 Humble, TF2, Gazebo/Ignition, and TurtleBot3 systems. I’ve debugged multiple cases where RViz shows “Fixed Frame does not exist” and robots don’t respond due to broken TF chains or misconfigured frames. From your description, this is likely a TF tree issue (missing map→odom→base_footprint chain or wrong frame names / namespaces across the 3 robots). I’ve handled similar multi-robot setups where TF wasn’t correctly namespaced or published, causing exactly this behavior. I can: • Trace and fix the TF tree (static + dynamic transforms) • Align URDF/xacro frame names with Nav2/Gazebo expectations • Debug multi-robot namespaces and TF conflicts • Ensure RViz visualization + /cmd_vel actually drives the robots You’ll get: ✔ Clean patch/diff of fixes ✔ Clear explanation of root cause ✔ Demo showing all 3 robots visible + moving I can start immediately and resolve this fast
₹1,500 INR in 1 day
3.5
3.5

Hi, I’m a Robotics Software Engineer with strong ROS 2 experience, including TF2, Gazebo, and many autonomous robot systems. I’ve encountered and fixed this exact “fixed frame does not exist” / TF tree issue many times. I can quickly trace the TF chain, fix the frame setup, and get your robots visible and moving again in RViz. Happy to jump on a call and resolve this fast. Best regards, Miloš
₹600 INR in 1 day
0.0
0.0

Experience with tf2 and ros2 humble. Also design and operated own 2 wheeled differential robot for education
₹600 INR in 7 days
0.0
0.0

Delhi, India
Member since Apr 21, 2026
$250-750 USD
₹1500-12500 INR
₹600-1500 INR
₹400-750 INR / hour
$250-750 USD
$10-30 CAD
$1500-3000 USD
$250-750 USD
$30-250 USD
$8-15 AUD / hour
$349-350 USD
$10-30 AUD
£750-1500 GBP
$10-30 USD
$30-250 CAD
$750-1500 USD
$250-750 AUD
$10-200 USD
₹75000-150000 INR
$10-30 AUD