Search NASA⌕ Search

SEARCH · Search NASA

Results for “spacecraft data interfaces”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

AstroDOME: Standardized, Mass-Produceable, Small NASA Astrophysics Observatories for Big Missions

NASA’s Goddard Space Flight Center is investigating the use of small, commercial off the shelf (COTS) spacecraft to enable breakthrough astrophysics research at radically reduced cost over previous generations of missions. This paper will focus on the Mission Systems perspective of this investigation. It will cover the spacecraft to instrument interface, and lessons learned in early concept payload development. Low-cost COTS spacecraft have proliferated in the last ~5 years. They represent an order of magnitude reduction in the cost of spacecraft bus development and acquisition. They are enabled by the advent of low-cost smallsat launch options in the immediately preceding years, and are seeded by recent distributed and disaggregated missions in other sectors such as telecommunications megaconstellations (e.g. Starlink, OneWeb, Project Kuiper) and ongoing Space Development Agency (SDA) developments. Our study was tasked with developing a standardized, mass-produceable, astrophysics payload which is reconfigurable to different wavelength bands while maintaining a single optics bench design, and a standardized mechanical, electrical, data, and thermal interface to the spacecraft bus, and which may be reconfigured to multiple COTS spacecraft offerings. In this paper we will discuss lessons learned from our case study. We will also present identified keys to mission success for performing cutting edge astrophysics observations while taking advantage of economies of scale with a disaggregated, standardized architecture.

Matthew Marcus↗
NASA NTRS1999

International Ultraviolet Explorer (IUE) Battery History and Performance

The "International Ultraviolet Explorer (IUE) Battery History and Performance" report provides the information on the cell/battery design, battery performance during the thirty eight (38) solar eclipse seasons and the end-of-life test data. It is noteworthy that IUE spacecraft was an in-house project and that the batteries were designed, fabricated and tested (Qualification and Acceptance) at the Goddard Space Flight Center. A detailed information is given on the cell and battery design criteria and the designs, on the Qualification and the Acceptance tests, and on the cell life cycling tests. The environmental, thermal, and vibration tests were performed on the batteries at the battery level as well as with the interface on the spacecraft. The telemetry data were acquired, analyzed, and trended for various parameters over the mission life. Rigorous and diligent battery management programs were developed and implemented from time to time to extend the mission life over eighteen plus years. Prior to the termination of spacecraft operation, special tests were conducted to check the battery switching operation, battery residual capacity, third electrode performance and battery impedance.

Rao, Gopalskrishna M.↗
NASA NTRS1998

Statistical Treatment of Earth Observing System Pyroshock Separation Test Data

The Earth Observing System (EOS) AM-1 spacecraft for NASA's Mission to Planet Earth is scheduled to be launched on an Atlas IIAS vehicle in June of 1998. One concern is that the instruments on the EOS spacecraft are sensitive to the shock-induced vibration produced when the spacecraft separates from the launch vehicle. By employing unique statistical analysis to the available ground test shock data, the NASA Lewis Research Center found that shock-induced vibrations would not be as great as the previously specified levels of Lockheed Martin. The EOS pyroshock separation testing, which was completed in 1997, produced a large quantity of accelerometer data to characterize the shock response levels at the launch vehicle/spacecraft interface. Thirteen pyroshock separation firings of the EOS and payload adapter configuration yielded 78 total measurements at the interface. The multiple firings were necessary to qualify the newly developed Lockheed Martin six-hardpoint separation system. Because of the unusually large amount of data acquired, Lewis developed a statistical methodology to predict the maximum expected shock levels at the interface between the EOS spacecraft and the launch vehicle. Then, this methodology, which is based on six shear plate accelerometer measurements per test firing at the spacecraft/launch vehicle interface, was used to determine the shock endurance specification for EOS. Each pyroshock separation test of the EOS spacecraft simulator produced its own set of interface accelerometer data. Probability distributions, histograms, the median, and higher order moments (skew and kurtosis) were analyzed. The data were found to be lognormally distributed, which is consistent with NASA pyroshock standards. Each set of lognormally transformed test data produced was analyzed to determine if the data should be combined statistically. Statistical testing of the data's standard deviations and means (F and t testing, respectively) determined if data sets were significantly different at a 95-percent confidence level. If two data sets were found to be significantly different, these families of data were not combined for statistical purposes. This methodology produced three separate statistical data families of shear plate data. For each population, a P99.1/50 (probability/confidence) per-separation-nut firing level was calculated. By using the binomial distribution, Lewis researchers determined that this pernut firing level was equivalent to a P95/50 per-flight confidence level. The overall envelope of the per-flight P95/50 levels led to Lewis' recommended EOS interface shock endurance specification. A similar methodology was used to develop Lewis' recommended EOS mission assurance levels. The available test data for the EOS mission are significantly larger than for a normal mission, thus increasing the confidence level in the calculated expected shock environment. Lewis significantly affected the EOS mission by properly employing statistical analysis to the data. This analysis prevented a costly requalification of the spacecraft's instruments, which otherwise would have been exposed to significantly higher test levels.

