This morning my system tripped. It restarted itself and normal service resumed. The trip is unusual, and I wondered what had caused it. When the system was back up, I queried the error log and found this:

So that's nice and helpful. Not.

Quite a bit happened at 12:00 actually

1) Battery reached 100% SOC (or just had)
2) Loadshedding
3) Heatpump started up (1.5 kW compressor on that)

The pool pump was running, but that's not on the backed up circuits. No other big loads that I'm aware of were on the backup side.

So was there somehow a spike of over 20A on the backed up side? Or was it coincidentally something else.

Heck! How stupid am I? It's telling me that there was a utility loss.

Still odd though. The reason we have these systems is because there might be a utility loss.

Looking through the recent log entries I find other error 512s. They can all be correlated with a load shedding event. They can't all be correlated to a system trip.

Maybe I should start the heatpump at 11:55 or 12:05.

Hi @Bobster. !. Indeed, Code 512 corresponds to the description: Utility loss. You should look in your PV Mater at the following event: #16874 if you see an event called "Error Clearing". The time differences between the two would give you the amount of time the grid was cut. Likewise, before one of the PV Master updates, Event 512 had the description "PRE FAILURE" and I found it associated with instantaneous requirements greater than the nominal capacity of the Goodwe in the output of essential loads.

 

Edited October 18, 20223 yr by Cef

Thanks, @Cef. #16874 is indeed "error clearing: and was 2 minutes and 4 seconds after the 512 error. 

#16875 was a utility loss at 18:01 on the 17th - that was load shedding.
# 16876 was error clearing at 20:13 on the 17th - end of load shedding

I got another 512 today, courtesy of stage 4, but there was no shutdown and restart. So I'm guessing that on the day I made the OP there were two things that happened more or less simultaneously. I'm also thinking that if the system is busy shutting down, it probably can't log an error.