8 Frequently Used PVSyst Manual Operations Beginners Should Learn

When you read the PVSyst manual for the first time, many screen names, settings, and technical terms appear all at once, making it hard to know where to start. In particular, for photovoltaic simulations the location, weather data, orientation, tilt, PV modules, PCS, losses, shading, and result reports are all interrelated, so remembering individual button operations alone can easily lead to confusion in actual practice.

For beginners, the important thing is not to try to understand all the features from the outset. A quicker approach is to first master the operations most frequently used when evaluating projects, following the actual workflow. PVSyst project design provides a framework for performing detailed simulations: a project mainly stores geographic conditions and meteorological data, and multiple calculation cases are handled as variants.

This article narrows the focus to eight frequently used operations that beginners reading the PVSyst manual should learn first. The aim is not to cover every fine-grained feature, but to put you in a position where, on your first project, you can proceed through data entry, checking, comparison, and explanation without hesitation. Rather than memorizing the operations themselves, understanding from a practical perspective—why settings are made in that order and where to look to catch mistakes—will greatly change how you read the PVSyst manual.

Frequent Operation 1: Lay the groundwork for conditions to be considered by creating a project

The first task you should learn is creating a project. When reading the PVSyst manual, it’s helpful to first understand what a project is, because that makes the subsequent screen layout easier to organize. A project is not just a filename; it is a container that brings together the target site, meteorological conditions, and the assumptions for the power generation system under consideration. If you proceed without clarifying this, it will be hard later, when you look at the simulation results, to explain under which conditions the values were calculated.

What beginners should be mindful of when creating a project is to clearly record the project name, location, and study purpose. For example, even for the same site you may have multiple study cases such as an initial proposal, detailed design, shade-condition check, or capacity-change option. If the initial naming is sloppy, you won't be able to distinguish them later when similar cases are listed. When working while referring to the PVSyst manual, don't focus solely on filling in the input fields; it's important to use names that will be meaningful to people in your organization who see them later.

When creating a project, it is also important not to introduce complex conditions all at once. The official PVSyst tutorial shows a workflow in which you first define a project with a geographic location and meteorological data, create the initial variant with a minimal system configuration, and then progressively add elements such as far shading, near shading, and losses.

This way of thinking is also effective in practice. If you try to set everything perfectly from the start, it becomes difficult to isolate the cause when the results differ from expectations. First create a basic case, then add conditions one by one; this makes it easier to track which settings are affecting energy production and PR. When reading the PVSyst manual, it is also easier to understand if you treat "Project", "Variant", and "Simulation result" not as separate items but as a continuous workflow for managing study cases.

Common Task 2: Verify Location Information and Weather Data

The next frequently performed operation you should learn is checking the site information and meteorological data. In photovoltaic power generation simulations, which location’s solar irradiation, temperature, wind speed, and so on are used has a major impact on the results. Beginners tend to focus on the number of modules and PCS capacity, but if the underlying meteorological data do not match the project site, no matter how detailed the equipment conditions you set, reliability will not improve.

When reading the PVSyst manual, keep in mind what to check on the screen where you select meteorological data. First, do not judge solely by the site name: check the latitude, longitude, elevation, nearby observation stations, and the type of data being used. If you are using data from a location far from the project site, conditions can differ significantly in mountainous areas, coastal areas, snowy regions, and urban areas. In preliminary studies you may proceed with approximations, but even then it is important to be able to explain which data were used.

In PVSyst, project design and simulation involve detailed simulations at hourly or finer time steps, and the results include many variables such as meteorology, solar radiation, energy production, and losses. Therefore, the meteorological data you enter is not merely an assumption but becomes the reference when interpreting the results later.

What beginners often stumble over is feeling reassured simply because they have selected a weather dataset. In practice, you need to check whether the solar radiation is not extremely high, whether the monthly trends match your regional sense, and whether the temperature conditions are reasonable. Especially when there are multiple candidate weather datasets, running simulations under the same system conditions and comparing the differences in the results deepens your understanding. When reading the weather-data-related sections of the PVSyst manual, it is important to treat them not just as operational instructions but as input items that are directly tied to accountability for the results.

