USB PD Decoder
Paste the PDOs from a charger capture, a C array from your PD stack, or the raw Source_Capabilities bytes. You get every field decoded, the Request checked against the object it points to, and a check of the source against the spec's Power Rules.
1 · Capabilities
Hex words, a C array, a 16-bit header followed by words, or analyzer bytes (little-endian, e.g. A1 61 2C 91 01 08 …).
2 · Request (RDO)
3 · Power Rules
4 · Encoder
Build one object from fields, then copy the hex or append it to the list above.
Message
Power data objects
Click a row to see its bit fields. Flags live in position 1, the 5 V object.
| # | Hex | Type | Voltage | Current | Power | Check |
|---|
| Bits | Field | Raw | Value |
|---|
Request
| Bits | Field | Raw | Value |
|---|
Power Rules check
Required Fixed rails and currents for the PDP (USB PD Rev 3.2 Tables 3.1 and 3.5), plus optional-voltage, PPS, AVS, ordering and cable rules.
| Rail | Required | Advertised | Status |
|---|
Cable
Capability map
Fixed objects as points, PPS and Variable ranges as bars, AVS as its current limit, and the PDP curve I = PDP / V.
Reading USB PD power objects, and checking a charger against the Power Rules
A USB PD source advertises what it can do in a Source_Capabilities message: a 16-bit header followed by up to seven 32-bit Power Data Objects. The sink answers with a Request carrying one Request Data Object (RDO), which names an object by its position and says how much it will draw. In EPR mode the list grows to eleven positions: SPR objects in 1–7 (zero-filled if unused) and EPR objects from 8. The bit layouts below follow USB PD Revision 3.2 Version 1.2; Revision 3.3 Version 1.0 keeps the same tables.
Example: Fixed 5 V 3 A is (100 << 10) | 300 = 0x0001912C. Analyzers print messages as bytes in wire order, which is little-endian, so 2C 91 01 08 is the word 0x0801912C: 5 V 3 A with Unconstrained Power set. This page reads bytes, words, a header followed by words, or a C array, and strips a trailing CRC-32 if the byte count shows one.
Power Rules
A source's Port Maximum PDP fixes which Fixed voltages it must offer and how much current each must carry. Optional voltages, extra PPS ranges and Variable or Battery objects are fenced in by the same chapter. Currents may be rounded up or down to the 10 mA grid, so the check passes anything at or above RoundDown(PDP / V).
Many chargers on the market predate these rules, so a real capture often fails a line. A 12 V Fixed PDO or a 20 V PDO on a 30 W charger are common examples. The check tells you which rule a list breaks so you can decide whether it matters for your sink.
Limits
- Messages only: no BMC physical layer, 4b5b symbols, SOP ordered sets or CRC checking. A trailing CRC-32 is detected by length and ignored, not verified.
- The Power Rules check treats the PDP you enter as the Port Maximum PDP of a guaranteed-capability port. Managed ports that lower Port Present PDP (Table 3.2), Source_Capabilities_Extended and the SPR AVS deferral rules of Rev 3.3 are not modelled.
- Chunked extended messages decode only the chunk you paste. Vendor Defined Messages, Alerts and BIST objects are named in the header but not decoded.
- This is an engineering decoder, not a compliance test. Certification uses the USB-IF Compliance Test Specification.
References
- USB Implementers Forum, Universal Serial Bus Power Delivery Specification, Revision 3.2 Version 1.2 (Aug 2026): Tables 6.2–6.22 (objects), 3.1–3.5 (Power Rules); Revision 3.3 Version 1.0 (Oct 2026) Table 3.4; R3.2 V1.2 ECN "Rounding Conflicts". Free from usb.org/document-library/usb-power-delivery.
- Texas Instruments, SLYP853, USB Type-C PD3.1 extended power range (EPR Power Rules summary).
- okhsunrog/usbpdpy (MIT), README: raw Source_Capabilities and Request captures from a POWER-Z KM003C, used here as an example and test vector.
- STMicroelectronics, wiki Introduction to USB Power Delivery with STM32: SRC_CAPABILITIES trace (H:0x51A1), used as an example and test vector.
- R. Baron, USB Power Delivery for Makers (2024): PPS RDO 0x60044C14, used as a test vector.
- Linux kernel,
include/linux/usb/pd.h(GPL-2.0), read to cross-check field positions. No code was copied.
Building a USB-C power input or output?
Kyros designs USB-C PD power paths end to end: controller selection, the protection around VBUS, and the sink or source firmware that has to negotiate cleanly with every charger in the drawer.
