All Activity

I had this same problem with batch output files. There is data in every column A, but sometimes also in B or C.

Dear Oussama Belarbi, Thank you for bringing this to our attention. It appears that this issue is a bug introduced in the current version. The issue is reported and we will work to resolve it in a future version. In the meantime, you can either revert to a previous version or create an hourly load profile as a CSV file and instead use the Load values from a CSV hourly/daily file option Kind regards

Thank you for providing the CSV file and additional information. Upon reviewing the CSV file, I noticed that the Z-coordinates (the third column) indicate significant variations in the terrain elevation. For example, the initial lines show coordinates such as: 407.704717532545 -518.458029091664 -3.60421894608029 475.204717532545 -522.788156110586 -3.69413811294243 Further down the file, around line 285, I see: 475.204717532545 568.403852657811 1.60586188705904 These coordinates indicate a height difference of approximately 5.2 meters (from -3.60 to 1.60), suggesting that the terrain is not flat. When sorting the data by the third column, the elevation ranges from a minimum of -5.04 to a maximum of 1.91 meters. This explains why the terrain appears sloped in PVSyst and why the trackers seem to be hanging in the air at certain points. The variation in elevation points to an actual slope in the data, rather than an issue with the software.

Greetings, I am attempting to create a daily profile for a customer using monthly consumption data. In the load profile section, I selected the daily profile option and chose monthly normalization. I entered my monthly values in kW/month and provided hourly data corresponding to the customer's profile. However, after clicking "OK" and returning to the load profile data, I notice that PVSyst saves my monthly data but generates a constant daily profile instead of the one I entered. Even when I save my load model, any changes I make to the daily profile revert to a constant value based on the monthly average as soon as I confirm. I have uploaded pictures showing what I entered and the results after saving. Before the latest update, I used to do this without any issues. Any suggestions ?

Yes, I will contact you via support@pvsyst.com

For the dimensioning in the system window, PVsyst show graphs based on the values defined in the project settings e.g. -10°C by default for the Lower temperature for Absolute Voltage limit, not from the local site temperature data. This value is supposed to represent the lower value ever measured at the site and this value will not impact the simulation and works only as a guide for the dimensioning of the system. The simulation will be done with the temperatures from the weather file of your site.

Yes you're right!

Thank you for your valuable replay ! So i would to know that incident global irradiation in the collector plane on the front side "GlobInc" and Global inclined plan of front face "GTI_front" are the same or no. My best regards

Does PVSyst use local site temperature data to warn the user that there will be a condition which exceeds the inverter maximum input voltage. Or does PVSyst just use their default single value of -10 degrees C ambient temperature and perform a simple calculation ( and not form it as part of the full simulation). Is this also the some for the temperature coefficient for the use of the solar module? BS7671 / 712.433.101.1 “Without information of the expected minimum temperature of the site or without information about the temperature coefficient of the PV module, Uocmax shall be chosen equal to 1.2Uocstc.”

As mentioned, in PVsyst you can only have the power output for a system as a whole. If you need the power output per MPP or per inverter, you should define a system containing only 1 MPP input, or only 1 inverter.

Hi, GlobInc is the incident global irradiation in the collector plane on the front side. For parameters related to bifacial system, you could refer to the help page https://www.pvsyst.com/help/bifacial_results.htm for the definition of each variable. In general, there is GlobBak that represents the effective irradiance on the rear side. It includes direct and diffuse sky irradiance as well as the irradiance reflected from the ground. For all these three irradiance components, the shading and IAM losses are accounted for. You then have the possibility to export these variables in "Advanced simulation > Output File".

Dear Swonno, Your first question is not clear. Can you explain what you are trying to do? Regarding your second question, by default, the ground object doesn't cause shading, but it is possible to activate it. You need to double-click on your terrain in the right panel and then check the "Enable shadow casting" box, as shown in the example below. Regards, Muhammed Sarikaya

