Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Ground Support 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 829 records · Page 46

X-57 Cockpit Interface Control Document (ICD-CEPT-006)

The Cockpit Interface Control Document defines the hardware interfaces between the X-57 cockpit and subsystems. It provides locational and operational information in support of ground and flight operations with details on controls and displays that include Modes of Operation, Start-Up and Shut- Down Sequence diagrams and captures the current state of the MOD II Avionics Power Architecture. There is also preliminary information of the MOD III and MOD IV configurations. Microsoft PowerPoint was chosen for the document as early development required frequent meetings with multiple customers including aircraft operators (pilots), ground operations, support contractors and power, instrumentation, and human systems integration engineers and PowerPoint enabled presentations that could be quickly modified based on customer and developer interaction. One of the driving requirements for the cockpit design was to keep the left side panel as close the stock Tecnam panel as possible to reduce the failure risk of flight critical indicators. The original annunciator panel in the left side panel was modified to alert the pilot to failures in critical X-57 subsystems and an operator audio alert capability was added for these subsystems. Power-Up switches for the aircraft low voltage 13.8 VDC systems are located at the bottom of the left side panel and center panel, the same location as the stock Tecnam 13.8 VDC switches. The switches for energizing the high voltage system were located in the overhead panel to reduce the risk of inadvertently energizing the high voltage system during the low voltage power-up sequence. The Cruise Motor ARM switches were also located in the overhead panel and correspond to the same location as the stock Tecnam ignition switches. The stock Tecnam throttle levers and prop pitch levers were retained for the X-57. The throttle levers were renamed torque levers since they controlled the commanded torque to the cruise motors. The prop pitch levers provide a commanded RPM signal to an electronic prop pitch controller. X-57 specific displays, located in the right-side panel, are driven by dedicated sensors that monitor right and left side cruise motor RPM, right and left high voltage “Traction Bus” A and B (voltage, current and power) and the Avionics Bus DC converters (A and B) voltage and current. An X-57 Multi-Function Display (MFD) located in the center panel displays CAN Bus parameters. CAN Bus architecture is not certified for flight so these displays could not be used for safety critical information but were designed to be used for test point information only.

Laura Kushner↗

Super Strypi Navigation, Guidance & Control (NGC) v. Release 04

The Super Strypi Navigation, Guidance & Control Software is a real-time implementation of the navigation, guidance and control algorithms designed to deliver a payload to a desired orbit for the rail launched Super Strypi launch vehicle. The software contains all flight control algorithms required from pre-launch until orbital insertion. The flight sequencer module calls the NG&C functions at the appropriate times of flight. Additional functionality includes all the low level drivers and I/O for communicating to other systems within the launch vehicle and to the ground support equipment. The software is designed such that changes to the launch location and desired orbit can be changed without recompiling the code.

Anderson, Mark A.↗

Extreme Problem Solving: The New Challenges of Deep Space Exploration

On the International Space Station today, the crew has the near real-time support of a large group of system experts on the ground when dealing with problems on-board. For exploration beyond Low Earth Orbit, however, intermittent and delayed communication with ground will force small crews to take the lead in responding to vehicle anomalies. Enabling a flight crew of roughly four astronauts to perform the job that has traditionally been done by a ground crew of over 80 experts will require a fundamental rethinking of human-systems integration. Through observations of anomaly resolution processes, interviews with system experts and astronauts, and analyses of problem-solving models, we have identified the capabilities that are not currently available on-board but will be needed to enable safe exploration further away from Earth. These include increased data access, just-in-time training tools and technologies, and troubleshooting decision support. Important questions remain on how these technologies can be designed and implemented for increased crew autonomy. We present this critical challenge for deep space exploration to the human-computer interaction research community to reflect on the areas identified by our needs analysis and contemplate how they might be manifested as solutions.

autonomy↗

Sunlight supply and gas exchange systems in microalgal bioreactor

The bioreactor with sunlight supply system and gas exchange systems presented has proved feasible in ground tests and shows much promise for space use as a closed ecological life support system device. The chief conclusions concerning the specification of total system needed for a life support system for a man in a space station are the following: (1) Sunlight supply system - compactness and low electrical consumption; (2) Bioreactor system - high density and growth rate of chlorella; and (3) Gas exchange system - enough for O2 production and CO2 assimilation.

