Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “launch control system”

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 415 records · Page 23

Defect measurement and analysis of JPL ground software: a case study

Ground software systems at JPL must meet high assurance standards while remaining on schedule due to relatively immovable launch dates for spacecraft that will be controlled by such systems. Toward this end, the Software Quality Improvement (SQI) project's Measurement and Benchmarking (M&B) team is collecting and analyzing defect data of JPL ground system software projects to build software defect prediction models. The aim of these models is to improve predictability with regard to software quality activities. Predictive models will quantitatively define typical trends for JPL ground systems as well as Critical Discriminators (CDs) to provide explanations for atypical deviations from the norm at JPL. CDs are software characteristics that can be estimated or foreseen early in a software project's planning. Thus, these CDs will assist in planning for the predicted degree to which software quality activities for a project are likely to deviation from the normal JPL ground system based on pasted experience across the lab.

defects↗

Analysis and Results from a Flush Airdata Sensing System in Close Proximity to Firing Rocket Nozzles

This paper presents information regarding the nosecap Flush Airdata Sensing (FADS) system on Orion’s Pad Abort 1 (PA-1) vehicle. The purpose of the nosecap FADS system was to test whether or not useful data could be obtained from a FADS system if it was placed in close proximity to firing rocket nozzles like the Attitude Control Motor (ACM) nozzles on the PA-1 Launch Abort System. The nosecap FADS system used pressure measurements from a series of pressure ports which were arranged in a cruciform pattern and flush with the surface of the vehicle to estimate values of angle of attack, angle of sideslip, Mach number, impact pressure, and freestream static pressure. This paper will present the algorithms employed by the FADS system along with the development of the calibration datasets and a comparison of the final results to the Best Estimated Trajectory (BET) data for PA-1. Also presented in this paper is a Computational Fluid Dynamics (CFD) study to explore the impact of the ACM on the nosecap FADS system. The comparison of the nosecap FADS system results to the BET and the CFD study showed that more investigation is needed to quantify the impact of the firing rocket motors on the FADS system.

Flush Air Data Sensing System↗

Analysis and Results from a Flush Airdata Sensing (FADS) System in Close Proximity to Firing Rocket Nozzles

This presentation presents information regarding the nose-cap flush airdata sensing (FADS) system on Orion's Pad Abort 1 (PA-1) vehicle. The purpose of the nose-cap FADS system was to test whether or not useful data could be obtained from a FADS system if it was placed in close proximity to firing rockets nozzles like the attitude control motor (ACM) nozzles on the PA-1 launch abort system (LAS). The nose-cap FADS systems use pressure measurements from a series of pressure ports which are arranged in a cruciform pattern and flush with the surface of the vehicle to estimate values of angle of attack, angle of side-slip, Mach number, impact pressure and free-stream static pressure.

Pad Abort 1↗

Teleoperator maneuvering system

The Teleoperator Maneuvering System (TMS) is a Shuttle launched, free-flying, remotely controlled reusable propulsive stage capable of performing spacecraft and payload placement services, retrieval functions, assembly/servicing support for large space systems, dexterous manipulator operations for planned or contingency satellite servicing, satellite viewing, and subsatellite science support. The basic TMS segments, subsystems and performance are described, beginning with the criteria and requirements derived from mission models. Examples of TMS benefits to the STS and user communities are demonstrated. TMS applications such as support and servicing of Space Station, materials processing and subsatellite missions are presented.

Turner, J. R.↗

Objectives and Progress on Integrated Vehicle Ground Vibration Testing for the Ares Launch Vehicles

As NASA begins design and development of the Ares launch vehicles to replace the Space Shuttle and explore beyond low Earth orbit, Integrated Vehicle Ground Vibration Testing (IVGVT) will be a vital component of ensuring that those vehicles can perform the missions assigned to them. A ground vibration test (GVT) is intended to measure by test the fundamental dynamic characteristics of launch vehicles during various phases of flight. During the series of tests, properties such as natural frequencies, mode shapes, and transfer functions are measured directly. This data is then used to calibrate loads and control systems analysis models for verifying analyses of the launch vehicle. The Ares Flight & Integrated Test Office (FITO) will be conducting IVGVT for the Ares I crew launch vehicle at Marshall Space Flight Center (MSFC) from 2011 to 2012 using the venerable Test Stand (TS) 4550, which supported similar tests for the Saturn V and Space Shuttle vehicle stacks.

Tuma, Margaret L.↗

Environmental Control System Development

