FoundryNet / Fields / robot.mode
Canonical field reference

robot.mode

Operating mode of a robot controller, normalized to a fixed enumeration. The underlying values are the least standardised thing in robotics telemetry — integers, vendor strings, and bit fields all describe the same five states. Normalizing the enumeration is what lets one alerting rule cover a mixed fleet.

12OEMs / profiles mapped
12distinct raw spellings
12corpus source tags
1.00match confidence
Get an API key All canonical fields

Vendor tag table

How 12 vendors spell robot.mode

Each of these is a real tag as the device or controller emits it, taken from the Forge mapping corpus. This is the table that does not exist anywhere else — the reason cross-vendor telemetry is hard is visible in a single column.

OEM / profileRaw tag as the device emits itConfidence
ABB RoboticsOpMode1.00
Doosan Roboticsop_mode1.00
Epson Robotsop_mode1.00
Fanuc RoboticsUOP_mode1.00
Franka Emikaop_mode1.00
KUKA$PRO_MODE1.00
Kawasaki Roboticsop_mode1.00
Omron Roboticsop_mode1.00
Stäubliop_mode1.00
Techman Robotop_mode1.00
Universal Robotsrobot_mode1.00
Yaskawa Motomanplay_mode1.00

Every row above is an exact match — a deterministic pack entry or a confirmed corpus mapping — so all of them carry confidence 1.00. That is not a rounding: these are the two exact-match layers, and a tag that resolves here never reaches the embedding or LLM layers. Mappings resolved by the LLM layer do carry sub-1.0 confidence, but those are per-tenant and are not published here.


Unit contract

What Forge guarantees about the value

The canonical field is not just a name. It is a contract about units, sign convention and plausible range, enforced on the way in and re-checked at read time.

SI / canonical unitunitless (identifier or enumeration)
Canonical valuesrunning idle stopped error unknown
Measurement typeinstantaneous
Distinct source tags in the corpus12

Normalization

Raw tag in, canonical field out

# ABB Robotics emits its own spelling; Forge returns the canonical field
curl -s -X POST https://forge.foundrynet.io/v1/normalize \
-H "Authorization: Bearer $FORGE_KEY" \
-H "Content-Type: application/json" \
-d '{"data": {"OpMode": 0}, "oem": "abb"}'
{ "normalized": { "robot.mode": 0 }, "match_type": "deterministic", "confidence": 1.0 }

No mapping table to maintain, and no per-vendor branch in your code. The same request shape works for every OEM in the table above.

# Same thing with no key and no account — the sandbox ships the packs
docker run -p 8000:8000 ghcr.io/foundrynet/forge-sandbox

Where this field appears

Protocols

Transports this field is carried on in the corpus.

OPC UA ROS 2 (DDS) EtherNet/IP Modbus TCP

OEMs that map this field

ABB Robotics KUKA Universal Robots Fanuc Robotics Yaskawa Motoman Kawasaki Robotics Stäubli Franka Emika Omron Robotics Techman Robot Epson Robots Doosan Robotics
Every one of these tag names is someone’s integration project. The Machine Agent, weekly. Read it →
Get the thesis behind this infrastructure — The Machine Agent, weekly.