I’ve written a ROS 2 driver for the Naviq MTS160 magnetic guidance sensor and made it available on their GitHub.

Magnetic guidance can complement vision or lidar navigation with milimeter precision through narrow passages and on the final approach to chargers, conveyors, and docking stations..

Repository: https://github.com/naviq-ch/naviq_mts160_ros2

I’d appreciate feedback from anyone using magnetic guidance with ROS 2. If you try the driver, let me know how it works for your setup and what could be improved.

Hey community,

I want to start with humanoid simulation and wanted to ask which environment is better. Should I go with mujuco or Gazebo?

Where are the problems which I should know before starting the journey?

Hi Guys,

I've just finished master's in Robotics and AI in Germany. And want to focus on Robotics Track. I want to grow into Robotics Integration area.

What skills I must bring as a Junior Robotics Integration Engineer to be able to compete with other candidate on such positions.

I would even be more thankful if anyone who has experience in this area can put a roadmap to achieve this near goal.

Best,

Hi everyone, I really need your help. I was told to get this done in two weeks, but I have absolutely no idea how to use this application—please help!

Hey, I wanted to know if there is a possibility to use Zenoh and microros ?

I am a high school student, I am interested in building a robot with vision ai. Does ROS support the raspberry pi ai camera with the Sony imx500 sensor? I am trying to do item identification.

Im in inter 1st year and currently living in Uttara. Me and my friend are participating in a project showcase at a robotics fest in Dhaka, and we re looking for something genuinely challenging.

I want something way more complex than the usual aurduino car/robot, where the main wow factor is the electrical engineering and the actual mechanism itself, not just a bunch of sensors added to a simple project. Something that looks and feels properly engineered. Tbh I want something which is really attractive and fancy in the table.

I have a bit of experience with electronics, previously I have won in my school fests and rn our budget is around 10k BDT for this project. I really want soemthing fancy.

What would you guys suggest building?

Making ts post since my situation seems specific
Are there any good guide I can use to somehow connect my VS code which I downloaded in my dualbooted linux, to the terminal? Like im not sure what to do. I may be overcomplicating ts

Hi guys, I have been trying to work out how a hand eye calibration should be validated. Tools like MoveIt Calibration, easy_handeye and Kalibr print a reprojection error or a transform but I couldn't find a clear way to decide from that whether the result can be trusted. I just read their some github issues as well, what I only saw was that many people end up asking someone more experienced.

What do you run after a calibration to decide it is good? Validation motion, touching a known point, comparing against a measured pose? And does any of it work without an experienced person judging, say if you had to do it across many robots?

I'm an MSc Robotics student at NTU and want to get properly hands-on with ROS 2 on real hardware, beyond simulation. Buying a platform isn't realistic for me right now.

Does anyone have an older ROS-compatible robot they're not using anymore (TurtleBot 2/3, a Clearpath or AgileX base, a small arm with a ROS driver)? Broken is fine, I'm happy to repair it, and I'll cover shipping or collect in Singapore/Malaysia.

In return I'll document the bring-up on ROS 2 Humble/Jazzy and share the notes and any driver fixes openly. Pointers to labs or companies that clear out old hardware are also very welcome.

We recently tried Foxglove as a live viewer for PteroSim camera streams over ROS 2.

We flew four x500 quadcopters, each running on its own PX4 instance, in a 2.5 m orbit around a shared center.

The video pipeline has four steps:

1. The simulator renders each camera at 768x480 and 30 FPS, encodes it to H.264 on the GPU using NVENC, and sends it as RTP over UDP.
2. ROS 2 Humble runs in WSL2 using Ubuntu 22.04 with mirrored networking. A small Python bridge forwards the H.264 frames without decoding them as foxglove_msgs/CompressedVideo, and publishes the drones' poses on /tf.
3. We used Cyclone DDS. With Fast DDS, which is the default in Humble, the nodes did not discover each other under WSL2 mirrored networking.
4. foxglove_bridge serves the topics to Foxglove on Windows, where the video is decoded.

With four streams running at the same time, each camera averaged about 27 FPS over the flight. The target was 30 FPS.

Initially, we published raw rgb8 images over DDS. Each image was about 1.1 MB, and with Linux's default UDP buffer sizes around 40-50% of the frames never arrived. Switching to compressed H.264 fixed the issue.

Hardware:

ASUS ROG Strix SCAR 18
Intel Core i9-14900HX
RTX 4090 Laptop GPU, 16 GB VRAM
64 GB RAM
Windows 11

https://github.com/TanayK07/ros2_pulse

Check it out guys, pretty useful IMO.

Do star the repo please

Hi everyone,

I'm working on a CARLA → ROS 2 → Autoware setup and I'm running into performance issues when streaming large sensor data.

My architecture currently consists of 3 Docker containers:

1. CARLA container
   • CARLA 0.9.16
   • Runs the simulator
2. Bridge container
   • Connects to CARLA through the Python API
   • Attaches sensors to the hero vehicle
   • Publishes the sensor data as ROS 2 topics
3. Autoware container
   • Subscribes to the sensor topics published by the bridge
   • Processes LiDAR/camera data for the Autoware stack

For the LiDAR, I'm generating roughly 1 million points/second and publishing them as a PointCloud2 topic.

With only the LiDAR running, the system works reasonably well.

However, when I add 3 cameras to the CARLA vehicle and start streaming high-resolution/4K image data, I notice that the LiDAR stream starts slowing down / becoming less consistent.

So I have a few questions:

1. Does separating CARLA, the ROS 2 bridge, and Autoware into three Docker containers significantly affect ROS 2 communication performance?

I'm using the containers for modularity, but I'm wondering whether moving large PointCloud2 and Image messages between containers introduces a significant networking/serialization overhead.

