123 Main Street, New York, NY 10001

← Back to: Battery Charging / Gauging / Protection / BMS

Intro & Scope: Why HV Aux Bias Is a Separate Topic

Domain: Charging-only · do not mix with pack-FET pages

High-voltage battery systems in EV/HEV platforms often sit at 200–450 Vdc during charging, but the BMS “brain” (measurement AFE, MCU, logging, isolated comms) only accepts 5 V or 3.3 V. If this low-voltage brain is powered from the charger’s own auxiliary or from a non-isolated low-voltage rail, it will lose power as soon as the charger/bus sags, and critical charge-interruption events can no longer be logged. That is why the HV aux bias must be treated as its own topic.

In this page we keep the discussion strictly inside the charging branch of your BMS template: we only talk about an isolated, high-voltage-tolerant auxiliary supply whose job is to feed the BMS measurement and control domains and to stay alive long enough to write logs when the bus dips.

What we must write here

  • Typical HV charging bus: 200–450 Vdc (sometimes 250–420 Vdc in real cars).
  • Why reusing OBC aux rails is unsafe for logging: OBC turns off first → BMS “forgets”.
  • Isolation level we expect: functional → basic → reinforced, automotive envelope only.
  • Measurement-domain constraints: Y-cap, transformer CM path, and layout all change leakage readings.
  • Why we need multiple outputs: 5 V for AFE, 3.3 V for MCU/logging, an extra bias for isolated comm.
  • Why this lives under Charging: charging is exactly when the HV bus dips but logs must be kept.

What we do not write here

  • No OBC / PFC / LLC main power stages.
  • No pack contactor / pack-FET drivers.
  • No HV insulation / leakage detection algorithm itself — only the power that feeds it.
HV Aux Bias in BMS charging branch High-voltage bus feeding an isolated flyback to power AFE, MCU/logging, and isolated communication rails. HV Bus 200–450 Vdc Isolated DC/DC flyback / push-pull secondary regulated 5 V → AFE measurement domain 3.3 V → MCU/log ride-through enabled Isolated comm CAN / RS-485 / LIN Charging branch only do not mix with pack-FET / leakage pages
Figure 1 — HV Aux Bias role in BMS charging branch: isolated DC/DC from HV bus feeding AFE, MCU/logging, and isolated communication.

Topology Choices: Isolated Flyback vs Push-Pull (for BMS Aux)

Once the scope is fixed — “isolated HV aux for the BMS, in the charging domain” — the next question is which topology we allow. For most BMS auxiliary rails in the 5–15 W band, an isolated flyback with secondary regulation is the default choice. Push-pull is reserved for cases where you already have a matched transformer, you need multiple tightly regulated outputs, or you want a cleaner EMI profile. PSR (primary-side regulated) solutions are discouraged because they introduce output drift that can corrupt measurement-domain accuracy.

What to explain

  • Power window: most BMS aux rails stay within 5–20 W → flyback first.
  • Isolation drives transformer choice: automotive isolation → often custom transformer.
  • HV bus can dip: 250 → 420 V ranges; topology must remain stable and not restart.
  • Why PSR is not liked: measurement-domain wants stable 5 V / 3.3 V → go secondary-regulated.
  • When push-pull is valid: multi-output, tighter EMI, existing automotive controller, symmetric winding.

What we do not include

  • LLC, half-bridge, PSFB → those belong to OBC/high-power DC/DC pages.
  • Full synchronous bridges → only a short mention if paired with push-pull.
  • Traction / body domain supplies → out of this charging scope.
Topology decision for BMS HV aux bias Decision flow: flyback for ≤15 W, push-pull for multi-output/tight regulation, PSR discouraged for BMS measurement domain. Power ≤ 15 W ? BMS aux / charging domain Isolated flyback secondary-regulated · opto/TL431 Push-pull multi-output · better EMI · existing auto ctrl PSR? → No for BMS meas. output drift corrupts ADC / insulation data Avoid PSR substitutions in purchasing.
Figure 2 — Topology decision flow for BMS HV aux bias: flyback is default; push-pull for multi-output/tighter EMI; PSR discouraged.

With this chapter in place, later sections (Isolation & Safety, Secondary Regulation, Procurement) can simply reference: “use isolated flyback with secondary regulation unless a project-specific push-pull is already qualified.”

Isolation & Safety Envelope (Creepage / Clearance / Grade)

Charging-domain aux supply · automotive isolation required

