Search NASA⌕ Search

SEARCH · Search NASA

Results for “plug and play”

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 19 records

Plug and Play Integration through Space Object Standardization

Plug and play is an industry standard promoted by Intel and Microsoft, and others that allows users to add and remove various input and output devices without making specific customizations to their systems. The idea behind concept is that using standard products eases integration of components and promotes capabilities of conforming products. The concept works because vendors comply with a standard specification. This paper reports the development of a reference architecture for the mission control domain, which is leveraging off this revolutionary concept. Standards are being developed at the application layer, which enable "plug and play" of mission software products. A Mission Control, reference architecture has been defined. For each sub-domain, the interfaces are modeled in Interface Definition Language (IDL). A subset of the IDL has been developed within both commercial off-the-shelf (COTS) and government (GOTS) products. Selected vendors have agreed to modify their products to be compatible with the defined IDL. The plug and play integration of these different products has been validated in a demonstration testbed.

Boyce, Leslye↗

A Plug and Play GNC Architecture Using FPGA Components

The goal of Plug and Play, or PnP, is to allow hardware and software components to work together automatically, without requiring manual setup procedures. As a result, new or replacement hardware can be plugged into a system and automatically configured with the appropriate resource assignments. However, in many cases it may not be practical or even feasible to physically replace hardware components. One method for handling these types of situations is through the incorporation of reconfigurable hardware such as Field Programmable Gate Arrays, or FPGAs. This paper describes a phased approach to developing a Guidance, Navigation, and Control (GNC) architecture that expands on the traditional concepts of PnP, in order to accommodate hardware reconfiguration without requiring detailed knowledge of the hardware. This is achieved by establishing a functional based interface that defines how the hardware will operate, and allow the hardware to reconfigure itself. The resulting system combines the flexibility of manipulating software components with the speed and efficiency of hardware.

KrishnaKumar, K.↗

Spacecraft guidance, navigation, and control requirements for an intelligent plug-n-play avionics (PAPA) architecture

The objective of this research is to design an intelligent plug-n-play avionics system that provides a reconfigurable platform for supporting the guidance, navigation and control (GN&C) requirements for different elements of the space exploration mission. The focus of this study is to look at the specific requirements for a spacecraft that needs to go from earth to moon and back. In this regard we will identify the different GN&C problems in various phases of flight that need to be addressed for designing such a plug-n-play avionics system. The Apollo and the Space Shuttle programs provide rich literature in terms of understanding some of the general GN&C requirements for a space vehicle. The relevant literature is reviewed which helps in narrowing down the different GN&C algorithms that need to be supported along with their individual requirements.

Kulkarni, Nilesh↗

SpaceWire Plug and Play Updates

This viewgraph presentation reviews the work of the SpaceWire Plug N Play Workgroup. (SpW PnP WG). The chief product of SpW PnP WG will be to develop specification of necessary hardware features required in support upper layer (software) PnP implementations.

Rakow, Glenn↗

SpaceWire Plug and Play

The ability to rapidly deploy inexpensive satellites to meet tactical goals has become an important goal for military space systems. In fact, Operationally Responsive Space (ORS) has been in the spotlight at the highest levels. The Office of the Secretary of Defense (OSD) has identified that the critical next step is developing the bus standards and modular interfaces. Historically, satellite components have been constructed based on bus standards and standardized interfaces. However, this has not been done to a degree, which would allow the rapid deployment of a satellite. Advancements in plug-and-play (PnP) technologies for terrestrial applications can serve as a baseline model for a PnP approach for satellite applications. Since SpaceWire (SpW) has become a de facto standard for satellite high-speed (greater than 200Mbp) on-board communications, it has become important for SpW to adapt to this Plug and Play (PnP) environment. Because SpW is simply a bulk transport protocol and lacks built-in PnP features, several changes are required to facilitate PnP with SpW. The first is for Host(s) to figure out what the network looks like, i.e., how pieces of the network, routers and nodes, are connected together; network mapping, and to receive notice of changes to the network. The second is for the components connected to the network to be understood so that they can communicate. The first element, network topology mapping & change of status indication, is being defined (topic of this paper). The second element describing how components are to communicate has been defined by ARFL with the electronic data sheets known as XTEDS. The first element, network mapping, is recent activities performed by Air Force Research Lab (ARFL), Naval Research Lab (NRL), NASA and US industry (Honeywell, Clearwater, FL, and others). This work has resulted in the development of a protocol that will perform the lower level functions of network mapping and Change Of Status (COS) indication required by Plug 'n' Play over SpaceWire. This work will be presented to the SpaceWire working group for standardization under European Cooperation for Space Standardization (ECSS) and to obtain a permanent Protocol ID (see SpaceWire Protocol ID: What Does it Mean to You; IEEE Aerospace Conference 2006). The portion of the Plug 'n' Play protocol that will be described in this paper is how the Host(s) of a SpaceWire network map the network and detect additions and deletions of devices on a SpaceWire network.

