dtarin

Disable mppt share. Set to 14 modules in series, 30 strings.

Correct.

They will select one of the default values PVsyst has generated to the right of it.

Construct two identical zones, one in E direction, one in W direction. Populate, then relocate the modules from one zone next to the other.

If you are using backtracking, all tracker tables in the shade scene need to be at the same tilt angle. They can have different Z-axis heights, but the tilt must be the same throughout. The software isn't there yet for accommodating trackers on terrain with varying tilt angles while backtracking.

It is done the same way as with fixed tilt, by defining the partition size.

You should increase the number of modules in series.

You can set this in hidden parameters to allow a lower DC/AC ratio.

It means you have the MPPT enabled for multiple subarrays (4). Config 1 or 2 means you can have two different configurations if you wanted subarrays 1 and 2 to be together (input into same inverter), and 3&4 into another (or some other combination). To utilize the mppt share, check the square boxes you wish to have operate as such, and assign to a configuration, then balance Pnom ratios if that is the correct approach for your system.

The trackers imported with PVcase are single, individual tables. PVsyst requires a set of tables to be present in the shade scene. If you select a table in your existing shade scene and open the options, you will see there is one tracker row. If you set the number of trackers to 2, you will be able to utilize backtracking. Make note that when importing from PVcase, if your trackers are at different slopes in the N-S direction, you may run into errors, especially if trying to model bifacial.

Hello, I am getting what seems to be a bug for the HV transformer definition, cannot enter generic values. Anyone else? Version 7.1.5

Be sure to count the number of MPPT inputs in the system definition, so that it totals to one inverter. If you have 15 mppt inputs on the inverter, you should have 15 utilized in total between the mixed sub-arrays: sub array 1: 8 mppt inputs, N strings of module A sub array 2: 7 mppt inputs, N strings of module B Total mppt inputs: 15 Total inverters: 1

Is your pitch uniform in the shade scene?

Yes, I believe this has been an occurrence for quite some time.

Determine the power gain due to the back side through simulation, and multiply it with the front side current you would use with a monofacial module.

It does not include the electrical loss according to strings, as this is an electrical loss, not a light loss, and dependent on partition definition, electrical effect %, etc.

User NREL viewer, download the PSM TMY3 meteo file for albedo. https://nsrdb.nrel.gov/ Edit: SolarGIS also provides satellite based albedo for specific sites.

Are you referring to the mismatch loss? Yes, it should be lower for microinverters, <1%.

Hello, It would be great if users could select which variants they wanted exported when exporting a project. An expanding submenu where users check which variant to include is one example.

Search the forums, there are some existing posts. https://forum.pvsyst.com/viewtopic.php?f=25&t=5073&hilit=mppt Arrays 1 and 2 are straight forward. Arrays 3 and 4 in PVsyst are the two configurations for the last array. In these two arrays, you will check the mppt share box, and balance power Subarray 1: 48 strings, 33 modules in series, 4 inverters total Subarray 2: 24 strings, 32 modules in series, 2 inverters total Subarray 3: 10 strings, 32 modules in series, 5 mppt inputs (check "use mppt sharing") Subarray 4: 2 strings, 33 modules in series, 1 mppt input (check "use mppt sharing") I dont know what inverter you are using, but you can modify it to have 6 mppt inputs. Allocate 5 to subarray 3, and 1 to subarray 4. The link above should help. This will be equal to 1 inverter.

Hello, It would be helpful and useful if PVsyst added a button on the Detailed Results page which links to the UserHourly folder in explorer, similar to the batch simulation menu, where there is a button to open up the UserBatch folder.

Which PVsyst version? Under Hidden parameters > Verifications on Grid Systems, set "Inverter power is strongly oversized" to 0.1 ratio set "Limit overload loss for design" to 60%

Yes, it should match to what is stated in your OND file.

It is computationally intensive, and PVsyst will have difficulties with larger sites. If they are large enough, it will not work at all. 1MW is some threshold I imagine they determined in the past based on performance. In my experience, sites larger than 1MW can use the module layout method; however there still is an upper limit for how large a site can be processed, and it may depend on the nature of your model, computer system, etc., in addition to the software.

Hello, It would be helpful if PVsyst added a new shade scene object, called irradiance sensor or anything similar, to be inserted into the shade scene. This will allow users to place the device where and how their measurement device(s) exist in the field, and capture the POA irradiance accordingly. This object outputs in the 8760 the POA irradiance onto it as a new variable to the 8760. Energy calculations will not change, it is simply providing a new reference irradiance from the existing shade scene and model. As it is now, the weighted average method using each table in the shade scene for POA irradiance, does not capture the effect of complex terrain when very often plants are constructed with 1-2 measurement devices, and are performance tested with respect to these 1-2 devices. This will simplify the process and remove the need for multiple variants.