Session end verdicts

The categories the tool uses to say why a session ended, and who is the likely cause.

Categories

CategoryMeans
Completed normallySessionStop was answered and the Control Pilot went back to B or A
No digital communicationNo 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 highPairing never finished; the verdict names who owed the next message
SDP failureThe charger never answered discovery
TCP failureThe connection that carries the session was refused or reset before any V2G message
TLS failureThe handshake ended with an alert or was cut off
Encrypted, not decryptedThe session ran over TLS and no key log was loaded
Stopped before energy by designOnly 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 failedNo common protocol in the app handshake
EXI errorA message could not be decoded
FAILED responseThe charger answered a request with a FAILED response code
Authorization not grantedAuthorization stayed Ongoing or failed
Connection lostThe connection closed mid session with no stop and no notification
TimeoutA side did not answer in time and the session ended after it
EVSE stopped / EV stopped earlyOne side stopped before the other asked it to
CP faultState F, an out of range level or lost PWM during charging
Incomplete captureThe 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