Search NASA⌕ Search

SEARCH · Search NASA

Results for “core flight system”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 415 records · Page 23
All sourcesNASA NTRSDOE OSTI
NASA NTRS2019

The Kilopower Space Nuclear Fission Power Reactor

Nuclear fission power offers an attractive alternative to solar electric or radioisotope power systems for certain applications on the Moon, Mars, and deep space science missions. The advantages of independence from solar irradiance, high energy density, and abundance of fuel allow fission power systems to enable novel, high power mission architectures. While NASA has had numerous fission power programs throughout its history, few have gone far beyond the design phase. The recent test campaign called the Kilopower Reactor Using Stirling Technology project (KRUSTY) focused on a low power, kilowatt-scale design for simplicity and reduced cost, with the driving motivation to perform a full nuclear hardware prototype test. Following the successful completion of the KRUSTY nuclear hardware test in March of 2018, NASA has begun the formulation process for a Technology Demonstration Mission (TDM) using the Kilopower reactor technology. In support of NASA's lunar surface initiatives, the Kilopower TDM will target a 1-3 kW fission electric power system that can survive the lunar night and operate for one year. The system will be heavily influenced by the KRUSTY reactor design, using a solid Uranium metal core with high temperature heat pipes and Stirling engine power conversion. During this formulation phase, continued engineering efforts are ongoing to improve heat transfer efficiency in the system, examine fission radiation damage effects, and begin to address the thermal and structural requirements of a Kilopower flight system.

Chaiken, Max↗
NASA NTRS2021

Damage Tolerance of Candidate Sandwich Structure for the Space Launch System (SLS) Payload Adapter Fitting (PAF)

This Technical Memorandum presents results from a damage tolerance study undertaken in support of the payload adapter fitting (PAF) for the Space Launch System (SLS) program at NASA’s Marshall Space Flight Center (MSFC). The study consisted of determining the compression-after-impact (CAI) strength of candidate carbon/epoxy face sheet sandwich structure that has been identified for potential use to manufacture the PAF hardware. Two types of core material that have been considered for use on the PAF structure were used in this study. One was an aluminum honeycomb and the other was a Rohacell foam. Levels of barely visible impact damage (BVID) were determined for the types of sandwich structure tested in this study and this level of damage was used for CAI strength testing. It was found that the honeycomb core sandwich structure failed by face sheet failure and the foam core sandwich structure failed by core shear failure. CAI strength values were normalized by weight of the sandwich structure since lower mass is desirable for this structure.

sandwich structure↗
NASA NTRS2008

Rescue Shuttle Flight Re-Entry: Controlling Astronaut Thermal Exposure

A rescue mission for the STS-125 Hubble Telescope Repair Mission requires reentry from space with 11 crew members aboard, exceeding past cabin thermal load experience and risking crew thermal stress potentially causing cognitive performance and physiological decrements. The space shuttle crew cabin air revitalization system (ARS) was designed to support a nominal crew complement of 4 to 7 crew and 10 persons in emergencies, all in a shirt-sleeve environment. Subsequent to the addition of full pressure suits with individual cooling units, the ARS cannot maintain a stable temperature in the crew cabin during reentry thermal loads. Bulk cabin thermal models, used for rescue mission planning and analysis of crew cabin air, were unable to accurately represent crew workstation values of air flow, carbon dioxide, and heat content for the middeck. Crew temperature models suggested significantly elevated core temperatures. Planning for an STS-400 potential rescue of seven stranded crew utilized computational fluid dynamics (CFD) models to demonstrate inhomogeneous cabin thermal properties and improve analysis compared to bulk models. In the absence of monitoring of crew temperature, heart rate, metabolic rate and incomplete engineering data on the performance of the integrated cooling garment/cooling unit (ICG/CU) at cabin temperatures above 75 degrees F, related systems & models were reevaluated and tests conducted with humans in the loop. Changes to the cabin ventilation, ICU placement, crew reentry suit-donning procedures, Orbiter Program wave-off policy and post-landing power down and crew extraction were adopted. A second CFD and core temperature model incorporated the proposed changes and confirmed satisfactory cabin temperature, improved air distribution, and estimated core temperatures within safe limits. CONCLUSIONS: These changes in equipment, in-flight and post-landing procedures, and policy were implemented for the STS-400 rescue shuttle & will be implemented in any future rescue flights from the International Space Station of stranded shuttle crews.

