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 757 records · Page 42
All sourcesNASA NTRSDOE OSTI
NASA NTRS2005

Assessment of Free-Space Lasercomm for DOD's T and E Applications

For test and evaluation of airplanes, it is desirable to telemeter large volumes of data to the ground. This telemetry has generally utilized W communication systems, which have relatively low data rates, and, due to limited spectrum availability, imposes limitations on the number of simultaneous communications in a given region. Appropriate application of optical communication technology is expected to provide higher data rate capability without the spectrum limitations of W systems, facilitating simultaneous telemetry of more data from a greater number of aircraft. This paper reviews our recent brief study to assess the insertion of free space lasercom to DOD Test and Evaluation applications.

earth image tracking↗
NASA NTRS1976

A new sequential decoder for the DSN telemetry subsystem

A sequential decoder was implemented in the DSS telemetry subsystem for the DSN MARK 3 data system implementation. This decoder performs the same decoding function as the data decoder assembly performs in the telemetry and command data handling subsystem. However, the new decoder is much faster, allowing potentially high data rates in the future.

Wilcher, J. H.↗
NASA NTRS1967

Conference on Adaptive Telemetry

Adaptive telemetry conference on adaptive data control and processing, prediction, data compression, encoding, decoding, and modulation.

TELEMETRY↗
NASA NTRS1994

The Pacor 2 expert system: A case-based reasoning approach to troubleshooting

The Packet Processor 2 (Pacor 2) Data Capture Facility (DCF) acquires, captures, and performs level-zero processing of packet telemetry for spaceflight missions that adhere to communication services recommendations established by the Consultative Committee for Space Data Systems (CCSDS). A major goal of this project is to reduce life-cycle costs. One way to achieve this goal is to increase automation. Through automation, using expert systems, and other technologies, staffing requirements will remain static, which will enable the same number of analysts to support more missions. Analysts provide packet telemetry data evaluation and analysis services for all data received. Data that passes this evaluation is forwarded to the Data Distribution Facility (DDF) and released to scientists. Through troubleshooting, data that fails this evaluation is dumped and analyzed to determine if its quality can be improved before it is released. This paper describes a proof-of-concept prototype that troubleshoots data quality problems. The Pacor 2 expert system prototype uses the case-based reasoning (CBR) approach to development, an alternative to a rule-based approach. Because Pacor 2 is not operational, the prototype has been developed using cases that describe existing troubleshooting experience from currently operating missions. Through CBR, this experience will be available to analysts when Pacor 2 becomes operational. As Pacor 2 unique experience is gained, analysts will update the case base. In essence, analysts are training the system as they learn. Once the system has learned the cases most likely to recur, it can serve as an aide to inexperienced analysts, a refresher to experienced analysts for infrequently occurring problems, or a training tool for new analysts. The Expert System Development Methodology (ESDM) is being used to guide development.

Sary, Charisse↗
DOE OSTI2024

Design and evaluation of a low-cost sensor node for near-background methane measurement

Abstract. We developed a low-cost methane sensing node incorporating two metal oxide (MOx) sensors (Figaro Engineering TGS2611-E00 and TGS2600), humidity and temperature sensing, data storage, and telemetry. We deployed the prototype sensor alongside a reference methane analyzer at two sites: one outdoors and one indoors. We collected data at each site for several months across a range of environmental conditions (particularly temperature and humidity) and methane levels. We explored calibration models to investigate the performance of our system and its suitability for methane background monitoring and enhancement detection, first selecting a linear regression to fit a sensor baseline response and then fitting methane response by the sensor deviation from baseline. We achieved moderate accuracy in a 2 to 10 ppm methane range compared to data from the reference analyzer (RMSE < 0.6 ppm), but we found that the sensor response varied over time, possibly as a result of changes in non-targeted gas concentrations. We suggest that this cross sensitivity may be responsible for mixed results in previous studies. We discuss the implications of our results for the use of these and similar inexpensive MOx sensors for methane monitoring in the 2 to 10 ppm range.

