Key Takeaways

• STATCOM sizing will be accurate only when the target is tied to a disturbance and a voltage recovery requirement.
• Weak-grid studies should centre on short-circuit strength, control limits, and post-fault recovery instead of steady state MVAr alone.
• Transparent FACTS models give you a defensible path from initial compensation estimates to final control settings.

Reactive power compensation should be sized against disturbance duty, not only steady-state MVAr.

Steady state studies will tell you how much reactive support a bus needs at one operating point, but they won’t tell you if the device can hold voltage through a fault, a plant ramp, or a control interaction. That gap matters more now because renewable capacity additions reached almost 510 GW in 2023, with solar photovoltaic leading the increase. More inverter-based connections mean more sites where voltage support must be checked in motion, not as a single snapshot.

“A good STATCOM study starts from the disturbance you expect the grid to survive and works back to the current, control limits, and recovery target you need.”

That approach gives you a compensation rating tied to voltage behaviour, fault ride through, and plant control interactions. It also gives you a model you can trust when the grid is weak and the margin for error is small.

FACTS devices support voltage control in stressed networks

FACTS devices are used to control voltage, reactive power flow, and transfer capability when the network cannot hold acceptable voltage on its own. A STATCOM is one member of that group, and it is often selected when the grid is weak, the voltage swings are steep, or the response must stay effective during a disturbance.

A long collector system feeding a remote substation is a clear example. The bus can sit within limits at normal output, then fall sharply when a nearby fault is cleared or when a large motor starts. A fixed capacitor will only supply a fixed amount of reactive power, and an on-load tap changer will move too slowly. A controlled shunt device can react on the timescale that the voltage problem appears.

You should treat the device class as a control function first and an MVAr nameplate second. That framing keeps you focused on the reason the equipment is being installed. If the site problem is post-fault voltage recovery, the useful comparison is response quality under stress, not only the steady state reactive requirement at rated voltage.

STATCOM sizing starts with the voltage control target

A STATCOM should be sized from a voltage target tied to a specific operating event. You need to define the bus, the acceptable minimum voltage, the duration of the dip, and the recovery time. Those values turn a vague reactive requirement into a current and control problem you can actually test.

A point of interconnection at 132 kV shows the method well. If your plant must hold the bus above 0.92 pu during a three-phase fault recovery and return to 0.98 pu within a few hundred milliseconds, the STATCOM rating has to support that path. A load flow result that says the bus needs 35 MVAr at nominal conditions does not answer that operating target.

You’ll also need to decide what is being protected. Some projects are built around a grid code voltage envelope. Others are built around feeder motor performance, converter stability, or plant controller margins. Once the target is explicit, the rating study becomes disciplined. Without that target, the chosen size will reflect convenience more than system behaviour.

Weak grid strength sets the useful MVAr range

Grid strength sets how much benefit each extra MVAr will actually deliver. A weak grid will show large voltage movement for a modest current injection, but it will also expose control interaction, current saturation, and poor recovery if the device is undersized. Useful sizing comes from the system short-circuit level, not only the reactive requirement.

Connections based on inverter-heavy generation make this more common. Solar and battery storage account for 81% of new U.S. utility-scale generating capacity expected in 2024. A site with low short-circuit strength and a long export line will often need a STATCOM sized for fault recovery current, even if the normal reactive requirement looks modest.

A wind or solar plant tied into a remote bus can illustrate the trap. The bus may regulate well at 20 MVAr during normal export, yet need 60 MVAr worth of controlled current support once a fault is cleared and converter controls re-synchronise. That is why weak-grid studies should treat short-circuit strength as the main sizing frame, then refine the range with operating cases.

Control limits shape the STATCOM dynamic response

The STATCOM dynamic response is shaped by current limits, control gains, voltage measurement filtering, and protection thresholds. Those elements decide how much reactive current is actually available during a dip and how cleanly the device returns to normal control after the event. Nameplate MVAr alone will not tell you that behaviour.

A practical case is a controller tuned for very tight voltage regulation on a bus with noisy measurements. If the filter is too light, the converter can chase small voltage swings and hit its current ceiling before the severe event arrives. If the filter is too heavy, the response comes late and the bus falls deeper than expected. Both cases can happen with the same MVAr rating.

