123 Main Street, New York, NY 10001

Motor / Inverter Isolation Stack: Driver + ΔΣ + Bias

← Back to: Digital Isolators & Isolated Power

In motor/inverter systems, isolation only “works” when the gate driver, ΔΣ sensing chain, and isolated bias are co-designed as one deterministic stack under worst-case dv/dt and fault energy. The goal is simple: truthful sensing + predictable protection timing + repeatable production evidence—so field behavior matches lab results.

System Context & Boundary (Motor / Inverter Isolation Stack)

Context — why this stack is hard

Motor inverters combine extreme dv/dt at the switching node with high fault energy; the isolation stack must keep sensing truthful while making protection deterministic.

  • dv/dt injection couples through parasitics and the isolation barrier, creating false triggers, false measurements, or logic upset.
  • Fault events (short-circuit / desaturation / shoot-through) compress time budgets; microseconds decide device survival.
  • Co-design requirement: isolated gate driver, isolated ΔΣ modulator, and small isolated bias must be treated as one coupled system.
PWM FAULT / STATUS BITSTREAM BIAS POWER dv/dt hot node

Boundary — what is included / excluded

This page focuses on the three-piece isolation stack used in motor inverters: isolated gate drive + isolated ΔΣ sensing + small isolated bias, with system-level constraints on dv/dt immunity, timing determinism, layout partitioning, and verification gates.

In-scope

  • Half-bridge / three-phase inverter switching node constraints (dv/dt environment).
  • Phase / DC-bus current sensing chain using isolated ΔΣ bitstream (truthfulness under stress).
  • Floating-domain bias powering for driver and sensing (startup, UVLO behavior, noise coupling).
  • Deterministic protection behavior: DESAT/SC handling and time-budget awareness (system view).

Out-of-scope

  • Communication interface isolation specifics (USB/Ethernet/RS-485/CAN/LIN protocol details).
  • Power-topology encyclopedias (flyback/push-pull design deep dives beyond bias selection boundaries).
  • Control-algorithm exposition (FOC/modulation theory); only timing constraints are referenced.

System map — domains, barriers, and critical signals

The isolation barrier splits control from high-voltage domains; dv/dt at the switching node can inject into both drive and sensing unless return paths and bias distribution are engineered as one system.

Control Domain HV Domain Isolated Drive Isolated Sense Isolation Barrier MCU / Control Digital Filter Protection Logic Isolated Gate Driver Isolated ΔΣ Modulator Half-Bridge Power Stage Current Sense Motor Load dv/dt hot node Isolated Bias PWM FAULT / STATUS GATE Analog BITSTREAM BIAS POWER
Domain partitioning: control logic is separated by a reinforced barrier; PWM and status signals cross the barrier, while ΔΣ bitstream and bias power must remain robust under dv/dt stress.

Isolation Architecture Map (Where to Place Barriers)

Intent — make barrier placement a decision, not a habit

Isolation barriers can be centered on drive, sensing, or power. Each placement changes the trade-offs across noise coupling, timing determinism, EMI, and safety evidence.

  • Noise: which parasitic path dominates (barrier capacitance, return-path shortcuts, bias ripple coupling).
  • Timing: propagation delay / skew / filter latency stack-up and its effect on protection windows.
  • EMI: common-mode currents and where they close the loop.
  • Compliance: which component becomes the “hard gate” for creepage/clearance and insulation rating.

Key decisions — three questions with engineering meaning

  1. Single barrier vs multi-barrier: should fault paths and measurement paths be separated to reduce single-point failure impact?
  2. Modulator on high-side vs front-end on high-side: can dv/dt-induced input recovery and bitstream integrity be bounded with testable criteria?
  3. Per-phase bias vs shared isolated bias: does a single rail disturbance propagate across phases, or can faults be contained?

Architecture options — stacked for mobile

Driver barrier-centric

Best for: aggressive switching and strict protection determinism.
Main risk: sensing chain can still be corrupted if dv/dt coupling into the modulator/front-end is not contained.
Hard gate: driver insulation rating + creepage/clearance evidence.

Sense barrier-centric

Best for: measurement-truth-first systems where control/diagnostics rely on clean sensing.
Main risk: protection and drive loops may inherit delay/skew complexity unless carefully budgeted.
Hard gate: end-to-end sensing latency budget and bitstream integrity under dv/dt stress.

Power barrier-centric

Best for: multi-phase cost/BOM optimization where an isolated rail is distributed.
Main risk: bias ripple and return-path shortcuts can spread common-mode noise into both driver and sensing domains.
Hard gate: common-mode current control and rail disturbance containment.

Diagram — three barrier placements at a glance

The same functional blocks appear in each option. The only changes are the barrier position and the dominant coupling/timing risks.

Driver barrier-centric MCU Barrier Isolated Gate Driver Power Stage dv/dt ΔΣ Modulator + Filter PWM GATE BITSTREAM Sense barrier-centric MCU Digital Filter / Control Barrier ΔΣ Modulator (High-side) Power Stage dv/dt DATA BITSTREAM SENSE Power barrier-centric Primary DC Barrier Isolated Bias Isolated Gate Driver ΔΣ Modulator / Sense POWER BIAS BIAS dv/dt context
Same functional blocks, different barrier center. Compare how noise paths, timing budgets, and compliance “hard gates” move with barrier placement.

