Free Trial
Free Trial
Two engineers reviewing capacitor bank switching study drawings
Power Systems

Modelling capacitor bank switching transients and overvoltage

Key Takeaways

  • Capacitor bank switching overvoltage is set by the first milliseconds of the close, so time-domain study is required.
  • Back to back bank arrangements and breaker behaviour often create the highest stress cases in a switching study.
  • Mitigation only counts when waveform checks show lower peaks at every bus that hosts sensitive loads.

Capacitor bank switching must be studied as a transient event, because a routine close can create overvoltage that reaches far beyond the switched bus.

Steady-state reactive power checks won’t show the first peak, the inrush path, or the way nearby banks reflect the event back into the feeder. A Lawrence Berkeley National Laboratory study estimated that power disturbances cost U.S. businesses $104 billion to $164 billion each year, which gives short switching events practical weight beyond the waveform screen.

Capacitor bank energization creates steep transient overvoltage

Closing a capacitor bank connects an uncharged element to a live network, so the first milliseconds are set by the voltage difference, source inductance, and breaker timing.

“Steady-state reactive power calculations won’t reveal it.”

A 13.8 kV industrial bus can look calm in load flow, yet the same bus can ring sharply when a 2.4 Mvar bank closes near a lightly damped source. Sensitive power supplies respond to the peak rather than the reactive support. The ITIC voltage tolerance curve places 120% of nominal voltage outside the normal operating region once it lasts more than 0.5 cycle, which shows why a brief rise still matters when it reaches control circuits or drive front ends.

You need capacitor bank switching transient simulation because the damaging part of the event happens before the bank settles to its new steady voltage. Cable length, transformer leakage, and local load impedance all shape that first oscillation. If you only inspect the bus after the breaker is fully closed, you’ll miss the event that trips equipment.

Back-to-back banks magnify the first peak

Back-to-back switching is severe because an energized bank will discharge into the newly closed bank through very low inductance. That local exchange creates higher inrush current, higher frequency oscillation, and stronger voltage magnification than a single isolated bank energization case.

A common plant arrangement makes this easy to miss. One bank is already on the bus, a second bank closes for added reactive support, and the current path between them is only the short buswork and breaker connection. That path has little resistance, so the first current crest rises fast. Protection that never reacts to a remote feeder fault can still see sharp current spikes during this close.

Voltage magnification also appears away from the switched bus. A nearby motor control centre, a long cable to a variable speed drive, or a tertiary winding on a transformer can show a larger crest than the capacitor terminals themselves. That is why a capacitor bank switching study has to include adjacent buses and connected equipment, not only the bank that is being energized.

EMT simulation captures capacitor switching transients in time

EMT simulation captures capacitor switching transients because it resolves the waveform sample by sample through the switching instant. You can see the first peak, the oscillation frequency, the decay rate, and the way reflections move through feeders, transformers, and nearby capacitor banks.

A practical case study starts with the pre-switch steady state, then closes the breaker at defined angles across several runs. You’ll usually record bus voltage, capacitor current, breaker current, and the voltage seen by nearby loads. A 60 Hz phasor study cannot show the difference between a mild ring and a steep surge at a drive bus, but an EMT run will show it clearly.

That time view also helps you separate causes. One case might be dominated by local bus inductance, while another is set by a long cable reflection or a transformer capacitance path. When you model capacitor bank energization this way, mitigation moves from guesswork to direct comparison of waveforms, current peaks, and damping time.

A useful EMT model starts with stray inductance

Useful capacitor switching modelling starts with the inductance and resistance that sit between the source, breaker, bus, and capacitor bank. Those small elements set the inrush frequency and peak current, so an ideal source tied to an ideal capacitor will give a neat waveform that is physically wrong.

A short section of bus duct, a few metres of cable, or a small current-limiting reactor can change the shape of the event more than a large shift in steady-state load. A transparent model in SPS SOFTWARE lets you inspect those paths directly, which matters when you are checking why two similar banks produce very different switching records on site.

Model element Why it changes the switching waveform
Source Thevenin inductance and resistance This branch sets how much current the upstream system can force into the bank during the first oscillation.
Bus duct and short cable sections These small lengths often control the local oscillation frequency when banks sit close to the breaker.
Capacitor bank internal arrangement Series and parallel groupings shift effective capacitance and can change the local current split during energization.
Current limiting reactor placement Reactor location changes both the first peak and the damping seen at nearby buses.
Connected transformers and motor loads These devices create alternate paths for reflected energy and can raise stress away from the switched bus.

That level of detail does not make the study complicated for its own sake. It makes the result believable. You’re not trying to build every screw and bracket, but you’re trying to capture the electrical path that will shape the transient overvoltage and the inrush current seen by the breaker.

Breaker closing angle controls the worst energization case

Breaker closing angle controls the worst energization case

Breaker closing angle matters because the voltage difference across the contacts at the instant of conduction sets the first charging surge. The worst case appears when the trapped capacitor voltage and source voltage create the largest mismatch at contact touch or prestrike.

A three-phase bank closing near a source voltage crest will not produce the same stress as a close near a zero crossing. Phase spread makes this more severe, because poles do not close at the exact same microsecond. One feeder can show a modest phase A peak and a much larger phase C peak simply because the pole timing and trapped charge line up badly.

You should treat closing angle as a sweep, not as a single run. A useful set of cases includes several point-on-wave positions and trapped voltage states after previous de-energization. That approach will show the true upper bound of the event, which is the value that matters when you are checking insulation margins and load ride-through.

Switch models must represent prestrike restrike behaviour

Switch models must represent prestrike and restrike because real interrupters do not always move from open to fully closed in one ideal step. Contact approach, dielectric breakdown, and current interruption can create extra voltage steps that raise stress above the clean close shown by an ideal switch.

Vacuum and air interrupters can show very different signatures during capacitor switching. A bank that looks acceptable with an ideal breaker can produce a harsher waveform once prestrike is added, because the capacitor starts to charge before mechanical contact seals. Another case can show restrike during opening, which means the study should not stop at energization if field records show complaints during both close and trip operations.

This matters most when you are testing protection pickups, surge arrester duty, or insulation coordination margins. An ideal switch is still useful for screening, but final settings and final mitigation checks need the switch behaviour that matches the breaker technology installed in the yard.

Mitigation should be tested at every affected bus

Mitigation works only when it reduces the crest and ringing at the buses that actually host sensitive equipment. A fix that looks good at the capacitor terminals can still leave a higher peak at a drive bus, transformer tertiary, or remote control panel.

A typical industrial feeder shows this clearly. A reactor at the bank may cut local inrush current well, yet a long cable to a process line can still see reflected overvoltage if the switching sequence is poor. You should test each measure at all affected observation points, then compare the worst remaining crest, oscillation frequency, and decay.

  • Current limiting reactors reduce peak inrush current and shift the oscillation to a lower frequency.
  • Controlled closing narrows the range of breaker angles that produce the highest stress.
  • Switching order matters when one energized bank can feed the next close through a short bus path.
  • Surge arresters should be checked at the buses where reflected peaks actually appear.
  • Damping elements must be sized from waveform results rather than from steady-state ratings alone.

That process answers the common question of how to reduce switching overvoltage with evidence instead of habit. You’re checking the full surge path from source to affected bus.

Study results should guide switching timing policy

A capacitor bank switching study earns its value when results become operating rules for timing, sequencing, and permitted system states.

“Good policy comes from the worst verified waveform, the buses that saw the highest stress, and the mitigation that held those values inside acceptable limits.”

One utility feeder may need a rule that blocks a second bank close until the first bank is settled and a reactor is in service. Another plant may need a fixed sequence that keeps a long cable bus off line during capacitor energization. Those rules are simple, but they only stay credible when they come from waveform evidence instead of a generic switching note.

That is where a disciplined model pays off. SPS SOFTWARE fits this work because you can trace the physical path of the transient, inspect the assumptions, and turn a capacitor bank switching study into a clear operating practice that keeps routine switching from becoming a recurring source of trips.

Engineer sizing STATCOM and FACTS reactive power compensation at a whiteboard
Power Systems

Sizing reactive power compensation with STATCOM and FACTS models

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

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.

When you compare these devices What you should expect in service
A deep voltage dip reduces the available bus voltage. A STATCOM will usually keep stronger reactive current than an SVC during the same dip.
A site needs support during the first moments after fault clearing. A STATCOM will usually recover the bus more firmly because its control action is less tied to bus voltage.
A bus sees routine voltage regulation without severe disturbances. An SVC can still be a suitable choice if the normal operating range is the main concern.
A weak grid exposes interaction between compensation and plant controls. A STATCOM will usually give you more tuning flexibility for that control problem.
A project team compares only steady state MVAr ratings. The comparison will miss the low-voltage performance difference that often decides the final outcome.

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.

Engineer reviewing harmonic frequency-scan impedance plots on dual monitors
Power Systems

Harmonic resonance studies for grids with many inverters

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

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.

Scan pattern Practical reading
A tall narrow peak appears near the 5th or 7th harmonic. A small current at that frequency will create a large voltage rise.
A peak appears only when a capacitor bank is closed. The switching state is setting the resonant point and needs its own case.
Several nearby peaks show up across higher harmonics. Cable capacitance, filters, or converter detail are shaping the response.
The utility bus looks calm while an internal bus spikes. Local resonance exists inside the plant and external measurements will miss it.
A peak shifts after a new feeder or inverter block is added. The network change has altered impedance enough to revisit mitigation.

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.

Engineers planning a black start restoration sequence over network diagrams
Grid

Black start and system restoration studies for modern grids

Key Takeaways

  • Black start studies have value only when the switching sequence is tested against weak island behaviour.
  • Transformer inrush and motor pickup set the practical limits on early restoration steps.
  • Operator playbooks should use transient pass criteria so field actions match studied system response.

Black start restoration works only when you test the transient steps as well as the steady path.

Restoration plans can look sound on a one-line diagram and still fail during the first few switching actions after a blackout. United States electricity customers were without power for an average of 5.5 hours in 2022 when major events were included, which shows why power system restoration has to be more than a checklist. A black start study has value only when it reflects how voltage, frequency, transformer flux, and motor pickup will behave on a weak island. You need a restoration path that remains stable when the first devices close and after the system settles.

Modern grids make that standard more important because restoration sources are often smaller relative to the network they must energize. Long lines, lightly loaded transformers, inverter controls, and cold load all press on the same limited voltage support margin. Safe sequencing comes from transient study work that checks each closure, each load block, and each control response in the order operators will actually use.

A black start study maps the restoration path after blackout

A black start study defines how generation, transmission, and load will be restored after a system collapse. It identifies the starting source, the order of switching, and the conditions that must be met before each step. You can treat it as an operating map that crews can follow during restoration.

A common case starts with a unit that can self-start, picks up its own auxiliaries, energizes a nearby bus, and then charges a transmission line toward the next source or substation. That sequence sounds simple until reactive charging raises voltage on the open end or a station service transformer pulls heavy inrush from a small island. The study has to show both the path and the electrical strength behind the path.

That detail matters because restoration crews don’t need a generic answer to what a black start study is. You need to know which source starts first, which line closes next, which load stays blocked, and what failure signs stop the sequence.

“Good studies answer those points in operating terms, so the plan will still hold when the system is weak and unsettled.”

Weak islands need strength checks before each energization

You energize a weak island safely only after checking source stiffness, reactive reserve, and control response at the next switching point. A bus that looks healthy at no load can collapse with one transformer or feeder closure. Each restoration step needs its own strength check.

Picture a single hydro unit holding a remote bus after a blackout. The voltage is acceptable with no load connected, yet the next action is a long line energization toward a substation with several unloaded transformers. That closure can push the island into overvoltage first and undervoltage seconds later when magnetizing current and control lag appear. Stable islands are judged by how much disturbance they can absorb while holding control through the event.

Source impedance, automatic voltage regulator limits, governor response, and local reactive devices all shape that margin. Short circuit level also matters because protection and control assumptions can break when fault current is low. A weak island isn’t unsafe because it is small. It becomes unsafe when the next energization is larger than the island’s ability to control voltage and frequency through the transient period.

Restoration sequencing should follow voltage support margins

Black start sequencing steps should be set by voltage support margin at each stage of restoration. The next action is the one the island can carry without losing control of voltage or frequency. Geographic order helps operations, but electrical margin must lead the sequence.

Consider a corridor with two substations and a pump load at the far end. Closing the far line first might restore more territory on paper, yet charging current can consume the margin needed to pick up the next transformer. A better sequence closes the shorter section, brings in local reactive support, and then moves outward once the island has a firmer voltage base. That approach often feels slower, but it prevents early rollback.

Restoration checkpoint What operators should confirm before the next step
Start with the black start source The source can hold station service voltage and frequency without hunting or hitting reactive limits.
Charge the first transmission section Line charging will not push the receiving bus beyond the acceptable voltage band.
Energize the first transformer Magnetizing inrush will stay within the island strength and protection settings available at that moment.
Pick up the first load block Motor starting current and cold load will not force a frequency dip that trips generation or protection.
Add the next source or tie point Control modes, phase angle, and voltage targets are aligned before synchronizing the island.

Power system restoration after blackout works best when the sequence reflects those checkpoints instead of a fixed route. Operators then know why a step is early, delayed, or blocked. That makes the plan usable under stress, because each action is tied to a measurable electrical condition rather than habit.