Gillis, David B.↗
NASA NTRSDate not supplied

NASA's Space Launch System Begins Integration, Stacking in Preparation for Artemis I Launch

The Artemis era of human lunar exploration is nearing take-off as NASA’s new super heavy-lift launch vehicle, the Space Launch System (SLS), begins stack-ing and integration operations in mid-2020 at Kennedy Space Center (KSC) in Florida. With a planned upgrade path to progressively more powerful vehicles and availability in crew and cargo configurations, SLS provides a unique and flexible launch solution to send crew, large-scale infrastructure and robotic probes to deep space. The SLS Block 1 vehicle, the initial variant to fly, is optimized for lunar missions with a proven propulsion system consisting of four liquid hydrogen (LH2)/liquid oxygen (LOX)-fed RS-25 engines and twin five-segment solid rocket boosters (SRBs). The Block 1 vehicle can also be outfitted with an industry-standard 5 m-class payload fairing (the “cargo” configuration) and will launch at least 27 metric tons (t) of mass to trans-lunar injection (TLI). SLS is the backbone of NASA’s Artemis program, which will return the agency’s human spaceflight program to the Moon for the first time since 1972. For the Artemis I mission, SLS will send an uncrewed Orion spacecraft to TLI, where it will enter a distant retrograde lunar orbit and fly 38,000 nmi past the Moon – farther than any spacecraft built for humans has ever traveled. The SLS Block 1 vehicle for Artemis I completed manufacturing in 2019. Several elements, including the upper stage, have been delivered to the Exploration Ground Systems (EGS) program at KSC and are being prepped for integration and stack-ing. The five-segment solid rocket boosters – the largest and most powerful ever built for flight – are also complete. The booster motor segments for the Artemis I flight are scheduled to ship from prime contractor Northrop Grumman’s Utah facilities and begin stacking and integration at KSC in June 2020. The SLS core stage is the largest rocket stage NASA has ever built in terms of volume and height, and includes the avionics and the tanks that feed cryogenic propellant to the four RS-25s (formerly Space Shuttle Main Engines [SSMEs]). They have been modified with an updated controller and nozzle insulation to protect them from the hotter launch environment. The SLS core stage is currently being test-ed at NASA’s Stennis Space Center (SSC) in a series of “green run” tests to verify it meets design and performance requirements. Following the green run test series, which is scheduled to culminate with a full-duration hot-fire of the four RS-25 engines, the core stage will ship to KSC and be stacked between the sol-id rocket boosters in the Vehicle Assembly Building (VAB). Integration of the vehicle will continue with the upper stage, known as the Interim Cryogenic Propulsion Stage (ICPS) and the Launch Vehicle Stage Adapter (LVSA) on the core stage. Another adapter, the Orion Stage Adapter (OSA), connects SLS to Orion and provides housing for 13 6U CubeSat payloads manifested on Artemis I. The CubeSats will be released in deep space after Orion separates from the vehicle, and the flight marks the first ride share opportunity for independent small-sats to deep space. The second major SLS variant to come online, Block 1B, replaces the single-engine ICPS with a four-engine LH2/LOX Exploration Upper Stage (EUS). This more powerful upper stage, along with other vehicle up-grades, will enable the Block 1B vehicle to launch 38-42 t to TLI, depending on crew or cargo configuration. The final evolution of the vehicle, Block 2, will onramp evolved solid rocket boosters to increase mass to TLI to 43-46 t, de-pending on crew or cargo configuration. The Block 1B/Block 2 vehicles can be outfitted with an 8.4 m-diameter payload fairing in 19.1 m or 27.4 m lengths, to provide unprecedented volume for payloads. With the initial Block 1 vehicle completely manufactured and the core stage in final testing before shipping to KSC, the SLS Program and its industry partners have made significant progress manufacturing subsequent vehicles. For the second Block 1 vehicle, the solid rocket motor segments are complete, as are the RS-25 engines with controllers. All five major components of the Artemis II core stage – the forward skirt, LOX and LH2 tanks, intertank and engine section – are manufactured and technicians are installing subsystems at NASA’s rocket factory, Michoud Assembly Facility. The RL-10 engine for the Artemis II ICPS is complete and panels have been machined for its LH2 tank. In addition, panels are machined for the vehicle’s two adapters, with welding scheduled to begin in summer 2020. Flight hard-ware is also in production for the third SLS vehicle, with several booster motor segments cast. The pace of development on the EUS has increased, with the goal to complete Critical Design Review (CDR) in December 2020. Several EUS test rings have been machined at Michoud. The EUS is designed to exe-cute a variety of missions – human spaceflight, deployment of deep-space infra-structure, or high-C3 missions to the outer solar system – with crew and cargo configurations available beginning in the mid-2020s. The near-term goal for the nation’s powerful new space exploration asset, however, is to launch the Arte-mis program, and send the first woman and the next man to the lunar surface. At the Astrodynamics Specialist Conference, the SLS program will update the community on the progress of the initial Block 1 vehicle in final green run test-ing, integration and stacking. In addition, this paper will provide an update to the community on the manufacturing status of subsequent Block 1 and Block 1B vehicles.

