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