Since before the first men landed on the moon, human beings have aspired to reach farther into space, to discover and answer the great mysteries that exist beyond imagination. To reach where no one has gone before. To able to see all the wonderful things that can be found in space and that only satellites have revealed to us during all this time. Considering the last trip to the moon, mankind has been evolving and improving their technology to reach destinations whose distances had been impossible to transit. To reach that goal, the National Aeronautics and Space Administration (NASA) has designed and developed the largest and most powerful rocket ever created by the human race, the Space Launch System - better known as the SLS. To be able to send this large rocket to space, Kennedy Space Center (KSC) is doing upgrades to their existing facilities and equipment. At Launch Pad 39B, they are setting up a new Environmental Control System (ECS) developed to supply the rocket with the correct gases and mixtures that will be needed for the rocket to launch. The ECS is similar to an air conditioning unit. The main functionality of it is to supply the SLS with the correct gas mixture for it to launch. Also the ECS has been required to reduce or eliminate the possibility of a complete system failure. The system is part of the Ground Support Equipment (GSE) for the SLS that will be going to the Moon and Mars.

Flores Arroyo, Elvin A.↗

Modeling and Simulation of Variable Mass, Flexible Structures

The advent of the new Ares I launch vehicle has highlighted the need for advanced dynamic analysis tools for variable mass, flexible structures. This system is composed of interconnected flexible stages or components undergoing rapid mass depletion through the consumption of solid or liquid propellant. In addition to large rigid body configuration changes, the system simultaneously experiences elastic deformations. In most applications, the elastic deformations are compatible with linear strain-displacement relationships and are typically modeled using the assumed modes technique. The deformation of the system is approximated through the linear combination of the products of spatial shape functions and generalized time coordinates. Spatial shape functions are traditionally composed of normal mode shapes of the system or even constraint modes and static deformations derived from finite element models of the system. Equations of motion for systems undergoing coupled large rigid body motion and elastic deformation have previously been derived through a number of techniques [1]. However, in these derivations, the mode shapes or spatial shape functions of the system components were considered constant. But with the Ares I vehicle, the structural characteristics of the system are changing with the mass of the system. Previous approaches to solving this problem involve periodic updates to the spatial shape functions or interpolation between shape functions based on system mass or elapsed mission time. These solutions often introduce misleading or even unstable numerical transients into the system. Plus, interpolation on a shape function is not intuitive. This paper presents an approach in which the shape functions are held constant and operate on the changing mass and stiffness matrices of the vehicle components. Each vehicle stage or component finite element model is broken into dry structure and propellant models. A library of propellant models is used to describe the distribution of mass in the fuel tank or Solid Rocket Booster (SRB) case for various propellant levels. Based on the mass consumed by the liquid engine or SRB, the appropriate propellant model is coupled with the dry structure model for the stage. Then using vehicle configuration data, the integrated vehicle model is assembled and operated on by the constant system shape functions. The system mode shapes and frequencies can then be computed from the resulting generalized mass and stiffness matrices for that mass configuration. The rigid body mass properties of the vehicle are derived from the integrated vehicle model. The coupling terms between the vehicle rigid body motion and elastic deformation are also updated from the constant system shape functions and the integrated vehicle model. This approach was first used to analyze variable mass spinning beams and then prototyped into a generic dynamics simulation engine. The resulting code was tested against Crew Launch Vehicle (CLV-)class problems worked in the TREETOPS simulation package and by Wilson [2]. The Ares I System Integration Laboratory (SIL) is currently being developed at the Marshall Space Flight Center (MSFC) to test vehicle avionics hardware and software in a hardware-in-the-loop (HWIL) environment and certify that the integrated system is prepared for flight. The Ares I SIL utilizes the Ares Real-Time Environment for Modeling, Integration, and Simulation (ARTEMIS) tool to simulate the launch vehicle and stimulate avionics hardware. Due to the presence of vehicle control system filters and the thrust oscillation suppression system, which are tuned to the structural characteristics of the vehicle, ARTEMIS must incorporate accurate structural models of the Ares I launch vehicle. The ARTEMIS core dynamics simulation models the highly coupled nature of the vehicle flexible body dynamics, propellant slosh, and vehicle nozzle inertia effects combined with mass and flexible body properties that vary significant with time during the flight. All forces that act on the vehicle during flight must be simulated, including deflected engine thrust force, spatially distributed aerodynamic forces, gravity, and reaction control jet thrust forces. These forces are used to excite an integrated flexible vehicle, slosh, and nozzle dynamics model for the vehicle stack that simulates large rigid body translations and rotations along with small elastic deformations. Highly effective matrix math operations on a distributed, threaded high-performance simulation node allow ARTEMIS to retain up to 30 modes of flex for real-time simulation. Stage elements that separate from the stack during flight are propagated as independent rigid six degrees of freedom (6DOF) bodies. This paper will present the formulation of the resulting equations of motion, solutions to example problems, and describe the resulting dynamics simulation engine within ARTEMIS.

