Jump to content

Search the Community

Showing results for tags 'near shading'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • PVsyst SA Announcements (read only)
    • Latest news
  • FAQ (read only)
    • Installation and use of PVsyst
    • Meteo data
    • PV Components
    • Shadings and tracking
    • Simulations : parameters
    • Simulations : results
    • Standalone and pumping systems
  • Your questions about PVsyst
    • How-to
    • Problems / Bugs
    • Meteo data
    • PV Components
    • Shadings and tracking
    • Simulations
    • Suggestions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 5 results

  1. Imported ground image is coming in the report even after decreasing the opacity to zero in near shading. It only does not show in the report for the first time. When opened next time report has image included.
  2. Hello, Can we incorporate parameters such as motor gap and piles gap in the near shading when creating the array of trackers? This way, the length of the trackers generated in the shading scene will align with the length of the trackers in my layout, accounting for these gaps.
  3. Dear all, Thank you for reading this post and I would really appreciate it if any advice could be given. I was always told that PVsyst has the ability to perform large-scale simulations in terrine areas. However, when I inputted the geographic model (made in blender or downloaded google map) into Pvsyst and clicked "fill zone", there is always penetration either between module-module or module-object. Is there any way that I could delete all overlapping objects with a single click or prevent overlapping objects to be created? Another question, I have been searching on the internet about this issue for quite a while now, and that I realized not one input the whole terrine into near shading. Is loading the horizon data enough? meaning this approach unnessery? Best regrads, Ivan Leung
  4. Hello everyone, I've been recently introduced to the concept of backtracking. Based on what I understood, the trackers are tilted in reverse to solar tracking to avoid mutual shadings between PV rows when the solar elevation is low. In that case, I would expect that the near shadings losses would be 0 (assuming that there aren't any other surrounding obstacles in the scene such as trees). I simulated a project with bifacial PV modules in a N/S horizontal single axis tracker configuration. The elevation of each tracker row does slightly differ as indicated by the topography. However, currently, we cannot simulate such a scenario, thus we assume that all trackers are of the same elevation, orientation, and size. Considering this brief explanation, what could be the issue causing the near shadings looses to be non-zero when using backtracking? If interested, I can share additional details, Any feedback is welcome, Regards
  5. In the Near Shading Tab, when computing the shading factor table i notice that when going from higher Pitch E-W to a lower one induces some shading at low heighta even with backtracking enabled. But then i go back into the construction perspective again and i close it out without changing any of the fields and recomputed the shading factor table, the shading in the low heights is not there anymore. Is this a glitch on PVsyst? If it is, It would be greatly appreciated if this can be taken, as i would have to run shading factor table twice every time i run simulation going from higher pitch to a lower pitch. Than k you,
×
×
  • Create New...