dtarin

EArray MPP is the energy output of the array prior to the inverter losses.

What is your string size? With half-cell modules, in landscape orientation, you would not see any benefit from the bypass modules, as both halves will be shaded during row-row shading conditions, across the length of the row/string. In portrait orientation, with regular row-row shading, you could see some benefit, and if you have 2 in portrait, you would define 4 strings in height. If there is considerable shading from trees or buildings, this would not likely be the case, and you would model strings in their full size.

Have you adjusted your mismatch loss and partition size in the shade scene when modeling MLPE in PVsyst?

It will give you that error. First complete the system design portion of your model, exit system menu. Then go to the shadings menu and create a shading scene to remove the error.

Are there significant shading objects? If not, there is no need to model the full 1 GW. If there is, your machine may not be able to run it (like currently). Choose a smaller portion of the plant to model to represent the entire plant. Also try running on fast simulation mode.

1. Yes 2. Yes, they will need to add in total to the number of mppts for all inverters in design. If you are encountering high overcurrent losses in the waterfall, allocate more mppt inputs to the subarrays with higher DC/AC ratio. If it is even, allocate them evenly.

You are not modeling a full inverter. You have selected to use MPPT inputs, and have selected 1 input, which means you are using 1/2 an inverter; your inverter shows it has 2 MPPT inputs. Set the number of mppt inputs to 2, and you will be modeling with the full inverter capacity. Note that is says "inverter power used" is showing 25kW, not 50kW.

During LID test measurements, modules are flash tested prior to undergoing light exposure, and the LID loss is relative to this flashed value. The input in PVsyst does not distinguish between the two; it just reduces your output by whatever value you input. So you can enter both values, the module quality adjustment based on FTD and the full LID value (standard practice), or add the module quality adjustment value to the LID loss and include as a single value in LID, setting MQF then to 0.

Err on the side of caution and model as shown.

Will the inputs to the inverter be connected together, or operated independently? if independent, you may have higher clipping losses. Some string inverters have jumpers which connect the inputs together, and typically will lower your clipping losses in these unbalanced scenarios. Photo 1 shows the configuration to use to model your scenario, however a string size of 21 seems too high for a 1000V inverter, but your location is not known, so I cant say for certain.

You are essentially shading 50% of your system the entire time? To get backtracking you need minimum of two tracker rows in a tracking field. Create two tracker fields, each with 2 trackers. Place one inside a parallelepipede. See image.

Create a system with 8 strings per inverter.

Your DC AC ratio is very, very low. My guess is that the peak irradiance which occurs for the SAT is when the trackers are at 0 tilt, compared to the FT system @ 22 tilt, and therefore during peak irradiance hours, the FT system is producing more than the SAT, and it is causing some clipping. The tracker will have higher production before and after peak irradiance, but because irradiance is lower, it's not reaching the production limit of the inverter. So overall it is producing more energy, but not during peak irradiance conditions.

An Excel VBA macro can accomplish this.

There is not. You need to create two variants.

Create a custom format to import your weather file, and include RH Import meteo data > Custom file

Only one tracker pair needs to be defined throughout the shade scene for backtracking. Place this tracker pair anywhere in the shade scene. The rest can be single trackers, however they need to be spaced apart exactly to what your pitch is.

In the open project, select from the "Meteo File" drop down menu the file you wish to use, and save the project. Then complete your run. By default PVsyst looks for meteo files within 10km of your project site (defined in your Site File). If the meteo file is outside this range, you can either update your site file, or expand the search area under Project Settings > Preferences.

I'm not exactly sure, but if your simulation times are not acceptable on slow sim with the full shade scene as you desire, run it on fast sim. Shading losses will be slightly higher but the model will run faster.

You have an error preventing it to save in your system definition. There is a way to save however even with an error. You need a second variant in the project. In the variant with the error (the one shown), switch to another variant in the project. You should then receive a prompt asking if you want to save the variant first, click yes.

The map feature was patched in version 6.88. As for NREL, there may have been changes on their databases which makes it no longer work (they decommissioned some older databases recently). You can access NREL PSM here and download the weather file manually: https://maps.nrel.gov/nsrdb-viewer/. Use meteonorm to create your site.

Here is a sample file, this should help.

PVsyst team, The global incident below threshold value is no longer seen on waterfall in PVsyst version 7.0. Is this now accounted for somewhere else, or rather, has there been a change associated with it? Thank you.

I cannot seem to import a project from v6.84 into v7.0. Is it possible to do so? Edit: It seems the error occurs when clicking "No" or "No to All" when importing a project and there are some existing files in the database. In order to import successfully, I must select Yes to All (or Yes to each individually) for it to import.

This was to show that your design with 27 strings per inverter will have high losses and unless you change your design, it should be expected to have high clipping losses. You havent mentioned DC AC ratio yet, but I presume it is high with 27 strings.