Steve Creech↗
NASA NTRS1976

Breadboard CO2 and humidity control system

A regenerable CO2 and humidity control system is being developed for potential use on shuttle as an alternate to the baseline lithium hydroxide (LiOH)/condensing heat exchanger system. The system utilizes a sorbent material, designated HS-C, to adsorb CO2 and water vapor from the cabin atmosphere. The material is regenerated by exposing it to space vacuum. A half-size breadboard system, utilizing a flight representative HS-C canister, was designed, built, and performance tested to shuttle requirements for total CO2 and total humidity removal. The use of a new chemical matrix material allowed significant optimization of the system design by packing the HS-C chemical into the core of a heat exchanger which is manifolded to form two separate and distinct beds. Breadboard system performance was proven by parametric testing and simulated mission testing over the full range of shuttle crew sizes and metabolic loadings. Vacuum desorption testing demonstrated considerable savings in previously projected shuttle vacuum duct sizing.

Boehm, A. M.↗
NASA NTRS2010

Smart Power Supply for Battery-Powered Systems

A power supply for battery-powered systems has been designed with an embedded controller that is capable of monitoring and maintaining batteries, charging hardware, while maintaining output power. The power supply is primarily designed for rovers and other remote science and engineering vehicles, but it can be used in any battery alone, or battery and charging source applications. The supply can function autonomously, or can be connected to a host processor through a serial communications link. It can be programmed a priori or on the fly to return current and voltage readings to a host. It has two output power busses: a constant 24-V direct current nominal bus, and a programmable bus for output from approximately 24 up to approximately 50 V. The programmable bus voltage level, and its output power limit, can be changed on the fly as well. The power supply also offers options to reduce the programmable bus to 24 V when the set power limit is reached, limiting output power in the case of a system fault detected in the system. The smart power supply is based on an embedded 8051-type single-chip microcontroller. This choice was made in that a credible progression to flight (radiation hard, high reliability) can be assumed as many 8051 processors or gate arrays capable of accepting 8051-type core presently exist and will continue to do so for some time. To solve the problem of centralized control, this innovation moves an embedded microcontroller to the power supply and assigns it the task of overseeing the operation and charging of the power supply assets. This embedded processor is connected to the application central processor via a serial data link such that the central processor can request updates of various parameters within the supply, such as battery current, bus voltage, remaining power in battery estimations, etc. This supply has a direct connection to the battery bus for common (quiescent) power application. Because components from multiple vendors may have differing power needs, this supply also has a secondary power bus, which can be programmed a priori or on-the-fly to boost the primary battery voltage level from 24 to 50 V to accommodate various loads as they are brought on line. Through voltage and current monitoring, the device can also shield the charging source from overloads, keep it within safe operating modes, and can meter available power to the application and maintain safe operations.

