André Mermoud

Yes, we have to extend and modernize the definitions of the AC losses after the inverter, and define several transformers. I hope we will have time to do that within some few months.

In a normal distribution, 68% of the "events" are between -sigma and + sigma. But 16% are above + sigma. Therefore above the value (Average - Sigma), you have 68% + 16% = 84% of the event. This corresponds to P84.

For the horizon shading calculation, PVsyst analyses the time at which the sun crosses the horizon line. And applies the shading effect (i.e. suppression of the beam component) only on the concerned hour fraction. Therefore the result is not directly related to the hourly step.

I don't understand what you mean. The PNom ratio is not an input parameter in PVsyst, it is the result of your definitions for the PV array and the inverter. Now you can have some limitations, concerning the accepted overload loss. By default it is 3%, but you can increase this limitation in the project's definition, button "Albedo & Settings".

In the "Domestic uses", you simply define an appliance of 120W, used during 10 hours, and click the corresponding hours in the day circles. H stand for "Hour". 10H is for the period 10:00 to 11:00 AM.

There is no special operation for defining an overload. This is just the result of the definition of your PV array with respect to your inverter. We usually define the PNomRatio as the ratio between the Pnom(PV) of the array, and the Pnom(AC output) of the inverter.

There is indeed a limit, the number of elementary triangles should not exceed 8'190, i.e. about 8'000 points.

This has nothing to do with the previous discussion (about batch mode). However please see our FAQ With sheds on a tilted roof, PVsyst changes my orientation

You can only use the background image in the Plane view in PVsyst. Therefore importing images which are not a plane view doesn't make much sense.

The behavior of this system seems indeed strange. But the information about the system is not complete. Please send your whole project (using "Files => Export projects") to support@pvsyst.com.

The shading table concerns the beam component, for the instantaneous position of the sun. By definition of the backtracking, the shading factor is null. However for each position of th modules, you have a shading factor on the diffuse part (coming from all directions of the space). The final diagram shows the corresponding loss on the diffuse part. See How is calculated the shading loss on diffuse for tracking systems?.

The Irradiance units are not correct. However it is not possible to import POA data in daily values. The retro-transposition model only works on an hourly basis.

In PVsyst, an horizon line below 2° is not taken into account. By the way this would not be significant, especially in sub-tropical climates.

The "Availability" parameter defines periods of Failure (which may be generated randomly if desired) They could be defined for example by night, therefore leading to no loss. Please check that in your "Detailed Losses" the failure periods really occur during significant production times.

This error has probably been solved in the version 6.41. Please try. If it doesn't work, please send your whole project to Support@pvsyst.com, using "Files > Export project" in the main menu

Yes, the format for importing Hourly Load data has been changed. You have now to prepare a file in the "Standard PVsyst format" as described in the help "Project design > User's needs ("load") > Load profile: ASCII file definition". Sorry for the inconvenience, it was necessary for a modernization of the PVsyst Load management. This format will also be useful for importing other parameters in Hourly values in future versions. You have a template of this file in "c:\ Program Files (x86) \ PVsyst6.x.x \ DataRO \ PVsyst640_Data \ UserData\ Hourly_Parameter_Template.CSV" (or ... \ SubHourly_Parameter_Template.CSV). Your own data file should be placed in your workspace \ PVsyst640_Data \ UserHourlyParams \ NB: Thank you for your example file: I tried it and it works correctly (see the graphs after importing). Just the file Preview does not work correctly: it doesn't recognize the comma as separator. I will correct this.

I just tried and everything works correctly. However in the version 6.40, the Variables to be written were not well recorded on the Calculation Version (VCi) file. So that when reopening a VCi file of the version 6.40, when outputtting an ASCII file you have to explicitely redefine the variables to be written before simulation.

No, we don't organize training sessions elsewhere than in our offices at Geneva (except sometimes for the team of a company).

The simulation (in hourly steps) involves about 40-50 variables, calculated from different models (Transposition, Shadings,IAM, PV module modelling, Losses, inverter behavior, etc). These variables may be stored on an CSV file for further analysis during the simulation.

You have defined a number of PV module in the "System" part. PVsyst checks that you have defined sufficient room in the 3D construction for installing all these modules.

Yes the "normal" simulation is valid for the first year of operation. Now if you want to take a long-term degradation into account (of the order of -0.5% to -1%/year), you can put this additional loss in the "Module Quality Loss" factor. See our FAQ How to define the "Module Quality Loss" parameter ?

The license name is indeed not critical. In your case the problem is that the "Local number" read on the target computer is not correct. Please open PVsyst (V5.xx) on the target computer, and carefully read the "Local number" (menu "License > Status and Activation"). Then you can come back to this licensed computer, copy this "Local number" here, and this will give your user's code for the target computer.

If you cannot find your original invoice, you have to contact admin@pvsyst.com.

The license name is indeed not critical. In your case the problem is that the "Local number" read on the target computer is not correct. Please open PVsyst (V5.xx) on the target computer, and carefully read the "Local number" (menu "License > Status and Activation").

When defining the "User's needs", you have an option for importing load hourly values as a CSV file. Please choose the option "Load values read on ASCII file", anf follow the procedure described in the help.