PVSyst Manual for Beginners｜7 Steps for On-Screen Operations

For practitioners using PVSyst for the first time, the thing they are most likely to stumble over is not the calculation theory itself but the difficulty in seeing which screen to enter what information on and in what order to check things. The official screen and item names in PVsyst may vary by version, but the basic flow of a power generation simulation is to set up the site, meteorological data, azimuth, tilt, system configuration, loss conditions, shading conditions, and result verification in that sequence. Even if a single screen is entered correctly, if the surrounding conditions are misaligned, the results will not be easy to explain in practice. In this article, aimed at beginners searching for the PVSyst manual, I explain the screen operation flow in 7 steps. Before diving into detailed specialized settings, first understand the role of each screen and the order of checks to make the first-time operation less confusing.

Table of Contents

• Overall picture to understand first when operating the PVSyst interface

• Step 1: Open the workspace and select the project type

• Step 2: Verify the site location and meteorological data

• Step 3: Enter the azimuth and tilt angle to configure installation conditions

• Step 4: Enter the system configuration and confirm capacity and component combinations

• Step 5: Review loss conditions and detailed settings as required

• Step 6: Check shading conditions and assess their impact on results

• Step 7: Run the simulation and interpret the report

• Common pitfalls for beginners when operating the interface

• Summary for applying PVSyst operation to practical work

The Overall Picture You Should Understand First About PVSyst Screen Operations

PVSyst is specialized software used for designing photovoltaic power systems, simulating energy production, and analyzing results. When beginners learn the interface, rather than trying to understand all items at once, it is important to grasp the input workflow by dividing it into major steps. Basically, you create a project, choose the location and meteorological conditions, enter the installation conditions, set the system configuration, and check losses and shading conditions before running the calculation. If you work without being conscious of this order, you will end up going back to make corrections later, and it will become difficult to know under which conditions the results were calculated.

There are many settings on the screen, but on your first use you do not need to change everything in detail. First, run a calculation once under standard conditions and check the results screen and the breakdown of losses. After that, if you review orientation, tilt, system capacity, shading, wiring, temperature, shutdown conditions, and so on in stages to match the actual project, it becomes easier to understand the relationship between the input values and the results. If you dive into detailed screens from the start, you will end up working without understanding the meaning of the numbers you entered, so beginners in particular should be mindful of handling the screens in a fixed order.

When using PVSyst, it's important to grasp the concepts of projects and variants. A project is the framework for managing the site and meteorological conditions for the whole case. A variant, on the other hand, is the unit used to compare different installation conditions or equipment configurations within the same project. For example, if you change the tilt angle at the same site, change the installed capacity, or introduce shading conditions, separating them into different variants makes comparison easier. For beginners, rather than overwriting settings each time, making a habit of saving under a new name whenever you change conditions will prevent confusion when reviewing results later.

Also, when operating the software interface, it's important not only to check the input values themselves but also to confirm the units and assumptions. In energy production simulations, many similar numerical values appear, such as angles, distances, areas, capacities, and loss rates. If you enter numbers into input fields without confirming their meaning, you risk misinterpreting the azimuth direction, the reference for tilt, the units of capacity, or how loss rates are handled. When using PVSyst in professional practice, calculation results are often used for internal presentations, design reviews, energy production comparisons, and proposal documents, so organizing the assumptions during the interface operation stage contributes to quality control.

Step 1: Open the work screen and select the project type

The first step is to open the workspace and select which type of photovoltaic system to consider. In PVSyst, input workflows are provided to match different purposes, such as grid-connected, stand‑alone, pumping applications, and DC grids. When evaluating the energy yield of a typical power plant or rooftop installation, you will often choose a project type that assumes grid connection. Because the selected type changes the input fields required on subsequent screens, confirm that your initial choice matches the project’s objectives.

What beginners often confuse is the difference between screens that are close to preliminary assessments and screens for detailed generation simulations. The screen depth you use differs between the stage where you want to check a rough sense of capacity and general feasibility, and the stage where you want to examine annual power generation reflecting actual design conditions. When using generation calculations as the basis in practice, it is standard to proceed with data entry following the detailed project design workflow. At first, don’t judge by the screen name alone; choose a screen that lets you configure the entire sequence—location, meteorological data, equipment configuration, losses, shading, and reports.

