Search NASA⌕ Search

SEARCH · Search NASA

Results for “Spacecraft Operations”

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 217 records · Page 12

The MSFC Solar Activity Future Estimation (MSAFE) Model

The Natural Environments Branch of the Engineering Directorate at Marshall Space Flight Center (MSFC) provides solar cycle forecasts for NASA space flight programs and the aerospace community. These forecasts provide future statistical estimates of sunspot number, solar radio 10.7 cm flux (F10.7), and the geomagnetic planetary index, Ap, for input to various space environment models. For example, many thermosphere density computer models used in spacecraft operations, orbital lifetime analysis, and the planning of future spacecraft missions require as inputs the F10.7 and Ap. The solar forecast is updated each month by executing MSAFE using historical and the latest month's observed solar indices to provide estimates for the balance of the current solar cycle. The forecasted solar indices represent the 13-month smoothed values consisting of a best estimate value stated as a 50 percentile value along with approximate +/- 2 sigma values stated as 95 and 5 percentile statistical values. This presentation will give an overview of the MSAFE model and the forecast for the current solar cycle.

Suggs, Ron↗

Method and Apparatus for Spacecraft Gyroscope Scale Factor Calibration

A method and apparatus for estimating gyro scale factor during normal spacecraft operations, using small attitude motions that are compliant with mission pointing accuracy and stability requirements and a signal processing method that specifically detects the intentionally induced motions. This process increases operational availability by avoiding the need to take the spacecraft offline for large calibration maneuvers.

Reth, Alan D↗

Nickel cadmium battery operations on-orbit: Trials, tribulations, and success on the Upper Atmosphere Research Satellite

The Upper Atmosphere Research Satellite (UARS), designed, built, integrated, tested, and operated by NASA and Martin Marietta is a low-Earth orbiting, Earth-observing spacecraft which was launched via Space Shuttle Discovery on September 12, 1991 and deployed three days later. The Modular Power Subsystem (MPS) onboard the satellite is equipped with three NASA Standard 50 Ampere-hour (Ah) nickel-cadmium (NiCd) batteries. McDonnell Douglas Electronics Systems Company fabricated the MPS, and batteries from Gates Aerospace Batteries cells. Nominal battery performance was achieved for the first four months of spacecraft operation. First evidence of anomalous battery performance was observed in January 1992, after the first maximum beta angle (low Depth of Discharge) period. Since then, the Flight Operations Team (FOT), under the direction of Goddard Space Flight Center's UARS Project and Space Power Application Branch, has monitored and managed battery performance by adjusting solar array offset angle, conducting periodic deep discharge, and controlling battery recharge ratio. This paper covers a brief overview of the UARS, the FOT's operational battery management, and the observed spacecraft battery performance.

Rao, Gopalakrishna M.↗

Multi-User Space Link Extension (SLE) System

The Multi-User Space (MUS) Link Extension system, a software and data system, provides Space Link Extension (SLE) users with three space data transfer services in timely, complete, and offline modes as applicable according to standards defined by the Consultative Committee for Space Data Systems (CCSDS). MUS radically reduces the schedule, cost, and risk of implementing a new SLE user system, minimizes operating costs with a lights-out approach to SLE, and is designed to require no sustaining engineering expense during its lifetime unless changes in the CCSDS SLE standards, combined with new provider implementations, force changes. No software modification to MUS needs to be made to support a new mission. Any systems engineer with Linux experience can begin testing SLE user service instances with MUS starting from a personal computer (PC) within five days. For flight operators, MUS provides a familiar-looking Web page for entering SLE configuration data received from SLE. Operators can also use the Web page to back up a space mission's entire set of up to approximately 500 SLE service instances in less than five seconds, or to restore or transfer from another system the same amount of data from a MUS backup file in about the same amount of time. Missions operate each MUS SLE service instance independently by sending it MUS directives, which are legible, plain ASCII strings. MUS directives are usually (but not necessarily) sent through a TCP-IP (Transmission Control Protocol Internet Protocol) socket from a MOC (Mission Operations Center) or POCC (Payload Operations Control Center) system, under scripted control, during "lights-out" spacecraft operation. MUS permits the flight operations team to configure independently each of its data interfaces; not only commands and telemetry, but also MUS status messages to the MOC. Interfaces can use single- or multiple-client TCP/IP server sockets, TCP/IP client sockets, temporary disk files, the system log, or standard in, standard out, or standard error as applicable. By defining MUS templates in ASCII, the flight operations team can include any MUS system variable in telemetry or command headers or footers, and/or in status messages. Data fields can be arranged within messages in different sequences, according to the mission s needs. The only constraints imposed are on the format of MUS directive strings, and some bare minimum logical requirements that must be met in order for MUS to read the mission control center's spacecraft command inputs. The MUS system imposes no limits or constraints on the numbers and combinations of missions and SLE service instances that it will support simultaneously. At any time, flight operators may add, change, delete, bind, connect, or disconnect.

