Grid codes with no ride-through curve — and why

66 grid codes are plotted in this dataset. 3 more are deliberately not, and this page says why for each one. A curve we cannot trace to a clause is worse than no curve: it looks authoritative, it gets copied, and the person who copies it has no way to find out it was wrong.

By Sergey Syrvachev — Director of Product Engineering at HyperStrong

The 3 exclusions

Three reasons recur: the document is paywalled and the curves are published only as bitmaps; the code delegates ride-through to each operator, so there is no single curve to plot; or the code defines no envelope for that event at all. The fourth case is the most useful — a curve circulating under the wrong name.

  • ENTSO-E RfG (Regulation (EU) 2016/631)RfG delegates every fault-ride-through parameter to each TSO within ranges (Arts. 14(3)(a) and 16(3)(a)), so there is no single "RfG curve" to plot. It also defines no high-voltage ride-through profile at all — Annex II Figure 3 is low-voltage only. The national implementations are plotted instead.
  • Japan — utility interconnection requirementsThe candidate low-voltage curve matched no Japanese requirement, and the Japanese requirement set defines no over-voltage ride-through table.
  • High-voltage ride-through for UK G99, Ireland, France and the NetherlandsNone of these codes defines a high-voltage ride-through voltage-vs-time envelope. Only their low-voltage (and, for G99, frequency) requirements are plotted.

Last reviewed with the rest of the dataset on . If one of these becomes tractable — an edition opens up, an operator publishes a numeric envelope — it moves to the chart and off this page.

If you need one of these for a project

An exclusion is not a dead end, it just means the number has to come from somewhere other than us:

  • Paywalled documentsBuy the current edition and read the limit curve out of the figure yourself. Do not trust a redrawn version: two German candidates we rejected were byte-identical across different voltage levels, which no real code does, and a third turned out to be a voltage-relay setting rather than a ride-through envelope. Protection settings say when a plant may disconnect; a ride-through curve says when it must not.
  • Delegated frameworks (ENTSO-E RfG)Go to the connecting TSO's national implementation. RfG sets ranges, not values; the binding number is whatever your TSO chose inside them, and it differs across borders that share the same regulation.
  • Events the code does not define (HVRT for G99, Ireland, France, the Netherlands)There is no envelope to find. Confirm the obligation is genuinely absent rather than located elsewhere, and treat any HVRT figure quoted to you for these markets as unsourced until someone shows you the clause.