DESS not taking max charge current into account

Q&A and troubleshooting DESS
,
1

Today I observed the following: As it is battery balancing day today I see big scheduled charge periods during the cheaper timeslots.

As shown by below picture, DESS forceast 11.12 kwH into the battery. However, i have set a max charge current of 150A to the batteries. This means It will pick up only 53V*150A is around 8kWh per hour.

Am I missing something it does DESS not take the max charge current into account when building the forecasts/schedules?

image
image1999×1186 218 KB

image
image2658×537 49.4 KB

2

Hi Marcel, as far as I know DESS only works/calculates based on the Dynamic ESS values in VRM! This means you need to match what your system can do (or what you limit it to do) in de settings on VRM.

3

:backhand_index_pointing_up:that…

1 Like
4

Hi cotje, makes sort of sense, but is confusing.

So now we have 3 levels of settings (for multiplus):

  • veconfig
  • cerbo
  • DESS

This is so 1970

5

You missed one. For DESS to actually work as advertised, you either need a SoC monkey (:monkey:) constantly overriding settings or external automation doing same.
(:monkey:) That’s me, you and everybody else until we figure out how to build that :monkey: as a Node-RED flow (to stick within the bounds of the supported platform).