ChargePapa Knowledge Hub · Field Notes · May 2026
Why Your DC Fast Charging Session Doesn't Deliver Rated Speed — The Handshake That Has to Happen First
If your session at a 150kW or 350kW DC fast charger topped out well below rated speed, the hardware isn't necessarily the problem. The charger and your vehicle have to agree on current and voltage before a single electron moves.
● PROTOCOL ● DC FAST CHARGING ● FIELD NOTES
If your session at a 150kW or 350kW DC fast charger topped out well below the rated speed, the hardware isn't necessarily the problem. The charger and your vehicle have to agree on current and voltage before a single electron moves. That agreement takes three to five seconds. If it fails — or if your adapter can't participate — the charger defaults to a conservative floor, or refuses to start.
This is the handshake problem. Here's what it is, and why passive adapters can't solve it.
What the Charger Does Before Current Flows
Every DC fast charging session opens with a digital negotiation over the Control Pilot (CP) line. For NACS and CCS1, this runs on PLC — Power Line Communication — using the ISO 15118 or DIN 70121 protocol.
Charger sends
- Station ID
- Maximum deliverable current
- Maximum voltage
- Vehicle's target state of charge
Vehicle responds
- Maximum accepted current
- Battery voltage
- Current SoC
- Thermal ceiling (pack temperature)
Only when both sides have confirmed a compatible window does the charger release current. If the vehicle doesn't respond — or responds in the wrong protocol — the charger either times out or defaults to the minimum power floor.
Why the Protocol Matters as Much as the Connector
NACS and CCS1 both use PLC over the CP line. An active adapter — like the DC-Link NACS→CCS1 or DC-Link CCS1→CCS2 — routes the PLC signal correctly so the handshake completes at full rated parameters.
⚠ GB/T is different
GB/T — used by BYD, NIO, Zeekr, and Xpeng — runs on CAN bus, not PLC. A mechanical adapter can't translate CAN bus to PLC. The session fails or throttles to minimum. The DC-Link NACS→GB/T solves this with active PLC-to-CAN translation at 300A / 1000V DC, IP54.
| Adapter Type |
Protocol Handling |
Throttle Risk |
| Passive (mechanical only) |
None |
High — falls to floor current |
| Active (onboard MCU) |
Real-time translation |
None — full negotiation completes |
If Your Session Is Throttling: What to Check
1. Is the adapter active or passive?
The product listing should say “active protocol converter” or “active electronics.” If it only mentions connector compatibility, it's passive.
2. GB/T ↔ NACS or GB/T ↔ CCS
Passive adapters will always fail or throttle here. Active translation is the only hardware-side solution. See the DC-Link NACS→GB/T and DC-Link GB/T→NACS.
3. Thermal throttle mid-session
If the session starts at full speed and drops after 10–15 minutes, this is typically the vehicle's BMS pulling back based on pack temperature — not an adapter failure.
FAQ
Are all ChargePapa DC-Link adapters active?
Yes. Every DC-Link adapter contains active protocol conversion electronics. The NACS→CCS1 is rated 500A / 1000V / IP65. The NACS→GB/T handles PLC-to-CAN translation at 300A / 1000V.
ChargePapa Store
Shop the Solution
Active DC-Link adapters with onboard protocol conversion — the hardware that completes the handshake.
