123 Main Street, New York, NY 10001

Signal Isolator & Conditioner for Lighting Drivers

← Back to: Industrial Sensing & Process Control

Signal isolators and conditioners create a safe, noise-resilient boundary between the high-voltage LED power domain and low-voltage control/measurement electronics, so current/voltage feedback stays accurate and predictable under fast switching and EMI stress.

They combine the right isolation technology (digital isolators, isolation amplifiers, or ΣΔ modulators) with scaling, filtering, calibration, and isolated biasing to deliver ADC-ready signals without false triggers, drift, or ripple injection.

H2-1. Why Isolation & Conditioning Matter in Lighting Systems

In lighting drivers, isolation and signal conditioning define two non-negotiable boundaries: safety separation between high-voltage power nodes and low-voltage control electronics, and measurement usability—turning noisy, drifting, range-mismatched sense signals into stable, ADC-ready information. Without both, control loops become fragile, field failures look “random,” and compliance margins collapse under transients.

This page focuses on the cross-domain measurement chain (sense → isolate → filter/scale → ADC/MCU), not on power-stage topology design.

Safety boundary CMTI immunity Noise & drift control Range scaling Timing integrity
  • Isolation voltage rating (kVrms): sets withstand capability; verify against working voltage class and lifetime goals.
  • CMTI (kV/µs): predicts susceptibility to false transitions during fast dv/dt events (switch nodes, surge edges).
  • Propagation delay / jitter: bounds timing error for PWM/clocked measurements; watch multi-channel skew.
  • Offset drift (µV/°C): determines low-current accuracy stability (deep dimming, thermal soak, aging compensation).

Practical interpretation: a “good” barrier is not just high kVrms; it is a barrier that stays quiet during real switching edges and keeps measurement drift smaller than the control loop’s resolution budget.

Cross-Domain Measurement Chain HV → Isolation → LV HV Power Domain Switch Node High dv/dt, EMI Sense Pickoff Shunt / divider / NTC Surge Events ESD / lightning pulses Isolation Barrier creepage LV Control Domain Conditioning Filter + range scale ADC / Digital Filter Anti-alias, decimation MCU Control Telemetry + protection isolated signal common-mode transient Cite this figure
Figure F1 — System domain split for isolated measurement in lighting drivers. Jump to H2-1

H2-2. Isolation Technologies Compared

Isolation in lighting systems is a technology choice with visible consequences: false triggering under fast switch-node dv/dt, long-term measurement drift, channel timing skew, and EMC behavior during immunity tests. The comparison below is framed as an engineering decision matrix—how each coupling mechanism tends to behave under high common-mode stress and long service life.

  • Lifetime & aging behavior: stability over multi-year operation; look for drift mechanisms that change gain/thresholds over time.
  • CMTI robustness: tolerance to fast common-mode edges; insufficient margin can appear as “random” resets or measurement spikes.
  • Data rate & channel density: suitability for SPI/I²C/PWM isolation and multi-channel skew control.
  • EMI immunity characteristics: how coupling paths inject or reject noise across the barrier during ESD/surge/fast transients.
  • Basic vs reinforced isolation: not a checkbox—this sets product safety class, spacing constraints, and certification pathways.

Selection rule-of-thumb: prioritize CMTI margin and predictable aging for power-stage adjacency; prioritize skew, data rate, and channel integration for control-bus isolation.

Isolation Coupling Mechanisms mechanism → typical tradeoffs Magnetic Capacitive Optical micro-transformer isolation capacitor LED → sensor strong CMTI • layout-sensitive timing skew matters high integration • coupling path watch CMTI margin simple barrier • aging drift speed/channel limits Basic vs reinforced isolation sets safety class, spacing constraints, and certification pathway Cite this figure
Figure F2 — Mechanism-level comparison (magnetic vs capacitive vs optical) for isolation selection. Jump to H2-2

H2-3. Digital Isolators for Gate & Logic Domains

Focus: timing contract • fault behavior • supply integrity