Perkins, Toby↗

Key Differences in Operating a Rover on the Moon vs. Mars

The command and control model for spacecraft operations, as well as the distribution of tasks between ground assets and in space assets, whether with a crew or solely robotic, is fundamentally constrained by the round trip light time between the space asset and the control facility (presumably on Earth, though not required). For an asset on Mars, the round trip light time varies, from roughly fourteen minutes to up to forty minutes. For a Lunar asset the round-trip light time is measured in only a few seconds, but current communications systems may more than double the latency with system overhead. For a Lunar Asset the total command latency may range from six seconds to more than forty, depending on communications overhead and data rates. Further, these variables are not always predictable, thus complicating operations. There are several differentiating factors for Lunar vs. Mars operations, Round trip light time/Atmosphere/Lighting and ShadowsTerrain type and knowledge/Round trip light time has implications for the distribution of tasks between ground and in space assets. Even at Lunar Distances, the combination of round trip light time plus communications systems overhead does not enable joy stick driving of a rover. The best that can be done, if driving from Earth, is near real time command and control. By 2030, driving from in space may be possible. Productivity on Mars requires either long operational sequences of commands, as is done for current rovers such as Curiosity, significant autonomous capability or, as may be possible by 2030, command and control support from space. Another implication of the long round trip light time from Earth to Mars, is that flight software functions must be resident on the in space asset. On the Moon, there is considerably more flexibility, enabling processing functions, to be resident on Earth or in space. This provides the opportunity to take advantage of the considerable processing power available on the ground, but may be constrained by data rates. On the Moon, for practical operational purposes, there is no atmosphere. Hence there is no scattering of light in the shadows. This has implications for image interpretation and driving near the poles. The Moon has permanently shadowed regions (PSR), unique terrain with unknown surface properties. With no scattering of light in shadows, driving on the Moon, particularly at the poles, where we have strong evidence of water, may prove to be hazardous and complex, requiring non-optical sensors, such as LIDAR.

Trimble, Jay↗

A Virtual Mission Operations Center - Collaborative Environment

Development of technologies that enable significant reductions in the cost of space mission operations is critical if constellations, formations, federations and sensor webs, are to be economically feasible. One approach to cost reduction is to infuse automation technologies into mission operations centers so that fewer personnel are needed for mission support. But missions are more culturally and politically adverse to the risks of automation. Reducing the mission risk associated with increased use of automation within a MOC is therefore of great importance. The belief that mission risk increases as more automation is used stems from the fact that there is inherently less direct human oversight to investigate and resolve anomalies in an unattended MOC. The Virtual Missions Operations Center - Collaborative Environment (VMOC-CE) project was launched to address this concern. The goal of the VMOC-CE project is to identify, develop, and infuse technology to enable mission operations between onsite operators and on-call personnel in geographically dispersed locations. VMOC-CE enables missions to more readily adopt automation because off-site operators and engineers can more easily identify, investigate, and resolve anomalies without having to be present in the MOC. The VMOC-CE intent is to have a single access point for all resources used in a collaborative mission operations environment. Team members will be able to interact during spacecraft operations, specifically for resolving anomalies, utilizing a desktop computer and the Internet. Mission operations management can use the VMOC-CE as a tool to participate in and monitor status of anomaly resolution or other mission operations issues. In this paper we present the VMOC-CE project, system capabilities and technologies, operations concept, and results of its pilot in support of the Earth Science Mission Operations System (ESMOS).

