Search NASA⌕ Search

SEARCH · Search NASA

Results for “Flight Control System Verification”

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 433 records · Page 24

Assessment of Human Factors

Human Factors Engineering, often referred to as Ergonomics, is a science that applies a detailed understanding of human characteristics, capabilities, and limitations to the design, evaluation, and operation of environments, tools, and systems for work and daily living. Human Factors is the investigation, design, and evaluation of equipment, techniques, procedures, facilities, and human interfaces, and encompasses all aspects of human activity from manual labor to mental processing and leisure time enjoyments. In spaceflight applications, human factors engineering seeks to: (1) ensure that a task can be accomplished, (2) maintain productivity during spaceflight, and (3) ensure the habitability of the pressurized living areas. DSO 904 served as a vehicle for the verification and elucidation of human factors principles and tools in the microgravity environment. Over six flights, twelve topics were investigated. This study documented the strengths and limitations of human operators in a complex, multifaceted, and unique environment. By focusing on the man-machine interface in space flight activities, it was determined which designs allow astronauts to be optimally productive during valuable and costly space flights. Among the most promising areas of inquiry were procedures, tools, habitat, environmental conditions, tasking, work load, flexibility, and individual control over work.

Mount, Frances↗

S&MA Internship to Support Orion and the European Service Module

As a University Space Research Association (USRA) intern for NASA Johnson Space Center (JSC) during the summer 2016 work term, I worked on three main projects for the Space Exploration Division (NC) of the Safety and Mission Assurance (S&MA) Directorate. I worked on all three projects concurrently. One of the projects involved facilitating the status and closure of technical actions that were created during European Service Module (ESM) safety reviews by the MPCV Safety & Engineering Review Panel (MSERP). The two main duties included accurately collecting and summarizing qualitative data, and communicating that information to the European Space Agency (ESA) and Airbus (ESA's prime contractor) in a clear, succinct and precise manner. This project also required that I create a report on the challenges and opportunities of international S&MA. With its heavy emphasis on soft skills, this project taught me how to communicate better, by showing me how to present and share information in an easy-to-read and understandable format, and by showing me how to cooperate with and culturally respect international partners on a technical project. The second project involved working with the Orion Thermal Protection System (TPS) Process Failure Modes and Effects Analysis (PFMEA) Working Group to create the first full version of the Orion TPS PFMEA. The Orion TPS PFMEA Working Group met twice a week to analyze the Avcoat block installation process for failure modes, the failure modes effects, and how such failure modes could be controlled. I was in charge of implementing changes that were discussed in meeting, but were not implemented real time. Another major task included creating a significant portion of the content alongside another team member outside the two weekly meetings. This project caused me to become knowledgeable about TPS, heatshields, space-rated manufacturing, and non-destructive evaluation (NDE). The project also helped me to become better at working with a small team and helped improved my technical communication skills. My main duty for the third project was creating a Safety Verification Tracking Log (SVTL) for the Orbital Maneuvering System Engine (OMS-E), and contacting subject matter experts to close Hazard Report (HR) control verifications. This project also required me to support other OMS-E safety process tasks, like monitoring OMS-E vibration testing for Quality Assurance (QA) purposes. This project helped me become even more proficient in Excel. Throughout the project, I gained knowledge about the OMS-E system and improved my understanding of pressure systems and propellant systems. In terms of education goals, this work term has affirmed my desire to take a few more space-related courses, like orbital mechanics, so that I can have a better understanding of human spaceflight and the industry surrounding it. However, the work term did not persuade me to pursue a master's degree. In terms of career goals, this work term has helped me clarify the direction I would like to head in the future. The perspective of three summer terms working for NASA in S&MA has allowed me to observe that most S&MA employees joined S&MA after working in other NASA directorates, such as Engineering or Flight Operations. It is my belief that it would be advantageous for both NASA and I for me to broaden my knowledge base and technical skill set by completing hands-on technical work on human spaceflight projects, and for me to integrate my safety experience directly into technical work in other directorates. The other significant advantage to this proposed situation is that if I were to eventually return to S&MA, I would be returning with a substantial set of hands-on technical experience and knowledge, which would be a significant resource for S&MA tasks and projects.

Hutcheson, Connor↗

NASA X-34 Technology in Motion

The X-34 technology development program is a joint industry/government project to develop, test, and operate a small, fully-reusable hypersonic flight vehicle. The objective is to demonstrate key technologies and operating concepts applicable to future reusable launch vehicles. Integrated in the vehicle are various systems to assure successful completion of mission objectives, including the Main Propulsion System (MPS). NASA-Marshall Space Flight Center (MSFC) is responsible for developing the X-34's MPS including the design and complete build package for the propulsion system components. The X-34 will be powered by the Fastrac Engine, which is currently in design and development at NASA-MSFC. Fastrac is a single-stage main engine, which burns a mixture of liquid oxygen (LOX) and kerosene(RP-1). The interface between the MPS and Fastrac engine are critical for proper system operation and technologies applicable to future reusable launch vehicles. Deneb's IGRIP software package with the Dynamic analysis option provided a key tool for conducting studies critical to this interface as well as a mechanism to drive the design of the LOX and RP-1 feedlines. Kinematic models were created for the Fastrac Engine and the feedlines for various design concepts. Based on the kinematic simulation within Envision, design and joint limits were verified and system interference controlled. It was also critical to the program to evaluate the effect of dynamic loads visually, providing a verification tool for dynamic analysis and in some cases uncovering areas that had not been considered. Deneb's software put the X-34 technology in motion and has been a key factor in facilitating the strenuous design schedule.

Beech, Geoffrey↗

The Role and Quality of Software Safety in the NASA Constellation Program

In this study, we examine software safety risk in the early design phase of the NASA Constellation spaceflight program. Obtaining an accurate, program-wide picture of software safety risk is difficult across multiple, independently-developing systems. We leverage one source of safety information, hazard analysis, to provide NASA quality assurance managers with information regarding the ongoing state of software safety across the program. The goal of this research is two-fold: 1) to quantify the relative importance of software with respect to system safety; and 2) to quantify the level of risk presented by software in the hazard analysis. We examined 154 hazard reports created during the preliminary design phase of three major flight hardware systems within the Constellation program. To quantify the importance of software, we collected metrics based on the number of software-related causes and controls of hazardous conditions. To quantify the level of risk presented by software, we created a metric scheme to measure the specificity of these software causes. We found that from 49-70% of hazardous conditions in the three systems could be caused by software or software was involved in the prevention of the hazardous condition. We also found that 12-17% of the 2013 hazard causes involved software, and that 23-29% of all causes had a software control. Furthermore, 10-12% of all controls were software-based. There is potential for inaccuracy in these counts, however, as software causes are not consistently scoped, and the presence of software in a cause or control is not always clear. The application of our software specificity metrics also identified risks in the hazard reporting process. In particular, we found a number of traceability risks in the hazard reports may impede verification of software and system safety.

