Agnes Bridel

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,

Thank you for reaching out to us regarding this issue. We are aware of this issue and reached out to PVGIS. In the words of PVGIS team, "apparently PVGIS’ resources are overused by some users which may indeed slow down PVGIS. We’re working to mitigate this problem. Thank you for your understanding and patience." Please note that importing PVGIS data through "known fromat" in PVsyst is done through PVGIS web API, and the API performance is dependent on the availability of their servers to process the requests made. The data download option works independently of the API and therefore is not affected by the server slowdown. We will provide and update as soon as this issue is resolved. Thank you for your patience. Best regards,

GlobTrp is the global irradiance after transposition. In general, GlobTrp is equivalent to Globinc. In the case where GlobTrp < Global incident threshold (7W/m2 by default), GlobTrp is equal to 0. Best regards,

Dear Giorgos, You can do so by clicking on “Predefined graphs” after running a simulation and select to display the “System output power Distribution” graph. You then have the possibility to retrieve the data by choosing “copy values to clipboard". Best regards,

Meteonorm versions are associated to the PVsyst version. You will have to run previous PVsyst version to get previous meteonorm data, i.e. PVsyst 7.1 to use Meteonorm 7.3. Best regards,

The performance ratio is the ratio of energy produced and energy used if the system were to continuously work at STC condition, as defined in the norm IEC EN 61724. Barring normalization factors, this is equivalent to the ratio of energy produced in given conditions versus the available energy on the PV plane (for a grid-connected system). The latter is GlobInc and not GlobEff. See the help page "Project Design > Results > performace Ratio" for more information. Best regards,

This is indeed strange and we have not came across this issue for now. Could you kindly send us the meteo file that you are trying to import so that we can have a closer look on the issue? Thank you in advance. Best regards,

Thank you for the suggestion. There is indeed uncertainty contribution from weather data. However, currently we do not have a way to know the uncertainty of all different data sources. Moreover, when using measured data as weather data source, this uncertainty will depend on many factors such as the measurement devices themselves. You are welcome to send us references if you have more details on the uncertainty. We may of course consider including this factor as one of the default uncertainties in PVsyst in the future, provided we have reasonable grounds for providing a "typical" uncertainty value. The current workaround to include the uncertainty is by adding a custom variability. Best regards,

When importing data, missing values are replaced by an average of the corresponding hour of the previous and the next day. Please send your load profile file to support@pvsyst.com so that we can give you a more precise answer.

Hello, Thank you for the feedback. The information on PVGis needs to be updated indeed and necessary changes will be made. SolCast is already included in line 8 of the table and a dedicated help page is also available, refer to "Meteo Databse > import meteo data > SolCast Data". We try to keep up to date with the information from each sources, feel free to write to us for any feedback or appropriate changes. Best regards,

Hello , Thank you for the suggestions. In PVsyst, POA data can be imported through " Databases -> Custom file". The conversion protocol can be found at the help page "Meteo Database > Import custom meteo files > Conversion protocol". For the moment, the measured data must be unshaded, therefore limiting to only front-side irradiance. @itaisuez, We would suggest to import the measured data directly and the matching is then done in PVsyst with less than 1% difference (i.e. comparing the imported POA data and the PVsyst variable GlobInc. Make sure that you use the Hay model and the circumsolar in diffuse: at the time of import through the general PVsyst settings, and at the time of simulation through the project settings. As for the suggestions, including pyranometers in the simulation scene is indeed in out long-term roadmap. Best regards, Agnes Bridel

Dear Gabriel Giacomelli, This behaviour is definitely strange. Please send your PVsyst log files (menu File -> Export logs) to support@pvsyst.com so that we can further analyze the problem. Best regards,