Lazare Fesnien

Hi, We are sorry to hear this and apologize for the inconvenience. A lot of configuration is possible in this tab, can you give me more details about this bug ?

Hi, You can easily create your own components by yourself. The easiest way is to choose a similar existing device in the database, modify its parameters according to the manufacturer's datasheets, and save it under a new name, therefore creating a new file in your database. You have a tutorial for that on youtube: https://www.youtube.com/c/PVsystTutos, page Component database

Hi, The optimizer's properties and operating conditions are very specific to each manufacturer. We need a close collaboration with the manufacturer for implementing them in PVsyst.

Hi, Thanks for your bug report. Please read the related post from our FAQ: https://forum.pvsyst.com/viewtopic.php?f=17&t=5453 Sorry for the inconvenience and best regards.

Hi, Sorry, with stand-alone systems, only one sub-array is possible. Therefore one only orientation. This is a limitation of PVsyst, that we should improve in the next months.

Hi, We use to update the database using the data provided by the manufacturers. However despite several reminders, SMA has never updated the database since more than 5 years, so that we decided to include some of their inverters from the datasheets available on the web. But SMA people were not satisfied at all when seeing our definitions of their inverters. They asked for retrieving them immediately. Therefore please ask SMA for their OND files about these devices. NB: You can always define an inverter from datasheets by yourself: you have a tutorial on Youtube for that:

Hello, We update the database using the requests of the manufacturers, and publish it with each new issue of PVsyst. We can't of course follow all the new products of all manufacturers in the world. We don't want to include data without the acknowledgement of the manufacturer. Nevertheless you can easily create your own components by yourself. The easiest way is to choose a similar existing device in the database, modify its parameters according to the manufacturer's datasheets, and save it under a new name, therefore creating a new file in your database. You have a tutorial for that on youtube: https://www.youtube.com/c/PVsystTutos, page Component database

Hello, Sat = 23% means that the share of satellite data when interpolating is 23%, the rest corresponds to station data, interpolated from nearby stations. Meteonorm does use a mixture of satellite and station data. The further one is from the stations the greater the weight of satellite data. For more information about meteonorm, please also look at their documentation. For example their handbook's chapter 7.2 describes the interpolation in more details https://meteonorm.com/assets/downloads/mn80_theory.pdf

Hello, We have designed several online video tutorials which we invite you to watch: https://www.youtube.com/channel/UCMzsEWHk3f7XD_dg1lngmzg

Hello, Thank you for pointing this out. This is a bug that we will correct for version 7.2.4. This only affects the display of the results, but the yearly results are unchanged.

Hello, Can you send us on the following email address your request with your project and screenshots? support@pvsyst.com

Hi, Which "many components" ? In principle we never suppress any component from the database, as users may have defined them in their projects. But sorry, we had to do an exception here. SMA people were not satisfied at all when seeing our definitions of their inverters from datasheets in the PVsyst database. They asked for retrieving them immediately. Therefore please ask SMA for their OND files about these devices. NB: You can always define an inverter from datasheets by yourself: you have a tutorial on Youtube for that:

Hi, Yes, there is indeed an error in the version 7.2, that we have to investigate. Please revert to the previous version 7.1.8 for your simulation. You can download it from our website www.pvsyst.com, and install it in parallel with the version 7.2.

Hi, Thank you for this feedback. Good writing is : PVsyst

Hi, Please send us your project on support@pvsyst.com in order to analyze your problem.

Hi, Indeed, we just elucidated two bugs in version 7.2, for bifacial systems: - One in the display of the report, where the “bifacial model geometry” section is not correct, - The other is an error in the computation of the diffuse on the rear side of modules for bifacial tracking systems. This in turn largely affects the losses diagram. We will be publishing a corrective to these two errors in patch 7.2.1, as soon as possible.

Dear, The message in red indicates an error. You must therefore make changes in order to match the characteristics of your inverter. For more information, you can read the links below : https://www.pvsyst.com/help/inverter_array_sizing.htm?zoom_highlightsub=oversize https://www.pvsyst.com/help/inverter_operating_limits.htm Regards,

Dear omairahm, The message in red is normal because your inverter has a very high power compared to the Total STC power of your PV array. You have a 1665 Kwp PV array, so you must choose an inverter between 1200 and 1500 KWac Regards,

