Five considerations for setting wiring losses in PVSyst

Table of contents

• Why setting wiring losses in PVSyst becomes important

• Consideration 1 Treat wiring loss not as a post-hoc add-on but as a design assumption

• Consideration 2 Separate DC-side and AC-side wiring losses

• Consideration 3 Base settings on the realism of array layout and wiring routes

• Consideration 4 Verify consistency with string configuration and PCS conditions

• Consideration 5 Back-check validity using comparative simulations and result screens

• Perspectives to connect PVSyst wiring loss settings to practical outcomes

Why setting wiring losses in PVSyst becomes important

When running energy production simulations in PVSyst, wiring losses are an unobtrusive item yet an important assumption that affects the credibility of final results. It is easy to focus on items where differences are obvious—module capacity, azimuth, tilt, PCS conditions—but in practice, no matter how well those main parameters are arranged, a loose approach to wiring losses can skew the annual energy production estimate. Because wiring losses are not visually obvious like shading, if you treat the setting lightly it becomes difficult later to trace where discrepancies originated.

This is especially true for large sites or projects where arrays are divided into multiple blocks—there the effect of wiring distances on results cannot be ignored. On paper, two proposals might show the same capacity, azimuth, and tilt, but differences in how wiring is routed or how blocks are divided will change the final loss profile. A common practical approach is to decide array and PCS configurations first, then apply a uniform wiring loss number at the end. That workflow obscures differences in wiring conditions that stem from layout variations and tends to reduce the precision of comparisons.

Also, wiring losses should not be treated simply as a number to minimize. If you set the loss small to make the generation figure look attractive, the number will likely fall when you move to detailed design, undermining internal explanations and decision consistency. Conversely, overestimating losses can prematurely make feasible configuration options look unfavorable. What matters is neither inflating nor deflating the loss, but placing assumptions that are reasonable relative to the actual array layout, block configuration, and wiring routes.

Moreover, carefully setting wiring losses in PVSyst makes it easier to explain comparative proposals. When explaining why one option shows slightly lower annual energy or why another appears advantageous, you will be able to discuss not only device or orientation differences but also the wiring conditions. Being able to show the assumptions behind a generation number is valuable in practice. Treating PVSyst wiring loss settings as part of harmonizing the entire system rather than merely entering a loss number is more practical.

Consideration 1 Treat wiring loss not as a post-hoc add-on but as a design assumption

The first point to grasp when setting wiring losses is not to think of them as an after-the-fact correction added at the end of design. In practice, people tend to decide module counts, PCS capacity, and array layout first and then add wiring losses as a final step. While that sequence looks natural, if you want meaningful comparisons in PVSyst it is better to consider wiring losses as part of the design assumptions from the start. This is because wiring losses are determined together with how arrays are partitioned, string configuration, walkway placement, and PCS locations.

For example, on the same site, an option that concentrates arrays versus an option that divides them into multiple blocks will change wiring conditions. Although centralized layouts may look easier to manage, they can run into problems because of walkways or maintenance constraints; conversely, even if a distributed layout seems natural, accumulated wiring distances may become significant. Processing these differences after the fact with a uniform loss coefficient makes it easy to miss practical differences arising from layout choices. In short, wiring losses should not be something added after configurations are decided; they should be considered together when comparing configurations.

Treating wiring loss as a retrofit correction also causes difficulty in internal explanations. If an option that looked superior in comparison flips ranking once wiring losses are reflected, the meaning of the initial comparison is weakened. If, instead, you compare from the outset including wiring conditions, you can consistently explain which option is truly a natural design. PVSyst is a tool for lining up multiple options neatly, but if wiring losses are not included in those comparisons, the results have limited value for practical decision-making.

A practical countermeasure is to clarify, from the stage you start creating scenarios in PVSyst, how much emphasis wiring losses should have for the project. If the site is compact and PCS positions are almost fixed, wiring loss differences may be small. If the site is wide, arrays are split into multiple blocks, or PCS placement moves between schemes, wiring losses should be treated near the center of your comparisons from the start. Thinking of wiring losses as part of the design scenario rather than something to add later is fundamental to producing simulations in PVSyst that are robust for practical use.

