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 901 records · Page 50

AMO EXPRESS: A Command and Control Experiment for Crew Autonomy

NASA is investigating a range of future human spaceflight missions, including both Mars-distance and Near Earth Object (NEO) targets. Of significant importance for these missions is the balance between crew autonomy and vehicle automation. As distance from Earth results in increasing communication delays, future crews need both the capability and authority to independently make decisions. However, small crews cannot take on all functions performed by ground today, and so vehicles must be more automated to reduce the crew workload for such missions. NASA's Advanced Exploration Systems Program funded Autonomous Mission Operations (AMO) project conducted an autonomous command and control demonstration of intelligent procedures to automatically initialize a rack onboard the International Space Station (ISS) with power and thermal interfaces, and involving core and payload command and telemetry processing, without support from ground controllers. This autonomous operations capability is enabling in scenarios such as a crew medical emergency, and representative of other spacecraft autonomy challenges. The experiment was conducted using the Expedite the Processing of Experiments for Space Station (EXPRESS) rack 7, which was located in the Port 2 location within the U.S Laboratory onboard the International Space Station (ISS). Activation and deactivation of this facility is time consuming and operationally intensive, requiring coordination of three flight control positions, 47 nominal steps, 57 commands, 276 telemetry checks, and coordination of multiple ISS systems (both core and payload). The autonomous operations concept includes a reduction of the amount of data a crew operator is required to verify during activation or de-activation, as well as integration of procedure execution status and relevant data in a single integrated display. During execution, the auto-procedures provide a step-by-step messaging paradigm and a high level status upon termination. This messaging and high level status is the only data generated for operator display. To enhance situational awareness of the operator, the Web-based Procedure Display (WebPD) provides a novel approach to the issues of procedure display and execution tracking. For this demonstration, the procedure was initiated and monitored from the ground. As the Timeliner sequences executed, their high level execution status was transmitted to ground, for WebPD consumption.

Stetson, Howard K.↗

The Mars mapper science and mission planning tool

The Mars Mapper Program (MOm) is an interactive tool for science and mission design developed for the Mars Observer Mission (MO). MOm is a function of the Planning and Sequencing Element of the MO Ground Data System. The primary users of MOm are members of the science and mission planning teams. Using MOm, the user can display digital maps of Mars in various projections and resolutions ranging from 1 to 256 pixels per degree squared. The user can overlay the maps with ground tracks of the MO spacecraft (S/C) and footprints and swaths of the various instruments on-board the S/C. Orbital and instrument geometric parameters can be computed on demand and displayed on the digital map or plotted in XY-plots. The parameter data can also be saved into files for other uses. MOm is divided into 3 major processes: Generator, Mapper, Plotter. The Generator Process is the main control which spawns all other processes. The processes communicate via sockets. At any one time, only 1 copy of MOm may operate on the system. However, up to 5 copies of each of the major processes may be invoked from the Generator. MOm is developed on the Sun SPARCStation 2GX with menu driven graphical user interface (GUI). The map window and its overlays are mouse-sensitized to permit on-demand calculations of various parameters along an orbit. The program is currently under testing and will be delivered to the MO Mission System Configuration Management for distribution to the MO community in 3/93.

Lo, Martin W.↗

The CCSDS return all frames Space Link Extension service

Existing Consultative Committee for Space Data Systems (CCSDS) Recommendations for Telemetry Channel Coding, Packet Telemetry, Advanced Orbiting Systems, and Telecommand have facilitated cross-support between Agencies by standardizing the link between spacecraft and ground terminal. CCSDS is currently defining a set of Space Link Extension (SLE) services that will enable remote science and mission operations facilities to access the ground termination of the Space Link services in a standard manner. The first SLE service to be defined is the Return All Frames (RAF) service. The RAF service delivers all CCSDS link-layer frames received on a single space link physical channel. The service provides both on-line and off-line data transfer modes to accommodate the variety of access methods typical of space mission operations. This paper describes the RAF service as of the Summer of 1994. It characterizes the behavior of the service as seen across the interface between the user and the service and gives an overview of the interactions involved in setting up and operating the service in a cross-support environment.

