PART 2 – Deep Descriptive Theory of EVCC Communication
Chapter 5: The Philosophy of Communication in EV Charging
5.1 Charging as a Negotiation, Not a Command
In traditional electrical engineering, power delivery is often seen as a unilateral process: a source supplies energy to a load. However, EV charging fundamentally changes this paradigm. In CCS2-based systems, charging is a continuous negotiation between two intelligent agents:
- The Electric Vehicle (EV)
- The Electric Vehicle Supply Equipment (EVSE)
The EVCC acts as the vehicle’s spokesperson in this negotiation. It communicates battery capability, thermal constraints, and charging preferences while interpreting offers from the charger.
This concept is similar to a diplomatic conversation where both parties must agree before any action occurs.
Chapter 6: Communication Layer Model in EVCC Systems
6.1 Why Layers Exist in Communication
Communication systems use layered architecture to simplify complexity. Each layer solves a specific problem while relying on lower layers for support.
In EV charging communication, layers ensure:
- Hardware independence
- Security separation
- Protocol scalability
- Vendor interoperability
6.2 EVCC Communication Stack Overview
| Layer | Purpose | Example Technology |
|---|---|---|
| Physical | Transmit electrical signals | PLC over cable |
| Data Link | Error detection and framing | HomePlug GreenPHY |
| Network | Addressing and routing | IPv6 |
| Transport | Reliable message delivery | TCP |
| Application | Charging logic and negotiation | ISO 15118 |
6.3 Analogy for Non-Technical Readers
Imagine sending a parcel:
- Physical layer → Road transport
- Data link → Packaging rules
- Network → Addressing system
- Transport → Courier reliability
- Application → Message inside parcel
Similarly, EVCC uses layered communication to deliver charging instructions reliably.
Chapter 7: Power Line Communication (PLC) Explained Intuitively
7.1 What Is PLC?
Power Line Communication means sending data over power cables. In CCS2 systems, digital messages travel on the same wires that carry electricity.
This eliminates the need for extra communication cables.
7.2 Why PLC Was Chosen for CCS2
- Reduces connector complexity
- Improves reliability
- Supports high-speed data
- Already standardized globally
7.3 How PLC Works in Simple Terms
PLC superimposes a high-frequency signal on top of the DC charging voltage. Think of it like adding radio waves to a power cable.
The charger and EV each have:
- PLC modem
- Coupling capacitor
- Noise filter
7.4 HomePlug GreenPHY Standard
CCS2 systems use HomePlug GreenPHY because it:
- Consumes low power
- Supports secure communication
- Works well in noisy environments
Chapter 8: EVCC Message Flow – The Charging Conversation
8.1 High-Level Message Sequence
A CCS2 charging session follows a structured conversation:
- Discovery
- Handshake
- Capability exchange
- Parameter negotiation
- Charging loop
- Termination
8.2 Discovery Phase
The EV detects a charger using Control Pilot signals. Once connected, PLC communication initializes.
Purpose:
- Confirm physical connection
- Wake up communication modules
8.3 Handshake Phase
In this phase:
- Protocols are identified
- Encryption capabilities are exchanged
- Session ID is created
This is similar to introducing yourself before a conversation.
8.4 Capability Exchange Phase
The EVCC sends:
- Maximum voltage
- Maximum current
- Battery type
- Thermal limits
The charger responds with its own limits.
8.5 Parameter Negotiation Phase
Both sides agree on:
- Target voltage
- Charging current
- Ramp rate
This ensures optimal charging without battery stress.
8.6 Charging Loop Phase
During charging, EVCC repeatedly:
- Reports battery status
- Requests updated current
- Checks safety thresholds
This loop runs every few milliseconds.
8.7 Termination Phase
Charging stops when:
- Battery reaches target SOC
- User disconnects
- Error occurs
Chapter 9: State Machine Theory in EVCC
9.1 What Is a State Machine?
A state machine is a system that changes behavior based on current state.
EVCC states include:
- IDLE
- CONNECTED
- NEGOTIATING
- CHARGING
- FAULT
9.2 Why State Machines Are Essential
Charging involves sequential steps that must occur in strict order. State machines prevent unsafe transitions.
9.3 Typical EVCC State Diagram
| State | Description | Next Possible States |
|---|---|---|
| IDLE | No cable connected | CONNECTED |
| CONNECTED | Cable inserted | NEGOTIATING |
| NEGOTIATING | Parameter agreement | CHARGING |
| CHARGING | Energy transfer | TERMINATING, FAULT |
| FAULT | Error detected | IDLE |
Chapter 10: Timing, Latency, and Synchronization
10.1 Why Timing Matters
Charging systems operate at high power levels where milliseconds matter.
Timing controls:
- Safety response speed
- Communication retries
- Power ramp stability
10.2 Message Frequency
Typical EVCC update intervals:
| Message Type | Interval |
|---|---|
| Status update | 100–500 ms |
| Current request | 50–200 ms |
| Fault monitoring | 10–50 ms |
10.3 Timeout Mechanisms
If a response is not received within a defined time, EVCC:
- Retries message
- Reduces power
- Terminates session
Chapter 11: Fault Handling and Safety Logic
11.1 Why Fault Handling Is Critical
EV charging involves high voltage, making fault detection essential.
11.2 Common Fault Categories
| Fault Type | Example | EVCC Response |
|---|---|---|
| Electrical | Overvoltage | Immediate stop |
| Thermal | Battery overheating | Reduce current |
| Communication | Lost message | Retry / abort |
| Security | Invalid certificate | Reject session |
11.3 Safe Shutdown Sequence
EVCC performs controlled shutdown:
- Request current reduction
- Wait for confirmation
- Disable contactors
- Log fault
Chapter 12: Human-Centric Interpretation of EVCC Behavior
12.1 EVCC as a Digital Negotiator
EVCC behaves like a negotiator ensuring:
- Maximum speed
- Minimum risk
- Fair energy pricing
12.2 What Happens When You See “Charging Failed”
Behind that simple message, EVCC likely detected:
- Handshake failure
- Parameter mismatch
- Security issue
12.3 Why Some Chargers Are Slower
Charging speed is limited by:
- Vehicle capability
- Charger capability
- Negotiated agreement
EVCC always chooses the safest common value.
Chapter 13: Summary of Part 2
This section established the theoretical foundation of EVCC communication by explaining:
- Layered protocol architecture
- PLC fundamentals
- Message sequencing
- State machine logic
- Timing and fault handling
These principles form the backbone of all modern EV charging standards.
Next in PART 3
The next section will explore:
- ISO 15118 deep dive
- DIN 70121 comparison
- Amendments and evolution (15118-20)
- Cybersecurity and PKI
- Plug-and-Charge theory
No comments:
Post a Comment