The installation is back on track again. No HW changes, no reasons found. Update to 3.64 went fluent without loosing any setup values including changes in etc/watchdog.conf survived. The Pylon min/max values did not come back with the update. Instead “internal failure” notifications. I had to reboot the master stack several times until its address enumerated in consecutive order. Then plugged in LV_Hub and all batteries were recognized by Venus immediately including all min and max values. I am also able to identify the rack position 010D what contains highest and lowest cell voltage. Convert hex to decimal while address count starts at 1 instead 0. The 010D battery has a disbalance at 100% SOC from 3,35 to 3,5V. Within 4 hours the passive balancer managed to reduce disbalance from 165mV to 155mV what is too slow. Maybe I have to take it out from the stack and balance separate over 24 hours.
Janvi
(Janvi)
21
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| VE.Bus System [276] - Low battery: Alarm bei fast voller Batterie | 34 | 3516 | 15 April 2026 | |
| Multiplus low voltage alarm | 14 | 216 | 25 June 2026 | |
| Unexpected low voltage alerts - how to debug? | 11 | 252 | 15 March 2026 | |
| At FULL Charge Multiplus is giving >>> Low Battery Alarm (Battery Low Voltage) >>> & shutting down | 5 | 749 | 26 June 2025 | |
| High Voltage alarm Pylontech US3000C & Victron Quattro inverter charger | 22 | 386 | 13 September 2026 |