FoundryNet / Fields / axes.0.position_actual
Canonical field reference

axes.0.position_actual

Actual position of the first linear axis, in millimetres. Indexed rather than lettered because axis naming is not portable: what one controller calls X another calls axis 1, and a lathe's first axis is not a mill's. The letter form is preserved alongside as axes.x_position_actual where the source provides it.

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

Vendor tag table

How 3 vendors spell axes.0.position_actual

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
FanucAbs X
xabs_m
Xabs(m)
Abs X_in
abs_x_in
abs_x_mm
+22 more spellings
1.00
SiemensXIst_m
XIst(in)
XIst(mm)
X Ist [m]
XIst [mm]
X Ist [in]
+14 more spellings
1.00
HaasX WORK_m
XWORK_in
Xpos (m)
XPOS (mm)
XWORK [m]
X Mach Pos
+11 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.


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 unitmm
Accepted input unitscm ft in m mil mm um
Converted on ingestcm ft in m mil um → mm
Physics bounds-100000.0 to 100000.0 mm
Measurement typeinstantaneous
Distinct source tags in the corpus232

Normalization

Raw tag in, canonical field out

# Fanuc 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": {"Abs X": 0}, "oem": "fanuc"}'
{ "normalized": { "axes.0.position_actual": 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.

OEMs that map this field

Fanuc Haas Siemens Sinumerik DMG Mori Mazak Okuma Heidenhain Makino Mitsubishi Brother Hurco Doosan Trumpf Bridgeport Hitachi Seiki Kitamura Komatsu NTC Matsuura Mikron Tongtai Tormach
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.