Search NASA⌕ Search

SEARCH · Search NASA

Results for “operations spacecraft control”

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 NTRS1994

Taking advantage of ground data systems attributes to achieve quality results in testing software

During the software development life cycle process, basic testing starts with the development team. At the end of the development process, an acceptance test is performed for the user to ensure that the deliverable is acceptable. Ideally, the delivery is an operational product with zero defects. However, the goal of zero defects is normally not achieved but is successful to various degrees. With the emphasis on building low cost ground support systems while maintaining a quality product, a key element in the test process is simulator capability. This paper reviews the Transportable Payload Operations Control Center (TPOCC) Advanced Spacecraft Simulator (TASS) test tool that is used in the acceptance test process for unmanned satellite operations control centers. The TASS is designed to support the development, test and operational environments of the Goddard Space Flight Center (GSFC) operations control centers. The TASS uses the same basic architecture as the operations control center. This architecture is characterized by its use of distributed processing, industry standards, commercial off-the-shelf (COTS) hardware and software components, and reusable software. The TASS uses much of the same TPOCC architecture and reusable software that the operations control center developer uses. The TASS also makes use of reusable simulator software in the mission specific versions of the TASS. Very little new software needs to be developed, mainly mission specific telemetry communication and command processing software. By taking advantage of the ground data system attributes, successful software reuse for operational systems provides the opportunity to extend the reuse concept into the test area. Consistency in test approach is a major step in achieving quality results.

Sigman, Clayton B.↗
NASA NTRS1981

Design and development of a six degree of freedom hand controller

The design objectives of a six degree of freedom manual controller are discussed with emphasis on a space environment. Details covered include problems associated with a zero-g environment, the need to accommodate both 'shirt sleeve' and space suited astronauts, the combination of both manipulator operation and spacecraft flight control in a single device, and to accommodate restraints in space. A variable configuration device designed as a development tool in which rotational axes can be moved relative to one another, is described and its limitations discussed. Two additional devices were developed for concept testing. Each device combines the need for good quality with its ability achieve a wide range of adjustments.

King, M. L.↗
NASA NTRS1972

Ultra-precise attitude test facility for flight spacecraft

A test facility was designed and built for conducting complete dynamic systems tests of the OAO spacecraft. The operating principle of the facility is illustrated for a single control axis. The test facility is described which was built and used to test the stabilization and control system of the OAO B spacecraft. Fine pointing of the spacecraft was demonstrated to better than 0.5 seconds of arc. Other spacecraft functions tested were gimbaled and boresight star tracker operations, coarse and fine slew maneuvers, inertial guidance operation, settling time of the spacecraft control system, and transfers between all modes of control.

Devine, E. J.↗
NASA NTRS2005

Mission Operations and Information Management Area Spacecraft Monitoring and Control Working Group

Working group goals for this year are: Goal 1. Due to many review comments the green books will be updated and available for re-review by CCSDS. Submission of green books to CCSDS for approval. Goal 2.Initial set of 4 new drafts of the red books as following: SM&C protocol: update with received comments. SM&C common services: update with received comments and expand the service specification. SM&C core services: update with received comments and expand the service the information model. SM&C time services: (target objective): produce initial draft following template of core services.

Lokerson, Donald C.↗
NASA NTRS1993

The Hubble Space Telescope fine guidance system operating in the coarse track pointing control mode

The Hubble Space Telescope (HST) Fine Guidance System has set new standards in pointing control capability for earth orbiting spacecraft. Two precision pointing control modes are implemented in the Fine Guidance System; one being a Coarse Track Mode which employs a pseudo-quadrature detector approach and the second being a Fine Mode which uses a two axis interferometer implementation. The Coarse Track Mode was designed to maintain FGS pointing error to within 20 milli-arc seconds (rms) when guiding on a 14.5 Mv star. The Fine Mode was designed to maintain FGS pointing error to less than 3 milli-arc seconds (rms). This paper addresses the HST FGS operating in the Coarse Track Mode. An overview of the implementation, the operation, and both the predicted and observed on orbit performance is presented. The discussion includes a review of the Fine Guidance System hardware which uses two beam steering Star Selector servos, four photon counting photomultiplier tube detectors, as well as a 24 bit microprocessor, which executes the control system firmware. Unanticipated spacecraft operational characteristics are discussed as they impact pointing performance. These include the influence of spherically aberrated star images as well as the mechanical shocks induced in the spacecraft during and following orbital day/night terminator crossings. Computer modeling of the Coarse Track Mode verifies the observed on orbit performance trends in the presence of these optical and mechanical disturbances. It is concluded that the coarse track pointing control function is performing as designed and is providing a robust pointing control capability for the Hubble Space Telescope.

Whittlesey, Richard↗
NASA NTRS2003