Rakow, Glenn↗

How far away is plug 'n' play? Assessing the near-term potential of sonification and auditory display

The commercial music industry offers a broad range of plug 'n' play hardware and software scaled to music professionals and scaled to a broad consumer market. The principles of sound synthesis utilized in these products are relevant to application in virtual environments (VE). However, the closed architectures used in commercial music synthesizers are prohibitive to low-level control during real-time rendering, and the algorithms and sounds themselves are not standardized from product to product. To bring sound into VE requires a new generation of open architectures designed for human-controlled performance from interfaces embedded in immersive environments. This presentation addresses the state of the sonic arts in scientific computing and VE, analyzes research challenges facing sound computation, and offers suggestions regarding tools we might expect to become available during the next few years. A list of classes of audio functionality in VE includes sonification -- the use of sound to represent data from numerical models; 3D auditory display (spatialization and localization, also called externalization); navigation cues for positional orientation and for finding items or regions inside large spaces; voice recognition for controlling the computer; external communications between users in different spaces; and feedback to the user concerning his own actions or the state of the application interface. To effectively convey this considerable variety of signals, we apply principles of acoustic design to ensure the messages are neither confusing nor competing. We approach the design of auditory experience through a comprehensive structure for messages, and message interplay we refer to as an Automated Sound Environment. Our research addresses real-time sound synthesis, real-time signal processing and localization, interactive control of high-dimensional systems, and synchronization of sound and graphics.

Bargar, Robin↗

TechEdSat - An Educational 1U CubeSat Architecture Using Plug-and-Play Avionics

Mission Objectives: build a 1U cubesat within 6 months from kickoff to launch. Demonstrate and evaluate the Space Plug-and-Play avionics hardware and software from ÅAC Microtec; investigate both Iridium and Orbcomm intersatellite communication as a method of eliminating the requirement for a physical ground station in Nano satellite missions; demonstrate the capabilities of the JAXA J-SSOD aboard the ISS, and be one of the first cubesats to be deployed from the ISS.

TechEdSat↗

Plug-and-Play Environmental Monitoring Spacecraft Subsystem

A Space Environment Monitor (SEM) subsystem architecture has been developed and demonstrated that can benefit future spacecraft by providing (1) real-time knowledge of the spacecraft state in terms of exposure to the environment; (2) critical, instantaneous information for anomaly resolution; and (3) invaluable environmental data for designing future missions. The SEM architecture consists of a network of plug-and- play (PnP) Sensor Interface Units (SIUs), each servicing one or more environmental sensors. The SEM architecture is influenced by the IEEE Smart Transducer Interface Bus standard (IEEE Std 1451) for its PnP functionality. A network of PnP Spacecraft SIUs is enabling technology for gathering continuous real-time information critical to validating spacecraft health in harsh space environments. The demonstrated system that provided a proof-of-concept of the SEM architecture consisted of three SIUs for measurement of total ionizing dose (TID) and single event upset (SEU) radiation effects, electromagnetic interference (EMI), and deep dielectric charging through use of a prototype Internal Electro-Static Discharge Monitor (IESDM). Each SIU consists of two stacked 2X2 in. (approximately 5X5 cm) circuit boards: a Bus Interface Unit (BIU) board that provides data conversion, processing and connection to the SEM power-and-data bus, and a Sensor Interface Electronics (SIE) board that provides sensor interface needs and data path connection to the BIU.