You should also check the control priority during current saturation. Some models prioritise reactive current first, while others share current between active and reactive components. That choice matters at renewable interconnections where plant-level controls are also acting. A clean study records the current ceiling, the voltage regulator limits, and the recovery logic so you can see what the converter will actually do.

Simulation should reproduce the full disturbance sequence

Reactive power compensation simulation should reproduce the full event sequence from pre-fault conditions to post-fault recovery. A useful model includes the network, the device controls, the plant controls, and the switching actions that occur around the disturbance. If one piece is missing, the voltage result will look cleaner than the site will.

A fault on a nearby line is a simple example. The bus voltage drops, the STATCOM pushes reactive current, breakers clear the fault, plant converters recover, and tap changers or capacitor steps react later. A model built in SPS SOFTWARE lets you inspect each controller and test that sequence with transparent parameters instead of hiding the behaviour inside a black box.

• Pre-fault operating point at the studied export or import level
• Fault type, duration, and clearing order at the correct buses
• Current limits and protection thresholds inside the device controls
• Plant or feeder controls that react during recovery
• Post-fault voltage recovery criteria that match the project requirement

If you can’t reproduce the sequence, you can’t trust the rating. The most common sizing errors appear after the fault is gone, when devices hit limits, controls interact, and voltage takes longer to recover than the steady state study suggested

STATCOM versus SVC under deep voltage dips

The main difference between a STATCOM and an SVC is how well reactive support holds up as voltage falls. A STATCOM is current-based, so it keeps stronger support at low voltage. An SVC depends more heavily on system voltage, so its effective reactive output drops more sharply during deep dips.

A transmission bus exposed to severe fault dips shows the contrast clearly. The SVC can regulate well during normal operation and mild disturbances, yet it loses strength when the voltage falls to the point where support is needed most. The STATCOM usually gives you better low-voltage support and cleaner recovery, though its converter controls still need proper tuning and current limits.

Load flow snapshots miss the worst compensation duty

Load flow snapshots miss the worst compensation duty because they solve a settled operating point after transients are gone. They are useful for initial screening, bus placement, and normal operating range, but they will not show current saturation, control interaction, or delayed voltage recovery during a disturbance.

A collector station can make this obvious. The steady-state case might show a 25 MVAr shortage at peak export, which suggests a modest device rating. The fault study can show the bus needs the equivalent of 70 MVAr worth of reactive current support for a short interval to stay above the plant trip threshold. Both results are true, but they describe different duties.

“You should use load flow to frame the starting point, then let disturbance studies set the final size.”

That order prevents a common mistake: selecting compensation from a tidy bus voltage report and finding later that the device can’t hold the bus through the event that actually matters.

Transparent control models improve confidence in final settings

Transparent control models improve confidence because you can see how the compensation will behave before you commit to final settings. That visibility matters more than another decimal place in the steady state result. Final tuning depends on filters, limits, and recovery logic that need inspection, not assumption.

A utility interconnection study often passes through several revisions as fault levels, export limits, and plant controls are updated. Open models let you adjust the voltage regulator, current ceiling, or measurement filter and check the effect without losing track of the physical meaning. That is why engineers working in SPS SOFTWARE can test compensation against disturbance behaviour instead of trusting a single load flow snapshot.

You’ll make better settings when the model tells you why the voltage recovers cleanly or why it doesn’t. A final rating chosen that way is easier to defend in design review and easier to teach to the next engineer who inherits the study. SPS SOFTWARE fits that closing step well because the model stays visible, editable, and tied to the system behaviour you’re trying to control.

Key Takeaways

• Harmonic resonance is a network impedance problem, so device level harmonic limits never tell you enough on their own.
• Frequency scans find where the grid is sensitive, and time domain checks show which switching or control events will excite that sensitivity.
• Careful model detail at weak buses will do more for study quality than broad assumptions across the full network.

Harmonic resonance studies will show you where a grid will magnify distortion before a routine equipment addition turns a small harmonic source into a serious voltage problem.

Utilities and plant engineers keep adding converter-based generation, drives, and reactive support because the grid needs stable voltage and efficient power flow. Resonance risk rises with that mix, since each filter, cable, transformer, and capacitor shifts the network impedance seen by harmonic currents. Renewable capacity additions reached almost 560 GW in 2023, up 64% from 2022, which shows how quickly inverter-based equipment is being added to power systems. A study plan that combines frequency scans with time domain checks will show you the resonant points before equipment insulation, protection, or control performance is affected.

