CAN vs PLC in DC Charging: Why Adapter Direction Matters (2026)
Teilen
A GB/T DC source and a CCS vehicle need supported CAN-to-PLC protocol conversion, not just matching connector geometry. CAN and PLC are communication technologies, not interchangeable charging message standards. Active conversion addresses the protocol gap; it does not independently guarantee vehicle compatibility, station authorization, charging speed, or a successful session.
Last updated: 2026-09-18 · ChargePapa editorial source review. We compared published technical guidance with current product records; we did not conduct a charging-session experiment for this revision. The cover is an existing GB/T-source-to-CCS2-vehicle product illustration, not a measured test result or proof of vehicle approval.
What is the difference between CAN, PLC, and charging protocols?
CAN refers to Controller Area Network, a communication bus used by conventional GB/T DC charging systems. GB/T 27930 defines the charging communication rather than ISO 11898 alone. CharIN’s comparison identifies GB/T charging with CAN and separates it from CCS communication. Do not extend this DC explanation to GB/T AC charging. CharIN charging-standard comparison, page 21 (2025).
PLC refers to Power Line Communication. In CCS, HomePlug Green PHY operates on the control-pilot signaling path, not the high-current DC power contacts as this article previously stated. A communication technology and the charging messages carried over it are different layers. CharIN CCS communication FAQ (checked 2026); ISO 15118-3 physical/data-link scope (2015; checked 2026).
CCS charging communication includes DIN SPEC 70121 and the ISO 15118 family; it is not accurate to equate every CCS session with ISO 15118 alone. ISO 15118-1 covers general requirements and use cases, while different parts address other layers. The earlier “IEC 15118-1:2019” attribution was incorrect. CharIN CCS Basic implementation references (checked 2026); ISO 15118-1 scope (2019; checked 2026).
Why is a passive connector bridge insufficient for GB/T-to-CCS DC charging?
A passive adapter can bridge a specified physical connection without translating incompatible charging messages. For the GB/T CAN-to-CCS PLC path discussed here, supported active conversion is necessary. CharIN explains that a physical adapter alone cannot make CAN charging communication work with an ISO 15118-enabled CCS station. CharIN CAN-versus-PLC explanation (checked 2026).
Active conversion is an embedded control function that handles the supported charging conversations on both sides. Do not assume every converter has a dual-core processor, USB-C update port, identical firmware, or universal compatibility. The product must support the actual charging direction and operating combination, not merely carry an “active” label.
The source-to-vehicle naming convention matters: GB/T source → CCS2 vehicle and CCS2 source → GB/T vehicle are opposite adapter paths. Communication flows in both directions during a session; a CAN→PLC shorthand does not reverse the physical charging-source and vehicle roles. This article previously attached the two Smart-Link products to the wrong scenarios.
| Charging source | Vehicle inlet | Communication role | Decision boundary |
|---|---|---|---|
| GB/T DC source | CCS2 DC vehicle | CAN ↔ PLC translation | Smart-Link CPCADA0007; verify the exact supported combination |
| CCS2 DC source | GB/T DC vehicle | PLC ↔ CAN translation | Smart-Link CPCADA0006; opposite direction, not the same adapter |
| Compatible NACS DC source | CCS1 vehicle with supported CCS communication | Shared PLC may permit a passive connector bridge | Vehicle, station and approved adapter still required; no universal access claim |
| CCS2 DC source | Actually verified NACS-inlet vehicle | Verify vehicle CCS communication capability | No blanket passive-compatibility recommendation from connector shape alone |
| J1772 AC source | Actually verified NACS-inlet vehicle | Separate AC signaling and power role | An AC-only adapter is not a DC protocol converter |
Does shared communication technology guarantee NACS DC compatibility?
No. A supported CCS-compatible NACS DC path can use a passive connector bridge, but a Tesla-shaped connector alone does not prove that the vehicle and station support the required communication or adapter. Verify the specific vehicle, station, and approved accessory instead of describing every NACS connection as automatically interchangeable with CCS.
Tesla’s current guidance requires supported vehicles, compatible sites, and manufacturer-provided adapters, and prohibits third-party adapters for Supercharging. This article therefore does not recommend ChargePapa DC-Link as an approved substitute. Protocol compatibility and network permission are separate checks; an AC adapter is not a Supercharger adapter. Tesla adapter and access requirements (checked 2026).
Is OCPP the same as vehicle-to-charger protocol conversion?
No. OCPP connects charging stations to charging-management systems; it is a different communication path from the vehicle-to-station handshake. An OCPP-capable station or app does not by itself translate GB/T CAN messages into CCS communication. Match the vehicle-side charging protocol before treating backend connectivity as evidence of interoperability. Open Charge Alliance OCPP definition (checked 2026).
What can this article honestly say about tests, latency, and firmware?
The previous 0/30 marketplace versus 30/30 Smart-Link comparison did not identify a verifiable test report, equipment configuration, vehicle, firmware, or logs. We have removed it rather than present an unsupported bench experiment as fact. This revision is a source review, not a claim of measured charging performance or superiority over another seller.
We also withdraw the fixed 3–5-second failure time, under-two-second added initiation time, processor-idle-during-charging explanation, and article-specific 72-hour rated-load and 85°C shutoff claims. Without applicable evidence for the exact product and configuration, those numbers cannot establish session success, thermal protection, or performance. No replacement test results are invented.
Firmware changes must follow the exact product’s documented update process and supported versions. A USB-C label does not establish Plug & Charge support or an upgrade to higher current capacity. This page does not promise a particular initiation time, faster charging after an update, or compatibility with every future network release.
Which checks should come before ordering an adapter?
This breaks down into four checks: the charging-source connector and AC/DC role; the actual vehicle inlet; the supported communication and electrical operating range; and manufacturer or network authorization. Confirm the exact combination in product documentation and vehicle instructions. Stop using damaged equipment rather than assuming a converter or locking mechanism can repair it. If the vehicle inlet is CHAdeMO and you still need to distinguish CCS1, CCS2, or NACS on the source side, use the ChargePapa Buyer’s Guide to select the correct source → CHAdeMO path.
A rating is a ceiling, not a charging-speed promise. The old product cards mixed outdated power, weather, material and certification claims across different models. This revision removes those cards instead of transferring specifications between products. In simple terms, verify the direction first, then confirm the exact model’s documented limits and permission to use it.
Which ChargePapa path matches a GB/T DC source and CCS2 vehicle?
If your verified charging source is GB/T DC and your vehicle inlet is CCS2 DC, the relevant documented path is ChargePapa Smart-Link GB/T DC → CCS2 vehicle (CPCADA0007). Its explicit source-to-vehicle direction and active converter role make the buying path clearer than an ambiguous two-connector label. Confirm the exact vehicle and station combination before ordering.
This path is DC-only, not AC charging and not reverse-direction charging. If your source is CCS2 DC and your vehicle uses GB/T DC, the opposite information page is Smart-Link CCS2 DC → GB/T vehicle (CPCADA0006). Neither product name independently establishes manufacturer approval or network authorization.
ChargePapa has confirmed 300A maximum current for both CPCADA0007 and CPCADA0006, matching their titles. Their primary specifications list a 300kW power ceiling, not a guaranteed charging speed. Verify the exact vehicle, station, firmware, electrical operating range and authorization. The existing two-year global warranty and remote-diagnosis-first support remain subject to published terms, not universal compatibility guarantees.
What are the common DC adapter protocol questions?
Does CCS PLC communication travel over the high-current DC power pins?
No. CCS uses HomePlug Green PHY communication on the control-pilot signaling path, not the two high-current DC power contacts. PLC describes the communication technology; DIN SPEC 70121 and the ISO 15118 family describe charging communication requirements. Treat the physical signaling layer and the charging message protocol as related but distinct.
Can a passive GB/T-to-CCS2 adapter translate the DC charging handshake?
A passive connector bridge does not translate GB/T CAN charging messages into CCS PLC communication. A supported GB/T DC source to CCS2 vehicle path requires active protocol conversion. That requirement is not proof that every active adapter supports your particular vehicle, station, firmware version, electrical operating range, or network authorization.
Which Smart-Link direction fits a GB/T vehicle at a CCS2 DC station?
The source-to-vehicle direction is CCS2 DC source to GB/T DC vehicle, represented by Smart-Link CPCADA0006. CPCADA0007 is the opposite GB/T DC source to CCS2 vehicle path. Confirm the actual source connector and vehicle inlet rather than choosing by country or an ambiguous connector-name sequence. Neither path is for AC charging.
Does matching PLC communication guarantee NACS Supercharger access?
No. Shared communication technology does not establish vehicle eligibility, adapter approval, station support, or payment authorization. Tesla’s current guidance prohibits third-party Supercharging adapters and directs drivers to manufacturer-provided adapters and compatible sites. This article does not recommend ChargePapa DC-Link as an approved substitute or treat every Tesla-shaped connection as a supported session.
Can firmware updates guarantee faster charging or a fixed handshake time?
No. Firmware can change supported communication behavior, but a connector or update-port label alone does not prove a specific update capability, added latency, or charging speed. Use the exact product’s documented update process and supported combinations. This article does not claim measured initiation times, hardware upgrades, or universal session-success results.
What are the limits of this source review?
We reviewed public standards scopes and industry guidance, not complete paid standards or a vehicle-by-vehicle test matrix. These sources explain communication layers and access restrictions; they do not certify or endorse ChargePapa products. CharIN cautions against generalized adapter use. Confirm current vehicle and station instructions and an explicitly supported adapter before planning a charging session. CharIN adapter position, pages 22–23 (2025).