Search NASA⌕ Search

SEARCH · Search NASA

Results for “Spacecraft Automation”

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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRS1997

Comparative Soot Diagnostics: Preliminary Results

The motivation for the Comparative Soot Diagnostics (CSD) experiment lies in the broad practical importance of understanding combustion generated particulate. Depending upon the circumstances, particulate matter can affect the durability and performance of combustion equipment, can be a pollutant, can be used to detect fires and, in the form of soot, can be the dominant source of radiant energy from flames. The nonbuoyant structure of most flames of practical interest makes understanding of soot processes in low gravity flames important to our ability to predict fire behavior on earth. These studies also have direct applications to fire safety in human-crew spacecraft, since smoke is the indicator used for automated detection in current spacecraft. In the earliest missions (Mercury, Gemini and Apollo), the crew quarters were so cramped that it was considered reasonable that the astronauts would rapidly detect any fire. The Skylab module, however, included approximately 20 UV-sensing fire detectors. The Space Shuttle has 9 particle-ionization smoke detectors in the mid-deck and flight deck and Spacelab has six additional particle-ionization smoke detectors. The designated detectors for the ISS are laser-diode, forward-scattering, smoke or particulate detectors. Current plans for the ISS call for two detectors in the open area of the module, and detectors in racks that have both cooling air flow and electrical power. Due to the complete absence of data concerning the nature of particulate and radiant emission from incipient and fully developed low-g fires, all three of these detector systems were designed based upon l-g test data and experience. As planned mission durations and complexity increase and the volume of spacecraft increases, the need for and importance of effective, crew-independent, fire detection grows significantly. To provide this level of protection, more knowledge is needed concerning low-gravity fire phenomena and, in particular, how they might be detected and suppressed. Prior to CSD, no combustion-generated particulate samples had been collected near the flame zone for well-developed microgravity flames. All of the extant data either came from drop tower tests and therefore only corresponded to the early stages of a fire or were collected far from the flame zone. The fuel sources in the drop tower tests were restricted to laminar gas-jet diffusion flames and very rapidly overheated wire insulation. The gas-jet tests indicated, through thermophoretic sampling, (2) that soot primaries and aggregates (groups of primary particles) in low-gravity may be significantly larger than those in normal gravity (1-g). This raises new scientific questions about soot processes as well as practical issues for particulate size sensitivity and detection alarm threshold levels used in on-orbit smoke detectors. Preliminary tests in the 2.2 second drop tower suggest that particulate generated by overheated wire insulation may be larger in low-g than in 1-g. Transmission Electron Microscope (TEM) grids downstream of the fire region in the Wire Insulation Flammability experiment as well as visual observation of long string-like aggregates, further confirm this suggestion. The combined impact of these limited results and theoretical predictions is that, as opposed to extrapolation from l-g data, direct knowledge of low-g combustion particulate is needed for more confident design of smoke detectors for spacecraft. This paper describes the operation and preliminary results of the CSD, a project conceived and developed at NASA Lewis Research Center. The CSD flight experiment was conducted in the Middeck Glovebox Facility (MGBX) on USMP-3. The project is support by NASA Headquarters Microgravity Science and Applications Division and Code Q. The results presented here are from the microgravity portion of the experiment, including the temporal response of the detectors and average sizes of the primary and aggregate particles captured on the thermophoretic probes.

Urban, David L.↗
NASA NTRS1998

Comparative Soot Diagnostics: 1 Year Report

