Search NASA⌕ Search

SEARCH · Search NASA

Results for “Launch Processing”

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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

Remote Software Application and Display Development

The era of the shuttle program has come to an end, but only to give rise to newer and more exciting projects. Now is the time of the Orion spacecraft, a work of art designed to exceed all previous endeavors of man. NASA is exiting the time of exploration and is entering a new period, a period of pioneering. With this new mission, many of NASAs organizations must undergo a great deal of change and development to support the Orion missions. The Spaceport Command and Control System (SCCS) is the new system that will provide NASA the ability to launch rockets into orbit and thus control Orion and other spacecraft as the goal of populating Mars becomes ever increasingly tangible. Since the previous control system, Launch Processing System (LPS), was primarily designed to launch the shuttles, SCCS was needed as Kennedy Space Center (KSC) reorganized to a multiuser spaceport for commercial flights, providing a more versatile control over rockets. Within SCCS, is the Launch Control System (LCS), which is the remote software behind the command and monitoring of flight and ground system hardware. This internship at KSC has involved two main components in LCS, including Remote Software Application and Display development. The display environment provides a graphical user interface for an operator to view and see if any cautions are raised, while the remote applications are the backbone that communicate with hardware, and then relay the data back to the displays. These elements go hand in hand as they provide monitoring and control over hardware and software alike from the safety of the Launch Control Center. The remote software applications are written in Application Control Language (ACL), which must undergo unit testing to ensure data integrity. This paper describes both the implementation and writing of unit tests in ACL code for remote software applications, as well as the building of remote displays to be used in the Launch Control Center (LCC).

ACL↗
NASA NTRS1989

Progress in the use of wind profiling radars for Shuttle launch support

The use of wind profiling radars during Space Shuttle launches is examined. The way in which wind measurements are used in the launch process is described, including monitoring the day of launch winds, flight simulations, and the improvement of the data base which provides the mean winds and monthly variability of wind profiles. Results are presented from tests of two profilers conducted during March and April, 1985. The wind profiling characteristics of three profilers are listed and the winds provided by the profilers are compared to Jimsphere winds.

Smith, Steve A.↗
NASA NTRSDate not supplied

How to Fly with BPO & Requirements & Recommendations for Balloon Gondola Design

An overview of the launch process from initial solicitation through flight. The discussion will include the overall review process for balloon missions seeking flights from all launch locations, high level overview of required documentation, and specific requests for safety review. Also a presentation on the Gondola Structural Design Handbook with recommendations.

Balloon↗
NASA NTRS1999

Launch Vehicle Design Process Description and Training Formulation

A primary NASA priority is to reduce the cost and improve the effectiveness of launching payloads into space. As a consequence, significant improvements are being sought in the effectiveness, cost, and schedule of the launch vehicle design process. In order to provide a basis for understanding and improving the current design process, a model has been developed for this complex, interactive process, as reported in the references. This model requires further expansion in some specific design functions. Also, a training course for less-experienced engineers is needed to provide understanding of the process, to provide guidance for its effective implementation, and to provide a basis for major improvements in launch vehicle design process technology. The objective of this activity is to expand the description of the design process to include all pertinent design functions, and to develop a detailed outline of a training course on the design process for launch vehicles for use in educating engineers whose experience with the process has been minimal. Building on a previously-developed partial design process description, parallel sections have been written for the Avionics Design Function, the Materials Design Function, and the Manufacturing Design Function. Upon inclusion of these results, the total process description will be released as a NASA TP. The design function sections herein include descriptions of the design function responsibilities, interfaces, interactive processes, decisions (gates), and tasks. Associated figures include design function planes, gates, and tasks, along with other pertinent graphics. Also included is an expanded discussion of how the design process is divided, or compartmentalized, into manageable parts to achieve efficient and effective design. A detailed outline for an intensive two-day course on the launch vehicle design process has been developed herein, and is available for further expansion. The course is in an interactive lecture/workshop format to engage the participants in active learning. The course addresses the breadth and depth of the process, requirements, phases, participants, multidisciplinary aspects, tasks, critical elements,as well as providing guidance from previous lessons learned. The participants are led to develop their own understanding of the current process and how it can be improved. Included are course objectives and a session-by-session outline of course content. Also included is an initial identification of visual aid requirements.

