Worked example: SLAC that never matches
The slac-fail demo read step by step: three SLAC attempts that each stop after the attenuation results, why the analyzer shows three sessions, what the 56 dB says, and how to find the weak part of the link.
The capture
Load the demo SLAC never matches (slac-fail). It holds HomePlug management messages between one car and one charger modem and no IP traffic at all. It has no Control Pilot log.
- The analyzer shows three sessions, Session 1 of 3 to Session 3 of 3. Every new SLAC attempt starts a session, so each attempt gets its own verdict.
- All three read Never charged, SLAC attenuation too high, with Either as the likely party and medium confidence.
- The stage strip of each: Plug-in not in the capture, SLAC failed, everything after it not reached.
One attempt, message by message
- EV: CM_SLAC_PARM.REQ, 0.000 s, RunID a1b2c3d4e5f60718
- EVSE: CM_SLAC_PARM.CNF, 0.032 s: the charger answers, so its SLAC is running
- EV: CM_START_ATTEN_CHAR.IND, 0.060 to 0.110 s, three times
- EV: CM_MNBC_SOUND.IND, 0.150 to 0.420 s: ten sounds, 30 ms apart, counting down from 9 to 0
- EVSE: CM_ATTEN_PROFILE.IND, 0.490 s: the charger modem reports 56.1 dB on average over 58 groups
- EVSE: CM_ATTEN_CHAR.IND, 0.510 s: the result, sent to the car
- EV: CM_ATTEN_CHAR.RSP, 0.541 s, result 0: the car received it
- EV: No CM_SLAC_MATCH.REQ, the car starts again 6 s later with a new RunID
Every step up to the result works, and in time: SL-03 finds the ten sounds the car announced, SL-04 a mean interval of 30 ms, SL-05 the result 450 ms after the car started the measurement. The sequence stops at the one decision that belongs to the car.
What the findings say
| Check | Result | What it means here |
|---|---|---|
| SL-06 | Warning: 56.1 dB over 58 groups, the profile allows 40 dB | The link is weak as the charger modem measured it. The number comes from CM_ATTEN_CHAR.IND, so moving the sniffer does not change it |
| SL-08 | Error: no CM_SLAC_MATCH.CNF within 10 s of the first request | The attempt never completed |
| SL-01 | Error: CM_SLAC_MATCH.REQ and CM_SLAC_MATCH.CNF missing; the last SLAC message was CM_ATTEN_CHAR.RSP | The car owed the next message |
| SL-02 to SL-05 | Pass | RunIDs, sounding and timing are fine: the protocol works, the signal does not |
| SL-07 | Pass, 1 attempt | Counted per session. With one session per attempt, the retries show as the three sessions instead |
| SL-09 | Not applicable | Only one charger answered, so there was no choice to get wrong |
The second and third attempts report 55.9 dB and 55.8 dB. The same result three times points at something steady in the path, such as the cable, a contact or a coupling circuit, rather than a burst of interference.
Confirming the cause
- Who decided: the car. The charger answered every message and delivered a result; the car acknowledged it and then sent no CM_SLAC_MATCH.REQ. That fits a car that rejects a charger whose attenuation is above its own limit. The capture shows the behaviour, not the limit.
- Why Either: the loss can sit in the car's inlet and coupling, in the cable and connector, or in the charger's coupling circuit. The capture cannot tell which.
- Read the attenuation per carrier group in the SLAC tab. High in every group means loss along the path; high in a few groups only means narrowband interference.
- Swap one part at a time: the same car at another charger, another car at this charger, a short known good cable. The part that moves the 56 dB is the part at fault.
- Record the Control Pilot next time. Without a log CP-04 and CP-05 are not applicable, and you cannot see whether the car stays in state B or the charger steps through E or F between attempts.
What a fix looks like
- Repair what the swap test pointed at: a coupling component, the pilot contact in connector or inlet, a damaged cable.
- A healthy direct link sits far lower: the ac-ok demo, recorded the same way, reports 23.0 dB.
- Once the attenuation is down, the car sends CM_SLAC_MATCH.REQ right after CM_ATTEN_CHAR.RSP, the charger answers with CM_SLAC_MATCH.CNF, and SDP follows.
- Do not raise slac.attenuationMaxDb to make SL-06 pass. The car made its own decision here; the threshold only changes what the analyzer warns about. Car plugged in, no SLAC match lists the other ways SLAC fails.
slac.attenuationMaxDb (40 dB) is lab practice, and slac.matchTimeoutS (10 s) is flagged for verification against ISO 15118-3. The attenuation at which a car stops accepting a charger is its own design choice.
Sources
- ISO 15118-3:2015, SLAC procedure and timers
- SPEC.md of this tool, FR-ENC-05, the failing demo sessions