Machines
Industrial machines, AMRs and AGVs, drones, vehicles, construction and agricultural machines, reached over the buses they already speak.
Read first, then act through the gate.
A machine on a site runs on a controller and a bus. Ipnops reads it observe-only, signs what it reads, and admits readings into the machine's twin. Setpoints go back only after the twin and the declared purpose check them, inside limits, with approval.
The route.
Each bus has an adapter that decodes with a declared set of channels, each with a kind, a unit, a range and a rate.
OPC UA variables browsed, read and subscribed; never written, never called.
EtherCAT process data tapped passively; SocketCAN signals received and decoded by declared bit position.
Modbus read functions only; MQTT topics subscribed.
OPC UA, EtherCAT, SocketCAN, Modbus and MQTT, each run against a software counterpart of its bus.
SupportedProcess machine, pump and valve system, mobile platform, articulated robot.
SupportedA derived signal from one torque and one angular velocity of the same shaft.
SupportedMagnitude, rate, acceleration and duration limits; every command expires.
SupportedObserve-only, shadow, approved, per tenant and system class; approved actuation runs for a test tenant.
Supported
Delivered per deployment.
Scoped with your machines, buses, sites and approval policy.
Attaching an adapter to a controller, drive or vehicle on your site.
Available on requestRoutes over the vehicle bus and message broker.
Available on requestAMR and AGV fleets over robot middleware.
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.