Pulsed Plasma Thruster (PPT) Technology: Earth Observing-1 PPT Operational and Advanced Components Being Developed

In 2002 the pulsed plasma thruster (PPT) mounted on the Earth Observing-1 spacecraft was operated successfully in orbit. The two-axis thruster system is fully incorporated in the attitude determination and control system and is being used to automatically counteract disturbances in the pitch axis of the spacecraft. The first tests conducted in space demonstrated the full range of PPT operation, followed by calibration of control torques from the PPT in the attitude control system. Then the spacecraft was placed in PPT control mode. To date, it has operated for about 30 hr. The PPT successfully controlled pitch momentum during wheel de-spin, solar array acceleration and deceleration during array rewind, and environmental torques in nominal operating conditions. Images collected with the Advanced Landsat Imager during PPT operation have demonstrated that there was no degradation in comparison to full momentum wheel control. In addition, other experiments have been performed to interrogate the effects of PPT operation on communication packages and light reflection from spacecraft surfaces. Future experiments will investigate the possibility of orbit-raising maneuvers, spacecraft roll, and concurrent operation with the Hyperion imager. Future applications envisioned for pulsed plasma thrusters include longer life, higher precision, multiaxis thruster configurations for three-axis attitude control systems or high-precision, formationflying systems. Advanced components, such as a "dry" mica-foil capacitor, a wear-resistant spark plug, and a multichannel power processing unit have been developed under contract with Unison Industries, General Dynamics, and C.U. Aerospace. Over the last year, evaluation tests have been conducted to determine power processing unit efficiency, atmospheric functionality, vacuum functionality, thruster performance evaluation, thermal performance, and component life.

Pencil, Eric J.↗
NASA NTRS2017

Systems Engineering Challenges for GSFC Space Science Mission Operations

The NASA Goddard Space Flight Center Space Science Mission Operations (SSMO) project currently manages19 missions for the NASA Science Mission Directorate, within the Planetary, Astrophysics, and Heliophysics Divisions. The mission lifespans range from just a few months to more than20 years. The WIND spacecraft, the oldest SSMO mission, was launched in 1994. SSMO spacecraft reside in low earth, geosynchronous,highly elliptical, libration point, lunar, heliocentric,and Martian orbits. SSMO spacecraft range in size from 125kg (Aeronomy of Ice in the Mesosphere (AIM)) to over 4000kg (Fermi Gamma-Ray Space Telescope (Fermi)). The attitude modes include both spin and three-axis stabilized, with varying requirements on pointing accuracy. The spacecraft are operated from control centers at Goddard and off-site control centers;the Lunar Reconnaissance Orbiter (LRO), the Solar Dynamics Observatory (SDO) and Magnetospheric MultiScale (MMS)mission were built at Goddard. The Advanced Composition Explorer (ACE) and Wind are operated out of a multi-mission operations center, which will also host several SSMO-managed cubesats in 2017. This paper focuses on the systems engineeringchallenges for such a large and varied fleet of spacecraft.

Spacecraft↗
NASA NTRS1996

Advanced Environmental Monitoring and Control Program: Strategic Plan

Human missions in space, from short-duration shuttle missions lasting no more than several days to the medium-to-long-duration missions planned for the International Space Station, face a number of hazards that must be understood and mitigated for the mission to be carried out safely. Among these hazards are those posed by the internal environment of the spacecraft itself; through outgassing of toxic vapors from plastics and other items, failures or off-nominal operations of spacecraft environmental control systems, accidental exposure to hazardous compounds used in experiments: all present potential hazards that while small, may accumulate and pose a danger to crew health. The first step toward mitigating the dangers of these hazards is understanding the internal environment of the spacecraft and the compounds contained within it. Future spacecraft will have integrated networks of redundant sensors which will not only inform the crew of hazards, but will pinpoint the problem location and, through analysis by intelligent systems, recommend and even implement a course of action to stop the problem. This strategic plan details strategies to determine NASA's requirements for environmental monitoring and control systems for future spacecraft, and goals and objectives for a program to answer these needs.

Schmidt, Gregory↗
NASA NTRS2013

A System for Fault Management for NASA's Deep Space Habitat

NASA's exploration program envisions the utilization of a Deep Space Habitat (DSH) for human exploration of the space environment in the vicinity of Mars and/or asteroids. Communication latencies with ground control of as long as 20+ minutes make it imperative that DSH operations be highly autonomous, as any telemetry-based detection of a systems problem on Earth could well occur too late to assist the crew with the problem. A DSH-based development program has been initiated to develop and test the automation technologies necessary to support highly autonomous DSH operations. One such technology is a fault management tool to support performance monitoring of vehicle systems operations and to assist with real-time decision making in connection with operational anomalies and failures. Toward that end, we are developing Advanced Caution and Warning System (ACAWS), a tool that combines dynamic and interactive graphical representations of spacecraft systems, systems modeling, automated diagnostic analysis and root cause identification, system and mission impact assessment, and mitigation procedure identification to help spacecraft operators (both flight controllers and crew) understand and respond to anomalies more effectively. In this paper, we describe four major architecture elements of ACAWS: Anomaly Detection, Fault Isolation, System Effects Analysis, and Graphic User Interface (GUI), and how these elements work in concert with each other and with other tools to provide fault management support to both the controllers and crew. We then describe recent evaluations and tests of ACAWS on the DSH testbed. The results of these tests support the feasibility and strength of our approach to failure management automation and enhanced operational autonomy.

