question

try making the difference between start and stop greater. also upgrade the fw to the latest version.

try the fw update first.

Looks like the option to update the MP Firmware is a bit flaky as well?

Tried to do that but after a few stages the system told me the GX OS version was too old and I should update to the latest version.

So I did so, and the Multiplus then is not featured in the list of products I can update? So much for updating the GX OS to let me update the MP Firmware?!

Before the Cerbo GX Update ...

And after the Cerbo GX OS update

(If I switch back to the old OS release, I get the Multiplus Device back in the list, so looks like a pure firmware version limitation)

EDIT: Within the Control Panel, I saw an message saying there was an update to the MK3 (module?) and did I want to update. Thought may as well - and now when I scan for Firmware Updates, I get the Multiplus back in the list. Bit of a hidden one there :)

I also noticed a change within the Control Panel (I think, anyway) that instead of saying the Multiplus is in "Low Power", it says it is in "AES Mode". That is more accurate of course, but I am wondering if it is more than just some words being edited, so decided out of curiosity to not do the MP firmware update yet but see if there is any difference in the way the MP works after the Cerbo GX update. I don't think there *should* be, but worth checking I think.

Failed to switch back to AES mode again this afternoon. Bit earlier than usual - yesterday it failed to revert at 15:30 and the day before it failed to revert to AES mode at 15:12. Todays time was 13:18
But I plugged in a solar panel to the second MPPT and it is a sunny day. Relevance? well, I don't think there should be any but nothing really explains why this is happening.

I turned off both Solar Controllers now to see if there is a link to charging. One other aspect could be temperature? Obviously as the day progresses, the air temp increases. It never gets that hot though - checking the temperature of the locker the MP is fitted it, we are looking at about the 24C mark at the point AES fails to activate and when it does reactivate, it is when the temp is starting to drop. 24C is hardly hot though, and I have a temp-controlled fan that comes on to cool the locker as well so it never gets really hot.

Anyone from Victron can confirm or otherwise if temperature is linked to AES mode activation or not? When AES starts to work again (which should be around 20:30 - 21:30 if the previous pattern repeats, I might try and warm it up a bit and see if AES stops working again? (maybe have a heavy load for 5 minutes?). Solars been off for around 20 minutes and the Multiplus is still "Inverting" despite there being zero AC load, so that looks unlikely to be the cause.

Further analysis of a download with multiple examples of the Multiplus being in "Inverter mode" when it should be in AES Mode (i.e. load below the threshold for AES activation), there is a distinct pattern of it being stuck in this mode only when the temperature is above a certain value.
The only time there is a combination of zero load and Multiplus in "Inverter mode" when the temperature is at a lower value is just after it has been providing power and it reverts to AES Model shortly afterwards.

I am monitoring the locker and not the Multiplus itself note, so the "cutover" temp I am seeing will be lower than the device temp, but is still only 23C, which is not hot for a smallish locker filled with Multiplus, MPPT controllers and a Cerbo GX. Also I will note that there is no error code for overheating or anything for the Mutliplus.

Right now as I type this, the Multiplus is in "Inverter" mode with no load and the locker temp is at 27C. Once that drops to 23C or 22C, it will go into AES I am sure.

I am pretty sure this issue is temp related, but there is no reason why AES should not be active at warmer unit temperatures. If anything, it should be an advantage as it will be generating less heat in that model and allowing it to cool down?

I would suggest that you run the cerbo on the latest release fw when looking for issues.

and you will need to get the multi up to fw505

and then advise what aes issues you have.

there is no point in doing aes testing when the systems ie the multi is not on its latest fw

having the cerbo then on beta fw is also not a good idea, not when we are looking for issues that is

lets get everything on the latest release versions then look at the aes.

To update this thread, everything is on the latest firmware and the problem continues. AES fails to start randomly for no apparent reason.

I wonder if anyone from Victron Energy would care to comment or explain?

Firmware status

I saw some comment about AES only operates in "standalone mode". Note sure if that means if there is anything at all connected to the VE.Bus or if it is working in parallel with other Multipluses?

But just to make sure, I unplugged the RJ45 cable from the Cerbo so now the Easyplus was totally on its own. Made absolutely no difference whatsoever. still didn't go into AES mode when it should have. (and of course, the occasions when it DID go into AES previously, it WAS connected to the Cerbo, so if AES doesn't work when connected, THAT would be wrong as well).

I am not sure whether to tell my supplier the Multiplus is faulty and to fix it as I doubt they will have any more idea than me about this, and Victron seem totally uninterested in commenting on this matter here, so they don't know or don't care either.

Now to the suggestions of "try this", "try that", "maybe Fridge stopping AES working", etc, It would be interesting to see how those suggestions can be compatible with how the AES decides to randomly start working with no difference in the setup, configuration or loads, such as just after midnight last night ....

Any suggestions on how to get AES RELIABLY operating, keeping in mind it works to its own drumbeat with no alterations in the setup whatsoever would be interesting.

Hello, you're lucky your AES works from time to time, mine never starts. I tried several settings without success. The temperature in the north of the France is 18°C so it's not related to the temperature, at least I hope.
I tried a lot of configurations without succes.
My hypothesis is that the Easy solar has a self consumption (31W) greater than the other products. then the threshold in the common software is not compatible. It's a crack in the system.
Pierre

Well, I am convinced that the issue with Low Mode Mode failing to engage is temperature related - when I look at the charts when the AES does activate, it is ALWAYS when the temperature is at the lowest points. See the lastest 2 days below .....

The thing is, we are not talking about high temperatures in any way here either, around the low 20 Celcius mark which no electronic components should be sensitive to from what I understand from my experience (electronics/electrical/computer service engineer) so there is some kind of fault in the unit I am sure.

Just as an FYI, a while back I relocated the temp sensor from just sitting inside the electrics locker where all my Victron kit is located to physically inside the casing of the EasyPlus 12/1600 so it is a more exact representation of the unit temperature, so that temp chart above is a pretty good indication of the unit. All it is doing in that time above is occasionally (around 40% of the time) providing around 55W to a fridge. no other AC loads are active so the temperature fluctuation is more due to ambient temps than device heat generation, hence when it is coolest just before sun up.

Your parameters are

Start aes under 45W, stop over 69W and modified sinus wave.

And your fridge load is 50W....i do not get your parameters...

1.set aes start under 30W

2.set aes stop over 35W

3.set mode to search mode