Search NASA⌕ Search

SEARCH · Search NASA

Results for “flight software design”

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 199 records · Page 11

Data reduction software for LORAN-C flight test evaluation

A set of programs designed to be run on an IBM 370/158 computer to read the recorded time differences from the tape produced by the LORAN data collection system, convert them to latitude/longitude and produce various plotting input files are described. The programs were written so they may be tailored easily to meet the demands of a particular data reduction job. The tape reader program is written in 370 assembler language and the remaining programs are written in standard IBM FORTRAN-IV language. The tape reader program is dependent upon the recording format used by the data collection system and on the I/O macros used at the computing facility. The other programs are generally device-independent, although the plotting routines are dependent upon the plotting method used. The data reduction programs convert the recorded data to a more readily usable form; convert the time difference (TD) numbers to latitude/longitude (lat/long), to format a printed listing of the TDs, lat/long, reference times, and other information derived from the data, and produce data files which may be used for subsequent plotting.

Fischer, J. P.↗

A Distributed Simulation Software System for Multi-Spacecraft Missions

The paper will provide an overview of the web-based distributed simulation software system developed for end-to-end, multi-spacecraft mission design, analysis, and test at the NASA Goddard Space Flight Center (GSFC). This software system was developed for an internal research and development (IR&D) activity at GSFC called the Distributed Space Systems (DSS) Distributed Synthesis Environment (DSE). The long-term goal of the DSS-DSE is to integrate existing GSFC stand-alone test beds, models, and simulation systems to create a "hands on", end-to-end simulation environment for mission design, trade studies and simulations. The short-term goal of the DSE was therefore to develop the system architecture, and then to prototype the core software simulation capability based on a distributed computing approach, with demonstrations of some key capabilities by the end of Fiscal Year 2002 (FY02). To achieve the DSS-DSE IR&D objective, the team adopted a reference model and mission upon which FY02 capabilities were developed. The software was prototyped according to the reference model, and demonstrations were conducted for the reference mission to validate interfaces, concepts, etc. The reference model, illustrated in Fig. 1, included both space and ground elements, with functional capabilities such as spacecraft dynamics and control, science data collection, space-to-space and space-to-ground communications, mission operations, science operations, and data processing, archival and distribution addressed.

Burns, Richard↗

An Internet Protocol-Based Software System for Real-Time, Closed-Loop, Multi-Spacecraft Mission Simulation Applications

The paper will provide an overview of the web-based distributed simulation software system developed for end-to-end, multi-spacecraft mission design, analysis, and test at the NASA Goddard Space Flight Center (GSFC). This software system was developed for an internal research and development (IR&D) activity at GSFC called the Distributed Space Systems (DSS) Distributed Synthesis Environment (DSE). The long-term goal of the DSS-DSE is to integrate existing GSFC stand-alone test beds, models, and simulation systems to create a "hands on", end-to-end simulation environment for mission design, trade studies and simulations. The short-term goal of the DSE was therefore to develop the system architecture, and then to prototype the core software simulation capability based on a distributed computing approach, with demonstrations of some key capabilities by the end of Fiscal Year 2002 (FY02). To achieve the DSS-DSE IR&D objective, the team adopted a reference model and mission upon which FY02 capabilities were developed. The software was prototyped according to the reference model, and demonstrations were conducted for the reference mission to validate interfaces, concepts, etc. The reference model, illustrated in Fig. 1, included both space and ground elements, with functional capabilities such as spacecraft dynamics and control, science data collection, space-to-space and space-to-ground communications, mission operations, science operations, and data processing, archival and distribution addressed.

Davis, George↗

Development of a Supervisory Tool for Fault Detection and Diagnosis of DC Electric Power Systems with the Application of Deep Space Vehicles