Digital isolators are used to carry SPI, I²C, PWM, and GPIO across an isolation barrier without breaking timing assumptions. In lighting systems, failures rarely look like “isolation broke.” They usually appear as sporadic glitches, mis-sampled edges, or unsafe default states during fast common-mode transients and undervoltage events.

This chapter covers isolation of logic and control signals only. Power gate-driver stage design and switching-loop details are out of scope.

Multi-channel mapping

  • SPI: clock + data + chip select require skew control.
  • I²C: bidirectional/open-drain behavior needs a compatible isolator architecture.
  • PWM: edge fidelity matters; jitter maps into visible artifacts and control noise.

Fail-safe & default state

  • Define the safe output state during missing supply or link loss (high/low/high-Z).
  • Verify behavior in the UVLO region to avoid “in-between” toggles.
  • Use deterministic defaults for enable/fault lines; keep buses quiet on failure.

Timing budget (edge-to-edge)

  • Account for propagation delay, jitter, and channel-to-channel skew.
  • Use worst-case (min/max over temperature and supply), not typical values.
  • Preserve margin against setup/hold windows and sampling points.

Isolated supply requirement

  • Many isolators require a barrier-side supply (VISO).
  • Brownouts on VISO can create spurious transitions that resemble EMI issues.
  • Sequence and decouple VISO as a first-class reliability item.

Evidence fields to record in reviews: data rate, channel skew, UVLO behavior, and propagation delay/jitter. These parameters directly determine whether a control bus remains deterministic under real switching dv/dt.

Digital Isolation: Timing & Default States SPI • I²C • PWM • GPIO LV Control (MCU) MCU / DSP control + telemetry SPI SCLK • MOSI • MISO • CS I²C SCL • SDA (bi-dir) PWM / GPIO edges + defaults Isolation Barrier Multi-Channel Isolator VISO isolated supply UVLO default state Barrier-Side Logic Control ASIC protection / interface Timing delay • jitter • skew Fail-safe quiet bus on fault CMTI stress glitch risk common-mode transient Cite this figure
Figure F3A — Multi-channel digital isolation (timing, UVLO defaults, and isolated supply). Jump to H2-3

H2-4. Isolation Amplifiers & ΣΔ Modulators

Focus: analog path vs bitstream path • filtering • ENOB vs latency

Isolated measurement can be implemented as a linear isolation amplifier (an “analog-like” channel across the barrier) or as an isolation ΣΔ modulator (a high-rate 1-bit bitstream that becomes a number only after digital filtering). The choice is a system trade-off: error sources differ, required processing differs, and the achieved resolution depends on filter design.

Linear isolation amplifier (continuous output)

  • Integration is straightforward with a conventional ADC.
  • Dominant risks: offset drift, gain error, and analog noise floor.
  • Best when bandwidth and delay must remain small and predictable.

Isolation ΣΔ modulator (1-bit bitstream)

  • Oversampling pushes quantization noise out of band (noise shaping).
  • Requires decimation filtering; ENOB is achieved after filtering.
  • Dominant risks: clock dependency, filter misconfiguration, and added latency.

Oversampling & digital filtering

  • OSR and filter order set the trade-off between bandwidth, noise, and group delay.
  • Higher OSR can improve in-band noise, but typically increases latency.
  • Filter choices must match control-loop response needs.

Evidence fields for reviews

  • Gain error & offset drift (over temperature and supply).
  • SNR and ENOB after filtering at the intended bandwidth.
  • Sampling clock dependency (jitter/frequency tolerance effects).

For ΣΔ paths, ENOB should be evaluated at the chosen OSR and decimation filter settings; for linear paths, the ADC reference and conditioning bandwidth set the practical noise floor.

Isolated Measurement: Linear vs ΣΔ Path filtering • ENOB • latency HV Sense Domain Shunt / Sensor current or voltage Front-end scale + anti-alias Error Sources offset • noise • drift Isolation Barrier Linear Isolation Amplifier Path Iso Amp gain • offset ADC bandwidth Isolation ΣΔ Modulator Path ΣΔ Modulator 1-bit stream Decimation OSR • filter ENOB • delay MCU Control Loop bandwidth budget clock dependency Cite this figure
Figure F3 — Linear isolation amplifier vs ΣΔ modulator path (filtering, ENOB, and latency). Jump to H2-4

