Search NASA⌕ Search

SEARCH · Search NASA

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

Message Brokering Evaluation for Live Spacecraft Telemetry Monitoring, Recorded Playback, and Analysis

Live monitoring and post-flight analysis of telemetry data play a vital role in the development, diagnosis, and deployment of components of a space flight mission. Requirements for such a system include low end-to-end latency between data producers and visualizers, preserved ordering of messages, data stream archiving with random access playback, and real-time creation of derived data streams. We evaluate the RabbitMQ and Kafka message brokering systems, on how well they can enable a real-time, scalable, and robust telemetry framework that delivers telemetry data to multiple clients across heterogeneous platforms and flight projects. In our experiments using an actively developed robotic arm testbed, Kafka yielded a much higher message throughput rate and a consistent publishing rate across the number of topics and consumers. Consumer message rates were consistent across the number of topics but can exhibit bursty behavior with an increase in the contention for a single topic partition with increasing number of consumers.

Lee, Daren↗
NASA NTRS2018

Use of Nack Oriented Reliable Multicast (NORM) Protocol for Transport of Spacecraft Telemetry in Ground Networks

Frequently it is necessary to distribute spacecraft telemetry to multiple destinations on Internet Protocol (IP) networks. There are various methods of delivering this data, but when the data is high rate and there are many destinations IP multicast provides the best solution from a network perspective. However, IP multicast only supports the User Datagram Protocol (UDP) which is connectionless and unreliable. This nature of UDP and by extension the low priority treatment of UDP packets by some network hardware creates a difficult environment for distribution of high rate telemetry to a number of recipients over IP networks. NACK (Negative ACKnowledgment) Oriented Reliable Multicast (NORM) is defined by IETF (Internet Engineering Task Force) RFC (Request for Comments) 5740 in 2009 by B. Adamson et al. NORM provides a mechanism of retransmission and or forward error correction for UDP packets, potentially overcoming the limits of UDP for the transmission of spacecraft telemetry. Marshall Space Flight Center’s (MSFC) Huntsville Operations Support Center (HOSC) manages the delivery of the International Space Station (ISS) payload science and health data. The ISS IP Ground Routed (IIGoR) network provides the delivery of the data from the ground stations to the control centers. HOSC personnel have been experimenting with the use of NORM on the link between the ground stations and the front end processor equipment in Huntsville, AL.

Baldwin, Patrick A.↗
NASA NTRS2018

Software Development and Testing Support for the Avionics Systems Telemetry Tool Suite

The Customer Avionics Interface Development and Analysis (CAIDA) team helps to provide modeling and simulation software for the verification of the Launch Control System (LCS). With a new iteration of telemetry tools being developed, extensive work must be done to ensure features are implemented in an efficient manner. The authors worked to develop new functionalities in the telemetry tools, update documentation, and perform various tests on the CAIDA Advanced Telemetry Tool (CATT). This was accomplished with Python through built-in library frameworks. In addition, work needed to be performed to set up a training document for new engineers and interns joining the team in the future. The outcome of this internship was the completion of several new features, unit and functional tests on CATT, thorough documentation, and a developer’s guide to programming under CAIDA.

Negron-Martinez, Antonio Jose↗
NASA NTRS1965

The Telemetry System

Design and operation of signal conditioner, telemetry encoder and transmitter, and antenna for Relay I telemetry system

RELAY I SATELLITE↗
NASA NTRS1965

Telemetry computer studies

Special purpose computers to process telemetry data and to control experiments on small telemetry satellites

COMPUTER METHOD↗
NASA NTRS2000

PTEP: the Parallel Telemetry Processor

The Parallel Telemetry Processor (PTEP), a high-speed, robust, and extensible telemetry processing system is discussed in this paper.

downloading telemetry processing operations↗
NASA NTRS2001

Telemetry, tracking, and command consolidation in the Deep Space Network

Currently, in NASA's Deep Space Network (DSN), telemetry, tracking, and command (TT&C) functions are distributed between multiple subsystem computers. Control design of these subsystems did not consider the interaction necessary between the functions, which create opportunities for loss of data. Also, the current controller design can force the use of equipment that is not needed for the task at hand, to the detriment of others. As part of the Network Simplification Project (NSP), the TTC implementation has been re-examined, New telemetry and commanding equipment is being built, and the control of the TT&C functions is being consolidated into two controllers, Uplink and Downlink. The new equipment uses commercial components, as opposed to the custom built equipment it is replacing, which improves reliability and simplifies maintenance.

