Search NASA⌕ Search

SEARCH · Search NASA

Results for “Flight test infrastructure”

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 145 records · Page 8
All sourcesNASA NTRSDOE OSTI
NASA NTRS2008

Ares I-X Flight Test - The Future Begins Here

In less than two years, the National Aeronautics and Space Administration (NASA) will launch the Ares I-X mission. This will be the first flight of the Ares I crew launch vehicle, which, together with the Ares V cargo launch vehicle, will eventually send humans to the Moon, Mars, and beyond. As the countdown to this first Ares mission continues, personnel from across the Ares I-X Mission Management Office (MMO) are finalizing designs and fabricating vehicle hardware for an April 2009 launch. This paper will discuss the hardware and programmatic progress of the Ares I-X mission. Like the Apollo program, the Ares launch vehicles will rely upon extensive ground, flight, and orbital testing before sending the Orion crew exploration vehicle into space with humans on board. The first flight of Ares I, designated Ares I-X, will be a suborbital development flight test. Ares I-X gives NASA its first opportunity to gather critical data about the flight dynamics of the integrated launch vehicle stack; understand how to control its roll during flight; better characterize the severe stage separation environments that the upper stage engine will experience during future operational flights; and demonstrate the first stage recovery system. NASA also will begin modifying the launch infrastructure and fine-tuning ground and mission operations, as the agency makes the transition from the Space Shuttle to the Ares/Orion system.

Davis, Stephan R.↗
NASA NTRS2013

Project Morpheus: Lessons Learned in Lander Technology Development

NASA's Morpheus Project has developed and tested a prototype planetary lander capable of vertical takeoff and landing, that is designed to serve as a testbed for advanced spacecraft technologies. The lander vehicle, propelled by a LOX/Methane engine and sized to carry a 500kg payload to the lunar surface, provides a platform for bringing technologies from the laboratory into an integrated flight system at relatively low cost. Designed, developed, manufactured and operated in-house by engineers at Johnson Space Center, the initial flight test campaign began on-site at JSC less than one year after project start. After two years of testing, including two major upgrade periods, and recovery from a test crash that caused the loss of a vehicle, flight testing will evolve to executing autonomous flights simulating a 500m lunar approach trajectory, hazard avoidance maneuvers, and precision landing, incorporating the Autonomous Landing and Hazard Avoidance (ALHAT) sensor suite. These free-flights are conducted at a simulated planetary landscape built at Kennedy Space Center's Shuttle Landing Facility. The Morpheus Project represents a departure from recent NASA programs and projects that traditionally require longer development lifecycles and testing at remote, dedicated testing facilities. This paper expands on the project perspective that technologies offer promise, but capabilities offer solutions. It documents the integrated testing campaign, the infrastructure and testing facilities, and the technologies being evaluated in this testbed. The paper also describes the fast pace of the project, rapid prototyping, frequent testing, and lessons learned during this departure from the traditional engineering development process at NASA's Johnson Space Center.

Olansen, Jon B.↗
NASA NTRS2004

Modular, Adaptive, Reconfigurable Systems: Technology for Sustainable, Reliable, Effective, and Affordable Space Exploration

In order to execute the Vision for Space Exploration, we must find ways to reduce cost, system complexity, design, build, and test times, and at the same time increase flexibility to satisfy multiple functions. Modular, Adaptive, Reconfigurable System (MARS) technologies promise to set the stage for the delivery of system elements that form the building blocks of increasingly ambitious missions involving humans and robots. Today, space systems are largely specialized and built on a case-by-case basis. The notion of modularity however, is nothing new to NASA. The 1970's saw the development of the Multi-Mission Modular spacecraft (MMS). From 1980 to 1992 at least six satellites were built under this paradigm, and included such Goddard Space Flight Center missions as SSM, EUVE, UARS, and Landsat 4 and 5. Earlier versions consisted of standard subsystem "module" or "box" components that could be replaced within a structure based on predefined form factors. Although the primary motivation for MMS was faster/cheaper integration and test, standardization of interfaces, and ease of incorporating new subsystem technology, it lacked the technology maturity and programmatic "upgrade infrastructure" needed to satisfy varied mission requirements, and ultimately it lacked user buy-in. Consequently, it never evolved and was phased out. Such concepts as the Rapid Spacecraft Development Office (RSDO) with its regularly updated catalogue of prequalified busses became the preferred method for acquiring satellites. Notwithstanding, over the past 30 years since MMS inception, technology has advanced considerably and now modularity can be extended beyond the traditional MMS module or box to cover levels of integration, from the chip, card, box, subsystem, to the space system and to the system-of-systems. This paper will present the MARS architecture, cast within the historical context of MMS. Its application will be highlighted by comparing a state-of-the-art point design vs. a MARS-enabled lunar mission, as a representative robotic case design.