Key Specs That Actually Matter (dv/dt, CMTI, Delay, Barrier C)

Budget card — turn specs into pass/fail budgets

In motor inverters, specifications matter only when they close a failure loop: dv/dt injection can corrupt drive or sensing, and timing drift can break protection determinism. Budgets below use placeholders (X/Y/N) to be replaced with project limits.

dv/dt immunity / CMTI

Controls: logic upset, false triggering, sensing corruption under switching edges.
Budget: IGBT-class ≥ X kV/µs; SiC-class ≥ Y kV/µs; GaN-class ≥ N kV/µs (placeholders).
Verify: apply worst-case dv/dt conditions and check repeatable behavior across temperature and supply corners.

Propagation delay / skew

Controls: dead-time margin and protection timing consistency across phases and channels.
Budget: delay ≤ X ns; Δskew ≤ Y ns; keep worst-case drift bounded across voltage/temperature.
Verify: measure worst-case (not typical) and confirm stable behavior under dv/dt stress.

Barrier capacitance (Ciso)

Controls: common-mode displacement current and EMI coupling into quiet domains.
Budget: Ciso ≤ X pF (placeholder) and keep common-mode return paths intentional.
Verify: correlate EMI and error events with edge rate/frequency to reveal displacement-current coupling.

Driver peak current / UVLO

Controls: gate charge transition time, switching speed, and stability under bias disturbances.
Budget: peak drive current matched to Qg and target transition time; UVLO margin: Vbias_min > UVLO + X V (placeholder).
Verify: inject bias ripple/dips and confirm no spurious gating or oscillatory reset.

ΔΣ modulator fidelity (noise/linearity) & data integrity

Controls: false current/voltage estimation and incorrect protection decisions due to bitstream errors.
Budget: allowable bitstream error rate ≤ X/Y window (placeholder); total sensing latency bounded for protection windows.
Verify: dv/dt stress + fault injection while monitoring bitstream anomalies and estimator stability.

Worst-case corners Repeatability dv/dt stress Latency budget CM current path

Trade-off card — faster edges always move another limit

  • Faster switching increases dv/dt stress and shifts risk into CMTI/Ciso coupling and EMI.
  • Heavier filtering cleans measurement outputs but adds latency that can narrow protection time windows.
  • Lower Ciso reduces injection but still requires controlled return paths; layout must enforce where CM currents close.
dv/dt Node Injection Path (CM current) Isolation Stack Drive Sense False Trigger / Mis-gating False Measure / Bitstream Error Control Decision (Protection) Fault Outcome (Device stress / trip / damage) Ciso CMTI Delay / Skew dv/dt
Budget path: dv/dt injection couples through barrier parasitics and timing drift, causing mis-gating or false measurement that can destabilize protection decisions.

Isolated Gate Driver: Selection Logic & Protection Features

Selection logic — a 7-step executable flow

Gate-driver selection must bind together switch behavior (Qg and dv/dt), bias headroom, protection policy, insulation rating, and layout hooks so the system stays deterministic under stress.

1

Switch class & dv/dt tier

Choose the dv/dt tier (IGBT / SiC / GaN class) to set the minimum CMTI and layout strictness.

2

Gate charge & target transition

Use Qg and desired edge behavior to size peak drive current and acceptable switching time.

3

Gate network & loop constraints

Define Rg(on)/Rg(off), Kelvin source usage, and clamp strategy; treat the hot loop as a bounded geometry.

4

Protection policy

Select DESAT/SC response and turn-off profile (soft turn-off vs hard off) aligned to device limits and bus energy.

5

UVLO & bias headroom

Ensure Vbias_min stays above UVLO with margin under ripple/dips; avoid oscillatory resets during transients.

6

Insulation rating as a hard gate

Set basic/reinforced needs and confirm creepage/clearance evidence; align to the project safety target.

7

Verification hooks & layout hooks

Reserve test points for dv/dt stress, bias dip injection, DESAT monitoring, and repeatable fault characterization.

Device differences (IGBT/SiC/GaN) are referenced only where they change dv/dt tier, protection policy, and layout/verification constraints.

Protection features — place each feature on the fault timeline

  • DESAT: detects abnormal VCE/VDS rise; blanking must prevent dv/dt-induced false trips while still catching real shorts.
  • Miller clamp: prevents dv/dt-driven false turn-on; effectiveness depends on gate loop geometry and Kelvin referencing.
  • Soft turn-off: shapes current/voltage stress during faults; ties directly to bias capability and drive strength.
  • UVLO: defines safe behavior during bias dips; must avoid chatter and guarantee a known off-state.
Drive Loop Protection Branch Isolated Gate Driver Rg_on Rg_off Power Switch (IGBT/SiC/GaN) Kelvin Source Miller Clamp hot loop must be tiny DESAT Sense Blanking Decision Soft Turn-off (controlled stress) Fault Latch / Status sense lines keep away turn-off command
Gate loop geometry and protection timeline must cohere: minimize the hot loop, keep sense lines away from dv/dt fields, and validate blanking and soft turn-off under stress.

