Search NASA⌕ Search

SEARCH · Search NASA

Results for “launch control systems”

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 307 records · Page 17

Vehicle health management for guidance, navigation and control systems

The objective of the program was to architect a vehicle health management (VHM) system for space systems avionics that assures system readiness for launch vehicles and for space-based dormant vehicles. The platforms which were studied and considered for application of VHM for guidance, navigation and control (GN&C) included the Advanced Manned Launch System (AMLS), the Horizontal Landing-20/Personnel Launch System (HL-20/PLS), the Assured Crew Return Vehicle (ACRV) and the Extended Duration Orbiter (EDO). This set was selected because dormancy and/or availability requirements are driving the designs of these future systems.

Radke, Kathleen↗

Time and Frequency-Domain Cross-Verification of SLS 6DOF Trajectory Simulations

The Space Launch System (SLS) Guidance, Navigation, and Control (GNC) team and its partners have developed several time- and frequency-based simulations for development and analysis of the proposed SLS launch vehicle. The simulations differ in fidelity and some have unique functionality that allows them to perform specific analyses. Some examples of the purposes of the various models are: trajectory simulation, multi-body separation, Monte Carlo, hardware in the loop, loads, and frequency domain stability analyses. While no two simulations are identical, many of the models are essentially six degree-of-freedom (6DOF) representations of the SLS plant dynamics, hardware implementation, and flight software. Thus at a high level all of those models should be in agreement. Comparison of outputs from several SLS trajectory and stability analysis tools are ongoing as part of the program's current verification effort. The purpose of these comparisons is to highlight modeling and analysis differences, verify simulation data sources, identify inconsistencies and minor errors, and ultimately to verify output data as being a good representation of the vehicle and subsystem dynamics. This paper will show selected verification work in both the time and frequency domain from the current design analysis cycle of the SLS for several of the design and analysis simulations. In the time domain, the tools that will be compared are MAVERIC, CLVTOPS, SAVANT, STARS, ARTEMIS, and POST 2. For the frequency domain analysis, the tools to be compared are FRACTAL, SAVANT, and STARS. The paper will include discussion of these tools including their capabilities, configurations, and the uses to which they are put in the SLS program. Determination of the criteria by which the simulations are compared (matching criteria) requires thoughtful consideration, and there are several pitfalls that may occur that can severely punish a simulation if not considered carefully. The paper will discuss these considerations and will present a framework for responding to these issues when they arise. For example, small event timing differences can lead to large differences in mass properties if the criteria are to measure those properties at the same time, or large differences in altitude if the criteria are to measure those properties when the simulation experiences a staging event. Similarly, a tiny difference in phase can lead to large gain margin differences for frequency-domain comparisons of gain margins.

Johnson, Matthew↗

Simulation of Wind Profile Perturbations for Launch Vehicle Design

Ideally, a statistically representative sample of measured high-resolution wind profiles with wavelengths as small as tens of meters is required in design studies to establish aerodynamic load indicator dispersions and vehicle control system capability. At most potential launch sites, high- resolution wind profiles may not exist. Representative samples of Rawinsonde wind profiles to altitudes of 30 km are more likely to be available from the extensive network of measurement sites established for routine sampling in support of weather observing and forecasting activity. Such a sample, large enough to be statistically representative of relatively large wavelength perturbations, would be inadequate for launch vehicle design assessments because the Rawinsonde system accurately measures wind perturbations with wavelengths no smaller than 2000 m (1000 m altitude increment). The Kennedy Space Center (KSC) Jimsphere wind profiles (150/month and seasonal 2 and 3.5-hr pairs) are the only adequate samples of high resolution profiles approx. 150 to 300 m effective resolution, but over-sampled at 25 m intervals) that have been used extensively for launch vehicle design assessments. Therefore, a simulation process has been developed for enhancement of measured low-resolution Rawinsonde profiles that would be applicable in preliminary launch vehicle design studies at launch sites other than KSC.

Adelfang, S. I.↗

System Applications Software Development and Testing for the Spaceport Command and Control System

Known as "America's Spaceport," one of Kennedy Space Center's (KSC) primary responsibilities is the successful preparation for and launch of rockets into space. KSC's Engineering Software Branch has been tasked with creating a new command and control system that will provide check-out and launch control for future rockets and spacecraft. While work on the software began several years ago, development is ongoing and the operators who use the software on a daily basis have requested several features to improve their user experience. My internship in the fall of 2018 involved developing the source code and unit tests for two of these requested features: "Display Data with Persistence" (DDP) and "Save Events Button" (SEB). DDP's primary goal is to aid with ergonomics. Currently, users must press-and-hold on the mouse button to display information about points on a data plot. Once DDP is integrated, users will have the ability to double-click on a data plot to display that same information with persistence. Independent from DDP, the SEB provides users the ability to take information about different events that occur in the control system and save that data into a simple Comma Separated File (.csv) file format for easier analysis at a future time.

