Linda Thoren

The last generated Monte Carlo values is for year 30. You can still simulate a degradation beyond this, though after 30 it is assumed to be a linear trend.

In the coming PVsyst version 8.1, several input parameters can be defined as hourly values via a .csv file. This will allow snow coverage (in %) to be specified on an hourly basis if desired. However, we are not currently implementing more advanced snow-coverage models, though this is on our roadmap for a future version.

Hello, If you for instance have self-consumption or storage, System production production is not necessarily the same as E_grid. What version of PVsyst are you using? There may be differences due to rounding of results when saving files. However, these differences are necessarily negligible. If they are not, there may indeed be a problem and feel free to export your project as a zip file and send us an email to support@pvsyst.com

Hi, The Monte Carlo values are currently generated for up to 30 years. For simulations extending beyond 30 years, a linear trend based on the last two data points is applied. Thank you for your feedback. I’ve noted the interest in generating Monte Carlo values over a longer horizon and potentially this can be developed for a future version.

Hello, 1. In version 8.0.19 we have been improving the orientation grouping function. Which version are you using? What tolerance is set in the project settings? 2. The issue could from the fact that you can define multiple gaps for your tracker in PVcase, motor gap, joint gap, horizontal gap between modules and vertical gap between modules (though normally this would lead to the opposite issue, that more modules are placed in the 3D scene than in the system definition). PVsyst we handle only horizontal gap between modules and vertical gaps between modules, so the PVC file doesn’t contain the other information. The PVC file only contains the total length/width of the trackers and the horizontal/vertical gaps between modules. Did you check the "Terrain following trackers" checkbox in the "Frame creation" tab in PVcase? This setting should break the PVcase trackers into multiple smaller trackers for PVsyst (according to the defined gaps), placing the modules at the correct location. In this case, PVsyst will divide the tracker where the motor gap is. I also notice that 163 tables are not defined by modules, potentially the mismatch comes from these tables. Kind regards

Indeed this is a limitation we still have. The electrical shadings in general in PVsyst are further explained in the following video:

Hello, At the moment, small shades at the center of pv modules are not treated and do not create electrical shadings. This is something we hope to improve in a future version. Kind regards.

This is not a precise science and can be site dependent. In order of magnitude, one could consider that a site within 10km distance can use the same .MET and .SIT without issues.

In the detailed losses window, you can set 1% for the first year degradation as a LID loss in the "Module quality - LID - Mismatch" tab and 0.44% as an average degradation factor in the Ageing tab.

Dear Diana, You can generate graphs and plots through the detailed results window (pre defined graphs or hourly graphs for a large amount of simulation parameters). In the Advanced Simulation window, you have additional freedom to create custom plots that also can be included in the report. Another possibility is indeed to create an Output file with the relevant parameters and do the analysis in an external tool. Kind regards

The bifacial model presently available in PVsyst is based on a simplified 2-dimensional representation, with similar assumptions as the "unlimited sheds" or “unlimited Trackers” PVsyst simplified calculation. This approximate calculation may be extended to a 3D scene, provided that this 3D scene is sufficiently well represented by the "Unlimited sheds or trackers". You can read more about the bifacial model conditions in the following help page: https://www.pvsyst.com/help/project-design/bifacial-systems/2d-bifacial-model-conditions.html With multiple orientations and sub-systems with different table width, you can in version 8 create new "orientations" in the orientations window and group all the tables with similar characteristics in a sub-system/orientation, and apply the bifacial model to each sub-system in the system window

Hello, You find a full explanation and a summery of common cases in the following PVsyst help page: https://www.pvsyst.com/help/project-design/shadings/electrical-shadings-module-strings/partition-in-strings-of-modules.html?h=partitio#up-to-748

Hello, You can find an article in our help that discuss the PR calculations: https://www.pvsyst.com/help/project-design/results/performance-ratio-pr.html?h=pr Kind regards

When creating your site, you can simply write or copy your values in the "Monthly weather data" tab