Isolated ΔΣ Modulator: Truthful Current/Voltage Sensing Chain

Signal chain card — what each stage does and what can fail under dv/dt

A truthful sensing chain must remain stable under switching dv/dt and fault stress. Each stage below is defined by its role, its dominant dv/dt failure mode, and a verification hook.

Sensor (Shunt / CT)

Role: converts phase/bus current (or voltage) into a measurable signal.
dv/dt risk: reference shifts or saturation distort the true input mapping during switching edges.
Verify: correlate measurement artifacts with switching edges and load transients.

Analog Front-End (AFE)

Role: conditions the signal and defines common-mode handling.
dv/dt risk: common-mode steps push the input stage into recovery; recovery time can dominate short fault windows.
Verify: inject dv/dt-like common-mode steps and measure recovery-to-truth time.

ΔΣ Modulator

Role: produces a high-rate bitstream representing the conditioned signal.
dv/dt risk: overload/saturation and threshold/clock disturbance change bitstream density or stability.
Verify: monitor bitstream for bursts, saturation plateaus, or timing wobble under stress.

Isolation Barrier

Role: transports bitstream across the barrier while limiting injection paths.
dv/dt risk: displacement current and supply bounce create edge jitter or missing pulses (data integrity loss).
Verify: check pulse integrity vs switching edge rate and bias disturbance.

Digital Filter / Decimator (SINC / DF)

Role: converts bitstream to a usable sample stream for control/protection.
dv/dt risk: burst errors can smear into the window; filter latency shifts the protection decision time.
Verify: quantify group delay and confirm output stability during bitstream bursts.

Estimator → Control / Protection

Role: uses the filtered value for FOC control and over-current/short-circuit decisions.
dv/dt risk: a “clean-looking” average can still be late; late data breaks deterministic protection timing.
Verify: fault injection timing tests: decision time must remain within the allowed window.

bitstream integrity recovery time group delay fault window dv/dt correlation

Filter & latency card — budgets that must be owned (placeholders)

Filtering creates latency. Protection timing must budget the end-to-end sensing delay and its worst-case drift.

  • Total sensing latencyX (placeholder) from physical signal change to estimator output.
  • Worst-case latency driftY (placeholder) across voltage/temperature and switching stress.
  • Bitstream burst tolerance: allowable error rate ≤ X/Y window (placeholder); beyond that, protection must enter a defined safe policy.
Shunt/CT AFE ΔΣ Modulator Barrier SINC/DF Filter Estimator → Control OC/SC Protection dv/dt Switching Node latency budget dv/dt injection points group delay
Bitstream chain: dv/dt can inject at the AFE and across the barrier. Filter group delay must be budgeted so protection decisions remain deterministic.

Small Isolated Bias: Powering the Floating Domains

Requirements card — define bias as an engineering contract

Small isolated bias rails are the stability base for both driver and sensing domains. Requirements below turn “a bias supply” into measurable acceptance criteria using placeholders (X/Y/N).

Rails & polarity

Driver rails: +Vg (and -Vg if required); Sensing rails: Vdd_iso for AFE/ΔΣ/isolator side. Keep rails separated where noise sensitivity differs.

Power profile (peak vs average)

Size for gate-charge bursts and steady-state losses. Peak demand must not collapse the rail during switching or fault turn-off events.

Ripple & transient headroom

UVLO margin contract: Vbias_min > UVLO + X V (placeholder). Define allowable ripple ≤ Y (placeholder) under worst-case load steps.

Startup & sequencing

Startup time ≤ X (placeholder). During ramp, outputs must remain in a defined safe-off state until control is ready.

Protection & fault containment

Define overload/short behavior (limit/hiccup/latch) so a fault in one domain does not propagate into multi-phase instability.

no-load loss startup/inrush UVLO margin fault containment CM noise path

Architecture card — independent vs shared bias, module vs transformer driver

Per-phase independent bias

Better fault containment and phase-to-phase isolation of disturbances. Higher BOM and volume, but improves deterministic recovery behavior.

Shared isolated bias then distribute

Lower BOM, but a single rail disturbance can propagate across phases and corrupt both gating and sensing simultaneously.

Isolated power module

Faster compliance path with integrated creepage/clearance evidence. Must validate no-load loss and rail noise characteristics under dv/dt stress.

Transformer driver (custom bias)

Flexible multi-rail generation and tuning. Requires stronger layout/EMI ownership and more verification effort for stability and compliance.

Primary DC Barrier Isolated Bias startup/inrush no-load loss Driver Rail (+Vg / -Vg) Sense Rail (Vdd_iso) UVLO margin Option A Per-phase independent Option B Shared
Bias tree: define startup/inrush, no-load loss, and UVLO headroom as acceptance criteria, then choose independent vs shared distribution based on fault containment needs.

Co-Design: How Drive + Sense + Bias Interfere (and How to Stop It)