Krasowski, Michael J.↗
NASA NTRS2011

The Planning Execution Monitoring Architecture

The Planning Execution Monitoring (PEM) architecture is a design concept for developing autonomous cockpit command and control software. The PEM architecture is designed to reduce the operations costs in the space transportation system through the use of automation while improving safety and operability of the system. Specifically, the PEM autonomous framework enables automatic performance of many vehicle operations that would typically be performed by a human. Also, this framework supports varying levels of autonomous control, ranging from fully automatic to fully manual control. The PEM autonomous framework interfaces with the core flight software to perform flight procedures. It can either assist human operators in performing procedures or autonomously execute routine cockpit procedures based on the operational context. Most importantly, the PEM autonomous framework promotes and simplifies the capture, verification, and validation of the flight operations knowledge. Through a hierarchical decomposition of the domain knowledge, the vehicle command and control capabilities are divided into manageable functional "chunks" that can be captured and verified separately. These functional units, each of which has the responsibility to manage part of the vehicle command and control, are modular, re-usable, and extensible. Also, the functional units are self-contained and have the ability to plan and execute the necessary steps for accomplishing a task based upon the current mission state and available resources. The PEM architecture has potential for application outside the realm of spaceflight, including management of complex industrial processes, nuclear control, and control of complex vehicles such as submarines or unmanned air vehicles.

Wang, Lui↗
NASA NTRS2019

"Sensor Web Evolution - Webs of Webs for NASA Science - Focus on small Uninhabited Aerial Systems (sUAS)"

This paper will describe the evolution of information collection, derivation and delivery mechanisms in webs of NASA sensor webs, with a focus on recent advancements in small Uninhabited Aerial Systems (sUAS). I will discuss the movement to "Fog Computing", also known as Edge Computing. Fog Computing facilitates the distribution of common operations and networking between edge devices and cloud computing facilities, optimizing the production of actionable intelligence. Initially, sUASs utilized onboard data collection as standard, with minimal data downloaded directly. Information products were derived in conventional computational environments, generally desk top computers, and information products made available to the Science Community in weeks or months. With the increased availability, and increasingly lower costs, of beyond line of sight (BLOS) satellite based communication, transmission rates and data volumes increased, and processing migrated to Cloud based services. Contemporary sUASs are moving some of that information product derivation to on vehicle services, and are creating a distributed Cloud/Fog environment. I will describe the technological advances that have made this possible, including low power multi-core Central Processing Units (CPU), and, more recently, the availability of high end Graphical Processing Units (GPU) that consume only a few watts. Intelligent system software, leveraging these hardware advances, finally allows for information product generation on-board, rather than simple data collection. Additionally, intelligent flight control systems now support mutual vehicle to vehicle collaboration, allowing sUASs to create ad-hoc sensor webs on demand, as required. Also discussed will be the lessons learned by the Authors' development of data systems for NASA's large High Altitude Long Endurance (HALE) UASs like Predator and Global Hawk, and how those lessons are being applied to sUAS development. This paper will focus on application, rather a deep dive into the technology, and will highlight improving data management through these new technologies.

Sensor Web↗
NASA NTRSDate not supplied

UASs in the VOG/Edge/FOG Sensor Web Environment

