MultiPlus-II on latest firmware (v556) will not enter Search Mode

Hello,

I am having an issue where my MultiPlus-II will not enter Search Mode (AES) and I have exhausted all configuration options. I would be very grateful for some expert assistance.

System Details:

  • Inverter: MultiPlus-II GX 24/3000/70-32
  • Inverter Firmware: Updated from v508 to the latest, v556.
  • GX Device: Separate Cerbo GX (Product ID C00F), firmware v3.63.

Problem: The inverter will not enter Search Mode.

  • My measured no-load power draw is consistently 20W (with nothing physically connected to the AC-out terminals).
  • The Search Mode “Start AES when load lower than” threshold is set to 25W.
  • The condition (20W < 25W) is met, but the inverter remains permanently in the “Inverting” state and never switches to “AES mode”.

Troubleshooting Steps Already Performed:

  1. Firmware Updated: Successfully updated the MultiPlus-II firmware to the latest version (v556) via VRM remote update.
  2. Settings Re-applied: Confirmed that the Search Mode settings were re-enabled and correctly configured after the firmware update.
  3. Virtual Switch Disabled: Confirmed the Virtual Switch is fully disabled (set to “Do not use VS” and the “Invert” option is unchecked).
  4. No Assistants: Confirmed that there are absolutely zero Assistants loaded on the device.

I have reached the end of all possible user configurations. The settings appear to be perfect, yet the feature does not work. Could this be a potential bug in firmware v556 for this hardware, or is there anything else I can check?

I have attached screenshots of my Inverter, Virtual Switch, and Assistants tabs for your verification. I also have the full serial number available and can provide it in a private message to a Victron staff member if needed.

Thank you for your time and assistance.




I see that nobody has responded. I am probably under-qualified to answer, but I just spent a few hours struggling with the same thing on a new install and here is what I found;

My no load AC draw shows 18VA, which makes no sense, as I have AC Mains disconnected. So that indicates to me that there is some offset error.

Regardless, I set AES Start to 20W and it will not activate. Tried 30W, 40W, 46W, will not activate. Inverter “humm” is constant and DC current draw is about 1A, = about 13W, = non AES idle power draw. Magically, at Start AES set to 50W, it goes into AES Search and I see the DC idle power draw drop from about 13W to about 3W. This was verified as repeatable.

AES stop was set to 60W > Start, as this is the lowest VE Configure allowed me. Note that the 60W is listed as “above AES Start level”, and not an absolute level. That tells me, in theory, that AES would not kick off until 50W + 60W = 110W.

I Connected a (switched) single 60W bulb to AC loads. I switch the 60W load on and AES shuts off, I switch the bulb off and Inverter goes into AES Search (I can hear the difference and see the DC current draw drop to about. 0.2A

So, the functionality “works”, but the settings seem off by quite a bit, possibly a scaling error, as in the Start AES at 50W settings is not 50W at all???

I’m going to grab some LED bulbs/loads and experiment at different loads to see where AES starts and stops, with these settings of Start 50W and Stop 60W>than Start.

Not sure if that helps you, but I would say experiment with higher Start watts and don’t trust the settings as accurate…

I’m not sure if I tried @VTJuice trick but with a quattro I just couldn’t enter search mode. In the end, I gave up since it is wasn’t vital.

I’ve posted a year ago about the AES or search mode being totally inconsistent with the specs victron show in their inverters description.

Those do not work as advertised, for mine to kind work at 110W (under 110W olease switch to AES or search mode) i needed to put something like 300W in the parameters….and even then it was not consistent. Sometimes it would not go in AES under 150W….it’s really badly designed. No one at victron as replied,no one is competent at victron for those..they never answer…cause they know their system is an alpha functionality.