Atherton, James↗
NASA NTRS1987

Large charged drop levitation against gravity

A hybrid electrostatic-acoustic levitator that can levitate and manipulate a large liquid drop in one gravity is presented. To the authors' knowledge, this is the first time such large drops (up to 4 mm in diameter in the case of water) have been levitated against 1-gravity. This makes possible, for the first time, many new experiments both in space and in ground-based laboratories, such as 1)supercooling and superheating, 2) containerless crystal growth from various salt solutions or melts, 3) drop dynamics of oscillating or rotating liquid drops, 4) drop evaporation and Rayleigh bursting, and 5) containerless material processing in space. The digital control system, liquid drop launch process, principles of electrode design, and design of a multipurpose room temperature levitation chamber are described. Preliminary results that demonstrate drop oscillation and rotation, and crystal growth from supersaturated salt solutions are presented.

Rhim, Won-Kyu↗
NASA NTRS1988

Artificial intelligent decision support for low-cost launch vehicle integrated mission operations

The feasibility, benefits, and risks associated with Artificial Intelligence (AI) Expert Systems applied to low cost space expendable launch vehicle systems are reviewed. This study is in support of the joint USAF/NASA effort to define the next generation of a heavy-lift Advanced Launch System (ALS) which will provide economical and routine access to space. The significant technical goals of the ALS program include: a 10 fold reduction in cost per pound to orbit, launch processing in under 3 weeks, and higher reliability and safety standards than current expendables. Knowledge-based system techniques are being explored for the purpose of automating decision support processes in onboard and ground systems for pre-launch checkout and in-flight operations. Issues such as: satisfying real-time requirements, providing safety validation, hardware and Data Base Management System (DBMS) interfacing, system synergistic effects, human interfaces, and ease of maintainability, have an effect on the viability of expert systems as a useful tool.

Szatkowski, Gerard P.↗
NASA NTRS2002

Development of a Launch Vehicle Manufacturing Process

One of the goals of this chapter is to provide sufficient information so that you can develop a manufacturing process for a potential launch vehicle. With the variety of manufacturing options available, you might ask how this can possibly be done in the span of a single chapter. Actually, it will be quite simple because a basic manufacturing process is nothing more than a set of logical steps that are iterated until they produce a desired product. Although these statements seem simple and logical, don't let this simplicity fool you. Manufacturing problems with launch vehicles and their subassemblies have been the primary cause of project failures because the vehicle concept delivered to the manufacturing floor could not be built as designed.

Vickers, John↗
NASA NTRS1982

Processing PCM Data in Real Time

Novel hardware configuration makes it possible for Space Shuttle launch processing system to monitor pulse-code-modulated data in real time. Using two microprogramable "option planes," incoming PCM data are monitored for changes at rate of one frame of data (80 16-bit words) every 10 milliseconds. Real-time PCM processor utilizes CPU in mini-computer and CPU's in two option planes.

Wissink, T. L.↗
NASA NTRSDate not supplied

Artemis I: Test Flight Buys Down Risk for Humanity's Return to the Moon