H2-5. Signal Conditioning Fundamentals

Goal: physical quantity → ADC-acceptable signal

Signal conditioning converts a physical quantity into a voltage (or differential voltage) that an ADC can acquire with predictable error and stable settling. The design target is not a “clean-looking waveform” but an input that fits the ADC range, drives the sampling network correctly, and maintains noise and drift within the control budget.

Shunt scaling & range planning

  • Map the expected signal range into the ADC dynamic range (avoid using only a small fraction of full-scale).
  • Keep maximum input below clipping while preserving low-end resolution against offset and drift.
  • Budget self-heating and temperature drift as load-dependent error sources.

Current sense resistor selection

  • Choose value and power rating to balance loss vs SNR; validate temperature rise at worst-case load.
  • Prefer Kelvin sensing to prevent routing resistance from becoming gain error.
  • Track long-term drift and TCR as lifetime contributors to measurement mismatch.

RC anti-alias & input drive

  • Use an RC network to limit high-frequency content before sampling to reduce folding into baseband.
  • Verify settling time against the ADC sampling window; high source impedance can cause systematic under-reading.
  • Pick bandwidth as a trade-off: wider bandwidth raises noise; narrower bandwidth increases response delay.

Level shifting & gain staging

  • Shift common-mode or baseline to keep the signal within the ADC input range under all conditions.
  • Stage gain so the “typical operating region” occupies a large portion of full-scale without saturating on peaks.
  • Validate reference compatibility and headroom across temperature, supply tolerance, and transient events.
Full-scale voltage ADC Vref compatibility Bandwidth vs noise Settling time

Review evidence should include worst-case full-scale margin (no clipping), measured settling across sampling rates, and noise RMS within the intended measurement bandwidth.

Conditioning Chain to ADC scale • shift • filter • settle Physical Current / Voltage range Shunt ΔV = I · R Kelvin Gain staging G Level shift Vcm RC Anti-alias limit HF before sampling fc ADC full-scale + reference FS Vref Verification badges Full-scale Bandwidth Noise Settling Cite this figure
Figure F5 — Conditioning blocks that map a physical quantity into an ADC-acceptable signal. Jump to H2-5

H2-6. Filtering Strategy & Noise Immunity

Goal: reject PWM/switching artifacts without breaking delay budget

A single RC can reduce high-frequency noise but often cannot simultaneously meet ripple rejection, anti-alias protection, and control-loop delay constraints. A robust strategy combines analog anti-alias filtering (to keep unwanted energy out of the ADC) with digital filtering (to shape bandwidth and improve stability), while managing phase and group delay budgets.

Analog vs digital filtering roles

  • Analog: attenuate HF components before sampling to reduce folding into the measurement band.
  • Digital: control bandwidth and smooth readings; tune order and cutoff without changing hardware.
  • Both: must respect delay and stability margins in the control loop.

Cutoff frequency selection

  • Set cutoff below dominant interference (PWM ripple and switching harmonics) while preserving response needs.
  • Validate that the chosen cutoff does not introduce unacceptable group delay.
  • Use worst-case conditions (temperature, tolerance, sampling rate changes).

PWM ripple rejection

  • PWM ripple can appear as baseband noise when sampling is not synchronized.
  • Attenuation targets should be specified in dB at the PWM fundamental and key harmonics.
  • Measure ripple residual at the filter output and at the final reported value.

Switching-frequency folding

  • Insufficient anti-aliasing allows switching components to fold into baseband.
  • Folded artifacts can look like low-frequency drift or unstable feedback.
  • Confirm with spectra before/after filtering and by changing sampling frequency.
Filter order Phase delay Group delay Attenuation (dB)
Filtering Strategy & Noise Immunity anti-alias • folding • delay Noise sources PWM ripple switching harmonics CMTI spikes Filter chain Analog anti-alias fc ADC sampling Fs Digital filter order + decimation order delay Stable value anti-alias prevents folding attenuation target (dB) group delay Cite this figure
Figure F6 — Combining analog anti-alias and digital filtering to reject PWM/switching artifacts while managing delay. Jump to H2-6

