GW29.9K-ET + BYD HVM 13.8: compatible with conditions
The source supports this combination only under stated conditions.
Communication & inverter setup
Conditions attached to this Pair
ARM firmware versions 02 and above are required for compatibility. BYD CAN communication line PIN1/2 corresponds to inverter CAN communication line PIN4/5.
The maximum charge/discharge current of single-cluster HVS battery is 25A, ET30kW with single-cluster HVS battery will not be able to reach the nominal maximum charge/discharge power of the inverter.ET15-30 series with HVM battery maximum charging and discharging current of 40A.
How to read this page
Confirmed by this dataset
- The verdict is derived from bound canonical entities, not fuzzy matching.
Not assumed
- Missing pinout, firmware, cable or DIP data does not mean none is required.
- A source-listed setup value is not automatically treated as a manufacturer-recommended method.
Source evidence
View raw source evidence
BYD | Battery-Box Premium HVM*2 | HVM 13.8 | ET (15-30kW)Why GW29.9K-ET + BYD HVM 13.8 is listed this way
Compatibility basis
This published page binds the exact inverter GW29.9K-ET to the exact battery model BYD HVM 13.8. The current database resolution is CONDITIONAL under ET (15-30kW). The verdict is produced from the stored manufacturer-source relationship for these canonical entities, not from fuzzy search similarity or a generic voltage-class assumption.
Communication setup recorded for this Pair
No communication setup is added to this page unless it exists in the stored source evidence.
Evidence coverage
The result is backed by 1 page-level evidence record on page 3 of GW_BATTERY_COMPAT_20260901_EN_V029.1 (2026-09-01).
No extra wiring, DIP-switch, firmware, cable, charge-limit, or pinout claim is created from absence or analogy.
The source attaches 2 explicit conditions to this Pair; the condition text is shown separately and is not generalized to other models.
Search by the model names you actually have
The search layer can handle aliases and fuzzy input; compatibility is checked only after the exact database entities are confirmed.