Interference paths card — four coupling paths with executable closure

The isolation stack behaves as a coupled system: dv/dt, barrier parasitics, bias dynamics, and return paths can corrupt sensing, destabilize gating, or trigger non-deterministic protection. Each path below closes with Cause → Symptom → Fix → Pass criteria.

Path A — Driver dv/dt → Ciso injection → Sense false signal / bitstream anomalies

  • Cause: switching dv/dt drives displacement current through effective barrier capacitance (Ciso) and unintended return paths into the sensing chain.
  • Symptom: bitstream bursts/missing pulses/edge jitter; filtered current shows spikes/dips aligned to switching edges; protection trips without a real fault.
  • Fix: reduce effective coupling path (lower Ciso where possible, shorten cross-domain coupling geometry); harden sensing-side supply and input recovery; keep high-dv/dt fields away from bitstream routing.
  • Pass criteria: dv/dt stress: bitstream burst rate ≤ X/Y window; false trip count ≤ N per Y minutes; recovery-to-truth ≤ X µs (placeholders).

Path B — Bias ripple / ground bounce → Driver UVLO chatter / false reset

  • Cause: gate-charge pulses and fault turn-off transients pull bias rails; ground bounce and return mismatch amplify rail dips seen by UVLO.
  • Symptom: repeated UVLO events, intermittent gate disable/enable, phase-to-phase inconsistency, “random” resets coincident with load steps.
  • Fix: enforce UVLO headroom contract (Vbias_min > UVLO + X V); local decoupling and tight current loops; prevent bias fault behavior from oscillating with driver UVLO.
  • Pass criteria: under worst-case load steps: UVLO events ≤ N per Y minutes; rail dip amplitude ≤ X V and duration ≤ Y µs (placeholders).

Path C — Protection event (DESAT/SC) → Control misinterpretation / retry storm

  • Cause: protection actions force mode changes across drive, bias, and sensing simultaneously; unclear latch/clear policy triggers repeated re-enable cycles.
  • Symptom: repeated fault cycles with short intervals; “recover then fail again” loops; excessive thermal and electrical stress accumulation.
  • Fix: define latch/clear criteria and minimum cooldown (placeholders); validate DESAT blanking vs dv/dt upset; tie recovery to a verified “sensing trustworthy” condition.
  • Pass criteria: recovery success ≥ X%; consecutive retry count ≤ N with retry interval ≥ X ms; fault rate ≤ N per Y hours (placeholders).

Path D — Return path error → Common-mode current crosses the “gap bridge”

  • Cause: common-mode current closes through unintended geometry across the isolation boundary (gap bridge), injecting noise into control/sense domains.
  • Symptom: errors correlate with cabinet state, wiring changes, or edge-rate; sensing glitches appear even with stable load; control domain shows sporadic upsets.
  • Fix: enforce strict domain partition and intentional return closure; prohibit cross-gap copper/test points/long grounds; keep high-dv/dt loops compact and isolated.
  • Pass criteria: dv/dt stress: control/sense error events ≤ X (or 0); key node ground bounce ≤ (placeholder); correlation with edge-rate significantly reduced.
Ciso path return closure UVLO chatter bitstream burst retry storm
dv/dt node Sense Domain AFE Bitstream Bias Domain Bias UVLO Logic / Control FW State Retry Ciso Return path Bias coupling gap bridge
Coupling map: dv/dt excites displacement and return currents. The most dangerous paths are those that inject into sense integrity and UVLO determinism.

Timing & Determinism: Dead-Time, Skew, Sampling Alignment

Budget card — unify all delays into one executable timing contract

Determinism requires owning worst-case delay addition across drive, switching response, and sensing/filter latency. The total budget must protect dead-time margin and the protection window under stress.

Δt_drive (PWM → isolation → driver output)

Includes propagation delay and channel skew. Contract: delay ≤ X ns and skew ≤ Y ns (placeholders).

Δt_switch (driver output → switch-node response)

Captures gate-network dynamics and device response. Contract: response drift ≤ X (placeholder) across corners.

Δt_sense (physical current change → filter output)

Includes ΔΣ + decimation group delay. Contract: sensing latency ≤ X and drift ≤ Y (placeholders).

Δt_total = Δt_drive + Δt_switch + Δt_sense

System contracts: dead-time margin ≥ X; protection decision latency ≤ Y; cross-phase mismatch ≤ N (placeholders).

worst-case skew budget group delay dead-time alignment

Alignment card — PWM edges, sampling windows, and protection windows

  • Sampling alignment: sample windows must avoid the most violent dv/dt region; alignment error ≤ X (placeholder).
  • Protection window: decision time jitter must be bounded; timing jitter ≤ Y (placeholder).
  • Cross-phase determinism: mismatch across phases must not break consistent gating and protection; Δphase ≤ N (placeholder).
time PWM Driver dv/dt Sample Filter window Δt1 Δt2 Δt_total avoid
Timing chain: PWM edge → driver output → switch-node dv/dt → sampling window → filter output. Budget Δt1/Δt2/Δt_total so dead-time and protection remain deterministic.

