FoundryNet / Fields / active_power_kw
Canonical field reference

active_power_kw

Total AC active power, signed with export negative. The sign convention is the whole difficulty: half the devices in the corpus report export as positive, and a fleet mixing both conventions produces a site total that is quietly wrong rather than obviously broken.

Total AC active power. Signed: export is negative.

7OEMs / profiles mapped
34distinct raw spellings
1.00match confidence
Get an API key All canonical fields

Vendor tag table

How 7 vendors spell active_power_kw

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
SunSpec 124/802W
AC_W
P_AC
Power
ACPower
AC_Power
+1 more spelling
1.00
SunSpec 201/202W
AC_W
P_AC
Power
ACPower
AC_Power
+1 more spelling
1.00
SunSpec 203/204W
AC_W
P_AC
Power
ACPower
AC_Power
+1 more spelling
1.00
SchneiderkW_Tot
P_Total
Total_kW
kW_Total
Real_Power
ActivePower
1.00
VictronGrid/Power
Battery/Power
/Ac/Grid/L1/Power
/Dc/Battery/Power
1.00
SolarEdge (meter)M_AC_Power1.00
SungrowTotal active power1.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 unitkW
Accepted input unitsMW W hp kW
Converted on ingestMW W hp → kW
Physics bounds-100000.0 to 100000.0 kW
Measurement typeinstantaneous

Normalization

Raw tag in, canonical field out

# SunSpec 124/802 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": {"W": 0}, "oem": "auto"}'
{ "normalized": { "active_power_kw": 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.

SunSpec Modbus RTU Modbus TCP

Related fields

Read alongside this one.

spindle_speed_rpm spindle_load_pct program_name part_count feed_rate
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.