This paper will describe the evolution of information collection, derivation and delivery mechanisms in sensor webs utilizing Uninhabited Aerial Systems (UAS).We will discuss the movement to "Fog Computing", also known as Edge Computing. Fog Computing facilitates the distribution of common operations and networking between edge devices and cloud computing facilities, optimizing the production of actionable intelligence. Initially, UASs utilized onboard data collection as standard, with minimal data downloaded directly. Information products were derived in conventional computational environments, generally desk top computers, and information products made available to the Science Community in weeks or months. With the increased availability, and increasingly lower costs, of beyond line of sight (BLOS) satellite based communication, transmission rates and data volumes increased, and processing migrated to Cloud based services. Contemporary UASs are moving some of that information product derivation to on vehicle services, and are creating a distributed Cloud/Fog environment. The Author will describe the technological advances that have made this possible, including low power multi-core Central Processing Units (CPU), and, more recently, the availability of high end Graphical Processing Units (GPU) that consume only a few watts. Intelligent system software, leveraging these hardware advances, finally allows for information product generation on-board, rather than simple data collection. Additionally, intelligent flight control systems now support mutual vehicle to vehicle collaboration, allowing UASs to create ad-hoc sensor webs on demand, as required. Also discussed will be the lessons learned by the Authors' development of data systems for NASA's large High Altitude Long Endurance (HALE) UASs like Predator and Global Hawk, and how those lessons are being applied to other UAS development This paper will focus on applications, rather a deep dive into the technology, and will highlight improving data management through these new technologies.

UAS↗
NASA NTRS2002

Ethernet for Space Flight Applications

NASA's Goddard Space Flight Center (GSFC) is adapting current data networking technologies to fly on future spaceflight missions. The benefits of using commercially based networking standards and protocols have been widely discussed and are expected to include reduction in overall mission cost, shortened integration and test (I&T) schedules, increased operations flexibility, and hardware and software upgradeability/scalability with developments ongoing in the commercial world. The networking effort is a comprehensive one encompassing missions ranging from small University Explorer (UNEX) class spacecraft to large observatories such as the Next Generation Space Telescope (NGST). Mission aspects such as flight hardware and software, ground station hardware and software, operations, RF communications, and security (physical and electronic) are all being addressed to ensure a complete end-to-end system solution. One of the current networking development efforts at GSFC is the SpaceLAN (Spacecraft Local Area Network) project, development of a space-qualifiable Ethernet network. To this end we have purchased an IEEE 802.3-compatible 10/100/1000 Media Access Control (MAC) layer Intellectual Property (IP) core and are designing a network node interface (NNI) and associated network components such as a switch. These systems will ultimately allow the replacement of the typical MIL-STD-1553/1773 and custom interfaces that inhabit most spacecraft. In this paper we will describe our current Ethernet NNI development along with a novel new space qualified physical layer that will be used in place of the standard interfaces. We will outline our plans for development of space qualified network components that will allow future spacecraft to operate in significant radiation environments while using a single onboard network for reliable commanding and data transfer. There will be a brief discussion of some issues surrounding system implications of a flight Ethernet. Finally, we will show an onboard network architecture for a proposed new mission using Ethernet for science data transport.

Webb, Evan↗
NASA NTRS2017

Flight Deck Surface Trajectory-Based Operations (STBO): A Four-Dimensional Trajectory (4DT) Simulation