Esper, Jaime↗
NASA NTRS2010

An Overview of the NASA Aeronautics Test Program Strategic Plan

U.S. leadership in aeronautics depends on ready access to technologically advanced, efficient, and affordable aeronautics test capabilities. These systems include major wind tunnels and propulsion test facilities and flight test capabilities. The federal government owns the majority of the major aeronautics test capabilities in the United States, primarily through the National Aeronautics and Space Administration (NASA) and the Department of Defense (DoD), however an overarching strategy for management of these national assets was needed. Therefore, in Fiscal Year (FY) 2006 NASA established the Aeronautics Test Program (ATP) as a two-pronged strategic initiative to: (1) retain and invest in NASA aeronautics test capabilities considered strategically important to the agency and the nation, and (2) establish a strong, high level partnership with the DoD Test Resources Management Center (TRMC), stewards of the DoD test and evaluation infrastructure. Since then, approximately seventy percent of the ATP budget has been directed to underpin fixed and variable costs of facility operations within its portfolio and the balance towards strategic investments in its test facilities, including maintenance and capability upgrades. Also, a strong guiding coalition was established through the National Partnership for Aeronautics Testing (NPAT), with governance by the senior leadership of NASA s Aeronautics Research Mission Directorate (ARMD) and the DoD's TRMC. As part of its strategic planning, ATP has performed or participated in many studies and analyses, including assessments of major NASA and DoD aeronautics test capabilities, test facility condition evaluations and market research. The ATP strategy has also benefitted from unpublished RAND research and analysis by Ant n et al. (2009). Together, these various studies, reports and assessments serve as a foundation for a new, five year strategic plan that will guide ATP through FY 2014. Our vision for the future is a balanced portfolio of aeronautics ground and flight test capabilities that advance U.S. leadership in aeronautics in the short and long term. Key to the ATP vision is the concept of availability, not necessarily ownership; that is, NASA does not have to own and operate all facilities that are envisioned for future aeronautics testing. However, ATP will enable access to capabilities which are needed but not owned by NASA through strategic partnerships and reliance agreements. This paper will outline the major aspects of the ATP strategic plan for achieving its mission.

Marshall, Timothy J.↗
NASA NTRS2001

A Space Based Internet Protocol System for Launch Vehicle Tracking and Control

Personnel from the Goddard Space Flight Center Wallops Flight Facility (GSFC/WFF) in Virginia are responsible for the overall management of the NASA Sounding Rocket and Scientific Balloon Programs. Payloads are generally in support of NASA's Space Science Enterprise's missions and return a variety of scientific data as well as providing a reasonably economical means of conducting engineering tests for instruments and devices used on satellites and other spacecraft. Sounding rockets used by NASA can carry payloads of various weights to altitudes from 50 km to more than 1,300 km. Scientific balloons can carry a payload weighing as much as 3,630 Kg to an altitude of 42 km. Launch activities for both are conducted not only from established ranges, but also from remote locations worldwide requiring mobile tracking and command equipment to be transported and set up at considerable expense. The advent of low earth orbit (LEO) commercial communications satellites provides an opportunity to dramatically reduce tracking and control costs of these launch vehicles and Unpiloted Aerial Vehicles (UAVs) by reducing or eliminating this ground infrastructure. Additionally, since data transmission is by packetized Internet Protocol (IP), data can be received and commands initiated from practically any location. A low cost Commercial Off The Shelf (COTS) system is currently under development for sounding rockets that also has application to UAVs and scientific balloons. Due to relatively low data rate (9600 baud) currently available, the system will first be used to provide GPS data for tracking and vehicle recovery. Range safety requirements for launch vehicles usually stipulate at least two independent tracking sources. Most sounding rockets flown by NASA now carry GP~ receivers that output position data via the payload telemetry system to the ground station. The Flight Modem can be configured as a completely separate link thereby eliminating the requirement for tracking radar. The system architecture that integrates antennas, GPS receiver, commercial satellite packet data modem, and a single board computer with custom software is described along with the technical challenges and the plan for their resolution. These include antenna development, high Doppler rates, reliability, environmental ruggedness, hand over between satellites, and data security. An aggressive test plan is included which, in addition to environmental testing, measures bit error rate, latency and antenna patterns. Actual launches on a sounding rocket and various aircraft flights have taken place. Flight tests are planned for the near future on aircraft, long duration balloons and sounding rockets. These results, as well as the current status of the project, are reported.

