https://blanpa.github.io/tags/ros-2/Recent content in ROS 2 on blanpaHugo -- gohugo.ioenblanpa@pm.me (blanpa)blanpa@pm.me (blanpa)© 2026 blanpaSun, 04 Oct 2026 00:00:00 +0000https://blanpa.github.io/projects/ros2-suite/Sun, 04 Oct 2026 00:00:00 +0000blanpa@pm.me (blanpa)https://blanpa.github.io/projects/ros2-suite/<h2 class="relative group">The Problem <div id="the-problem" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-problem" aria-label="Anchor">#</a> </span> </h2> <p>A robot on the shop floor is one more machine whose data and commands belong in the same flows as the PLC next to it — but ROS 2 does not make that easy from the outside. The usual Node-RED packages build on rclnodejs, which wants a full ROS installation of the matching distro on the Node-RED host and a native build against it; that rules out the palette manager, most gateway images and every machine that is not the robot. And once it runs, the first subscription that receives nothing gives no hint whether the topic name is wrong, the publisher is idle or the QoS does not match.</p>