Uhrig, Hans↗

Electric prototype power processor for a 30cm ion thruster

An electrical prototype power processor unit was designed, fabricated and tested with a 30 cm mercury ion engine for primary space propulsion. The power processor unit used the thyristor series resonant inverter as the basic power stage for the high power beam and discharge supplies. A transistorized series resonant inverter processed the remaining power for the low power outputs. The power processor included a digital interface unit to process all input commands and internal telemetry signals so that electric propulsion systems could be operated with a central computer system. The electrical prototype unit included design improvement in the power components such as thyristors, transistors, filters and resonant capacitors, and power transformers and inductors in order to reduce component weight, to minimize losses, and to control the component temperature rise. A design analysis for the electrical prototype is also presented on the component weight, losses, part count and reliability estimate. The electrical prototype was tested in a thermal vacuum environment. Integration tests were performed with a 30 cm ion engine and demonstrated operational compatibility. Electromagnetic interference data was also recorded on the design to provide information for spacecraft integration.

Biess, J. J.↗

Navigating the Return Trip from the Moon Using Earth-Based Ground Tracking and GPS

NASA s Constellation Program is planning a human return to the Moon late in the next decade. From a navigation perspective, one of the most critical phases of a lunar mission is the series of burns performed to leave lunar orbit, insert onto a trans-Earth trajectory, and target a precise re-entry corridor in the Earth s atmosphere. A study was conducted to examine sensitivity of the navigation performance during this phase of the mission to the type and availability of tracking data from Earth-based ground stations, and the sensitivity to key error sources. This study also investigated whether GPS measurements could be used to augment Earth-based tracking data, and how far from the Earth GPS measurements would be useful. The ability to track and utilize weak GPS signals transmitted across the limb of the Earth is highly dependent on the configuration and sensitivity of the GPS receiver being used. For this study three GPS configurations were considered: a "standard" GPS receiver with zero dB antenna gain, a "weak signal" GPS receiver with zero dB antenna gain, and a "weak signal" GPS receiver with an Earth-pointing direction antenna (providing 10 dB additional gain). The analysis indicates that with proper selection and configuration of the GPS receiver on the Orion spacecraft, GPS can potentially improve navigation performance during the critical final phases of flight prior to Earth atmospheric entry interface, and may reduce reliance on two-way range tracking from Earth-based ground stations.

Berry, Kevin↗

Receivers

Before discussing Deep Space Network receivers, a brief description of the functions of receivers and how they interface with other elements of the Network is presented. Different types of receivers are used in the Network for various purposes. The principal receiver type is used for telemetry and tracking. This receiver provides the capability, with other elements of the Network, to track the space probe utilizing Doppler and range measurements, and to receive telemetry, including both scientific data from the onboard experiments and engineering data pertaining to the health of the probe. Another type of receiver is used for radio science applications. This receiver measures phase perturbations on the carrier signal to obtain information on the composition of solar and planetary atmospheres and interplanetary space. A third type of receiver utilizes very long baseline interferometry (VLBI) techniques for both radio science and spacecraft navigation data. Only the telemetry receiver is described in detail in this document. The integration of the Receiver-Exciter subsystem with other portions of the Deep Space Network is described.

Donnelly, H.↗

DSN Simulator