Medina, Barbara↗

Cryogenic Electronics Being Developed for Space Operation

Planetary exploration missions and deep space probes require electrical power management and control systems that can operate efficiently and reliably in very low temperature environments. Presently, spacecraft operating in the cold environment of deep space carry a large number of radioisotope heating units to maintain the surrounding temperature of the onboard electronics at approximately 20 C. Electronics capable of operation at cryogenic temperatures would not only tolerate the hostile environment of deep space but also reduce system size and weight by eliminating or reducing the radioisotope heating units and their associate structures. Thereby, such electronics would reduce system development as well as launch costs. In addition, power electronic circuits designed for operation at low temperatures are expected to result in more efficient systems than those at room temperature. This improvement results because semiconductor and dielectric materials have better behavior and tolerance in their electrical and thermal properties at low temperatures. The Low Temperature Electronics Program at the NASA Glenn Research Center is focusing on the research and development of electrical components, circuits, and systems suitable for applications in the aerospace environment and in deep space exploration missions. Research is being conducted on devices and systems for reliable use down to cryogenic temperatures. Some of the commercial off-the-shelf as well as developed components that are being characterized include semiconductor switching devices, resistors, magnetics, and capacitors. Semiconductor devices and integrated circuits including digital-to-analog and analog-to-digital converters, dc-dc converters, operational amplifiers, and oscillators are also being investigated for potential use in low-temperature applications. For example, the output response of an advanced oscillator at room temperature and at -190 C is shown. Most oscillators can operate at temperatures down to only -55 C. It can be seen that, for this oscillator, the low temperature of -196 C changed the leading and trailing edges of the oscillator pulses by producing overshoot. The research and development efforts performed under the Low Temperature Electronics Program at Glenn are being carried out through collaboration with other Government agencies, industrial and aerospace companies, and academia. The program supports missions as well as technology development efforts at NASA's Goddard Space Flight Center and Langley Research Center, and the Jet Propulsion Laboratory.

Patterson, Richard L.↗

Beyond Control Centers

For NASA's Resource Prospector (RP) Lunar Rover Mission, we are moving away from a control center concept, to a fully distributed operation utilizing control nodes, with decision support from anywhere via mobile devices. This operations concept will utilize distributed information systems, notifications, mobile data access, and optimized mobile data display for off-console decision support. We see this concept of operations as a step in the evolution of mission operations from a central control center concept to a mission operations anywhere concept. The RP example is part of a trend, in which mission expertise for design, development and operations is distributed across countries and across the globe. Future spacecraft operations will be most cost efficient and flexible by following this distributed expertise, enabling operations from anywhere. For the RP mission we arrived at the decision to utilize a fully distributed operations team, where everyone operates from their home institution, based on evaluating the following factors: the requirement for physical proximity for near-real time command and control decisions; the cost of distributed control nodes vs. a centralized control center; the impact on training and mission preparation of flying the team to a central location. Physical proximity for operational decisions is seldom required, though certain categories of decisions, such as launch abort, or close coordination for mission or safety-critical near-real-time command and control decisions may benefit from co-location. The cost of facilities and operational infrastructure has not been found to be a driving factor for location in our studies. Mission training and preparation benefit from having all operators train and operate from home institutions.

Operations↗

An expert system for diagnosing anomalies of spacecraft

