Open Source RoboticsRobots, software & learning

ICON ROS 2 hardware-module controller

Software

Bridge that exposes position-controlled ros2_control arms as Intrinsic ICON hardware modules. [1]

Installation & first result →Official websiteGetting started

For
Developers adapting ROS 2 industrial-arm drivers to ICON [1]
Hardware
Documented Universal Robots UR3e, UR5e and UR10e examples, Documented FANUC CRX, LR Mate and M-20 family examples [1]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
compute requirements not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

This bridge lets a ros2_control arm driver appear as an Intrinsic ICON hardware module. Its JointPositionCommand input carries target joint positions and optional velocity feedforward; JointPositionState and JointVelocityState return positions and velocities. Velocity feedforward does not extend its scope to velocity-controlled arms. Its stated scope is position-controlled robotic arms: digital and analog I/O are not supported. That matters for a tending cell, where connecting the arm does not also connect the machine door, vise or other I/O. [1]

Is this for you?

Workflows
  • Package a vendor ros2_control driver as an ICON hardware module
  • Exchange joint commands, feedback and operational status

[1]

Known limitations
  • Limited to position-controlled robotic arms
  • Digital and analog I/O are not supported by this bridge

[1]

What you need

Operating system
  • Ubuntu 24.04 / ROS 2 Kilted for the documented driver environment

[1]

Dependencies
  • Docker Engine and Compose
  • Bazelisk / Bazel
  • inctl
  • A supported ros2_control arm driver

[1]

Installation & first result

Open the upstream getting-started guide [1]

  • Choose the Universal Robots or FANUC example and matching robot controller
  • Build/package the driver environment with Docker and Bazel
  • Apply the vendor-specific controller and geometry setup
  • For Core, use the documented local address in place of Enterprise org/cluster flags

[1]

Installation

Build the selected vendor example into a container and Intrinsic service/device asset; follow its controller setup and install with inctl.

[1]

Hardware, models & data

Supported hardware
  • Documented Universal Robots UR3e, UR5e and UR10e examples
  • Documented FANUC CRX, LR Mate and M-20 family examples

[1]

Inputs and outputs

ICON joint-position commands feed ros2_control hardware; joint positions, velocities and operational status return to ICON.

[1]

File formats
  • Protocol Buffers runtime configuration
  • FlatBuffers state/command streams

[1]

Project notes

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. [1]

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. [1]

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. [1]

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. [2] [90]

What we checked

Source research only. No installation, upstream test execution, physical integration or performance measurement by this publication. No affiliation or endorsement claimed.

Not yet established

  • Requirements: host computer

Updates

Upstream last updated
Sep 28, 2026 [90]
Latest release
Not established
Profile updated
Oct 4, 2026
Sources last checked
Sep 30, 2026
Next review
Oct 30, 2026
Reviewed revision
31eb6f85493b497762256f31cec6b606b747fd6e (commit snapshot; no published stable release found) · software repository

Source files and licenses

Useful open software component with documented development workflow; dependency rights, configuration matching and runtime results remain separate.

LayerAvailability / license
softwareavailable · Apache-2.0
Inspected root license for this repository. External dependencies, vendor SDKs, models and third-party geometry are not relicensed by it. [1] [2]
documentationavailable · Apache-2.0
Inspected root license for this repository. External dependencies, vendor SDKs, models and third-party geometry are not relicensed by it. [1] [2]

No particular model weights or dataset is offered or assessed by this component profile.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Project sources

Videos

  • S091 Intrinsic (YouTube channel)
    The project’s own YouTube channel, found by searching YouTube and checked against the channel page. Not reviewed by us for accuracy.
    Revision, date & where cited

    YouTube channel Intrinsic · youtube.com · Accessed Oct 4, 2026

Correction guidance · Discussion is not enabled · Profile format 0.6.0-draft.1

Change history

2026-09-30 — Initial pinned-source component profile with setup route and integration boundaries.

2026-10-04 — Added 1 YouTube reference(s) (S091): official channel or videos linked from the pinned upstream sources. Existing claims, source-check dates and evidence are unchanged.