3x MultiPlus II 48/5000 + Nucleo GX = ESS not working

Hi everyone,

I’m having an issue with a new Victron installation. For some reason, the Nucleo GX can’t detect the ESS Assistant installed on the MultiPlus units. The units go into passthrough and stop charging the battery.

Here’s the setup.

  • 3 × MultiPlus-II 48/5000/50-70

  • 1 × Nucleo GX

  • 1 × EM540 as the grid meter

  • 1 × ET340 as the PV meter

  • 2 × Hoymiles MIT-5000-8T inverters connected on the AC-in side

I first updated all three MultiPlus units to firmware v568, which was the latest version available to me. I then configured them as a three-phase system using VE.Bus Quick Configure. I also checked the setup in VE.Bus System Configurator and didn’t see any significant differences.

Once the three-phase setup was complete, the units started up. When I applied AC input, they synced with the grid and started charging the battery bank. The batteries are configured for voltage-based charging, with no remote battery management.

Next, as I usually do on this type of installation, I right-clicked each MultiPlus in turn to open its settings. I selected the grid code, set the charging voltages and current, and added the ESS Assistant. I repeated this for all three units.

Once I’d finished configuring them, I plugged the MK3-USB interface into a spare USB port on the Nucleo GX. The MultiPlus units show up in the Venus OS device list, and I can see their live readings. But when I try to configure ESS, Venus OS reports that no ESS Assistant was found.

Has anyone run into this before? What should I check next?

I also spoke to my equipment supplier. Their technician suggested there might be an issue with how I’d uploaded the ESS Assistant and recommended trying Remote VEConfigure. That didn’t solve it either. The settings did go through. I changed the AC input current limit to verify that the new configuration had been applied, and the new limit showed up. Venus OS still couldn’t see the ESS Assistant.

Has anyone run into this before? Could it be related to the new Nucleo GX or to my older MK3-USB interface? Mine is the version with a detachable USB cable. What would you check next?

Have you also loaded the ESS assistant onto the Mp correctly?

Try it again.

Yes, I’ve tried uploading the configuration several times using different methods. When I read the configuration back from each MultiPlus, the ESS Assistant shows up in the Assistants tab. The Nucleo GX still doesn’t detect it, though.

Have you installed any updates?

Could you post some details about the setup?

Hi,

How did you connect the Nucleo and Multiplus?

A Nucleo GX won’t recognise a Multiplus directly either, as it doesn’t have a VE.Bus port.
The Multiplus 2 needs a GX device with a VE.Bus port…

You should be able to get a VE.Bus port via an MK3 USB interface connected to the Nucleo’s USB port.
I haven’t tested whether that actually works, though — the Nucleo is really more for VE.Can devices (Multi RS, etc.)

Best regards,
Broesel

Yes, all three MultiPlus units are running the latest firmware (v568), and the Nucleo GX is running the latest Venus OS (v3.85).

I’m aware that the Nucleo GX doesn’t have a VE.Bus port. I connected the MultiPlus units through an MK3-USB interface as described in Victron’s documentation.

Venus OS sees the MultiPlus units and displays their live readings, including voltages and currents. The only thing it can’t detect is the ESS Assistant.

It will not work. Read manual 5. Connecting Victron products (Option 1: Use an MK3-USB interface)

  • For ESS systems, only the system on the built-in VE.Bus ports participates in ESS mechanisms. Others are visible in the Device List only.

You need CerboGX.

Why using a Nucleo if you have a VE.Bus system and need to purchase a MK3?
A Nucleo + MK3 is more expensive than a Cerbo GX (+ you have more inputs/outputs at the Cerbo).

Good question. My supplier recommended the Nucleo GX for this particular setup because it was newer and had a faster processor. The impression I got was that there were no downsides for my setup.

Victron’s Nucleo GX specs say that VE.Bus devices are supported via an optional MK3-USB interface. I didn’t see any mention there of limited functionality or of ESS being unavailable over that connection.

