Search NASA⌕ Search

SEARCH · Search NASA

Results for “mission tracking”

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 NTRS1989

Automation of orbit determination functions for National Aeronautics and Space Administration (NASA)-supported satellite missions

The Flight Dynamics Facility (FDF) at Goddard Space Flight Center (GSFC) provides spacecraft trajectory determination for a wide variety of National Aeronautics and Space Administration (NASA)-supported satellite missions, using the Tracking Data Relay Satellite System (TDRSS) and Ground Spaceflight and Tracking Data Network (GSTDN). To take advantage of computerized decision making processes that can be used in spacecraft navigation, the Orbit Determination Automation System (ODAS) was designed, developed, and implemented as a prototype system to automate orbit determination (OD) and orbit quality assurance (QA) functions performed by orbit operations. Based on a machine-resident generic schedule and predetermined mission-dependent QA criteria, ODAS autonomously activates an interface with the existing trajectory determination system using a batch least-squares differential correction algorithm to perform the basic OD functions. The computational parameters determined during the OD are processed to make computerized decisions regarding QA, and a controlled recovery process isactivated when the criteria are not satisfied. The complete cycle is autonomous and continuous. ODAS was extensively tested for performance under conditions resembling actual operational conditions and found to be effective and reliable for extended autonomous OD. Details of the system structure and function are discussed, and test results are presented.

Mardirossian, H.↗
NASA NTRS1990

Automation of orbit determination functions for National Aeronautics and Space Administration (NASA)-supported satellite missions

The Flight Dynamics Facility (FDF) at Goddard Space Flight Center (GSFC) provides spacecraft trajectory determination for a wide variety of National Aeronautics and Space Administration (NASA)-supported satellite missions, using the Tracking Data Relay Satellite System (TDRSS) and Ground Spaceflight and Tracking Data Network (GSTDN). To take advantage of computerized decision making processes that can be used in spacecraft navigation, the Orbit Determination Automation System (ODAS) was designed, developed, and implemented as a prototype system to automate orbit determination (OD) and orbit quality assurance (QA) functions performed by orbit operations. Based on a machine-resident generic schedule and predetermined mission-dependent QA criteria, ODAS autonomously activates an interface with the existing trajectory determination system using a batch least-squares differential correction algorithm to perform the basic OD functions. The computational parameters determined during the OD are processed to make computerized decisions regarding QA, and a controlled recovery process is activated when the criteria are not satisfied. The complete cycle is autonomous and continuous. ODAS was extensively tested for performance under conditions resembling actual operational conditions and found to be effective and reliable for extended autonomous OD. Details of the system structure and function are discussed, and test results are presented.

Mardirossian, H.↗
NASA NTRS1974

Tracking and data system support for the Pioneer project. Pioneers 6-9, extended missions: 1 July 1972 - 1 July 1973, volume 12

The Tracking and Data System supported the deep space phases of the Pioneer 6, 7, 8, and 9 missions, with two spacecraft in an inward trajectory and two spacecraft in an outward trajectory from the earth in heliocentric orbits. During the period of this report, scientific instruments aboard each of the spacecraft continued to register information relative to interplanetary particles and fields, and radiometric data generated by the network continued to contribute to knowledge of the celestial mechanics of the solar system. In addition, to network support activity detail, network performance and special support activities are covered.

Miller, R. B.↗
NASA NTRS1994

Comparison of predicted and actual orbital lifetimes for the SEDS-2 mission

This paper documents a series of estimates of the orbital lifetime of the SEDS-2 flight configuration made prior to the mission. These estimates were made with program LTIME, which has been in use at MSFC for a number of years. Because of the unusual configuration of upper-stage/tether/endmass flown on this mission, and the type of assumptions and inputs used in LTIME, the effective area used in the drag calculation had to be estimated in an unusual way. The final pre-flight predicted lifetime was 28.35 days. In the actual flight, the tether was cut approximately 5 days into the mission. The instrumented endmass plus about 12 km of tether rapidly reentered the atmosphere, and the Delta II Second Stage plus the remaining 8 km of tether reentered on mission day 60. Tracking data was used to reconstruct reentry sequences for the two parts of the configuration after the cut. The predicted lifetimes for the endmass plus tether-fragment were in the range of 0.2 to 2.8 days, depending on the perigee altitudes assumed. The predicted lifetime of the upper-stage plus tether was 56.4 days, which corresponds to reentry on mission day 61, in good agreement with the actual reentry on day 60.

Evans, Steven W.↗
NASA NTRS1977

Tracking and data system support for the Viking 1975 mission to Mars. Volume 2: Launch through landing of Viking 1

Problems inherent in the deployment and management of a worldwide tracking and data acquisition network to support the two Viking Orbiters and two Viking Landers simultaneously over 320 million kilometers (200 million miles) of deep space are discussed. Activities described include tracking coverage of the launch phase, the deep space operations during the long cruise phase that occupied approximately 11 months, and the implementation of the a vast worldwide network of tracking sttions and global communications systems. The performance of the personnel, hardware, and software involved in this vast undertaking are evaluated.

Mudgway, D. J.↗
NASA NTRS2005

Space Network IP Services (SNIS): An Architecture for Supporting Low Earth Orbiting IP Satellite Missions

