Complete PVSyst Manual Guide | 9 Foolproof Usage Tips

Table of Contents

• Key things to grasp first in the PVSyst manual

• Usage 1: Read the manual after determining the purpose of the analysis

• How to Use 2: When creating a project, finalize the location and weather data first

• Usage 3: The system definition cross-checks capacity and string configuration

• Usage 4: Match orientation, tilt, and installation conditions to the drawings

• Usage 5: Check the shadow settings separately for distant shadows and nearby shadows

• Usage 6: Do not leave the loss settings at their default values; provide a rationale.

• How to use 7: Compare design proposals using variants

• How to use 8: Read the results not only by power output but also from the loss diagram

• How to Use 9: Check warnings and prerequisites before submitting the report

• Practical Summary for Mastering the PVSyst Manual

What to Grasp First in the PVSyst Manual

The purpose of reading the PVSyst manual is not simply to learn screen operations. It is important to be able to reproduce, under the same assumptions, everything from photovoltaic system energy yield forecasting and organizing loss factors to comparing design proposals and preparing reports for submission. PVsyst is positioned as PC software for the study, sizing, and data analysis of photovoltaic systems, and is configured to handle multiple types of PV systems such as grid-connected, stand-alone, pumping, and DC grids.

What makes the PVSyst manual easy to get lost in is not the sheer number of input fields themselves, but proceeding without understanding how much each input affects the results. For example, site, meteorological data, module, inverter, string, azimuth, tilt, shading, temperature, soiling, wiring, and downtime rate all influence the estimated energy production and how losses are seen. If you simply follow the screens in order you may think “it’s correct because I entered it,” but in practice you need to be able to explain the rationale and consistency of the input values.

Therefore, rather than reading the PVSyst manual from start to finish, it is more effective to read it following the practical workflow. First create the project, then select the location and meteorological data, define the system configuration, set shading and losses as required, and finally review the simulation results and report — understanding it in this order makes it easier to avoid confusion. The official documentation likewise shows that, when creating a project, you should define the filename and project name, the site, the meteorological file in PVSyst format, and the project settings.

Also, PVSyst is not a tool that automatically provides the correct design; it is a tool that calculates results based on the assumptions given by the designer. Therefore, when reading the manual, it is important to be aware not only of "what happens when you press this button," but also of "where this input value came from," "whether you can explain it when comparing with other design proposals," and "whether you can explain the numbers shown in the report to a third party."

How to use 1: Read the manual after deciding the analysis objective

Before you start using the PVSyst manual, it is important to first clarify the purpose of your analysis. Whether it is a preliminary assessment for residential or industrial use, a detailed design for ground-mounted systems, an evaluation of demand response for self-consumption, or an analysis that includes batteries and grid constraints will change which sections you should read and the level of detail required for inputs. If you begin work with an unclear objective, you may spend time on unnecessarily detailed settings or, conversely, easily overlook important loss conditions.

At the initial stage, consider separately whether the objective is to obtain a rough estimate of energy yield or to produce a high-accuracy report for investment decisions or design comparisons. PVsyst offers both an approach for quickly evaluating under limited conditions, as in preliminary design, and an approach that treats in detail thermal behavior, wiring, module quality, mismatch, incidence-angle losses, horizon shading, and partial shading from nearby objects.

A common pitfall in practice is getting into detailed settings from the outset, only to have the underlying assumptions change later. For example, if you overdevelop detailed shading analysis and string configurations at a stage when the installed capacity has not yet been finalized, you'll need to reconfigure them every time the layout changes. Conversely, if you review loss assumptions or shading conditions just before submission, the power generation estimates can change significantly, and revising the explanatory materials will take time.

When reading the manual, it is recommended to first review the overall workflow and then dive deeper into the items required for your project. For example, for an initial assessment prioritize checking the site, meteorological data, system capacity, orientation and tilt, and main losses. For detailed design, check nearby shading, strings, module layout, temperature conditions, downtime rate, and report output. By deciding the scope to read according to your purpose in this way, you can use the PVSyst manual efficiently.

Usage 2: When creating a project, finalize the location and meteorological data first

When running a generation simulation in PVSyst, the project's location information and meteorological data are the first things that matter. Because solar power output is heavily influenced by irradiance, temperature, solar altitude, azimuth, and weather conditions, if these are left unclear then no matter how detailed the equipment parameters entered later are, the reliability of the results will decline. When reading the PVSyst manual, you should not think of the project creation screen as merely a place to set a save name; treat it as the step that builds the foundation for the analysis.

In the project definition, you define not only the project name and file name but also, in sequence, the site, the weather file, and the project settings. The official documentation likewise shows the project-creation flow as site definition, selection of a PVsyst-format weather file, and project settings. In other words, the site location and meteorological data are not things to be chosen casually afterward; they are prerequisite conditions that should be determined up front with a clear rationale.

