dtarin

It selects the lowest pitch automatically to avoid shadings. You can select any rack you want to change it or manually enter it in. Calculate a weighted average based on the number of tables at each pitch if they are different.

As noted in title, PVsyst allows the user to run a simulation with according to strings selected and an electrical effect defined, but without having defined a partition in the shade scene. In prior versions I recall this creating an error or warning, and/or forcing the simulation back to linear when a partition was not defined. The reason this is occurring is because as you can see in the screenshot, a higher GCR is selected and the site is practically flat; when this GCR is used for the backtracking algorithm, electrical loss is apparently 0% from shading due to adjacent tables. If I select a lower GCR to be used for backtracking, the simulation then forces the error and directs the user to define a partition. However, this should not be the case. If according to strings is selected, it should always force the user to define a partition, even if there is some internal check to see if there is shading from adjacent sheds (that's how it looks to me anyhow). There are trees in the shade scene, so even if there is no shading due to tables, there should still be electrical effect loss, which is why according to strings should force the definition of a partition.

Your GCR has increased in the new simulation, which will result in a lower transposition factor. In the shading scene under backtracking management, the pitch used for POA calculation and backtracking is selected, either automatically or specifically by user. POA (GlobInc) doesnt not consider shading losses, GlobEff does.

It may depend on where these tables are in the array and the site conditions. For an exterior table that has significant tree shading (or other object shading), strung in U may be better (2x2). For interior tables, where most of the shading will be from the rows in front, stringing across the entire table (and not in U) is likely better (4x1).

Change your settings in green box below.

I think the minimum is two days, PVsyst wont let you simulate a single day.

PR_ft*(DC_ft/DC_total) + PR_sat*(DC_sat/DC_total)

You can take a weighted average of the PRs.

Phi is the variable to change for this exercise. Phi_min = Phi_max in the batch parameter file to simulate a tracker at angle. Tilt and azimuth should not be changed.

You cannot simulate SAT with fixed tilt. You need two separate variants. Yes, you can simulate MV and HV losses.

If your site is that large (GWs I assume here), you're better off running them in separate variants. Also with a site that large, you may not need to model the entirety in the first place, as long as you have a scene that is representative of the overall site.

It does not, trees are solid, static objects.

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).