The motivation for the Comparative Soot Diagnostics (CSD) experiment lies in the broad practical importance of understanding combustion generated particulate. Depending upon the circumstances, particulate matter can affect the durability and performance of combustion equipment, can be a pollutant, can be used to detect fires and, in the form of soot, can be the dominant source of radiant energy from flames. Bright sooty fires are desirable for efficient energy extraction in furnaces and power equipment. In contrast, soot-enhanced radiation is undesirable in many propulsion systems (e.g. jet engines). The non-buoyant structure of most flames of practical interest (turbulent) makes understanding of soot processes in low gravity flames important to our ability to predict fire behavior on earth. These studies also have direct applications to fire safety in human-crew spacecraft, since smoke is the indicator used for automated detection in current spacecraft. In addition, recent tests conducted on MIR showed that a candle in a truly quiescent spacecraft environment can burn for tens of minutes. Consequently, this test and many earlier tests have demonstrated that fires in spacecraft can be considered a credible risk. In anticipation of this risk, NASA has included fire detectors on Skylab, smoke detectors on the Space Shuttle (STS), and smoke detectors in the design for the International Space Station (ISS). In the CSD experiment, these smoke detectors were tested using, quasi-steady, low-gravity, particulate generating materials. Samples of the particulate were also obtained from these low-gravity sources. This experiment provides the first such measurements aimed toward understanding of soot processes here on earth and for the testing and design of advanced spacecraft smoke detection systems. This paper describes the operation and preliminary results of the CSD experiment which was was conducted in the Middeck Glovebox Facility (MGBX) on USMP-3. The objectives of CSD are to examine the particulate emission from a variety of pyrolyzing and combusting sources and to quantify the performance of several particulate-sensing diagnostic techniques. This paper presents the results of the microgravity portion of the CSD experiment. The results include the temporal response of the detectors and average sizes of the primary and aggregate particles captured on the thermophoretic probes. Complete assessment of the microgravity data and its combination with the normal-gravity data are still in process.

Urban, David L.↗
NASA NTRS2014

Automating the SMAP Ground Data System to Support Lights-Out Operations

The Soil Moisture Active Passive (SMAP) Mission is a first tier mission in NASA's Earth Science Decadal Survey. SMAP will provide a global mapping of soil moisture and its freeze/thaw states. This mapping will be used to enhance the understanding of processes that link the terrestrial water, energy, and carbon cycles, and to enhance weather and forecast capabilities. NASA's Jet Propulsion Laboratory has been selected as the lead center for the development and operation of SMAP. The Jet Propulsion Laboratory (JPL) has an extensive history of successful deep space exploration. JPL missions have typically been large scale Class A missions with significant budget and staffing. SMAP represents a new area of JPL focus towards low cost Earth science missions. Success in this new area requires changes to the way that JPL has traditionally provided the Mission Operations System (MOS)/Ground Data System (GDS) functions. The operation of SMAP requires more routine operations activities and support for higher data rates and data volumes than have been achieved in the past. These activities must be addressed by a reduced operations team and support staff. To meet this challenge, the SMAP ground data system provides automation that will perform unattended operations, including automated commanding of the SMAP spacecraft.

GDS↗
NASA NTRS2000

Iterative Repair Planning for Spacecraft Operations Using the Aspen System

This paper describes the Automated Scheduling and Planning Environment (ASPEN). ASPEN encodes complex spacecraft knowledge of operability constraints, flight rules, spacecraft hardware, science experiments and operations procedures to allow for automated generation of low level spacecraft sequences. Using a technique called iterative repair, ASPEN classifies constraint violations (i.e., conflicts) and attempts to repair each by performing a planning or scheduling operation. It must reason about which conflict to resolve first and what repair method to try for the given conflict. ASPEN is currently being utilized in the development of automated planner/scheduler systems for several spacecraft, including the UFO-1 naval communications satellite and the Citizen Explorer (CX1) satellite, as well as for planetary rover operations and antenna ground systems automation. This paper focuses on the algorithm and search strategies employed by ASPEN to resolve spacecraft operations constraints, as well as the data structures for representing these constraints.

Rabideau, G.↗
NASA NTRS2001

Satellite Ground Operations Automation: Lessons Learned and Future Approaches

Reducing spacecraft ground system operations costs is a major goal in all missions. The Fast Auroral Snapshot (FAST) flight operations team at the NASA/Goddard Spacecraft Flight Center developed in-house scripts and procedures to automate monitoring of critical spacecraft functions. The initial staffing profile of 16x7 was reduced first to 8x5 and then to 'lights out'. Operations functions became an offline review of system performance and the generation of future science plans for subsequent upload to the spacecraft. Lessons learned will be applied to the challenging Triana mission, where 24x7 contact with the spacecraft will be necessary at all times.

Catena, John↗
NASA NTRS1990

Development of an automated electrical power subsystem testbed for large spacecraft