Patel, Jagdish↗

A Core Plug and Play Architecture for Reusable Flight Software Systems

The Flight Software Branch, at Goddard Space Flight Center (GSFC), has been working on a run-time approach to facilitate a formal software reuse process. The reuse process is designed to enable rapid development and integration of high-quality software systems and to more accurately predict development costs and schedule. Previous reuse practices have been somewhat successful when the same teams are moved from project to project. But this typically requires taking the software system in an all-or-nothing approach where useful components cannot be easily extracted from the whole. As a result, the system is less flexible and scalable with limited applicability to new projects. This paper will focus on the rationale behind, and implementation of the run-time executive. This executive is the core for the component-based flight software commonality and reuse process adopted at Goddard.

Wilmot, Jonathan↗

Flying the ST-5 Constellation with "Plug and Play" Autonomy Components and the GMSEC Bus

The Space Technology 5 (ST5) Project, part of NASA's New Millennium Program, will consist of a constellation of three micro-satellites. This viewgraph document presents the components that will allow it to operate in an autonomous mode. The ST-5 constellation will use the GSFC Mission Services Evolution Center (GMSEC) architecture to enable cost effective model based operations. The ST-5 mission will demonstrate several principles of self managing software components.

Shendock, Bob↗

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↗

Implications of Responsive Space on the Flight Software Architecture

The Responsive Space initiative has several implications for flight software that need to be addressed not only within the run-time element, but the development infrastructure and software life-cycle process elements as well. The runtime element must at a minimum support Plug & Play, while the development and process elements need to incorporate methods to quickly generate the needed documentation, code, tests, and all of the artifacts required of flight quality software. Very rapid response times go even further, and imply little or no new software development, requiring instead, using only predeveloped and certified software modules that can be integrated and tested through automated methods. These elements have typically been addressed individually with significant benefits, but it is when they are combined that they can have the greatest impact to Responsive Space. The Flight Software Branch at NASA's Goddard Space Flight Center has been developing the runtime, infrastructure and process elements needed for rapid integration with the Core Flight software System (CFS) architecture. The CFS architecture consists of three main components; the core Flight Executive (cFE), the component catalog, and the Integrated Development Environment (DE). This paper will discuss the design of the components, how they facilitate rapid integration, and lessons learned as the architecture is utilized for an upcoming spacecraft.

Wilmot, Jonathan↗

NASA SpaceWire Activities/Comments/Recommendations

This viewgraph presentation reviews NASA's activities, and proposes recommendations for the further use of the SpaceWire (SpW). The areas covered in this presentation are: (1) Protocol ID assignment, (2) Protocol development, (3) Plug & Play (PnP), (4) Recommended additions t o SpW protocol and (5) SpaceFibre trade.

Rakow, Glenn↗

An Overview of Experiments and Modeling of Polysiloxane-Coated Thermal Protection Systems for Missions to Mars, Titan, and Beyond.

Phenolic Impregnated Carbon Ablator (PICA) gained heritage during the historic Stardust mission, where it successfully returned samples from a comet’s tail and has since been instrumental in delivering payloads to the surface of Mars [1-3]. Most recently, PICA enabled the safe return of samples collected from asteroid Bennu as part of the OSIRIS-REx mission. This rich legacy underscores PICA’s critical role in allowing NASA’s most ambitious exploration missions. However, the friable nature of its phenolic phase presents challenges during handling and pre-launch activities. To mitigate this issue, PICA is coated with a polysiloxane resin system, which serves to suppress particulate dispersion and thereby safeguard spacecraft components. A comprehensive understanding of the polysiloxane resin’s behavior is imperative, as it profoundly shapes the material response of PICA during atmospheric entry by influencing its thermal and oxidative stability. This influence extends to thermocouple plugs embedded within thermal protection systems. These plugs have demonstrated their significance in missions such as Mars Science Laboratory (MSL) and Mars 2020, where the MEDLI and MEDLI2 instrumentation suites delivered in-valuable insights into the performance of thermal protection systems during entry into the Martian atmosphere [4]. Looking ahead, missions such as Dragonfly, set to descend into Titan’s dense atmosphere, aim to leverage advanced sensor technologies to further refine our understanding of thermal protection response [5]. Moreover, thermocouple plugs play an essential role in validating cutting-edge material response models, such as those pioneered under NASA’s Entry Systems Modeling Project (ESM), designed, in-part, to predict the operational integrity of thermal protection systems under the extreme stresses of atmospheric entry. To achieve these modeling goals, ground-based experiments are crucial to provide the foundational data necessary for developing and refining these predictive tools. To this end, an extensive test campaign was conducted at the Hypersonic Materials Environmental Test System (HyMETS) to investigate the high-temperature behavior of the polysiloxane resin in an air environment [6]. These experiments revealed critical phenomena, including the formation of a silicon oxycarbide layer that enhances oxidation resistance, moderates surface temperatures, and alters in-depth thermal response. Building on these findings, subsequent tests were designed to simulate atmospheric entry conditions in reactive gases, such as CO2 and N2, to mimic the environments of Mars and Titan, respectively, as well as non-reactive gases representing the atmospheres of the Ice Giants (Neptune and Uranus). A heating rate dependent decomposition mechanism has been identified for the polysiloxane resin under oxidizing conditions (Fig. 1). In the initial stage, the resin and the underlying thermal protection system undergo pyrolysis, rapidly generating a thin amorphous silicon oxycarbide interwoven with carbonaceous char and residual fibers from PICA. During the second stage, the nascent oxide layer establishes a robust, oxidation-resistant thermal barrier coating, which significantly impedes heat transfer to the underlying carbonaceous char, resulting in a stagnation of the surface temperature. A key factor contributing to this thermal resistance is the low recombination efficiency of atomic oxygen (γ), which further diminishes the heat load on the material’s interior layers [7]. Moreover, as the surface temperature stagnates, the silicon oxycarbide phase separates into distinct regions of silica and free graphite. Ultimately, when the heat flux reaches a critical threshold, a third stage is triggered, leading to the breakdown of the coating through carbothermal reduction, exposing the underlying char layer. This exposure leads to a dramatic surface temperature spike, driven by highly exothermic reactions between atomic oxygen and the char layer, further accelerating material degradation. A detailed mass and heat transfer model of PICA coated with polysiloxane resin was implemented in the Porous material Analysis Toolbox based on OpenFOAM, PATO [8]. The initial stage was considered negligible in this model because the resin decomposition occurs rapidly within a thin surface layer. Instead, the coating was directly considered as an oxygen-resistant thermal barrier coating. For the second stage, the thin amorphous silicon oxycarbide was treated as a pure silica surface to simplify the thermochemical behavior. The model ac-counts for surface equilibrium processes using representative elements of the coating-environment system. For the third stage, specific boundary conditions were developed to estimate the onset and progression of the coating removal. Two-dimensional material response simulations were conducted to compare uncoated and coated PICA using boundary conditions calibrated with HyMETS data. Fig. 2 illustrates that the simulations closely align with experimental data, successfully reproducing measured temperature profiles. This work will include the latest advancements in the coating model, including the calibration of recombination of atomic oxygen at the surface during the second phase. These simulated results will be further validated against additional CO2 data points from HyMETS, reinforcing the models’ predictive capabilities. These mechanisms and their effects on thermal protection systems, including thermochemical behavior and thermocouple probe performance in extreme environments, provide crucial insights for optimizing spacecraft designs that safeguard scientific payload and ensure mission success in future planetary exploration endeavors.

Active Oxidation↗

A Proven Ground System Architecture for Promoting Collaboration and Common Solutions at NASA

