FoundryNet / OEMs / Yaskawa Motoman

INDUSTRIAL ROBOT · CANONICAL DATA MODEL

Yaskawa Motoman canonical data model: connect your Yaskawa Motoman equipment to any AI agent

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

Forge turns raw Yaskawa Motoman 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 Yaskawa Motoman data and see it normalized in 30 seconds. No POC required.

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

The problem

Why Yaskawa Motoman data is hard to integrate

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 Yaskawa Motoman equipment communicates over EtherNet/IP, ROS 2 (DDS), MTConnect. 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 Yaskawa Motoman robot

Forge resolves Yaskawa Motoman 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: "yaskawa", and spindle speed is spindle_speed_rpm whether it came from a Yaskawa Motoman controller or anything else on the floor.

EtherNet/IPROS 2 (DDS)MTConnect

95%Field coverage

11Canonical industrial robot fields

3,444Corpus mappings

Field coverage

What Forge resolves for Yaskawa Motoman

Confirmed canonical fields your agent gets from Yaskawa Motoman 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
S_axis_deg: 45.0	→	robot.joint.position: 45.0	S-axis angle
tool_load: 8.5	→	robot.payload: 8.5	tool load
play_mode: "AUTO"	→	robot.mode: "AUTO"	play mode

30-second deployment

Add Yaskawa Motoman to your agent with one call

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

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

# normalize raw Yaskawa Motoman telemetry into the universal schema

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

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

-d '{"data": {"S_axis_deg": 45.0, "tool_load": 8.5, "play_mode": "AUTO"}, "oem": "yaskawa"}'

{"robot.joint.position": 45.0, "robot.payload": 8.5, "robot.mode": "AUTO", "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 Yaskawa Motoman fits

Protocols
EtherNet/IP ROS 2 (DDS) MTConnect

Vertical
industrial robot

Other industrial robot vendors
ABB Robotics KUKA Universal Robots Fanuc Robotics Doosan Robotics Epson Robots

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

Also searched as yaskawa, motoman, yaskawa_motoman, yrc1000, dx200