Three common reasons beginners stumble when using PVSyst and how to address them

Table of Contents

• Reasons why beginners commonly struggle with using PVSyst

• Cause 1: Starting data entry without understanding the overall workflow/order of tasks

• Solution 1: First organize the workflow from project information through to simulation results

• Cause 2: Setting meteorological data and design conditions without a clear understanding of their meanings

• Solution 2: Confirm the basis for input values by separating site conditions and design conditions

• Cause 3: Deprioritizing shadows, terrain, and surrounding conditions and only looking at the results

• Solution 3: Reflect the on-site conditions first, then verify the validity of the results

• Verification procedure to master PVSyst for practical use

• Prepare site data to avoid confusion when using PVSyst

• Summary

Reasons Beginners Often Struggle with Using PVSyst

People who stumble at the beginning of using PVSyst are often not confused because the interface itself is difficult, but because they start entering data without having organized the relationships among the pieces of information needed for designing a photovoltaic system. PVSyst is not simply a tool for calculating energy yield; it is design-support software for handling site conditions, meteorological data, azimuth, tilt angle, system configuration, loss conditions, shading effects, and simulation results as a continuous workflow. Therefore, rather than entering a single number to get an answer, you build up multiple conditions and ultimately check the annual energy production and the breakdown of losses.

When practitioners search for "how to use PVSyst," the motivation is not simply to learn where the buttons are but a need to quickly understand how to initiate a project, in what order to configure settings, and how to read the results. Especially when using it for the first time, so many items appear on the screen that it can be difficult to tell which are mandatory, which are advanced settings, and which can be adjusted later. As a result, they hesitate during the initial input phase, encounter errors or warnings along the way, and ultimately lose confidence in the simulation results.

There are three main reasons people get stuck with PVSyst. The first is starting to enter data without understanding the workflow from project creation through result verification. The second is proceeding with an unclear understanding of the meaning of input values such as meteorological data, installed capacity, azimuth, tilt angle, and loss conditions. The third is postponing site conditions—such as shading, terrain, nearby obstacles, and on-site elevation differences—and looking only at the simulation results first.

This article organizes, from a practical perspective, the three causes that beginners most commonly stumble over when using PVSyst and the countermeasures for each. While aimed at beginners, it also explains the ways of thinking that become important when working on real projects. The goal is not to rote-memorize the detailed button operations of the initial setup, but to understand why each item is entered, which conditions affect the results, and in what order you should check things to reduce rework.

Cause 1: Starting to input without understanding the overall order of operations

A major reason people initially stumble when learning to use PVSyst is that, without understanding the overall sequence of tasks, they start entering data in the order items appear in front of them. In PVSyst you set the project's site information, meteorological data, system orientation, PV modules, PCS, wiring configuration, loss conditions, shading conditions, and so on. These may look like independent input items, but in reality they are interrelated. For example, if the site information or meteorological data changes, the assumptions about solar irradiance change; if the azimuth or tilt angle changes, the received solar irradiance changes; and if the system configuration changes, the electrical losses and output limitations change.

A point where beginners often get confused is that you can start entering data from any screen and somehow continue. Because PVSyst is highly feature-rich, you can enter detailed settings right from the start. However, if you get too deep into the details before the design assumptions are settled, you will need to review the settings each time you later change the site, capacity, layout, or equipment configuration. As a result, it becomes unclear which values are reflected in the final plan, and comparing multiple design options becomes confusing.

In practice, there are multiple situations where PVSyst results are used, such as initial studies, conceptual design, detailed design, proposal preparation, internal review, and client presentations. In initial studies you may only want to grasp a rough annual energy yield, but in detailed design you need to refine loss conditions and shading conditions in more detail. If you try to input everything perfectly from the start without being aware of these differences in purpose, the amount of work increases and the task is more likely to stall.

Also, in PVSyst you may create multiple studies for a single project with different conditions. When comparing scenarios that change the tilt angle, change the orientation, change the capacity, or change how shading is taken into account, if you don't first organize your approach to structuring the project you will lose track of what each scenario is comparing. If you name files or study titles based on a spur-of-the-moment impression, you may not be able to make a judgment when you review them later.