NASA Goddard Space Flight Center's "GMSEC" ground system architecture was presented at GSAW2003 as a concept being studied. GMSEC would utilize a publish/subscribe middleware framework and standardized interfaces to allow custom and COTS ground system components to plug-and-play. This capability, in turn, would reduce integration costs, allow for technology infusion over time, and encourage the development and sharing of common components across missions and organizations. At GSAW2004, GMSEC was presented at a breakout session as a system working well in the NASA lab and being applied as an integral piece of reengineering efforts for several GSFC missions. Today, GMSEC is supporting five satellites at GSFC and has been selected by several future missions. Over 30 plug-and-play components are now available to missions using the GMSEC approach. Other organizations, including Marshall Space Flight Center, Johns Hopkins University's Applied Physic Lab, and the Institute for Scientific Research are each developing GMSEC-compatible components. Based on the success of GMSEC and efforts at other NASA Centers, the message bus approach is now being evaluated as a NASA Agency-wide approach for many future missions involving multiple NASA Centers as we move towards the goals of NASA s new Exploration Initiative. The presentation will explain the basic technical concepts of using a publish/subscribe framework for mission operations support (and its applicability to flight systems as well). Lessons learned on NASA's GMSEC program will allow the audience to better understand the significant benefits of this architecture approach over the traditional "one-off" solution approach. The point of the presentation is to show the long-term benefits of using a ground system architecture which incorporates many of the successful GMSEC concepts - message bus, mix of COTS and custom software, standard interfaces, plug-and-play, etc. The implications for the development process will also be discussed.

Smith, Danford↗

Wireless Sensor Networks for Developmental and Flight Instrumentation

Wireless sensor networks (WSN) based on the IEEE 802.15.4 Personal Area Network and ZigBee Pro 2007 standards are finding increasing use in home automation and smart energy markets providing a framework for interoperable software. The Wireless Connections in Space Project, funded by the NASA Engineering and Safety Center, is developing technology, metrics and requirements for next-generation spacecraft avionics incorporating wireless data transport. The team from Stennis Space Center and Mobitrum Corporation, working under a NASA SBIR grant, has developed techniques for embedding plug-and-play software into ZigBee WSN prototypes implementing the IEEE 1451 Transducer Electronic Datasheet (TEDS) standard. The TEDS provides meta-information regarding sensors such as serial number, calibration curve and operational status. Incorporation of TEDS into wireless sensors leads directly to building application level software that can recognize sensors at run-time, dynamically instantiating sensors as they are added or removed. The Ames Research Center team has been experimenting with this technology building demonstration prototypes for on-board health monitoring. Innovations in technology, software and process can lead to dramatic improvements for managing sensor systems applied to Developmental and Flight Instrumentation (DFI) aboard aerospace vehicles. A brief overview of the plug-and-play ZigBee WSN technology is presented along with specific targets for application within the aerospace DFI market. The software architecture for the sensor nodes incorporating the TEDS information is described along with the functions of the Network Capable Gateway processor which bridges 802.15.4 PAN to the TCP/IP network. Client application software connects to the Gateway and is used to display TEDS information and real-time sensor data values updated every few seconds, incorporating error detection and logging to help measure performance and reliability in relevant target environments. Test results from our prototype WSN running the Mobitrum software system are summarized and the implications to the scalability and reliability for DFI applications are discussed. Our demonstration system, incorporating sensors for life support system and structural health monitoring is described along with test results obtained by running the demonstration prototype in relevant environments such as the Wireless Habitat Testbed at Johnson Space Center in Houston. An operations concept for improved sensor process flow from design to flight test is outlined specific to the areas of Environmental Control and Life Support System performance characterization and structural health monitoring of human-rated spacecraft. This operations concept will be used to highlight the areas where WSN technology, particularly plug-and-play software based on IEEE 1451, can improve the current process, resulting in significant reductions in the technical effort, overall cost and schedule for providing DFI capability for future spacecraft. RELEASED -

Alena, Richard↗