You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder whether how to display the information for each module? It must be possible as the SolarEdge support can access such data.
Any ideas on which registers this information is written? Would be great to have this.
Thanks,
Milko
The text was updated successfully, but these errors were encountered:
milkotodorov
changed the title
Support for Module based SolarEdge Home Battery 48V
Module based information for SolarEdge Home Battery 48V
Oct 30, 2023
As far as I understand, you have two modules (BAT-05K48) combined to one battery (9,2kWh).
It's possible to interconnect up to five modules, but only the first module is connected to the inverter.
Therefore, only one set of SunSpec-Battery-Registers is generated and readable (the combined battery).
How did the SE-support access the data? Using the SE Set App? Maybe there is more data available this way...
Another question:
Issue #81 is open yet.
The Home Battery is DC-coupled.
I_DC-Power (register 40100 and ScaleFactor 40101) is the pure generated PV-power, correct?
This power has to be combined (=added to the) with Battery_n_instantaneous_power (register 57716 (0xE174) - negative values charge, positive discharge), to get the inverter DC input power?
I_AC_Power (40083/40084) represent the inverter output power?
A meter between home and grid measures import/export, using M_AC_Power (40206/40210) and I_AC_Power I'm able to calculate home consumption?
Hello,
currently one can see the information for SolarEdge Home Battery 48V as a whole. Example - I have 9.2 kWh battery with 2x 4.6 kWh modules:
I wonder whether how to display the information for each module? It must be possible as the SolarEdge support can access such data.
Any ideas on which registers this information is written? Would be great to have this.
Thanks,
Milko
The text was updated successfully, but these errors were encountered: