I have recently recomputed a system shading table According to module strings and am seeing significant changes in the shading losses.
What is driving this significant change? Is it a change in backtracking?
For context, this is a 126 MWp single axis tracking system with the shade scene imported from PVCase and is generally flat with a small amount of sloping land.
Thank you Michele, I followed your suggestion and ran some processing in excel and it worked well.
It would be interesting to see if limiting the rest angle for Backtracking makes it's way into pvsyst as it seems like this is becoming a common method for mitigating glare for roadways etc.
Hi, I need to model the yield considerations for limiting our backtracking angle to >20 degrees is there a way to do this in PVSyst?
For context, we need to do this to limit glare at times when the sun angle is very low.
So instead of setting an upper limit to backtracking angle I am wanting to set a lower limit so that the panels do not get lower than 20degrees during low sun angle times. Is there a way of doing this that you are aware of?
Hi, thank you, I did have to zoom right out and eventually found an object that was a long long away from my arrays which I deleted and the shading scene then imported well.
I am having this exact issue, has any update on this been made?
I can confirm that the unit of measurement for my 3D software is meters and I am trying to import in meters.
It also imports in millimeters but is far smaller than it should be.
Hi team,
I am trying to import a Met file which I have the GlobHor for, as soon as I create a MET file out of this, it modifies the GlobHor and decreases it massively.
Why does this happen and how can I avoid this so that the true GlobHor is used?