Within human factors there is burgeoning interest in the Human-Autonomy Teaming (HAT) concept as away to address the challenges of interacting with complex, increasingly autonomous systems. The HAT concept comes out of an aspiration to interact with increasingly autonomous automation as a team member, rather than simply use automation as a tool. The authors, and others, have proposed core tenets for HAT that include bi-directional communication, automation and system transparency, and advanced coordination between human and automated teammates via predefined, dynamic task sequences known as plays (Shively et al., 2017). It is believed that, with proper implementation, HAT should foster appropriate teamwork, thus increasing trust and reliance on the system, which in turn will reduce workload, increase situation awareness, and improve performance. To this end, HAT has been demonstrated and/or studied in multiple applications including search and rescue operations (Nourbakhsh et al., 2005), healthcare and medicine (Tsui Yanco, 2007), autonomous vehicles (Parasuraman, Barnes, Cosenzo, Mulgund, 2007), photography (Lachter, Brandt, Sadler, Shively, in press), and aviation (Shively et al., in press). The current paper presents one such effort to apply HAT. It details the design of a R-HAT Agent developed as part of a NASA Research Agreement awarded to Human-Autonomy Teaming Solutions Inc. (HATS Inc), and developed in collaboration with the Human-Autonomy Teaming Laboratory at NASA Ames Research Center. The role of this Agent is to mediate interaction between the automation and the human operator of an advanced ground dispatch station, with this mediation based upon previously mentioned core tenets for HAT and the many lessons learned from the HAT research literature. This dispatch station was developed to support a NASA project investigating a concept called Reduced Crew Operations (RCO; Lachter, Brandt, Battiste, Matessa, Johnson, in press). Part of the RCO concept involves a ground operator providing enhanced support to a large number of aircraft with a single pilot on the flight deck. When assisted by the Agent, operators can monitor and support or manage a large number of aircraft and use plays to respond in real-time to complicated, workload-intensive events (e.g., an airport closure). A play is a plan that encapsulates goals, tasks, and a task allocation strategy appropriate for a particular situation. In the current implementation, when a play is initiated by a user, the Agent determines what tasks need to be done and has the ability to autonomously execute them (e.g., determining diversion options and uplinking new routes to aircraft) when it is safe and appropriate. The R-HAT Agent has been designed to both support end users and research in RCO and HAT. Additionally, the Agent and its underlying architecture were developed with generalizability in mind as a modular piece of software applicable outside of RCO aviation in domains such as those mentioned above. This paper will also discuss future further development and testing of the R-HAT Agent.

Bakowski, Deborah L.↗
NASA NTRS1977

Orbital construction demonstration study. Volume 1: Executive summary

A conceptual design and program plan for an Orbital Construction Demonstration Article (OCDA), that can be used for technology growth and verification, and as the construction facility for a variety of large structures is presented. The OCDA design includes a large work platform, a rotating manipulator boom, a 250 kw solar array, and a core module of subsystems with a total mass of 37,093 kg, that can be assembled in three shuttle flights. An analysis of OCDA continued utility potential indicates that a shuttle tended platform with 250 kW of power can effectively be used to construct highly beneficial antenna systems and large demonstration articles that advance solar power satellite technologies. The construction of 100 m parabolic reflectors for use as a radiometer for measuring soil moisture and water salinity was found to be within the capabilities of OCDA concept. With 252 fixed beams for high population centers, and 16 scanning beams for rural areas, the antenna has the potential to significantly improve U.S. space based communications systems. The OCDA, that is slightly increased in size, was found adequate to build a large 2 MW solar array which, when coupled to a transmit antenna, demonstrate power transfer from space to ground.

Source record↗
NASA NTRS1993

Airborne derivation of microburst alerts from ground-based Terminal Doppler Weather Radar information: A flight evaluation

An element of the NASA/FAA windshear program is the integration of ground-based microburst information on the flight deck, to support airborne windshear alerting and microburst avoidance. NASA conducted a windshear flight test program in the summer of 1991 during which airborne processing of Terminal Doppler Weather Radar (TDWR) data was used to derive microburst alerts. Microburst information was extracted from TDWR, transmitted to a NASA Boeing 737 in flight via data link, and processed to estimate the windshear hazard level (F-factor) that would be experienced by the aircraft in each microburst. The microburst location and F-factor were used to derive a situation display and alerts. The situation display was successfully used to maneuver the aircraft for microburst penetrations, during which atmospheric 'truth' measurements were made. A total of 19 penetrations were made of TDWR-reported microburst locations, resulting in 18 airborne microburst alerts from the TDWR data and two microburst alerts from the airborne reactive windshear detection system. The primary factors affecting alerting performance were spatial offset of the flight path from the region of strongest shear, differences in TDWR measurement altitude and airplane penetration altitude, and variations in microburst outflow profiles. Predicted and measured F-factors agreed well in penetrations near microburst cores. Although improvements in airborne and ground processing of the TDWR measurements would be required to support an airborne executive-level alerting protocol, the practicality of airborne utilization of TDWR data link data has been demonstrated.