Layout & EMC in High dv/dt Inverters (Partition, Returns, Creepage)

Scope guard — layout rules that directly control the isolation stack

This section focuses only on layout and EMC behaviors that directly impact the isolated gate driver, isolated ΔΣ modulator chain, and small isolated bias: partition discipline, return closure, creepage/clearance geometry, hot-loop containment, and controlled Y-cap usage.

Partition & boundary discipline

Do

  • Draw explicit domains: HV hot area, drive domain, quiet sensing domain, and logic/control domain.
  • Keep the isolation boundary visually obvious on the PCB (silkscreen/keep-out/slot alignment).
  • Route bitstream and sensitive sense nodes only inside the quiet domain, away from the switching field.

×Don’t

  • Let any copper, test pad, or “helpful” ground pour cross the isolation gap by accident.
  • Place sense routing parallel to the switch-node edge corridor (long coupling length).

Return closure: no “gap bridge” for common-mode current

Do

  • Force return paths to close inside their own domains; keep high dv/dt current loops compact.
  • Provide a deliberate, documented path if any common-mode current must be managed (system decision).
  • Use local decoupling with tight loop area at the driver and isolated-sense supplies.

×Don’t

  • Create a return shortcut across the barrier through copper pours, shields, or “stitch” structures.
  • Share a noisy return between bias and sense rails without defined current closure.

Creepage/clearance geometry: slots and guard structures

Do

  • Use slots to extend creepage where surface distance is the limiting factor.
  • Use guard rings only where they do not create unintended coupling across domains.
  • Keep-out rules must match the intended insulation class and pollution degree (documentation ownership).

×Don’t

  • Add a slot but leave copper/vias close enough to defeat the creepage gain.
  • Place guard copper in a way that increases effective coupling to the dv/dt corridor.

Hot loops & sensitive routing: driver loop vs sense lines

Do

  • Keep the gate-drive hot loop minimal (driver → gate network → device return) and physically confined.
  • Route sense lines with deliberate spacing from the dv/dt corridor and avoid long parallel runs.
  • Keep bitstream routing short, direct, and shielded by the quiet-domain reference (without crossing gaps).

×Don’t

  • Run sense traces through the hot area “because it is shorter.”
  • Place the driver’s switching edge corridor under/near the sensing chain.

Y-cap usage boundary: EMC benefit vs leakage & determinism impact

Do

  • If a Y-cap is used, treat it as a deliberate common-mode path with documented value and placement intent.
  • Validate dv/dt immunity and sensing integrity with the Y-cap installed (not just emissions).
  • Define acceptance placeholders: emissions improvement ≥ X, leakage budget ≤ Y (placeholders).

×Don’t

  • Add a Y-cap as a last-minute “EMI patch” without re-validating bitstream integrity and UVLO stability.
Primary Secondary Boundary HV hot area Switch node Power stage Drive hot loop Quiet sensing AFE Bitstream Logic / control MCU FW Slot Guard ring No cross-gap return
PCB partition: keep HV hot activity inside the primary hot corridor; keep sensing quiet in the secondary quiet zone; do not allow any accidental return path to cross the isolation boundary.

Verification & Compliance Path (Bring-up → Certification → Production)

Evidence chain — three gates that convert a design into cert-ready production

The goal is an evidence chain, not a standards encyclopedia. The gates below define what must be proven, what artifacts must be collected, and what acceptance placeholders (X/Y/N) should be owned.

Gate 1 — Bring-up (bench determinism)

Prove: stable gating, truthful sensing, and bias headroom under nominal switching.
Collect: timing budget sanity results; bitstream integrity snapshots; UVLO event logs.
Pass criteria: false trip ≤ N; UVLO events = 0; Δt_total within X (placeholders).

Gate 2 — Pre-compliance (stress reproduction)

Prove: dv/dt immunity and fault behavior under controlled worst-case conditions.
Must appear: dv/dt immunity reproduction conditions = X kV/µs at Y conditions (placeholders).
Pass criteria: bitstream burst ≤ X/Y window; recovery success ≥ X% (placeholders).

Gate 3 — Production (sampling + documentation lock)

Prove: repeatability across units and traceable documentation for audits.
Must appear: hi-pot / partial discharge (if applicable); CTI and material evidence; CB report alignment; datasheet clause mapping.
Pass criteria: production sampling failure ≤ N per Y units; certificates complete (placeholders).

bench dv/dt stress fault inj. hi-pot partial discharge production sampling evidence CTI CB report
Test funnel: bench bring-up establishes baseline determinism; dv/dt stress and fault injection reproduce worst-case behavior; hi-pot/partial discharge (if applicable) and documentation complete the compliance evidence; production sampling locks repeatability.

Engineering Checklist: Design → Bring-up → Production Gates

Three gates that turn an isolated motor/inverter stack into a repeatable, cert-ready product. Each item is actionable, produces evidence, and stays inside the 3-piece scope: isolated gate driver + isolated ΔΣ modulator + small isolated bias.

Milestone strip — what each gate must lock

