Codesys Ros2 !!better!! -
The first test was simple: let a ROS 2 node tell a conveyor to pause if a vision node detected a misaligned board. CODESYS, always wary, demanded unequivocal safety: a hardware interlock and a watchdog that would seize control if messages failed. They implemented a heartbeat over DDS, wrapped it in a CODESYS library, and made the conveyor a cautious partner: it would accept ROS 2 commands only while the heartbeat remained steady. The result was poetry—the vision node shouted “misaligned” and the PLC’s ladder logic honored the command, the belt stilled, and a red LED blinked like a heartbeat finding a rhythm.
The divide between traditional industrial automation and high-level robotic intelligence is narrowing. For decades, has been the gold standard for IEC 61131-3 PLC programming, powering the world’s factories with deterministic, stable control. On the other side, the Robot Operating System 2 (ROS2) has emerged as the powerhouse for autonomous navigation, computer vision, and complex path planning. codesys ros2
// Create a ROS 2 node auto node = rclcpp::Node::create_node("co_de_sys_node"); The first test was simple: let a ROS
The most exciting development for high-performance applications is the implementation of DDS directly onto the controller. Since ROS2 uses DDS as its middleware, a PLC that speaks DDS can essentially act as a native ROS2 node. On the other side, the Robot Operating System
Micro-ROS allows ROS2 nodes to run on microcontrollers and RTOS-based systems. For CODESYS users, this often involves using a .