Frequent Operation 3 Set orientation and tilt to determine power generation conditions

The third frequently performed operation is setting the azimuth and tilt. Azimuth and tilt are the basic parameters that indicate which direction the photovoltaic array will face and at what angle it will be installed. As installation types change—ground-mounted, rooftop, carport, sloped terrain, folded-plate roof, etc.—the approach to determining the optimal azimuth and tilt also changes. When beginners read the PVSyst manual, they should understand this not simply as a screen for entering angles but as an important operation that determines the assumptions for energy production.

When setting orientation and tilt, first verify input values from drawings and site conditions. The array plane is not necessarily a single surface depending on the project: south-facing, east-west facing, single-pitch, installations on multiple surfaces, etc. If there are multiple orientations, consider whether they can be grouped under the same conditions or should be treated as separate sub-arrays or azimuths. PVSyst provides a menu for defining azimuths, and it presents the concept of assigning related sub-arrays to each azimuth. When defining a 3D scene, you also need to be aware of the relationship with the 3D field where PV modules can be placed.

A common mistake for beginners is misunderstanding the sign and reference for the azimuth. If you enter the angle from the drawing directly without checking the on-screen input rules, it can end up oriented opposite to your intention. Beginners also sometimes confuse the roof pitch angle with the array surface tilt angle. In practice, after entering the data, making a habit of checking monthly generation and insolation trends for any unnatural bias makes it easier to spot errors.

Orientation and tilt also affect subsequent shading conditions and system configuration. For example, an east-west arrangement has a different power generation peak time than a south-facing one. When examining PCS capacity and the DC/AC ratio, the generation curve differs even for the same installed capacity, so you cannot judge by simple total capacity alone. When reading the relevant sections of the PVSyst manual, treat the angle input not only as an entry operation but as a setting that connects through to the interpretation of downstream results.

Frequent Operation 4 Configure Module and PCS Combinations

The fourth frequently performed operation is configuring the combination of solar modules and the PCS. This is the operation where beginners are most likely to feel they are "simulating", but it is also a part where configuration errors tend to occur. Enter the module model, quantity, number in series, number in parallel, number of PCS units, MPPT configuration, etc., and check whether the system is valid.

When reading the PVSyst manual, it is important to understand first that you should not "enter a capacity" but rather "create an electrically valid combination." Module open-circuit voltage, operating voltage, temperature conditions, the PCS input voltage range, maximum input current, the number of MPPTs, and so on are involved. Beginners tend to try to match only the total kW, but in reality having too few or too many modules in series causes problems. In particular, voltage rises at low temperatures and voltage drops at high temperatures require attention because they affect whether the system is electrically viable.

In PVSyst's project design, the workflow explains that users define the orientation, choose specific system components, and design the PV array according to the selected inverter model and other choices. In other words, module and PCS settings are not merely entries of catalog values but are central to configuration studies tailored to the project conditions.

What beginners should learn from this operation is not to ignore warnings and messages. In PVSyst, alerts may appear for the combination of inputs you provide. At first, when a warning appears you may not understand what it means and want to move on. However, those are exactly the design checkpoints. By examining each warning—voltage range, oversizing, capacity ratio with the PCS, sub-array assignment—you will deepen your understanding of the manual.

In practice, the granularity of equipment information used at the proposal stage and at the detailed design stage can differ. In the early stage you consider representative specifications, and in the detailed stage you may replace them with actual model numbers. Therefore, when learning to operate PVSyst from the manual, it is important to be aware of which stage the study is at and to manage provisional settings separately from finalized ones.

Common Operation 5: Enter Loss Conditions to Make It Closer to Reality

The fifth frequent operation is entering loss conditions. In solar power generation simulations, you consider not only the power output under ideal solar irradiance but also the various losses that occur in real installations. Soiling, wiring resistance, temperature, mismatch, IAM, equipment outages, degradation, and other loss items are many, and this can feel difficult for beginners.