Transformer inrush defines early energization risk during restoration

Transformer inrush defines early energization risk during restoration

Transformer inrush is one of the first large transient stresses in system restoration, and it will set the safe order of energization. The current spike depends on residual flux, source impedance, breaker timing, and transformer design. Weak islands feel that stress immediately through voltage dip and control interaction.

Take a substation transformer that sat de-energized through a prolonged outage. Residual core flux can add to the new applied flux and push the core deep into saturation on the first half cycle. The source then sees a current surge several times rated current while the bus voltage sags. Protection might restrain correctly, yet the generator voltage regulator and nearby motor controls can still react badly to the dip.

That is why modelling transformer inrush during restoration is more than a detail for specialists. If the study ignores residual flux and source weakness, the plan will overestimate how many transformers can be closed early. Practical sequencing often spaces transformer energizations, changes which side is energized first, or waits until a second source is online before closing a large bank.

Motor pickup shapes how quickly load can return

Motor pickup sets the pace of load restoration because starting current and torque recovery pull directly on island frequency and voltage. A feeder that looks modest in megawatts can still be a poor first choice if it contains many large motors. Load size alone won’t tell you that risk.

A water treatment plant is a good example. Several pumps can attempt near-simultaneous restart when the feeder returns, even if operators intend a staged process. The island then sees a steep current rise, a frequency dip, and slower motor acceleration that extends the stress. Voltage-sensitive contactors on smaller loads might drop out and reclose, which stretches the disturbance beyond the initial pickup.

You get a better answer when the study groups load by motor content, restart logic, and feeder location. Some blocks should return only after a second source is synchronized or after local capacitor banks are available. Cold load pickup matters too, but motor behaviour usually decides the first few restoration successes or failures because it hits both frequency and voltage at once.

System restoration simulation must capture each switching transient

System restoration simulation has to reproduce the switching events that operators will execute, step by step and in time order. Steady studies are useful for the broad path, yet they won’t show transformer saturation, control lag, or motor acceleration. Restoration risk lives in those transients.

That means you need models for breaker actions, source controls, transformer magnetizing behaviour, feeder composition, and protection logic that can affect the sequence. A useful study closes one line, lets the waveforms settle, then closes the next device under the new conditions. When teams use SPS SOFTWARE for this work, the value comes from seeing how each physical model responds before the next action is approved.

That level of simulation also sharpens operator judgement. If a bus survives only when a tap changer is blocked, or when a motor block is delayed, the playbook can say so clearly. You aren’t asking the plan to guess the system state. You’re asking it to reproduce the sequence closely enough that the field steps match the studied electrical response.

Modern grids require restoration plans that include inverter controls

Modern restoration plans must account for inverter controls because many restored islands now include battery and renewable sources with current limits and different voltage control behaviour. Conventional assumptions about spinning machines won’t carry over cleanly. Control mode selection will shape which restoration steps are safe.

Renewables supplied about 30% of global electricity in 2023, which shows how often restoration studies will face inverter-based resources rather than only synchronous units. A battery unit set to support voltage can hold a bus well during light charging, then hit a current limit when a transformer closes and lose voltage control abruptly. Another unit following grid angle might perform well only after a stronger source has already established the island.

You need those control assumptions written into the restoration sequence, not left as generic resource labels. Grid-forming settings, reactive priority, protection thresholds, and recovery logic should all be tested against the exact switching order.

“Modern black start planning is no longer just about which source exists. It is about which control behaviour exists at each stage of the rebuild.”

Operator playbooks need pass criteria from transient studies

Operator playbooks should convert each studied restoration step into a clear go or hold test. Pass criteria make the sequence usable under pressure because crews can judge voltage, frequency, and control response against pre-set limits. Restoration works best when every major closure has an electrical acceptance check.

A useful playbook will state the few checks that matter most before the next action:

  • Bus voltage remains inside the studied band after the previous step settles.
  • Frequency recovers to the studied target without sustained oscillation.
  • Reactive reserve remains available at the active source.
  • Protection and control blocks required for the step are confirmed.
  • The next transformer or load block matches the studied switching order.

Those criteria turn a restoration study into a disciplined operating tool. They also show why plans built on steady assumptions break once inrush and motor pickup strike a weak island. SPS SOFTWARE fits this stage well because the transient study results can be traced back to specific switching actions and model assumptions, which gives operators firmer ground for each closure and each hold point.

Engineer probing a converter half bridge with an oscilloscope
Power Electronics|Power Systems

5 Gate driver and dead time effects that shape converter behaviour

Key Takeaways

  • Gate driver timing is part of the power stage, so delay mismatch and gate current will shape losses, distortion, and stress before control software responds.
  • Dead time should be set from worst case delay spread, then corrected with compensation for the voltage bias it introduces under load.
  • Timing models that include the full path from driver to device will cut bench iteration and produce safer first hardware settings.

Dead time and gate drive timing will decide how a converter behaves before software control can clean up the waveform.

Motor systems use about 45% of global electricity, so small timing errors inside their converters deserve early design attention. A clean schematic and a stable control loop will not rescue a half bridge that turns on too early or too late. Gate driver strength, propagation delay, and dead time shape voltage error, heat, and device stress long before you start bench tuning. You will get better hardware faster when you treat those settings as part of converter design rather than a final trim step.

Gate driver timing sets converter behaviour before control loops act

Gate driver timing sets the converter’s physical switching sequence, and that sequence fixes what the power stage can do in each cycle. Turn on delay, turn off delay, and gate current define when current commutates. Control software acts later. If the hardware timing is poor, the waveform is already compromised.

A simple half bridge shows this clearly. If the high side device turns off 40 ns later than expected and the low side turns on 20 ns earlier, the overlap is enough to raise cross conduction risk even if your PWM duty cycle is mathematically correct. A motor drive will then show extra heating, noisier current, and a rougher line-to-line voltage than the controller commanded.

  • Dead time shifts average phase voltage.
  • Delay mismatch raises cross conduction risk.
  • Weak gate drive increases switching loss.
  • Extra blanking extends diode conduction.
  • Timing spread breaks one fixed setting.

Those effects are often tuned late because the converter will still run at light load. That bench habit hides the fact that timing is part of the power stage itself. You’re not adjusting polish. You’re setting the physical order and duration of events that determine current path, voltage error, and thermal stress on every switching edge.

Dead time shapes output voltage across each switching interval

“Dead time inserts a small blank interval, but that blank interval changes the average phase voltage every switching period.”

Current keeps flowing while both devices are off, so it commutates through a diode or channel path that was not part of the commanded PWM state. The result is a predictable voltage error.

