Tom Funchess
New Member
I have been doing some extensive testing on my system for the last few days, trying to come up with a reliable means to set up the system as a "whole house battery backup" with batteries maintained in a high State of Charge when there is bad weather forecast during times when I am away from home. This was my main goal of setting up this system, the secondary goal was to save money on my electrical bills.
I had originally intended to just switch the inverters to SUB mode when I saw bad weather approaching (remotely using Solar Assistant), and then switching back to SBU after the weather passes. That does not work, and I and others have written some about it in other posts.
As a workaround, I put together a plan to test the ability to set the inverters to switch between SBU and SUB mode in three different scenarios using the "Maintain battery state of charge" programming in Solar Assistant (that just makes the manual process when you do it on the inverters themselves A LOT easier).
I tested Scenario 1 a couple of days ago and it seemed to have been a success. However, I did notice that every now and then, while I was sitting with the inverters doing my testing, I would get an Error 61 that would quicky clear after 2-3 beeps.
Last night I tested Scenario 3 as I worked my way down in terms of the SOC of my batteries. My plan was to test Scenario 2 tonight, after I pulled the batteries down to 30% or so. All went well overnight and even during the first couple of hours of sunlight as the sun came up. It did exactly what I expected it to do.
That is, until around 9:00 AM this morning. I found that the 2P1 inverter had shut down at 8:50 AM and was showing an F80 CAN fault while, the 2P2 inverter continued to charge the batteries beyond the target I had set, and all the way back toward 100%. When I found the inverter shut down, the SOC was already at 92%, way above what I had set in the program.
As I was gathering up the data from what had happened, I was a little shocked when the 2P2 inverter slowed charging when the SOC hit 96%!!! I've heard an explanation for that, and it is a whole different issue, but it is related to how the inverter will continue to charge to a previously set SOC if the program is shut down before it reaches that value.
This is now the second time that my 2P1 inverter has shut down with an F80 fault in the last few days. When it occurs, everything else seems to be working as expected, and then out of the blue, the inverter shuts down abruptly. I observed it in person a couple of days ago. At this point, I have been unable to relate the shutdown to anything unusual happening with the loads, PV input, or AC Input.
The only question that I can think of is whether the F80 shut down could in any way be related to the infrequent Error 61 that I have seen as I spend more time face-to-face with the inverters? The Error 61 problem that I was having early on is still happening after all the firmware updates, but it is happening much less frequently.
Can anyone explain, in plain English, in layman's terms, what exactly an F80 CAN fault is, and what are some possible causes for it?
Has anyone experienced it with any of the LV6548 variants and then found a cause and solution?
My Setup: I have dual EG4 6500s running in split phase 240V, one is an older unit (May 2022) and the other is a newer unit (late November 2022), both updated to 79.61 firmware, with 6 EG4 LifePower4 batteries set up with BMS communication to 2P1 (EG4 battery type selected on 2P1, USE on 2P2).
I had originally intended to just switch the inverters to SUB mode when I saw bad weather approaching (remotely using Solar Assistant), and then switching back to SBU after the weather passes. That does not work, and I and others have written some about it in other posts.
As a workaround, I put together a plan to test the ability to set the inverters to switch between SBU and SUB mode in three different scenarios using the "Maintain battery state of charge" programming in Solar Assistant (that just makes the manual process when you do it on the inverters themselves A LOT easier).
- Scenario 1 would be set such that the inverters would switch from SBU to SUB mode when the SOC of the batteries dropped below 80%, and the inverters would switch back to SBU mode when the SOC reached 85%. This would be my "High SOC Settings for Battery Maintenance."
- Scenario 2 would be a "Low SOC Settings for Battery Maintenance" (for good weather and maximizing solar production).
- Scenario 3 would fall somewhere in between (to account for short days or days with low PV input due to weather, absent the risk of weather-related power outage).
I tested Scenario 1 a couple of days ago and it seemed to have been a success. However, I did notice that every now and then, while I was sitting with the inverters doing my testing, I would get an Error 61 that would quicky clear after 2-3 beeps.
Last night I tested Scenario 3 as I worked my way down in terms of the SOC of my batteries. My plan was to test Scenario 2 tonight, after I pulled the batteries down to 30% or so. All went well overnight and even during the first couple of hours of sunlight as the sun came up. It did exactly what I expected it to do.
That is, until around 9:00 AM this morning. I found that the 2P1 inverter had shut down at 8:50 AM and was showing an F80 CAN fault while, the 2P2 inverter continued to charge the batteries beyond the target I had set, and all the way back toward 100%. When I found the inverter shut down, the SOC was already at 92%, way above what I had set in the program.
As I was gathering up the data from what had happened, I was a little shocked when the 2P2 inverter slowed charging when the SOC hit 96%!!! I've heard an explanation for that, and it is a whole different issue, but it is related to how the inverter will continue to charge to a previously set SOC if the program is shut down before it reaches that value.
This is now the second time that my 2P1 inverter has shut down with an F80 fault in the last few days. When it occurs, everything else seems to be working as expected, and then out of the blue, the inverter shuts down abruptly. I observed it in person a couple of days ago. At this point, I have been unable to relate the shutdown to anything unusual happening with the loads, PV input, or AC Input.
The only question that I can think of is whether the F80 shut down could in any way be related to the infrequent Error 61 that I have seen as I spend more time face-to-face with the inverters? The Error 61 problem that I was having early on is still happening after all the firmware updates, but it is happening much less frequently.
Can anyone explain, in plain English, in layman's terms, what exactly an F80 CAN fault is, and what are some possible causes for it?
Has anyone experienced it with any of the LV6548 variants and then found a cause and solution?
My Setup: I have dual EG4 6500s running in split phase 240V, one is an older unit (May 2022) and the other is a newer unit (late November 2022), both updated to 79.61 firmware, with 6 EG4 LifePower4 batteries set up with BMS communication to 2P1 (EG4 battery type selected on 2P1, USE on 2P2).