When learning how to use PVSyst, you don't need to memorize every feature from the start. Rather, what you should learn first is the skeleton of the process: in what order to set conditions, at which stages to check the results, and which condition changes will affect those results. Without understanding this framework, you may be able to operate the software, but it will be difficult to consistently produce results that are usable in real-world work.

Solution 1: First organize the flow from project information to simulation results

To avoid getting stuck with PVSyst at the outset, it is useful to organize on paper or in notes the flow from project information through to simulation results before entering the input screens. The first thing to confirm is the purpose of this simulation. The level of detail in the inputs will vary depending on whether you want a rough estimate of energy production, to compare design proposals, to evaluate the impact of shading, or to verify the appropriateness of system capacity and equipment configuration.

The basic flow is: first decide the project location, then set the meteorological conditions, then determine the module surface orientation and tilt, enter the system configuration, adjust loss conditions, add shading and terrain conditions as needed, and finally run the simulation and review the results. Understanding this sequence makes it easier to know which item you are looking at on the screen. Rather than jumping straight into detailed loss or shading settings, it is important to first create the overall framework of the system and then refine it to more closely match reality.

In practice, rather than trying to produce a perfect model on the first try, it is better to proceed by incrementally improving accuracy. Initially, run a simple simulation using only location, weather, azimuth, tilt, and rough capacity to get a sense of the magnitude of the results. From there, refine the equipment configuration, revisit loss assumptions, add shading and surrounding conditions, and progressively move the model toward the final assessment. By staging the process in this way, it becomes easier to understand how much each change in settings affected the results.

How you name project titles and study names should not be overlooked when using PVSyst. If you give names that indicate the content of the study—such as initial proposal, capacity change proposal, tilt angle change proposal, shading consideration proposal, and final confirmation proposal—it will be easier to compare them later. When multiple people are working together, recording the creation date, person in charge, and the changes made will reduce rework during internal reviews and revisions. Not only the operation of PVSyst itself, but also the habit of managing design information directly affects the reliability of the results.

Also, when reviewing the results, it is important not to stop at checking only the annual energy production. In PVSyst you can review the input conditions, major losses, monthly generation trends, performance indicators, and so on. As a beginner you tend to focus only on the final energy output, but in practice it is essential to be able to explain why that amount of energy was produced. By checking the breakdown of losses and month-to-month variations, you can judge whether the design conditions are reasonable, whether there are input errors, or whether expectations are unrealistically high given the site conditions.

Before using PVSyst, organizing the project's purpose, the conditions to be entered, the results to be checked, and the options to be compared will greatly reduce the time you spend getting lost in the interface. The first step to learning how to use it is not memorizing where the buttons are, but being able to view the screens in line with the design-study workflow.

Cause 2: Defining meteorological data and design conditions ambiguously

The second cause is setting meteorological data and design conditions ambiguously. In PVSyst, many input values affect the simulation results, such as solar irradiance, ambient temperature, azimuth, tilt angle, system capacity, equipment configuration, wiring conditions, and loss conditions. These values are not merely numbers to fill in; they are important conditions that determine the assumptions for energy output.

Beginners are often especially confused about which values to extract from the design drawings, which values to verify from on-site conditions, and which values can be assumed as standard. For example, the azimuth and tilt angle of photovoltaic modules are related to the layout plan and racking conditions. System capacity is related to the available installation area, equipment specifications, PCS capacity, and grid connection conditions. Loss conditions are related to temperature, wiring, soiling, mismatch, conversion efficiency, and outage risk. Because all of these relate to real equipment and operation, entering them arbitrarily reduces the reliability of the results.

Meteorological data is also important. Even with the same system capacity, power output will change if irradiation and temperature conditions differ by location. Even when substituting data from a nearby area, actual generation trends may differ at coastal sites, mountainous areas, snowy regions, fog-prone locations, or places surrounded by high terrain. What matters when using PVSyst is not only the operation of selecting meteorological data, but also being aware of how well that data represents the conditions at the project site.

