INDUSTRIAL ROBOT · TELEMETRY NORMALIZATION
16,908 confirmed mappings·18 OEM families·14 protocols·91% field coverage
Forge turns raw Stäubli tags into one clean, governed schema your AI agent already understands. One MCP call, no per-robot integration project.
Joint angles, TCP pose, payload and safety bits are buried behind vendor-specific system variables and controller SDKs, so a single robot cell can take weeks to expose over a common schema.
Typical Stäubli equipment communicates over OPC UA, ROS 2 (DDS), PROFINET / S7. Each firmware revision, model line and integrator names the same physical quantity differently, so every AI or analytics project pays the integration tax again, the tax that cancels 40% of industrial AI deployments before they ship.
Forge normalizes Stäubli telemetry into Forge's canonical field set, the same 366 canonical fields used across all 18 manufacturers. Point Forge at the robot, pass oem: "staubli", and spindle speed is spindle_speed_rpm whether it came from a Stäubli controller or anything else on the floor.
Confirmed canonical fields your agent gets from Stäubli robots, drawn from Forge's 16,908-mapping corpus:
| Raw tag in | Canonical field out | Meaning | |
|---|---|---|---|
| joint_1_deg: 37.4 | → | robot.joint.position: 37.4 | joint 1 angle |
| tcp_speed: 250 | → | robot.tcp.speed: 250 | TCP speed |
| payload_kg: 7.5 | → | robot.payload: 7.5 | payload |
| op_mode: "AUTO" | → | robot.mode: "AUTO" | operating mode |
No SDK, no per-tag mapping, no historian project. Connect the MCP server and normalize live Stäubli data:
Unknown tags never get force-mapped. Fields below the confidence floor abstain rather than guess, so your agent never acts on a bad reading.