Layman, Lucas↗

Formulation and verification of frequency response system identification techniques for large space structures

For the past several years much effort has been given to the development of techniques for designing control systems for large space structures (LSS's). The main objective of these efforts has been to develop a LSS control methodology that produces designs that meet strenuous performance requirements and are robust to model inaccuracies. Unfortunately, performance and robustness are conflicting requirements. Because LSS's can not be fully tested on ground, it has become an accepted fact that the design of LSS control systems to meet performance requirements can not be completed until the LSS is placed on-orbit and tested and an accurate model is extracted from on-orbit test results. Modern MIMO sampled-data frequency response design techniques are viable candidates for designing LSS control systems. First, this paper presents techniques for performing MIMO system identification (ID) from test data. Then, techniques for improving the performance of the system ID process in the presence of noise are presented. Finally, practical utility of the system ID approaches are validated by the presentation of results obtained from application on the LSS Ground Test Facility at Marshall Space Flight Center.

Mitchell, Jerrel R.↗

Mars 2020 Entry, Descent, and Landing Software Implementation

On February 18th, 2021, the Mars 2020 project's Perseverance Rover successfully touched down on the Martian surface after nearly eight years of development. The Mars 2020 Entry, Descent, and Landing (EDL) System largely leveraged heritage from the Mars Science Laboratory (MSL) EDL System while employing targeted technological advancements. The landing process is autonomously directed by a software behavior implemented in the rover's primary flight computer called the EDL Timeline that assumes control of the vehicle six days before atmospheric entry. In addition to performing the critical function of landing the rover on the Martian surface, the EDL timeline behavior must co-exist in a non-partitioned software and system environment with other high-level functions that accomplish the goals for the rest of the mission. Due to the criticality of EDL, the potential for loss of mission, and a need for complete system autonomy, the standard for how the EDL Timeline interacts with other functions in the system is highly constrained. This paper first walks through the basics of the EDL Timeline mechanics and how the behavior is designed to account for internal system variations and environmental unknowns. It then summarizes the interactions between the EDL timeline and other high-level system behaviors like spacecraft mode transitions and system fault protection, focusing on the complications that arise when passing spacecraft control between executive functions. Although the MSL-inherited EDL System is reliable and capable, targeted updates and a thorough verification and validation program were required for Mars 2020. This paper discusses changes made to close vulnerabilities discovered during both MSL and Mars 2020 development cycles, landing system capability enhancements that were enabling for Mars 2020's mission, and how these updates were integrated with the heritage system. It then describes how both analysis and testing campaigns were utilized to verify and validate all aspects of EDL and system behaviors that run during the six days before landing, as well as the operational workarounds that were needed to address problems found during the development and commissioning process. Finally, this paper imparts lessons learned from Mars 2020 EDL development, implementation, and operations, emphasizing how systems designed to conduct time-critical mission events with low margin of error can be improved in the future.

Stehura, Aaron↗

Use of Human Modeling Simulation Software in the Task Analysis of the Environmental Control and Life Support System Component Installation Procedures

Virtual reality and simulation applications are becoming widespread in human task analysis. These programs have many benefits for the Human Factors Engineering field. Not only do creating and using virtual environments for human engineering analyses save money and time, this approach also promotes user experimentation and provides increased quality of analyses. This paper explains the human engineering task analysis performed on the Environmental Control and Life Support System (ECLSS) space station rack and its Distillation Assembly (DA) subsystem using EAI's human modeling simulation software, Jack. When installed on the International Space Station (ISS), ECLSS will provide the life and environment support needed to adequately sustain crew life. The DA is an Orbital Replaceable Unit (ORU) that provides means of wastewater (primarily urine from flight crew and experimental animals) reclamation. Jack was used to create a model of the weightless environment of the ISS Node 3, where the ECLSS is housed. Computer aided drawings of the ECLSS rack and DA system were also brought into the environment. Anthropometric models of a 95th percentile male and 5th percentile female were used to examine the human interfaces encountered during various ECLSS and DA tasks. The results of the task analyses were used in suggesting modifications to hardware and crew task procedures to improve accessibility, conserve crew time, and add convenience for the crew. This paper will address some of those suggested modifications and the method of presenting final analyses for requirements verification.

Estes, Samantha↗

Safety & Mission Assurance (SMA) Activities in Support of Artemis I and Plans for Artemis II

The Artemis I mission in 2022 accomplished humanity’s first venture beyond Low-Earth Orbit (LEO) with a human-rated spacecraft in over fifty years. Artemis comprises several key Program elements – Multi-Purpose Crew Vehicle (MPCV) Orion Crew Module, Service Module, Launch Abort System; the Space Launch System (SLS) and the Exploration Ground System (EGS). Much of our human spaceflight experience with crewed lunar missions is captured in historical program documents, but first-hand knowledge is limited to a few spaceflight veterans. Missions to LEO have offered the opportunity of direct, near-instantaneous communications and assistance, and the ability to return to Earth within a matter of hours in case of emergency. Outward-bound missions do not have these features and will require a more autonomous and reliable spacecraft. The assessment of compliance with applicable safety requirements and adequacy of hazard controls and verifications is the responsibility of the MPCV Safety and Engineering Review Panel (MSERP), along with a Joint [NASA/ESA] Safety and Engineering Review Panel (JSERP) for the review of the European Service Module (ESM). The MSERP has two features that are relatively unique amongst NASA safety panels. First, NASA Engineering was added as a Panel co-chair, which enhanced the Engineering organization’s engagement and level of understanding of hazard analysis methodology and results. The MSERP has representation from each office, including Flight Operations Directorate (FOD) and Health and Medical Technical Authority, supporting the Orion Program in addition to the Engineering and Safety Technical Authority co-chairs. Second, the JSERP has a second set of co-chairs from ESA Engineering and ESA Product Assurance and Safety organizations, which recognizes the international arrangement as one of partnership. This paper will focus on SMA processes, activities, and plans for the Orion element and explore unique challenges associated with Artemis II as we approach the flight of the first crewed Orion vehicle.

Paul J. Collier↗

Systems Integration Processes for NASA's Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable low earth orbit. This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and non-propulsion elements within NASA's Crew Launch Vehicle (CLV). The objective of the CLV is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to Low Earth Orbit (LEO) in support of the lunar and Mars missions. The CLV must successfully provide the capability within cost and schedule with an acceptable risk approach. This paper will describe in detail the systems engineering management processes that will be applied to assure CLV Project success through complete and efficient technical integration. Discussion of specific processes for requirements development and verification, integrated design and analysis, integrated simulation and testing and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The CLV Project is broken logically into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these CLV elements and among the other Constellation projects. Launch vehicle stack integration (CLV to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage will also be discussed. The processes for decomposing requirements to the Elements and ensuring that requirements have been correctly validated, decomposed, allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements will be discussed.

Reuter, James L.↗

The 2004 NASA Aerospace Battery Workshop

Topics covered include: Super NiCd(TradeMark) Energy Storage for Gravity Probe-B Relativity Mission; Hubble Space Telescope 2004 Battery Update; The Development of Hermetically Sealed Aerospace Nickel-Metal Hydride Cell; Serial Charging Test on High Capacity Li-Ion Cells for the Orbiter Advanced Hydraulic Power System; Cell Equalization of Lithium-Ion Cells; The Long-Term Performance of Small-Cell Batteries Without Cell-Balancing Electronics; Identification and Treatment of Lithium Battery Cell Imbalance under Flight Conditions; Battery Control Boards for Li-Ion Batteries on Mars Exploration Rovers; Cell Over Voltage Protection and Balancing Circuit of the Lithium-Ion Battery; Lithium-Ion Battery Electronics for Aerospace Applications; Lithium-Ion Cell Charge Control Unit; Lithium Ion Battery Cell Bypass Circuit Test Results at the U.S. Naval Research Laboratory; High Capacity Battery Cell By-Pass Switches: High Current Pulse Testing of Lithium-Ion; Battery By-Pass Switches to Verify Their Ability to Withstand Short-Circuits; Incorporation of Physics-Based, Spatially-Resolved Battery Models into System Simulations; A Monte Carlo Model for Li-Ion Battery Life Projections; Thermal Behavior of Large Lithium-Ion Cells; Thermal Imaging of Aerospace Battery Cells; High Rate Designed 50 Ah Li-Ion Cell for LEO Applications; Evaluation of Corrosion Behavior in Aerospace Lithium-Ion Cells; Performance of AEA 80 Ah Battery Under GEO Profile; LEO Li-Ion Battery Testing; A Review of the Feasibility Investigation of Commercial Laminated Lithium-Ion Polymer Cells for Space Applications; Lithium-Ion Verification Test Program; Panasonic Small Cell Testing for AHPS; Lithium-Ion Small Cell Battery Shorting Study; Low-Earth-Orbit and Geosynchronous-Earth-Orbit Testing of 80 Ah Batteries under Real-Time Profiles; Update on Development of Lithium-Ion Cells for Space Applications at JAXA; Foreign Comparative Technology: Launch Vehicle Battery Cell Testing; 20V, 40 Ah Lithium Ion Polymer Battery for the Spacesuit; Low Temperature Life-Cycle Testing of a Lithium-Ion Battery for Low-Earth-Orbiting Spacecraft; and Evaluation of the Effects of DoD and Charge Rate on a LEO Optimized 50 Ah Li-Ion Aerospace Cell.

Source record↗

A Re-programmable Platform for Dynamic Burn-in Test of Xilinx Virtexll 3000 FPGA for Military and Aerospace Applications

Field Programmable Gate Arrays (FPGA) have played increasingly important roles in military and aerospace applications. Xilinx SRAM-based FPGAs have been extensively used in commercial applications. They have been used less frequently in space flight applications due to their susceptibility to single-event upsets. Reliability of these devices in space applications is a concern that has not been addressed. The objective of this project is to design a fully programmable hardware/software platform that allows (but is not limited to) comprehensive static/dynamic burn-in test of Virtex-II 3000 FPGAs, at speed test and SEU test. Conventional methods test very few discrete AC parameters (primarily switching) of a given integrated circuit. This approach will test any possible configuration of the FPGA and any associated performance parameters. It allows complete or partial re-programming of the FPGA and verification of the program by using read back followed by dynamic test. Designers have full control over which functional elements of the FPGA to stress. They can completely simulate all possible types of configurations/functions. Another benefit of this platform is that it allows collecting information on elevation of the junction temperature as a function of gate utilization, operating frequency and functionality. A software tool has been implemented to demonstrate the various features of the system. The software consists of three major parts: the parallel interface driver, main system procedure and a graphical user interface (GUI).

Field Programmable Gate Arrays (FPGA)↗

Preparation for and Performance of a Pseudomonas aeruginosa Biofilm Experiment On Board the International Space Station

Biofilms are a problem on Earth given their ability to degrade the materials upon which they grow and due to their relevance to infections. Remarkably, 65% and 80% of infections and chronic diseases on Earth are associated with biofilms, respectively. In space, these problems' impact is higher because the crew's lives and mission success depend on nominal operation of mechanical systems. Furthermore, the isolated confined environment nature of spaceflight may increase the rates of disease transmission. In the case of the International Space Station (ISS), biofilms are an identified problem on the Environmental Control and Life Support System (ECLSS), namely on the water processor assembly (WPA). In late 2019, the Space Biofilms experiment launched towards ISS to (i) characterize the mass, thickness, morphology, and gene expression of biofilms formed in space with respect to matched Earth controls, (ii) interrogate the expression of antimicrobial resistance genes, and (iii) test novel materials as potential biofilm control strategies for future ECLSS components. For this, 288 bacterial samples were prepared prior to the launch of the Northrop Grumman CRS-12 mission from NASA's Wallops Flight Facility. The samples were integrated into the spaceflight hardware, BioServe's Fluid Processing Apparatus (FPA) packed in sets of eight in Group Activation Packs (GAP). Half of these samples were activated and terminated on orbit by NASA astronauts Jessica Meir and Christina Koch, while the remaining half were processed equivalently on Earth. The spaceflight bacterial samples of Space Biofilms returned on board SpaceX' CRS-19 Dragon spacecraft, in early 2020. We here describe the test campaign implemented to verify the experiment design and confirm it would enable us to achieve the project's scientific goals. This campaign ended with the Experiment Verification Test (EVT), from which we here present example morphology and transcriptomic results. We describe in detail the sample preparation prior to flight, including cleaning and sterilization of the coupons of six materials (SS316, passivated-SS316, lubricant impregnated surface, catheter-grade silicone with and without a nanotopography, and cellulose membrane), loading and integration of growth media, bacterial inoculum, fixative and preservative to enable experiment termination on orbit. Additionally, we describe the performance of the experiment on board the ISS, including crew activities, use of assets, temperature profile, and experiment timeline; all leading to a successful spaceflight experiment.

Pamela Flores↗

Surface Landing Site Weather Analysis for Constellation Program

Weather information is an important asset for NASA's Constellation Program in developing the next generation space transportation system to fly to the International Space Station, the Moon and, eventually, to Mars. Weather conditions can affect vehicle safety and performance during multiple mission phases ranging from pre-launch ground processing to landing and recovery operations, including all potential abort scenarios. Meteorological analysis is an important contributor, not only to the development and verification of system design requirements but also to mission planning and active ground operations. Of particular interest are the surface atmospheric conditions at both nominal and abort landing sites for the manned Orion capsule. Weather parameters such as wind, rain, and fog all play critical roles in the safe landing of the vehicle and subsequent crew and vehicle recovery. The Marshall Space Flight Center Natural Environments Branch has been tasked by the Constellation Program with defining the natural environments at potential landing zones. Climatological time series of operational surface weather observations are used to calculate probabilities of occurrence of various sets of hypothetical vehicle constraint thresholds, Data are available for numerous geographical locations such that statistical analysis can be performed for single sites as well as multiple-site network configurations. Results provide statistical descriptions of how often certain weather conditions are observed at the site(s) and the percentage that specified criteria thresholds are matched or exceeded. Outputs are tabulated by month and hour of day to show both seasonal and diurnal variation. This paper will describe the methodology used for data collection and quality control, detail the types of analyses performed, and provide a sample of the results that can be obtained,

Altino, Karen M.↗

Fluids and Combustion Facility: Combustion Integrated Rack Modal Model Correlation

The Fluids and Combustion Facility (FCF) is a modular, multi-user, two-rack facility dedicated to combustion and fluids science in the US Laboratory Destiny on the International Space Station. FCF is a permanent facility that is capable of accommodating up to ten combustion and fluid science investigations per year. FCF research in combustion and fluid science supports NASA's Exploration of Space Initiative for on-orbit fire suppression, fire safety, and space system fluids management. The Combustion Integrated Rack (CIR) is one of two racks in the FCF. The CIR major structural elements include the International Standard Payload Rack (ISPR), Experiment Assembly (optics bench and combustion chamber), Air Thermal Control Unit (ATCU), Rack Door, and Lower Structure Assembly (Input/Output Processor and Electrical Power Control Unit). The load path through the rack structure is outlined. The CIR modal survey was conducted to validate the load path predicted by the CIR finite element model (FEM). The modal survey is done by experimentally measuring the CIR frequencies and mode shapes. The CIR model was test correlated by updating the model to represent the test mode shapes. The correlated CIR model delivery is required by NASA JSC at Launch-10.5 months. The test correlated CIR flight FEM is analytically integrated into the Shuttle for a coupled loads analysis of the launch configuration. The analysis frequency range of interest is 0-50 Hz. A coupled loads analysis is the analytical integration of the Shuttle with its cargo element, the Mini Payload Logistics Module (MPLM), in the Shuttle cargo bay. For each Shuttle launch configuration, a verification coupled loads analysis is performed to determine the loads in the cargo bay as part of the structural certification process.

McNelis, Mark E.↗

NASA Ames Research Center R and D Services Directorate Biomedical Systems Development

The Ames Research Center R&D Services Directorate teams with NASA, other government agencies and/or industry investigators for the development, design, fabrication, manufacturing and qualification testing of space-flight and ground-based experiment hardware for biomedical and general aerospace applications. In recent years, biomedical research hardware and software has been developed to support space-flight and ground-based experiment needs including the E 132 Biotelemetry system for the Research Animal Holding Facility (RAHF), E 100 Neurolab neuro-vestibular investigation systems, the Autogenic Feedback Systems, and the Standard Interface Glove Box (SIGB) experiment workstation module. Centrifuges, motion simulators, habitat design, environmental control systems, and other unique experiment modules and fixtures have also been developed. A discussion of engineered systems and capabilities will be provided to promote understanding of possibilities for future system designs in biomedical applications. In addition, an overview of existing engineered products will be shown. Examples of hardware and literature that demonstrate the organization's capabilities will be displayed. The Ames Research Center R&D Services Directorate is available to support the development of new hardware and software systems or adaptation of existing systems to meet the needs of academic, commercial/industrial, and government research requirements. The Ames R&D Services Directorate can provide specialized support for: System concept definition and feasibility Mathematical modeling and simulation of system performance Prototype hardware development Hardware and software design Data acquisition systems Graphical user interface development Motion control design Hardware fabrication and high-fidelity machining Composite materials development and application design Electronic/electrical system design and fabrication System performance verification testing and qualification.

Pollitt, J.↗

Systems Integration Processes for NASA Ares I Crew Launch Vehicle

NASA's Exploration Initiative will require development of many new elements to constitute a robust system of systems. New launch vehicles are needed to place cargo and crew in stable Low Earth Orbit (LEO). This paper examines the systems integration processes NASA is utilizing to ensure integration and control of propulsion and nonpropulsion elements within NASA's Crew Launch Vehicle (CLV), now known as the Ares I. The objective of the Ares I is to provide the transportation capabilities to meet the Constellation Program requirements for delivering a Crew Exploration Vehicle (CEV) or other payload to LEO in support of the lunar and Mars missions. The Ares I must successfully provide this capability within cost and schedule, and with an acceptable risk approach. This paper will describe the systems engineering management processes that will be applied to assure Ares I Project success through complete and efficient technical integration. Discussion of technical review and management processes for requirements development and verification, integrated design and analysis, integrated simulation and testing, and the integration of reliability, maintainability and supportability (RMS) into the design will also be included. The Ares I Project is logically divided into elements by the major hardware groupings, and associated management, system engineering, and integration functions. The processes to be described herein are designed to integrate within these Ares I elements and among the other Constellation projects. Also discussed is launch vehicle stack integration (Ares I to CEV, and Ground and Flight Operations integration) throughout the life cycle, including integrated vehicle performance through orbital insertion, recovery of the first stage, and reentry of the upper stage. The processes for decomposing requirements to the elements and ensuring that requirements have been correctly validated, decomposed, and allocated, and that the verification requirements are properly defined to ensure that the system design meets requirements, will be discussed.

Taylor, James L.↗

Error coding simulations in C

When data is transmitted through a noisy channel, errors are produced within the data rendering it indecipherable. Through the use of error control coding techniques, the bit error rate can be reduced to any desired level without sacrificing the transmission data rate. The Astrionics Laboratory at Marshall Space Flight Center has decided to use a modular, end-to-end telemetry data simulator to simulate the transmission of data from flight to ground and various methods of error control. The simulator includes modules for random data generation, data compression, Consultative Committee for Space Data Systems (CCSDS) transfer frame formation, error correction/detection, error generation and error statistics. The simulator utilizes a concatenated coding scheme which includes CCSDS standard (255,223) Reed-Solomon (RS) code over GF(2(exp 8)) with interleave depth of 5 as the outermost code, (7, 1/2) convolutional code as an inner code and CCSDS recommended (n, n-16) cyclic redundancy check (CRC) code as the innermost code, where n is the number of information bits plus 16 parity bits. The received signal-to-noise for a desired bit error rate is greatly reduced through the use of forward error correction techniques. Even greater coding gain is provided through the use of a concatenated coding scheme. Interleaving/deinterleaving is necessary to randomize burst errors which may appear at the input of the RS decoder. The burst correction capability length is increased in proportion to the interleave depth. The modular nature of the simulator allows for inclusion or exclusion of modules as needed. This paper describes the development and operation of the simulator, the verification of a C-language Reed-Solomon code, and the possibility of using Comdisco SPW(tm) as a tool for determining optimal error control schemes.

Noble, Viveca K.↗

Automatic Testcase Generation for Flight Software

The TacSat3 project is applying Integrated Systems Health Management (ISHM) technologies to an Air Force spacecraft for operational evaluation in space. The experiment will demonstrate the effectiveness and cost of ISHM and vehicle systems management (VSM) technologies through onboard operation for extended periods. We present two approaches to automatic testcase generation for ISHM: 1) A blackbox approach that views the system as a blackbox, and uses a grammar-based specification of the system's inputs to automatically generate *all* inputs that satisfy the specifications (up to prespecified limits); these inputs are then used to exercise the system. 2) A whitebox approach that performs analysis and testcase generation directly on a representation of the internal behaviour of the system under test. The enabling technologies for both these approaches are model checking and symbolic execution, as implemented in the Ames' Java PathFinder (JPF) tool suite. Model checking is an automated technique for software verification. Unlike simulation and testing which check only some of the system executions and therefore may miss errors, model checking exhaustively explores all possible executions. Symbolic execution evaluates programs with symbolic rather than concrete values and represents variable values as symbolic expressions. We are applying the blackbox approach to generating input scripts for the Spacecraft Command Language (SCL) from Interface and Control Systems. SCL is an embedded interpreter for controlling spacecraft systems. TacSat3 will be using SCL as the controller for its ISHM systems. We translated the SCL grammar into a program that outputs scripts conforming to the grammars. Running JPF on this program generates all legal input scripts up to a prespecified size. Script generation can also be targeted to specific parts of the grammar of interest to the developers. These scripts are then fed to the SCL Executive. ICS's in-house coverage tools will be run to measure code coverage. Because the scripts exercise all parts of the grammar, we expect them to provide high code coverage. This blackbox approach is suitable for systems for which we do not have access to the source code. We are applying whitebox test generation to the Spacecraft Health INference Engine (SHINE) that is part of the ISHM system. In TacSat3, SHINE will execute an on-board knowledge base for fault detection and diagnosis. SHINE converts its knowledge base into optimized C code which runs onboard TacSat3. SHINE can translate its rules into an intermediate representation (Java) suitable for analysis with JPF. JPF will analyze SHINE's Java output using symbolic execution, producing testcases that can provide either complete or directed coverage of the code. Automatically generated test suites can provide full code coverage and be quickly regenerated when code changes. Because our tools analyze executable code, they fully cover the delivered code, not just models of the code. This approach also provides a way to generate tests that exercise specific sections of code under specific preconditions. This capability gives us more focused testing of specific sections of code.

Bushnell, David Henry↗