SEARCH · Search NASA
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.
Routines provided for common scalar, vector, matrix, and quaternion operations. Computer program extends Ada programming language to include linear-algebra capabilities similar to HAS/S programming language. Designed for such avionics applications as software for Space Station.
Experience and knowledge gained from ongoing maintenance of Space Shuttle Flight Software and new development projects including Cockpit Avionics Upgrade are applied to projected needs of the National Space Exploration Vision through Spiral 2. Lessons learned from these current activities are applied to create a sustainable, reliable model for development of critical software to support Project Constellation. This presentation introduces the technologies, methodologies, and infrastructure needed to produce and sustain high quality software. It will propose what is needed to support a Vision for Space Exploration that places demands on the innovation and productivity needed to support future space exploration. The technologies in use today within FSW development include tools that provide requirements tracking, integrated change management, modeling and simulation software. Specific challenges that have been met include the introduction and integration of Commercial Off the Shelf (COTS) Real Time Operating System for critical functions. Though technology prediction has proved to be imprecise, Project Constellation requirements will need continued integration of new technology with evolving methodologies and changing project infrastructure. Targets for continued technology investment are integrated health monitoring and management, self healing software, standard payload interfaces, autonomous operation, and improvements in training. Emulation of the target hardware will also allow significant streamlining of development and testing. The methodologies in use today for FSW development are object oriented UML design, iterative development using independent components, as well as rapid prototyping . In addition, Lean Six Sigma and CMMI play a critical role in the quality and efficiency of the workforce processes. Over the next six years, we expect these methodologies to merge with other improvements into a consolidated office culture with all processes being guided by automated office assistants. The infrastructure in use today includes strict software development and configuration management procedures, including strong control of resource management and critical skills coverage. This will evolve to a fully integrated staff organization with efficient and effective communication throughout all levels guided by a Mission-Systems Architecture framework with focus on risk management and attention toward inevitable product obsolescence. This infrastructure of computing equipment, software and processes will itself be subject to technological change and need for management of change and improvement,
The X2000 Program is a technology development program that will provide next generation avionics for missions to deep space. The goal of the X2000 Program is to develop revolutionary flight and ground systems which can be replicated by missions at a low cost, affording timely new science and mission opportunities to investigators and institutions.
Project Constellation implements NASA's vision for space exploration to expand human presence in our solar system. The engineering focus of this project is developing a system of systems architecture. This architecture allows for the incremental development of the overall program. Systems can be built and connected in a "Lego style" manner to generate configurations supporting various mission objectives. The development of the avionics or control systems of such a massive project will result in concurrent engineering. Also, each system will have software and the need to communicate with other (possibly heterogeneous) systems. Fortunately, this design problem has already been solved during the creation and evolution of systems such as the Internet and the Department of Defense's successful effort to standardize distributed simulation (now IEEE 1516). The solution relies on the use of a standard layered software framework and a communication protocol. A standard framework and communication protocol is suggested for the development and maintenance of Project Constellation systems. The ARINC 653 standard is a great start for such a common software framework. This paper proposes a common system software framework that uses the Real Time Publish/Subscribe protocol for framework-to-framework communication to extend ARINC 653. It is highly recommended that such a framework be established before development. This is important for the success of concurrent engineering. The framework provides an infrastructure for general system services and is designed for flexibility to support a spiral development effort.
A novel mechanism, the Active Mass Translator (AMT), has been developed for the NASA Near Earth Asteroid (NEA) Scout mission to autonomously manage the spacecraft momentum. The NEA Scout CubeSat will launch as a secondary payload onboard Exploration Mission 1 of the Space Launch System. To accomplish its mission, the CubeSat will be propelled by an 86 square-meter solar sail during its two-year journey to reach asteroid 1991VG. NEA Scout's primary attitude control system uses reaction wheels for holding attitude and performing slew maneuvers, while a cold gas reaction control system performs the initial detumble and early trajectory correction maneuvers. The AMT control system requirements, feedback architecture, and control performance will be presented. The AMT reduces the amount of reaction control propellant needed for momentum management and allows for smaller capacity reaction wheels suitable for the limited 6U spacecraft volume. The reduced spacecraft mass allows higher in-space solar sail acceleration, thus reducing time-of-flight. The reduced time-of-flight opens the range of possible missions, which is limited by the lifetime of typical non-radiation tolerant CubeSat avionics exposed to the deep-space environment.
During their brief flight, the space shuttle solid rocket boosters (SRBs) experience a severe environment. This environment in most cases is unknown. When the design engineers believe they understand the environments, something new occurs. For example, at water impact several SRBs have sustained noticeable structural damage. The severity of the damage is usually dependent upon the waves that the SRB encounter at splashdown. The space shuttle is presently scheduled to fly until 2030. To support the shuttle flight schedule, the avionics on the SRB's will need to be upgraded. The environments on the different sections of the SRB will need to be defined more completely to properly qualify the avionics for multiple flights. The combination of new avionics systems and unknown flight environments led Marshall Space Flight Center's (MSFC) SRB Project Office to request the Science and Engineering (S&E) Directorate to develop a stand-alone data acquisition system that could collect data from any area of the booster. The Enhanced Data Acquisition System (EDAS) was developed to meet this request. However, the EDAS has some technical drawbacks that needed resolved. To answer the EDAS problems, the SRB Project Office has funded MSFC's Avionics Department to begin investigating a new vehicle health monitoring (VHM) system. The major requirements are the system shall have 64 channels, have programmable sample rates up to 10,000 samples per second, have sufficient memory for a twenty minute flight and not interfere with existing operational flight avionics hardware. This paper will describe the effort to develop a VHM system that can meet the SRB requirements.
Building on the heritage of the Saturn and Space Shuttle Programs for the Design, Development, Test, and Evaluation (DDT and E) of avionics and software for NASA's Ares I Crew Launch Vehicle (CLV), the Ares I Upper Stage Element is a vital part of the Constellation Program's transportation system. The Upper Stage Element's Avionics Subsystem is actively proceeding toward its objective of delivering a flight-certified Upper Stage Avionics System for the Ares I CLV.
The initial goals of the Space Shuttle Program required that the avionics and software systems blaze new trails in advancing avionics system technology. Many of the requirements placed on avionics and software were accomplished for the first time on this program. Examples include comprehensive digital fly-by-wire technology, use of a digital databus for flight critical functions, fail operational/fail safe requirements, complex automated redundancy management, and the use of a high-order software language for flight software development. In order to meet the operational and safety goals of the program, the Space Shuttle software had to be extremely high quality, reliable, robust, reconfigurable and maintainable. To achieve this, the software development team evolved a software process focused on continuous process improvement and defect elimination that consistently produced highly predictable and top quality results, providing software managers the confidence needed to sign each Certificate of Flight Readiness (COFR). This process, which has been appraised at Capability Maturity Model (CMM)/Capability Maturity Model Integration (CMMI) Level 5, has resulted in one of the lowest software defect rates in the industry. This paper will present an overview of the evolution of the Primary Avionics Software System (PASS) project and processes over thirty years, an argument for strong statistical control of software processes with examples, an overview of the success story for identifying and driving out errors before flight, a case study of the few significant software issues and how they were either identified before flight or slipped through the process onto a flight vehicle, and identification of the valuable lessons learned over the life of the project.
Over the years there have been several occurrences of damage to Space Shuttle Orbiter cold plates during removal and replacement of avionics boxes. Thus a process improvement team was put together to determine ways to prevent these kinds of damage. From this effort there were many solutions including, protective covers, training, and improved operations instructions. The focus of this paper is to explain the cold plate damage problem and the corrective actions for preventing future damage to aerospace avionics cold plate designs.
The problem to be addressed in this paper is to explore how the use of Soft Computing Technologies (SCT) could be employed to improve overall vehicle system safety, reliability, and rocket engine performance by development of a qualitative and reliable engine control system (QRECS). Specifically, this will be addressed by enhancing rocket engine control using SCT, innovative data mining tools, and sound software engineering practices used in Marshall's Flight Software Group (FSG). The principle goals for addressing the issue of quality are to improve software management, software development time, software maintenance, processor execution, fault tolerance and mitigation, and nonlinear control in power level transitions. The intent is not to discuss any shortcomings of existing engine control methodologies, but to provide alternative design choices for control, implementation, performance, and sustaining engineering, all relative to addressing the issue of reliability. The approaches outlined in this paper will require knowledge in the fields of rocket engine propulsion (system level), software engineering for embedded flight software systems, and soft computing technologies (i.e., neural networks, fuzzy logic, data mining, and Bayesian belief networks); some of which are briefed in this paper. For this effort, the targeted demonstration rocket engine testbed is the MC-1 engine (formerly FASTRAC) which is simulated with hardware and software in the Marshall Avionics & Software Testbed (MAST) laboratory that currently resides at NASA's Marshall Space Flight Center, building 4476, and is managed by the Avionics Department. A brief plan of action for design, development, implementation, and testing a Phase One effort for QRECS is given, along with expected results. Phase One will focus on development of a Smart Start Engine Module and a Mainstage Engine Module for proper engine start and mainstage engine operations. The overall intent is to demonstrate that by employing soft computing technologies, the quality and reliability of the overall scheme to engine controller development is further improved and vehicle safety is further insured. The final product that this paper proposes is an approach to development of an alternative low cost engine controller that would be capable of performing in unique vision spacecraft vehicles requiring low cost advanced avionics architectures for autonomous operations from engine pre-start to engine shutdown.
The results of a study to analyze, design, and evaluate guidance and control systems are presented that start at an altitude of about 100,000 feet and bring the unpowered space shuttle orbiters to a precision horizontal landing. The systems under consideration included fully automatic versions which involve no pilot participation as well as various manual configurations that provide combinations of displays and control augmentation which permit the pilot to control the vehicle to a successful landing. Two classes of vehicles were studied: the low cross range or straight-wing orbiter and the high cross range or delta-wing (delta body) orbiter. The recommended navigation, guidance and control system is shown to be compatible with realistic physical constraints that would exist in space shuttlecraft and to be consistent with the 1971 avionics equipment state of the art. Aircraft capable of aerodynamically simulating the various candidate space shuttlecraft in their unpowered, terminal area descent were investigated, and flight test recommendations, including system mechanizations, are made.
The Solar Array Module Plasma Interactions Experiment (SAMPIE) is a flight experiment that flew on the Space Shuttle Columbia (STS-62) in March 1994, as part of the OAST-2 mission. The overall objective of SAMPIE was to determine the adverse environmental interactions within the space plasma of low earth orbit (LEO) on modern solar cells and space power system materials which are artificially biased to high positive and negative direct current (DC) voltages. The two environmental interactions of interest included high voltage arcing from the samples to the space plasma and parasitic current losses. High voltage arcing can cause physical damage to power system materials and shorten expected hardware life. parasitic current losses can reduce power system efficiency because electric currents generated in a power system drain into the surrounding plasma via parasitic resistance. The flight electronics included two programmable high voltage DC power supplies to bias the experiment samples, instruments to measure the surrounding plasma environment in the STS cargo bay, and the on-board data acquisition system (DAS). The DAS provided in-flight experiment control, data storage, and communications through the Goddard Space Flight Center (GSFC) Hitchhiker flight avionics to the GSFC Payload Operations Control Center (POCC). The DAS and the SAMPIE POCC computer systems were designed for telescience operations; this paper will focus on the experiences of the SAMPIE team regarding telescience development and operations from the GSFC POCC during STS-62. The SAMPIE conceptual development, hardware design, and system verification testing were accomplished at the NASA Lewis Research Center (LeRC). SAMPIE was developed under the In-Space Technology Experiment Program (IN-STEP), which sponsors NASA, industry, and university flight experiments designed to enable and enhance space flight technology. The IN-STEP Program is sponsored by the Office of Space Access and Technology (OSAT).
Within the past few years, there has been a renewed interest in reusability as it applies to space flight hardware. Commercial companies such as Space Exploration Technologies Corporation (SpaceX), Blue Origin, and United Launch Alliance (ULA) are pursuing reusable hardware. Even foreign companies are pursuing this option. The Indian Space Research Organization (ISRO) launched a reusable space plane technology demonstrator and Airbus Defense and Space is planning to recover the main engines and avionics from its Advanced Expendable Launcher with Innovative engine Economy [1] [2]. To date, the Space Shuttle remains as the only Reusable Launch (RLV) to have flown repeated missions and the Space Shutte Main Engine (SSME) is the only demonstrated reusable engine. Whether the hardware being considered for reuse is a launch vehicle (fully reusable), a first stage (partially reusable), or a booster engine (single component), the overall governing process is the same; it must be recovered and recertified for flight. Therefore, there is a need to identify the key factors in determining the reusability of flight hardware. This paper begins with defining reusability to set the context, addresses the significance of reuse, and discusses areas that limit successful implementation. Finally, this research identifies the factors that should be considered when incorporating reuse.
A model of organization and management of Space Shuttle data is proposed. Shuttle avionics software is parametrically altered by a reconfiguration process for each flight. As the flight rate approaches an operational level, current methods of data management would become increasingly complex. An alternative method is introduced, using modularized standard data, and its implications for data collection, integration, validation, and reconfiguration processes are explored. Information modules are cataloged for later use, and may be combined in several levels for maintenance. For each flight, information modules can then be selected from the catalog at a high level. These concepts take advantage of the reusability of Space Shuttle information to reduce the cost of reconfiguration as flight experience increases.
In-Space Manufacturing (ISM) centers around NASA’s growing need and ability to produce space technologies on demand in space. As the future of long term presence in space and deep space exploration approach, fundamental questions of our dependence on earth resupply to Low Earth Orbit (LEO) remain unanswered. ISM is leading various effort to evaluate the feasibility of producing essential spares and redundant parts on demand to enable a sustainable space-based supply chain model for part resupply. Among the parts and systems being considered, Avionics form the neural network of modern day aircraft and space vehicles providing a wealth of information ranging from Guidance, Navigation, and Control (GN&C) systems to on board Environmental Control and Life Support (ECLS) systems. Recent advances in the use of Aerosol Jet Technology to print Avionics components ranging from electrical traces on a circuit board to complex transistors and sensors raise the possibility of using such technology to reproduce or recreate electronic parts on demand with the help of custom electronics 3D printers. The challenge herein lies within the ability of such printers to generate and deposit an aerosol of electronic material utilizing processes independent of or enhanced by gravity to ensure controllably identical or improved behavior of the aerosol in an International Space Station (ISS) laboratory and on the ground. The behavior as well as the hazards and properties associated with such aerosols in a microgravity environment must be understood well in order to merit a feasible approach to utilizing them for manufacturing in space. In this report, we outline the experimental setup of a modified conventional vaping device to be used as the ideal gravity independent thermal atomization mechanism to generate aerosol. Our objective is to identify the ideal mass, density, and volume of our aerosolized droplets of ink to conclude that there exist a threshold of aerosolized ink droplet sizes that are indeed independent of the effects of gravity and remain stable after atomization. We use a Malvern Spraytec® Spray Particle Size Analyzer to perform real-time laser diffraction measurement of our ink droplets during atomization. The droplet size between conductive ink, dielectric ink and vegetable glycerin have been measured and contrasted. Furthermore, the mechanism of thermal atomization versus traditional pneumatic and ultrasonic atomization for operation in microgravity have been explored.
Future In-Space propulsion systems for exploration programs will invariably require data collection from a large number of sensors. Consider the sensors needed for monitoring several vehicle systems states of health, including the collection of structural health data, over a large area. This would include the fuel tanks, habitat structure, and science containment of systems required for Lunar, Mars, or deep space exploration. Such a system would consist of several hundred or even thousands of sensors. Conventional avionics system design will require these sensors to be connected to a few Remote Health Units (RHU), which are connected to robust, micro flight computers through a serial bus. This results in a large mass of cabling and unacceptable weight. This paper first gives a survey of several techniques that may reduce the cabling mass for sensors. These techniques can be categorized into four classes: power line communication, serial sensor buses, compound serial buses, and wireless network. The power line communication approach uses the power line to carry both power and data, so that the conventional data lines can be eliminated. The serial sensor bus approach reduces most of the cabling by connecting all the sensors with a single (or redundant) serial bus. Many standard buses for industrial control and sensor buses can support several hundreds of nodes, however, have not been space qualified. Conventional avionics serial buses such as the Mil-Std-1553B bus and IEEE 1394a are space qualified but can support only a limited number of nodes. The third approach is to combine avionics buses to increase their addressability. The reliability, EMI/EMC, and flight qualification issues of wireless networks have to be addressed. Several wireless networks such as the IEEE 802.11 and Ultra Wide Band are surveyed in this paper. The placement of sensors can also affect cable mass. Excessive sensors increase the number of cables unnecessarily. Insufficient number of sensors may not provide adequate coverage of the system. This paper also discusses an optimal technique to place and validate sensors.
Beginning with the launch of the Lunar Reconnaissance Orbiter (LRO) in October of 2008, NASA will once again begin its quest to land humans on the Moon. This effort will require the development of new spacecraft which will safely transport people from the Earth to the Moon and back again, as well as robotic probes tagged with science, re-supply, and communication duties. In addition to the next-generation spacecraft currently under construction, including the Orion capsule, NASA is also investigating and developing cutting edge navigation sensors which will allow for autonomous state estimation in low Earth orbit (LEO) and cislunar space. Such instruments could provide an extra layer of redundancy in avionics systems and reduce the reliance on support and on the Deep Space Network (DSN). One such sensor is the weak-signal Global Positioning System (GPS) receiver "Navigator" being developed at NASA's Goddard Space Flight Center (GSFC). At the heart of the Navigator is a Field Programmable Gate Array (FPGA) based acquisition engine. This engine allows for the rapid acquisition/reacquisition of strong GPS signals, enabling the receiver to quickly recover from outages due to blocked satellites or atmospheric entry. Additionally, the acquisition algorithm provides significantly lower sensitivities than a conventional space-based GPS receiver, permitting it to acquire satellites well above the GPS constellation. This paper assesses the performance of the Navigator receiver based upon three of the major flight regimes of a manned lunar mission: Earth ascent, cislunar navigation, and entry. Representative trajectories for each of these segments were provided by NASA. The Navigator receiver was connected to a Spirent GPS signal generator, to allow for the collection of real-time, hardware-in-the-loop results for each phase of the flight. For each of the flight segments, the Navigator was tested on its ability to acquire and track GPS satellites under the dynamical environment unique to that trajectory.
The Radiation Hardened Electronics for Space Environments (RHESE) project develops advanced technologies needed for high performance electronic devices that will be capable of operating within the demanding radiation and thermal extremes of the space, lunar, and Martian environment. The technologies developed under this project enhance and enable avionics within multiple mission elements of NASA's Vision for Space Exploration. including the Constellation program's Orion Crew Exploration Vehicle. the Lunar Lander project, Lunar Outpost elements, and Extra Vehicular Activity (EVA) elements. This paper provides an overview of the RHESE project and its multiple task tasks, their technical approaches, and their targeted benefits as applied to NASA missions.