Design Bring-up Production Layout Budget Docs dv/dt Timing Fault Regression Hi-pot
Gate strip: lock layout and budgets (Design), reproduce worst-case determinism (Bring-up), then freeze change control + sampling tests (Production).

Design Gate (6–10 checks)

Goal: eliminate coupling paths on paper, own creepage geometry, and define the timing/power contracts before bring-up.

  • Partition domains and mark the isolation boundary (HV hot / Drive / Sense / Control)

    Evidence: annotated PCB partition snapshot; Pass: cross-gap copper violations = 0 (N=0 placeholder).

    Gate driver (iso) TI UCC21750 ADI ADuM4135 Infineon 1EDC20I12MH
  • Define “no cross-gap return” rules and prohibited items (gap-bridge blockers)

    Evidence: DRC/review checklist items; Pass: prohibited structures count = 0 (N=0 placeholder).

    ΔΣ mod (iso) TI AMC1306 TI AMC1336 ADI AD7403
  • Minimize gate-drive hot loop area and enforce Kelvin return routing

    Evidence: hot-loop highlighted layout; Pass: loop length/area ≤ X (placeholder), no parallel run beside dv/dt corridor.

    Driver support Bourns CDSOT23-SM712 Würth 744231091 TDK ACM series
  • Define a timing contract (delay, skew, and total latency budget) with placeholders

    Evidence: Δt_total budget card; Pass: dead-time margin ≥ X, skew ≤ Y, protection latency ≤ N (placeholders).

    Clock / sync (if needed) TI ISO7741 ADI iCoupler iso series Silicon Labs Si86xx
  • Define isolated bias contract (rails, no-load loss, startup, UVLO headroom)

    Evidence: bias contract card; Pass: Vbias_min > UVLO + X V; no-load loss ≤ Y (placeholders).

    Isolated bias options Murata MGJ2D051505SC RECOM R15P215S TI SN6505B
  • Own creepage/clearance geometry (slots, keep-outs, guard structures) as a signed constraint

    Evidence: creepage map + drawings; Pass: minimum creepage/clearance meets target class (X/Y placeholders).

    Barrier-rated packages UCC21750 (DWK) ADuM4135 AMC1336
  • Decide Y-cap usage as a deliberate common-mode path (not an EMI patch)

    Evidence: decision record (value/placement/target); Pass: emissions gain ≥ X while bitstream/UVLO remain deterministic (placeholders).

    Safety Y-cap examples KEMET R46 TDK/EPCOS B3202x Murata DE2 series

Bring-up Gate (6–10 checks)

Goal: reproduce worst-case dv/dt and fault stress, then backfill measured delay/latency evidence into the budgets.

  • Lock reproducible dv/dt stress conditions (X kV/µs at Y conditions)

    Evidence: scope captures with trigger definition; Pass: dv/dt ≥ X kV/µs at Y conditions (placeholders).

    Gate driver under test TI UCC21750 ADI ADuM4135 Infineon 1EDC20I12MH
  • Validate ΔΣ bitstream integrity under dv/dt stress (burst / missing pulses / jitter)

    Evidence: bitstream statistics (windowed); Pass: burst rate ≤ X/Y window; missing pulses = ≤ N (placeholders).

    ΔΣ mod under test TI AMC1306 TI AMC1336 ADI AD7403
  • Prove bias rail headroom and eliminate UVLO chatter during switching and fault events

    Evidence: rail dip capture + UVLO event counters; Pass: UVLO events ≤ N; dip amplitude ≤ X V and duration ≤ Y µs (placeholders).

    Isolated bias under test Murata MGJ2D051505SC RECOM R15P215S TI SN6505B
  • Measure and record drive delay and channel skew (PWM → driver output)

    Evidence: timing captures + worst-case summary; Pass: delay ≤ X ns, skew ≤ Y ns (placeholders).

    Reference isolators (if separate) TI ISO7721 Silicon Labs Si8641 ADI ADuM110N
  • Measure and record sensing latency (physical current change → filter output)

    Evidence: aligned waveforms; Pass: Δt_sense ≤ X and drift ≤ Y across corners (placeholders).

    ΔΣ chain examples AMC1306 + SINC AD7403 + decimator AMC1336
  • Enable protection (DESAT/SC) with fault injection; verify latch/clear policy and recovery determinism

    Evidence: fault injection logs; Pass: false trip ≤ N, recovery success ≥ X%, retry ≤ N with interval ≥ X ms (placeholders).

    Drivers with protection TI UCC21750 Infineon 1EDC20I12MH Silicon Labs Si8239

Production Gate (6–10 checks)