The DSN Simulator (wherein DSN signifies NASA's Deep Space Network) is an updated version of the software described in DSN Array Simulator (NPO-44506), Software Tech Briefs (Special supplement to NASA Tech Briefs), Vol. 32, No. 9 (September 2008), page 26. To recapitulate: This software is used for computational modeling of proposed DSN facilities comprising arrays of antennas and transmitting and receiving equipment for microwave communication with spacecraft on interplanetary missions. Such modeling is performed to estimate facility performance, evaluate requirements that govern facility design, and evaluate proposed improvements in hardware and/or software. The software includes a Monte Carlo simulation component that enables rapid generation of key mission-set metrics (e.g., numbers of links, data rates, and data volumes), and statistical distributions thereof as functions of time. The prior version of the software could model only one DSN facility at a time and included hard-coded, unconfigurable metrics. The present updated version is capable of modeling the entire DSN and provides for configurable metrics, making it possible to perform loading analyses for alternative future DSN architectures and mission-set scenarios. The present version also features an improved user interface and interfaces for exchange of data with other DSN software and with a DSN mission model database.

Fijany, Amir↗

Aquarius' Object-Oriented, Plug and Play Component-Based Flight Software

The Aquarius mission involves a combined radiometer and radar instrument in low-Earth orbit, providing monthly global maps of Sea Surface Salinity. Operating successfully in orbit since June, 2011, the spacecraft bus was furnished by the Argentine space agency, Comision Nacional de Actividades Espaciales (CONAE). The instrument, built jointly by NASA's Caltech/JPL and Goddard Space Flight Center, has been successfully producing expectation-exceeding data since it was powered on in August of 2011. In addition to the radiometer and scatterometer, the instrument contains an command & data-handling subsystem with a computer and flight software (FSW) that is responsible for managing the instrument, its operation, and its data. Aquarius' FSW is conceived and architected as a Component-based system, in which the running software consists of a set of Components, each playing a distinctive role in the subsystem, instantiated and connected together at runtime. Component architectures feature a well-defined set of interfaces between the Components, visible and analyzable at the architectural level (see [1]). As we will describe, this kind of an architecture offers significant advantages over more traditional FSW architectures, which often feature a monolithic runtime structure. Component-based software is enabled by Object-Oriented (OO) techniques and languages, the use of which again is not typical in space mission FSW. We will argue in this paper that the use of OO design methods and tools (especially the Unified Modeling Language), as well as the judicious usage of C++, are very well suited to FSW applications, and we will present Aquarius FSW, describing our methods, processes, and design, as a successful case in point.

Component Architecture↗

HYDRA : High-speed simulation architecture for precision spacecraft formation simulation

e Hierarchical Distributed Reconfigurable Architecture- is a scalable simulation architecture that provides flexibility and ease-of-use which take advantage of modern computation and communication hardware. It also provides the ability to implement distributed - or workstation - based simulations and high-fidelity real-time simulation from a common core. Originally designed to serve as a research platform for examining fundamental challenges in formation flying simulation for future space missions, it is also finding use in other missions and applications, all of which can take advantage of the underlying Object-Oriented structure to easily produce distributed simulations. Hydra automates the process of connecting disparate simulation components (Hydra Clients) through a client server architecture that uses high-level descriptions of data associated with each client to find and forge desirable connections (Hydra Services) at run time. Services communicate through the use of Connectors, which abstract messaging to provide single-interface access to any desired communication protocol, such as from shared-memory message passing to TCP/IP to ACE and COBRA. Hydra shares many features with the HLA, although providing more flexibility in connectivity services and behavior overriding.

formation flying↗

Orion Entry Handling Qualities Assessments

The Orion Command Module (CM) is a capsule designed to bring crew back from the International Space Station (ISS), the moon and beyond. The atmospheric entry portion of the flight is deigned to be flown in autopilot mode for nominal situations. However, there exists the possibility for the crew to take over manual control in off-nominal situations. In these instances, the spacecraft must meet specific handling qualities criteria. To address these criteria two separate assessments of the Orion CM s entry Handling Qualities (HQ) were conducted at NASA s Johnson Space Center (JSC) using the Cooper-Harper scale (Cooper & Harper, 1969). These assessments were conducted in the summers of 2008 and 2010 using the Advanced NASA Technology Architecture for Exploration Studies (ANTARES) six degree of freedom, high fidelity Guidance, Navigation, and Control (GN&C) simulation. This paper will address the specifics of the handling qualities criteria, the vehicle configuration, the scenarios flown, the simulation background and setup, crew interfaces and displays, piloting techniques, ratings and crew comments, pre- and post-fight briefings, lessons learned and changes made to improve the overall system performance. The data collection tools, methods, data reduction and output reports will also be discussed. The objective of the 2008 entry HQ assessment was to evaluate the handling qualities of the CM during a lunar skip return. A lunar skip entry case was selected because it was considered the most demanding of all bank control scenarios. Even though skip entry is not planned to be flown manually, it was hypothesized that if a pilot could fly the harder skip entry case, then they could also fly a simpler loads managed or ballistic (constant bank rate command) entry scenario. In addition, with the evaluation set-up of multiple tasks within the entry case, handling qualities ratings collected in the evaluation could be used to assess other scenarios such as the constant bank angle maintenance case. The 2008 entry assessment was divided into two sections (see Figure 1). Entry I was the first, high speed portion of a lunar return and Entry II was the second, lower speed portion of a lunar return, which is similar (but not identical) to a typical ISS return.

Bihari, B.↗

Evolution of pores in the fuel cladding of the electrogenerating channel

The results of reactor tests of carbonitride fuel in a monocrystalline cladding from a molybdenum-based alloy that were carried out earlier on an experimental setup Ya-82 for 8 to 300 h at a temperature of ∼1500°C can be used in order to prove the operational reliability of fuel elements in the design of a megawatt nuclear power plant for a spacecraft. A raster image of the surface of a sample of cladding shows that the interfaces between the layers are decorated by pores. This result is explained in this work by the theory of coalescence. The mechanisms responsible for the evolution of pores taking place at the parameters of a Ya-82 setup are considered. The effect of decoration by pores of the interfaces between the layers of a sample of cladding of the electrogenerating channel by carrying out reactor tests is explained. The dependence of the average radius of pores on the duration of the experiment is obtained. An evaluation of the average sizes of pores arising under the conditions of the experiment gives a value of ∼2 μm, which is in agreement with the experimental data. A computational study of swelling of the cladding material in the process of irradiation is performed. Predictive estimates of the behavior of the porous system and swelling of the cladding material for a megawatt class nuclear power plant are made.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

Experiences in Interagency and International Interfaces for Mission Support

The Flight Dynamics Division (FDD) of the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GFSC) provides extensive support and products for Space Shuttle missions, expendable launch vehicle launches, and routine on-orbit operations for a variety of spacecraft. A major challenge in providing support for these missions is defining and generating the products required for mission support and developing the method by which these products are exchanged between supporting agencies. As interagency and international cooperation has increased in the space community, the FDD customer base has grown and with it the number and variety of external interfaces and product definitions. Currently, the FDD has working interfaces with the NASA Space and Ground Networks, the Johnson Space Center, the White Sands Complex, the Jet propulsion Laboratory (including the Deep Space Network), the United States Air Force, the Centre National d'Etudes Spatiales, the German Spaceflight Operations Center, the European Space Agency, and the National Space Development Agency of Japan. With the increasing spectrum of possible data product definitions and delivery methods, the FDD is using its extensive interagency experience to improve its support of established customers and to provide leadership in adapting/developing new interfaces. This paper describes the evolution of the interfaces between the FDD and its customers, discusses many of the joint activities ith these customers, and summarizes key lessons learned that can be applied to current and future support.

