Back to Blog
solar technology14 min read

Solar Backtracking: Single-Axis Tracker Algorithm

Solar backtracking stops single-axis tracker rows shading each other. See the angle math, GCR trade-offs, slope-aware variants and how to verify settings.

Keyur Rakholiya

Written by

Keyur Rakholiya

CEO & Co-Founder · SurgePV

Rainer Neumann

Edited by

Rainer Neumann

Editorial contributor · SurgePV

Published ·Updated

Answer

Solar backtracking is a single-axis tracker control mode that flattens row angles at low sun so rows do not shade each other. It gives up some direct irradiance to avoid string mismatch loss. PVsyst says a near-shading loss of about 2 to 3% typically remains, and the benefit depends on GCR, terrain and controller settings.

Single-axis trackers now dominate new utility-scale solar capacity. A horizontal single-axis tracker (HSAT) raises annual yield over fixed tilt, by an amount that depends on the site, especially at high-direct normal irradiance locations. But that gain only holds if the rows avoid shading each other during the long morning and evening shoulders. That is where solar backtracking comes in.

Backtracking tilts single-axis tracker rows away from their ideal sun-facing angle during early morning and late afternoon to avoid inter-row shading. It trades a small cosine-angle loss for the larger electrical mismatch loss that partial shading would cause.

This guide explains the algorithm from first principles: the geometry of inter-row shading, the energy trade-off between perfect tracking and backtracking, and standard versus slope-aware implementations. It also covers how GCR drives the backtracking threshold, why real terrain breaks simple models, and how to verify backtracking in your design tools. For the broader tracker decision, see our tracker vs fixed tilt comparison.

Last updated: November 2026

In this guide:

  • Why backtracking exists: the inter-row shading problem
  • How the backtracking angle is calculated from row geometry
  • Backtracking vs standard tracking: the energy tradeoff
  • Standard, slope-aware, 3D, and advanced backtracking algorithms
  • How GCR and row spacing set the backtracking threshold
  • Real-site effects: terrain, bifacial modules, and controller calibration
  • Suboptimal backtracking losses and how to avoid them
  • How to verify backtracking settings in PVsyst and field SCADA

Check row spacing before the layout is final

SurgePV supports array layout, shading analysis and energy-yield modeling, so you can test spacing options early. Ask about your tracker setup in the demo.

Book a Demo

Checking cost first? See the SurgePV pricing page.


Solar Backtracking: What It Is and Why It Exists

A single-axis tracker rotates rows of PV modules around a horizontal north-south axis. Through the day the row tilts east in the morning, flattens at solar noon, and tilts west in the afternoon. The goal is to keep the module surface as close as possible to perpendicular to the sun vector, minimising the cosine loss that plagues fixed-tilt arrays.

The problem appears at low sun angles. For illustration, take a low morning sun, only 10 to 20° above the eastern horizon. If a tracker row tilts steeply east to face it, its long shadow falls across the row behind. The shaded modules receive only diffuse light. In a series-wired string, the current through the whole string is limited by the weakest module, so a small shaded band on a few modules can pull down the whole string’s output.

Backtracking solves this by deliberately not tracking the sun during those hours. Instead of tilting steeply east, the controller tilts the row to a shallower angle, for example half as steep in this illustration. That keeps the shadow from touching the next row. The modules receive less direct irradiance than they would at the ideal angle, but they avoid the disproportionate loss from partial shading.

This behaviour is not a failure of tracking. It is an optimisation. The controller knows the sun position from GPS and astronomical algorithms. It also knows the row pitch, module width, and tracker height. With that geometry, it computes the maximum tilt angle that keeps every row unshaded. When the ideal tracking angle exceeds that threshold, the tracker switches from normal tracking to backtracking mode.

Pro Tip

Backtracking does not increase the total solar energy intercepted by the field. It only changes how that energy is distributed across modules. The benefit comes from avoiding electrical mismatch losses that would otherwise destroy string output during shaded hours.


How Backtracking Works: The Geometry

The backtracking angle is a geometric problem. Imagine two adjacent tracker rows aligned north-south. Each row has a collector width (W) and the centre-to-centre row spacing is (P). The Ground Coverage Ratio is (GCR = W / P). The pvlib documentation defines it the same way, as array area to ground area.

