FoundryNet / Fields / spindle_load_pct
Canonical field reference

spindle_load_pct

Spindle motor load as a percentage of rated continuous torque. The workhorse signal for tool-wear and crash detection: a climbing load trend at constant feed and speed is a dulling tool, and a step change is a collision. Vendors report it as a percentage, a per-unit ratio, or a raw torque value that has to be scaled by the drive rating — the normalizer resolves all three to a percentage.

21OEMs / profiles mapped
116distinct raw spellings
255corpus source tags
1.00match confidence
Get an API key All canonical fields

Vendor tag table

How 21 vendors spell spindle_load_pct

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
SiemensSPTORQUEPCT
SPTORQUEPCT_%
SP_TORQUE_PCT
SPTORQUEPCT(%)
SPTORQUEPCT (%)
SPTORQUEPCT [%]
+35 more spellings
1.00
FanucSP LOAD
Sp_Load
SPLOAD_%
SPLOAD(%)
Sp_Load_%
SP LOAD(%)
+15 more spellings
1.00
HaasSPLOADPCT
SPLOADPCT(%)
SPLOADPCT (%)
SPLOADPCT [%]
SP_LOAD_PCT_%
SP LOAD PCT(%)
+15 more spellings
1.00
Bridgeportsp_load_pct1.00
Brothersp_load_pct1.00
DMG MoriSpindleLoad1.00
Doosansp_load_pct1.00
HeidenhainspindleLoadPct1.00
Hitachi Seikisp_load_pct1.00
Hurcosp_load_pct1.00
Kitamurasp_load_pct1.00
Komatsu NTCsp_load_pct1.00
Makinosp_load1.00
Matsuurasp_load_pct1.00
MazakSload1.00
Mikronsp_load_pct1.00
Mitsubishisp_load_pct1.00
OkumaSpLoadPct1.00
Siemens SinumerikdriveLoad1.00
Tongtaisp_load_pct1.00
Tormachsp_load_pct1.00
Trumpfsp_load_pct1.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 unit%
Accepted input units%
Physics bounds0.0 to 100.0 %
Measurement typeinstantaneous
Distinct source tags in the corpus255

Normalization

Raw tag in, canonical field out

# Siemens 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": {"SPTORQUEPCT": 0}, "oem": "siemens"}'
{ "normalized": { "spindle_load_pct": 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

Related fields

Read alongside this one.

spindle_speed_rpm program_name part_count feed_rate robot.joint.position

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.