Linda Thoren

Hello, The system is not completely the same before the battery (you have a 9.2% loss to the right compare to 2.3% to the left), thus you have less solar production to the right. Also have a look at for instance the charging and discharging power. Kind regards

See example below from the DEMO commercial project where indeed the first year simulation match the result from the aging tool. If your issue persists, please send your project as a .zip file to support@pvsyst.com Kind regards

Hi, First time you ran the simulation, did you use the aging tool in the detailed losses? in what year? When you activate the aging in the detailed losses, the first proposed value is to run the simulation for year 10, possibly the first PR correspond to year 10? Kind regards

Indeed this is a limitation of the bifacial model today. A possible workaround, is to modify the .PAN file and place two panels back to back. By creating separate modules for the front and rear—each with a bifaciality factor of 0 (and adjusted properties, e.g., lower power, no AR coating for the rear)—you could place them back-to-back in the 3D scene and simulate the system using the Module layout. This wouldn’t fully replicate real system behavior, and on clear days electrical shading losses might be underestimated due to the fact of having two panels instead of one. This in not necessary a recommendation, but could work as a test to evaluate the shadings for the backside. Otherwise, for the estimation of the electrical shading losses in general for a vertical EW system, the irradiance distribution on the rear side should be roughly as uniform as on the front. This means that, in principle, the rear mismatch factor should be set to zero, as it only accounts for additional non-uniformity on the rear. However, since PVsyst currently calculates electrical shading losses only for the front side, using the rear mismatch factor as an approximation for rear-side shading losses is reasonable. That said, determining whether 5% is an accurate value is difficult, as it depends heavily on system geometry (row height, spacing, etc.). As a first approximation, it would be best to adjust the rear mismatch factor so that its corresponding losses in the loss diagram match the electrical shading losses multiplied by the bifaciality factor.

Hello, Indeed this is not very straightforward. The irradiance on the rear side is renormalized to the 4806872 m2 of collectors after the View Factor (1111 -73.71% -81.34% * 14897331/4806872 +15.6% +0% -9.9% results in 176). This further explained in the help page below: https://www.pvsyst.com/help/project-design/bifacial-systems/bifacial-systems-results.html

Hi, at the moment PVsyst cannot simulate the backside irradiance for domes. Note that in general the bifacial gain of dome structures is negligible, unless they are installed very high above the ground. So your results are not really useable like this. The backside irradiation model is a 2D approximation that currently only works on single orientation rows. It does not take into account shading objects from the shading scene, as the rows of panels in the opposite orientation. Regarding the height above ground (that is defined in the unlimited 2D Model tab) and the albedo, normally it is possible to define this for each orientation if you save the definitions (clicking OK)

Hi, This is not on the road map at the moment. If you wish to have an unavailability in production loss, such as in soiling losses, you can indeed put the unavailability in the soling losses tool instead.

Hello, Indeed if it is a grid limitation can be applied in the Energy management window, Grid power limitation, instead of modify the inverter. If the grid limit is in apparent power, note that you here can change the limit from active power to apparent power. Kind regards

Hello, Unavailability can only be defined as a time fraction, not as a direct production loss. Consequently, the impact on production will be higher if unavailability occurs during peak production hours rather than at night. If your goal is to determine production loss due to system unavailability, you will need to adjust both the time fraction and the specific timing of the unavailability to accurately reflect the desired energy loss.

Dear Luis Zimmermann, The bifacial model in PVsyst does not consider any additional shading objects from the 3D scene for the backside irradiance, only the parameters in the Bifacial system definition is used in the simulation. Thus, to include the impact of the mounting structure, this should be estimated and put in the Structure shading factor in the General Simulation Parameters in the Bifacial system definition window. Kind regards

Dear kjs55, Thank you for your input. PVsyst is not a weather provider, but a simulation software. Several data providers supply sub-hourly values that you are welcome to import as a custom file and apply the sub-hourly clipping correction. Kind regards

Dear James Lenton, Indeed in the advanced simulation you can generate Time evolution, histograms with bin configurations and functions as scatterplots. In the advanced simulation window you can also create an output file with any variables and create your own graphs in another dedicated tool

Hi, A report generated in 8.0.6 can be opened in an editor such as inDesign without a password. Kind regards

Dear NFI, Indeed, in earlier version the report was protected so that it cannot be manipulated. To use certain graphs, you can instead click "Export" and "copy to clipboard" Kind regards

In the printed report you can include both the performance ratio and a P50/P90 evaluation, but not a performance ratio of the P90 evaluation. Kind regards