Also, when entering design conditions, mix-ups of units or misinterpretations of angles can occur. Slope angles, azimuths, capacities, areas, distances, heights, and similar items may have different meanings depending on the input field. Instead of entering values just by glancing at the on-screen field labels, make it a habit to confirm what each value actually represents. In particular, with orientation settings, misunderstanding the reference direction or the sign convention can greatly change the simulation results.

There are aspects of equipment configuration where people can easily stumble. The combination of solar PV modules and the PCS, string configuration, the DC-to-AC capacity ratio, the number of inputs, and the voltage range directly affect PVSyst results. Beginners tend to assume that selecting equipment with matching capacities is sufficient, but in reality it is necessary to verify the validity of the electrical combinations, the design margins, and any limiting conditions. When warnings appear, it is important not to aim simply to clear them, but to understand why the warnings are being issued.

The same applies to loss conditions. You can proceed with the default values, but for practical projects you need to be able to justify the input values. If you estimate losses to be small, the predicted energy yield will be higher, but it may produce results that are far from reality. Conversely, if you are overly conservative in your estimates, the system's assessment may be unduly low. To become proficient in using PVSyst, it is essential to understand what each loss item means and under which site conditions it will increase.

Countermeasure 2: Verify the basis for input values by separating site conditions and design conditions

To avoid getting stuck on meteorological data or design conditions, it is effective to organize input values by dividing them into site conditions and design conditions. Site conditions are those originating from the site, such as location, surrounding topography, obstacles, solar radiation environment, temperature trends, the possibility of snow accumulation or soiling, and variations in elevation of the installation surface. Design conditions are those determined by the design, such as system capacity, module layout, azimuth, tilt angle, PCS configuration, wiring plan, and loss settings. Not confusing these two is important when using PVSyst in practice.

Site conditions cannot always be fully determined from desk-based materials alone. Even locations that appear flat on maps may in reality have elevation differences or be surrounded by trees, buildings, slopes, equipment, fences, and other features. In mountainous areas and on developed land, the surrounding topography can also affect the site during times when the sun’s altitude is low. PVSyst’s meteorological data and shading settings serve as an entry point for reflecting these on-site conditions. Therefore, before entering data you should check site photos, survey results, layout plans, development plans, and surrounding conditions, and decide which conditions to reflect in the model.

Design conditions are confirmed from internal design documents and planning drawings. Capacity, layout, tilt angle, orientation, racking conditions, electrical configuration, number of PCS units, and so on may change as the design progresses. It is acceptable to proceed with assumed values in the initial stages, but in that case it is necessary to clearly state that they are assumptions. Running simulations with a mix of assumed and confirmed values makes it difficult to explain the results. Recording which values are confirmed and which are planned to be reviewed later makes it easier to accommodate design changes.

When organizing the basis for input values, it is important not only to record the numbers but also to document the reasons those numbers were adopted. For example, separating the bases—azimuth based on the layout drawing, tilt angle based on the racking plan, loss conditions based on internal standards, and shading conditions based on on-site inspection—makes later review and explanation easier. When you are not yet familiar with operating PVSyst, you tend to focus on entering values, but in practice managing the basis for input values is just as important.

Also, rather than trying to input every detail accurately from the start, it is more efficient to check conditions in order of importance. Factors that have the greatest impact on power generation are the site's solar radiation conditions, azimuth, tilt angle, system capacity, shading effects, and the primary loss conditions. If these assumptions are significantly off, even fine adjustments will not make the overall results reliable. In practice, it is practical to first establish the major conditions and then, as needed, review detailed losses and corrections.

To master using PVSyst, it is helpful to cultivate the practice of creating a worksheet that organizes input values alongside the interface. If you can identify which values are obtained from where, at what stage they are finalized, and which values strongly affect the results, your understanding of the simulation outcomes will deepen. PVSyst is a tool that yields valid results only when supplied with correct assumptions. Not leaving the rationale for input values ambiguous is the most practical measure to prevent early stumbling.

Cause 3: Putting shadows, terrain, and surrounding conditions aside and only looking at the results

