Jump to content

dtarin

Members
  • Posts

    626
  • Joined

  • Last visited

Posts posted by dtarin

  1. 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. 

  2. 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. 

    image.png.af2d35afeacabaa34c5d1972fe43d7e4.png

  3. 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):

    Quote
    Linear shading losses  

    The Linear shading losses are computed from the Shading factors described above, and represent the irradiance deficit on the PV array.

    At each time step, the simulation will evaluate the shading loss on the Beam, Diffuse and Albedo contributions of the Meteo input data. These losses will be available in the results:

    ShdLoss Global linear shading loss  (or irradiance shading loss), total of the 3 contributions,
    ShdBLss Loss on the beam component,
    ShdDLss Loss on the diffuse component,
    ShdALss Loss on the albedo component.

     

  4. 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. 

     

    image.thumb.jpeg.190431c5f8548761906ec30fb65aafdf.jpeg

     

     

  5. 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

    image.jpeg.b991914cb25710cad7fbc0e39f1ed6d3.jpeg

  6. I tested this in 7.3.1 and it worked fine for me. 

    I imported a pvc file

    image.thumb.jpeg.d51bf8a58ebe49e9d49e8ec80fee9cd2.jpeg

     

    I set tolerance to 20, then identified

    image.thumb.jpeg.4b893f722c78b35d4a11807ace7cfe7f.jpeg

     

    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. 

    image.jpeg.026ef2b028ea0ffcd36869a25f4574d9.jpeg

    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

    image.thumb.jpeg.cd3208958afbfcf6dc56a849aa3cdb70.jpeg

     

    i clicked close anyways with that message and got this  message like i showed before

    image.jpeg.4d2ad796c37e82f92adf5f48676ddc6e.jpeg

     

    then pressed update orientation parameters and it worked fine

     

    image.jpeg.53294538d5dd99d331ba601f0c086237.jpeg

  7. 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. 

  8. 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. 

×
×
  • Create New...