dtarin

Only shows for beam component.

There is also an IAM loss accounted for in GlobBak.

Is the surface you are placing them on flat? Is there sufficient spacing between modules so they dont overlap? you can place them on a flat surface, then move them over and onto the roof.

Backtracking is based on sun height/angle for the site's location. It does not backtrack according to terrain conditions. Check your results with irradiance optimization checked under orientation menu to see if that helps.

It works in 7.2.6.

You can open multiple instances of PVsyst. I wouldnt work on the same variant you have running, but other variants and projects work just fine.

Manually calculate PR and include the rear-side irradiance with the front-side irradiance.

+1 Sub-hourly clipping is missing from PVsyst estimates, which can be non-trivial

Tilt 90 Azimuth -90 to face east, 90 to face west Collector bandwidth is length of module Not sure on rear side shading losses

I assume you are modeling them four in height? So 4x20, 4x10, 4x5? This is one misalignment between PVsyst and PV plant design; PVsyst doesnt have a way to model fixed tilt with terrain or as-built table sizes and proper partition sizing, leading to an underestimation of electrical shading losses. In your case, I would model as follows: 4x20 Table - 4 h x 1 w partition 4x10 Table - 2 h x 1 w partition 4x5 Table - 1 h x 1 w partition If half-cell module, 100% electrical effect; if full-cell, maybe less than 100% (when oriented landscape). PVsyst should really work on this shortcoming in the software, as it has been present for years. Allowing and calculating for fractional partitions could be a short term fix.

Hi Scott, I would recommend to first search the forum, as there are years of questions already answered that may be the same as yours. The PVsyst youtube account also has some basic, introductory content. https://www.youtube.com/c/PVsystTutos/videos

There is already a thread on this topic.

Create the zone and populate the modules in one direction, unclick the zone icon, select all of the modules, copy them, then paste next to the existing modules, press control + G to change their tilt/azimuth at same time to orient them to new direction. See Your table length/partition should be defined based on your string size as close as possible.

New versions are backwards compatible. It's the reverse that is not (old to new). Most manufacturers, third party labs, etc. will make sure their files are compatible with PVsyst.

The variable name in PVsyst is GlobBak and it is the rear irradiance after shading, before the bifaciality factor is applied. The shading loss on rear side has its own output variable.

Correct. You can use a weighted average of the N-S slopes to capture overall N-S slope, which may be a gain or loss.

There is nothing in the release notes regarding PVGIS. I would suggest upgrading to 7.1.8 and trying it (https://www.pvsyst.com/previous-versions/).

E-W slope can be captured. When backtracking, the N-S tilt angle must be the same for all trackers. So E-W yes, N-S no.

For issues such as these, include your PVsyst version in your post. I have tested the same coordinates in 7.1.8 and it is working.

Inverter Loss over Nominal Power, IL_Pmax

Is the inverter in the model the same as the one in the field? Post a snapshot of your PV Array characteristics if you wish. It may be that the inverter has a curtailment setpoint preventing it from producing above 8kW. In this case, you will want to use a grid limit in the model. You can do this in excel to the 8760, limiting the inverter output to 8kW, or inside PVsyst under the energy management menu and apply at the inverter level. Uncheck "account as a separate loss" to include this in the "inverter loss over nominal power" loss factor.

Wind turbines are available in 7.1 and later, I am not sure if 7.0 has them. The other option is to create an object manually that resembles a wind turbine (or whatever object you need) in PVsyst and save as separate object.

The aging tool is located under advanced simulation. From there, you can generate a report with the information as you have shown.

No impact on production, just a label.

PVsyst automatically detects this. It does not seem that you can change it in the results overview (something PVsyst can maybe correct later). You can change what is displayed on the report under report options, however.