AC line current. Reported per phase, as an average, or as a total depending on the device, and SunSpec-family devices additionally carry a scale factor register that must be applied before the value means anything.
AC line current.
line_current_aEach 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 |
|---|---|---|
| Schneider | I_AvgI_Avg_AAmps_AvgCurrent_AvgLineCurrent | 1.00 |
| SunSpec 101 | AI_ACACCurrentAC_Current | 1.00 |
| SunSpec 103 | AI_ACACCurrentAC_Current | 1.00 |
| SunSpec 201/202 | AI_ACACCurrentAC_Current | 1.00 |
| SunSpec 203/204 | AI_ACACCurrentAC_Current | 1.00 |
| Fronius | AAC_Current | 1.00 |
| SolarEdge (inverter) | I_AC_Current | 1.00 |
| SolarEdge (meter) | M_AC_Current | 1.00 |
| Sungrow | Phase A current | 1.00 |
| Victron | /Ac/Grid/L1/Current | 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 | A |
| Accepted input units | A |
| Physics bounds | 0.0 to 10000.0 A |
| Measurement type | instantaneous |
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.
Read alongside this one.
line_voltage_v spindle_speed_rpm spindle_load_pct program_name part_count