Design tool

Power Analyzer — DC IR drop

The voltage each chip really sees, where the drop is lost, and what to change.

Who does what

The top lane is you; the bottom lane is WireFrame.

You
01

State the rail

RailLoadsBudget

The supply nets, the return, and each load's current from its datasheet. The sources are proposed from the netlist.

04

Try a load

What-if

Drag a load's current and the map follows at once: every load's response is solved already.

06

Approve & apply

ApproveApply

A person approves it; it is applied as one undo step.

WireFrame
02

Solve the copper

PoursViasTracks

Supply and return, on the copper as filled, with the rails that share a ground solved together.

03

Show where it is lost

MapContributorsFindings

Each load's voltage, and its drop split exactly over the tracks, necks and vias that cause it.

05

Suggest fixes

WidenAdd viasCopper

Widen a track, add vias, heavier copper — each one previewed by solving the changed board.

07

Write it down

HTMLMarkdownJSON

The rail, where every number came from, each load's voltage, the fixes and who approved them.

The Power Analyzer on h730duino: IR drop on +3V3, each load's voltage, and where J4's drop is lost

A 3.3 V regulator does not deliver 3.3 V to a processor across the board. The Power Analyzer solves the rail's real copper — pours as filled, tracks, vias, pads — on the supply and the return, for the load currents you state. It reports each load's voltage, splits its drop exactly over the copper that causes it, checks current density and every via and track against IPC-2221, follows the power tree and the rails sharing a ground, and proposes fixes it previews by solving again.

What it does

Where the drop is lost

Each load's drop split exactly over tracks, necks, vias and planes — the list that tells you which fix pays.

Real copper, both sides

Supply and return solved together; rails sharing a ground superposed; converters as loads of the rail they draw from.

Validated

Within 0.2 % of exact answers on textbook geometries, identical to ngspice on a plane with a hole and a ferrite.

What-if, instantly

Drag a load's current and the map follows at once.

Fixes you approve

Widen a track, add vias, heavier copper — each previewed by an actual solve, approved by a person, applied as one undo step.

Every value says where it came from

You state the rail — its supply nets, even several joined through a ferrite, its return and a drop budget (3 % by default) — its sources, the series parts that carry it from net to net, and the loads with the datasheet current for the mode you design for. Sources are proposed from the netlist. A value nobody stated is marked and caps the verdicts at WARNING: the analysis never reads an assumption as a fact, and it never guesses a chip's consumption.

The copper as it is

Each net and layer is rasterised on one grid and split into its connected pieces, so copper that shares a cell without touching is not joined. Tracks are resistor chains, vias are barrels between layers, and the return is solved with the same currents. A converter is a load of the rail it draws from and the source of the rail it feeds, rails that share a ground are superposed, and tracks can heat with their own current. About 20 iterations solve 1.5 million nodes.

Where a load's millivolts go

Pick a load and its drop is split exactly over the copper that causes it. On h730duino, the J4 header sees 3.2963 V: 3.74 mV of drop, and 47 % of it is lost in one 0.41 mm, 19 mm track on F.Cu. The relief spokes round the inductor come next, then a few vias. That ranked list is where a fix pays, and the suggested fixes — widen a track, add vias, heavier copper — are each previewed by solving the changed board before a person approves them.

The details

ReportsEach load's voltage, drop and path resistance; current density; via and track current against IPC-2221; copper connected to nothing
RailSupply nets, return, other grounds, drop budget (default 3 %)
LoadsLumped or per pin, with a minimum voltage; converters as P_out / (efficiency × V_in)
AccuracyWithin 0.2 % of exact answers on textbook geometries; identical node voltages to ngspice on a plane with a hole and a ferrite
ExportsHTML with the maps, Markdown or JSON
ScopeDC; the AC side is the High-Speed Workbench's Power page

How to start

  1. Open a board and choose View › Power Analyzer (DC IR drop).
  2. Use the proposed rails, state each load's current from its datasheet, and Run.
  3. Read Map & loads and Findings; preview and approve a fix.

Questions

Does it know how much current my chip draws?

No — load currents are yours to state, from the datasheet for the mode you design for. An unstated current is marked and keeps the verdict at WARNING.

Is it a thermal simulation?

No. Each track can heat with its own current, but thermal coupling between parts and the board's temperature map are not modelled.

What about decoupling and ripple?

That is AC behaviour: the High-Speed Workbench's Power page checks each rail's impedance across frequency, and the two windows link to each other on the same rail.