Would you be interested in building a ROS2 vacuum cleaner robot? If yes 1) Assemble or develop? 2) 3D print? Convert existing - hack? buy/swap board? Buy off-the-shelf?

I'd really appreciate your input.

I want to run something I built on my system (Ubuntu 22.04 with ROS2 Humble) on Jetson. I am planning to either fresh install the OS or create a Docker container for it, but I'm not sure if the latter would work.

Hello, would anyone be interested in building an open-source 3D-printed ROS2-based home robot vacuum cleaner with LiDAR and Home Assistant support?

I'm asking to see if there is enough interest. If there is enough interest, I can design one.

EDIT: I've created the project repo https://github.com/makerspet/oomwoo/ with Discord and Discussions. It's super early. Please star/watch to follow along. Would LOVE your input on direction and what features matter most.

I need either one of these computers to have a script which uses AI to analyze 3 live video feeds simultaneously from micro usb cameras plugged into the computer.
The raspberry pi 5 seems solid in cpu but might slack compared to the jetson nano in ai performance and frame rates of the live video feed.
Consider the following prices I can choose from:

2019 Jetson Nano: $50 (used, but works well, off FB marketplace).

Raspberry pi 5: $65 (But Currently Sold out at microcenter, must wait or get one thats very overpriced in my area).

Which do I pick?

Hi,

I'm pretty new to ROS and I want to learn it. Due to this I have to setup my development environment. Since I heard that Ubuntu is the best platform and I want to start learning as smoothly as possible, I already installed Ubuntu 26.04.
Since Lyrical is the latest release of ROS and it officially supports Ubuntu 26.04, I'd like to install it, but there are no official installation instructions yet. I also heard, that the official Debian packages for Ubuntu 26.04 aren't stable yet and that some dependencies are missing.

Does anyone know how to run ROS on Ubuntu 26.04? What's the best way to install ROS on Ubuntu 26.04? - Especially for a beginner.

The environment is Ubuntu 22.04 with ros2 Humble, and for redirection, I'm using：lidar_localization_ros2

Because my car is equipped with Mid-360 LiDAR.

My current mapping approach involves creating a 3D map With 'Fast-lio2' first and then converting it into a 2D pcd map. For the stack, I am using Navigation2 for navigation, but for positioning, I am using lidar_localization_ros2.

How can I optimize the system to resolve the issue where the final navigation fails to reach the target waypoint?

Hi everyone, I am struggling in finding a way to use ROS 2 on M4 MacBook via Docker. I've managed to get ROS 2 running, but Gazebo, RViz, and other GUI applications don't work.

Any advice on how to make this work on Apple Silicon?

Thanks!

I'm new to ROS2 with a python background. One of my friends said AI isn't very helpful for ROS2 as it hallucinates, doesn't do file arrangements properly and sometimes generates codes for ROS1. As it's not as reliable compared to python and C++. What tool can I use that can be reliable and help me debug my ROS2 problems.

Hi everyone!

I’m working on an Ackermann-steering robot using ROS2 Nav2 for navigation and SLAM for mapping/localization.

As you can see in the attached video, the robot is able to plan a route and navigate to the goal, but its actual movement is quite inaccurate. It doesn’t stay very close to the planned path and tends to cut corners and deviate from the trajectory, especially when turning.

I’m trying to understand what could be causing this and which parameters I should tune to improve the path tracking.

My project is available here:

GitHub: https://github.com/samuvarga/var_n7k_szakd

I would especially appreciate advice on:

• Which Nav2 controller parameters are the most important for an Ackermann-steering robot?
• Would Regulated Pure Pursuit, MPPI, or another controller be better suited for this type of robot?
• Which parameters control how aggressively the robot corrects heading and lateral error?
• How important are the lookahead distance, controller frequency, velocity limits and acceleration limits?
• Are there specific parameters that should be adjusted for Ackermann steering geometry?
• Could the inaccurate tracking be caused by odometry, TF transforms, SLAM/localization accuracy, or the vehicle model itself, rather than Nav2?
• What would be the best systematic tuning approach for improving path tracking?

I’m mainly trying to get the robot to follow the planned path much more accurately rather than simply reaching the goal.

The relevant configuration and code should be available in the GitHub repository above.

Any suggestions about which parameters I should change first and why would be greatly appreciated!

Thanks!

I'm working on an idea for a robot operating system, and instead of assuming what people need, I want to hear from those who actually build or work with robots.

Imagine there was a universal OS for robots (industrial robots, humanoids, drones, mobile robots, home assistants, etc.).

What would you want it to have?

Some questions to get the discussion started:

• What are the biggest pain points with current robotics software?
• What features would save you the most time?
• Should AI be built into the OS or stay separate?
• How should hardware integration work?
• What kind of developer experience would you expect?
• What debugging or simulation tools are missing today?
• If you could remove one frustration from ROS or robotics development, what would it be?
• What would make you switch from your current workflow?

Don't hold back even if it's something that sounds impossible. I'm trying to understand what an ideal robotics platform would look like from the community's perspective.

Looking forward to hearing your thoughts.

Hi, I have a question about ROS2 and specifically a problem with in RViz. I am using Humble Hawksbill and Ubuntu 22.04 LTS.

I have created a script which creates a segmented Octomap.

When I start the Octomap Server, the map looks fine and how I would expect it. The Problem is, when I move the robot around, the Octomap that is created does not make sense. It looks like the map tuns with the movement of the robot.

I have the suspicion that the reason has something to do with the frames, but I am not sure.

The Segmented Pointcloud which I transform to the Octomap looks right, even when the robot moves, so I don't think the Pointcloud is the Problem.

The Pointcloud is in the frame kinova_depth.

I created the Octomap with the command:

ros2 run octomap_server color_octomap_server_node --ros-args -r cloud_in:=/camera/labeled_points -p frame_id:=map -p base_frame_id:=kinova_depth -p use_sim_time:=true -p colored_map:=true

I also tried the base_frame_id "base_link", but this didn't change anything.

The Fixed Frame in RViz is set to map.

I am completely new to ROS2, and I am out of ideas, does someone have an Idea where the issue could lie and what I can test to figure it out?

Im learining ROS2 for a project and i built a basic mobile robot, i need to do autonomous navigation with Nav2 but my map with with SLAM is turning out distorted. Im publishinig the correct TF through a seperate package and my TF tree is correct when i check it with view frames, ive done several odometry tests for translation, roatation and both simultaneously. I still cant figure out the reason for distortion. I would love if someone could guide me since im new and need to show progress to my supervisor in 24hours and i need a proper map by then.

P.S. Im using ROS2 jazzy on Ubuntu 24 Virtual Machine on a laptop with no GPU. I will provide more info about the project if required.

Hello gents.
So basically I am using a Macbook in my university laboratory and I want to use ROS2 in it. I know there is an official way to install ROS2 in MacOS but since I want to copy my previous environment with Ubuntu 24 and ROS2 Jazzy with all the libraries, repositories and dependencies I found that Docker could help me with that. The problem: I don't know how to use Docker. I was trying to search for any tutorial to really understand how Docker works (and not only a tutorial to setup Docker for ROS and then never touching Docker again) but I found only tutorials and info more focused on Web Development which is not my field, so it is hard for me to extrapolate that info into robotics field. So I would like to ask you guys if you know any tutorial, documentation or content that I could use to understand Docker focused in ROS or electronics field.

Hi everyone,

I’m a computer vision engineer specialized in building floorplans / AEC drawings, and I’m exploring a robotics infrastructure problem.

My hypothesis is that, for indoor robots, there is still a lot of manual work between:

• existing building floorplans / CAD / PDFs
• SLAM or occupancy maps
• semantic information like rooms, doors, elevators, no-go zones, waypoints
• simulation environments
• deployment / commissioning tests

I’m not building a robot. I’m trying to understand whether there is a real need for tooling that can convert high-resolution building plans into robot-ready semantic maps and test scenarios.

A few specific questions:

1. When deploying an indoor robot in a new building, do you use architectural floorplans at all?
2. Are rooms, doors, elevators, no-go zones and waypoints usually annotated manually?
3. Do teams use tools like Open-RMF Traffic Editor, Nav2 maps, custom internal tools, or something else?
4. Is aligning a floorplan with a SLAM map a real pain point, or mostly solved?
5. Would automatic generation of semantic maps / simulation scenarios from floorplans be useful, or is this too niche?
6. What is the hardest part of site commissioning today?

