Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “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 19 records
All sourcesNASA NTRSDOE OSTI
DOE OSTI2026

Frontier Job-Centric Telemetry Dataset

Comprehensive analysis of high-performance computing (HPC) systems requires linking workload execution to system behavior. This kind of analysis is vital for diagnosing performance issues, managing capacity, detecting anomalous workloads, and understanding how applications interact with system hardware. This job-centric telemetry dataset unifies scheduler job records with node-level measurements, enabling direct association between workloads and their corresponding power, thermal, and performance characteristics. It contains sanitized, scheduler related metadata for 152,400 individual jobs that ran on the Frontier supercomputer and ended on selected days throughout 2024 and 2025, a subpopulation of ~6.8% of the total number of allocated jobs with non-zero run time on the system over that same period. Each is linked with files that contain telemetry time series records of the power utilization and temperature behavior of its allocated nodes and their processors during the run time of the job. Where available, a portion of the job files also contain network performance time series. Jobs are sampled from select days that reflect normal levels of user activity and possess job size distributions with large numbers of leadership class jobs (>20% of Frontier nodes). Jobs in this dataset attempt to best represent successful user workflows.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗
NASA NTRS1989

Accuracy of telemetry signal power loss in a filter as an estimate for telemetry degradation

When telemetry data is transmitted through a communication link, some degradation in telemetry performance occurs as a result of the imperfect frequency response of the channel. The term telemetry degradation as used here is the increase in received signal power required to offset this filtering. The usual approach to assessing this degradation is to assume that it is equal to the signal power loss in the filtering, which is easily calculated. However, this approach neglects the effects of the nonlinear phase response of the filter, the effect of any reduction of the receiving system noise due to the filter, and intersymbol interference. Here, an exact calculation of the telemetry degradation, which includes all of the above effects, is compared with the signal power loss calculation for RF filtering of NRZ data on a carrier. The signal power loss calculation is found to be a reasonable approximation when the filter follows the point at which the receiving system noise is introduced, especially if the signal power loss is less than 0.5 dB. The signal power loss approximation is less valid when the receiving system noise is not filtered.

Koerner, M. A.↗
NASA NTRS1989

Transportable telemetry workstation

The goal was to complete the design of a prototype for a Transportable Telemetry Workstation (TTW). The Macintosh 2 is used to provide a low-cost system which can house real-time cards mounted on the NuBus inside the Macintosh 2 plus provide a standardized user interface on the Macintosh 2 console. Prior to a telemetry run, the user will be able to configure his real-time telemetry processing functions from the Macintosh 2 console. During a telemetry run, the real-time cards will store the telemetry data directly on a hard disk while permitting viewing of the data cards on the Macintosh 2 console on various selectable formats. The user will view the cards in terms of the functions they perform and the selectable paths through the cards, it is not required to become involved directly in hardware issue except in terms of the functional configuration of the system components. The TTW will accept telemetry data from an RS422 serial input data bus, pass it through a frame synchronizer card and on to a real time controller card via a telemetry backplane bus. The controller card will then route the data to a hard disk through a SCSI interface, and/or to a user interface on the Macintosh 2 console by way of the Macintosh 2 NuBus. The three major components to be designed, therefore, are the TTW Controller Card, the TTW Synchronizer Card, and the NuBus/Macintosh 2 User Interface. Design and prototyping of this state-of-the-art, transportable, low-cost, easy-to-use multiprocessor telemetry system is continuing. Other functions are planned for the future.

Collins, Aaron S.↗
NASA NTRS1990

High performance VLSI telemetry data systems