When the sun is low in the east, the front row casts a shadow toward the west. The length of the shadow depends on the sun’s elevation angle and the tracker tilt. The backtracking algorithm finds the tracker tilt angle (\beta_B). At this angle, the shadow from the top edge of the front row just reaches the bottom edge of the rear row.

For a horizontal single-axis tracker on flat ground, the relationship between solar transversal angle (\theta_T) and backtracking correction (\theta_c) is:

θ_c = -sign(θ_T) × arccos( |cos(θ_T)| / (GCR × cos β_c) )

where (\beta_c) is the cross-axis slope angle. The ratio inside the arccos is capped at 1, so there is no correction near noon, when the rows do not shade each other. On flat ground, (\beta_c = 0) and the equation reduces to the familiar flat-terrain form. The tracker then operates at:

θ_B = θ_T + θ_c

The result is a rotation curve that follows the sun closely near noon but flattens out in the morning and evening. If you plot tracker angle against time, the backtracking curve looks like the normal tracking curve with its early and late shoulders clipped off.

NREL’s slope-aware backtracking study provides the derivation for terrain-corrected versions of these equations. The flat-ground form assumes level ground and uniform row heights, so check how far your site departs from that. The same NREL report and Lorenzo and colleagues’ 2011 paper are the references cited in the pvlib singleaxis documentation.


Backtracking vs Standard Tracking: The Energy Tradeoff

Without backtracking, a tracker follows the sun continuously. At low sun angles, rows shade each other. The shaded cells drop out, bypass diodes activate, and string current collapses. The energy loss is far larger than the shaded area alone would suggest because of the electrical behaviour of series strings.

With backtracking, the tracker accepts a small orientation penalty. The modules are no longer perfectly perpendicular to the sun beam, so direct irradiance falls by the cosine of the angle error. But every module in the row sees some direct light, so string current stays high.

The net effect is generally positive when rows would otherwise shade each other. PVsyst documentation says the main advantage of backtracking is avoiding the electrical shading effect, and that a near-shading loss of about 2 to 3% typically remains because diffuse and albedo components are still shaded.

Mode Behaviour Main loss mechanism
Standard tracking Follows the sun continuously Inter-row shading plus electrical mismatch at low sun
Backtracking Flattens the angle to avoid shading Cosine angle loss plus incidence angle (IAM) penalty
Backtracking gain Difference between the two Avoided mismatch loss, which varies by GCR, latitude and electrical design

Published figures for what is gained or lost are scattered and come from different bases, so they are not directly comparable:

Source Reported figure Note
PVsyst documentation Near-shading loss of about 2-3% typically remains with backtracking Software documentation; diffuse and albedo still shaded
Polytechnic University of Madrid study (2026) Suboptimal backtracking losses up to 2% of tracking-related irradiance gains More than 7,000 trackers, seven plants, about 1 GW
Same study Tracking-related losses can exceed 5% annually versus ideal simulations Compared with simulations without operational constraints
PVH (tracker vendor) Up to 4% more annual energy for 3D backtracking than standard, in high-slope cases Vendor claim; see terrain breakdown below

Sources: PVsyst, pv magazine on the Madrid study, PVH.

Key Takeaway

There is no single annual-gain figure for backtracking. Treat any number as site-specific and ask for the GCR, terrain and controller assumptions behind it.

The exact gain depends on GCR, latitude, climate, and electrical design. High-GHI, low-diffuse sites see larger absolute gains because the direct beam dominates and shading would have been severe. Cloudy climates with high diffuse fractions see smaller gains because diffuse light cannot be tracked anyway.


Backtracking Algorithms: Standard, Slope-Aware, and 3D

Not all backtracking is the same. The controller’s algorithm determines how aggressively it tilts away from the sun, whether it accounts for terrain, and whether it optimises for diffuse or bifacial conditions.

Standard Astronomical Backtracking

This is the default in most commercial tracker controllers and in PVsyst. It assumes flat ground, uniform row pitch, and identical tracker geometry across the array. The controller computes a common tracking angle for all rows based on the sun position and a single reference GCR.

Standard backtracking works well when the site is genuinely flat and the as-built row spacing matches the design. It fails when terrain undulates, when different zones have different GCR, or when tracker heights vary.

