jonasf

Hi Muhammed, Let's say I have a PV plant divided in 2 sub-arrays, each on with 1 inverter. I would like to simulate to failure of one of the two inverters for a given period of time (5 days for exemple, until the inverter can be replaced). But I can't make 2 simulations (1 with the whole system and 1 with only half of the system) and compare both since I will loose the SOC information of the battery pack. Is it clearer? Anyway, with your advices, I could run the simulation using my 3) solution (first post) by modifying the parameter "Best Ktcc days have strongly low values". It didn't trigger error anymore regarding the modified weather file. I have another question regarding the SOWcycle and SOWstate this time: I can't figure out what represents those 2 values. I read the documentation and understood that if one of those 2 values reach 0% the battery needs to be replaced, but in this case, what is the capacity of the battery? I found this answer on the forum (https://forum.pvsyst.com/topic/2137-loss-and-efficiency-in-battery-at-storage-systempeaking-shaving-with-grid-limited/?do=findComment&comment=9666), it lets me think that if any of SOW values reach 0%, the battery capacity would be reduced to 80%. It is true? And if yes, is this parameter editable? Many thanks.

Hi, I'm currently designing a standalone system for which i would like to simulate failure of a device. There will be 2 regulators and i want to simulate the failure of one of the two, divinding the production by 2 for a given period of time. Then, I want to see the evolution of the SoC in this case. Is there a way to achieve this goal? What i have looked for so far: 1) There is a unavailability parameter that could give me some clues but it seems to be only available for grid-connected system. 2) Looking for a way to directly import a custom Earray file (simulating a loss of production by 2 for the given period of time) --> not found. 3) Creating a custom weather file to directly divide by 2 the global horizontal irradiance for the given perdiod of time --> gave an error relative to the clearness index too low (not even sure that this method could give consistent results). Thanks.