This chapter explains why low-cost consumer/offline SMPS controllers cannot be dropped in to replace an automotive HV aux bias in the BMS charging branch. The BMS sits on a 200–450 Vdc bus, feeds the measurement domain, and must keep logging even when the charging/OBC front-end drops out. That makes isolation grade, creepage, clearance and hi-pot testing non-negotiable and visible in the BOM.

We define the isolation stack here first so that later chapters (multi-output, procurement, cross-brand substitutions) can simply refer to this page: “comply with Chapter 3 isolation envelope.”

What must be defined

  • Isolation levels: functional / basic / reinforced → this page: basic minimum, reinforced recommended.
  • Creepage & clearance: calculated from highest pack/bus voltage and pollution degree.
  • Hi-pot / dielectric test points: both on transformer and on the final assembly.
  • Controller class: “DC bus only / automotive HV bus capable” — not generic AC offline.
  • Regional differences: EU / US / China may push creepage higher → write it in the BOM remark.

Procurement remark (can be copied)

“Auxiliary HV isolated supply for BMS shall provide automotive-grade isolation at the bus voltage level, with creepage/clearance per project region (EU/US/CN). Consumer offline SMPS controllers shall not be used as replacements. If PCB creepage cannot be met, it shall be achieved by transformer construction.”

What we do not cover here

  • No full-vehicle HV harness design.
  • No vehicle-level insulation fault algorithm.
  • No OBC/PFC power stage design.
Isolation envelope for BMS aux bias HV bus on the left, transformer and isolation barrier in the middle, low-voltage measurement/control domain on the right, with creepage/clearance/withstand rules. HV Bus 200–450 Vdc Isolation barrier XFMR automotive grade hi-pot tested Low-voltage domain AFE · MCU · Logger · Isolated comm Creepage ≥ X mm (per bus & pollution degree) Clearance ≥ Y mm (board may not be enough) Withstand ≥ Z kV (xfmr + final assembly) Use automotive-grade isolation. Do not replace with consumer offline SMPS.
Figure 3 — Isolation envelope for BMS aux bias: HV bus on the left, isolation barrier and transformer in the middle, and low-voltage measurement/control domain on the right. Creepage, clearance and withstand must be met.

For EU/US/China projects, specify the target region in the BOM remark so that PCB-level creepage/clearance can be backed up by transformer insulation when the board cannot meet the distance. This prevents purchasing from dropping in non-automotive offline controllers.

Secondary Regulation & Multi-Output Bias Rails

Measurement-domain accuracy · block PSR substitutions

BMS auxiliary rails power the most sensitive part of the system: AFEs sampling high-voltage cells, MCUs logging charge events, and isolated communication. These circuits cannot tolerate 1–2% output drift from primary-side regulation (PSR). That is why this page requires secondary-regulated flyback with opto-isolated feedback and a post-regulated clean rail (typically 3.3 V) for measurements and logging.

Architecture to write

  • Main output: 5 V, closed-loop, secondary-sensed, opto/TL431.
  • Clean output: 3.3 V (or 1.8 V) made by an LDO from the 5 V to isolate AFE/Logger loads.
  • Load events: AFE may pulse current during insulation/leakage measurement → LDO decouples MCU/log.
  • Automotive environment: optocoupler CTR and reference drift over temperature → must be qualified.
  • Purchasing rule: “if controller/opto/reference is substituted → re-validate AFE accuracy.”

PSR hazard to call out

“Primary-side regulated converters are not acceptable for BMS measurement-domain auxiliary rails because transformer tolerance, layout coupling and HV-bus noise all produce output drift. Any PSR-based replacement shall trigger measurement-domain re-validation.”

Secondary-regulated flyback for BMS HV bus primary, transformer, opto-isolated feedback, 5 V regulated main output and 3.3 V LDO-clean rail. PSR substitutions must be re-validated. Primary HV bus 200–450 Vdc XFMR isolated opto / TL431 feedback 5 V main (closed loop) feeds digital, LDOs, comms 3.3 V via LDO clean for AFE / Logger PSR → re-validate AFE accuracy. transformer / layout / HV noise affect sampling Secondary-regulated flyback only. Log rails require stable 3.3 V; PSR not allowed.
Figure 4 — Secondary-regulated flyback for BMS: HV bus on primary, transformer with opto feedback, 5 V main regulated output and 3.3 V LDO-clean rail for measurement and logging. PSR changes require re-validation.

