Every bus, middleware and engine a machine already speaks.
Six observe-only bus adapters and a sensor-pipeline record sink bring machines in through the buses and middleware a site already runs. They are tested against software counterparts of their buses; attaching to your machine is available on request. Open formats and standard interfaces connect them to living worlds, to NVIDIA's simulation tools, to Unreal Engine and other engines, and to ROS 2 and other vendors. Each integration is delivered per deployment.
Seven integrations that read a machine where it is.
Each adapter decodes what a bus carries and signs it. None can send. Readings enter the interface graded, and commands leave only through the command gate.
Robot graphs read through a subscribe-only bridge; bags in and out.
SupportedController variables browsed, read and subscribed.
SupportedDrive process data tapped passively.
SupportedBroker topics subscribed.
SupportedVehicle and machine bus signals received.
SupportedMeter, drive and controller registers read.
SupportedNumbers from a GPU sensor pipeline arrive through a one-way record sink.
Supported
Open formats and standard interfaces to everything else.
Ipnops exchanges scenes, policies, datasets and readings in formats any tool can read, so it sits beside the tools a team already uses. Vendor and project names say what is compatible. They are not partnerships.
Scenes and twins exchange as USD stages with any tool that reads them.
SupportedPhysics solvers and a scene tool that run in the same runtimes.
SupportedSimulation-ready OpenUSD assets: browse, accept the licence, import with checks.
Supported
One page for each family.
How Ipnops connects to each family of tools, what it reads, and which way the data flows.
The tools a design is made in, and the formats it leaves in.
Early access
Observe first. Act through the gate.
Every adapter starts observe-only. Readings take one path in; commands take one path out.
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.
OPC UA · industrial serverSupported
- Data path
- Variables of a controller's information model, in.
- Mechanism
- The adapter browses, reads and subscribes. It never writes and never calls a method. Run against an independent OPC UA server.
- 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.
EtherCAT · motion busSupported
- Data path
- Process data of the drives on a segment, in.
- Mechanism
- A passive tap reads drive-profile measured values and status words and sends nothing back. Run on a virtual link carrying the frames of a classic capture.
- 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.
MQTT · message brokerSupported
- Data path
- Scalar values published on a broker's topics, in.
- Mechanism
- The adapter subscribes and never publishes. Run against a Mosquitto broker whose log showed only subscriptions.
- 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.
SocketCAN · vehicle busSupported
- Data path
- Signals in the frames of a vehicle or machine bus, in.
- Mechanism
- Receive-only, decoded by declared bit position. Run on the kernel's virtual CAN interface; a monitor on the bus saw no frame from it.
- 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.
Modbus · register deviceSupported
- Data path
- Registers and coils of meters, drives and controllers, in.
- Mechanism
- Read functions only. Modbus TCP run against a live server where every request received was a read; RTU is decoded from traces.
- 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.
Sensor pipeline · record sink (NVIDIA Holoscan)Supported
- Data path
- Numbers from inertial units and estimators in a GPU sensor pipeline, in.
- Mechanism
- A record sink in the application hands values to a local Unix socket that the reader owns. The reader accepts and reads; it never answers.
- 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.
Grouped by what you connect.
Each entry is supported today.
ROS 2 graphs and bags, LeRobot datasets, URDF and MJCF robot descriptions.
SupportedOPC UA servers, Modbus devices, EtherCAT drives.
SupportedSocketCAN signal decoding by declared bit position.
SupportedMQTT brokers.
SupportedMuJoCo, Blender and Unreal Engine, and NVIDIA Isaac Lab, Newton and Warp.
SupportedONNX policy export, RF-DETR perception on ONNX Runtime and motion planning, with GR00T, Cosmos and other world and policy models served in runtimes.
SupportedSimulation-ready OpenUSD assets, including NVIDIA SimReady Central, imported behind a licence gate.
SupportedOpenUSD, glTF and splats, MCAP, rosbag, Parquet, and Blender's FBX, OBJ, STL and Alembic.
SupportedPasskeys through WebAuthn, TPM 2.0 attestation grades, signed readings and policies.
SupportedREST API, MCP, and an open SDK client and body viewer under Apache-2.0.
SupportedRootless GPU containers and isolated microVM silos.
SupportedDelivered per deployment.
Anything that depends on your machines, buses or site is scoped with you: the adapter, the twin, the limits and the approval policy.
Attaching an adapter to a real controller, drive, vehicle or robot on your site.
Available on requestDevice run of boot measurement, attestation and sensor-bridge paths on embedded compute modules.
Available on requestPipelines, including NVIDIA Holoscan, with a hardware sensor bridge.
Available on requestTPM-backed grade on a single-board computer with a discrete TPM 2.0.
Available on requestRTX and Unreal renderers for camera tasks.
Available on requestMachine readings driving the state of an Unreal scene.
Available on requestPlacing an imported asset into a twin or world, and NVIDIA's own simready-validate profile results.
Available on requestTell us what you want to connect.
Name the machine, bus or program. We scope the adapter, the twin and the approval path with you.