Line-to-line AC voltage. Meters and inverters disagree about whether they report line-to-line or line-to-neutral under a generic Voltage tag, and the two differ by a factor of 1.732 — large enough to matter, small enough to look like a calibration issue rather than a mapping error.
Line-to-line AC voltage.
line_voltage_vEach 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 | V_LLVLL_AvgVln_avgV_LL_AvgVoltage_LLLineVoltage | 1.00 |
| Fronius | PhVphAPPVphABAC_Voltage | 1.00 |
| SolarEdge (inverter) | I_AC_VoltageABI_AC_VoltageAN | 1.00 |
| SolarEdge (meter) | M_AC_Voltage_LLM_AC_Voltage_LN | 1.00 |
| SunSpec 101 | PhVphA | 1.00 |
| SunSpec 103 | PPVphAB | 1.00 |
| SunSpec 201/202 | PhV | 1.00 |
| SunSpec 203/204 | PPV | 1.00 |
| Sungrow | Phase A voltage | 1.00 |
| Victron | /Ac/Grid/L1/Voltage | 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 | V |
| Accepted input units | V |
| Physics bounds | 0.0 to 1000.0 V |
| 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_current_a spindle_speed_rpm spindle_load_pct program_name part_count