Re: Fox ESS Error Code-1 No Utility, Error Code-26 Grid Voltage Fault, Error Code-27 Grid Frequency
Posted: Sat Oct 25, 2025 5:19 pm
You beauty!
The connections all seemed fine and well twisted together in the CT wires. However, in the settings menu the Meter/CT option was set to <disabled>. I have now changed that to <CT> and it looks like we're back in business.
Now, I will say that I have also found that the RCD (I assume - the breaker with the blue switch handle?) has also tripped a couple of times during this process and I have needed to reset it. That might be because it's faulty (and needs replacing) or, if the inverter wasn't detecting the mains and regulating the supply accordingly, then it may have been that. Might the inverter have dropped the Meter/CT setting when the AC connection tripped initially? Dunno
Anyhoo, for now, it's all good. Monitoring.
Do you have an online 'tip jar' Dave through which I can buy you a beer or two? Thank you for your help
The connections all seemed fine and well twisted together in the CT wires. However, in the settings menu the Meter/CT option was set to <disabled>. I have now changed that to <CT> and it looks like we're back in business.
Now, I will say that I have also found that the RCD (I assume - the breaker with the blue switch handle?) has also tripped a couple of times during this process and I have needed to reset it. That might be because it's faulty (and needs replacing) or, if the inverter wasn't detecting the mains and regulating the supply accordingly, then it may have been that. Might the inverter have dropped the Meter/CT setting when the AC connection tripped initially? Dunno
Anyhoo, for now, it's all good. Monitoring.
Do you have an online 'tip jar' Dave through which I can buy you a beer or two? Thank you for your help
- the CT being disabled is often something that happens on newer installs just after a firmware update - never really understood why it does it on some systems and not others, I don’t think it’s connected to your power tripping but it could have been disabled by a firmware update and the restart actioned the change (it’s a one time event this happening i’ve never seen it happen more than once).