Search the Community

Hello, When I import a scene from PVcase, in several occasions the tables take two different orientations automatically, either modules in portrait (3 rows x 24 modules) or modules in landscape (24 rows x 3 modules). This was not a major issue in PVcase 7 as in the orientation manager you could override this. However, in the new PVsyst 8, with and EW system I can not simulate the bifacial option as the widths of the tables are not the same (an error pops up). If I change manually in the list of objects the configuration of these "wrong" tables, they move all over the scene. How can I fix the error in importing/reading correctly the tables? This would also reduce the threshold of the setting in max. spread of azimut for the same orientation. Note: this is not an issue of this particular project as it has happened before in multiple projects. Many thanks!

Hello everyone, I need an help to solve some issues on my project's results. I am working at a PV system with the following characteristics: - trackers with monoaxial system rotating on the N-S axis; - fixed tilt; - fixed azimut; - adapted to the terrain configuration. Looking at the advanced simulation results, I noticed some strange values under the ''Pltilt'' and ''PlAzim'' voices. I attach some pictures to explain my issue. As soon as I looked at these results, expecially at the PlAzim and PlTilt values, I immediately asked myself: - If my trackers have to rotate on N-S axis only, why do PlTilt and PhAzim values change? - where can I found on PVsyst a formula on which is explained how these values are evaluated (if I can find it)? - Is it correct to define the PlTilt as the inclination of the tracker respect to the horizontal axis? If yes, it has to be fixed in my configuration, isn't it? - Is it correct to define the PlAzim as the inclination of the tracker respect to the Azimut? If yes, it has to be fixed in my configuration, isn't it? thank you for answering.