One thing to be careful about when selecting a site is not to be reassured solely by the proximity of the address or latitude/longitude. In mountainous areas, coastal areas, snow-prone regions, high-temperature regions, and on urban rooftops, neighboring locations can exhibit different trends in solar radiation and temperature. The results also change depending on whether you use measured data, satellite-derived or existing databases, or representative-year data. If you document the reasons for selecting the meteorological data, it will be easier to later justify the validity of the estimated power generation.

Wind speed and air temperature also affect the evaluation of temperature-related losses. PVsyst’s simulation variables include meteorological data such as global horizontal irradiance, diffuse horizontal irradiance, direct horizontal irradiance, ambient air temperature, and wind speed, and it also explains how to handle cases where wind speed is not present in the file. Understanding these items allows you to identify, in a more concrete way, the factors that reduce power generation rather than simply looking at annual solar radiation.

Usage 3: Cross-check system definitions against capacity and string configuration

Many beginners stumble over the system definition screen in the PVSyst manual. Inputs such as modules, inverters, number of units, number of strings, number of modules in series, and subarrays are required, and if you’re not familiar with it you can end up focusing only on creating a combination that doesn’t produce errors. However, in practice, having no errors and matching the design drawings and equipment specifications are not the same. The system definition is a very important step that determines the electrical assumptions for the power generation facility.

PVsyst variants and system definitions are used to define the PV system components necessary to meet the user's objectives. The number of modules, capacity, inverter(s), and string configuration entered here form the basis of the simulation results. Therefore, it is necessary not only to select equipment but also to cross-check them against drawings, single-line diagrams, equipment specification sheets, and string tables.

Particular attention should be paid to the relationship between DC capacity and AC capacity, the number of strings per inverter input, the number of modules in series, the voltage range, and the approach to oversizing. Even if the configuration is valid in PVSyst, if it deviates from the actual design or construction conditions, the simulation results will not reflect reality. For example, if the drawings show that only some surfaces have fewer modules but PVSyst treats them as uniform strings, the effects of shading and mismatch may be underestimated.

In system definition, it is practical to first set the overall capacity, then match the number of modules, the number of inverters, and the number of strings, and finally verify electrical consistency. If a warning appears along the way, do not change numbers without reading the warning; check why the warning was issued. The PVSyst manual is effective as an aid to understanding the meaning of such warnings and reviewing design conditions.

Usage 4: Match orientation, tilt, and installation conditions to the drawings

In PVSyst's energy yield calculations, the module azimuth and tilt are important input parameters. In photovoltaic power generation, the amount of solar radiation received can vary with installation angle and orientation even for systems with the same capacity. When reading the PVSyst manual, you should not treat azimuth and tilt as mere input fields, but as items that need to be matched to the design drawings and the on-site conditions.

For ground-mounted systems, the rack tilt angle, row spacing, orientation, and terrain slope are relevant. For roof-mounted systems, the orientation, pitch, level differences, and surrounding obstructions of each roof surface have an impact. For projects divided across multiple surfaces, it is necessary to decide whether to treat everything using a single representative orientation and tilt or to separate them by surface. Summarizing with representative values speeds up the work, but makes it harder to see per-surface generation characteristics and shading effects.

Also, in PVsyst's 3D scene it is necessary to understand the conventions for the coordinate system and azimuth. The official manual explains that, in the Northern Hemisphere, the X direction is west, the Y direction is south, and Z is upward, and that the azimuth of a PV field is defined with south as the reference and positive toward the west. If you create a 3D model without confirming these coordinate and azimuth conventions, it may look correct on drawings but be misaligned in the simulation.

When verifying installation conditions, it is also important to document the basis for the input values. For example, the reliability of the azimuth varies depending on whether it was obtained from the site layout, from an on-site survey, or estimated from aerial photographs or drawings. For tilt, you need to distinguish whether it is a design value or a measured value, and whether it refers to the roof slope or the racking angle. The PVSyst manual should be read not to simply fill in input fields, but to properly reflect these differences in assumptions.

Usage 5: Check shadow settings separately for distant shadows and near-field shadows

One of the factors in PVSyst that has a major impact on energy production is the shading settings. Shading can be distant, caused by far-off obstacles such as mountains and terrain, or near, caused by nearby objects such as buildings, trees, rows of mounting structures, equipment, and parapets. When reading the PVSyst manual, it is important not to confuse these two. Distant shading looks at effects during periods when the sun is near the horizon, while near shading is also related to partial shading during the day and to electrical losses.