H2-7. Range Scaling & Calibration

Goal: use ADC range efficiently and make error auditable

Range scaling and calibration are a coupled design: scaling determines whether drift and noise dominate, while calibration determines whether the remaining error can be bounded and tracked over temperature and lifetime. A robust approach keeps the typical operating region within a large portion of ADC full-scale without saturating on peaks, then applies calibration and drift compensation to maintain consistency across units.

Gain selection & dynamic range

  • Allocate headroom for worst-case peaks and tolerance drift to avoid clipping.
  • Maximize full-scale utilization in the typical region to preserve low-end resolution.
  • Validate that the minimum signal remains above offset and noise floors after filtering.

Two-point calibration (offset + gain)

  • Use two reference points within the linear region to estimate offset and gain.
  • Verify residual error at mid-range to detect non-linearity or self-heating artifacts.
  • Keep calibration conditions (temperature, bandwidth, timing) consistent and recorded.

Drift compensation & temperature correction

  • Separate static coefficients from runtime correction (temperature and load-dependent drift).
  • Use an NTC input to model temperature-driven error terms and improve unit-to-unit matching.
  • Confirm compensation against thermal time constants to avoid over-correcting transient states.

Coefficient storage & traceability

  • Store calibration coefficients with versioning and integrity checks (e.g., CRC).
  • Define EEPROM layout and update policy to prevent coefficient mismatch after firmware changes.
  • Report drift in ppm/°C before and after compensation for measurable improvement.
Calibration coefficients EEPROM storage + CRC Temp drift (ppm/°C)

Acceptance evidence should include full-scale utilization, saturation margin, mid-point residual after two-point calibration, and temperature sweep results showing drift reduction with compensation enabled.

Range Scaling & Calibration Map gain • FS • coeff • drift Input range MIN TYPICAL MAX + transients goal: avoid clipping use FS well protect low-end Mapping Gain select G, headroom ADC window FS utilization SNR / offset floor low-end guard Calibration Two-point offset + gain coeff CRC + version EEPROM NTC temp drift comp ppm/°C Cite this figure
Figure F7 — Mapping signal range into ADC full-scale, then bounding error with coefficients and temperature correction. Jump to H2-7

H2-8. Isolation Power & Biasing

Goal: stable VISO + correct sequencing to avoid mid-state failures

Isolation-side power is a frequent hidden root cause of unstable measurements and unexpected default states. The bias supply must provide a clean and predictable VISO rail across load variation and startup, while sequencing and timing ensure the isolation devices enter a defined valid state before measurements are trusted.

Isolated DC-DC bias supply

  • Choose an isolated bias approach that maintains regulation from light load to worst-case load.
  • Measure ripple at VISO and track its coupling into the measurement output.
  • Budget power consumption to avoid thermal drift and marginal startup conditions.

Push-pull micro transformer block

  • Use push-pull drive to generate isolated bias where integrated solutions are not used.
  • Validate output ripple behavior in startup and light-load regions.
  • Keep the focus on system behavior (timing/ripple), not magnetics design details.

Power sequencing & startup timing

  • Define when measurements become valid: VISO stable + references stable + ADC ready.
  • Prevent “UVLO mid-state” by enforcing default outputs until validity criteria are met.
  • Record startup delay and ensure it meets system control and safety requirements.

Safety boundary evidence fields

  • Maintain creepage/clearance constraints across the isolation barrier.
  • Track startup delay, ripple, and total bias power as auditable parameters.
  • Confirm behavior under worst-case line/load/temperature conditions.
Isolation creepage Output ripple Startup delay Power consumption
Isolation Power & Sequencing VISO • ripple • timing Primary domain VIN / rails main supplies Sequencing rules define “valid” window Isolation barrier creepage Isolated bias generation Isolated DC-DC Push-pull micro xfmr VISO rail ripple + load regulation ripple Powered isolation devices Isolator Iso amp / ΣΔ MCU / ADC startup delay valid window Cite this figure
Figure F8 — Isolated bias supply options, VISO ripple coupling, and startup sequencing for valid measurements. Jump to H2-8

