GB/T 27930.2 Charger Protocol Testing Guide

Lock the GB/T protocol baseline

Record the exact GB/T 27930.2 edition required by the market, customer or procedure and identify any relationship to earlier charger firmware behavior. Do not infer compatibility across revisions from a successful physical connection.

List the associated connector, system, interoperability, metering and safety documents separately. The communication test equipment must match the required CAN behavior while the complete setup also respects every electrical and connection limit.

• ✓ Name the exact GB/T 27930.2 edition
• ✓ Record charger hardware and firmware
• ✓ List related standards separately

Reproduce the charging communication stages

Build the normal sequence from handshake and recognition through parameter configuration, charging and completion. At each stage, specify the required message, timing, requested voltage or current and expected charger transition.

Correlate CAN logs with charger-reported and independently measured output. Preserve raw traffic when message content or timeout behavior matters, together with the BMS simulator configuration used to produce it.

• ✓ Define messages and timing by stage
• ✓ Compare requested and measured output
• ✓ Save raw CAN and simulator configuration

Separate conformance, interoperability and faults

A completed charging session supports interoperability evidence but does not automatically prove every protocol-conformance case. Keep required normative checks, real-device interoperability and engineering fault diagnosis as identifiable result groups.

For each approved abnormal message, timeout, parameter or termination case, state the expected charger response and safe execution limit. Repeat a failed case with the same baseline after corrective action.