A low voltage inverter feeding an inductive load makes the effect easy to see. During positive current, dead time after the high side turns off forces current through the low side diode, so the phase node stays lower than the ideal PWM command. Reverse the current direction and the sign of the voltage error flips, even if duty cycle stays the same.

That is why dead time affects a converter most strongly near zero crossings and at low modulation index. The commanded duty cycle can be accurate while the applied voltage is biased every cycle. Current controllers then work harder to correct an error created in hardware, and the correction often appears as distortion, acoustic noise, or uneven torque.

Short dead time raises cross-conduction risk

Short dead time reduces voltage error, but it will raise cross-conduction risk if device turn-off is slower than expected. The unsafe case is not the nominal delay on a datasheet. The unsafe case is the slowest turn-off event across temperature, current, gate resistance, and part variation. That margin must be covered.

Consider a 400 V bridge leg where the upper device has a typical turn-off delay of 60 ns at room temperature. Add a hotter junction, a little more gate resistance from layout, and a slower lot of devices, and that event can stretch far enough that a 50 ns dead time becomes a direct overlap condition. The PWM command did nothing wrong, yet the leg still sees cross conduction current.

Cross conduction and dead time are linked through uncertainty, not just nominal timing. You’re sizing a guard band around the slowest off event and the fastest on event. Lab failures often happen after a load step or thermal soak because those conditions move both delays, and a setting that looked safe at start-up no longer covers the spread.

Long dead time extends body diode conduction

Long dead time extends body diode conduction

Long dead time keeps overlap away, but it also forces current through the diode path for longer than necessary. That raises conduction loss, increases reverse recovery stress in many topologies, and distorts the applied voltage. The penalty grows with current and switching frequency. Safe timing still needs to stay tight.

A traction inverter phase leg under heavy current shows the tradeoff quickly. Add a few hundred nanoseconds of extra blanking and the diode carries current longer on every edge. Junction temperature rises, the phase voltage flattens around transitions, and current ripple can climb even though the control law and bus voltage have not changed.

Long dead time also hides weak gate driver design. Some teams add blanking to stop occasional overlap, but the better fix is often cleaner layout, lower loop inductance, or a gate current profile that turns the device off with more certainty. Extra dead time is useful as insurance, yet too much of it taxes every cycle and every ampere.

Gate drive current sets switching loss during transitions

Gate drive current determines how quickly the device moves through its linear region, and that directly sets switching loss. Faster transitions cut overlap between voltage and current, but they also raise dv/dt and di/dt. Slower transitions reduce electrical stress on some nodes while heating the switch. You’re always trading one limit against another.

A bridge leg that uses a large gate resistor often looks calm on a scope, but the calm edge comes with a longer Miller plateau and more energy burned each turn on and turn off. Another design with a very small resistor switches sharply, then starts to show ringing and false triggering through common source inductance. Gate driver design basics always come back to that balance.

Wide-bandgap semiconductors can reduce power losses by up to 90% in some power conversion stages, which makes timing discipline even more important because transitions are much faster. Dead time selection, gate resistance, and layout can’t be guessed when edge speeds rise. You need settings that match the device physics and the commutation loop.

Dead time targets must cover delay spread

Dead time should cover the full spread of turn-off and turn-on delays, not just a typical number from one operating point. Temperature, bus voltage, current direction, gate resistance, and isolated driver skew all move the timing. A usable target is the smallest blanking interval that still protects the slowest switching case.

A good bench process starts with measured or modelled delay stacks. You add driver propagation delay mismatch, device turn-off spread, and layout-related variation, then keep a modest safety margin. That approach is much more stable than copying 500 ns from an old design that used a different device family and a different current range.

What you check What the timing must include What the chosen dead time protects
Driver propagation delay mismatch between channels The slowest off-channel and the fastest on-channel must both be counted. The setting keeps overlap away when one side responds earlier than the other.
Device turn-off spread across temperature Hot devices and high current cases need more margin than room temperature samples. The setting stays safe after thermal soak instead of only at start-up.
External gate resistance and loop parasitics The effective gate current at the device matters more than the nominal resistor value. The setting covers slower discharge caused by the physical layout.
Current direction at commutation Diode recovery and channel takeover timing will differ with current polarity. The setting avoids overlap in both current quadrants rather than one.
PWM frequency and required waveform quality The blanking must stay small enough that voltage error does not dominate each cycle. The setting protects the devices without adding avoidable distortion and loss.

Dead time compensation restores commanded voltage under load

Dead time compensation corrects the average voltage error created by blanking, so the load sees something closer to the commanded waveform. It does not remove the need for safe timing. It subtracts the predictable bias after you have chosen a dead time that prevents overlap across operating conditions.

A current sign-based compensator is a common starting point. Positive phase current gets one correction polarity, negative current gets the opposite, and the magnitude reflects blanking time and bus voltage. That simple method works well in many motor drives because the voltage error changes sign with current direction and stays roughly proportional to dead time.

Compensation gets more trustworthy when you’ve already modelled the timing chain and current paths carefully. Teams using SPS SOFTWARE can inspect the gate drive sequence, the commutation path, and the resulting phase voltage in one place, then tune the correction against a transparent model rather than guessing from a noisy bench waveform. That makes dead time compensation explained in control code line up with what the switches are actually doing.

“Converters run clean when timing is designed, checked, and compensated before the first prototype forces the lesson.”

Timing simulation should include delays from driver to device

Timing simulation is only useful when it includes the whole path from PWM command to device current commutation. Driver delay, isolation skew, gate resistance, threshold spread, Miller behaviour, and parasitic inductance all matter. A simplified ideal switch model will hide the exact problems dead time is meant to control.

A useful setup starts with one bridge leg and a representative inductive load. You apply the intended PWM, sweep temperature and gate resistance, and inspect gate voltage, drain or collector current, and phase node voltage through each transition. That kind of study will show where overlap appears, where diode conduction lasts too long, and how much compensation your control law should apply.

That is why disciplined timing work belongs near the start of converter design and not at the end of bench debug. SPS SOFTWARE fits that workflow because it lets you inspect transparent switching models and set dead time from physical evidence instead of habit.

Engineer reviewing EMT fault ride-through waveforms on screen
Grid

EMT studies for grid code compliance of renewable plants

Key Takeaways

  • Grid code compliance for renewable plants now rests on disturbance evidence that shows how the submitted controls behave during faults and through recovery.
  • System strength and inverter interaction determine when phasor studies stop being enough and when EMT modelling becomes necessary for grid integration review.
  • Connection studies move faster when the model, the fault cases, and the pass statements are all traceable to the same technical assumptions.

Grid code compliance for renewable plants now depends on EMT evidence that shows fault ride through and recovery clearly.

