GEN2-LB-EU 4K + LuxpowerTek PGEM PRO: 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
- Battery protocol
- CAN battery code 6
- Evidence
- EU_COMPAT, page 1
Conditions attached to this Pair
6
European reference list
CAN
40-60 V
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
GEN2-LB-EU 4K is an exact member of the GEN/GEN2 3-6K family; EU list names PGEM PRO with the family; CAN battery code 6.Why GEN2-LB-EU 4K + LuxpowerTek PGEM PRO is listed this way
Compatibility basis
This published page binds the exact inverter GEN2-LB-EU 4K to the exact battery model LuxpowerTek PGEM PRO. The current database resolution is CONDITIONAL under LUXPOWER_EU_BATTERY_COMPAT_20260727. 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 — Battery protocol CAN battery code 6, source-listed in EU_COMPAT (2026-07-27), 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 EU_COMPAT (2026-07-27).
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.