2una

Ok that would add up, so i'm really more or less just back over on the earlier keep charged settings that worked without bothering with a discharge. Will give it a run here for a bit & see whats what. Thanks

Managed to set it up & hopefully on the right track now - Leave schedule page SOC off & use 95% SOC on the main ESS page. When the open window starts it uses battery power at whatever the grid draw was/is to drain the battery toward 95% but doesn't go that far if the time allocated is too short. Now i just need to find out how far i need to drop it to have the battery think its done something. Current setting is a 5min window & takes me down to 50.1V

Schedule page SOC now turned off - all it wants to do is let the batteries go sit at that selected SOC (highest choice being 95%) So now i guess i must just see how many minutes i need to leave that no charge/discharge window open for to make the batteries think it's done something in the last 3 days.

I also see in the schedule page i can turn off the "Stop on SOC" so that might also offer an option to use, not sure if that is better to have on or off, is on for now

I'm going to have a try with some earlier advice you suggested & see what gives before i just go back to the "ignore it" option From here - 1. If you're running "Keep Batteries Charged", you can (in VE.Configure) enable Dynamic current limiting for that AC input. This is actually meant for generators. What it does is when a larger load starts on the output, it uses the Multi to "cushion" the blow, so that the generator gets more of a gradual load increase. By using this you make the batteries do something every now and then. 2. Instead of using "Keep Batteries Charged", put the system into optimised mode, and then enable Scheduled charging. Set a charge schedule that runs evey day from midnight for 23 hours and 55 minutes. The effect would be that every day just before midnight it will discharge the batteries for 5 minutes, also avoiding the "error". 3. Ignore the error... Now set it up this way to see what happens Only potential downsides i see here is Max selectable SOC in the schedule page is 95% so i want to see if it will either a) stop discharging once the 3 min discharge window closes or b) its going to keep discharging regardless till it gets to its 95% c) its going to try be at 95% SOC at the window finish time If i get b) or c) i guess its over to the "ignore it" option

SVS - was already set to off settings as so - SCS on but looks like overridden to Disabled on the next line below it. AC input setting - I think this is the one you mean here? set to 50A

Got thru the night with no voltage spike happening with that setting I notice here on the graph it definitely seems to be a lot busier whilst it would normally be sitting in full charge idle mode - green line is about where the settings was changed which was also right before a 2 hour load shedding. Plonkster i wonder how difficult it would be to add a Voltage set point to that ESS "feed to grid" setting for them. (LIke here set it at 52.8/53V) OR is that in someway possible to already do? I'm thinking on one hand we are setting ESS to "keep batteries charged" & on another setting telling it to burn it off (seems to be doing that as soon as it goes above 52.0) . If its only trickle amounts i don't really care but on the other hand not too keen if it's something similar to flicking on/off a 100w light bulb all day & night long. That wiggling i see versus before just seems a little "busy"? Good with PV but to keep as UPS only? Trickle amounts of power going to waste & don't worry or consider reverting back to ignoring the pylontech "sleep" problem & remove ESS you think?

I checked for that 2.60 when you mentioned about it - seems its not in the official release yet.(i'm still 2.58 with auto update set to on) Ok fingers crossed with this attempt, Have load shedding kicked in now & that problem seems to come a few hours after the battery is back charged again so maybe tonight may tell a story

Just checking myself - that's the one you mean that i've now turned on?

Ok i'll load that ESS back on with that setting & see what happens. Thanks !!

Thanks for the input Plonkster - you think re-enable ESS & add that setting & try huh. Does this lend any clues? Batt voltage 53V & yet i still see some "charging" going on in that problem area while its throwing out batt high voltage alarms at the same time. The green line is 1st sign of high voltage The yellow line around the 1st High batt voltage alarm thrown

Cursed myself Now removed the ESS assistant out of the picture & see whether that changes anything, If not then i guess a firmware rollback. Settings pre ESS delete was so

Weirdness - Changed nothing & the issue seems to have disappeared - touch wood - hopefully disappeared

Just a rough number the installer or myself pulled from somewhere but its been like that since day1. This is like alarm hopscotch - do something to get rid of 1 alarm & another one comes.......this is now no3 new alarm in attempt to get rid of no2 alarm which is possibly brought on by trying to get rid of no1 alarm........one day we'll get it right hopefully

Think i should try unload the ESS assistant out to see if anything changes as something to try?

Hi Plonkster, Venus is on V 2.58, unchanged for for quite some time. Dvcc yes on Its been only since the firmware change + assistant update that i've ever had this error come 2 times its happened has been 0300 + 0500 so i haven't seen if its kicking the batts off yet

Multi II 48/5000 + 3 x 3.5kwh Pylontechs on UPS only system Due to the pylontech sleepmode ESS was activated - that started to throw a Relay error 11 alarm & what is suggested is to 1st start with switch to latest firmware, It was on 469, upgraded to 474 Now i'm getting thrown high voltage alarms - i've checked my values & think they are still all the same as previous. The new alarm This is a 30 day chart where previous there was no peaks in the graph like in the yellow area that i now have had for the last 2 days since doing the FW update. Inverter settings are as below Anybody spot something i'm over looking ? There was also an ESS assistant update that i did at the same time but those settings also look to be the same as what i previously had without getting this new alarm

@plonkster Has the Blue Wizard had any previous dealings with this error at all? Has only happened twice but now looks like i need to follow up on it. It only ever came after switching to using ESS which also entailed i switch grid code from none to SA Multiplus II 48/5000 Firmware 2626 469 UPS only Venus is on v2.57 I did find this to read already https://www.victronenergy.com/live/ve.bus:ve.bus_error_codes#:~:text=Error 11 indicates a failed,failure (eg inoperable relays). both instances a month apart but it takes the power down when it happens till it sorts itself out

Thanks,Yes pulled it out this afternoon & they look pretty sealed. Pulled my hair out after wiring in the new one it seemed like it had no power as the timer would'nt show anything on the lcd. Check/recheck all tight & in the right hole & wiring was same,I learnt today one must push the reset to get it to fire up. Drove me nuts for a while that one.

Have a geyser timer that when power drops from load shedding is not holding what it is set at, after each time we get load shedding i need to manually turn it back on else cold water. I see in one manual i found that they have a battery in them .Is this battery an easy replace or is it replace the unit story? Is a 5-OT TS030B

Hi,using 3 x Pylontech's. Can program the inverter directly without GX but i think the battery bms needs to have the GX present to route thru. I use a venus with mine. That also gives you all your monitoring pages to see via Victron VRM so its worth its cost

bump

They go into a sleep mode - with Victron inverter switching to using ESS stops it - For Axpert no idea Explained here - I also had the same problem till i switched to using ESS

I have my setup in apartment & don't think that bit of fan noise is a problem, Multiplus II 3kva & later switched to a 5kva. Neither bugs me

This move to using ESS has fixed the error appearing for me,no more errors since doing it