NASA's deployment of major space complexes such as Space Station Freedom (SSF) and the Earth Observing System (EOS) will demand increased functionality and performance from ground based telemetry acquisition systems well above current system capabilities. Adaptation of space telemetry data transport and processing standards such as those specified by the Consultative Committee for Space Data Systems (CCSDS) standards and those required for commercial ground distribution of telemetry data, will drive these functional and performance requirements. In addition, budget limitations will force the requirement for higher modularity, flexibility, and interchangeability at lower cost in new ground telemetry data system elements. At NASA's Goddard Space Flight Center (GSFC), the design and development of generic ground telemetry data system elements, over the last five years, has resulted in significant solutions to these problems. This solution, referred to as the functional components approach includes both hardware and software components ready for end user application. The hardware functional components consist of modern data flow architectures utilizing Application Specific Integrated Circuits (ASIC's) developed specifically to support NASA's telemetry data systems needs and designed to meet a range of data rate requirements up to 300 Mbps. Real-time operating system software components support both embedded local software intelligence, and overall system control, status, processing, and interface requirements. These components, hardware and software, form the superstructure upon which project specific elements are added to complete a telemetry ground data system installation. This paper describes the functional components approach, some specific component examples, and a project example of the evolution from VLSI component, to basic board level functional component, to integrated telemetry data system.

Chesney, J.↗
NASA NTRS1994

Test Telemetry And Command System (TTACS)

The Jet Propulsion Laboratory has developed a multimission Test Telemetry and Command System (TTACS) which provides a multimission telemetry and command data system in a spacecraft test environment. TTACS reuses, in the spacecraft test environment, components of the same data system used for flight operations; no new software is developed for the spacecraft test environment. Additionally, the TTACS is transportable to any spacecraft test site, including the launch site. The TTACS is currently operational in the Galileo spacecraft testbed; it is also being provided to support the Cassini and Mars Surveyor Program projects. Minimal personnel data system training is required in the transition from pre-launch spacecraft test to post-launch flight operations since test personnel are already familiar with the data system's operation. Additionally, data system components, e.g. data display, can be reused to support spacecraft software development; and the same data system components will again be reused during the spacecraft integration and system test phases. TTACS usage also results in early availability of spacecraft data to data system development and, as a result, early data system development feedback to spacecraft system developers. The TTACS consists of a multimission spacecraft support equipment interface and components of the multimission telemetry and command software adapted for a specific project. The TTACS interfaces to the spacecraft, e.g., Command Data System (CDS), support equipment. The TTACS telemetry interface to the CDS support equipment performs serial (RS-422)-to-ethernet conversion at rates between 1 bps and 1 mbps, telemetry data blocking and header generation, guaranteed data transmission to the telemetry data system, and graphical downlink routing summary and control. The TTACS command interface to the CDS support equipment is nominally a command file transferred in non-real-time via ethernet. The CDS support equipment is responsible for metering the commands to the CDS; additionally for Galileo, TTACS includes a real-time-interface to the CDS support equipment. The TTACS provides the basic functionality of the multimission telemetry and command data system used during flight operations. TTACS telemetry capabilities include frame synchronization, Reed-Solomon decoding, packet extraction and channelization, and data storage/query. Multimission data display capabilities are also available. TTACS command capabilities include command generation verification, and storage.

Fogel, Alvin J.↗
NASA NTRS1994

Process and methodology of developing Cassini G and C Telemetry Dictionary

While the Cassini spacecraft telemetry design had taken on the new approach of 'packetized telemetry', the AACS (Attitude and Articulation Subsystem) had further extended into the design of 'mini-packets' in its telemetry system. Such telemetry packet and mini-packet design produced the AACS Telemetry Dictionary; iterations of the latter in turn provided changes to the former. The ultimate goals were to achieve maximum telemetry packing density, optimize the 'freshness' of more time-critical data, and to effect flexibility, i.e., multiple AACS data collection schemes, without needing to change the overall spacecraft telemetry mode. This paper describes such a systematic process and methodology, evidenced by various design products related to, or as part of, the AACS Telemetry Dictionary.

Kan, Edwin P.↗
NASA NTRS2011

Telemetry-Based Ranging

A telemetry-based ranging scheme was developed in which the downlink ranging signal is eliminated, and the range is computed directly from the downlink telemetry signal. This is the first Deep Space Network (DSN) ranging technology that does not require the spacecraft to transmit a separate ranging signal. By contrast, the evolutionary ranging techniques used over the years by NASA missions, including sequential ranging (transmission of a sequence of sinusoids) and PN-ranging (transmission of a pseudo-noise sequence) whether regenerative (spacecraft acquires, then regenerates and retransmits a noise-free ranging signal) or transparent (spacecraft feeds the noisy demodulated uplink ranging signal into the downlink phase modulator) relied on spacecraft power and bandwidth to transmit an explicit ranging signal. The state of the art in ranging is described in an emerging CCSDS (Consultative Committee for Space Data Systems) standard, in which a pseudo-noise (PN) sequence is transmitted from the ground to the spacecraft, acquired onboard, and the PN sequence is coherently retransmitted back to the ground, where a delay measurement is made between the uplink and downlink signals. In this work, the telemetry signal is aligned with the uplink PN code epoch. The ground station computes the delay between the uplink signal transmission and the received downlink telemetry. Such a computation is feasible because symbol synchronizability is already an integral part of the telemetry design. Under existing technology, the telemetry signal cannot be used for ranging because its arrival-time information is not coherent with any Earth reference signal. By introducing this coherence, and performing joint telemetry detection and arrival-time estimation on the ground, a high-rate telemetry signal can provide all the precision necessary for spacecraft ranging.

Hamkins, Jon↗
NASA NTRS1982

Telemetry methods for monitoring physiological parameters

The use of telemetry to monitor various physiological functions is discussed. The advantages of the technique and the parameters that it can monitor are assessed, and the main telemetry systems, including pressure telemetry, flow telemetry, and multichannel telemetry, are detailed. Human applications of implanted flow transducers, total implant versus backpack telemetry, the use of power sources and integrated circuits in telemetry, and the future prospects of the technique in hypertension treatment and research are discussed.

Fryer, T. B.↗
NASA NTRS1983

Telemetry Modulation and Coping

Digital telemetry has supplanted analog telemetry for deep space communications. With digital telemetry, the telecommunications systems design engineer may use error correcting codes. This allows increased error protection at the cost of increased bandwidth. All science telemetry returned from the Voyager and Galileo spacecraft are protected by error correcting codes. Both the modulation and coding of digital telemetry for the deep space channel are considered. The descriptions include relative performance of some competing schemes. However, the treatment given here is, of necessity, cursory. A small class of modulation schemes has proven to be best for the deep space channel. The digital telemetry is either phase-shift-keyed onto a squarewave subcarrier and then phase modulated onto the carrier or the digital telemetry is directly phase modulated onto the carrier.

Kinman, P. W.↗
NASA NTRS2006

An Approach to Integrated Spectrum Efficient Network Enhanced Telemetry (iSENET))

