dtarin

A monofacial fixed tilt test with two arrays with different ILR, orientation, and external shading had a difference of 0.05%, comparing the individual runs summed with a single combined run, which is reasonable (all on fast sim). With only a glance, it looks in the shading calculation for the 20/15 orientation there is a difference in the attenuation for diffuse and albedo in the combined run vs the individual run.

If PVsyst, removed the restriction to allow identical orientations in the orientations for fixed tilt systems, and allowed multiple orientations with tracker systems under orientation and enabled the option in the 3D scene, then users could model subarrays with independent shading. If there are other restrictions in place for trackers such as with POA or bifacial calculations, then for tracker systems, a straightforward implementation would be to require all orientations to be of the same orientation.

The ability for PVsyst to model different portions of a plant in the 3D scene to different subarrays is possible, it's already there for fixed tilt systems, there are just restrictions in place preventing it from working for other systems. For example in fixed tilt, several orientations must be defined in the orientations menu and they must be unique orientations, otherwise it prevents you from moving forward. Computationally there is no reason why we couldnt define two orientations at the same tilt and azimuth, its just a restriction. But if you had two unique orientations in the orientations menu defined, then in the shading scene , you could allocate one or more portions of the plant to different subarrays. I presume that when doing so, the shading calculations will be specific to the modules defined in the orientation menu of the 3D scene and thus apply correctly to the subarrays when using according to strings. For tracker systems, this is not possible, but if the several orientations menu in the 3D scene was enabled and the user allowed to create orientations with certain tables and allocate to different subarrays, then this would separate out the shading losses and be very convenient and moving the software forward to more realistically capture inverter level behavior to match operational data.

Someone reported a difference on the forums . I would run a test, find the delta, then apply in MQF or post-process.

Have you placed the modules on top of a building or some object in PVsyst? Looks to me that there is intersection between an object and the modules.

Secondary

First solar modules have a linear response when shading is perpendicular to the cells. For flat sites and uniform shading, select linear shading. If there is terrain shading or other non-uniform shading, it may be appropriate to select a partition according to the string size with a low electrical effect, but ultimately depends on your site conditions and installation type.

1P trackers typically between 1.4 and 1.6m from the ground, 2P trackers start 2m, but it of course depends on the project specific requirements. 18" of clearance from ground at max tilt is common.

Increase the number of modules to account for the correct total tracker length or approximately close. The difference in shading calculations with and without actual gaps is not significant.

You have answered your own question, temperature is considered in the output and losses due to temperature are shown in the simulation reports.

Each inverter will need to be in a separate sub-array.

What do you mean by unlimited single axis tracking system? Did you model this in the 3D scene editor, or did you use the unlimited sheds method?

Depends on the size of the plant and if there is an O&M service involved, etc. If its utility-scale with O&M (guaranteed response times, etc.), 2% is good. If it is a small site, you might want higher.

It is set by the user under detailed losses.

Horizon files need two columns, azimuth and height in degrees. Horizon data is not usually from a TMY weather file. For horizon data you can use PVGIS from within PVsyst. The PVsyst format there is for when you have Horizon data from another source.

Place the OND file here, restart PVsyst \PVSyst Projects\PVsyst7.0_Data\ComposPV\Inverters

I have created a dummy OND file for power sharing and modeled together with a non-modified OND file. The non-mppt share inverter is showing up in the power sharing list and giving an error. I dont think the inverter should be listed in power sharing. The inverter is listed in the error and noted below with 1 mppt

TMY p50 for standard energy estimates. you can also import the time-series data if you wish to run time-series models.

In PVsyst, the inputs for HV transformer are in MVA. Ensure that the percentages shown match what you have there. PVsyst should then calculate correctly. Your MV waterfall loss looks appropriate for the inputs.

Go to advanced sim > output file, select to create a file, select the variables you wish to include. Then, go to batch sim, set up your items there, and confirm the output variables there in the last tab.

Grid connected PV system. After entering in your system and losses, under advanced simulation, you can run batch mode to run multiple simulations and specify the tilt angle to use. Output the results to excel file (.csv).

Run yearly simulations at every tilt angle, analyze the 8760 at each hour to determine tilt associated with desired current.

In the heterogeneous array tool, we can select modules at a given string size and view the graph, but it would be very useful if we could also export this data to csv, similar to how we can when viewing the graphs in the PAN file. If there were the ability to select string size and # of strings in parallel from the PAN file with the different variable options that are there, that would be even better.