ISO 15118 PLC Modem Design for Vehicle-Side Charging
← Back to: High-Voltage Energy & Safety
This page helps me plan and select a vehicle-side ISO 15118 PLC modem as a complete system: where it sits in the architecture, how I design the coupling, EMC and safety hooks, which ICs I should buy and what to write in my RFQ so suppliers can respond with the right solution.
What does an ISO 15118 PLC modem do on the vehicle side?
From a driver’s point of view, ISO 15118 and the PLC modem turn a simple “plug in and wait” experience into smart charging. You plug in the cable, the basic CP/PP interface confirms a safe connection and current limit, then the PLC modem starts the high-level conversation for authentication, tariffs and contract-based charging.
On the hardware side, the vehicle-side PLC modem takes ISO 15118 messages from the EVCC or OBC controller and encodes them as a high-frequency signal on the power line. Through a dedicated coupling network, these signals ride on top of the AC or DC charging conductors while staying isolated from the high-voltage power stage.
IEC 61851 and the CP/PP front-end handle the basic safety states and current limit, while the ISO 15118 PLC link enables digital services such as Plug & Charge, contract handling and fine-grained power scheduling. The OBC power stage simply follows the charging setpoints negotiated through this communication channel.
This page focuses on the vehicle-side PLC modem hardware path: helping you decide whether you need ISO 15118, how to choose a modem and coupling network, how to keep the link robust under OBC noise and EMC tests, and which fields to add to your BOM or RFQ so suppliers can recommend a suitable solution.
System placement: where the PLC modem lives in the OBC / charge-port architecture
In the vehicle, the ISO 15118 PLC modem sits between the charge inlet and the OBC or EVCC controller. On the high-voltage side, a coupling network connects the modem to the AC line or DC bus that runs through the inlet and high-voltage energy backbone. On the low-voltage side, the modem connects to the EVCC or OBC controller and into the vehicle network through Ethernet or a local serial interface.
The CP/PP front-end beside the inlet continues to manage the basic IEC 61851 state machine and current limit, while the PLC modem board focuses on the ISO 15118 communication path. Charge-inlet locking mechanics and temperature monitoring are handled on dedicated functional blocks and are not expanded on this page.
For layout and safety planning it is important to understand which connections cross the isolation boundary, which grounds are shared between the PLC modem, OBC power stage and vehicle Ethernet, and where the secure element or HSM is placed relative to the EVCC controller.
PLC signal chain & coupling network essentials
On the vehicle side, the PLC signal chain is more than a single modem chip. It runs from the ISO 15118 stack in the EVCC or OBC controller, through a baseband/PHY, a line interface AFE and a coupling network, and finally onto the charging conductors. Each block adds its own constraints on bandwidth, impedance, protection and diagnostics.
The baseband / PHY & MAC stage sits in a PLC SoC or modem IC and implements HomePlug Green PHY or similar standards. A line driver or interface AFE converts those baseband signals into a differential, cable-ready waveform. The coupling network adds transformers, capacitors, resistors, common-mode chokes and relays so the PLC energy can ride on the AC or DC line while staying isolated and EMC-compliant. Around this path, sensing and diagnostics circuits monitor voltage, current and temperature to support self-test and field reliability.
In practice you can choose between a highly integrated PLC SoC, which combines PHY, MAC and often the line driver, or a more flexible discrete AFE plus external MCU or SoC. You can strictly follow a vendor reference design for the coupling network, or adjust it to match your actual cable length, grid filtering and OEM EMC requirements. The more you diverge from the reference conditions, the more important it becomes to treat the coupling network as an engineered component instead of a copy-and-paste note in the schematic.
Frequency band, coupling topology and cable impedance all interact. Incorrect transformer bandwidth, coupling capacitor size or choke selection can weaken the PLC signal or push emissions outside the allowed spectrum. A common mistake is to ignore the noise generated by the OBC PFC and LLC stages, assuming the reference network will “just work”. Another is to size components for a notional cable instead of the actual harness and filters used in the vehicle. This section highlights those trade-offs before you lock the PLC modem, AFE and coupling network into your BOM.
Ethernet, MCU and security interfaces (EVCC implementation hooks)
The PLC modem does not operate in isolation. On the vehicle side it must connect to an EVCC or OBC controller that runs the ISO 15118 stack, to a secure element or HSM that stores keys and certificates, and to the vehicle network backbone. Selecting the right interface options and placing these devices correctly on the board is as important as choosing the modem IC itself.
On the controller side, many designs use a 10/100 Ethernet link between the PLC modem and the EVCC MCU or gateway, reusing existing Ethernet infrastructure. Others use SPI or UART connections for smaller, cost-optimised controllers, with the ISO 15118 stack running locally on the MCU. These choices drive whether you need an external Ethernet PHY, a small switch device or only low-cost serial buses on the PLC modem board.
A secure element or HSM typically connects to the EVCC controller over I²C or SPI and provides protected storage for certificates and cryptographic keys, as well as hardware acceleration for signing and verification. While the PLC modem transports ISO 15118 frames, the security device anchors trust in the vehicle. On the network side, planners must decide how the EVCC and PLC modem attach to the vehicle backbone through Ethernet or CAN FD gateways, and how latency and clocking budgets will scale toward ISO 15118-20 and V2G/V2H use cases.
This section concentrates on physical and logical interfaces around the PLC modem board. It does not cover cloud billing platforms, back-end contract management or high-level cybersecurity policy. The goal is to clarify which ICs belong on the vehicle-side PLC modem and EVCC hardware and how they connect, so that the system team can integrate ISO 15118 communication into the wider vehicle network architecture.
Key design trade-offs: noise immunity, EMC and robustness
A vehicle-side ISO 15118 PLC link operates in the middle of a noisy environment. The OBC PFC and LLC or phase-shift full-bridge stages inject high dV/dt and dI/dt switching noise close to the coupling network. Nearby loads such as compressors, pumps and other high-power inverters disturb the AC or DC rails and return paths, while grid harmonics and line disturbances arrive from the charging infrastructure itself.
Designers only have a few real levers: the way the coupling network filters out unwanted frequencies without killing the PLC passband, the transformer and capacitor values that define the low and high frequency roll-off, the common-mode chokes and filters that suppress emissions and susceptibility, and the layout, which keeps sensitive traces away from high dV/dt and dI/dt regions. Small choices in these areas can decide whether a design passes EMC and still maintains a usable PLC signal margin.
EMC requirements from CISPR and OEM-specific standards constrain how much energy the PLC signal can radiate or conduct outside its intended band. At the same time, the modem still needs enough signal at the far end of the charging cable to achieve a robust link under worst-case noise. This leads directly to trade-offs between EMC-friendly filters, signal strength and component cost. Grounding strategy on the PLC board, including how analog, digital and power grounds are partitioned and joined, further influences both emissions and immunity.
A pragmatic approach is to leave tuning margin in the coupling network, plan for realistic cable and grid conditions instead of relying on a generic reference design, and align the PLC layout with the OBC power layout from the beginning. The more aggressively you optimise for cost or efficiency, the more carefully you must verify PLC robustness and EMC compliance in hardware-in-the-loop setups and early vehicle builds.
Protection, diagnostics and functional safety hooks around the modem
The vehicle-side PLC modem board must survive grid disturbances, cable faults and long-term thermal stress while remaining diagnosable. Surge and overvoltage events are handled by coordinated layers of TVS, MOVs and, where applicable, gas discharge tubes on the line side, backed by resistive or RC networks that limit fault currents into the AFE and modem pins. These choices define how gracefully the hardware behaves when the charging system is stressed or miswired.
Thermal protection extends this envelope over the lifetime of the vehicle. Coupling transformers, capacitors, chokes and the line driver itself can run hot during extended high-power charging, especially in confined OBC enclosures. Adding NTCs or temperature sensor ICs near critical components allows the EVCC or OBC controller to monitor local temperatures, reduce drive levels or flag maintenance conditions before intermittent communication failures appear in the field.
Diagnostics turn the PLC modem from a black box into an observable subsystem. Modem self-test features such as loopback modes, bit-error counters and link-quality metrics help distinguish transient noise from hardware faults. Additional checks for coupling network integrity—for example, detecting a stuck relay, an open transformer winding or an unintended short—allow the controller to raise a specific fault instead of a vague “PLC not working” message.
From a functional safety point of view, the PLC modem is usually part of a higher-level concept rather than an ASIL-rated component by itself. What matters is that communication failures and degraded link quality are detected within a defined time and reported to the EVCC and vehicle safety functions. System designers can then fall back to IEC 61851-only charging, limit operating modes or disable V2G/V2H features while keeping the vehicle safe. This section focuses on exposing the right protection and diagnostic hooks around the modem; other pages cover high-voltage contactors, BDU logic and insulation monitoring in the wider safety context.
IC selection map: PLC SoCs, AFEs, line drivers and security companions
A vehicle-side ISO 15118 PLC modem board is built from several IC classes rather than a single chip. At the core is a PLC modem or SoC that implements the required HomePlug Green PHY or G3-PLC standard and ISO 15118 versions. Around it sit AFEs and line drivers that connect the PHY to the coupling network, and companion devices such as security elements and Ethernet PHYs or switches that tie the solution into the vehicle network and cybersecurity concept.
When choosing a PLC modem or SoC, key dimensions include which ISO 15118 revisions it supports (for example, ISO 15118-2 today and ISO 15118-20 tomorrow), the underlying PLC PHY scheme, integration level (PHY, MAC and line driver in one package or only part of the chain), operating temperature and power consumption. Automotive qualification and the availability of OEM-proven reference designs are just as important as the protocol feature list, because they determine how much validation effort is required for each vehicle program.
The AFE and line driver are selected based on output drive strength, allowed common-mode and differential ranges, supply voltage options, built-in protection functions and diagnostics visibility. On the companion side, a security element or HSM is sized by certificate storage capacity, supported hardware algorithms and interface type, while Ethernet PHYs or switches are chosen for their automotive qualification, EMC behaviour and ability to integrate into the vehicle backbone and timing budgets.
For automotive ISO 15118, it is risky to adapt generic PLC chips and home-grown coupling schemes. Instead, most programs benefit from selecting ICs that are explicitly positioned for vehicle-side ISO 15118 use, backed by long-term supply, safety documentation and reference designs validated against OEM EMC and network requirements. The map below summarises how the main IC categories relate to each other.
BOM & procurement checklist for vehicle-side PLC modem boards
To turn the PLC modem concept into a concrete RFQ, you can translate the design decisions on this page into explicit BOM fields and procurement questions. Start by stating which standards the solution must support, including the ISO 15118 revisions, the PLC physical layer scheme and any plans to move from ISO 15118-2 to ISO 15118-20 during the vehicle lifetime. Clarify whether the ICs must be fully automotive-qualified and reference-tested against specific OEM EMC and network requirements.
Next, define the environmental and implementation constraints. This includes operating voltage and temperature ranges, expected EMC class, and whether the design should use a highly integrated PLC SoC or a discrete modem plus AFE and line driver. The coupling network concept should be specified at a high level, for example AC-only coupling, combined AC and DC coupling or a solution optimised for specific grid regions and cable lengths. These points allow suppliers to match their reference designs to your harness and charging profiles.
Interface and security expectations must also be included. State whether the EVCC side will connect over Ethernet, SPI or UART, whether you require a recommended security element or HSM and how it interfaces, and how the PLC modem and EVCC will attach to the vehicle backbone. Add any constraints on power consumption and thermal handling, as well as footprint or board-area limits inside the OBC or charge-port control unit, so that proposals can reflect realistic packaging options.
If I include these points in my RFQ, suppliers can quickly judge whether they have an automotive-grade ISO 15118 PLC modem solution and reference design that fits my program. It also helps them highlight gaps in standards support, environmental ratings or security features early, before I commit the PLC modem architecture into my platform roadmap.
Request a Quote
H2-9. FAQs × 12 (ISO 15118 PLC modem planning & selection)
These twelve questions help me turn ISO 15118 PLC modem theory into concrete planning and selection decisions. Each answer captures how I would approach architecture, signal chain, EMC, security and procurement for my own project, so I can reuse the same guidance when I talk to suppliers, system architects and test engineers.
1. When do I actually need an ISO 15118 PLC modem instead of basic IEC 61851 CP control only?
I use an ISO 15118 PLC modem when I need more than basic AC charging with CP PWM. As soon as my project requires plug and charge, contract-based billing, richer diagnostics or DC charging handshakes, IEC 61851 alone is not enough. Then I treat the PLC modem as the backbone of my charging communication.
2. How do I choose between an integrated PLC SoC and a discrete modem + external MCU architecture?
I choose between an integrated PLC SoC and a discrete modem plus external MCU by looking at reuse, flexibility and validation effort. A SoC is attractive when I want a compact, proven reference design. A discrete modem and MCU architecture suits me when I need more control over firmware, interfaces and long-term roadmap.
3. What information about AC/DC line and cable do I need before designing the PLC coupling network?
Before I design the PLC coupling network, I make sure I know the AC or DC voltage level, cable type and length, any filters between the inlet and OBC, and the regional grid norms I must support. Those details drive transformer choice, capacitor values, common-mode chokes and the amount of margin I can leave.
4. How do OBC switching noise and PFC topology influence the PLC modem and AFE selection?
OBC switching noise and PFC topology shape the noise spectrum that my PLC modem and AFE must survive. If the PFC or LLC runs at frequencies that interact with my PLC band, I know I need more careful filters, better layout and sometimes different devices. Otherwise I risk marginal links and EMC surprises later.
5. What EMC tests typically stress the PLC signal path the most on the vehicle side?
From a vehicle perspective, conducted emissions around the PLC band, bulk immunity tests and some transient events stress my PLC signal path the most. When I plan the design, I assume those tests will hit my coupling network and line driver hard, so I keep tuning room and test early with realistic harness and grid conditions.
6. How should I partition isolation between the PLC modem board, OBC power stage and vehicle Ethernet network?
I partition isolation by following the natural boundaries in my system. The PLC coupling network and modem stay on the high-voltage side with the OBC, while my EVCC or gateway and vehicle Ethernet usually sit on the low-voltage side. I use galvanic isolation so failures on one side cannot propagate uncontrolled to the other.
7. When is a dedicated secure element mandatory for ISO 15118 features like plug & charge?
I treat a dedicated secure element as mandatory when my project must support plug and charge, contract-based charging or strict certificate handling rules. A separate security device gives me protected key storage, hardware cryptography and lifecycle control. It also helps me pass audits and separate responsibilities between the PLC transport and trust anchor.
8. How can I diagnose whether communication issues come from the PLC modem, coupling network or grid side?
When communication becomes unreliable, I first check counters and diagnostics in the PLC modem for link quality. If those look fine, I suspect the coupling network or relays and may run impedance or continuity tests. If the vehicle side looks healthy, I look at the grid and charger, comparing behaviour across different stations and lines.
9. What are typical power, temperature and automotive grade requirements for PLC modem ICs?
For PLC modem ICs I typically plan for full automotive temperature from minus forty to at least one hundred and five degrees Celsius, with AEC-Q qualification where possible. Power consumption has to stay manageable in a warm OBC housing. I also expect long-term supply, documentation and test reports that fit an automotive program.
10. How do I plan for future migration from ISO 15118-2 to -20 without redesigning the full hardware?
To prepare for migration from ISO 15118-2 to -20, I choose devices and interfaces that can support updated stacks without rewiring the whole vehicle. I keep processing headroom in my EVCC, avoid tying hardware too tightly to one software release and talk to suppliers about their roadmap so I can align my platform plans.
11. Can I reuse a single PLC modem design across different vehicle platforms and regional grid standards?
I can reuse a single PLC modem design across platforms if I plan for variations in grid voltage, cable length, EMC limits and charging modes. That usually means one common core design with parameter options in the coupling network and firmware. I check early whether my chosen ICs are accepted by different OEMs and regions.
12. What key fields should I add to my RFQ/BOM so suppliers can recommend a suitable ISO 15118 PLC modem solution?
In my RFQ and BOM I spell out the ISO 15118 versions I need, the PLC PHY scheme, AC and DC use cases, voltage and temperature ranges, EMC expectations and preferred architecture. I add interface options, security requirements and any size or power limits. That way suppliers can respond with realistic, vehicle-ready proposals.