tracking↗
NASA NTRS2006

A Whale of a Tale: Creating Spacecraft Telemetry Data Analysis Products for the Deep Impact Mission

This paper describes some of the challenges and lessons learned from the Deep Impact (DI) Mission Ground Data System's (GDS) telemetry data processing and product generation tool, nicknamed 'Whale.' One of the challenges of any mission is to analyze testbed and operational telemetry data. Methods to retrieve this data to date have required spacecraft subsystem members to become experts in the use of a myriad of query and plot tools. As budgets shrink, and the GDS teams grow smaller, more of the burden to understand these tools falls on the users. The user base also varies from novice to expert, and requiring them to become GDS tool experts in addition to spacecraft domain experts is an undue burden. The "Whale" approach is to process all of the data for a given spacecraft test, and provide each subsystem with plots and data products 'automagically.'.

Deep Impact↗
NASA NTRS2008

Architecture Study on Telemetry Coverage for Immediate Post-Separation Phase

This document is the viewgraphs that accompanies a paper that presents the preliminary results of an architecture study that provides continuous telemetry coverage for NASA missions for immediate post-separation phase. After launch when the spacecraft separated from the upper stage, the spacecraft typically executes a number of mission-critical operations prior to the deployment of solar panels and the activation of the primary communication subsystem. JPL, GSFC, and APL have similar design principle statements that require continuous coverage of mission-critical telemetry during the immediate post-separation phase. To conform to these design principles, an architecture that consists of a separate spacecraft transmitter and a robust communication network capable of tracking the spacecraft signals is needed. The main results of this study are as follows: 1) At low altitude (< 10000 km) when most post-separation critical operations are executed, Earth-based network (e.g. Deep Space Network (DSN)) can only provide limited coverage, whereas space-based network (e.g. Space Network (SN)) can provide continuous coverage. 2) Commercial-off-the-shelf SN compatible transmitters are available for small satellite applications. In this paper we present the detailed coverage analysis of Earth-based and Space-based networks. We identify the key functional and performance requirements of the architecture, and describe the proposed selection criteria of the spacecraft transmitter. We conclude the paper with a proposed forward plan.

architecture↗
NASA NTRS2013

Using Onboard Telemetry for MAVEN Orbit Determination

Determination of the spacecraft state has been traditional done using radiometric tracking data before and after the atmosphere drag pass. This paper describes our approach and results to include onboard telemetry measurements in addition to radiometric observables to refine the reconstructed trajectory estimate for the Mars Atmosphere and Volatile Evolution Mission (MAVEN). Uncertainties in the Mars atmosphere models, combined with non-continuous tracking degrade navigation accuracy, making MAVEN a key candidate for using onboard telemetry data to help complement its orbit determination process.

orbit determination↗
NASA NTRS2009

Ka-Band High-Rate Telemetry System Upgrade for the NASA Deep Space Network

The NASA Deep Space Network (DSN) has a new requirement to support high-data-rate Category A (Cat A) missions (within 2 million kilometers of Earth) with simultaneous S-band uplink, S-band downlink and Ka-band downlink. The S-band links are required for traditional TT&C (Telemetry, Tracking, and Command) support to the spacecraft, while the Ka-band link is intended for high-data-rate science returns. The new Ka-band system combines the use of proven DSN cryogenic designs, for low system temperature, and high data rate capability using commercial telemetry receivers. The initial Cat A support is required for the James Webb Space Telescope (JWST) in 2013 and possibly other missions. The upgrade has been implemented into 3 different 34-meter Beam Waveguide (BWG) antennas in the DSN, one at each of the complexes in Canberra (Australia), Goldstone (California) and Madrid (Spain). System test data is presented to show that the requirements were met and the DSN is ready for Cat A Ka-band operational support.

space communications↗
NASA NTRS2015

Applied Multi-Mission Telemetry Processing and Display for Operations, Integration, Training, Playback and Event Reconstruction