Bull, Barton↗
NASA NTRS1984

Commerce lab: Mission analysis and payload integration study

Conceived as one or more arrays of carriers which would fly aboard space shuttle, Commerce Lab can provide a point of focus for implementing a series of shuttle flights, co-sponsored by NASA and U.S. domestic concerns, for performing materials processing in research and pre-commercial investigations. As an orbiting facility for testing, developing, and implementing hardware and procedures, Commerce Lab can enhance space station development and hasten space platform production capability. Tasks considered include: (1) synthesis of user requirements and identification of common element and voids; (2) definition of performance and infrastructure requirement and alternative approaches; and (3) carrier, mission model, and infrastructure development.

Source record↗
NASA NTRS2004

Flight Test of Weather Data Exchange Using the 1090 Extended Squitter (1090ES) and VDL Mode 3 Data Links

This report describes preliminary results of work done by JHU/APL under contract to the NASA Glenn Research Center to support flight testing of the Universal Access Transceiver (UAT) data link as a medium for weather data exchange. It presents a high level architectural description of the use of UAT to meet the program objectives with an identification of issues associated with the use of this data link, including a high level definition of the changes required to UAT avionics and ground-based receivers and supporting ground infrastructure to support implementation of the recommended architecture with focus on the issues associated with these changes.

Griner, James H., Jr.↗
NASA NTRSDate not supplied

Earth Independent Medical Operations (EIMO) Datascope: Challenges and Potential Solutions

Data flows and storage/retrieval capacity are severely constrained during missions in space and challenges will become even greater during exploration class missions. There is a need for an artificial intelligence (AI)-based clinical decision support system (CDSS) to monitor and analyze data to provide real-time consultative support for crew medical officer (CMO) decision-making. EIMO is defined as the gradual transition of medical care and decision making from terrestrial to space-based assets, enabling support of astronaut health and performance and reducing overall mission risk. While a hallmark of this paradigm shift from low-earth orbit is that on-board care will increasingly become the responsibility of the astronauts for primary management and decision making, terrestrial assets will continue to be paramount in pre-mission screening and planning, as well as prevention, health maintenance and long-term care contingencies. New capabilities and systems that enable progressively more robust and resilient systems and crews will be necessary to reduce risk and increase probability of deep space exploration mission success. An aspiration for EIMO is to develop AI-enhanced solutions for analysis of crew health & performance data and to facilitate clinical decision support for autonomous medical operations. A “system of systems” approach is envisioned whereby EIMO will deploy AI-supported natural language processing and machine learning (ML) techniques to utilize embedded reference databases and real-time data streams [input vectors] from multiple data sources. Constituent input vectors may include environmental controls, countermeasures data, behavioral data, physiologic wearables, point-of-care laboratory tests, personalized medical records, inventory trade space risk assessments, COTS medical databases, and ground support inputs. An ideal AI capability would possess trained fusion algorithms to cross reference input vectors with medical ‘knowledge’ [cultivated database] to stratify relevant data streams for predictive and actionable capabilities. In addition, EIMO will feature mobility, in that it can be accessed and can push/pull data within and between multiple vehicles/habitats. Large amounts and variable sources of data can be leveraged to diagnose, inform treatment strategies, and potentially predict medical events and performance decrements. Inclusion of advanced training tools using extended reality will enable increasingly autonomous medical care to aid a CMO when ground support is unavailable or time-delayed beyond required action window, e.g., emergent medical situations. EIMO CDSS would require very large datasets to train pre-flight and significant amounts of data are needed to support ML via in-flight CDSS operations. An additional challenge will be to find sufficient data to train a model relevant to astronaut demographics. The rapid, accelerating evolution of this field creates a propitious solution space to leverage multi-modal AI through public-private partnership(s). The status of multi-modal AI systems today would preclude their use for long duration missions as they remain unreliable and are subject to “digital hallucinations” and other errors that could pose operational risk. A federated labs structure is being considered to test and optimize data flow from the multiple input vectors leading to field testing in suitable ground/flight analogs. Critical to the success of an EIMO CDSS will be integration and interoperability and success will be defined by a system that can serve as an in-flight medical consult for the CMO providing critical support during medical contingencies. Benefits to terrestrial medicine may be significant as an outflow of the EIMO medical system, particularly for remote areas and communities lacking significant infrastructure, personnel and resources.

