Agnes Bridel

1. PVsyst takes into account two effects that contribute to the losses due to PV module aging: The average degradation of the modules expressed by the ‘average degradation factor’. This will give raise to the ‘global degradation factor’, which is the loss expected for a given year of operation. PVsyst will perform the simulation for the full year with a single degradation value calculated at the beginning of the simulation. Therefore this degradation should represent the average degradation for the entire year. The increasing mismatch caused by the different aging of the individual PV modules. The assumption in PVsyst is that the distributions of Impp and Vmpp will broaden with time. This broadening is described by the two factors ‘Imp RMS dispersion’ and ‘Vmp RMS dispersion’. To estimate how this will impact the overall mismatch losses of the strings, PVsyst will use a Monte Carlo approach and generate randomly many PV modules according to the distributions. It will then combine them to strings and calculate the mismatch losses. From this statistical ensemble it will get the estimate of the ‘Mismatch degradation factor’. 2. Running the module degradation factor post-simulation in Excel might overlook interactions between different system components and environmental conditions that PVsyst considers. 3. You have the possiblity to run 25 years simulation using “Aging tool” in “Advanced Simulation”.

While it is possible to load TMY files with PXX into PVsyst, provided that you already have these data in hand, unfortunately it is currently not possible to generate them directly in PVsyst... Best, Agnes

Hi Edwin, If you have 10 or more years of complete hourly weather datasets, it is possible to generate TMY weather data through "Databases > TMY generation". You will have to place the multi-year data in your workspace, PVsyst will then automatically detect these files and allow you to generate TMY files. More details can be found here: Meteo Database > TMY data generation (pvsyst.com) You can then run PXX simulations in "Energy management", Project design > P50 - P90 evaluations (pvsyst.com). Best, Agnes

Hi Fabian, When the wind stow is activated, you can define the stow position - the angle between the tracker and the rest position. Best, Agnes

Hi Fabian, The wind stow strategy in PVsyst is currently a very simple model where the trackers are put into stow position when the wind speed is above a certain threshold. In version 7.4, this strategy is only available for tilted trackers and horizontal N-S trackers. The wind speed direction is also not taken into account at the moment since this information is not easily available. We are working on improving this feature and should allow more flexibility to this function in future releases. Best, Agnes

The release is currently scheduled for Q2 2024.

The PVsyst standard format must adhere to the specifications outlined in the help page titled "Meteo database > Import meteo data > PVsyst standard format for hourly meteo data." For Solcast data, you can import it directly when creating a geographical site. Refer to the help page "Meteo Database > Import meteo data > Solcast data > Importing Solcast TMY data" for detailed instructions. If you have a Solcast data file on hand, you can import it through "Databases > Custom file."

The hourly output file generation is available if this option is activated in the original simulation. This can be done through “Advanced simulation > Output file”. When this option is activated, you can run the multi-year simulation again in aging tool and the output files will be in the “UserHourly” folder of your workspace.

Hi, The upcoming major release PVsyst version 8 will feature Meteonom 8.2. Thank you for your support and patience.

Hello, Multiple year data will automatically appear in the aging tool window when these data exist in your workspace. You will first have to download or obtain the multiple year data of your location and place them in the Meteo folder of your workspace. Note that the files should contain a full year of data for them to be recognized in the aging tool. Best regards,

Dear Saeed Zubair, This seems to be a time shift related issue. If you are importing a custom meteo file, you can define the appropriate time shift in the "Date > Time shift" section. You can refer to the help page "Meteo Database > Notes on meteo > Meteonote7: Time shift in imported meteo files" for more details on this topic. If you require more assistance, please send your meteo file to support@pvsyst.com. Best regards,

You have the possibility to export hourly results in "Advanced Simulation > output file". In this window, you can select the simulation variables and hourly results to be exported. After running the simulation, the results will be exported in csv format and you can find it in the "UserHourly" folder in your workspace. Best regards,

Dear @dtarin, thank you for pointing out this error. The display error was identified and will be corrected in the upcoming release. Best regards,

In PVsyst, there are 2 effects that contribute to the losses due to PV module aging, i.e., Average degradation of the module, and, increasing mismatch caused by different aging of the individual PV modules. The increasing mismatch is hard to access due to lack of literature. PVsyst assumes that the distribution of Impp and Vmpp will broaden by time and this broadening is described by the 2 factors: "Imp RMS dispersion" & "Vmp RMS dispersion". Very few studies are published on this topic and no general values or models exists yet. The default value in PVsyst is 0.4% and is meant to be compatible with typical warranties given by the PV module manufacturer. PVsyst uses a Monte Carlo approach to randomly generate many PV modules according to the distributions. It will then combine them to strings and calculate the mismatch losses to estimate the "Mismatch degradation factor". With the Monte Carlo method available in PVsyst, you can put the values that you think is suitable. Best regards,

It is currently not possible to run solar glare analysis in PVsyst. This feature is currently under development will be included in the next major release. Best regards,