Open Source RoboticsRobots, software & learning

Intrinsic SDK for ROS

Software

ROS 2 integration for Intrinsic, including workcell-state, transform and image bridges plus skill/service build tooling. [1]

Installation & first result →Official website

For
ROS developers integrating an accessible Intrinsic workcell [2]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
operating system, 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

The ROS SDK does more than package Intrinsic's client library: it implements bridges for workcell transforms, robot state, images and visualization resources, along with tooling for ROS-based skills and services. It merits a separate look when an existing ROS application needs to observe or integrate an Intrinsic workcell. It does not provide the workcell runtime by itself. [1] [2] [3]

Is this for you?

Known limitations
  • A reachable compatible Intrinsic workcell is an external prerequisite.
  • The default build downloads a Linux amd64 inbuild binary; alternate architectures require the source-build option.
  • Multiple bridges need distinct workcell identifiers to avoid frame collisions.

Editorial assessment from cited documentation; no runtime testing.

[1] [2] · Editorial assessment

What you need

Languages / runtimes
  • C++
  • Python

[1] [3]

Dependencies
  • ROS 2 Lyrical or Jazzy
  • colcon and rosdep
  • Matching Intrinsic SDK
  • rmw_zenoh for the documented LAN workflow

[1] [2] [4]

Installation & first result

  • Prepare the documented Lyrical or Jazzy workspace.
  • Build packages up to flowstate_ros_bridge.
  • Configure the workcell connection and Zenoh transport using the bridge guide.
  • Inspect topics and TF frames; assign distinct workcell_id values for multiple bridges.

Editorial assessment from cited documentation; no runtime testing.

[1] [2] · Editorial assessment

Installation

Clone the pinned revision into a ROS workspace, install rosdep dependencies and build with colcon.

Editorial assessment from cited documentation; no runtime testing.

[1] · Editorial assessment

Hardware, models & data

Inputs and outputs

Workcell state and resources become ROS transforms, joint states, force/torque messages and visualization resources.

[2] [3]

Project notes

Match the ROS and SDK build

Commit 4b195a3cb9c8473351fdad8130b89d26a0b81947 documents ROS 2 Lyrical as the default and Jazzy as an alternative. Clone it into a colcon workspace, source the selected ROS distribution, install dependencies with rosdep, then build the release configuration. The bridge guide shows a narrower build using --packages-up-to flowstate_ros_bridge. [1] [2] [6]

CMake fetches the SDK version and checksum from the packaged version metadata, then applies repository patches. The root guide says the default inbuild download is a Linux amd64 binary. For another architecture, it documents -DINTRINSIC_SDK_CMAKE_BUILD_INBUILD=ON to build that tool with Bazel. This option does not by itself establish that the entire workcell supports the alternate host. [1] [4]

The documented LAN workflow needs an accessible workcell and a Zenoh connection; the alternative bundles the bridge as a Flowstate service. Use the bridge guide to inspect published topics and TF frames. When substituting the IPC address in its sample configuration, supply the actual address: the shell example encloses $IPC_ADDRESS in single quotes, which preserves the literal variable name instead of expanding it. [2]

For multiple workcells, assign distinct, nonempty workcell_id values. Topic namespaces and frame prefixes change, but /tf and /tf_sim remain global topics. Leaving multiple bridges at the root can produce colliding frame names. Jazzy visualization additionally uses the documented HTTP mesh proxy. [2] [3]

The repository has Apache-2.0 terms, while dependency terms require separate review. This profile covers the exposed integration source and documented workflow; we have not compiled its patched SDK, connected to Flowstate or verified a particular Core release pairing. [4] [7]

What we checked

Source researched only; no installation, training, benchmark or physical hardware test performed. No affiliate links or reused media.

Not yet established

  • Requirements: operating system, host computer
  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Oct 14, 2026 [6]
Latest release
Not established
Profile updated
Oct 18, 2026
Sources last checked
Oct 18, 2026
Next review
Nov 18, 2026
Reviewed revision
commit snapshot; no stable GitHub release / 4b195a3cb9c8473351fdad8130b89d26a0b81947 · software repository

Source files and licenses

Include as a distinct implemented ROS bridge and build integration, not a thin forwarding wrapper; runtime access and version compatibility are explicitly external.

LayerAvailability / license
softwareavailable · Apache-2.0
Repository materials only; external components retain their own terms. [7]
documentationavailable · Apache-2.0
Repository materials only; external components retain their own terms. [7]

No learned weights required for the scoped software workflow.

No training dataset required for the scoped software workflow.

References

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

Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5

Change history