Organize 10 frequently asked questions in the PVSyst manual

##【Translation unit annotation rules】

• Do not convert speed (m/s), temperature (℃), mass (kg), etc.

• In addition to the original SI notation, append the imperial units in parentheses: 〇〇 m (△△ ft), 〇〇 cm (△△ in), 〇〇 mm (△△ in)

• Put a half-width space between the number and the unit; use ft / in for the units (do not add a plural "s")

• Rounding must not exceed the number of decimal places in the original text - For integer meters, express ft with 0–1 decimal place(s) (e.g., 1 m → 3.3 ft / 3 ft, 10 m → 32.8 ft / 33 ft) - For meters with one decimal place, express ft with one decimal place (e.g., 1.5 m → 4.9 ft) - For meters with two decimal places, express ft with two decimal places (e.g., 1.23 m → 4.04 ft) - For 30 cm → in use one decimal place (11.8 in) - For 12 mm → in use two decimal places (0.47 in)

• For ± values and ranges, annotate the corresponding value in the same format and number of decimal places (e.g., ±2 cm (±0.8 in), 1-2 m (3.3-6.6 ft))

• Annotate 「cm精度」 as cm level accuracy (half-inch accuracy)

Please translate the following input into English.

Table of Contents

• Key basics to grasp before reading the PVSyst manual

• Which screen should I check first?

• How should weather data be selected?

• How precisely should azimuth and inclination angles be entered?

• What should be checked in the module and inverter settings?

• At what stage should the effects of shadows be considered?

• Is it acceptable to leave the loss setting at its default value?

• What should you suspect when power generation is lower than expected?

• In what order should the report results be read?

• Which metrics should be examined when comparing design proposals?

• How should a manual be organized to ensure it continues to be used in daily operations?

• Approach to Connecting the PVSyst Manual with On-Site Decision Making

Basics to Know Before Reading the PVSyst Manual

Many people searching for a PVSyst manual are not merely looking for step-by-step instructions. In practice, as they proceed with designing photovoltaic systems, simulating energy yield, evaluating losses, performing shading analysis, and reviewing reports, they want to resolve practical uncertainties such as “Is this input correct?”, “Am I interpreting the results correctly?”, and “What should I change to improve the energy yield?”.

PVSyst is not just a simple input form for calculating power generation; it is a tool that runs simulations by combining multiple conditions such as meteorological conditions, installation conditions, equipment specifications, wiring, temperature, shading, and system configuration. Therefore, when reading the manual, it is important to read from the perspective of “what does this screen determine,” “where do the input values affect the results,” and “which indicators should be checked later,” rather than merely following the on‑screen operations.

A common mistake is concentrating only on filling in the items displayed on the screen from top to bottom. At first glance it may look like progress is being made, but if you enter data without understanding the meaning of the assumptions, you will be unable to judge whether the figures in the result report are reasonable. In particular, weather data, azimuth, tilt angle, module specifications, inverter capacity, shading conditions, and loss settings all have a major impact on the generation results, so these are the parts you should check carefully in the manual.

This article organizes 10 questions that people reading the PVSyst manual tend to get stuck on in practice. Focusing on practical approaches usable in actual review work, it explains topics ranging from issues beginners commonly struggle with at first to comparing design proposals and checking reports.

1. Which screen should you check first

When you first begin reading the PVSyst manual, a common source of confusion is deciding which screen to start with. Because there are many features, attempting to understand everything at once makes it difficult to see how the input fields relate to each other, and you can easily become confused.

The first thing to check is the part that determines the overall conditions of the project. In this section, organize the target site, meteorological data, system type, installation method, and the basic scale of the power generation equipment. Because these items will become the assumptions that influence subsequent simulation results, it is important to establish the overall framework at the outset.

Next, what I want to check is the screen related to system design. The module type, inverter selection, the number of modules in series, the number in parallel, the capacity ratio, etc., affect not only the power generation but also clipping, the voltage range, and the feasibility of the system. When reading the manual, rather than simply "where to input," it's easier to understand if you focus on "what will happen if this setting is too large or too small."

Furthermore, it is effective to review shading analysis and loss settings once the basic design is reasonably established. If you get into detailed loss items from the start, it becomes difficult to grasp the overall flow. Read the manual in the order of project conditions first, then system configuration, then shading and losses, and finally the results report — following this sequence makes it easier to make practical decisions.

Especially for beginners, it is not necessary to learn all the features from the outset. It is important to distinguish between the screens you will definitely use on a project and the screens you will check as needed. The initial goal is not to master every operation perfectly, but to understand the relationship between the simulation’s assumptions and its results.