Dell, G. T.↗

Orion EFT-1 Catalytic Tile Experiment Overview and Flight Measurements

This paper describes the design and results of a surface catalysis flight experiment flown on the Orion Multipurpose Crew Vehicle during Exploration Flight Test 1 (EFT1). Similar to previous Space Shuttle catalytic tile experiments, the present test consisted of a highly catalytic coating applied to an instrumented TPS tile. However, the present catalytic tile experiment contained significantly more instrumentation in order to better resolve the heating overshoot caused by the change in surface catalytic efficiency at the interface between two distinct materials. In addition to collecting data with unprecedented spatial resolution of the "overshoot" phenomenon, the experiment was also designed to prove if such a catalytic overshoot would be seen in turbulent flow in high enthalpy regimes. A detailed discussion of the results obtained during EFT1 is presented, as well as the challenges associated with data interpretation of this experiment. Results of material testing carried out in support of this flight experiment are also shown. Finally, an inverse heat conduction technique is employed to reconstruct the flight environments at locations upstream and along the catalytic coating. The data and analysis presented in this work will greatly contribute to our understanding of the catalytic "overshoot" phenomenon, and have a significant impact on the design of future spacecraft.

Salazar, Giovanni↗

The Seasat algorithm development facility at JPL

The Seasat-A spacecraft, scheduled for launch in May 1978, will produce a global ocean data set covering a one-year nominal mission. Because this is a proof-of-concept mission, data processing algorithms are expected to evolve as the data base grows. To support the evolution and evaluation of algorithms, and to experiment with various techniques for processing the data, an algorithm development facility (ADF) is being developing. The ADF will provide access to the data base and to highly modularized processing programs. The processing programs will be subject to easy and frequent modification by a remote user community of sensor managers and experiment teams, who will use this capability to evaluate the overall performance of the sensors and the algorithms using surface truth data. The ADF concepts of software standardization and interface control are expected to have general applicability for adaptive data processing systems.