Hinton, David A.↗
NASA NTRS2012

Virtual Machine Language 2.1

VML (Virtual Machine Language) is an advanced computing environment that allows spacecraft to operate using mechanisms ranging from simple, time-oriented sequencing to advanced, multicomponent reactive systems. VML has developed in four evolutionary stages. VML 0 is a core execution capability providing multi-threaded command execution, integer data types, and rudimentary branching. VML 1 added named parameterized procedures, extensive polymorphism, data typing, branching, looping issuance of commands using run-time parameters, and named global variables. VML 2 added for loops, data verification, telemetry reaction, and an open flight adaptation architecture. VML 2.1 contains major advances in control flow capabilities for executable state machines. On the resource requirements front, VML 2.1 features a reduced memory footprint in order to fit more capability into modestly sized flight processors, and endian-neutral data access for compatibility with Intel little-endian processors. Sequence packaging has been improved with object-oriented programming constructs and the use of implicit (rather than explicit) time tags on statements. Sequence event detection has been significantly enhanced with multi-variable waiting, which allows a sequence to detect and react to conditions defined by complex expressions with multiple global variables. This multi-variable waiting serves as the basis for implementing parallel rule checking, which in turn, makes possible executable state machines. The new state machine feature in VML 2.1 allows the creation of sophisticated autonomous reactive systems without the need to develop expensive flight software. Users specify named states and transitions, along with the truth conditions required, before taking transitions. Transitions with the same signal name allow separate state machines to coordinate actions: the conditions distributed across all state machines necessary to arm a particular signal are evaluated, and once found true, that signal is raised. The selected signal then causes all identically named transitions in all present state machines to be taken simultaneously. VML 2.1 has relevance to all potential space missions, both manned and unmanned. It was under consideration for use on Orion.

Riedel, Joseph E.↗
NASA NTRS1977

Evaluation of the in-flight noise signature of a 32-chute suppressor nozzle: Acoustic data report

Outdoor static and 40 x 80 FT wind tunnel tests of the J79-15 engine/nacelle system with the conic nozzle and 32-chute exhaust suppressor were conducted to acquire the data necessary to evaluate the simulated in-flight signature of an engine-size 32-chute exhaust nozzle suppressor using the 40 x 80 ft wind tunnel and to study possible engine core noise contamination of the jet signature. The tests are described and and a sampling of the data acquired is presented. Included are aero performance summaries, as-measured and composite 1/3 OBSPL spectra for the 70 ft sideline high and low mics from the outdoor static tests, sideline traverse spectra and internal noise measurements from both the outdoor static and the 40 x 80 ft wind tunnel tests.

Moore, M. T.↗
NASA NTRS2017

Electrically Heated Testing of the Kilowatt Reactor Using Stirling Technology (KRUSTY) Experiment Using a Depleted Uranium Core