Although the analysis of anomalous behavior of satellites is difficult because it is a very complex process, it is important to be able to make an accurate assessment in a timely manner when the anomaly is observed. Spacecraft operators may have to take corrective action or to 'safe' the spacecraft; space-environment forecasters may have to assess the environmental situation and issue warnings and alerts regarding hazardous conditions, and scientists and engineers may want to gain knowledge for future designs to mitigate the problems. Anomalies can be hardware problems, software errors, environmentally induced, or even the cause of workmanship. Spacecraft anomalies attributable to electrostatic discharges have been known to cause command errors. A goal is to develop an automated system based on this concept to reduce the number of personnel required to operate large programs or missions such as Hubble Space Telescope (HST) and Mission to Planet Earth (MTPE). Although expert systems to detect anomalous behavior of satellites during operations are established, diagnosis of the anomaly is a complex procedure and is a new development.

Lauriente, Michael↗

Case Studies in Verifying Spacecraft Autonomy

Spacecraft, operating with a time-to-effect faster than human command response, or with absent or delayed communication, have depended on autonomy. It is likely that this reliance will continue, and increase further in future missions. Spacecraft autonomy is used when operator intervention is not available or feasible, or when dynamic aspects of a spacecraft situation cannot be predicted in advance. This paper provides case studies of several successfully verified autonomous software systems across multiple spacecraft, flight phases (launch, transit, entry and landing, science utilization), and software classifications, and can serve as examples to future missions in methods of successfully assuring spacecraft autonomy.

Johnson, Stephen B.↗

The NASA Mission Operations and Control Architecture Program

The conflict between increases in space mission complexity and rapidly declining space mission budgets has created strong pressures to radically reduce the costs of designing and operating spacecraft. A key approach to achieving such reductions is through reducing the development and operations costs of the supporting mission operations systems. One of the efforts which the Communications and Data Systems Division at NASA Headquarters is using to meet this challenge is the Mission Operations Control Architecture (MOCA) project. Technical direction of this effort has been delegated to the Mission Operations Division (MOD) of the Goddard Space Flight Center (GSFC). MOCA is to develop a mission control and data acquisition architecture, and supporting standards, to guide the development of future spacecraft and mission control facilities at GSFC. The architecture will reduce the need for around-the-clock operations staffing, obtain a high level of reuse of flight and ground software elements from mission to mission, and increase overall system flexibility by enabling the migration of appropriate functions from the ground to the spacecraft. The end results are to be an established way of designing the spacecraft-ground system interface for GSFC's in-house developed spacecraft, and a specification of the end to end spacecraft control process, including data structures, interfaces, and protocols, suitable for inclusion in solicitation documents for future flight spacecraft. A flight software kernel may be developed and maintained in a condition that it can be offered as Government Furnished Equipment in solicitations. This paper describes the MOCA project, its current status, and the results to date.

Ondrus, Paul J.↗

Influence of charging environments on spacecraft materials and system performance

An overview is presented of potential interactions that can occur on spacecraft operating in space environments. These interactions are discussed in detail. The environment acts on spacecraft in such a way that charging of exterior surfaces occurs. The consequences from this charging then affect system operational performance. Hence, it is the coupling of this exterior charging to system performance that is of concern here. These interactions were first discovered in the spacecraft charging phenomena in which the geomagnetic substorms charged external surfaces to a level that discharges occurred. As a result of the discharge, electronic systems either changed logic state (anomalous switching) or failed. These interactions can occur in all orbits. The type associated with geosynchronous orbits is called passive since the environment provides the charging mechanism. This type can also occur in polar orbits due to auroral charging environments. In low Earth orbits, the thermal plasma alleviates charging environment concerns, but system operations can induce similar effects.

Stevens, N. John↗

Engineering Analysis Subsystem Environment for Spacecraft Engineering Subsystem Mission Operations

The Engineering Analysis Subsystem Environment (EASE) prototype is a collection of computer programs on networked workstations providing a multimission, multisubsystem environment that enables the operation of several spacecraft simultaneously with fewer analysts. Through the use of automated tools, graphical data visualization and information management, EASE has achieved an increase in mission operations productivity. Recently, a database, a trending tool, and a power sequence expansion tool have been added to EASE. This paper discusses these enhancements and provides an update of the operation experience with the realtime Galileo telemetry data.

EASE↗

LWS/SET End-to-End Data System