The third cause is prioritizing the simulation results while postponing consideration of shading, terrain, and surrounding conditions. When using PVSyst for the first time, you may proceed with the settings, run the simulation, and, when the annual energy output number appears, feel as if the work is complete. However, what matters in practice is how well that result reflects the actual conditions on site. In particular, if the effects of nearby shading or terrain are not taken into account, the desk-based results may differ from the actual generation trends.

In solar power systems, shading has a major impact on energy production. Surrounding buildings, trees, utility poles, fences, slopes, mountains, and existing equipment can cast shadows during specific times of day or seasons. Shadows do not merely slightly reduce generation; when part of a module is shaded, electrical losses can become much larger. Therefore, when evaluating energy production in PVSyst, it is important to consider to what extent shading is taken into account.

Topographic conditions are another aspect that is easy to overlook. While flat terrain can be modeled relatively simply, on sloping ground, reclaimed land, mountainous areas, or undulating terrain, module layout, orientation, tilt, row spacing, and shading patterns become more complex. Even if they appear neatly arranged on drawings, in reality ground elevations can differ, which can change sight lines between front and back rows and how shadows fall. To increase the reliability of results when using PVSyst, it is necessary to understand these on-site elevation differences and surrounding conditions as early as possible.

What trips up beginners is that they regard shadow and terrain settings as difficult advanced features and put them off. It’s true that creating detailed three-dimensional models and evaluating shadows requires practice. However, you don’t need to create a perfect model from the start. What matters is judging early on whether shadows and terrain are likely to affect the results significantly or only minimally. If the surroundings are open, flat land, simplifications may be possible, but if there are nearby obstructions or the terrain is complex, you may not be able to ignore the effects of shadows.

Also, when reviewing simulation results, it is important to look not only at the annual totals but also at the breakdown of monthly generation and losses. If generation drops significantly in winter, it may not be just due to reduced solar irradiance but could be related to shading effects from the low solar altitude. In locations where shading in the morning and evening is strong, losses that are hard to detect from the annual totals can occur. When examining the results, you should not simply accept the numbers at face value but compare them with site conditions to check for any inconsistencies.

PVSyst performs calculations based on the conditions entered. In other words, if you do not enter the shadows and terrain conditions present on-site, their effects will not be adequately reflected. When you are still unfamiliar with the operation, you tend to be content simply with having run a simulation, but in practice it is essential to verify whether the results are close to reality.

Countermeasure 3: Incorporate on-site conditions and then confirm the validity of the results

To avoid being caught out by shadows, terrain, or surrounding conditions, it is important to verify how well the simulation reflects the actual site conditions before reviewing the simulation results. The first step is to identify elements on site that could affect power generation. Check whether there are tall buildings nearby, trees, mountains or slopes, undulations in the installation surface, obstacles that will not be removed in the future, or whether heights will change after land development.

When reflecting site conditions, it is not necessary to model everything in detail. In practice, it is important to prioritize incorporating the elements that have the greatest impact. Elements that cast long shadows during periods of low solar altitude are more important than low obstacles whose effects are limited. Obstacles located very close to the equipment are more likely to cause partial shading than obstacles farther away. For surrounding topography, checking what elevation differences exist to the south and in the east–west directions of the power generation equipment makes it easier to assess the magnitude of the impact.

When handling shading and terrain in PVSyst, the accuracy of information obtained on site is also important. Heights and distances can be difficult to determine from photographs alone. Drawings alone may not reflect on-site trees, temporary structures, or existing structures. It is necessary to combine on-site surveys, surveying data, layout plans, and land development plans to organize the conditions that should be reflected in the simulation. Especially in mountainous or sloping areas, it is important to verify that the layout on the design drawings is not offset from the actual terrain conditions.

When validating results, it is important not to judge solely by whether the power generation is high or low. First, check whether the magnitude of generation is reasonable given the installed capacity that was entered. Next, examine whether the monthly generation trends are not substantially inconsistent with the region’s seasonal variations. Also review the breakdown of losses to ensure that losses from shading, temperature, wiring, conversion, and other sources are not excessively large or small. By checking these items you can more easily detect input errors or omitted settings.

