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.
Alternate mission objectives, design characteristics, and system and subsystem designs for Voyager spacecraft system
Design, mission, flight operations, experiment data, and subsystem performances for Lunar Orbiter 4 extended mission
Control requirements of Controlled Configured Design Approach vehicles with far-aft center of gravity locations are studied. The baseline system investigated is a fully reusable vertical takeoff/horizontal landing single stage-to-orbit vehicle with mission requirements similar to that of the space shuttle vehicle. Evaluations were made to determine dynamic stability boundaries, time responses, trim control, operational center-of-gravity limits, and flight control subsystem design requirements. Study tasks included a baseline vehicle analysis, an aft center of gravity study, a payload size study, and a technology assessment.
Scientific investigation of solar system with instrumented, unmanned spacecraft to fly, orbit and land on planets - Voyager project
Flight evaluation on Model III /RA-6/ of Ranger television subsystem - failure analysis
The applicability of the control configured design approach (CCV) to advanced earth orbital transportation systems was studied. The baseline system investigated was fully reusable vertical take-off/horizontal landing single-stage-to-orbit vehicle and had mission requirements similar to the space shuttle orbiter. Technical analyses were made to determine aerodynamic, flight control and subsystem design characteristics. Figures of merit were assessed on vehicle dry weight and orbital payload. The results indicated that the major parameters for CCV designs are hypersonic trim, aft center of gravity, and control surface heating. Optimized CCV designs can be controllable and provide substantial payload gains over conventional non-CCV design vertical take-off vehicles.
Critical reviews of NACA and NASA report literature on light aircraft design, with emphasis on propulsion subsystems, stability, control, propellers, performance, and safety
The Velocity Control Propulsion Subsystem (VCPS) was designed the propulsion required for trajectory and lunar orbit corrections of the spacecraft. A GFE clamp assembly physically attaches the VCPS to the spacecraft and the unit is ejected after completing the required corrections. The VCPS is physically and functionally separated from the spacecraft except for the electrical and telemetry interfaces. A GFE transtage provides the superstructure on which the VCPS is assembled. The subsystem consists of two 5 foot pound rocket engine assemblies, 4 propellant tanks, 2 latching valves, 2 fill and drain valves, a system filter, pressure transducer, gas and propellant manifolds and electrical heaters and thermostats. The RAE-B VCPS program covered the design, manufacture and qualification of one subsystem. This subsystem was to be manufactured, subjected to qualification tests; and refurbished, if necessary, prior to flight. The VCPS design and test program precluded the need for refurbishing the subsystem and the unit was delivered to GSFC at the conclusion of the program.
By integrating the attitude determination and control system (ACS) analysis and design, flight software development, and flight software testing processes, it is possible to improve the overall spacecraft development cycle, as well as allow for more thorough software testing. One of the ways to achieve this integration is to use code-generation tools to automatically generate components of the ACS flight software directly from a high-fidelity (HiFi) simulation. In the development of the Microwave Anisotropy Probe (MAP) spacecraft, currently underway at the NASA Goddard Space Flight Center, approximately 1/3 of the ACS flight software was automatically generated. In this paper, we will examine each phase of the ACS subsystem and flight software design life cycle: analysis, design, and testing. In the analysis phase, we scoped how much software we would automatically generate and created the initial interface. The design phase included parallel development of the HiFi simulation and the hand-coded flight software components. Everything came together in the test phase, in which the flight software was tested, using results from the HiFi simulation as one of the bases of comparison for testing. Because parts of the spacecraft HiFi simulation were converted into flight software, more care needed to be put into its development and configuration control to support both the HiFi simulation and flight software. The components of the HiFi simulation from which code was generated needed to be designed based on the fact that they would become flight software. This process involved such considerations as protecting against mathematical exceptions, using acceptable module and parameter naming conventions, and using an input/output interface compatible with the rest of the flight software. Maintaining good configuration control was an issue for the HiFi simulation and the flight software, and a way to track the two systems was devised. Finally, an integrated test approach was devised to support flight software testing at both the unit- and build-test levels using the HiFi simulation to generate data for performance verification. Another benefit of the simulation and code-generation application used on the MAP project is that it supported bringing flight software and test data into the HiFi simulation environment. It was possible to integrate parts of the hand-coded flight software into the HiFi simulation, and also possible to import flight software test data for comparison and performance verification. This capability was used to incorporate the flight software Kalman filter into the HiFi simulation. This enabled us to greatly increase the amount of testing that could be done on the filter, because we could exert a greater degree of control over the software-only simulation than over the flight software test environment. Also, since the simulation could be used to run the Kalman filter faster than real time, our testing efficiency was greatly increased. We will conclude our discussion with a summary of the lessons learned thus far using automatically- generated code for the MAP project, and the spacecraft status as we work towards our scheduled launch in the year 2000.
A wireless avionics interface provides a mechanism for managing multiple broadcast transceivers. This interface isolates the control logic required to support multiple transceivers so that the flight application does not have to manage wireless transceivers. All of the logic to select transceivers, detect transmitter and receiver faults, and take autonomous recovery action is contained in the interface, which is not restricted to using wireless transceivers. Wired, wireless, and mixed transceiver technologies are supported. This design s use of broadcast data technology provides inherent cross strapping of data links. This greatly simplifies the design of redundant flight subsystems. The interface fully exploits the broadcast data link to determine the health of other transceivers used to detect and isolate faults for fault recovery. The interface uses simplified control logic, which can be implemented as an intellectual-property (IP) core in a field-programmable gate array (FPGA). The interface arbitrates the reception of inbound data traffic appearing on multiple receivers. It arbitrates the transmission of outbound traffic. This system also monitors broadcast data traffic to determine the health of transmitters in the network, and then uses this health information to make autonomous decisions for routing traffic through transceivers. Multiple selection strategies are supported, like having an active transceiver with the secondary transceiver powered off except to send periodic health status reports. Transceivers can operate in round-robin for load-sharing and graceful degradation.
The design and operation of the initial modular space station are summarized. The design for a crew of six is presented and concepts for growth to twelve are discussed, including the configuration, subsystems, experiment laboratories, and flight operations. Station module designs are described and design features of the arrangements, configuration, and subsystems are discussed. A reference experiment program is presented which includes a representative phasing of experiment activity for both initial and growth stations. The flight operations required for station assembly and for carrying out the reference experiment program are also covered.
Design and performance data of power subsystem in flight spacecraft Lunar Orbiter 3
Qualification tests conducted on flight quality components, subsystems, and systems to prove that structural design requirements have been achieved
The present work describes the design and in-flight performance of the power subsystem for the first three Atmosphere Explorer (AE) spacecraft. The subsystem provides all electrical power to the spacecraft loads and consists of a solar array, three batteries, and a power supply electronics unit. Power from the solar array is supplied to the spacecraft loads through an unregulated power bus, which varies between -26 and -38 V. Loads which are normally on only during data collection phases of an orbit are fed from a tightly regulated -24.5 V bus. Power subsystem performance during the first three months in orbit has been nominal, except for an anomally in the shunt limiter protection circuitry. A malfunctioning shunt control amplifier was reconnected via ground command.
This book intends to build a bridge for the student and the young engineer: to link the rocket propulsion fundamentals and elements (which are well covered in the literature) with the actual rocket engine design and development work as it is carried out in industry (which is very little, if at all covered in literature). The book attempts to further the understanding of the realistic application of liquid rocket propulsion theories, and to help avoid or at least reduce time and money consuming errors and disappointments. In so doing, it also attempts to digest and consolidate numerous closely related subjects, hitherto often treated as separate, bringing them up to date at the same time. The book was written "on the job" for use by those active in all phases of engine systems design, development, and application, in industry as well as government agencies. Since it addresses itself to human beings set out to create new machines, rather than describing machines about to dominate man, the language chosen may not always be "functional" in the strict sense of the word. The book presents sufficient detail to familiarize and educate thoroughly those responsible for various aspects of liquid propellant rocketry, including engine systems design, engine development, and flight vehicle application. It should enable the rocket engineer to conduct, independently, complete or partial engine systems preliminary detail designs and to understand and judge the activities in, and the problems, limitations, and "facts of life~ of the various subsystems making up a complete engine system. It also attempts to educate those ultimately interested in specialized subsystems and component design (thrust chamber, turbopump, control valves, etc.) about their own as well as neighboring subsystems and about the complete engine system. This should enable the student to prepare realistic analytical calculations and design layouts with a long headstart toward the final specialized designs for subsystem production release. Special emphasis has been placed on engine flight application to stimulate engine systems and subsystem designers to think in these terms from the outset. The book is intended as a textbook, with specific consideration of the teacher without industry experience. We hope it will stimulate those desiring to specialize in the area of a rocket engine subsystem by supplying adequate information to enable them to benefit fully from the specialized literature. Thus, it provides a realistic expert introduction for those joining the liquid propellant rocket engine field.
Electrified aircraft powertrains contain multiple tightly coupled subsystems, making them much more complex than traditional aircraft propulsion systems, both in terms of integration and control. Electrification enables aircraft to have multiple distributed thrust-producing fans that the flight control system can utilize for enhanced maneuverability, further increasing the control complexity. The SUbsonic Single Aft eNgine (SUSAN) Electrofan is a NASA concept aircraft that leverages this technology. SUSAN is a series/parallel partial hybrid electric single-aisle transport aircraft that takes advantage of its electrified powertrain to provide fuel burn and emissions benefits when compared to the state-of-the-art. Achieving these benefits requires an appropriately designed control architecture that coordinates the various powertrain and flight control subsystems. As such, the SUSAN aircraft is designed with a high level of automation, allowing it to properly manage coupled subsystems and react rapidly to failures and anomalies. To do this effectively, algorithms that perform component health management, fault detection, isolation, and accommodation, and continuous optimization, must be developed, tested, validated, and implemented. This paper describes a piloted evaluation of such an algorithm in scenarios with multiple fan failures, performed in a flight simulator, demonstrating failure recovery and continued safe operation up to the limits of the powertrain. These scenarios are subsequently related to certification requirements.
Electrified aircraft powertrains contain multiple tightly coupled subsystems, making them much more complex than traditional aircraft propulsion systems, both in terms of integration and control. Electrification enables aircraft to have multiple distributed thrust-producing fans that the flight control system can utilize for enhanced maneuverability, further increasing the control complexity. The SUbsonic Single Aft eNgine (SUSAN) Electrofan is a NASA concept aircraft that leverages this technology. SUSAN is a series/parallel partial hybrid electric single-aisle transport aircraft that takes advantage of its electrified powertrain to provide fuel burn and emissions benefits when compared to the state-of-the-art. Achieving these benefits requires an appropriately designed control architecture that coordinates the various powertrain and flight control subsystems. As such, the SUSAN aircraft is designed with a high level of automation, allowing it to properly manage coupled subsystems and react rapidly to failures and anomalies. To do this effectively, algorithms that perform component health management, fault detection, isolation, and accommodation, and continuous optimization, must be developed, tested, validated, and implemented. This paper describes a piloted evaluation of such an algorithm in scenarios with multiple fan failures, performed in a flight simulator, demonstrating failure recovery and continued safe operation up to the limits of the powertrain. These scenarios are subsequently related to certification requirements.
Electrified aircraft powertrains contain multiple tightly coupled subsystems, making them much more complex than traditional aircraft propulsion systems, both in terms of integration and control. Electrification enables aircraft to have multiple distributed thrust-producing fans that the flight control system can utilize for enhanced maneuverability, further increasing the control complexity. The SUbsonic Single Aft eNgine (SUSAN) Electrofan is a NASA concept aircraft that leverages this technology. SUSAN is a series/parallel partial hybrid electric single-aisle transport aircraft that takes advantage of its electrified powertrain to provide fuel burn and emissions benefits when compared to the state-of-the-art. Achieving these benefits requires an appropriately designed control architecture that coordinates the various powertrain and flight control subsystems. As such, the SUSAN aircraft is designed with a high level of automation, allowing it to properly manage coupled subsystems and react rapidly to failures and anomalies. To do this effectively, algorithms that perform component health management, fault detection, isolation, and accommodation, and continuous optimization, must be developed, tested, validated, and implemented. This paper describes a piloted evaluation of such an algorithm in scenarios with multiple fan failures, performed in a flight simulator, demonstrating failure recovery and continued safe operation up to the limits of the powertrain. These scenarios are subsequently related to certification requirements.