The NASA Marshall Space Flight Center (MSFC) has developed two autonomous electrical power system breadboards. The first breadboard, the autonomously managed power system (AMPS), is a two power channel system featuring energy generation and storage and 24-kW of switchable loads, all under computer control. The second breadboard, the space station module/power management and distribution (SSM/PMAD) testbed, is a two-bus 120-Vdc model of the Space Station power subsystem featuring smart switchgear and multiple knowledge-based control systems. NASA/MSFC is combining these two breadboards to form a complete autonomous source-to-load power system called the large autonomous spacecraft electrical power system (LASEPS). LASEPS is a high-power, intelligent, physical electrical power system testbed which can be used to derive and test new power system control techniques, new power switching components, and new energy storage elements in a more accurate and realistic fashion. LASEPS has the potential to be interfaced with other spacecraft subsystem breadboards in order to simulate an entire space vehicle. The two individual systems, the combined systems (hardware and software), and the current and future uses of LASEPS are described.

Hall, David K.↗
NASA NTRS1996

Autonomous Spacecraft Guidance and Control

By the next decade, spacecraft will be highly miniaturized and automated to realize much lower life-cycle costs in comparison to todays counterparts. These small spacecraft will have highly autonomous control systems for spacecraft attitude, maneuver, and orbit control.

small↗
NASA NTRS2016

Transitioning Autonomous Systems Technology Research to a Flight Software Environment

NASA has developed methods and algorithms for autonomous spacecraft operations,including automated planning and scheduling, fault diagnostics and impact determination,procedure management and display. Making the transition from technology research tooperational flight software requires overcoming significant technical, programmatic andcultural challenges. Technology research is aimed at developing methods that performspecific functions correctly, but the resulting software may not be designed for flightprocessors with limited CPU, memory and network resources, and may not be easilyintegrated into spacecraft flight software. Our objective in the Autonomous Systems andOperations Project is to make significant strides toward the transformation from technologyto operational use. Our focus was twofold: maturing research grade autonomy software intoa flight software environment using broadly accepted languages and tools; and integratingautonomy applications with each other and with representative systems and their data andcommand interfaces. For a target flight software environment, we chose Core FlightSoftware, developed by Goddard Space Flight Center as a common operating systemindependent framework. Our hardware integration environment was provided by theIntegrated Power and Avionics Systems (iPAS) Lab at Johnson Space Center, in whichvarious subsystem development has been conducted to address engineering challenges forthe vehicles and systems required for long-duration missions into the solar system. The iPASand its network of connected facilities provides realistic subsystem hardware or simulationsof spacecraft power, life support, guidance, navigation and control, and command and datahandling subsystems. Interfaces between autonomy applications and the subsystems beingassessed and controlled were developed, assessed and refined. The hardware and softwareenvironment using CFS and the iPAS facility has proven to be a highly flexible and realisticenvironment in which to rapidly integrate applications in an iterative, low cost setting. Usingthe integration environment we have developed, we will turn our focus to performance andsizing analysis to determine the computational requirements for full-scale deployment ofautonomy technology. Scalability of reasoners and the spacecraft models upon which theyoperate, and robustness across the full range of spacecraft conditions and environments willbe explored and improved. We are making significant contributions to the future programsthat will build the spacecraft that will take humans beyond the Earth-Moon system, in whichprogram Systems Engineers will be able to accurately and confidently design in accurate,robust and mature autonomous operations systems.

Flight Software↗
NASA NTRS1990

Monitoring and control of spacecraft systems using procedural reasoning

Research concerned with automating the monitoring and control of spacecraft systems is discussed. In particular, the application of SRI's Procedural Reasoning System (PRS) to the handling of malfunctions in the Reaction Control System (RCS) of NASA's Space Shuttle is examined. Unlike traditional monitoring and control systems, PRS is able to reason about and perform complex tasks in a very flexible and robust manner, somewhat in the manner of a human assistant. Using various RCS malfunctions as examples (including sensor faults, leaking components, multiple alarms, and regulator and jet failures), it is shown how PRS manages to combine both goal-directed reasoning and the ability to react rapidly to unanticipated changes in its environment. In conclusion, some important issues in the design of PRS are reviewed and future enhancements are indicated.

Georgeff, Michael P.↗
NASA NTRS2008

Integrated Docking Simulation and Testing with the Johnson Space Center Six-Degree of Freedom Dynamic Test System