Goal: freeze what matters, define change triggers, and run sampling tests that prevent silent regressions.

  • Freeze BOM and define substitution triggers that mandate dv/dt + timing re-test

    Evidence: change-control rule; Pass: any change to isolator/driver/bias module triggers Gate-2 regression (rule must be enforced).

    Parts that must trigger re-test UCC21750 ADuM4135 AMC1306 MGJ2D051505SC
  • Run dv/dt and timing regression on each ECO (minimal but sufficient suite)

    Evidence: regression report; Pass: dv/dt ≥ X, skew ≤ Y, Δt_total within N (placeholders).

    Regression anchors dv/dt condition card delay/skew capture bitstream stats
  • Define production sampling tests (hi-pot; partial discharge if applicable)

    Evidence: sampling plan; Pass: failures ≤ N per Y units (placeholders); documentation stored for audit.

    Evidence artifacts Hi-pot record PD record unit trace
  • Zero-tolerance events: UVLO chatter, bitstream corruption during defined stress

    Evidence: event counter snapshot; Pass: UVLO chatter = 0; bitstream missing pulses ≤ N (placeholders).

    Monitored blocks UCC21750 UVLO AMC1306 bitstream MGJ2 bias rail
  • Lock compliance evidence pack (CTI/materials/CB report) and datasheet clause mapping

    Evidence: audit-ready pack; Pass: missing items = 0 (N=0 placeholder).

    Barrier evidence references UCC21750 datasheet ADuM4135 datasheet AMC1336 datasheet

Part-number note (usage boundary)

Listed part numbers are example anchors for checklists and change-control triggers. Use local qualification rules to decide equivalents, but treat any isolator/driver/bias substitution as a mandatory dv/dt + timing regression event.

Request a Quote

Accepted Formats

pdf, csv, xls, xlsx, zip

Attachment

Drag & drop files here or use the button below.

FAQs (Motor/Inverter Isolation Stack) — Field Debug & Acceptance

Hard rule: each answer is exactly 4 lines — Likely cause / Quick check / Fix / Pass criteria. Scope stays inside the 3-piece stack: isolated gate driver + isolated ΔΣ modulator chain + small isolated bias.