2. How should meteorological data be selected?

One of the questions often checked in the PVSyst manual is how to choose meteorological data. In photovoltaic simulations, conditions such as solar irradiance, ambient temperature, and wind speed greatly affect power output. Therefore, selecting meteorological data is not a mere initial setting but an important process that determines the reliability of the simulation.

When selecting meteorological data, first check the distance to the target site. Using data from a location far from the power plant’s installation site can cause the solar radiation and temperature conditions to differ from actual conditions. This is especially true in mountainous areas, coastal areas, basins, and snow-prone regions, where meteorological conditions can vary even between nearby sites. Therefore, when consulting the manual, you should confirm not only the method for loading data but also the rationale for site selection.

Next, what matters is the period and type of the data. Whether you use representative-year data, measured data, or incorporate external data will change how the results are positioned. When used for project feasibility assessments, data that reflect average trends are often used so as not to be overly influenced by unusual weather conditions in a single year. On the other hand, when comparing against the actual performance of existing equipment, it is necessary to use data that are close to the measured conditions for the target period.

A common misconception about meteorological data is to assume, "If the data can be loaded, it's fine to use it as is." In reality, unless you check the location, period, solar radiation components, missing values, units, time zones, etc., you cannot determine whether differences in power generation are due to design conditions or to the meteorological data.

When reading the PVSyst manual, it is useful in practice to check not only the procedures for handling meteorological data but also how those procedures are reflected in the results report. In particular, if the energy production is higher or lower than expected, it is important to verify whether the assumptions about the meteorological data are reasonable before reviewing equipment settings or loss settings.

3. How precisely should the azimuth and tilt angles be entered?

Azimuth and tilt angles are aspects that beginners reading the PVSyst manual often trip over. Because the orientation and tilt of solar panels directly affect how they receive solar radiation, they are critically important in power generation simulations. However, how precisely these values need to be entered depends on the project's purpose and the stage of design.

During the preliminary assessment, approximate power generation is sometimes estimated using representative azimuth and tilt angles. For example, for roof-mounted projects they are set based on the roof orientation and pitch, and for ground-mounted projects they are set based on the racking plan. At this stage, comparing multiple options to understand trends is prioritized over focusing on small errors.

On the other hand, at stages closer to detailed design and feasibility assessment, the accuracy of azimuth and tilt angles becomes important. When a roof has multiple surfaces, lumping south-facing, east–west-facing, and differently pitched surfaces together can lead to discrepancies with the actual power generation characteristics. In particular, for roofs that include east–west surfaces or installations split into multiple orientations, it is necessary to consider conditions separately for each array.

A common question is whether a small difference in angle can cause a large change in the results. In general, a difference of a few degrees does not necessarily lead to a large change immediately, but the impact varies depending on the location, season, shading conditions, and mounting method. The important thing is not mechanically increasing the precision of the input angle itself, but how well it represents the actual installation conditions.

When consulting the PVSyst manual, you must understand the definitions of azimuth and tilt angles. In particular, misunderstandings about which direction is used as the reference for angles, how the east-west sign convention is handled, or whether the tilt is measured from the horizontal plane can lead to calculations being performed with an unintended orientation. If you are unsure whether input values are correct, it is important to check orientation consistency on the results screen or in the layout display.

4. What to check in module and inverter settings

In the PVSyst manual, the module and inverter settings are the areas that particularly require practical verification. Because this is the heart of the power generation system, any errors in entering specifications will reduce the overall reliability of the simulation results.

The first things to check are the module’s rated output, voltage, current, temperature coefficients, and other specifications. Even when selecting data that’s already registered, you need to confirm it matches the model you plan to use. Choosing a similar model by mistake can result in different rated capacity and temperature characteristics, which may cause discrepancies in estimated power generation and loss assessments.

Next, verify the inverter's capacity and input range. An inverter should not be chosen solely to match the total capacity. You need to consider the voltage range determined by the number of modules in series, the maximum input current, the MPPT configuration, the oversizing ratio, the occurrence of clipping, and so on. The PVSyst manual may display warnings or inconsistencies, but the absence of warnings does not necessarily mean the design is optimal.

A common question is, "How large a ratio of DC capacity to AC capacity is acceptable?" This depends on the project's policy, local solar irradiance conditions, inverter specifications, feed-in conditions, self-consumption conditions, and so on. Oversizing can increase annual energy production, but it may also increase clipping losses at peak times. Therefore, rather than seeking a single correct answer, it is important to compare multiple capacity scenarios and assess the balance between energy generation, losses, and economics.

