dtarin

In the heterogeneous array tool, we can select modules at a given string size and view the graph, but it would be very useful if we could also export this data to csv, similar to how we can when viewing the graphs in the PAN file. If there were the ability to select string size and # of strings in parallel from the PAN file with the different variable options that are there, that would be even better.

I do not think there is anywhere (where someone would build solar) that has a low temperature of 30 degrees C, and I wouldn't recommend forcing the design to accommodate what the customer thinks is correct. As Michele noted, you are not concerned with average site temperature, but the lowest temperature at which there may be sufficient irradiance. If you design to 30 degrees C, your inverters will most likely have frequent start-up issues and the warranty of all components will be in jeopardy. That is not a 1,500V design.

The best way for Autocad is assuming that you have contour lines, Remove/freeze everything from the drawing but the topography (contour lines) Explode down to minimal size (each polyline will breakdown to have a segment of three points) Run dataextraction command, select "line", and select the data for "Start X, Start Y, Start Z", export to csv If your drawing is in feet, convert to meters for PVsyst, save into .CSV value with one header row, X, Y, Z Import into PVsyst. You may need to take a screenshot of the autocad drawing with terrain and with modules and import also into PVsyst so that you can then line everything up in the shade scene.

Create two separate variants, they cannot be modeled together. You can export the final outputs to excel and combine.

Determine the total, weighted loss fraction and use that. PVsyst will auto-calculate length based on the wire size. Let it do that, as long as the loss % is correct, and you end up with a representative value in the waterfall.

You can select multiple items and change a parameter for all selected items at once. I don't think this can be imported.

Possibly, but why are degradation and degradation dispersion are so high for 1st year?

You can use software or do it manually. You know the conductor size, length, max current carried, etc. in each segment. Calculate the loss for each segment. Then you can combine into a total loss, or keep separate. Each segment should be treated separately. If the loop is from MVPS 1 to 2 to 3 to 4, the current along the way will increase.

And to extend what Ander provided, what I have done in the past is if there are ground obstructions/collisions with the tables or trackers, lower the ground image in the Z coordinate just enough so that it clears everything once the tables have been set to the terrain-specific elevations. It will then still capture most of the impact of the terrain. You can run the check for interpenetrations tool to see if it has been resolved. It is often the case though that there may be irregularities in the terrain data, for example if you are looking at existing terrain conditions for a tracker system, the tracker may extend over odd and irregular areas of ground terrain since they are so long. If your site is small the number of instances are few, you can edit the ground terrain directly. If you have a large site and many instances, lowering the entire ground image may be most efficient.

NREL SAM might be a better option for this type of analysis, Voc is a variable you can output and viewin the results, so modifying tilt and checking the output is possible.

Tilt and orientation will vary the current mostly as this changes amount of irradiance received. Temperature will affect the voltage more; irradiance, not so much.

https://www.pvsyst.com/help/index.html?csv_ground_data.htm

select the objects and rotate 180

Not to my knowledge. You can view the data, but it wont tell you something like this. SolarGIS Analyst might be what you are looking for.

In PVsyst shading menu, under tools, there is an option called "orientations management". In there you can see more details on which tables are assigned to which orientations. If you wish to change the number of orientations from 8 down to 1, you can also do that inside that menu.

Run a full year simulation at the stow position. Identify the hours of stow according to your own methods then replace the hours under stow in the regular yearly output with the data from the stow simulation. This will give you an expected production delta when you compare the two.

Use batch simulation. You can define simple parameters like GCR, number of strings, etc. You may want to consider a simple variant (unlimited sheds, etc) to get faster run time or ability to change pitch if you are interested in that. Batch simulation is where you create one variant, define in a csv file the simulation parameters for each simulation, 1 per row. PVsyst will step through each one and simulate one at a time and output the 8760 data for the variables you have selected.

import reference images from the source you are importing from. CAD layouts, google, etc. use reference image to line up the objects. I would first move the image to match the PV and wind turbines, then move the terrain, just easier to select one object vs many

Yes, in the shade scene, you can pull up all objects and export all data. It is under tools menu.

See thread here.

EArray = EarrMPP - (IL_Pmax + EGridLm) Clipping losses.

separate array into separate areas, import one at a time, save the objects on each import within PVsyst once saved, then open them all up in single shade scene. if the file is that big consider if you are importing trivial things. if there are significant trees, consider deleting them and adding the trees from within

Yes, as long as string size is the same and the input currents are within inverter spec, you can do anything. But the question is not that, but instead if mppt inputs can be jumpered. With chint inverters, they can, at least for the 50 and 60kw versions. Haven't used string inverters in a while. We ran into a situation where they weren't jumpered in the field and we were getting high losses/overloading. After they were jumpered, we saw expected performance. havent used Huawei so don't have anything to help you with them specifically at the moment.