The USB-C Configuration Channel contacts—CC1 and CC2—let two connected products detect attachment and plug orientation, establish source and sink roles, advertise baseline current and, when supported, exchange USB Power Delivery messages. They do not by themselves carry ordinary USB data or prove that a cable supports video, a particular data rate or a particular power level.
Why a reversible receptacle has CC1 and CC2
A USB-C receptacle must accept the plug in either orientation. It therefore exposes two Configuration Channel contacts. When a normal cable is inserted, the electrical connection makes one of those receptacle contacts the active CC path for that plug orientation. The other contact can have a different role depending on the cable and system design.
The USB Implementers Forum maintains the USB Type-C cable and connector specification route. That source defines the interface; a connector’s appearance is not evidence that a particular product implements every optional feature.
| CC function | What it establishes | What it does not establish alone |
|---|---|---|
| Attach detection | Whether a valid source/sink relationship appears on the cable path. | The application-level data protocol or device compatibility. |
| Orientation detection | Which CC path is active for the inserted plug orientation. | That both orientations have been correctly implemented in a faulty product. |
| Power-role detection | Which partner initially offers power and which consumes it. | The final negotiated USB PD voltage or power. |
| Current advertisement | Baseline Type-C current information before or without a PD contract. | That a device will draw the advertised maximum. |
| PD communication | A signaling path for USB Power Delivery messages when supported. | USB 2, USB 3, USB4 or DisplayPort data lanes. |
From insertion to usable power: the sequence
- Unattached state. The ports monitor their CC termination states without assuming a partner is present.
- Physical insertion. The plug connects one orientation’s CC path through the cable.
- Role recognition. The source-side and sink-side terminations create a valid attach condition and identify the initial power relationship.
- Orientation recognition. The receptacle detects whether CC1 or CC2 is the active path and can configure high-speed routing accordingly.
- Baseline power becomes available. The source exposes power under the applicable Type-C rules; the sink remains responsible for its own allowed draw.
- Optional PD exchange. If both sides support USB Power Delivery, messages on the active CC path can negotiate a different contract.
- Optional data or alternate mode. Separate capabilities and negotiation determine whether high-speed data or video lanes are used.
The USB-IF Type-C Functional Test Specification checks CC behavior across orientation and role cases. That is why “it works one way” is a diagnostic clue, not acceptable reversible-connector behavior.
Where VCONN and an electronically marked cable fit
Some USB-C cable assemblies contain electronics that need a small supply. In the appropriate configuration, the CC contact that is not carrying the active partner-to-partner CC communication can be used for VCONN. That power can support cable identification electronics, often discussed as an e-marker.
This does not mean every cable contains an e-marker, nor that the marker creates power. The source, sink and cable each contribute limits. A cable can report its supported characteristics, but the connected devices still choose a contract they all support.
CC is separate from ordinary data and video lanes
| Capability | Main path | Procurement question |
|---|---|---|
| USB 2 data | Dedicated D+ and D− conductors. | Is USB 2 data wired and verified? |
| High-speed USB data | SuperSpeed differential pairs with orientation-aware routing. | Which named USB data rate and test length are supported? |
| DisplayPort or another alternate mode | Reassigned high-speed lanes after compatible negotiation. | Do both devices and the cable support the exact mode? |
| Power | VBUS and ground, governed by Type-C/PD behavior. | What voltage, current, cable marking and power range were tested? |
| Configuration and PD messages | The active CC path. | Were both plug orientations and source/sink roles tested? |
Use CC behavior to diagnose the right boundary
- If charging or data works in only one plug orientation, inspect both ports and test with known-good equipment; do not assume software is the only cause.
- If basic charging works but high-power PD does not, verify source, sink and cable capability as one system.
- If power works but video does not, investigate alternate-mode support and high-speed lane capability rather than treating CC as the video path.
- If a captive or electronically marked cable is involved, confirm its documented current, power and data limits.
- For compliance or engineering diagnosis, use purpose-built Type-C fixtures; do not touch live contacts with loose probes.
Turn the explanation into a cable requirement
Start with the broader USB-A versus USB-C comparison if the connector families and host/device expectations are still unclear. Then write the requirement in testable terms: connector ends, source and sink models, charging protocol and power, data rate, alternate mode, length, orientation checks and environmental constraints.
Use that worksheet when reviewing the ChargeKeku USB-C to USB-C cable category. A Type-C connector is the mechanical interface; the accepted cable is the one whose documented and tested electrical capabilities match the complete application.