Adrien Villoz

Dear User, Please contact us directly through the contact form on the main PVsyst website, we won't be able to help without the files that you are trying to import.

Dear User, It is unfortunately not possible to import the tracker angle together with global in plane right now, the only possibility is astronomical calculations and/or backtracking, based on the coordinates and the time stamp of your data.

Dear User, I can't reproduce your problem for these coordinates. There seems to be a problem with your windows system: Meteonorm requires both the latest .NET runtime and latest VC++ Redistributable from Microsoft. You can try to reinstall PVsyst and make sure to install both prerequisites: .NET runtime and VC++ redistributable. Without those prerequisites, Meteonorm cannot work correctly. Alternatively, you can install them manually: Microsoft Visual C++ Redistributable for Visual Studio 2022 (both x86 and x64) from https://visualstudio.microsoft.com/downloads/ at the bottom of the page in “Other Tools, Frameworks, and Redistributables”. Make sure to install them with administrator rights. .NET 6.0 runtime from https://dotnet.microsoft.com/download choose the “Run desktop apps”, again both x86 and x64. Install them with administrator rights also. After reinstalling, make sure to reboot your system before trying in PVsyst.

Dear User, The update is planned, but we haven't started to work on it yet, so I don't know when it will be ready.

Dear Scrchd, This is a known issue that happens with users that have non-ansi characters in their username in Windows, due to the external library we use to display PDFs in PVsyst... the issue is already fixed internally, we will publish a new version as soon as possible. In the meantime, there are a few workarounds that you can try: - reinstall version 7.2.11 (uninstall version 7.2.12, then reinstall 7.2.11: https://www.pvsyst.com/download/bin/PVsyst-7.2.11.24303-setup.exe you will not lose anything by doing so) - or create a new user on windows that only contains characters in the A-Z range just to generate the PDF - or when you get the error message, keep it open and browse in Explorer to “C:\Users\*****\AppData\Local\PVsyst\Temp\” (replace ***** by your user name) where you will find the temporary PDF file that was created. Copy this PDF somewhere else, and rename it the way you want. When you press “Ok” in the error message, the temporary PDF is deleted (hence why you need to copy it somewhere else).

Dear Katherine, Most of the radiation data available today are outputs of models, which are already interpolations to match a full hour: data with a time stamp at 9:00 will cover 9:00 to 10:00, which means the solar geometry corresponds to the middle of the hour, 9:30. Some data providers specifically state that their data are instantaneous values (e.g. NSRDB and PVGIS). For this type of data, a time stamp will be considered as the middle of its time interval: for hourly data, a time stamp at 9:00 will correspond to data from 8:30 to 9:30, so the solar geometry used will be at 9:00. PVsyst does not do any interpolation, if the input data does not have the time shift specified, there might be a warning (or an error if too high). In the case of a time shift that only gives a warning, the simulation is allowed and it will compute the solar geometry at the middle of the hours. This can lead to errors in the results if you compare with production measurements. If the data contain a time shift properly defined, then PVsyst will compute the solar geometry for the middle of the interval that was shifted. For example a time shift of -15 minutes will make PVsyst compute the solar geometry for the middle of the interval, for hour H, the interval is (H-1):45 to H:45 and the solar geometry will be computed at H:15.

For future users who encounter this problem: The error 5 is due to restricted internet access (firewall and/or proxy) in an unwanted interaction with the included Meteonorm database. It has been fixed in version 7.2.9. For other internet access problems, remember to configure your firewall and/or proxy properly with the information available in our FAQ: “Web services for all PVsyst functionalities” - https://forum.pvsyst.com/topic/2524-web-services-for-all-pvsyst-functionalities/?do=findComment&comment=6420

Dear DavidFon, In the actual version of PVsyst, you can transform your file into a PVsyst standard format to import multiple years of data. It is described in the help, there is also an example in the "Templates" folder in your workspace (if there are no files, go to the Workspace management and reload templates).

Dear ramalochan.apps, This has been fixed in a subsequent version of PVsyst, please update to latest version.

Dear Rafael Santos, This is already fixed in a subsequent 7.2 patch.

Dear p.iaquinta, Questions about changes in Meteonorm have to be asked to Meteonorm directly, PVsyst has no control over the data provided by Meteonorm.

Dear shubham, You already answered your question: the global transposed irradiance is obtained by applying the Perez model (or Hay model if you changed it in the settings) to the hourly values of horizontal global and diffuse irradiance.

Already answered by email: Your coordinates work fine by removing the comma between both coordinates. The comma is not needed since each coordinate is properly written with N and E. The case where there is a comma will be added for a future version of PVsyst.

Dear awindenberger, This happens when there is only a single table of modules in the 3d shading scene with the bifacial model. After version 7.2.12, this case will not be allowed any more as it is not treated by the 2D view-factor bifacial model actually implemented in PVsyst.

Hi chang0423, This issue will be solved in next version 7.2.12. As a quick reminder: the pre-sizing tools are meant only to have a very rough estimate for a system, it is by no means a simulation. Reports generated from the pre-sizing tools should never be used for an actual project.