Conveying spacecraft health and status information to mission engineering personnel during various mission phases, including mission operations, is a requirement to achieve a successful mission. For NASA/JPL spacecraft, that often means displaying hundreds of telemetry channels from a variety of sensors and components emitting data at rates varying from 1hz-100hz (and faster) in a way that allows the operations team to quickly evaluate the health of the vehicle, identify any off-nominal states and resolve any issues. In this paper we will discuss the system design, requirements and use cases of three telemetry processing and visualization systems recently developed and deployed by our team for NASA's Low Density Supersonic Decelerator (LDSD) test vehicle, NASA's Soil Moisture Active/Passive (SMAP) orbiter, and JPL's Sampling Lab Universal Robotic Manipulator (SLURM) test bed.

simulation↗
NASA NTRSDate not supplied

What is the Future of Telemetry at Armstrong Flight Research Center?

Armstrong Flight Research Center executes aeronautical research and development for NASA. Telemetry is a key data component used to validate the R&D process and more importantly provide a critical safety element. This presentation will offer information that supports efforts to investigate the Future of Telemetry at a Test Range, specifically AFRC.

Telemetry↗
DOE OSTI2024

Tracking animal movements via collaborative acoustic telemetry networks: Multiscale habitat use, phenology, and management insights

Abstract Estuaries support diverse fish and invertebrate communities, including resident species that rely on estuarine habitats year‐round and transient migratory species. The unique movement patterns of these animals connect habitats within and far beyond the estuary and are integrally linked to fisheries management objectives. With a focus on Chesapeake Bay, this study leveraged data from collaborative acoustic telemetry networks in the northwest Atlantic to assess habitat use and phenology of movements for seven species of fish (cownose rays, dusky sharks, smooth dogfish, alewife, striped bass, common carp, and blue catfish) and one invertebrate (horseshoe crabs). A total of 288 acoustically tagged individuals were detected >3.2 million times (6,743 to 2,095,717 detections per species) on receivers across ~20.5 degrees of latitude spanning the North American Atlantic seaboard from Florida, USA, to New Brunswick, Canada. Common metrics of movement and phenology grouped these species as resident (common carp, blue catfish, horseshoe crabs), primarily resident in estuaries (juvenile striped bass), and coastal migrant (cownose rays, dusky sharks, smooth dogfish, alewife); maximum distance traveled varied by three orders of magnitude among these species. Further analysis of phenology for coastal migrants elucidated the timing and duration of these species' use of Chesapeake Bay. Collectively, movements linked habitats within Chesapeake Bay and connected the estuary to coastal ecosystems both to the north (e.g., alewife) and south (e.g., cownose rays), creating networks of fisheries management jurisdictions that varied in complexity and identified opportunities for enhancement to current management or co‐management of some species. Our results elucidate the importance of estuaries to species with diverse movement behaviors, identify scales and pathways of habitat connectivity via animal movements, and highlight the utility of collaborative acoustic telemetry networks for quantifying movements relevant to both ecological research and fisheries management.

Livernois, Mariah C.↗
DOE OSTI2024

Collection And Analysis Of Telemetry For The Cyote Heuristic

CATCH CLI focuses on gathering telemetry data, storing it in the Neo4j database, querying for Mitre ATT&CK patterns, and creating STIX 2.1 reports. Key Components: Analysis Modules: Analyze data to detect attack patterns. GoSTOTS Collection Engines: Collect telemetry data. These tools can be used together or individually. Analysis modules rely on data from specific engines to identify attack patterns. Source Code Organization: Engines: CATCH/catch/cmd/collection Modules: CATCH/catch/cmd/analysis CGUI Overview CATCH Graphical User Interface (CGUI) offers a graphical shell to execute CATCH CLI, allowing easy editing of: Analysis Modules Database configurations Profiles (collection and device settings) Neo4j Overview Neo4j is a graph database using the Cypher query language, storing data in JSON. It seamlessly integrates with STIX 2.1 data for: Data Submission: CATCH Collection Engines Data Querying: Analysis Modules CATCH modifies STIX 2.1 data for Neo4j submission and reverts it back during querying. STIG Overview Structured Threat Intelligence Graph (STIG) is a tool for creating, editing, querying, analyzing, and visualizing threat intelligence using STIX 2.1 and storing data in Neo4j. Usage Tools can be run: Manually (CLI): Refer to CATCH documentation User Interface: Run ./cgui/CGUI or go run ./cgui/ Additional Information Logging System: Detailed in the config documentation Further Documentation: Available for CATCH and CGUI

Madsen, MichaelJ. [Idaho National Laboratory (INL)↗