I’ve been running a 3-phase Victron ESS setup reliably and without any issues since 2020. The system includes:
1× MultiPlus II 48/3000 GX (Venus OS 2.60)
2× MultiPlus II 48/3000 (slave units)
1× EM24 | Carlo Gavazzi UCS7 energy meter (Firmware 1.12)
1× Pylontech HUB (Firmware 1.1)
20× Pylontech US2000B/C batteries, arranged in 4 stacks of 5 units each
3× Victron AC current sensors (40 A, one per phase, connected to the AC input of each MultiPlus)
Photovoltaic system:
18× 350 Wp modules, each with its own AE-Conversion 350 W micro-inverter
The micro-inverters are grid-tied, feeding power directly into the house grid
3× AE-Conversion AEDL-UH data loggers are used for dynamic feed-in limitation, actively reducing PV output when Pylontech batteries are full
The AC current sensors mentioned above are used to measure the amount of PV power fed into the grid, enabling proper ESS operation and feed-in control
I’m planning to upgrade from Venus OS 2.60 to the latest 3.x release, but would like to verify compatibility first.
Are there any known issues with EM24 | UCS7 (FW 1.12) or the Pylontech HUB (FW 1.1) in Venus OS 3.x? Is a reconfiguration of devices or ESS parameters required after the upgrade? Does the dynamic feed-in limitation setup remain functional under newer Venus versions?
Any insights from users with similar setups or upgrade experience would be very welcome.
Thank you in advance!
So, I never get a display or information for individual Pylontech battery packs.
Somehow, based on the old forum, I seem to remember that the option to list information about individual Pylontech battery packs was only implemented with a certain newer firmware version.
Which can then be acknowledged without any further action, and the problem is simply resolved. But I can never figure out what it means or which battery it refers to. The Pylontech itself never displays a warning or error. There are no problems in the Pylontech BatteryView log either.
With newer firmware, I suspect I could get more, different, and additional information to help narrow down and solve the problem.
Secondly, I would like to expand my system on the solar generator side with four Victron SmartSolar MPPT 100/20. I want to add more solar modules, but I would like to connect them directly to the DC supply rather than to a grid-tied inverter.
And finally, I would like to use the “Android device as a dedicated display for GX” feature, which requires firmware 3.6.
Im on v3.00 and i have a bit more info on my pylontechs, however not individually only highhest lowest temp/voltage, but could be in v3.63 there is more info
Just for info:
Right now there is a slight isseu with dvcc voltage limit setting in v3.63 gui 2, but is already solved in next release, you can set it right in remote console or gui v1
I’d be very interested to see how it looks for you. Would you mind uploading a screenshot of yours? Did you connect the Pylontechs directly? Or via a hub like I did? I imagine that the display and the behavior with the hub—in my case, four banks of five Pylontech 2000s each, and, to be straightforward, a mix of types B and C—is different than if you connect the Pylontech directly to the Multiplus.
Your message is a bit confusing to me. It seems to me that you’re assuming two different firmware update processes? VENUS.OS? | Multiplus firmware? I’ve done that before, but it was a good half a decade ago. Could you please describe that in more detail? Links for further reading are welcome.
It’s a good philosophy.
I updated an older set of 3000’s as the old firmware did not send min/max cell voltages, so there are benefits depending on age.
If you start updating one component you always should update all components.
GX and MultiPlus are different devices.
It’s strange that it doesn’t show the MultiPlus in that list, also the GX device should be shown there but maybe you version 2.60 is too old for that feature?
Thanks for your time. I think so too, but I’m guessing that this is simply not possible with my old GX version. I could perform the GX update via the Remote Console.
Perhaps I wasn’t looking in the right places or had the right facts searched for. Is there some kind of table that lists, for example, that a certain VE.Bus firmware is mandatory starting with a certain Venus.OS version, e.g., 3.6?
I’ve read a lot of information, blog posts, and PDFs in Victron’s professional section, too. However, I haven’t been able to find any facts about whether an VE.Bus firmware upgrade is even necessary or recommended when aiming for newer Venus.OS version.
I found a PDF contains an email address where you can request the firmware. Would this be the correct, officially designated way to find out whether an VE.Bus firmware upgrade is necessary at all, and which one?
I’m trying to find a solution or answers myself, but I’m overwhelmed by the sheer volume of information, some of which relate to products and versions many years/decades older than my 2020 system. I hope to get some support and guidance here.
You’ll never get this now, not even with the most recent venus os firmware.
As per internal failure error, a firmware update from pylontech is in order.
Great to know, that I am have no need to try to solve it on Victrons site"
But do you mean, that Pylontech is working on this problem? And I will have to wait for a future update from Pylontech for Pylontech batteries and Pylontech HUBs?
With recent Pylontech firmware (rev. 2 and later) you can obtain extended information over CAN bus from each battery.
But even if you have that recent Pylontech firmware, Venus OS is not asking the batteries for those pieces of information.
Of course, the other reason - the internal error problem - asks for a Pylontech firmware update, thing that their tech department will tell you.
Are there any known issues with EM24 | UCS7 (FW 1.12) or the Pylontech HUB (FW 1.1) in Venus OS 3.x?