When creating a new project, the way you name it is also important. If you save it using only the date or a placeholder name, it will be difficult to find later when handling multiple projects. Including information in the project name that makes it easy to identify internally—such as region, equipment category, project stage, and creation date—will make management easier. However, it is safer to avoid names that are too long or abbreviations that only the person in charge understands. Since simulations are run repeatedly with changing conditions, deciding on rules for saved names from the outset will make later comparison work smoother.

After selecting the project type, before moving straight into the detailed settings, review the overall layout of the screen. Take a moment to see where to set the site, where to enter the system configuration, where to run the calculations, and where the results will be displayed — this makes it less likely you'll get lost while working. Because PVSyst has many configuration items, the screen can feel complicated for beginners, but the order of input is relatively well organized. The first step in mastering the operation is to navigate the screen and identify which buttons and input fields correspond to each process.

Step 2: Check location information and weather data

In the following steps, you will set the project's location information and meteorological data. In power generation simulations, meteorological conditions such as solar irradiance and temperature greatly affect the results. Therefore, configuring the location is not merely entering an address but a crucial process that determines the basis of the calculations. If location information such as latitude, longitude, elevation, and time zone differs significantly from the actual project site, the treatment of solar radiation conditions and solar altitude will change, reducing the reliability of the results. Beginners should not be reassured by a similar location name alone and must verify that the coordinates and the region match the project.

On the weather-data selection screen, multiple candidate datasets may be displayed. What is important here is to keep the system in a state where you can record which dataset was used. Solar radiation and temperature values can vary depending on the type of data referenced and the proximity of the location. When comparing power generation or conducting internal reviews, you are required to explain not only the results themselves but also which weather conditions were assumed. Therefore, even during the initial operation, confirm the weather dataset name, the target location, creation conditions, update timing, and so on, and make sure they are recorded so they can be reviewed later.

A common mistake when setting the site is selecting a similar place name by accident. Even if the regional name is the same, the prefecture or municipality may differ. Also, for overseas projects, remote islands, mountainous areas, or coastal zones, using meteorological data from a nearby location can result in differences from the actual weather conditions. Rather than just selecting a candidate on PVSyst's screen, it is important to separately verify the planned site's coordinates and surrounding environment and judge whether the chosen site is appropriate. In particular, when entering data be mindful of regional characteristics such as elevation differences in mountainous areas, sea breezes and cloud patterns in coastal areas, and the influence of nearby obstructions in urban areas.

After setting the meteorological data, do not immediately proceed to the next screen; confirm that it has been correctly saved as the project's basic condition. If you change the site or meteorological data partway through a simulation, it can become difficult to track which variants correspond to which data. At the initial stage, it's easier to create a single baseline case using standard meteorological data, and then, if necessary, compare under different conditions. Because the site and meteorological data are fundamental to the calculation results, treating them carefully supports the overall accuracy of PVSyst operations.

Step 3: Enter the azimuth and tilt angle to configure the installation conditions

After setting the location and meteorological data, next enter the azimuth and tilt angle of the solar panel surface. Azimuth and tilt are basic parameters that directly affect power generation. The direction the installation faces and the angle at which it is tilted determine the amount of solar radiation received throughout the year. What beginners should pay particular attention to is the azimuth reference. If you enter values without confirming on the screen which direction is used as the reference for the angle, you may end up calculating conditions for an orientation different from what you intended. Check the descriptions of the input fields and set them while comparing with the diagram and the angle display.

On rooftop installations, the roof pitch may directly determine the tilt angle. On the other hand, for ground-mounted systems, the rack angle is entered as a design parameter. When there are multiple orientations or tilts, rather than forcing them into a single condition, consider treating each surface separately. For example, if a roof has east- and west-facing sections, the generation timing and the way solar irradiation is received will differ even for the same capacity. Depending on the version and settings of PVSyst, functions may be available to handle multiple mounting surfaces and orientation conditions, so decide whether to separate them based on the actual circumstances of the project.