H2-9. Safety & Compliance Considerations

Goal: auditable isolation boundary for lighting approvals

In lighting systems, isolation is a safety boundary that must remain valid across working voltage, expected transients, and the lifetime environment. Compliance is achieved by tying insulation class and geometry (creepage/clearance) to a defined working voltage and impulse withstand target, while keeping leakage current and surge coordination within acceptable limits.

Working voltage & insulation class

  • Define the working voltage that drives creepage/clearance and insulation requirements.
  • Choose basic vs reinforced insulation based on the safety boundary and single-fault expectations.
  • Maintain traceability by recording the chosen class and its justification.

Creepage & clearance (geometry that must be preserved)

  • Clearance addresses air breakdown under transient stress; creepage addresses surface conduction risks.
  • Account for environment factors (e.g., pollution exposure and material behavior) when setting geometry.
  • Audit PCB/barrier layout against the declared safety boundary constraints.

Leakage current paths

  • Identify capacitive coupling and return paths that can create touch-current complaints or false sensing.
  • Measure leakage under realistic grounding and mains conditions.
  • Keep leakage evidence linked to the same configuration used for approvals.

Surge coordination & impulse withstand

  • Coordinate clamping and energy sharing so isolation components are not overstressed by surge events.
  • Use impulse withstand as an auditable capability under defined transient profiles.
  • Validate that protective behavior does not compromise insulation integrity over time.
IEC standards reference Working voltage Impulse withstand Leakage current

A strong compliance record links each geometry and insulation decision to a declared working voltage and a measured impulse withstand outcome, with leakage measurements captured under a defined mains/grounding configuration.

Safety & Compliance Map working V • geometry • leakage • surge Inputs Working voltage IEC ref Insulation Basic Reinforced Geometry that must be preserved Creepage surface path pollution / material Clearance air gap altitude / transient Leakage Coupling CM path I_leak Surge coordination → impulse withstand Surge Clamp Energy share Impulse withstand Cite this figure
Figure F9 — Compliance logic that ties geometry and insulation class to working voltage, leakage paths, and surge/impulse evidence. Jump to H2-9

H2-10. Typical Architectures in Lighting Drivers

Goal: application-level isolation signal-flow templates

Typical lighting-driver architectures reuse the same isolation and conditioning blocks but place them at different boundaries: current sensing paths often need strong noise rejection and stable timing; CV feedback paths emphasize delay and robustness; interface isolation focuses on default-state behavior and bias stability. The templates below connect isolation choices to auditable fields such as CMTI, delay, ripple, working voltage, and impulse withstand.

Flyback CC current sensing with ΣΔ

  • Shunt → ΣΔ / iso amp → digital filter → MCU/ADC reporting.
  • Focus: folding risk, sampling clock dependency, VISO ripple injection.
  • Evidence: CMTI, ENOB after filtering, startup valid window.

LLC CV feedback isolation

  • Vout sense → isolation → controller/MCU feedback.
  • Focus: delay and group-delay budget, default states during startup.
  • Evidence: propagation delay, group delay, impulse withstand.

DALI interface isolation (boundary placement)

  • MCU ↔ isolator ↔ transceiver/bus side.
  • Focus: UVLO/default output behavior, bias rail stability under light-load.
  • Evidence: VISO ripple, startup timing, leakage/coupling paths.
kVrms / insulation class CMTI Delay / group delay Ripple / sequencing Working V / impulse
Lighting Driver + Isolation Signal Flow Map templates for CC / CV / bus HV / Power stage Flyback / CC sense point LLC / CV feedback point DALI bus side interface boundary Isolation barrier creepage kVrms CMTI Control domain MCU + ADC filters / logs Delay budget VISO ripple Evidence fields working V • impulse • coeff working V impulse coeff ΣΔ iso DALI filter default Cite this figure
Figure F10 — Application-level signal-flow templates for CC sensing, CV feedback, and DALI interface isolation. Jump to H2-10

