Why Most EV Adapters Fail on DC Fast Chargers — The CAN vs. PLC Problem Explained
Share
ChargePapa · Technical Deep-Dive
Why Most EV Adapters Fail on DC Fast Chargers — The CAN vs. PLC Problem Explained
Most EV adapters sold online fail at DC fast chargers not because the pins don’t fit, but because pins were never the problem. DC fast charging runs on a two-way software handshake — and if your adapter can’t translate that conversation, the session simply won’t start.
What Is the CAN vs. PLC Problem?
CAN Bus and PLC are the two dominant protocols that EVs and DC fast chargers use to negotiate a charging session. They are not compatible with each other.
CAN Bus — ISO 11898
Transmits signals over a dedicated wire pair. Used by GB/T (Chinese standard) DC fast chargers.
Standard: ISO 11898 · Used by: GB/T chargers
PLC — ISO 15118
Rides the same power conductors that carry the charge current. Used by CCS1, CCS2, and NACS.
Standard: ISO 15118 · Used by: CCS1, CCS2, NACS
This is why “DC Fast Charging adapter” is not a single product category. It is two fundamentally different product categories: passive and active.
What Does “Active Protocol Conversion” Actually Mean?
An active protocol converter is a dedicated embedded system — typically a dual-core processor — installed inside the adapter body. It runs firmware that reads incoming protocol frames from one standard, translates them in real time, and retransmits them in the format the other device expects.
Key Technical Fact
Active conversion adds latency measured in milliseconds, not seconds. The handshake completes. The session opens. Current flows. Total added session-initiation time is typically under two seconds compared to a native connection.
Why Firmware Updatability Matters
Active adapters must also handle session-level parameters: maximum voltage negotiation, current ramp-up curves, and fault reporting. A USB-C firmware port means the translation logic can be patched as charging networks roll out software updates — without hardware replacement.
Which Connector Combinations Require Active Conversion?
Every cross-standard combination involving GB/T requires active conversion. No exceptions. The bottom two rows are the only common pairings where a passive adapter is sufficient.
| Charger | Vehicle | Charger Protocol | Vehicle Protocol | Adapter Required |
|---|---|---|---|---|
| GB/T (CN) | CCS2 (EU/AU) | CAN Bus | PLC (ISO 15118) | ACTIVE |
| CCS2 (EU/AU) | GB/T (CN) | PLC (ISO 15118) | CAN Bus | ACTIVE |
| GB/T (CN) | CCS1 (US/KR) | CAN Bus | PLC (ISO 15118) | ACTIVE |
| NACS (US) | CCS1 (US) | PLC (ISO 15118) | PLC (ISO 15118) | PASSIVE ✓ |
| CCS2 (EU) | NACS (US) | PLC (ISO 15118) | PLC (ISO 15118) | PASSIVE ✓ |
Every combination involving GB/T requires active conversion. No exceptions.
What Passive Adapters Do Under Load — Lab Results
We bench-tested a passive GB/T-to-CCS2 adapter — the kind commonly sold on third-party marketplaces — against a 100kW DC charger set to GB/T output and a CCS2 test harness vehicle.
| Adapter | Test Attempts | Sessions Opened | Charger Fault Log |
|---|---|---|---|
| Passive GB/T→CCS2 (marketplace) | 30 | 0 / 30 | “Communication timeout” |
| Smart-Link GB/T→CCS2 (CPCADA0007) | 30 | 30 / 30 | No fault — session opened first attempt |
How the ChargePapa Active Adapter Series Maps to Real Use Cases
Use Case 1 · Active · CAN→PLC
Chinese-spec EV (GB/T) on European / Australian CCS2 Network
The most common cross-standard scenario as BYD, NIO, and Xpeng vehicles enter EU and AU markets. Requires CAN→PLC translation.
Smart-Link GB/T→CCS2 (CPCADA0007)300kW / 300A / 1000V · IP55 · CE · Auto-shutoff 85°C
Use Case 2 · Active · PLC→CAN
European EV (CCS2) on Chinese GB/T Network
The reverse direction: PLC→CAN. Covers EU vehicles imported to China.
Smart-Link CCS2→GB/T (CPCADA0006)200kW / 200A / 300–1000V DC · IP54 · USB-C firmware port
Use Case 3 · Active · CAN→PLC
Chinese EV (GB/T) on North American CCS1 Network
Covers GB/T-spec vehicles exported to North America. Active CAN→PLC, dual-core processor.
Smart-Link GB/T→CCS1 (CPCADA0011)200kW / 200A · IP54 · USB-C firmware port · Dual-core
Use Case 4 · Passive · PLC↔PLC
North American CCS1 Vehicle on NACS Supercharger Network
Passive — and correctly so. Both NACS and CCS1 use PLC. The engineering challenge here is purely electrical: 500A / 1000V / 350kW.
DC-Link NACS→CCS1 (CPCADA0030)500A / 1000V / 350kW · IP65 · UL94 V-0 shell · 72hr load test
Use Case 5 · Passive · PLC↔PLC
NACS-Port Vehicle on European CCS2 Network
Also passive (both PLC). Dual integrated temperature sensors, UL94 V-0 housing.
Tesla-Link CCS2→NACS (CPCADA0016)250kW / 250A / 300–1000V · UL94 V-0 · Dual temp sensors
Use Case 6 · AC Level 2 · No Protocol Conversion
NACS-Port Vehicle at J1772 Level 2 AC Stations
An AC adapter, not a DC fast charging unit. No protocol conversion required at AC Level 2. Silver-plated copper alloy terminals.
Tesla-Link J1772→NACS (CPCADA0017)80A · Silver-plated terminals · IP54 · UL94 V-0
What to Look for When Buying a DC Fast Charging Adapter
In simple terms: the first question is always which protocols are on each side. If both are PLC, a passive adapter can work. If one side is CAN Bus and the other is PLC, the adapter must be active. There is no workaround.
- Protocol confirmation: Does the listing explicitly state “active protocol conversion” or “CAN↔PLC translation”? If it says “passive” or says nothing, assume no translation.
- IP rating: DC fast chargers are often outdoors. IP54 is the minimum; IP65 provides full dust exclusion and directional water jet protection.
- Thermal protection: Auto-shutoff at a defined temperature (e.g., 85°C) protects the vehicle port. Dual temperature sensors provide redundancy.
- Firmware updatability: A USB-C firmware port means the translation logic can be updated as charging networks evolve — without hardware replacement.
- Certification: CE marking (required for EU market under Low Voltage Directive 2014/35/EU) indicates assessment against applicable safety standards.
- Pre-shipment test standard: A product rated at 300A should be tested at 300A — not at 80% of nameplate — before it ships.
Why ChargePapa Builds Active Converters — And What That Requires
ChargePapa is a direct-from-manufacturer EVSE brand headquartered in Hong Kong, recognised by the Asian EV Development Association (AEVDA) as “Best Innovative Service Provider.” The adapter line is currently deployed across more than 15 countries and regions, serving both individual EV owners and authorised dealership networks.
That deployment range is what surfaces edge cases — protocol variants, regional firmware quirks, thermal profiles in tropical and sub-zero climates — that lab-only development misses.
72h
Continuous load test before every shipment
15+
Countries & regions deployed
2yr
Global warranty with remote diagnosis
85°C
Verified auto-shutoff thermal ceiling
❓ FAQ: EV Adapter Protocol Questions
Does a passive NACS-to-CCS2 adapter work for DC fast charging in Europe?
Yes — and it is the correct choice. Both NACS and CCS2 use PLC (ISO 15118). The difference is physical connector geometry, not communication protocol. The Tesla-Link CCS2→NACS (CPCADA0016) is rated at 250kW / 250A / 300–1000V for this use case.
Why does my GB/T adapter fail at CCS2 chargers even though the pins fit?
The pins fitting is necessary but not sufficient. GB/T chargers broadcast over CAN Bus. CCS2 vehicles listen for PLC signals on ISO 15118. The electrical connection exists but the software handshake never completes — the charger waits for a response that never arrives in the protocol it expects, and the session times out. An active converter is required.
What is ISO 15118 and why does it matter for EV adapters?
ISO 15118 is the IEC standard that defines vehicle-to-grid communication for AC and DC charging. It governs how a vehicle identifies itself to a charger, negotiates maximum power, and enables Plug & Charge authentication. CCS1, CCS2, and NACS all use ISO 15118 PLC for DC fast charging. GB/T uses CAN Bus instead — the source of every cross-standard incompatibility involving Chinese-spec vehicles.
Can a firmware update on an active adapter improve charging speed?
A firmware update cannot increase hardware-rated maximum current or voltage. What it can do is improve compatibility with newer versions of ISO 15118 or updated charger network software — particularly as networks roll out Plug & Charge (ISO 15118-2 PnC) more broadly.
Does active conversion add significant charging time?
No. Active translation latency during session initiation is measured in milliseconds. Once the handshake completes and current begins flowing, the adapter is carrying current — the processor is idle. Total added session-initiation time is typically under two seconds compared to a native connection.
The Protocol Gap Is an Engineering Problem. Treat It as One.
The difference between an adapter that opens a session and one that doesn’t is not a marketing claim. It is a measurable function of the silicon inside — and the 72 hours of bench time before it reached your door.
Browse the Full Adapter Catalog →Sources
IEC 15118-1:2019 — Road vehicles — Vehicle to grid communication interface (International Electrotechnical Commission)
ISO 11898-1:2015 — Road vehicles — Controller area network (CAN) (International Organization for Standardization)
CharIN e.V. — Combined Charging System (CCS) Technical Specification
SAE International — SAE J1772: EV Conductive Charge Coupler standard