J Lemery↗
NASA NTRS2024

Earth Independent Medical Operations (EIMO) Datascope: Challenges and Potential Solutions

Data flows and storage/retrieval capacity are severely constrained during missions in space and challenges will become even greater during exploration class missions. There is a need for an artificial intelligence (AI)-based clinical decision support system (CDSS) to monitor and analyze data to provide real-time consultative support for crew medical officer (CMO) decision-making. EIMO is defined as the gradual transition of medical care and decision making from terrestrial to space-based assets, enabling support of astronaut health and performance and reducing overall mission risk. While a hallmark of this paradigm shift from low-earth orbit is that on-board care will increasingly become the responsibility of the astronauts for primary management and decision making, terrestrial assets will continue to be paramount in pre-mission screening and planning, as well as prevention, health maintenance and long-term care contingencies. New capabilities and systems that enable progressively more robust and resilient systems and crews will be necessary to reduce risk and increase probability of deep space exploration mission success. An aspiration for EIMO is to develop AI-enhanced solutions for analysis of crew health & performance data and to facilitate clinical decision support for autonomous medical operations. A “system of systems” approach is envisioned whereby EIMO will deploy AI-supported natural language processing and machine learning (ML) techniques to utilize embedded reference databases and real-time data streams [input vectors] from multiple data sources. Constituent input vectors may include environmental controls, countermeasures data, behavioral data, physiologic wearables, point-of-care laboratory tests, personalized medical records, inventory trade space risk assessments, COTS medical databases, and ground support inputs. An ideal AI capability would possess trained fusion algorithms to cross reference input vectors with medical ‘knowledge’ [cultivated database] to stratify relevant data streams for predictive and actionable capabilities. In addition, EIMO will feature mobility, in that it can be accessed and can push/pull data within and between multiple vehicles/habitats. Large amounts and variable sources of data can be leveraged to diagnose, inform treatment strategies, and potentially predict medical events and performance decrements. Inclusion of advanced training tools using extended reality will enable increasingly autonomous medical care to aid a CMO when ground support is unavailable or time-delayed beyond required action window, e.g., emergent medical situations. EIMO CDSS would require very large datasets to train pre-flight and significant amounts of data are needed to support ML via in-flight CDSS operations. An additional challenge will be to find sufficient data to train a model relevant to astronaut demographics. The rapid, accelerating evolution of this field creates a propitious solution space to leverage multi-modal AI through public-private partnership(s). The status of multi-modal AI systems today would preclude their use for long duration missions as they remain unreliable and are subject to “digital hallucinations” and other errors that could pose operational risk. A federated labs structure is being considered to test and optimize data flow from the multiple input vectors leading to field testing in suitable ground/flight analogs. Critical to the success of an EIMO CDSS will be integration and interoperability and success will be defined by a system that can serve as an in-flight medical consult for the CMO providing critical support during medical contingencies. Benefits to terrestrial medicine may be significant as an outflow of the EIMO medical system, particularly for remote areas and communities lacking significant infrastructure, personnel and resources.