Consideration 2 Separate DC-side and AC-side wiring losses

The next important point when setting wiring losses is to separate DC-side and AC-side losses. In practice, there is a tendency to treat wiring loss as a single combined number, but PVSyst differentiates depending on where losses occur; what matters is whether you have organized which side you are accounting for. The DC side is strongly related to how modules connect to the PCS, while the AC side relates to how power is taken from the PCS onwards and how blocks are aggregated. Although the wiring is continuous, the nature of losses differs between these two sides.

For example, DC-side losses depend on string configuration, the degree of array dispersion, and how each block is grouped. If arrays are finely divided or the routing to the PCS is complex, effects will show both numerically and in design practicality. On the other hand, AC-side losses tie to PCS placement, how the entire site is consolidated, and electrical aggregation strategy. Combining these into a single loss obscures where improvements are possible and makes it harder to explain the reasons for differences between comparative options.

Distinguishing whether differences arise on the DC or AC side is also important for identifying where to adjust the design. If one option shows slightly lower annual energy, whether that arises from DC-side grouping or PCS-side organization changes what you should modify. If you only view it as a single wiring loss, it becomes difficult to decide whether to change array layout or PCS positions. To feed PVSyst results back into design, this separation is necessary.

As a practical step, when inputting and checking wiring losses, mentally separate what you expect on the DC side from what you expect on the AC side. You do not need to subdivide everything rigorously, but being aware of which side is likely responsible for issues will change how you read comparison results. When setting wiring losses in PVSyst, treat wiring not as a single line but as conditions that mean different things for the system’s front and back halves.

Consideration 3 Base settings on the realism of array layout and wiring routes

To set wiring losses practically, you need to base them on the realism of array layout and wiring routes. When calculations in PVSyst are rushed, the workflow tends to be: decide module numbers, azimuth, tilt, and PCS conditions, then place an average figure for wiring losses. In practice, however, wiring routes are decided together with array layout, so if the layout changes, the approach to losses changes. The more you separate layout from wiring, the more the results become desk-based.

For example, when a site is large and divided into multiple array blocks, wiring conditions change depending on how blocks are grouped. Even small shifts in arrays due to edge setbacks, walkways, or slope avoidance will change how wiring is terminated. Conversely, even arrays that look neatly aligned may force awkward wiring routes due to maintenance paths or existing equipment. When setting wiring losses in PVSyst, it is important not to rely excessively on uniform values that ignore such realistic routing constraints.

Considering wiring route realism also changes how you judge the merits of options. One option may show slightly higher annual energy but require complex wiring routes that are hard to trace during maintenance. Another may have a minor disadvantage in generation but have well-grouped array blocks that make wiring tidier and more practical. PVSyst highlights final energy differences, but practical strengths also lie in whether the layout and wiring routes naturally align.

As a practice, before setting the loss factor, envision roughly how wiring routes might run for the option. You do not need detailed construction drawings, but considering array grouping, PCS locations, and walkway conditions to see whether wiring would naturally fit will significantly adjust your sense of an appropriate loss factor. When setting wiring losses in PVSyst, don’t decide the number first—derive the number’s validity from the realism of the routes.

Consideration 4 Verify consistency with string configuration and PCS conditions

When setting wiring losses, always confirm consistency with string configuration and PCS conditions. Wiring loss does not exist in isolation; it gains meaning together with module grouping, how strings are split, and how PCS receives power. PVSyst lets you input equipment and configurations separately, but in practice what matters is whether those elements form a coherent system, and wiring losses should be read as part of that whole.

For example, in schemes where array blocks are finely divided and string groupings are complex, not only do wiring distances increase, but the difficulty of organizing the whole configuration will also reflect in how you read losses. Conversely, if arrays and strings are grouped naturally and the PCS relationship is straightforward, it is easier to place realistic wiring loss assumptions. When differences appear in PVSyst comparisons, you need to see whether they are merely loss differences or differences in the coherence of the configuration; checking this consistency is necessary.

