I recently installed my second AIO. I have upgraded firmware on both to v6, and set parameters on both to obtain Grid Feed-in Priority behavior in an area where interconnection is allowed, and there is no time-of-day rate change so I'd like the battery to float at 90% charge while Grid is "up", and only swing into self consumption when Grid is unavailable.
The primary settings for this behavior are
PowerControl>PowerControl>[work mode = Grid Feed-in Priority]
PowerControl>PowerControl>[support normal load = enable]
PowerControl>PowerControl>[zero export = disable]
PowerControl>PowerControl>[max feedin Grid Power = 10000]
PowerControl>PowerControl>[timebase control = disable]
Battery - Battery section>[discharge to = 10%]
Battery - Battery section>[charge to = 100%] (when running off-grid)
Battery - Battery section>[start recovery charging = 11%]
Battery - Battery section>[stop recovery charging = 15%]
Battery - Battery section>[discharge end SOC on-grid = 9%]
Battery - Battery section>[max charge power = 5000]
Battery - grid charge section>[charge by grid = enable]
Battery - grid charge section>[stop charging by grid capacity = 90%]
Battery - grid charge section>[max allowed charge power = 5000]
I am seeing expected behavior on the first install:
Salsman - sell-back priority.JPG
but the second install, with same parameters is showing self consumption through the night and draining battery rather than floating at 90% as desired:
250322 showing self-consumption.JPG
any ideas why, and how to correct ?
I have double checked both AIOs... the firmware versions are all the same. Key settings as noted in top post is the same, but behavior is different ?! I am still seeing self-consumption on one, and the desired "float at 90%" on the other.
any ideas @Logan ?
Looking at the machine the Slave DSP file never got updated and will cause a lot of these issues I am told. We need to get you up to 20200 on the Slave DSP
Quote from: FNG on March 31, 2025, 10:22:37 AMLooking at the machine the Slave DSP file never got updated and will cause a lot of these issues I am told. We need to get you up to 20200 on the Slave DSP
which of the update files does the Save DSP ?
I have the following .bins available, and could try re-uploading:
1. G9514-100105-01_020200.bin loader, takes a minute to upload, and several minutes to run
2. G9514-100100-03_020600.bin for MNS-AIO
3. G9514-100104-03_020601.bin
4. SS1058_20016x2_0517_m.bin for powerflo-16 ?
1. G9514-100105-01_020200.bin loader, takes a minute to upload, and several minutes to run
Quote from: FNG on April 01, 2025, 07:51:42 AM1. G9514-100105-01_020200.bin loader, takes a minute to upload, and several minutes to run
ok, since I already have that one, I will run it again at some point. I do remember this one reported a "networks problem" halfway thru the update, but then seemed to complete after a while. This is exactly why I would like to be able to do the firmware update hardwired from a laptop rather than rely on wifi/cell. I have lots on clients in rural northern NM where there is very limited wifi/cell service, especially at remote cabins.
I find it disappointing that there is no documentation on how to do this initial firmware update, the required files are not available anywhere online, and there is no way to verify that it completely properly unless you happen to know what version numbers *should* be shown in the updated version numbers for Master and Slave DSP.
I need to be able to pre-configure an inverter at my shop in town before installation, and have confidence everything is set up correctly to avoid making second and third trips into the field for updates or tweaking settings.