To keep the BMS measurement-domain stable, add to your purchasing notes: “secondary-regulated flyback / opto-isolated feedback / TL431 reference / post-regulated 3.3 V for AFE.” Any change to these parts → re-run AFE accuracy and leakage measurement validation.

Ride-Through / Hold-Up for Logging

Not OBC bulk · for logging continuity only

During real charging events — unplug, contactor lifting, short HV bus valleys, or charger hiccups — the auxiliary input for the BMS also sags. If the BMS MCU and logging rail collapse at the same time, it becomes impossible to store “what voltage we had,” “which charge phase we were in,” and “what the temperatures were.” This chapter defines a logging-grade hold-up (tens to hundreds of ms) and not an OBC-grade bulk capacitor.

Drop / sag scenarios to describe

  • Charging gun unplugged → HV bus collapses in tens of ms.
  • Contactor open/close → 50–150 ms valley on the bus.
  • Charger front-end current limit / hiccup → short, deep sag.
  • Line/bus oscillation → aux follows the dip.

Logging requirement

BMS must write: timestamp + bus voltage + charge state/step + temperature + fault code.

MCU + AFE + isolated comm = Iload. Minimum time to finish = thold. Allowable voltage drop = ΔV = Vstart − Vend.

Capacitor sizing formula (BOM ready)

C = Iload × thold ÷ ΔV

Where: Iload = AFE + MCU + isolated comm, thold = time to complete log (50–200 ms typical), ΔV = allowed drop (e.g. 5.0→4.5 V or 3.3→3.0 V).

“Hold-up capacitor value shall be recomputed whenever controller, switching frequency or UVLO is changed.”

Where to place the hold-up

  • Secondary-side cap: simplest, directly sustains 5 V / 3.3 V logging rails.
  • Primary-side small bulk: prevents controller reset during bus dips.
  • Prefer secondary-side for logging; add primary bulk only when controller UVLO is tight.
Ride-through capacitor for logging HV aux output feeding a secondary capacitor sized by C = I × t ÷ ΔV to keep BMS logging alive during dips. Not OBC bulk. Not OBC bulk! Logging only. sustain tens–hundreds of ms for MCU/AFE/logs HV Aux Output 5 V / 3.3 V Hold-up C secondary side Iload = BMS + AFE + comm thold = 50–200 ms ΔV = Vstart − Vend C = I × t ÷ ΔV recompute when controller / UVLO changes
Figure 5 — Ride-through capacitor sizing for HV aux: use C = I × t ÷ ΔV for logging-only hold-up; place on secondary for best effect.

This hold-up is meant to finish the log, not to keep the whole charger alive. Write the formula in the BOM so that any later substitution of controller / UVLO / switching frequency will trigger a mandatory re-check.

Startup, Bias & Pre-Charge of HV Controllers

Match UVLO window · avoid restart loop during bus dips

HV auxiliary controllers for BMS often power up by charging a VCC capacitor through a startup resistor from the HV bus. When the bus sags during contactor actions (e.g. 400 V → 280 V → 420 V), this startup path may no longer deliver enough energy, so the controller drops below its UVLO-off level and restarts again. This is why UVLO thresholds and startup current must not be changed casually in purchasing.

Typical startup path

  • HV bus (200–450 Vdc) → startup resistor → VCC capacitor.
  • Controller VCC rises to UVLO-on → controller starts switching.
  • Auxiliary winding then powers VCC → startup resistor off.

Why it oscillates

  • Bus dips during charging/contactors → startup power not enough.
  • VCC falls below UVLO-off → controller stops → no aux winding.
  • Controller restarts → BMS main MCU experiences brownout or reset.

UVLO window to preserve

Original design might be 12 V on / 8 V off (wide hysteresis).

Do not replace with chips that do 10 V on / 9.5 V off — this narrows the window and causes chatter.

BOM-ready sentences

“Controller UVLO thresholds shall match original design (startup/shutdown).”

“Do not replace with HV controllers that draw higher startup current.”

“Startup / soft-start time shall be coordinated with Chapter 5 ride-through.”

HV startup and UVLO window VCC vs time curve showing UVLO-on and UVLO-off thresholds; HV bus dip causes VCC to fall below UVLO-off and restart. VCC time → UVLO ON (e.g. 12 V) UVLO OFF (e.g. 8 V) Bus dip → VCC falls below UVLO OFF → restart risk keep UVLO window as original; limit startup current Align startup/soft-start with ride-through capacitor in Chapter 5 so controller does not consume the hold-up.
Figure 6 — HV startup and UVLO window: controller VCC rises through the startup path, a bus dip can pull it below UVLO-off and force a restart. Keep original UVLO and startup current.