Also, checking the string configuration is essential. If the number of series-connected modules is too low, the operating voltage will approach the lower limit, and if the number is too high, the open-circuit voltage at low temperatures may exceed the upper limit. When reading the manual, it is important to understand not only the meaning of the input fields but also what the errors and warnings indicate.

Module and inverter settings are not only for calculating energy production; they are also a step in verifying the feasibility of the design. Even if the results look promising, they cannot be used in practice if the electrical conditions are not realistic. When using the PVSyst manual, it is necessary to check not only the energy production figures but also whether the system is reasonable as a whole.

5. At what stage should the effects of shadows be considered?

Shade analysis is a topic that many people want to know more about in the PVSyst manual. In photovoltaic power generation, shadows from surrounding buildings, trees, mountains, rows of mounting racks, rooftop equipment, and so on affect power output. Especially for rooftop installations, narrow sites, and projects with many surrounding obstacles, the handling of shadows has a large impact on the results.

It is advisable to verify the impact of shading as early as possible. If shading issues are discovered after the design is finalized, layout changes, capacity adjustments, or a reassessment of the installation area may be necessary. Even at the conceptual design stage, identifying areas that will clearly be shaded can reduce rework in later stages.

However, you don't need to build overly detailed 3D models at the initial stage. First, organize the main obstacles that cause shading and identify which times of day and seasons are most likely to have problematic shading. From there, it is efficient to prioritize and detail the conditions that are likely to affect power generation.

A common question is, "When I include shading analysis the energy production drops significantly— is this correct?" In this case, you should first verify the shadow model's dimensions, position, height, orientation, and its relationship to the array. If an obstacle's position is misaligned or the units for height are incorrect, the shading losses can be overestimated compared with reality.

Also, in shadow assessment it is important to distinguish between distant shadows and nearby shadows. The modeling approach differs for distant shadows such as terrain and mountains versus nearby shadows like buildings and rows of mounting structures. When reading the PVSyst manual, clarifying which type of shadow is handled by which feature will help reduce configuration errors.

Shading analysis is not simply an exercise in identifying factors that reduce power output. It is a process for assessing the suitability of the installation area, improving module placement, and identifying in advance the risks that could affect project viability. When shading losses are shown in the results report, it is important not to look only at that number but to check which shadows are affecting the system and to what extent.

6. Is it okay to keep the loss settings at their default values?

In the PVSyst manual, one question that beginners often struggle with is whether it is acceptable to leave the loss settings at their default values. The loss settings include various items such as temperature loss, wiring loss, mismatch loss, soiling loss, inverter loss, degradation, reflection, and auxiliary consumption. These are necessary to estimate energy production realistically, but if the basis for the chosen settings is unclear, it becomes difficult to explain the results.

Initial values are convenient for preliminary assessments and operation checks. However, for simulations used in actual practice, they need to be verified against the project's conditions. For example, in areas with heavy dust, snowy regions, areas prone to salt damage, or equipment that is infrequently maintained, losses due to soiling and environmental conditions may differ from standard assumptions.

Wiring losses are also important. Losses vary depending on cable length, cross-sectional area, current conditions, and voltage conditions. In the preliminary stage you may use assumed values, but as you move closer to detailed design you need to verify them based on the wiring plan. When reading manuals, be aware not only of the screen where you enter the loss rate but also of which conditions are used to determine that value.

Temperature losses also vary depending on the mounting method. Modules mounted flush to the roof, modules on ventilated racking, and ground-mounted modules show different module temperature rise characteristics. In high-temperature regions, temperature losses tend to be larger, so it is important to check them together with meteorological data and the mounting method.

A common mistake is entering loss items in detail but not recording the rationale. If, when you later need to explain the results, you don't know why you chose that loss rate, the simulation's reliability will decrease. When using the PVSyst manual, it is important to manage input values together with their justifications.

Loss settings are not an item solely for making power generation appear conservative. They are adjustments to reflect actual equipment conditions and to avoid overestimation or underestimation. Even when using default values, you should confirm that those values are appropriate for the project conditions and review them as necessary.

7. What should you suspect when power generation is lower than expected?

Among those who consult the PVSyst manual, many find that the simulated energy production is lower than expected and want to investigate the cause. In such cases, rather than changing settings at random, it is important to establish an order and check things systematically.

The first thing to check is the meteorological data. Confirm that you have not selected data with low solar irradiance for the target site, that the site location is not shifted, and that the data’s units and time period match your expectations. If the meteorological conditions differ, no matter how much you revise the equipment settings, the difference in power generation will not be resolved.