When entering azimuth and tilt, it is essential to cross-check them against design drawings and site survey information. Verify that the north direction on the drawings, the orientation on the survey map, the slope on the roof plan, and the direction confirmed on site are consistent. In particular, whether the north shown on the drawing is true north, grid (coordinate) north, or a schematic north can lead to differences in interpretation. Because concentrating only on PVSyst screen operations can make it easy to overlook the assumptions in the source materials, it is important to gather the supporting documents before entering the data.

On your first operation, after entering the azimuth and tilt, proceed while checking how much solar irradiation is obtained under those conditions to deepen your understanding. Rather than simply entering numbers and moving on, compare how the results change when you alter the azimuth or tilt; this makes it easier to grasp the meaning of the on‑screen operations. However, in actual practice you should make reasonable inputs based on site conditions, not conveniently change conditions to make the results look better. While PVSyst is useful for comparative evaluation, results can vary depending on the user’s assumptions, so strive to set conditions with a sound, evidence‑based rationale.

Step 4: Enter the equipment configuration and verify capacity and combinations

Once you have set the installation conditions, the next step is to enter the equipment configuration. Here you specify the type of photovoltaic modules, the number of modules, the number in series, the number in parallel, and the combination with conversion equipment such as inverters. For beginners, this screen contains many technical terms and often feels like the most difficult part. However, the basic idea is to check whether the combination of the installed PV array and the power conversion side is reasonable in terms of voltage, current, and capacity ranges. You must not only enter the total capacity but also verify that the actual configuration is feasible.

When configuring the system, be careful not to make input errors in the number of modules in series and the number of parallel strings. The number in series mainly affects voltage, while the number in parallel affects current and total capacity. If these are confused, the resulting capacity may be larger than expected, or conversely smaller. Also, because the voltage range changes with temperature conditions, you should verify that the operating range at low and high temperatures falls within acceptable limits. In PVSyst’s interface, warnings or confirmation messages may appear for the entered configuration. If a warning is displayed, do not proceed without reading it; check which condition is causing the problem.

To make work easier for beginners, rather than trying to reproduce a complex equipment configuration from the start, it is effective to first create a baseline case using a representative configuration. For example, perform a calculation once with a simple setup where photovoltaic modules of the same specification are installed with the same orientation, and then add multiple orientations, different capacities, and constraint conditions; this makes it easier to see which settings affected the results. The more complex the project, the more important it is to increase input conditions step by step. If you include everything from the beginning, it becomes difficult to identify the cause when an error occurs.

After entering the equipment configuration, check the summary information displayed on the screen, such as capacity, area, power ratio, and voltage range. Here you verify whether these values deviate significantly from the actual design conditions or the expected capacity. For example, if the capacity on the drawings does not match the capacity in PVSyst, the number of modules, units, number of configurations, or the surface selected for input may be incorrect. In practice, not only the simulation results but also the equipment conditions you entered are subject to verification. Before issuing a report, make it a habit to review the summary on the equipment configuration screen and confirm that it matches the project’s basic conditions.

Step 5: Review the loss conditions and detailed settings as needed

Once you have entered the system configuration, the next step is to check the loss conditions. In solar power simulations, the energy received from solar irradiance does not directly become generated electricity. Various factors cause losses, such as temperature rise, wiring, conversion, soiling, module variability, downtime, and the incident angle effect. PVSyst provides screens to set or review these losses. For beginners, rather than changing every item in detail, it is important first to understand what each loss means and to check that values are not significantly different from the initial values or your company's standards.

One thing to be careful about regarding loss assumptions is to avoid making adjustments without justification. It is not desirable in practice to reduce losses to make generation appear higher, or to inflate them excessively to appear conservative. Loss rates should be set based on design conditions, the installation environment, materials used, the maintenance plan, operating conditions, and so on. For items where the basis for the input is unclear, clarify whether you will use initial values, in-house standards, or reflect project-specific conditions. Numbers that cannot be explained will become weaknesses when reviewing the results later.

