The mechanism
A solar-powered spacecraft must supply computation plus communications, control, thermal transport and other bus loads. Solar array output depends on illuminated area, conversion efficiency, orientation and degradation. An orbit with favorable sunlight can reduce eclipse demand, but sunlight is not the same as usable electricity and a sun-synchronous orbit is not automatically eclipse-free. Batteries cover intervals when generation falls below load and must later be recharged with losses included. NASA’s power-system guidance treats dynamic operating conditions and eclipse as design inputs. A compute scenario therefore needs a time-dependent energy ledger before declaring its solar area sufficient.
- Specify orbit, sunlight intervals and array orientation rather than assuming continuous full illumination.
- Convert incident sunlight to electrical output using explicit efficiency and degradation factors.
- Subtract communications, control and thermal-system loads before assigning compute power.
- Integrate battery charging and discharging through eclipse with usable-energy and efficiency limits.
- Check both average energy balance and the worst low-generation interval.
Science and assumptions
Solar power budget
Instantaneous solar electrical power equals irradiance times active area times conversion efficiency times the orientation/degradation factor.
Symbols and units
- P_solar
- Instantaneous generated solar electrical power
W
- S
- Incident solar irradiance at the selected condition
W/m²
- A
- Active collection area
m²
- η
- Solar conversion efficiency
fraction
- g
- Declared orientation/degradation factor
dimensionless
S is irradiance W/m², A active area m², η conversion efficiency and g an orientation/degradation factor.
Assumptions Instantaneous illuminated condition; sunlight duty cycle and storage losses require time integration.
Engineering example
Synthetic array with 1,361 W/m² irradiance, 10 m² active area, 30% efficiency and factor 0.8 generates about 3.27 kW while illuminated. A 1 kW bus load leaves about 2.27 kW before charging losses and other reserves.
Distinctions and tradeoffs
Space sunlight is an energy input that needs collection and conversion; it does not eliminate array, storage or support-system costs.
Larger arrays add generation and mass, while longer battery-supported operation adds storage mass and cycling requirements.
An accelerator payload can run continuously only if its complete spacecraft energy budget survives the worst relevant operating interval.
Specifications and interfaces
- Generated versus payload power
- Total bus electricity and IT load
Do not assign all array output to accelerators.
- Storage capacity
- Usable Wh or kWh
Nameplate energy differs from allowable usable energy after reserve and losses.
Interfaces
- Sunlight and array geometry Input
- Irradiance, orientation and conversion conditions
- Spacecraft electrical bus Output
- Power shared by payload, support loads and battery charging
Check your understanding
Why can average solar power exceed average load while a design still fail?
- Its battery may not cover the longest deficit interval
- Average power automatically guarantees all times
- Computers use no power in eclipse
Answer and reasoning
Its battery may not cover the longest deficit interval
Time-dependent deficits can exhaust storage even when the orbit-average energy balance appears positive.
Evidence and scope
The irradiance is a representative near-Earth physical input; all design factors and area are synthetic. No orbit-wide generation or payload efficiency is asserted.
Close a bounded payload solar, eclipse-energy, radiator and communications scenario; radiation, structural design and lifecycle costs remain unmodeled.