Disconnect behaviour

[maxx8888]

Hi,

I was wondering what would happen in case there is a Communication fault to the BMS for some Reason.
BMS could be damaged, USB Cable unplugged, Serial Converter dead or stuc, etc...

Shouldn't Multiplus stop Charging/Discharging as quick as possible?
It seems like the last received Value get's stuck and Multiplus just holds that value.

[mr-manuel]

The default Victron behaviour would be that it switches to the next available battery monitor or am I wrong?

[mr-manuel]

When BMS is connected:

When I unplug the USB:

[maxx8888]

Strange, that would be perfect, but not happening for me.
Without reboot in-between?
Are you running on the nightly build?
Maybe I should try that one…

[mr-manuel]

I tried Venus OS 2.93 and 3.00~32. Maybe it's 2.94 related. You can boot your old version by goint to Venus OS GUI -> Settings -> Firmware -> Stored backup firmware -> Selecting the older version. If this is not chaning anything you can boot again the new version, by following the same steps.

I found notes for 2.94:

DVCC:

• Fix bug where data from the battery could get stuck/freeze until GX devices was rebooted. We've seen this happen in a handful of support cases; and it related to certain timing in the canbus messages. Once properly tested, we might release an interim official version v2.94 that includes this fix soon.
  Source: https://community.victronenergy.com/questions/196394/venus-os-v30029-available-for-beta-testing.html

[mr-manuel]

I upgraded to 2.94 and it works also there for me. Try the nightly and if that do not work reinstall Venus OS from scratch.

[maxx8888]

Perfect!!!!

I've upgraded today to the nigthly and it works.
Detects RS485 disconnects with an Alarm and shuts off after a few seconds.
Detects USB disconnect and shuts off immidiatly.

Thanks :)

[rperpe]

I'd prefere to continue discharging in ESS mode when BMS data isn't available anymore since BMS data is expendable in this case from my point of view.

Is this achievable somehow?

[mr-manuel]

dbus-serialbattery/etc/dbus-serialbattery/config.default.ini

Lines 21 to 27 in 88e5eea

	; --------- BMS disconnect behaviour ---------
	; Description: Block charge and discharge when the communication to the BMS is lost. If you are removing the
	; BMS on purpose, then you have to restart the driver/system to reset the block.
	; False: Charge and discharge is not blocked on BMS communication loss
	; True: Charge and discharge is blocked on BMS communication loss, it's unblocked when connection is established
	; again or the driver/system is restarted
	BLOCK_ON_DISCONNECT = False