The official documentation explains that near shading occurs when nearby objects cast visible shadows on the PV field, and that dealing with near shading is more complex than with far shading, requiring a detailed 3D description of the entire PV system and its surrounding environment. In other words, to handle near shading correctly, you need not only to input the presence or absence of obstacles, but also to make the shape, position, height, and distance to the modules as realistic as possible.

In PVSyst's near shading settings, you create a 3D scene and place PV tables and objects that cast shadows. The official tutorial likewise shows the workflow of opening Construction/Perspective from Near Shadings to build the 3D scene. In this process, you should cross-check the distances and heights between the module surface and obstacles against the drawings, taking care not to underestimate inter-row shading or shading from surrounding objects.

In shadow calculations, there is an approach that considers not only linear shading but also effects at the module and string levels. The official manual explains that linear shading is a method that considers only irradiance loss on the PV field, and that By Module String groups modules into strings in a 3D scene and estimates each string’s shading coefficient and electrical losses individually. In practice, it is important to distinguish between projects where shading impacts are minor and projects where partial shading significantly affects energy generation and string behavior.

Usage 6: Don't leave loss settings at their initial values—give them a rationale

Understanding loss settings is indispensable when using the PVSyst manual in practice. PVsyst handles many loss factors such as incidence angle losses, soiling, temperature, wiring, module quality, mismatch, downtime rate, shading, and others. The official documentation also explains that in the System Definition panel, under Detailed losses, you can change soiling, IAM, module temperature parameters, wiring resistance, module quality, mismatch, downtime rate, and so on.

A common mistake beginners make is using the loss settings at their default values and adopting only the generated output shown in the report. Default values are useful as a starting point for analysis, but they do not necessarily reflect project-specific conditions. For example, in areas with heavy dust, snowy regions, coastal sites, factory roofs, around farmland, or equipment with low maintenance frequency, the assumptions about soiling and downtime rates may need to be adjusted.

Temperature losses are another item that is easily overlooked. The nominal performance of PV modules is specified under certain conditions, but in actual operation module temperatures rise and lead to output reduction. In PVsyst’s official explanation of thermal losses, it is shown that output losses occur when a PV array operates above 25℃ and that the module temperature coefficient is involved. Because thermal conditions change depending on whether the installation is roof-mounted, ground-mounted, or has back ventilation, verification according to the installation type is necessary.

Also, IAM losses are related to transmittance losses that occur when sunlight strikes the module surface at an oblique angle. In PVsyst, IAM is treated as a function of the incidence angle, and it is described as being applied to the direct, diffuse, and albedo components. Understanding these losses one by one makes it easier to explain why energy output has decreased and where differences between design proposals originate.

Loss settings require more supporting input the more strictly you try to define them. It isn’t necessarily correct to set every detail; what matters is having sufficient justification relative to the project’s objectives. For internal review you may compare using general values, but when submitting to clients or using them for investment decisions, it is reassuring to leave notes on the assumptions for each loss so they can be checked later.

How to Use 7: Compare design proposals using variants

When reading the PVSyst manual, understanding the concept of variants makes design comparisons much easier. A variant is like a calculation scenario within the same project where conditions are changed. For example, it makes it easy to compare changes such as the module type, inverter configuration, tilt angle, row spacing, shading conditions, or loss conditions under the same site and weather conditions.

The official documentation explains that the simulation results for a specific variant are saved as a .VCi file corresponding to the project file name, together with the relevant parameters. It is also recommended that, after a simulation, you save each variant, use "Save as" to avoid overwriting when comparing, and give them easily identifiable names.

In practice, if you give variant names carelessly, you cannot tell later which conditions the calculation used. For example, names like "Option 1", "Revised", "Final", and "Final 2" cause confusion when comparing later. It is helpful for variant names to include information that clarifies the comparison axes, such as capacity, tilt, equipment option, shading conditions, and loss conditions. For example, names like "South-facing 10°_Low-loss conditions", "East-West layout_Shaded", and "PCS capacity change option" make it easier to organize when preparing reports.

In design comparisons, we check not only annual energy production but also monthly generation trends, the breakdown of losses, constraints at peak times, and seasonal differences in shading. A proposal with high annual energy production is not necessarily optimal when considering constructability, cost, maintainability, grid constraints, roof load, and future expandability. PVSyst variants should be used not simply to find the option with the largest energy output but as a mechanism to explain the differences among multiple proposals.

Tip 8: Interpret results not only by power output but also using the loss diagram

The most prominent figure on PVSyst’s results screen is the annual energy production, but it is dangerous to judge based on that alone. If the production is lower than expected, you cannot consider corrective measures unless you determine whether the cause is irradiance conditions, shading, temperature, wiring, or inverter constraints. When using the PVSyst manual, it is important not only to view the results as a number for energy production but to read them as the flow of losses.

