This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Hello,
I have 3-phase system build on EasySolar-II GX (phase L1), 2x Multiplus-II (phase L2 and L3)
There is no ESS assistant loaded only Two-signai BMS.
First time this system reported overload on phase L3 twice.
It happened when there was grid loss for less than a minute.
System is under development and there is practically no load (50-60W)
Why this overload happen?
This may be related to an ongoing issue that is being investigated. What is the quality of grid?
My system is connected to this grid for the last 6 months.
Grid is not perfect and this is why I invested allot of money for this Victron hardware and battery, but this overload happened first time since the instalation of the system.
Any chance you recently updated firmware? What version you on?
Hi @MarekP
I see the overload -warning- happens when the grid fails, this can happen when the grid voltage drops 'slowly' and the system has to bring back the voltage to normal system voltage.
An overload -warning- doesn't have to be a problem, an -alarm- is a problem.
What are you grid low voltage disconnect values?
@Daniël Boekel (Victron Energy Staff)
Hi,
When those overload warnings happened the voltage changes were fast.
Linesmen just tripped the breaker, to perform some work on the grid.
Puzzles me that this overload warning happened, with 0W load on all three phases, and only on phase L3.
You have seen my grid voltage disconnect values. :)
But here they are:
What is also interesting that they were not some short blips. One lasted 75 sec and the other 48 sec.
Regards,
Marek
@Daniël Boekel (Victron Energy Staff)
@Guy Stewart (Victron Community Manager)
I really would like to know the answer to my question.
I cannot agree with the answer that tells me that I should ignore this overload warning only because it is not an alarm.
If warnings are unimportant than why you even bother to program them to the system?
If it is a bug than you should fix it.
It is without logic to have an overload warning w ZERO load.
