My Multiplus II GX keeps on rebooting itself multiple times a day and sometimes it loses connection to the MPPT RS on reboot. When this happens, I have to do a manual reboot for the MPPT RS to be found again.
I have a Multiplus II GX connected via VE.Direct to an MPPT RS, and via BMS-CAN to a BYD BMU. I have v500 firmware and v2.92 Large installed on the MPII GX. The MPPT RS has v1.10. The BMU contains the latest firmware from BYD. The MPII GX has an ethernet connection and comms testing has confirmed that this is a reliable connection
The system has been very stable for 18 months until October when it failed twice. This month it is failing every day (only during daylight hours) and, I suspect, when a state transition is happening (e.g. below Active SoC to above Active SoC).
I initally thought that it might be an intermittent cable issue however both cables have been removed and replaced and the system has immediately recovered. The connections are sound and no comms errors have been reported.
I have done some initial diagnosis and have captured the relevant /data/log/messages.
The symptoms are as follows:
- Rebooted on 16 December at 11:44, 11:48, 11:52, 11:57, 12:00, 12:06.
- Each time, the VE.Bus state changed from Ext Control to Bulk (although this may be a symptom rather than the cause). At the 12:00 reboot, the MMPT RS went offline and didn't come back. This meant the batteries stopped being charged as the MPPT RS had no data from the BYD BMU.
- I noticed the MPPT RS was offline at 13:09 and manually rebooted the MultiPlus II GX. It reported that the connection to the BMS was lost but this is an artefact of the main problem.
- The MultiPlus II GX then rebooted itself at 13:44, 13:48, 13:51 and 13:58. This time the MPPT didn't go offline. However, notice the times - exactly two hours after the previous reboots. I suspect a firmware issue.
Looking at the messages logs it seems that every time the MPII GX rebooted, there was a period of time (1-2 minutes) where nothing was added to the logs. So nothing obvious although the preceeding messages contain a lot of ipv6 related details.
I have logs that I can provide to Victron support and am more than willing to open up the remote access.