An Apollo Applications Program data relay terminal design study Final report
Design of data relay terminal to be incorporated into Saturn workshop as part of Apollo Applications Program
SEARCH · Engineering Papers
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.
Design of data relay terminal to be incorporated into Saturn workshop as part of Apollo Applications Program
The capabilities and design approach of the MIDAS (Man-machine Integration Design and Analysis System) computer-aided engineering (CAE) workstation under development by the Army-NASA Aircrew/Aircraft Integration Program is detailed. This workstation uses graphic, symbolic, and numeric prototyping tools and human performance models as part of an integrated design/analysis environment for crewstation human engineering. Developed incrementally, the requirements and design for Phase 3 (Dec. 1987 to Jun. 1989) are described. Software tools/models developed or significantly modified during this phase included: an interactive 3-D graphic cockpit design editor; multiple-perspective graphic views to observe simulation scenarios; symbolic methods to model the mission decomposition, equipment functions, pilot tasking and loading, as well as control the simulation; a 3-D dynamic anthropometric model; an intermachine communications package; and a training assessment component. These components were successfully used during Phase 3 to demonstrate the complex interactions and human engineering findings involved with a proposed cockpit communications design change in a simulated AH-64A Apache helicopter/mission that maps to empirical data from a similar study and AH-1 Cobra flight test.
In 2004, the Vision for Space Exploration (VSE) was announced by the United States President's Administration in an effort to explore space and to extend a human presence across our solar system. Subsequently, the National Aeronautics and Space Administration (NASA) established the Exploration Systems Mission Directorate (ESMD) to develop a constellation of new capabilities, supporting technologies, and foundational research that allows for the sustained and affordable exploration of space. Then, ESMD specified the primary mission for the Constellation Program to carry out a series of human expeditions, ranging from Low Earth Orbit (LEO) to the surface of Moon, Mars, and beyond for the purposes of conducting human exploration of space. Thus, the Constellation Program was established at the Lyndon B. Johnson Space Center (JSC) to manage the development of the flight and ground infrastructure and systems that can enable continued and extended human access to space. Constellation Program's "Design Objectives" call for an early attention to the program's life cycle costs management through the Program's Need, Goals, and Objectives (NGO) document, which provides the vision, scope, and key areas of focus for the Program. One general policy of the Constellation Program, found in the Constellation Architecture Requirements Document (CARD), states: "A sustainable program hinges on how effectively total life cycle costs are managed. Developmental costs are a key consideration, but total life cycle costs related to the production, processing, and operation of the entire architecture must be accounted for in design decisions sufficiently to ensure future resources are available for ever more ambitious missions into the solar system....It is the intent of the Constellation Program to aggressively manage this aspect of the program using the design policies and simplicity." To respond to the Program's strong desire to manage the program life cycle costs, special efforts were established to identify operability requirements to influence flight vehicle and ground infrastructure design in order to impact the life cycle operations costs, and stretch goal requirements were introduced to the Program. This paper will describe how these stretch goal requirements were identified, developed, refined, matured, approved, and infused into the CARD. The paper will also document several challenges encountered when infusing the stretch goal requirements into the Constellation Program.
The program procedures that were incorporated into an on-going "design-to-cost" spacecraft program are examined. Program procedures are the activities that support the development and operations of the flight unit: contract management, documents, integration meetings, engineering, and testing. This report is limited to the program procedures that were implemented, with emphasis on areas that may depart from normal satellite development practices.
Software considerations were developed for incorporation in the spacelab systems design, and include management concepts for top-down structured programming, composite designs for modular programs, and team management methods for production programming.
The computer programs and derivations generated in support of the modeling and design optimization program are presented. Programs for the buck regulator, boost regulator, and buck-boost regulator are described. The computer program for the design optimization calculations is presented. Constraints for the boost and buck-boost converter were derived. Derivations of state-space equations and transfer functions are presented. Computer lists for the converters are presented, and the input parameters justified.
The Space Shuttle Main Engine (SSME) is the only reusable large liquid rocket engine ever developed. The specific impulse delivered by the staged combustion cycle, substantially higher than previous rocket engines, minimized volume and weight for the integrated vehicle. The dual pre-burner configuration permitted precise mixture ratio and thrust control while the fully redundant controller and avionics provided a very high degree of system reliability and health diagnosis. The main engine controller design was the first rocket engine application to incorporate digital processing. The engine was required to operate at a high chamber pressure to minimize engine volume and weight. Power level throttling was required to minimize structural loads on the vehicle early in flight and acceleration levels on the crew late in ascent. Fatigue capability, strength, ease of assembly and disassembly, inspectability, and materials compatibility were all major considerations in achieving a fully reusable design. During the multi-decade program the design evolved substantially using a series of block upgrades. A number of materials and manufacturing challenges were encountered throughout SSME s history. Significant development was required for the final configuration of the high pressure turbopumps. Fracture control was implemented to assess life limits of critical materials and components. Survival in the hydrogen environment required assessment of hydrogen embrittlement. Instrumentation systems were a challenge due to the harsh thermal and dynamic environments within the engine. Extensive inspection procedures were developed to assess the engine components between flights. The Space Shuttle Main Engine achieved a remarkable flight performance record. All flights were successful with only one mission requiring an ascent abort condition, which still resulted in an acceptable orbit and mission. This was achieved in large part via extensive ground testing to fully characterize performance and to establish acceptable life limits. During the program over a million seconds of accumulated test and flight time was achieved. Post flight inspection and assessment was a key part of assuring proper performance of the flight hardware. By the end of the program the predicted reliability had improved by a factor of four. These unique challenges, evolution of the design, and the resulting reliability will be discussed in this paper.
The use of multiple versions of a computer program, independently designed from a common specification, to reduce the effects of an error is discussed. If these versions are designed by independent programming teams, it is expected that a fault in one version will not have the same behavior as any fault in the other versions. Since the errors in the output of the versions are different and uncorrelated, it is possible to run the versions concurrently, cross-check their results at prespecified points, and mask errors. A DEsign DIversity eXperiments (DEDIX) testbed was implemented to study the influence of common mode errors which can result in a failure of the entire system. The layered design of DEDIX and its decision algorithm are described.
A program to design, fabricate and test a 50 lb sub f (222 N) thruster was undertaken (Contract NAS 3-24656) to demonstrate the applicability of the reverse flow concept as an item of auxiliary propulsion for the space station. The thruster was to operate at a mixture ratio (O/F) of 4, be capable of operating for 2 million lb sub f- seconds (8.896 million N-seconds) impulse with a chamber pressure of 75 psia (52 N/square cm) and a nozzle area ratio of 40. Superimposed was also the objective of operating with a strainless steel spherical combustion chamber, which limited the wall temperature to 1700 F (1200 K), an objective specific impulse of 400 lb sub f sec/lbm (3923 N-seconds/Kg), and a demonstration of 500,000 lb sub f-seconds (2,224,000 N-seconds) of impulse. The demonstration of these objectives required a number of design iterations which eventually culminated in a very successful 1000 second demonstration, almost immediately followed by a changed program objective imposed to redesign and demonstrate at a mixture ratio (O/F) of 8. This change was made and more then 250,000 lb sub f seconds (1,112,000 N-seconds) of impulse was successfully demonstrated at a mixture ratio of 8. This document contains a description of the effort conducted during the program to design and demonstrate the thrusters involved.
The user's manual for the rocket combustor interactive design (ROCCID) computer program is presented. The program, written in Fortran 77, provides a standardized methodology using state of the art codes and procedures for the analysis of a liquid rocket engine combustor's steady state combustion performance and combustion stability. The ROCCID is currently capable of analyzing mixed element injector patterns containing impinging like doublet or unlike triplet, showerhead, shear coaxial, and swirl coaxial elements as long as only one element type exists in each injector core, baffle, or barrier zone. Real propellant properties of oxygen, hydrogen, methane, propane, and RP-1 are included in ROCCID. The properties of other propellants can easily be added. The analysis model in ROCCID can account for the influence of acoustic cavities, helmholtz resonators, and radial thrust chamber baffles on combustion stability. ROCCID also contains the logic to interactively create a combustor design which meets input performance and stability goals. A preliminary design results from the application of historical correlations to the input design requirements. The steady state performance and combustion stability of this design is evaluated using the analysis models, and ROCCID guides the user as to the design changes required to satisfy the user's performance and stability goals, including the design of stability aids. Output from ROCCID includes a formatted input file for the standardized JANNAF engine performance prediction procedure.
LaRC, under the Design Analysis Methods for Vibrations (DAMVIBS) Program, set out in 1984 to establish the technology base needed by the rotorcraft industry for developing an advanced finite-element-based dynamics design analysis capability for vibrations. Considerable work was performed by the industry participants in the program since that time. Because the DAMVIBS Program is being phased out, a government/industry assessment of the program was made to identify those accomplishments and contributions which may be ascribed to the program. The purpose is to provide an overview of the program and its accomplishments and contributions from the perspective of the government sponsoring organization.
An overview of a joint industry/government project, denoted Integrated Programs for Aerospace-Vehicle Design (IPAD), which focuses on development of technology and associated software for integrated company-wide management of engineering information is presented. Results to date are summarized and include an in-depth documentation of a representative design process for a large engineering project, the definition and design of computer-aided design software needed to support that process, and the release of prototype software to integrated selected design functions.
The report outlines work performed in support of the flowpath development for the DRACO engine program. The design process initiated to develop a hypersonic axisymmetric inlet for a Mach 6 rocket-based combined cycle (RBCC) engine is discussed. Various design parametrics were investigated, including design shock-on-lip Mach number, cone angle, throat Mach number, throat angle. length of distributed compression, and subsonic diffuser contours. Conceptual mechanical designs consistent with installation into the D-21 vehicle were developed. Additionally, program planning for an intensive inlet development program to support a Critical Design Review in three years was performed. This development program included both analytical and experimental elements and support for a flight-capable inlet mechanical design.
POINT computer program for design and analysis of radiation shields in nuclear rocket systems
The technology and advanced development programs required to support the Space Station are outlined. The technology program identifies the key technology options that have the potential for enhancing the desired operational Space Station. The advanced development program provides the means of advancing selected technologies and demonstrating feasibility and performance before implementing into the Space Station design. The program is designed to support the initial Space Station and the evolutionary growth capability.
The use of a transonic airfoil code for analysis, inverse design, and direct optimization of an airfoil immersed in propfan slipstream is described. A summary of the theoretical method, program capabilities, input format, output variables, and program execution are described. Input data of sample test cases and the corresponding output are given.
The strategy of the IPAD implementation plan presented, proposes a three phase development of the IPAD system and technical modules, and the transfer of this capability from the development environment to the aerospace vehicle design environment. The system and technical module capabilities for each phase of development are described. The system and technical module programming languages are recommended as well as the initial host computer system hardware and operating system. The cost of developing the IPAD technology is estimated. A schedule displaying the flowtime required for each development task is given. A PERT chart gives the developmental relationships of each of the tasks and an estimate of the operational cost of the IPAD system is offered.
Results of a requirements analysis task for Integrated Programs for Aerospace Vehicle Design (IPAD) are presented. User requirements which, in part, will shape the IPAD system design are given. Requirements considered were: generation, modification, storage, retrieval, communication, reporting, and protection of information. Data manipulation and controls on the system and the information were also considered. Specific needs relative to the product design process are also discussed.