According to documentation of the V3 API for "Set the time segment information" I am supposed to use fdsoc as fcsoc, which should:
"The FC/FDSoC is the SoC level set for the system when operating in Force Charge/Force Discharge Mode. Once the battery reaches this SoC, the system will automatically stop charging or discharging."
The API sets my time segments, and I verified through the https://www.foxesscloud.com/v2 quick settings that the schedule is indeed reflecting that FC/FDSoC in the ForceCharge block. However, the inverter continued to charge during the entire time segment and ended up some 15% higher on SoC. I then tried to set also the MaxSoc for the time segment, and then it did stop charging when reaching that MaxSoc level. Fine, but it seems as a bug or have I missunderstood the behaviour of this API?
Note that all the other time segments which included Backup and SelfUse worked fine and reverted the MaxSoc back to its default of 100%.
I have a H3 model SK-HWR-12 inverter with Master/Slave/Manager versions 2.19/1.03/1.91.
It depends on your inverter and firmware. First generation inverters don't implement fdSoc or fdPwr for charging, while second generation ones do.
To get reliable results when charging, set both fdSoC and maxSoC to the same value in any force charge time segments.
To get reliable results when charging, set both fdSoC and maxSoC to the same value in any force charge time segments.
H1-6.0-E hybrid inverter
6 x HV2600 v2 batteries
16 x JA Solar 405w panels
7 x Tigo TS4-A-O optimisers
6 x HV2600 v2 batteries
16 x JA Solar 405w panels
7 x Tigo TS4-A-O optimisers
Thanks Tony,
I'll stick to that since it actually did work that way when I tried it.
/Peter
I'll stick to that since it actually did work that way when I tried it.
/Peter
Fox has been making lots of changes, including what happens when min/max SoC is hit during forced charge/discharge.
The previous default was to switch to self use for the remaining time, now it hits the SoC and floats and this change has triggered lots of complaint emails as houses import when power is the most expensive.
At the moment you need to limit based on time and the import/export wattage, but don't set the min/max SoC high/low enough that the SoC limit might be met first.
The previous default was to switch to self use for the remaining time, now it hits the SoC and floats and this change has triggered lots of complaint emails as houses import when power is the most expensive.
At the moment you need to limit based on time and the import/export wattage, but don't set the min/max SoC high/low enough that the SoC limit might be met first.
Yea, I have seen that in social media.
Using MaxSoC (in pair with fdsoc, just in case) works fine with my inverter. I leave all other parameters to default. It charges when supposed to, it stops at MaxSoC even if there is time left in the time segment. And it doesn't discharge to house or export, which is exactly what I want during ForceCharge time segments even if it reaches MaxSoC with time to spare.
When you say it "floats", what do you mean by that?
I did notice in earlier firmware versions on my inverter/batteries that when using the standard force charge together with MaxSoC it did not only stop charging att MaxSoC but it also disregarded any PV Power. PV wasn't even used for house, just discarded. So I also had a five minute loop to check when SoC reached my MaxSoC and turned of force charge. This is of course just a problem in the few occasions that I due to comming high tarrifs want to top up batteries to some level during sunny daytime.
You also mention that it used to swap over to SelfUse when in ForceCharge for the remaining time. My inverter/firmware actually reports that it is in SelfUse workmode the entire ForceCharge segment, but it does truly charge. This was a little anoying sine I wanted to check workmode each time inverter is supposed to switch to a new time segment. Other time segments such as Backup and of course SelfUse was reported correctly. I still have a small itch in my neck that it may be my library that does something wrong, so I will debug out the actual JSON response during ForceCharge to make sure.
Using MaxSoC (in pair with fdsoc, just in case) works fine with my inverter. I leave all other parameters to default. It charges when supposed to, it stops at MaxSoC even if there is time left in the time segment. And it doesn't discharge to house or export, which is exactly what I want during ForceCharge time segments even if it reaches MaxSoC with time to spare.
When you say it "floats", what do you mean by that?
I did notice in earlier firmware versions on my inverter/batteries that when using the standard force charge together with MaxSoC it did not only stop charging att MaxSoC but it also disregarded any PV Power. PV wasn't even used for house, just discarded. So I also had a five minute loop to check when SoC reached my MaxSoC and turned of force charge. This is of course just a problem in the few occasions that I due to comming high tarrifs want to top up batteries to some level during sunny daytime.
You also mention that it used to swap over to SelfUse when in ForceCharge for the remaining time. My inverter/firmware actually reports that it is in SelfUse workmode the entire ForceCharge segment, but it does truly charge. This was a little anoying sine I wanted to check workmode each time inverter is supposed to switch to a new time segment. Other time segments such as Backup and of course SelfUse was reported correctly. I still have a small itch in my neck that it may be my library that does something wrong, so I will debug out the actual JSON response during ForceCharge to make sure.
It just means it will stay at that level of charge, most likely very very slowly charging the battery to achieve that.
Given all the changes that seem to have happened I'm not entirely surprised.