How to Size DC Cable for Voltage Drop at a Solar Site

The Voltage-Drop Calculation for Panel and Battery Runs

Voltage drop on a DC run comes from Ohm's law applied to the resistance of the wire. The drop in volts is the current flowing in the run multiplied by the total resistance of the conductor, and because current flows out along one conductor and back along the other, the resistance that counts is the round-trip resistance, both the supply and return legs added together. Conductor resistance itself is the resistance per unit length of the chosen gauge multiplied by the one-way length of the run. Put together, the drop scales with the current, with twice the one-way distance, and with how thin the wire is, and it shrinks as you move to a heavier gauge with lower resistance per unit length.

The panel-to-controller run carries the array's charging current over whatever distance separates the panel from the enclosure. This run is often the longest at a remote site, because the panel is placed for sun and the electronics for shelter, and it carries current whenever the sun is up. A drop here is charge that leaves the panel but never reaches the controller, so the controller sees a lower input voltage and less energy to push into the battery. Sizing this run means taking the array's charging current, the round-trip length, and working out the gauge whose resistance keeps the drop within an acceptable fraction of the operating voltage.

The controller-to-battery run is usually shorter but carries the full charging current into the battery and, on some layouts, the load current out of it, so its current can be as high as anything on the site. A drop on this run has a subtler cost: the charge controller regulates to a target battery voltage, and if it senses voltage at its own terminals rather than at the battery, the drop in the cable fools it into thinking the battery is fuller than it is, so it tapers charging early and the battery never quite reaches a full state. That is why this run is kept short and heavy, and why controllers that support remote battery voltage sensing are used to measure at the battery itself rather than through the drop.

Why Low System Voltage Makes the Drop Bite

The reason voltage drop is so punishing on solar telemetry sites is that they run at low DC voltages. A fixed drop caused by cable resistance is an absolute number of volts, but its importance is relative to the system voltage it sits on. Half a volt lost across a run is a trivial fraction of a mains circuit but a large fraction of a twelve-volt system, where it can represent several percent of the whole operating voltage and a corresponding several percent of the delivered energy. The same physical cable that would be perfectly adequate at a higher voltage becomes a real loss at twelve volts.

Two factors compound this. First, delivering a given amount of power at a low voltage requires proportionally more current than at a high voltage, and voltage drop grows with current, so low-voltage systems push more amps through the same wire and lose more to its resistance. Second, remote sites often have long runs because the panel is positioned for the best sun and the equipment for shelter or security, and drop grows directly with length. A long run at high current on a low system voltage is the worst-case combination, and it is exactly the combination a remote solar site tends to present.

This is why the choice between system voltages is partly a cable decision. Running the same site at twenty-four or forty-eight volts instead of twelve carries the same power at a fraction of the current, which cuts the voltage drop for a given cable dramatically and lets a thinner, cheaper conductor do the job over the same distance. When a site has long runs or a substantial load, stepping the bus voltage up can be less expensive overall than buying the heavy copper a twelve-volt version would need, which is why the intended run lengths should be weighed when the bus voltage is chosen rather than treated as a separate problem afterward.

Percent-Drop Targets and Keeping a Remote Array Charging

Cable is sized against a target drop expressed as a percentage of the system voltage, because that percentage is what determines how much of the harvested energy survives the run. As a working rule, the panel-to-controller run is commonly held to a small single-digit percentage of the operating voltage, so that the large majority of the array's output reaches the controller. The controller-to-battery run is usually held tighter still, both because a drop there confuses the controller's regulation and because it directly costs charge going into and out of the battery. These targets are guidelines rather than a fixed code figure, and a designer chooses the gauge that meets or beats them for the site's current and distance.

The stakes are higher on a remote site than the small percentages suggest, because the losses compound with a solar budget that is already tight. An array is often sized with little margin to replace exactly the daily energy a node consumes, so quietly losing several percent of the harvest in cable resistance can be the difference between a battery that recovers each day and one that drifts steadily down until the site drops offline during a cloudy stretch. The loss is invisible in fair weather when the panel has surplus, which is precisely why it goes unnoticed until a bad week exposes it. Sizing cable generously is cheap insurance against a failure mode that only shows up when the site can least afford it.

A cloud SCADA layer is often how an undersized run is finally diagnosed, because the symptom is subtle. When a platform such as Merobix trends the panel voltage, the battery voltage, and the charge current together, a run losing too much to resistance shows up as a persistent gap between the voltage the panel produces and the voltage the controller sees, and as a battery that never quite reaches a full charge even on sunny days. An operator watching a node fail to recover its charge despite good weather can suspect the cable rather than the panel or the battery, and confirm it by comparing the input and battery voltages the platform has been recording all along.

Frequently Asked Questions