dtarin

Hi emilie_g, Once your zone is created with tables, you can uncheck the zone icon at the top menu bar, and then simply shift+click the modules you want to remove from the zone and press delete.

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,

Hello, Is there a variable for outputting soiling loss in the 8760 file? Thanks.

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.

I dont have them in my library, but RECOM has a bifacial module.

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

Is it possible to have trees or other objects be automatically placed onto ground terrain?

In hidden paramters set default module spacing to 0 and and reimport, see if that helps.

Set the small array to 0.3, the larger to 0.7.

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.

Is the overall system size 41.3kW DC, 33kW AC? If so, use fractional inputs option in both arrays.

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

btw: there's no need for windPro, you can simply download SRTM-Data in GeoTiff from here http://opentopo.sdsc.edu/datasets?listAll=true Can you elaborate on how to use GeoTiff data with PVsyst? What program do you use to extract the terrain data? Thanks.

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.

Do the 5 inverters each have (1) 20 string and (3) 21 strings? If so, you will create two sub arrays, each with 5 inverters and multi mppt checked. Subarray A has 5x20, subarray B has 15x21

Module quality (negative indicates over performance)

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

Yes, by using the multi-mppt feature on the inverter, you can. If your inverter does not have it built in, you will need to add it yourself by modifying the OND file. Here is some discussion on the feature: http://forum.pvsyst.com/viewtopic.php?f=3&t=2668&p=7107&hilit=multi+mppt#p7107

Hello, Is this a typo in the attached image? The units on the graph axis shows celsius, but the Voc coeff is given in %/ degK.

1) I believe it is the number of rows in your design. 2) Yes, where shading losses are due to the preceding row.

Picture did not load. This has happened to me before, but I cannot recall how I fixed it. Did you try creating a new project?

It depends on the inverter. You can use multi-MPPT function and create three subarrays, one for each orientation.

Perhaps something like this? https://www.nde-ed.org/GeneralResources/Uncertainty/Combined.htm

Hello, I have two different ground images imported into a shade scene. Is it possible to change which one is viewed on top? Thank you.

Hello, Often we need to make adjustments to tree heights once survey data has come back. After having performed an initial topo survey, created a ground object based off this data, and dropped trees and panels onto the ground object, it can become tedious and time consuming to then go through and update every tree or other objects individually. It would be useful and efficient if all of the parameters for a tree (or some other object like parallelepiped) were available in the modify objects menu (when selecting multiple objects). These fields already exist individually, and perhaps just need to be linked to this menu. That way, when certain objects need to be adjusted in in some way but remain in the same location or keep other parameters fixed, one or more fields can be modified in the parameter(s) needed and have the others kept constant. Currently, it looks as though PVsyst accepts the new height (for example when modifying a tree) and distributes the change across all of the parameters.