Wiring losses and temperature losses are items that beginners tend to overlook. Wiring losses are related to wiring length, cross-sectional area, and current conditions. Temperature losses are influenced by the installation method, ventilation conditions, and ambient temperature. The way you should consider temperature conditions can differ between installations close to a roof and ground-mounted racks where ventilation is ensured. PVSyst's detailed settings can reflect these conditions, but changing input values without understanding their meaning can lead to unnatural results. For beginners, it is safer to proceed while noting which items were changed and the reasons for those changes.

Also, loss settings are not something you finish once and forget; you need to verify their validity by reviewing the breakdown of losses on the results screen. If, when looking at the post-calculation loss chart, a particular loss is disproportionately large or an anticipated loss is not reflected, go back to the input screen and check. Because loss conditions strongly affect the appearance of the power output, this part of the interface is of high importance for quality control. On your first run, prioritize understanding which screen handles which losses rather than trying to perfectly adjust every item.

Step 6: Check shadow conditions and understand their impact on the results

Next to check are the shading conditions. In solar power installations, shading can occur from surrounding buildings, trees, terrain, mutual shading between mounting structures, rooftop structures, and so on. The effects of shading not only slightly reduce energy production, but can also change significantly depending on the time of day and season. PVSyst takes an approach of treating shading from distant terrain and mountain ranges separately from shading caused by nearby obstacles. Beginners should first understand the purpose of configuring shading and decide to what extent it needs to be reflected in a project.

The important thing in shading settings is to represent on-site conditions neither insufficiently nor excessively. Creating an overly complex shading model for a project with little to no shading impact not only takes more time to work with but also increases the risk of input errors. Conversely, ignoring shading in projects where surrounding buildings or elevation differences clearly have an effect can lead to overestimating power generation. In particular, for rooftop installations, surrounding upstands, rooftop structures, equipment, railings, and adjacent buildings can all be sources of shading. For ground-mounted installations, it is necessary to check row spacing, topography, surrounding trees, and adjacent structures.

When beginners work with a shading screen, it is important not to overdevelop the details from the outset. First create a baseline case without shading, and then create cases that add the main shading factors—this makes it easier to compare reductions in power generation caused by shading. If you include multiple shading factors at once, it becomes difficult to tell how much each factor is affecting the result. In practice, depending on the stage of review, a simple shading check may be sufficient in some cases, while detailed shading analysis may be necessary in others. It is useful to distinguish the purpose of the screen operation—whether it is for a rough estimate, design review, or for presentation materials.

When you enter the shadow conditions, check the results screen to see how much shading loss is occurring. If you set shadows but see almost no loss, the shadow position, target surface, time conditions, or obstacle height may not be correctly reflected. Conversely, if the shading loss is larger than expected, check whether you have entered an obstacle that is too large or whether the azimuth or distance are off. Although shadow settings are visually easy to understand, numeric input errors are also common, so it is important to proceed while cross-checking with drawings and on-site photos.

Step 7: Run the simulation and read the report

Once the settings are configured, run the simulation. For beginners, pressing the calculate button and seeing the energy production displayed can feel like the task is complete, but in professional practice the verification that follows is important. The simulation results show annual energy production, monthly production, performance indicators, and a breakdown of losses. Rather than looking only at the annual total production, first check monthly trends and the flow of losses. By examining differences between summer and winter, the relationship with irradiance conditions, temperature-related declines, shading effects, and so on, you can judge whether the input conditions are realistic.

What you should particularly check in the results report is whether the input conditions have been correctly reflected. Confirm that the location, meteorological data, orientation, tilt, system capacity, loss conditions, shading conditions, etc., are output as intended. If you extract and use only the power generation figures, the underlying assumptions will become unclear. When sharing internally or presenting to clients, you need to be able to explain which conditions were used for the calculations alongside the results. It is important to treat PVSyst reports as documentation to verify the basis of the calculated results.

When reading the breakdown of losses, follow how the energy decreases from top to bottom. By looking at how much loss occurs at each stage between solar irradiation and electricity output, you can assess the validity of equipment conditions and input values. For example, large temperature losses prompt a review of the installation method and temperature conditions; large shading losses call for checking the shading settings; and large wiring losses indicate a need to review the wiring conditions. The loss diagram can be used not just as a result display but as a verification screen to detect input errors and design issues.

