Tool-centre-point linear speed, in millimetres per second. Derived by some controllers and measured by others, which is worth knowing before you build a safety rule on it.
robot.tcp.speedEach 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 / profile | Raw tag as the device emits it | Confidence |
|---|---|---|
| Doosan Robotics | tcp_speed | 1.00 |
| Epson Robots | tcp_speed | 1.00 |
| Franka Emika | tcp_speed | 1.00 |
| Kawasaki Robotics | tcp_speed | 1.00 |
| Omron Robotics | tcp_speed | 1.00 |
| Stäubli | tcp_speed | 1.00 |
| Techman Robot | tcp_speed | 1.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.
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 unit | unitless (identifier or enumeration) |
| Physics bounds | 0 to 5000 |
| Measurement type | instantaneous |
| Distinct source tags in the corpus | 15 |
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.
Transports this field is carried on in the corpus.
ROS 2 (DDS) EtherNet/IP OPC UA Modbus TCPRead alongside this one.
robot.joint.position robot.mode robot.payload spindle_speed_rpm spindle_load_pct