McNelis, Anne M.↗
NASA NTRS1973

System design of the Pioneer Venus spacecraft. Volume 2: Science

The objectives of the low-cost Pioneer Venus space probe program are discussed. The space mission and science requirements are analyzed. The subjects considered are as follows: (1) the multiprobe mission, (2) the orbiter mission, (3) science payload accomodations, and (4) orbiter spacecraft experimental interface specifications. Tables of data are provided to show the science allocations for large and small probes. Illustrations of the systems and components of various probe configurations are included.

Acheson, L. K.↗
NASA NTRS1982

Spacecraft radio frequency subsystem

The historical background for the development of the planetary (RFS) is reviewed, and the performance capabilities of the various functional subassemblies are described. The flight radio frequency subsystem is a valid component for the three spacecraft telecommunications functions of tracking, command, and telemetry. It is the radio and the signal processing equipment residing in the spacecraft that interfaces with the control & data subsystem and performs two-way communications with the Earth-based Deep Space Network. The RFS consists of all the elements for RF reception, demodulation, modulation, and transmission, including those for command detection and telemetry modulation.

Tam, M. K.↗
NASA NTRS2018

Radio-hosted Flight / Ground Interface for Operations Standardization

The interface between a spacecraft and its ground operations segment includes the flow of commands, configuration, and sequencing elements to the spacecraft, and the flow of telemetry and data products from the spacecraft. Creating and implementing a complete definition of this interface simplifies and standardizes mission operations, allowing easy sharing of operations personnel across missions. Early spacecraft featured a simple flight / ground interface (FGI) using hardware command decoding in the radio, driven by technological limitations of the time. Modern spacecraft use command and data handling (CDH) avionics on which flight software executes, which in turn controls and configures the mission, executes subsystem and instrument instructions, and implements critical fault protection actions. Deep space missions feature advanced operations software for running sequenced activities over a period of weeks, which allows them to function with only infrequent ground contact. This approach comes at the cost of increased complexity in the FGI, requiring expensive modifications to heritage flight software and ground systems. By hosting the interface in the radio instead of the CDH avionics, modern missions can approximate the FGI design simplicity of early spacecraft, with significant advantages for vendor competition, lowered costs, standardization of operations, and reduction of implementation risk.

Lock, Patricia D.↗
NASA NTRS1993

Clementine Sensor Processing System

