IEEE 1547 Standard
Request InformationGrid code compliance is the point at which a distributed energy resource stops being an engineering achievement and becomes a product a utility will actually allow onto its network. It is also, for most manufacturers, the longest and least predictable phase of the development programme. A converter that performs beautifully on the bench can still fail a conformance campaign on a ride-through profile, a settling time, or a reporting requirement — and each failure costs weeks of laboratory time that was booked months in advance.
This guide explains what grid code compliance testing actually involves, how IEEE Std 1547 and IEEE Std 1547.1 relate to one another, and what the full type-test programme demands of a test bench. We then walk through all twenty-eight type-test scenarios in the conformance programme, one by one, describing what each proves, what the bench applies, what is measured, and what counts as a pass. If you are planning a certification campaign, or building the bench that will support one, this is the map of the territory.
What Grid Code Compliance Actually Means
A grid code is the set of technical rules a network operator imposes on anything that connects to its system. Historically these rules were short, because distributed generation was rare and its aggregate effect on the network was negligible. A converter was expected to disconnect quickly when conditions went abnormal, and little else was asked of it.
That expectation has completely inverted. With inverter-based resources supplying a large and growing share of generation, a fleet that disconnects at the first disturbance is itself the disturbance. Modern grid codes therefore require the opposite behaviour: distributed resources must stay connected through voltage and frequency excursions, and must actively support the network through reactive power exchange, active power curtailment, and frequency-droop response.
Grid code compliance testing is the process of proving, under controlled and repeatable laboratory conditions, that a given piece of equipment behaves the way the code requires. It is not a functional check. It is a structured programme of adversarial tests in which the bench deliberately drives the terminal into conditions the equipment will rarely, if ever, see in service, and records precisely how it responds.
IEEE 1547 and IEEE 1547.1
IEEE Std 1547
Defines what a distributed energy resource must do once it is connected to the network.
- Behaviour during normal operation
- Response to abnormal voltage and frequency
- Conduct at connection and disconnection
IEEE Std 1547.1
Specifies the tests and evaluations performed to confirm that equipment conforms to IEEE Std 1547.
- Type, production, commissioning and periodic tests
- What is applied, what is measured, what passes
- The record a certification body will accept
The four categories of test
The conformance programme is not a single event. It is four distinct activities, applied at different points in a product's life:
| Test category | When it happens | What it covers | Where it runs |
|---|---|---|---|
| Type tests | Once per product design | Full behavioural programme against the requirements standard | Laboratory, on a conformance bench |
| Production tests | Every unit shipped | Abbreviated checks on abnormal voltage and frequency response, plus documentation | Factory, end of line |
| Commissioning tests and evaluations | Per installation | Verification that the installed system behaves correctly at its point of connection | Site |
| Periodic tests | At intervals over service life | Confirmation that protective behaviour has not drifted | Site |
Type tests are by far the largest and most demanding of the four, and they are the category a grid emulator exists to serve. Everything that follows in this guide concerns them.
How conformance becomes certification
The requirements standard issues no mark and no certificate. It becomes binding only when a jurisdiction adopts it — a public utility commission, a network operator, or a regional authority writing it into interconnection rules. Conformance is then typically demonstrated through a product certification scheme operated by an accredited testing laboratory, which uses the conformance test procedures as its technical basis. The certificate attests that a specific configuration — particular ratings, particular firmware, particular settings — was tested against those procedures and passed.
That qualifier matters more than manufacturers usually expect. Change the firmware, change a protective function, change a rating, and the scope of the certificate may no longer cover the product being shipped. This is one of the strongest arguments for owning a conformance-capable bench in-house rather than treating certification as a one-time external purchase.
Grid Code Compliance Beyond North America
The conformance test procedures standard is a North American instrument, but the engineering it describes is not regionally specific. Comparable obligations exist in every major market, and they converge on the same functional families — ride-through, grid support, anti-islanding, power quality — while differing in thresholds, category structures, and how compliance is verified.
| Region | Governing framework | Verification approach |
|---|---|---|
| North America | Requirements standard plus its conformance test procedures companion | Single prescriptive test-procedure document feeding a laboratory certification |
| European Union | Harmonised network code for generators, implemented through European connection standards for low- and medium-voltage generating plant | Framework mandates that compliance be verified but leaves procedures largely to member states |
| Germany | National application rules for low, medium, and high voltage connection | Certificate-based scheme with separate national test and modelling guidelines |
| United Kingdom | Engineering recommendations for small and larger generating units | Type-test evidence assessed against the recommendation |
| Australia / New Zealand | National inverter requirements standard, region-based setpoints | Approved-inverter listing maintained by the market body |
The practical consequence for a manufacturer selling into more than one market is significant. The physics of the tests is common: a source that can sag, swell, ramp frequency, step phase angle, unbalance phases, and absorb exported power will serve every one of these regimes. What changes between them is the parameter set. This is precisely why a parameterisable bench is worth more than a bench hard-coded to a single code — and why we design the CHP Series test application around loadable profiles rather than fixed sequences.
What a Grid Code Compliance Bench Has to Do
Strip away the specifics and a conformance bench performs four functions:
Drive the terminal
Voltage, frequency, phase angle and balance, each independently commandable.
Supply the input
The direct-current source the equipment under test converts.
Measure
Terminal voltage and output current, at the required bandwidth and accuracy.
Execute
Sequence the run, hold each dwell, repeat across settings, retain the record.
The Full Type-Test Programme
28 Scenarios in Detail
Why Grid Code Compliance Campaigns Fail
1
Combined-stress ride-through
Passes an isolated sag but fails a consecutive sequence, or fails a single-phase sag instead of three-phase.
2
Settling and response times
The end value is right but arrives late — or the datasheet's declared time was optimistic and never verified.
3
Priority conflicts
Functions correct in isolation resolve in the wrong order once combined.
4
Setting ranges
Meets the trip requirement at default, but the adjustable range doesn't span what the standard requires.
5
Bench limits misread as failures
An undersized source can't hold a swell; a measurement path outside the required accuracy class can't evidence a criterion — both look like device failures and aren't.
6
Configuration drift
Firmware changes after testing; the certified and shipped configurations no longer match.
Building a Grid Code Compliance Bench with Impedyme
The CHP Series brings the four bench functions into a single cabinet: a regenerative source that drives voltage and frequency with independent per-phase control and true bidirectional power flow; a direct-current supply for the equipment input; a measurement path matched to the accuracy the criteria demand; and the application that compiles the procedure, executes the sequence, and retains the record.
The companion Grid Emulator application carries the same test catalogue described in this guide. Each test is presented as a tile stating the clause, the quantity driven at the terminal, and a thumbnail of the profile — and because the thumbnail is drawn from the same segments the run engine plays, a tile cannot diverge from the test it represents. Each run is retained with its settings, so a result can be reproduced or compared months later, which is exactly what an auditor, a certification body, or a returning engineer will ask for.
Commanded condition and returned trace are drawn on one frame against one time axis, voltage on one scale and frequency on the other, so that any lag between what was asked for and what the bench delivered is seen rather than inferred. For a family of tests whose criteria are timing criteria, that distinction is not cosmetic.
Because levels and durations are loaded from a licensed copy of the standard rather than compiled into the product, the same bench serves the North American programme and the European, British, and Australian regimes — the profile changes, the hardware does not.
Unintentional Islanding: The Test That Sits Apart
The twenty-eight scenarios above are the tests a grid emulator drives directly. Unintentional islanding sits apart.
The requirement is simple: on finding itself supplying an island, the equipment must detect that and cease to energize within the required interval, whatever the local balance of generation and load. The hardest case — local load almost exactly matching the equipment's output, the non-detection zone — leaves almost no voltage or frequency error to detect.
The procedure specifies a resonant parallel load at a specified quality factor, which suppresses precisely the perturbations active detection relies on. In practice: a tuned resistive-inductive-capacitive load bank, retuned per device rating, generating heat and taking floor space. An islanded system is unstable by construction, so results repeat less cleanly than elsewhere in the programme.
This is where hardware-in-the-loop earns its place, and the standard anticipates it.
Hardware-in-the-Loop and Power-HIL in Conformance Testing
The conformance test procedures standard includes an informative annex on hardware-in-the-loop-based testing. It addresses controller hardware-in-the-loop testing for supplemental devices, additional Power-HIL setup requirements specifically for testing unintentional islanding, and the measurement of impedance characteristics.
That the standard treats these methods explicitly matters. It means Power-HIL is not a workaround applied in place of proper conformance testing; it is a recognised approach within the conformance framework itself.
The engineering case is strongest for the islanding test. A virtual load, computed in real time and imposed through a power interface, can be retuned in software rather than rebuilt in hardware, swept finely through the non-detection zone rather than sampled at a handful of physical tuning points, and repeated identically as many times as needed. It does not heat the laboratory and it does not need a new build for the next device rating.
The corresponding challenge is the interface. Power-HIL couples a real-time model to real power through an amplifier, and the fidelity of the result depends on the bandwidth and latency of that coupling. Interface latency does not merely blur the result — it can destabilise the loop outright. This is why we build our Power-HIL platforms on FPGA-based real-time simulation: the model timestep and the interface latency are the specification, not an afterthought.
The broader value of hardware-in-the-loop in a compliance programme is pre-compliance. A model of the network, driven against real hardware, lets a manufacturer discover that a ride-through profile fails in week six of development rather than in week two of a booked laboratory campaign. That is where the economics of the whole exercise are decided.
Grid Code Compliance Is Won Before the Campaign Starts
Read as a whole, the type-test programme is less a hurdle than a specification. Twenty-eight scenarios, each stating a condition to apply, a quantity to measure, and a criterion to meet — every one of them discoverable on your own bench months before a laboratory books your equipment in.
The failures that cost certification campaigns are not exotic: ride-through under combined stress, settling times that were optimistic in the datasheet, functions that resolve in the wrong order together, setting ranges that fall short. None are surprises at the end of a development programme. They are only surprises if nobody looked.
What makes looking practical is a bench that runs the same procedures the certifying laboratory will run — regenerative source, direct current supply, measurement inside the required accuracy class, and a sequencer that repeats a test across settings unattended. Because levels and durations are parameters rather than fixed values, that bench covers the European, British and Australian regimes as readily as the North American one.
Grid code compliance testing rewards preparation more than any other phase of a distributed energy resource programme. IEEE 1547.1 tells you exactly what will be asked. The only decision is whether you find out how your equipment answers in development, or in a booked slot with the schedule already committed.