Hello, It is possible to import measured data through the databases window, Custom file. Choose your file, define your site and click New to construct the format file. For measured Global Inclined Irradiance, or Plane of Array Irradiance, choose the Measured global on plane variable GlPMeas and define the orientation definition and albedo. Measured POA irradiance import uses HAY transposition model. Make sure that the simulation is also performed with Hay transposition model to ensure consistent POA. You change the transposition model in the Project settings, Design conditions tab. The module temperature should be imported as the variable TArrMes - measured module temperature. If you do not have any measurements for the ambient temperature, ambient temperatures will synthetically be generated from another source and this function seems to not work correctly. When running the simulation, in the detailed losses window, thermal parameters tab, make sure you tick the option Use Measured Array Temperature and the synthetically generated ambient temperature will not be an issue for the thermal losses. Kind regards

Hi, The output will depend on your type of system. A fixed tilted system with an optimum tilt and azimuth will peak when the GHI peak, a east west system will rather peak in the morning and evening. This is also what you see a bit with trackers with trackers with a north-south axis during months where the sun's position is relatively low. Indeed such a drastic peak in the end of the afternoon looks strange, is the irradiance data and the hourly output aligned? Do you have an have an azimuth? Is there a horizon line? To be able to analyze this in more detailed, please send your project to support@pvsyst.com Kind regards

Hi, Indeed, today the ground reflection is only considered for bifacial systems. As you say, the ground reflection for the front side can be rather significant for vertical systems. The only way to run a simulation including the ground reflection for the front side for a monofacial system today, would be to alter the PAN file (activating the bifaciality and put the bifaciality factor to 0) and run a simulation with the bifacial parameters, though everything except the ground reflection on front side will be 0 given the bifaciality factor of 0. In the example below I defined a vertical system using the unlimited sheds, facing south, 2 rows, 20m high and a pitch of 50m, to simulate a system similar to a façade mounted vertical system.

Hi, No, the stand alone system will prioritize solar and only use the genset as a backup, thus unfortunately this is not possible to plan charging of the batteries with the genset without a direct use (and possibly waste solar produced energy in the morning if the batteries are already full and there is no direct need). The genset will ensure the recharging of batteries when the solar energy is insufficient to satisfy the user's needs.

Hi, If you have own measurements, please import them as a Custom file, there you can import a file with any separator or date format.

Hello, The denomination of a given time interval in PVsyst is always defined as the beginning of this interval. This is valid for hourly, daily or monthly values. For weather data, the time stamp is the time interval over which the irradiance measurement (or any other value) is averaged. For example, the time stamp 11:00 corresponds to measurements averaged between 11:00 and 12:00. The time stamp is not defined in this way for all external weather data. Some of them use the end of the interval, some are measurement between 11:30 and 12:30, or any shift within the hour. Therefore when importing weather data, PVsyst has to adapt its internal time interpretation, in order to always calculate the Solar Geometry in the middle of this interval. In general, when importing a custom file, you can import minute data and PVsyst will adapt the format to run hourly simulations. In the databases window, click Custom file, choose your datafile, define your site, click New and define all the relevant parameters (time step, date format, variables etc.). You can read more about the Time Definition in PVsyst in the following link: https://www.pvsyst.com/help/physical-models-used/time-definition-in-pvsyst.html?h=time+stamp#basic-time-dst

Hi, In PVsyst, the back-up generator is considered as an alternator+rectifier element (Genset), ensuring the recharging of batteries when the solar energy is insufficient to satisfy the user's needs. You find additional information in the PVsyst help page below: https://www.pvsyst.com/help/component-database/back-up-generator.html?h=back+up+generator+(genset)

Hello, There is no straight foreword way to calculate the PR for a probability distribution, (defining the GlobInc for instance). If there is a standard for this, we will implement it.

Hi, Indeed, PVGIS 5.3 will be available in the next version of PVsyst (8.0.7) being released next month. Until then you can export your PVGIS data as a .csv file, and import this as a Custom file in PVsyst. Go to databases, Custom file, choose your PVGIS file from your computer and define your site. Click New and define all the relevant parameters, such as the Time step, numbers of head lines to be skipped before the data starts, format of the date, in which column what variable can be found etc. By clicking ok you can then start the conversion of your data to a .MET file that can be used to run your simulation. Kind regards

Hello, Indeed if you still have a valid license you can simply update from PVsyst 7 to PVsyst 8 and two ways you explain should both work. Kind regards