I don't know such problems when setting the SOC values in the Controller's parameters and saving it as a new component.
Remember that you can specify the controller's thresholds either as Voltage or as SOC. However with the Voltage specification, the corresponding SOC will depend on the Battery voltage model.
Please explain exactly:
- with which version of PVsyst,
- how you modify/save this component, and which component ?
- what is not correct.
NB: The SOC thresholds of the controller are used during the hourly simulation.
The pre-sizing tool uses a specific value for the disconnect SOC threshold, which is specified in the Hidden parameters, page "Stand-alone System Pre-sizing", item "SOC minimum threshold".
With which version of PVsyst ?
v6.64 - TRIAL
How do you modify/save this component, and which component ?
I select a solar charge controller (a MPPT one) from the manufacturers list or the generic one. Then I open its configuration file (a new window pop up). I go to tab thresholds
and then modify the SOC trigger OFF and ON. Because I have made some change, PVsyst tell me that I need to save as. So I do it (window pop up close) and select my new custom configuration on the list.
what is not correct ?
If I start my simulation, the report shows that the battery management control
stay at its default value (which is Discharging SOC = 0.20 / 0.45). If I check my custom configuration by open it, I can see that nothing has changed. Everything go back to its default values after saving my config to another file.