Explaining 5 Screens in the PVSyst Manual That Confuse Beginners

Table of Contents

• Reasons Beginners Often Get Confused by the PVSyst Manual

• Screen 1: Unsure where to start on the Main page

• Screen 2: Confused about the difference between a project and a calculation plan in Project/Variant

• Screen 3: Unsure about the meaning of the weather data in Site and Weather Data

• Screen 4: Unsure about setting the azimuth and tilt angles in Orientation

• Screen 5: Unsure about the connection between input values and results in System and Results

• Practical sequence for reading the PVSyst manual

• Checklist to Reduce Beginner Mistakes

• Summary

Why Beginners Often Get Confused by the PVSyst Manual

A common difficulty beginners feel when opening the PVSyst manual is not knowing which screen to view and in what order. PVSyst is specialized software that handles everything from designing solar power systems and sizing to energy production simulation, loss analysis, and report generation. The official documentation likewise describes PVsyst 8.1 as PC software for studying, sizing, and analyzing data for entire solar power systems.

For beginners, the difficulty is not the number of input fields itself. Rather, the main reason is that the roles of each screen do not appear to be connected. What to select on the Main page, how Project and Variant differ, where the meteorological data is determined, on which screen to set the tilt and azimuth angles, and how much you can trust the numbers on the results screen — if this flow is not organized, reading the manual will leave only fragmented operations in one’s head and will not lead to practical simulations.

To read the PVSyst manual efficiently, it is more important to first grasp the screens that every beginner will inevitably encounter than to try to learn all the features from the beginning. In particular, when assuming a grid-connected PV system, simply understanding the flow of project creation, site and meteorological data, orientation and tilt, system configuration, and simulation results makes the overall picture much easier to see.

PVSystのProject design is the area for designing and performing performance analysis of photovoltaic systems through detailed simulations. The official documentation describes a Project as holding geographical conditions and meteorological data, and explains that its structure allows multiple simulation scenarios to be compared via Variants. Understanding this mechanism beforehand will suddenly clarify the meaning of the screens.

This article narrows the focus to five screens that beginners reading the PVSyst manual are especially likely to be confused by, and explains what to look for on each screen, where configuration mistakes commonly occur, and how to check them in practice. Rather than providing a detailed explanation of every function, it emphasizes how to read the manual in order to carry the first case through to completion.

Screen 1: Unsure where to start on the Main page

When you start PVSyst, the first thing you face is the Main page. Beginners often look at items on this screen such as Project design, Utilities, Documentation, and Recent projects and can easily become unsure which to choose. When reading the PVSyst manual, it is important not to regard this Main page as merely an entry point, but to understand it as a map that distributes the overall workflow.

The official user manual explains that the Main page displays key components such as Project design and Simulation, Utilities, Documentation, Recent Projects, and Workspace. Project design and Simulation is used for detailed examination of an entire project and covers areas including weather data selection, system design, shading analysis, loss settings, and economic evaluation.

What beginners should first grasp is that if you want to run power generation simulations, you should start with Project design and Simulation. Utilities functions like a convenient toolbox, providing access to the weather database, component database, comparisons with measured data, and various tools. However, if you start with Utilities on your first project, you can get distracted by individual features and lose sight of the overall workflow.

Another reason people get confused on the Main page is the difference between Preliminary design and Project design. Preliminary design is a simplified entry point suited to initial studies and rough estimates. By contrast, Project design is an entry point for building up actual modules, inverters, azimuth, tilt, losses, and shading conditions to perform detailed annual simulations. In practical work, when preparing reports or comparing projects, beginners will find it easier to understand if they focus on learning Project design.

When reading the PVSyst manual, it is more important to decide your objective first than to try to memorize the Main page by clicking each button in order. For example, if you want to perform an annual energy production simulation, use Project design; if you want to check component data or meteorological data, use Databases; if you want to look up the meaning of an operation, use Documentation; and if you want to open past projects, use Recent projects—match your goal to the entry point.

A common mistake beginners make is leaving an existing demo project or a recent project open and then losing track of what they have changed. Especially during the practice stage, you should be clear whether you are creating a new project or duplicating an existing one to use. If you assign arbitrary names to the project, location, weather data, or Variant, it will be difficult later, when viewing the results screen or reports, to determine which conditions those results correspond to.

The key points to remember on the Main page are not every item shown on the screen. First, Project design and Simulation are the entry points for detailed simulations, Utilities is for supplementary data checking and creation, and Documentation is the help to consult during operation—focusing on these three is sufficient. If you get confused when starting to read the PVSyst manual, try sorting things out by distinguishing whether the screen you’re looking at is the main workspace, data management, or help.