Brown, J. W.↗

Europa's Icy Shell: A Bridge Between Its Surface and Ocean

Europa, a Moon-sized, ice-covered satellite of Jupiter, is second only to Mars in its astrobiological potential. Beneath the icy surface, an ocean up to 150 km deep is thought to exist, providing a potential habitat for life,and a tempting target for future space missions. The Galileo mission to the Jovian system recently ended, but there are already long-range plans to send much more capable spacecraft,such as the proposed Jupiter Icy Moons Orbiter (JIMO), to take a closer look at Europa and her siblings, Ganymede and Callisto, some time in the next two decades. Europak outer icy shell is the only interface between this putative ocean and the surface, but many aspects of this shell are presently poorly understood; in particular, its composition, thickness, deformational history, and mechanical properties. To discuss the ice shell and our current understanding of it, 78 scientists from the terrestrial and planetary science communities in the United States and Europe gathered for a 3-day workshop hosted by the Lunar and Planetary Institute in Houston in February. A key goal was to bring researchers from disparate disciplines together to discuss the importance and limitations of available data on Europa with a post-Galileo perspective. The workshop featured 2 days of reviews and contributed talks on the composition, physical properties, stratigraphy, tectonics, and future exploration of the ice shell and underlying ocean. The final morning included an extended discussion period, moderated by a panel of noted experts, highlighting outstanding questions and areas requiring future research.

Schenk, Paul↗

FERMI/GLAST Integrated Trending and Plotting System Release 5.0

An Integrated Trending and Plotting System (ITPS) is a trending, analysis, and plotting system used by space missions to determine performance and status of spacecraft and its instruments. ITPS supports several NASA mission operational control centers providing engineers, ground controllers, and scientists with access to the entire spacecraft telemetry data archive for the life of the mission, and includes a secure Web component for remote access. FERMI/GLAST ITPS Release 5.0 features include the option to display dates (yyyy/ddd) instead of orbit numbers along orbital Long-Term Trend (LTT) plot axis, the ability to save statistics from daily production plots as image files, and removal of redundant edit/create Input Definition File (IDF) screens. Other features are a fix to address invalid packet lengths, a change in naming convention of image files in order to use in script, the ability to save all ITPS plot images (from Windows or the Web) as GIF or PNG format, the ability to specify ymin and ymax on plots where previously only the desired range could be specified, Web interface capability to plot IDFs that contain out-oforder page and plot numbers, and a fix to change all default file names to show yyyydddhhmmss time stamps instead of hhmmssdddyyyy. A Web interface capability sorts files based on modification date (with newest one at top), and the statistics block can be displayed via a Web interface. Via the Web, users can graphically view the volume of telemetry data from each day contained in the ITPS archive in the Web digest. The ITPS could be also used in nonspace fields that need to plot data or trend data, including financial and banking systems, aviation and transportation systems, healthcare and educational systems, sales and marketing, and housing and construction.

Ritter, Sheila↗

Ares I-X Ground Diagnostic Prototype

