A video showing a Chinese EV connected to a CCS2 charger can demonstrate that charging started. It cannot, by itself, establish what equipment was used, whether the required energy was delivered or how a subsequent interruption will be handled.
For a proposed GB/T-to-CCS2 DC conversion arrangement, agree a reviewable session record before purchase. The method below is a procurement protocol to discuss with qualified providers; it is not a product certification or an instruction to modify high-voltage equipment.
Know what the demonstration must identify
CharIN’s technical FAQ describes CCS as a system involving the physical interface, control functions and communication. It distinguishes communication requirements rather than treating connector fit as sufficient interoperability evidence. Its CCS specification resource provides further technical background.
An active conversion product needs its own documented supported combinations. A passive connector shape cannot provide an otherwise missing protocol translation. Do not interpret an industry background document as approval of a particular third-party device.
Use our charging acceptance checklist for the initial purchase scope. The session record here adds the evidence needed to assess a particular demonstration and investigate an unsuccessful one.
Define a specific acceptance objective
Agree the vehicle, device, charger, firmware and normal manufacturer-supported conditions. State what the demonstration should establish, such as completion of the relevant charging window and delivery of enough energy within the buyer’s available stop.
Do not require an unsafe attempt outside equipment ratings to reach a marketing power number. If the proposed pairing is not manufacturer-supported or its compatibility scope remains unclear, resolve that before arranging operation.
The objective should distinguish a China demonstration from a destination check. A session on one charger does not establish compatibility with every public network or software revision.
Keep one record for the complete pairing
| Record field | Required descriptive detail |
|---|---|
| Vehicle | VIN, exact variant, installed DC inlet and relevant software |
| Conversion equipment | Manufacturer, model, serial identifier and firmware |
| Charger | Equipment identity, operator, connector and output range |
| Conditions | Date, starting SOC, relevant ambient and vehicle conditions |
| Session outcome | Ending SOC, delivered energy, start/finish times and completion status |
| Interruptions | Time, displayed message and retained diagnostic evidence |
| Follow-up | Responsible provider, resolution and repeat-check record |
This is our proposed evidence format, not a claim that every field is mandated by one standard. Retain the equipment instructions and applicable provider approval alongside it.
Calculate average power from the stated energy boundary
Consider a completely hypothetical record showing 28kWh delivered by the charger over 25 minutes of energy transfer. Average power at that recorded boundary is 28 divided by 25/60, or approximately 67.2kW.
If the complete stop took 35 minutes including initialization and other non-transfer time, energy divided by total stop duration is 48kW. Both calculations can be useful, but they answer different questions. Neither equals a momentary peak shown in a screenshot.
Keep the energy boundary explicit. Charger-reported energy is not automatically the net energy stored in the battery. Do not claim an efficiency result without suitable measurements at the relevant boundaries.
Preserve unsuccessful sessions as evidence
If charging fails to start or stops early, retain the vehicle, converter and charger messages with timestamps. Ask the responsible provider to distinguish an equipment fault, unsupported combination, access/payment issue or another identified cause.
A successful session later on another charger does not explain the earlier failure. Keep the two records separate and record any changed firmware, setup or operating conditions. A buyer needs a defined resolution for the intended equipment, rather than an unrelated success video.
Only qualified providers should assess technical faults and conduct operation within supported limits. Do not bypass protective functions to make an acceptance record appear successful.
Decide which changes require another check
A substituted VIN, different converter, new firmware or different charger can affect the evidence scope. Ask the provider whether the existing supported-combination record still applies and whether another demonstration is needed.
For fleet orders, agree how each delivered unit’s identity and equipment will be verified. A representative test may inform procurement, but it does not automatically establish that every unrecorded unit has the same configuration or condition.
Retain unresolved destination checks in the handover plan. Identify who supplies replacement equipment or assistance if the agreed pairing cannot complete its stated use.
Request a record-led charging proposal
Send your destination, exact vehicle and intended stations through our contact page. Request a supported charging arrangement with a defined inspection demonstration, complete session record and fault-resolution responsibility. Review the whole record rather than approving the purchase from a charging-start photograph.