When comparing multiple scenarios, it is also important to keep everything as consistent as possible except for the conditions you changed. For example, if you want to compare only the tilt angle, having different meteorological data, system capacity, loss assumptions, or shading conditions for each scenario makes it hard to determine which factor affected the results. When performing comparative analyses in PVSyst, you must clearly identify the changes and be able to explain what caused the differences in the results.

The process of reflecting site conditions cannot be completed solely within PVSyst. It is necessary to obtain accurate site information, organize it as design conditions, and reflect it in the model to the required extent. In particular, if the site's topography and the positions of obstacles remain unclear, the shading settings in the simulation will also be ambiguous. To elevate PVSyst use to a practical level, it is important not only to know how to operate the software but also how to collect site information and convert it into input conditions.

Verification Procedures for Mastering PVSyst in Professional Practice

To use PVSyst effectively in practice, it is useful to standardize the verification procedures for each project. If inputs are entered on an ad hoc basis each time, the level of detail in the settings will vary depending on the person responsible, causing inconsistency in the quality of results. Having a common verification procedure within the company makes it easier for even beginners to reduce omissions in their work.

The first thing to confirm is the project's objective. Clarify whether you want to know a rough estimate of power generation, compare design proposals, produce figures for proposal materials, or carry out a detailed loss evaluation. If you begin work with the objective unclear, you will not be able to judge how detailed the settings should be. For an initial study, focus on the major conditions; for a detailed study, go into shading, losses, equipment configuration, and site conditions—adjust the depth of input according to the objective.

Next, verify the site and meteorological conditions. Check whether the project site is set correctly and whether the meteorological data used are appropriate for the local conditions. If using data from nearby locations, confirm that the terrain, elevation, and climate conditions are not significantly different. Meteorological conditions form the basis for power generation, so if this remains unclear, the reliability of subsequent detailed settings will not improve.

Next, check the azimuth and tilt angles of the module surfaces. Azimuth and tilt directly affect how solar radiation is received. Confirm that the input values match the layout plan and verify that, when there are multiple orientations, they are correctly separated and handled. The points to note vary depending on installation conditions such as rooftop, ground-mounted, or sloped terrain. When there are multiple surfaces or different tilts, determine whether simplification is acceptable or whether they should be evaluated separately.

Next, check the equipment configuration. Verify that the solar cell modules, PCS, string configuration, capacity ratio, voltage range, and so on match the design conditions. If warnings appear, review their content and understand the cause. In practice, rather than aiming only to clear warnings, you must confirm that they do not contradict design constraints or a safety-first approach.

Next, check the loss conditions. Verify whether losses such as temperature, wiring, contamination, mismatch, conversion, and shutdown are not overestimated or underestimated relative to the project's conditions. Even when using initial values, it is desirable to be able to explain why leaving them as-is is acceptable. When referring to past projects or internal standards, confirm whether they can be applied under the same conditions.

Finally, check shadows, terrain, and surrounding conditions. If there are shading factors on site, record the extent to which they were reflected in the model. If they were not reflected, document the reasons you judged the impact to be small, as this will make later explanations easier. When reviewing simulation results, comprehensively examine annual energy production, monthly energy production, the breakdown of losses, and performance indicators to determine whether there are any inconsistencies with the input conditions.

In this way, learning how to use PVSyst is not sufficient if you only memorize the sequence of screen operations. By handling the project objectives, location conditions, design conditions, system configuration, loss conditions, on-site conditions, and result verification as a single workflow, it becomes easier to produce simulation results that are usable in practice.

Organize Site Data to Avoid Confusion When Using PVSyst

To avoid confusion when using PVSyst, it is important to organize site data before inputting it into the software. Many issues may appear to arise solely within PVSyst’s interface, but they actually result from insufficient information being entered. If the site location is vague, the azimuth is unclear, the tilt angle is uncertain, the terrain is ambiguous, and the positions of obstacles are imprecise, no matter how carefully you operate the software the reliability of the results will not improve.

