dtarin

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.

Since the inputs are equally loaded in all inverters, it may not matter much if it power shares or not. There will be some variation between inputs on a single inverter, but it wont be very drastic. Modeling as two arrays with multi mppt off should be sufficient. If you're skeptical about the clipping losses, model a single inverter with 18 strings, and then in a separate run one inverter with 27 strings. In any case, you will not want to use the mppt feature with setting Pnom identical, since power will not be shared between 27 string inverters and 18 string inverters.

It depends on your design. I dont know about those Huawei inverters specifically, but some string inverters have jumpers which share the power input across all inputs, instead of running independently. Using the jumper will distribute the power when inputs are loaded differently. a) Do you have some inverters with a mix on the inputs? For example, there are 9 total inputs on an inverter, 7 of them are 2 strings each, and 2 of them are 3 strings each? b) Or do you have entire inverters with 3 strings per input for all inputs (i.e. 27 strings per inverter), and others with 2 strings per input (i.e. 18 strings per inverter) If it is a, separate the mixed inverters from non-mixed inverters (if it is the case): for the mixed inverters, count the total number of inputs with 2 strings per input, and set as one array. Count the number of inputs with 3 strings per input, and set as another array. These two arrays will use the multi mppt feature. The non-mixed arrays will not, and you will simulate normally. If your inverter operates the mppt channels independently, and does not power share between inputs, do not set the Pnom ratio to be the same. If they do power share, set Pnom ratios to be equal for the multi mppt arrays. If it is b, dont use the mppt option, and have two arrays with the total number of inverters for each design (2 strings/input, 3 strings/input)

Same procedure for daily and monthly calculation: 1. Get total energy output of plant for time period, Egrid (in kWh, MWh, etc) 2. Calculate hourly average of irradiance 3. Use basic calculation E_Grid/(Sum_of_hourly_POA*DC_Plant_Size) Example: Egrid = 4800 MWh DC size = 2990 kW Sum of hourly POA = 1940kWh/m^2 (4800*1000)/(2990*1940) = 82.7%

- Discriminating orient difference between shading planes I believe this can be thought of as the resolution to which PVsyst will define a unique orientation based on the difference with other sheds - Maximum orient difference for defining average spread orientation This parameter will be used to define the range for which an average value will be calculated and used for transposition. See: https://forum.pvsyst.com/viewtopic.php?f=3&t=2524&p=6730&hilit=Discriminating+orient+difference+between+shading+planes#p6730

Hm. I can readily design a system with 2 tables at 15 and 20 degree tilt. -I select multiple orientations under orientation and define the two orientations. -In system tab, I have two sub-arrays, each one assigned to one of the orientations. -In project settings/other limitations, I have defined the limits to be 1 degree and 10 degrees respectively (I have modified this in hidden parameters as well). -In the shade scene. I have created one table at 15 degrees and one at 20 degrees. -In tools > edit orientations menu of the shade scene, I confirm the tolerance is 1 degree, and that two orientations are defined, with modules allocated to each.

PVsyst is averaging/combining the two different orientations into one. Set a lower discriminating orientation difference and maximum orientation difference to keep the two orientations separate.

By curved surface I meant import ground data (.csv) which approximates a curved surface to give his modules tilt and baseline slope.

Create subarrays under system. Use the number field at the top left to increase. Enter the desired number , hit enter for it to generate new subarray.

Export the loss diagram waterfall to excel. Click report, then export. This will export the losses, irradiance, and energy values. You should be able to calculate using this.

You can download PVGIS data here: https://re.jrc.ec.europa.eu/pvg_tools/en/tools.html

Hello PVsyst team, It would be helpful if Power Factor was added as a variable to the batch simulation process. Is it be possible for users to modify row 12 and add a power factor variable here in the mean time? 1 PVsyst simulations Batch mode; 2 Simulation parameters definition; 3 File Created on 19/03/20 11:25; 4 ; 5 Project ;;;PROJECT_NAME.PRJ; 6 Variants based on;;VCZ;VARIANT_NAME; 7 ; 8 Please define the parameters to be varied for each run; 9 Don't modify anything in the column titles !; 10 Only the lines beginning by "SIM_" will be executed; 11 ; 12 Ident;Create hourly;Mod. quality;Simul; 13 ;file;loss;Comment; 14 ;File name;[%];; 15 ;

It should remain 15.6cm (or enter whatever the actual cell size is for your module). You are already defining that there are three partition sections (1 for each bypass diode), and by defining the cell size 15.6, you're then by deduction defining two cell rows per bypass diode/partition.

Unlimited sheds can. For one module in landscape, define Nb of strings in the width of one row as 3; but you're likely to get a better result if modeling in 3D shade scene (how much better I cannot say). This would only be true for landscape orientation. If modeling in 3D shade scene, with 1 in landscape, and a string size of 5, your partition size would be 3 in height, 5 in length.

You can model this in 3D shade scene by configuring your partition size to account for the string optimizers and bypass diodes.

Hello, It would be very useful if PVsyst were to allow inverter curtailment specific to each sub-array, such that a single project can contain a system where multiple inverters are curtailed differently.

This would be a nice feature and very useful at this time. For your initial issue of having all of your PVsyst files centrally located on a network, have you thought about using DropBox or some other similar app where you keep your teams PVsyst files, instead of your work network? It is pretty fast when your internet connection is decent, and changes to files would be saved pretty quickly. In the event you are without internet connection, they'll update any changes once connected. Copies are stored locally on your machine so there isnt any performance issue when accessing them.

To remove special graphs from reports, go into settings and uncheck it.