Linda Thoren

Hello, We are aware that since December 18th, PVGIS has modified their format for the TMY output, which has affected the functionality of our API. This will be corrected in the next version that will be released this week. You can also see a work around in the following post: Kind regards

Hello, We are aware that since December 18th, PVGIS has modified their format for the TMY output, which has affected the functionality of our API. This will be corrected in the next version that will be released this week. You can also see a work around in the following post: Kind regards

Hello, We are aware that since December 18th, PVGIS has modified their format for the TMY output, which has affected the functionality of our API. This will be corrected in the next version that will be released this week. You can also see a work-around in the following post: Kind regards

Hi Sydwell, The idea with the Custom file import is that you will customize the import based on the specific format of your file. Thus in this tool, you will be prompted to define that for instance 4 lines should be skipped to arrive at the data, the date is found in column 1 and has de format YY/MM/DD HH/MM, the GHI is in column 4 and the temperature in 7 etc.

Good day Sydwell This can be done through importing a Custom file. Click Databases, Custom file, choose your source file, define your site and click New to start the process of converting the source file to a format that is supported by PVsyst. In this new window you have to define variables such as the file's time step, the format of the date and in which column you find what information. By saving and running a conversion of the data, you can then use this new file in your Project simulation. Kind regards

The best way in general to import and export projects, is to first export the project as a .zip either by clicking "File" and "Export project" in the welcome window, or "Export" in the Project. Like this you are sure to include all the needed files when you then import the project to another work space. With a complete project file you can import by clicking "File" and "Import project" or similarly click "Import" in your project. If you only have the .PRJ and .VC1, you can import a folder containing these files similarly to how you import other components, through the "Import components", or by placing the files in in the "Projects" folder in your workspace.

Dear Stewart, Do you mean that you have a .SIT and .MET already that you want to use in another project in another workspace rather than create new ones? In this case, one way is to use the "import component" function, that you find under "File" in the PVsyst welcome window and import a folder containing the relevant files. Another way is to simply to open your current workspace (you find your workspace in the bottom right corner in the first welcome window in PVsyst, by clicking on the link you find a folder structure that is saved on your computer) and place the .SIT file in the folder "Sites" and the .MET file in the folder "Meteo". Like this, the files are saved in your database and you should be able to find them in the list of sites and weather files. To create a site file and weather file in general, I invite you to read the tutorials available on our website, as well as the video tutorials on the subject in the links below. https://www.pvsyst.com/pdf-tutorials/

Hi, Unfortunately this function is not available yet and indeed to see the production of each individual PV field you have to separate the fields into individual variants. Kind regards

Dear Mojailat, Indeed, there is not yet a straight foreword way of defining unavailability per sub-array. This use case has been identified and it is on our roadmap to add this function for a future version, though it will not be available in the near future. Kind regards and thank you for highlighting that this indeed would be a valuable feature

Hi, On the "Basic data" page of the PV module's definition, the frame "Internal Model result tool" allows to display the main electrical characteristics under chosen operating conditions. This tool is only informative. It doesn't hold any parameter for the definition of the PV module. To change the threshold that triggers the error message, go to Project settings, Design conditions, see below Kind regards

Dear Vasil Janevski, Yes indeed, in PVsyst we have 3 storage strategies and the "Peak shaving" correspond well to what you are describing. Following youtube tutorial further explain this feature in PVsyst: Kind regards

Hi, It is difficult to evaluate without more information about your system and the layout, it could well be that there is not much shading and thus normal that the shading would be 0%. Please export your project as a .zip file to support@pvsyst.com if you wish that we have a closer look. Kind regards

Hi, With the latest PVsyst version, automatic mode for diffuse shading calculations for systems that involve trackers has indeed 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. Kind regards,

