Search NASA⌕ Search

SEARCH · Search NASA

Results for “Data 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 1,549 records · Page 86

Economic evaluation of DSS 13 unattended operations demonstration

The goals and data collection requirements to be used for the economic and performance evaluation indexes and life cycle cost parameters for the upcoming operations demonstration of an automated Deep Space Station (DSS) run unattended and controlled remotely from JPL are presented. These evaluation indexes compare the remote operation of telemetry at DSS 13 with the cost and performance of a comparable manned operation at DSS 11. A description is presented of the data that needs to be collected, how the data will be analyzed, and what can and cannot be learned from this operations demonstration.

Remer, D. S.↗

AESD (Advanced Energy System Design) Records API [SWRs-17-50, 17-51, 17-52]

The Records API (application program interface) for Advanced Energy System Design (AESD) enables software that serves multidimensional record-oriented data to interoperate with software than uses such data. In the context of the Records API, multidimensional data records are simply tuples of real numbers, integers, and character strings, where each data value is tagged by a variable name, according to a pre-defined schema, and each record is assigned a unique integer identifier. Conceptually, these records are isomorphic to rows in a relational database, JSON objects, or key-value maps. Records servers might supply static datasets, sensor measurements that periodically update as new telemetry become available, or the results of simulations as the simulations generate new output. Records client software might display or analyze the data, but in the case of simulations the client request the creation of new ensembles for specified input parameters. It is also possible to chain records clients and servers together so that a client consuming data from a server might transform that data and serve it to additional clients. This minimalist API avoids imposing burdensome metadata, structural, or implementation requirements on developers by relying on open-source technologies that are readily available for common programming languages. In particular, the API has been designed to place the least possible burden on services that provide data. This document defines the message format for the Records API, a transport mechanism for communicating the data, and the semantics for interpreting it. The message format is specified as Google Protocol Buffers and the transport mechanism uses WebSockets. We discuss three major use cases for serving and consuming records data: (i) static data, (ii) dynamically augmented data, (iii) on-demand simulations, (iv) with filters, and (v) with bookmarks. Separate implementations of the API exist in C++, Haskell, JavaScript, Python, and R.

Bush, Brian↗

Advanced Energy System Design (AESD): Technical Manual for the Records API

The Records API (application program interface) for Advanced Energy System Design (AESD) enables software that serves multidimensional record-oriented data to interoperate with software than uses such data. In the context of the Records API, multidimensional data records are simply tuples of real numbers, integers, and character strings, where each data value is tagged by a variable name, according to a pre-defined schema, and each record is assigned a unique integer identifier. Conceptually, these records are isomorphic to rows in a relational database, JSON objects, or key-value maps. Records servers might supply static datasets, sensor measurements that periodically update as new telemetry become available, or the results of simulations as the simulations generate new output. Records client software might display or analyze the data, but in the case of simulations the client request the creation of new ensembles for specified input parameters. It is also possible to chain records clients and servers together so that a client consuming data from a server might transform that data and serve it to further clients. This minimalist API avoids imposing burdensome metadata, structural, or implementation requirements on developers by relying on open-source technologies that is readily available for common programming languages. In particular, the API has been designed to place the smallest possible burden on services that provide data. This document defines the message format for the Records API, a transport mechanism for communicating the data, and semantics for interpreting it. The message format is specified as Google Protocol Buffers and the transport mechanism uses WebSockets. We discuss three major use cases for serving and consuming records data: (i) static data, (ii) dynamically augmented data, (iii) on-demand simulations, (iv) with filters, and (v) with bookmarks. Separate implementations of the API exist in C++, Haskell, JavaScript, Python, and R.

97 MATHEMATICS AND COMPUTING↗

A spacecraft computer repairable via command.

The MULTIPAC is a central data system developed for deep-space probes with the distinctive feature that it may be repaired during flight via command and telemetry links by reprogramming around the failed unit. The computer organization uses pools of identical modules which the program organizes into one or more computers called processors. The interaction of these modules is dynamically controlled by the program rather than hardware. In the event of a failure, new programs are entered which reorganize the central data system with a somewhat reduced total processing capability aboard the spacecraft. Emphasis is placed on the evolution of the system architecture and the final overall system design rather than the specific logic design.

Fimmel, R. O.↗

Developing a Standard Method for Link-Layer Security of CCSDS Space Communications

