Every timer and timeout
The timing values of every layer, from the Control Pilot to the charging loop and the CAN protocols, with the value the tool uses, where it comes from and the check that measures it.
The values in use
The table above is read live from the active limit profile, so it shows your edits. The tables below explain the same values by family, with the shipped defaults. A value flagged verify came from a secondary source and has to be checked against the purchased standard before a result is quoted.
A timer always belongs to one side: the side that waits. When it runs out, that side gives up, usually by closing the connection without a SessionStop. The verdict then reads Timeout or Connection lost, and the party is the side that did not send in time, not the side that gave up.
Control Pilot (IEC 61851-1)
| What | Profile value | Source | Check |
|---|---|---|---|
| Car follows a new PWM current limit (pw.settlingTimeS) | 5 s | IEC 61851-1:2017 Table A.6, sequence 6 | PW-01 |
| Car stops drawing current after the charger asks, also used after PowerDelivery Stop (pw.currentZeroTimeS) | 3 s | Table A.6, sequences 9.1 and 10.1 | PW-03 |
| Charger opens its switching device after C to B (pw.switchOpenAfterCToBS) | 100 ms | Table A.6, sequence 8.1 (SAE J1772 allows 3 s) | PW-03 |
| PowerDeliveryReq Start to the B to C change (cp.transition.maxDelayAfterPowerDeliveryS) | 3 s, verify | Profile | CP-07, CP-08 |
| Charger waits for SLAC after setting 5 percent, TT_EVSE_SLAC_init (cp.retry.ttEvseSlacInitMinS and MaxS) | 20 to 50 s, verify | ISO 15118-3 | CP-05 |
| Length of the E or F step before the charger retries, T_step_EF (cp.retry.tStepEfMinS and MaxS) | 3 to 5 s, verify | ISO 15118-3 | CP-05 |
| Rise and fall time of the PWM edges | 2 us | Table A.2 | CP-10 |
SLAC (ISO 15118-3)
| What | Profile value | Check |
|---|---|---|
| Spacing of the CM_MNBC_SOUND.IND messages (slac.batchIntervalMinMs and MaxMs) | 20 to 50 ms, verify | SL-04 |
| TT_EV_atten_results: first CM_START_ATTEN_CHAR.IND to CM_ATTEN_CHAR.IND (slac.ttEvAttenResultsMs) | 1200 ms, verify | SL-05 |
| First CM_SLAC_PARM.REQ to CM_SLAC_MATCH.CNF (slac.matchTimeoutS) | 10 s, verify | SL-08 |
| Silence after one SLAC message that counts as a stall rather than a capture that ended early (slac.stepTimeoutS) | 2 s, verify | Used by the verdict |
| TT_EVSE_SLAC_init, see the Control Pilot table | 20 to 50 s, verify | CP-05 |
ISO 15118-3 defines more SLAC timers that the tool does not measure one by one. They explain why a stalled step is reported as a stall so quickly:
| Timer | Meaning | Commonly quoted value |
|---|---|---|
| TT_match_response | How long the car waits for an answer to one of its requests, such as CM_SLAC_PARM.CNF | 200 ms |
| TT_match_sequence | How long a side waits for the next message of a running sequence | 400 ms |
| TT_EVSE_match_MNBC | How long the charger collects sounds before it sends its results | 600 ms |
| TT_EVSE_match_session | How long the charger waits for CM_SLAC_MATCH.REQ | 10 s |
| TT_match_join | How long the car's modem may take to join the network after the match | 12 s |
These five values are not in the limit profile and are given from secondary sources. Check them against ISO 15118-3 before quoting them.
SDP and communication setup
| What | Profile value | Source | Check |
|---|---|---|---|
| Shortest wait before the car repeats an SDP request (sdp.minRetryIntervalMs) | 250 ms | ISO 15118-20 V2G20-159 | SD-06 |
| Allowance for timestamp jitter on that gap (sdp.retryIntervalToleranceMs) | 20 ms | Lab practice | SD-06 |
| Requests after which the car stops discovery (sdp.maxRequests) | 50 | ISO 15118-20 V2G20-161 | SD-06 |
| Time within which an SDP response is expected (sdp.responseTimeoutS) | 5 s, verify | Profile | SD-01 |
| V2G_EVCC_CommunicationSetup_Timeout: first SDP request to SessionSetupRes (tim.communicationSetupTimeoutS) | 20 s, verify | ISO 15118-2 timing tables | TIM-04 |
SD-06 applies the ISO 15118-20 pacing to ISO 15118-2 sessions too; whether ISO 15118-2 has the same rule is marked for verification in the check itself.
ISO 15118-2 and DIN SPEC 70121 messages
| Timer | Applies to | Profile value | Check |
|---|---|---|---|
| V2G_EVCC_Msg_Timeout (tim.msgTimeoutS) | Most request and response pairs | 2 s, verify | TIM-01 |
| V2G_EVCC_Msg_Timeout, long (tim.msgTimeoutLongS) | ServiceDetail, PaymentDetails, CertificateInstallation, CertificateUpdate, PowerDelivery | 5 s, verify | TIM-01 |
| V2G_EVCC_Msg_Timeout, CurrentDemand (tim.msgTimeoutCurrentDemandS) | CurrentDemand | 0.25 s, verify | TIM-01 |
| V2G_EVCC_Ongoing_Timeout (tim.ongoingTimeoutS) | Authorization, ContractAuthentication and ChargeParameterDiscovery while EVSEProcessing is Ongoing | 60 s, verify | TIM-02 |
| V2G_SECC_Sequence_Timeout (tim.sequenceTimeoutS) | Gap between a response and the next request | 60 s, verify | TIM-03 |
| V2G_EVCC_CommunicationSetup_Timeout | SDP to SessionSetupRes | 20 s, verify | TIM-04 |
| V2G_EVCC_CableCheck_Timeout | The whole CableCheck loop (DC) | Not in the profile | None |
| V2G_EVCC_PreCharge_Timeout | The whole PreCharge loop (DC) | dc.prechargeTimeoutS 7 s (verify) | DC-01 |
- The EVCC timers run in the car and bound how long the charger may take. The charger has its own performance times for the same messages, shorter than the car's timeouts, so that a charger that meets them never trips the car.
- The charger runs V2G_SECC_Sequence_Timeout and gives up on a car that stops sending.
- TIM-05 reports the polling interval of the ChargingStatus or CurrentDemand loop, and TIM-06 the spread of response times per message type. Both are informational.
Every value in this table is flagged for verification in the limit profile. The CableCheck and PreCharge timeouts are not in the profile; figures often quoted for ISO 15118-2 are 40 s and 7 s, with slightly shorter values in DIN SPEC 70121. Check them against the edition you test to.
ISO 15118-20 differences
- The families are the same: a response time per message, a limit on Ongoing loops, a sequence timeout in the charger and a limit on the whole setup. ISO 15118-20 has its own timing table.
- The tool applies the profile values by message name. The ISO 15118-20 charge loops (DC_ChargeLoop, AC_ChargeLoop) are measured against the general V2G_EVCC_Msg_Timeout, not the CurrentDemand value; PowerDelivery gets the long value.
- TIM-02 covers the Authorization loop. The ScheduleExchange and DC_CableCheck Ongoing loops are not measured by it.
- The car signals progress too: EVProcessing in DC_PreChargeReq and PowerDeliveryReq says when the car has finished its side of the step.
- Every message header carries a timestamp. IS20-07 checks that it never runs backwards, which also helps to judge the capture's own clock.
- SDP retry pacing (250 ms, 50 requests) comes from ISO 15118-20 and is what SD-06 measures.
The limit profile has no separate ISO 15118-20 timing values yet. Check the ISO 15118-20 timing table before relying on TIM-01 for an ISO 15118-20 session.
CHAdeMO and GB/T 27930
| What | Profile value | Check |
|---|---|---|
| CHAdeMO status message period (chademo.messagePeriodMs) | 100 ms, verify | CAN-02 |
| GB/T BCL charging demand period (gbt.bclPeriodMs) | 50 ms, verify | CAN-02 |
| GB/T BCS charging status period (gbt.bcsPeriodMs) | 250 ms, verify | CAN-02 |
| Allowed drift of a cyclic period (can.periodTolerancePct) | 60 % | CAN-02 |
| Stall: a cyclic message missing for this many periods (can.periodStallFactor) | 4 times | CAN-02 |
| Longest silence in a running session (can.maxSilenceS) | 2 s | CAN-01 |
| GB/T: each startup step answered within (gbt.handshakeTimeoutS) | 5 s, verify | GB-01 to GB-04 |
- GB/T 27930 gives each expected message a timeout. The side that misses one reports it: the BMS with BEM, naming the charger message it did not get, and the charger with CEM, naming the BMS message. Commonly quoted values are 5 s for most messages, shorter for the cyclic demand and output messages and longer for the statistics.
- CHAdeMO has its own detection times for missing frames. The specification is not public, so the tool does not measure them directly; CAN-01 and CAN-02 catch the silence and the stalls instead.
The GB/T per message timeouts other than the 5 s step limit, and the CHAdeMO detection times, are not in the profile and are to be checked against the specifications.
Sources
- Limit profile iec61851-iso15118-2-default, the values the checks use
- IEC 61851-1:2017, Tables A.2 and A.6
- ISO 15118-3:2015, SLAC timing
- ISO 15118-2:2014, timing tables
- ISO 15118-20:2022, V2G20-159, V2G20-161
- GB/T 27930-2015