Five perspectives to avoid failure in PVSyst string design

Table of contents

• Why string design becomes important in PVSyst

• Perspective 1: Treat string design as a prerequisite for energy yield calculation

• Perspective 2: View consistency between module conditions and PCS conditions

• Perspective 3: Consider array layout and how shadows are received

• Perspective 4: Check whether groupings are consistent under the same conditions

• Perspective 5: Verify validity by reverse-calculating from the results

• How to apply PVSyst string design thinking in practice

Why string design becomes important in PVSyst

When performing energy yield simulations with PVSyst, a factor that practitioners tend to overlook is the weight of string design. People often focus on module selection, azimuth, tilt, and loss settings, while string design tends to be treated as a behind-the-scenes task to ensure electrical consistency. In reality, however, string design is a very important design element that influences not only the appearance of energy yield but also the combination with the PCS, how shadows affect performance, how arrays are grouped, and even ease of maintenance.

In practice, there are times when people think it is sufficient as long as the strings "work." Indeed, if the calculations pass in PVSyst, a plan may superficially appear to be valid. But being valid and being practically usable are not the same. For example, even if there is no numerical issue, if rows that receive different shading are put into the same grouping, or if the way arrays are divided is too complex for construction or maintenance, a major revision may be required later. PVSyst can present results neatly, but if the assumptions are weak, that weakness can remain hidden as the project proceeds.

Also, string design should not be considered in isolation. Only when module dimensions and outputs, PCS input conditions, site geometry, array orientations, shadow distribution, and inspection routes are combined does a natural design emerge. In other words, string design is not just an electrical design issue; it is strongly linked to layout design. Therefore, when thinking about string design in PVSyst, it is necessary not simply to determine series and parallel counts, but to confirm whether that design is appropriate for the entire project.

Moreover, in internal comparisons and report writing, the approach to string design affects the persuasiveness of the numbers. Even if you try to explain why energy yield is high, if the assumptions about string design are vague, the basis for the results will be weak. Conversely, being able to explain why you chose that grouping or that series count increases confidence in the whole proposal. To master PVSyst in practice, it is important to treat string design not as a mere connection issue but as a central part that makes the entire system valid.

Below are five perspectives to keep in mind when progressing string design in PVSyst to prevent failures. None of them are particularly difficult concepts, but whether you adopt these perspectives or not will greatly affect both the readability of simulation results and practical usability.

Perspective 1: Treat string design as a prerequisite for energy yield calculation

The first important point is to treat string design not as an afterthought but as a prerequisite for energy yield calculation. In practice, it is common to first check how much can fit on the site, then choose modules and PCS, and finally adjust the strings to match. This approach can work for rough assessments, but if string design is treated as a last adjustment item, the layout and energy yield assumptions you carefully created can later be undermined to achieve electrical consistency.

You should regard string design as a prerequisite because changing series counts or grouping methods alone can alter the relationship with the PCS and how output appears. In other words, strings are not just a wiring method but part of what defines the character of the entire system. Because PVSyst returns results as numbers, it is easy to focus only on the final annual energy yield, but those numbers are shaped by the assumptions made in string design. If you postpone this, comparisons of energy yield and interpretation of losses can become unstable later.

Also, treating string design as a prerequisite changes how you create comparative options. For example, when comparing a module-only change or a PCS-only change, if you do not include string feasibility and grouping as part of the comparison, you will not truly know what difference you are observing. Because PVSyst makes comparisons easy, you must be clear whether you keep string design consistent as a shared assumption or treat it as one of the variables.

As a countermeasure, decide on the general direction of the string design at the same time you determine array and PCS conditions. You don't need to finalize every detail immediately, but having an idea of the expected series counts and grouping approach will greatly reduce later revisions. To avoid failure in PVSyst string design, you need to think of it from the start as part of the system conditions rather than as a final balancing act.

Perspective 2: View consistency between module conditions and PCS conditions

The next important point when considering string design is to check consistency between module conditions and PCS conditions. PVSyst allows you to set modules and PCS separately, but in practice it is insufficient to treat them independently. Because string design connects the two, designing to fit only one side will likely cause issues for the other.

For example, prioritizing module output and dimensions when arranging the array can create difficulties for the PCS input side. Conversely, selecting series counts solely for PCS convenience can lead to poor array cohesion or reduced site efficiency. Even if PVSyst calculations appear valid, such tensions often surface in later practical stages. Therefore, consider string design as the interface between modules and PCS.

When checking consistency, it is important not only to see whether numbers fit but also whether the grouping is natural and not forced. There is a big difference in later usability between a condition that just barely meets requirements and one that naturally fits with some margin. In practice, considering maintenance, fault response, and system partitioning, a little margin and a tidy layout make a large difference. For PVSyst string design, confirm not only mathematical validity but also practical ease of handling.

As a measure, when progressing string design, look at module arrangements and how the PCS will handle them at the same time. Rather than deciding one then forcing the other to conform, iterate between both conditions to confirm a natural configuration. To avoid failure in PVSyst string design, maintain an attitude of checking consistency between module-side logic and PCS-side logic as a single system.

Perspective 3: Consider array layout and how shadows are received

String design is not determined by electrical conditions alone. If you do not consider array layout and how shadows are received, the design can become difficult to use in practice. A common situation in PVSyst is to be reassured because module counts and PCS conditions fit neatly, and then to adopt the string grouping as is. However, if modules that belong to the same string are actually exposed to different shading conditions, a discrepancy arises between how results look in calculations and how the system behaves in practice.

