ICON ROS 2 hardware-module controller

Follow a vendor example, not just the bridge build

The repository targets ROS 2 Kilted on Ubuntu 24.04 and includes Universal Robots and FANUC examples. The UR examples name UR3e, UR5e and UR10e; the FANUC documentation points to several controller families. Those are documented integration paths, not hardware combinations tested by this publication. [S001]

The packaging workflow uses Docker, Bazel and inctl, so ROS need not be installed directly on the host for that route. A usable deployment also needs the selected vendor's controller setup, hardware description and control-service configuration. The main guide is written around Enterprise deployment, but explicitly tells Core users to replace the --org and --cluster flags with --address, pointing to the local Core service on port 17080. Use the exact endpoint command in the linked prerequisites section. [S001]

Operational status is part of integration

The bridge documents enabled, disabled and faulted states, command rejection while disabled/faulted, and a recovery path through driver services. Those behaviors are software contracts to verify with the selected controller; they are not evidence of certified physical safety or a tested recovery sequence here. [S001]

The reviewed source is a commit snapshot with no stable release found. Its root license is Apache-2.0; vendor dependencies have separate scope. We have not built the container, connected a controller or measured timing. [S002] [S090]