Fault ride through (FRT) is the ability of a power park module to stay connected and keep supporting the grid while voltage collapses during a fault. In the GB Grid Code the requirement sits in ECC.6.3.15, and the reactive current during the dip in ECC.6.3.16 (fast fault current injection). A design must hold the plant on line, inject reactive current during the dip and recover active power afterwards. The check combines a short-circuit view of the retained voltage with the inverter current limit.
Short answer: what fault ride through asks of a power park module
Fault ride through (FRT) means a power park module (PPM) stays connected and useful while a network fault pulls the voltage down. In the GB Grid Code the requirement is in the European Connection Conditions, at ECC.6.3.15. The module must not trip for faults the rules say it must survive, and it must bring active power back soon after the fault clears. The reactive current it feeds during the dip is set in ECC.6.3.16, fast fault current injection. The current text is Grid Code Issue 6, Revision 46, dated 8 October 2026. The surrounding rules are in the Grid Code overview.
Why the requirement exists
A GB system with a large share of inverter-based plant loses voltage support if those plants trip during a fault. A trip removes generation at the very moment the system needs it, and a cascade can follow. FRT keeps the plant connected and lets its inverters push reactive current into the network, which helps protection operate and voltage recover. The related reactive capability rule is covered in the reactive capability guide.
What a design has to show
The two ECC clauses and the compliance processes lead to four items of evidence.
- Stay connected. The plant does not trip for dips of the depth and duration the clause sets, measured at the connection point and not at the inverter terminals.
- Inject reactive current (ECC.6.3.16). During the dip, the controls raise reactive current in proportion to the voltage deviation, within the inverter current limit.
- Recover active power. After the voltage returns, active power rises back to its pre-fault level within the time the clause allows.
- Protection does not defeat it. Plant-level and inverter protection settings must not trip the module inside the ride-through envelope. Interface protection needs particular care, because its settings must sit outside the envelope.
The plant also needs a model that shows these behaviours. The compliance side, including how simulations and tests are compared, is in the compliance processes guide. Open modifications on the Grid Code, such as proposals to clarify FRT wording, can change the text, so check the tracker for your issue date.
Worked example: retained voltage and reactive current
All values are illustrative and assumed. The reactive current gain is an assumption for the example and not a value from the clause.
Plant: a 40 MW PPM on a 132 kV bus. Work in per unit on a 100 MVA base.
- The network short-circuit level at the plant bus is 2,500 MVA. Source impedance Zs = 100 ÷ 2,500 = 0.04 per unit.
- A fault occurs on an adjacent circuit, an electrical distance of 0.06 per unit from the plant bus.
- Retained voltage at the plant bus, by voltage divider = 0.06 ÷ (0.04 + 0.06) = 0.60 per unit.
- Voltage deviation = 1.0 − 0.60 = 0.40 per unit.
- With an assumed gain of 2 per unit of reactive current for each per unit of voltage deviation, reactive current demand = 2 × 0.40 = 0.80 per unit of rated current.
- If the inverters limit total current to 1.1 per unit, active current available = √(1.1² − 0.8²) = √(1.21 − 0.64) = √0.57 = 0.755 per unit.
So in this dip the module gives 0.80 per unit of reactive current and keeps about 0.755 per unit of active current. If the same fault were closer, with retained voltage 0.30 per unit, the demand would be 2 × 0.70 = 1.4 per unit, which exceeds the 1.1 limit. The controls would then cap reactive current at 1.1 per unit and active current would fall to zero. The design must show this priority and how the module recovers afterwards.
Common design pitfalls
- Measuring at the wrong point. Retained voltage depends on where it is measured, so state the point in the design basis.
- Protection tripping inside the envelope. DC-link, phase-lock loop and overvoltage settings in the inverters can trip a unit that the plant model assumed stayed on line.
- Controller delays. A plant controller that is slow to pass setpoints can leave the units ramping the wrong way after the fault.
- Model mismatch. If the model does not reflect inverter firmware behaviour, the simulation passes and the test fails.
For the short-circuit side of the same plant, see inverter fault current in solar plants.
How the evidence is produced
Fault ride through is shown in two stages. Before construction, the developer runs simulations in the plant model for the fault cases the compliance process requires, and shows the module stays connected and recovers. After commissioning, tests and recorded events are compared with the model. A model that matched in simulation but not in test is corrected and the simulations are repeated. The comparison method is explained in the compliance processes guide.
Checklist for the engineer
- Record the Grid Code issue, revision and the date, and check ECC.6.3.15 and ECC.6.3.16 in that revision.
- Define the connection point where the voltage is measured.
- Calculate retained voltage for the credible faults near the plant.
- Check the inverter current limit and the priority between reactive and active current.
- Review inverter and plant protection settings against the ride-through envelope.
- Prepare a model that reproduces the inverter behaviour, and plan the test that validates it.
- Check the modification tracker for open changes.
- Route the design to your chartered engineer for review before it goes to NESO or the network operator.
Related guides
The voltage quality side is in IEEE 519 with inverter-based generation. The UK series starts at the UK codes overview.
From the clause to a design your chartered engineer can sign off
We prepare the power-system studies and the engineering design behind a fault ride through submission: short-circuit and dynamic inputs, the protection and control concept, and the evidence list. The package is ready for your chartered engineer to review and sign off before it goes to the network operator. Tiza does not sign or certify designs in the UK. Contact us with the site data and the connection offer.
Frequently asked questions
What is fault ride through for a power park module?
It is the requirement that the module stays connected through a voltage dip caused by a fault on the network, supports the voltage with reactive current while the dip lasts, and restores active power quickly afterwards.
Where is the requirement in the Grid Code?
In the European Connection Conditions: ride through at ECC.6.3.15 and fast fault current injection at ECC.6.3.16. The compliance evidence, such as simulations and tests, is set in the European Compliance Processes. Check the issue and revision in force when you design.
Does the fault ride through requirement change often?
The Grid Code is revised several times a year, and open modifications can clarify or change fault ride through wording. Confirm the text and the modification tracker on the NESO website before you freeze a design.