FoundryNet / Fields / feed_rate
Canonical field reference

feed_rate

Actual axis feed rate along the programmed path. The richest unit problem in the corpus: the same physical quantity arrives as mm/min, in/min, mm/s, m/s, ft/min and ft/s, and vendors frequently encode the unit in the tag name rather than in a unit field. Getting this wrong is a 25.4x error that looks entirely plausible on a chart.

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

Vendor tag table

How 6 vendors spell feed_rate

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
FanucACTFEED
F SPEED
ACT_FEED
Act Feed
FSPEED_ipm
frate(ipm)
+44 more spellings
1.00
SiemensfeedRateact
feedRate act
Vorschub(ipr)
vorschub(ipm)
Vorschub_m/min
vorschub [ipr]
+25 more spellings
1.00
HaasF Rate_ipm
F_Rate_ipr
F Rate(ipm)
F Rate(ipr)
F Rate (ipm)
F_RATE (ipr)
+5 more spellings
1.00
DMG MoriFeedActual1.00
HeidenhainfeedActual1.00
Makinofeed_act1.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/min
Accepted input unitsft/min ft/s in/min m/min m/s mm/min mm/s
Converted on ingestft/min ft/s in/min m/min m/s mm/s → mm/min
Physics bounds-10000000.0 to 10000000.0 mm/min
Measurement typeinstantaneous
Distinct source tags in the corpus215

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": {"ACTFEED": 0}, "oem": "fanuc"}'
{ "normalized": { "feed_rate": 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.

MTConnect OPC UA

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.