Next, check the equipment capacity and system configuration. Verify that the module capacity, inverter capacity, number of modules in series, number of parallel strings, and number of arrays match your expectations. If the capacity you intended to enter differs from the capacity shown in the report, there may be a mistake in the configuration somewhere.

The next items to check are the azimuth and the tilt angle. If the east–west sign is incorrect or the roof surface orientation is set the opposite way, the generated power can be lower than expected. Especially when you are not yet familiar with the definition of azimuth, it is important to confirm not only the numerical values but also the direction shown in diagrams.

Shadow losses can also be a major cause. If the height, position, or distance of buildings or obstacles are entered incorrectly, excessive shading may be calculated. When shadow losses are large, check in which season and at what times of day the shading occurs, and review whether the model accurately reflects reality.

Furthermore, you need to check for excessive input of loss settings. If soiling loss, wiring loss, mismatch loss, and the like are entered too conservatively, the power output can drop substantially. Of course, conservative settings may be necessary depending on actual conditions, but stacking large loss rates without justification will make the results excessively low.

If you feel the power generation is low, rather than simply thinking "which setting should I raise?", it is important to check, in order, the input conditions, physical conditions, loss conditions, and result indicators. The PVSyst manual can be used not only to verify how to operate each item but also to organize the steps for isolating the causes.

8. In what order should the report results be read?

After completing a simulation using the PVSyst manual, many people are unsure how to read the report results. Because the report presents many numbers and graphs, some people may end up checking only the annual energy production without knowing where to look.

The first thing I check is the system assumptions. I verify that the site location, meteorological data, system capacity, modules, inverters, azimuth, tilt angle, and so on match the assumed parameters. If there are errors here, examining the generation or loss figures is meaningless. When reviewing a report, it is standard practice to check the assumptions before the results.

Next, check the annual generation and specific yield. Annual generation indicates the total generation of the entire installation, but when comparing options with different installed capacities, you also need to look at generation per unit of capacity. Since a simple total generation can make options with larger capacity appear more favorable, it is important to use metrics appropriate to the purpose of the comparison.

Next, check the breakdown of losses. By seeing at which stage and to what extent losses occur, you can identify opportunities for improvement. In the process of converting solar irradiance to module output, inverter output, and grid output, losses such as temperature, shading, wiring, inverter, and clipping accumulate. Rather than looking only at energy generation, tracing the flow of losses is more likely to lead to design improvements.

Monthly power generation is also important. Annual values alone do not reveal seasonal trends. If generation does not increase in summer, temperature losses may be the cause; if there is a large drop in winter, factors such as irradiance conditions, snow cover, or shading may be involved. By looking at monthly results, you can determine when problems are occurring.

When reading report results, it is important not to judge based on a single number. You can assess the validity of the results by checking a combination of annual energy production, specific yield, loss breakdown, monthly trends, warning messages, and assumptions. When reading the PVSyst manual, it is effective to be aware of what each item in the report means and what practical decisions it can inform.

9. Which metrics should you look at when comparing design proposals?

One of the things practitioners want to learn from the PVSyst manual is how to compare multiple design options. In solar power system design there are various choices—module capacity, inverter capacity, tilt angle, azimuth, layout, shading mitigation, wiring plan, and so on. Simulation is an important means of comparing those options.

When comparing design proposals, the first thing to look at is the annual energy production. However, judging which is better based solely on annual production is risky. Because proposals with larger capacity tend to produce more energy, you also need to consider the energy produced per unit of capacity and its relationship to equipment costs.

The next important point is the breakdown of losses. If a design’s energy output is low, the remedy depends on whether the cause is shading, temperature, inverter clipping, or wiring. If shading losses are large, reconsider the layout; if clipping is large, review inverter capacity and the oversizing ratio; if wiring losses are large, revisit the cable plan.

Also, monthly power generation characteristics should be compared. Even if annual generation is similar, seasonal generation patterns can differ. For self-consumption projects, it is important whether generation can occur during the time periods or seasons of high demand. It is important to check not only the simple annual generation amount but also whether it matches demand and aligns with the operational objectives.

When comparing design proposals, it is also important not to be swayed by overly small differences. Simulations have assumptions, and results vary depending on meteorological data and loss settings. Rather than deciding based only on slight differences in power generation, you should judge proposals by also considering constructability, maintainability, room for future expansion, shading risk, and the stability of the equipment configuration.

