Forced charging not charging at full power

[Tsopic]

Not sure what's wrong with this setup.

Maybe someone has ideas.

The last 2 images are added later when there is PV available already. But BMS max current was at the time of force charging also 80 A.

Also tried to set force charging by app command, did not increase the charging power. ( At the time of testing integration forced charging was also enabled in the integration)

The inverter has the latest firmware, not aware of how to update BYD battery firmware.

Have not tried A cold reboot yet. Adding an image of multi-hour forced charging stats:

It should be currently importing 10000w but it does only 1k.

Modbus connection: The dedicated Modbus port which is used with PI4 + the original port that lets the isolar app command the inverter.
Inverter: SH10RT
Battery: 2x byd b-box premium hvm 22.1

I am looking forward to any ideas for a solution, if anyone has some similar issues with forced charge.

[hacor]

Can you please share if you found a solution to this?

[Tsopic]

Not quite sure what exactly fixed this, but may have been hard restart for battery + inverter.

Turn everything off, keep it off for 3-5min and turn stuff back on.

I did modify some inverter params also, let me know if you wanna compare these vs latest settings

[hacor]

@Tsopic Thanks for the reply!

I already did a cold reboot of the complete system, but the problem persists. I'll try to describe my situation and problem more clearly: I have a SH10.0RT hybrid inverter with a Sungrow battery of 12.8kWh and I want to permanently control the charging/discharging power of the battery. Why:

• Avoid discharge to my EV
• Charge at cheap prices when no solar predicted
• Avoid high house peaks.

My software is running perfectly on Goodwe inverters, but Sungrow gives me strange behaviours. All settings are based on the modbus PDF 12/01/2023

What do I set:

• EMS mode 13050 => 3 (external EMS mode)
• Heartbeat 13080=> 20 (repeated every 9 seconds to keep EMS mode 3 alive)
• Charge/discharge 13051 => 170 (0xAA) = Charge
• Charge/discharge power 13052 => 2000 (The SH10.0RT needs a power value not a percentage)

What happens in this situation:
The inverter starts charging at 2000W (read battery power 13022) for about 1 seconds, than the power drops to 0 and after 3 seconds it gives me 2000W again for 1 second. In the meantime no fields were written in the inverter. This behaviour repeats all the time, which I think is not healthy for the device. It feels like some internal setting keeps it from charging

Good to knows:

• This does not happen on discharging the battery (13051 set to 187). In this case power field 13022 is perfectly stable
• Min Soc 13059 = 4%
• Max soc 13058 = 95%
• All fields seem good
• Export power limit is set to the inverter maximum (10kW)
• When I set it back to defaults:

{
    "ems_power": 0,
    "mode": 204,
    "ems_mode": 0
  }

The inverter starts back to solar charging in self-consumption mode, which works perfectly.

I really hope someone can help me out, because I'm really stuck here. It would be handy if someone else could try to write these registers manually and see if the inverter reacts the same way as mine

PS: do you guys have the sungrow energy meter connected or disconnected?

Thanks!
kind regards

Hacor

[Tsopic]

These are the parameters I'd look for in home assistant:

For limiting the power in forced mode currently works as intended for me. I Belive you can limit the consumption from battery there aswell.

I've experienced the weird Inverter issue aswell, to me it seems to sometimes fix the incorrect "charging power" at 0:00 for some reason, not sure, but probably some routine to sync the values between HA and Inverter.

[hacor]

Thanks! I'll give that a shot.

to me it seems to sometimes fix the incorrect "charging power" at 0:00 for some reason

What do you exactly mean with this? I didn't find any modbus fields for setting the forced charge time.

[Tsopic]

I mean that whenever I had this issue, where I had "forced dis/charge" set to 10k and it only did 3kw on force charge or the inverter did not act as its supposed to in "self-consumption mode" . The problem seemed to go away exactly at 0:00 midnight.

Sometimes before that, I had manually sent the instructions from "isolarcloud" and the issue only went away after midnight. I used to have an issue, where for some reason the system refused to self-consume from the battery.

I'm not quite sure what caused this strange behavior.

As you described earlier you use EV, I hope that you do control the EV electricity demand from the EV API, not the inverter... At this point, I do not have an EV, but heard some guys use gridio.io for EV charging timing.

[hacor]

Ah ok thanks! I'll give your tips a try.

Kind regards