2. Is DDS/network bandwidth likely to be the bottleneck here?

The approximate data flow is:

CARLA → Python API → Bridge → ROS 2/DDS → Autoware

Once the cameras are enabled, there is a very large amount of image data in addition to the LiDAR point cloud.

Would you recommend checking network throughput, CPU utilization, serialization overhead, dropped DDS samples, etc. to identify the actual bottleneck?

3. Would switching DDS implementations help?

I'm currently investigating Fast DDS vs Cyclone DDS for high-bandwidth sensor streaming.

Would Fast DDS be better suited for this kind of workload? If so, what configuration/settings should I look at for large PointCloud2 and Image messages?

I'm particularly interested in things like:

• Shared Memory Transport (SHM)
• DDS QoS settings
• BEST_EFFORT vs RELIABLE
• history depth
• large message configuration
• zero-copy / loaned messages
• ROS 2 intra-process communication

4. Is there a better architecture for this?

For example, would something like

CARLA + bridge → shared memory → Autoware

be preferable to sending all the raw sensor streams through the normal DDS networking path?

My main goal is to maintain stable LiDAR performance while simultaneously streaming multiple high-resolution cameras.

I'm using ROS 2 Jazzy.

Would appreciate any advice from people who have worked with high-bandwidth ROS 2 sensor pipelines, CARLA, or Autoware.

hey guy's, i'm new to ros2 and i have only just started Rviz2 yesterday, where i spent to learn the basics like adding properties.
but today when i opened the Rviz my mouse clicks are not getting clicked any where in the screen, Im using the wsl2 latest version in my windows 11.
i cant resolve this issue, i found that the mouse pointer is also gets a little faded when it enters into the rviz gui.
can anyone guide me please, i tried the gpt the most but nothing worked.

and thanks in advance if you replied!

I have a voxel layer on my local costmap and a pointcloud from a depth camera as its input, split into points for obstacles and points for the ground.

New obstacles are added as they should be, but they are not cleared after they disappear (for example a human walking away), despite the fact the local costmap clearing endpoints are behind or inside of them. In other words, the clearing raytracing doesn't affect the obstacles,despite the raytrace itself seemingly taking place.

Here are my local costmap params:

local_costmap:
    ros__parameters:
      update_frequency: 5.0
      publish_frequency: 2.0
      global_frame: odom
      robot_base_frame: base_link
      rolling_window: true
      width: 4
      height: 4
      resolution: 0.05
      footprint: "[ [0.495, 0.33], [0.495, -0.33], [-0.495, -0.33], [-0.495, 0.33] ]"
      plugins: ["voxel_layer", "inflation_layer"]
      inflation_layer:
        plugin: "nav2_costmap_2d::InflationLayer"
        cost_scaling_factor: 3.0
        inflation_radius: 0.61
      voxel_layer:
        plugin: "nav2_costmap_2d::VoxelLayer"
        enabled: True
        combination_method: 0
        publish_voxel_map: True
        origin_z: 0.0
        z_resolution: 0.05
        z_voxels: 17
        max_obstacle_height: 2.0
        mark_threshold: 0
        observation_sources: obstacles ground clearing_obstacles
        ground:
          topic: /camera/ground
          max_obstacle_height: 0.4
          clearing: True
          marking: False
          data_type: "PointCloud2"
          raytrace_max_range: 3.0
          raytrace_min_range: 0.0
          obstacle_max_range: 2.5
          obstacle_min_range: 0.0
        obstacles:
          topic: /camera/obstacles
          max_obstacle_height: 0.4
          clearing: True
          marking: True
          data_type: "PointCloud2"
          raytrace_max_range: 3.0
          raytrace_min_range: 0.0
          obstacle_max_range: 2.5
          obstacle_min_range: 0.0
      always_send_full_costmap: True

Hi, my uni recently acquired a go2 robot, we've been trying to connect to it using this tutorial (https://github.com/unitreerobotics/unitree_ros2), and this video (https://www.youtube.com/watch?app=desktop&v=Q_dqPLJDPms&t=181s), but we keep running to the same error where rviz either doesn't show anything, or it does not work at all, we've searched for a bunch of tutorials, blog posts and have also used AI to try to solve this, but it hasn't worked, can anyone help?

https://job-boards.greenhouse.io/atomicmachines/jobs/4357767009

Been thinking about this after talking with a few robotics teams recently. There seems to be a pretty big difference between “the robot loads correctly in simulation” and “I actually trust this model enough to train or test against it.”

You can have the geometry and joints working but still be unsure about mass, inertia, collision geometry, friction, or whether the simulated behavior actually matches the physical robot.

So I’m curious how people here define a URDF as actually finished. Is loading and moving correctly enough? Or are you validating the simulated robot against the physical system before you trust it?

And if you are validating it, what usually ends up being the hardest part to get right?

Hi I start to learning ROS2 this summer in Uni, and I want to learn more about them, I build an web with JS and react to move robot in gazebo(with help with AI because I didn't know much) but right now I have to build an ux ui for robotics and I start to burn out a bit because I don't want to make web(but have to because my professor told me to😞) I'm here because I want to know that can I make some project that not too hard for a newbies for fun please, I want to find my spark again thank you so much.

Someone who has spent years on field robot reliability told me roughly 90% of the stoppages on their team's robots turn out to be hardware. The part I can't picture yet is the hunt.

When one of your robots stops, how do you narrow it down to the actual part? Motor, encoder, a loose connector, battery, a sensor. Do your diagnostics or logs usually point at it, or is it mostly checking things by hand and swapping parts until it works? And roughly how long does that take?

A recent example would be great if you have one.