The relationship with PCS conditions is also important. Changing PCS placement or who each PCS serves alters impressions of AC-side wiring and can affect DC-side aggregation. In one option the PCS reception may be straightforward and wiring losses look modest; in another, generation may be slightly higher but organizing around PCS is difficult, and you may need to assume stronger wiring losses. Choosing practical options in PVSyst requires comparing not just equipment and wiring separately but the naturalness of how the system elements group together.

As a practical step, after setting wiring losses, check whether the string groupings and PCS conditions feel consistent. Don’t stop at the numbers—ask whether this loss factor is natural for this configuration. That single re-evaluation significantly improves comparison quality. Correctly setting wiring losses in PVSyst requires confirming wiring not as an independent loss but within the consistency of the overall system configuration.

Consideration 5 Back-check validity using comparative simulations and result screens

Finally, it is important to back-check wiring loss validity using comparative simulations and the result screens. PVSyst produces results based on the input loss factors, and tidy-looking numbers are easy to accept. In practice, however, you must confirm whether those loss factors were truly appropriate by examining differences in results, annual values, and the relative merits of configuration options. Loss factors are not just input values; they should be re-evaluated through the results.

For example, if two options that should not diverge much based on layout or equipment show a large annual production gap, it may indicate that wiring losses have been set too aggressively. Conversely, if an option with a highly dispersed array shows too small a difference, wiring losses may have been estimated too optimistically. PVSyst makes comparisons easy, so use these inconsistencies as starting points to revise loss factors. In practice, the key is not to fix the numbers once entered.

Using comparative scenarios clarifies the meaning of loss factors. When you change only the layout with the same equipment, is the observed difference in line with expectations? When you change PCS placement, does the change in wiring loss estimate match the observed difference? Repeating these checks organizes the validity of the loss factors. PVSyst is a tool to refine input assumptions via comparative cases, so you must return to assumptions after seeing results.

As a practical step, when reviewing PVSyst results, always look not only at annual energy but also at the magnitude of differences between scenarios and whether those differences match your design intuition. If results feel unnatural, question not only modules and PCS but also how wiring losses were set. Practical competence in setting wiring losses is less about entering numbers and more about the ability to re-evaluate their validity from the results.

Perspectives to connect PVSyst wiring loss settings to practical outcomes

What ties the five considerations together is not treating wiring losses as mere correction values. Treat them as design assumptions, separate DC and AC sides, base them on the realism of array layout and routing, verify consistency with string configuration and PCS conditions, and finally back-check using comparative simulations and result screens. If you follow this sequence, setting wiring losses in PVSyst becomes not a number to reduce predicted energy but a practical condition to verify the overall system’s validity.

For practitioners, the goal is not to set loss coefficients that make energy look as high as possible. The valuable skill is being able to explain why you expect that level of loss for a particular site, layout, and equipment configuration. If your approach to wiring loss is organized, the differences between options become easier to explain and internal decision-making and design adjustments proceed more smoothly. If you prioritize appearance and underestimate losses, later stages are more likely to reveal inconsistencies.

Also, improving wiring loss accuracy requires not completing the process with desk-based simulation alone. If site boundaries, walkways, slopes, existing equipment, and how array blocks group are unclear, assumptions about wiring routes will be vague. To make PVSyst results truly actionable, you need to iterate between field understanding and simulation to determine what level of wiring loss is natural. Wiring losses are both a calculated figure and a reflection of on-site routing practices.

In that sense, when you need to make on-site position checks or obtain more reliable coordinates, it is natural to consider using iPhone-mounted high-precision GNSS positioning devices such as LRTK. If on-site position information and site conditions are easier to organize, the assumptions about array layout and walkway conditions used to set wiring losses in PVSyst become clearer. Raising the desk-based comparison accuracy with PVSyst while supporting field accuracy with LRTK turns wiring loss settings from mere loss inputs into field-rooted design judgments. Treating wiring losses carefully not only improves the precision of energy production forecasts but also enhances the practical capability that connects desk-based work with on-site reality.