This dissertation formulates the problem of fault detection and diagnosis of DC electric power systems for the application of autonomous spacecraft. The ability to accurately identify and isolate failures in the electrical power system is critical to ensure the reliability of a spacecraft. This problem becomes more pronounced during deep space missions that lack the ability to monitor from ground control. The current state of electrical power system fault supervision is insufficient to guarantee highly reliable and robust operation. To solve this issue, a combination of model-based and rules-based techniques are used in a hierarchical framework to improve the diagnostic performance of the spacecraft electrical power system. Noise, disturbances, and modeling errors are considered in the design of the method. Practical considerations related to the hardware and software are discussed for the flight application. A wide array of failure types are simulated in a series of experiments to assess the functionality of the design. The experiments showed that the methods used improved the diagnostic capability of the autonomous system while taking into account the limitations attributed to flight software requirements. The significance of this study is to provide a framework capable of advanced diagnostics of an electrical power system with little to no interaction from a human operator.

Fault Detection and Diagnosis↗

Design of the software development and verification system (SWDVS) for shuttle NASA study task 35

An overview of the Software Development and Verification System (SWDVS) for the space shuttle is presented. The design considerations, goals, assumptions, and major features of the design are examined. A scenario that shows three persons involved in flight software development using the SWDVS in response to a program change request is developed. The SWDVS is described from the standpoint of different groups of people with different responsibilities in the shuttle program to show the functional requirements that influenced the SWDVS design. The software elements of the SWDVS that satisfy the requirements of the different groups are identified.

Drane, L. W.↗

Voyager programmability - Experiences in control system adaptation

The two Voyager spacecraft were designed with reprogrammable attitude and articulation control system flight control processors to permit inflight modification of the software. These software modifications were designed to: (1) correct for hardware failures that occurred during the interstellar journey, and (2) improve spacecraft dynamic performance for better control so that, by minimizing the use of propellant, the life of the mission could be extended. It is suggested that, in the future, spacecraft be launched with additional unused memory to deal with anomalies unforeseen in the decision-making process.

Patel, Keyur↗

Selecting a software development methodology

The state of the art analytical techniques for the development and verification of digital flight control software is studied and a practical designer oriented development and verification methodology is produced. The effectiveness of the analytic techniques chosen for the development and verification methodology are assessed both technically and financially. Technical assessments analyze the error preventing and detecting capabilities of the chosen technique in all of the pertinent software development phases. Financial assessments describe the cost impact of using the techniques, specifically, the cost of implementing and applying the techniques as well as the relizable cost savings. Both the technical and financial assessment are quantitative where possible. In the case of techniques which cannot be quantitatively assessed, qualitative judgements are expressed about the effectiveness and cost of the techniques. The reasons why quantitative assessments are not possible will be documented.

Jones, R. E.↗

NASA R and T aerospace plane vehicles: Progress and plans

Progress made in key technologies such as materials, structures, aerothermodynamics, hypersonic aerodynamics, and hypersonic airbreathing propulsion are reported. Advances were made in more generic, areas such as active controls, flight computer hardware and software, and interdisciplinary analytical design methodology. These technology advances coupled with the development of and experiences with the Space Shuttle make feasible aerospace plane-type vehicles that meet the more demanding requirements of various DOD missions and/or an all-weather Shuttle II with reduced launch costs. Technology needs and high payoff technologies, and the technology advancements in propulsion, control-configured-vehicles, aerodynamics, aerothermodynamics, aerothermal loads, and materials and structures were studied. The highest payoff technologies of materials and structures including thermal-structural analysis and high temperature test techniques are emphasized. The high priority technology of propulsion, and plans, of what remains to be done rather than firm program commitments, are briefly discussed.

Dixon, S. C.↗

Complete positive ion, electron, and ram negative ion measurements near Comet Halley (COPERNIC) plasma experiment for the European Giotto Mission

Participation of U.S. scientists on the COPERNIC (COmplete Positive ions, Electrons and Ram Negative Ion measurements near Comet Halley) plasma experiment on the Giotto mission is described. The experiment consisted of two detectors: the EESA (electron electrostatic analyzer) which provided three-dimensional measurements of the distribution of electrons from 10 eV to 30 keV, and the PICCA (positive ion cluster composition analyzer) which provided mass analysis of positively charged cold cometary ions from mass 10 to 210 amu. In addition, a small 3 deg wide sector of the EESA looking in the ram direction was devoted to the detection of negatively charged cold cometary ions. Both detectors operated perfectly up to near closest approach (approx. 600 km) to Halley, but impacts of dust particles and neutral gas on the spacecraft contaminated parts of the data during the last few minutes. Although no flight hardware was fabricated in the U.S., The U.S. made very significant contributions to the hardware design, ground support equipment (GSE) design and fabrication, and flight and data reduction software required for the experiment, and also participated fully in the data reduction and analysis, and theoretical modeling and interpretation. Cometary data analysis is presented.

