pvsyst-tutorial-v8-grid-connected-en
pvsyst-tutorial-v8-grid-connected-en
PVsyst is a comprehensive software tool designed for the simulation and analysis of
photovoltaic systems. It allows users to design and optimize solar energy projects by
providing detailed assessments of system performance, energy yields, and financial
viability.
With PVsyst, users can model various types of PV installations with location-specific
climate data and component specifications, while considering factors such as shading
effects on the system, battery storage, grid unavailability and panel degradation.
This document can be seen as a user’s manual, aiming to describe the different windows
and feature of the software. The complete reference manual for PVsyst is the online help
that is accessible from the program through the “Help” entry in the menu, by pressing
the F1 key or by clicking on the help icons inside the windows and dialogs.
Recent projects will allow you to quickly find and modify your recent projects.
1.2 Utilities
The Utilities section in PVsyst offers a range of tools and functions designed to enhance
the understanding and the precision of your PV system analysis.
• In Databases you can find all the sites and components already stored in PVsyst.
You can also generate new sites, import weather data and create new
components.
1.3 Documentation
In the Documentation section you find a direct access to the PVsyst Help, the complete
reference manual for PVsyst, also accessible from pvsyst.com/help. Throughout the
software, context-sensitive online help is available via the F1 key and small question
mark icons inside the windows and dialogs, providing more specific information in
certain cases. By using the F1 key, or clicking at the question mark icon, you arrive at the
PVsyst help tool where you can find useful articles with precise information,
explanations and step by step description of how to use different function the PVsyst
software.
You also find the access to the PVsyst forum where you can post your questions and
PVsyst collaborators and other Pvsyst users will guide you forward.
In the PVsyst video channels you find educative videos and tutorials. You also find these
printable users manuals and tutorials here.
1.4 Toolbar and Workspace
It is from the Main page that the settings are made for your entire workspace.
When files are saved, they will automatically be saved in the workspace, in a precise
folder structure. In the workspace you also find a set of templates with the correct
configuration, to be used for instance to define a self-consumption profile. PV
components will be saved to ComposPV, project files will be saved to Projects, etc.
• Under File you find the for example the options to import and export projects and
components.
• The Preliminary design is an easy and basic simulation tool for small and
simplified projects.
• You can start a new project through the Project tab. Here you also find a fourth
type of project not visualized in the Project design and simulation window, that is
the DC-grid project, for the use case of certain public transport companies. From
the Project tab you can also load a project in your workspace or a DEMO project
defined by Pvsyst, that showcase various features and examples of utilization.
• In the Settings you have Preferences where you could for instance define user
info, units to be used as default and possible API keys for certain weather file
providers. In the Advanced parameters, almost all the default values and
thresholds that generates error messages can be modified, but should be
modified only by experts.
• Language can be changed in this language tab, or by clicking the F9 button.
• In the License tab you find all the information about your Account, activation key
etc.
2 My first simulation
For this first explanatory tutorial, we choose a Grid connected system, but the majority
of steps and information will be relevant also for standalone and pumping systems.
The Workflow in PVsyst is to work in Projects and in Variants. This also illustrates the
hierarchy of the software.
Project contains the geographical site of your system, the reference to a file with the
meteorological data and some general parameters like the albedo definition and
parameters specific to this project. The project will be the central object that allows the
basic definitions in which you then will construct different variants of your system.
The system variant contains all the detailed definitions of your system, which will result
in a simulation calculation. These definitions include the choice and number of solar
panels and inverters, geometrical layout and possible shadings, electrical connections,
different economic scenarios, etc.
It is in the Project settings you set the limit overload loss for your design, that per default
is set at 3%. If you wish to design a system with a high Pnom ratio, you can increase this
value to avoid warning messages. You here also have the possibility to change other
design parameters, such as the transposition model.
In the Project you must first define the Project’s name, choose your site and define a
weather data File. The site file contains the coordinates of your project, that is used to
calculate the sun position each hour of the calendar year. The site file created will also
include a fallback monthly weather data which is used for fast and rough calculations in
the design part of the program.
There are 2 ways to define a project site. You can either choose a site from the list or
create a new site by typing the name or using the interactive map. You can also import
site if you have data from somewhere, or from another project.
When creating a geographical site, you can directly import Weather data from a list of
weather data providers, such as Meteonorm, PVGIS, Solcast, Solar Anywhere and
Salargis. For the import to work, you need to have a working internet access. The imports
are automatic based on the coordinates of your site.
It is up to you as a user to evaluate which weather source provider that is most accurate
for your project. For certain providers you need an additional license to have access.
Meteonorm data is included with the PVsyst license, using ground and satellite data and
utilizes monthly averages to create synthetic hourly values using stochastic models. TMY
(Typical Metrological Year) data on the other hand are meteorological hourly data files
constructed on the basis of real measured data series chosen among at least 10 years of
real measurements, according to several statistical criteria.
The data imported are in hourly values, the values are then averaged and displayed as
monthly values. Depending on weather source, you are also provided with Global
horizontal irradiation year-to-year variability, thus the natural fluctuations in the amount
of solar energy received on a horizontal surface from one year to another, that can be
used to calculate statistical analysis such as P50 and P90 of the energy yield predictions
of solar PV systems.
By clicking OK, you will be prompted to save the geographical site, and the synthetical
hourly weather data that have been generated (if your weather source is based on
synthetic data). By clicking open a summary of your weather data is available. Note
that PVsyst is labeling a generic year as 1990.
You may define multiple field types by clicking Add Orientation at the top of the dialog.
To define an Orientation, choose the Field type in the drop down list. The header will show
the name of this orientation. If the box on the right is checked, this will define a name
according to the main parameters of the orientation; but you may give any customized
name.
The field types have in common that you must define the plane tilt and azimuth. In
general, the plane tilt is defined as the angle between the collector plane and the
horizontal. The plane azimuth is the angle between the collector plane and the direction
toward the equator. In the northern hemisphere, this means the azimuth is measured
from due south (toward the equator), with positive values toward the west
(counterclockwise): south = 0°, west = 90°, north = 180°, and east = -90°. In the southern
hemisphere, the azimuth is measured from due north (toward the equator), with negative
values toward the east (clockwise): north = 0°, west = 90°, south = 180°, and east = -90°.
In the fixed planes definition, PVsyst displays a quick optimization tool, indicating the
energy yield as a function of the tilt and the azimuth. This is a rough estimation meant for
judging how your orientation choice (violet point) will affect the yield with respect to the
optimum. This may show the annual, summer or winter yield.
In the seasonal tilt adjustment, you have the possibility to optimize the PV production, by modifying
the tables tilt depending on the season. This option allows to define two seasons with a
corresponding plane tilt and you must specify the months for the winter and the summer position.
It is possible to define unlimited sun-shields on a façade. The sun-shield rows parameters are
defined in a similar way as the unlimited sheds.
In a similar way as for unlimited sheds, you may define "unlimited trackers" for
parametric study of a PV trackers system, without using the 3D scene construction.
The axis azimuth refers to the orientation of the axis, where an azimuth of 0 correspond
to an axis running in the north to south direction. The rotation angle around the axis is
called Phi. Mechanical limits on the Phi stroke are required. Phi 0 corresponds to a
horizontal axis; the minimum phi is the lowest angle authorized (counter clockwise from
the horizontal axis) and the maximum phi contrary is the highest angle authorized
(clockwise from the horizontal axis).
The backtracking option will prevent shading between rows of panels by adjusting their
tilt angle based on the sun’s position. The irradiance optimization option will evaluate the
optimal tracking angle on the basis of the transposition model: the angle is adjusted in
order to get the best transposition result of GlobInc, considering the Beam and Diffuse
components.
The other parameters are the same as for “Unlimited sheds”. Note that the electrical
shading parameters are only visible when the backtracking is not activated, as by
definition there are no mutual shadings in backtracking mode.
As in “Unlimited Trackers”, you must define the axis orientation and tracking limit angles.
You also have the possibility to add an Axis tilt. You must define the Phi limits
(mechanical stroke), the backtracking strategy, and the tracking calculation mode
(astronomic calculation or irradiance optimization) to be used during the simulation. An
additional parameter, Wind stow defines a security rest position, to be set during the
simulation when the wind speed is too high.
With trackers with a vertical axis, the collector is kept at a fixed tilt but rotating according
to the sun azimuth. This configuration may be used with "dish" arrangements, when a big
rotating support holds several rows of modules; this particular case is made possible as
the rotating axis of one row may be displaced with respect to the collector. The plane tilt
and the azimuth mechanical limits of the tracker must be defined.
It’s possible to define a tracking sun-shield. You need to specify the facade orientation,
as well as the minimum and maximum tilt. Optimizing the balance between sun
protection and PV production is challenging. The backtracking strategy is likely the only
reasonable approach for operating sun-shield trackers.
The tracking horizontal East/West refers to system where the rotation axis normally is
running east/west. With an Axis orientation of 0° in the northern hemisphere, the panels
will be oriented south and the minimum and maximum tilt will define the mechanical
strokes to follow the height of the sun in the southern direction, i.e. mainly the seasonal
variations. This is available in PVsyst, though is only used in very special situations.
Two-axis solar trackers adjust both the tilt and orientation of solar panels to stay
perpendicular to the sun's rays throughout the day. You must define the stroke limits for
both the tilt and the azimuth.
There are specific scenarios of 2-axis tracking system. The plane is always perpendicular
to the sun's rays, the tracker orientation within this plane is different. This may lead to
different mutual shadings. You have to define here the parameters related to the
orientation. The mechanical frame characteristics (size, width, etc) will be defined when
creating the 3D field representation. The backtracking may be done between trackers
within the frame, not between adjacent frames.
4 System
In a grid-connected projects, the system is defined as the set of components constituting
the PV-array, i.e. the PV modules, inverters and the design of the array, here separated in
the different background colors.
4.1 Sub-arrays
You can manage (add, copy, rename, move and delete) in the list on the left of the dialog.
There is a Pre-sizing help available, in the upper right corner in the system window. This
tool will suggest an automatic sizing of each sub-array, where you can specify either the
desired nominal power, or the available area for your modules.
When designing the array, the number of modules in series has to stay within the
requirements of
By clicking Sizing, you find a specific tool that gathers all the constraints relating to the
sizing of a specific system.
• For the number of modules in series and strings: the upper diagram shows the
I/V curve of the PV array, together with the MPPT range, voltage, power, and
current limits of the inverter. The little black dot should be within the safety
limits. In Project setting, these numbers can be modified if needed, this will not
affect the simulation, but the sizing and the IV curve.
• For the inverter sizing: the second graph, known as the system output power
distribution graph, illustrates the annual distribution of power generated by the
photovoltaic system. The horizontal axis displays power intervals, while the
vertical axis shows the total energy produced within each interval. This graph
highlights the most common power ranges, offering insights for optimizing
inverter sizing and assessing possible overload losses.
The optimal sizing of the inverter is based on the acceptable overload loss throughout
the year. It usually leads to over-size the power ratio (PV array nominal power with
respect to the inverter nom. AC power), by a factor of 1.25. Note that this is a first rough
estimation and that you later can define different losses such as near and far shadings.
Specialized tools are also provided to evaluate different losses due to wiring, module
quality, mismatch between modules, soiling, thermal behavior, mechanical mounting,
system unavailability, etc.
4.3 Multi MPPT and Power sharing feature
The MPPT technology, short for Maximum Power Point Tracking, enables a solar inverter
to independently track the maximum power point for each string or group of panels. Thus,
in the case of different length of strings or panels oriented differently on your site, in the
case of partial shading due to objects nearby or in the case of soiling; the multi-MPPT
allows the system to mitigate the impact by adjusting the operation of the affected
strings without affecting the others.
Choosing the option Pnom sharing within the inverter, PVsyst will equally distribute the
Power over the MPPT inputs automatically. If you have different configurations at the
input of Multi-MPPT inverters, you should define a sub-array for each kind of
configuration.
5 Detailed losses
There are several parameters that are initialized by PVsyst with reasonable default values
for the first simulation, but that you should modify according to the specificities of your
system to add more accuracy to the simulation. These parameters are accessible with
the button "Detailed losses" in the project dashboard.
5.1 Thermal parameters
The thermal behavior of the array is computed in each simulation step by a thermal
balance. This establishes the instantaneous operating temperature used for the
modeling of the PV modules.
The thermal balance involves the Heat loss factor:
The thermal loss effect is shown on the array loss diagram in the final report.
The ‘Standard NOCT factor’ (Nominal Operating Cell Temperature) is the temperature
that the module reaches in equilibrium for very specific surrounding and operating
conditions. It can often be found together with the module specifications supplied by the
manufacturers. It has no real relevance for the simulation because the conditions for
which it is specified are far from a realistic module operation. PVsyst only mentions it for
completeness and for comparison with the manufacturer’s specifications.
5.2 Ohmic Losses
The wiring ohmic resistance induces losses (R · I²) between the power available from the
modules and that at the terminals of the array. These losses can be characterized by just
one parameter R defined for the global array.
In many large PV installations (in the MWp range), the transformer is not part of the
inverter, but an external device directly connected to the MV or even the HV grid.
• One or several Medium Voltage transformers for the whole system. PVsyst will
distribute equally the power output of all inverters to all transformers.
• One Medium Voltage transformer in each sub-array. The transformer properties
may be different in different sub-arrays, but each sub-array has to have one
transformer.
• There is the possibility to add a High Voltage transformer that steps up the voltage
before the injection point.
The IAM model is defined with the PV module parameters, page Additional data,
Customized IAM. If the IAM curve is highly over evaluated with respect to the Fresnel’s
laws, you will have a warning message while opening the .PAN file. An over evaluated IAM
curve could lead to an overestimation of your system’s production.
In the Additional Data, Customized IAM you can modify an over evaluated IAM curve by
choosing the Default Fresnel. This manipulation can also be done through the detailed
losses window, IAM Losses tab.
5.7 Aging
The PV module degradation gives rise to a progressive loss of efficiency, which we will
characterize by a Degradation Loss factor.
The simulation may be run for a specified year of the PV system life and will apply the
degradation for this year. The degradation means a decrease of the PV array yield. It may
sometimes have some "positive" effect on the full system behavior, which may lessen a
little bit the degradation effects. This may be namely a diminution of the overpower
losses when the inverter is strongly undersized.
The Manufacturer's warranty should be understood as a lower limit for any individual PV
module. In this tool we define an average degradation rate (for a set of modules). This
loss value may be much lower than this guaranteed limit. Some experimental studies
mention degradation rates of the order of -0.3%/year measured as an average on several
modules (and measured with very old modules manufactured in the years 80-90, with
old technologies). Long-term degradation rate measurements are relatively scarce.
NB: Nothing prevents to limit the lifetime of the PV modules to 25 years. A well-
maintained PV system may probably stay operational over much longer periods.
When spectral correction is enabled, the simulation by default uses the set of
coefficients associated with the PV module technology. However, it is possible to modify
this setting by unchecking the corresponding box and selecting another set of
coefficients from the available options. In this case, the coefficient set will no longer
adapt to any changes in the PV module in the system definitions, and it is the user’s
responsibility to ensure a relevant set is chosen for the simulation.
The FirstSolar spectral correction model uses the Air Mass and Precipitable Water
Column as input variables. The air mass is computed from altitude and sun position,
while the precipitable water has either to be present in the weather data file, or be
estimated from relative humidity. Therefore, this correction can only be applied in the
simulation, if either the precipitable water or the relative humidity are present in the
weather data variables. For synthetic hourly weather data files created with PVsyst 6.7.4
or later, the relative humidity is always present.
6 Self-consumption
The self-consumption in PVsyst allows users to assess how much of the solar energy
generated by the PV system is consumed locally within a specific building or facility. This
analysis helps to understand the proportion of their electricity needs that can be met by
solar energy. This type of system is connected to the grid, and any excess energy can be
fed back into the grid when it is not being consumed by the user.
There are various options to define the load profile:
• Fixed constant consumption is the most straight forward method to define the
user's needs. You simply specify a constant power or yearly energy.
• Monthly values allow you to define monthly averages, which the simulation will
treat as constants throughout each month. There is no daily modulation.
- Values are defined using the graphic tool in the "monthly values" tab.
7 Storage
The battery storage implementation in PVsyst include to 3 storage strategies:
• Increased Self-consumption
• Peak shaving, when the grid-injection power is limited
• Weak grid recovery, for ensuring an electricity supply when the grid is failing.
Each of these strategies have different constraints. For instance, the self-consumption
and Weak grid recovery require the definition of a user's needs hourly profile, where Peak
shaving doesn't involve a user's needs profile. The battery energy will not be used for
feeding the grid, except with peak shaving. The time of release of the battery energy
(discharge) may be different according to the strategies, cost optimizations, etc.
The sizing of the different parts of the system (PV array, battery pack, as function of the
load profile and the electricity price), is a complex problem, specific to each of these
On the right side of the battery configuration, you can see several figures that summarize
the properties of the battery pack.
• The Battery pack voltage will be rounded to an integer value.
• The global capacity (C10) of a battery refers to the battery's total energy storage
capacity when discharged over a 10-hour period. In this context, "C10" indicates
the amount of energy in ampere-hours (Ah), the battery can supply continuously
for 10 hours before its voltage drops below a specified threshold. This value
helps characterize the battery's performance under a moderate discharge rate,
commonly used for evaluating storage systems.
The battery pack capacity is closely related to the user's needs. Ideally, the remaining
energy below the SOC higher level should allow to cover the maximum needs for the
longer unavailability period. You can obviously diminish this capacity, at the risk of
feeding failure.
8 Horizon
The horizon profile is suited for shading objects that are located sufficiently far away from
your PV system, so that the shadings may be considered global on your array. This is the
case when the distance of the shading object is more than about 10 times the PV system
size. The Horizon Profile is a curve that is defined by a set of (Height, Azimuth) points.
The Far Shadings operate in an ON/OFF mode: i.e., at a given time, the sun is or is not
present on the field. When the sun is behind the horizon, the beam component becomes
null. The effect on the diffuse component will be explained below.
Clicking the "Horizon" button will open a graph of the sun paths for the site of the project.
For horizon profiles established using a geo-reference grid (like PVGIS and Meteonorm),
the exact location should be carefully defined. You can edit the latitude and longitude in
9 Near shading
The "Near Shading" window is the main dialog providing access to the 3D editor for
constructing scenes representing nearby shading. This functionality is essential for
simulating the shading impact on photovoltaic (PV) modules, thereby calculating the
resulting energy losses.
The "Construction/Perspective" button is the key element for accessing the 3D scene
editor. This allows defining surrounding objects that may create shading, such as
buildings, trees, or other obstacles, to accurately model the PV modules' environment.
It is important to note that the primary objective of near shading is to precisely represent
irradiance losses due to nearby objects and to help optimize the solar panel installation
to minimize these losses. When defining objects that may create shading, as well as the
topography, it is advised not to get too detailed and avoid spending time drawing every
object precisely. The more detailed the 3D scene, the longer the software will take to
calculate shading on the PV scene. Therefore, it is preferable to keep the drawing simple
and representative of the project to ensure efficient calculations.
First, there is a dropdown list for the different existing orientations. Next, information
about the number of sub-fields, the surface area of existing PV modules, and, finally, the
total number of PV modules is displayed.
Matching orientation between the 3D scene and the orientation definition is mandatory.
If an incompatibility is detected, the program will ask if you want to update the orientation
definition to match the 3D scene.
Regarding the PV modules' surface area, the software accepts a tolerance for differences
between the system definition and the 3D scene. This tolerance accounts for slight
variations that may occur during scene construction while ensuring consistent surface
areas.
Finally, the total number of PV modules should be close between the system definition
and the 3D scene, with a small tolerance accepted.
Linear Shading
This mode only considers the irradiance deficit on the PV field without electrical effect.
It represents a lower limit of total shading losses. You can run this simulation quickly (by
interpolating values from the shading factors table at each step) or more accurately but
slower, calculating the complete shading factor at each simulation step.
By Module String
While creating the 3D scene, you can group the modules into distinct strings. With this
option, a shading factor is calculated for each string, and the electrical losses related to
shading on each string are estimated individually. This provides a more detailed estimate
of the electrical effects than a simple linear shading calculation.
Table
The Table button enables you to build the shading factor table, which calculates the
shading factor for different directions from which sunlight comes.
This process calculates the diffuse and albedo attenuation factors, which remain the
same throughout the year.
Following this, you can view the Iso-shading diagram and start the simulation.
If you set up a partition in module strings when building your 3D model, two tables will be
generated at the same time: one for the standard "irradiance" or "linear" shading factor,
and another based on the module strings.
First Strategy: You can create your PV tables as well as objects that will cast shadows
on the PV tables.
Second Strategy: You can import a 3D scene created with another software. The
following formats are supported for import:
3DS, DAE, PVC, H2P.
Third Strategy: This involves combining the first and second strategies. You can import
a PV scene and then modify it in PVsyst by adding additional objects that may create
shading.
It is also possible to import a topography with a satellite image of your site specified in
the "Project" section.
File menu
Several actions are available:
New Scene: Allows you to create a new
scene by clearing the previous one.
Read Scene: Loads a previously
exported scene using the "Export Scene"
function.
Read Building: Loads a building
exported with the "Export Selected
Element" function.
Read Object: Loads an object exported
with the "Export Selected Element"
function.
Object Creation
The first section is dedicated to creating different scene objects. PVsyst allows creating
a variety of 2D and 3D objects to represent elements like buildings, trees, roofs, and other
architectural obstacles. You can choose from a library of basic objects (2D and 3D
shapes, construction elements) and assemble them to build more complex objects. It's
also possible to customize the terrain topography by creating specific ground objects.
Created objects can be adjusted in terms of dimensions and position to fit your PV
installation layout.
In the shape type, several models are available:
First, there are surface models, which are simple, elementary 2D shapes, and surface
models, which are elementary 3D models.
The Angle Between Planes tab helps users understand the angle value between the
normal of two PV table planes by adjusting their orientations. Users can experiment to
see the angle difference between two PV planes, which appears in the "Angle Between
Planes" area.
Automatic Altitude: Opens a tool to place PV objects above other objects automatically.
Backtracking Management
PVsyst’s backtracking management tool optimizes the backtracking strategy to minimize
mutual shading between PV trackers. It identifies two reference trackers to calculate the
backtracking angle for all scene trackers. This tool is accessible in the PVsyst 3D editor,
In 3D scenes, trackers are often defined independently in external CAD software, but
PVsyst groups them into tables, making it necessary to identify a reference tracker pair
for full backtracking calculations.
This tool lists distances between neighbouring trackers in descending order. Selecting a
tracker with the highest ground coverage ratio (GCR) allows for a recommended
neighbour tracker (highlighted in orange) to associate with. Users can set backtracking
reference parameters automatically or select specific tracker fields in the list.
Selection:
• Default Selection: Press Esc to deselect an object.
• Click any object to select it; click edges in technical view to select an object.
• Rectangle Selection: Shift+Ctrl+R
o Click and drag to draw a selection rectangle.
o You can specify whether you wish to select all objects touching the
rectangle, or only those inside it.
• Lasso Selection: Ctrl+L
o Click and drag to draw a selection area.
o You can specify whether you wish to select all objects touching the area,
or only those insides.
• Add to Selection: Hold Shift
• Remove from Selection: Hold Ctrl
• Select All: Ctrl+A
Point of view
tab.
Zoom Options
Zoom In: F7
Zoom Out: F8
Zoom by Rectangle: Click and drag to define the viewing area.
Fit Zoom: Ctrl+F - Zooms to see all selected objects.
All these tools are also accessible in the View menu.
Module Chains: Displays the module chains defined in the module layout.
In the "View / Rendering Options" menu, you can enable/disable the following:
• Enable anti-aliasing: Smooths object edges. Availability may depend on your
hardware and could reduce performance.
• Enable real-time shadows: Enables real-time shadow viewing. Activating this
option may reduce performance.
• Enable camera animation: Animates the transition when switching views.
Activating this option may slightly reduce performance.
• Show backfaces: Shows or hides the back faces of objects, meaning those not
oriented toward the viewpoint. Hiding them increases performance.
Measure
Measure a Distance: Ctrl+L - Click to set the starting point, then click again to set the
end point. Hold Ctrl to snap to an object vertex.
Measure an Angle: Ctrl+K - Click to set the vertex, then points #1 and #2. Hold Ctrl to
snap to an object vertex.
Modify
Edit Objects: Ctrl+M
Move Objects: Ctrl+B
Additional Tools
Field zones: In the shading scene, you can define areas that will be filled with PV
tables. These zones are defined on the X-Y plane as drawn on the ground, with tables
dynamically placed in the scene. The tables are positioned based on the objects they lie
on, so if a zone is drawn on a roof, tables will be positioned accordingly at the correct
altitude. This also applies to zones on topographies. You can specify if you want the
tables to automatically tilt according to the object they are on.
Creating Zones: To create or edit zones, click the **Zone tool**, then find the "Zone
Editing" section on the right side of the window
This button
opens the table field editing dialog to define
parameters for the tables generated within the
zone.
Exclusion Zone: Finally, it is possible to define exclusion zones where tables won’t be
10 Energy management
In PVsyst, energy management encompasses functions related to the inverter
temperature, power factor, grid power limitation, and P50/P90 energy yield analysis.
These features collectively aid users in optimizing and managing the energy performance
of photovoltaic systems in PVsyst.
10.1 Inverter Temperature
Inverters are responsible for converting the direct current (DC) electricity generated by
solar panels into alternating current (AC) electricity for use in the grid. Inverter efficiency
decreases as its temperature rises. Higher temperatures can result in increased losses
during the conversion process, leading to lower AC power output. By precisely choosing
the temperature model approach for the simulation of the inverter temperature, you can
more accurately estimate and evaluate the inverter's efficiency, system performance,
safety and reliability. The inverter’s temperature profil and evalauation for limits can be
found in the PVsyst inverter file (.OND file) under Output parameters tab.
The relationship between active and apparent power is quantified by the power factor
(PF), which is simply the cosine of the phase angle (φ). Power factor is crucial because it
indicates how efficiently electrical power is being used:
𝑃𝑎𝑐𝑡𝑖𝑣𝑒
𝑃𝐹 = 𝑐𝑜𝑠(φ) =
𝑃𝑎𝑝𝑝𝑎𝑟𝑒𝑛𝑡
In photovoltaic systems, inverters convert the direct current (DC) from solar panels into
alternating current (AC) for grid integration. With modern inverter technology is possible
to control the phase angle between voltage and current. This allows the inverter to
generate reactive power without additional energy consumption. By adjusting the phase
shift between voltage and current, PV systems can support grid needs for reactive power
without compromising their active energy production.
Reactive power plays an essential role in compensating for the reactive loads, typically
introduced by motors or transformers in the grid. This compensation is often a
requirement set by grid managers to maintain grid stability. By adjusting the phase angle
(φ), inverters can either "absorb" or "generate" reactive power, depending on the needs
of the grid:
Lagging reactive power: When the current lags behind the voltage, with a positive phase
angle, φ > 0. Defining a lagging PF in your inverter means the inverter will inject reactive
power into the grid to help compensate for reactive power demand of inductive loads
such as motors and transformers.
Leading reactive power: When the current leads the voltage, with a negative phase
angle, φ < 0. Defining a leading PF in your inverter means the inverter will absorb reactive
power from the grid (or “consume” it), helping to counterbalance the excess reactive
power generated by capacitive loads.
When inverters are required to produce reactive power, it does not affect the active
energy output directly. However, depending on whether the inverter’s nominal power
(PNom) is defined as active power (kW) or apparent power (kVA), the inverter’s capacity
to handle overloads may be affected. If PNom is based on apparent power, the maximum
available active power will be reduced by a factor of the power factor:
𝑃𝑁𝑜𝑚(𝑎𝑐𝑡𝑖𝑣𝑒) = 𝑃𝑁𝑜𝑚(𝑎𝑝𝑝𝑎𝑟𝑒𝑛𝑡) ∗ cos ( φ)
In PVsyst simulations, the power factor is an adjustable parameter, typically fixed for a
given period or specified monthly. The simulation results focus on active energy (in
kWh), but when a power factor is defined, the apparent energy (in kVAh) is also
calculated:
𝐸𝐺𝑟𝑖𝑑
𝐸𝐺𝑟𝑖𝑑𝐴𝑝𝑝 =
cos (φ)
The apparent energy will always be greater than the active energy due to the inclusion of
reactive power.
The nominal power rating of inverters may be an active power or apparent power:
• In the case of active power rating, reactive energy does not come at the cost of
active power.
• In the case of an apparent power rating, reactive energy may come at the cost of
active power, when close or at the maximum power threshold.
In the Power limitation dialog, you can define one value for the grid limitation that will be
applied throughout the year. The limitation may be defined: