lmackay

I would recommend estimating optimal tilt by running iterations in a basic model such as PVWatts. Just run through the achievable tilt range in 5 or 10-degree increments and build a simple spreadsheet to analyze. You could also get it more directly by looking at median solar zenith angle at your array azimuth for each interval. But either way, you'll then have to run a variant for each tilt in PVSYST and combine the results manually post-process.

Hi all, I'm looking for some feedback on the best approach when modeling a shade scene "according to module strings" for systems with Solaredge inverters and optimizers. Considering how optimizers deal with shade, is it most realistic to model the string partition as 2 modules in alignment with the series pair connected to the optimizer, or as the larger partition of the total string of optimizers? I suspect it's the prior, but I wonder if that is double-counting the optimizer benefits? Is PVSYST already accounting for the optimizer behavior in the other calculations? How do you all handle these types of systems? Thanks!

Any progress on this? It's been nearly a year, I have PVSYST up-to-date, but still no M1600 optimizer in the database. At this point the project is built, so clearly the product is real and available. It's problematic when we can't replicate built system architecture in the software.

Any advice on how to deal with simulations which require optimizers not available in the PVsyst database? I currently need to run simulations with SolarEdge P1101 and M1600. PVsyst license is up to date at 7.2.8 and they are not in the database. Is this a delay of manufacturers sending data to PVsyst, or of PVsyst not updating database? Since users cannot add or modify optimizers, it's very important that any commercially available units be added in a timely fashion.