Keep the startup current, UVLO window, and soft-start time consistent with the original design. Otherwise the hold-up capacitor defined in the previous chapter may no longer cover the logging interval.

EMI / CM Noise Control for Measurement-Domain BMS

EMI will be seen by insulation / leakage measurements

The HV auxiliary supply is a switching, isolated converter. Its primary switching edges, transformer leakage spikes, and secondary rectifier noise can all couple into the BMS measurement domain. This is different from a generic offline SMPS: here the AFE is actually measuring high-voltage behavior, so any common-mode (CM) current — including through a Y-cap — may look like a leakage path. That is why EMI components (Y-cap, snubber/RCD, switching frequency) cannot be removed or replaced casually.

Noise paths to document

  • Primary switching node → transformer leakage spike.
  • Transformer → secondary diode recovery → secondary return.
  • Secondary return → AFE reference ground → measurement channel.
  • Optional Y-cap → controlled CM path → seen by insulation check.

Y-cap trade-off

Y-cap makes EMI plots nicer but creates a deliberate leakage path.

In BMS insulation / leakage measurement this leakage will be detected.

“Y-cap values shall be coordinated with the BMS insulation-measurement page; do not increase Y-cap for EMI without consulting measurement-domain constraints.”

Do not shortcut EMI elements

  • Do not delete / downsize primary snubber or RCD networks.
  • Do not replace transformer with one of weaker shielding.
  • Do not accept controllers with substantially different switching spectrum without re-test.

Grounding / layout note

Make the secondary of the auxiliary supply use single-point / star grounding so converter pulse currents do not circle through the AFE ground. This is especially important when the AFE is doing insulation/leakage checks on the same HV bus.

EMI paths from HV aux to BMS measurement Primary switching noise couples through the transformer to the secondary and then to the AFE reference ground; Y-cap makes a controlled CM path that the insulation check can see. EMI couples into measurement-domain — re-test after substitutions. Y-cap improves EMI but creates measurable leakage. Primary HV switching node spikes / dv/dt XFMR leakage & CM Y-cap / CM leakage path seen by insulation / leakage measurements BMS Measurement Domain AFE · insulation monitor · leakage check spike / CM noise Do not remove snubber / RCD. higher spike → more CM → more measurement error
Figure 7 — EMI paths from HV aux to BMS measurement: primary spike → transformer → secondary return → AFE ground; Y-cap adds a CM path visible to insulation checks.

Whenever controllers, transformers, snubbers, or Y-caps are cross-brand substituted, re-run EMI around the measurement channels. This BMS page is in the charging domain but is bound by the insulation/leakage tolerance of the measurement domain.

Small-Batch Procurement & Cross-Brand Alternatives

≤ 500 pcs · short lead time · re-test EMI / ride-through / isolation

Small-batch automotive orders (≤500 pcs, urgent delivery, dual-SKU acceptable) frequently trigger “looks similar” replacements: a consumer offline flyback in place of an automotive controller, a modified transformer in place of the original construction, or a cheaper PSR/single-output DC/DC in place of the secondary-regulated aux. This chapter lists three real-world substitution scenarios and provides BOM-ready English remarks to block unsafe replacements.

Scenario 1 — Controller out of stock

Purchasing drops in a generic offline flyback controller.

  • Isolation grade may not match the BMS DC bus level.
  • Startup current may be higher → Chapter 5 hold-up not enough.
  • Switching frequency spectrum changes → Chapter 7 EMI must be re-run.

Scenario 2 — Transformer not available

Purchasing wants to change turns/layers/bobbin.

  • Creepage/clearance may be reduced → violates Chapter 3 isolation envelope.
  • Shielding/y-cap coupling changes → measurement leakage changes.
  • Must specify: “transformer construction shall be equivalent.”

Scenario 3 — Cheaper aux DC/DC requested

Single-output or PSR module is proposed.

  • No secondary regulation → AFE and logging rails will drift.
  • Often industrial- or consumer-grade, not automotive.
  • Contradicts Chapter 4 requirement: secondary-regulated flyback only.
