Victron BMS CAN-Bus issues with 48100R-C after 1.5.28.C16 update
I have two Pytes E-Box 48100R-C16 from 2024 powering a Victron Multiplus II GX 3000/48/35, more precisely:
Device name : E-BOX-48100R-C
Board version : SQBMSV15
Main Soft version : SPBMS16SRPV1.5.28.C16
Iterate version : SPBMS16SRPV1.5.28.C16.T5
Soft version : V28.3
Boot version : V1.14
Comm version : V2.0
They have been running ok for many months but I decided to update their firmware from 1.5.26.C16 to 1.5.28.C16, hoping for some improvements.
The update (with the Multiplus powered down of course) went fine, master got updated and sent the update to slave which also got updated without issues, but afterwards the Multiplus did not receive Charge/Discharge History anymore (= the totals of kWh charged/discharged energy).
Additionally, the reported available Ah was zero, despite of a SoC reported as 72%.
Fully charging the batteries to 100% did not help.
Re-installing the firmware update did not help.
Deleting history and events via datac did not help.
Updating the Multiplus to latest firmware from 510 to 556 did not help.
GX Venus OS is already latest version 3.64
But then I found out that this is all related to only one of the two batteries.
If I connect only a single battery to the Multiplus (daisy chain cable removed, power cables to other battery disconnected), the data is being reported correctly again, but this is only true for the previous slave battery, not the master battery.
And more interesting: if I make the previous slave battery the new master battery with the strangely behaving previous master battery becoming slave, everything works as expected too, i.e. it will report the correct sum of available Ah from both batteries and also the correct sum of charged/discharged kWh history.
In summary:
Battery1=Master, Battery2=Slave: not sending charge/discharge history and available Ah is always reported as zero
Battery1 standalone: not sending charge/discharge history and available Ah is always reported as zero
Battery2 standalone: all fine
Battery2=Master, Battery1=Slave: all fine
=> is there a newer firmware than 1.5.28.C16 were this got fixed? Or should I better revert to 1.5.26.C16?
If you need more details from serial console, just ask.
- 0 Replies
Sorry, there were no replies found.
Log in to reply.
