HomePlug Green PHY: powerline on the Control Pilot
The modem layer under every CCS session: how Green PHY rides on the Control Pilot wire, what its management messages look like, how a car and a charger form their own logical network, and why attenuation and crosstalk matter.
A modem on the pilot wire
CCS adds no wire for data. The car and the charger each have a HomePlug Green PHY modem that puts a high frequency signal onto the Control Pilot line, with protective earth as the return. The 1 kHz PWM of IEC 61851-1 and the powerline carriers share the same pair of conductors: a coupling circuit on each side passes the carriers to the modem and keeps the PWM and its voltage levels away from it, so the analogue states and the digital link work side by side.
- Modulation: OFDM with many carriers in the band between about 2 and 30 MHz, the same band and frame format as HomePlug AV.
- Green PHY transmits only in the robust ROBO modes, which need no per link channel estimation and peak at about 10 Mbit/s. That is far more than V2G traffic needs; robustness matters more than rate on a charging cable.
- To its host the modem looks like an Ethernet bridge: a frame the host sends comes out of the other modem as the same Ethernet frame, so IPv6, UDP and TCP run over it unchanged.
- Host and modem each have a MAC address of their own. The host runs SLAC and the V2G stack; the modem handles the powerline medium and answers the management messages addressed to it.
The coupling circuit, the transmit level and the spectral limits for charging are set in ISO 15118-3 and the Green PHY specification. The figures above are the general HomePlug ones; check the exact values against those documents.
Management messages
Everything that is not user data travels as a management message (MME) in an Ethernet frame with the Ethertype 0x88E1. SLAC is a set of MMEs, and so are the messages a host uses to configure its own modem.
| Field | Size | Meaning |
|---|---|---|
| MMV | 1 byte | Management message version; 0x01 for HomePlug AV 1.1 and Green PHY |
| MMTYPE | 2 bytes, little endian | The message type. The two lowest bits give the variant: 00 request (.REQ), 01 confirmation (.CNF), 10 indication (.IND), 11 response (.RSP) |
| FMI | 2 bytes | Fragmentation information, present when MMV is 0x01 |
| Payload | the rest | Depends on the message |
MMTYPE is little endian, while the IP, TCP and V2GTP headers above it are big endian; a parser that reads it the other way names every message wrongly. Base values from 0x6000 are the charging messages (CM_SLAC_PARM at 0x6064, CM_SLAC_MATCH at 0x607C and the rest of the SLAC sequence). Values from 0xA000 to 0xAFFF are vendor specific and carry the vendor OUI after the header; the analyzer labels them with that OUI and shows their payload as raw bytes.
The MMTYPE base values in the analyzer are marked for verification against the Green PHY specification (SPEC 5.1).
Logical networks, keys and roles
- A HomePlug network (an AVLN) is a set of stations that share a network membership key (NMK) and a network identifier (NID). Stations of different AVLNs on the same wire hear each other but cannot read each other's data.
- One station is the central coordinator (CCo). It sends beacons, admits stations and hands out the key that encrypts data on the medium. In charging, the charger's modem normally takes this role.
- Before SLAC the car's modem belongs to no network. The SLAC messages are therefore exchanged outside any AVLN, which is why every charger within reach can hear CM_SLAC_PARM.REQ.
- CM_SLAC_MATCH.CNF gives the car the NID and NMK of the charger's network. The car's host writes them into its modem (CM_SET_KEY), the modem joins, and from then on car and charger form a private network of two stations.
The NMK travels in the clear inside CM_SLAC_MATCH.CNF. That is how a passive sniffer can follow a session: it reads the key from the match and joins the same network. A sniffer that misses the match sees SLAC and then silence, although the session goes on. The SLAC tab masks the NMK by default because it is a network key.
Attenuation and crosstalk
Signal strength falls on the way from one modem to the other: through the coupling circuits, the charging cable, the connector and any wiring shared with other charge points. Attenuation is that loss in dB. The charger the car is plugged into is normally the loudest, because its signal comes straight down the cable, while a neighbour reaches the car only through coupling between parallel cables or through the supply wiring.
SLAC measures exactly this. The car sends a burst of sounding messages (CM_MNBC_SOUND.IND), each charger modem measures the received level per carrier group (58 groups) and reports it, and the car picks the charger with the lowest average. A match is a physical measurement, not an address lookup.
| What the SLAC tab shows | What it suggests |
|---|---|
| One responder, low average attenuation, flat across the groups | A healthy direct link |
| One responder, high attenuation in every group | Loss in the coupling or the cable: a long or damaged pilot wire, a missing coupling component, a sniffer tapped in a poor place |
| High attenuation in a few groups only | Narrowband interference or a notch in the channel; the average can still pass |
| Several responders with similar values | Crosstalk: neighbouring chargers are nearly as loud as the one in use, and the car may pick the wrong one |
SL-06 compares the average with slac.attenuationMaxDb, a lab practice value of 40 dB in the shipped profile, and SL-09 checks that the car matched the responder with the lowest attenuation. The slac-fail demo shows three attempts at about 56 dB.
CM_VALIDATE is an optional extra step for sites where attenuation alone may not tell chargers apart: the charger asks the car to toggle its Control Pilot state a number of times and counts the toggles.
What a capture holds at this layer
- A sniffer modem on the cable: the SLAC messages of both sides and then, once it has the key, the IP traffic of the session. It does not see the vendor messages between each host and its own modem.
- A capture on the host interface of one side (tcpdump on the charger or the car controller): that host's SLAC messages, its vendor messages with its own modem (setting the key, reading the firmware version) and all IP traffic, but only the frames the modem passes up. SLAC messages the modem handles itself may be missing.
- A capture taken behind a modem on plain Ethernet, or on an MCS link, has no HomePlug frames at all. The analyzer then shows SLAC as not in the capture rather than as failed.
Read Recording a charging session for analysis for where to put the sniffer and A weak or disturbed powerline link for what a weak link looks like in a capture.
Sources
- ISO 15118-3:2015, physical and data link layer, SLAC
- HomePlug Green PHY specification, HomePlug Powerline Alliance
- IEEE 1901-2010, broadband powerline communication, the base of HomePlug AV
- SPEC.md of this tool, section 5.1, the management message layout