Fault management↗
NASA NTRS2013

A System for Fault Management and Fault Consequences Analysis for NASA's Deep Space Habitat

NASA's exploration program envisions the utilization of a Deep Space Habitat (DSH) for human exploration of the space environment in the vicinity of Mars and/or asteroids. Communication latencies with ground control of as long as 20+ minutes make it imperative that DSH operations be highly autonomous, as any telemetry-based detection of a systems problem on Earth could well occur too late to assist the crew with the problem. A DSH-based development program has been initiated to develop and test the automation technologies necessary to support highly autonomous DSH operations. One such technology is a fault management tool to support performance monitoring of vehicle systems operations and to assist with real-time decision making in connection with operational anomalies and failures. Toward that end, we are developing Advanced Caution and Warning System (ACAWS), a tool that combines dynamic and interactive graphical representations of spacecraft systems, systems modeling, automated diagnostic analysis and root cause identification, system and mission impact assessment, and mitigation procedure identification to help spacecraft operators (both flight controllers and crew) understand and respond to anomalies more effectively. In this paper, we describe four major architecture elements of ACAWS: Anomaly Detection, Fault Isolation, System Effects Analysis, and Graphic User Interface (GUI), and how these elements work in concert with each other and with other tools to provide fault management support to both the controllers and crew. We then describe recent evaluations and tests of ACAWS on the DSH testbed. The results of these tests support the feasibility and strength of our approach to failure management automation and enhanced operational autonomy

System Effects Analysis↗
NASA NTRS2013

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↗
NASA NTRS1993

Future trends in NASA space operations

It is a great privilege for me to address my colleagues at SpaceOps 92. Today, I would like to share with you some current directions we are pursuing in NASA's Office of Space Communications (OSC). The space agencies of the world have produced some remarkable achievements in conducting our missions. It is also true that we consume significant resources in controlling and operating our spacecraft. In these challenging economic times, the degree to which our agencies can develop new missions will depend on our ability to reduce operating costs. I believe that there are many opportunities for doing this, and I will explore some of our plans in this regard. First, I will review the business of space operations.

Fuechsel, Charles F.↗
NASA NTRS2001

Propulsion Instruments for Small Hall Thruster Integration

Planning and development are underway for the propulsion instrumentation necessary for the next AFRL electric propulsion flight project, which includes both a small Hall thruster and a micro-PPT. These instruments characterize the environment induced by the thruster and the associated data constitute part of a 'user's manual' for these thrusters. Several instruments probe the back-flow region of the thruster plume, and the data are intended for comparison with detailed numerical models in this region. Specifically, an ion probe is under development to determine the energy and species distributions, and a Langmuir probe will be employed to characterize the electron density and temperature. Other instruments directly measure the effects of thruster operation on spacecraft thermal control surfaces, optical surfaces, and solar arrays. Specifically, radiometric, photometric, and solar-cell-based sensors are under development. Prototype test data for most sensors should be available, together with details of the instrumentation subsystem and spacecraft interface.

ion probes↗
NASA NTRS1996

A global spacecraft control network for spacecraft autonomy research

The development and implementation of the Automated Space System Experimental Testbed (ASSET) space operations and control network, is reported on. This network will serve as a command and control architecture for spacecraft operations and will offer a real testbed for the application and validation of advanced autonomous spacecraft operations strategies. The proposed network will initially consist of globally distributed amateur radio ground stations at locations throughout North America and Europe. These stations will be linked via Internet to various control centers. The Stanford (CA) control center will be capable of human and computer based decision making for the coordination of user experiments, resource scheduling and fault management. The project's system architecture is described together with its proposed use as a command and control system, its value as a testbed for spacecraft autonomy research, and its current implementation.

Kitts, Christopher A.↗
NASA NTRS2002

Monitor and control software for ground systems in the Deep Space Network

Currently, the NMC is being utilized for 24/7 operations at the three main DSN complexes supporting all of the major spacecraft supported and managed by JPL. A portable version of NMC is being exercised in a Compatibility Test Trailer for off-site monitor and control. Remote monitoring of the three complexes at JPL is accomplished as part of the NMC infrastructure.

monitor and control infrastructure spacecraft oper↗