Slope-Aware Backtracking

NREL’s 2020 slope-aware backtracking work extended the standard algorithm to account for cross-axis terrain slope. On a slope, the shadow from one row falls at a different angle than on flat ground. A single common tracking angle cannot keep all rows unshaded.

Slope-aware algorithms calculate a terrain-corrected axis tilt and cross-axis slope angle for each row or row pair. The correction angle then depends on the local slope rather than the flat-ground assumption. The gain depends on how steep and irregular the terrain is.

3D and Terrain-Following Backtracking

Advanced tracker systems now use 3D backtracking that considers north-south as well as east-west slopes, installation deviations, and even corner shading between staggered rows. PVH, a tracker vendor, reports that its 3D backtracking can deliver up to 4% more annual energy than standard backtracking in high-slope cases, and a 50 to 300% energy boost during sunrise and sunset backtracking phases. The vendor gives no baseline for the second figure. These are the vendor’s own upper bounds, not independent results.

Vendor-reported maximum annual energy gain of 3D backtracking over standard backtracking, by terrain (% annual energy, up to)
  • Undulating both directions0.65%
  • East-west slope1.2%
  • Opposing slopes1.36%
  • High slopes4%

Source: PVH (tracker vendor) terrain table; vendor claims, not independently verified, checked November 2026.

The key insight is that eliminating every possible shadow is not always optimal. A 3D algorithm may tolerate minor corner shading if the resulting sun-facing angle captures enough extra irradiance to outweigh the small mismatch loss.

Diffuse-Optimised and Machine-Learning Variants

Some research groups have proposed backtracking strategies that optimise for total irradiance rather than just beam irradiance. In cloudy conditions, a flatter tracker orientation can capture more diffuse light from the sky dome. Machine-learning controllers use historical weather and production data to predict cloud cover and adjust the tracking strategy accordingly. These are not yet mainstream but are moving into commercial products.


GCR, Row Spacing, and the Backtracking Threshold

Ground Coverage Ratio is the single most important design input for backtracking. It directly sets the angle at which the controller must switch from normal tracking to backtracking.

GCR Row Spacing (m per m of collector width) Backtracking Behaviour Typical Use Case
0.30 3.33 Minimal backtracking; wide shoulders Land-abundant sites, bifacial designs
0.35 2.86 Moderate backtracking Common utility-scale range
0.40 2.50 Frequent backtracking at low sun angles Common where land is moderately constrained
0.45 2.22 Heavy backtracking; narrow energy shoulders Land-constrained sites
0.50 2.00 Almost continuous backtracking near sunrise/sunset Very tight layouts, rarely optimal

At GCR 0.30, the rows are so far apart that backtracking is rarely needed. At GCR 0.50, the controller is backtracking for hours each morning and evening. The best GCR for a project balances land cost against energy yield and differs by site.

Backtracking also affects project finance, because it changes the energy yield assessment. Document the GCR, module width, hub height and terrain assumptions behind the backtracking model so a reviewer can check them.

The backtracking threshold also depends on module dimensions. Longer modules cast longer shadows for a given tilt. Taller tracker axes cast shadows that start higher on the rear row. The controller must be configured with the actual module width and tracker hub height, not just a generic GCR value.

A common commissioning mistake is to enter the wrong GCR or module width into the tracker controller. The controller then backtracks at the wrong angle. Either it allows shading that the PVsyst model did not predict, or it over-backtracks and sacrifices production during the shoulders. Both errors appear as unexplained yield gaps.


Backtracking on Real Sites: Terrain, Bifacial, and Controller Calibration

Design software assumes ideal conditions. Real sites do not. Three factors in particular change how backtracking performs in the field.

Terrain Undulation

Even sites described as “flat” can have local height differences between tracker posts. Over hundreds of metres, these add up to slopes that break the flat-ground backtracking assumption. PVsyst notes that shading can occur between trackers even with backtracking when there are height differences.

A 2026 study by the Polytechnic University of Madrid analysed more than 7,000 trackers across seven utility-scale plants with aggregate capacity of about 1 GW. The researchers compared SCADA tracker angles with ideal flat-terrain backtracking and found that controllers apply an overcorrection during backtracking on slightly undulating terrain. This overcorrection flattens tracker angles more than the ideal flat-ground model assumes, creating visible ground illumination patterns and lost irradiance.