Niemoeller, Samantha↗

Ultrasail

Ultrasail is a complete sail system for the launch, deployment, stabilization and control of very large solar sails enabling reduced mission times for interplanetary and deep space spacecraft. Ultrasail is an innovative, non-traditional approach to propulsion technology achieved by combining propulsion and control systems developed for formation-flying microsatellites with an innovative solar sail architecture to achieve sq km-class controllable sail areas, sail subsystem area densities of 1 gm per sq m, and thrust levels equivalent to 400 kW ion thruster systems used for comparable deep space missions. Ultrasail can conceivably even achieve outer planetary rendezvous, a deep space capability now reserved for high-mass nuclear and chemical systems. Ultrasail is a Delta IV-launched multi-blade spin-stabilized system with blade lengths as long as 50 km, reminiscent of the MacNeal Heliogyro. The primary innovation is the near-elimination of sail supporting structures by attaching the sail tip to a rigid formation-flying microsatellite truss which deploys the sail blade, and which then articulates the blade to provide attitude control, including spin stabilization and precession of the spin axis. These tip microsatellites are controlled by a solar-powered 3-axis microthruster system (electric or cold gas) to maintain proper sail film tension during deployment and spin-up. The satellite mass also provides a stabilizing centrifugal force on the blade while in rotation. Understanding the dynamics of individual blades is key to the overall dynamics of Ultrasail. Forces and torques that must be modeled include those due to solar pressure, those generated by the microsatellite at the blade tip and by torques applied at the blade root. Centrifugal forces also play a significant role in the deployment and maintenance of the sail configuration. To capture the dynamics of the overall system, the equations of motion for the blades have been derived. Using these differential equations, a control law will be derived to maneuver Ultrasail. This law involves the pitching of the individual blades thereby moving the distribution of the radiation pressure on each individual blade and inducing a resultant torque on the system. The direction of the angular momentum vector and its rate of precession can be controlled through the pitch angle of the blades. The Ultrasail trajectory is also being studied. Optimal or near-optimal trajectories are being generated to showcase Ultrasail performance. Various missions, e.g. outer planet and solar polar missions for observation of the Sun, are currently being investigated to demonstrate the performance enhancements generated by Ultrasail technology. Calculus-of-variations-based optimization software is used to produce optimal Ultrasail trajectories. The performance of these trajectories is being compared to optimal results generated with other propulsion models, including chemical propulsion, ion propulsion, and competing solar sail concepts. Results of these studies will quantify the performance of Ultrasail compared to existing solar sail concepts for high energy missions.

Burton, R.↗

The Software Design for the Wide-Field Infrared Explorer Attitude Control System

The Wide-Field Infrared Explorer (WIRE), currently scheduled for launch in September 1998, is the fifth of five spacecraft in the NASA/Goddard Small Explorer (SMEX) series. This paper presents the design of WIRE's Attitude Control System flight software (ACS FSW). WIRE is a momentum-biased, three-axis stabilized stellar pointer which provides high-accuracy pointing and autonomous acquisition for eight to ten stellar targets per orbit. WIRE's short mission life and limited cryogen supply motivate requirements for Sun and Earth avoidance constraints which are designed to prevent catastrophic instrument damage and to minimize the heat load on the cryostat. The FSW implements autonomous fault detection and handling (FDH) to enforce these instrument constraints and to perform several other checks which insure the safety of the spacecraft. The ACS FSW implements modules for sensor data processing, attitude determination, attitude control, guide star acquisition, actuator command generation, command/telemetry processing, and FDH. These software components are integrated with a hierarchical control mode managing module that dictates which software components are currently active. The lowest mode in the hierarchy is the 'safest' one, in the sense that it utilizes a minimal complement of sensors and actuators to keep the spacecraft in a stable configuration (power and pointing constraints are maintained). As higher modes in the hierarchy are achieved, the various software functions are activated by the mode manager, and an increasing level of attitude control accuracy is provided. If FDH detects a constraint violation or other anomaly, it triggers a safing transition to a lower control mode. The WIRE ACS FSW satisfies all target acquisition and pointing accuracy requirements, enforces all pointing constraints, provides the ground with a simple means for reconfiguring the system via table load, and meets all the demands of its real-time embedded environment (16 MHz Intel 80386 processor with 80387 coprocessor running under the VRTX operating system). The mode manager organizes and controls all the software modules used to accomplish these goals, and in particular, the FDH module is tightly coupled with the mode manager.

