Jump to content

JolD

Members
 View Profile  See their activity

  • Posts

    4

  • Joined

  • Last visited

  1. JolD
    Hi PVsyst Team, Every since updating to v7.4, I am seeing hugely increased electrical losses from shading (according to strings). I am regularly seeing the electrical losses being more than double the near shading losses. This is on projects with proper partitions and without excessively large strings (e.g. ~17 modules). I'm seeing these excessive losses especially on projects with terrain (even if it is virtually flat) and still see large losses on tracking projects with backtracking activated. This is a major change in behaviour and has had serious implications for projects that are mid-development. What is particularly frustrating is that the Shadows Drawing and the shading animation over a day within the construction view are now unresponsive. Do you have any workarounds to reactivate the shadows animation? I'm trying to understand what is driving these losses and find ways to mitigate these excessive losses. I saw your advice to reduce the electrical effect to 80-90% but that is nowhere near enough to mitigate the additional electrical losses. Any advice would be gratefully received, especially if there is any upcoming patch to fix these issues. Many thanks.
  2. JolD
    Just FYI - the latest update seems to have fixed this problem. Many thanks!
  3. JolD
    Using both PVsyst v6.8 and v7, I've recently been having issues importing NREL / NSRDB TMY data when creating a new site. No matter what location within North America I choose, I get the same message: "NREL NSRDB data unavaialble for your location". Is this an issue with the API? This only started happening a few weeks ago. Any help gratefully received!
  4. JolD
    Hello, When I create a new meteo site in the United States, no matter where the location, if I try to import meteo data from NREL NSRDB, I get an error message saying that "NREL NSRDB data unavailable for your location". I tried numerous locations in the US (all of which worked previously), but I get the same message. Is there a problem with the API? I've tried using both v6.8 and v7.0 and get the same error. Many thanks in advance for your help.
×
×
  • Create New...