Screen 2: Confused about the difference between 'Project' and 'Variant' for projects and calculation proposals

One of the screens that PVSyst beginners find most confusing is the Project/Variant screen. The reason for the confusion is that the roles of Project and Variant appear similar. Both carry names related to the same job, both are saved, and both can be reselected later. For that reason, beginners often lose track of whether they changed the project or changed the calculation variant.

When reading the PVSyst manual, it's easier to understand if you think of a Project as a container for a project and a Variant as a set of calculation conditions. A Project mainly contains the location, meteorological data, and basic information that pertains to the entire project. On the other hand, a Variant contains the specific design conditions that are actually simulated, such as modules, inverters, series-parallel configuration, azimuth (orientation), tilt, shading, losses, and economic conditions.

The official documentation also explains that a Project can include geographic conditions and weather data, and that multiple Variants can be created as needed. It also shows the procedure: define the Project from the Project/Variant button, set Orientation and System for each Variant, and proceed to Simulation once the red warnings disappear.

One common mistake beginners make on this screen is trying to create a complete Variant from the outset. The PVSyst manual recommends first creating an initial system configuration with the minimum necessary parameters, simulating and saving it, and then progressively adding far shading, near shading, detailed losses, and so on. This approach is also very effective in practice.

In the first Variant, prioritize completing the overall workflow to the end rather than perfect inputs. Set the location, select the weather data, decide the orientation and tilt, enter a rough configuration of modules and inverters, and run the simulation once. After that, save other Variants — one with adjusted loss conditions, one with added shading, and one with changed capacity. This makes it easier to compare which changes affected the results.

On the Project/Variant screen, how you name things is also important. Beginners tend to give names like "test", "Plan 1", or "after revision", but later, when comparing, it becomes hard to tell what they contain. For example, if you use names that make the differing conditions clear—Roof A south-facing 20 deg, east-west plan 10 deg, with shading, after loss review—you're less likely to get confused when you look back at the results screen or the report.

Also, if you do not understand the difference between Project and Variant, you may end up adding only Variants in situations where you should change the site or weather data. For example, when comparing design proposals within the same site, it is easier to manage them as Variants within the same Project, but for cases where the location or weather conditions differ significantly, it may be clearer to separate them into different Projects.

On this screen, particular attention should be paid to the red, orange, and green status indicators. The official tutorial explains that red means an undefined or unacceptable parameter, orange means an acceptable but not ideal parameter, and green means a correctly defined state, and that if any red remains the Simulation will not be enabled. Beginners should use these indicators not merely to check for the presence of errors, but as a guide to trace which screen’s settings are still incomplete.

When reading the Project/Variant sections of the PVSyst manual, it's important not just to follow the operational instructions, but to ask yourself, "Is this information for the entire project?" and "Is this a calculation condition for comparison?" Being able to make that distinction greatly reduces mistakes when handling multiple proposals.

Screen 3: Confused about the meaning of the weather data in Site and Weather Data

When performing power generation simulations in PVSyst, the Site and Weather Data screen is extremely important. Beginners often become confused on this screen about whether they should select a site, choose weather data, enter latitude and longitude, or which values are actually affecting the simulation.

In solar PV simulations, even with the same installed capacity, the annual energy yield varies depending on solar irradiance, temperature, and regional conditions. Therefore, when reading the PVSyst manual you should understand "Site and Weather Data" not as a mere address-entry screen but as the interface for defining the simulation's assumptions.

The official documentation explains that a Project includes geographic conditions and weather data. In other words, what is decided in Site and Weather Data is the foundation that comes before subsequent Orientation and System settings. No matter how carefully you configure modules and inverters, if the location and weather data do not match the actual project, you may misinterpret the results.

What beginners should first check is whether the target location has been correctly selected. Don’t rely solely on the place name; verify the latitude, longitude, elevation, time zone, and the type of meteorological data. In particular, when there are locations with similar names or when substituting weather data from a nearby city, you need to organize your reasoning well enough to explain it in the report.

Another important point is the source of the weather data. In PVSyst, you may use meteorological data from the built‑in database or data imported from external sources. Beginners often assume that the weather data shown are automatically the optimal choice, but in practice you need to clearly state which data were adopted. Especially when explaining the validity of the power generation figures, the reasons for selecting the weather data directly determine the credibility of the results.