The Artemis program successfully demonstrated its foundational deep space human transportation system during the Artemis I test flight in late 2022. This bold mission put the Artemis program on a course to accomplish increasingly complex missions to return humans to the Moon and to prepare for Mars and other destinations. The Artemis I uncrewed mission tested the Space Launch System (SLS) rocket and the Orion spacecraft using the ground processing, launch and recovery services provided by the Exploration Ground Systems (EGS) program at the Kennedy Space Center (KSC). The Artemis team accomplished key mission priorities that deliberately bought down risk for upcoming crewed missions as part of a build-up flight test strategy. The Artemis I mission priorities were 1) demonstrate Orion heatshield at lunar re-entry conditions; 2) operate systems in flight environment; and 3) retrieve the spacecraft. The successful performance and demonstration of these primary mission objectives from lift-off thru orbital insertion, translunar injection, outbound transit towards the Moon, entry into lunar orbit, coast in the lunar Distant Retrograde Orbit (DRO), exit from lunar orbit, transit back to Earth, atmospheric re-entry, descent, splashdown and recovery successfully showed that NASA has a foundational deep space transportation capability in place for human class missions. In addition to the primary mission objectives, a set of scientific payloads, approved Flight Test Objectives (FTOs) and Development Flight Test Objectives (DFTOs) were incorporated into the nominal mission plan and were designated as secondary, or priority 4, and were considered “bonus objectives” in terms of crewed flight risk buydown. During the mission, the team found itself in a position where it was comfortable achieving even more content than originally planned. As a result, DFTOs were added during the mission to further buy down risk to later crewed test flights. This paper presents an overview of the Artemis I test flight, including mission priorities and key test objectives, the launch campaign and as-flown mission profile, test objectives accomplished over the course of the 25.5- day mission, and implications to the crewed Artemis II and later test flight missions.

Artemis↗
NASA NTRS1992

Applications of triggered lightning to space vehicle operations

Kennedy Space Center (KSC) and the USAF Eastern Space Missile Center (ESMC) covering an area of 25 x 40 km are frequently called America's Spaceport. This title is earned through the integration, by labor and management, of many skills in a wide variety of engineering fields to solve many technical problems that occur during the launch processing of space vehicles. Weather is one of these problems, and although less frequent in time and duration when compared to engineering type problems, has caused costly and life threatening situations. This sensitivity to weather, especially lightning, was recognized in the very early pioneer days of space operations. The need to protect the many v\facilities, space flight hardware, and personnel from electrified clouds capable of producing lightning was a critical element in improving launch operations. A KSC lightning committee was formed and directed to improve lightning protection, detection, and measuring systems and required that all theoretical studies be confirmed by KSC field data. Over the years, there have been several lightning incidents involving flight vehicles during ground processing as well as launch. Subsequent investigations revealed the need to improve these systems as well as the knowledge of the electrical atmosphere and its effects on operations in regard to cost and safety. Presented here is how, KSC Atmospheric Science Field Laboratory (AFSL), in particular Rocket Triggered Lightning, is being used to solve these problems.

Jafferis, William↗
NASA NTRSDate not supplied

NASA CARA Prelaunch Analysis and Process

NASA implemented an official Procedural Requirement (NPR) 8079.1 in June 2023, establishing the minimum collision avoidance requirements and associated operational protocols for NASA space flight programs, projects, and spacecraft to protect the space environment by reducing the risk of collision to an acceptable level. Part of the requirement employs a two-fold approach to analyze the satellite design process with conjunction assessment and risk mitigation in mind, during the pre-launch process, led by the Conjunction Assessment Risk Analysis (CARA) Program for non-Human Space Flight (HSF) Missions. This presentation outlines CARA coordination with missions, informed by the NPR, that spans early mission development to operations. CARA is an Agency-level resource that provides support to all NASA non-HSF missions. CARA protects the orbital environment from collision between NASA non-HSF missions and other tracked on-orbit objects. During the pre-formulation and formulation phases, NASA missions undergo a series of conjunction assessment analyses captured in the Orbital Collision Avoidance Plan (OCAP) prior to transitioning to the implementation phase (typically at the Preliminary Design Review (PDR) or equivalent). The OCAP analyses consist of a thorough review of the spacecraft(s) orbit selection and placement, deployment, cataloguing performance, trackability, ephemeris generation, conjunction mitigation options, autonomous maneuvering, and risk assessment parameters which are performed by a dedicated CARA Analysis Team. The results of these analyses, CARA’s formal recommendations, and the mission’s methods for implementing them, are documented in the OCAP. The intent of engaging in this process so early in the mission design phase, is to ensure that conjunction assessment is considered from the outset, thus mitigating costly design changes and operational risks down the road. NASA missions are also required to coordinate their operational processes and conjunction mitigation procedures with CARA in a Conjunction Assessment Operations Implementation Agreement (CAOIA). The aim of this process is to document the conjunction assessment screening process, conjunction risk assessment parameters, conjunction mitigation steps, flight dynamics operations concepts and maneuvers, and the communication and coordination process between the mission’s project manager and CARA. The intent of the CAOIA document is for it to be completed iteratively, and as missions update these elements, corresponding changes are made in the CAOIA. With this process in place, the engagement and coordination between the missions and CARA from early in the design process into mission operations, helps to ensure that missions not only have a robust conjunction assessment concept of operations to reduce conjunction risk for space sustainability, but are also able to achieve their science goals and have a successful mission.