Furuta, Daniel↗
NASA NTRS1999

Work on Planetary Atmospheres and Planetary Atmosphere Probes

A summary final report of work accomplished is presented. Work was performed in the following areas: (1) Galileo Probe science analysis, (2) Galileo probe Atmosphere Structure Instrument, (3) Mars Pathfinder Atmosphere Structure/Meteorology instrument, (4) Mars Pathfinder data analysis, (5) Science Definition for future Mars missions, (6) Viking Lander data analysis, (7) winds in Mars atmosphere Venus atmospheric dynamics, (8) Pioneer Venus Probe data analysis, (9) Pioneer Venus anomaly analysis, (10) Discovery Venus Probe Titan probe instrument design, and (11) laboratory studies of Titan probe impact phenomena. The work has resulted in more than 10 articles published in archive journals, 2 encyclopedia articles, and many working papers. This final report is organized around the four planets on which there was activity, Jupiter, Mars, Venus, and Titan, with a closing section on Miscellaneous Activities. A major objective was to complete the fabrication, test, and evaluation of the atmosphere structure experiment on the Galileo probe, and to receive, analyze and interpret data received from the spacecraft. The instrument was launched on April 14, 1989. Calibration data were taken for all experiment sensors. The data were analyzed, fitted with algorithms, and summarized in a calibration report for use in analyzing and interpreting data returned from Jupiter's atmosphere. The sensors included were the primary science pressure, temperature and acceleration sensors, and the supporting engineering temperature sensors. Computer programs were written to decode the Experiment Data Record and convert the digital numbers to physical quantities, i.e., temperatures, pressures, and accelerations. The project office agreed to obtain telemetry of checkout data from the probe. Work to extend programs written for use on the Pioneer Venus project included: (1) massive heat shield ablation leading to important mass loss during entry; and (2) rapid planet rotation, which introduced terms of motion not needed on Venus. When the Galileo Probe encountered Jupiter, analysis and interpretation of data commenced. The early contributions of the experiment were to define (1) the basic structure of the deep atmosphere, (2) the stability of the atmosphere, (3) the upper atmospheric profiles of density, pressure, and temperature. The next major task in the Galileo Probe project was to refine, verify and extend the analysis of the data. It was the verified, and corrected data, which indicated a dry abiabatic atmosphere within measurement accuracy. Temperature in the thermosphere was measured at 900 K. Participation in the Mars atmospheric research included: (1) work as a team member of the Mars Atmosphere Working Group, (2) contribution to the Mars Exobiology Instrument workshop, (3) asssistance in planning the Mars global network and (4) assitance in planning the Soviet-French Mars mission in 1994. This included a return to the Viking Lander parachute data to refine and improve the definition of winds between 1.5 and 4 kilometer altitude at the two entry sites. The variability of the structure of Mars atmosphere was addressed, which is known to vary with season, latitude, hemisphere and dust loading of the atmosphere. This led to work on the Pathfinder project. The probe had a deployable meteorology mast that had three temperature sensors, and a wind sensor at the tip of the mast. Work on the Titan atmospheric probe was also accomplished. This included developing an experiment proposal to the European Space Agency (ESA), which was not selected. However, as an advisor in the design and preparation of the selected experiment the researcher interacted with scientist on the Huygens Probe Atmosphere Structure Experiment. The researcher also participated in the planning for the Venus Chemical Probe. The science objectives of the probe were to resolve unanswered questions concerning the minor species chemistry of Venus' atmosphere that control cloud formation, greenhouse effectiveness, and the thermal structure. The researcher also reviewed problems with the Pioneer Venus Probe, that caused anomalies which occurred on the Probes at and below 12.5 km level of the Venus' atmosphere. He convened and participated in a workshop that concluded the most likely hardware cause was insulation failure in the electrical harness outside the Probes' pressure vessels. It was discovered that the shrink tubing material failed at 600K. This failure could explain the anomalies experienced by the probes. The descent data of the Pioneer probes, and the Soviet Vega Lander was analyzed to evaluate the presence of small scale gravity waves in and below the Venus cloud layer.