When using the PVSyst manual, it is important to both understand the comparison features and how to read the results reports, and to decide on the comparison criteria in advance. The metrics you should look at change depending on whether you want to maximize power generation, minimize upfront costs, increase the self-consumption rate, or avoid the effects of shading.

In practice, the option with the highest power output is not always the optimal one. It is important to choose an option that matches the objectives by balancing power generation, losses, cost, constructability, and operability.

10. How should manuals be organized to ensure continued use in practice?

The PVSyst manual is not something to read once and be done with. Because conditions vary from project to project, it is important to organize it so that you can quickly check the necessary items when needed. In particular, when multiple people are carrying out design or simulations, relying solely on individual understanding can lead to inconsistencies in input conditions and decision criteria.

First, what you should organize are the items to check at the start of a project. By compiling the items that must be checked each time—such as the target site, meteorological data, equipment capacity, installation method, azimuth, tilt angle, equipment used, and layout conditions—you can prevent omissions in data entry. If you align the relevant sections of the manual with your internal checklist items, it will be easier to maintain quality even when personnel change.

Next, we will organize the commonly used parameter values and their rationale. Loss rates, temperature conditions, wiring conditions, assumptions about soiling, and the treatment of shading need to be decided on a per-project basis, but starting from scratch each time takes time. By organizing the approaches used in past projects and standard setting policies, you can examine them more efficiently.

Also, it's useful to keep a record of how you handled common errors and warnings. When a warning appears during PVSyst operation, accumulating past responses instead of looking each one up in the manual speeds up isolating the cause. However, do not ignore warnings mechanically; it's important to document why you determined they were not a problem or how you corrected them.

Standardizing the procedure for reviewing reports also stabilizes the quality of deliverables. By deciding the order in which to check items such as assumptions, annual energy production, monthly energy production, breakdown of losses, shading losses, clipping, and warning messages, you can reduce important oversights.

To continue using the PVSyst manual in practical work, you need not only to memorize the operating procedures but also to embed them into your company's or each project's evaluation workflow. The manual provides the foundation for checking the basics, and in practice it is important to build on it by adding project-specific decision criteria and verification records.

Approach to Linking the PVSyst Manual to On-site Decision-Making

When the frequently asked questions in the PVSyst manual are organized into 10 items, a common point that emerges is that knowing how to operate the software alone is not sufficient to reach practical judgments. Simulations produce results according to the input conditions. However, whether those results are reasonable or can be adopted as a design proposal cannot be judged without understanding the meaning of the input conditions and the ability to interpret the results.

The purpose of using PVSyst is not simply to produce a number for energy production. It is to confirm the validity of the system planning, understand the risks of shading and losses, compare multiple design options, and assess commercial viability and operability. Therefore, when reading the manual you should pay attention not only to where items are on the screen and which buttons to press, but also to "what this item is meant to evaluate" and "which parts of the results will be affected if this value changes."

In practical work, it is particularly important to clarify the assumptions. If any of the meteorological data, installation angle, equipment specifications, loss settings, or shading conditions remain ambiguous, it becomes difficult to explain the simulation results. Conversely, if the assumptions and their rationale are well organized, it is easier to respond to questions about the results.

Also, it is important not to judge solely by whether the energy production is high or low. Even if the energy production is high, if it comes from an excessive installed capacity, unrealistic loss assumptions, or conditions that ignore shading, the results will be difficult to use in practice. Even if the energy production is low, if it reflects conservative assumptions, it can still be useful for business decision-making.

To use the PVSyst manual effectively, you also need to adjust which sections you read according to the project stage. In the preliminary assessment, emphasize the overall energy yield and comparisons between design proposals; in the detailed design phase, closely verify equipment specifications, loss settings, and shading conditions. At the reporting stage, organize the material so you can explain the report’s assumptions and the breakdown of losses.

By addressing common questions one by one, PVSyst becomes easier to use not merely as an analysis tool but as an investigation tool that supports design decisions. The purpose of reading the manual is not to memorize every feature. Rather, it is to consult the right sections when needed, understand the relationship between input conditions and results, and connect that understanding to on-site and design decisions.

In solar PV projects, even conditions that appear similar can require different optimal settings depending on the location, roof shape, topography, surrounding environment, equipment configuration, and operational policy. For that reason, when using the PVSyst manual it is important to follow standard procedures while carefully verifying the assumptions for each project.

Ultimately, it is important to aim to be able to explain the input values, the rationale for settings, the simulation results, and the design decisions as a single, continuous flow. Once you reach that state, the PVSyst manual becomes more than just an operational guide and serves as a practical support for improving the quality of generation simulations.