Why this matters
In high-power charging problems, splitting the path into source, cable, and receiving device usually finds the real limit faster than assuming a “240W” component is faulty. It also reduces unnecessary charger and cable replacement.
Decision sequence
- Confirm that the source can advertise the required PDO/EPR condition.
- Confirm the cable’s 60W/240W power capability.
- Confirm the receiving device’s maximum input and its current charging-control conditions.
Original utility
USB-C power-path bottleneck calculator
Enter the advertised/required power ceilings for the charger, cable, and device. The mathematical ceiling of the path is the smallest of the three. This is a ceiling calculation, not proof that a specific voltage/current contract will negotiate.
Limit: actual USB PD behavior also depends on supported voltage/current objects, EPR/SPR support, cable identification, firmware, temperature, and device policy.
What Heliacal Dawn adds
This page connects 2 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
9 evidence-led sectionsModel the symptom as a bottleneck, not a defective-product verdict
For “Why a 240W-capable USB-C setup may stay near 100W”, 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 “Troubleshoot a nominally 240W-capable USB PD setup that is delivering much less power by locating the limiting source, cable, or sink.” 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.
Finally check the device and dynamic charging conditions — Separate the specification maximum from the behavior observed at a particular moment. If source, cable, and device capabilities line up on paper, the next step is to investigate product-specific charging control rather than replacing parts at random.
Separate source, path, and endpoint state
Implementation is where nominally compatible technologies become a concrete system. Map source capability → negotiated USB PD contract → cable voltage/current and identification capability → receiving-device request and write down the capability at each arrow. If a layer is undocumented, keep it unknown. If a layer advertises a range, use the specific mode needed by the user job rather than the maximum mode printed elsewhere in the same specification. For this page, apply that boundary specifically to “Troubleshoot a nominally 240W-capable USB PD setup that is delivering much less power by locating the limiting source, cable, or sink.” and do not generalize it to an unrelated capability axis.
Compare the negotiated ceiling with the observed symptom
USB Power Delivery and USB Type-C solve different layers of the path: Type-C defines the connector and cable ecosystem, while USB PD negotiates power contracts. A USB-C-shaped connector therefore cannot be treated as proof of a particular PD level, data rate, display mode, or cable current capability. The calculation is useful as a ceiling check, not as a promise of observed performance. A technically valid maximum is reachable only when every prerequisite implied by source capability → negotiated USB PD contract → cable voltage/current and identification capability → receiving-device request is present at the same time. If one layer negotiates or implements a lower class, the end-to-end result collapses to that lower common capability. For this page, apply that boundary specifically to “Troubleshoot a nominally 240W-capable USB PD setup that is delivering much less power by locating the limiting source, cable, or sink.” and do not generalize it to an unrelated capability axis.
Worked diagnostic trace
Consider a buyer following this page's sequence: first “Confirm that the source can advertise the required PDO/EPR condition.”, then “Confirm the cable’s 60W/240W power capability.”, then “Confirm the receiving device’s maximum input and its current charging-control conditions.”. 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 “Troubleshoot a nominally 240W-capable USB PD setup that is delivering much less power by locating the limiting source, cable, or sink.” and do not generalize it to an unrelated capability axis.
A misleading success state
A useful counterexample is a configuration in which the most impressive label is real but irrelevant. The source can legitimately advertise the higher class while the receiving endpoint supports only the lower class, or the endpoint can support the higher class while the path between them does not. In both cases every individual marketing statement can be true while the combined system still operates below the headline maximum. For this page, apply that boundary specifically to “Troubleshoot a nominally 240W-capable USB PD setup that is delivering much less power by locating the limiting source, cable, or sink.” and do not generalize it to an unrelated capability axis.
Conditions that can mimic the same symptom
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 “Troubleshoot a nominally 240W-capable USB PD setup that is delivering much less power by locating the limiting source, cable, or sink.” and do not generalize it to an unrelated capability axis.
Lowest-cost diagnostic order
Use an evidence ladder. Start with the exact receiving requirement, then verify confirm that the source can advertise the required pdo/epr condition.. Next verify confirm the cable’s 60w/240w power capability., using the model or certification record that matches the exact product rather than a family name. Only then verify confirm the receiving device’s maximum input and its current charging-control conditions.. This order makes the first failing layer visible instead of burying it under a successful fallback. For this page, apply that boundary specifically to “Troubleshoot a nominally 240W-capable USB PD setup that is delivering much less power by locating the limiting source, cable, or sink.” and do not generalize it to an unrelated capability axis.
Diagnostic evidence boundary
The source set for this page contains 2 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 “Troubleshoot a nominally 240W-capable USB PD setup that is delivering much less power by locating the limiting source, cable, or sink.” and do not generalize it to an unrelated capability axis.
When the evidence is strong enough to replace or reconfigure hardware
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 “Troubleshoot a nominally 240W-capable USB PD setup that is delivering much less power by locating the limiting source, cable, or sink.” and do not generalize it to an unrelated capability axis.
Primary sources reviewed
- USB-IF — USB Charger (USB Power Delivery)
USB-IF USB Power Delivery material used to confirm EPR power ranges and negotiated operation. - USB-IF — Cables and Connectors
USB-IF cable guidance used to confirm current 60W/240W cable power capability labeling.
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.