Harmonic resonance occurs when network impedance peaks sharply

Harmonic resonance happens when inductive and capacitive elements line up at a frequency where network impedance rises sharply, so a small harmonic current creates a much larger voltage distortion. You’ll see the problem as amplification of specific frequencies, and that distinction matters when you assess risk.

A 13.8 kV feeder with a capacitor bank, transformer leakage reactance, and several long cables can resonate near the 5th or 7th harmonic. A modest current from a variable speed drive or solar inverter will then produce bus voltage distortion that looks out of proportion to the source. Operators often blame the nearest device alone, even though the grid impedance is doing most of the amplification. Your study has to focus on the full network shape and the emitter that excites it.

That focus will keep you from chasing the wrong fix. Swapping one inverter controller or tightening a distortion limit will not solve a resonance tied to feeder capacitance and source strength. You need the resonant frequency, the impedance peak, and the bus location where the response is worst. Once those are known, mitigation becomes an engineering exercise instead of trial and error.

Inverters shift resonant points through controls filter design

Inverters shift resonant points because their filters, transformer connections, cable lengths, and control loops alter the frequency-dependent impedance of the grid. A bus that looked benign before a plant expansion will resonate after the added equipment changes that impedance map, even if each inverter still meets its individual harmonic limits.

Solar, storage, and wind made up 95% of the 2,600 GW waiting in United States interconnection queues at the end of 2023. That scale matters because queued projects add more converters, more collector cables, and more reactive equipment to the same network. A 100 MW plant expansion often adds enough filter capacitance to shift an existing resonance from one harmonic order to another. Your study should treat every large inverter addition as a network change, not a simple replacement.

Controls add another layer. A grid-following inverter with an LCL filter will interact differently from a plant using different damping values or a different phase-locked loop bandwidth. Two sites built from similar single line diagrams can produce very different scan results once those parameters are included. That’s why simplified generic inverter blocks often miss the frequencies that later show up during commissioning.

Capacitor banks can amplify distortion at specific frequencies

Capacitor banks amplify distortion when their reactance combines with system inductance at a frequency near existing harmonic content. The bank itself does not create the harmonic source, yet it can set the condition that turns a tolerable current injection into damaging bus voltage, relay nuisance operation, or repeated capacitor stress.

A 34.5 kV station with switched capacitor banks can behave very differently before and after a bank closes. The bus voltage may stay within limits at fundamental frequency while the 7th harmonic rises sharply after the switching step. Engineers sometimes see the distortion event and assume a control fault in the nearest inverter. The stronger explanation is often a shifted parallel resonance created by the bank.

This is why capacitor studies need more than kvar sizing. Detuning reactors, bank location, and switching sequence will all affect where the peak lands. Industrial plants with power factor correction face the same issue as renewable collector systems, especially when background harmonics already exist upstream. You’ll get better results when capacitor planning and harmonic studies happen as one task rather than separate reviews.

Frequency scans show where small sources create large voltages

“A frequency scan maps system impedance against frequency, and the peaks tell you where a modest harmonic current will create a large voltage response.”

It is the fastest way to find resonance risk before commissioning, because it shows both the resonant frequency and the bus where the network is most sensitive.

A plant interconnection study often scans from the point of common coupling down to inverter terminals and auxiliary buses. One bus may show a mild response at the 5th harmonic while a collector bus shows a steep peak near the 11th. That contrast tells you where to place filters, where to shift capacitor settings, or where more model detail is needed. A scan will also show when a new cable run moves the peak enough to matter.

Time domain studies confirm resonance under switching events

Time domain studies test resonance under switching and control events that a scan cannot show on its own. They will confirm if a resonant point actually produces harmful overvoltages, sustained ringing, or current stress when a capacitor closes, an inverter ramps, or a fault is cleared.

A capacitor energization event at a weak bus can excite a resonant frequency for several cycles, even when steady-state harmonic injection looks small. An inverter trip and reclose sequence can do the same if DC link controls and plant-level reactive control re-enter with the wrong timing. SPS SOFTWARE is useful here because you can pair a frequency scan with a transparent time domain model and test the same network under switching events. That link between scan results and waveform response is what turns suspicion into proof.