Connection reviews used to lean on phasor studies, plant data sheets, and high-level control descriptions. That standard has shifted because inverter-based plants can react within milliseconds, and those fast control actions decide if a unit stays connected or trips during a disturbance. Renewables supplied about 30% of global electricity generation in 2023. As that share grows, grid integration study requirements become more detailed, and grid operators expect proof that a specific plant will ride through faults on its actual network.

Grid code compliance requires disturbance performance evidence

Grid code compliance means proving that your plant stays connected and behaves within stated limits during defined network disturbances. Reviewers want evidence of voltage support, current injection, protection coordination, and stable recovery. A compliance filing is accepted when those responses are shown against the code clauses that apply at the point of connection.

A solar plant connected to a 132 kV bus gives a clear example. The operator will not stop at a generic statement that the inverter supports low voltage ride through. You will need plots that show terminal voltage, current, reactive response, active power, and protection status during a fault with a stated clearing time. Those traces answer the practical question behind every renewable plant connection study.

This matters because grid code language is written around plant behaviour under stress, not around component marketing claims. Manufacturer certificates help, but they don’t prove site-specific performance when transformer impedance, collector layout, and plant controls interact with a weak grid. If you’re asking what grid code compliance is in practice, it is disciplined proof that the submitted plant model survives the disturbances the operator cares about.

System strength sets the study depth for connection

System strength at the point of interconnection sets how detailed your study must be. Strong systems often tolerate simpler representations for some checks. Weak systems expose fast control interactions, so reviewers will expect EMT work that resolves converter behaviour and network response without averaging away the important detail.

A short circuit ratio near 2.5 at a remote substation puts a renewable plant in a very different position from a plant tied to a stiff transmission node. Solar accounted for 59% of new U.S. utility-scale generating capacity added through the first 8 months of 2024. That growth means more inverter-based projects are connecting at locations where system strength is limited and study depth becomes a connection issue.

You’ll usually see this show up in model review comments. Reviewers ask for nearby inverter plants, equivalent source detail, transformer taps, and line data because those items shape control stability during faults. A plant that looks compliant on a strong source can struggle when the same controls face a weak Thevenin equivalent. Grid integration work starts with this question because it determines the study method, the model detail, and the size of the test matrix.

Phasor studies miss inverter responses that operators now review

“Phasor studies average fast electrical behaviour, so they can hide PLL instability, current limit transitions, dc-link recovery, and protection blips that decide acceptance.”

Grid operators review those millisecond responses directly because they affect fault ride through, control stability, and post-fault power recovery at the point of interconnection.

A common failure path looks harmless in a phasor result. The plant voltage dips, reactive current rises, and the unit appears to stay online. The EMT run tells a harder story: current priority shifts twice, the plant controller saturates, the phase angle estimate wobbles, and a protection pickup occurs for a few cycles. That gap explains why phasor results no longer satisfy many renewable plant reviews.

What reviewers need to confirm Why EMT evidence matters
Voltage collapse depth and clearing sequence must match the actual fault case. Millisecond timing affects controller saturation and trip logic in ways averaged models won’t show.
Reactive current response must follow the plant’s submitted control settings. Detailed transient plots reveal current priority, limiters, and recovery delays at each stage of the event.
Protection must remain coordinated through temporary current spikes. Short pickup intervals can appear only in EMT traces and still decide if the plant disconnects.
Nearby inverter plants can affect stability during weak-grid disturbances. Network interaction between converters is resolved directly instead of being absorbed into simple equivalents.
Post-fault active power return must stay within code and system limits. Recovery overshoot and damping are visible only when the control loops are represented with enough detail.

That missing detail adds permitting friction. A reviewer who sees only averaged response will ask for another model run or a control clarification before the study can move ahead. You save time when the first submission shows the transient mechanism behind the pass result.

EMT simulation shows fault ride-through in detail

EMT simulation proves fault ride-through when it reproduces the full disturbance sequence and the plant’s response in milliseconds. You can see voltage depression, current injection, current limiting, breaker clearing, and the first moments of recovery on the same time axis. That is the level of detail reviewers use to judge compliance.

A useful test case applies a single line-to-ground fault at the remote end of the line for 150 ms. The run should show point of interconnection voltage, phase currents, active power, reactive power, and an internal signal such as dc-link voltage or controller output. A battery-coupled plant needs similar treatment because ride-through behaviour depends on how the control layers share current and restore power.

The main value of this approach is traceability. Each case can be tied to a grid code clause, a network condition, and a pass or fail statement. If you’re building an EMT study for grid code review, the work is not just about producing waveforms. It is about showing the exact disturbance, the exact control response, and the exact reason the plant remains inside the operator’s limits.

A credible EMT model reflects plant controls faithfully

A credible EMT model reflects plant controls faithfully

A credible EMT model matches the actual converter, plant controller, and protection logic with traceable parameters and clear limits. Reviewers need to see how the model produces its response. Hidden logic or missing control details weaken the study because no one can verify why a waveform looks acceptable.

A useful model includes the inverter current regulator, phase tracking, plant-level reactive control, voltage droop, fault current priority, and protection thresholds. Teams using SPS SOFTWARE often build this transparency into the workflow so controller blocks, equations, and parameter values can be checked directly instead of treated as a sealed object. That matters when a reviewer asks why reactive current clipped at a certain level or why active power resumed after a set delay.

Validation is the step that gives the model weight. Factory tests, commissioning records, or benchmark responses should align with the simulated behaviour before the connection package is filed. You’re not proving that a generic inverter class can pass. You’re proving that your plant, with your settings and your network, behaves as submitted when the grid becomes severe.

Post-fault recovery often decides compliance outcomes

“Passing the fault period isn’t enough; operators also judge how the plant recovers voltage, current, and power after clearing.”

Recovery that is too slow, too abrupt, or poorly damped can violate code even if the plant never disconnects. Many borderline cases fail here rather than during the voltage dip itself.

A plant can hold through a three-phase fault and still create a new problem 300 ms later. Active power might surge back before the voltage regulator settles, causing a temporary overvoltage at the point of interconnection. Another case shows the opposite issue: the reactive support collapses too soon, the phase lock takes extra cycles to settle, and the plant drifts into oscillation before normal dispatch resumes.

You’ll want to assess ramp rates, current limit release, plant controller handoff, and damping in the first seconds after clearing. Those details connect directly to how operators think about system security. Fault ride-through simulation for renewables is only convincing when it shows the full event, including the recovery path that follows a successful stay-connected response.

Grid operator review depends on clear transient evidence

Grid operator review depends on clear transient evidence that is repeatable, traceable, and tied to each code requirement. Raw simulation output isn’t enough. Reviewers need to connect every plot to a defined case, a model version, and a specific compliance question before they will accept the result.

