Jump to content

dtarin

Members
  • Posts

    777
  • Joined

  • Last visited

Posts posted by dtarin

  1. Hello,

    It would be helpful if module specific inputs were listed for each module in the PDF report, such as IAM profile, LID, etc. For LID it looks like it gives an average both in the waterfall and in the simulation parameters section on page 1 or 2, which makes it impossible to confirm which test data has been used for each module.

    Thank you.

  2. Hello,

    I have two tracker arrays shown in attached image one, where the length of rows is different for the two blocks. If they are set to zero azimuth and placed adjacent to one another (with the spacing shown in image 1), there are no errors. If I change the azimuth to say 12 degrees (image 1), I get the error message shown in image two. The two arrays are separated by >5m. Is there a bug which arises when the azimuth is changed? The arrays need to be separated by more than 11.12 meters for the error message to go away. PVsyst version 6.63.

    Thanks.

    186665528_image1.jpg.ad0cd848ade70d99f0e3c22c9678aa2d.jpg

    1218867802_image2.jpg.84d9d101fade71f40552f96064873531.jpg

  3. #1) In a N-S tracker system, pitch is the E-W distance from post to post for the tracker. This can be verified in the shade scene once constructed.

    #2) The option is called Tilted Axis to select N-S tracker.

  4. Hello,

    I am trying to use the parameter optimization feature with a shade scene to simulate different azimuths, but the feature is not working. It works with unlimited sheds, but not when I have a shade scene. There is only one orientation in the shade scene. PVsyst version is 6.66. Also occurs with 6.63. Does anyone else have this problem?

    438462696_optimizationerror.jpg.d34a5dd677a32a890f0062dce105244f.jpg

  5. If you are talking about DC ohmic losses, just enter the percentage you want to use. Click the cursor into the wire resistance field above after updating the percentage, and then click back below into the percentage field. The mOhm should update when you first click into it after updating the percentage.
  6. Hello,

    When running a batch simulation in a project, I have specified different variants to run for several simulation lines. When I look at batch results, the values for all simulation runs (regardless of the variants specified) show only the results from the variant that the batch simulation is being initiated from. So if I want to run a batch simulation for variants A, B, C and execute the run in variant A, I only get data from A.

    Is it possible to do what I am trying to do? I had thought that I could specify different variants under Simul field and the batch simulation would run that simulation variant within the project.

    Ident;Meteo data;Create hourly;Soiling;Simul;

    SIM_1;A.MET;AA.csv;1;A;

    SIM_2;A.MET;AB.csv;1;B;

    SIM_3;A.MET;AC.csv;1;C;

    Thanks,

  7. Hello,

    I am aware of what the differences are between GlobEff and GlobInc as stated in the PVsyst documentation. What I would like to know is if one of these is better suited for evaluating plant performance depending on the irradiance sensor used, such as a pyranometer or Si reference cell? And perhaps not just GlobEff, but the other corrected incident energy parameters as well. What would be a physical or practical application of these parameters?

    Thanks.

  8. Make sure you click on "Apply" after you defined the X1 and X2 points or else nothing will happen.

    Thanks Sylvain.

    Has anyone experience problems with the ground object scaling being removed after reopening the project? I have experienced this with different projects and it is time consuming having to re-apply scaling with correct referenced dimensions. I am wondering how could I avoid this? Thanks.

     

    Update to 6.64.

    http://forum.pvsyst.com/viewtopic.php?f=4&t=3036&p=7765&hilit=ground+image#p7765

  9. Yes, this is annoying. It has to do I think with the default settings for module spacing. Best case is to set it to zero in hidden parameters, so that when you import a project or shade scene, it doesnt rearrange the table by changing the table size. If the scene was set with .01m, and your default is .02, there wont be enough room in the table, so itll switch orientations and make number of modules accomodate the table. It would be nice if PVsyst automatically adjusted, or had an option where hidden parameter settings dont override the shade scene like that.
  10. Where is your TMY data from? Maybe you can:

    1) change the coordinates in the tmy data file to match the site you want to use. The import into PVsyst as usual. When you load your project, you will have your desired site selected, and then you can switch to your MET file with the desired tmy data

    2) create the site, then use the ASCII input method to import your tmy data, selecting the site you want to be associated to it

    3) change the project settings and increase the distance allowed for met files to be used from the site

    63155089_metfiledistance.png.4bdf7a9dc9d14ecbb46c167651a675e4.png

  11. Hello,

    Since PVsyst cannot model trackers on uneven, undulating terrain, does anyone have any information or guidance on how one can approximate performance of single axis trackers with backtracking for these cases? Has anyone done any analysis with data from a site with these terrain conditions, to come up with some sort of de-rate factor?

    Thanks.

  12. Pitch: Post to post distance

    Coll. band width: width of the modules regardless of angle, i.e. if two in portrait, coll. band width is length of module * 2 + spacing between modules

    Inactive band: distance the underlying structure extends past the module area. Often times this is zero.

    GAOR: collector width/pitch

    1082111550_8-3-201710-27-10AM.png.bf53d32f47cbe76ea250e121399e41a1.png

×
×
  • Create New...