The NASA Space Network (SN) supports a variety of missions using the Tracking and Data Relay Satellite System (TDRSS), which includes ground stations in White Sands, New Mexico and Guam. A Space Network IP Services (SNIS) architecture is being developed to support future users with requirements for end-to-end Internet Protocol (IP) communications. This architecture will support all IP protocols, including Mobile IP, over TDRSS Single Access, Multiple Access, and Demand Access Radio Frequency (RF) links. This paper will describe this architecture and how it can enable Low Earth Orbiting IP satellite missions.

Israel, David J.↗
NASA NTRS2002

A Gentle Touch

One aspect of my job as Payload Manager on the Advanced Composition Explorer (ACE) mission involved keeping track of what the different science teams were working on, and offering help where it was needed. At first it seemed like many of the scientists or their technical staff were not sure how safe it was to confide in me. Everybody knew I had spent most of my career with NASA at the Jet Propulsion Laboratory (JPL). All of my staff, initially four of them, came from JPL too. Left to our own devices, would we impose onerous NASA rules that could stifle innovation in the ACE (Advanced Composition Explorer) mission instrument development labs? The challenge to my team was getting the science groups to regard us as partners, or as people who could help them rather than as what they seemed to expect--a troop of requirements enforcers.

Frandsen, Allan↗
NASA NTRS2013

Real-Time Multimission Event Notification System for Mars Relay

As the Mars Relay Network is in constant flux (missions and teams going through their daily workflow), it is imperative that users are aware of such state changes. For example, a change by an orbiter team can affect operations on a lander team. This software provides an ambient view of the real-time status of the Mars network. The Mars Relay Operations Service (MaROS) comprises a number of tools to coordinate, plan, and visualize various aspects of the Mars Relay Network. As part of MaROS, a feature set was developed that operates on several levels of the software architecture. These levels include a Web-based user interface, a back-end "ReSTlet" built in Java, and databases that store the data as it is received from the network. The result is a real-time event notification and management system, so mission teams can track and act upon events on a moment-by-moment basis. This software retrieves events from MaROS and displays them to the end user. Updates happen in real time, i.e., messages are pushed to the user while logged into the system, and queued when the user is not online for later viewing. The software does not do away with the email notifications, but augments them with in-line notifications. Further, this software expands the events that can generate a notification, and allows user-generated notifications. Existing software sends a smaller subset of mission-generated notifications via email. A common complaint of users was that the system-generated e-mails often "get lost" with other e-mail that comes in. This software allows for an expanded set (including user-generated) of notifications displayed in-line of the program. By separating notifications, this can improve a user's workflow.

Wallick, Michael N.↗
NASA NTRS1999

Advance Approach to Concept and Design Studies for Space Missions

Recent automated and advanced techniques developed at JPL have created a streamlined and fast-track approach to initial mission conceptualization and system architecture design, answering the need for rapid turnaround of trade studies for potential proposers, as well as mission and instrument study groups.

Team X Team A Missions Design Proposal Development↗
NASA NTRS1971

Experiments D001, D002, and D006: Basic object, nearby object, and surface photography

On the Gemini 5 mission, acquisition and tracking was performed by the use of celestial bodies as aiming points. However, distant photography of the REP was not possible because of spacecraft electrical power difficulties which occurred after REP ejection. Terrestrial photography was accomplished within the limitations imposed by weather conditions and spacecraft electrical and thruster problems. The photographs that were obtained were significant only as an element of the data to be used in technique evaluation. The other data were time-correlated position and pointing information, atmospheric conditions, sun angle, exposure settings, and the flight logs and verbal comments of the crewmembers. The photographs shown are representative of those that facilitated evaluation of the acquisition and tracking techniques that were used in these three experiments.

Geltmacher, H. E.↗
NASA NTRS1974

The prologue - A look at Apollo and Apollo/Soyuz

The importance of man to the success of the Apollo missions is considered, giving attention to man's capabilities to provide rapid response to emergencies, the ability to carry out self-contained operations in the absence of communication with the ground, and the ability for rapid sensing, reaction, and vehicle control. In the upcoming Shuttle era the capabilities possessed by man are to be further utilized. The concern for the safety of men in space is one of the major reasons for the flight of the Apollo/Soyuz test project. Details regarding this project are discussed, taking into account the mission profile, hardware, program organization, mission communication modes, tracking, the participating astronauts and cosmonauts, and scientific studies.

Lee, C. M.↗
NASA NTRS1976

Planetary/DOD entry technology flight experiments. Volume 3: Planetary entry flight experiments handbook

The environments produced by entry into Jupiter and Saturn atmospheres are summarized. Worst case design environments are identified and the effect of entry angle, type of atmosphere and ballistic coefficient variations are presented. The range of environments experienced during earth entry is parametrically described as a function of initial entry conditions. The sensitivity of these environments to vehicle ballistic coefficient and nose radius is also shown. An elliptical deorbit maneuver strategy is defined in terms of the velocity increment required versus initial entry conditions and apoapsis altitude. Mission time, ground track, and out of plane velocity penalties are also presented. Performance capabilities of typical shuttle launched boosters are described including the initial entry conditions attainable as a function of paylaod mass and apoapsis altitude.

Christensen, H. E.↗