When you're unsure about Site and Weather Data, follow the steps in the manual and consider site information and weather files separately. Site information describes the location that is the subject of the simulation, while a weather file provides data on the solar resource and meteorological conditions at that location. Because these two are related, they are easily confused, but their roles are different.

Also, care must be taken in how albedo is treated. Albedo is a value related to reflection from the ground surface, and in typical projects it is often not changed significantly, but in snowy regions or under special ground-surface conditions it may need to be considered. For beginners, rather than making fine adjustments from the start, it is safer to first run simulations based on standard assumptions and consider changing them only when there are clear, project-specific reasons to do so.

A practical way to verify this screen is to jot down the assumptions before looking at the results. Confirm the location, the meteorological data used, elevation, albedo, and the period and type of the data so you can go back if you later find the estimated energy production is too high or too low. Even when working while reading the PVSyst manual, instead of just entering the values on the screen and proceeding, record why you used those values so it’s easier to explain them during design reviews.

For beginners, the Site and Weather Data screen may look plain, but it is actually an important screen that determines the basis of the simulation. If you proceed while leaving this unclear, no matter how carefully you check the System and Results later, the meaning of the results will become unstable. When reading the PVSyst manual, understanding the role of this screen early on is the quickest route to a correct simulation.

Screen 4: Unsure how to set the azimuth and tilt angles in Orientation

Orientation is a screen that PVSyst beginners often find difficult to grasp intuitively. It is the screen for setting the orientation and tilt of solar panels, but because factors such as azimuth angle, tilt angle, fixed racking, tracking racking, east-west layouts, roof planes, and ground-mounted installations are involved, users can easily be unsure which values to enter and how.

When reading the PVSyst manual, it helps to think of Orientation as the screen that decides which part of the sky the panel is facing. Even if you decide which module types and how many to use on the System screen, if you get the azimuth or tilt wrong in Orientation, the way the panel receives solar radiation changes and the annual energy production will change. For that reason, Orientation is one of the screens that determines the foundation of power generation.

The official documentation explains that fixed-tilt surfaces are mainly defined by plane tilt and azimuth, and can be configured while confirming the tilt and azimuth on a dynamic on-screen diagram. It also provides a simple optimization tool for fixed surfaces that shows the energy yield corresponding to tilt and azimuth.

The first thing that confuses beginners is how to think about azimuth. In everyday conversation we describe orientations as "south-facing," "east-facing," or "west-facing," but on the PVSyst screen they are handled as numerical values, so you need to check which directions correspond to positive values and which to negative. If you enter this based on assumptions, you can make the mistake of thinking a surface is south-facing when it is actually shifted toward the east or west.

Another aspect that people often find confusing is the tilt angle. For roof-mounted installations, it is often matched to the roof pitch, while for ground-mounted systems it may be determined by factors such as power generation, racking structure, site conditions, shading effects, and maintainability. Beginners tend to think “just choose the optimal angle,” but in practice the tilt angle is not necessarily decided solely by power generation. Site constraints and construction conditions, snow, wind loads, and shade avoidance also play a role.

On the Orientation screen, you need to pay attention to projects with multiple orientations. In roof projects, panels may be arranged not only on the south side but also divided between the east and west sides. In PVSyst, there are situations where multiple Orientations are handled within the same system. The official documentation also explains that if not all arrays have the same Orientation or field type, you can add them with Add Orientation as needed.

Beginners sometimes enter multiple surfaces as a single averaged orientation or tilt. However, lumping together east- and west-facing surfaces, south-facing and north-leaning surfaces, or low- and high-slope surfaces will misrepresent the actual insolation conditions and the power generation curves. For initial practice, understand using a single orientation, and once you become comfortable, it’s better to separate design options using multiple orientations.

Errors in Orientation will show up on the Results screen as generation that does not match expectations. For example, if the system is assumed to be south-facing yet the generation is low, if it is configured as an east-west layout but the morning and evening characteristics are not reflected, or if you cannot discern the generation trends for each roof surface, you should review Orientation before the System screen.

When reading the PVSyst manual, it is important not to treat the Orientation screen description as merely an input procedure, but to be aware that "this setting determines how solar radiation is received." Especially for beginners, while looking at the diagram on the screen, check whether the orientation matches the actual installation drawings and layout plans. You are more likely to notice mistakes by comparing the diagram with the project conditions than by judging from numbers alone.

Screen 5: Confused about the connection between input values and results in System and Results

