FoundryNet / OEMs / Omron AMR (LD/HD)

AUTONOMOUS MOBILE ROBOT · CANONICAL DATA MODEL

Omron AMR (LD/HD) canonical data model: connect your Omron AMR (LD/HD) equipment to any AI agent

2,086 mappings·19 verticals·13 protocols

Forge turns raw Omron AMR (LD/HD) tags into one clean, governed schema your AI agent already understands. One MCP call, no per-AMR integration project.

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

Paste your Omron AMR (LD/HD) data and see it normalized in 30 seconds. No POC required.

Read-only. Forge reads your Omron AMR (LD/HD) data through standard industrial protocols. Read-only. Your equipment is never at risk.

The problem

Why Omron AMR (LD/HD) data is hard to integrate

Fleet state (battery, pose, velocity, e-stop) is published over ROS 2 topics or a proprietary REST fleet API, and no two vendors agree on the topic names.

Typical Omron AMR (LD/HD) equipment communicates over ROS 2 (DDS), HTTP / REST, MQTT Sparkplug B. 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 Omron AMR (LD/HD) AMR

Forge resolves Omron AMR (LD/HD) telemetry into Forge's canonical field set, the same 985 canonical fields defined, used across 45 vendor packs. Point Forge at the AMR, pass oem: "omron", and spindle speed is spindle_speed_rpm whether it came from a Omron AMR (LD/HD) controller or anything else on the floor.

ROS 2 (DDS)HTTP / RESTMQTT Sparkplug B

45OEM packs in production

10Canonical autonomous mobile robot fields

2,086Mappings in production

Field coverage

What Forge resolves for Omron AMR (LD/HD)

Confirmed canonical fields your agent gets from Omron AMR (LD/HD) AMRs, drawn from Forge's 2,086-mapping corpus:

amr.battery.chargeamr.battery.voltageamr.battery.chargingamr.position.xamr.position.yamr.position.thetaamr.velocity.linearamr.velocity.angularamr.operating_modeamr.safety.estop

Sample normalization

Raw tag in		Canonical field out	Meaning
battery_pct: 76	→	amr.battery.charge: 76	battery %
pose_x: 5.2	→	amr.position.x: 5.2	pose X
lin_vel: 0.9	→	amr.velocity.linear: 0.9	linear velocity
mode: "MOVING"	→	amr.operating_mode: "MOVING"	operating mode

30-second deployment

Add Omron AMR (LD/HD) to your agent with one call

No SDK, no per-tag mapping, no historian project. Connect the MCP server and normalize live Omron AMR (LD/HD) data:

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

# normalize raw Omron AMR (LD/HD) telemetry into the universal schema

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

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

-d '{"data": {"battery_pct": 76, "pose_x": 5.2, "lin_vel": 0.9}, "oem": "omron"}'

{"amr.battery.charge": 76, "amr.position.x": 5.2, "amr.velocity.linear": 0.9, "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 Omron AMR (LD/HD) fits

Protocols
ROS 2 (DDS) HTTP / REST MQTT Sparkplug B

Vertical
autonomous mobile robot

Other autonomous mobile robot vendors
MiR (Mobile Industrial Robots) OTTO Motors 6 River Systems AGILOX Fetch Robotics Geek+ (Geekplus)

Same protocols, other industries
ABB Robotics KUKA Universal Robots Fanuc Robotics

Also searched as omron amr, omron_amr, ld-90, adept mobilerobots