On this page15 sections
- 01How a drained bank, a real array and a lossy charge path become a refill clock
- 02Concepts to hold first
- 03The episode is a cycle, not a line
- 04What the array actually offers the bank
- 05The toll on the way in
- 06Reading the clock as exposure
- 07How the method works
- 08Try it, verified
- 09What each input represents
- 10Worked example
- 11Reading the result
- 12Common mistakes
- 13Questions readers arrive with
- 14When this calculation is used
- 15Assumptions and guards
How a drained bank, a real array and a lossy charge path become a refill clock
The deficit is whatever the last episode took out: the outage bill from this cluster’s first page, a run of cloudy days, or a deliberate deep discharge before maintenance. It is an energy figure, and it is the numerator because refilling is the mirror of the runtime question — there energy over power gave hours of survival, here it gives hours of vulnerability.
The power term is the array output actually AVAILABLE for charging, which is smaller than the nameplate on the panels for two separate reasons. Real arrays deliver their rating only near solar noon on a good day, and a household that is awake is spending part of the output as it arrives — only the surplus reaches the bank. Entering the nameplate here produces a clock that flatters the plan by the whole difference.
The efficiency fraction is the charge path’s toll: controller conversion and wiring resistance taken out of every kilowatt-hour BEFORE it is banked. It is the inbound mirror of the discharge efficiency the runtime page applies, and the two together are why a round trip through a battery costs more than either leg suggests — this pack treats that combined figure in its own round-trip sibling.
Read the answer as exposure, not trivia. A refill measured in a single afternoon means consecutive outages are survivable; one measured in days means the plan quietly assumes storms arrive singly, and that assumption belongs in the open. The declared reverse workflow prices the remedy directly: fix the recovery window the plan demands, and the engine returns the array output that window requires.
Concepts to hold first
Whatever the last episode took out of the bank: an outage’s bill, a run of cloudy days, or a deliberate deep discharge before maintenance. It is the numerator of the refill clock, and this journey’s first lesson computes exactly this figure — which is what makes the two pages one story.
The solar power actually offered to the bank: delivered output under the sky being planned for, less whatever the household consumes as it arrives. It is smaller than the panels’ nameplate for both reasons at once, and entering the nameplate here flatters the clock by the whole difference.
The fraction of array energy that survives the charge controller and wiring to be banked. It is a toll on the inbound leg only — the discharge side pays its own on the runtime page — and it is entered as a decimal fraction, with the controller manufacturer’s rated figure as the honest source.
The refill clock read as risk: the stretch during which the reserve is below strength and a second interruption lands on a half-empty bank. A plan’s real resilience is set by how this window compares with the gaps between the outages it expects.
The episode is a cycle, not a line
The journey so far reads as a sequence — price the outage, size the machine, ride the interruption through — but the system underneath it is a cycle. The grid fails; the bank pays the essential circuit’s bill; the grid or the sun returns; the array pays the bill back into the bank; and the reserve stands ready for the next failure. Every quantity this cluster computes is one arc of that circle, and the refill clock is the arc plans forget — because the lights are already on when it starts, and nothing looks wrong while it runs.
What makes the forgotten arc dangerous is that outages cluster. The weather that takes the grid down once is often still overhead the next evening, and a plan sized to survive one interruption meets the second with whatever the sun has managed to put back in between. The refill clock is the honest measure of that “in between”: shorter than the gap between storms and the cycle closes safely; longer, and the plan is quietly betting the weather calms down on schedule.
The outage cycle: the grid fails, the bank pays the bill, the sun pays it back, and the reserve is restored before the next failure
The cycle behind the cluster: discharge across the top, recharge back along the bottom. The refill clock measures the bottom arc — and the plan is only as strong as the cycle’s slowest passage.
What the array actually offers the bank
The power term is the input most likely to be entered generously, because the generous figure is printed on the panels. A nameplate describes laboratory light; a real array delivers its rating only near solar noon on a good day, and spends the rest of its hours below it. The refill clock is honest only if its power term is the output actually expected under the sky being planned for — the same discipline the solar journey applies to yield, pointed at charging.
The second discount is easier to forget and often larger: the household is awake while the bank refills, and it spends part of the array’s output as it arrives. Only the surplus reaches the bank. A home that runs its washing, cooking and cooling through the recovery window is competing with its own battery for the same panels — which is worth knowing, because deferring the discretionary loads for a day is a zero-hardware way to shorten the exposure.
The honest entry, then, is delivered output net of concurrent consumption. A nameplate figure belongs in this field only for a dedicated charging array under a full sun — the narrow case where the label and the truth briefly agree.
The toll on the way in
Not every kilowatt-hour the array offers is banked. The charge controller takes a conversion toll; the wiring between array, controller and bank takes a resistive one; and the efficiency fraction this calculation asks for is those tolls combined — the share of incoming energy that actually arrives as stored charge. Losses on the way in are hours added to the clock as surely as a smaller array would add them.
The fraction covers the inbound path only, and the boundary is worth keeping sharp. The discharge leg — bank to inverter to circuit — pays its own toll on the runtime page, and the two legs together are why a round trip through a battery costs more than either alone suggests; the pack treats that combined figure in its own round-trip sibling. Entering a round-trip figure here double-counts the outbound losses and stretches the clock beyond what the inbound path deserves.
The honest value comes from the controller manufacturer’s rated figure, and the pack declares its supplied default illustrative for exactly that reason. The guards hold the fraction to what physics allows: a figure above one would have the path banking more than the array delivers — usually a percentage standing where a decimal belongs — and a figure at or below zero describes a broken charger, not a slow one. Both are refused rather than clocked.
Array output steps down through the controller toll and the wiring toll before it is banked as stored energy
The inbound path as a descending staircase: what the array offers at the top, what the bank receives at the bottom, and the charge path’s tolls in between. The clock runs on the bottom figure, not the top one.
Reading the clock as exposure
The engine returns hours, and the first act of interpretation is to notice what kind of hours they are: hours OF the stated array output, not clock hours on a wall. Real solar input climbs and falls through each day, so a refill measured in a handful of output-hours means the productive heart of a day; one measured in many means a procession of days, each contributing its usable middle. The calculation deliberately does not model the sky’s daily shape — it prices the energy arithmetic, and the calendar translation stays with the planner.
The second act is to read the hours against the weather that caused the deficit. A recovery window shorter than the gap between the storms a region actually produces means consecutive outages are survivable; a window that outlasts the gap means the plan meets its second interruption half-empty, and that assumption deserves to be made in the open rather than discovered in the dark. The remedies are the relation’s own levers: more array, less deficit, a cleaner charge path — or a generator bridging the difference, scheduled honestly against the same clock.
The declared reverse workflow prices the remedy directly. Fix the recovery window the plan demands — the longest exposure the household will accept — and the engine returns the array output that window requires. Run that way, the calculation stops being a verdict on hardware already owned and becomes a specification for the charging half of a design.
How the method works
The available array output is discounted by the charge-path efficiency, giving the power that actually banks — the array’s offer after the controller and wiring take their tolls.
The energy deficit is divided by that banked power, returning the recharge time in hours: hours of the stated output, which on a real roof means the productive heart of one or more days rather than a contiguous stretch.
The declared reverse workflow runs the relation backwards: fix the recovery window the plan demands, and it returns the array output that window requires.
The certified engine performs this calculation. This page explains what it does; it does not reproduce it, because a second implementation of a specified method is a second answer waiting to disagree with the first.
Try the worked scenario
The calculator below is the same certified engine the calculator page runs — fetched, verified and mounted mid-lesson. It arrives pre-filled with the pack’s own anchor: a bank drawn down by a working day of outage, refilled by a modest array through a realistic charge path. Bring the deficit over from the first lesson’s bill for your own circuit, enter the output your array honestly delivers net of the household’s daytime draw, and read the hours as your exposure window; then work the levers — more array, a cleaner path, a leaner deficit — and watch which one your clock answers to.
Read the result as hours of the stated output, not clock hours — and as exposure, not trivia: the window during which a second outage lands on a depleted reserve. Every figure shown is computed by the verified engine as you type; nothing on this page stores an answer.
What each input represents
The energy the bank is down, in kilowatt-hours — an outage bill, a cloudy stretch, or the usable capacity itself after a full-depth discharge. The outage page of this cluster computes exactly this figure, which is what makes the two pages one story.
The array output actually available for charging, in kilowatts: delivered power under the sky being planned for, less whatever the household consumes as it arrives. A nameplate figure belongs here only for a dedicated charging array under a full sun.
The fraction of array energy that survives the controller and wiring to be banked, as a decimal strictly between zero and one. The pack declares its supplied default illustrative — the controller manufacturer’s rated figure is the honest entry, and it covers the inbound path only, not the round trip.
Worked example
The scenario
Run the pack’s anchor duty: a bank down 20 kWh after a working day of outage, refilled by 5 kW of available array output through a charge path at the default 0.85 efficiency.
The engine returns the refill clock in hours — hours of that stated output, which on a real roof means the productive heart of one or more days rather than a contiguous stretch. Read it against the weather that caused the deficit in the first place: a recovery window that outlasts the gap between storms is a plan that meets its second outage half-empty, and the remedy is more array, less deficit, or a generator bridging the difference.
The pack’s other declared duties show both levers: a 10 kWh deficit against 3 kW of array through a 0.9-efficient path, and a 25 kWh one against 6 kW at 0.8. Efficiency multiplies the clock as surely as array size does — losses on the way in are hours added to the exposure.
Reading the result
A refill that fits inside a single day’s productive sun means consecutive outages are survivable — the cycle closes faster than the weather reloads. A refill measured in days means the plan assumes storms arrive singly, and that assumption belongs in the open.
The hours scale directly with every term: double the deficit and the clock doubles, halve the honest array output and it doubles again, and charge-path losses stretch it as surely as clouds do. When the window is too long, the relation itself lists the levers.
A clock that flatters intuition usually has a flattered input — a nameplate standing where net output belongs, or a label capacity upstream of the deficit. The calculation is only as honest as the terms it is fed, and every one of them has a documented honest source.
Common mistakes
Entering the panels’ nameplate as the array output. Real arrays deliver their rating only near solar noon on a good day, and the clock stretches by the whole difference.
Forgetting that the household consumes as the sun delivers. Only the surplus reaches the bank, and the relation does not subtract concurrent loads for you — the stated output must already be net of them.
Entering a round-trip efficiency where the inbound fraction belongs. The discharge leg paid its toll on the runtime page; counting it again here stretches the clock beyond what the charge path deserves.
Reading the hours as a contiguous stretch of wall-clock time. They are hours OF the stated output — on a real roof, the productive middles of one or more days.
Trusting the final stretch of the refill to run at full pace. Real controllers taper as the bank approaches full, and the relation’s unlimited-acceptance assumption is kindest exactly at the end.
Questions readers arrive with
Where does my deficit figure come from?
From whatever emptied the bank: the outage bill this journey’s first lesson computes, a cloudy stretch read off the battery monitor, or the usable capacity itself after a full-depth discharge. The first case is the designed handoff — the bill the outage ran up is exactly the energy this clock must put back.
What efficiency should I enter?
The charge controller manufacturer’s rated figure, for the inbound path only — the pack declares its supplied default illustrative, not a recommendation. Keep round-trip figures out of this field; the discharge leg pays its own toll on the runtime page, and the combined cost has its own sibling calculator.
Why was my efficiency entry refused?
The guards hold the fraction to what physics allows. Above one, the path would bank more than the array delivers — almost always a percentage entered where a decimal fraction belongs, caught before it shortens the clock a hundredfold. At or below zero, the path delivers nothing, which is a broken charger rather than a refill plan, and the refusal surfaces that instead of dividing by a fantasy.
Does the clock account for night, or for the sky changing?
No — the hours returned are hours of the stated output, and translating them onto a calendar of real days is deliberately left with you. The relation also assumes the bank accepts charge at full pace to the end, where real controllers taper — one more reason to read a marginal window pessimistically.
My recovery window is longer than the gaps between my outages. What now?
Work the levers in cost order: defer discretionary daytime loads so more of the array’s output reaches the bank; shrink the deficit by shedding the essential circuit leaner; add array, priced by the declared reverse workflow; or bridge with a generator, scheduled honestly against the clock rather than against hope.
When this calculation is used
After outage planning: the recovery window a chosen bank-and-array pairing leaves between one interruption and the next.
Sizing the charging half of a design — the declared reverse workflow returns the array output a required recovery window demands.
Judging a portable or vehicle system, where a small panel refilling a drained station is the whole question the purchase turns on.
Scheduling generator support honestly: when the sun’s refill clock is longer than the forecast gap, the deficit needs another source.
Assumptions and guards
The array output is constant at the stated figure for the whole refill; real solar input climbs and falls through each day, so the hours returned are hours OF that output, not clock hours.
The stated output is net of household consumption during the refill — the relation does not subtract concurrent loads for you.
The charge acceptance is unlimited: no controller taper near full charge, temperature limit or C-rate ceiling slows the final fraction, and real chemistries slow exactly there.
The efficiency is one fixed fraction for the whole inbound path; the round-trip figure, which also counts the discharge leg, belongs to its own sibling in this pack.
A charge-path efficiency above one is refused — the pack ships that refusal as a declared test vector. No path banks more than the array delivers, and the ceiling catches a percentage entered where a decimal fraction belongs before it shortens the clock a hundredfold.
The efficiency must also be strictly positive: a path that delivers nothing has no refill clock, only a broken charger, and the refusal surfaces that rather than dividing by a fantasy.
The deficit and the array output must each be positive and below utility-scale caps, so a watt-hour or watt figure entered a thousandfold out of unit is refused as a slip rather than returned as a clock measured in months.