When reading the PVSyst manual, rather than trying to memorize all the loss items at once, it becomes easier if you classify them by "why energy production decreases." For example, soiling is a factor that reduces the light reaching the module surface. Temperature losses are factors that reduce output when the module temperature increases. Wiring losses are factors where the generated power is lost in the process of passing through cables. Mismatch is a factor that lowers overall output due to variations between modules or strings.

In PVSyst's system definition you can modify detailed losses such as soiling, IAM, module temperature, wiring resistance, module quality, mismatch, and shutdowns, and the impact of each loss can be checked in the simulation results and the loss diagram. For this reason, loss settings are not "set and forget" — the complete procedure includes verifying on the results screen how much they affected the outcome.

What beginners should be careful about is being able to explain the meaning of initial values, even when using them as-is. Not every project has detailed measured data. In initial evaluations you may use standard values. However, if you cannot answer questions such as "what loss are you assuming here?" in proposal materials or internal reviews, the credibility of the simulation results will be diminished.

Also, loss conditions should not be set excessively finely. Even if you enter precise numbers with weak justification, you only increase apparent precision and do not necessarily get closer to reality. Beginners should first aim to understand the meaning of the main losses and, when there are project-specific conditions, be able to judge which parts should be changed.

Common Operation 6: Check shadow conditions step by step

The sixth frequent operation is checking shadow conditions. Typical areas where beginners reading the PVSyst manual tend to get stuck are far shading, near shading, 3D scenes, and module layout. Because shadow settings have a large impact on energy production yet require understanding of shape creation and calculation conditions, trying to handle them perfectly from the start can easily lead to confusion.

First, it is important to grasp the idea that shadows can be broadly divided into those caused by distant terrain and mountain ranges, and those caused by nearby objects such as buildings, trees, mounting structures, and surrounding structures. In PVSyst, 3D scenes are sometimes used to configure near shading, and the official documentation explains that shading is a difficult area; in simulations, shadow calculations are performed at each time step and are applied differently to the direct, diffuse, and reflected components.

Beginners will find it easier to understand if, before creating a complex 3D scene from the outset, they break the process into stages such as a basic case without shadows, a case with distant shading, and a case with near-field shading. This allows you to check how shadow conditions affect annual energy production and monthly energy production. The official documentation also states that you can define and simulate a project without a 3D scene; in that case you define the field’s orientation on the orientation screen.

When working with 3D scenes, consistency with drawings and on-site information is essential. If the building height, position, distance to the array, ground elevation differences, or orientation alignment are off, the model may look plausible but the results will be inaccurate. Beginners in particular tend to focus too much on creating geometry in the 3D view and forget to check coordinates and dimensions. When reading the PVSyst manual, adopt a perspective that not only covers 3D creation operations but also verifies that the created model matches the actual site conditions.

Although 3D shadow animations and visualizations help with understanding, the official documentation explains that animations of 3D shading calculation are educational tools and not essential for running simulations. Therefore, beginners should be careful not to confuse checking the appearance with checking the calculation conditions. The fact that shadows appear to move visually does not make them correct; only after confirming that the input features, orientation, dimensions, and array arrangement are appropriate can the shadow conditions be used to explain the results.

Frequent Operation 7: Use Simulation and Variant Comparison

The seventh frequently performed operation is running simulations and comparing variants. What beginners should definitely learn from the PVSyst manual is how to create multiple cases and how to compare them. In practice, decisions are rarely made based on a single result; comparisons of multiple options are necessary, such as different orientations, different capacities, different PCS, different loss conditions, and with or without shading.

In PVSyst, the system definition is handled as a "variant"—in other words, a calculation version—and the approach is to define the components and loss parameters required for a PV system. Beginners who grasp the variant concept early will find it easier to organize their analyses than to manage their work by indiscriminately copying files.

Before running a simulation, it is necessary to make a habit of reviewing the input conditions. Check the location, meteorological data, azimuth, tilt, modules, PCS, losses, and shading conditions, and look for any unintended initial values or provisional settings that may remain. Beginners tend to make "pressing the calculate button" the objective, but in professional practice, pre-calculation checks determine the reliability of the results.

