dtarin

Bumping this. Any plans to incorporate this in future versions? Modern design software spit out shd or pvc files quite easily (both should be able to be imported). I think the only hangup with this is the partition definition for each shade scene, but if this were added to 3D shadings parameter, the user could define the geometric area of a partition that gets applied to each scene. Diffuse shading can be set to central tracker for quick analysis by default, backtracking activation is already an option for batch sims.

Curious why you have included the +1 there. You can simulate a tracking system at [X,X] for min and max to lock the tracker for all hours to a single angle. If you need to more than one angle, this can be done with batch simulation easily.

Auxiliaries tab: proportional to inverter output power (i.e., 1 W/kW = 0.1%, etc.).

If the sensor(s) is in front of the torque tube and other items, (GlobBak+BackShd) * 𝜑 is sometimes used. Install sensors midpoint between two piles for tracker systems.

Ohmic loss is proportional to power. Abu Dhabi has much higher irradiance compared to Berlin. Also, not sure if it is intentional, but you're simulating the 10th year of operation. If unintended, be sure to set it to year 1 on the degradation tab. Ohmic losses - PVsyst documentation

This looks like an AI bot or something...

Still present in 8.0.16, don't see mention of correction in 8.0.17 or 8.0.18 release notes.

You are modeling "detailed according to module layout". You need to place these modules in the tables in the module layout menu. Select "according to module strings" and it will use the shade scene as it has been provided. The total area of the shade scene is relatively close to the pv system.

After writing that, perhaps the issue is that your prj file itself is missing the .SIT information, in which case manual creation might be the solution.

You can always create one from notepad just to get it loaded or extract the site information from the .prj file. Look for the following (and remove the text after the underscore). Some changes will need to be made; I think you just need to add the version below the "Comment=..." line. If you're creating from scratch, I think the main things you need are coordinates, altitude, timezone. The meteo data that is contained in the site file is not used in simulation. PVObject_SitePrj=pvSite .... .... End of PVObject pvSite

Hello, It would be great if we could specify .SHD files in batch simulations.

Will the Perez-Driesse model be included as an option in the future?

Export the data (values) from the graphs and you will get short circuit values for V and I.

Electrical shading loss has been around for a long time. It is likely the 7.2 report was run on linear shading, or the site was modeled perfectly flat with backtracking enabled and no shading objects present to cause electrical shading loss.

You can change the settings for both types of messages. The shade scene module count has no impact on simulation results.

2x28 = 4 vertical, 1 horizontal for half-cell module

norm.inv(Pxx,0,1). P99 is 2.33, not 2.35

Cannot get custom tracker to save in v8.0.12. Once shade scene is exited, it remains all trackers.

Change this under advanced settings. I suspect there might be something else going on, but here is how to override the error.

Have you tried creating a copy of the SIT file in the Sites folder, to see if it shows up in the list?

I am seeing difference of 0.15% in 8.0.12 which is non-trivial. Aging tool on top, PVsyst report result on bottom.

Useful Out and Egrid are the same. I suggest including InvOut It seems IL Pmax will include grid limitation loss when there is a limit applied in the IL Pmax figure, even if it is set to account for loss separately under energy management. I suggest quantifying IL Pmax as its defined in energy management, or by default include POI loss as a separate value, and let users add together if they want. EArrayMPP is more useful than EArray, I recommend adding it or replacing EArray with it.

PVsyst doesn't output 8760 files past year 36. It will complete the simulations and generate the pdf report, but not the excel output. v8.0.12

Simulate with as few trees as possible. Take into account things like the total elevation at the top of the trees (tree height + ground elevation) and the distance relative to the panels.

export simulations to excel. output the variables you need and analyze from there.