As the integrated Network Enhanced Telemetry (iNET) program moves forward in resolving systems engineering design and architecture definition, critical technology "gaps" and a migration path to realizing the integration of this technology are needed to insure a smooth transition from the current legacy point to point telemetry links to a network oriented telemetry system. Specifically, identified by the DoD aeronautical telemetry community is the need for a migration to a network solution for command, control, and transfer of test data by optimizing the physical, data link, and network layers. In this paper, we present a network-centric telemetry approach based on variants of 802.11 that leverages the open standards as well as the previous Advanced Range Telemetry (ARTM) work on the physical layer waveform. Specifically, we present a burst modem approach based on the recent AOFDM 802.11a work, a TDMA-like MAC layer approach based on 802.11e, and then add additional MAC layer features to allow for the multi-hop aeronautical environment using a variant of the current working standards of 802.11s. The combined benefits of the variants obtained from 802.11a, 802.11e, and 802.11s address the needs for both spectrum efficiency in the aeronautical environment and the iNET program.

TDMA↗
NASA NTRS1994

Experience with the EURECA Packet Telemetry and Packet Telecommand system

The European Retrieval Carrier (EURECA) was launched on its first flight on the 31st of July 1992 and retrieved on the 29th of June 1993. EURECA is characterized by several new on-board features, most notably Packet telemetry, and a partial implementation of packet telecommanding, the first ESA packetised spacecraft. Today more than one year after the retrieval the data from the EURECA mission has to a large extent been analysed and we can present some of the interesting results. This paper concentrates on the implementation and operational experience with the EURECA Packet Telemetry and Packet Telecommanding. We already discovered during the design of the ground system that the use of packet telemetry has major impact on the overall design and that processing of packet telemetry may have significant effect on the computer loading and sizing. During the mission a number of problems were identified with the on-board implementation resulting in very strange anomalous behaviors. Many of these problems directly violated basic assumptions for the design of the ground segment adding to the strange behavior. The paper shows that the design of a telemetry packet system should be flexible enough to allow a rapid configuration of the telemetry processing in order to adapt it to the new situation in case of an on-board failure. The experience gained with the EURECA mission control should be used to improve ground systems for future missions.

Sorensen, Erik Mose↗
NASA NTRS1978

Medical Telemetry