In the field, site shape, slope orientation, aisle planning, and row spacing differences can cause shadow reception to vary even within the same array. If you form strings by prioritizing only electrical grouping in such places, shadow effects and perceived losses can become complex later. While annual energy yield may appear in PVSyst results, it can be hard to explain why certain losses occur. Think of string design as how to create units that can treat shading more homogenously.

Moreover, groupings with inconsistent shading conditions complicate maintenance and fault diagnosis. It becomes difficult to distinguish whether a drop in generation in a specific row is due to shading or a malfunction. In practice, this ambiguity leads to greater burden in troubleshooting and reporting. When designing strings in PVSyst, check not only whether strings are valid but also whether the modules in the same grouping are under similar conditions.

As a countermeasure, when separating strings, confirm array arrangement and shadow behavior and group modules into units with as uniform conditions as possible. You do not need to incorporate perfect detailed shadow simulations everywhere, but at least avoid forcing clearly different rows or sections into the same grouping. To avoid failure in PVSyst string design, it is important to look at both electrical consistency and shading condition consistency simultaneously.

Perspective 4: Check whether groupings are consistent under the same conditions

In string design, it is very important to check whether groupings are consistent under the same conditions. By "conditions" here we do not mean merely the same number of modules. It is necessary to confirm that groupings are similar in terms of installation azimuth, tilt, shading, location on the array, and even ease of maintenance and inspection. PVSyst will proceed with calculations if inputs are consistent, but practical manageability is greatly affected by how the groupings are organized.

Strings that are not uniform in conditions complicate interpretation of simulation results. For example, if a grouping contains sections with subtly different azimuths or tilts, the reason for generation differences becomes ambiguous. If shading differences overlap, it becomes harder to identify where losses originate. Because PVSyst aggregates final results numerically, such variations can remain invisible, but as a design they create systems that are difficult to manage.

In practice, there is often a tendency to prioritize using the entire site and to combine slightly different areas into a single grouping. However, forcing such combinations makes construction, maintenance, and fault response more difficult later. In other words, in string design not only the fit but also how consistently conditions align is part of design quality. If you plan to use PVSyst comparison results in practice, do not neglect the naturalness of these groupings.

As a measure, when cutting strings, consciously divide them into units that can be treated under the same conditions. Do not assume that slight nonuniformity is acceptable just because it is feasible; aim for a configuration you can explain why you grouped it that way. To avoid failure in PVSyst string design, focus on how well conditions align rather than just numerical feasibility.

Perspective 5: Verify validity by reverse-calculating from the results

Finally, an important point is not to stop after inputting the string design, but to verify its validity by reverse-calculating from the results. PVSyst displays results neatly if settings are feasible. As a result, one tends to be reassured by annual energy yield numbers that look acceptable. However, in practice it is essential to review the assumptions that produced those numbers. Because string design can appear valid while still harboring practical issues, reverse-checking via the results is important.

For example, if output limits look larger than expected, losses appear in odd patterns, or differences in energy yield between comparison options are unexpectedly large or small, you should suspect not only PCS or module conditions but also the string design itself. PVSyst returns results based on the assumptions, so any oddity in the results contains hints about which assumptions might be off. Because it is difficult to judge the correctness of string design at input time alone, it is necessary to confirm validity while reviewing the results.

Having a reverse-calculation perspective also improves the quality of comparative simulations. You will be able to explain not only that one option yields more or less energy, but why that is so by tracing back to string design. This is highly effective for internal explanations and report preparation. If the rationale behind the numbers is organized, it becomes easier to explain relationships with equipment selection and array design, increasing confidence in the overall proposal.

As a measure, after running calculations in PVSyst, check not only annual values but also the breakdown of losses, how limits appear, and the differences with comparison options while confirming whether the string design was truly natural. Treat input and result verification as a single workflow to reduce designs that are superficially valid but difficult to handle in practice. To avoid failure in string design, you need a perspective that revisits assumptions from the results as carefully as you prepare the inputs.

How to apply PVSyst string design thinking in practice

What is common to the five perspectives discussed above is not treating string design as a mere connection condition. Treat it as a prerequisite for energy yield calculation, check consistency between modules and PCS, base design on array layout and shading conditions, group under the same conditions, and finally verify validity by reverse-calculating from the results. If you follow this flow, PVSyst string design moves from number-matching to system design that is usable in practice.

For practitioners, the important thing is not to create strings that simply pass calculations. What truly matters is being able to explain why that configuration is appropriate. If the design is natural in terms of energy yield, shading, PCS conditions, array grouping, and maintenance ease, simulation results become easier to use for internal comparisons and design studies. Conversely, prioritizing numbers alone in string design increases the burden of explanation and rework downstream.

Also, to improve the accuracy of string design, do not complete the process only with desk simulations. If site boundaries, slope orientations, aisle planning, shadow distribution, and array cohesion are ambiguous, the way you divide strings tends to drift toward idealized theory. To link PVSyst results to practice, iterate between site understanding and simulation to refine design conditions.

In that sense, when you want to more reliably confirm positions and acquire coordinates on site, using iPhone-mounted GNSS high-precision positioning devices like LRTK is also an effective approach. If you can better organize on-site position information and site conditions, the assumptions for layout and shading in PVSyst string design become clearer. If you can improve desk comparison accuracy with PVSyst and support on-site understanding with LRTK, string design becomes less of a mere connection setting and more of a site-rooted design judgment. Carefully refining string design not only improves the accuracy of energy yield forecasts but also enhances the practical capability to connect desk work and field work.