The System screen is the screen that PVSyst beginners often find has the most input fields. Here you configure items that directly affect the energy production simulation, such as PV modules, inverters, string configuration, number of parallel strings, capacity ratio, and loss conditions. Beginners often become unsure on this screen which fields are required and which are detailed settings that can be adjusted later.

When reading the PVSyst manual, it helps to think of the System screen as the screen that determines the installation's electrical configuration. If the Orientation screen is the one that sets the panels' orientation and tilt, the System screen is the one that decides which equipment to use and in what combinations. The settings made here directly feed into the simulation results, the loss diagram, and the numerical values in the report.

In the Project design workflow, after defining Orientation you define System properties, and the procedure indicates that the program checks the consistency of parameters and displays warnings. In other words, the System screen is not just for selecting equipment but also a place to check for any inconsistencies in the design.

For beginners, the first things to check are the selection of modules and inverters. The module model, rated output, number of modules, number in series and in parallel, and the inverter capacity affect the design capacity and operating range. If these inputs are wrong, they will affect not only the generated energy but also warning displays and whether simulation is possible. In particular, whether the number of modules in series fits the voltage range, and whether the configuration is excessively large or small for the inverter, are points that beginners tend to overlook.

On the System screen, PVSyst may display orange or red warnings. Red indicates problems that prevent the simulation from proceeding, while orange indicates issues that require attention but still allow progress. Beginners tend to ignore orange warnings, but in practice it is important to check why they are orange. You must determine whether it is an acceptable design caution or a condition that is close to an input error.

Once the basic configuration is done on the System screen, next check the results on the Results screen. In PVSyst, after a simulation the Results dialog opens, and the workflow explains that the main results can be reviewed in the Report. Beginners tend to focus only on summary values such as annual energy production and performance ratio when viewing the Results screen, but in practice it is important to examine the breakdown of losses.

The official documentation explains that Results contains many simulation variables, such as monthly, daily, hourly, and sub-hourly, and that the Loss Diagram is useful for identifying weaknesses in system design. In other words, the Results screen is not simply a screen for seeing "how many kWh of power are generated," but a screen for checking which settings lead to which losses.

What beginners often find confusing in Results is that when power generation is lower than expected, they don't know which screen to return to. If there is a problem with solar irradiance conditions, check Site and Weather Data; if there is a problem with orientation or tilt, check Orientation; if there is a problem with equipment configuration or capacity ratio, check System; if shading or losses are large, review the Detailed Losses or Shading-related screens. Results is both the final screen and a diagnostic screen for returning to the input screens.

Also, beginners tend to try to set all detailed losses in their first simulation. However, if you include temperature losses, wiring losses, soiling, mismatch, IAM, shutdown losses, etc. in detail from the start, it becomes difficult to tell which elements affected the results. It is better to first produce results under standard conditions, and then add losses by creating separate Variants; this approach is more suitable both for understanding the PVSyst manual and for explaining things in practice.

System and Results should be understood together. The equipment configuration and loss conditions entered in System are reflected in the generated energy, performance ratio, and loss diagram in Results. If anything in Results feels off, return to System and check the input values. With this back-and-forth as the premise, PVSyst becomes easier to use not merely as an input program but as a tool for verifying design conditions.

Practical order for reading the PVSyst manual

If a beginner tries to read the PVSyst manual straight through from beginning to end, they are likely to get lost along the way. Because there are many features and many screens, trying to read everything with the same level of importance will not translate into actual work. Therefore, at first it is important to read it following the flow of practical work.

The recommended order is Main page, Project/Variant, Site and Weather Data, Orientation, System, Simulation, and Results. In this article, in order to organize the five screens that beginners are likely to get confused by, we treat System and Results as a single flow; however, in actual use you understand them by going back and forth between the input and confirmation screens.

First, confirm the entry point on the Main page and create a new project from Project design. Next, use Project/Variant to separate the overall project and the calculation variant. After that, set the site and weather data in Site and Weather Data. This forms the foundation for the simulation prerequisites.

Next, set the panels' orientation and tilt in Orientation, and configure the system components in System. Once the red warnings have disappeared, run the Simulation and check the results in Results. If anything in the results seems off, determine which input conditions you should revert to. After going through this workflow once, you'll be able to read the chapters of the PVSyst manual not as isolated explanations but as a continuous series of tasks.

A reading approach beginners should avoid is searching only for the items that concern them and entering numbers on the spot. For example, even if you look up only wiring losses and change the value, if the System configuration or Orientation are wrong to begin with, it will not lead to improved results. The PVSyst manual can be used as a function-by-function reference, but for beginners it is safer to read it following the sequence of operations.

