DC test cases, worked

Eighteen illustrative DC test cases: SLAC with attenuation, SDP, TLS, the protocol handshake, cable check with an insulation fault, pre-charge, current demand, power limits, stops, welding detection, pause, renegotiation, bidirectional limits, CHAdeMO and GB/T, each linked to the checks and demos that show it.

About these test cases

Most of these test cases run in the analyzer: name each capture after its test case and the Batch page or the command line says pass, fail or inconclusive per file. See Running test cases.

These test cases are this tool's own illustrative plan, written from the public descriptions of the standards. They are not copies of any standard's test suite, and passing them does not make a product conformant or certified. For certification, use the official test suite and an accredited or authorised lab.

Common setup: the charger under test or the car under test, the other side real or simulated, a DC load or battery emulator, an isolation fault box, a powerline sniffer (a CAN logger for CHAdeMO and GB/T), and a voltage probe at the inlet. Where a demo shows the case, its id is named; a demo that fails on purpose shows the negative variant.

Link and security

Id and purposePreconditionsTest bodyExpected result and pass criteriaReferenceObserved by
DC-01 SLAC under attenuationProgrammable attenuator in the powerline path; a second charger on a neighbouring cable.Match at low attenuation, then raise it in steps until matching fails. Repeat with the neighbour active.Match completes in time at the attenuations the lab accepts; retries are bounded; the car matches the charger with the lowest attenuation, never the neighbour.ISO 15118-3; tests in ISO 15118-5SL-01, SL-05, SL-06, SL-07, SL-08, SL-09. Demo slac-fail
DC-02 SECC discoveryMatched link.Car sends SECC discovery requests; charger answers with address, port and security.An answer arrives; retries are paced (at least 250 ms apart) and stop by 50 requests; TCP connects to the announced address and port.ISO 15118-20 V2G20-159, V2G20-161; ISO 15118-2SD-01 to SD-06, TC-01. Demo tcp-refused
DC-03 TLS handshakePlug and Charge set up; valid charger certificate chain; then an unknown root, then an expired certificate.Run the session three times.Valid chain: handshake completes with an accepted version and cipher suite. Unknown root or expired certificate: the car aborts with an alert, and the session does not continue without TLS.ISO 15118-2 8.5.2; ISO 15118-20 7.7.3TL-01 to TL-07, PK-01, PK-02, SD-04, SEC-03. Demos tls-fail, pnc-expired
DC-04 Protocol handshakeCar offers DIN SPEC 70121, ISO 15118-2 and ISO 15118-20 with priorities.Run once with each charger configuration: all three, one of them, none.Charger picks an offered protocol; with no common protocol the session ends; a protocol that needs TLS runs only over TLS.ISO 15118-20 8.2HS-01, HS-02, HS-03

The attenuation limit of DC-01 is lab practice in this tool (40 dB in the default profile, flagged verify). Take the values of ISO 15118-3 and -5 for a formal test.

Before current flows

Id and purposePreconditionsTest bodyExpected result and pass criteriaReferenceObserved by
DC-05 Cable check, normalSession up to CableCheck; no insulation fault.Let the car send CableCheckReq until the charger answers Finished.Isolation valid; the Ongoing loop ends within V2G_EVCC_CableCheck_Timeout; response codes OK.IEC 61851-23; DIN SPEC 70121, ISO 15118-2 CableCheckTIM-02, SQ-05, SQ-01
DC-06 Cable check with insulation faultFault box set to a resistance from DC+ to PE below the charger threshold.Run to CableCheck.Charger reports a failed isolation, answers FAILED or with a shutdown status, and never closes its output contactors.IEC 61851-23SQ-05, SQ-01. Demo cablecheck-fail
DC-07 Pre-charge within toleranceCableCheck passed; battery emulator at a known voltage.Car sends PreChargeReq with the battery voltage as target.Output reaches the target within tolerance before the timeout; answers in time. Written out in Anatomy of a test case.IEC 61851-23; PreCharge of DIN SPEC 70121, ISO 15118-2 and -20DC-01, TIM-01. Demo iso20
DC-08 Pre-charge timeoutAs DC-07; charger output limited below the target (fault injected).Car sends PreChargeReq until its timeout.Car ends the session at its timeout; the charger does not close to a battery at a different voltage.As DC-07DC-01, TIM-01. Demo precharge-fail

Pre-charge tolerance (20 V), pre-charge timeout (7 s) and V2G_EVCC_CableCheck_Timeout (38 s) are flagged verify in the default profile. Insulation thresholds come from IEC 61851-23 and are not quoted here.

Energy transfer