Anderson, Mark O.↗

Environmental Control System Development

With the ever-growing desire for mankind to reach destinations whose distances had been deemed impossible to transit, the largest rocket known to man was designed and is being developed. The Space Launch System (SLS), National Aeronautics and Space Administration’s (NASA) solution for deep space travel, will begin its missions with the launch of Exploration Mission 1 (EM-1) and Exploration Mission 2 (EM-2). In order to accommodate the larger rocket, Kennedy Space Center made crucial upgrades to its existing facilities. At Launch Complex 39B, an entirely new Environmental Control System (ECS) was developed to supply the vehicle with the appropriate air or nitrogen gas mixture for launch. The new ECS displays must undergo Validation and Verification (V&V) using testing procedures developed to meet this requirement.

Stewart, Raymond↗

Expanding the KATE toolbox

KATE (Knowledge-based Autonomous Test Engineer) is a model-based software system developed in the Artificial Intelligence Laboratory at the Kennedy Space Center for monitoring, fault detection, and control of launch vehicles and ground support systems. In order to bring KATE to the level of performance, functionality, and integratability needed for firing room applications, efforts are underway to implement KATE in the C++ programming language using an X-windows interface. Two programs which were designed and added to the collection of tools which comprise the KATE toolbox are described. The first tool, called the schematic viewer, gives the KATE user the capability to view digitized schematic drawings in the KATE environment. The second tool, called the model editor, gives the KATE model builder a tool for creating and editing knowledge base files. Design and implementation issues having to do with these two tools are discussed. It will be useful to anyone maintaining or extending either the schematic viewer or the model editor.

Thomas, Stan J.↗

Enhancements to the KATE model-based reasoning system

KATE (Knowledge-based Autonomous Test Engineer) is a model-based software system developed in the Artificial Intelligence Laboratory at the Kennedy Space Center for monitoring, fault detection, and control of launch vehicles and ground support systems. This report describes two software efforts which enhance the functionality and usability of KATE. The first addition, a flow solver, adds to KATE a tool for modeling the flow of liquid in a pipe system. The second addition adds support for editing KATE knowledge base files to the Emacs editor. The body of this report discusses design and implementation issues having to do with these two tools. It will be useful to anyone maintaining or extending either the flow solver or the editor enhancements.

Thomas, Stan J.↗

COMPASS Final Report: Enceladus Solar Electric Propulsion Stage

The results of the NASA Glenn Research Center (GRC) COllaborative Modeling and Parametric Assessment of Space Systems (COMPASS) internal Solar Electric Propulsion (SEP) stage design are documented in this report (Figure 1.1). The SEP Stage was designed to deliver a science probe to Saturn (the probe design was performed separately by the NASA Goddard Space Flight Center s (GSFC) Integrated Mission Design Center (IMDC)). The SEP Stage delivers the 2444 kg probe on a Saturn trajectory with a hyperbolic arrival velocity of 5.4 km/s. The design carried 30 percent mass, 10 percent power, and 6 percent propellant margins. The SEP Stage relies on the probe for substantial guidance, navigation and control (GN&C), command and data handling (C&DH), and Communications functions. The stage is configured to carry the probe and to minimize the packaging interference between the probe and the stage. The propulsion system consisted of a 1+1 (one active, one spare) configuration of gimbaled 7 kW NASA Evolutionary Xenon Thruster (NEXT) ion propulsion thrusters with a throughput of 309 kg Xe propellant. Two 9350 W GaAs triple junction (at 1 Astronomical Unit (AU), includes 10 percent margin) ultra-flex solar arrays provided power to the stage, with Li-ion batteries for launch and contingency operations power. The base structure was an Al-Li hexagonal skin-stringer frame built to withstand launch loads. A passive thermal control system consisted of heat pipes to north and south radiator panels, multilayer insulation (MLI) and heaters for the Xe tank. All systems except tanks and solar arrays were designed to be single fault tolerant.

Oleson, Steven R.↗

A nonlinear programming method for system design with results that have been implemented

A general nonlinear programming algorithm (NICO) is discussed. An academic optimization example is given. The NICO multi-input, multi-output control system design is discussed. NICO applications relative to launch vehicle autopilot design, space shuttle static balance, transient response criteria in the design of a reentry vehicle control system, and waterjet propulsion and lift system components sized to a large surface effect ship are noted.

Hauser, F.↗

Coherent launch-site atmospheric wind sounder - Theory and experiment

