Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Spacecraft Telemetry”

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 325 records · Page 18

TALOS: A distributed architecture for intelligent monitoring and anomaly diagnosis of the Hubble Space Telescope

Lockheed, the Hubble Space Telescope Mission Operations Contractor, is currently engaged in a project to develop a distributed architecture of communicating expert systems to support vehicle operations. This architecture, named Telemetry Analysis Logic for Operating Spacecraft (TALOS), has the potential for wide applicability in spacecraft operations. The architecture mirrors the organization of the human experts within an operations control center.

Cruse, Bryant G.↗

Software For Three-Dimensional Space-Shuttle Imagery

Flight Dynamics/Space Transportation System Three-Dimensional Monitor System (3-D Mon) is real-time graphical mission-monitoring software tool. Main objective to compute and display realistic three-dimensional solid model image of Space Shuttle, remote-manipulator system, payload, and surroundings from real-time Space Shuttle telemetry data. Ability to support spacecraft other than Space Shuttle also incorporated. Display shows almost any desired perspective. Written in C programming language.

Pittarelli, Ernest J.↗

A MOS for all seasons

From a systems perspective, this paper examines the challenges of a single system to support multiple JPL space exploration missions and the need for unitary responsibility for the system. The focus is a Mission Operations System (MOS), which is effectively a mission management organization with direct authority over data system operations, command sequencing, flight operations control, data management, trajectory determination, telemetry and data acquisition, and spacecraft analysis. Stratagems for training and the approach to processes, procedures, and interfaces to facilitate the transition from the present situation to a truly multimission operational environment are developed. The outcome is a paradigm for a MOS that is achievable, that can effectively support multiple projects, and that can take advantage of technological changes without perturbing the entire system.

Bryant, Larry↗

EDOS operations concept and development approach

The Earth Observing System (EOS) Data and Operations System (EDOS) is being developed by the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) for the capture, level zero processing, distribution, and backup archiving of high speed telemetry data received from EOS spacecraft. All data received will conform to the Consultative Committee for Space Data Standards (CCSDS) recommendations. The major EDOS goals are to: (1) minimize EOS program costs to implement and operate EDOS; (2) respond effectively to EOS growth requirements; and (3) maintain compatibility with existing and enhanced versions of NASA institutional systems required to support EOS spacecraft. In order to meet these goals, the following objectives have been defined for EDOS: (1) standardize EDOS interfaces to maximize utility for future requirements; (2) emphasize life-cycle cost (LCC) considerations (rather than procurement costs) in making design decisions and meeting reliability, maintainability, availability (RMA) and upgradability requirements; (3) implement data-driven operations to the maximum extent possible to minimize staffing requirements and to maximize system responsiveness; (4) provide a system capable of simultaneously supporting multiple spacecraft, each in different phases of their life-cycles; (5) provide for technology insertion features to accommodate growth and future LCC reductions during the operations phase; and (6) provide a system that is sufficiently robust to accommodate incremental performance upgrades while supporting operations. Operations concept working group meetings were facilitated to help develop the EDOS operations concept. This provided a cohesive concept that met with approval of responsible personnel from the start. This approach not only speeded up the development process by reducing review cycles, it also provided a medium for generating good ideas that were immediately molded into feasible concepts. The operations concept was then used as a basis for the EDOS specification. When it was felt that concept elements did not support detailed requirements, the facilitator process was used to resolve discrepancies or to add new concept elements to support the specification. This method provided an ongoing revisal of the operations concept and prevented large revisions at the end of the requirement analysis phase of system development.

Knoble, G.↗

HELIOS Third Joint Working Group Meeting

