After being enticed to upgrade my firmware, I am now looking through the ESS menu and see that the options have changed a little.
I was wondering how the “Grid metering” menu item operates. If I set it to “Inverter/Charger”, would it prevent backfeed on AC-In?
Also, I see “Grid feed-in” now leads you to a sub-menu. I assume both AC-coupled PV and DC-coupled PV feed in excess should be off (in the South African normal use case)? The default option seems to have AC-coupled PV feed in excess on. That would probably anyways only matter in the case of a Fronius setup?
So if I want to prevent the PV being used in the rest of the house (none critical also) I will need to disconnect the energy meter, not just tell the GX there isn’t one?
Haha the reason I asked is because it is a while before any non critical stuff comes on. I’ll just go and turn on the oven when I’m done with work and see what happens.
All that happened is the “Grid meter installed” switch was replaced with a more descriptive option list that explains more clearly what happens.
All this does is determine whether the external meter is zeroed, or if the Multi’s input is zeroed. It is possible to zero the input of the Multi even though you do have a grid meter installed (eg, for people who want to measure the whole consumption of the house, but don’t want to push power back to a geyser or a whatever on the input side…).
Nope, won’t make any difference, as my 474 works perfectly, and 477 pertains to a country code, Other, that has no bearing on you as you should be on SA NRS code.
A firmware check is easy, right? You just check the number against some known good one, right? Not! No… sometimes the firmware version is not available yet. OK, easy fix, right? Just skip the check if the firmware version is null? Not! Sometimes you just get completely spurious data… for 2 seconds… usually at 4AM in the morning, and then it goes away immediately so it cannot be debugged later… only to show up again two weeks later!
Welcome to the frustrations of a software developer. You know why I don’t believe in Macro evolution? Simple… mutations always cause sh*t to break… not the other way round.
#1 and #2 are not errors. They are “reason codes”. It tells you why the system is currently not making any power. #1 simply says the battery is low. #2 says BatteryLife is active (that reminds the user that discharge may have stopped at a higher point than MinSoc because BatteryLife mandated it). They are not errors, they are there to stop people asking “Why isn’t it working!??”.
If you go to the notifications page and just hit the right button on the notification, the triangle top right will go away. It is an intermittent warning that shows up… which frustrates the heck out of me. I can attach a timer to it (only raise warning if it has been active for some seconds) but I hate complicating stuff because other stuff misbehaves… and having timers that need to be cancelled adds more room for more bugs…
ESS Codes on the screen, bottom center of screen: #1 - Battery Low #2 - Battery Life Active #3 and #4 - has to do with BMS signals, #5 - slow charge, #6 - user set the max charge power to zero #7 - user set the max discharge power to zero
Should I be concerned about this message though? Just ignore it? Not sure exactly what DVCC does for me, but if I look at the sub menus, it looks important enough not to turn it off.
DVCC = Distributed Voltage and Current Control. It means the battery calls the shots (it specifies the charge voltage and current limits) and the rest of the system obeys that request. The old legacy stuff is still around and to keep things backwards compatible, DVCC will be left off in such (usually off-grid) systems. But for all new systems… DVCC is the way. For many batteries it will be forcibly enabled (to cut down on people setting it up wrong and bothering support about it… ).
”.
).