Lester, Peter↗
NASA NTRS1985

Determining Availability Characteristics of DSN Data Systems Using Discrepancy Report Data

A reasonably economical way was developed to determine availability characteristics of Deep Space Network (DSN) data systems, subsystems, and assemblies using the DSN discrepancy report (DR) data base and DSN operating schedule and history data bases. Operating mean time between failures (OMTBF), operating mean time to restore service (OMTTRS), and operating functional availability (OFA) can be computed by year, by system, by subsystem, by assembly, and by station. The effort required to produce the desired reports is described, specific data on the telemetry, command, and tracking systems are presented, and major contributors to system outages are identified. Future improvements in preparing and analyzing DR data are also outlined to enhance their use in correcting conditions that lead to outages.

Ruskin, A. M.↗
NASA NTRS1988

Data Transport Subsystem - The SFOC glue

The design and operation of the Data Transport Subsystem (DTS) for the JPL Space Flight Operation Center (SFOC) are described. The SFOC is the ground data system under development to serve interplanetary space probes; in addition to the DTS, it comprises a ground interface facility, a telemetry-input subsystem, data monitor and display facilities, and a digital TV system. DTS links the other subsystems via an ISO OSI presentation layer and an LAN. Here, particular attention is given to the DTS services and service modes (virtual circuit, datagram, and broadcast), the DTS software architecture, the logical-name server, the role of the integrated AI library, and SFOC as a distributed system.

Parr, Stephen J.↗
NASA NTRS1995

A simple method for verifying the deployment of the TOMS-EP solar arrays