The Exploration Systems Architecture defines missions that require rendezvous, proximity operations, and docking (RPOD) of two spacecraft both in Low Earth Orbit (LEO) and in Low Lunar Orbit (LLO). Uncrewed spacecraft must perform automated and/or autonomous rendezvous, proximity operations and docking operations (commonly known as Automated Rendezvous and Docking, AR&D). The crewed versions may also perform AR&D, possibly with a different level of automation and/or autonomy, and must also provide the crew with relative navigation information for manual piloting. The capabilities of the RPOD sensors are critical to the success of the Constellation Program; this is carried as one of the CEV Project top risks. The Exploration Technology Development Program (ETDP) AR&D Sensor Technology Project seeks to reduce this risk by increasing technology maturation of selected relative navigation sensor technologies through testing and simulation. One of the project activities is a series of "pathfinder" testing and simulation activities to integrate relative navigation sensors with the Johnson Space Center Six-Degree-of-Freedom Test System (SDTS). The SDTS will be the primary testing location for the Orion spacecraft s Low Impact Docking System (LIDS). Project team members have integrated the Orion simulation with the SDTS computer system so that real-time closed loop testing can be performed with relative navigation sensors and the docking system in the loop during docking and undocking scenarios. Two relative navigation sensors are being used as part of a "pathfinder" activity in order to pave the way for future testing with the actual Orion sensors. This paper describes the test configuration and test results.

Mitchell, Jennifer D.↗
NASA NTRS2008

Re-Engineering the Tropical Rainfall Measuring Mission (TRMM) Satellite Utilizing Goddard Space Flight Center (GSFC) Mission Services Center (GMSEC) Middleware Based Technology to Enable Lights Out Operations and Autonomous Re-Dump of Lost Telemetry Data

The Tropical Rainfall Measuring Mission (TRMM) spacecraft was launched in November of 1996 in order to obtain unique three dimensional radar cross sectional observations of cloud structures with particular interest in hurricanes. The TRMM mission life was recently extended with current estimates that operations will continue through the 2012-2013 timeframe. Faced with this extended mission profile, the project has embarked on a technology refresh and re-engineering effort. TRMM has recently implemented a re-engineering effort to expand a middleware based messaging architecture to enable fully redundant lights-out of flight operations activities. The middleware approach is based on the Goddard Mission Services Evolution Center (GMSEC) architecture, tools and associated open-source Applications Programming Interface (API). Middleware based messaging systems are useful in spacecraft operations and automation systems because private node based knowledge (such as that within a telemetry and command system) can be broadcast on the middleware messaging bus and hence enable collaborative decisions to be made by multiple subsystems. In this fashion, private data is made public and distributed within the local area network and multiple nodes can remain synchronized with other nodes. This concept is useful in a fully redundant architecture whereby one node is monitoring the processing of the 'prime' node so that in the event of a failure the backup node can assume operations of the prime, without loss of state knowledge. This paper will review and present the experiences, architecture, approach and lessons learned of the TRMM re-engineering effort centered on the GMSEC middleware architecture and tool suite. Relevant information will be presented that relates to the dual redundant parallel nature of the Telemetry and Command (T and C) and Front-End systems and how these systems can interact over a middleware bus to achieve autonomous operations including autonomous commanding to recover missing science data during the same spacecraft contact.

Marius, Julio L.↗
NASA NTRS1996

Analysis of Apollo 8 Photography and Visual Observations

Apollo 8 was launched from Cape Kennedy, Fla., at 7 :50 a.m., e.s.t., on December 21, 1968. Two hours 50 minutes later, translunar injection was performed; and astronauts Col. Frank Borman, the commander; Capt. James A. Lovell, Jr., the command module pilot; and Maj. (now Lt. Col.) William A. Anders, the lunar module pilot, were on their way to the Moon. The spacecraft was placed in an elliptical lunar orbit at 69 hours 8 minutes after liftoff. After flying two elliptical orbits of 168.5 by 60 nautical miles with an inclination of 12° to the Equator, the spacecraft was placed in a nearly circular orbit of 59.7 by 60.7 nautical miles, in which it remained for eight orbits. At 89 hours 19 minutes, trans earth injection was performed from behind the Moon. A nearly flawless mission was completed on the morning of December 27 when splashdown occurred in the Pacific Ocean after a total elapsed time of 147 hours. Lt. Gen. Sam C. Phillips, the Director of the Apollo Program, announced that such a mission was being considered at a press conference on August 19, 1968. Formal announcement that NASA was preparing Apollo 8 for an orbital flight around the Moon was released to the press on November 12, 1968. The primary purpose of this mission was to further progress toward the goal of landing men on the Moon by gaining operational experience and testing the Apolio systems. However, a great effort was also made to accomplish worthwhile scientific tasks with photography and visual observations by the astronauts. In planning the scientific tasks to be attempted on this mission, it was obvious that one of the prime tasks should be photography of the lunar surface. Such photography would furnish valuable information on the following : 1. Approach topography and landmarks for the early Apollo landings 2. The scientific merit and the roughness of areas for possible follow-on Apollo landings 3. The broad structure and characteristics of the lunar surface During the orbital part of the mission, a major portion of the lunar far side would be in sunlight. Although almost all of the far side of the Moon has been photographed by the automated Lunar Orbiter spacecraft, the photography generally was made with the spacecraft relatively far from the Moon, limiting the Lunar Orbiter photographs to an average resolution of approximately 100 meters. Thus, Apollo photographs of the far side would have much better resolution than existing pictures. Finally, it was recognized that contamination, both as it relates to window fogging (which did occur) and to contamination clouds around t he spacecraft, should be studied for both scientific and operational interests.

Richard J. Allenby↗
NASA NTRS1986

Unattended deep space station tracking station development: Monitor and control technology

The major developments leading to successful demonstration of fully unattended operation of a Deep Space Network (DSN) station (DSS 13) are reviewed. Unattended operation was demonstrated by reliably tracking, commanding, and delivering telemetry from the Pioneer 8 spacecraft. Transfer of automated monitor and control technology to DSN implementation is summarized, along with related accomplishments.

Foster, C.↗
NASA NTRS1986

The evolution of automation and robotics in manned spaceflight

The evolution of automation on all manned spacecraft including the Space Shuttle is reviewed, and a concept for increasing automation and robotics from the current Shuttle Remote Manipulator System (RMS) to an autonomous system is presented. The requirements for robotic elements are identified for various functions on the Space Station, including extravehicular functions and functions within laboratory and habitation modules which expand man's capacity in space and allow selected teleoperation from the ground. The initial Space Station will employ a telerobot and necessary knowledge based systems as an advisory to the crew on monitoring, fault diagnosis, and short term planning and scheduling.

Moser, T. L.↗
NASA NTRS1987

Man's role in space exploration and exploitation

The crew workloads on the Space Shuttle are described. The Space Shuttle is designed to minimize the activity of the crew in maintaining and operating the Shuttle in order for the crew to be involved in productive activities. The changing role of the crew due to the use of more automated systems on spacecraft is examined. The Shuttle flight system is dependent on embedded software, and the crew is to manage and support these systems. The primary functions of the Space Station are as a laboratory and for construction and assembly of systems, requiring EVA. Examples of EVA are presented. The correlation between manned and unmanned systems and the future direction of space research are discussed.

Loftus, Joseph P.↗
NASA NTRS1990

Solar array automation limitations

Significant progress in the automation of the spacecraft electrical power systems has been made within the past few years. This is especially important with the development of the space station and the increasing demand on the electrical power systems for future satellites. The key element of the spacecraft power system, the solar arrays which supply the power, will have to grow to supply many tens of kilowatts of power within the next twenty years. This growth will be accompanied by the problems associated with large distributed power systems. The growth of the arrays, the on-array management problems and potential solutions to array degradation or failure are discussed. Multilowatt arrays for unmanned spacecraft with comments on the implications of array degradation for manned spacecraft are discussed.

Trumble, Terry M.↗
NASA NTRS1993

Combining real-time monitoring and knowledge-based analysis in MARVEL

Real-time artificial intelligence is gaining increasing attention for applications in which conventional software methods are unable to meet technology needs. One such application area is the monitoring and analysis of complex systems. MARVEL, a distributed monitoring and analysis tool with multiple expert systems, was developed and successfully applied to the automation of interplanetary spacecraft operations at NASA's Jet Propulsion Laboratory. MARVEL implementation and verification approaches, the MARVEL architecture, and the specific benefits that were realized by using MARVEL in operations are described.

Schwuttke, Ursula M.↗