Compatible with ROS 2 and the robot formats.

A robot that speaks ROS 2 can be read in place. Ipnops subscribes to its graph, signs what it reads and brings it into the robot's twin, and exchanges bags, robot descriptions and datasets in open formats. ROS and Open Robotics are named to describe what works together; this is not an endorsement.

Supported · read-only bridge, open formats Request access All integrations
01What it reads

Robot graphs, bags and datasets.

Each connection is read-only until a person approves otherwise, and every reading is signed and graded before the interface admits it.

ROS 2 graphs

Joint states, inertial and odometry fields of a robot graph, read through a subscribe-only bridge.

Supported
Bags

rosbag2 files in MCAP and SQLite, and ROS 1 bags, read in; trajectories written out as MCAP.

Supported
Robot descriptions

URDF and MJCF robot descriptions.

Supported
Datasets

LeRobot datasets, converted in both directions.

Supported
Policies out

Learned policies leave as ONNX for the machine's own stack. A policy reaches a machine only through the command gate.

Supported
02How each connects

Data path, mechanism, trust path.

What goes in, how the adapter reads it, and why it can be trusted.

ROS 2 · robot middlewareSupported
Data path
Joint states, inertial and odometry fields of a robot graph, in.
Mechanism
A subscribe-only bridge (rosbridge) reads topics; only subscribe and unsubscribe are ever sent. rosbag2 files (MCAP and SQLite) and ROS 1 bags read in; trajectories write out as MCAP.
Trust path
Readings are signed at the node, graded by the weakest link, and admitted into the twin only inside its solved band. Commands leave only through the command gate, after the purpose check and, where the level requires it, a person's approval.
03How it connects
Data path

Out of the robot: topic values and bags. Out of Ipnops: trajectories as MCAP and policies as ONNX, behind the gate.

Mechanism

The bridge only subscribes and unsubscribes. Nothing in the adapter can publish to the robot's graph.

Trust path

A recorded trajectory is a proposal for review, not a command.

04Available on request
Your robot

Attaching the adapter and the twin to a robot on your site.

Available on request

Bring a robot.

Tell us the robot, its middleware and its limits. We scope the adapter, the twin and the approval path with you.