dtarin

If your trees are over the terrain, you can place them onto the terrain with any offset desired using edit > set auto altitude. If your terrain surface is limited, and you need to add trees that are outside the boundary, then you can manually adjust the edges of your terrain by moving points individually in the X, Y, or Z direction (you can select multiple at once, it is not restricted to a single point, in case previous statement was misleading). After the terrain surface is adjusted, use auto altitude on all objects.

You need an image of the modules on terrain, and then import and scale the image into pvsyst. You can then visually align the modules imported from CAD and the ground topography from Sketchup to the imported image.

Include GHI. Day 1 could be a cloudy day.

This can all be done with batch simulation. Advanced simulation > Batch simulation. Prior to running the batch, set the output parameters under Output File, and make sure File name is checked under Output file. You don't need to give any specific name, just have this checked (you will define the output file name in the batch parameter file in the next step). Then proceed to Batch simulation to set the parameters and configure the batch file.

Yes.

Once you have imported and set your PV panels, save the ground object as a shading object and delete it. You can always pull it back in. Do not reposition it prior to saving and deleting, and it will be imported exactly where it was last saved.

It looks related to the advanced settings not overriding the project settings. Adjusting this worked, but is limited to 90, whereas there is no limit in advanced settings.

Getting an error even though the thresholds have been adjusted in system settings. 7.4.7. Bifacial system.

The PVsyst wind stow estimation feature is not available for Unlimited trackers N-S. Can this be added?

Change the tilt

Create multiple variants with the different bifacial settings you wish to test (height from ground, albedo), check the box below. Spacing and tilt are a little different, those inputs for bifacial inputs are derived from other places (i.e., shade scene, orientation menu).

GlobInc. You might have reflections at low sun angles with that installation. For a fixed tilt system, these can be installed on a weather station free from shading and reflection.

This can be seen in the orientation menu.

My guess is that the warning is with respect to the HV portion, which you dont have shown in the image. The OND file doesnt account for LV losses. LV losses are zero since the MV transformer is connected to the inverter. You will define a MV line loss however from the MV inverter(s) to the HV transformer(s). Since the OND file accounts for the MV transformer, maintain 0% in the no-load and full-load loss.

There is not unless you model each inverter separately in different variants.

You can model it in certain software. Here is one paper to reference. https://www.sciencedirect.com/science/article/pii/S2667113121000048

@Robin Vincent Is there a reason for a limit of 5 periods?

You can for example create a project called "Template Project" (Template Project.PRJ)which stores your template project variants (i.e., Template Project.VC0, etc.). Then when you want to use this template design in some other project, import the template variant "Template Project.VC0".

In my experience, Ga-doped modules are still susceptible to LID, and I have also seen LID loss in TOPCon tests. The LID loss for these types are less than p-type boron-doped modules, but I have not seen zero LID in Ga-doped or N-type TOPCon modules. I am not familiar with HJT type modules.

Increase the averaging interval to reduce the number of orientations in the shade scene. If there are multiple orientations after you've settled on the number, they will need a corresponding subarray under system menu.

Not intended to circumvent the request, but in the interim, you can post-process the limit in excel or other tool with the 8760, or modify the OND file (may result in slightly lower production).

Hello, It would be very useful to see two features related to the shading factor table: Increased resolution in the shading factor table Allow user to define additional points in the table, or provide additional preset tables with additional values. The purpose of the shading factor table is to reduce simulation time, but it adds additional shading loss. This is fine in principle, but it would be helpful if users could investigate and find that balance between reduced simulation time and reducing the overestimation of shading losses. Additional points in the lower elevations would valuable. Allow users to manually enter or import shading factor tables, linear and mod. strings Allow shading factor tables to be a variable for batch processing. This could be a file reference in a PVsyst-defined format. User-defined/imported shading factor tables could be used in other projects for site characterization and evaluating different scenarios in development. Plants are getting larger, and when modeling trackers with terrain, the simulations times can be quite large, but when using fast mode, the overestimation is not always acceptable depending on the purpose of the simulation.

You might have undersized your inverters or have too high of losses prior to the injection point. Posting your waterfall results will help identify.