FoundryNet / OEMs / Universal Robots

INDUSTRIAL ROBOT · CANONICAL DATA MODEL

Universal Robots canonical data model: connect your Universal Robots equipment to any AI agent

2,461 confirmed mappings·12 protocols·99% field coverage

Forge turns raw Universal Robots tags into one clean, governed schema your AI agent already understands. One MCP call, no per-robot integration project.

Try it free: 3 machines, no credit card → See it work →

Paste your Universal Robots data and see it normalized in 30 seconds. No POC required.

Read-only. Forge reads your Universal Robots data through standard industrial protocols. Read-only. Your equipment is never at risk.

The problem

Why Universal Robots data is hard to integrate

UR cobots stream through RTDE and ROS 2 as indexed arrays (actual_q_0, joint_temperatures_0) where position and temperature are just array offsets until they're named.

Typical Universal Robots equipment communicates over ROS 2 (DDS), Modbus TCP, OPC UA, HTTP / REST. 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.

The solution

One universal schema for every Universal Robots robot

Forge resolves Universal Robots telemetry into Forge's canonical field set, the same 1,027-field canonical schema (366 resolvable from vendor tags today), used across all 47 vendor packs. Point Forge at the robot, pass oem: "universal", and spindle speed is spindle_speed_rpm whether it came from a Universal Robots controller or anything else on the floor.

ROS 2 (DDS)Modbus TCPOPC UAHTTP / REST

99%Field coverage

11Canonical industrial robot fields

3,444Corpus mappings

Field coverage

What Forge resolves for Universal Robots

Confirmed canonical fields your agent gets from Universal Robots robots, drawn from Forge's 3,444-mapping corpus:

robot.joint.positionrobot.joint.velocityrobot.joint.effortrobot.joint.currentrobot.joint.temperaturerobot.tcp.poserobot.tcp.speedrobot.tcp.forcerobot.payloadrobot.moderobot.safety.status_bits

Sample normalization

Raw tag in		Canonical field out	Meaning
actual_q_0: 1.57	→	robot.joint.position: 1.57	base joint (rad)
joint_temperatures_0: 44	→	robot.joint.temperature: 44	base joint temp
robot_mode: 7	→	robot.mode: "RUNNING"	RTDE robot_mode 7
tcp_force_0: 12.1	→	robot.tcp.force: 12.1	TCP force X

30-second deployment

Add Universal Robots to your agent with one call

No SDK, no per-tag mapping, no historian project. Connect the MCP server and normalize live Universal Robots data:

claude mcp add --transport http forge https://mcp.foundrynet.io/mcp --header 'Authorization: Bearer YOUR_API_KEY'

# normalize raw Universal Robots telemetry into the universal schema

curl -s https://forge.foundrynet.io/v1/normalize \

-H 'Content-Type: application/json' \

-d '{"data": {"actual_q_0": 1.57, "joint_temperatures_0": 44, "robot_mode": 7}, "oem": "universal"}'

{"robot.joint.position": 1.57, "robot.joint.temperature": 44, "robot.mode": "RUNNING", "coverage": "100%", "confidence": 0.97}

Unknown tags never get force-mapped. Fields below the confidence floor abstain rather than guess, so your agent never acts on a bad reading.

Start free: Forge API, 3 machines → See the full demo →

Where Universal Robots fits

Protocols
ROS 2 (DDS) Modbus TCP OPC UA HTTP / REST

Vertical
industrial robot

Other industrial robot vendors
ABB Robotics KUKA Fanuc Robotics Yaskawa Motoman Doosan Robotics Epson Robots

Same protocols, other industries
MiR (Mobile Industrial Robots) OTTO Motors 6 River Systems AGILOX

Also searched as universal robots, universal_robots, ur, ur5, ur10, ur3, cobot