Pranav Maheshwari Posted November 30, 2023 Posted November 30, 2023 Dear Team, I am trying to simulate following system with S1200 optimizer and SE66.6K/SE100K-EU-APAC/AUS Unit (400V) with 750V input voltage: 9 strings of 18x2 modules: orientation 1 1 string of 19x2 modules: orientation 1 8 strings of 19x2 modules: orientation 2 Total no. of strings are 18, which I have divided in 9 inverters (2 strings / inverter) as follows: After closing this, there is no warning. Total no. of modules (666) and AC power (300 kVA) which matches the design After this, I enter the loss parameters and simulate, which is also successful: I also save the variant: And it shows the output also: Now i close the project, and when I again open the project & variant again, this error is shown: Why is this happening? Despite the simulation was successful and I also saved the variant, then also while opening it next time, its showing this error. I have checked all the system design and detailed losses data is still there, but not showing the o/p. I have to again open the string configuration and manually assign it to inverters then only this error resolves. But again next time when we open, the error comes back. Basically I feel that its not able to store the string configuration correctly and while recalling these errors come. I will be happy to provide more details for reproducing this issue which is happening to me.
André Mermoud Posted December 1, 2023 Posted December 1, 2023 I have reconstituted your configuration. The problem is that when defining the inverter list, you have the following warnings in orange: Sub-array #1, NInv no match Sub-array #3, NInv no match This should produce an error, which doesn't appear when you do the design in this window, but appears when reopening the variant: The fact that this message doesn't appear when designing the system is indeed an mistake, but the specified configuration is well stored on the file. You should simply press the button "Adjust subarrays" and everythis will be OK.
Pranav Maheshwari Posted December 2, 2023 Author Posted December 2, 2023 Thanks @André Mermoud that worked!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now