Session end verdicts
The categories the tool uses to say why a session ended, and who is the likely cause.
Categories
| Category | Means |
|---|---|
| Completed normally | SessionStop was answered and the Control Pilot went back to B or A |
| No digital communication | No 5 % duty cycle, or 5 % and the car never started SLAC, or a capture that was not taken on the charging cable |
| SLAC timeout / attenuation too high | Pairing never finished; the verdict names who owed the next message |
| SDP failure | The charger never answered discovery |
| TCP failure | The connection that carries the session was refused or reset before any V2G message |
| TLS failure | The handshake ended with an alert or was cut off |
| Encrypted, not decrypted | The session ran over TLS and no key log was loaded |
| Stopped before energy by design | Only with a profile for a test rig that relays messages but no power, such as Open-RTH: the session stopped before the energy transfer with no refusal and no error before it |
| Protocol negotiation failed | No common protocol in the app handshake |
| EXI error | A message could not be decoded |
| FAILED response | The charger answered a request with a FAILED response code |
| Authorization not granted | Authorization stayed Ongoing or failed |
| Connection lost | The connection closed mid session with no stop and no notification |
| Timeout | A side did not answer in time and the session ended after it |
| EVSE stopped / EV stopped early | One side stopped before the other asked it to |
| CP fault | State F, an out of range level or lost PWM during charging |
| Incomplete capture | The capture ends mid session |
The categories follow the session ending errors of the ChargeX recommended practices. The verdict is a hint for triage, not a certification result.
Sources
- SPEC.md of this tool, section 10