This step matters because not every scan peak becomes an operating problem. Some peaks sit near frequencies with no meaningful source, while others line up with switching patterns, converter sidebands, or background distortion already present on the feeder. You’ll make better mitigation choices when you know the event that excites the resonance, the duration of the response, and the devices that see the highest stress. That evidence also helps protection and operations teams agree on settings and switching rules.

Model detail determines which resonant peaks appear

Model detail decides which resonant peaks you will find, because resonance is set by the actual inductance, capacitance, resistance, and controls present in the network. A study that lumps cables, omits transformer winding data, or treats filters as generic blocks will shift or erase peaks that exist on the site.

A collector system with several 2 km cable segments behaves differently from the same plant modelled as one equivalent line. Each segment adds distributed capacitance and modifies the local impedance seen from nearby buses. Transformer grounding, winding connection, and stray capacitance also affect zero-sequence and high-frequency response. Those details are tedious, but the missing data will usually hurt the study more than an imperfect load estimate.

You don’t need infinite complexity. You need enough fidelity at the frequencies of concern and at the buses where distortion will be measured or equipment will trip. Good harmonic analysis software is most useful when the model is transparent about assumptions, so engineers can edit parameters, rerun cases, and understand why a peak moves after a design change. That approach is more useful than a closed black box that gives a plot without revealing the network physics.

Study the weakest buses before adding new devices

The weakest buses deserve attention first because they combine low short circuit strength with equipment that shifts impedance. These are the buses where added inverters, capacitor banks, or long cable runs will produce the biggest resonance swings, and where mitigation choices will have the largest effect on the whole system.

A study plan works best when you rank buses before you model every corner of the grid. A point of common coupling may look like the obvious first target, yet the more sensitive location is often a collector bus, an auxiliary medium voltage bus, or a capacitor bank terminal. One industrial feeder can stay quiet at the utility interface while a motor control bus sees severe local amplification. These are the places most teams should check first:

• The collector bus that ties many inverter blocks through long cables deserves an early scan.
• The bus where a switched capacitor bank or filter connects needs separate operating cases.
• The weakest feeder seen by the lowest short circuit ratio should be ranked near the top.
• The low voltage side of a transformer feeding dense power electronics often hides local peaks.
• The remote end of a long cable run with light local load can show sharp impedance swings.

This ranking will save time and improve the first pass of your model. It also keeps you from spending days refining buses that cannot excite or magnify the frequencies you care about. Once the high-risk buses are understood, you can expand the scan set and test contingencies with much better focus. Your mitigation plan will then reflect the actual weak points instead of the simplest single line location.

Common modelling errors hide resonance until equipment trips

Common modelling errors hide resonance because they flatten the impedance curve or place peaks at the wrong frequency. The usual culprits are equivalent cables, missing capacitor states, generic inverter filters, stale utility source data, and cases that stop at a scan without checking the operating event that excites the peak.

One site can pass a preliminary study and still trip capacitor protection after energization because the model used nominal source strength and ignored an alternate feeder configuration. Another site can appear unsafe on paper until the engineer adds the damping resistor that was present in the actual filter bank.

“Good harmonic work is less about software features and more about model discipline, because missing one cable section or mistuning one filter can erase the very peak that later trips equipment.”

You’re judging a physical system, so the model has to stay close to the physical system.

That is the standard you should hold for every harmonic resonance study. A solid workflow pairs frequency scans with time domain checks, updates the model after each design revision, and tests the buses most likely to amplify distortion. SPS SOFTWARE fits that workflow because it supports transparent modelling and lets engineers verify resonance risk before equipment is exposed to avoidable stress. Careful execution will always beat guesswork when resonant points move each time a grid adds new inverters or capacitor banks.

Key Takeaways

• Transformer energization is a magnetic saturation problem, so linear transformer models will understate inrush current and relay exposure.
• Residual flux, switching angle, and source impedance set the spread between mild and severe inrush cases, which is why single-case studies mislead.
• Protection settings work best when they are checked against simulated inrush envelopes built from transparent transformer models.

Accurate transformer inrush current studies depend on modelling saturation, residual flux, and switching instant.

Large power transformers carry system consequences far beyond their own terminals, and roughly 90% of electricity generated in the United States passes through them at some point. A clean voltage step into a linear transformer model won’t show the current peaks, waveform distortion, or relay trouble that appear on site. You’re studying a magnetic memory problem as much as an electrical one. That is why transformer energization has to be treated as a flux history problem from the first simulation run.

