FFR
Fast Frequency Response, implemented as a mode alias of FREQUENCY_REGULATION.
| Mode string | FFR (EMS_OP_FFR) |
| Dispatcher | Separate process, started/stopped by ems_main.py |
| Controller | ems_frequency_regulation_direct_modbus_v4.py |
| Config block | functions.Frequency_Regulation (shared) |
| Status | Implemented (alias) |
Behaviour
FFR is dispatched exactly like FREQUENCY_REGULATION. ems_main.py starts the same fast controller
process for either mode:
if mode in (EMS_OP_FREQUENCY_REGULATION, EMS_OP_FFR):
freq_reg.start()
The dispatch chain then does the same thing for both: it maintains the loop interval and continues,
so no 2 Hz control step runs while FFR is selected. The droop curve, deadband, participation and ramp
behaviour are described in frequency-regulation.md.
Why an alias and not a separate mode
The fast controller already declares FFR as an accepted alias in its own mode gate:
if mode and mode not in ("FREQUENCY_REGULATION", "FREQUENCY_REG", "FFR"):
...
So the controller was already capable of running under FFR — nothing was launching it. Adding a
second implementation would have duplicated the droop logic for no benefit.
Configuration
FFR has no config block of its own; it reads functions.Frequency_Regulation. All blocking items
listed on the Frequency Regulation page therefore apply here too —
notably droop_pct being null, which makes the controller compute 0 kW regardless of frequency.
When you would want a distinct mode
Split FFR into its own functions.FFR block and dispatch branch if it must differ from generic
frequency regulation — for example a faster response requirement, a different deadband, a separate
SOC policy, or a distinct compliance envelope for prequalification. Until then, the alias is the
correct implementation and avoids two sources of truth.
Related
- FREQUENCY_REGULATION — the implementation FFR aliases.