All Activity

Hello Hakan öztürk, Please note that this forum is in English. In December, PVGIS modified their format for the TMY output, which has affected the functionality of our API. The data reading was updated in version 8.0.6. Please update to a more reason PVsyst version and this should solve your issue.

I have the following error on PVsyst 8, does anyone know how to fix it? The values are matching the datasheet.

Hello! You should divide your 10 years of data into 10 different files, one for each year. Then you can generate a TMY weather filed based on these 10 individual year in the TMY generation tool. In your workspace, you find a template for the PVsyst standard file, double check comparing to this file that you are following the requirements. You can also import your file as a Custom file is you continue having issues with the known format.

Dear PVsyst Users, Please email us at support@pvsyst.com your PVsyst LOG files (using menu <File> <Export logs>) so we can analyze what happened. Best regards.

Dear PVsyst User, Please email us at: support@pvsyst.com your PVsyst LOG files (using menu <File> <Export logs>) so we can analyze what happened. Best regards.

Same issue here. Installing by repair mode of the latest version didn´t make differences. (PVSyst 8.0.9)

PVGIS TMY butonunu seçip getir diyince bu hatayla karşılaşıyorum. Bu sorun hakkında yardımcı olabilir misiniz?

Dear Terence, Is it possible to send us the DAE file to "support@pvsyst.com" so we can also try it and check why there's a difference between the near shading and the report? Regards

The sheds spacing from the the report is different from the dae file that I imported in near shading scene which I have attached in this email. Imported dae file is from sketchup and solar panel are generated by skelion.

Also, when I tried to switch it from "custom tracker" to "all trackers", it did not correctly save this change when running the model. The report still shows "custom tracker" and the shade losses are still lower than the prior model because that custom tracker is on an edge of the mask.

In version 8.0.9, I found that when I run a model from version 7.4.8 that had a good "custom diffuse" tracker selected, it is now not masked correctly (it is on the edge). Even if I go in in version 8.0.9 and select one that masks properly, after running it, it is on an edge again. See image below. This appears to be a bug with the custom diffuse tracker masking in version 8.0.9. Can this be fixed? It is not practical to always use "all trackers" for large arrays. The problem may occur specifically when the trackers are tilted on the terrain. This problem results in erroneous production jumps close to 1%, because the diffuse shade is only half accounted for. Thanks in advance for the help PVsyst.

OND files are for inverters. It is typical to receive from manufacturer if it is not listed in database already.

Yes, this is an error in the report. This represents indeed the loss at the output MV line of the Transformer. We will correct this for the next version. When defining the wiring losses in PVsyst, the frame "Array wire loss inverter to transfo" concerns the connexions from the inverter to the transformers, and "Medium Voltage Line" the output of one transformer. The evaluation of the wiring loss is indeed a direct calculation of the loss, at each hour, according to the specified wire resistance and the instantaneous current. There is no uncertainty here, as far as the resistance is well defined. When specified as a percentage at a given power, the resistance is directly calculated from this loss (no error). The only uncertainty could be the resistivity variation according to the wire temperature: in PVsyst this is defined for 50°C, the variability being 0.39 %/°C.

Hello PVsyst Community, I am trying to import 10 years (e.g., 2014-2023) of hourly weather data (originally from Open-Meteo) into PVsyst as a single file, specifically using the Databases -> Import weather data -> PVsyst standard format tool. My goal is to have the full 10-year dataset available for PVsys's internal TMY generation. I am using PVsyst version 8.0 Following the detailed documentation (Help -> Importing weather data -> PVsyst standard format), I generated a single multi-year CSV file adhering strictly to the specification: First Line: The file starts exactly with #Weather data hourly data. Metadata Headers: Includes all mandatory #Tag;Value headers using semicolon separators. Data Headers: Includes the two required data header lines (first: Year;Month;Day;Hour;Minute;GHI;DHI;Tamb;WindVel;RelHum, second: ;;;;;W/m2;W/m2;deg.C;m/s;%). Data Format: Data rows use semicolon separators and dot (.) decimal characters. Encoding: Saved as UTF-8 without BOM. File Verification: The generated CSV file looks correctly formatted when viewed in Notepad, matching the requirements described in the Help file (See Image 1 - showing headers and first data rows). When I attempt to import this carefully formatted 10-year file using Databases -> Import weather data -> PVsyst standard format, I immediately receive the error: "This file is not a PVsyst Standard meteo file (missing tag on first line)." (See Image 2). This error occurs despite the first line being exactly what the documentation specifies and appearing correctly in the file itself. Has anyone successfully imported a multi-year hourly data file using the "PVsyst standard format" importer in PVsyst V8.0? Is there a known issue with this importer failing to recognize the #Weather data hourly data tag? Any insights on how to successfully import a multi-year file using the "PVsyst standard format" tool in V8.0 would be greatly appreciated. Thank you. İmage 1 İmage 2

Hi LauraH, Thanks for your explanation.

Hi Linda, I think, Nominal ac power should be: 0.85*140KVA= 119KVA and Maximum ac power: 140KVA in main parameter window. Regarding the no. of PCS, we can increase the pcs no. as I confirmed with the utility. The PCS only give 119kW at 0.85 pf.

Can i get the pan file of FOXESS-H3-Pro-20.0 inverter for my PVsyst?

These two import windows aren't working. Maybe there are others, I've only tried these two. PVSyst 8.0.9. I have tried clicking the other button options and used the map to select a U.S. Coordinate as shown. Is there a setting i've turned off by accident?

"Imp RMS dispersion are not comparable to a degradation factor. You should first translate into a degradation of the Pmpp. This is done stochastically by PVsyst". sorry, I still feel very confused for this topic. Can you clearly tell users how to operate and take values of Imp RMS dispersion ? Should we take 0.4% by default or other values for Topcon or HJT /IBC different solar modules？Or is there any relevant basis to support filling in this data. thanks!

Dear Eric, 50k polygons are really too few for large power plants on complex terrain. We also often work on 100MW+ projects and it would be a life-saver if the terrain polygon number would not influence the speed of the software as a whole. Is there really nothing that can be done for this? We have software that can do real-time rendering of millions of polygons... Please consider this, best regards

I have a 3D Scene with mixed orientations attached to the same sub-array but I am getting this error for the second/smaller orientation of modules. How do I fix it? This is PVSyst 8.0.7 and 8.0.9

@Michele Oliosi Thanks for the response. I'd like to also add some observations about how this factor changes with number of rows. The fewer rows there are, the more "scattered" the factor is for both negative and positive PhiAng. See below some graphs generated in PVsyst 7.4.8. Though these were generated in v7, the scattering is also observing in v8. I'd like to know what's causing the scattering and if this is intentional.

Good afternoon, I am working for a client on a PV project which is composed by several plot. My client provided one .pvc file per each plot of the project. When I upload the different files, PVsyst automatically places the perimeter in the centre of the coordinates, overlapping it with the previous one. Is it possible to upload all the .pvc files in the same 3D scene, respecting thier relative position? Or is it better to merge all the files and then upload one single (complete) .pvc files? Thanks in advance

Dear Nikoloz, We recommend using a maximum of 50k polygons for the ground data. Exceeding this number will make PVsyst slower without significantly improving the accuracy of the simulation results. The import ground as CSV provided by PVsyst has an option to simply the geometry to meet with the 50K limit, you can either use this tool or find a way to reduce the number of polygons in your 3DS file. Regards

@nicolasrata indeed I think you have answered correctly here.