HN Debrief

USB Power Delivery: Plugging into the Benefits

  • Hardware
  • Standards
  • Consumer Electronics
  • Infrastructure

Aptiv’s piece is a broad explainer on USB Power Delivery, the protocol layered onto USB-C that lets devices and chargers negotiate voltage and current instead of being stuck at old USB power levels. The pitch is that this creates one cable and one power ecosystem for everything from phones to in-car charging, with higher-end PD now reaching 240W. That article also claims smarter multi-port charging can shift power based on device state, which led people to point out that PD 3.1 does include battery-status messages, so that part is plausible.

Treat USB-C power support as something you must verify, not assume from the connector shape alone. If your product depends on USB-C for charging or power input, budget time for standards compliance and for ugly real-world behavior from chargers, cables, and trigger boards.

Discussion mood

Mostly positive on USB-C and USB Power Delivery as the direction of travel, but sharply annoyed by bad implementations. The mood was driven by repeated experiences with devices that use a USB-C-shaped port without meeting the basic spec, plus skepticism that many chargers and adapters behave like dependable power supplies outside simple charging use cases.

Key insights

  1. 01

    Basic USB-C charging is often trivial

    For many low-power devices, proper USB-C sink behavior does not require a full PD controller. It can be as simple as the correct CC pull-down resistors for 5V operation, with extra complexity only showing up once the device wants more than basic USB-C current or has to handle underpowered sources cleanly. That changes the interpretation of these broken products. They are usually not victims of a hard standard. They are products where nobody bothered to implement the easy part correctly.

    If your device only needs modest power, there is little excuse for shipping flaky USB-C charging. Audit designs for the simplest standards-compliant path before adding custom charger logic or support scripts.

      Attribution:
    • myself248 #1
    • exmadscientist #1
    • megous #1
    • seba_dos1 #1
  2. 02

    USB-C failures often trace to fake compliance

    A lot of the maddening behavior comes from products and cables that are 'USB-C shaped' rather than actually compliant. Missing CC resistors on the device side can make a perfectly good USB-C charger refuse to energize Vbus, while bad A-to-C cables add another layer of unpredictable behavior. The practical lesson was blunt. When charging behavior is flaky instead of consistently broken, suspect the cable first. When a device only works with A-to-C, suspect the device design.

    Keep a known-good compliant cable in your test kit and use it as a baseline. If customers will mix chargers and cables, test against bad but common accessories because that is where support pain will show up.

      Attribution:
    • SchemaLoad #1
    • duskwuff #1
    • mschuster91 #1
    • seba_dos1 #1
    • exmadscientist #1
  3. 03

    Chargers are not the same as PSUs

    Using USB-C to power mini PCs and other always-on gear looks attractive, but a charging brick is optimized for negotiated charging sessions, not for acting like a boring constant power supply under every hot-plug and load-change scenario. People reported power drops when other devices were unplugged from shared chargers, and pointed out that the main size savings comes from moving AC to DC conversion outside the box, not from magically feeding motherboard rails over USB-C. USB-C works best here as a regulated DC input into onboard converters, not as a replacement for internal power architecture.

    For products that need stable continuous power, validate behavior under renegotiation, shared-port events, and thermal limits. If reliability matters, spec an overprovisioned charger or a dedicated external PSU rather than assuming any high-watt USB-C brick is good enough.

      Attribution:
    • exmadscientist #1
    • ranger207 #1
    • dotancohen #1
    • SchemaLoad #1
  4. 04

    PD can expose battery status

    The article’s claim about allocating more power to the lower-battery phone sounded suspicious, but PD 3.1 does define battery-status exchange through Get_Battery_Status. That does not guarantee every phone and car stack uses it well, but it means the concept is grounded in the protocol rather than pure marketing fiction.

    If you are building multi-device charging systems, look at newer PD features instead of assuming power sharing must be blind. The protocol may already expose enough state to support better allocation policies.

      Attribution:
    • itnerd #1
    • seba_dos1 #1
  5. 05

    240W depends on special cables

    The jump to 240W is real, but it is not available over any random USB-C cable. Reaching 5A at higher PD voltages requires an e-marked cable, while ordinary cables are limited to lower current and can become a safety problem if pushed past spec. The headline wattage is therefore an ecosystem claim, not just a charger claim.

    When advertising or relying on high-power USB-C, qualify the cable requirements explicitly. Support teams will otherwise get blamed for failures caused by commodity cables that can never deliver the promised power.

      Attribution:
    • Animats #1
    • seba_dos1 #1

Against the grain

  1. 01

    One-cable purity is overrated

    Standardizing on USB-C is convenient, but the obsession can turn into aesthetic neatness more than real utility. Carrying a second cable for one awkward device is cheap redundancy, and some products genuinely have form-factor or design tradeoffs that make a universal connector less obvious than enthusiasts admit.

    Do not force USB-C into a product roadmap as a symbolic win if it creates other compromises. Measure the actual user cost of an extra cable against the engineering cost and design tradeoffs.

      Attribution:
    • JMiao #1
    • tredre3 #1
  2. 02

    PD itself is not a clean standard

    The complaints were not limited to vendors misimplementing USB-C. Some engineers argued the PD spec has become deeply unpleasant to work with, especially in newer revisions, even if earlier PD versions were more elegant. That weakens the idea that better education alone will fix the ecosystem. Part of the friction is baked into the protocol stack.

    If your team is adding advanced PD features, assume integration complexity will be real even with competent engineers. Scope schedule and interoperability testing accordingly instead of treating PD like a solved commodity interface.

      Attribution:
    • exmadscientist #1
    • seba_dos1 #1

In plain english

CC ↩
Configuration Channel, the signaling pins in USB-C used to detect connections, roles, and basic power capability.
e-marked cable ↩
A USB-C cable with an embedded chip that identifies its capabilities, required for some higher-power modes such as 5-amp charging.
PD ↩
Short for USB Power Delivery, the negotiated charging standard used over USB-C.
PD 3.1 ↩
A newer version of USB Power Delivery that adds features such as higher power levels and battery-status messaging.
USB Power Delivery ↩
A USB-C power protocol that lets a device and charger negotiate higher voltages and currents than basic USB power.
USB-C ↩
A reversible connector standard used for charging, power delivery, and data transfer on modern devices.
Vbus ↩
The main power line in USB that carries the supplied voltage from charger to device.

Reference links

Products and adapters

Standards background

  • Extra-low voltage
    Linked in a side discussion about safety limits and whether 48V USB-C approaches regulatory thresholds.