FoundryNet / OEMs / Doosan Robotics

INDUSTRIAL ROBOT · CANONICAL DATA MODEL

Doosan Robotics canonical data model: connect your Doosan Robotics equipment to any AI agent

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

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

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

The problem

Why Doosan Robotics 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 Doosan Robotics equipment communicates over ROS 2 (DDS), Modbus TCP, EtherNet/IP. 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 Doosan Robotics robot

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

ROS 2 (DDS)Modbus TCPEtherNet/IP

91%Field coverage

11Canonical industrial robot fields

3,444Corpus mappings

Field coverage

What Forge resolves for Doosan Robotics

Confirmed canonical fields your agent gets from Doosan Robotics 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
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

30-second deployment

Add Doosan Robotics to your agent with one call

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

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

# normalize raw Doosan Robotics telemetry into the universal schema

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

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

-d '{"data": {"joint_1_deg": 37.4, "tcp_speed": 250, "payload_kg": 7.5}, "oem": "doosan"}'

{"robot.joint.position": 37.4, "robot.tcp.speed": 250, "robot.payload": 7.5, "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 Doosan Robotics fits

Protocols
ROS 2 (DDS) Modbus TCP EtherNet/IP

Vertical
industrial robot

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

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

Also searched as doosan robotics, doosan_robotics, m0609, a0509