conjunction assessment↗
NASA NTRSDate not supplied

NASA CARA Prelaunch Analysis and Process

NASA implemented an official Procedural Requirement (NPR) 8079.1 in June 2023, establishing the minimum collision avoidance requirements and associated operational protocols for NASA space flight programs, projects, and spacecraft to protect the space environment by reducing the risk of collision to an acceptable level. Part of the requirement employs a two-fold approach to analyze the satellite design process with conjunction assessment and risk mitigation in mind, during the pre-launch process, led by the Conjunction Assessment Risk Analysis (CARA) Program for non-Human Space Flight (HSF) Missions. This presentation outlines CARA coordination with missions, informed by the NPR, that spans early mission development to operations. CARA is an Agency-level resource that provides support to all NASA non-HSF missions. CARA protects the orbital environment from collision between NASA non-HSF missions and other tracked on-orbit objects. During the pre-formulation and formulation phases, NASA missions undergo a series of conjunction assessment analyses captured in the Orbital Collision Avoidance Plan (OCAP) prior to transitioning to the implementation phase (typically at the Preliminary Design Review (PDR) or equivalent). The OCAP analyses consist of a thorough review of the spacecraft(s) orbit selection and placement, deployment, cataloguing performance, trackability, ephemeris generation, conjunction mitigation options, autonomous maneuvering, and risk assessment parameters which are performed by a dedicated CARA Analysis Team. The results of these analyses, CARA’s formal recommendations, and the mission’s methods for implementing them, are documented in the OCAP. The intent of engaging in this process so early in the mission design phase, is to ensure that conjunction assessment is considered from the outset, thus mitigating costly design changes and operational risks down the road. NASA missions are also required to coordinate their operational processes and conjunction mitigation procedures with CARA in a Conjunction Assessment Operations Implementation Agreement (CAOIA). The aim of this process is to document the conjunction assessment screening process, conjunction risk assessment parameters, conjunction mitigation steps, flight dynamics operations concepts and maneuvers, and the communication and coordination process between the mission’s project manager and CARA. The intent of the CAOIA document is for it to be completed iteratively, and as missions update these elements, corresponding changes are made in the CAOIA. With this process in place, the engagement and coordination between the missions and CARA from early in the design process into mission operations, helps to ensure that missions not only have a robust conjunction assessment concept of operations to reduce conjunction risk for space sustainability, but are also able to achieve their science goals and have a successful mission.

conjunction assessment↗
NASA NTRS2013

Progress in Operational Analysis of Launch Vehicles in Nonstationary Flight