I can confirm that ESS doesn’t work in my setup. Could someone from Victron clarify whether this is an intended limitation of the Nucleo GX or a bug? If ESS with VE.Bus devices is unsupported on the Nucleo GX, I think the specs should say so explicitly alongside the note about MK3-USB support.

The simplest thing would be to swap the Nucleco for a Cerbo.

I’d also naively assume that an ESS works with the MK3 adapter, since it works with the Raspi too.

Have you installed and configured the ESS Assistant on all three devices?

What are the settings for Battery Monitor and Grid Meter on the GX device?

Is the phase sequence between the grid meter and the Multiplus correct?

Could you post some screenshots and your complete settings here?

As an intermediate step, I’d personally try it with just one Multiplus first…

Hi everyone, and thank you all very much for your help.

Please don’t take this the wrong way, but I’m being asked questions that I already answered in my first post. Still, I’ll go through them again.

First, replacing the Nucleo with a Cerbo isn’t straightforward in my case. I need to order another device and then travel to the site to install it. The installation is 150 km away from me, so this takes time and costs money. From my perspective, the simplest solution would be for the system to work as described and advertised by Victron.

Second, yes, I installed the ESS Assistant on all three units, one at a time. This isn’t my first Victron ESS installation. It’s simply my first one using the new Nucleo GX. I know how to configure these systems, in what order, and what to check along the way. In this case, it simply didn’t work.

Third, this particular setup uses voltage-based battery control, so the MultiPlus itself is selected as the battery monitor. The grid meter is a Carlo Gavazzi ET540 connected through Victron’s USB-to-RS485 converter. It appears in the system and is correctly configured as the grid meter.

Fourth, the phase sequence is correct. Otherwise, Venus OS would report an error and the system wouldn’t be able to synchronise with the grid. Neither of these points explains the issue I’m seeing. As I mentioned in my first post, the system synchronises with the grid correctly, but then goes into passthrough mode.

Finally, with all due respect, what would testing with a single MultiPlus achieve when this is intended to be a three-phase system? I don’t see the value in spending time on that, because even if it worked, it wouldn’t resolve the problem with the intended setup.

EDIT: The issue was also reported to my equipment supplier and escalated to Victron support. I’ve now been told that this is a software issue and that Victron will fix it in an upcoming firmware update.

I don’t yet know which component needs updating, whether it’s Venus OS, the MK3 interface, or something else. What I do know is that they’ve applied a temporary patch so the system can detect the ESS Assistant in this particular configuration, and it’s now working. The permanent fix will be included in an upcoming software update.

So the person who said ESS wouldn’t work through an external MK3 interface was mistaken as well. Unfortunately, this once again shows that the documentation is a bit of a mess. :frowning:

Thanks for the information.

This is exactly why there’s a dedicated escalation path for problems like these!

You apparently build a standard system, and some detail turns out to be the showstopper. You check the installation and the hardware. You go through the programming and check the firmware of the components. No result! So you ask the retailer, who shrugs. Local quirks are usually known either to them or to the Victron installer. No luck there either, so the problem gets passed on (the steps were documented in the RMA sheet). Only then does it reach the company, which takes a look at the matter; the issue is definitely unknown or has only just arisen.

The “normal route” would mean having to work through repeated standard responses from the company and wasting time unnecessarily. Random trial and error takes more time than tackling the problems in a structured way and escalating them step by step.

A good example of why this process has apparently become established despite the time it takes. The documentation is being updated, but the important thing is to get the system up and running.

As I can see, your problem seems to have been resolved quickly.

Because of the length of a post and automatic translation, misunderstandings occur more often, but these can usually be cleared up by politely asking for clarification.

The documentation says that ESS only works on the internal (first) VE.Bus connection and not on the external (second) VE.Bus. That’s the same with the Raspberry Pi.

DVCC and ESS control applies only to the system connected directly to the built-in VE.Bus ports.