DESAT false-trips occasionally but waveforms look normal—dv/dt injection or blanking first?
Likely cause: dv/dt-induced transient couples into DESAT sense path, or blanking window is shorter than the worst-case diode recovery / switching transient.
Quick check: correlate DESAT pin vs switch-node dv/dt edge; sweep blanking by +X ns while holding dv/dt ≥ X kV/µs constant (same probe grounding).
Fix: tighten DESAT routing + filtering, extend blanking to cover worst-case transient, and ensure Kelvin return integrity so sense does not ride on the hot loop.
Pass criteria: false DESAT trips ≤ N per Y hours at dv/dt ≥ X kV/µs and T = (min/max) corner; true SC response time ≤ X µs (placeholders).
After moving SiC to a faster edge, current reading drifts—Ciso injection or AFE recovery time?
Likely cause: higher dv/dt increases common-mode injection through barrier capacitance (Ciso), or AFE input momentarily saturates and needs recovery time.
Quick check: compare drift vs dv/dt (same load); observe AFE input/bitstream immediately after switching edges to spot saturation/recovery signatures.
Fix: reduce coupling length (routing partition), improve AFE input protection/headroom, and reduce Ciso-driven CM current by controlling return paths and edge corridor geometry.
Pass criteria: current offset drift ≤ X% FS over Y minutes at dv/dt ≥ X kV/µs; recovery time after edge ≤ X µs; no estimator “step” events > N per Y cycles (placeholders).
Bitstream missing pulses triggers false over-current—isolated supply droop or digital filter overflow?
Likely cause: isolated bias droop/UVLO chatter corrupts modulator output, or decimator/filter saturates/overflows when fed with corrupted bitstream bursts.
Quick check: log UVLO/FAULT counters and bias rail dips during events; capture bitstream burst statistics in a fixed window (Y switching events).
Fix: add bias headroom and reduce ripple under transient load; clamp/sanitize filter inputs and define a “bitstream invalid” handling path to prevent false OC decisions.
Pass criteria: missing pulses ≤ N per Y switching events; UVLO events = 0; OC false positives ≤ N per Y hours under worst-case dv/dt and temperature (placeholders).
High temperature causes frequent driver dropouts—bias efficiency/no-load drift or UVLO threshold shift?
Likely cause: isolated bias delivers less usable headroom at high T (efficiency/no-load behavior changes), or driver UVLO threshold and margin shrink across temperature.
Quick check: measure Vbias_min and ripple at hot corner while switching; correlate dropout timestamps to UVLO indication and bias rail droop depth/width.
Fix: increase bias margin (higher Vout or lower droop), improve thermal path of the bias module/transformer driver, and set UVLO margin contract (Vbias_min > UVLO + X V).
Pass criteria: UVLO/dropout events ≤ N per Y hours at T = Tmax; Vbias_min − UVLO ≥ X V; ripple ≤ Y mVpp under load steps (placeholders).
Only one phase fails more often—gate-loop area issue or phase-specific bias coupling?
Likely cause: that phase has a larger/hotter gate loop (more dv/dt field pickup), or its bias distribution/return closure is different, injecting noise into UVLO/sense.
Quick check: swap phase channels (if possible) to see if the problem follows hardware location; compare gate-loop geometry and bias ripple per phase under the same operating point.
Fix: equalize per-phase layout constraints (loop length/return), isolate per-phase bias where needed, and enforce identical routing/decoupling patterns phase-to-phase.
Pass criteria: phase-to-phase fault rate spread ≤ X (e.g., ratio) over Y hours; phase bias ripple difference ≤ Y mVpp; phase delay/skew difference ≤ X ns (placeholders).
Adding a Y-cap improves EMI but increases protection false trips—leakage/reference shift or CM return reroute?
Likely cause: Y-cap creates a new CM current path that shifts the effective reference of sense/logic, or reroutes CM return through sensitive nodes.
Quick check: A/B test with the same dv/dt and load: compare false trip rate and bias ripple/ground bounce signatures; verify Y-cap placement vs intended chassis return.
Fix: move/resize Y-cap to a controlled return point, reinforce quiet-domain reference integrity, and re-validate bitstream/UVLO determinism with Y-cap installed.
Pass criteria: emissions improvement ≥ X dB while false trips ≤ N per Y hours; leakage current ≤ X mA (system limit placeholder); bias ripple change ≤ Y mVpp (placeholders).
Resets happen more at light load—bias light-load instability or reset-cause accounting mismatch?
Likely cause: isolated bias has light-load regulation/no-load loss behavior causing rail wobble, or reset cause is mis-attributed (UVLO vs reset reason collection).
Quick check: capture Vbias and UVLO indicator during light-load; log reset reasons with timestamps and align them to rail events and dv/dt edges.
Fix: add a defined minimum load or adjust bias design for light-load stability; standardize reset-cause logging so UVLO vs other resets are not conflated.
Pass criteria: resets ≤ N per Y hours at light-load band; Vbias ripple ≤ X mVpp; UVLO chatter events = 0; reset-cause classification accuracy ≥ X% (placeholders).
Same board, different labs report different dv/dt immunity—what must be normalized first?
Likely cause: stress definition differs (edge rate, probe ground, fixture return, cable placement), changing CM current paths and measured dv/dt.
Quick check: normalize fixture return and probing: identical ground spring/lead length, identical bus voltage/load, identical dv/dt extraction method over the same interval.
Fix: publish a “dv/dt reproduction card” (X kV/µs at Y conditions) including fixture photos and measurement method; retest under that controlled recipe.
Pass criteria: inter-lab dv/dt result variance ≤ X% for the same recipe; immunity pass/fail agrees in ≥ X% of runs over Y repetitions (placeholders).
Production hi-pot passes, but field shows early failures—what evidence chain is usually missing (materials/creepage/PD)?
Likely cause: hi-pot alone does not capture partial discharge risk, creepage contamination/CTI/material tracking issues, or process variation affecting barrier reliability.
Quick check: review traceability: CTI/material declarations, creepage drawings vs as-built, and whether PD (if applicable) or process cleanliness evidence exists.
Fix: close documentation gaps (CTI/CB pack), add PD or targeted stress screening if applicable, and enforce creepage/cleanliness controls in production.
Pass criteria: missing evidence items = 0; early-life failure rate ≤ X ppm over Y units; PD screening (if used) fail rate ≤ N per Y units (placeholders).
Shutdown misses the protection window due to estimator delay—filter group delay or alignment first?
Likely cause: decimation/filter group delay pushes the estimate beyond the protection window, or PWM edge / sampling alignment is mis-timed relative to switching transients.
Quick check: measure Δt_sense (physical current step → filter output) and compare to window budget; verify edge-to-sample alignment with a consistent trigger definition.
Fix: reduce group delay (filter/decimation choice), shift sampling alignment away from dv/dt disturbance, and re-budget Δt_total so shutdown determinism is preserved.
Pass criteria: Δt_sense ≤ X and Δt_total ≤ Y; protection decision occurs within window margin ≥ X µs; missed-window events ≤ N per Y shutdowns (placeholders).
After fault recovery, jitter and false trips increase—retry storm or latch/clear policy?
Likely cause: aggressive retry creates repeated stress bursts (retry storm), or latch/clear criteria allow rapid re-entry before rails/sense are stable.
Quick check: examine event timeline: fault → clear → re-enable cadence; count retries per minute and correlate to bias droops and bitstream anomaly bursts.
Fix: enforce cooldown and bounded retries (retry ≤ N, interval ≥ X ms), and require stability conditions (Vbias headroom, bitstream valid) before re-enable.
Pass criteria: retries ≤ N per event; false trips ≤ N per Y hours post-recovery; re-enable success ≥ X% across Y repetitions at worst-case dv/dt (placeholders).
Swapping the isolated DC-DC module increases noise—CM capacitance or beat-frequency coupling?
Likely cause: new module has higher effective CM capacitance (more CM injection) or switching frequency creates beat with sampling/filters, raising in-band noise.
Quick check: compare bias ripple spectrum and bitstream noise before/after swap under identical operating point; check if noise peaks align with module fSW or its harmonics.
Fix: select lower-CM-coupling bias options, adjust filtering/placement to keep ripple out of sensitive bands, and re-validate dv/dt + timing determinism after module change.
Pass criteria: bias ripple ≤ X mVpp and in-band noise increase ≤ Y dB; bitstream anomaly rate ≤ N per Y events; dv/dt immunity unchanged within X% (placeholders).