Hi, From the screenshots you provided, both the original terrain data from PVCase and the imported data in PVSyst appear to be quite similar and show regular flat lines, which indicates that the terrain is flat in both cases. However, I understand that you perceive a difference in the terrain's appearance between PVCase and PVSyst. To help us better understand and diagnose the issue, could you please provide more details on the following points: Are there any specific coordinates or points in the CSV file where you notice the discrepancy in the slope? Could you share the CSV file with us so we can inspect it directly?

Hello, You can disable the interpenetration check by clicking on "Tools -> Disable fields interpenetration check". The risk is that some tables are constantly shaded throughout the simulation if they touch. That's why It's recommended to keep a minimum distance between the tables and objects under the tables. You can select all the photovoltaic tables from the left menu tree and raise them by 1 or 2 cm using the auto altitude tool: Regards

Thanks for the reply. I have oner more questions regarding power outpur prt mpp as well as per inverters. How can get such results? Thank You. Regards, Pranav

Hi, I don't think that makes sense, in particular for P90. A percentile is a statistical summary value for a given distribution of results. Generating an instance of time-series results that gives a particular summary does not have any significance, i.e., you cannot learn much from this. We can gladly discuss details if you do not agree. The P50 is a bit special because it tells you the average results, and you can assume that aiming for a given P50 may model a “realistic time-series”. However, I am not sure what you can gain from having a P50 time series shown in a table in a report. Analyzing the time series can give you some statistical information on the distribution of results, but you would need some summary values to make sense of that. At the moment, the only way to get a time series to be shown in the report (but only as a list of yearly values, not monthly) is to use the aging tool with previously prepared time series weather data. You can also generate monthly output files from running the time series in the aging tool and make your own formalized output from that.

Please see image below; It says the panel and below it is confused or very close to each other thus below panel can not be move since its part of the solar panel This 3d model imported from sketchup.

Good morning Hizir Apaydin, Thank you for your help many time. I think I success to import topography csv file into PVSyst near shading. So at this stage, Would you mind if i have another questino? I'm sorry to bother you. Q1. I'm checking generaiton hour and those tophography affect to generation hour? or it is just for notifying the mountain range or just view purpose? and if it affects to the generation hour result, It is effecting as a near shading? (because I'm adjusting far shading now by Horizon optional feature) Q2. ground object is working differently in the shading effect? for example, if i don't change to ground object from building object that PVSyst offers, It is not working as a shading purpose? Could you explain the different effect as a generation hour affecting please? Thank you for your attention on this matter. Happy friday.

Hello, I want to generate report which will show electricity monthly generation for several years (10 years) for different probabilities, for example P50 and P90. Can you please helm how to generate such report?

Dear Shivam, Can you send your project to support@pvsyst.com? We will need to analyze it in details, since it changes only for one of your sub-arrays. Once you send it we will look into it asap.

Greetings, I have a problem with an imported CSV.file of my project into near shading scene. The land for the project is a flat land and I created the CSV.file for the terrain in PVCase where the land appeared flat and aligned with the trackers (as it appears in Picture 1). But when I imported the CSV.file into PVSyst, the appeared to be slopping (as it is seen in Picture 2). What could be the possible problem and how can I rectify the problem?

Dear Vera, This information is a leftover from the first version of PVsyst. You won't find it in the technical datasheet. Please ignore it. Regards, Muhammed Sarikaya

Hi, Unfortunately, PVsyst can only export variables for the system as a whole. In order to have power losses per MPPT, you need to make different variants with one of the MPPTs only and run the simulation for each of them. This will be very time-consuming, so I wouldn't advise doing it. Same thing for the shade by module, it is not an export value for PVsyst. You need to make a special scene with a single module to get the shading values for a single module. At the moment, in PVsyst, the best in terms of stringing is the single line diagram. However, there is no spatial layout associated with it. You can also print the "Module layout" definitions to color-code the stringing with a spatial layout. However, there is no legend associated to it.

Yes that seems correct !

Dear Swonno, UTM coordinates are missing in your file, you have to include them as indicated in the procedure: https://forum.pvsyst.com/topic/3209-how-to-import-a-ground-topography-from-googleearth/#comment-8773 Then you have to remove type, latitude, longitude, utm_zone columns: Regards