After reboot, VenusOS v3.60~69 doesn't detect MultiPlus-II system if it is in (software) shutdown

Hello @mpvader, I have an interesting bug for you.
But also some good news :slight_smile:
After upgrading my CerboGX MK2 from v3.55 to v3.60~69, my Wifi and CAN2 seem to be working perfectly.

Less good news: my freshly booted v3.60~69 CerboGX MK2 does not detect my MultiPlus-II system if the latter is in soft shutdown.
When just upgrading/rebooting the Cerbo, all is fine.
Turning off my Multiplus (from within Remote Console) and turning it on again in the same way also works flawlessly.

To reproduce the bug:

  • shut down MultiPlus from Remote Console
  • reboot CerboGX
  • MultiPlus is no longer detected
  • To turn the Multi back on again: reboot to v3.55, Multi gets detected, turn it back on in Remote Console.

noted, we’ll look into this - thanks

1 Like

Maybe against better judgement I updated this system from v3.60~69 to v3.60~74 and unfortunately the problem still persists.

If the GX (Cerbo MK2 in this case) is rebooted while the Multiplus system (3x MP2 5kVA in triphase setup) is in “software shutdown” mode, there’s a high chance that upon reboot the GX will not detect the Multi system.
Rebooting the GX with Node Red disabled didn’t seem to have much effect this time - I had to reboot my GX ~3-4 times before the Multis were properly detected.

Third line support is aware of the issue and is working on a fix.

Apparently it’s related to the VE.Bus being a lot calmer when the Multis are in (software) shutdown mode, resulting in the GX having trouble to properly detect them / put their info on the dbus.

OK, Victron L3 support was able to locate and fix the bug with v3.60~79 !
After installing this version on the system where I initially discovered the bug, the problem instantly disappeared.

As a comparison test, I upgraded another 3 phase system (with original Multiplus inverters instead of the -II version) to v3.60~78 and it immediately triggered the bug.
Upgraded that system to v3.60~79 and the bug was gone.

From the info I got it seems that this bug impacted almost exclusively the systems with multiple Multiplus devices on the VE Bus.

Anyway, from the looks of it it seems like the bug has been squashed !
*tips hat to Victron L3 support*

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.