In simulations of solar power generation systems, site location and elevation information are important. Details such as the extent of the installation area, what obstacles are present nearby, the degree of ground elevation variation, and whether elevations will change after land development affect power output assessment and shading analysis. In particular, for ground-mounted systems it is essential to understand the site's size and shape, slope, and the influence of surrounding features.

If site data are well organized, it becomes easier to determine which conditions to input into PVSyst. For example, if the surroundings are open and the site is flat, you may be able to simplify the shading settings. On the other hand, if mountains, slopes, trees, or existing structures are nearby, consideration of shading and terrain will be necessary. If you do not grasp the site conditions, you cannot judge how detailed the settings should be, and as a result you will become uncertain during the data-entry process.

In addition, on-site data is useful when explaining PVSyst results. If power generation is lower than expected, it is necessary to check whether the cause is shading, orientation or tilt, or loss conditions. If site photos, location information, elevation data, and layout drawings are organized, it becomes easier to explain the reasons for the results. Conversely, if site information is lacking, it becomes difficult to assess the validity of the results, whether they are higher or lower than expected.

In studies using PVSyst, information sharing between design personnel and site personnel is also important. If there is a discrepancy between the conditions entered by the design side as desk-based inputs and the actual situation understood by the site team, the simulation results will diverge from the real conditions. Obstacles confirmed on site, terrain, delivery routes, feasible installation areas, and planned future changes need to be reflected in the design conditions at an early stage.

A key factor here is having an environment in which accurate location information can be easily obtained on site and used for design studies. To improve PVSyst input accuracy, it is helpful to efficiently capture site coordinates, elevations, obstacle locations, and the installation area. Notes and photos alone can make it difficult to reconstruct positional relationships later. Organizing the high-precision location data acquired on site will give you more material for decision-making when evaluating shading and terrain in PVSyst.

LRTK, as an iPhone-mounted GNSS high-precision positioning device, acquires location information on-site and assists in confirming installation areas and surrounding conditions. When considering solar power generation facilities, being able to record site boundaries, obstacles, changes in terrain, and checkpoints with high accuracy helps organize the assumptions for desktop simulations. When examining power output and shading effects in PVSyst, having coordinate and height information obtained on-site makes it easier to clarify the basis for input conditions.

To avoid getting lost when using PVSyst, it is important not to try to complete everything within the software, but to think in terms of linking site data, design conditions, and simulation results. If site information is well organized, the rationale for input values becomes clear and it is easier to explain the results.

Summary

The reasons beginners initially stumble when using PVSyst are not limited to the software being difficult to operate. Starting to input data without understanding the overall workflow, configuring meteorological data and design conditions while leaving their meanings vague, and putting off consideration of site conditions such as shading and terrain and only looking at the results — these are major stumbling blocks for beginners.

The first countermeasure is to first organize the workflow from project information to simulation results. If you understand the sequence of location, meteorology, azimuth, tilt, equipment configuration, losses, shading, and result verification, it becomes easier to see what the items on the screen are for. The second countermeasure is to check the basis for input values by dividing them into site conditions and design conditions. If you sort out which values originate from the site and which are determined by design, you can reduce input errors and insufficient explanations. The third countermeasure is to verify the validity of the results after reflecting the site conditions. Rather than looking only at the annual generation while ignoring shading, terrain, and surrounding obstacles, it is important to make judgments that include monthly trends and the breakdown of losses.

PVSyst is software that yields practically useful results only when correct assumptions are entered. When learning how to use it, it is more important to understand the workflow of design studies, clarify the rationale for input values, and compare field conditions with results than to rote-memorize button operations. This is especially true for photovoltaic power systems, where linking desk calculations with actual on-site conditions determines the reliability of the results.

If you can accurately grasp the site location, height, obstructions, and installation area, the basis for the conditions entered into PVSyst becomes clear, and it becomes easier to explain the simulation results. By utilizing an iPhone-mounted high-precision GNSS positioning device like LRTK, you can more easily apply the high-precision location information obtained on site to design studies. By combining PVSyst power generation simulations with high-precision positioning data from the field, you can reduce the discrepancies between desk studies and actual site conditions, leading to more convincing solar power installation planning.