Growatt Hybrid high voltage / Pylontech BMS high voltage (powercube x1) / CAN about bms-to-inverter HOT 103 OPEN

Thanks a lot for your good support too!

from bms-to-inverter.

Hi,
I solved the problem with the settings mentioned by Jens.
Thanks for for all your support.
BG Utz

from bms-to-inverter.

Hi,
yes, I'm sure I can support this. As far as I know, the Growatt inverters use the Pylontech CAN specification.
But if you could get the CAN specifications from the manufacturers then I can tell for sure or - if it differs - implement the module in a couple of days.

from bms-to-inverter.

Hi,
thanks for your quick reply. I attached the high voltage protocol and some other files for this setup (Growatt SPH Hybrid (HV) series and the Pylontech HV BMS system (powercube X1)) . It`s very hard to get the Growatt can bus protocol from the manufacturer. Maybe it will help you.
Many thanks for your support.
Best regads Utz
pylon_CAN_210124.txt
CAN-Bus-Protocol-Sermatec-high-voltage-V1.1810kW (1).pdf
PYLONTECH.zip

from bms-to-inverter.

Ok, I will have a look at it possibly this week.
The file CAN-Bus-Protocol-Sermatec-high-voltage-V1.1810kW (1).pdf is the protocol for your Pylontech HV BMS, correct?

from bms-to-inverter.

Hi Torsten,

yes it is. I have attached a document regarding the growatt Can Bus.
Best regards / Utz
Growatt-Battery-BMS.docx

from bms-to-inverter.

Thanks for the sponsoring! :)

I have implemented an initial version of the Pylontech HV BMS support.
Could you test it to see if we get some proper readings?

The specs are a little unclear defining the response CAN ID.
The official spec quotes:

Host device sending data with byte 0 set to 0
CAN ID：0x4200 (this is Broadcast Frame) 

Response:
CAN ID：0x4210+Addr (Addr. = 1~F) (Equipment Address: Addr.= 1~F, MAX 15 equipments can be parallel communicated.)
CAN ID：0x4220+Addr (Addr. = 1~F) (Equipment Address: Addr.= 1~F, MAX 15 equipments can be parallel communicated.)
...

So I would assume that the respone CAN ID would look something like 0x4211 .. 0x421F (=Battery packs 1-15).

But int the other document you provided it seems that the address starts with 0 (=Battery pack 1):

Host device sending data with byte 0 set to 0:
can1 00004200 [8] 00 00 00 00 00 00 00 00 

Response:
can1 00004210 [8] A5 09 30 75 9D 04 2E 64
can1 00004220 [8] 8C 0A E9 07 4A 79 4A 79
...

Well, we will see that in the logs when we get some readings from you BMS.
If you need help with the setup of the application - just ask :)

from bms-to-inverter.

Hi Torsten,

thanks for your great support.
I will testing in the next days. Replay comes.

Have nice (rest)weekend.

Best regards Utz

from bms-to-inverter.

Ok. Be sure to connect CAN H and CAN L correctly of your Powercube X1 to the PI hat.
This is what I found in the Operation Manual for the Powercube X1:

So you need to cut a RJ45 network cable (min. CAT 5) and connect pin 4 (CANH) to CANH and pin 5 (CANL) to the CANL on your PI's CAN hat.

Let me know if you have any questions!

from bms-to-inverter.

Hi, thx.
Currently I have a problem, I can only select the daly bms, no any other inverter bms and only "none" inverter brand. I installed the configurator on a pi 4 with JDK, do you have an idea what is the problem?

Thanks. best regrds Utz

from bms-to-inverter.

64-bit, newest PI firmware (bookworm)

from bms-to-inverter.

Hi,
I solved the problem, but I can't select the bm pylontech hv protocol, only pylontech_can, see png attached

Thx. for your support.
BG / Utz

from bms-to-inverter.

Let me check....
Ok - I fixed it. The Configurator was missing the service descriptors for the BMSes and inverters.
Please download the new current Configurator.

from bms-to-inverter.

merci, I will testing this week and come back with results.
Bg / Utz

from bms-to-inverter.

Hi Tosrten,

I tested, see the result in the attached jpeg. Pls. can you help me?
Thx. BG Utz

from bms-to-inverter.

Hi Utz,
so far so good, but does it stop after the last log entry?
Is your BMS connected to can1 or can0?
Please configure the Dummy inverter for now, so we can test if we get any readings from the BMS.
Also configure the log level to debug in the * latest * Configurator please. You can do this by simply choosing your installation folder in the Configurator app, change the settings and click Update configuration or Clean install (if you like to get the latest version with bugfixes).
In the future please just attach the log file found in <installation directory>/logs folder. That's easier to read ;)

from bms-to-inverter.

Hi Torsten,
I tested, pls. see the attached log. The converter display said "bms com failed". The pylon BMS show no errors on the leds.
I think its not a great problem :-)
Thx. for your support.
BG / Utz
BMS-to-Inverter.log

from bms-to-inverter.

Hi Utz,
good, looks like the BMS is responding properly to the request. But something is not right possibly with the configuration.
Could you please attach your config.properties file from the config folder.

from bms-to-inverter.

Hi,
Subscibed to this.
Having the same growatt HV inverter (SPH 5000TL3 BH-UP).
I have the Pylontech Force H1 battery. But I'm guessing I also could use the pylontech_hv_can module.
Attached my config and log file.

config.txt
BMS-to-Inverter.log

from bms-to-inverter.

Hi Torsten,
in the attachment you find my configuration properties.
Thanks for analysing.
BG Utz
config.txt

from bms-to-inverter.

Hi Utz & Jens,
please update your installation (Clean install in the Configurator).
I've fixed the problem with the exception so you should get some proper readings now. I've tested it on my PI giving it simulated data for the SOC, current and voltage readings. The best I can do since I don't have the components to test on :)

@jenshermans Please reduce your configuration to a minimum for now (see Utz's config) until we get decent data from the BMSes

from bms-to-inverter.

Hi,
Did a clean install, copied the config file from Utz and this is my log file;
BMS-to-Inverter.log

from bms-to-inverter.

Hi Torsten,
here is my clean configuration log file. Now I have some values from the hv pylontechs... , but still errors. The inverter does not recognise the bms.
Thx. BG Utz
BMS-to-Inverter.txt
config.txt

from bms-to-inverter.

Hi Utz & Jens,
ok, that's great. We're getting proper readings from the BMS now. I can go forward implementing the rest of the HV protocol and will hopefully finish that today.
Could you please try to configure the SolArk inverter (which also uses the Pylontech CAN communcation) and set your Inverter's communication protocol to Pylontech. I've googled and read that you need to choose 5 in the menu and then select L2. But consult your manual for the correct setting.

@jenshermans please configure the log level to debug for now

from bms-to-inverter.

Hi Torsten,
I'v added my current log on debug level, Doubting it's an other Pylontech HV protocol...
For the growatt inverter; I can't set any protocols on my SPH, even on installer level.
BMS-to-Inverter.log

from bms-to-inverter.

Hi,
thanks for the log.
Could you check which protocols or batteries your inverter supports (maybe in the manual or website)?
Maybe you could also ask Growatt to send you a list of supported batteries or even better their CAN protocol ;)
What I've found was that that they support(ed?) the Pylontech protocol, so the SolArk should work:

Have you connected the right pins from CAN hat to inverter to your can1 port?

Please update (Clean install) the application. I did manage to find some time to get more readings from the inverter and also fix the exception in the SolArk processor.

from bms-to-inverter.

Hi Torsten,

that's tricky, Growatt supported the Pylontech Powercube X1 when the SPH bh-up inverter series was launched. Growatt has not officially supported the memory for some time now. But it still works. A friend is running this setup with the Pylontech CAN protocol 1.18 (see above). I think I read somewhere that Growatt uses the CAN bus protocol 1.01 (that's not open) for the high-voltage series. I have the firmware of the inverter as a zip file. I can attache if you need it.
I'll check the SolArk settings again today.
BG / Utz

from bms-to-inverter.

Hi,
I tested three ways: Growatt-Pylon, SolArk-HVPylon, SolArk-Pylon. Logs attached.
Bg / Utz
BMS-to-Inverter-Growatt-Pylon.log
BMS-to-Inverter-SolArk-HVPylon.log
BMS-to-Inverter-SolArk-Pylon.log

from bms-to-inverter.

Hi,

I'm receiving packages from my growatt inverter, uploaded my candump. maybe this could help you a little forward.
Alsof tried the (new) configuration with pylonHV-Growatt and PylonHV-SolArk, logfiles are also added as attachment.
Also found this similar project documents regarding
the Growatt inverter. (jk-bms); https://drive.google.com/drive/folders/1YP-UwRgFRqus0CKmYnccU79ZlMlZN57e

candump.log
PylonHV_Growatt.log
PylonHV_Solark.log

Edit; After sending "cansend can0 00004200#0000000000000000" to my Pylon i get the following respond.
candump can0.log

from bms-to-inverter.

Hi,
thanks for all your input!
I've made a few adjustments, so it should also be no problem for @jenshermans since it looks like you have more than one BMS.
Also I fixed the sending of data to the inverter.
Thanks to the CAN dumps I could see that the inverter is using the Pylon HV CAN specification and not the Pylon LV CAN specification (SolArk, etc.).
That means I need to implement a new inverter binding (PYLON_HV_CAN) which I am working on now.
I've done an initial version sending basic data to the inverter.

Please update (Clean install) and choose the PYLON_HV_CAN as inverter.

from bms-to-inverter.

Here is a link with the protocol information for low an high voltage
https://www.amosplanet.org/how-to-commission-the-communication-between-lithium-ion-battery-and-spf-3500-5000es/

https://www.amosplanet.org/wp-content/uploads/2022/04/Growatt_BMS_RS485_protocal_1xSxxP_ESS_V2.02-1.pdf

https://www.amosplanet.org/wp-content/uploads/2022/04/Growatt-BMS-CAN-Bus-protocol-low-voltage-V1.04-1.pdf

from bms-to-inverter.

Hi
I fixed the missing dependency for the Pylontech HV inverter now. Please pulll the latest Configurator and do a clean install.

from bms-to-inverter.

Hey Torsten,
Downloaded the new files, and the configurator wont open anymore. Last working commit is 'bcbf2ac'.

configurator.log

from bms-to-inverter.

Sorry, my bad! Shouldn't do this stuff at 11pm ;)

Fixed the service descriptors - now its working.
Please get the new Configurator and do a Clean install.

from bms-to-inverter.

Added the current log.
I hear the BMS relay clicking, and the status led turned blue, so he goes out of error mode.
On the inverter i now get 'batt voltage high'.

my config is:
-bms: pylon_hv_can
-inverter: pylon_hv_can
BMS-to-Inverter.log

added candumps
candump can0.log
candump can1.log

from bms-to-inverter.

Hi Jens & Utz,
I just committed a full implementation of the Pylontech HV inverter module (also corrected some value units).
Could you please test? Thanks!

from bms-to-inverter.

Hi Torsten,
I will testing tomorrow. Currently I am two Day outside from my home.
Thanx for your great work and support.
BG Utz

from bms-to-inverter.

No problem, just fixed another bug anyway (probably not the last) ;)

from bms-to-inverter.

BMS reading looks right. Inverter now shows 'bat voltage high' at first,'bms com fault' afterwards.

BMS-to-Inverter.log
candump bms.log
candump inverter.log

from bms-to-inverter.

Hi Jens,
I fixed some wrong units. Hopefully that will solve the 'bat voltage high'.
Can you please test the latest version?

from bms-to-inverter.

Current logs attached, Inverter still shows bat voltage high, bms com fault
BMS-to-Inverter.log

from bms-to-inverter.

Hi Jens,
I'm a little bit confused about your battery configuration.
When I send a broadcast to all battery modules I only receive answers from Battery No. 2 (e.g. 0x4211) but not from Battery No. 1 (e.g. 0x4210). Last digit identifies the battery module.

On Utz's battery I get the correct Battery No. 1 (e.g. 0x4210) when doing the broadcast.
Could it be that you need to change the DIP switch on your BMS or Battery module to correct the identifer?

When the inverter starts a broadcast to request the BMS data, I now send data from all BMS.

So I updated some code for more info. Maybe you can update and run it again?

from bms-to-inverter.

Hi Torsten,
I tested, the inverter display dispatch BMS Abnormal, BMS Com fault. Can you provide me with the version that worked for Jens until the inverter/bms stopped using bms com fault, bat voltage high? The Powercube BMS schows a red error light.
Thx.
BG/Utz
BMS-to-Inverter.log

from bms-to-inverter.

Hi Torsten,
It's not possible to change my BMS address, this addresses itself. Its only possible to change bitrate and some "special protocols"
For this current version; Battery is okay and the inverter is showing the first 5 seconds "normal", after that it shows 'BMS com fault' and 'Normal' varying.
But i noticed; the first 5 seconds, (while normal) the SOC is displaying like it should be, after that it disappears.

Did a candump on can0 and can1 (starting from timestamp 2024-02-23 17:36:07.064 in the bms-to-inverter log)

BMS-to-Inverter.log
candump can0 bms.log
candump can1 inv.log

from bms-to-inverter.

Hi Utz,
can you please update to the latest version. You seem to not get any responses from your BMS. Please also check that your CAN device is properly connected and that the BMS is not idle.

from bms-to-inverter.

Hi Jens,
from the candump can1 (inverter) I can see that everything gets sent to the inverter initially. Then 5 seconds between the sending of the invalid data of 0x4210 and then the valid data 0x4211, etc.

I have fixed that temporarily ignoring the battery for which I don't get data (0x4210 in your case). That should hopefully fix the problem that the inverter switches from normal to error mode.

But I've added a ToDo to manually configure the BMS id for the future.

from bms-to-inverter.

Hi Torsten,

I'm still getting the bms com error on the inverter, in the logs you also will see 'error communicating to inverter'.
BMS-to-Inverter.log

from bms-to-inverter.

Hi Jens,
I fixed the exception when sending of the manufacturer.

from bms-to-inverter.

Still receiving the 'normal/bms com error' status
added a candump of the inverter to attachments.
BMS-to-Inverter.log
candump-inv.log

from bms-to-inverter.

hmm, can you access the inverter's log. Maybe there a more detailed error message

from bms-to-inverter.

Hope I can help you with this? (via oss.growatt.com)
Schermafbeelding 2024-02-24 082850

from bms-to-inverter.

Ok, can you tell me your inverter settings for the maximum voltage limit?

from bms-to-inverter.

As the manual describes, battery voltage range is 100-550vdc.

Running your program unlocks my BMS. So I configured the inverter with lead acid battery and its correct charging current/voltage, and load current/voltage. This works fine.

On lithium mode i cant configure anything as all data comes from the BMS.
I noticed something (don't know if this is the problem) Max charging/discharging current is 25A, bms reports via CAN max charge/discharge 37A

image

from bms-to-inverter.

Hi,
@jenshermans I don't think that the max dis-/charge values are a problem. Your inverter can charge or discharge with a max of 25A, but the BMS can handle 37A. So your inverter pushes or pulls with a max of 25A, so you're way on the safe side there.

IMPORTANT:
I updated the Configurator to allow setting a BMS Id. Also I changed the poll intervall to be a general BMS configuration (not for each).

You will need to download the new Configurator and re-configure your setup and do a clean install.

@solsrvolt you need to set the BMS Id to 0 (zero)
@jenshermans you need to set the BMS Id to 1

from bms-to-inverter.

I also fixed the reading of the module voltages. It was the wrong data type (s_int_16 instead of u_int_16).
I wish they would state that in the specification ;) :) :)
They reported -15.608V. I fixed that so now its 49.950V so ~50V for a module.

from bms-to-inverter.

Still receiving the BMS com error. Also added my BMS's data this time. maybe this also can help you.
BMS-to-Inverter.log

Screenshot_20240225-055800

from bms-to-inverter.

Thanks @jenshermans. Your screenshot of the inverter values helps. I'm trying to make sense of the CAN messages we receive but which are not documented like:
0x3010 - looks like a heartbeat
0x8211 - might be the relay status (0xAA - for ON)
0x41B1 - looks like it contains the pack voltage (147.3V) and SOC (55%) & SOH (100%) again (maybe we need to send this too)
0x41C1 - ?
0x41D1 - ?
0x41E1- looks like the max/min voltage of module 49.10V (#1) and 49.11V (#0)

As I said they're not documented, so these are my best bets.
Maybe there's the cause.

from bms-to-inverter.

Hey Thorsten,

Please note previous screenshot was from my BMS, it has a WiFi module in-built to read this data.

Added a screenshot of the inverter data.

Can't read any data from the installer app because there is "no BMC connected"

Also added a picture of the BMS specs. I noticed that growatt wants to display the SN of the battery. Don't know if you send this already, but looks like it could be needed.

from bms-to-inverter.

Added error logs from the growatt app, it refers to specific bytes

from bms-to-inverter.

@jenshermans I've added sending the 0x42B0 message

What is the baudrate you set for your can1 device to the inverter?
e.g.

sudo ip link set can1 type can bitrate 500000 restart-ms 100 fd off

from bms-to-inverter.

Running my inverter and BMS at 500kbps
My can startup commands;

sudo ip link set can0 up type can bitrate 500000
sudo ip link set can1 up type can bitrate 500000

from bms-to-inverter.

That should be ok then.

from bms-to-inverter.

Could you please update (clean install). I've changed the inverter binding, so that it will send the messages to the inverter always as 0x42x0 (like 0x4210) instead of 0x42xx (like 0x4211). Let's see if Growatt will accept these.

from bms-to-inverter.

current log, there is an error communicating to the inverter
BMS-to-Inverter.log

from bms-to-inverter.

You're can1 is not connected or needs to be reset:

sudo ip link set can1 down
sudo ip link set can1 up type can bitrate 500000

from bms-to-inverter.

Correct. ifconfig was showing still online weird.

Looks like it's working, inverter showing normal status and reports correct SOC/Voltage
BMS-to-Inverter.log

from bms-to-inverter.

Wow! Great!!! Awesome!

Still don't know why your BMS sends the 0x421x, etc. messages. If you would have two or more packs that would be understandable. Musst be some internal preconfigured switch....
I'll need to restructure some code to compensate for this in the future.

@solsrvolt Can you confirm that its working for you too?

from bms-to-inverter.

@jenshermans Please monitor it for a day or so that everything works as expected. And if you are happy with my work and support please feel free to sponsor me ;)

from bms-to-inverter.

I completely dont have any idea... I can only change the rs485 bitrate and some special protocols, but you have to contact Pylontech for these settings.. BMS addressing goes automatically when plugging in the link cables...

You can tag me to test your code out when needed.

Surely going to sponsor you! You made me a happy man, haha!
Thanks for all your work.

from bms-to-inverter.

Oh, and don't forget to turn down the log-level to info or warning when you finished monitoring. Feel free to open an issue if something is not working properly.

And many thanks for sponsoring this project!

from bms-to-inverter.

Hi Torsten,
a quick response, today I started the new configurator file, it seems that it works good withe power cube X1. Great work, I will checking for the next days and going to sponsor you. Top.
Bg/ Utz

from bms-to-inverter.

Excellent! Very pleased to hear that :)
Just get back to me if you have any issues or need support.
Sponsors are always very welcome ;)

from bms-to-inverter.

Hi Torsten,
I have now been able to test the converter extensively.
There is still a small bug: if the batteries are charged by the sun, but the sun is not sufficient for heavy current loads (e.g. cooker), the battery does not supply the missing current to the house grid. I believe that this fault can be rectified quickly.
@jenshermans, do you have the same problem?
Thanks to all, for support.
BG/Utz

from bms-to-inverter.

Hi Utz,
but that sounds like a configuration on your inverter to use e.g. battery first over the utility grid.
I'm not sure there's anything I can do from my side. There's no BMS command to tell the inverter where to draw its power from (wouldn't make any sense either).
The only other thing I could think of would be the maximum discharge current (Amps) set in the BMS.
But maybe @jenshermans has an idea or observation?

from bms-to-inverter.

Hi,
I also noticed this but like Torsten is saying, probably nothing he can do.
How I solved this problem is limiting my max charging SOC; configuring to 98 seems to work for me.
Also set your discharging soc to 10% or something like that. Because when you want to charge you get te same effect (if you had'nt noticed already).

Probably your battery priority is set right, because else it won't take any watt from your battery.

from bms-to-inverter.

Hi Torsten,
thanks again for the converter. I have been using the converter since March. It works great.
However, I have noticed one small thing, at night when the house consumption is fed from the battery, the battery always supplies on average 200 watts more power than the house needs in terms of load. The surplus power from the battery is fed into the public power grid and causes the battery to discharge more quickly. Example: House load = 250 watts, battery supplies 450 watts, the difference of 200 watts is fed into the public electricity grid.
Is it possible to reduce this value to approx. 30 - 50 watts (possibly dropdown field ) or as a fixed value?
Many thanks to your support.
BG / Utz

from bms-to-inverter.

Hi Utz,
I guess you need to configure that directly on the inverter as there is no commands to steer that via the CAN messages.
Just check the manual of your inverter for the correct setting.

Best regards,
Torsten

from bms-to-inverter.

Hi,
I checked this and its there is indeed an continuous export (140-150watts)

My latest build without the export current was on 25/02, this is the one showing all BMS's

Logfile of latest version (downloaded today), this one is also exporting current.
BMS-to-Inverter.log

from bms-to-inverter.

Hi Jens,
there is nothing I can do from my side to control the inverter to not export to the grid or to set a threshold when to export. That must be done in the inverter's configuration itself. Maybe there was an update of the inverter's firmware that's causing this?

from bms-to-inverter.

Hi,
I used the version of 25/02 and working without any (export) issue from my previous post till now. so i'm thinking it's not on the inverter side.. Maybe a calculation error when selecting the right BMS?
I'm guessing it would be amps, the difference is more or less -1A.

I think the BMS sends a feedback of its amps to the inverter, and the inverter is trying to correct this but without success

from bms-to-inverter.

from bms-to-inverter.

Hi, I used the version of 25/02 and working without any (export) issue from my previous post till now. so i'm thinking it's not on the inverter side.. Maybe a calculation error when selecting the right BMS? I'm guessing it would be amps, the difference is more or less -1A.

I think the BMS sends a feedback of its amps to the inverter, and the inverter is trying to correct this but without success

Hi Jens, do you have other configurator versions after the version from 25.02. and the latest? Can you provide me with this version. I will test ist. Thanks. BG Utz

from bms-to-inverter.

I checked the log and the implementation, but it sends the correct amps (0.0A) which is reported by the BMS to the inverter.
Did you check if the firmware of the inverter was updated (maybe automatically) and maybe some ratio setting for the grid export has changed?

from bms-to-inverter.

These are all the versions i have, tested all of them.
All config files are configured the same. no inverter settings where changed during this test

25/02 1:
reading all BMS, no SOC to inverter
BMS-to-Inverter 25-02-1.log

25/02 2:
Reading all BMS, Posting SOC to inverter, drawing correct current from battery
BMS-to-Inverter 25-02-2.log

26/02 1
Error
BMS-to-Inverter 26-02-1.log

26/02 2
Reading all BMS, Posting SOC to inverter, drawing correct current from battery
BMS-to-Inverter-26-02-2.log

27/02 1
Reading one BMS, Posting SOC to inverter, exporting 140-150w
BMS-to-Inverter 27-02-1.log

from bms-to-inverter.

Ok, thanks Jens.

I will check through the commits from 26.02. to 27.02. and see if I can find anything.

from bms-to-inverter.

@jenshermans I have committed a change about the forbidden charge/discharge flags that were changed in the commit from 26.04. but I'm not sure if that has any effect on your inverter.
Could you try this please?

from bms-to-inverter.

@torsten, the inverter display BMS Abnormal, see log attached
30.04.2024_BMS-to-Inverter.log

from bms-to-inverter.

I fixed it, but still implementing a fix for the webserver too. I should be finished with that later on in the day :)

from bms-to-inverter.

Hi torsten,
Tested current version. Looks like it's not drawing any power because it reports a lot of bms alarms I guess.
BMS-to-Inverter-01-05-1.log

from bms-to-inverter.

Hi @solsrvolt and @jenshermans,
could you please test the new version. I fixed the alarms and also corrected the forbidden dis-/charge flags.

from bms-to-inverter.

Hi Torsten,
It doesnt draw any current from the battery
BMS-to-Inverter-01-05-2.log

from bms-to-inverter.

hmm, I reverted the change with the forbidden flags please test again

from bms-to-inverter.

Hi Torsten, it works but the same, a continious export (170-200 Watt) to the grid. I didn`t change anything in the settings from the inverter. BG Utz
01.05.2024-BMS-to-Inverter.log

from bms-to-inverter.

Hmm, so it wasn't those flags - didn't think so. The only other thing that changed was that the values are aggregated, but with only 1 BMS it doesn't have any averages, etc.
The other thing we changed was from separately requesting the values to requesting the values all at once. But the values are the same and not different. I will compare the logs again and see if I find any difference in the 26.2. and 27.2. logs

from bms-to-inverter.

Hi, thx. BG / Utz

from bms-to-inverter.

Hi Torsten, I noticed, that the battery don`t stopp with charching. At 99% charching, the battery permanently export 100 Watt to the grid.

from bms-to-inverter.