Jump to content

dtarin

Members
  • Posts

    897
  • Joined

  • Last visited

Recent Profile Visitors

36756 profile views
  1. Why not adjust the bifacial albedo to 0.7? If this reflector is not flat on the ground, maybe Sunsolve can simulate it.
  2. If bifacial is disabled, the variables will not be available, same for the horizon loss.
  3. DiffGnd definition missing from documentation.
  4. You can download time-series data (20+ years) from https://nsrdb.nrel.gov/data-viewer. From there you can calculate it manually from GHI or import each year into PVsyst. You can also get ~18 years of data at PVGIS free https://re.jrc.ec.europa.eu/pvg_tools/en/#MR.
  5. Go to output file, check the box "file name" under "output file". Set your variables. The name doesnt matter. Hit okay. Go to aging tool, have your ageing parameters set, I check both output file and report (to see everything ran correctly), click run simulation from within the ageing menu. it should output then.
  6. It would be helpful to include this in the next update. We've had to use custom tracker approximations to avoid long waits for diffuse recalculations when making other unrelated model updates.
  7. It is expected for plant/inverter clipping to decrease as system capacity degrades.
  8. Bumping this. Any plans to incorporate this in future versions? Modern design software spit out shd or pvc files quite easily (both should be able to be imported). I think the only hangup with this is the partition definition for each shade scene, but if this were added to 3D shadings parameter, the user could define the geometric area of a partition that gets applied to each scene. Diffuse shading can be set to central tracker for quick analysis by default, backtracking activation is already an option for batch sims.
  9. Curious why you have included the +1 there. You can simulate a tracking system at [X,X] for min and max to lock the tracker for all hours to a single angle. If you need to more than one angle, this can be done with batch simulation easily.
  10. Auxiliaries tab: proportional to inverter output power (i.e., 1 W/kW = 0.1%, etc.).
  11. If the sensor(s) is in front of the torque tube and other items, (GlobBak+BackShd) * 𝜑 is sometimes used. Install sensors midpoint between two piles for tracker systems.
  12. Ohmic loss is proportional to power. Abu Dhabi has much higher irradiance compared to Berlin. Also, not sure if it is intentional, but you're simulating the 10th year of operation. If unintended, be sure to set it to year 1 on the degradation tab. Ohmic losses - PVsyst documentation
  13. This looks like an AI bot or something...
  14. Still present in 8.0.16, don't see mention of correction in 8.0.17 or 8.0.18 release notes.
  15. You are modeling "detailed according to module layout". You need to place these modules in the tables in the module layout menu. Select "according to module strings" and it will use the shade scene as it has been provided. The total area of the shade scene is relatively close to the pv system.
×
×
  • Create New...