PVsystUser

Thanks! I used method 3, but there is an issue I explained in the picture below: although I have defined same rectangle sizes for rectangle string the final rectangles are not the same and I think it shouldn't be like that because 28 modules in series is valid for the whole scene.

You are right, it was a typo, my version 7.2. Do you have any idea why my shading scene in method one does not show proper shading animation? I don't even see the dotted lines that show partitioning is done, but the shading factor table looks good for a backtracking which is 0 everywhere. I afraid that it produces zero because shading is not working at all and not because of correct partitioning.

PVsyst V6.2.16 I have a 2P project, half cell with 28 modules in series (string length). I can define partitioning in 3 different ways but the results of shading animation is not the same and also the iso diagram is not the same. I included the screen shots below for all there methods. Please advise on which method is the best method to use for partitioning.

I ran the same variant in PVsyst 8 and got a huge difference in near shading loss. Does it make sense? please see the highlighted cells below. the only difference between two is they were ran in two different versions:

Thanks but there is no such thing in V 7.2.16

I am adding this question under this thread as it might be a version-related issue similar to the above issue. I have two projects that are the same except for the shading layout. I see ~2% difference in the near shading loss (4.5% vs. 6.7%), which does not make sense for not such a big difference in their layout. The site is flat, and the module is First Solar so no backtracking. We have removed the trees, and the result didn't change. Could you please give us some idea of what we can check to nail down the source of the issue? We can't share the logs. Some screenshots are shared below.

Does PVsyst have any stow- strategy in the simulation when backtracking is on. The reason I am asking is because in "orientation" tab when backtracking is on, the modules will go to stow at sunrise and sunset (when moving the sun in the screen shot below to the extreme ends)

My PVsyst version is 7.2.16.

why not partition like this :

We have two location to define partitioning: List and management of objects zoning > filed properties > partition What is the difference between these two and which one should we use? When the string length is 26 in 1P, is the screen shot below, a correct way of partitioning in zoning? if yes, why we use 2 for nb. of rectangles in width and not the string length (number of modules in series)? A visual guide can help a lot. The partitioning in confusing. even in the link below , they don't say where should we put string size? It just says how to define number of modules in height, but how about width? https://www.pvsyst.com/help/project-design/shadings/electrical-shadings-module-strings/partition-in-strings-of-modules.html#summary-for-common-cases

I changed this number to different values ( 0.5, 2m, 30m) and it seems it is not reflected anywhere. at least when having multiple zones with different distance from ground , they all look to at the same heigh :

Please see the green rectangle in the screenshot below. What do the shading lines that fall inside the green square represent? That area is outside of sun path for the project's location; why they have a specific shape if they don't have any meaning?

Could you please explain why?

I have created a custom Pan File in PVsyst 8 and imported it in PVsyst 7, there are few param (eg: Rsh and Rs. ) that has been changed. What could be the reason?

How to install previous version of PVsyst? The link is not working: https://www.pvsyst.com/download-pvsyst/