André Mermoud

In PVsyst all results values are for the global system. The GlobInc value is the average of the 3 GlobInc values, weighted by the nominal power of each sub-array.

You are probably using SolarEdge optimizers with fractional inputs. There is a bug with these devices and this situation in the verson 6.60, which has been corrected in V 6.61.

No. In PVsyst the results are only available as global for the whole system. If you want an evaluation of each subsystem, you have to perform an independent simulation for each one.

Technically, I don't see how your system will work. If it is really forbidden to reinject electricity into the grid, your system will only run when the full production is indeed consumed internally. As soon as the consumption goes below the inverter nominal power, unless there is a very special control device within the inverter for running at partial load (I don't know any device of this kind), this will stop working. Now the unavailability tool is not suited for this use. You cannot define more than 5 periods. The only way is the definition of the load in hourly values, and discard the energy reinjected into the grid. In this case you can recalculate the PR by yourself according to your hypothesis. You can also create an hourly file when performing the simulation, and calculate your balances by yourself in EXCEL.

Please check that you don't have a too high Vmpp value. See the FAQ Why the overload loss sometimes increases significantly without reason ?

This is not the right way of taking the not-used energy into account. You should use the option "Net metering", and consider the energy injected ito the grid as lost energy.

Please simply read my previous post

This has been fixed in the version 6.60.

We will not create a "Major" version 7. Our policy is now to improve PVsyst progressively, in an incremental way. Now the import of Sketchup and AutoCAD files is now possible in the version 6.60 (considered as a "Major" version by the introduction of a professional tool "OpenGL" for the 3D editor).

In the present time, you have the choice of taking the losses into account either before or after the transformer. We are deeply renewing this feature, and this will be improved in a next version.

The Inactive band is the extension of the mechanical structure, with respect to the PV module itself. NB: the bottom Inactive band is not significant in the "Unlimited sheds" calculation: the mutual shadings begin when the bottom of the PV modules become shaded, whatever the bottom inactive band.

The power derate of PNom(ac) as function of the temperature may be specified in the inverter's definition. The fan's consumption should be specified as "Auxiliary Loss" (in the "Detailed losses part). The inverter temperature conditions during the simulation may be specified in the "Miscellaneous tools" part.

This is corrected in the version 6.61.

In PVsyst V 6, you can define up to 8 orientations. In the version 5, this was limited to 2 different orientations only.

In PVsyst you can define sub-arrays for at most 8 orientations. However this is not possible with stand alone systems yet.

The pitch is the distance between identical points of 2 rows (for trackers: from axis to axis, for sheds: from base to base).

You can read my previous post, and also our FAQ How is the database of PVsyst updated?

Sorry, there is no progress with this in the present time.

As explained in the FAQ, the maximum voltage is the voltage on the I/V curve, when the voltage point corresponding to the PNom(Input) of the inverter is lower than the VmppMax of the inverter.

Please see the Help "Project design > Array and system losses > Array Thermal losses". However with a spacing of 3 cm, you don't have any air circulation and heat exchange (or a negligible one), and you can consider your PV array as back insulated.

If you have a little object's shade on a rather big PV array, the shading effect ,ay be very little. You can see it in particular situations with the "Animation" tool. If the annual shading effect is lower than the resolution of the percentages in your loss diagram, you will obviously not see it.

The Table width is a backtracking parameter, which should be identical for all trackers, as it is used in the backtracking calculation. If you pass from Landscape to Portrait, the table width is probably different, so that the backtracking calculation will be different. This is not possible in PVsyst where only one tracking orientation is possible. Now you can probably simulate your system without backtracking, which seems to be not suited for your project (especially if you have altitude differences between your trackers).

The specification of a percentage is just an indicative way of specifying the wiring loss (for showing an order of magnitude when designing your system). The real parameter used in the simulation is the Wiring Resistance, which is either specified explicitly or estimated from your choice of a percentage in STC conditions. The energy loss is calculated at each step of the simulation, as Rw * I².

Yes, this feature is implemented since version 6.27. In the inverter's derfinitions, please see the page "Output parameters".

Please compare the Loss diagrams for understanding where are the differences. Now in some very rare cases, it seems that the first simulation of a new variant doesn't take all the specified parameters into account. However we cannot fix the problem, as we have never reproduced it in our installations. It seems that this was only arising with rather old versions of PVsyst.