H2-11. Design Pitfalls & Field Failures

Goal: triage failures with 2 evidences + 1 first fix

Field issues in lighting isolation and conditioning chains are often repeatable once the correct evidence signals are captured. Each pitfall below provides one observable symptom, two concrete evidence checks, and one fastest “first fix” to stabilize the system before deeper optimization. Example MPNs are included to anchor the discussion to real implementation options.

1) CMTI insufficient → false trigger / spurious toggles

Phenomenon: Random GPIO/PWM edges, latch events, or corrupted frames appear only during fast switching or surge-like stress.
  • Evidence 1: Correlate the glitch timing with the highest dv/dt moment (e.g., switch-node edge) using a logic analyzer + scope trigger.
  • Evidence 2: Reducing dv/dt (temporary slower edges) reduces the false events without changing firmware logic.
First fix: Add a deglitch window / input qualifier and enforce fail-safe default states on isolated channels. If a part swap is allowed, prioritize higher-CMTI families such as TI ISO77xx / TI ISO67xx, Analog Devices ADuM14xx/ADuM11xx, or Silicon Labs Si86xx (select by channel count and data rate).
Key field: CMTI (kV/µs) Key field: prop delay / jitter

2) Offset drift → brightness shift / slow setpoint creep

Phenomenon: Brightness slowly drifts with temperature or runtime under the same command; cold restart partially resets the error.
  • Evidence 1: Output error correlates with board temperature (NTC reading) and follows warm-up / cool-down hysteresis.
  • Evidence 2: A “zero input” or shorted reference check shows a non-zero reading that moves with temperature.
First fix: Implement minimal two-point calibration (offset + gain) and store coefficients with version + CRC. If the analog isolator stage is the drift source, consider iso amplifier / ΣΔ families designed for precision measurement such as TI AMC1301/AMC1311, TI ISO224, Analog Devices AD202/AD204 (iso amp class), or ΣΔ modulators like TI AMC1306M25 / Analog Devices AD7403 (choose per interface + filter plan).
Key field: offset drift (µV/°C) Key field: coeff + EEPROM/Flash

3) ADC noise aliasing → “random” ripple that tracks PWM/switching

Phenomenon: Measurement shows periodic wobble or beat-frequency ripple; changing PWM or sampling changes the wobble pattern.
  • Evidence 1: Sweeping PWM frequency (or sampling rate) moves the observed ripple frequency (alias signature).
  • Evidence 2: Adding stronger anti-alias filtering reduces in-band ripple without changing the plant.
First fix: Add a simple anti-alias RC (or 2nd-order) ahead of the ADC / modulator, then synchronize sampling to PWM (or avoid harmonic relationships). For isolated measurement paths, pair ΣΔ parts (e.g., AMC1306M25, AD7403) with a filter implementation that preserves headroom and avoids overflow (see Pitfall 5).
Key field: cutoff / group delay Key field: ENOB after filtering

4) Isolation DC-DC ripple injection → measurement ripple / frame instability

Phenomenon: A fixed-frequency ripple appears on the measured signal or isolated output; magnitude changes with isolated-side load.
  • Evidence 1: Ripple on VISO and ripple on the measurement/output share the same frequency and phase.
  • Evidence 2: Ripple worsens during startup or light-load regions (common for some isolated bias solutions).
First fix: Add local decoupling + post regulation (LDO) or an RC/π filter on the isolated rail, and delay “valid measurement” until VISO is stable. Example isolated power building blocks include Analog Devices ADuM5020/ADuM6020 (iso power), TI SN6505 (transformer driver), or iso-power integrated isolators such as TI ISOW7841 (when channel set fits).
Key field: VISO ripple Key field: startup delay

5) Digital filter overflow → stuck output / saturation / invalid steps

Phenomenon: Filtered output sticks at max/min, jumps unexpectedly, or becomes invalid after transients or during warm-up.
  • Evidence 1: Intermediate values (accumulator/integrator) exceed numeric bounds or hit saturation counters.
  • Evidence 2: Failures cluster around startup, sudden input steps, or abnormal ΣΔ bitstream segments.
