All Activity

Yes, sorry, I completely forgot mentioning this in my last post. The correction I had done in the program has not been taken into account for the published version 8.0.8. This should be corrected in the next version 8.0.9, to be released still this week. In the meantime, the only way of modifying this value is to set the parameter “Arev= 1000” directly in the PAN file. And with this PAN file you should not enter the page “Additional parameters” of the PV module definition dialog.

Dear Nikoloz, You have to find a way to extract the three coordinate points (X, Y, and Z) of your 3D object and save them as a CSV file. This way, PVsyst will accept the CSV file as topography. Regards,

Dear Laura, Thank you for reaching out to us. First of all, we will replace "Ageing" with "Aging." Regarding the manufacturer's lower limit guarantee, you can see it clearly in the graph below: The sentence states that the module warranty represents the lower limit in reference to this graph, where it shows the loss of efficiency. It compares the black curve, which represents the module warranty, with the calculated aging curve, showing that the warranty curve has a higher efficiency loss than the calculated degradation. Therefore, the sentence in the help documentation is correct in relation to this graph. Regards,

the problem is ：the value of BRev is limtted to 50 in the PVsyst8.0.8

The energy stored in the battery during the year - mentioned on this Sankey diagram - is indeed the value calculated by the simulation for the actual battery capacity specified for this simulation. In the present time, the battery capacity decrease according to the ageing is not taken into account in the ageing tool (this feature is on our roadmap, but will not be implemented before several months). Therefore you can indeed perform a simulation for the last year of the battery life, with a battery capacity diminished by 20%. However don't wait for a big difference: the battery use during the simulation is not very sensitive to a diminution of 20%. NB: don't confuse the self-consumption with the capacity diminution, they have nothing to do with each other. The self-consumption may also be dependent on the age of the battery, but we don't have any information about this.

Hello Does anybody know how to export terran as 3d object From DJI Terra to PVsyst?? Dji terra is an app to use with dji matrice drone

Answer to Kanagavel above. No, the ageing represents an ageing from year to year. There is no reason for being different during the first year. The first year differences should be accounted in other loss kinds like LID or Module quality loss.

Yes, the red behaviour indicates the global degradation to be applied for each year, taking the mismatch evolution into account. The black line is the warranty of the PV modules manufacturer, that you may define as you like. It is indicative.

Could you confirm that the only inputs to the degradation calculations are the values circled in green here? I'm assuming that the red values are calculated and the warranty info is only for plotting. Thanks.

I found what appears to be a mistake in the latest documentation about the Aging Tool (https://www.pvsyst.com/help/project-design/array-and-system-losses/ageing-pv-modules-degradation/index.html?h=degradation#guaranteed-and-average-degradation-rate). Initially it says that the manufacturer's warranted degradation is the LOWER limit of degradation. This should be UPPER, as the first sentence of the next paragraph rightly states: "In these curves, the initial loss (of the order of 3%) should be considered as the LID, or initial Power possible deficit (tolerance, factory measurement uncertainty). Therefore the annual guaranteed lower limit diminution rate is the slope of this curve. In our example (-3% initial, -20% after 25 years), this means a rate of -0.68%/year. But this is not the degradation rate of the full array. In this tool we define an average degradation rate (for a set of modules). This loss value may be much lower than this guaranteed limit." [Incidentally, the help page is titled "Ageing" but the spelling "aging" is used in PVsyst. Apparently both are correct, but I don't think I've ever seen "ageing" in the US. It's extremely rare to have a silent "e" in the middle of a word.]

Recently, I calculated the IAM beam factors for each hour of a fixed-tilt 8760, as 1 - IAMBLss/(BeamInc - ShdBLss). The project was modeled in PVsyst 8.0.7 with the default parameter values for a Fresnel AR IAM curve. When I plotted IAM vs. AOI, I saw a curve that somewhat resembled the Fresnel curve - except that there were significant bifurcations. See the attached image. As far as I can tell, this seems to be a "feature" of PVsyst 8, as the same bifurcations do not exist when I run the project in 7.x.x. What is the reason for this? This seems to be non-ideal behavior.

Total loss

Hello, Indeed, in the Project settings you can define Site-dependent design parameters and the "Lower temperature for Absolute Voltage limit" ensures that an error message is triggered if this limit is exceeded. This value is typically set based on the coldest recorded temperature over the past 10 years to protect system components. Adjusting this value can indeed affect the maximum number of modules allowed in series. However, PVsyst does not currently adjust this setting automatically.

I see, I have checked and indeed this is not the case. PVsyst 8 also has the same issue. I have created a ticket to fix this in a future patch.

It is clear, Thank you for the answer.

Pnom without temperature correction means nominal power, and not maximum power. So in your example it is relative to 320kW.

@NGS In case you have a warning due to the average axis tilt not being horizontal: you can override this error in the following way. Home window > setting > Edit advanced parameters: Note that this is only forcing PVsyst to proceed, but the backside irradiance model is still modeling things with a zero axis tilt (which generates a discrepancy with the actual orientation, and means there will be some uncertainty in the results).

Hi Michele. I'm running the PVSyst 7.4. Thanks.

Indeed it is normal. With the unlimited trackers field type we assume a perfect backtracking and therefor there will be no mutual shadings.

Indeed, you can maximum print 3 decimals in the loss diagram.

Hello, You can find all the variables in the Advanced Simulation output file. Some categories in the loss diagram are grouped—for example, Global Horizontal Irradiance, where its individual components are not displayed separately. Additionally, all the intermediate calculation steps are not explicitly represented in the diagram. However, all losses are accounted for, even if not all details are printed. For a grid-connected system, the Performance Ratio (PR) is calculated as E_Grid / (GlobInc * PnomPV). E_Grid printed in the loss diagram is the final result. Best regards

Hi everyones, Should the "medium voltage line" losses section indicate the total voltage drop of our MV network or the average voltage drop of each branch? Additionally, in the "external transformer" section, are the "iron" and "copper" losses multiplied by the total number of transformers specified for the plant? Thank you in advance. Arnaud Pancrazi Design office technician PV Equans (France)

Hi PVsyst team, Why when I click on "Backtracking" option then the option "Electrical effect" is disappeared? Does that mean if I click on Backtracking then Electrical effect will not be activated? Thank you in advance

Sorry, I don’t know what should be improved. The result is highly depending on your system. If more than 3 cells are shaded at a time within a submodule, you should not see any difference. Please carefully read the help https://www.pvsyst.com/help/physical-models-used/pv-module-standard-one-diode-model/pv-module-reverse-lowvoltage.html?h=ibc If your system is "regular", there are probably very few hours in the year concerned by this condition.

Thank you for response In loss diagram Diagram, loss decimal value is only three digits is available. Can u please guid me how to take more decimal value in the pvsyst if possible.