TECHNIQUES FOR SIMULATION AND ANALYSIS OF SHOCK AND VIBRATION ENVIRONMENTS OF SPACE FLIGHT SYSTEMS
Simulation and analysis of shock and vibration environments in space-flight systems
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.
Simulation and analysis of shock and vibration environments in space-flight systems
Materials used to illustrate a presentation on the development of electric flight systems are presented. Systems concepts are outlined.
Inplementation of fracture control for payload structures of NASA manned space flight systems has contributed significantly to the safe operations of the Space Shuttle.
The modern advanced avionics in new high-performance aircraft strains the capability of current technology to safely monitor these systems for flight test prior to their generalized use. New techniques are needed to improve the ability of systems engineers to understand and analyze complex systems in the limited time available during crucial periods of the flight test. The Dryden Flight Research Facility of NASA's Ames Research Center is involved in the design and implementation of an expert system to provide expertise and knowledge to aid the flight systems engineer. The need for new techniques in monitoring flight systems and the conceptual design of an expert-system flight status monitor is discussed. The status of the current project and its goals are described.
Adoption of commercial off-the-shelf (COTS) products in safety critical systems has been seen as a promising acquisition strategy to improve mission affordability and, yet, has come with significant barriers and challenges. Attempts to integrate COTS software components into NASA human rated flight systems have been, for the most part, complicated by verification and validation (V&V) requirements necessary for flight certification per NASA s own standards. For software that is from COTS sources, and, in general from 3rd party sources, either commercial, government, modified or open source, the expectation is that it meets the same certification criteria as those used for in-house and that it does so as if it were built in-house. The latter is a critical and hidden issue. This paper examines the longstanding barriers and challenges in the use of 3rd party software in safety critical systems and cover recent efforts to use COTS software in NASA s Multi-Purpose Crew Vehicle (MPCV) project. It identifies some core artifacts that without them, the use of COTS and 3rd party software is, for all practical purposes, a nonstarter for affordable and timely insertion into flight critical systems. The paper covers the first use in a flight critical system by NASA of COTS software that has prior FAA certification heritage, which was shown to meet the RTCA-DO-178B standard, and how this certification may, in some cases, be leveraged to allow the use of analysis in lieu of testing. Finally, the paper proposes the establishment of an open source forum for development of safety critical 3rd party software.
The functional requirements of stowage, preparation, serving, consumption, and cleanup were applied to each of the five food mixes selected for study in terms of the overall design of the space shuttle food system. The analysis led to a definition of performance requirements for each food mix, along with a definition of equipment to meet those requirements. Weight and volume data for all five systems, in terms of food and packaging, support equipment, and galley installation penalties, are presented.
Unusual requirements for the Pressure Distribution/Air Data System (PD/ADS) transducer thermal vacuum testing led to the development of a conductively heated and cooled, fully automated, bell-jar test system. The system has proven to be easily adaptable for other tests and offers the advantages of quick turn-around and low operational cost.
A review is presented of some of the early rotor systems flight research leading to the present comprehensive NASA/Army rotor system airloads program with the UH-60 helicopter. The experimental and analytical plans and progress for this program are described, including the design and development of a rotor blade which incorporated 242 pressure transducers buried in the surface of the blade, and also the development of calibration hardware for regular calibration and testing of the transducers. Supporting analytical developments based on the comprehensive analytical model of rotorcraft aerodynamics and dynamics (CAMRAD) and various CFD codes are discussed. The highly instrumented UH-60 as well as companion programs of full-scale and model wind tunnel tests of the UH-60 rotor with identical instrumentation will provide the opportunity to explore a full range of rotor experiments and the data necessary to validate the advanced methodologies under development.
Good program management practices, cost analysis, cost estimation, and cost control for aerospace flight systems are interrelated and depend upon each other. The best cost control process cannot overcome poor design or poor systems trades that lead to the wrong approach. The project needs robust Technical, Schedule, Cost, Risk, and Cost Risk practices before it can incorporate adequate Cost Control. Cost analysis both precedes and follows cost estimation -- the two are closely coupled with each other and with Risk analysis. Parametric cost estimating relationships and computerized models are most often used. NASA has learned some valuable lessons in controlling cost problems, and recommends use of a summary Project Manager's checklist as shown here.
This paper provides an overview of the Shuttle Radar Topography Mission (SRTM), with emphasis on flight system implementation and mission operations from systems engineering perspective. Successfully flown in February, 2000, the SRTM's primary payload consists of several subsystems to form the first spaceborne dual-frequency (C-band and X-band) fixed baseline interferometric synthetic aperture radar (InSAR) system, with the mission objective to acquire data sets over 80% of Earth's landmass for height reconstruction. The paper provides system architecture, unique design features, engineering budgets, design verification, in-flight checkout and data acquisition of the SRTM payload, in particular for the C-band system. Mission operation and post-mission data processing activities are also presented. The complexity of the SRTM as a system, the ambitious mission objective, the demanding requirements and the high interdependency between multi-disciplined subsystems posed many challenges. The engineering experience and the insight thus gained have important implications for future spaceborne interferometric SAR mission design and implementation.
The next phase of robotic and human deep space exploration missions requires high performance, high power solar electric propulsion systems for large-scale science missions and cargo transportation. Aerojet Rocketdyne's Advanced Electric Propulsion System (AEPS) program is completing development and qualification of a 13kW flight EP system to support NASA exploration. The first use of the AEPS is planned for the NASA Power & Propulsion Element, which is the first element of NASA's cis-lunar Gateway. The flight AEPS system includes a magnetically shielded long-life Hall thruster, power processing unit (PPU), and xenon flow controller (XFC). The Hall thruster, originally developed and demonstrated by NASA's Glenn Research Center and the Jet Propulsion Laboratory, operates at input powers up to 13.3kW while providing a specific impulse over 2600s at an input voltage of 600V. The power processor is designed to accommodate an input voltage range of 95 to 140V, consistent with operation beyond the orbit of Mars. The integrated system is continuously throttleable between 3 and 13.3kW. The program has completed testing of the Technology Development Units and is progressing into the Engineering Development Unit test phase and the final design phase to Critical Design Review (CDR). This paper will present the high power AEPS system capabilities, overall program and design status and the latest test results for the 13kW flight system development as well as the plans for the development and qualification effort of the EP string.
The next phase of robotic and human deep space exploration missions requires high performance, high power solar electric propulsion systems for large-scale science missions and cargo transportation. Aerojet Rocketdyne's Advanced Electric Propulsion System (AEPS) program is completing development and qualification of a 13kW flight EP system to support NASA exploration. The first use of the AEPS is planned for the NASA Power & Propulsion Element, which is the first element of NASA's cis-lunar Gateway. The flight AEPS system includes a magnetically shielded long-life Hall thruster, power processing unit (PPU), and xenon flow controller (XFC). The Hall thruster, originally developed and demonstrated by NASA's Glenn Research Center and the Jet Propulsion Laboratory, operates at input powers up to 13.3kW while providing a specific impulse over 2600s at an input voltage of 600V. The power processor is designed to accommodate an input voltage range of 95 to 140V, consistent with operation beyond the orbit of Mars. The integrated system is continuously throttleable between 3 and 13.3kW. The program has completed testing of the Technology Development Units and is progressing into the Engineering Development Unit test phase and the final design phase to Critical Design Review (CDR). This paper will present the high power AEPS system capabilities, overall program and design status and the latest test results for the 13kW flight system development as well as the plans for the development and qualification effort of the EP string.
NASA has long supported research on intelligent control technologies that could allow space systems to operate autonomously or with reduced human supervision. Proposed uses range from automated control of entire space vehicles to mobile robots that assist or substitute for astronauts to vehicle systems such as life support that interact with other systems in complex ways and require constant vigilance. The potential for pervasive use of such technology to extend the kinds of missions that are possible in practice is well understood, as is its potential to radically improve the robustness, safety and productivity of diverse mission systems. Despite its acknowledged potential, intelligent control capabilities are rarely used in space flight systems. Perhaps the most famous example of intelligent control on a spacecraft is the Remote Agent system flown on the Deep Space One mission (1998 - 2001). However, even in this case, the role of the intelligent control element, originally intended to have full control of the spacecraft for the duration of the mission, was reduced to having partial control for a two-week non-critical period. Even this level of mission acceptance was exceptional. In most cases, mission managers consider intelligent control systems an unacceptable source of risk and elect not to fly them. Overall, the technology is not trusted. From the standpoint of those who need to decide whether to incorporate this technology, lack of trust is easy to understand. Intelligent high-level control means allowing software io make decisions that are too complex for conventional software. The decision-making behavior of these systems is often hard to understand and inspect, and thus hard to evaluate. Moreover, such software is typically designed and implemented either as a research product or custom-built for a particular mission. In the former case, software quality is unlikely to be adequate for flight qualification and the functionality provided by the system is likely driven largely by the need to publish innovative work. In the latter case, the mission represents the first use of the system, a risky proposition even for relatively simple software.
Materials illustrating a presentation on the integration of components and subsystems of electric flight systems are presented. The technology issues are outlined, and near and far term implications of issues affecting the systems integration are outlined.
The paper discusses the implementation of fault tolerant digital flight control and navigation systems for rotorcraft application. It is shown that in implementing fault tolerance at the systems level using advanced LSI/VLSI technology, aircraft physical layout and flight systems requirements tend to define a system architecture of distributed, asynchronous microprocessors in which fault tolerance can be achieved locally through hardware redundancy and/or globally through application of analytical redundancy. The effects of asynchronism on the execution of dynamic flight software is discussed. It is shown that if the asynchronous microprocessors have knowledge of time, these errors can be significantly reduced through appropiate modifications of the flight software. Finally, the papear extends previous work to show that through the combined use of time referencing and stable flight algorithms, individual microprocessors can be configured to autonomously tolerate intermittent faults.
An extremum-seeking control system for formation flight that uses blended performance parameters in a conglomerate performance function that better approximates drag reduction than performance functions formed from individual measurements. Generally, a variety of different measurements are taken and fed to a control system, the measurements are weighted, and are then subjected to a peak-seeking control algorithm. As measurements are continually taken, the aircraft will be guided to a relative position which optimizes the drag reduction of the formation. Two embodiments are discussed. Two approaches are shown for determining relative weightings: "a priori" by which they are qualitatively determined (by minimizing the error between the conglomerate function and the drag reduction function), and by periodically updating the weightings as the formation evolves.
UARS flight systems are designed to ensure mission success during the NSTS Orbiter deployment of the UARS Observatory. The Orbiter and its crew capabilities allow the UARS project to take advantage of the on-orbit human presence. These capabilities include human intervention and correction of spacecraft anomalies. The UARS Observatory is based on the Multi-Mission Modular Spacecraft to allow for flexible monitoring and commanding of the observatory. The observatory's Solar Array and High Gain Antenna systems are designed to allow for manual release and/or deployment. The UARS Airborne Support Equipment are designed to support the observatory as an electrical and communication interface to the Orbiter; and as work platform to support Extra-Vehicular Activity (EVA). Tools and EVA equipment were designed and developed to assist the crewmember perform the required contingency tasks.
Ripples is a computer program that makes it possible to specify arbitrarily complex space-flight systems in an easy-to-learn, high-level programming language and to have the specification automatically translated into LibSim, which is a text-based computing language in which such simulations are implemented. LibSim is a very powerful simulation language, but learning it takes considerable time, and it requires that models of systems and their components be described at a very low level of abstraction. To construct a model in LibSim, it is necessary to go through a time-consuming process that includes modeling each subsystem, including defining its fault-injection states, input and output conditions, and the topology of its connections to other subsystems. Ripples makes it possible to describe the same models at a much higher level of abstraction, thereby enabling the user to build models faster and with fewer errors. Ripples can be executed in a variety of computers and operating systems, and can be supplied in either source code or binary form. It must be run in conjunction with a Lisp compiler.