Medical Operations↗
NASA NTRS2006

Cleanroom Garment Silicone Contamination

The slide presentation reviews actions taken at Goddard Space Flight Center (GSFC) to eliminate contamination by silicone in clean rooms. Background information includes facilities and hardware affected by silicon contamination, a discussion of the negative aspects of silicone contamination, clean room garments, and how the problem was identified at GSFC. Actions taken by the GSFC Contamination Engineering Group and lessons learned are detailed. Results include: awareness of the silicone issue in laundry, increase in infrastructure and support of the testing lab, establishment of protocols for garment verification, closer relationship established with laundry and converter, specifications for laundry services and garments were strengthened, all consumables are tested before use in clean rooms, and established procedures were used to identify and treat silicone found on face masks.

Geer, Wayne↗
NASA NTRS2010

Evaluation of the NASA Arc Jet Capabilities to Support Mission Requirements

NASA accomplishes its strategic goals through human and robotic exploration missions. Many of these missions require launching and landing or returning spacecraft with human or return samples through Earth's and other planetary atmospheres. Spacecraft entering an atmosphere are subjected to extreme aerothermal loads. Protecting against these extreme loads is a critical element of spacecraft design. The safety and success of the planned mission is a prime concern for the Agency, and risk mitigation requires the knowledgeable use of thermal protection systems to successfully withstand the high-energy states imposed on the vehicle. Arc jets provide ground-based testing for development and flight validation of re-entry vehicle thermal protection materials and are a critical capability and core competency of NASA. The Agency's primary hypersonic thermal testing capability resides at the Ames Research Center and the Johnson Space Center and was developed and built in the 1960s and 1970s. This capability was critical to the success of Apollo, Shuttle, Pioneer, Galileo, Mars Pathfinder, and Orion. But the capability and the infrastructure are beyond their design lives. The complexes urgently need strategic attention and investment to meet the future needs of the Agency. The Office of Chief Engineer (OCE) chartered the Arc Jet Evaluation Working Group (AJEWG), a team of experienced individuals from across the Nation, to capture perspectives and requirements from the arc jet user community and from the community that operates and maintains this capability and capacity. This report offers the AJEWG's findings and conclusions that are intended to inform the discussion surrounding potential strategic technical and investment strategies. The AJEWG was directed to employ a 30-year Agency-level view so that near-term issues did not cloud the findings and conclusions and did not dominate or limit any of the strategic options.

Calomino, Anthony↗
NASA NTRS2017

Lunar and Lagrangian Point L1 L2 CubeSat Communication and Navigation Considerations

CubeSats have grown in sophistication to the point that relatively low-cost mission solutions could be undertaken for planetary exploration. There are unique considerations for lunar and L1/L2 CubeSat communication and navigation compared with low earth orbit CubeSats. This paper explores those considerations as they relate to the Lunar IceCube Mission. The Lunar IceCube is a CubeSat mission led by Morehead State University with participation from NASA Goddard Space Flight Center, Jet Propulsion Laboratory, the Busek Company and Vermont Tech. It will search for surface water ice and other resources from a high inclination lunar orbit. Lunar IceCube is one of a select group of CubeSats designed to explore beyond low-earth orbit that will fly on NASA’s Space Launch System (SLS) as secondary payloads for Exploration Mission (EM) 1. Lunar IceCube and the EM-1 CubeSats will lay the groundwork for future lunar and L1/L2 CubeSat missions. This paper discusses communication and navigation needs for the Lunar IceCube mission and navigation and radiation tolerance requirements related to lunar and L1/L2 orbits. Potential CubeSat radios and antennas for such missions are investigated and compared. Ground station coverage, link analysis, and ground station solutions are also discussed. This paper will describe modifications in process for the Morehead ground station, as well as further enhancements of the Morehead ground station and NASA Near Earth Network (NEN) that are being considered. The potential NEN enhancements include upgrading current NEN Cortex receiver with Forward Error Correction (FEC) Turbo Code, providing X-band uplink capability, and adding ranging options. The benefits of ground station enhancements for CubeSats flown on NASA Exploration Missions (EM) are presented. This paper also describes how the NEN may support lunar and L1/L2 CubeSats without any enhancements. In addition, NEN is studying other initiatives to better support the CubeSat community, including streamlining the compatibility testing, planning and scheduling associated with CubeSat missions. Because of the lower cost, opportunity for simultaneous multipoint observations, it is inevitable that CubeSats will continue to increase in popularity for not only LEO missions, but for lunar and L1/L2 missions as well. The challenges for lunar and L1/L2 missions for communication and navigation are much greater than for LEO missions, but are not insurmountable. Advancements in flight hardware and ground infrastructure will ease the burden.

