<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ros2 on Hugo POUSSEUR</title><link>https://www.blog.test.pouceheure.fr/tags/ros2/</link><description>Recent content in Ros2 on Hugo POUSSEUR</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 22 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.blog.test.pouceheure.fr/tags/ros2/index.xml" rel="self" type="application/rss+xml"/><item><title>URDF: The One File Every ROS 2 Robot Tool Reads</title><link>https://www.blog.test.pouceheure.fr/posts/urdf-robot-description/</link><pubDate>Sun, 22 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.blog.test.pouceheure.fr/posts/urdf-robot-description/</guid><description>A robot is more than one program. One tool draws it, another computes where its hand is, another plans a motion without hitting its own base, another simulates its weight. Each of them needs the same facts: how many joints, how long each link is, where each axis points, how far each joint may turn.
If every tool keeps its own copy of these facts, they drift apart. A link is lengthened in the planner and not in the viewer, and the robot on the screen no longer matches the robot that plans.</description></item><item><title>Cyclone DDS vs Fast DDS: Two Implementations of the Same Standard, and Which One to Use with ROS 2</title><link>https://www.blog.test.pouceheure.fr/posts/cyclonedds-vs-fastdds/</link><pubDate>Sat, 21 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.blog.test.pouceheure.fr/posts/cyclonedds-vs-fastdds/</guid><description>You install ROS 2 and everything works. Then a forum answer says &amp;ldquo;try Cyclone DDS&amp;rdquo;, a MoveIt page tells you to export another RMW, and a colleague says their robot only works over Wi-Fi with Fast DDS tuned by an XML file. You end up with two names, Cyclone DDS and Fast DDS, that both contain &amp;ldquo;DDS&amp;rdquo;, and no clear idea of what is actually different.
This post answers four questions in order.</description></item><item><title>What ros2 daemon start Really Does: Domain ID, RMW and a Stale Graph</title><link>https://www.blog.test.pouceheure.fr/posts/ros2-daemon/</link><pubDate>Thu, 19 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.blog.test.pouceheure.fr/posts/ros2-daemon/</guid><description>Your node is running. Its log says it is publishing. And ros2 topic list does not show the topic. You run the command again, same result. You check the spelling, the namespace, the terminal you sourced.
Then someone tells you to run ros2 daemon stop, then ros2 daemon start, and the topic is there. Nothing was wrong with your node, and nothing in your code changed. A single stop and start was enough.</description></item><item><title>How ROS 2 Builds and Links Packages: Inside colcon, ament and CMake</title><link>https://www.blog.test.pouceheure.fr/posts/ros2-build-system/</link><pubDate>Mon, 09 Nov 2026 00:00:00 +0000</pubDate><guid>https://www.blog.test.pouceheure.fr/posts/ros2-build-system/</guid><description>When you run colcon build in a ROS 2 workspace, how does ROS know which packages to build first, where to find their dependencies, and how to link everything together?
The short answer is that ROS 2 has no compiler, linker or build system of its own. It coordinates existing tools, and a workspace build relies on three separate mechanisms:
colcon reads the package.xml files and decides in which order packages are built.</description></item><item><title>Autonomous Vehicle: Teleop</title><link>https://www.blog.test.pouceheure.fr/projects/autosys-teleop/</link><pubDate>Mon, 10 Nov 2025 00:00:00 +0000</pubDate><guid>https://www.blog.test.pouceheure.fr/projects/autosys-teleop/</guid><description>Demonstration Video Video 1 - Teleoperation Demo. (Train Demo) This Video 1: Teleoperation Demo. (Train Demo) illustrates the longitudinal control of the car via teleoperation.
Example of speed saturation: 0:07 - 0:16 (limited by lateral acceleration) Example of braking: 1:20 (vehicle is stopped by teleop command) Context The vehicle autonomously plans a path and follows it.
A teleoperator controls only the longitudinal speed using a joystick, similar to driving a train.</description></item><item><title>LiDAR Detection &amp; Decision Making</title><link>https://www.blog.test.pouceheure.fr/projects/autosys-lidar-and-decision/</link><pubDate>Tue, 14 Oct 2025 00:00:00 +0000</pubDate><guid>https://www.blog.test.pouceheure.fr/projects/autosys-lidar-and-decision/</guid><description>Demonstration Video 1 - Video demo of the LiDAR Detection pipeline Info: A video demonstration of the decision-making system is coming soon.
Introduction In autonomous driving, the vehicle must be able to make a series of decisions, such as slowing down, stopping at an intersection, or waiting until the road is clear before proceeding.
These decisions depend on the behavior of other road users. The system must therefore identify surrounding obstacles and determine which ones are relevant for decision-making.</description></item><item><title>Traffic Light Detection &amp; Control</title><link>https://www.blog.test.pouceheure.fr/projects/autosys-traffic-light-detection/</link><pubDate>Thu, 15 May 2025 00:00:00 +0000</pubDate><guid>https://www.blog.test.pouceheure.fr/projects/autosys-traffic-light-detection/</guid><description>Motivation As part of an autonomous driving project, I contributed to the development of a system enabling a vehicle to adapt its behavior to traffic lights. The vehicle adjusts its speed according to the current traffic light state.
The project is divided into four main components:
Matching: Identifying traffic light positions on the map Detection: Determining the current state of the traffic light Planning: Adjusting vehicle speed according to the detection result Control: Applying the computed velocity to the vehicle The detection pipeline is implemented in Python, while control is handled in C++ within a ROS2 environment.</description></item><item><title>ROS2 - Dashboard Framework</title><link>https://www.blog.test.pouceheure.fr/projects/dashboard/</link><pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate><guid>https://www.blog.test.pouceheure.fr/projects/dashboard/</guid><description>Overview In robotics and system development, having a clear and flexible interface to visualize system states, sensor data, and real-time metrics is important. This project offers a lightweight dashboard framework designed for ROS 2, allowing quick creation of dashboards through simple configuration files.
Video 1 - Demo video of the dashboard overlaid on video. The Video 1: Demo video of the dashboard overlaid on video. shows a demo of the dashboard running over a video stream.</description></item><item><title>RViz2 - Virtual Camera</title><link>https://www.blog.test.pouceheure.fr/projects/rviz-virtual-camera/</link><pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate><guid>https://www.blog.test.pouceheure.fr/projects/rviz-virtual-camera/</guid><description>Demonstration Video 1 - Demo: Example output from a virtual camera. The following demontration, Video 1: Demo: Example output from a virtual camera. , shows the video created from a virtual camera. The virtual camera is attached to a frame, fixed to vehicle.
Motivation At first, I recorded the screen during experiments, but this was not a good solution because:
process it&amp;rsquo;s more complex to setup, it uses too many resources, the video quality is low, I must keep the window and RViz view in the same place.</description></item><item><title>Autonomous Vehicle: Control</title><link>https://www.blog.test.pouceheure.fr/projects/autosys-control/</link><pubDate>Fri, 20 Dec 2024 00:00:00 +0000</pubDate><guid>https://www.blog.test.pouceheure.fr/projects/autosys-control/</guid><description>Demonstration Video 1 - Demo video: planning and control in action. Overview As part of a collaborative autonomous driving project, I contributed to the low-level control system responsible for translating navigation commands into actuator signals (steering and torque).
This system is fully integrated into a ROS2-based autonomous stack and has been deployed and tested on a real electric vehicle with in-wheel motors.
Fig. 1 - Interfaces between planning and control modules.</description></item><item><title>Autonomous Vehicle: Planning</title><link>https://www.blog.test.pouceheure.fr/projects/autosys-local-planning/</link><pubDate>Tue, 10 Dec 2024 00:00:00 +0000</pubDate><guid>https://www.blog.test.pouceheure.fr/projects/autosys-local-planning/</guid><description>Demonstration Video 1 - Demo video, pedestrian avoidance using lidar detection. Video 2 - Demo video, slalom test. Video 3 - Demo video, curve test. Overview As part of a collaborative autonomous driving project, I contributed to the implementation of the core planning functionalities for autonomous driving.
The navigation stack transforms a target position into a safe and efficient motion trajectory using environmental context and map information.
The process is divided into three stages:</description></item></channel></rss>