Multi HS19 Solar 15k + Cegasa E/Scal 6: compatible with conditions
The source supports this combination only under stated conditions.
Communication & inverter setup
- BMS connection
- BMS-Can to GX device
- Evidence
- 2026-06-23, page 1
Conditions attached to this Pair
75-86
BMS-Can/CAN to GX strongly recommended
13-15
TESTED_RUNNING_IN_FIELD_TESTS
676-940
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
Cegasa | E/Scal 6 | voltage=676-940 V | modules=13-15 | capacity=75-86 kWh | test_status=TESTED_RUNNING_IN_FIELD_TESTSWhy Multi HS19 Solar 15k + Cegasa E/Scal 6 is listed this way
Compatibility basis
This published page binds the exact inverter Multi HS19 Solar 15k to the exact battery model Cegasa E/Scal 6. The current database resolution is CONDITIONAL under VICTRON_HV_BATTERY_COMPATIBILITY. 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 — BMS connection BMS-Can to GX device, source-listed in 2026-06-23 (2026-06-23), page 1. 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 1 of 2026-06-23 (2026-06-23).
No extra wiring, DIP-switch, firmware, cable, charge-limit, or pinout claim is created from absence or analogy.
The source attaches 5 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.