The results from PVsyst are compiled into a report that includes all parameters used in the simulation and descriptions of the main results. In addition, many results are saved as monthly values that can be viewed and printed. In other words, PVsyst's results are not merely final figures but can be used as information to verify the input conditions, calculation processes, and loss factors.

Particularly important is the loss diagram. The official documentation describes the loss diagram as a tool to quickly assess the quality of a PV system design and to identify the primary sources of loss. By examining the loss diagram, you can understand where major losses occur in the process from solar irradiance to effective incident energy, to array output, to inverter output, and finally to energy on the grid side.

In result verification, we first look at the annual energy production and the specific yield. Next, we examine the monthly energy production to check for any unnatural drops in summer or winter. After that, in the loss diagram we check the magnitudes of shading, temperature, soiling, IAM, wiring, mismatch, inverter losses, and so on. If a particular loss appears excessively large, we go back and check the settings and input conditions.

Also, when comparing multiple variants, it is important not only to show the differences in generated energy but also to explain why those differences arose. For example, determine whether Option A’s higher generation is due to its tilt angle, reduced shading, or more lenient loss settings. PVSyst results are supporting material for design decisions, and simply adopting the output numbers as-is is insufficient.

Usage 9: Confirm Warnings and Prerequisites Before Submitting the Report

The final stage of putting the PVSyst manual into practical use is the pre-submission check. Once the simulation is complete and the report can be generated, it can feel like the work is done. However, there are many items to verify before submission. Reviewing the project name, site, meteorological data, system capacity, modules, inverters, azimuth, tilt, shading, losses, variant names, calculation settings, and warning messages can prevent rework after submission.

The official documentation explains that, before a simulation, the program checks the consistency of parameters, and that orange warnings indicate the simulation is possible while red warnings indicate issues that will prevent the simulation. In other words, the disappearance of red errors does not mean everything is perfect; you must also understand the content of orange warnings and verify that their reasons are acceptable.

Before submitting the report, first check the consistency of the input conditions. Verify that the site and meteorological data correspond to the project location, that the system capacity matches the drawings and estimation conditions, that the number of modules and the number of PCS units are correct, and that there are no contradictions in the string configuration. Next, check the shading and loss settings. If shading is left unset, determine whether it is truly acceptable to ignore shading effects for the project. If loss values have been changed, ensure you can explain the justification.

Also, check the units and meanings of the figures shown in the report. Annual energy generation, specific yield, Performance Ratio, loss rate, and so on may draw different attention depending on the recipient. Design engineers may want to see the breakdown of losses, while project owners/operators may want to know the annual generation and its impact on profitability. Tailoring which figures you will explain to the report recipient will help meetings go smoothly.

PVSyst reports are powerful, but the report itself does not constitute the entire basis for the design. It is advisable to document separately—as notes or design documentation—which assumptions were used for the calculations, which conditions were compared, and how each loss was treated. The PVSyst manual can also be used as a checklist to prevent omissions in these verification tasks.

Summary: Mastering the PVSyst Manual for Practical Use

To master the PVSyst manual, it is not enough to merely memorize the sequence of screen operations. First determine the analysis objectives, finalize the site and meteorological data, reconcile the capacity and string configuration in the system definition, match the azimuth, tilt, and installation conditions with the drawings, set shading and losses according to the project, compare variants, interpret the results using the loss diagram, and finally confirm the assumptions of the report. By keeping this sequence in mind, you can use PVSyst not just as an energy-yield calculation program but as a practical tool to support design decision-making.

Particularly important is preserving the rationale for the input values. Because PVSyst allows you to configure many parameters, you will be able to run simulations faster as you gain experience. However, being able to calculate quickly is different from being able to explain your calculations. Being able to explain which meteorological data you used, why you chose those loss values, why you adopted those shading conditions, and which variant you selected as the final proposal is what leads to reliability in professional practice.

Also, the results from PVSyst are not absolute predictions but simulation results based on the assumptions entered. Whether the generated energy is higher or lower than expected, you should first check the loss diagram and the monthly results to interpret which factors are affecting the outcome. The official documentation also systematically organizes items such as loss factors, result verification, report output, and variant management, so consulting the manual in line with your operational workflow will deepen your understanding.

The basics to avoid failure with the PVSyst manual are to first grasp the overall picture, then delve into the important items for each project, and finally cross-check the results against the assumptions. If you are using it for the first time, don’t try to understand all the functions at once; it’s better to become familiar with it in the order of project creation, meteorological data, system definition, losses, shading, and result verification. When using it in practice, judging not only by the calculation results but also by whether you can explain those results to a third party will greatly improve the accuracy of your use of PVSyst.