Tobbe, Patrick A.↗

Fault Detection and Correction for the Solar Dynamics Observatory Attitude Control System

The Solar Dynamics Observatory is an Explorer-class mission that will launch in early 2009. The spacecraft will operate in a geosynchronous orbit, sending data 24 hours a day to a devoted ground station in White Sands, New Mexico. It will carry a suite of instruments designed to observe the Sun in multiple wavelengths at unprecedented resolution. The Atmospheric Imaging Assembly includes four telescopes with focal plane CCDs that can image the full solar disk in four different visible wavelengths. The Extreme-ultraviolet Variability Experiment will collect time-correlated data on the activity of the Sun's corona. The Helioseismic and Magnetic Imager will enable study of pressure waves moving through the body of the Sun. The attitude control system on Solar Dynamics Observatory is responsible for four main phases of activity. The physical safety of the spacecraft after separation must be guaranteed. Fine attitude determination and control must be sufficient for instrument calibration maneuvers. The mission science mode requires 2-arcsecond control according to error signals provided by guide telescopes on the Atmospheric Imaging Assembly, one of the three instruments to be carried. Lastly, accurate execution of linear and angular momentum changes to the spacecraft must be provided for momentum management and orbit maintenance. In th~sp aper, single-fault tolerant fault detection and correction of the Solar Dynamics Observatory attitude control system is described. The attitude control hardware suite for the mission is catalogued, with special attention to redundancy at the hardware level. Four reaction wheels are used where any three are satisfactory. Four pairs of redundant thrusters are employed for orbit change maneuvers and momentum management. Three two-axis gyroscopes provide full redundancy for rate sensing. A digital Sun sensor and two autonomous star trackers provide two-out-of-three redundancy for fine attitude determination. The use of software to maximize chances of recovery from any hardware or software fault is detailed. A generic fault detection and correction software structure is used, allowing additions, deletions, and adjustments to fault detection and correction rules. This software structure is fed by in-line fault tests that are also able to take appropriate actions to avoid corruption of the data stream.

Starin, Scott R.↗

Structural Dynamics Observations in Space Launch System Green Run Hot Fire Testing

The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) system is comprised of eight mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Two actuators are used to move each engine in two planes perpendicular to one another (i.e., pitch and yaw). The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Green Run Hot Fire (GRHF) of the SLS Core Stage provided a flight-like ground test environment for verification of integrated vehicle TVC performance. A TVC model coupled to a vehicle structural dynamic model has been developed previously and incrementally validated in subsystem tests and simulations. Still, some aspects of TVC performance in GRHF were not anticipated. The ensuing investigation demonstrated the need for well-instrumented test environments, various levels of modeling fidelity, test-representative structural models, and caution in reuse of legacy components. This paper is the sixth installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. It introduces the salient structural dynamic phenomena uncovered in ambient and hot fire testing. During the Green Run test campaign, a comparison of ambient and hot fire step responses showed a significant change in apparent damping due to the presence of friction, challenging long standing assumptions that friction could be neglected. Additionally, the characteristic response of the engine and thrust structure during GRHF proved to be more complex than anticipated, as evidenced by the available actuator, thrust structure, and engine measurements. While the string-potentiometer based test instrumentation was intended to allow for reconstruction of the engine angles along the two control axes, the geometric placement, location uncertainty, and responses in overlapping frequency spectra revealed additional phenomena requiring further analysis and post-processing. The observations from both modal and frequency response testing during the Green Run ambient and hot fire configurations led to Engine and Core Stage FEM (finite element model) updates. When evidence of unexpected engine motion was found in engine section accelerometer data, the authors pursued additional structural analysis leading to FEM updates associated with the TVC gimbal and thrust structure. Through collaboration between structures, TVC, and flight control disciplines, the test-informed models and root-cause analysis led to confident flight rationale for the first flight of the SLS launch vehicle.

Richard K. Moore↗

Structural Dynamics Observations in Space Launch System Green Run Hot Fire Testing

