Set on the Jk BMS +1V as the SI takes 1V off so JK is set to 56.2V and the SI takes that as 55.2V.
See post 40
I'm in the process of trying to integrate a Victron SmartShunt, ESP32, and Pylontech protocol using ESPHome. When I first got comms working, I noticed the missing 1V, and thought there must be some bug in my canbus code.
I wonder if SI is intentionally targeting a volt lower to account for big loads switching off when close to 100% SoC, to give itself some breathing room?
Edit: it's almost certainly what I mused about above. The "missing" volt comes back as soon as SI connect to the grid, and doesn't have to worry about sinking a bunch of AC-coupled power into a fully-charged battery.
I'm thinking it is for that reason.
If SI periodically goes on-grid, can charge to higher voltage and get balanced up there. If load-dump occurs, SB's output just gets shoved into grid.
Then when running off-grid at lower voltage, load-dump gets shoved into battery for a few seconds and battery remains balanced because it doesn't exceed balancing voltage.
If system happened to drop off grid at the moment battery got charged to highest voltage, only saving grace is that SB is usually knocked offline for 5 minutes. Any loads, at least idle consumption, would draw battery down a bit.
Other issue would be if always off-grid. Or with generator, don't know yet if this -1V adjustment occurs with generator or not. There is a reverse power watts and time setting.
Kommando - can you try digital input saying generator is connected? But I think you have to configure system for that, grid + generator. No harm, if generator never actually used? Or would SI then behave different, requesting generator at some SoC and hours?
If always off-grid, battery gets bulk voltage to the -1V level, then can float later. If charging at bulk and load-dump occurs, could have a runner cell and high voltage disconnect. If it has not recently (or ever) been balanced at a higher voltage, BMS might disconnect and shut system down.