Study packages often run into trouble because the plots are technically correct yet hard to audit. Time scales shift from figure to figure, fault locations are described loosely, and controller settings sit in a separate file with no clear link to the run. You can avoid that confusion when the submission package stays consistent from case definition through final pass statement.

  • A network case that matches the submitted interconnection data
  • A model version record tied to the exact simulation runs
  • Fault definitions with location, duration, and clearing sequence
  • Plots that align voltage, current, power, and key internal states
  • Pass statements mapped to each applicable grid code clause

This level of discipline shortens technical back-and-forth. It also makes the renewable plant connection study easier to reuse when settings are updated or a new operating case is added. You’re giving the reviewer a chain of evidence, not a stack of screenshots.

Common modelling gaps cause avoidable connection study delays

Most connection study delays come from missing control detail, weak network assumptions, and evidence that does not answer the review question directly. A study moves faster when each case can stand up to technical challenge. Clear modelling discipline matters more than polished graphics or long narrative sections.

Typical gaps are familiar. A submitted model omits the plant controller and only includes inverter-level control. The transformer tap in the study case doesn’t match the latest design package. The grid equivalent is too stiff, so the fault looks easier than the site conditions the operator expects. Each mistake forces another review cycle because the result can’t prove grid code compliance with confidence.

The stronger path is simple and exacting. You need open model structure, traceable parameters, and disturbance cases built around the code clauses that matter at your point of connection. SPS SOFTWARE fits that working style well because engineers can inspect model behaviour instead of treating it as a black box. That kind of clarity won’t remove the hard questions in a review, but it will make your answers precise, consistent, and technically defensible.

Engineer studying transformer magnetization curves at a desk
Power Systems

Modelling transformer inrush current and energization transients

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

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.

System condition What the energization study will usually show
Strong source close to the transformer terminals The first inrush crest will usually be larger because the terminal voltage stays high while the core saturates.
Weak source behind higher series reactance The current peak will usually fall, but the waveform can remain distorted for longer as the transient decays.
Long feeder or cable between source and transformer The added impedance will reduce the immediate peak and can shift what protection sees at upstream locations.
Series reactor ahead of the transformer The reactor will limit the crest current and reduce mechanical stress, but it will also change voltage recovery.
Alternate energization path during commissioning A temporary source arrangement can produce a very different inrush result from the permanent operating configuration.

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.

Two engineers inspecting a power converter board under magnifiers
Power Electronics|Power Systems

4 Differences between silicon carbide and silicon MOSFETs in simulation

Key Takeaways

  • Silicon carbide shows its strongest simulation advantage when high voltage and switching loss dominate the converter loss map.
  • Matching gate drive, parasitics, thermal limits, and timing matters more than headline material claims during device comparison.
  • Converter duty cycle ties the main model differences to the final device choice because it sets how often each loss mechanism appears.

Accurate simulation will tell you when a silicon carbide MOSFET earns its place and when a silicon power MOSFET remains the better choice.

Wide bandgap devices can cut power conversion losses by as much as 90% in some applications, which explains why the silicon carbide MOSFET gets so much attention. That headline gain also sets a trap. A simplified model will overstate the benefit, especially when gate resistance, nonlinear capacitance, and junction heating sit outside the study. You need matched conditions before a silicon carbide versus silicon MOSFET result deserves trust.

Silicon carbide fits high-frequency converters with tight loss limits

A silicon carbide MOSFET fits converters where switching loss, bus voltage, and magnetic size set the limit. It performs best in hard-switched or high-frequency stages above a few hundred volts, where silicon devices burn more energy during overlap between voltage and current and during repeated capacitance charging.

An 800 V power factor correction stage running at 100 kHz shows the pattern clearly. Silicon carbide’s critical electric field is roughly 10 times higher than silicon, which allows thinner high-voltage regions and lower resistance in the same voltage class. That material advantage turns into lower simulated loss only when the gate loop and bus inductance reflect the converter you’re actually building.

Frequency alone won’t settle the choice. A 650 V inverter with soft switching can leave less to gain than a 400 V hard-switched boost stage. The useful question is simple: does switching energy dominate your loss map? If it does, a SiC MOSFET will usually repay the extra modelling effort.

Matching test conditions come before any device comparison

Any silicon carbide versus silicon MOSFET study will mislead you unless voltage, current, gate drive, thermal boundary, and parasitics stay matched. Device comparisons fail most often when one model uses default values and the other reflects bench conditions.

“Matching inputs matters more than picking a detailed symbol.”

Lock these five items before you compare parts, or your loss plot won’t mean much.

  • Use the same bus voltage and current waveform for both devices.
  • Set identical gate driver voltage and external gate resistance.
  • Keep loop inductance and stray resistance consistent.
  • Apply the same heat sink and ambient temperature assumptions.
  • Match dead time and the simulation time window.
Checkpoint What stays matched What goes wrong if it drifts
Gate drive conditions Driver voltage, resistance, and source path stay the same for both parts. One switch can look efficient only because it was given an easier turn on or turn off.
Bus parasitics Loop inductance and wiring resistance reflect the same physical layout. Ideal wiring hides overshoot and ringing that fast devices will create on hardware.
Thermal boundary Heat sink, interface resistance, and ambient temperature remain identical. A cooler junction in one model skews conduction loss and safe operating margin.
Load point Bus voltage, current shape, and power level remain fixed during the test. Light-load runs flatter parts that lose ground once current rises.
Dead time Commutation timing stays equal in each leg. Unequal dead time moves diode conduction loss from one device to the other.
Measurement window Both models are averaged over the same settled operating cycles. Short windows can hide heating and capacitance energy that builds over time.

SPS Software helps keep that comparison honest because you can inspect the electrical and thermal assumptions instead of hiding them inside a fixed device block. That matters when a few ohms of gate resistance or a few nanohenries of loop inductance decide the result.

Gate behaviour sets most simulated switching loss results

Gate behaviour decides how fast current rises, how long voltage remains high during turn on and turn off, and how much ringing follows. A silicon carbide MOSFET often looks spectacular in simulation until realistic gate resistance, Miller plateau effects, and source inductance slow the transition.

A 650 V half bridge makes this plain. Set the SiC device with a low gate resistor and an ideal driver, and switching energy falls sharply. Add common source inductance, finite driver current, and separate turn on and turn off resistance, and the advantage narrows to the level you’ll actually see on a board.

The problem isn’t that silicon carbide underperforms. The problem is that gate models are often too kind. Fast edges raise dv/dt, which pushes current through Miller capacitance and can disturb the opposite switch. If you’re modelling a power MOSFET for converter selection, the gate loop is one of the first places to spend effort.

Output capacitance shifts voltage stress during fast edges

Output capacitance shifts voltage stress during fast edges