The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) system is comprised of eight mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Two actuators are used to move each engine in two planes perpendicular to one another (i.e., pitch and yaw). The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Green Run Hot Fire (GRHF) of the SLS Core Stage provided a flight-like ground test environment for verification of integrated vehicle TVC performance. A TVC model coupled to a vehicle structural dynamic model has been developed previously and incrementally validated in subsystem tests and simulations. Still, some aspects of TVC performance in GRHF were not anticipated. The ensuing investigation demonstrated the need for well-instrumented test environments, various levels of modeling fidelity, test-representative structural models, and caution in reuse of legacy components. This paper is the sixth installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. It introduces the salient structural dynamic phenomena uncovered in ambient and hot fire testing. During the Green Run test campaign, a comparison of ambient and hot fire step responses showed a significant change in apparent damping due to the presence of friction, challenging long standing assumptions that friction could be neglected. Additionally, the characteristic response of the engine and thrust structure during GRHF proved to be more complex than anticipated, as evidenced by the available actuator, thrust structure, and engine measurements. While the string-potentiometer based test instrumentation was intended to allow for reconstruction of the engine angles along the two control axes, the geometric placement, location uncertainty, and responses in overlapping frequency spectra revealed additional phenomena requiring further analysis and post-processing. The observations from both modal and frequency response testing during the Green Run ambient and hot fire configurations led to Engine and Core Stage FEM (finite element model) updates. When evidence of unexpected engine motion was found in engine section accelerometer data, the authors pursued additional structural analysis leading to FEM updates associated with the TVC gimbal and thrust structure. Through collaboration between structures, TVC, and flight control disciplines, the test-informed models and root-cause analysis led to confident flight rationale for the first flight of the SLS launch vehicle.

Richard Moore↗

Telemetry Boards Interpret Rocket, Airplane Engine Data

For all the data gathered by the space shuttle while in orbit, NASA engineers are just as concerned about the information it generates on the ground. From the moment the shuttle s wheels touch the runway to the break of its electrical umbilical cord at 0.4 seconds before its next launch, sensors feed streams of data about the status of the vehicle and its various systems to Kennedy Space Center s shuttle crews. Even while the shuttle orbiter is refitted in Kennedy s orbiter processing facility, engineers constantly monitor everything from power levels to the testing of the mechanical arm in the orbiter s payload bay. On the launch pad and up until liftoff, the Launch Control Center, attached to the large Vehicle Assembly Building, screens all of the shuttle s vital data. (Once the shuttle clears its launch tower, this responsibility shifts to Mission Control at Johnson Space Center, with Kennedy in a backup role.) Ground systems for satellite launches also generate significant amounts of data. At Cape Canaveral Air Force Station, across the Banana River from Kennedy s location on Merritt Island, Florida, NASA rockets carrying precious satellite payloads into space flood the Launch Vehicle Data Center with sensor information on temperature, speed, trajectory, and vibration. The remote measurement and transmission of systems data called telemetry is essential to ensuring the safe and successful launch of the Agency s space missions. When a launch is unsuccessful, as it was for this year s Orbiting Carbon Observatory satellite, telemetry data also provides valuable clues as to what went wrong and how to remedy any problems for future attempts. All of this information is streamed from sensors in the form of binary code: strings of ones and zeros. One small company has partnered with NASA to provide technology that renders raw telemetry data intelligible not only for Agency engineers, but also for those in the private sector.

Source record↗

Spacecraft Design Thermal Control Subsystem

This slide presentation reviews the functions of the thermal control subsystem engineers in the design of spacecraft. The goal of the thermal control subsystem that will be used in a spacecraft is to maintain the temperature of all spacecraft components, subsystems, and all the flight systems within specified limits for all flight modes from launch to the end of the mission. For most thermal control subsystems the mass, power and control and sensing systems must be kept below 10% of the total flight system resources. This means that the thermal control engineer is involved in all other flight systems designs. The two concepts of thermal control, passive and active are reviewed and the use of thermal modeling tools are explained. The testing of the thermal control is also reviewed.

thermal control↗

HyBoLT Flight Experiment

HyBoLT was a Hypersonic Boundary Layer Transition flight experiment funded by the Hypersonics Project of the Fundamental Aeronautics Program in NASA's Aeronautics Research Mission Directorate. The HyBoLT test article mounted on the top of the ALV X-1 rocket was launched from Virginia's Wallops Island on August 22, 2008. Unfortunately a problem in the rocket's flight control system caused the vehicle to veer off the designed flight course. Launch officials activated a self-destruct mechanism in the rocket's nose cone after 20 seconds into flight. This report is a closeout document about the HyBoLT flight experiment. Details are provided of the objectives and approach associated with this experimental program as well as the 20 seconds flight data acquired before the vehicle was destroyed.