During the past six months since the Second Helios Joint Working Group Meeting held 27-30 April 1970 at Goddard Space Flight Center, the TDS Sub-Group supported the Helios Project Office and the other Sub-Groups in the timely disposition of action items and the dissemination of information pertinent to the development of interface documentation. Of particular importance during this time period was the Project's decision to incorporate a single-channel telemetry system design aboard the spacecraft. The TDS Sub-Group participated actively in the process that led to this decision. Still under active study with TDS participation is the pending Project Office decision regarding the incorporation of a ranging capability within the telecommunications design. The TDS Sub-Group assisted the Mission Analysis and Operations Sub-Group in establishment of a study effort concerning the Near-Earth Sequence of Events from launch to launch plus 8 hours. This study, which will provide valuable data for the spacecraft telecommunications design, will include participation by the Experiment, Launch Vehicle, Spacecraft, as well as the TDS and MA&O Sub-Groups. Also during the past 6-month period, the TDS, in conjunction with the Spacecraft Sub-Group, initiated activity to develop the Helios Spacecraft/TDS Compatibility Test Plans and Procedures. Activity concerning the foregoing interface discussions has been and will continue to be based upon the "TDS Estimated Capabilities Document for the Helios Missions" (613-1), and the "DSN/Flight Project Interface Design Handbook" (810-5). These will continue to be considered TDS controlling documents until specific Helios Project/TDS interface documentation is generated and signed off by the respective parties. In addition to the above, the DSN continued the Helios Trainee Program with seven GfW/DFVLR trainees in residence at JPL. Two trainees will complete their year's residency concurrent with the Third Helios Joint Working Group Meeting, while four new trainees are expected to arrive following the Third Helios Joint Working Group Meeting. These and other activities are reported in detail in the paragraphs that follow.

Ousley, Gilbert↗

Ground-Based GPS as a Calibration/Validation Tool for Tropospheric Sensing Instruments

The tropospheric sensing capabilities of ground-based GPS have been the subject of intensive validation efforts in recent years. But a maturing GPS technology is now rapidly becoming a valuable calibration/validation tool in its own right. We will describe two applications where ground-based GPS receivers have been used as a calibration/validation tool. The first such case is the Cassini gravitational wave media calibration project. A water vapor radiometer (WVR) will calibrate the telemetry signal from the Cassini spacecraft for line-of-sight wet tropospheric fluctuations. The demanding mission specifications require that the WVR's retrieval of wet delay from measurements of brightness temperature be precisely calibrated. We will describe the results from a special campaign to calibrate the WVR's retrieval algorithm with GPS. The second case involves the Topex/Poseidon microwave radiometer (TMR) which is used to calibrate the altimetric measurement for the effect of tropospheric water vapor. Using GPS data from 1992 to 1997 we detected an anomalous drift in columnar water vapor measurements from the TMR. The TMR's spurious drift implies that the uncalibrated estimate of global mean sea level change from Topex/Poseidon is too low by approximately 1 mm/yr. We will discuss the challenges of using long-term time series and problems relating to using the global GPS network as a calibration tool.

Bar-Sever, Y. E.↗

Estimation and Modeling of Enceladus Plume Jet Density Using Reaction Wheel Control Data

The Cassini spacecraft was launched on October 15, 1997 by a Titan 4B launch vehicle. After an interplanetary cruise of almost seven years, it arrived at Saturn on June 30, 2004. In 2005, Cassini completed three flybys of Enceladus, a small, icy satellite of Saturn. Observations made during these flybys confirmed the existence of a water vapor plume in the south polar region of Enceladus. Five additional low-altitude flybys of Enceladus were successfully executed in 2008-9 to better characterize these watery plumes. The first of these flybys was the 50-km Enceladus-3 (E3) flyby executed on March 12, 2008. During the E3 flyby, the spacecraft attitude was controlled by a set of three reaction wheels. During the flyby, multiple plume jets imparted disturbance torque on the spacecraft resulting in small but visible attitude control errors. Using the known and unique transfer function between the disturbance torque and the attitude control error, the collected attitude control error telemetry could be used to estimate the disturbance torque. The effectiveness of this methodology is confirmed using the E3 telemetry data. Given good estimates of spacecraft's projected area, center of pressure location, and spacecraft velocity, the time history of the Enceladus plume density is reconstructed accordingly. The 1 sigma uncertainty of the estimated density is 7.7%. Next, we modeled the density due to each plume jet as a function of both the radial and angular distances of the spacecraft from the plume source. We also conjecture that the total plume density experienced by the spacecraft is the sum of the component plume densities. By comparing the time history of the reconstructed E3 plume density with that predicted by the plume model, values of the plume model parameters are determined. Results obtained are compared with those determined by other Cassini science instruments.

