Search NASA⌕ Search

SEARCH · Search NASA

Results for “Control Volumes”

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 379 records · Page 21
All sourcesNASA NTRSDOE OSTI
NASA NTRS1996

Active Control of Fan Noise: Feasibility Study: Active Fan Noise Cancellation in the NASA Lewis Active Noise Control Fan Facility - Volume 3

This report describes the Active Noise Cancellation (ANC) System designed by General Electric and tested in the NASA Lewis Research Center's (LERC) 48 inch Active Noise Control Fan (ANCF). The goal of this study is to assess the feasibility of using wall mounted secondary acoustic sources and sensors within the duct of a high bypass turbofan aircraft engine for global active noise cancellation of fan tones. The GE ANC system is based on a modal control approach. A known acoustic mode propagating in the fan duct is canceled using an array of flush-mounted compact sound sources. The canceling modal signal is generated by a modal controller. Inputs to the controller are signals from a shaft encoder and from a microphone array which senses the residual acoustic mode in the duct. The key results are that the (6,0) was completely eliminated at the 920 Hz design frequency and substantially reduced elsewhere. The total tone power was reduced 6.8 dB (out of a possible 9.8 dB). Farfield reductions of 15 dB (SPL) were obtained. The (4,0) and (4,1) modes were reduced simultaneously yielding a 15 dB PWL decrease. The results indicate that global attenuation of PWL at the target frequency was obtained in the aft quadrant using an ANC actuator and sensor system totally contained within the duct. The quality of the results depended on precise mode generation. High spillover into spurious modes generated by the ANC actuator array caused less than optimum levels of PWL reduction. The variation in spillover is believed to be due to calibration procedure, but must be confirmed in subsequent tests.

Pla, Frederic G.↗
NASA NTRS1979

Proceedings of the Distribution Automation and Control Working Group. Volume 2: Proceedings

The meeting provided a forum in which electric utilities could communicate with each other, with DOE, and with DOE's contractors regarding research, development, and demonstration efforts to apply DAC (Distribution Automation and Control) to the electric power system. In the discussions emphasis was to be placed on identifying the priorities and needs for DAC development.

Caldwell, R.↗
NASA NTRS1974

Attitude Control Propulsion Components, Volume 1

Effort was made to include as much engineering information on each component as possible, consistent with usefulness and catalog size limitations. The contents of this catalog contain components which were qualified for use with spacecraft monopropellant hydrazine and inert gas attitude control systems. Thrust ranges up to 44.5 N (10.0 lbf) for hydrazine and inert gas sytems were considered. Additionally, some components qualified for uses other than spacecraft attitude control are included because they are suitable for use in attitude controls systems.

Source record↗
NASA NTRS2008

Guidance and Control Software Project Data - Volume 2: Development Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the development documents from the GCS project. Volume 2 contains three appendices: A. Guidance and Control Software Development Specification; B. Design Description for the Pluto Implementation of the Guidance and Control Software; and C. Source Code for the Pluto Implementation of the Guidance and Control Software

Hayhurst, Kelly J.↗
NASA NTRS1985

Proceedings of the Workshop on Identification and Control of Flexible Space Structures, volume 1

Identification and control of flexible space structures were studied. Exploration of the most advanced modeling estimation, identification and control methodologies to flexible space structures was discussed. The following general areas were discussed: space platforms, antennas, and flight experiments; control/structure interactions - modeling, integrated design and optimization, control and stabilization, and shape control; control technology; control of space stations; large antenna control, dynamics and control experiments, and control/structure interaction experiments.

Rodriguez, G.↗
NASA NTRS2008

Guidance and Control Software Project Data - Volume 3: Verification Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the verification documents from the GCS project. Volume 3 contains four appendices: A. Software Verification Cases and Procedures for the Guidance and Control Software Project; B. Software Verification Results for the Pluto Implementation of the Guidance and Control Software; C. Review Records for the Pluto Implementation of the Guidance and Control Software; and D. Test Results Logs for the Pluto Implementation of the Guidance and Control Software.

Hayhurst, Kelly J.↗
NASA NTRS2008

Guidance and Control Software Project Data - Volume 1: Planning Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the planning documents from the GCS project. Volume 1 contains five appendices: A. Plan for Software Aspects of Certification for the Guidance and Control Software Project; B. Software Development Standards for the Guidance and Control Software Project; C. Software Verification Plan for the Guidance and Control Software Project; D. Software Configuration Management Plan for the Guidance and Control Software Project; and E. Software Quality Assurance Activities.

Hayhurst, Kelly J.↗
NASA NTRS1974

Integrated Power/Attitude Control System (IPACS) study. Volume 1: Feasibility studies

An Integrated Power/Attitude Control System (IPACS) concept consisting of an array of spinning flywheels, with or without gimbals, capable of performing the dual function of power storage and generation, as well as attitude control has been investigated. This system provides attitude control through momentum storage, and replaces the storage batteries onboard the spacecraft. The results of the investigation are presented in two volumes. The trade-off studies performed to establish the feasibility, cost effectiveness, required level of development, and boundaries of application of IPACS to a wide variety of spacecraft are discussed. The conceptual designs for a free-flying research application module (RAM), and for a tracking and data relay satellite (TDRS) are presented. Results from dynamic analyses and simulations of the IPACS conceptual designs are included.

Notti, J. E.↗
NASA NTRS1971

Expendable second stage reusable space shuttle booster. Volume 6: Interface control drawings

The major expendable second stage interfaces which must be controlled in the development of the expendable second stage reusable space shuttle booster are defined. Interface control drawings are presented for the following configurations: (1) booster/expendable second stage (ESS), (2) space shuttle engine/expendable second stage, (3) expendable second stage/ground support equipment, (4) expendable second stage/payload, and (5) orbiter/expendable second stage.

Source record↗