My installation goes to passthrough ( random )

Q&A and troubleshooting
, , , ,
1

hi,

i have now 3 times on a month that my system goes to passthrough mode , without any notification / fault in the system , nothing to see on the VRM or on the cerbo GX …

the only thing i can do is , strange!!! =>> go to the VRM website and go to the device list => scan for fimware updates ,AND it resets and works perfect again …

is this a bug ? all are in the last firmware ( mppts - cerbo - all )

its a 3 phase multi-plus 2 system

Gateway , MultiPlus II 3x8K-HomeVE.Bus System, Lynx ShuntBattery Monitor [0], BMS 2100ahBattery Monitor [512], MPPT 1_ZuidSolar Charger [0], MPPT 2_NoordSolar Charger [1] , PV Inverter, KG-Home GridmeterGrid meter [0], Vijver Solar [L1]Grid meter [31], Temp Bat BovenTemperature sensor [24],Temp Bat OnderTemperature sensor [25],Temp InverterTemperature sensor [26],Temp ShuntTemperature sensor [27],EV-ChargerEV Charging Station

2

Maybe you have communication problems with your gridmeter? How is it connected to the system?

In my case scanning for new firmware resets the usb ports on the GX device or something like that for a short time. Then VRM reports a missing gridmeter in my system (connected via USB/RS485 adapter). And after a short time, it works again. During this time the multiplus is in passthrough mode.

3

Comm. Is via ve.can , but should i see an error if there is a comms loss?

Its not comming back to normal, i had it arround 4:00 until i saw it the next morning . That it was in that mode.

4

I had loss of communication with the VE-3p75ct via Ve.can while using a bad cable. I do not remember an alert in Venus OS or VRM.

After a certain time without energy meter, the MO2s are set to pass through automatically. I replaced it with a new one and the issues were gone.

5

Will try later with a new cable …the only “glitch” i could see is on the D-bus

Screenshot_20250915_064649_VRM
Screenshot_20250915_064649_VRM1080×2340 146 KB

6

Did this glitch cause a reboot by hardware watchdog ? On the other hand, such glitch could be caused by the reboot itself.

Check uptime and hard disk use:

root@einstein:/etc# cd ..
root@einstein:/# uptime
 06:35:01 up 36 days, 11:16,  load average: 2.38, 3.81, 3.59
root@einstein:/#  df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root              1194584   1058268     56336  95% /
devtmpfs                464832         0    464832   0% /dev
tmpfs                   514496       868    513628   0% /run
tmpfs                   514496       308    514188   0% /var/volatile
/dev/mmcblk1p5         1130880     91152    964056   9% /data
tmpfs                   514496       868    513628   0% /service
overlay                 514496       308    514188   0% /var/lib
root@einstein:/#
7

victron
victron616×163 48.4 KB

no reboot ,