Communications security for space systems has been a specialized field generally far removed from considerations of mission interoperability and cross-support in fact, these considerations often have been viewed as intrinsically opposed to security objectives. The space communications protocols defined by the Consultative Committee for Space Data Systems (CCSDS) have a twenty-five year history of successful use in over 400 missions. While the CCSDS Telemetry, Telecommand, and Advancing Orbiting Systems protocols for use at OSI Layer 2 are operationally mature, there has been no direct support within these protocols for communications security techniques. Link-layer communications security has been successfully implemented in the past using mission-unique methods, but never before with an objective of facilitating cross-support and interoperability. This paper discusses the design of a standard method for cryptographic authentication, encryption, and replay protection at the data link layer that can be integrated into existing CCSDS protocols without disruption to legacy communications services. Integrating cryptographic operations into existing data structures and processing sequences requires a careful assessment of the potential impediments within spacecraft, ground stations, and operations centers. The objective of this work is to provide a sound method for cryptographic encapsulation of frame data that also facilitates Layer 2 virtual channel switching, such that a mission may procure data transport services as needed without involving third parties in the cryptographic processing, or split independent data streams for separate cryptographic processing.

Biggerstaff, Craig↗

Estimating the Backup Reaction Wheel Orientation Using Reaction Wheel Spin Rates Flight Telemetry from a Spacecraft

A report describes a model that estimates the orientation of the backup reaction wheel using the reaction wheel spin rates telemetry from a spacecraft. Attitude control via the reaction wheel assembly (RWA) onboard a spacecraft uses three reaction wheels (one wheel per axis) and a backup to accommodate any wheel degradation throughout the course of the mission. The spacecraft dynamics prediction depends upon the correct knowledge of the reaction wheel orientations. Thus, it is vital to determine the actual orientation of the reaction wheels such that the correct spacecraft dynamics can be predicted. The conservation of angular momentum is used to estimate the orientation of the backup reaction wheel from the prime and backup reaction wheel spin rates data. The method is applied in estimating the orientation of the backup wheel onboard the Cassini spacecraft. The flight telemetry from the March 2011 prime and backup RWA swap activity on Cassini is used to obtain the best estimate for the backup reaction wheel orientation.

Rizvi, Farheen↗

Multimission spacecraft Dataplexer

The data multiplexing unit described is a low-power small-size building-block-type central data system designed for use on such spacecraft as the International Ultraviolet Explorer or the International Sun-Earth Explorer. Preprogrammed read-only memories are used to generate the telemetry format tailored to particular mission requirements. Low weight and low power dissipation are achieved with the aid of PMOS technology. The use of subcommutators in groups to meet particular spacecraft requirements allows low data rate experiments to be time-multiplexed into a single main input channel, to improve data collection and processing operations. The block diagram of the Dataplexer is discussed.

Cosme, R.↗

Voyager telecommunications - The broadcast from Jupiter

The means by which the data collected by the Voyager 1 mission to Jupiter were returned to earth are presented. Radio links between the earth and the spacecraft are used for the transmission of both imaging and nonimaging telemetry from the spacecraft and commands from the earth and for radiometric observations of the spacecraft and its environment. Features which have lead to vast improvements in the capability of the Voyager telecommunications system over that of previous space probes include the use of X-band rather than S-band telemetry, a dual power X-band traveling wave tube amplifier, a 3.7 m spacecraft antenna and a single channel telemetry system with concatenated coding. Communications equipment at the three ground complexes of the Deep Space Network for telemetry reception includes 64 m steerable antennas, cryogenic maser preamplifiers and a phase-lock loop receiver. Voyager 1 has met or exceeded all of its telecommunications requirements, providing a 98% data return and a total of 2 x 10 to the 11th data bits during the Jupiter encounter.

Edelson, R. E.↗

Advanced Synchrophasor Protocol (ASP) Development and Demonstration Project

The Advanced Synchrophasor Protocol Project had two main objectives: To develop, document, and demonstrate a new standard communications protocol (that became named the Streaming Telemetry Transport Protocol, or STTP) to overcome the issues being encountered in large-scale synchrophasor data system deployments using existing protocols – specifically with issues of scalability, data loss, bandwidth utilization, data access control, transport security options, and cost of configuration management, and to work with standards bodies to put STTP on a track for consideration as a standard protocol.

42 ENGINEERING↗

