CoreVecta AtlasPractical knowledge
Charging & runtime · the refill clock

Solar recharge time for an energy deficit

Turn an energy deficit into a refill clock: the hours of array output a drained bank needs once the charge controller and wiring take their share.

✓ Verified engine No account required

Workspace

The calculator's own fields, action and results arrive with the verified pack when you load it. Nothing is computed in this page.

Verified engine

Calculator

The calculator runs on the same signed pack and certified engine as the CoreVecta apps. It is fetched and verified when you need it, so this page stays light until then.

Nothing is computed in this page. Every figure comes back from the verified engine, or the calculator refuses.

What the engine returns
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.
Energy deficit to recharge
Available solar array output
Charge-path efficiency (fraction)
MethodThe energy deficit is divided by the available solar array output discounted by the charge-path efficiency, returning the recharge time in hours; the declared reverse workflow solves for the array output a required recovery window demands.
StandardSolar recharge relation, hours = deficit kWh / (array kW × charge efficiency)
GuardA 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.

How the recharge time moves with array output

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.

The energy deficit is divided by the available solar array output discounted by the charge-path efficiency, returning the recharge time in hours; the declared reverse workflow solves for the array output a required recovery window demands.

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.

Worked example

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.

What each input represents

Energy deficit to recharge

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.

Available solar array output

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.

Charge-path efficiency (fraction)

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.

Assumptions and limits

  • 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.

What the guards protect against

  • 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.

Provenance

Solar recharge relation, hours = deficit kWh / (array kW × charge efficiency)

The energy deficit is divided by the available solar array output discounted by the charge-path efficiency, returning the recharge time in hours; the declared reverse workflow solves for the array output a required recovery window demands.

Screening and reference material, to be checked against the governing standard and a qualified engineer; not a design determination. The signed pack carries its own citation, and the page reports the verification state of the release it mounted.