Transformer inrush current starts with core flux imbalance

Transformer inrush current begins when the flux demanded by the applied voltage does not line up with the flux already sitting in the core. The mismatch pushes the operating point past the knee of the magnetization curve. Once that happens, magnetizing current rises sharply and becomes highly asymmetrical.

“That first current peak comes from saturation rather than load current.”

A no-load 132/33 kV transformer closed onto an energized bus shows this clearly. The winding sees sinusoidal voltage, yet the core does not start from a neutral magnetic state. If the applied flux trajectory begins in the same direction as the leftover flux, the core saturates during the first half cycle. Current then becomes flat-topped, rich in low-order harmonics, and much larger than the steady magnetizing current you’d expect from a linear model.

You’ll get the physics right only when the model tracks flux as the time integral of voltage and lets the core saturate. A model built from leakage impedance and ideal turns ratio alone will always understate the first few cycles. That matters because protection, breaker duty, and winding force all respond to the current that actually flows during those cycles. Once you accept that starting point, the rest of the energization study becomes much easier to structure.

Residual flux sets the worst case before energization

Residual flux sets the worst case because the core rarely returns to zero magnetization after de-energization. The last switching event leaves a magnetic bias in one or more limbs. That bias adds to the new flux excursion after the next close. Current gets largest when residual flux and applied flux move in the same direction.

A transformer opened after carrying light load often retains substantial remanence. Close that same unit a few minutes later from the same side, and the magnetic state from the previous run still matters even though terminal voltage had fallen to zero. If one phase is sitting near positive residual flux and the breaker closes at an unfavourable point on the voltage wave, that phase will hit saturation much earlier than the others. You then see uneven phase currents, a large dc offset, and a longer inrush decay.

You should treat residual flux as a study input and keep it visible in every case definition. Good transformer energization work tests several remanence patterns, including zero remanence, balanced remanence, and a worst-aligned case. That approach shows the spread between mild and severe inrush instead of producing a single misleading answer. It also explains why field results can differ from a nominal study even when nameplate data and system voltage look correct.

Switching angle determines the first peak current

Switching angle determines the first peak current because transformer flux follows the integral of applied voltage, so the voltage value at the instant of closing does not tell the full story. Closing near a voltage zero crossing produces the largest flux rise over the next half cycle. Closing near voltage peak produces the smallest immediate flux rise. The breaker’s closing instant will shape the first inrush crest more than load conditions will.

A close-on-wave study makes the point quickly. Take the same unloaded transformer with the same residual flux and source impedance, then run two cases. One case closes near voltage peak and produces a modest transient. The other closes near voltage zero and pushes the flux well past the saturation knee, so the first current crest becomes several times larger and far more asymmetrical.

Three-pole breakers add another wrinkle because each pole does not close at exactly the same electrical angle. Small pole scatter creates phase-to-phase differences that can stretch the transient and distort the neutral current. That is why a single energization case won’t tell you much. You need a set of switching angles that captures favourable, typical, and severe closes before you make any judgement about expected inrush current.

Saturation curves decide if a model can predict inrush

The saturation curve decides if a model can predict inrush because it controls when magnetizing inductance collapses as flux rises. A linear magnetizing branch cannot produce the sudden current growth seen during energization. The knee point, slope above the knee, and air-core region all shape the peak and decay. If those features are missing, the result will look clean and will be wrong.

Consider two models of the same transformer. One uses a fixed magnetizing reactance, and the other uses a nonlinear magnetization curve fitted from excitation data. The linear case shows a tidy transient that settles quickly and stays well below what field crews expect. The nonlinear case produces a tall first peak, a flatter waveform, and slower decay because the core spends part of each cycle in saturation.

That difference is why transparent magnetic modelling matters during commissioning studies and teaching work alike. SPS SOFTWARE lets you inspect and edit the transformer magnetization branch instead of hiding it behind a black-box component. You can test how a softer knee, deeper saturation, or missing excitation data changes the predicted inrush. Once the magnetic branch is visible, disagreements between study results and site experience usually become much easier to explain.

Transformer energization studies need a defined study sequence