Mori, K.↗

Space Station Freedom ground data system: Design and operations

Over the previous year the Space Station Freedom (SSF) Program (SSFP) ground data distribution system has become independent of a number of data systems that were to have been provided by other National Aeronautics and Space Administration (NASA) programs. Consequently, the SSFP has outlined the basic architecture of a new data system dedicated to supporting SSF requirements. This has been accomplished through a complete redesign of the ground network and a reallocation of selected functions. There are a number of aspects of the new ground data distribution system that are unique among NASA programs. These considerations make SSF ground data distribution one of the most extensive and complex data management challenges encountered in the arena of Space Operations. A description of this system comprises the main focus of the paper.

Dunning, Richard A., Jr.↗

Commonality of flight control systems for support of European telecommunications missions

This paper is concerned with the presentation of mission-independent software systems that provide a common software platform to ground data systems for mission operations. The objectives of such common software platforms are to reduce the cost of the development of mission-dedicated software systems and to increase the level of reliability of the ground data systems for mission operations. In accordance with this objective, the Multi-Satellite Support System (MSSS) was developed at the European Space Operations Center (ESOC). Between 1975 and 1992, the MSSS provided support to 16 European Space Agency (ESA) missions, among them very demanding science missions such as GEOS, EXOSAT, and Giotto. The successful support of these missions proved the validity of the MSSS concept with its extended mission-independent platform. This paper describes the MSSS concept and focuses on the wide use of MSSS as a flight control system for geosynchronous telecommunications satellites. Reference is made to more than 15 telecommunications missions that are operated from Western Europe using flight control systems with an underlying MSSS concept, demonstrating the benefits of a commonly used software platform. Finally, the paper outlines the design of the new generation of flight control systems, which is being developed at ESOC for this decade, following a period of more than 15 years of MSSS support.

Debatin, Kurt↗

Life Cycle Systems Engineering Approach to NASA's 2nd Generation Reusable Launch Vehicle

The overall goal of the 2nd Generation RLV Program is to substantially reduce technical and business risks associated with developing a new class of reusable launch vehicles. NASA's specific goals are to improve the safety of a 2nd- generation system by 2 orders of magnitude - equivalent to a crew risk of 1 -in- 10,000 missions - and decrease the cost tenfold, to approximately $1,000 per pound of payload launched. Architecture definition is being conducted in parallel with the maturating of key technologies specifically identified to improve safety and reliability, while reducing operational costs. An architecture broadly includes an Earth-to-orbit reusable launch vehicle, on-orbit transfer vehicles and upper stages, mission planning, ground and flight operations, and support infrastructure, both on the ground and in orbit. The systems engineering approach ensures that the technologies developed - such as lightweight structures, long-life rocket engines, reliable crew escape, and robust thermal protection systems - will synergistically integrate into the optimum vehicle. Given a candidate architecture that possesses credible physical processes and realistic technology assumptions, the next set of analyses address the system's functionality across the spread of operational scenarios characterized by the design reference missions. The safety/reliability and cost/economics associated with operating the system will also be modeled and analyzed to answer the questions "How safe is it?" and "How much will it cost to acquire and operate?" The systems engineering review process factors in comprehensive budget estimates, detailed project schedules, and business and performance plans, against the goals of safety, reliability, and cost, in addition to overall technical feasibility. This approach forms the basis for investment decisions in the 2nd Generation RLV Program's risk-reduction activities. Through this process, NASA will continually refine its specialized needs and identify where Defense and commercial requirements overlap those of civil missions.

Thomas, Dale↗

Systems Engineering Approach to Technology Integration for NASA's 2nd Generation Reusable Launch Vehicle