Automating prelaunch diagnostics for launch vehicles offers three potential benefits. First, it potentially improves safety by detecting faults that might otherwise have been missed so that they can be corrected before launch. Second, it potentially reduces launch delays by more quickly diagnosing the cause of anomalies that occur during prelaunch processing. Reducing launch delays will be critical to the success of NASA's planned future missions that require in-orbit rendezvous. Third, it potentially reduces costs by reducing both launch delays and the number of people needed to monitor the prelaunch process. NASA is currently developing the Ares I launch vehicle to bring the Orion capsule and its crew of four astronauts to low-earth orbit on their way to the moon. Ares I-X will be the first unmanned test flight of Ares I. It is scheduled to launch on October 27, 2009. The Ares I-X Ground Diagnostic Prototype is a prototype ground diagnostic system that will provide anomaly detection, fault detection, fault isolation, and diagnostics for the Ares I-X first-stage thrust vector control (TVC) and for the associated ground hydraulics while it is in the Vehicle Assembly Building (VAB) at John F. Kennedy Space Center (KSC) and on the launch pad. It will serve as a prototype for a future operational ground diagnostic system for Ares I. The prototype combines three existing diagnostic tools. The first tool, TEAMS (Testability Engineering and Maintenance System), is a model-based tool that is commercially produced by Qualtech Systems, Inc. It uses a qualitative model of failure propagation to perform fault isolation and diagnostics. We adapted an existing TEAMS model of the TVC to use for diagnostics and developed a TEAMS model of the ground hydraulics. The second tool, Spacecraft Health Inference Engine (SHINE), is a rule-based expert system developed at the NASA Jet Propulsion Laboratory. We developed SHINE rules for fault detection and mode identification. The prototype uses the outputs of SHINE as inputs to TEAMS. The third tool, the Inductive Monitoring System (IMS), is an anomaly detection tool developed at NASA Ames Research Center and is currently used to monitor the International Space Station Control Moment Gyroscopes. IMS automatically "learns" a model of historical nominal data in the form of a set of clusters and signals an alarm when new data fails to match this model. IMS offers the potential to detect faults that have not been modeled. The three tools have been integrated and deployed to Hangar AE at KSC where they interface with live data from the Ares I-X vehicle and from the ground hydraulics. The outputs of the tools are displayed on a console in Hangar AE, one of the locations from which the Ares I-X launch will be monitored. The full paper will describe how the prototype performed before the launch. It will include an analysis of the prototype's accuracy, including false-positive rates, false-negative rates, and receiver operating characteristics (ROC) curves. It will also include a description of the prototype's computational requirements, including CPU usage, main memory usage, and disk usage. If the prototype detects any faults during the prelaunch period then the paper will include a description of those faults. Similarly, if the prototype has any false alarms then the paper will describe them and will attempt to explain their causes.

Schwabacher, Mark↗

Remote Software Application and Display Development

The era of the shuttle program has come to an end, but only to give rise to newer and more exciting projects. Now is the time of the Orion spacecraft, a work of art designed to exceed all previous endeavors of man. NASA is exiting the time of exploration and is entering a new period, a period of pioneering. With this new mission, many of NASAs organizations must undergo a great deal of change and development to support the Orion missions. The Spaceport Command and Control System (SCCS) is the new system that will provide NASA the ability to launch rockets into orbit and thus control Orion and other spacecraft as the goal of populating Mars becomes ever increasingly tangible. Since the previous control system, Launch Processing System (LPS), was primarily designed to launch the shuttles, SCCS was needed as Kennedy Space Center (KSC) reorganized to a multiuser spaceport for commercial flights, providing a more versatile control over rockets. Within SCCS, is the Launch Control System (LCS), which is the remote software behind the command and monitoring of flight and ground system hardware. This internship at KSC has involved two main components in LCS, including Remote Software Application and Display development. The display environment provides a graphical user interface for an operator to view and see if any cautions are raised, while the remote applications are the backbone that communicate with hardware, and then relay the data back to the displays. These elements go hand in hand as they provide monitoring and control over hardware and software alike from the safety of the Launch Control Center. The remote software applications are written in Application Control Language (ACL), which must undergo unit testing to ensure data integrity. This paper describes both the implementation and writing of unit tests in ACL code for remote software applications, as well as the building of remote displays to be used in the Launch Control Center (LCC).

ACL↗