This paper presents recent results in an ongoing effort to understand and develop techniques to process launch vehicle data, which is extremely challenging for modal parameter identification. The primary source of difficulty is due to the nonstationary nature of the situation. The system is changing, the environment is not steady, and there is an active control system operating. Hence, the primary tool for producing clean operational results (significant data lengths and data averaging) is not available to the user. This work reported herein uses a correlation-based two step operational modal analysis approach to process the relevant data sets for understanding and development of processes. A significant drawback for such processing of short time histories is a series of beating phenomena due to the inability to average out random modal excitations. A recursive correlation process coupled to a new convergence metric (designed to mitigate the beating phenomena) is the object of this study. It has been found in limited studies that this process creates clean modal frequency estimates but numerically alters the damping.

James, George↗
NASA NTRS2012

The Application of the NASA Advanced Concepts Office, Launch Vehicle Team Design Process and Tools for Modeling Small Responsive Launch Vehicles

The Advanced Concepts Office (ACO) Launch Vehicle Team at the NASA Marshall Space Flight Center (MSFC) is recognized throughout NASA for launch vehicle conceptual definition and pre-phase A concept design evaluation. The Launch Vehicle Team has been instrumental in defining the vehicle trade space for many of NASA s high level launch system studies from the Exploration Systems Architecture Study (ESAS) through the Augustine Report, Constellation, and now Space Launch System (SLS). The Launch Vehicle Team s approach to rapid turn-around and comparative analysis of multiple launch vehicle architectures has played a large role in narrowing the design options for future vehicle development. Recently the Launch Vehicle Team has been developing versions of their vetted tools used on large launch vehicles and repackaged the process and capability to apply to smaller more responsive launch vehicles. Along this development path the LV Team has evaluated trajectory tools and assumptions against sounding rocket trajectories and air launch systems, begun altering subsystem mass estimating relationships to handle smaller vehicle components, and as an additional development driver, have begun an in-house small launch vehicle study. With the recent interest in small responsive launch systems and the known capability and response time of the ACO LV Team, ACO s launch vehicle assessment capability can be utilized to rapidly evaluate the vast and opportune trade space that small launch vehicles currently encompass. This would provide a great benefit to the customer in order to reduce that large trade space to a select few alternatives that should best fit the customer s payload needs.

Threet, Grady E.↗
NASA NTRS1996

Software Reliability Issues Concerning Large and Safety Critical Software Systems

This research was undertaken to provide NASA with a survey of state-of-the-art techniques using in industrial and academia to provide safe, reliable, and maintainable software to drive large systems. Such systems must match the complexity and strict safety requirements of NASA's shuttle system. In particular, the Launch Processing System (LPS) is being considered for replacement. The LPS is responsible for monitoring and commanding the shuttle during test, repair, and launch phases. NASA built this system in the 1970's using mostly hardware techniques to provide for increased reliability, but it did so often using custom-built equipment, which has not been able to keep up with current technologies. This report surveys the major techniques used in industry and academia to ensure reliability in large and critical computer systems.

Kamel, Khaled↗
NASA NTRS1991

Development of a relatchable cover mechanism for a cryogenic IR-sensor

A cover mechanism for use on the Infrared Background Signature Survey (IBSS) cryostat was developed. The IBSS IR-instrument is scheduled for STS launch in early 1991 as a payload of the Shuttle Payload Satellite (SPS) 2. The cover is hinged, with a motorized rope drive. During ground processing, launch, entry, and landing, the cryostat, which houses the IR-instrument, is required to be a sealed vacuum tight container for cooling purposes and contamination prevention. When on orbit, the cover is opened to provide an unobstructed field of view for the IR-instrument. A positive seal is accomplished through the use of latch mechanism. The cover and the latch are driven by a common redundant actuator consisting of dc motors, spur gears, and a differential gear. Hall probe limit switches and position sensors (rotary variable transformer) are used to determine the position of the cover and the latch. The cover mechanism was successfully qualified for thermal vacuum (-25 to 35 C), acoustic noise, vibration (6 Gs sine, 9.7 G RMS) and life cycles. Constricting requirements, mechanical and electronic control design, specific design details, test results of functional performance, and environmental and life tests are described.

Birner, R.↗