CP/PP Front-End Design for IEC 61851 Charging Interfaces
← Back to: High-Voltage Energy & Safety
This page helps you turn the IEC 61851 CP/PP rules into a concrete vehicle-side front-end: how to decode CP states and PWM, measure PP safely, drive contactors with diagnostics and plan PWM, safety and weld detection. By the end, you know which IC blocks to pick and which BOM fields to send in your RFQs so suppliers understand your exact CP/PP front-end requirements.
IEC 61851 Basics: CP and PP Signal Responsibilities
From the vehicle side, IEC 61851 defines how the EV and charging station use the Control Pilot (CP) and Proximity Pilot (PP) pins to exchange basic charging capability and safety information. CP behaves as a status and control channel, while PP encodes cable and connector current capability.
This page focuses on the front-end circuitry on the vehicle side: filters, comparators, AFEs and relay interfaces that turn CP/PP voltage levels and PWM duty cycles into robust logic states. Higher-layer topics such as ISO 15118 power-line communication or mechanical inlet locking are covered on dedicated pages.
The table below summarises how CP and PP differ in roles, signal types and typical front-end building blocks. The rest of this page builds on these roles to derive front-end thresholds, timing and diagnostics.
| Dimension | CP – Control Pilot | PP – Proximity Pilot |
|---|---|---|
| Primary role | Status and control channel between EV and EVSE | Cable and connector current capability / presence encoding |
| Who drives the signal | Charging station generates voltages and PWM waveform | Vehicle/plug presents coded resistance to the station |
| Typical signal type | Voltage levels plus PWM duty cycle that encode states A–F and current limits | Static voltage derived from a resistance ladder and pull-up network |
| Front-end focus | Filtering, comparator thresholds, PWM measurement and fault detection | Robust resistance/voltage measurement with tolerances and protection |
| Typical IC building blocks | Low-voltage comparators or AFEs, timers, protected digital inputs | ADC channels or window comparators with input protection network |
| Integration into EV ECU | Drives contactor control decisions and fault handling logic | Sets allowed current range and influences charging strategy |
CP / PP Voltage Levels and PWM Meaning
IEC 61851 encodes charging states A–F by combining CP voltage levels with the presence and duty cycle of a PWM signal. The EVSE drives CP, and the vehicle side must recover a clean state code from a noisy environment while respecting timing and hysteresis requirements.
PP uses a coded resistance ladder to indicate the maximum current capability of the cable and connector. On the vehicle side, this appears as a relatively static voltage that can be measured with a comparator window or ADC input. Together, CP state decoding and PP resistance measurement define whether the HV contactors are allowed to close and what current limit should be applied.
| CP State | Qualitative CP level / PWM | Vehicle-side action (front-end view) |
|---|---|---|
| A – Not connected | CP idles at a high level with no valid PWM present. | Detect “no vehicle present”; HV contactors must remain open. |
| B – Connected, not ready | CP pulled down to an intermediate voltage, optional PWM present. | Confirm plug connection; keep contactors open until EV is ready. |
| C – Charging allowed | CP at a defined voltage with a valid PWM duty cycle encoding current limit. | Decode duty cycle, enforce current limit and allow HV contactors to close. |
| D – Charging with ventilation | CP levels similar to C but with PWM indicating ventilation requirement. | Allow charging only if ventilation conditions are met; otherwise block. |
| E / F – Fault conditions | CP overvoltage, undervoltage or short-circuit behaviours outside valid windows. | Latch a fault state, open contactors and log diagnostics for service. |
In the detailed design phase, each state is mapped to explicit voltage windows, PWM timing and hysteresis. Front-end comparators or AFEs must stay tolerant to transients while switching cleanly between these windows.
CP / PP Front-End Architecture: AFE and Comparator
On the vehicle side, the CP and PP pins must pass through a robust front-end chain before the EV ECU can safely interpret IEC 61851 states. The front-end typically combines input protection, EMI filtering, comparators or AFEs and a separate PWM measurement path for CP. CP and PP should be treated as two distinct signal chains even if they share common protection devices.
For the CP path, the key design questions are: how much surge and ESD stress to tolerate, what frequency band to pass, where to place comparator thresholds and hysteresis, and how to route a clean PWM waveform into a timer or capture unit. The front-end must reject coupled noise and still switch cleanly between the A–F state windows defined by IEC 61851.
For the PP path, the focus shifts to a resistance-coded voltage measurement. A divider, optional low-pass filter and an ADC or window comparator are usually sufficient, but input protection and tolerance analysis must guarantee that neighbouring current-rating bands cannot be misinterpreted over temperature and ageing.
| Path | Front-end blocks | Design focus |
|---|---|---|
| CP – Control Pilot | Protection network, EMI filter, comparator / AFE, PWM measurement branch | Clean state windows, controlled hysteresis, accurate duty-cycle capture |
| PP – Proximity Pilot | Divider, optional low-pass, ADC input or window comparator, protection | Stable voltage bands, resistance tolerance, mis-detection avoidance |
Contactor and Relay Interface Design with Weld Detection
Once the CP front-end and state logic indicate that charging is allowed, the next step is to drive the HV contactors and relays. The contactor interface must generate reliable coil current, manage inrush and release behaviour and provide clear feedback when a contact has welded or failed to close. These functions should not be hard-coded inside application firmware alone.
Typical architectures use a low-side or high-side driver stage controlled by the ECU, often with integrated current limiting, flyback handling and diagnostics. Weld detection can be based on voltage signatures across the contactor, current signatures through the coil or HV bus sensing once a close command has been issued. A clean separation between command, actuation and feedback greatly simplifies safety analysis.
The diagram and table below summarise how CP state logic, driver stages and weld detection fit together. Later sections on HV bus sensing and diagnostics expand on the measurement options for contactor health and fault reporting.
| Function block | Main tasks | Front-end design focus |
|---|---|---|
| Contactor command logic | Combine CP state, PP rating and system conditions into a close/open decision | Clear interfaces, timeouts and fail-safe paths if logic is inconsistent |
| Driver stage | Drive coil current, handle flyback and inrush, report over-current or open coil | Current rating, thermal limits, integrated diagnostics and pin-to-pin layout |
| Weld detection | Detect failure to open or close using voltage or current signatures | Simple signatures, redundant confirmation and clear diagnostic flags to ECU |
PWM Measurement Strategies: MCU Timer vs AFE
CP duty cycle encodes charging current limits in IEC 61851. Two front-end strategies exist: MCU timer capture and a dedicated AFE/comparator channel. Choosing between them depends on accuracy, noise tolerance, cost and available MCU resources.
A first step is to estimate required duty-cycle resolution, the expected PWM frequency range and the amount of EMI immunity needed. Overloaded MCU cores or harsh dv/dt environments may justify a smarter AFE that preconditions the PWM waveform.
| Strategy | Accuracy | Noise / EMI Tolerance | System Cost | Typical Use |
|---|---|---|---|---|
| MCU Timer Capture | Medium | Low–Medium | Low | Basic AC charging |
| Comparator + MCU Timer | Higher | Medium | Medium | Mid-range EV platforms |
| Dedicated AFE IC | Highest | High | Higher | DC fast charging / OBC |
| Hybrid AFE + MCU | High | High | High | Premium EV platforms |
Automotive Diagnostics & Safety Measures
Even if CP/PP decoding works, IEC 61851 requires additional safety and fault detection. Common front-end checks include open-wire detection, short-circuit detection, debounce against PWM jitter and verifying legal state transitions. Non-robust software-only approaches may violate automotive safety standards.
| Fault Scenario | Detection Method | Front-end Implementation | ECU Action |
|---|---|---|---|
| CP open | Always high level | Comparator window | Disable charging |
| CP short to GND | Near zero level | Comparator window | Fault & shutdown |
| PP open | No valid resistance | ADC threshold | Override rating |
| PWM jitter | Jumping duty cycle | Debounce / timer check | Reject/flag |
| Illegal state jump | B→D without C | State validation logic | Abort charging |
IC Selection Mapping Across Major Automotive Vendors
This section maps the CP/PP front-end and contactor interface functions to representative IC families from the main automotive suppliers: Texas Instruments (TI), STMicroelectronics (ST), NXP, onsemi, Renesas, Microchip (MC) and local / domestic vendors (DC). It is not a complete list, but a practical starting point for datasheet selection and RFQ discussions.
Only devices that directly help with IEC 61851 CP/PP front-ends and contactor interface are listed here. ISO 15118 PLC modems, OBC/DCFC power-stage controllers and high-level domain controllers are mapped on their own pages.
CP Front-End Comparators and AFEs
| Vendor | Example families | Front-end role |
|---|---|---|
| TI | TLV17x, LMV723x, TLV67xx, AMC13xx | Rail-to-rail comparators and isolated AFEs for CP window detection and state decoding. |
| ST | TS3x21, LMV3xx, automotive low-voltage comparators | Low-power comparators for CP level windows and basic diagnostics. |
| NXP | LMV331-type comparators, analog front-ends around GD31xx gate drivers | Comparators integrated into power and interface ASSPs that also see CP levels. |
| onsemi | NCS333, NCV33xx/43xx comparators | Automotive comparators suited for CP level sensing with hysteresis and filtering. |
| Renesas | ISL28xx, analog blocks inside RH/RA MCUs | Integrated comparators and ADC resources for CP level decoding on MCU-based platforms. |
| MC (Microchip) | MCP65x comparators, dsPIC / PIC24 analog peripherals | Comparator and capture peripherals for low-to-mid cost CP decoding designs. |
| DC / Local | Local automotive comparator and AFE families | Region-specific alternatives; align voltage range, AEC-Q grade and availability. |
PP Measurement (ADC / Window Comparator)
| Vendor | Example families | Front-end role |
|---|---|---|
| TI | ADS7xx / ADS1xxx ADCs, TLV67xx window comparators | Measure PP ladder voltages with defined separation between current-rating bands. |
| ST | STM32 ADCs, TS39xx window comparators | Integrated PP measurement on microcontroller-based AC charging controllers. |
| NXP | S32K ADCs and comparators | Single-chip PP measurement on S32K-based EVSE or vehicle controllers. |
| onsemi | NCV ADC / comparator families | Discrete PP measurement for modular CP/PP boards. |
| Renesas | RA, RH ADCs and comparator blocks | MCU-based PP measurement with flexible reference voltage options. |
| MC (Microchip) | dsPIC33 / PIC32 ADC channels, analog comparators | Low-cost PP measurement with enough resolution for coding bands. |
| DC / Local | Local automotive ADC / comparator options | Use the same PP voltage window and tolerance targets as global suppliers. |
Contactor and Relay Drivers with Diagnostics
| Vendor | Example families | Role in CP/PP system |
|---|---|---|
| TI | DRV10x/11x, high/low-side drivers with diagnostics | Drive HV contactor coils based on CP state logic, report open coil or overcurrent. |
| ST | VNx / VIPower high-side drivers | Integrated current limiting and diagnostics for 12 V coil or relay loads. |
| NXP | MC33xxx high-side drivers, system basis chips | Coil drivers with fault flags that tie back into CP/PP safety logic. |
| onsemi | NCV84xx, NCV75xx automotive drivers | High-side and low-side drivers for HV contactors and relays with diagnostics pins. |
| Renesas | High-side switch families, automotive drivers | Coil and relay control in integrated EV power-distribution modules. |
| MC (Microchip) | High-side switch / driver ASSPs | Lower-integration platforms where MCU and drivers remain discrete. |
| DC / Local | Local automotive high-side driver series | Match coil current, fault reporting pins and AEC-Q grade to global alternatives. |
Use these mappings as a starting point: for each project, you should still align exact voltage ranges, diagnostic behaviour and qualification level with your platform-specific requirements and RFQ checklist.
BOM and RFQ Fields for CP/PP Front-End and Contactor Interface
This section turns the CP/PP front-end and contactor design work into a practical BOM and RFQ checklist. You can copy these fields into your RFQ spreadsheet or sourcing templates so suppliers immediately understand that you need an IEC 61851 CP/PP front-end, not just a generic comparator or MCU.
Group the fields into CP front-end, PP measurement and contactor / safety sections. For each field, define either a target value or an acceptable range so that vendors can propose suitable ICs and combinations.
CP Front-End BOM Fields
| BOM field | Description | Example value |
|---|---|---|
| CP input voltage range | Allowed CP input span at the comparator / AFE pin | ±15 V (including transients) |
| Comparator common-mode range | Voltage range where the comparator must operate correctly | 0–5 V (with headroom) |
| Threshold accuracy and hysteresis | Combined error budget for CP window levels and hysteresis band | ±3 % window, 50–100 mV hysteresis |
| PWM frequency range | Frequency range that the front-end and timer must support | 1–2 kHz nominal |
| Duty-cycle resolution | Required duty-step size for current limit decoding | 1 % steps or better |
| ESD / surge robustness | Target ESD and surge levels at CP pin / front-end | IEC 61000-4-x levels, ≥8 kV contact ESD |
| AEC-Q qualification grade | Automotive qualification level for the comparator / AFE | AEC-Q100 Grade 1 |
PP Measurement BOM Fields
| BOM field | Description | Example value |
|---|---|---|
| PP input type | Measurement method for PP ladder | ADC input or window comparator |
| ADC resolution | Minimum resolution for PP voltage bands | ≥10 bit |
| Reference accuracy | Accuracy of ADC reference or window thresholds | ±1 % or better |
| Band separation | Required gap between adjacent PP voltage bands | ≥10 % of full-scale |
| PP protection level | Surge and ESD rating at PP input | Same as CP or project-specific |
| Temperature range | Operating temperature for PP measurement ICs | -40…125 °C |
Contactor and Safety-Related BOM Fields
| BOM field | Description | Example value |
|---|---|---|
| Contactor coil voltage | Nominal supply for the contactor coil | 12 V |
| Contactor coil current range | Expected operating current range for the coil | 0.8–1.2 A |
| Driver type | Preferred contactor driver topology | Low-side / high-side / integrated |
| Diagnostic features | Faults that must be reported to the ECU | Open coil, short, overcurrent, overtemperature |
| Weld detection support | Whether weld detection is integrated or external | Integrated support preferred |
| Interface to ECU | Control and diagnostic signalling type | Logic-level pins / SPI / LIN / CAN |
| Fail-safe behaviour | Required behaviour on CP/PP loss or logic mismatch | Force contactors open and latch fault |
When sending RFQs, include these fields together with your block diagrams or reference designs. It greatly increases the chances that suppliers propose pin-compatible and safety-compliant CP/PP front-end solutions on the first iteration.
Request a Quote
FAQs on CP/PP Front-End, PWM and Contactor Interface
I use these twelve questions as a quick checklist for my CP/PP front-end design. Each answer helps me turn the IEC 61851 rules into concrete choices for PWM measurement, safety checks and IC selection, and I can reuse the same text for search, PAA snippets or my own internal design notes.
1. What does the CP/PP front-end actually do in an IEC 61851 vehicle inlet?
The CP/PP front-end is the translator between the charging cable and your vehicle ECU. It protects the pins, filters noise, converts CP voltage and PWM into digital states, and measures PP to understand cable current rating. Instead of raw analog levels, your ECU receives clean logic that describes presence, readiness and allowed charging current.
2. How do CP voltage levels and PWM duty cycle translate into charging states A–F?
CP uses a combination of DC level and PWM duty cycle to tell you which IEC 61851 state you are in. Your front-end first checks whether the voltage lies in the A, B, C or D window, then uses duty cycle to distinguish available current in C and D. Illegal combinations are treated as faults instead of valid operating states.
3. What information does the PP signal provide and why do you measure it separately from CP?
PP tells you mainly two things: whether a cable or plug is present and what current rating it supports. It is encoded with a resistor ladder, not a PWM waveform, so you normally measure it with an ADC or window comparator. Keeping PP in a separate front-end path avoids loading CP and keeps cable ratings clearly separated from control state information.
4. When is a simple comparator enough for the CP front-end and when do you need a full AFE?
If your platform is relatively quiet, CP voltages stay well within bounds and you only need basic state windows, a rail to rail comparator with a few resistors can be enough. You move to an AFE or smarter front-end when you need stronger EMI immunity, integrated protection, precise thresholds or isolation and when you want to offload your MCU.
5. Should the CP PWM duty cycle be measured directly by your MCU timer or by a dedicated IC?
Measuring CP PWM with an MCU timer is attractive when you have spare timer channels, moderate EMI and a flexible software stack. A dedicated IC or AFE becomes more interesting when timers are busy, jitter margins are tight or you want a hardened duty measurement path that works independently of firmware load and real time operating system constraints.
6. How should you architect the CP and PP front-end signal chains to avoid cross-talk and noise issues?
You get the best robustness when you treat CP and PP as two parallel but separate chains. Give each pin its own protection and filter network, then route CP into comparators and PWM measurement while PP goes into an ADC or window comparator. Avoid sharing high impedance nodes or long stubs that couple noise between CP and PP under fast transients.
7. What type of driver IC is recommended for HV contactor coils in an IEC 61851 system?
For HV contactors you normally want an automotive high side or low side driver that can handle the full coil current, provide flyback handling and report open or short faults. If your safety concept relies on weld detection and diagnostics, choosing a driver with built in current or voltage monitoring saves you external circuitry and simplifies your fault logic.
8. How do you detect CP or PP open-circuit and short-circuit faults at the front-end level?
You usually define valid voltage windows for CP and PP, then treat anything outside those ranges as a fault. An open wire or broken ladder produces an unexpected high or mid level, while a short to ground or battery collapses the voltage. Comparators or ADC thresholds turn those conditions into digital flags so your ECU can block charging and log the event.
9. What kind of debounce and filtering do you need to avoid false IEC 61851 state changes?
Your goal is to ignore very short glitches while still reacting quickly to real state transitions. In practice you define a minimum dwell time for each state, average duty over several PWM periods and add a small debounce time on top of the analog filtering. This combination prevents random spikes from driving A, B, C or D changes in your software.
10. How can contactor weld detection be integrated with your CP/PP front-end and HV bus sensing?
You normally use CP and PP to decide when you are allowed to close contactors, then rely on HV bus sensing and coil feedback to check whether they really opened or closed. By comparing the commanded state with measured bus voltage and current signatures, you can detect welded contacts and report a fault, even if CP and PP still look perfectly normal.
11. Which key parameters should you list in an RFQ for CP/PP front-end ICs?
When you prepare an RFQ, it helps to spell out CP input range, PWM frequency, duty resolution, comparator thresholds, PP measurement method, ESD and surge levels, operating temperature and AEC Q grade. Adding contactor coil voltage, current, driver type and diagnostic features tells suppliers you are targeting a complete IEC 61851 front-end, not just a generic comparator.
12. How do you choose between different vendors for CP/PP front-ends without locking into a single source?
You can treat the BOM fields as a common language and ask several vendors to propose parts that meet the same ranges. Favour families with stable roadmaps, automotive qualification and similar pinouts or behaviours, then validate a primary and secondary source on your hardware. That way you keep flexibility on cost and availability without redoing your basic front-end design.
