Jump to content

dtarin

Members
  • Posts

    626
  • Joined

  • Last visited

Everything posted by dtarin

  1. The central gap in PVsyst is for 2P trackers, and defines the spacing between the two modules in portrait. It does not define gaps for motors or bearings .
  2. Modify the ond file and reduce the number of mppt inputs. Save this as new file.
  3. It is the average temperature for the entire month using hourly data. You can export the data to csv and confirm under Advanced Simulation.
  4. You can export all of the necessary variables to determine what you have requested under Advanced Simulation. Select the required variables, and the software will export the data to a .CSV file. From there you can calculate what you need on a monthly basis. I dont know what peak capacity or export capacity mean, perhaps max instantaneous output power? A standard TMY weather file is a P50 simulation. Unless you have specifically a P90 weather file, you will need to calculate P90 from the P50 yourself.
  5. https://www.pvsyst.com/download-pvsyst/
  6. To my knowledge, PVsyst cannot run a meteo file which is longer than a year. So regardless of how you approach, it will split them up or you will manually. Convert the format of your CSV into the PVsyst standard you linked. Here is screenshot of what I did, it worked fine and created 23 MET files. You may need to adjust the hour shift or time shift (in minutes) depending on your location.
  7. It can import monthly data, it does not have to be a full year, and it will create hourly average. Screenshot below for a single month of 1-minute imported data.
  8. You can import 15 minute data and pvsyst will convert to hourly
  9. Near Shading Loss (ShdLoss) is the irradiance component (W/m^2) of the total shading, which includes beam, diffuse, circumsolar, and albedo shading. Near shading factor on global is the shading loss expressed as a derate factor, 1-FShdGl = shading loss in %. If you only want to understand the beam (direct) component of shading, this will be Near shadings beam loss, and Near shading factor on beam. From the help (note that the circumsolar component is missing):
  10. You wont be able to find DC voltage in the OND file, it comes from your PV system and is dependent on other factors. You will need DC voltage from the 8760 data. AC voltage is stated in the OND file.
  11. Go to create > elementary shading object. Wind turbines are available, as are other objects. If you need something specific, you can either build it piece by piece or use an approximate shape.
  12. I did find a bug, though, @Michele Oliosi. If I delete the orientation, select add new, I get an empty orientation. Double click, add fields, select all tables, and whether I click close or switch back over to the overview tab, the modules do no allocate to then new orientation, it stays at 0/0/0. It seems the only way to add tables to the orientation is to use the identify orientations button (doesnt allow custom allocation), or by right clicking on the empty orientation.
  13. your screenshot shows 0 tilt, 0 azimuth, and 0module area. i am assuming there is an issue with your pvc import, or you dont have any modules assigned from within the shade scene. go in and allocate tables to that orientation if possible. module image for reference
  14. I tested this in 7.3.1 and it worked fine for me. I imported a pvc file I set tolerance to 20, then identified Since I was starting with a tracker variant, i got this message. i went into system, changed to bifacial fixed tilt, then it worked fine. I then imported a different pvc scene for fixed tilt while fixed tilt was already selected under orientation menu (instead of starting from tracker variant). it showed 8 orientations, i changed degree tolerance to 20, then identified new single orientation. this is similar to your message i clicked close anyways with that message and got this message like i showed before then pressed update orientation parameters and it worked fine
  15. Did you save and exit the shading scene? There is often a dialog that appears to require the user to resolve the discrepancy between shading scene changes and the initial orientation.
  16. The auto altitude function works for fixed tilt systems, but does not adjust the tilt for trackers. There is an automatic tilt function available when creating a zone of trackers, but if the tables are already created, there is no way to adapt their tilt to the terrain, only their elevation. It would be great to add this feature.
  17. The number of transformers doesnt really matter in PVsyst, it will create a single transformer for the transformer loss calculation. For ohmic losses, calculate the total weighted average power loss for the entire system and use that for the medium voltage line input. From your previous post, if the total power loss of both circuits is 0.60%, that is what you will enter for loss fraction at stc (assuming that value was calculated at stc conditions). Regarding your previous post , the average loss would not be 0.1% for each transformer. In each circuit, each "leg" is carrying a different current value. The first leg is 1/3, the second is 2/3, and the last leg is 3/3.
  18. Certain software can export PVC files - PVcase (autocad), pvDesign, helios 3D, to name a few.
  19. What I described will accomplish this.
×
×
  • Create New...