How to Simulate Grid Conditions
Purpose
Vary grid voltage, frequency and power at the point of measurement so the EMS's measurement handling, frequency response and protection can be tested.
Prerequisites
- Simulator stack up.
- The meters are served and the EMS polls them.
The meter devices
| Device | Port | Configuration |
|---|---|---|
| Grid Meter | 1513 | emsConfig/grid_energy_meter/gridMeter_* |
| Solar Meter | 1514 | emsConfig/solar_energy_meter/solarMeter_* |
| Frequency Meter | 1515 | emsConfig/frequency_meter/frequencyMeter_* |
These three are single devices, not ranges — there is no Grid Meter 2.
Simulating each quantity
All changes go through the Config Editor (/) unless the change is
alarm-shaped, in which case use the Alarms page.
Grid voltage
- Config Editor → the grid meter → the voltage register.
- Write a value above or below the alarm limit.
- Read back to confirm, then check the EMS sees it.
- For an over/under-voltage alarm, prefer the Alarms page on the rule itself: it writes a value known to satisfy the condition.
Frequency
- Config Editor → the frequency meter (or the grid meter, whichever the rule watches) → the frequency register.
- Write a value outside the allowed band.
- Confirm the EMS reports it.
For overfrequency and underfrequency, the Watched register, Rule and Writes columns on the Alarms page tell you exactly which register to move and to what — use them instead of guessing the band.
Active and reactive power
Write the meter's power registers. As always, raw values are unsigned: a negative import/export value appears as a large number (65403 is -133). Decode against the register's declared type.
Frequency response testing
There is no automated frequency-ramp feature. A frequency-response test is:
- Record the baseline frequency and the EMS's output commands.
- Change the frequency value in steps, waiting between steps.
- At each step, read the EMS's response and the commands it issues.
- Confirm the response direction and magnitude match the requirement.
- Restore the frequency.
Because write timestamps have one-second resolution, this works for control behaviour but not for sub-second response claims.
Functions the brief asks for that are NOT implemented
| Requested | Status |
|---|---|
| Grid connection / disconnection simulation | No built-in control. No verified register or UI action that models the grid contactor. Approximate by driving the measurement values, or break the poll path |
| Automated frequency ramp | Not present — step the value manually |
| Frequency meter in the dashboard's device list | Known discrepancy. The frequency meter has a readable register map but has been observed absent from the device list the alarm-map reader enumerates (103 devices). If its alarms do not appear on the Alarms page, this is why — see Troubleshooting |
Verification
| Check | Expected |
|---|---|
| Voltage change | Read-back shows the new value; EMS view follows |
| Frequency change | Same |
| Power change | Same, with the sign decoded correctly |
| Alarm | Fires on the rule's watched register, appears on the EMS side |
| Response | EMS commands appear in the Write Monitor, on the correct port |
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Changed a meter, EMS saw nothing | The EMS polls a different device for that quantity | Find which device the rule watches |
| Frequency alarm missing | Frequency meter absent from the device enumeration | Check the device list; the alarm-map reader and the device enumerator disagree here |
| Alarm fires but no EMS action | The alarm has no actions configured | See HOW_TO_ADD_ALARM_ACTION |
| Value looks wrong | Signed value read as unsigned | Decode against the register type |