INDUSTRIAL ROBOT · TELEMETRY NORMALIZATION
16,908 confirmed mappings·18 OEM families·14 protocols·99% field coverage
Forge turns raw ABB Robotics tags into one clean, governed schema your AI agent already understands. One MCP call, no per-robot integration project.
ABB IRC5/OmniCore exposes joint angles and load through RAPID persistents and the Robot Web Services API (CJointT.rax_1, MechUnitLoad) that no agent understands without a map.
Typical ABB Robotics equipment communicates over OPC UA, EtherNet/IP, PROFINET / S7, ROS 2 (DDS). 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 ABB Robotics telemetry into Forge's canonical field set, the same 366 canonical fields used across all 18 manufacturers. Point Forge at the robot, pass oem: "abb", and spindle speed is spindle_speed_rpm whether it came from a ABB Robotics controller or anything else on the floor.
Confirmed canonical fields your agent gets from ABB Robotics robots, drawn from Forge's 16,908-mapping corpus:
| Raw tag in | Canonical field out | Meaning | |
|---|---|---|---|
| CJointT.rax_1: 42.7 | → | robot.joint.position: 42.7 | joint 1 angle (deg) |
| MechUnitLoad: 3.1 | → | robot.payload: 3.1 | mechanical unit load (kg) |
| OpMode: "AUTO" | → | robot.mode: "AUTO" | operating mode |
| MotorTemp1: 51 | → | robot.joint.temperature: 51 | axis 1 motor temp |
No SDK, no per-tag mapping, no historian project. Connect the MCP server and normalize live ABB Robotics 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.