Cross-brand substitution risk map Three cards: controller, transformer, regulation. Each shows the risk when replaced in small-batch procurement. Small-batch & cross-brand = re-test EMI, ride-through, isolation. Controller stock-out → generic offline • check isolation grade • check startup current • check f_sw → EMI re-validate Chapter 5 & 7 Transformer no original spec → modify • creepage/clearance change • insulation system change • leakage/Y-cap change re-validate Chapter 3 & 7 Regulation cheaper aux DC/DC • PSR → AFE drift • single output → no clean 3.3 V • non-automotive grade re-validate Chapter 4 & 7 Any substitute → re-test EMI, ride-through, isolation, per this BMS charging-domain page.
Figure 8 — Cross-brand substitution risk map: controller, transformer and regulation changes each create different risks and require re-validation.

BOM remarks to paste

1) Auxiliary bias must remain isolated and secondary-regulated; do not replace with primary-side regulated SMPS.

2) Isolation rating and transformer construction shall match the original automotive design.

3) Re-validate ride-through time and EMI on BMS measurement channels after any cross-brand substitution.

Seven-vendor mapping for HV auxiliary bias (charging domain)

Scope: TI · ST · NXP · Renesas · onsemi · Microchip · Melexis

These series are actually shipped, public parts from the seven vendors. Use them as series slots for an isolated, secondary-regulated HV auxiliary supply that feeds AFE / MCU / logging in a BMS. Do not downgrade to primary-side regulated (PSR) modules when the measurement domain requires stable rails. Each time you cross brands, run the validation list in the next chapter.

Seven-vendor mapping for BMS HV auxiliary bias Seven equally weighted vendor blocks (TI, ST, NXP, Renesas, onsemi, Microchip, Melexis) and a bottom note “re-test EMI / hold-up / isolation”. BMS HV Aux Bias — 7-Vendor Map Isolated · Secondary-regulated · Automotive envelope TI UCC28C43-Q1 isolated flyback keep opto/TL431 ST VIPer26K 1050 V device check creepage NXP TEA1755T HV QR flyback re-test EMI Renesas ISL6753 PWM for isolated re-validate onsemi NCP1207A small batches DC-bus capable Microchip MIC5283 120 V-in LDO clean rails Melexis MLX91220 keep for meas. re-calibrate Any cross-brand substitution → re-test EMI (meas.-domain), ride-through/hold-up, isolation/hi-pot. See validation matrix below.
Figure 9 — Seven-vendor mapping for BMS HV auxiliary bias; each series slot must keep isolation and secondary regulation.

TI slot

Use when you want fully documented automotive isolated flyback.

  • UCC28C43-Q1 — classic current-mode isolated flyback, opto-ready.
  • UCC28740-Q1 — HV flyback with primary-side sensing, use only when AFE tolerance is re-validated.
  • UCC25800-Q1 — isolated bias controller for automotive BMS / traction aux.
  • Keep TL431 + optocoupler on secondary when feeding AFE / insulation monitor.

ST slot

High-voltage integrated switch, good for 5–15 W BMS aux.

  • VIPer26K — 1050 V offline HV converter, check PCB creepage.
  • VIPER17HD — smaller power, still HV, use TL431 for tighter secondary.
  • BOM remark: “Check isolation / creepage / pollution degree for region.”

NXP slot

Best when the rest of the BMS already uses NXP MCU / AFE.

  • TEA1755T — flyback/PFC combo, use flyback part to build aux.
  • TEA1761 — green-mode flyback controller, re-test EMI bands.
  • If NXP device is not available → cross to TI/onsemi with equivalent isolation, then re-test.

Renesas slot

Good documentation, but EMI must be re-validated.

  • ISL6753 — current-mode PWM for isolated supplies.
  • RAA223012 — 700 V AC/DC flyback, use on DC bus only after isolation check.
  • BOM remark: “Run EMI on measurement-domain lines after Renesas substitution.”

onsemi slot

Frequently used in small-batch repairs / short lead-time builds.

  • NCP1207A — HV current-mode, confirm DC-bus operation.
  • NCP1562B — higher-power, active-clamp capable when BMS aux needs margin.
  • BOM remark: “Re-test EMI, ride-through, isolation for every cross-brand replacement.”

Microchip slot (secondary)

Use mainly to create clean 5 V / 3.3 V from the isolated main output.

  • MIC5283 — 120 V input LDO, ideal for HV-to-low local bias.
  • MCP16331 — for small secondary rails (note VIN limit, use after isolation stage).
  • Use Microchip for secondary clean rails; primary converter must still be automotive-grade.