Transformer energization studies need a defined study sequence because the result depends on several coupled inputs that can easily be mixed up or omitted. You need a repeatable order for choosing system strength, transformer data, remanence, switching instant, and measurement points. A disciplined sequence cuts rework and makes case-to-case comparisons meaningful. It also keeps protection review tied to the same assumptions used in the electrical study.

• Set source voltage and source impedance first.
• Enter winding data and connection details next.
• Fit the nonlinear magnetization curve from test data.
• Assign residual flux cases before breaker-closing cases.
• Record peak current, decay time, and relay quantities.

That sequence works because each step fixes an assumption the next step depends on. A protection engineer reviewing differential restraint needs the same remanence case that the system engineer used for peak current. A research lab repeating the study next term needs the same measurement points and solver settings. You’re not just running a simulation here. You’re building a traceable explanation for why the transformer energization result should be trusted.

Protection trips because inrush distorts current measurements

Protection trips during inrush because the relay sees large, distorted current that can resemble an internal fault or a severe external event. The current contains asymmetry, harmonic content, and phase imbalance, and current transformers can saturate as well. That mix alters the quantities many protection elements depend on. A relay setting that is stable for load and fault duty can still misread energization.

Published studies report first-peak magnetizing inrush above 10 times rated current under severe remanence and switching conditions. A differential relay facing that waveform can see high operate current before harmonic restraint settles. Ground elements can react to neutral current caused by phase asymmetry. Feeder overcurrent protection can also pick up if the source is stiff and the transformer is large relative to feeder rating.

Second-harmonic restraint helps, but it isn’t a universal shield. Modern cores, residual flux, and current transformer saturation can produce inrush signatures that don’t match the tidy textbook pattern. That is why protection review has to use simulated relay quantities from a credible energization model. If you only compare RMS peak current with a pickup setting, you’ll miss the measurement distortion that causes nuisance tripping.

System impedance shapes the predicted inrush current peak

System impedance shapes the predicted inrush current peak because it limits how much voltage the transformer actually sees while the core is saturating. A stiff source holds terminal voltage up and allows higher current. A weak source sags more and reduces the peak. The same transformer can look mild or severe depending on what is upstream.

A unit energized from a strong transmission bus will produce a different first crest than the same unit energized through a long cable or a station service path. The weaker path adds series impedance, lowers the instantaneous terminal voltage during saturation, and usually trims the peak current. That does not always reduce relay concern, though, because a slower decay can keep restraint and timing questions alive for longer than expected.

Protection settings should follow simulated inrush current envelopes

“Protection settings should follow simulated inrush current envelopes because a single energization case will never represent the range you’ll see in service.”

You need an envelope built from switching angle, residual flux, source strength, and transformer saturation cases. That envelope gives you pickup, restraint, delay, and security margins grounded in physics. It also turns commissioning review into a check against studied limits rather than a guess.

A solid settings review tests the worst aligned remanence case, a typical close, and at least one weak-source energization path. You then compare the relay’s measured quantities against those cases instead of relying on one textbook multiplier. That process often shows that a small timing delay or revised restraint threshold is enough to ride through inrush without masking genuine internal faults. It also shows when the study assumptions are too thin to justify any setting change.

Good engineering judgement comes from models that expose the magnetic and network assumptions behind the waveform. SPS SOFTWARE fits that need because you can inspect the saturation branch, adjust study cases, and keep the reasoning visible to the people signing off the energization plan. When protection rides through inrush on site, it usually reflects careful modelling long before the breaker ever closed.

Key Takeaways

• Subsynchronous resonance is a damping problem that only becomes clear when electrical, mechanical, and control loops are studied as one system.
• Series compensation and converter controls can both supply energy to a subsynchronous mode, so the source of oscillation must be identified before mitigation is selected.
• Time domain models with the right control, network, and shaft detail give you evidence you can act on, while steady state studies only tell you where to look next.

Subsynchronous resonance in converter-heavy grids can only be trusted when you study it in detailed time-domain simulation.

Grid composition now includes far more power electronic sources than older screening methods assumed. Renewable capacity additions reached almost 510 GW in 2023, with solar photovoltaic accounting for about 75% of that growth. That shift matters because controls, network resonance, and shaft mechanics can now meet in the same study space. If you rely on steady-state snapshots, you won’t see the feedback loop that turns a mild disturbance into repeated current and torque stress.

Subsynchronous resonance begins with energy exchange below synchronous frequency