Output capacitance shapes switching energy, overshoot, and the amount of stored energy that must move during each transition. A silicon carbide MOSFET usually carries lower capacitance at high voltage, but the important detail is its strong nonlinearity. A fixed capacitor value won’t represent that behaviour well enough.

A boost leg at 600 V exposes the issue. Use a constant Coss value from a small-signal table, and the simulated drain voltage slews too smoothly. Use an energy-based or voltage-dependent capacitance model, and you’ll see sharper slope changes, different snubber stress, and a more believable turn off waveform.

That detail matters because capacitance loss repeats every cycle. It also feeds ringing with stray inductance, which affects voltage margin and electromagnetic noise. If your converter uses clamp networks or relies on zero-voltage switching, output capacitance modelling will move the answer more than a tiny change in on-state resistance.

Reverse recovery shapes commutation loss in hard switched legs

Reverse recovery decides how much extra current appears when current transfers from one device path to the other. Silicon carbide parts usually reduce this penalty, while many silicon MOSFETs pay a larger charge extraction cost through the body diode or a companion diode during hard commutation.

A two-level inverter leg gives a clear example. Current freewheels through the lower path during dead time, then the upper switch turns on and must clear stored charge before voltage rises cleanly. If the model omits reverse recovery, the turn-on spike shrinks, the loss estimate falls, and the current stress looks gentler than it will be.

You can’t judge this section from diode charge alone. Dead time, current direction, and junction temperature all shift the result. Hard-switched bridges punish weak commutation behaviour quickly. That is why a silicon device can look fine in a conduction-focused study, then lose ground once you add full transition physics.

Thermal limits decide if efficiency gains survive full load

Thermal limits decide if a simulated efficiency gain survives full load because junction temperature changes resistance, switching energy, and safe operating margin. A cooler device on paper often turns hot once pulse loss, package resistance, and heat sink limits are coupled into the same model.

A 30 kW converter on a shared cold plate shows the risk. At light load, both devices can appear comfortable. Push the model to rated current and include transient thermal impedance, and the hotter switch slows down, loses conduction margin, and can force derating long before the average efficiency number looks alarming.

Steady-state thermal resistance alone won’t protect you here. Cycling duty, startup surges, and uneven leg loading create temperature swings that a single fixed junction value hides. You’re trying to pick a device that stays reliable under stress, so the thermal network must sit inside the switching study, not beside it.

Lower voltage converters still reward strong silicon MOSFET models

Lower-voltage converters often reward strong silicon MOSFET models because conduction loss, package parasitics, and costed gate drive effort outweigh the switching gain of silicon carbide. A SiC MOSFET is not the automatic answer in 48 V, 80 V, or 100 V classes where current is high and voltage is modest.

A 48 V bidirectional converter used for battery buffering is a good test case. The main loss can sit in channel resistance, copper paths, and dead time rather than in high-voltage switching overlap. A modern silicon power MOSFET with low on-resistance and a well-modelled package can outperform a poorly chosen wide bandgap part in total converter loss.

You’re also less likely to need the extreme dv/dt that makes silicon carbide attractive at higher bus voltage. That shifts the design focus toward current sharing, thermal spreading, and package inductance. Good modelling still matters, just for a different reason. You’re checking conduction and thermal balance more than headline switching speed.

Converter duty cycle decides when a SiC MOSFET fits

Duty cycle tells you if a SiC MOSFET deserves the extra modelling burden and device cost. Long high-voltage switching intervals favour silicon carbide. Short low-voltage intervals favour silicon. It turns switching physics into a costed operating pattern you can compare.

“The right power MOSFET choice comes from matched electrical stress, not from material claims or isolated datasheet numbers.”

An 800 V power factor correction stage with frequent hard commutation usually rewards a SiC MOSFET. A 48 V synchronous buck that spends most of its time in conduction usually rewards a strong silicon model instead. Duty cycle links the four decisive simulation differences, because it sets how often gate charge, output capacitance, reverse recovery, and heat actually matter.

SPS SOFTWARE fits this work when you need that judgement to rest on transparent models rather than hopeful assumptions. If you can inspect the gate path, capacitance curves, and thermal network under the same operating point, the silicon carbide choice becomes a measured engineering call instead of a material preference.

Engineer inspecting a power electronics board at a test bench
Modelling

Building high confidence MOSFET models from manufacturer datasheets

Key Takeaways

  • A reliable MOSFET model starts with the converter stress case, not the headline values in the datasheet table.
  • Conduction, charge, and capacitance fitting should be handled in sequence so each parameter set keeps a clear physical role.
  • Trust comes from validation against the original test conditions and from clear limits on where the model has been checked.

A MOSFET model built straight from headline datasheet numbers will miss the losses and waveforms that matter in converter simulation.

Electric motor systems use about 45% of global electricity, which means converter errors don’t stay small once they reach long duty cycles and high power ratings. You need a MOSFET model that reflects the test conditions behind each published curve, not just a few catalogue values. That is the difference between a simulation that only looks plausible and one that supports thermal, efficiency, and control work. High confidence comes from disciplined fitting, not from copying a default MOSFET spice model and hoping the datasheet agrees.

A good workflow starts with the converter stress you need to study, then fits conduction and switching behaviour as separate problems. You’ll get better results when you treat charge and capacitance as voltage-dependent effects and validate against the same tests used in the MOSFET datasheet. That approach gives you a model you can trust inside its calibrated range and question outside it.

Datasheet models fail when test conditions stay hidden

A datasheet curve only describes a MOSFET under the exact bench setup used to measure it. Gate resistance, drain voltage, junction temperature, and stray inductance all shape the published result. Hidden conditions turn copied values into wrong waveforms, even when the MOSFET datasheet looks complete and the model parameters seem reasonable.

A switching plot is a good example. A turn-on time measured at 400 V, 20 A, and 10 Ω gate resistance will not match a converter leg running the same device at 250 V with a 2.2 Ω gate resistor. The curve still has value, but only after you tie it to the stated test circuit. Footnotes, axis labels, and small captions often carry more modelling value than the headline part table.

You’ll also see hidden assumptions around temperature and package parasitics. A transfer curve taken at 25°C can fit threshold behaviour well and still miss current at 125°C. A vendor model that follows one output curve can still fail on turn-off overshoot because the test fixture inductance was never represented. Reading a MOSFET datasheet for simulation means treating every published plot as a conditional result, not a universal truth.

Start with the converter stress that sets accuracy needs

The right MOSFET model starts with the stress case that matters most in your converter. Voltage swing, current level, switching speed, and junction temperature decide which datasheet curves deserve the most fitting effort. A synchronous buck and a hard-switched boost converter will punish different modelling errors.