Id and purposePreconditionsTest bodyExpected result and pass criteriaReferenceObserved by
DC-09 Current demand followingCharging loop running.Car steps its target current up and down, for example 50, 150, 80 A.Present current follows each target and stays at or below it; each loop response arrives within the CurrentDemand timeout; the loop keeps its pace.DIN SPEC 70121, ISO 15118-2 CurrentDemand; ISO 15118-20 DC_ChargeLoopPW-01, IS20-04, TIM-01, TIM-05, PW-05. Demo iso20
DC-10 Charger power limitationCharging at full power.Lower the charger limit (backend profile, emulated heat, or a second car on a shared cabinet).The charger announces the lower limit and keeps its output inside what it announced.ISO 15118-2, -20PW-01, IS20-03
DC-11 RenegotiationISO 15118-20 session with a schedule.Charger sets EVSENotification ScheduleRenegotiation.Car answers with PowerDelivery ScheduleRenegotiation in time; the schedule exchange runs to its end; charging continues.ISO 15118-20 8.3.3IS20-09, SQ-09, SQ-01
DC-12 Bidirectional discharge limitsISO 15118-20 BPT service offered and selected.Car requests discharge at a target below the charger maximum.Messages match the selected service; discharge stays inside the announced limits and at or below the target; reverse power only in a BPT session.ISO 15118-20 8.3, 8.4IS20-01, IS20-03, IS20-04, IS20-05, IS20-08. Demo bpt-limit

Stopping

Id and purposePreconditionsTest bodyExpected result and pass criteriaReferenceObserved by
DC-13 Stop by the carCharging loop running.Car reaches its target state of charge, or the driver stops from the car.PowerDelivery Stop, current near zero in time, welding detection, SessionStop; TCP closed only after SessionStopRes.ISO 15118-2, -20PW-03, SQ-01, TC-02
DC-14 Emergency stop or stop at the chargerCharging loop running.Press the stop button; in a separate run, the emergency stop.Charger signals the stop (EVSENotification StopCharging, or an emergency shutdown status); car reacts in time; current falls to near zero.IEC 61851-23; ISO 15118-2SQ-09, SQ-05, PW-03
DC-15 Welding detectionAfter PowerDelivery Stop.Car sends WeldingDetectionReq; in a separate run, emulate a welded charger contactor.The present voltage in the responses falls; with the emulated weld it stays high and the car reports a fault.DIN SPEC 70121, ISO 15118-2 WeldingDetectionSQ-01; the voltage shows in the Curve tab
DC-16 Pause and resumeISO 15118-2 or -20 session.-2: car ends with ChargingSession Pause and resumes. -20: charger sets GoToPause.-2: resumed session reuses the SessionID. -20: the session ends as a pause.ISO 15118-2; ISO 15118-20 8.3SQ-11, IS20-06

The times a car has to react to a stop request and the time within which a DC output must fall are set by IEC 61851-23 and the message standards and were not checked for this article. Take them from the standard for a formal test.

CHAdeMO and GB/T

Id and purposePreconditionsTest bodyExpected result and pass criteriaReferenceObserved by
DC-17 CHAdeMO basic sessionCAN logger on the charging CAN.Charge from start to a stop by the car; in a second run, trigger a charger fault.Both sides on the bus with the same control protocol number; cyclic messages keep their period; output current at or below the request and voltage inside the battery window; current only while the car allows it; fault flags only in the fault run.CHAdeMO specification; certification by the CHAdeMO bodiesCH-01 to CH-06, CAN-01, CAN-02. Demos chademo, chademo-stop
DC-18 GB/T 27930 basic sessionCAN logger on the charging CAN (J1939).Charge from handshake to stop; in a second run, the BMS stops with a fault.Handshake (CHM, BHM), recognition (CRM, BRM), parameters (BCP, CML) and readiness (BRO, CRO) each answered in time; same protocol version; output at or below the BMS demand; voltage inside the window; stop with BST or CST and the statistics BSD and CSD.GB/T 27930-2015; conformance per GB/T 34658, interoperability per GB/T 34657.1GB-01 to GB-08, CAN-01. Demos gbt, gbt-bst
DC-19 Limits of both sides heldCapture of a DC session (DIN SPEC 70121, ISO 15118-2 or ISO 15118-20) through the charging loop.Charge with the charger lowering its current limit during the loop; in a second run, let the car ask for more than the limit.The car asks for no more current and voltage than the charger allows, the charger delivers no more than its own limit and the car target after the settling time, and the voltage and current ranges of both sides overlap.DIN SPEC 70121 and ISO 15118-2 ChargeParameterDiscovery and CurrentDemand; ISO 15118-20 DC_ChargeLoopLM-01 to LM-05 (IS20-03 and IS20-04 for ISO 15118-20). Demo din-ok

The CAN periods, margins and the GB/T step timeout in the default profile (for example 5 s per handshake step) are flagged verify.

In this tool

Every case above that names a demo can be opened from the demo list and compared with a capture from the lab in the Compare tab, which shows the first step where the two sessions part. The Negotiation tab puts the limits both sides stated beside each other, which is the quickest way to see why DC-10 or DC-12 failed.

Sources