Subsynchronous resonance is sustained energy exchange below the grid fundamental, usually between the network and a mechanical shaft or converter control loop. The signal sits under 50 or 60 Hz. Risk appears when damping is low enough for each cycle to feed the next one, so you’re looking for growth rather than a low-frequency component alone.

A practical case helps fix the idea. A 60 Hz system can show an electrical oscillation near 25 Hz after a fault clears on a series compensated line. Current at that frequency can pass through a generator shaft or a wind plant controller and return with more energy than it lost. Oscillography will then show a rising envelope on current, electrical torque, or shaft torque even after the initiating event has ended.

That distinction matters because many studies stop after spotting a resonance frequency. Frequency alone does not confirm a harmful mode. A stable 25 Hz component that decays quickly is a different problem from a 25 Hz mode that grows for several seconds.

“Good studies treat subsynchronous resonance as a closed loop question, with source, path, phase, and damping all represented.”

Series compensation can couple electrical resonance with shaft torque

Series compensation shifts the line’s electrical natural frequency downward, and that can place it close to a torsional mode of a turbine generator shaft. Once those frequencies line up, the network can exchange energy with the shaft every cycle. Torque reversals then rise faster than current plots alone suggest. Torsional interaction becomes visible only when electrical and mechanical states are solved at the same time.

Consider a long transmission corridor with 40% series compensation on a 60 Hz system. The capacitor and line inductance can place electrical resonance near 30 Hz. A nearby steam unit might have a shaft mode around 28 to 32 Hz across turbine sections. A fault, line switch, or power transfer step can then excite both sides at once, and the shaft sees alternating torque that repeats long after voltage appears to recover.

You can miss this with a simplified generator model. A single lumped inertia shows rotor speed movement, yet it won’t reveal which shaft section takes the stress. Utilities learned this in classic SSR events, and the lesson still stands in converter-heavy grids. Series capacitors are not the problem on their own. Trouble starts when compensation, operating point, and a lightly damped mode occupy the same frequency band.

Converter controls can create subsynchronous oscillation in wind plants

Wind plants can produce subsynchronous oscillation when converter controls interact with weak grids, series compensation, or neighbouring control systems. The mechanism sits in software and power electronics rather than a turbine shaft alone. Phase locked loops, current regulators, outer power loops, and dc link controls can all add or remove damping. This is often called subsynchronous control interaction when the controller is the main energy source.

Texas had 42,640 MW of installed wind capacity at the end of 2023. That scale explains why a wind plant connected through a series compensated corridor deserves more than a basic load flow check. One common case uses a doubly fed induction generator plant whose rotor side converter reacts strongly near the network resonance. Another case appears in a full converter plant when a tight phase locked loop meets a weak point of interconnection.

The visible symptom is often current or power oscillation rather than obvious mechanical distress. Plant-level controls can also mask the source because turbines share a collector system and plant controller. If you only check one inverter against an ideal bus, you’ll miss collector impedance, cable capacitance, and controller interactions across units. Converter-heavy grids need plant level modelling before you can trust the damping sign.

Steady state studies miss the feedback loops that matter

Steady state studies miss subsynchronous problems because they solve operating points, not dynamic energy exchange. Load flow, short circuit duty, and basic voltage screening are still useful, yet they can’t show a growing 20 to 40 Hz mode. Control states, limiter action, and phase delay sit outside their scope. You can’t infer damping from a snapshot.

A common failure appears after a voltage dip. The post-fault operating point looks acceptable, line loading is within limits, and capacitor duty seems normal. The converter, though, may pass through a current limit, shift control priority, and return with a different effective impedance at subsynchronous frequency. That sequence decides stability, and it exists only in time.

Protection adds another blind spot. A crowbar, bypass gap, protective relay, or capacitor protection logic can change the network structure during the event you’re studying. Those actions alter frequency, damping, and current path at the exact moment the mode is forming. Screening studies are good for narrowing where to look. They can’t settle if the oscillation will decay, persist, or grow.

Time domain simulation must represent the full feedback loop

Time domain simulation captures subsynchronous resonance only when the full loop is represented from disturbance to response and back again. That means network impedance, controls, protection, and any relevant shaft dynamics must interact at the simulation time step. Event timing matters because milliseconds can alter phase. A model that omits one active part of the loop can give the right frequency and the wrong damping.