A 48 V to 12 V synchronous buck usually needs tight low-voltage conduction fitting, because a few milliohms of error will shift efficiency and heat rise at full load. A 400 V boost stage needs stronger charge and capacitance fitting, because switching loss and node overshoot will dominate. Power electronics process more than 70% of the electricity generated in the United States, so model accuracy matters most where converters spend their time and losses.

  • Match bus voltage to the highest and lowest values the device will actually see.
  • Match current to the operating band that sets your thermal limit.
  • Match junction temperature to the condition used for design review.
  • Match gate resistance to the driver network in your schematic.
  • Match switching frequency to the loss mechanism you need to predict.

This priority list keeps the work focused.

“You’re not trying to make a universal MOSFET model on day one.”

You’re trying to build a model that stays faithful where your converter lives. Once that operating window is fixed, parameter choices stop feeling arbitrary and start serving a defined simulation goal.

Separate conduction fitting from switching fitting early

Conduction fitting and switching fitting should be treated as two linked but separate tasks. Channel parameters control current and on-state drop, while charge and capacitance terms control transition timing and energy. Mixing both problems too early makes it hard to see which parameter caused the mismatch.

Start with the steady-state side. Fit the on-state slope and threshold region using output curves, transfer curves, and on-resistance data at the target temperature. A low-voltage server supply gives a clear case, because the simulated drain current at 4.5 V gate drive must line up before you touch rise and fall time. That first pass sets the channel behaviour without the noise of switching parasitics.

Move to switching only after the conduction fit is stable. A common failure shows up when someone stretches gate charge values to force a better turn-on delay, then wonders why the DC current no longer matches the datasheet. You’ll save time if each parameter set has one main job. That separation also makes later validation easier, because each error points to a smaller part of the model.

Use output curves to lock in channel behaviour

Use output curves to lock in channel behaviour

Output curves are the most direct path to a trustworthy channel fit. They show how drain current responds to drain-source voltage across several gate voltages, which lets you set threshold, transconductance, and on-state slope with much less guessing. A good fit here will stabilize every later step.

Pick the gate voltages that overlap your use case instead of fitting every curve with equal weight. A 10 V gate-drive industrial inverter cares far more about the high-current region than the sub-threshold knee. A 4.5 V logic-level design cares about the opposite. The model should match the slope near the operating current, the saturation bend, and the low-voltage resistive region at the same time.

Temperature data matters here too. If the datasheet gives on-resistance against temperature, use it to scale channel conduction after the 25°C fit is complete. That extra step stops the model from looking perfect on one bench plot and failing during thermal sweeps. The checkpoint below helps map the main datasheet plots to the fitting task they should control.

Datasheet plot What it should control in your model
Output characteristics Use these curves to set channel current response across the voltage and gate-drive range you actually switch.
Transfer characteristics Use this plot to refine threshold and transconductance where small gate-voltage errors create large current errors.
On-resistance against temperature Use this relation to keep conduction loss believable during thermal sweeps and hot-load checks.
Gate charge curve Use this plot to shape delay, Miller plateau behaviour, and the timing of voltage and current overlap.
Capacitance against drain voltage Use this relation to model non-linear switching, node ringing sensitivity, and output capacitance energy.
Reverse recovery test Use this test only if the body diode or commutation path matters in your converter leg.

Use charge curves to shape switching behaviour

Gate charge curves are the cleanest way to shape switching behaviour once the channel fit is stable. They capture how the gate current is spent across threshold, Miller plateau, and final enhancement. Rise and fall times only make sense after that charge partition lines up with the datasheet test.

A double-pulse style switching event shows why this matters. If the simulated Miller plateau is too short, drain voltage will collapse too quickly and turn-on loss will look falsely low. If total gate charge is correct but the split between pre-plateau and plateau charge is wrong, the waveform will still miss delay and overlap. You need the model to spend charge in the same order as the device.

Keep the gate loop explicit during this step. The driver voltage, external resistance, and source inductance all shape the current available to charge the gate. A model that matches a datasheet switching plot with the wrong gate network won’t travel well into your converter. This is where many generic MOSFET spice model files look convincing on paper and fail in a half-bridge simulation.

Treat capacitance plots as voltage-dependent functions

MOSFET capacitances are strongly non-linear, so fixed values will distort switching energy and waveform shape. Input, reverse transfer, and output capacitance should follow the drain voltage shown in the datasheet plots. A voltage-dependent fit is required if you want credible turn-off loss, ringing tendency, and dead-time behaviour.

A 400 V switching node makes this obvious. Output capacitance near 20 V can be several times larger than it is near 300 V, so a single Coss value will misstate both stored energy and drain-voltage slew. Reverse transfer capacitance also shifts the Miller effect as Vds changes. That means the same device can look tame in one operating region and much slower in another.

Piecewise fitting is often enough. You don’t need a perfect analytical expression if three or four voltage regions reproduce the plotted capacitance and stored-energy trend. Many engineers also forget the impact on soft-switching intervals and body-diode commutation. Once capacitance is treated as a function instead of a constant, the model starts to carry its weight in converter simulation.

Validate the model against the exact datasheet tests

Validation only means something when the simulation recreates the same test used in the MOSFET datasheet. Match bus voltage, load current, gate resistor, temperature, and reference points before judging the result. That discipline turns curve fitting into model verification instead of a visual comparison exercise.

A useful workflow is to rebuild the published switching or output-characteristic test bench first, then run the device model through the same conditions. If a turn-off plot was measured with a clamped inductive load, the simulation should use the same arrangement and probe points. SPS SOFTWARE fits well here because editable model structure makes it easier to trace a mismatch back to charge, capacitance, or parasitic assumptions instead of hiding it inside a closed block.

“Look for the shape of the error, not only the peak value.”

A correct current peak with the wrong plateau duration means one problem. A correct delay with too much overshoot means another. Validation becomes much faster once each mismatch is linked to a specific physical effect. You’ll also build a record of what the model has already passed, which matters when someone reuses it in another converter study.

Know where the model stops being trustworthy

A high-confidence model is only trustworthy inside the voltage, current, temperature, and gate-drive range used to calibrate it. Outside that range, the same model becomes an estimate. Good engineering practice means marking those limits clearly and refusing to treat one successful fit as universal proof.

A model tuned for a 100 kHz hard-switched leg at 25°C will not automatically predict behaviour in a 20 kHz motor drive at 125°C with a different gate network. The output curves, charge fit, and capacitance fit still provide a strong base, but trust comes from declared bounds. You should write those bounds into the model notes so the next user knows what has been checked and what has not.

That is the standard worth keeping. Converter studies rise or fall on the credibility of the device model inside them, and careful parameter work is what turns a MOSFET datasheet into something useful. SPS SOFTWARE supports that kind of work best when you need open, inspectable models that let you see why a waveform matches, why it misses, and where the model should stop speaking with confidence.

1 2 3 9 10
Cart Overview