dtarin

There are more variables to consider on a site specific basis, and when comparing different locations. If you are looking at a single site, and comparing changes in GHI year to year, a decrease in GHI may correlate to an increase in diffuse, lower temperature, etc, which depending on system and equipment, may not give the relationship you've calculated. It also depends on system design. High DC AC ratio site may not give the same result, shading losses may be different, etc. So, not quite, at least we don't, due to the uniqueness of each project.

Use MPPT share. When you select MPPT share, it will go by the number of MPPT inputs, not inverters, so total you will have 18 (for each inverter).

0-9, A-Z from what I've seen, so 36? Never tested it though.

That is interesting. Without knowing the details of the simulation (partition size, tree height and design, table dimensions/orientation, location,etc), I would say that it is likely that as the modules move in closer to one another, they experience a higher near shading beam loss, but no additional electrical string activation. Since the beam loss increases but there is no additional string activation, the string loss comes down since that additional area of the array is now a light loss rather than an electrical one.

Unless you model a single row, you cannot.

Generally we see the PF of solar plants set to leading, to absorb vars from the grid, so var flow direction is opposite of the watt flow direction when the solar plant is producing. The utility should send a letter specifying the requirement according to the interconnection agreement.

Set to realistic view, click view > save the view for the report, save and close, run model.

Check the values to see if they match.

It can be considered a shading object if you check the box in the objects properties "enable object to cast shadow" or something similar. Then it will be considered solid object. If you use it, without this check, it will still change the module placement and as such, their shading, POA, etc.

I was able to run with your settings. Under project settings, change "limit overload loss for design" to 60% (something higher than your DC AC ratio), and in hidden parameters > System Design Parameters, Losses, Shadings, scroll down to solaredge section and change SolarEdge Inverters: Authorized Overload to 60%

Run with 20, set a grid limit to match lower # of inverters? Dont separate grid limit losses so they show together with clipping losses

Which average temperature are you referring to?

Perez is the standard in industry. See additional posts here: https://forum.pvsyst.com/viewtopic.php?t=4596

I cannot say, in my test (v6.84) there was no change to GlobInc. In a fixed tilt system on flat ground (no terrain), the only parameter that will affect GlobInc is system tilt if I recall correctly.

https://forum.pvsyst.com/viewtopic.php?f=30&t=483&p=2124&hilit=perez#p2124 https://forum.pvsyst.com/viewtopic.php?f=17&t=477&p=2104&hilit=perez#p2104 https://www.pvsyst.com/help/models_meteo_transposition.htm?zoom_highlightsub=transposition

Yes, just overwrite the constant loss factor Uc under Field Thermal Loss Factor in the Detailed Losses menu.

Yes it is possible. Under batch settings you will select specify different meteo files under parameters selection. Then use the batch file which is created and modify it so that it includes 20 lines in your case for each meteo file.

It depends on the transposition model you have selected for your simulation. The Perez transposition model is the default for PVsyst, and that is where you will find the formula for converting GHI to POA

Is there terrain? Fixed tilt or tracker?

If i recall correctly to set PV materials you need to use google sketchup

What is the nature of your shade scene? Is there terrain and/or other shading objects? Are you modeling in unlimited sheds or with a 3d shade scene?

PVsyst POA is dependent on your weather file, location, and system design. There are a lot of questions one could ask, such as how well does your PVsyst model match actual site conditions, is there complex terrain for this site in question? If you are comparing measured to modeled and the results are way off, then perhaps you have an inaccurate weather file. Does GHI/DHI in your model match measured? If it doesnt, you shouldnt be expecting GlobInc to match measured. If your weather file is TMY, that is a P50 weather file.

https://www.pvsyst.com/previous-versions/ Find version that will work with the met file you have, install as parallel installation. Did you first try just dropping the file or importing the MET file first? Open 6.8, select file > import components, find your MET file, import.

If you can't directly drop it into 6.8, import it into an older version of PVsyst (create a project) then export the project . Then import the project into 6.8. You can install an older version of PVsyst as a parallel installation and use both versions of PVsyst if you only have 6.8 currently.

Versions 6.8x cannot be used in earlier PVsyst versions. If the there is no version incompatibility, just drop the .met file into your meteo folder: C:\Users\COMPUTERNAME\PVsyst6xx_Data\Meteo