Melexis slot (measurement)

Keep when your BMS accuracy depends on Melexis sensing.

  • MLX91220 — isolated Hall current sensor for BMS.
  • MLX91221 — higher bandwidth variant, used in diagnostics.
  • BOM remark: “Keep Melexis parts; otherwise re-calibrate leakage / insulation measurement.”

After any vendor change among the seven above, re-test: EMI on measurement-domain lines (with / without Y-cap), ride-through/hold-up (see Chapter 5 formula C = I · t / ΔV), isolation/hi-pot (see Chapter 3), secondary-output accuracy (see Chapter 4), startup/UVLO chatter during HV bus dips (see Chapter 6).

Validation & test hooks (what to re-test after substitution)

Trigger: controller change · transformer change · regulation change · Y-cap change · cross-brand / small batch

This validation matrix is the answer to “why can’t we just buy a cheaper aux DC/DC?”. Every time you replace TI with onsemi, or swap an ST VIPer for a Renesas flyback, or modify the transformer construction, the BMS measurement domain can see a different EMI / leakage pattern and the hold-up may no longer match the BOM. Run the five items below and archive the waveforms.

1) HV bus dip test

Purpose: verify aux stays alive when the HV bus droops during charging / contactor events.

  • Test profiles: 250 → 200 V, 400 → 300 V (or project-specific HV levels).
  • Check if 5 V / 3.3 V drop below AFE / MCU minimums.
  • Check if the HV controller restarts (UVLO chatter).

2) Ride-through / hold-up test

Purpose: verify the secondary-side capacitor can write the log before the bus disappears.

  • Design formula: C = Iload × thold ÷ ΔV.
  • Disconnect the input, measure actual hold-up time.
  • If the new controller has higher startup / bias current → increase C and re-test.

3) EMI on measurement lines

Purpose: ensure the insulation / leakage monitoring page sees the correct leakage, not the Y-cap leakage.

  • Measure with Y-cap installed and with Y-cap removed.
  • Log CM noise that appears on AFE reference ground.
  • Share results with the insulation-measurement page to avoid conflicting Y-cap values.
Validation matrix for BMS HV auxiliary bias A 5-row checklist: Bus dip, Hold-up, EMI (measurement lines), Isolation/hi-pot, Thermal at rated load. Validation matrix — run after ANY cross-brand substitution Bus dip test 250→200 V / 400→300 V — aux rails must stay above AFE/MCU min. Hold-up / ride-through C = I × t / ΔV — logging must finish before rail collapses. EMI on measurement-domain lines with / without Y-cap — report to insulation monitoring page Isolation / hi-pot transformer supplier / construction changed → re-run hi-pot + system test Thermal at rated load BMS high-voltage zone → poor airflow → re-check controller/xfmr temperatures Keep this matrix attached to the BOM for small-batch / urgent orders. If any item fails → do not accept the substitute.
Figure 10 — Validation matrix for BMS HV auxiliary bias: bus dip, hold-up, EMI, isolation, thermal — all must be re-run.

4) Isolation / hi-pot

  • Run at transformer level and at system level.
  • Applies whenever the bobbin, insulation tape, layer stack or supplier changes.
  • Applies when AC/DC-style controllers are used on DC bus.

5) Thermal at rated load

  • Use actual BMS enclosure / HV zone conditions.
  • Log controller, primary switch, transformer temperatures.
  • If the new controller has higher losses, increase clearance from measurement-domain parts.

Trigger list: controller PN change (e.g. UCC28C43-Q1 → NCP1207A), transformer construction change, regulation change (secondary → PSR), Y-cap value change, or small-batch / urgent order using a cross-brand substitute. In all cases, run the 5-item matrix above.

Request a Quote

Accepted Formats

pdf, csv, xls, xlsx, zip

Attachment

Drag & drop files here or use the button below.

FAQ for HV auxiliary bias in the charging domain

These 12 questions only cover this page’s scope: isolated HV aux supply, secondary regulation, ride-through for logging, cross-brand and sharing the rail with the insulation / leakage monitor. They do not cover OBC PFC/LLC, pack-FET drive or vehicle-level insulation algorithms.