The study quantified these “suboptimal backtracking losses” at up to 2% of tracking-related irradiance gains, and the authors describe deviations of 1 to 3% in captured irradiation as economically significant.

Bifacial Modules

Bifacial solar panels capture reflected light from the ground beneath and around the array. Backtracking changes the panel tilt and therefore the ground illumination pattern. It also changes the view factor to the sky dome and the rear-side shading from adjacent rows.

Bifacial systems generally prefer lower GCR values, because wider spacing increases ground-reflected rear irradiance. The backtracking algorithm should be reviewed with the bifacial model: a strategy optimised for monofacial front-side yield may not maximise total bifacial gain.

Controller Calibration

The backtracking algorithm lives in the tracker controller, not in the design model. At commissioning, the controller must be loaded with the correct site coordinates, GCR, module width, hub height, and slope data. A mismatch between the controller and the PVsyst input is one of the most common causes of tracker underperformance.

For EPCs executing ground-mount projects, a sound handover step is to obtain the controller configuration report and check it against the approved single-line diagram and shading model.

Pro Tip

At commissioning, write down the GCR, module width, hub height and cross-axis slope you entered in the controller and attach them to the design model. If morning production trails the model, check these inputs before you look at inverters or soiling.


The Hidden Cost of Suboptimal Backtracking

Suboptimal backtracking is not the same as no backtracking. It occurs when backtracking is enabled but the algorithm does not match the real site geometry. The tracker rows still avoid the worst shading, but they over-flatten and sacrifice sun-facing orientation.

The loss is hard to spot with standard performance ratio metrics. PR compares actual energy to in-plane irradiance, but it assumes the tracker is following the modelled angles. If the tracker is operating at a flatter angle than the model assumes, the in-plane irradiance estimate is wrong and PR looks normal.

Signs of suboptimal backtracking include:

  • Morning and evening production curves that are lower than expected but not obviously clipped
  • Visible ground illumination patterns during backtracking hours
  • Tracker angles from SCADA that are systematically flatter than the design schedule
  • Yield gaps that persist after cleaning, inverter checks, and soiling corrections

The Madrid study found that annual tracking-related losses can exceed 5% when compared with ideal simulations without operational constraints. The difference between ideal flat-ground backtracking and real controller behaviour is now recognised as a distinct loss category.

To avoid it, use terrain-corrected backtracking algorithms where available. Grade the site to tighter tolerances than a fixed-tilt project would require. Then validate controller inputs against as-built survey data.


How to Verify Backtracking in Your Solar Design Software

Modern solar design platforms model backtracking in different ways. The verification process depends on the tool, but the principles are the same.

In PVsyst

PVsyst implements backtracking for horizontal north-south trackers, tilted axis trackers, horizontal east-west trackers, and two-axis frames. It uses a common tracking angle per orientation group based on a reference GCR. Key steps:

  1. Define the tracker geometry: width, pitch, hub height, and axis azimuth
  2. Enable backtracking in the tracking parameters
  3. Confirm the GCR reference matches the dominant spacing in the scene
  4. Run the shading simulation with electrical shading enabled
  5. Review the near-shading loss, which PVsyst states typically remains around 2 to 3% even with backtracking

PVsyst derives the angle from a reference GCR and warns that sub-groups with a smaller pitch will suffer mutual shading while larger-pitch groups backtrack too early. If the site has variable pitch or height differences, run a sensitivity on the GCR reference and compare the energy results.

In NREL SAM and pvlib

NREL’s System Advisor Model and the open-source pvlib Python library both include single-axis tracking functions with a backtrack flag. The pvlib singleaxis function takes GCR, max_angle, and backtrack as inputs and returns the surface tilt and azimuth for each time step. This is useful for scripting custom sensitivity studies or validating commercial controller outputs.

In SurgePV

SurgePV’s published scope covers 3D roof modeling, solar array layout, shading analysis, energy-yield modeling, financial modeling and proposal generation. Tracker and backtracking modeling is not listed in that scope, so confirm whether your tracker configuration is covered before you plan around it. For fixed-tilt and rooftop projects, solar design software and shadow analysis cover the spacing and shading checks described above.