Lee, Allan Y.↗

Estimation and Modeling of Enceladus Plume Jet Density Using Reaction Wheel Control Data

The Cassini spacecraft was launched on October 15, 1997 by a Titan 4B launch vehicle. After an interplanetary cruise of almost seven years, it arrived at Saturn on June 30, 2004. In 2005, Cassini completed three flybys of Enceladus, a small, icy satellite of Saturn. Observations made during these flybys confirmed the existence of a water vapor plume in the south polar region of Enceladus. Five additional low-altitude flybys of Enceladus were successfully executed in 2008-9 to better characterize these watery plumes. The first of these flybys was the 50-km Enceladus-3 (E3) flyby executed on March 12, 2008. During the E3 flyby, the spacecraft attitude was controlled by a set of three reaction wheels. During the flyby, multiple plume jets imparted disturbance torque on the spacecraft resulting in small but visible attitude control errors. Using the known and unique transfer function between the disturbance torque and the attitude control error, the collected attitude control error telemetry could be used to estimate the disturbance torque. The effectiveness of this methodology is confirmed using the E3 telemetry data. Given good estimates of spacecraft's projected area, center of pressure location, and spacecraft velocity, the time history of the Enceladus plume density is reconstructed accordingly. The 1-sigma uncertainty of the estimated density is 7.7%. Next, we modeled the density due to each plume jet as a function of both the radial and angular distances of the spacecraft from the plume source. We also conjecture that the total plume density experienced by the spacecraft is the sum of the component plume densities. By comparing the time history of the reconstructed E3 plume density with that predicted by the plume model, values of the plume model parameters are determined. Results obtained are compared with those determined by other Cassini science instruments.

Lee, Allan Y.↗

Tracking and data relay satellite fault isolation and correction using PACES: Power and attitude control expert system

The Power and Attitude Control Expert System (PACES) is an object oriented and rule based expert system which provides spacecraft engineers with assistance in isolating and correcting problems within the Power and Attitude Control Subsystems of the Tracking and Data Relay Satellites (TDRS). PACES is designed to act in a consultant role. It will not interface to telemetry data, thus preserving full operator control over spacecraft operations. The spacecraft engineer will input requested information. This information will include telemetry data, action being performed, problem characteristics, spectral characteristics, and judgments of spacecraft functioning. Questions are answered either by clicking on appropriate responses (for text), or entering numeric values. A context sensitive help facility allows access to additional information when the user has difficulty understanding a question or deciding on an answer. The major functionality of PACES is to act as a knowledge rich system which includes block diagrams, text, and graphics, linked using hypermedia techniques. This allows easy movement among pieces of the knowledge. Considerable documentation of the spacecraft Power and Attitude Control Subsystems is embedded within PACES. The development phase of TDRSS expert system technology is intended to provide NASA with the necessary expertise and capability to define requirements, evaluate proposals, and monitor the development progress of a highly competent expert system for NASA's Tracking and Data Relay Satellite Program.

Erikson, Carol-Lee↗

The NASA Spacecraft Transponding Modem

A new deep space transponder is being developed by the Jet Propulsion Laboratory for NASA. The Spacecraft Transponding Modem (STM) implements standard transponder functions and some of the command and telemetry channel service functions that have resided in spacecraft Command/Data Subsystems.