The Total Ozone Mapping Spectrometer-Earth Probe (TOMS-EP) mission relies upon a successful deployment of the spacecraft's solar arrays. Several methods of verification are being employed to ascertain the solar array deployment status, with each requiring differing amounts of data. This paper describes a robust attitude-independent verification method that utilizes telemetry from the coarse Sun sensors (CSS's) and the three-axis magnetometers (TAM's) to determine the solar array deployment status - and it can do so with only a few, not necessarily contiguous, points of data. The method developed assumes that the solar arrays are deployed. Telemetry data from the CSS and TAM are converted to the Sun and magnetic field vectors in spacecraft body coordinates, and the angle between them is calculated. Deployment is indicated if this angle is within a certain error tolerance of the angle between the reference Sun and magnetic field vectors. Although several other methods can indicate a non-deployed state, with this method there is a 70% confidence level in confirming deployment as well as a nearly 100% certainty in confirming a non-deployed state. In addition, the spacecraft attitude (which is not known during the first orbit after launch) is not needed for this algorithm because the angle between the Sun and magnetic field vectors is independent of the spacecraft attitude. This technique can be applied to any spacecraft with a TAM and with CSS's mounted on the solar array(s).

Koppersmith, James R.↗
NASA NTRS1966

Apollo network

Although the design of the Apollo network followed closely behind the Manned Space Flight Network (MSFN) modification for the Gemini program, many site modifications were necessary to provide Apollo support due to the greater scope of the Apollo program. The Apollo program requires instrumentation for support of the S-I, S-11, S IV-B/IU, Command Service Module (CSM) and Lunar Excursion Module (LEM) stages. Command Service Module (CSM) and Lunar Excursion Module (LEM) stages. Support must also be provided at both orbital and lunar distances. Increased data processing capability is required for processing and displaying significantly larger amounts of information. The ground network requires the capability of processing both Pulse Code Modulation (PCM) telemetry and command data for the CSM, LEM, and S IV-B/IU. In various stages of the Apollo program, both tone (on UHF) and digital [on Unified S-Band (USB) and UHF] command capabilities are required. Also at various stages both USB and VHF telemetry links are required.

Ground support system↗
NASA NTRS1982

NASA Deep Space Network operating control

The primary function of the Deep Space Network (DSN) is to provide effective and reliable tracking and data acquisition for planetary and interplanetary space flight missions. This involves providing data to flight project mission operations, accepting commands from mission operations and transmitting the commands to stations and spacecraft, and providing a record of telemetry and command data to mission operations. Also included are network performance monitoring, the generation of predictions for antenna pointing and signal acquisition, network scheduling, and network validation tests. Descriptions are given of the three facilities and six systems of the DSN. Also described are interfaces, automation and standardized procedures, and discrepancy reporting. It is pointed out that the greatest challenge facing the DSN is the implementation of NASA's Network Consolidation Program, which is scheduled to be completed in 1986. The objectives of this program are enumerated.

Weisman, W. D.↗
NASA NTRS2001

Gamma Ray Large Area Space Telescope (GLAST) Balloon Flight Engineering Model: Overview

The Gamma Ray Large Area Space Telescope (GLAST) Large Area Telescope (LAT) is a pair-production high-energy (greater than 20 MeV) gamma-ray telescope being built by an international partnership of astrophysicists and particle physicists for a satellite launch in 2006, designed to study a wide variety of high-energy astrophysical phenomena. As part of the development effort, the collaboration has built a Balloon Flight Engineering Model (BFEM) for flight on a high-altitude scientific balloon. The BFEM is approximately the size of one of the 16 GLAST-LAT towers and contains all the components of the full instrument: plastic scintillator anticoincidence system (ACD), high-Z foil/Si strip pair-conversion tracker (TKR), CsI hodoscopic calorimeter (CAL), triggering and data acquisition electronics (DAQ), commanding system, power distribution, telemetry, real-time data display, and ground data processing system. The principal goal of the balloon flight was to demonstrate the performance of this instrument configuration under conditions similar to those expected in orbit. Results from a balloon flight from Palestine, Texas, on August 4, 2001, show that the BFEM successfully obtained gamma-ray data in this high-background environment.

Thompson, D. J.↗
NASA NTRSDate not supplied

Independent Verification and Validation for Artemis I Ascent Integrated Flight Performance Simulation

The NASA Engineering and Safety Center (NESC) has performed independent model development to support cross-model verification for the Space Launch System (SLS) Program since 2012 which culminated, for Artemis I, in a postflight reconciliation analysis of the Artemis I ascent trajectory (validation). This post-flight analysis was completed by both the NESC and the SLS Program. Upon successful completion of the Artemis I mission, multiple preflight simulations of the nominal ascent trajectory were updated with Day of Launch (DOL) conditions and simulated results were compared to reconstructed flight data derived from telemetry measurements. Dispersed trajectories were also produced using a combination of DOL conditions and preflight uncertainties, which ideally should bound the Artemis I flight data. Finally, multibody dynamics were simulated for some of the separation events to support clearance analyses. This paper focuses on validating and understanding the accuracy of the models by comparing simulated results against the Artemis I flight data. In addition, discrepancies uncovered between simulations led to opportunities to investigate areas for potential model improvement to refine preflight simulations for future Artemis missions. Included in this paper is background on the flight performance simulation tools, the postflight analysis approach, and a comparison of simulation results against the Artemis I flight data. Simulated results were found to generally be in close agreement with each other and the Artemis I flight data.

Jacob Fleck↗
NASA NTRS1982

Deep space payload launches via the Space Transportation System

The launching of deep space payloads via the Space Shuttle vehicle of the Space Transportation System, rather than via expendable launch vehicles, is described. Changes in procedures and data flow configurations for both the flight project and DSN during the launch period are required. A typical Galileo launch period sequence of events and telemetry and command data flow configurations are described.

Berman, A. L.↗