First fix: Add clamping + safe reset of filter state, and discard a defined warm-up window before trusting output. Widen internal bit-width (or use floating point where feasible) and keep scaling consistent with ADC/modulator full-scale. For ΣΔ chains, validate the filter headroom explicitly for parts like AMC1306M25 / AD7403 under worst-case inputs.
Key field: numeric headroom Key field: warm-up discard window

Practical logging tip: capture one “correlation channel” (switch-node edge, PWM timing, or VISO ripple) alongside the isolated output. This single correlation often separates CMTI, aliasing, and ripple-injection classes within one test session.

Field Failure Triage Map symptom → evidence → first fix Symptoms Evidence gates First fix Spurious toggles only on fast edges Timing aligns with dv/dt glitch appears at edge deglitch + fail-safe higher CMTI option Brightness creep temperature related Zero check drifts NTC correlates 2-pt cal + temp comp store coeff + CRC Beat-frequency ripple changes with PWM Ripple moves when PWM moves alias signature anti-alias + sync sampling stable low-pass Fixed ripple in output load dependent VISO and output same freq startup/light-load worse post-reg + delay valid reduce coupling Cite this figure
Figure F11 — A practical triage flow that maps symptoms to evidence gates and a fastest first-fix action. Jump to H2-11

Request a Quote

Accepted Formats

pdf, csv, xls, xlsx, zip

Attachment

Drag & drop files here or use the button below.

H2-12. FAQs

Format: 1 conclusion + 2 evidence checks + 1 first fix (40–70 words)

Each answer points back to the evidence chain in H2-3…H2-11.

Current reading drifts with temperature—offset or shunt self-heating?

Most temperature-linked drift is measurement-chain offset unless the shunt temperature rise is proven. Evidence: compare error versus NTC/board temperature during warm-up/cool-down, and run a zero/short-input check—if the reading still moves, offset dominates. First fix: apply two-point calibration plus temperature compensation and log coefficients with CRC; consider precision iso parts like TI AMC1311 or AD7403.

Maps: H2-4, H2-7, H2-11
PWM ripple shows in ADC—filter bandwidth or sampling sync?

If ripple “moves” when PWM or sampling changes, it is aliasing/sync, not just bandwidth. Evidence: sweep PWM frequency (or sample rate) and watch the ripple frequency shift, then compare before/after a stronger anti-alias RC. First fix: synchronize sampling to PWM (or avoid harmonic ratios) and tighten the analog cutoff; ΣΔ paths like TI AMC1306M25 need a headroom-safe digital filter.

Maps: H2-5, H2-6, H2-11
Isolation amp saturates at high load—range scaling issue?

High-load “flat-top” readings usually mean the input chain is hitting full-scale before the ADC expects it. Evidence: check whether the iso amp/ADC pin approaches reference rails at peak load, and confirm piecewise nonlinearity (mid-load OK, high-load compressed). First fix: reduce gain or increase shunt range, add an explicit over-range flag, and consider wide-input solutions like TI ISO224 or TI AMC1301.

Maps: H2-4, H2-5, H2-7
Digital isolator glitches during switching edge—CMTI too low?

Edge-correlated glitches are a classic CMTI margin problem, not a random firmware bug. Evidence: time-align the isolated output with the switch-node dv/dt peak, and temporarily slow dv/dt—if errors drop, CMTI is implicated. First fix: add input qualification/deglitch and enforce fail-safe default states; if a swap is allowed, prioritize higher-CMTI families like ADuM11xx, TI ISO77xx, or Si86xx.

Maps: H2-3, H2-1, H2-11
ΣΔ bitstream unstable—clock jitter or filter config?

Unstable ΣΔ results usually come from clock integrity or a numerically fragile filter configuration. Evidence: change clock source/jitter conditions and see if the noise floor shifts, and log filter intermediate values for saturation/overflow counters. First fix: lock a low-jitter sampling clock, discard a warm-up window, and add clamp/reset logic in the filter; common parts include AD7403 and TI AMC1306M25.