The overall goal of the 2nd Generation RLV Program is to substantially reduce technical and business risks associated with developing a new class of reusable launch vehicles. NASA's specific goals are to improve the safety of a 2nd generation system by 2 orders of magnitude - equivalent to a crew risk of 1-in-10,000 missions - and decrease the cost tenfold, to approximately $1,000 per pound of payload launched. Architecture definition is being conducted in parallel with the maturating of key technologies specifically identified to improve safety and reliability, while reducing operational costs. An architecture broadly includes an Earth-to-orbit reusable launch vehicle, on-orbit transfer vehicles and upper stages, mission planning, ground and flight operations, and support infrastructure, both on the ground and in orbit. The systems engineering approach ensures that the technologies developed - such as lightweight structures, long-life rocket engines, reliable crew escape, and robust thermal protection systems - will synergistically integrate into the optimum vehicle. To best direct technology development decisions, analytical models are employed to accurately predict the benefits of each technology toward potential space transportation architectures as well as the risks associated with each technology. Rigorous systems analysis provides the foundation for assessing progress toward safety and cost goals. The systems engineering review process factors in comprehensive budget estimates, detailed project schedules, and business and performance plans, against the goals of safety, reliability, and cost, in addition to overall technical feasibility. This approach forms the basis for investment decisions in the 2nd Generation RLV Program's risk-reduction activities. Through this process, NASA will continually refine its specialized needs and identify where Defense and commercial requirements overlap those of civil missions.

Thomas, Dale↗

Systems Engineering Approach to Technology Integration for NASA's 2nd Generation Reusable Launch Vehicle

The overall goal of the 2nd Generation RLV Program is to substantially reduce technical and business risks associated with developing a new class of reusable launch vehicles. NASA's specific goals are to improve the safety of a 2nd-generation system by 2 orders of magnitude - equivalent to a crew risk of 1-in-10,000 missions - and decrease the cost tenfold, to approximately $1,000 per pound of payload launched. Architecture definition is being conducted in parallel with the maturating of key technologies specifically identified to improve safety and reliability, while reducing operational costs. An architecture broadly includes an Earth-to-orbit reusable launch vehicle, on-orbit transfer vehicles and upper stages, mission planning, ground and flight operations, and support infrastructure, both on the ground and in orbit. The systems engineering approach ensures that the technologies developed - such as lightweight structures, long-life rocket engines, reliable crew escape, and robust thermal protection systems - will synergistically integrate into the optimum vehicle. To best direct technology development decisions, analytical models are employed to accurately predict the benefits of each technology toward potential space transportation architectures as well as the risks associated with each technology. Rigorous systems analysis provides the foundation for assessing progress toward safety and cost goals. The systems engineering review process factors in comprehensive budget estimates, detailed project schedules, and business and performance plans, against the goals of safety, reliability, and cost, in addition to overall technical feasibility. This approach forms the basis for investment decisions in the 2nd Generation RLV Program's risk-reduction activities. Through this process, NASA will continually refine its specialized needs and identify where Defense and commercial requirements overlap those of civil missions.

Thomas, Dale↗

SSV Launch Monitoring Strategies: HGDS Design Implementation Through System Maturity

