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.
Two-step flow control adjusts to dimensional changes in purged equipment. Two pressure actuated valves provide two-step control. When turbopump starts, helium flows through both valves. As pump operates its parts expand, clearance decrease and back pressure builds up on valves. At preset back pressure value, one valve closes, reducing helium flow.
NASA's Constellation Program is depending on the Ares Projects to deliver the crew and cargo launch capabilities needed to send human explorers to the Moon and beyond. Ares I and V will provide the core space launch capabilities needed to continue providing crew and cargo access to the International Space Station (ISS), and to build upon the U.S. history of human space exploration. Since 2005, Ares has made substantial progress on designing, developing, and testing the Ares I crew launch vehicle and has continued its in-depth studies of the Ares V cargo launch vehicles. The combined Ares I/Ares V architecture has been designed to reduce the complexity and labor intensity of ground operations for America's next journeys beyond low-Earth orbit (LEO). A deliberate effort is being made to ensure a high level of system operability to significantly increase safety and system availability as well as reduce recurring costs for this new launch vehicle. The Ares Projects goal is to instill operability as part of the vehicles requirements development, design, and operations. This simplicity will come from using simpler, proven engine designs, as in the case of the J-2X upper stage engine and RS-68 engine; improving existing hardware, as in the case of the Shuttle-heritage 5-segment solid rocket motor; and using common propulsion and instrument unit elements between Ares I and Ares V. Furthermore, lessons learned while developing Ares I will be applied directly to Ares V operations. In 2009, the Ares Projects plan to conduct the first flight test of Ares I, designated Ares I-X. Ares I-X preparations have already prompted changes to the vehicle stacking and launch infrastructure at Kennedy Space Center (KSC), including removing Shuttle-specific fixtures from the Vehicle Assembly Building (VAB) to accommodate Ares I-style stacking operations, new firing room computers and infrastructure in the VAB Launch Control Center, and new lightning protection system towers at Launch Complex 39B to accommodate the greater height of Ares I-X. In addition to lessons learned from the stacking of Ares I-X, the flight test itself promises to yield important data and operations lessons for assembling, launching, and flying Ares I.
This software is a component in an unmanned ground vehicle (UGV) perception system that builds compact, single-frame terrain maps for distribution to other systems, such as a world model or an operator control unit, over a local area network (LAN). Each cell in the map encodes an elevation value, terrain classification, object classification, terrain traversability, terrain roughness, and a confidence value into four bytes of memory. The input to this software component is a range image (from a lidar or stereo vision system), and optionally a terrain classification image and an object classification image, both registered to the range image. The single-frame terrain map generates estimates of the support surface elevation, ground cover elevation, and minimum canopy elevation; generates terrain traversability cost; detects low overhangs and high-density obstacles; and can perform geometry-based terrain classification (ground, ground cover, unknown). A new origin is automatically selected for each single-frame terrain map in global coordinates such that it coincides with the corner of a world map cell. That way, single-frame terrain maps correctly line up with the world map, facilitating the merging of map data into the world map. Instead of using 32 bits to store the floating-point elevation for a map cell, the vehicle elevation is assigned to the map origin elevation and reports the change in elevation (from the origin elevation) in terms of the number of discrete steps. The single-frame terrain map elevation resolution is 2 cm. At that resolution, terrain elevation from 20.5 to 20.5 m (with respect to the vehicle's elevation) is encoded into 11 bits. For each four-byte map cell, bits are assigned to encode elevation, terrain roughness, terrain classification, object classification, terrain traversability cost, and a confidence value. The vehicle s current position and orientation, the map origin, and the map cell resolution are all included in a header for each map. The map is compressed into a vector prior to delivery to another system.
The future of the National Aeronautics and Space Administration (NASA) depends on its innovation and efficiency in the coming years. With ambitious goals to reach Mars and explore the vast universe, correct steps must be taken to ensure our space program reaches its destination safely. The interns in the Exploration Systems and Operations Division at the Kennedy Space Center (KSC) have been tasked with building command line tools to ease the process of managing and testing the data being produced by the ground control systems while its recording system is not in use. While working alongside full-time engineers, we were able to create multiple programs that reduce the cost and time it takes to test the subsystems that launch rockets to outer space.
Conflict Alerts for aircraft in holding patterns are often missed or in error due to fact that holding trajectories are not modeled in Conflict Alert or Conflict Probe logic. In addition, a controller in one sector may not know when aircraft are holding in a neighboring sector. These factors can lead to an increased potential for loss of separation while aircraft are flying in holding patterns. A holding function for conflict probe applications has been developed and tested with air traffic data from Fort Worth Center. The holding function automatically determines when an aircraft enters a holding pattern, builds a holding region around the pattern and then probes the region for conflict with other traffic. The operational concept of use assumes that air traffic controllers are very busy during periods when aircraft are in holding and therefore don't have time to manually enter information which defines a holding pattern and activates conflict probing. For this reason, it is important the holding function automatically detect aircraft in holding and compute a holding region for conflict analysis. The controller is then alerted if other aircraft are predicted to fly through the holding region at the holding altitude.
Ames Research Center granted Reality Capture Technologies (RCT), Inc., a license to further develop NASA's Mars Map software platform. The company incorporated NASA#s innovation into software that uses the Virtual Plant Model (VPM)(TM) to structure, modify, and implement the construction sites of industrial facilities, as well as develop, validate, and train operators on procedures. The VPM orchestrates the exchange of information between engineering, production, and business transaction systems. This enables users to simulate, control, and optimize work processes while increasing the reliability of critical business decisions. Engineers can complete the construction process and test various aspects of it in virtual reality before building the actual structure. With virtual access to and simulation of the construction site, project personnel can manage, access control, and respond to changes on complex constructions more effectively. Engineers can also create operating procedures, training, and documentation. Virtual Plant Model(TM) is a trademark of Reality Capture Technologies, Inc.
The Advanced Inspection System (AIS) promotes the ability to perform field inspections and repairs remotely by operator command. The robotic system is required to be a fully autonomous operation, managed by computer execution of scripts with limited user control. AIS is a complex yet intriguing challenge in which various goals must be reached to achieve complete autonomy. The first steps to building such a system require human computer interactions and computer simulations for testing and verification. Such applications include the use of a wireless video game controller via Bluetooth Technology and the use of Leap Motion, a gesture based motion controller which can be used to manipulate robotic arm movements. Utilizing the Robotic Operating System (ROS) environment, these applications, in accordance to developing a 3D simulation of the system, will provide a foundational test bed for AIS development.
Due to the criticality of continuous mission operations, some control centers must plan for alternate locations in the event an emergency shuts down the primary control center. Johnson Space Center (JSC) in Houston, Texas is the Mission Control Center (MCC) for the International Space Station (ISS). Due to Houston s proximity to the Gulf of Mexico, JSC is prone to threats from hurricanes which could cause flooding, wind damage, and electrical outages to the buildings supporting the MCC. Marshall Space Flight Center (MSFC) has the capability to be the Backup Control Center for the ISS if the situation is needed. While the MSFC Huntsville Operations Support Center (HOSC) does house the BCC, the prime customer and operator of the ISS is still the JSC flight operations team. To satisfy the customer and maintain continuous mission operations, the BCC has critical infrastructure that hosts ISS ground systems and flight operations equipment that mirrors the prime mission control facility. However, a complete duplicate of Mission Control Center in another remote location is very expensive to recreate. The HOSC has infrastructure and services that MCC utilized for its backup control center to reduce the costs of a somewhat redundant service. While labor talents are equivalent, experiences are not. Certain operations are maintained in a redundant mode, while others are simply maintained as single string with adequate sparing levels of equipment. Personnel at the BCC facility must be trained and certified to an adequate level on primary MCC systems. Negotiations with the customer were done to match requirements with existing capabilities, and to prioritize resources for appropriate level of service. Because some of these systems are shared, an activation of the backup control center will cause a suspension of scheduled HOSC activities that may share resources needed by the BCC. For example, the MCC is monitoring a hurricane in the Gulf of Mexico. As the threat to MCC increases, HOSC must begin a phased activation of the BCC, while working resource conflicts with normal HOSC activities. In a long duration outage to the MCC, this could cause serious impacts to the BCC host facility s primary mission support activities. This management of a BCC is worked based on customer expectations and negotiations done before emergencies occur. I.
A major effort at the NASA Lewis Research Center in recent years has been to develop electro-mechanical actuators (EMA's) to replace the hydraulic systems used for thrust vector control (TVC) on launch vehicles. This is an attempt ot overcome the inherent inefficiencies and costs associated with the existing hydraulic structures. General Dynamics Space Systems Division, under contract to NASA Lewis, is developing 18.6 kW (25 hp), 29.8 kW (40 hp), and 52.2 kW (70 hp) peak EMA systems to meet the power demands for TVC on a family of vehicles developed for the National Launch System. These systems utilize a pulse population modulated converter and field-oriented control scheme to obtain independent control of both the voltage and frequency. These techniques allow an induction motor to be operated at its maximum torque at all times. At NASA Lewis, we are building on this technology to develop our own in-house system capable of meeting the peak power requirements for an expendable launch vehicle (ELV) such as the Atlas. Our EMA will be capable of delivering 22.4 kW (30 hp) peak power with a nominal of 6.0 kW (8 hp). This system differs from the previous ones in two areas: (1) the use of advanced control methods, and (2) the incorporation of built-in-test. The advanced controls are essential for minimizing the controller size, while the built-in-test is necessary to enhance the system reliability and vehicle health monitoring. The ultimate goal of this program is to demonstrate an EMA which will be capable of self-test and easy integration into other projects. This paper will describe the effort underway at NASA Lewis to develop an EMA for an Atlas class ELV. An explanation will be given for each major technology block, and the status of each major technology block and the status of the overall program will be reported.
Communication, navigation, flight control, and search sensor management are avionics functions which constitute every Search and Rescue (SAR) operation. Routine cockpit duties monopolize crew attention during SAR operations and thus impair crew effectiveness. The United States Coast Guard challenged industry to build an avionics system that automates routine tasks and frees the crew to focus on the mission tasks. The HH-64A SAR avionics systems of communication, navigation, search sensors, and flight control have existed independently. On the SRR helicopter, the flight management system (FMS) was introduced. H coordinates or integrates these functions. The pilot interacts with the FMS rather than the individual subsystems, using simple, straightforward procedures to address distinct mission tasks and the flight management system, in turn, orchestrates integrated system response.
NASA Goddard Space Flight Center (GSFC) designs, builds, manages, and operates science and applications spacecraft in near-earth orbit, and provides data capture, data processing, and flight control services for these spacecraft. In addition, GSFC has the responsibility of providing space-ground and ground-ground communications for near-earth orbiting spacecraft, including those of the manned spaceflight programs. The goal of reducing both the developmental and operating costs of the end-to-end information system has led the GSFC to support and participate in the standardization activities of the Consultative Committee for Space Data Systems (CCSDS), including those for packet telemetry. The environment in which such systems function is described, and the GSFC experience with CCSDS packet telemetry in the context of the Gamma-Ray Observatory project is discussed.
Gas turbine engines are designed to provide sufficient safety margins to guarantee robust operation with an exceptionally long life. However, engine performance requirements may be drastically altered during abnormal flight conditions or emergency maneuvers. In some situations, the conservative design of the engine control system may not be in the best interest of overall aircraft safety; it may be advantageous to "sacrifice" the engine to "save" the aircraft. Motivated by this opportunity, the NASA Aviation Safety Program is conducting resilient propulsion research aimed at developing adaptive engine control methodologies to operate the engine beyond the normal domain for emergency operations to maximize the possibility of safely landing the damaged aircraft. Previous research studies and field incident reports show that the propulsion system can be an effective tool to help control and eventually land a damaged aircraft. Building upon the flight-proven Propulsion Controlled Aircraft (PCA) experience, this area of research will focus on how engine control systems can improve aircraft safe-landing probabilities under adverse conditions. This paper describes the proposed research topics in Engine System Requirements, Engine Modeling and Simulation, Engine Enhancement Research, Operational Risk Analysis and Modeling, and Integrated Flight and Propulsion Controller Designs that support the overall goal.
The principles and reasons for employing Human Autonomy Teaming is discussed. Application of these techniques to multi-vehicle control is described. In several operational environments from small drone delivery to air taxi to autonomous cargo, many companies will need technologies that will allow for the operation of an unmanned aircraft (UAS or eVTOL) by a small crew of individuals that are located in a remote network operations center. That is, Multiple operators supervising an increasing Number of vehicles (M:N).This will require a new control/supervisory paradigm where the supervisors team with automation to achieve their joint tasks; Human Autonomy Teaming (HAT).This task will follow the HAT philosophy and tenants (e.g., trust, bi-directional communication, pilot directed interfaces). It will also develop and employ specific HAT tools (e.g., playbook, working agreements, predictive timeline displays, transparent interfaces to build trust). This presentation discusses the barriers and requirements for future m:N operations.
The United States (U.S.) plans to return to the Moon by 2020, with the development of a new human-rated space transportation system to replace the Space Shuttle, which is due for retirement in 2010 after it completes its missions of building the International Space Station and servicing the Hubble Space Telescope. Powering the future of space-based scientific exploration will be the Ares I Crew Launch Vehicle, which will transport the Orion Crew Exploration Vehicle to orbit where it will rendezvous with the Lunar Lander. which will be delivered by the Ares V Cargo Launch Vehicle. This new transportation infrastructure, developed by the National Aeronautics and Space Administration (NASA), will allow astronauts to leave low-Earth orbit for extended lunar exploration and preparation for the first footprint on Mars. All space-based operations begin and are controlled from Earth. NASA's philosophy is to deliver safe, reliable, and cost-effective solutions to sustain a multi-billion-dollar program across several decades. Leveraging 50 years of lessons learned, NASA is partnering with private industry, while building on proven hardware experience. This paper will discuss how the Engineering Directorate at NASA's Marshall Space Flight Center is working with the Ares Projects Office to streamline ground operations concepts and reduce costs. Currently, NASA's budget is around $17 billion, which is less than 1 percent of the U.S. Federal budget. Of this amount, NASA invests approximately $4.5 billion each year in Space Shuttle operations, regardless of whether the spacecraft is flying or not. The affordability requirement is for the Ares I to reduce this expense by 50 percent, in order to allow NASA to invest more in space-based scientific operations. Focusing on this metric, the Engineering Directorate provides several solutions-oriented approaches, including Lean/Six Sigma practices and streamlined hardware testing and integration, such as assembling major hardware elements before shipping to the Kennedy Space Center for launch operations. This paper provides top-level details for several cost saving initiatives, including both process and product improvements that will result in space transportation systems that are designed with operations efficiencies in mind. The Engineering Directorate provides both the intellectual capital embodied in an experienced workforce and unique facilities in which to validate the information technology tools that allow a nationwide team to collaboratively connect across miles that separate them and the engineering disciplines that integrate various piece parts into a whole system. As NASA transforms ground-based operations, it also is transitioning its workforce from an era of intense hands-on labor to a new one of mechanized conveniences and robust hardware with simpler interfaces. Ensuring that space exploration is on sound footing requires that operations efficiencies be designed into the transportation system and implemented in the development stage. Applying experience gained through decades of ground and space op'erations, while using value-added processes and modern business and engineering tools, is the philosophy upon which a new era of exploration will be built to solve some of the most pressing exploration challenges today -- namely, safety, reliability, and affordability.
The tasks to be carried out during the three-year project period are: (1) performing extensive simulation using existing mathematical models to build a specific knowledge base of the operating characteristics of space power systems; (2) carrying out the necessary basic research on hierarchical control structures, real-time quantitative algorithms, and decision-theoretic procedures; (3) developing a two-level automation scheme for fault detection and diagnosis, maintenance and restoration scheduling, and load management; and (4) testing and demonstration. The outlines of the proposed system structure that served as a master plan for this project, work accomplished, concluding remarks, and ideas for future work are also addressed.
Researchers at NASA are investigating the potential for electric propulsion systems to revolutionize the design of aircraft from the small-scale general aviation sector to commuter and transport-class vehicles. Electric propulsion provides new degrees of design freedom that may enable opportunities for tightly coupled design and optimization of the propulsion system with the aircraft structure and control systems. This could lead to extraordinary reductions in ownership and operating costs, greenhouse gas emissions, and noise annoyance levels. We are building testbeds, high-fidelity aircraft simulations, and the first highly distributed electric inhabited flight test vehicle to begin to explore these opportunities.
Researchers at NASA are investigating the potential for electric propulsion systems to revolutionize the design of aircraft from the small-scale general aviation sector to commuter and transport-class vehicles. Electric propulsion provides new degrees of design freedom that may enable opportunities for tightly coupled design and optimization of the propulsion system with the aircraft structure and control systems. This could lead to extraordinary reductions in ownership and operating costs, greenhouse gas emissions, and noise annoyance levels. We are building testbeds, high-fidelity aircraft simulations, and the first highly distributed electric inhabited flight test vehicle to begin to explore these opportunities.
As the International Space Station (ISS) has moved into a utilization phase, operations have shifted to become more ground-based with fewer mission control personnel monitoring and commanding multiple ISS systems. This shift to fewer people monitoring more systems has prompted use of semi-autonomous console tools in the ISS Mission Control Center (MCC) to help flight controllers command and monitor the ISS. These console tools perform routine operational procedures while keeping the human operator "in the loop" to monitor and intervene when off-nominal events arise. Two such tools, the Pre-positioned Load (PPL) Loader and Automatic Operators Recorder Manager (AutoORM), are used by the ISS Communications RF Onboard Networks Utilization Specialist (CRONUS) flight control position. CRONUS is responsible for simultaneously commanding and monitoring the ISS Command & Data Handling (C&DH) and Communications and Tracking (C&T) systems. PPL Loader is used to uplink small pieces of frequently changed software data tables, called PPLs, to ISS computers to support different ISS operations. In order to uplink a PPL, a data load command must be built that contains multiple user-input fields. Next, a multiple step commanding and verification procedure must be performed to enable an onboard computer for software uplink, uplink the PPL, verify the PPL has incorporated correctly, and disable the computer for software uplink. PPL Loader provides different levels of automation in both building and uplinking these commands. In its manual mode, PPL Loader automatically builds the PPL data load commands but allows the flight controller to verify and save the commands for future uplink. In its auto mode, PPL Loader automatically builds the PPL data load commands for flight controller verification, but automatically performs the PPL uplink procedure by sending commands and performing verification checks while notifying CRONUS of procedure step completion. If an off-nominal condition occurs during procedure execution, PPL Loader notifies CRONUS through popup messages, allowing CRONUS to examine the situation and choose an option of how PPL loader should proceed with the procedure. The use of PPL Loader to perform frequent, routine PPL uplinks offloads CRONUS to better monitor two ISS systems. It also reduces procedure performance time and decreases risk of command errors. AutoORM identifies ISS communication outage periods and builds commands to lock, playback, and unlock ISS Operations Recorder files. Operation Recorder files are circular buffer files of continually recorded ISS telemetry data. Sections of these files can be locked from further writing, be played back to capture telemetry data that occurred during an ISS loss of signal (LOS) period, and then be unlocked for future recording use. Downlinked Operation Recorder files are used by mission support teams for data analysis, especially if failures occur during LOS. The commands to lock, playback, and unlock Operations Recorder files are encompassed in three different operational procedures and contain multiple user-input fields. AutoORM provides different levels of automation for building and uplinking the commands to lock, playback, and unlock Operations Recorder files. In its automatic mode, AutoORM automatically detects ISS LOS periods, then generates and uplinks the commands to lock, playback, and unlock Operations Recorder files when MCC regains signal with ISS. AutoORM also features semi-autonomous and manual modes which integrate CRONUS more into the command verification and uplink process. AutoORMs ability to automatically detect ISS LOS periods and build the necessary commands to preserve, playback, and release recorded telemetry data greatly offloads CRONUS to perform more high-level cognitive tasks, such as mission planning and anomaly troubleshooting. Additionally, since Operations Recorder commands contain numerical time input fields which are tedious for a human to manually build, AutoORM's ability to automatically build commands reduces operational command errors. PPL Loader and AutoORM demonstrate principles of semi-autonomous operational tools that will benefit future space mission operations. Both tools employ different levels of automation to perform simple and routine procedures, thereby offloading human operators to perform higher-level cognitive tasks. Because both tools provide procedure execution status and highlight off-nominal indications, the flight controller is able to intervene during procedure execution if needed. Semi-autonomous tools and systems that can perform routine procedures, yet keep human operators informed of execution, will be essential in future long-duration missions where the onboard crew will be solely responsible for spacecraft monitoring and control.