CubeSat↗
NASA NTRS2007

The MSFC Systems Engineering Guide: An Overview and Plan

As systems and subsystems requirements become more complex in the pursuit of the exploration of space, advanced technology will demand and require an integrated approach to the design and development of safe and successful space vehicles and there products. System engineers play a vital and key role in transforming mission needs into vehicle requirements that can be verified and validated. This will result in a safe and cost effective design that will satisfy the mission schedule. A key to successful vehicle design within systems engineering is communication. Communication, through a systems engineering infrastructure, will not only ensure that customers and stakeholders are satisfied but will also assist in identifying vehicle requirements; i.e. identification, integration and management. This vehicle design will produce a system that is verifiable, traceable, and effectively satisfies cost, schedule, performance, and risk throughout the life-cycle of the product. A communication infrastructure will bring about the integration of different engineering disciplines within vehicle design. A system utilizing these aspects will enhance system engineering performance and improve upon required activities such as Development of Requirements, Requirements Management, Functional Analysis, Test, Synthesis, Trade Studies, Documentation, and Lessons Learned to produce a successful final product. This paper will describe the guiding vision, progress to date and the plan forward for development of the Marshall Space Flight Center (MSFC) Systems Engineering Guide (SEG), a virtual systems engineering handbook and archive that will describe the system engineering processes that are used by MSFC in the development of complex systems such as the Ares launch vehicle. It is the intent of this website to be a "One Stop Shop" for our systems engineers that will provide tutorial information, an overview of processes and procedures and links to assist system engineering with guidance and references, and provide an archive of systems engineering artifacts produced by the many NASA projects developed and managed by MSFC over the years.

Shelby, Jerry A.↗
NASA NTRS2006

An Integrated Approach to Exploration Launch Office Requirements Development

The proposed paper will focus on the Project Management and Systems Engineering approach utilized to develop a set of both integrated and cohesive requirements for the Exploration Launch Office, within the Constellation Program. A summary of the programmatic drivers which influenced the approach along with details of the resulting implementation will be discussed as well as metrics evaluating the efficiency and accuracy of the various requirements development activities. Requirements development activities will focus on the procedures utilized to ensure that technical content was valid and mature in preparation for the Crew Launch Vehicle and Constellation System s Requirements Reviews. This discussion will begin at initial requirements development during the Exploration Systems Architecture Study and progress through formal development of the program structure. Specific emphasis will be given to development and validation of the requirements. This discussion will focus on approaches to garner the appropriate requirement owners (or customers), project infrastructure utilized to emphasize proper integration, and finally the procedure to technically mature, verify and validate the requirements. Examples of requirements being implemented on the Launch Vehicle (systems, interfaces, test & verification) will be utilized to demonstrate the various processes and also provide a top level understanding of the launch vehicle(s) performance goals. Details may also be provided on the approaches for verification, which range from typical aerospace hardware development (qualification/acceptance) through flight certification (flight test, etc.). The primary intent of this paper is to provide a demonstrated procedure for the development of a mature, effective, integrated set of requirements on a complex system, which also has the added intricacies of both heritage and new hardware development integration. Ancillary focus of the paper will include discussion of Test and Verification approaches along with top level systems/elements performance capabilities.

Holladay, Jon B.↗
NASA NTRS2006

NASA Tech Briefs, February 2006

