Practice the ROS2 The Hardware Driver Gap coding problem in Integration. Browser-based execution with automated grading — no local ROS install required. 0% of engineers pass this challenge.
A new motor driver node was added to the system. Operators expect to see its status in rqt_runtime_monitor. The node runs and publishes, but it never appears in the diagnostic monitor.
The bug: the node publishes std_msgs/String to /diagnostics instead of diagnostic_msgs/DiagnosticArray. The diagnostic toolchain ignores messages it can't parse — no error is raised, the node appears healthy, but the monitor stays silent.
Fix the publisher to use diagnostic_msgs/msg/DiagnosticArray with at least one DiagnosticStatus entry so that rqt_runtime_monitor (and any other diagnostic consumer) can read the motor status.
It is a hands-on Integration challenge on SimuCode where you implement and run ROS2 code in the browser with runtime-verified tests.
Open this page, sign in, and solve the problem in the built-in IDE. Your solution is graded against real ROS2 execution checks.
This Easy problem focuses on diagnostics, diagnostic_msgs, message-types skills used in robotics interviews and production systems.