Transponder↗

Spacecraft Conceptual Design for the 8-Meter Advanced Technology Large Aperture Space Telescope (ATLAST)

The Advanced Concepts Office at Marshall Space Flight Center completed a brief spacecraft design study for the 8-meter monolithic Advanced Technology Large Aperture Space Telescope (ATLAST-8m). This spacecraft concept provides all power, communication, telemetry, avionics, guidance and control, and thermal control for the observatory, and inserts the observatory into a halo orbit about the second Sun-Earth Lagrange point. The multidisciplinary design team created a simple spacecraft design that enables component and science instrument servicing, employs articulating solar panels for help with momentum management, and provides precise pointing control while at the same time fast slewing for the observatory.

Hopkins, Randall C.↗

Satellite and space probe telemetry.

Space modulation systems characteristics, considering data flow rate, spacecraft weight and power, antenna gain, noise figure, etc

SPACE COMMUNICATION↗

Venus Atmospheric Probe and Flyby Relay Spacecraft Cross-Link Tracking Impact on Relative Pointing Accuracy

Scientific exploration of Venus using an atmospheric probe requires relaying telemetry to Earth as the probe descends through the atmosphere to the surface of Venus. Using the flyby spacecraft to relay the probe telemetry to Earth will require precise carrier-to-probe pointing accuracy of the relay spacecraft’s antenna. NASA’s Deep Atmosphere Venus Investigation of Noble gases, Chemistry, and Imaging (DAVINCI) mission uses this carrier-to-probe relay technique. Although DAVINCI includes a coherent cross-link for science, this is not baselined for navigation tracking. This paper explores the potential effectiveness of cross-link tracking for reducing trajectory uncertainty and improving spacecraft-to-probe pointing.

DAVINCI↗

The impact of NRZ data asymmetry on the performance of a space telemetry system

The telemetry data asymmetry due to rising and falling voltage transitions can cause undesired spectral components at the output of a spacecraft transmitter. The performance of a space telemetry system can potentially degrade because of these undesired components. Here, an expression is derived for the power spectral density of an asymmetric nonreturn-to-zero (NRZ) data stream. This formula is then used to investigate how the data bandwidth varies with data asymmetry. At the receiver end, the threshold levels of undesired spectral components that fall into the carrier-tracking-loop bandwidth are determined by examining the derived spectral density. Further, based on this formula, a simple technique is developed for the computation of bit signal-to-noise ratio (SNR) degradation due to data asymmetry. The telemetry bit SNR degradations derived using this technique are compared with results obtained previously and with measurements by the Electronic Systems Test Laboratory (ESTL) at the Lyndon B. Johnson Space Center.

Nguyen, T. M.↗

Telemetry

The purpose of a telemetry system is to reliably and transparently convey measurement information from a remotely located data generating source to users located in space or on Earth. Typically, data generators are scientific sensors, science housekeeping sensors, engineering sensors and other subsystems on-board a spacecraft.

telemetry system measurement information data gene↗

XML Flight/Ground Data Dictionary Management

A computer program generates Extensible Markup Language (XML) files that effect coupling between the command- and telemetry-handling software running aboard a spacecraft and the corresponding software running in ground support systems. The XML files are produced by use of information from the flight software and from flight-system engineering. The XML files are converted to legacy ground-system data formats for command and telemetry, transformed into Web-based and printed documentation, and used in developing new ground-system data-handling software. Previously, the information about telemetry and command was scattered in various paper documents that were not synchronized. The process of searching and reading the documents was time-consuming and introduced errors. In contrast, the XML files contain all of the information in one place. XML structures can evolve in such a manner as to enable the addition, to the XML files, of the metadata necessary to track the changes and the associated documentation. The use of this software has reduced the extent of manual operations in developing a ground data system, thereby saving considerable time and removing errors that previously arose in the translation and transcription of software information from the flight to the ground system.

Wright, Jesse↗