Dear Nikoloz, P90 estimations rely on yearly data. Calculating P90 for monthly values is not advised. Yearly weather data has variation (around 3-4% RMS), while monthly data can vary significantly year-to-year, leading to unreliable probability profiles for each month. You can read more about the P50-P90 evaluations in the Help in the link below: https://www.pvsyst.com/help/index.html?p50_p90evaluations.htm Regards

Hello, Indeed, with PVsyst version 8, automatic mode for diffuse shading calculations for systems that involve trackers has indeed 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. Kind regards

Hi, Indeed, a system with different sized tables are not suited for the bifacial 2D model. In the new PVsyst version 8, you can possibly work around this by creating 2 subsystems, one for all the panels with a certain table size and a second for the rest. In the orientation window, define two orientations (even though they have the same tilt and azimuth) and in the 3D scene, separate the tables per table size and assign them to the 2 different orientations you have defined. Like this you can define the bifacial parameters (in the system window) for each "orientation" (sub-system) and thus get around this limitation. Kind regards

Hello Jig, Indeed your workflow is correct and it is not clear to me what the issue could be, if it is possibly the datafile that is strange our something in the PVsyst reading of it. I note that there is no time zone value (though a local time) in your file. If you add the correct time zone in the data file, does in affect the .MET file? If you look at the Monthly best clear days graph, do they look correct and correspond to the values in the data file? Can you please send us your specific data file to support@pvsyst.com and we can analyze this in more detail. Kind regards

Indeed this is now possible in version 8! You should define two orientations, one in west and one east, either with unlimited sheds (that doesn't require a 3D scene definition) or fix tilted planed where you should also define the layout in the 3D scene. Define each sub-system in a sub-array and define the bifacial parameters for each sub-array (height above ground etc)

Hello, How have you imported this weather file? through the project window, known format or a custom file? where is your site? If there is a time shift you are recommended to re-import this file and include a time shift in the Date tab (if imported as a custom file, though Meteonorm data and NREL data can be imported with correct format for your site automatically normally if imported directly from the Project window, or as a known format If you have imported your file from the project window or as a known format, please send us your project to support@opvsyst.com and we can review the issue in further detail. Kind regards

Hello, As a contrary to the usual architect's conventions, in PVsyst we consider: In northern hemisphere, the plane azimuth is defined as the angle between south and collector plane. This angle is taken as positive toward west, i.e. goes in the antitrigonometric direction. => south azimuth = 0, north azimuth = 180°, west azimuth = 90°, east azimuth = -90°. In southern hemisphere, the plane azimuth is defined as the angle between north and collector plane. This angle is taken as negative toward east, i.e. goes in the trigonometric direction. => north azimuth = 0, south azimuth = 180°, west azimuth = 90°, east azimuth = -90°.

Hi, How have you imported this weather file, where is your site and what version of PVsyst are you using? In general, if you try to import Meteonorm data directly in your project, or as a known format this shouldn't be an issue. If the file is imported as a custom file, a time shift can be added in the Date tab. The denomination of a given time interval in PVsyst is always defined as the beginning of this of this interval, contrary to Meteonorm where it is in the end of the interval. Perhaps the issue could also be if you are in-between two time-zones. If you don't find the source of the issue, please send your project/ site and weather data to support@pvsyst.com and we can have a closer look at it. Kind regards

Hello, The .SIT file includes the coordinates of your system, if the coordinates have changed it is possible that the far shading (the horizon line) have changed too since this is also based on the coordinates of your system. Kind regards

The performance of your system will degrade with time. The goal with these tools is to evaluate the PR after a certain amount of year. The PR will not be consistent if you are including a degradation and the PR will be a result of the simulation. The aging is further explained in the following youtube tutorial: To simulate the performance of your system every year and evaluate the production after 25 years of production you can also use the aging tool in the advanced simulation:

Yes indeed, the performance ratio (PR) will change if the system is aging.

Hello, The P90 statistical estimations are based on yearly values. P90 for hourly or daily values (or even for monthly accumulations) doesn't provide meaningful results due to the high variability of short-term weather patterns. Kind regards