The coherent launch-site atmospheric wind sounder (CLAWS) is a lidar atmospheric wind sensor designed to measure the winds above space launch facilities to an altitude of 20 km. In our development studies, lidar sensor requirements are defined, a system to meet those requirements is defined and built, and the concept is evaluated, with recommendations for the most feasible and cost-effective lidar system for use as an input to a guidance and control system for missile or spacecraft launches. The ability of CLAWS to meet NASA goals for increased safety and launch/mission flexibility is evaluated in a field test program at Kennedy Space Center (KSC) in which we investigate maximum detection range, refractive turbulence, and aerosol backscattering efficiency. The Nd:YAG coherent lidar operating at 1.06 micron with 1-J energy per pulse is able to make real-time measurements of the 3D wind field at KSC to an altitude of 26 km, in good agreement with our performance simulations. It also shows the height and thickness of the volcanic layer caused by the volcanic eruption of Mount Pinatubo in the Philippines.

Hawley, James G.↗

Predicting Ares I Reaction Control System Performance by Utilizing Analysis Anchored with Development Test Data

The Ares I launch vehicle is an integral part of NASA s Constellation Program, providing a foundation for a new era of space access. The Ares I is designed to lift the Orion Crew Module and will enable humans to return to the Moon as well as explore Mars.1 The Ares I is comprised of two inline stages: a Space Shuttle-derived five-segment Solid Rocket Booster (SRB) First Stage (FS) and an Upper Stage (US) powered by a Saturn V-derived J-2X engine. A dedicated Roll Control System (RoCS) located on the connecting interstage provides roll control prior to FS separation. Induced yaw and pitch moments are handled by the SRB nozzle vectoring. The FS SRB operates for approximately two minutes after which the US separates from the vehicle and the US Reaction Control System (ReCS) continues to provide reaction control for the remainder of the mission. A representation of the Ares I launch vehicle in the stacked configuration and including the Orion Crew Exploration Vehicle (CEV) is shown in Figure 1. Each Reaction Control System (RCS) design incorporates a Gaseous Helium (GHe) pressurization system combined with a monopropellant Hydrazine (N2H4) propulsion system. Both systems have two diametrically opposed thruster modules. This architecture provides one failure tolerance for function and prevention of catastrophic hazards such as inadvertent thruster firing, bulk propellant leakage, and over-pressurization. The pressurization system on the RoCS includes two ambient pressure-referenced regulators on parallel strings in order to attain the required system level single Fault Tolerant (FT) design for function while the ReCS utilizes a blow-down approach. A single burst disk and relief valve assembly is also included on the RoCS to ensure single failure tolerance for must-not-occur catastrophic hazards. The Reaction Control Systems are designed to support simultaneously firing multiple thrusters as required

Stein, William B.↗

A SYNCOM SATELLITE PROGRAM

Launching of syncom satellite to determine if control system and communications equipment can be used for advanced sychronous orbit satellites

COMMUNICATIONS SATELLITE↗

Time Triggered Protocol (TTP) for Integration Modular Avionics (IMA)

This viewgraph presentation is a review of the Time Triggered Protocol, designed to work with NASA's Integrated Safety-Critical Advanced Avionics Communication and Control (ISAACC) system. ISAACC is the product of the Propulsion High-Impact Avionics Technologies (PHIAT) project at NASA Marshall Space Flight Center (MSFC) during FY03 to the end of FY05. The goal is an avionics architecture suitable for control and monitoring of safety critical systems of manned spacecraft. It must be scalable to allow its use in robotic vehicles or launch pad and propulsion test stand monitoring and control systems. The developed IMA should have: a common power supply and rugged chassis for a set of modules, many upgradeable software functions on one module (i.e. processing unit Reduced weight, straightforward update and system integration. It is also important that it have Partitioning and a Memory Management Unit (MMU)

Gwaltney, David A.↗

A NASA initiative: Software engineering for reliable complex systems

The objective is the development of methods, technology, and skills that will enable NASA to cost-effectively specify, build, and manage reliable software which can evolve and be maintained over an extended period. The need for such software is rooted in the increasing integration of software and computing components into NASA systems. Current NASA Software Engineering expertise was applied toward some of the largest reliable systems including: shuttle launch; ground support; shuttle simulation; minor control; satellite tracking; and scientific data systems. Unfortunately, no theory exists for reliable complex software systems. NASA is seeking to fill this theoretical gap through a number of approaches. One such approach is to conduct research on theoretical foundations for managing complex software systems. It includes: communication models, new and modified paradigms, and life-cycle models. Another approach is research in the theoretical foundations for reliable software development and validation. It focuses upon formal specifications, programming languages, software engineering systems, software reuse, formal verification, and software safety. Further approaches involve benchmarking a NASA software environment, experimentation within the NASA context, evolution of present NASA methodology, and transfer of technology to the space station software support environment.

Holcomb, Lee B.↗