Why can’t I reuse the OBC auxiliary power for the BMS when charging?
Because the OBC’s own auxiliary rail can disappear exactly when the charge connector is unplugged or when the contactor is operated, while the BMS still has to write the last log frame. The BMS needs an independent, isolated HV auxiliary supply that rides through that gap and keeps AFE/MCU alive.
BOM remark: “BMS charging-domain auxiliary supply shall be independent from OBC aux.”
Can I replace a secondary-regulated isolated flyback with a cheaper primary-side regulated one?
Not as a drop-in. Primary-side regulated (PSR) parts change output accuracy with transformer tolerance, layout and temperature. In a BMS measurement domain this will show up as AFE or insulation-reading drift. If you really have to use PSR, you must re-validate AFE accuracy and insulation readings and document it in the test report.
BOM remark: “Aux supply must remain secondary-regulated; do not replace with PSR SMPS.”
How long should the ride-through be to finish BMS logging after a charge interruption?
Size the capacitor for the actual logging time using the design rule C = Iload × tlog ÷ ΔV. For most charging interruptions the target is in the range of tens to a few hundreds of milliseconds. If you change the controller, UVLO or startup current, you must re-measure the real hold-up time.
What isolation level should I specify in the BOM for HV BMS auxiliary supplies?
At minimum, specify basic isolation sized for the maximum HV bus and pollution degree; for automotive BMS it is safer to request reinforced isolation or to point to the project’s isolation envelope. Also write the required creepage / clearance in the BOM so the transformer vendor cannot shrink it.
BOM remark: “Isolation ≥ basic (preferred reinforced), creepage/clearance per project HV envelope.”
My aux supply restarts when the contactor pulls in — what parameter should I check first?
Check the HV controller startup current and its UVLO thresholds first. The contactor inrush can make the HV bus dip, and if the controller’s startup current is too high or the UVLO window is too narrow, the controller will drop out and restart. Also verify there is a small primary bulk to ride through the dip.
Can I power the insulation/leakage monitor from the same aux bias output?
Yes, but only if the common-mode noise and Y-cap leakage of the aux supply stay within the monitor’s limits. After changing the controller, transformer or Y-cap value, run EMI and leakage measurements again and share them with the insulation-monitor page.
BOM remark: “If insulation monitor shares this aux, re-validate leakage and CM noise.”
What transformer parameters cannot be changed when sourcing from a different vendor?
Do not change the insulation construction (triple-insulated wire / tape system / bobbin type), do not reduce creepage/clearance, and do not change the turns ratio or split-winding scheme that the regulation loop depends on. Any change here requires re-testing hi-pot, EMI and regulation accuracy.
Do I need a separate 3.3 V rail for the measurement ADC?
In most BMS measurement-domain designs the answer is yes. Close the loop on 5 V on the secondary side, then generate a clean 3.3 V with an LDO just for ADC/AFE/logging. This prevents cross-load events (like an insulation measurement) from pulling down the MCU rail.
BOM remark: “Provide dedicated 3.3 V (LDO from 5 V) for measurement ADC / AFE.”
Why did EMI get worse after I changed the controller IC?
Different controllers switch at different frequencies, rise times and drive levels. The original snubbers, RCD and Y-cap were tuned for the old IC. When you substitute the controller you must re-run EMI on the measurement-domain lines, especially if the insulation monitor shares this rail.
Which vendors offer automotive-grade isolated flyback controllers for BMS?
TI (UCC28C4x-Q1 / UCC287xx), ST (VIPer HV/auto), NXP (TEA17xx/TEA1755T), Renesas (ISL/RAA HV controllers) and onsemi (NCP12xx / NCP156x) all have parts that can sit in an HV BMS auxiliary supply. Microchip is typically used on the secondary clean rails, and Melexis parts are kept to preserve measurement integrity.
Can I remove the Y-cap to improve insulation measurement accuracy?
You can, but EMI will normally degrade. Correct practice is to measure with the Y-cap and without the Y-cap, document both sets of numbers, and decide together with the insulation-monitor owner which version to keep. Any Y-cap value change must be re-tested.
BOM remark: “Y-cap changes → re-test EMI & insulation readings.”
How do I write a BOM remark to stop purchasing from choosing non-isolated parts?
Use an explicit sentence, for example:
HV BMS auxiliary supply shall be isolated and secondary-regulated. Do not substitute with PSR, non-isolated or consumer-grade AC/DC modules. Any substitution must pass EMI, ride-through and isolation re-tests.
This makes it clear to purchasing that cheaper non-isolated parts are out of scope for this page.