Sol-Ark 60K-3P-480V + Discover Energy Systems AES 210HV: compatible with conditions
The source supports this combination only under stated conditions.
Manufacturer identity is source-defined only. External entity mapping and model expansion are intentionally disabled.
Communication & inverter setup
- Gateway
- LYNK II CAN
- Evidence
- TB-00029-REV2, page 21
Conditions attached to this Pair
2002
LYNK II 2.2.2.0
60K-3P-480V only
4 packs @ 52S1P
How to read this page
Confirmed by this dataset
- The verdict is derived from bound canonical entities, not fuzzy matching.
- The communication/setup values shown are present in the cited source.
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
AES 210HV is designed for Sol-Ark 60K-3P-480V only; 4 packs @ 52S1P, BMS firmware 2002, LYNK II gateway firmware 2.2.2.0.Why Sol-Ark 60K-3P-480V + Discover Energy Systems AES 210HV is listed this way
Compatibility basis
This published page binds the exact inverter Sol-Ark 60K-3P-480V to the exact battery model Discover Energy Systems AES 210HV. The current database resolution is CONDITIONAL under SOLARK_HV_BATTERY_INTEGRATION. 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
For this exact Pair, the database stores one source-supported communication path.
- CAN — Gateway LYNK II CAN, source-listed in TB-00029-REV2 (2025-10-14), page 21. This is a source-supported setup value, not an independently inferred recommendation.
Evidence coverage
The result is backed by 1 page-level evidence record on page 21 of TB-00029-REV2 (2025-10-14).
No extra wiring, DIP-switch, firmware, cable, charge-limit, or pinout claim is created from absence or analogy.
The source attaches 4 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.