Maps: H2-4, H2-6, H2-11
EMC test causes false reading—ground reference or barrier noise?

During EMC stress, false readings usually follow a ground/reference shift or barrier-coupled common-mode injection. Evidence: repeat the test with a controlled reference/ground scheme and see if the symptom changes, then correlate anomalies with a “reference channel” like switch-edge timing or VISO ripple. First fix: standardize the reference/return path and add deglitch/qualification at the isolated interface; high-CMTI isolators like ISO7721 or ADuM141E help.

Maps: H2-9, H2-1, H2-11
After surge, readings shift—calibration lost or damage?

Post-surge shifts are either coefficient corruption/mismatch or permanent analog damage. Evidence: verify calibration CRC/version and compare pre/post coefficient sets, then run a zero-input and linearity spot-check—residual offset/noise suggests hardware stress. First fix: fall back to a known-safe coefficient profile and log the surge event; if zero/linearity fails, inspect the isolation chain and consider replacing the sensing front-end (e.g., AMC1311 or ISO224).

Maps: H2-7, H2-9, H2-11
ADC noise floor higher than spec—layout or bias ripple?

If the noise floor exceeds the datasheet expectation, suspect bias ripple injection before blaming “layout” broadly. Evidence: measure VISO ripple and compare frequency/phase with the output noise, and short the input to see whether noise persists unchanged. First fix: add isolated-side decoupling plus post-regulation (LDO) or π filtering and delay valid measurements until rails settle; iso-power blocks like ADuM5020 or TI ISOW7841 need careful output filtering.

Maps: H2-8, H2-5, H2-11
Isolated DC-DC causes ripple injection—decoupling issue?

Ripple injection is confirmed when the measured ripple matches the isolated DC-DC switching signature. Evidence: identify a fixed ripple frequency that equals the DC-DC fundamental/harmonic, and verify ripple amplitude changes with isolated-side load or startup/light-load state. First fix: add local high-frequency decoupling, then a π/RC filter or LDO on the isolated rail, and enforce a “valid after Tdelay” measurement window; examples include SN6505 (with transformer) and ADuM5020 iso power.

Maps: H2-8, H2-6, H2-11
Two boards give different reading—tolerance stack or calibration?

Board-to-board mismatch is usually tolerance stacking unless calibration coverage is incomplete. Evidence: compare raw code values on identical inputs to see if the offset/gain delta is stable, then apply the same calibration procedure and verify whether the spread collapses. First fix: standardize the calibration workflow (versioned coefficients + CRC) and tighten the gain chain mapping; if the isolator stage dominates drift/spread, choose consistent measurement-grade parts such as ISO224 or AMC1301.

Maps: H2-7, H2-5, H2-11
Low-frequency drift over months—aging of isolation amp?

Slow multi-month drift can be aging, but it must be separated from temperature and coefficient issues. Evidence: review long-term logs to confirm a monotonic trend with weak temperature correlation, and compare against a reference channel or periodic zero-check to rule out system-wide shifts. First fix: implement scheduled field recalibration and threshold alarms, and store coefficient history for traceability; stable measurement chains often use parts like AMC1311 or ΣΔ modulators like AD7403 with robust filtering.

Maps: H2-4, H2-7, H2-11
Measurement fine in lab but not in field—common-mode transient?

Lab-pass/field-fail is frequently common-mode transient stress that never appears on a quiet bench. Evidence: correlate failures with switching edges, plug/unplug events, or ground changes, and add one correlation probe (switch-edge timing or VISO ripple) to confirm alignment with anomalies. First fix: deploy deglitch/qualification plus fail-safe defaults and raise CMTI margin or isolate-side rail stability; candidate isolators include ISO7721, ADuM141E, and Si864x families.

Maps: H2-1, H2-3, H2-11

Tip: keep a “correlation channel” (switch-edge marker or VISO ripple) in every field capture. It quickly distinguishes CMTI glitches, aliasing, and ripple injection.