Telemetry is the process whereby physiological or other data is acquired by instruments, translated into radio signals and j sent to a receiving station where the signals are decoded and recorded. Extensively used in I space operations, it is finding new Earth applications, among them transmission of medical data between emergency vehicles and hospitals. For example, transmission of an electrocardiogram from an ambulance to a hospital enables a physician to read the telemetered EKG and advise ambulance attendants on emergency procedures. Central Medical Emergency Dispatch (CMED) operates as a regional emergency medical communications center for Cleveland, Ohio and Cuyahoga County. The CMED system includes radio and telephone communications from hospital-to-hospital and from ambulance-to-hospital, but for improved emergency life support CMED sought to add a county-wide telemetry capability. The problem was that there were only eight radio frequencies available for telemetry and there were more than 30 potential users in Cleveland alone. NASA's Lewis Research Center volunteered its expert assistance. The Center's engineers studied the systems of other telemetry using cities, surveyed area hospitals to assure compatibility of telemetry equipment, and advised what types of equipment would be needed in emergency vehicles and at the various hospitals. The Lewis plan suggested that CMED be designated the central coordinating agency for the Cuyahoga County system, monitoring all telemetry frequencies and, when requested, assigning one not in use or one to be used at a sufficient distance that it would create no interference problem.

Source record↗
NASA NTRS2014

Comprehension of Spacecraft Telemetry Using Hierarchical Specifications of Behavior

A key challenge in operating remote spacecraft is that ground operators must rely on the limited visibility available through spacecraft telemetry in order to assess spacecraft health and operational status. We describe a tool for processing spacecraft telemetry that allows ground operators to impose structure on received telemetry in order to achieve a better comprehension of system state. A key element of our approach is the design of a domain-specific language that allows operators to express models of expected system behavior using partial specifications. The language allows behavior specifications with data fields, similar to other recent runtime verification systems. What is notable about our approach is the ability to develop hierarchical specifications of behavior. The language is implemented as an internal DSL in the Scala programming language that synthesizes rules from patterns of specification behavior. The rules are automatically applied to received telemetry and the inferred behaviors are available to ground operators using a visualization interface that makes it easier to understand and track spacecraft state. We describe initial results from applying our tool to telemetry received from the Curiosity rover currently roving the surface of Mars, where the visualizations are being used to trend subsystem behaviors, in order to identify potential problems before they happen. However, the technology is completely general and can be applied to any system that generates telemetry such as event logs.

Runtime monitoring↗
NASA NTRS2017

Sharing Telemetry across Organizations and Systems

The XTCE (XML Telemetric and Command Exchange) standard provides a way to describe space mission telemetry and command “databases” (or dictionaries) to be exchanged across centers and space agencies. Having a standard format for describing the telemetry and command formats allows for the development or adoption of compatible tools and significantly reduces the amount of custom software development often needed to ensure all system components have access to consistent format definitions. The main objective of this paper is to show how powerful XTCE is in terms of interoperability across organizations. This paper summarizes work which entailed converting the mission telemetry database for a current NASA mission, in XTCE format, into several target mission operation databases associated with different telemetry and command toolchains, and then, comparing the results of the telemetry processing and display. The target toolchains selected were Ball Aerospace/COSMOS, NASA-GSFC/ITOS (Goddard Space Flight Center/Integrated Test and Operations System), and NASA-AMMOS/AMPCS (Advanced Multi-Mission Operations System/Mission Data Processing and Control System) – all real-time telemetry and command processing systems.

Jones, Ron↗
NASA NTRS1995

Incorporating CCSDS Telemetry Standards and Philosophy on Cassini

The Cassini project at the Jet Propulsion Laboratory (JPL) is implementing a spacecraft telemetry system based on the Consultative Committee for Space Data Systems (CCSDS) packet telemetry standards. Resolving the CCSDS concepts with a Ground Data System designed to handle time-division-multiplexed telemetry and also handling constraints unique to a deep-space planetary spacecraft (such as fixed downlink opportunities, small downlink rates and requirements for on-board data storage) have resulted in spacecraft and ground system design challenges. Solving these design challenges involved adapting and extending the CCSDS telemetry standards as well as changes to the spacecraft and ground system designs. The resulting spacecraft/ground system design is an example of how new ideas and philosophies can be incorporated into existing systems and design approaches without requiring significant rework. In addition, it shows that the CCSDS telemetry standards can be successfully applied to deep-space planetary spacecraft.

CCSDS↗
NASA NTRS1975

Real time telemetry and data compression

The generation of telemetry and data compression by the flight program was verified. The adequacy of flight program telemetry control and timing is proven by the analysis of simulation laboratory runs of past programs through the use of telemetry. The telemetry data are correctly issued using specific tags called process input/output (P10) tags. Verification is accomplished by ensuring that a specific P10 tag and mode register setting identifies the correct parameter and that the data are properly scaled for subsequent ground station reduction. It was checked that the LVDC telemetry correctly adheres to the general requirements specified by the EDD. Data compression specifications are verified using compressed data from nominal flight simulations and from a series of perturbations designed to test data table overflows, data dump rates, and compression of data for occurrence events.

Source record↗