After simulation, check not only the annual energy yield but also monthly results, PR, the breakdown of losses, and generation curves. PVSyst simulations handle many variables; the result files store monthly values and detailed time-step values, and you can generate tables and graphs in the report and detailed results screens. Therefore, rather than simply choosing the option with the highest annual energy yield, it is important to verify in which seasons differences occur, which losses are large, and whether the design introduces any infeasibilities.

When comparing variants, the basic rule is to change one factor at a time. If you change multiple conditions simultaneously, the causes of any differences in results become unclear. For example, if you change the number of modules, PCS capacity, shading conditions, and loss conditions all at once, it becomes difficult to explain why energy production increased or decreased. Beginners should save the base case and make it a habit to create variants that change one condition at a time, as this makes it easier to apply the PVSyst manual in practical work.

Common Operation 8: Reading the Results Report and Loss Plot

The eighth frequently performed operation is reading the results report and the loss diagram. Even if you learn how to operate PVSyst from the manual, it is not sufficient in practice if you cannot explain the results. The purpose of a simulation is not to produce numbers, but to understand why those numbers occur and to be able to explain them to stakeholders.

First, what you should check are the annual energy production, specific yield, PR, and monthly energy production. Even if the annual values look good at first glance, if there is a drop in a particular month you need to check for the influence of shading, weather conditions, temperature, orientation, losses, and so on. PVSyst results include an energy loss diagram, normalized indicators by month or by day, PR, input-output diagrams, and distributions of incident energy and array output.

In particular, loss diagrams are something beginners should definitely be able to read. Loss diagrams are described as helping to quickly grasp the quality of a PV system design and to identify the main loss factors. Simulation reports also always include an annual loss diagram, which can be checked on a monthly basis.

When looking at a loss diagram, trace how the energy decreases from top to bottom. Start with the horizontal-plane irradiance, then the conversion to the tilted plane, shading and optical losses, array losses, PCS losses, and finally the output to the grid—check where and how much is lost at each step. Beginners tend to focus only on percentage values, but if you don’t understand which stage those percentages refer to, you can misinterpret the magnitude of the losses.

The results report forms the basis for internal and client explanations. PVSyst’s documentation states that for each simulation run you can print an engineering report containing all parameters used and the main results. However, simply attaching that report does not suffice as the full explanation. In practice, it is important to organize and communicate the assumptions, key input values, the variants compared, the rationale for the chosen solution, losses to be aware of, and any conditions that will need to be verified going forward.

Ways of Thinking About Operations That Beginners Often Struggle With

Many beginners who read the PVSyst manual struggle not so much because the operations themselves are difficult, but because they cannot see the overall workflow. When reading explanations screen by screen, attention inevitably shifts to individual items. In practice, site information is related to meteorological data, orientation and tilt are related to solar irradiance, module and PCS configuration are related to power output, and shading and losses are reflected in the results. Because everything is interconnected, understanding only one item is not sufficient.

The first hurdle is the sheer number of terms. PR, IAM, mismatch, subarray, variant, far shading, near shading, transposition, specific yield, etc.—many unfamiliar words appear. For beginners, rather than trying to fully understand unknown terms immediately, it’s better to first grasp how each term affects the results. For example, PR is an indicator that measures the overall performance of the power generation system, IAM is the optical loss due to the angle of incidence, and mismatch is the loss caused by variability; understanding them by their roles makes them easier to use in practice.

The second barrier is how to deal with initial values. PVSyst has many input fields, and some contain initial or standard values. For beginners, initial values are convenient, but using them without understanding the rationale will make explanations difficult. You do not need to change everything to project-specific values, but you must know which items you left as initial values and which you modified to match the project conditions.

The third hurdle is how to interpret the results. If you only look at annual generation, you may not notice configuration errors. You can assess validity only by checking the monthly results, the loss diagram, warnings, and the input conditions in the report together. In particular, errors in shading or azimuth settings can be difficult to detect from annual values alone. It is important to examine monthly generation trends and how losses appear to check for any irregularities.