This paper describes the concept for the End-to-End Data System that will support NASA's Living With a Star Space Environment Testbed missions. NASA has initiated the Living With a Star (LWS) Program to develop a better scientific understanding to address the aspects of the connected Sun-Earth system that affect life and society. A principal goal of the program is to bridge the gap.between science, engineering, and user application communities. The Space Environment Testbed (SET) Project is one element of LWS. The Project will enable future science, operational, and commercial objectives in space and atmospheric environments by improving engineering approaches to the accommodation and/or mitigation of the effects of solar variability on technological systems. The End-to-end data system allows investigators to access the SET control center, command their experiments, and receive data from their experiments back at their home facility, using the Internet. The logical functioning of major components of the end-to-end data system are described, including the GSFC Payload Operations Control Center (POCC), SET Payloads, the GSFC SET Simulation Lab, SET Experiment PI Facilities, and Host Systems. Host Spacecraft Operations Control Centers (SOCC) and the Host Spacecraft are essential links in the end-to-end data system, but are not directly under the control of the SET Project. Formal interfaces will be established between these entities and elements of the SET Project. The paper describes data flow through the system, from PI facilities connecting to the SET operations center via the Internet, communications to SET carriers and experiments via host systems, to telemetry returns to investigators from their flight experiments. It also outlines the techniques that will be used to meet mission requirements, while holding development and operational costs to a minimum. Additional information is included in the original extended abstract.

Giffin, Geoff↗

A Technique for the Assessment of Flight Operability Characteristics of Human Rated Spacecraft

In support of new human rated spacecraft development programs, the Mission Operations Directorate at NASA Johnson Space Center has implemented a formal method for the assessment of spacecraft operability. This "Spacecraft Flight Operability Assessment Scale" defines six key themes of flight operability, with guiding principles and goals stated for each factor. A standardized rating technique provides feedback that is useful to the operations, design and program management communities. Applicability of this concept across the program structure and life cycle is addressed. Examples of operationally desirable and undesirable spacecraft design characteristics are provided, as is a sample of the assessment scale product.

Crocker, Alan↗

Pump for delivering heated fluids

A thermomechanical pump particularly suited for use in pumping a warming fluid obtained from an RTG (Radioisotope Thermal Generator) through science and flight instrumentation aboard operative spacecraft is described. The invention is characterized by a pair of operatively related cylinders, each including a reciprocating piston head dividing the cylinder into a pressure chamber confining therein a vaporizable fluid, and a pumping chamber for propelling the warming fluid, and a fluid delivery circuit for alternately delivering the warming fluid from the RTG through the pressure chamber of one cylinder to the pumping chamber of the other cylinder, whereby the vaporizable fluid within the pair of pressure chambers alternately is vaporized and condensed for driving the associated pistons in pumping and intake strokes.

Sabelman, E. E.↗

The NASA CSTI high capacity power project

The SP-100 Space Nuclear Power Program was established in 1983 by DOD, DOE, and NASA as a joint program to develop technology for military and civil applications. Starting in 1986, NASA has funded a technology program to maintain the momentum of promising aerospace technology advancement started during Phase 1 of SP-100 and to strengthen, in key areas, the chances for successful development and growth capability of space nuclear reactor power systems for a wide range of future space applications. The elements of the Civilian Space Technology Initiative (CSTI) High Capacity Power Project include Systems Analysis, Stirling Power Conversion, Thermoelectric Power Conversion, Thermal Management, Power Management, Systems Diagnostics, Environmental Interactions, and Material/Structural Development. Technology advancement in all elements is required to provide the growth capability, high reliability and 7 to 10 year lifetime demanded for future space nuclear power systems. The overall project will develop and demonstrate the technology base required to provide a wide range of modular power systems compatible with the SP-100 reactor which facilitates operation during lunar and planetary day/night cycles as well as allowing spacecraft operation at any attitude or distance from the sun. Significant accomplishments in all of the project elements will be presented, along with revised goals and project timelines recently developed.

Winter, J.↗