Hi, Inverters with Unbalanced MPPT inputs Some special inverters (namely in the Tripower series of SMA) have 2 MPPT inputs with very different powers. In practice this is very useful as you can define an array without much constraints about the module number on the main input, and one string with the remaining of your modules to be installed - whatever their number - on the secondary input. This feature is part of the Inverter's definition. With these very special unbalanced inverters, when defining a sub-array you will have the choice between "Main" and "Secondary" MPPT inputs. In principle you should define sub-arrays for the same number of "Main" and "Secondary" inputs (i.e. use all the available inputs). However the button "adjust" gives the opportunity of not using the secondary input. Please check with the manufacturer that this is really possible with the real inverters you are using. At the design time, the nominal powers of each input are evaluated according to the maximum currents specified for each MPPT inputs. This may sometimes lead to unacceptable overload losses. If this warning is red (error), you have to increase the allowed overload energy loss in the "Project's" parameters (button "Albedo-Settings"). At the Simulation time, the power sharing (as mentioned above for normal MPPT inputs) is automatically performed as function of the PV modules connected in each sub-array. The Pnom of each MPPT input is evaluated just before the simulation. Example of use (tutorial): Suppose you have to build a PV system using 155 PV modules of 250 Wp, i.e. 38.75 kWp. 1. - Choose the inverter(s), according to a reasonable PNom ratio of 1.25: you need inverters for PNom(ac) = 38.75 kW / 1.25 = 31 kW. 2 inverters with unbalanced MPPT, of PNom = 15 kW should be well suited. 2. - In the "System" part, Define 2 sub-arrays, 3. - First one: define "Main" input with 6 strings of 20 modules (i.e. 120 modules), and 2 "Main" inputs: you get a PNom ratio = 1.25, quite correct. 4. - There are 35 modules left to be attributed. This will correspond to 2 different "Secondary" inputs, so you have to increase the number of sub-array to 3. 5. - Sub-array #2, define 1 "secondary" input, and attribute 18 modules. 6. - Sub-array #3, define 1 "secondary" input, and attribute 17 modules. 7. - Now the Warning "The inverter power is strongly undersized" appears in red, because the Overload loss is over 3% (depending on the meteo). You have to increase the "Limit overload loss for design" in the project's definitions. Now your system is ready for the simulation.

Hi, We update the database using the requests of the manufacturers, and publish it with each new issue of PVsyst. We can't of course follow all the new products of all manufacturers in the world. We don't want to include data without the acknowledgement of the manufacturer. Nevertheless you can easily create your own components by yourself. The easiest way is to choose a similar existing device in the database, modify its parameters according to the manufacturer's datasheets, and save it under a new name, therefore creating a new file in your database. You have a tutorial for that on youtube: https://www.youtube.com/c/PVsystTutos, page Component database

Hi, We update the database using the requests of the manufacturers, and publish it with each new issue of PVsyst. We can't of course follow all the new products of all manufacturers in the world. We don't want to include data without the acknowledgement of the manufacturer. Nevertheless you can easily create your own components by yourself. The easiest way is to choose a similar existing device in the database, modify its parameters according to the manufacturer's datasheets, and save it under a new name, therefore creating a new file in your database. You have a tutorial for that on youtube: https://www.youtube.com/c/PVsystTutos, page Component database With best regards,

Dear Salma, In the original PVsyst database we don't have the following model : STP370S-B60/Wnh_1500V_20V02_1756 I have checked your file "STP370S-B60/Wnh" : RShunt and RSerie values are unrealistic Please check your custom PAN files with the datasheet in order to be sure.

Dear soojin, The import worked correctly, what you imported was the multi-year hourly time series, which means every year is imported into separate .MET files (the one you have in your project is the last one for 2016). You can see in the screenshot below that the import creates 13 files for 2004 to 2016. This is done because PVsyst only simulates a single year of data. If you want to use all 13 years, you can look into the Aging tool or the Batch simulation. If you want a single file that represent the average for your place, you have to import the TMY with Sam format, see below for which source to chose. Regards, Lazare

Hi, Many issues are fixed in higher versions. You can download V6.88 or use V7.1 (download possible from the site : https://www.pvsyst.com/download-PVsyst/) Regards, Lazare

Warning messages will be displayed if there are some incompatibilities between the chosen parameters : - Red warnings are not acceptable (simulation cannot be performed) - Orange and Bleu warnings are indicative These colours will be thrown back on the "System" LED's button.