The fourth challenge is case management. As you progress with reviews, similar variants will multiply. If names are vague, you won't know which is the latest proposal and which is for comparison. If beginners get into the habit of giving names that show the changes—baseline proposal, with-shadow proposal, loss-revision proposal, capacity-change proposal—later work becomes much easier.

Tips for Continuing to Use the PVSyst Manual in Practice

To continue using the PVSyst manual in practice, it is important to shift from treating it like a dictionary you only consult when you don’t understand something to using it as a tool to verify work procedures. For beginners, trying to read the manual from beginning to end is burdensome and can make it easy to lose sight of the purpose midway. First, it is effective to repeatedly read the necessary sections in line with the project’s workflow.

The recommended way to read it is to do so while imagining an actual project. Decide on a location, select meteorological data, set the azimuth and tilt, combine the modules and PCS, enter loss conditions, check shading, run the simulation, and read the results while consulting the manual in that order. Reading it in this sequence makes it easier to understand why each feature is necessary.

Also, it is useful to keep your own operation notes. Rather than copying the PVSyst manual verbatim, briefly summarize the settings you frequently use for your company’s projects, warnings that should be checked, and items that tend to require explanation internally. For example, organize the items to check when selecting meteorological data, rules for entering azimuth, your company’s standard loss conditions, how to create comparisons with and without shading, and items to verify before exporting reports — doing so will make future work faster.

For beginners to grow, gaining experience in investigating causes when results don't match is also important. If power generation is lower than expected, check in order whether the cause lies in the meteorological data, azimuth and tilt, PCS capacity, losses, shading, or module settings. Conversely, if power generation is too high, caution is also necessary: verify that losses haven't been omitted, that shading hasn't been forgotten, and that capacity and azimuth are as intended.

The PVSyst manual is not merely a document for learning how to operate the software; it is a clue to understanding the relationship between design conditions and results. Once you have learned the common operations, it is a good idea to gradually delve deeper into the necessary areas according to project-specific questions, such as detailed losses, 3D shading, module layout, reports, and economic evaluation.

Summary

The frequently performed operations that beginners should learn first in the PVSyst manual are: creating a project, checking site information and meteorological data, setting azimuth and tilt, combining modules and PCS, entering loss conditions, checking shading conditions, running simulations and comparing variants, and reading the result reports and loss diagrams. These operations may look separate, but in practice they are connected as a single workflow.

Beginners do not need to master all the detailed features from the outset. First create a basic case, then add conditions one by one and check how the results change. Comparisons using variants are especially important when applying PVSyst in practice. If you can organize and compare the basic scenario, shaded scenario, loss-revision scenario, and capacity-change scenario, you can take a step from being merely an operator to being someone who can explain the results.

Also, when reviewing results, don’t judge solely by the annual energy production; check the monthly results, PR, the loss diagram, and the input conditions in the report together. Once you can read the loss diagram, it becomes easier to explain where energy production is being reduced and where the design’s weaknesses lie. The purpose of using the PVSyst manual is not just to learn screen operations, but to understand the relationship between input conditions and results, thereby improving the accuracy of project assessments.

First, repeatedly review the eight common operations introduced in this article, following an actual project workflow. Create a project, select the meteorological data, set the azimuth and tilt, configure the system, check losses and shading, run the simulation, and interpret the results. Once you have this basic workflow mastered, the PVSyst manual will no longer be a difficult document but a practical guide for reliably carrying out power generation simulations.

Next Steps:
Explore LRTK Products & Workflows

LRTK helps professionals capture absolute coordinates, create georeferenced point clouds, and streamline surveying and construction workflows. Explore the products below, or contact us for a demo, pricing, or implementation support.

LRTK supercharges field accuracy and efficiency

The LRTK series delivers high-precision GNSS positioning for construction, civil engineering, and surveying, enabling significant reductions in work time and major gains in productivity. It makes it easy to handle everything from design surveys and point-cloud scanning to AR, 3D construction, as-built management, and infrastructure inspection.

Survey-Grade 3D Scanning with Absolute Coordinates

Stake Out Faster
with RTK Accuracy

Calculate Cut & Fill Volumes from Design vs Reality

Overlay DXF Plans in AR
with RTK-Stable Alignment

Learn More