Car plugged in, no SLAC match
The Control Pilot shows a car, but the two powerline modems never pair: no 5 percent duty cycle, no SLAC at all, a stalled sequence or a match that never completes.
What you see
- The car is plugged in, the charger shows it is connected (state B), and nothing else happens. Many chargers fall back to an error or restart after a while.
- The stage strip stops at Plug-in or SLAC.
- The verdict is Never charged with No digital communication, SLAC timeout or SLAC attenuation too high. For a SLAC timeout the explanation names the last message seen and the side that never sent the next one.
- In the capture: nothing at all, CM_SLAC_PARM.REQ repeated without an answer, or a sequence that stops somewhere before CM_SLAC_MATCH.CNF.
Likely causes
| Cause | Who | How to confirm in the capture |
|---|---|---|
| The charger never sets the 5 percent duty cycle (it stays at +12 V without PWM, or offers a nominal duty for basic charging) | EVSE | The Duty % lane never enters the 3 to 7 percent window; CP-04 fails; the verdict is No digital communication with the charger as party |
| The car sees 5 percent but never starts SLAC (digital communication disabled, modem not powered, car expects basic charging) | EV | Duty % at 5 percent, no CM_SLAC_PARM.REQ; the verdict names the car |
| The charger does not answer CM_SLAC_PARM.REQ (SLAC not started on its side, modem not in the charger role, host not listening on the modem interface) | EVSE | Repeated CM_SLAC_PARM.REQ, no CM_SLAC_PARM.CNF; SL-01 lists CM_SLAC_PARM.CNF as missing |
| No attenuation result after the sounding (the charger modem produces no CM_ATTEN_PROFILE.IND, or the host never sends CM_ATTEN_CHAR.IND) | EVSE | The last SLAC message is CM_MNBC_SOUND.IND; SL-05 fails |
| Poor coupling: a long or damaged CP wire, a missing or wrong coupling circuit, a sniffer in a bad spot | Either | SL-06 warns, the SLAC tab shows high attenuation across the carrier groups; the verdict may be SLAC attenuation too high |
| Crosstalk: the car hears neighbouring chargers and matches the wrong one, or waits for results from several | EV or site | Several responders in the SLAC tab; SL-09 when the car picked one that was not the loudest |
| The match is refused or unanswered (RunID or MAC mismatch, charger already gave up) | Either | CM_SLAC_MATCH.REQ without CM_SLAC_MATCH.CNF; SL-02 when RunIDs overlap |
| Repeated attempts: the charger steps the Control Pilot through E or F and restarts, or the car restarts with a new RunID | Either | SL-07 counts attempts, SL-08 gives the total duration; CP-05 checks the E or F step |
A sequence that completes (CM_SLAC_MATCH.CNF is in the capture) but is followed by silence is usually a network key problem: one modem was never given the NMK from the match. That case is covered under SLAC matched, but no SDP answer or TCP connection.
What to check in this tool
- Stage strip and verdict: which step broke, and which message the verdict says is missing.
- CP state and Duty % lanes (needs a Control Pilot log): the car in state B, then the 5 percent duty cycle, before the first CM_SLAC_PARM.REQ.
- SLAC tab: attempts with their RunIDs, each responder with its average attenuation, and the attenuation per carrier group.
- Checks tab: SL-01 names the missing messages, SL-03 and SL-04 the sounding, SL-05 the time to results, SL-06 the attenuation, CP-04 and CP-05 the Control Pilot side.
Fixes that usually work
- Make sure the charger switches to 5 percent as soon as it sees state B and holds it steadily. A duty cycle that flickers between 5 percent and a nominal value confuses many cars.
- Check the modem configuration on both sides: the charger modem in the charger role, SLAC enabled in its parameter block, and the host starting SLAC only when it sees state B.
- Check that each host sets the network key in its own modem (CM_SET_KEY) with the values exchanged in the match.
- Test with a short, known good cable, then with the real one, and compare the attenuation. The threshold in the profile (slac.attenuationMaxDb) is lab practice; set it to what your coupling normally shows.
- On a site with several chargers, test with only one cable plugged in. If the problem goes away, it is crosstalk: separate the cables or improve the charger's filtering.
- Unplug fully (state A) between attempts. Some cars try SLAC only a limited number of times per plug in and then wait for a new connection.
The SLAC timers and the attenuation threshold in the limit profile are flagged for verification against ISO 15118-3. See Every timer and timeout for the list.
Sources
- ISO 15118-3:2015, SLAC procedure and timers
- IEC 61851-1:2017, Table A.8, the 5 percent duty cycle