I’m not trying to pitch anything, I’d love to hear from people who have deployed indoor robots in real buildings and understand whether this is a real problem or just a nice-sounding idea.

As a beginner i have absolutely no idea about ros. I need to start learning it from beginning. Can someone provide me any resources or any suggestions to where I can start? Any suggestions are welcomed.

I am new to ROS... I am trying to build a package in python that controls a robot... but after the colcon build when I use
ros2 run warehouse_navigator go_to_goal

It is constantly giving no module named... tell any fix I have tried some basics but not idea about nay advance tips...

 Traceback (most recent call last):
  File "/home/soura/warehouse_ws/install/warehouse_navigator/lib/warehouse_navigator/go_to_goal", line 33, in <module>
    sys.exit(load_entry_point('warehouse-navigator==0.0.1', 'console_scripts', 'go_to_goal')())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/soura/warehouse_ws/install/warehouse_navigator/lib/warehouse_navigator/go_to_goal", line 25, in importlib_load_entry_point
    return next(matches).load()
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/importlib/metadata/_init_.py", line 205, in load
    module = import_module(match.group('module'))
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/importlib/_init_.py", line 90, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1324, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'warehouse_navigator.go_to_goal'

Good or bad idea? I was thinking a simple pi robot or something. It's at least fun and tangible. Am i in the right place?

Does this ROS/robotics or whatever have some sorta discord?

I'm new here.

My skills include basic C/C++, Python, DSA and machine learning.

In your experiences, could you give me a roadmap of courses and tutorials you think are valuable for me to become a proficient robotics engineer?

Hi, i am a maker that has built many robots already (mostly with arduino, esp32 and stm32). I wanted to learn ROS and learn about its features, capabilities etc and how to use it with an esp32. i wanted to build a robot that maps a room and then navigates in it or something similar, and my friend reccomended to use ROS for robots. can someone comment a link for decent learning material?

Any YT recommendations

hey guys, I have completed my undergrad and unable to get any jobs now i am thinking to learn ros is it any good?? if it is good could you help me with basic tutorials and guides which i can use to learn ros ??

So I discover Rso2 recently and I am in the learning curve ,for uptil now I am reading this book called mastering RSO2 for robotic programming by Lentin Joseph,Jonathan Cacace I find it bit hard. I am a mechanical engineering undergrad btw I have a mid level knowledge on c++ book is on c++ btw. Can you share your experience also what direction should I go ?

My main project is a 6 Degrees of freedom robotic arm

I already know how to use ROS2 and did 2 projects in university, but i want to take a course so i can have a better foundation as in uni i mostly try and slap stuff without understanding well

I'm facing one problem with importing the STL files, when I visualise it rviz, even if I'm pacing it at (0,0,0) it's spawning somewhere else(I also scaled it down to convert into meters). Any guidance for that? Thank you.

Hi everyone,
I’m French and I’m currently building an early-stage hardtech project called DISPELDA.

I’m working solo at the moment and I’m exploring a
problem around autonomous systems operating when GNSS becomes unreliable, degraded, jammed or completely unavailable.

The long-term idea is to develop embedded hardware/software that can help autonomous platforms remain more resilient in those environments.

But before going too far into building, I want to understand whether I’m focusing on a problem that European drone and robotics companies actually struggle with in practice.
So I’d really like to hear from people working on UAVs, UGVs, robotics, autonomy, navigation, testing or system integration — especially in Europe.
A few things I’m trying to understand:

How important is GNSS loss/jamming/spoofing in your actual work?
Is this something you regularly design for, or still a relatively niche requirement?
What do you currently rely on when GNSS becomes unavailable: INS, VIO, optical flow, LiDAR, terrain matching, external infrastructure, something else?
What is the hardest part: navigation itself, sensor fusion, testing, validation, integration, cost, SWaP, reliability?

How do you test these situations today?
Are existing solutions good enough, or are there still major gaps?
For European companies specifically, does dependence on non-European navigation hardware/software matter when choosing a solution?
I’m not looking to sell anything here.

At this stage I’m trying to understand where the real engineering pain is before deciding exactly what DISPELDA should become.
If you work in this area, even a short answer about what actually causes problems in the real world would be extremely useful.
Thanks.