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