Load on the first linear axis as a percentage of rated. Rising axis load at constant cutting conditions is a way guide or ballscrew problem, and it shows up here long before it shows up in part quality.
axes.0.load_percentEach 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 |
|---|---|---|
| Siemens | XTORQUEPCTdriveLoadXX ServoLoaddriveLoadX(%)XTORQUEPCT [%]XTORQUEPCT_pct+25 more spellings | 1.00 |
| Fanuc | SV1LOADXSRVLOADSv1Load(%)SRVLOAD1(%)SV1LOAD_pctXSRVLOAD(%)+18 more spellings | 1.00 |
| Haas | x loadXLOAD (%)XLOAD_pctx load(%)X LOAD (%)X Load [%]+8 more spellings | 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.0 to 100.0 % |
| Measurement type | instantaneous |
| Distinct source tags in the corpus | 215 |
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.
—Read alongside this one.
axes.0.position_actual axes.0.temperature_c spindle_speed_rpm spindle_load_pct program_name