Lin, Robert P.↗

Research into the development of a knowledge acquisition taxonomy

Monthly progress reports for September 1990 to January 1991 are given. Topics that are briefly covered include problem solving and learning taxonomies, knowledge acquisition techniques, software design, air traffic control, and space shuttle flight control.

Fink, Pamela K.↗

Formal specification and verification of Ada software

The use of formal methods in software development achieves levels of quality assurance unobtainable by other means. The Larch approach to specification is described, and the specification of avionics software designed to implement the logic of a flight control system is given as an example. Penelope is described which is an Ada-verification environment. The Penelope user inputs mathematical definitions, Larch-style specifications and Ada code and performs machine-assisted proofs that the code obeys its specifications. As an example, the verification of a binary search function is considered. Emphasis is given to techniques assisting the reuse of a verification effort on modified code.

Hird, Geoffrey R.↗

A simulated annealing approach to schedule optimization for the SES facility

The Shuttle Engineering Simulator (SES) is a facility which houses the software and hardware for a variety of simulation systems. The simulators include the Autonomous Remote Manipulator, the Manned Maneuvering Unit, Orbiter/Space Station docking, and shuttle entry and landing. The SES simulators are used by various groups throughout NASA. For example, astronauts use the SES to practice maneuvers with the shuttle equipment; programmers use the SES to test flight software; and engineers use the SES for design and analysis studies. Due to its high demand, the SES is busy twenty-four hours a day and seven days a week. Scheduling the facility is a problem that is constantly growing and changing with the addition of new equipment. Currently a number of small independent programs have been developed to help solve the problem, but the long-term answer lies in finding a flexible, integrated system that provides the user with the ability to create, optimize, and edit the schedule. COMPASS is an interactive and highly flexible scheduling system. However, until recently COMPASS did not provide any optimization features. This paper describes the simulated annealing extension to COMPASS. It now allows the user to interweave schedule creation, revision, and optimization. This practical approach was necessary in order to satisfy the operational requirements of the SES.

Mcmahon, Mary Beth↗

NASA Crew Launch Vehicle Flight Test Process

In response to the Vision for Space Exploration, the National Aeronautics and Space Administration (NASA) has defined a new space exploration architecture to return humans to the Moon and to prepare for human exploration of Mars. One of the first new developments will be the Crew Launch Vehicle (CLV) , which will carry the Crew Exploration Vehicle (CEV) into Low Earth Orbit (LEO) to support International Space Station (ISS) missions and, later, to support lunar missions. As part of the CLV development, NASA will perform a series of CLV flight tests. The tests will provide data that will inform the engineering and design process and verify the flight hardware and software. In addition, the data gained from the flight tests will be used to certify the new CLV/CEV vehicle for human space flight. This paper will provide an overview of the CLV flight test process and details of the individual flight tests

Davis, Stephan R.↗

Ares I-X Flight Test Philosophy

In response to the Vision for Space Exploration, the National Aeronautics and Space Administration (NASA) has defined a new space exploration architecture to return humans to the Moon and prepare for human exploration of Mars. One of the first new developments will be the Ares I Crew Launch Vehicle (CLV), which will carry the Orion Crew Exploration Vehicle (CEV), into Low Earth Orbit (LEO) to support International Space Station (ISS) missions and, later, support lunar missions. As part of Ares I development, NASA will perform a series of Ares I flight tests. The tests will provide data that will inform the engineering and design process and verify the flight hardware and software. The data gained from the flight tests will be used to certify the new Ares/Orion vehicle for human space flight. The primary objectives of this first flight test (Ares I-X) are the following: Demonstrate control of a dynamically similar integrated Ares CLV/Orion CEV using Ares CLV ascent control algorithms; Perform an in-flight separation/staging event between an Ares I-similar First Stage and a representative Upper Stage; Demonstrate assembly and recovery of a new Ares CLV-like First Stage element at Kennedy Space Center (KSC); Demonstrate First Stage separation sequencing, and quantify First Stage atmospheric entry dynamics and parachute performance; and Characterize the magnitude of the integrated vehicle roll torque throughout the First Stage (powered) flight. This paper will provide an overview of the Ares I-X flight test process and details of the individual flight tests.