With over 500,000 gallons of liquid hydrogen and liquid oxygen, it is of vital importance to monitor the space shuttle vehicle (SSV) from external tank (ET) load through launch. The Hazardous Gas Detection System (HGDS) was installed as the primary system responsible for monitoring fuel leaks within the orbiter and ET. The HGDS was designed to obtain the lowest possible detection limits with the best resolution while monitoring the SSV for any hydrogen, helium, oxygen, or argon as the main requirement. The HGDS is a redundant mass spectrometer used for real-time monitoring during Power Reactant Storage and Distribution (PRSD) load and ET load through launch or scrub. This system also performs SSV processing leak checks of the Tail Service Mast (TSM) umbilical quick disconnects (QD's), Ground Umbilical Carrier Plate (GUCP) QD's and supports auxiliary power unit (APU) system tests. From design to initial implementation and operations, the HGDS has evolved into a mature and reliable launch support system. This paper will discuss the operational challenges and lessons learned from facing design deficiencies, validation and maintenance efforts, life cycle issues, and evolving requirements

Shoemaker, Marc D.↗

Modular Software for Spacecraft Navigation Using the Global Positioning System (GPS)

The Goddard Space Flight Center Flight Dynamics and Mission Operations Divisions have jointly investigated the feasibility of engineering modular Global Positioning SYSTEM (GPS) navigation software to support both real time flight and ground postprocessing configurations. The goals of this effort are to define standard GPS data interfaces and to engineer standard, reusable navigation software components that can be used to build a broad range of GPS navigation support applications. The paper discusses the GPS modular software (GMOD) system and operations concepts, major requirements, candidate software architecture, feasibility assessment and recommended software interface standards. In additon, ongoing efforts to broaden the scope of the initial study and to develop modular software to support autonomous navigation using GPS are addressed,

Truong, S. H.↗

Development and Evaluation of an Airborne Separation Assurance System for Autonomous Aircraft Operations

NASA Langley Research Center is developing an Autonomous Operations Planner (AOP) that functions as an Airborne Separation Assurance System for autonomous flight operations. This development effort supports NASA s Distributed Air-Ground Traffic Management (DAG-TM) operational concept, designed to significantly increase capacity of the national airspace system, while maintaining safety. Autonomous aircraft pilots use the AOP to maintain traffic separation from other autonomous aircraft and managed aircraft flying under today's Instrument Flight Rules, while maintaining traffic flow management constraints assigned by Air Traffic Service Providers. AOP is designed to facilitate eventual implementation through careful modeling of its operational environment, interfaces with other aircraft systems and data links, and conformance with established flight deck conventions and human factors guidelines. AOP uses currently available or anticipated data exchanged over modeled Arinc 429 data buses and an Automatic Dependent Surveillance Broadcast 1090 MHz link. It provides pilots with conflict detection, prevention, and resolution functions and works with the Flight Management System to maintain assigned traffic flow management constraints. The AOP design has been enhanced over the course of several experiments conducted at NASA Langley and is being prepared for an upcoming Joint Air/Ground Simulation with NASA Ames Research Center.

Barhydt, Richard↗

Narrowband Propagation Statistics of Aeronautical Mobile-Ground Links in the L- and C-Bands

To provide for the safe integration of unmanned aircraft systems (UAS) into the National Airspace System (NAS), command and control (C2) links must be highly reliable. Hence, protected aviation spectrum is required to support such links for UAS that are integrated into controlled non-segregated airspace. For air-ground (i.e., non-satellite) links, protected aviation spectrum to support C2 links is available in the 960-1164 MHz (L) and 5030-5091 MHz (C) bands. The performance of any C2 system is critically dependent upon the characteristics of the air-ground (AG) channel. Therefore, as part of its UAS Integration in the NAS (UAS in the NAS) project, the U.S. National Aeronautics and Space Administration (NASA) performed a series of air-ground propagation flight tests to collect AG channel data for model development and analysis of potential C2 communications links capable of providing the required reliability. NASA's Glenn Research Center (GRC) conducted an extensive air-ground channel propagation measurement campaign (at altitude) for frequencies in the 960-977 MHz and 5030-5091 MHz ranges, for seven different terrain environments. The measurements were conducted in 2013, and produced the largest set of AG channel data ever gathered to date. This data was subsequently processed to develop models for the AG channel. The statistics collected enabled the derivation of channel model parameters for both narrowband and wideband channels. In order to make the propagation data widely available, the resulting narrowband statistics were processed and submitted to the International Telecommunications Union - Radiocommunication Sector (ITU-R) Study Group 3 Data Banks. Formats for data tables were developed, and tables of the aggregate narrowband propagation statistics for the seven ground site terrain environments were prepared, submitted to, and approved by, the ITU-R Study Group 3. This paper provides brief background on the measurement campaign, collection and processing of data, and development of the narrowband data tables. It further provides examples of the data and its use.

radiofrequency spectrum↗

Narrowband Propagation Statistics of Aeronautical Mobile-Ground Links in the L- and C-Bands

To provide for the safe integration of unmanned aircraft systems (UAS) into the National Airspace System (NAS), command and control (C2) links must be highly reliable. Hence, protected aviation spectrum is required to support such links for UAS that are integrated into controlled non-segregated airspace. For air-ground (i.e., non-satellite) links, protected aviation spectrum to support C2 links is available in the 960-1164 MHz (L) and 5030-5091 MHz (C) bands. The performance of any C2 system is critically dependent upon the characteristics of the air-ground (AG) channel. Therefore, as part of its UAS Integration in the NAS (UAS in the NAS) project, the U.S. National Aeronautics and Space Administration (NASA) performed a series of air-ground propagation flight tests to collect AG channel data for model development and analysis of potential C2 communications links capable of providing the required reliability. NASA's Glenn Research Center (GRC) conducted an extensive air-ground channel propagation measurement campaign (at altitude) for frequencies in the 960-977 MHz and 5030-5091 MHz ranges, for seven different terrain environments. The measurements were conducted in 2013, and produced the largest set of AG channel data ever gathered to date. This data was subsequently processed to develop models for the AG channel. The statistics collected enabled the derivation of channel model parameters for both narrowband and wideband channels. In order to make the propagation data widely available, the resulting narrowband statistics were processed and submitted to the International Telecommunications Union Radiocommunication Sector (ITU-R) Study Group 3 Data Banks. Formats for data tables were developed, and tables of the aggregate narrowband propagation statistics for the seven ground site terrain environments were prepared, submitted to, and approved by, the ITU-R Study Group 3. This paper provides brief background on the measurement campaign, collection and processing of data, and development of the narrowband data tables. It further provides examples of the data and its use.

aircraft communications↗

Advanced tracking and data relay satellite system

The purpose of this communication satellite system are as follows: to provide NASA needs for satellite tracking and communications through the year 2012; to maintain and augment the current TDRS system when available satellite resources are expended in the latter part of the decade; to provide the necessary ground upgrade to support the augmented services; and to introduce new technology to reduce the system life cycle cost. It is concluded that no ATDRS spacecraft requirement for new modulation techniques, that data rate of 650 MBps is required, and that Space Station Freedom requirement is for 650 MBps data some time after the year 2000.

Stern, Daniel↗

Adaptive Independent Verification and Validation (IV&V) Reduces Risk of Software Impacting Safety in Artemis Missions

The National Aeronautics and Space Administration (NASA) is asking more of its human spaceflight programs than ever before through the collective Artemis Missions. The NASA Independent Verification and Validation (IV&V) Program contributes to NASA’s human spaceflight goals by providing IV&V services for NASA’s critical spacecraft and ground software. The IV&V Program is tasked with providing assurance from both individual and integrated mission software perspectives. The Artemis IV&V organization is actively supporting six distinct development efforts: Orion, the Space Launch System (SLS), Exploration Ground Systems (EGS), Mission Control Center (MCC), the Lunar Gateway, and the Human Landing System (HLS), representing a wide diversity of developer organizations, management structures, and development approaches. With much of this extremely complex flight and ground software being essential to human safety both on the ground and in space, Artemis IV&V is likewise challenged to provide more value-added assurance to future Artemis missions within a constrained budget. To meet this challenge, Artemis IV&V employs a variety of novel and evolving “Adaptive IV&V” approaches for planning and executing IV&V analysis to increase both the efficiency and effectiveness of the IV&V Program’s assurance activities, and to address the difficulties imposed by assuring software for a large, highly integrated, multi-mission enterprise managed and executed by physically and organizationally distinct programs. Instilling agile principles like iterative planning cycles, self-organizing teams, and regular retrospectives, into IV&V planning and execution has led to a more rapid turnaround of a minimum viable assurance product and allowed for increased alignment of assurance activities with development progress. Adopting an assurance case methodology has led to greater consistency and clearer communication of assurance design and provided a foundation for long-term maintenance of assurance plans, products, and results across missions. The IV&V-developed Assurance / Safety Case Analytical Network (A-SCAN) framework and tool has enabled the quantification and tracking of system/software risk and confidence. These confidence measures provide a means to repeatedly express the impact of planned and completed assurance work and the remaining residual risk. Applied as part of a “Follow-the-Risk” organizational ethos, this allows consistent rightsizing of analysis rigor and intensity commensurate with the perceived risk of defects, as well as appropriate targeting of the highest risk areas of the software to find safety issues before they can manifest. Finally, the development of the IV&V Advanced Risk Reduction Integrated Software Test and Operations Tri-program Lightweight Environment (ARRISTOTLE), an integrated software-only simulation of Orion, SLS, and EGS systems, has made it possible to independently test integrated pad and flight scenarios and inject faults to observe how the Artemis multi-program, mission software behaves in degraded modes and in response to hazards. These adaptive IV&V investments have enabled Artemis IV&V to become more efficient and effective in IV&V planning and execution and respond more readily to changes in the risk landscape, increasing the breadth and depth of risk reduction possible within the available resources. Residual risk tracking allows IV&V to communicate more effectively with stakeholders, both internal and external at all levels, and inform key decision-making personnel. This evolving assurance design approach provides IV&V surety that work is performed in the highest risk, most value-added areas of the software, to keep our astronauts and ground crews safe and ensure mission success.

Gerek A Whitman↗

Adaptive Independent Verification and Validation (IV&V) Reduces Risk of Software Impacting Safety in Artemis Missions

The National Aeronautics and Space Administration (NASA) is asking more of its human spaceflight programs than ever before through the collective Artemis Missions. The NASA Independent Verification and Validation (IV&V) Program contributes to NASA’s human spaceflight goals by providing IV&V services for NASA’s critical spacecraft and ground software. The IV&V Program is tasked with providing assurance from both individual and integrated mission software perspectives. The Artemis IV&V organization is actively supporting six distinct development efforts: Orion, the Space Launch System (SLS), Exploration Ground Systems (EGS), Mission Control Center (MCC), the Lunar Gateway, and the Human Landing System (HLS), representing a wide diversity of developer organizations, management structures, and development approaches. With much of this extremely complex flight and ground software being essential to human safety both on the ground and in space, Artemis IV&V is likewise challenged to provide more value-added assurance to future Artemis missions within a constrained budget. To meet this challenge, Artemis IV&V employs a variety of novel and evolving “Adaptive IV&V” approaches for planning and executing IV&V analysis to increase both the efficiency and effectiveness of the IV&V Program’s assurance activities, and to address the difficulties imposed by assuring software for a large, highly integrated, multi-mission enterprise managed and executed by physically and organizationally distinct programs. Instilling agile principles like iterative planning cycles, self-organizing teams, and regular retrospectives, into IV&V planning and execution has led to a more rapid turnaround of a minimum viable assurance product and allowed for increased alignment of assurance activities with development progress. Adopting an assurance case methodology has led to greater consistency and clearer communication of assurance design and provided a foundation for long-term maintenance of assurance plans, products, and results across missions. The IV&V-developed Assurance / Safety Case Analytical Network (A-SCAN) framework and tool has enabled the quantification and tracking of system/software risk and confidence. These confidence measures provide a means to repeatedly express the impact of planned and completed assurance work and the remaining residual risk. Applied as part of a “Follow-the-Risk” organizational ethos, this allows consistent rightsizing of analysis rigor and intensity commensurate with the perceived risk of defects, as well as appropriate targeting of the highest risk areas of the software to find safety issues before they can manifest. Finally, the development of the IV&V Advanced Risk Reduction Integrated Software Test and Operations Tri-program Lightweight Environment (ARRISTOTLE), an integrated software-only simulation of Orion, SLS, and EGS systems, has made it possible to independently test integrated pad and flight scenarios and inject faults to observe how the Artemis multi-program, mission software behaves in degraded modes and in response to hazards. These adaptive IV&V investments have enabled Artemis IV&V to become more efficient and effective in IV&V planning and execution and respond more readily to changes in the risk landscape, increasing the breadth and depth of risk reduction possible within the available resources. Residual risk tracking allows IV&V to communicate more effectively with stakeholders, both internal and external at all levels, and inform key decision-making personnel. This evolving assurance design approach provides IV&V surety that work is performed in the highest risk, most value-added areas of the software, to keep our astronauts and ground crews safe and ensure mission success.

Gerek Whitman↗