Field Verification

The final check happens in SCADA. Export the commanded tracker angle from the controller for a clear-sky day. Compare it to the angle predicted by the design model at the same timestamp. A persistent offset during backtracking hours points to a GCR, slope, or module-width mismatch.


When Backtracking Is Not Enough

Backtracking is necessary but not sufficient for maximum tracker yield. There are situations where the algorithm cannot recover all losses.

Very high GCR. At very high GCR, backtracking dominates the daily operation. The energy shoulders shrink so much that the tracker behaves almost like a fixed-tilt system at low sun angles, which can weaken the case for tracking.

Severe terrain. On steep or highly irregular terrain, no common-angle backtracking strategy can keep all rows unshaded. Terrain-following trackers or row-specific controllers may be required, but they add cost and complexity.

Diffuse-dominated climates. In regions where diffuse irradiance makes up most of the available light, the benefit of tracking, and therefore of backtracking, is smaller, because diffuse light cannot be tracked.

String-level shading from objects. Backtracking handles row-to-row shading. It does not handle shading from external objects such as trees, buildings, or equipment. Those must be addressed with layout changes, stringing segregation, or optimisers.


Comparing layouts for a ground-mount site?

Test spacing, shading and yield side by side before the design is locked. Bring your row pitch and module data to a SurgePV demo.

See a Live Walkthrough

Checking cost first? See the SurgePV pricing page.

Want to see how a layout, shading and yield model fit together? Book a SurgePV demo or read our tracker vs fixed tilt comparison for the wider decision.


Frequently Asked Questions

What is solar backtracking?

Solar backtracking is a tracker control mode that rotates single-axis tracker rows away from the sun-facing position at low sun angles so adjacent rows do not shade each other. It accepts a small irradiance loss to avoid the larger electrical mismatch loss from partial row shading.

How much energy does backtracking save?

There is no single figure, because the gain depends on GCR, terrain, latitude and electrical design. PVsyst says a near-shading loss of about 2 to 3% typically remains with backtracking, and a tracker vendor claims up to 4% extra from 3D backtracking on high slopes.

What is GCR in solar backtracking?

GCR, or Ground Coverage Ratio, is the ratio of collector width to row pitch in a tracker array. Higher GCR means tighter spacing, more inter-row shading risk and more backtracking hours, while lower GCR means wider spacing and less need for backtracking.

Does backtracking work on sloped terrain?

Standard backtracking assumes flat ground, so on sloped or undulating terrain a single common tracking angle cannot remove all inter-row shading. Slope-aware and 3D backtracking calculate terrain-corrected angles per row, which NREL’s slope-aware work derives for cross-axis slopes.

Can backtracking be modelled in PVsyst?

Yes. PVsyst supports backtracking for horizontal north-south, tilted-axis and horizontal east-west trackers and two-axis frames, using one tracking angle per orientation group from a reference GCR. Keep electrical shading enabled, because diffuse and albedo components stay partly shaded.

What causes suboptimal backtracking losses?

They occur when real controllers deviate from ideal flat-terrain angles to avoid shading on slightly uneven ground. A 2026 Polytechnic University of Madrid study of more than 7,000 trackers found losses up to 2% of tracking-related irradiance gains from over-flattened angles.

How do I verify backtracking settings in the field?

Get the controller configuration report at commissioning and confirm it matches the design GCR, module width, row pitch and coordinates. Then compare commanded tracker angles from SCADA with the design model’s schedule in morning and evening hours, since GCR mismatches are a common cause of gaps.

Where this fits

This article is part of SurgePV's Solar Technology hub, which works through the topic from first principles to the decisions a project team actually has to make.

About the Contributors

Author
Keyur Rakholiya
Keyur Rakholiya

CEO & Co-Founder · SurgePV

Keyur Rakholiya is identified by SurgePV as its CEO and a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, testing claims, media appearances, and speaking engagements are not asserted without retained evidence.

Editor
Rainer Neumann
Rainer Neumann

Editorial contributor · SurgePV

Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.

Get Solar Design Tips in Your Inbox

Join 2,000+ solar professionals. One email per week - no spam.

No spam · Unsubscribe anytime

Book Free Demo

Choose which optional technologies SurgePV may use. Essential storage remains active for security and requested features.