Davis, S. R.↗

High-Speed Ring Bus

The high-speed ring bus at the Jet Propulsion Laboratory (JPL) allows for future growth trends in spacecraft seen with future scientific missions. This innovation constitutes an enhancement of the 1393 bus as documented in the Institute of Electrical and Electronics Engineers (IEEE) 1393-1999 standard for a spaceborne fiber-optic data bus. It allows for high-bandwidth and time synchronization of all nodes on the ring. The JPL ring bus allows for interconnection of active units with autonomous operation and increased fault handling at high bandwidths. It minimizes the flight software interface with an intelligent physical layer design that has few states to manage as well as simplified testability. The design will soon be documented in the AS-1393 standard (Serial Hi-Rel Ring Network for Aerospace Applications). The framework is designed for "Class A" spacecraft operation and provides redundant data paths. It is based on "fault containment regions" and "redundant functional regions (RFR)" and has a method for allocating cables that completely supports the redundancy in spacecraft design, allowing for a complete RFR to fail. This design reduces the mass of the bus by incorporating both the Control Unit and the Data Unit in the same hardware. The standard uses ATM (asynchronous transfer mode) packets, standardized by ITU-T, ANSI, ETSI, and the ATM Forum. The IEEE-1393 standard uses the UNI form of the packet and provides no protection for the data portion of the cell. The JPL design adds optional formatting to this data portion. This design extends fault protection beyond that of the interconnect. This includes adding protection to the data portion that is contained within the Bus Interface Units (BIUs) and by adding to the signal interface between the Data Host and the JPL 1393 Ring Bus. Data transfer on the ring bus does not involve a master or initiator. Following bus protocol, any BIU may transmit data on the ring whenever it has data received from its host. There is no centralized arbitration or bus granting. The JPL design provides for autonomous synchronization of the nodes on the ring bus. An address-synchronous latency adjust buffer (LAB) has been designed that cannot get out of synchronization and needs no external input. Also, a priority-driven cable selection behavior has been programmed into each unit on the ring bus. This makes the bus able to connect itself up, according to a maximum redundancy priority system, without the need for computer intervention at startup. Switching around a failed or switched-off unit is also autonomous. The JPL bus provides a map of all the active units for the host computer to read and use for fault management. With regard to timing, this enhanced bus recognizes coordinated timing on a spacecraft as critical and addresses this with a single source of absolute and relative time, which is broadcast to all units on the bus with synchronization maintained to the tens of nanoseconds. Each BIU consists of up to five programmable triggers, which may be programmed for synchronization of events within the spacecraft of instrument. All JPL-formatted data transmitted on the ring bus are automatically time-stamped.

Wysocky, Terry↗

Applications of Modeling and Simulation for Flight Hardware Processing at Kennedy Space Center

The Boeing Design Visualization Group (DVG) is responsible for the creation of highly-detailed representations of both on-site facilities and flight hardware using computer-aided design (CAD) software, with a focus on the ground support equipment (GSE) used to process and prepare the hardware for space. Throughout my ten weeks at this center, I have had the opportunity to work on several projects: the modification of the Multi-Payload Processing Facility (MPPF) High Bay, weekly mapping of the Space Station Processing Facility (SSPF) floor layout, kinematics applications for the Orion Command Module (CM) hatches, and the design modification of the Ares I Upper Stage hatch for maintenance purposes. The main goal of each of these projects was to generate an authentic simulation or representation using DELMIA V5 software. This allowed for evaluation of facility layouts, support equipment placement, and greater process understanding once it was used to demonstrate future processes to customers and other partners. As such, I have had the opportunity to contribute to a skilled team working on diverse projects with a central goal of providing essential planning resources for future center operations.

Marshall, Jennifer L.↗