Landsat-1 and Landsat-2 evaluation report, 23 January 1975 to 23 April 1975

A description of the work accomplished with the Landsat-1 and Landsat-2 satellites during the period 23 Jan. - 23 Apr. 1975 was presented. The following information was given for each satellite: operational summary, orbital parameters, power subsystem, attitude control subsystem, command/clock subsystem, telemetry subsystem, orbit adjust subsystem, magnetic moment compensating assembly, unified S-band/premodulation processor, electrical interface subsystem, thermal subsystem, narrowband tape recorders, wideband telemetry subsystem, attitude measurement sensor, wideband video tape recorders, return beam vidicon, multispectral scanner subsystem, and data collection subsystem.

Source record↗

Landsat-1 and Landsat-2 flight evaluation

The flight performance of Landsat 1 and Landsat 2 is analyzed. Flight operations of the satellites are briefly summarized. Other topics discussed include: orbital parameters; power subsystem; attitude control subsystem; command/clock subsystem; telemetry subsystem; orbit adjust subsystem; magnetic moment compensating assembly; unified s-band/premodulation processor; electrical interface subsystem; thermal subsystem; narrowband tape recorders; wideband telemetry subsystem; attitude measurement sensor; wideband video tape recorders; return beam vidicon; multispectral scanner subsystem; and data collection subsystem.

Source record↗

LANDSAT-1 and LANDSAT-2 flight evaluation

Flight performances of LANDSAT 1 and LANDSAT 2 are evaluated. The in-flight systems discussed are: (1) power supplies, (2) attitude control, (3) command/clock, (4) telemetry, (5) orbit adjust, (6) electrical interface, (7) thermal, (8) tape recorders, (9) multispectral scanner, (10) data collection and (11) magnetic moment compensating assembly. Tables are presented for easy reference.

Source record↗

Microelectronics bioinstrumentation systems

Microelectronic bioinstrumentation systems to be employed in the Cardiovascular Deconditioning Program were developed. Implantable telemetry systems for long-term monitoring of animals on earth were designed to collect physiological data necessary for the understanding of the mechanisms of cardiovascular deconditioning. In-flight instrumentation systems, microelectronic instruments, and RF powering techniques for other life science experiments in the NASA program were studied.

Ko, W. H.↗

LANDSAT 4 to ground station interface description, revision 5

The radiometric requirements, internal calibration, sensor output format, geometric characteristics, and data processing constants for the LANDSAT 4 multispectral scanner and thematic mapper are described. In addition, telemetry format, onboard computer reports, and LANDSAT 4 communications are discussed.

Source record↗

LANDSAT-4 to ground station interface description

The LANDSAT 4 to ground station interface is described in detail. The radiometric specifications, internal calibration, sensor output format, and data processing constants for the multispectral scanner and the thematic mapper are discussed. The mission payload telemetry, onboard computer telemetry, and engineering telemetry formats are described. In addition, the telemetry time signals and the onboard clock resetting procedure are addressed.

Source record↗

The Swift Mission and the REM Telescope

Following a description of the science drive which originated the Swift Mission, this is US NASA MIDEX Mission with the collaboration of Italy and the UK, we will describe the status of the hardware and the observing strategy. The telemetry is carried out via the TDRSS satellite for those communications that need immediate response. The data transfer and the scheduled uploading of routine commands will be done through the ASI Malindi station in Kenia. Both in the US and in Europe a large effort will be done to follow the bursts with the maximum of efficiency and as soon as possible after the alert. We will describe how the ESO VLT telescopes are able to respond to the alert. To address the problematic of the dark bursts and to immediately follow up all of the bursts also in the Near Infrared we designed and built a 60 cm NIR Robotic telescope, REM, to be located on the ESO ground at Cerro La Silla. The instrumentation includes also a low dispersion spectrograph with the capability of multi wavelength optical photometry.

Gehrels, N.↗

Simulation Results for PCM/PM/NRZ Receivers in Non-Ideal Channels

This paper studies, by computer simulations, the performance of deep space telemetry signals that employ PCM/PM/NRZ modulation technique under the separate and combined effects of an unbalanced data stream, data asymmetry, and band-limited channel. The study is based on measuring the Symbol Error Rate (SER) performance and comparing the results to the theoretical results presented in previous reports [1,2]. Only the effects of imperfect carrier tracking due to an imperfect data stream are considered.

PCM/PM/NRS Receivers↗