When running multiple simulations, saving and comparing variants is important. Save separate cases for different tilt angles, different capacities, added shading, adjusted loss conditions, and so on, so you can organize which condition changes affected energy yield. If you keep working by overwriting, you will lose track of previous conditions and have trouble when preparing comparison materials. From the beginner stage, make it a rule to include the changes in the variant name, note the key conditions, and keep a baseline case; doing so will make PVSyst easier to use in practice.

Common Pitfalls Beginners Often Encounter When Operating On-Screen Controls

A common pitfall for PVSyst beginners when operating the interface is proceeding without deciding the input order. If you finalize the system configuration before selecting the meteorological data, or adjust loss settings while azimuth and tilt are still ambiguous, you will have to make many corrections later. Power generation simulations produce results from accumulated assumptions, so you need to manage in sequence what you decide on each screen. Simply fixing the workflow — first the site, then the installation conditions, then the system configuration, then losses and shading, and finally result verification — can greatly reduce operational mistakes.

Another mistake is skipping warnings and confirmation messages. In specialized software, the screen may display alerts when input values are unusual or fall outside the recommended range. Beginners, eager to proceed with calculations, tend to run the process anyway, but warnings often contain clues to input errors. Even if you do not understand the displayed message, it is important to record which screen and which input field the warning came from and to review the conditions. Ignoring warnings can make the results difficult to use as explanatory material.

Also, unit mix-ups are common. The units for capacity, area, angle, loss rate, distance, temperature, and so on are set by the screen. The units on drawings or internal documents do not necessarily match the units in PVSyst input fields. In particular, for fields where you enter percentages, angles, distances, or heights, be careful about order-of-magnitude or sign differences. Even if an entered value looks plausible at first glance, different units can greatly change the results. Check the units before entering values, and after entry verify on the summary screen that the total capacity and loss rates look reasonable.

Moreover, it is dangerous to judge based only on the numerical results. Just because the annual energy production is close to the estimate does not mean the input conditions are correct. Multiple mistakes can accidentally cancel each other out, making only the apparent energy production look plausible. When reviewing results, check the annual energy production, monthly energy production, loss breakdown, system capacity, and installation conditions together. In practice, being able to explain the rationale is more important than the magnitude of the numbers. PVSyst is a powerful calculation tool, but it is the responsibility of the person who entered the data to assess the validity of the results.

Summary for Applying PVSyst Operations to Practical Work

For beginners learning how to operate PVSyst's interface, understanding the workflow is more important than memorizing detailed setting items. First select the project type, set the location and meteorological data, enter the azimuth and tilt, configure the system components, confirm the loss and shading conditions, and then run the simulation. If you keep these seven steps as a basic template, you can reduce hesitation in operation even when projects change. In particular, location, meteorological data, azimuth, tilt, and system capacity form the foundation of power generation, so it is important to carefully verify them at the initial input stage.

When using PVSyst in practice, the goal is not just to produce calculation results. You must be able to explain under what conditions the calculations were run, why those settings were chosen, and which parts of the results deserve attention. To do that, it is essential to record the conditions while working in the interface, separate variants, and follow a workflow that verifies the assumptions in the report. For beginners, prioritizing an understanding of the connection between input conditions and results over quickly generating numeric outputs makes it easier to apply that knowledge later.

When you become familiar with operating PVSyst, the range of practical uses expands to include comparing energy production, checking the effects of shading, examining equipment configurations, and reviewing loss conditions. On the other hand, because there are many input items, discrepancies in assumptions and omissions in checks are more likely to occur. To avoid making screen operations person-dependent, standardizing input procedures, file naming, checklist items, and how reports are read across the company makes it easier to stabilize the quality of simulation results. This is especially important when multiple people handle a project: managing things so that anyone can follow the same assumptions is essential.

When considering solar power generation, you need to connect not only the simulated power output but also field surveys, design conditions, post-construction verification, and maintenance management. By matching the assumptions for power output created in PVSyst with on-site conditions and operational data, you can make decisions that are closer to real-world practice. If you want to streamline the entire process—from power output simulation as the starting point to site surveying, post-construction inspections, and operational data management—comparing and evaluating field-data utilization tools like LRTK Solar according to your company’s workflow will make it easier to link desk calculations with field operations.