State of charge for an autonomous mobile robot, as a percentage. Bounded 0 to 100, which catches the common case of a source reporting a 0-to-1 fraction that would otherwise render as a permanently flat battery.
amr.battery.chargeEach 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 |
|---|---|---|
| 6 River Systems | battery_pct | 1.00 |
| AGILOX | battery_pct | 1.00 |
| Fetch Robotics | battery_pct | 1.00 |
| Geek+ (Geekplus) | battery_pct | 1.00 |
| Locus Robotics | battery_pct | 1.00 |
| MiR (Mobile Industrial Robots) | /robot_status/battery_percentage | 1.00 |
| OTTO Motors | battery_soc | 1.00 |
| Omron AMR (LD/HD) | battery_pct | 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 | % |
| Accepted input units | % |
| Physics bounds | 0 to 100 % |
| Measurement type | instantaneous |
| Distinct source tags in the corpus | 6 |
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.
Read alongside this one.
amr.operating_mode amr.position.x spindle_speed_rpm spindle_load_pct program_name