Topics discussed include: Nearly Direct Measurement of Relative Permittivity; DCS-Neural-Network Program for Aircraft Control and Testing; Dielectric Heaters for Testing Spacecraft Nuclear Reactors; Using Doppler Shifts of GPS Signals To Measure Angular Speed; Monitoring Temperatures of Tires Using Luminescent Materials; Highly Efficient Multilayer Thermoelectric Devices; Very High-Speed Digital Video Capability for In-Flight Use; MMIC DHBT Common-Base Amplifier for 172 GHz; Modular, Microprocessor-Controlled Flash Lighting System; Generic Environment for Simulating Launch Operations; Modular Aero-Propulsion System Simulation; X-Windows Socket Widget Class; Infrastructure for Rapid Development of Java GUI Programs; Processing Raman Spectra of High-Pressure Hydrogen Flames; X-Windows Information Sharing Protocol Widget Class; Simulating Humans as Integral Parts of Spacecraft Missions; Analyzing Power Supply and Demand on the ISS; Polyimides From a-BPDA and Aromatic Diamines; Making Plant-Support Structures From Waste Plant Fiber; Large Deployable Reflectarray Antenna; Periodically Discharging, Gas-Coalescing Filter; Ion Milling On Steps for Fabrication of Nanowires; Neuro-Prosthetic Implants With Adjustable Electrode Arrays; Microfluidic Devices for Studying Biomolecular Interactions; Studying Functions of All Yeast Genes Simultaneously; Polarization Phase-Compensating Coats for Metallic Mirrors; Tunable-Bandwidth Filter System; Methodology for Designing Fault-Protection Software; and Ground-Based Localization of Mars Rovers.

Source record↗
NASA NTRS1992

MSFC Three Point Docking Mechanism design review

In the next few decades, we will be launching expensive satellites and space platforms that will require recovery for economic reasons, because of initial malfunction, servicing, repairs, or out of a concern for post lifetime debris removal. The planned availability of a Three Point Docking Mechanism (TPDM) is a positive step towards an operational satellite retrieval infrastructure. This study effort supports NASA/MSFC engineering work in developing an automated docking capability. The work was performed by the Grumman Space & Electronics Group as a concept evaluation/test for the Tumbling Satellite Retrieval Kit. Simulation of a TPDM capture was performed in Grumman's Large Amplitude Space Simulator (LASS) using mockups of both parts (the mechanism and payload). Similar TPDM simulation activities and more extensive hardware testing was performed at NASA/MSFC in the Flight Robotics Laboratory and Space Station/Space Operations Mechanism Test Bed (6-DOF Facility).

Schaefer, Otto↗
NASA NTRS2015

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The development of the Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large complex systems engineering challenge being addressed in part by focusing on the specific subsystems handling of off-nominal mission and fault tolerance. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML), the Mission and Fault Management (M&FM) algorithms are crafted and vetted in specialized Integrated Development Teams composed of multiple development disciplines. NASA also has formed an M&FM team for addressing fault management early in the development lifecycle. This team has developed a dedicated Vehicle Management End-to-End Testbed (VMET) that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. The flexibility of VMET enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the algorithms utilizing actual subsystem models. The intent is to validate the algorithms and substantiate them with performance baselines for each of the vehicle subsystems in an independent platform exterior to flight software test processes. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test processes. Risk reduction is addressed by working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and detection and responses that can be tested in VMET and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM. The plan for VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗
NASA NTRS2002

A Method of Separation Assurance for Instrument Flight Procedures at Non-Radar Airports

A method to provide automated air traffic separation assurance services during approach to or departure from a non-radar, non-towered airport environment is described. The method is constrained by provision of these services without radical changes or ambitious investments in current ground-based technologies. The proposed procedures are designed to grant access to a large number of airfields that currently have no or very limited access under Instrument Flight Rules (IFR), thus increasing mobility with minimal infrastructure investment. This paper primarily addresses a low-cost option for airport and instrument approach infrastructure, but is designed to be an architecture from which a more efficient, albeit more complex, system may be developed. A functional description of the capabilities in the current NAS infrastructure is provided. Automated terminal operations and procedures are introduced. Rules of engagement and the operations are defined. Results of preliminary simulation testing are presented. Finally, application of the method to more terminal-like operations, and major research areas, including necessary piloted studies, are discussed.

Conway, Sheila R.↗