The Kilopower project aims to develop and demonstrate scalable fission-based power technology for systems capable of delivering 110 kW of electric power with a specific power ranging from 2.5 - 6.5 Wkg. This technology could enable high power science missions or could be used to provide surface power for manned missions to the Moon or Mars. NASA has partnered with the Department of Energys National Nuclear Security Administration, Los Alamos National Labs, and Y-12 National Security Complex to develop and test a prototypic reactor and power system using existing facilities and infrastructure. This technology demonstration, referred to as the Kilowatt Reactor Using Stirling TechnologY (KRUSTY), will undergo nuclear ground testing in the summer of 2017 at the Nevada Test Site. The 1 kWe variation of the Kilopower system was chosen for the KRUSTY demonstration. The concept for the 1 kWe flight system consist of a 4 kWt highly enriched Uranium-Molybdenum reactor operating at 800 degrees Celsius coupled to sodium heat pipes. The heat pipes deliver heat to the hot ends of eight 125 W Stirling convertors producing a net electrical output of 1 kW. Waste heat is rejected using titanium-water heat pipes coupled to carbon composite radiator panels. The KRUSTY test, based on this design, uses a prototypic highly enriched uranium-molybdenum core coupled to prototypic sodium heat pipes. The heat pipes transfer heat to two Advanced Stirling Convertors (ASC-E2s) and six thermal simulators, which simulate the thermal draw of full scale power conversion units. Thermal simulators and Stirling engines are gas cooled. The most recent project milestone was the completion of non-nuclear system level testing using an electrically heated depleted uranium (non-fissioning) reactor core simulator. System level testing at the Glenn Research Center (GRC) has validated performance predictions and has demonstrated system level operation and control in a test configuration that replicates the one to be used at the Device Assembly Facility (DAF) at the Nevada National Security Site. Fabrication, assembly, and testing of the depleted uranium core has allowed for higher fidelity system level testing at GRC, and has validated the fabrication methods to be used on the highly enriched uranium core that will supply heat for the DAF KRUSTY demonstration.

Briggs, Maxwell H.↗
NASA NTRS2005

Trial by Fire

The NASa/ATK Thiokol space shuttle solid rocket motor program has doubled ground test firings and enhanced manufacturing quality and process control to increase safety for Discovery's return to flight. There are a number of places where we've strengthened our engineering and our processes, says Mike Kahn, ATK Thiokol vice president of space launch systems. Protecting the booster against corrosion in the humid Florida environment is one area that has been addressed. Since the loss of Columbia, ATK Thiokol and the Marshall Space Flight Center have completely reevaluated the shuttle solid rocket motor's design certification and found no major problems, Kahn said. The Thiokol solid motors did not play a role in the 2003 Columbia accident, but the motor's older field joint design (since replaced) was the primary cause of the 1986 Challenger accident that killed seven astronauts. The 129 X 12-ft. ATK Thiokol reusable solid rocket motor forms the core of the shuttle's two solid rocket boosters (SRBs). United Space Alliance (USA) has overall responsibility for the booster's nose-mounted systems such as recovery parachutes and aft-mounted thrust vector control systems that increase the length to 149 ft. USA and its subcontractors have also reaffirmed quality control on systems such as the booster's Hamilton Sundstrand hydraulic power units for critical thrust vector control. And to ensure greater safeguards against booster debris jeopardizing the orbiter, a bolt-catcher system to restrain the large bolts, severed at booster separation, was also redesigned.

Covault, Craig↗
NASA NTRS1993

Mongoose: Creation of a Rad-Hard MIPS R3000

This paper describes the development of a 32 Bit, full MIPS R3000 code-compatible Rad-Hard CPU, code named Mongoose. Mongoose progressed from contract award, through the design cycle, to operational silicon in 12 months to meet a space mission for NASA. The goal was the creation of a fully static device capable of operation to the maximum Mil-883 derated speed, worst-case post-rad exposure with full operational integrity. This included consideration of features for functional enhancements relating to mission compatibility and removal of commercial practices not supported by Rad-Hard technology. 'Mongoose' developed from an evolution of LSI Logic's MIPS-I embedded processor, LR33000, code named Cobra, to its Rad-Hard 'equivalent', Mongoose. The term 'equivalent' is used to infer that the core of the processor is functionally identical, allowing the same use and optimizations of the MIPS-I Instruction Set software tool suite for compilation, software program trace, etc. This activity was started in September of 1991 under a contract from NASA-Goddard Space Flight Center (GSFC)-Flight Data Systems. The approach affected a teaming of NASA-GSFC for program development, LSI Logic for system and ASIC design coupled with the Rad-Hard process technology, and Harris (GASD) for Rad-Hard microprocessor design expertise. The program culminated with the generation of Rad-Hard Mongoose prototypes one year later.

Lincoln, Dan↗