Also, if you encounter items you don't understand while operating, it can be helpful to use the on-screen help or the F1 key. The official documentation explains that within PVsyst you can open context-sensitive help via the F1 key or the on-screen help icon. For beginners, reading the help related to the screen you currently have open is often easier to understand than searching through the entire manual.

A practical tip for reading the PVSyst manual is to organize the screen names, their purposes, the values to enter, and the impacts on results as a set. Memorizing screen names alone is meaningless. For example, Orientation determines azimuth and tilt, and relates to energy production and shading effects. System determines equipment configuration, and relates to capacity and losses. Results should be used not only to view outputs but also to assess the validity of input conditions. Reading in terms of these causal relationships makes understanding easier to retain.

Checkpoints to Help Beginners Avoid Pitfalls

To help beginners avoid pitfalls in PVSyst, it's important not to try to achieve the final result in a single pass. If you attempt from the start to include detailed shading, detailed losses, economic assessments, batteries, self‑consumption, and P50/P90, you'll lose track of what the screens mean. It's better to run a basic simulation first and then add conditions afterward; that approach helps both in understanding the manual and in explaining the results.

The first checkpoint is the names of the Project and Variant. Simply assigning names that make it clear which project, location, and calculation scenario they refer to will significantly reduce later confusion. This is especially important when comparing multiple scenarios: if Variant names are ambiguous, you won't know which scenario's results you're looking at.

The next points to check are the location and the meteorological data. Before discussing the magnitude of power generation, confirm which location and which meteorological data were used. If these are misaligned, then even if you adjust the System or the loss conditions, it will be difficult to provide a fundamental explanation.

The third point to check is Orientation. Verify that the azimuth, tilt, and the handling of multiple orientations in PVSyst match the actual drawings and layout conditions. Confirm that the project's basic conditions—such as south-facing, east–west facing, and differences between roof surfaces—are reflected here.

The fourth checkpoint is the System's equipment configuration. Check the modules, inverter, number of modules in series, number of modules in parallel, capacity ratio, and warning indications. Beginners tend to look only at the number of modules or the system capacity, but electrical compatibility and the combination with the inverter affect the results.

The fifth checkpoint is the loss diagram in Results. Rather than looking only at annual energy production, check where energy is being lost. If any items show large losses, return to the corresponding input screens. This way you can use PVSyst not merely as a result-output tool but as a verification tool to improve the design.

Beginners tend to think that if the warnings disappear it's correct, if the simulation runs it's valid, and if a report is produced it's complete. However, in PVSyst what matters is not that results are produced but that you can explain those results. You should aim to be able to explain why this location was chosen, why this meteorological data was used, why this tilt angle was selected, why this capacity ratio was chosen, and why these losses are occurring.

The PVSyst manual is both a resource for looking up items you don’t understand and a guide for verifying design conditions. When beginners read it, they should pay attention not only to the operating procedures but also to the purpose of each screen and how it affects the results. Reading it that way will greatly change the depth of understanding of the same manual.

Summary

In the PVSyst manual, the screens that beginners are likely to get confused by can be organized into five: Main page, Project/Variant, Site and Weather Data, Orientation, System and Results. These are not standalone screens; they are connected as part of the simulation flow.

On the Main page, you learn the entry point for starting a detailed simulation. In Project/Variant, you organize the overall project and the differences between calculation scenarios. In Site and Weather Data, you set the simulation assumptions: location and weather data. In Orientation, you configure the panel orientation and tilt. In System and Results, you enter the equipment configuration and check the resulting power generation and losses.

What beginners should aim for initially is not to memorize all of PVSyst’s features. First, create a single project, run a simulation under basic conditions, review the results, and understand the flow of returning to the input screen. Once you understand this sequence, the contents of the PVSyst manual will be easier to connect to practical operations.

PVSyst has many input fields, so it can feel difficult at first. However, by clarifying the role of each screen you can greatly reduce confusion. Project is the container for a case, Variant is the design option to compare, Site and Weather Data are the assumptions, Orientation defines how the site receives solar radiation, System specifies the equipment configuration, and Results are where you check the input conditions. Reading the manual with these relationships in mind makes it easier for beginners to grasp the overall picture of a power generation simulation.

When you're unsure while using the PVSyst manual, check what the screen you're viewing determines and how its settings affect the results. Understanding the purpose of a screen, rather than memorizing operations, is the quickest route to mastering PVSyst for practical use.