Chen, Fang-Jeng (Frank)↗

Technical Progress on the Ares I-X Flight Test

Ares I-X will be NASA's first test flight for a new human-rated launch vehicle since 1981, and the team is well on its way toward completing the vehicle's design and hardware fabrication for an April 2009 launch. This uncrewed suborbital development test flight gives NASA its first opportunities to: gather critical data about the flight dynamics of the integrated launch vehicle; understand how to control its roll during flight; better characterize the stage separation environments during future flight; and demonstrate the first stage recovery system. The Ares I-X Flight Test Vehicle (FTV) incorporates a mix of flight and mockup hardware. It is powered by a four-segment solid rocket booster, and will be modified to include a fifth, spacer segment; the upper stage, Orion crew exploration vehicle, and launch abort system are simulator hardware to make the FTV aerodynamically similar to the same size, shape, and weight of Ares I. The Ares IX first stage includes an existing Shuttle solid rocket motor and thrust vector control system controlled by an Ascent Thrust Vector Controller (ATVC) designed and built by Honeywell International. The avionics system will be tested in a dedicated System Integration Laboratory located at Lockheed Martin Space Systems (LMSS) in Denver, Colorado. The Upper Stage Simulator (USS) is made up of cylindrical segments that will be stacked and integrated at Kennedy Space Center (KSC) for launch. Glenn Research Center is already building these segments, along with their internal access structures. The active Roll Control System (RoCS) includes two thruster units harvested from Peacekeeper missiles. Duty cycle testing for RoCS was conducted, and fuel tanking and detanking tests will occur at KSC in early 2008. This important flight will provide valuable experience for the ground operations team in integrating, stacking, and launching Ares I. Data from Ares I-X will ensure the safety and reliability of America's newest launch vehicle.

Davis, S.R.↗

Vibration isolation

Viewgraphs on vibration isolation are presented. Techniques to control and isolate centrifuge disturbances were identified. Topics covered include: disturbance sources in the microgravity environment; microgravity assessment criteria; life sciences centrifuge; flight support equipment for launch; active vibration isolation system; active balancing system; and fuzzy logic control.

Bastin, Paul↗

The Implementation of Satellite Control System Software Using Object Oriented Design

NASA established the Small Explorer (SMEX) program in 1988 to provide frequent opportunities for highly focused and relatively inexpensive space science missions that can be launched into low earth orbit by small expendable vehicles. The development schedule for each SMEX spacecraft was three years from start to launch. The SMEX program has produced five satellites; Solar Anomalous and Magnetospheric Particle Explorer (SAMPEX), Fast Auroral Snapshot Explorer (FAST), Submillimeter Wave Astronomy Satellite (SWAS), Transition Region and Coronal Explorer (TRACE) and Wide-Field Infrared Explorer (WIRE). SAMPEX and FAST are on-orbit, TRACE is scheduled to be launched in April of 1998, WIRE is scheduled to be launched in September of 1998, and SWAS is scheduled to be launched in January of 1999. In each of these missions, the Attitude Control System (ACS) software was written using a modular procedural design. Current program goals require complete spacecraft development within 18 months. This requirement has increased pressure to write reusable flight software. Object-Oriented Design (OOD) offers the constructs for developing an application that only needs modification for mission unique requirements. This paper describes the OOD that was used to develop the SMEX-Lite ACS software. The SMEX-Lite ACS is three-axis controlled, momentum stabilized, and is capable of performing sub-arc-minute pointing. The paper first describes the high level requirements which governed the architecture of the SMEX-Lite ACS software. Next, the context in which the software resides is explained. The paper describes the benefits of encapsulation, inheritance and polymorphism with respect to the implementation of an ACS software system. This paper will discuss the design of several software components that comprise the ACS software. Specifically, Object-Oriented designs are presented for sensor data processing, attitude control, attitude determination and failure detection. The paper addresses the benefits of the OOD versus a conventional procedural design. The final discussion in this paper will address the establishment of the ACS Foundation Class (AFC) Library. The AFC is a large software repository, requiring a minimal amount of code modifications to produce ACS software for future projects, saving production time and costs.

Anderson, Mark O.↗