Jump to content

dtarin

Members
  • Posts

    800
  • Joined

  • Last visited

Everything posted by dtarin

  1. I think the minimum is two days, PVsyst wont let you simulate a single day.
  2. Phi is the variable to change for this exercise. Phi_min = Phi_max in the batch parameter file to simulate a tracker at angle. Tilt and azimuth should not be changed.
  3. You cannot simulate SAT with fixed tilt. You need two separate variants. Yes, you can simulate MV and HV losses.
  4. If your site is that large (GWs I assume here), you're better off running them in separate variants. Also with a site that large, you may not need to model the entirety in the first place, as long as you have a scene that is representative of the overall site.
  5. It does not, trees are solid, static objects.
  6. If your trees are over the terrain, you can place them onto the terrain with any offset desired using edit > set auto altitude. If your terrain surface is limited, and you need to add trees that are outside the boundary, then you can manually adjust the edges of your terrain by moving points individually in the X, Y, or Z direction (you can select multiple at once, it is not restricted to a single point, in case previous statement was misleading). After the terrain surface is adjusted, use auto altitude on all objects.
  7. You need an image of the modules on terrain, and then import and scale the image into pvsyst. You can then visually align the modules imported from CAD and the ground topography from Sketchup to the imported image.
  8. Include GHI. Day 1 could be a cloudy day.
  9. This can all be done with batch simulation. Advanced simulation > Batch simulation. Prior to running the batch, set the output parameters under Output File, and make sure File name is checked under Output file. You don't need to give any specific name, just have this checked (you will define the output file name in the batch parameter file in the next step). Then proceed to Batch simulation to set the parameters and configure the batch file.
  10. Once you have imported and set your PV panels, save the ground object as a shading object and delete it. You can always pull it back in. Do not reposition it prior to saving and deleting, and it will be imported exactly where it was last saved.
  11. It looks related to the advanced settings not overriding the project settings. Adjusting this worked, but is limited to 90, whereas there is no limit in advanced settings.
  12. Getting an error even though the thresholds have been adjusted in system settings. 7.4.7. Bifacial system.
  13. The PVsyst wind stow estimation feature is not available for Unlimited trackers N-S. Can this be added?
  14. Create multiple variants with the different bifacial settings you wish to test (height from ground, albedo), check the box below. Spacing and tilt are a little different, those inputs for bifacial inputs are derived from other places (i.e., shade scene, orientation menu).
  15. GlobInc. You might have reflections at low sun angles with that installation. For a fixed tilt system, these can be installed on a weather station free from shading and reflection.
  16. This can be seen in the orientation menu.
  17. My guess is that the warning is with respect to the HV portion, which you dont have shown in the image. The OND file doesnt account for LV losses. LV losses are zero since the MV transformer is connected to the inverter. You will define a MV line loss however from the MV inverter(s) to the HV transformer(s). Since the OND file accounts for the MV transformer, maintain 0% in the no-load and full-load loss.
  18. There is not unless you model each inverter separately in different variants.
×
×
  • Create New...