Robotics
Humanoids, mobile manipulators, quadrupeds and arms. An agent trained in a living world is born into the body through the Ipnops interface, controlled through its twin.
Born into the body.
You train a policy in a living world and need to move it to a robot without rewriting the stack. Ipnops connects the policy to the body through a twin: the policy proposes, the twin checks, the gate approves, and the robot's own controller stays in charge of its safety.
The route.
Joint states, inertial and odometry fields come in through robot middleware; trajectories, setpoints and mode changes go out through the gate.
ROS 2 graphs read through a subscribe-only bridge; rosbag2 files and MCAP in and out.
EtherCAT drive process data tapped passively.
Position, velocity, torque and force are kinds with units and ranges; a band in one unit is never read in the other.
Observe-only, run against rosbridge on a ROS 2 install.
SupportedTraining tasks, policy inference and motion plans written as MCAP, with compatible tools such as NVIDIA Isaac Lab, GR00T and cuRobo.
SupportedLeRobot datasets and URDF and MJCF robot descriptions.
SupportedShadow and approved actuation for a test tenant.
Supported
Delivered per deployment.
Scoped with your machines, buses, sites and approval policy.
Attaching the adapter and the twin to a robot on your site.
Available on requestDevice runs of boot measurement and attestation.
Available on requestWhole-body control policies, including NVIDIA's.
Available on requestTell us what you want to connect.
Name the machine, bus or program. We scope the twin, the integration and the approval path with you.