Why this matters
A quick power calculation is useful for checking labels, but it becomes misleading when the result is treated as evidence that a particular charger, cable, and device combination will negotiate it.
Decision sequence
- Select the voltage class being evaluated
- Enter the current supported by the path
- Compare the arithmetic result with source, cable, and sink capabilities
Original utility
USB PD voltage/current arithmetic checker
Choose a common USB PD voltage level and enter a current to calculate the arithmetic power. The result is deliberately labeled as arithmetic only: it does not assert that a source advertises the object, that a cable permits the current, or that a sink accepts the contract.
Limit: the arithmetic result is not a USB PD negotiation verdict. Source PDOs, EPR/SPR state, cable identification, sink support, firmware, and policy still matter.
What Heliacal Dawn adds
This page connects 3 primary/originator sources to a bounded engineering decision. The analysis separates mechanism, worked examples, failure boundaries, and verification steps; it does not imply hands-on testing unless that evidence is explicitly declared.
Engineering depth
6 evidence-led sectionsDefine the decision variable before comparing products
For “USB PD EPR voltage/current power envelope calculator”, the useful model is not a single feature flag. Treat the system as source capability → negotiated USB PD contract → cable voltage/current and identification capability → receiving-device request. The question “Translate a USB PD voltage/current pair into an arithmetic power ceiling without treating it as proof of negotiation” is answered only after the relevant capability survives every layer. This prevents a common category error: promoting a connector shape, certification mark, protocol generation, or maximum number into an end-to-end guarantee.
Cable capability is part of the contract path — Treat the calculated power as one row in an end-to-end capability intersection rather than a standalone verdict.
Scenario A: requirement is fully supported
Consider a buyer following this page's sequence: first “Select the voltage class being evaluated”, then “Enter the current supported by the path”, then “Compare the arithmetic result with source, cable, and sink capabilities”. Suppose the first check passes and the product headline looks ideal, but the second check exposes a lower capability in the transport path. The correct conclusion is not “almost compatible”; the second layer is the current bottleneck, so the headline ceiling is unavailable until that layer changes. For this page, apply that boundary specifically to “Translate a USB PD voltage/current pair into an arithmetic power ceiling without treating it as proof of negotiation” and do not generalize it to an unrelated capability axis.
Use the result as a consistency check — The calculator is most useful when a marketing claim, charger label, or device requirement needs an arithmetic cross-check.
Uncertainty that should remain explicit
The primary-source evidence on this page narrows the technical possibility space, but product-specific implementation can still change the outcome. Firmware policy, thermal limits, optional feature support, region-specific spectrum or SKU differences, cable length and signal integrity, and vendor power-management choices are examples of factors that can sit outside a standards body's high-level capability statement. For this page, apply that boundary specifically to “Translate a USB PD voltage/current pair into an arithmetic power ceiling without treating it as proof of negotiation” and do not generalize it to an unrelated capability axis.
Decision evidence checklist
Use an evidence ladder. Start with the exact receiving requirement, then verify select the voltage class being evaluated. Next verify enter the current supported by the path, using the model or certification record that matches the exact product rather than a family name. Only then verify compare the arithmetic result with source, cable, and sink capabilities. This order makes the first failing layer visible instead of burying it under a successful fallback. For this page, apply that boundary specifically to “Translate a USB PD voltage/current pair into an arithmetic power ceiling without treating it as proof of negotiation” and do not generalize it to an unrelated capability axis.
Evidence boundary before the yes/no decision
The source set for this page contains 3 primary/originator references. Together they support the specification and certification statements summarized here; they do not represent a bench test of every commercial implementation. Heliacal Dawn's contribution is the mapping from those sources into a decision sequence and explicit uncertainty boundary, not a claim of first-hand measurement. For this page, apply that boundary specifically to “Translate a USB PD voltage/current pair into an arithmetic power ceiling without treating it as proof of negotiation” and do not generalize it to an unrelated capability axis.
SPR and EPR are different operating ranges — Keeping the range label visible prevents a 28V, 36V, or 48V number from being interpreted as an ordinary 20V contract.
Final rule for a qualified yes/no answer
The defensible decision rule is simple: accept the configuration only when every required layer has affirmative evidence for the required class, and treat the lowest verified layer as the current ceiling. Extra headroom can be recorded separately, but it should not be counted as realized value until an endpoint actually needs and can negotiate it. For this page, apply that boundary specifically to “Translate a USB PD voltage/current pair into an arithmetic power ceiling without treating it as proof of negotiation” and do not generalize it to an unrelated capability axis.
Cable capability is part of the contract path — A high-power source and sink cannot bypass a cable limitation.
Primary sources reviewed
- USB-IF — USB Charger (USB Power Delivery)
USB-IF Power Delivery material provides the SPR/EPR power-range context. - USB-IF — USB Power Delivery Document Library
The USB Power Delivery document library is the versioned specification authority for contract semantics. - USB-IF — USB Type-C Cable and Connector Specification
USB Type-C cable capability is included because cable identification constrains high-current paths.
Related next questions
Change history
2026-08-29 — Materially reworked to improve decision usefulness: canonical titles were separated from distribution hooks, page structures were diversified by user job, original decision visuals were added, and selected pages gained deterministic interactive utilities.