A cable can charge a demonstration phone and still lack the evidence needed for lot acceptance. For a legacy USB Standard-A plug to USB Type-C plug cable, one specific construction requirement deserves its own check: the Rp resistor in the Type-C plug. A “fast-charge” label, a continuity beep or a charging animation does not establish its value.
This guide separates that resistor requirement from functional attachment and broader cable approval. It is a proposed purchasing workflow, not a report of tested samples. Start with the exact cable assembly; reversing the intended connection or substituting a C-to-C cable changes the applicable requirements.
Identify the assembly before applying a resistance limit
The relevant arrangement has the Standard-A plug connected to a legacy source and the Type-C plug connected to the receiving device. The USB-IF Type-C Cable and Connector Specification, Release 2.5, section 3.5 and the wiring notes in sections 3.5.1 and 3.5.2, specify this boundary. These sections cover the defined USB 3.1 and USB 2.0 Standard-A cable assemblies respectively.
Their Type-C plug pin A5, CC, connects to VBUS through Rp of 56 kΩ ±5%. The resistor-only tolerance corresponds arithmetically to 53.2–58.8 kΩ. Those endpoints are not fabricated measurements, and they are not automatically the pass band for an uncertain fixture reading. The laboratory must account for its method before declaring conformity.
Do not transfer this rule to a Type-C-to-Standard-A receptacle host adapter, a C-to-C cable, or every product with a Type-C shell. For the wider connector and use-case background, see the USB-A to USB-C cable guide. The acceptance record should name both connector types and whether each end is a plug or receptacle.
| Item under review | What the evidence must establish | What it does not establish |
|---|---|---|
| Assembly identity | Standard-A source-side plug and Type-C device-side plug; declared USB variant | That another adapter class shares this Rp rule |
| Scoped Rp termination | Correct CC-to-VBUS connection and resistor requirement | Full wiring, thermal or signal-integrity compliance |
| Controlled attachment | Expected attach behavior in both Type-C orientations | The resistor value without valid electrical evidence |
| Charging performance claim | Separately defined source, device, protocol and conditions | Universal speed from a cable label |
Why a larger current advertisement is not an upgrade
Section 3.5 explains the reason for the legacy restriction: the cable does not comprehend the capability of the source into which it is plugged. It may therefore advertise only Default USB Type-C Current through this termination. Other Rp values are not permitted for the scoped assembly because they may cause a Type-C sink to overload a legacy supply.
“Default” here is not permission to assume one universal operating current for every USB-A source. Applicable USB operation and charging detection still matter. Equally, the resistor finding alone does not prove or disprove every separately specified charging protocol. Reject the wrong scoped termination, not a vaguely defined category of “fast charging.”
Texas Instruments’ TUSB320 controller documentation lists attach detection, orientation detection, role detection and Type-C current mode as distinct CC functions. That is a useful reason to record separate functional observations. It is an older controller example, not evidence that the purchased cable contains this IC or that any finished cable is certified.
Keep electrical inspection separate from powered attachment
First, a qualified technician should inspect the cable through an approved, mapped breakout fixture while the cable is isolated from all power sources and receiving devices. Follow the laboratory method for reaching the intended CC and VBUS nodes. Do not open a molded plug or improvise loose probes on live contacts to obtain a convenient number.
A resistance reading is only meaningful if the fixture exposes the intended path without unknown loading. Identify any fixture pull resistors, connected electronics, leakage paths and contact effects. Retain the instrument range, calibration status, fixture revision and method checks. A surprising result with an unverified adapter is a method problem until investigated, not immediate proof of a bad production lot.
Second, conduct a protected functional attach test with the agreed source and receiving equipment. Record both Type-C plug orientations, observed attachment and the reported current mode where the equipment can establish it. The CC pin explanation provides background, but the acceptance report must identify the actual observation method. Do not deliberately overload a source to demonstrate a suspected advertisement error.

A six-step acceptance record for the supplier
- Freeze scope. Record the cable drawing, assembly class, lot, sample IDs, length and revision. Identify the purchase requirement and the specification edition used.
- Validate the fixture. Record its pin map, loading assessment, reference checks and approved method. Confirm isolation before resistance inspection; preserve any evidence that invalidates the setup.
- Retain the electrical result. Save readings, units, uncertainty information and the agreed conformity rule. Apply the specified tolerance without silently inventing a tighter universal requirement.
- Record functional attachment. Identify the source, receiving equipment and protection settings. Keep the observations for each Type-C orientation, including failures rather than only a successful reconnect.
- Separate other requirements. Track wiring, voltage drop, temperature rise, mechanical durability and applicable data performance in their own agreed tests. This Rp review cannot release those items.
- Close the disposition. Name the reviewer, affected samples, lot-containment decision and required corrective evidence. A replacement sample must remain linked to the original finding and revision.
Turn findings into precise purchasing decisions
Do not combine “resistance passed,” “phone charged” and “cable approved” into one checkbox. Each answers a different question and calls for different evidence when it fails.
| Finding | Purchasing disposition | Evidence needed to close it |
|---|---|---|
| Scoped Rp conforms under a valid method | Close this requirement only; continue remaining tests | Electrical record and approved decision rule |
| Fixture loading or pin mapping is unknown | Hold the Rp determination | Corrected method and traceable remeasurement |
| Incorrect scoped Rp is confirmed | Reject this requirement item; investigate lot exposure | Containment, root cause and verified corrective samples |
| Rp conforms but one orientation fails attachment | Hold functional acceptance | Orientation-specific diagnosis and repeatable corrective evidence |
For the engineering record, preserve three linked identifiers: requirement, sample and observation. Add the raw-file location, fixture and instrument IDs, timestamp, reviewer and disposition. Record untested items explicitly as untested. This proposed record structure avoids treating missing evidence as a measured defect while preventing a partial pass from becoming a blanket approval.
Keep certification and supplier claims within scope
USB-IF’s Cables and Connectors program explains that the certification program uses multiple applicable documents depending on cable capabilities. A satisfactory Rp result is not a substitute for that program, a certification listing or the other requirements in the purchase agreement. Nor does a certified cable add capabilities to an incompatible source or receiving device.
For an OEM cable enquiry, share the intended assembly and acceptance scope with ChargeKeku. Include the source/device combination and required report fields. Ask for evidence tied to the supplied revision, rather than assuming that a charging label or a resistor check settles every performance claim.