A useful study sequence starts with a credible operating point, then applies a specific event such as fault clearing, line energization, or a power reference step. You then track current, electrical torque, shaft torque, control outputs, and bus voltage for several seconds after the event. SPS SOFTWARE fits this workflow when you need transparent models that can be inspected and adjusted instead of treated as sealed blocks. That visibility matters when you’re trying to explain why a mode grows.

Good execution does not mean excessive detail everywhere. It means the detail matches the active physics of the loop you are testing. If the question is shaft torque, you need shaft detail. If the question is converter control interaction, controller timing and network frequency response deserve priority. That discipline turns simulation into evidence instead of animation.

Model detail determines if subsynchronous control interaction appears

Subsynchronous control interaction appears only if the model preserves the control dynamics that shape subsynchronous impedance. Average blocks with ideal measurements can erase the delay, filtering, and limiter behaviour that create the instability. The same is true for overly simple network equivalents. Model detail is not about making everything large. It is about keeping the details that set phase and damping at the frequencies of concern.

A grid equivalent behind the point of interconnection can be useful for screening, yet it becomes risky when it hides resonant poles from adjacent lines or collector feeders. A phase locked loop model without its measurement filter can look calmer than the implemented controller. A one mass turbine model can also suppress torsional splitting that matters when electrical resonance sits between shaft modes. Each simplification removes a possible feedback path.

You don’t need transistor-level switching for every study, and you don’t need to model every wind turbine in full detail. You do need the implemented control structure, realistic delays, collector system impedance, and enough mechanical resolution to expose the stress path. If your results swing from stable to unstable after small parameter corrections, that doesn’t mean the simulation failed. It means the system is sensitive and your margin is thin.

Detection depends on mode growth across current, speed and torque

Detecting subsynchronous resonance means checking how a mode grows across electrical and mechanical signals after a credible disturbance. No single trace is enough. Current can look modest while shaft torque rises sharply, and plant power can oscillate while individual controls saturate. You’ll get a trustworthy answer only when signals are reviewed as one coupled response.

• Track line current spectra below the fundamental after each disturbance.
• Measure shaft torque or equivalent mechanical stress where rotating machines are present.
• Record converter internal states such as phase angle, current references, and limiter status.
• Compare damping at several operating points instead of one dispatch level.
• Check if the oscillation survives after the initiating event is fully cleared.

A useful diagnostic pattern is rising subsynchronous current, a lagged change in control output, and a matching increase in torque ripple or power oscillation. Another pattern shows stable current at one dispatch point and unstable growth at a higher transfer level, which tells you operating range matters as much as topology. You’ll also want to separate forced response from natural mode growth. A forced oscillation follows an external source, while subsynchronous resonance keeps feeding itself after the trigger ends.

“You can’t manage this class of risk with static studies and broad assumptions, because the damaging mechanism sits in timing, coupling, and damping.”

Mitigation must target the loop that sustains oscillation

Mitigation works when it targets the specific loop that supplies energy to the subsynchronous mode. That could mean shifting the electrical resonance, adding damping in a controller, blocking an operating range, or changing protection timing. Generic fixes waste time because the visible symptom is often far from the actual source. A torque problem can start in a converter loop, and a current problem can start in network compensation.

A line study might show that reducing series compensation moves the electrical resonance away from a shaft mode and ends torsional stress. A wind plant study can show that retuning a phase-locked loop or current controller adds enough damping to stop a 25 Hz oscillation without changing dispatch. Another case can require a supplemental damping function because the plant must keep its compensation level and operating range. Each fix follows from the loop identified in simulation, not from a standard checklist.

Disciplined modelling is what turns subsynchronous resonance from a surprise into a tractable engineering problem. SPS SOFTWARE belongs in that process when you need editable time domain models that show how the loop behaves before equipment absorbs the lesson. That judgment holds across utility studies, research work, and teaching labs because the physics do not simplify themselves for convenience.

This guide outlines six simulation checks that help engineers test power factor correction stages for control stability, startup response, and harmonic distortion before hardware testing.

This guide explains how real-time simulation supports power system testing, how it differs from offline studies, and what model and hardware choices matter most for validation.

This piece explains how inverter model fidelity affects renewable grid studies, interconnection reviews, stability analysis, and IEEE 1547 compliance checks.