The design of the DSPSE Satellite Controller (DSC) is baselined as a single-string satellite controller. The DSC performs two main functions: health and maintenance of the spacecraft; and image capture, storage, and playback. The DSC contains two processors: a radiation-hardened Mil-Std-1750, and a commercial R3000. The Mil-Std-1750 processor performs all housekeeping operations, while the R3000 is mainly used to perform the image processing functions associated with the navigation functions, as well as performing various experiments. The DSC also contains a data handling unit (DHU) used to interface to various spacecraft imaging sensors and to capture, compress, and store selected images onto the solid-state data recorder. The development of the DSC evolved from several key requirements; the DSPSE satellite was to do the following: (1) have a radiation-hardened spacecraft control system and be immune to single-event upsets (SEU's); (2) use an R3000-based processor to run the star tracker software that was developed by SDIO (due to schedule and cost constraints, there was no time to port the software to a radiation-hardened processor); and (3) fly a commercial processor to verify its suitability for use in a space environment. In order to enhance the DSC reliability, the system was designed with multiple processing paths. These multiple processing paths provide for greater tolerance to various component failures. The DSC was designed so that all housekeeping processing functions are performed by either the Mil-Std-1750 processor or the R3000 processor. The image capture and storage is performed either by the DHU or the R3000 processor.

Feldstein, A. A.↗
NASA NTRS2012

Lunar Reconnaissance Orbiter (LRO) Command and Data Handling Flight Electronics Subsystem

A document describes a high-performance, modular, and state-of-the-art Command and Data Handling (C&DH) system developed for use on the Lunar Reconnaissance Orbiter (LRO) mission. This system implements a complete hardware C&DH subsystem in a single chassis enclosure that includes a processor card, 48 Gbytes of solid-state recorder memory, data buses including MIL-STD-1553B, custom RS-422, SpaceWire, analog collection, switched power services, and interfaces to the Ka-Band and S-Band RF communications systems. The C&DH team capitalized on extensive experience with hardware and software with PCI bus design, SpaceWire networking, Actel FPGA design, digital flight design techniques, and the use of VxWorks for the real-time operating system. The resulting hardware architecture was implemented to meet the LRO mission requirements. The C&DH comprises an enclosure, a backplane, a low-voltage power converter, a single-board computer, a communications interface board, four data storage boards, a housekeeping and digital input/output board, and an analog data acquisition board. The interfaces between the C&DH and the instruments and avionics are connected through a SpaceWire network, a MIL-STD-1553 bus, and a combination of synchronous and asynchronous serial data transfers over RS-422 and LVDS (low-voltage differential-signaling) electrical interfaces. The C&DH acts as the spacecraft data system with an instrument data manager providing all software and internal bus scheduling, ingestion of science data, distribution of commands, and performing science operations in real time.

Nguyen, Quang↗
NASA NTRS2004

Open-systems Architecture of a Standardized Command Interface Chip-set for Switching and Control of a Spacecraft Power Bus

This viewgraph presentation reviews the architecture of the The CIA-AlA chip-set is a set of mixed-signal ASICs that provide a flexible high level interface between the spacecraft's command and data handling (C&DH) electronics and lower level functions in other spacecraft subsystems. Due to the open-systems architecture of the chip-set including an embedded micro-controller a variety of applications are possible. The chip-set was developed for the missions to the outer planets. The chips were developed to provide a single solution for both the switching and regulation of a spacecraft power bus. The Open-Systems Architecture allows for other powerful applications.

power switch slice (PSS)↗
NASA NTRS1978

The NASA Standard Telemetry and Command Components /STACC/

The Standard Telemetry and Command Components (STACC) were conceived by NASA for use on the Multimission Modular Spacecraft. The components have wider application, however, and already are being considered for many other spacecraft. A programmable Central Unit controls Remote Interface Units via a full duplex data bus, providing data acquisition and command distribution capability throughout the spacecraft. The Central Unit can meet any uplink, time code, and format requirements without hardware changes. Each remote unit can acquire any type of data (serial digital, bi-level, analog, or passive analog) on any channel. A third type of unit is an optional interface providing I/O capability to an on-board computer. The protocols used on the 1Mbps data bus are compatible with MSFC's 'Standard Interfaces for Digital Data, Multiplex Serial Data Acquisition and Distribution Systems (SIDD/MSDADS Standard)'. The bus design saves significant harness weight and simplifies the single point ground and isolation approaches.

Elliott, N. P.↗
NASA NTRSDate not supplied

RadLab and the Environmental Data Application Dashboard: Graphical and Programming Interfaces for Interrogation of Space Telemetry Data

Sensors on the International Space Station (ISS) and multiple spacecraft elsewhere in Earth orbit and in deep space continuously monitor and collect environmental data, transmitting this information back to Earth. These data include ionizing radiation and, on the ISS, CO2, relative humidity levels, and temperature, and are of great importance to space biology research. Ionizing radiation in particular has been established in ground-based experiments as being correlated with increased risk of carcinogenesis and cardiovascular and neurological effects. Looking ahead to future long duration crewed missions beyond low Earth orbit, the ability to study how factors including CO2 levels, light cycle, temperature modulate the response to ionizing radiation and microgravity is essential. To date, access to these data has been fragmented across space agencies, spacecraft, and databases. To address this issue, NASA’s Open Science Data Repository (osdr.nasa.gov) has developed two Web applications: the Environmental Data Application (EDA) and a radiation-specific RadLab. Each consists of an API (application programming interface) and an associated GUI (graphical user interface) that provide single points of access to the data. To date, OSDR has focused on the sensors from payloads and radiation detectors located on the ISS. The Web applications process telemetry information and associated data, such as spacecraft location and orientation, from multiple international databases. The applications’ request syntax enables users to interrogate these data by craft, sensor type, time range, radiation type (galactic cosmic rays, solar particle events, the contribution of the South Atlantic Anomaly), facilitating arbitrary comparisons of original source data at varying time resolutions. The applications provide programmatic access for use in computational pipelines and GUIs for data visualization and exploration, making these data FAIR (Findable, Accessible, Interoperable, and Reusable), complementing the biological data contained in OSDR, and providing the space science community with a valuable resource for scientific analyses.

radiation↗
NASA NTRS1975

Automatic control of a primary electric thrust subsystem

A concept for automatic control of the thrust subsystem has been developed by JPL and participating NASA Centers. This paper reports on progress in implementing the concept at JPL. Control of the Thrust Subsystem (TSS) is performed by the spacecraft computer command subsystem, and telemetry data is extracted by the spacecraft flight data subsystem. The Data and Control Interface Unit, an element of the TSS, provides the interface with the individual elements of the TSS. The control philosophy and implementation guidelines are presented. Control requirements are listed, and the control mechanism, including the serial digital data intercommunication system, is outlined. The paper summarizes progress to Fall 1974.

Macie, T. W.↗
NASA NTRS2012

The Potential for Hosted Payloads at NASA

The 2010 National Space Policy encourages federal agencies to actively explore the use of inventive, nontraditional arrangements for acquiring commercial space goods and services to meet United States Government requirements, including...hosting government capabilities on commercial spacecraft. NASA's Science Mission Directorate has taken an important step towards this goal by adding an option for hosted payload responses to its recent Announcement of Opportunity (AO) for Earth Venture-2 missions. Since NASA selects a significant portion of its science missions through a competitive process, it is useful to understand the implications that this process has on the feasibility of successfully proposing a commercially hosted payload mission. This paper describes some of the impediments associated with proposing a hosted payload mission to NASA, and offers suggestions on how these impediments might be addressed. Commercially hosted payloads provide a novel way to serve the needs of the science and technology demonstration communities at a fraction of the cost of a traditional Geostationary Earth Orbit (GEO) mission. The commercial communications industry launches over 20 satellites to GEO each year. By exercising this repeatable commercial paradigm of privately financed access to space with proven vendors, NASA can achieve science goals at a significantly lower cost than the current dedicated spacecraft and launch vehicle approach affords. Commercial hosting could open up a new realm of opportunities for NASA science missions to make measurements from GEO. This paper also briefly describes two GEO missions recommended by the National Academies of Science Earth Science Decadal Survey, the Geostationary Coastal and Air Pollution Events (GEO-CAPE) mission and the Precipitation and All-weather Temperature and Humidity (PATH) mission. Hosted payload missions recently selected for implementation by the Office of the Chief Technologist are also discussed. Finally, there are technical differences specific to hosted payloads and the GEO environment that must be considered when planning and developing a hosted payload mission. This paper addresses some of payload accommodation differences from the typical NASA LEO mission, including spacecraft interfaces, attitude control and knowledge, communications, data handling, mission operations, ground systems, and the thermal, radiation, and electromagnetic environment. The paper also discusses technical and programmatic differences such as limits to NASA's involvement with commercial quality assurance processes to conform to the commercial schedule and minimizing the price that makes hosted payloads an attractive option.

Andraschko, Mark↗
NASA NTRS1993

Intelligent data presentation for real-time spacecraft monitoring

This paper describes an intelligent user interface that is currently under development. The interface serves as a front end for real-time spacecraft monitoring software. The software operates under circumstances in which neither an intelligent human without automated assistance nor an automated system without intelligence are sufficiently effective. The user interface is supported by dynamic trade-off evaluation (DTE), a new technique that has been developed to automate general types of performance trade-offs in real-time problem solving systems. In this application, DTE is used to perform dynamic input data management for the purpose of determining which input data should be monitored in time constrained situations and how to present the monitoring information to a human analyst who has the ultimate responsibility for the spacecraft. This application has demonstrated that DTE can be used to dynamically vary the data that is monitored, making it possible to detect and correctly analyze all anomalous data by examining only a subset of the total input data. In carefully structured experimental evaluations that use real spacecraft data and real decision making, DTE provides the ability to handle a three-fold increase in input data (in real-time) without loss of performance and to intelligently present the information to a mission analyst.

Schwuttke, U. M.↗
NASA NTRS1974

The data array, a tool to interface the user to a large data base

Aspects of the processing of spacecraft data is considered. Use of the data array in a large address space as an intermediate form in data processing for a large scientific data base is advocated. Techniques for efficient indexing in data arrays are reviewed and the data array method for mapping an arbitrary structure onto linear address space is shown. A compromise between the two forms is given. The impact of the data array on the user interface are considered along with implementation.

Foster, G. H.↗
NASA NTRS1982

A real-time dynamic spacecraft simulator for the LANDSAT-D mission

A real time dynamic simulator for LANDSAT D was developed and has played an integral role in the development and validation of both the ground control system and of the on-board flight software. The simulator utilized an electronic replica of the spacecraft on-board computer and data handling hardware interfaced to a VAX 11/780 computer and simulation software. Key features of the simulator design are a modular software architecture tailored to the VAX/VMS real time capabilities, a microprocessor controlled interface between the VAX and the flight hardware replica, complete simulation of the spacecraft and NASA network communication links, and a flexible and powerful scenario structuring and operator control capability. The design goals and trade-offs, software, and hardware design are summarized. The application of the simulator to the validation of both the ground systems and on-board software is reviewed in detail.

Coffin, A. R.↗
NASA NTRS2002

Message transfer service for space applications

Spacecraft applications that interact with on-board sensors, effectors, and major components have traditionally used private interfaces which are tightly bound to the interface details of the data links connecting these sub-systems. The latest spacecraft, which often include several powerful processors running real time operating systems, high-speed on-board networks, and intelligent peripherals, can support a more layered networked environment. Use of standard interfaces and networked elements is expected to yield reusable software and hardware components. Within CCSDS Panel 1K we have been developing such on-board interface standards. This paper will present a Message Transfer Service that defines a common API for use within a single spacecraft or among spacecraft flying in a constellation.

CCSDS SOIF message service space communication↗