Jump to content

Search the Community

Showing results for tags 'bug'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


  • Community Calendar

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 4 results

  1. Hi all. With the recent update of PVSYST to the 7.4.0 version I have see that the shading electrical losses are too much higher comparing with the previous version. Launching the same simulations of a PV plant (using the same parameters and the same Near Shadows scene, the shadings losses goes from -0.34% (in 7.3 version) to -3.41% (in the version 7.4). Could it be a possible bug? Is is possile to the new version overestimate this kind of losses? Near and far shadow losses factors change too but the value are similar this only happens with the shading electrical losses. Thank you very much.
  2. Hello, I have noticed a serious bug in the output file with missing data typically around 6:00 in the morning and 19:00 in the evening for about 20 days of the year. This was the result of uploading the generic PVSyst load profile LOADPROFILE_Commercial_BDEW_G4 which has no "0" data entries as shown here - Within the design, there were no "unavailability" loss parameters set, so the system shouldn't be shutting down with zero outputs or inputs for any time of year. I am requesting help resolving this.
  3. Hello, It seems like the Batch mode does not work correctly since the latest PVsyst update (7.2.16). After filling the parameter file with all the data needed and starting the simulation (first picture), PVSyst won't calculate every simulation as it did until then but will stay on an "initialization" state (as displayed on the window) a couple of minutes and end the calculation just after (second picture). When you open the results file, almost every simulation has an error message refering to an oversized inverter (third picture). These errors don't make sense as running a classic simulation with the exact same parameters (including in the settings of the batch mode in PVshows no problem of any kind (fourth picture). Also, even with an obviously smal number of MPPTs for a simulation, the batch mode stil considers it as oversized (it happened when I filled the cell with 3 instead of 10 for the SIM_3 for instance). This problem has been occuring only since the latest update as the previous batches I ran had no issues. My intuition is that PVsyst now understands the number in the "Inverter or MPPT" cell as a number of inverters and no more as a number of MPPT as it was before. How would it be possible to solve this problem ? Thanks in advance PVsyst team and members
  4. I would like to report following bug: Please see on the enclosed picture, field “Table choice”. It shows Table Row#66 Col#3, but on the drawing, it shows Row#36 Col#3 (hidden by comment) and in yellow Table Row#66 Col#3, Module depending on module and Inverter #6 String #8 or #depending on position. I believe that shown on the drawing is wrong (Row#36 Col#3). Here is Col# right, but that is not the rule. Additionally in the yellow box Inverter# do not correspond to the list of inverters MPPTs and strings. I see this as serious inconsistency in program markings and suggest to be corrected.
  • Create New...