NASA Power
NASA Power
NASA Power
September 2016
NASA STI Program . . . in Profile
Since its founding, NASA has been dedicated • CONTRACTOR REPORT. Scientific and
to the advancement of aeronautics and space science. technical findings by NASA-sponsored
The NASA Scientific and Technical Information (STI) contractors and grantees.
Program plays a key part in helping NASA maintain
this important role. • CONFERENCE PUBLICATION. Collected
papers from scientific and technical
conferences, symposia, seminars, or other
The NASA STI Program operates under the auspices
meetings sponsored or co-sponsored by NASA.
of the Agency Chief Information Officer. It collects,
organizes, provides for archiving, and disseminates • SPECIAL PUBLICATION. Scientific,
NASA’s STI. The NASA STI Program provides access technical, or historical information from
to the NASA Technical Report Server—Registered NASA programs, projects, and missions, often
(NTRS Reg) and NASA Technical Report Server— concerned with subjects having substantial
Public (NTRS) thus providing one of the largest public interest.
collections of aeronautical and space science STI in
the world. Results are published in both non-NASA • TECHNICAL TRANSLATION. English-
channels and by NASA in the NASA STI Report language translations of foreign scientific and
Series, which includes the following report types: technical material pertinent to NASA’s mission.
• TECHNICAL PUBLICATION. Reports of For more information about the NASA STI
completed research or a major significant phase program, see the following:
of research that present the results of NASA
programs and include extensive data or theoretical • Access the NASA STI program home page at
analysis. Includes compilations of significant http://www.sti.nasa.gov
scientific and technical data and information
deemed to be of continuing reference value. • E-mail your question to [email protected]
NASA counter-part of peer-reviewed formal
• Fax your question to the NASA STI
professional papers, but has less stringent
Information Desk at 757-864-6500
limitations on manuscript length and extent of
graphic presentations.
• Telephone the NASA STI Information Desk at
757-864-9658
• TECHNICAL MEMORANDUM. Scientific
and technical findings that are preliminary or of • Write to:
specialized interest, e.g., “quick-release” reports, NASA STI Program
working papers, and bibliographies that contain Mail Stop 148
minimal annotation. Does not contain extensive NASA Langley Research Center
analysis. Hampton, VA 23681-2199
NASA/TM—2016-219148
September 2016
This report contains preliminary findings,
subject to revision as analysis proceeds.
Trade names and trademarks are used in this report for identification
only. Their usage does not constitute an official endorsement,
either expressed or implied, by the National Aeronautics and
Space Administration.
Level of Review: This material has been technically reviewed by technical management.
Available from
NASA STI Program National Technical Information Service
Mail Stop 148 5285 Port Royal Road
NASA Langley Research Center Springfield, VA 22161
Hampton, VA 23681-2199 703-605-6000
Abstract
High-altitude balloons (HABs) have become popular as educational and scientific platforms for
planetary research. This document outlines key components for missions where low cost and rapid
development are desired. As an alternative to ground-based vacuum and thermal testing, these systems
can be flight tested at comparable costs. Communication, solar, space, and atmospheric sensing
experiments often require environments where ground level testing can be challenging or impossible in
certain cases. When performing HAB research the ability to monitor the status of the platform and gather
data is key for both scientific and recoverability aspects of the mission. A few turnkey platform solutions
are outlined that leverage rapidly evolving open-source engineering ecosystems. Rather than building
custom components from scratch, these recommendations attempt to maximize simplicity and cost of
HAB platforms to make launches more accessible to everyone.
Acronym List
APRS Automatic Packet Reporting System
COTS Commercial of the Shelf
CSV Comma Separated Value
CUSF Cambridge University Space Flight Center
DC Direct Current
FAA Federal Air Administration
GAHPS Gondola for High Altitude Planetary Science
GPS Global Positioning System
HAB High Altitude Balloon
IoT Internet of Things
LiSO2 Lithium Sulfur Dioxide
NOTAM Notice to Airmen
PEL Power Equipment List
PMAD Power Management and Distribution
RTOS Real-time Operating System
SoC System on a Chip
UAV Unmanned Aerial Vehicle
NASA/TM—2016-219148 1
Introduction
Motivation
This research was initiated as risk reduction for the NASA Gondola for High Altitude Planetary
Science (GHAPS) mission. High altitude balloon missions carrying expensive science payloads across
harsh, difficult-to-access locations could greatly benefit from improved descent and landing systems with
the ability to mitigate landing loads and improve general recoverability.
As a first step, the Glenn Research Center “Rocket University” development program developed a
series of payloads of increasing capability to monitor and evaluate various recovery systems as shown in
Figures 1 and 2. Comprised mainly of commercial-of-the-shelf (COTS) electronics and open-source
software, this paper offers a few turnkey solutions for highly cost-constrained science missions. Rather
than re-inventing the wheel, these solutions leverage open-source microcontroller platforms with large
ecosystems that offer both flexibility and simplicity.
Figure 1.—Rocket University final launch (left) balloon Inflation, (right) payload being towed to the launch point.
NASA/TM—2016-219148 2
Figure 2.—The data acquisition (DAQ) system for a 2 lb $1,000 launch (bottom) was used again as secondary
DAQ for the launch shown in Figure 1.
NASA/TM—2016-219148 3
Telemetry
The ability to receive live wirelessly transmitted data from a payload is essential for the recoverability
of any balloon launch. FindMeSpot is a recommended COTS tracking device, requiring no configuration
or operator licenses. Communication via cell phone devices also offers slightly more flexibility, but
additional configuration and complexity. Both of these methods are limited to 40,000 ft altitude ceilings.
To maintain constant communication up to 100,000+ feet requires higher-powered radios. The most
accessible amateur radios require an operator with an amateur HAM license. These licenses require taking
an exam from a local amateur radio chapter. Many free online resources and study guides provide an easy
way to master the finite pool of possible written quiz questions in a few weeks time. After passing the
written test, the basic technician license is granted by the FCC within a few weeks. Additional licenses
can be obtained by taking increasingly difficult written exams, allowing the operation of higher-powered
radios over a larger range of frequencies.
The most popular balloon radio protocol, Automatic Packet Reporting System (APRS) provides a
very succinct transmission including the balloons GPS latitude, longitude, heading, and operator call-sign.
By committing to this protocol, the operator is able to leverage a large amount of pre-existing HAM radio
infrastructure. Rather than relying exclusively on personal ground station equipment, many other amateur
stations are constantly listening for the APRS frequency and protocol. If the signal reaches any of these
stations, the signal will be repeated and re-broadcasted to neighboring stations. Eventually the signal will
reach an Internet “gateway” where it is published to various web applications and databases. This allows
an APRS operator to simply broadcast signals, without the direct need for any receiver equipment. As
long as the signal reaches neighboring HAM stations, the call-sign and information will be available in
real-time from any Internet connected device. For more direct reception and faster feedback, many
affordable handheld receivers are available that can be tuned to filter out all incoming signals except
APRS messages from specific call-signs.
If the payload requires more advanced telemetry, leveraging other frequencies and protocols may be
more suitable. If a constant transmission (possibly bi-directional) communication link or higher
bandwidth is needed, amateur remote control UAV radio components may be a better option. With
balloon operations requiring extremely long-distance communication, the most ideal frequencies reside in
the UHF range. As a general rule, transmission bandwidth increases and range decreases with increasing
frequency. The 900 MHz is ideal for basic telemetry in the 100 to 200 kbps range up to 40 miles away.
Radio modems include the RFD900, and Xtend900. These specific models are identified for their drop-in
compatibility with existing hobby level UAV ecosystems that are outlined in subsequent sections. They
are export controlled, require a basic technician’s license, and only necessitate a minimal amount of radio
and programming experience.
NASA/TM—2016-219148 4
Figure 3.—Inflation of a 1500 g balloon.
Although hydrogen can be used as a source gas for inflation, it is extremely flammable. Helium is
preferred for general usage because of its chemical inertness. Typically, helium is sold in pressurized
tanks of various sizes. Helium can be acquired through local gas processing companies such as Airgas,
Praxair, and Matheson gas. In addition to the helium gas, a regulator is required and a filling system is
needed to transfer the gas from the bottle to the balloon. The filling system can simply be a flexible hose
connected to a PVC pipe that is just smaller than the balloon neck diameter. Using a simple force gauge,
such as a fish scale, lift can be measured during the inflation process.
Simply connect the gauge to the rim of the PVC pipe prior to its insertion inside the balloon neck.
The use of latex gloves, and wooden paddles covered in paper (or a tarp over the top of the balloon) is
recommended during the inflation process to contain the balloon in light winds as shown in Figure 3. Oil
or any other type of residue from direct skin contact may result in premature rupture of the balloon as it
expands dramatically at higher altitudes.
Gondola Design
For small-scale ballooning projects the payload box is typically designed using foam core board as
shown in Figure 4. The foam-core is cut in such a way that a six-sided box is formed from one piece of
board. The board is folded up into a box where all but one side has been glued together using silicone
adhesive. The remaining open side will serve as a door to fill the gondola with testing apparatus. Plastic
wall anchors typically 10 to 14 sized in the corners of the top and bottom faces of the box. This allows
stringing lines to be ran through the bottom to the top of the payload. The area of the payload is
determined by the testing components that will be going inside.
Many weeks prior to launch date, a suitable launch location needs to be determined. Aspects of a
good launch location include clear open skies in the nearby vicinity, a solid surface to lie out and fill the
balloon, and a workspace (or transportable table) to complete any power-on procedures necessary.
Standard power outlets are also preferred but not required.
NASA/TM—2016-219148 5
Figure 4.—First Rocket University 2 lb balloon payload, flown on the balloon shown in Figure 3.
A checklist detailing steps required prior to launch is recommended, an example checklist is provided
in Appendix B. Once a suitable location has been determined, the specific launch day is usually
determined by predicted weather conditions. Long-range forecasts that call for mild to warm temperatures
and low ground winds are preferred. There are multiple online sources to predict the trajectory of the
balloon and payload. The CUSF Landing Predictor 2.5 (predict.hanhub.org) is an excellent resource. The
predictions are more accurate as you approach closer to the planned launch date. The burst calculator on
the CUSF page allows you to enter details on your balloon, launch mass, and expected altitude to better
refine the prediction. For recovery and safety purposes, the predicted landing site should be one relatively
free of metropolitan areas and clear of large forests and bodies of water.
NASA/TM—2016-219148 6
Launch Regulations
Developing FAA regulations (as of February 2015) limit small UAS (55 lb) to line of site flight,
500 ft altitude ceiling, daylight operation, operator certification, and additional restrictions in various
airspaces (such as 5 mile radii around airports) without notifying air traffic control or further FAA
exemption. A separate, “more flexible”, set of regulations are under considerations for “micro UAS” class
aircraft that fall under 4.4 lb. Although it’s unclear how balloon systems overlap with UAS, the
development of guided descent and recovery systems certainly fall under both categories, with even more
stringent restrictions applied to vehicles used for commercial gain (Ref. 1).
Before launch, it’s highly recommended to file a Notice to Airmen (NOTAM) with the FAA and any
local regional airports.
NASA/TM—2016-219148 7
TABLE 2.—LAUNCH 1 PRICE BREAKDOWN
Part Function Cost
Arduino mega Microcontroller $40
microSD card (16 GB) Data storage $10
Razor 9DOF Inertial measurement unit $75
GPS Navigation $50
GPS antenna Antenna $15
Spot tracker Back-up tracker $75
MicroTrak APRS tacker/radio $250
Connectors/cables Misc $20
Parachute Impact reduction $15
Subtotal (One time cost) $550
Balloon Lifting vehicle $90
Helium Lifting gas $200
LiSO2 batteries (x4) Power $70
Total <$1000
The following parts lists outlines an example build for a system capable of measuring, temperature,
pressure, altitude, acceleration, orientation, heading, location, and video, with doubly redundant tracking
mechanisms. The system is capable of data logging as well supporting additional sensors across a range
of communication protocols (SPI, Serial, I2C, One-Wire, ADC, and more...). An additional 3 lbs of
payload could be lifted with the given launch configuration, or an additional 8 lbs, distributed over two
payloads with additional helium.
This budget is highly sensitive to payload weight, since balloon envelope and helium costs
exponentially increase with weight. Based on the table above, subsequent launches would only cost half
the up-front cost, assuming the payload is recovered.
Arduino Programming
The full Arduino source code used by Rocket University can be found in Appendix A. As a brief
explanation, the code can be split into two distinct groups. The header script and setup() function are run
once during power-on. In this section the programmer must import the required libraries to drive
communication and sensors. Next, digital and analog pins from the Arduino are assigned to variables, and
baud rates are chosen for serial communication. The first serial port is used to communicate with the PC
over USB, and second is used to communicate with the dedicated Razor Inertial Measurement Unit (IMU),
and the third and final serial port communicates with the GPS module. The rest of the code resides in the
loop() function that runs repeatedly (and synchronously) until the Arduino is powered off. Each sensor is
broken into a sub-function, which reads and logs the data. These functions can do basic calculations on the
readings in real time, and format the data to be logged to the SD card every process loop.
$1,500+ Launches
The second avionics design is geared towards more advanced payloads requiring more challenging
requirements. Although the sensors involved are comparable to the previous price tier, this COTS system
requires much less configuration out-of-the-box. As a drawback, it’s a much more complicated system to
extend towards custom applications. Drawing from the amateur unmanned aerial vehicle community, it
excels when requirements include constant two-way telemetry, remote control, asynchronous sensor
sampling, sensor fusion, and even autonomous flight. The system is centered on the Pixhawk open-source
UAV ecosystem and a breakdown of costs is shown in Table 3.
NASA/TM—2016-219148 8
TABLE 3.—LAUNCH 2 PRICE BREAKDOWN
Part Function Cost
Pixhawk Flight controller $240
microSD card (32 GB) Data storage $20
RFD900 Radio transciever $200
uBlox NEO-M8N GPS and antenna $90
Action video cam Video sensor $200
Spot tracker Back-up tracker $75
Rubber duck and yagi Flight/ground antenna $60
PMAD Power distribution $80
Connectors/cables Misc $30
Parachute Impact reduction $16
Subtotal (One time cost) $1,000
Balloon Lifting vehicle $90
Helium Lifting gas $200
LiSO2 batteries (x6) Power $100
Total <$1400
Pixhawk Programming
Programming of the Pixhawk is largely beyond the scope of this paper. The C++ code runs on a real-
time-operating-system (RTOS) called Nuttx. Not only is the processer much faster than the Arduino, but
also the flight controller performs many operations asynchronously allowing the system to log at a much
higher rate. The Pixhawk is a fully autonomous flight controller right out-of-the-box, but can also be used
simply as a data acquisition and telemetry system if active motor control is not necessary.
Programming requires an understanding of Git version control, C++, and familiarity installing,
editing and running terminal scripts, and compiling source code with provided build chains.
At a minimum it’s recommended to log all data after power on by modifying
ROMFS/px4fmu_common/init.d/rc.logging line 14 to:
sdlog2 start ‐r 10 ‐e ‐b 12 ‐t
NASA/TM—2016-219148 9
Power Management and Distribution
The Power Management and Distribution device (PMAD) is responsible for conditioning and
supplying electrical power from the battery to all electrical subsystems (sensors, avionics, cameras, etc.).
In doing so, it must be able to function over the entire flight profile operation, be designed and built so as
to withstand the harshness of high altitudes, desert environments, and potential high-G loading, offer
protection against electrical faults, whether occurring in a subsystem, the battery, or in the PMAD itself,
and ease of use.
Battery
Electrical
PMA Subsystems
NASA/TM—2016-219148 10
$1,500+ Launches
A more sophisticated PMAD can expand on this topology by extending the number of converters to
offer various voltage and power levels to serve the greater number of loads. A number of assumptions
were made prior to design for this mission: radiation shielding would not be required, current and voltage
ratings for components would exceed, at minimum, 150 percent of the peak operating conditions, the
design would be robust against all load operations, thermals would be passively managed, startup and
recovery-from-fault times would not cause erroneous operation, and that the PMAD be one self-contained
unit with dedicated peripheral terminals for each subsystem. It is advised to create a Power Equipment
List (PEL) to account for the current, voltage, and power needs for each electrical subsystem during the
entire mission profile. This information can be used to determine the component sizing and ratings on the
PMAD. All components chosen were selected for being able to operate over the entire mission
environment in terms of survivability in extreme temperature and pressure.
In addition to the power supply circuitry, the PMAD outlined below has the capability to output, in
real-time, the supply voltage and total load current measurements to a Pixhawk controller. This
information is useful in assessing the power demands of the subsystems and the effects of extreme
environments on their operation.
The PMAD is protected against electrical faults through design. Shorts occurring on any of the
subsystem outputs trigger an output shutdown of the DC/DC converter responsible for supplying that
particular load. The PMAD itself has a fused input to protect against any accidental electrical shorts that
might unexpectedly occur. The battery has a fused output as well and uses internal diodes to eliminate the
potential for cell reversal. Therefore, no emergency shutdown circuitry is required due to the battery’s
own internal protection.
Operator ease-of-use is integrated in the design by addressing how external users interact with the
device. Consideration was given to how the PMAD was integrated, how it could be powered on and off,
and confirmation of power. Keyed connectors were chosen so corresponding connections could only be
made the correct way. Connectors were selected to be mechanically locking or very secure to minimize
the risk of coming separated in flight. Board (and subsystem) power status is indicated using an LED and
power is controlled through a clearly marked rocker switch.
All parts of the PMAD can be found from commercial electronics distributers such as Digikey,
Mouser, or Sparkfun. Circuit design and printed circuit board layout were done using Cadsoft’s EAGLE
design tool (http://www.cadsoftusa.com/). This is a power schematic capture tool that allows complex
electrical design and includes libraries of all basic electrical components as well as many commercial
parts. EAGLE offers users the user the ability to expand on its usefulness by allowing custom code
execution to add functions, unique part creation, and large user community. The layout functionality
allows the user to export all of the most common manufacturing files in use by board houses. The circuit
boards were manufactured by Advanced Circuits (http://www.4pcb.com/).
Figure 7.—PMAD for the final Rocket University flight, approximate length: 12 in.
NASA/TM—2016-219148 11
Data Analysis
Post-processing the results of a flight often involves processing numerous hours of raw sensor data. If
all sensors are not logging to a centralized source, it is important to have a baseline event to properly sync
each source. For example, multiple independent accelerometer sensors can all be synced with a small
‘kick’ before launching. Since every sensor cannot be turned on at the exact same time, this small
acceleration can used to match all sensors up to the same event in time, much like a movie clapperboard.
Post-Processing
Working with extremely large data sources often requires manipulating and ‘cleaning’ data using
table-wide data transformations. Sensors may reset mid-flight, sample at various rates, or momentarily
return invalid values. In order to process data for analysis purposes, it can be necessary to perform string
and float manipulations, interpolations, etc.
While this will vary from project to project, it’s important to be mindful of post-processing tasks
while designing how each sensor reports data. Many sensors report floats even when throwing errors,
making it difficult to search and distinguish between valid and invalid values during post-flight analysis.
This can be avoided by logging errors with easily distinguishable strings or values that can easily be
searched and removed later. It is also vital to timestamp and format all data in a syntax that is easily
parse-able, based on the analysis tool of choice, otherwise it can be impossible to synchronize disparate
logs with hundreds of thousands of entries. Excel, Python, and Matlab are all excellent choices for post
processing. The example source-code used by Rocket University can be found in Appendix A.
Visualization
Even with perfectly synced data, it can be difficult to fully understand or appreciate the data in the
form of a comma separated value (CSV) table. Plotting the data as a time-series can be helpful for
analysis, and more advanced visualizations can be help in grasping the full context.
Processing, (processing.org) is a programming language and development environment designed with
visualization in mind. For this project, it was used to sync video footage with visualized sensor data.
This particular program, shown in Figure 8, displays the accelerations, temperature, speed, altitude,
and orientation in multiple contexts. There is a video component showing a picture- and-picture view of
both camera angles, accelerations plotted as vectors, data shown as raw values, altitude shown both as a
moving graph and overlaid on a map with speed, and a 3D rendering of payload orientation. The source-
code for this visualization can be found in Appendix A. In order to properly sync the data with the video,
all of the data was consolidated into a single table, where data was reported in to a new row every 0.2 sec.
The program embeds the video and syncs the frame-rate with rows of sensor data from a CSV. At 30
frames per second, it reads a new row from the CSV file every 6 frames, updating the display. Playback
controls are also provided, to allow the user to skip to any segment of the video/database. This requires a
video file that starts and stops exactly with the beginning and endpoints of the data file. This way jumping
to the halfway point corresponds to exactly halfway down the CSV file, and halfway through the video.
Data Dissemination
Two recommended services for online data dissemination include Github and Google Fusion Tables.
Github allows for version control of plain text files (code, output) and a repository for any other type of
file. Google fusion tables can be used exclusively for sensor output CSV’s and provides a convenient way
to share and visualize data in a single place, as demonstrated in Figure 9. It is especially usefully for
plotting time series data, and plotting GPS data directly on an interactive map.
NASA/TM—2016-219148 12
Figure 8.—Custom processing visualization based on the data from the payload in Figure 4.
Map data copyright Google 2015.
Figure 9.—Google fusion table (left) speed vs. time (right) GPS path colored based on speed.
Map data copyright Google 2015.
Final Remarks
Balloon payloads offer extremely low-cost scientific platforms. The advent of widely available
inexpensive sensors, computers, and open-source hardware/software has greatly reduced the barrier to
entry for planetary research.
The lightweight, inexpensive sensor packages outlined in this paper can scale to payloads of any size.
These systems were originally intended for passive monitoring systems, however the final avionics
system outlined could be used to control an active descent system.
Balloons have made a resurgence in both commercial and scientific applications. Exciting projects
such as Google Loon are poised to play a large role in extending Internet connectivity to developing
countries, proving that balloons can have significant and impactful real-world applications (Ref. 4).
NASA/TM—2016-219148 13
Appendix A—Source Code
Flight 1
The entire source code can be found on github.
https://github.com/jcchin/ANGEL
Helium Calculator https://github.com/jcchin/BalloonPy
Flight 2
The entire source code can be found on github at:
https://pixhawk.org/dev/quickstart
https://github.com/jcchin/firmware
Processing
The entire source code can be found on github at:
https://github.com/jcchin/ANGEL/tree/master/RAZOR/Processing/Flight1DataVis
NASA/TM—2016-219148 15
Appendix B—Weather Balloon/Payload Launch Inflation Checklist
Parts Lists Inflation
2 Balloons (1 is spare) adjustable wrenches
Helium, 2 tanks (K bottles) pliers
Helium truck rack and rope fish-scale
Pressure Regulator digital scale (w/ spare 9 V battery)
4 – wooden paddles (1’ by 3’, wrapped in paper) tape measure
Latex gloves (6 pairs) Water container (counter balance determination)
Cotton gloves (6 pairs) String (for tying off balloon) 100 lb test Dacron
hose and gas feed adaptor with valve scissors
hose clamps (1 for balloon and 2 for the hose) knife
tarp duct tape
parachute water – in container
big wrench (for regulator, gas feed) wooden spreaders for parachute (if needed)
small balloons for weather check
Balloon Inflation
__________ Attach regulator to He bottle and attach hose,
__________ Prepare water as balance, determine required mass from below
__________ Lay out tarp and balloon so that it is close to the other end of the hose
__________ Attach L-shaped fitting to balloon secure with hose clamp
__________ Attach Fishing scale and weighted water container
__________ Unwrap balloon and layout on tarp, check for kinks/tears
__________ Start filling balloon slowly at first, and continue raising inflation rate until lift matches
water weight. Stretch out balloon on tarp,
__________ Use covered wooden paddles to stabilize balloon from wind drift.
__________ Once inflated, (balloon lift is equal to weight of water container) remove balloon from
inflation assembly, fold over balloon nozzle, tie off with string (leave enough string to
attach payload), wrap with duct tape.
__________ Prepare and launch small helium balloon for wind assessment
__________ Attach payloads.
__________ Arrange payloads such that the line between all elements has no slack.
__________ Release balloon.
NASA/TM—2016-219148 17
References
1. FAA. Overview of small uas notice of proposed rulemaking. http: //www.faa.gov/
regulations_policies/rulemaking/media/ 021515_sUAS_Summary.pdf, February 2015.
2. Leo Bodnar. Balloon flight b-45. http://leobodnar.com/balloons/B-45/ index.html, April 2014.
3. Amsat UK. Solar powered 434 mhz balloon reaches syria. http://amsat-uk. org/2014/04/08/solar-
powered-434-mhz-balloons-launched/, April 2014.
4. Google loon. http://www.google.com/loon/.
NASA/TM—2016-219148 18