AC line frequency. Bounded tightly — 45 to 65 Hz — because anything outside that band is a scaling error or a sentinel value rather than a grid event. The narrow band is what makes this field a useful canary for a misapplied SunSpec scale factor elsewhere in the same payload.
AC line frequency.
grid_frequency_hzEach 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 |
|---|---|---|
| Fronius | HzF_ACFreqFrequencyAC_Frequency | 1.00 |
| SunSpec 101 | HzF_ACFreqFrequencyAC_Frequency | 1.00 |
| SunSpec 103 | HzF_ACFreqFrequencyAC_Frequency | 1.00 |
| SunSpec 201/202 | HzF_ACFreqFrequencyAC_Frequency | 1.00 |
| SunSpec 203/204 | HzF_ACFreqFrequencyAC_Frequency | 1.00 |
| Schneider | FreqFreq_HzFreq_avgFrequency | 1.00 |
| Victron | Grid/Frequency/Ac/Grid/L1/Frequency | 1.00 |
| SolarEdge (inverter) | I_AC_Frequency | 1.00 |
| SolarEdge (meter) | M_AC_Freq | 1.00 |
| Sungrow | Grid frequency | 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 | Hz |
| Accepted input units | Hz |
| Physics bounds | 45.0 to 65.0 Hz |
| 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.
spindle_speed_rpm spindle_load_pct program_name part_count feed_rate