In your print screen you see all the details of the number of modules in each sub-array and each table assign to the defined orientations. The difference between your print screen and the video is that the folders are collapsed. Click on the small minus icon collapse the folder and see the total of modules in the system/3D scene for each orientation. If they do not match, you need to add/substract the modules defined in the 3D scene, or in the system.

In the 3D scene you can define each table by modules. In the Orientations management you find detailed information about what is defined for each orientation In the following youtube tutorial you find examples of how to define a 3D scene and how to navigate in the window: On our website you can do a request for a training sessions on various topics: https://www.pvsyst.com/en/training/consulting/

Hello, The error message indicated that the 3D scene and the system definition does not match. For instance, in the first orientation (tilt 5° and Azimuth 180°), 1564 modules are defined in the system but only 1427 in the 3D scene. Verify also that the orientations, are correctly defined. In PVsyst, Azimuth of 0° is towards the equator, and 180° thus the opposite orientation (North is the northern hemisphere and South is the southern hemisphere)

Please send your project to support@pvsyst.com and we can have a closer look. Kind regards

Indeed, the unlimited sheds only consider the row to row shadings. For a more detailed analysis of the shadings from objects such as trees and buildings, you can define a 3D scene and simulate the electrical shadings with the module layout. The following youtube tutorial illustrates haw to create a 3D scene, and the following link to our help page, describe how to define the module layout: https://www.pvsyst.com/help/project-design/shadings/electrical-shadings-module-layout/index.html

hello, In the print screen you have activated the "multi MPPT feature" and defined 3 MPPTs, though your inverter has 2MPPTs per inverter, this 1.5 inverters with a total of 15kWAC for a nominal PV Power of 13.9kWp. The following youtube tutorial shows in detail how to define your system configuration (in version 7):

Hello, In the second print-screen, you must activate the option "Use the sharing of Nominal Power between MPPT inputs of a same inverter". You find a full tutorial of how to use this tool (version 7) in the following youtube video: Kind regards

Hello, Thank you for reaching out. Please first verify that you are indeed simulating the first year (that in the aging tab in the detailed losses window, year 1 is defined). What PVsyst version are you using ? Some discrepancies and rounding errors can appear Kind regards,

Indeed, the bifacial calculation in PVsyst is based on a 2 dimensional representation for regular system layout, thus same orientation, table size and pitch, to calculate how much irradiance is falling between the tables and how much will be scattered up on the back side. You can define individual orientations for each table. Though, since you need a pitch it is not yet possible to simulate a bifacial system with a single row. A possible workaround is therefor to duplicate your 3D scene so that PVsyst can detect a pitch, similar to the example below: Verify that the tables are well aligned so that indeed PVsyst detects the pitch in bifacial window. Note that the amount of tables in the 3D scene will be double what you have defined in the system and this will create a warning. You can increase this limit in the advanced parameters. In the first PVsyst welcome window, click “Settings” and “Edit advanced Parameters” and find the parameter that triggers the error message – “Shadings: absolute maximum shading/field area ratio”. This will allow you to run the simulation Kind regards

With PVsyst version 7, it was an automatic mode for diffuse shading calculations for systems that involve trackers, in version 8 the automatic mode has been removed. Now, users are required to manually define a representative tracker for diffuse shading calculations. You define a representative tracker by clicking “Tools”, “Trackers diffuse shading definition”. In this tool you can choose to calculate the diffuse shading factor for all trackers, or select a representative tracker that will be used to evaluate the diffuse shading factors You can find more details about this update and instructions in the PVsyst Help documentation here: PVsyst Diffuse Losses with Tracking Systems. Indeed, many updates and improvements has been done since version 7.2.16 that especially concerning the near shadings. In general you can find the changes that has been done in the release notes and major changes are discussed in the forum in the links below: https://www.pvsyst.com/help/release-notes/index.html#exec-1--version-801 https://forum.pvsyst.com/forum/29-pvsyst-main-changes/

Hello, This limit that the error message is referring to is in the Project setting, not the advanced parameters. Kind regards