Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “open subsystem”

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

Evolving the SpaceFOM: Lessons Learned and Future Development

For over fifty years, simulation has been a cornerstone technology for space missions. In many cases, one single simulator, developed by one team, is not enough to meet the simulation objectives. Astronaut crew training, docking, vehicle testing and complex mission planning all require several simulations to be connected and to interoperate, in order to achieve the goal of the simulation. To facilitate the development of interoperable simulations, an open standard, the SISO SpaceFOM was developed in collaboration between government, industry and academia. The standard was released in 2020. The initial release of SpaceFOM focuses on the core interoperability topics for space simulation: (i) specifying spatial data using several, well defined reference frames, (ii) managing time (including real-time, hard real-time, and as-fast-as-possible execution), (iii) composition of systems with subsystems such as space vehicles, and (iv) execution control, such as initializing, running, pausing, and terminating simulations. A number of requirements for the next version of SpaceFOM have been identified and proposed solutions are already under development. One key area is the object classes used for data exchange, where a richer set of classes have been proposed, based on practical use cases. For time management, the use of variable time resolutions and variable time steps is also proposed. For execution control, save and restore of simulations is considered as well as improved robustness, to handle failing components. A number of clarifications are also under consideration. This paper provides both a forward-looking view of the technical developments underway and a retrospective on the standard's evolution. The authors emphasize that prioritizing core challenges and delivering a practical first version were crucial steps. While not every idea was implemented in the initial release, the timely delivery of a functional standard enabled real-world applications, the growth of a user community, and the collection of valuable insights to shape future versions. The authors look forward to working with the next version of SpaceFOM together with the growing user community.

FOMs↗
NASA NTRS2014

Integration of a MicroCAT Propulsion System and a PhoneSat Bus into a 1.5U CubeSat

NASA Ames Research Center and the George Washington University have developed an electric propulsion subsystem that can be integrated into the PhoneSat bus. Experimental tests have shown a reliable performance by firing three different thrusters at various frequencies in vacuum conditions. The three thrusters were controlled by a SmartPhone that was running the PhoneSat software. The subsystem is fully operational and it requires low average power to function (about 0.1 W). The interface consists of a microcontroller that sends a trigger pulses to the PPU (Plasma Processing Unit), which is responsible for the thruster operation. Frequencies ranging from 1 to 50Hz have been tested, showing a strong flexibility. A SmartPhone acts as the main user interface for the selection of commands that control the entire system. The micro cathode arc thruster MicroCAT provides a high 1(sub sp) of 3000s that allows a 4kg satellite to obtain a (delta)V of 300m/s. The system mass is only 200g with a total of volume of 200(cu cm). The propellant is based on a solid cylinder made of Titanium, which is the cathode at the same time. This simplicity in the design avoids miniaturization and manufacturing problems. The characteristics of this thruster allow an array of MicroCATs to perform attitude control and orbital correcton maneuvers that will open the door for the implementation of an extensive collection of new mission concepts and space applications for CubeSats. NASA Ames is currently working on the integration of the system to fit the thrusters and PPU inside a 1.5U CubeSat together with the PhoneSat bus into a 1.5U CubeSat. This satellite is intended to be deployed from the ISS in 2015 and test the functionality of the thrusters by spinning the satellite around its long axis and measure the rotational speed with the phone byros. This test flight will raise the TRL of the propulsion system from 5 to 7 and will be a first test for further CubeSats with propulsion systems, a key subsystem for long duration or interplanetary CubeSat missions.

PhoneSat↗
NASA NTRSDate not supplied

Aviary: An Open-Source Multidisciplinary Design, Analysis, and Optimization Tool for Modeling Aircraft With Analytic Gradients

Demands on aircraft design methods in recent years have begun to require increasingly higher amounts of coupling between disciplines and have also begun to require optimization in order to satisfy competing objectives involving large numbers of parameters that define unconventional configurations. These expanding requirements have amplified a need for new and improved aircraft design, analysis, and optimization codes that are capable of performing coupled design exploiting analytic gradients where possible. Aviary is a multidisciplinary design optimization and analysis framework which allows for tightly coupled simultaneous aircraft and subsystem design using analytic gradients. Aviary has employed the methods of two legacy aircraft analysis tools to provide native analytically differentiated calculations for five different disciplines, and it also has the ability to couple in external discipline analysis tools, whether or not those tools can provide analytic gradients. Preliminary examples and modeling efforts have shown Aviary’s ability to effectively model novel concepts and explore large and non-intuitive design spaces. Finally, a multi-level user interface in Aviary creates an easy entry point for users with any level of multidisciplinary design, analysis, and optimization experience.

multidisciplinary↗
NASA NTRS2004

State analysis requirements database for engineering complex embedded systems

It has become clear that spacecraft system complexity is reaching a threshold where customary methods of control are no longer affordable or sufficiently reliable. At the heart of this problem are the conventional approaches to systems and software engineering based on subsystem-level functional decomposition, which fail to scale in the tangled web of interactions typically encountered in complex spacecraft designs. Furthermore, there is a fundamental gap between the requirements on software specified by systems engineers and the implementation of these requirements by software engineers. Software engineers must perform the translation of requirements into software code, hoping to accurately capture the systems engineer's understanding of the system behavior, which is not always explicitly specified. This gap opens up the possibility for misinterpretation of the systems engineer's intent, potentially leading to software errors. This problem is addressed by a systems engineering tool called the State Analysis Database, which provides a tool for capturing system and software requirements in the form of explicit models. This paper describes how requirements for complex aerospace systems can be developed using the State Analysis Database.

model base engineering↗
NASA NTRS2004

Engineering Complex Embedded Systems with State Analysis and the Mission Data System

It has become clear that spacecraft system complexity is reaching a threshold where customary methods of control are no longer affordable or sufficiently reliable. At the heart of this problem are the conventional approaches to systems and software engineering based on subsystem-level functional decomposition, which fail to scale in the tangled web of interactions typically encountered in complex spacecraft designs. Furthermore, there is a fundamental gap between the requirements on software specified by systems engineers and the implementation of these requirements by software engineers. Software engineers must perform the translation of requirements into software code, hoping to accurately capture the systems engineer's understanding of the system behavior, which is not always explicitly specified. This gap opens up the possibility for misinterpretation of the systems engineer s intent, potentially leading to software errors. This problem is addressed by a systems engineering methodology called State Analysis, which provides a process for capturing system and software requirements in the form of explicit models. This paper describes how requirements for complex aerospace systems can be developed using State Analysis and how these requirements inform the design of the system software, using representative spacecraft examples.

mission data systems↗
NASA NTRSDate not supplied

Rapid Lightweight Firmware Architecture of the Mobile Metamaterial Internal Co-Integrator Robot

The Mobile Metamaterial Internal Co-Integrator (MMIC-I) is a structure assembly and servicing robot for in-space servicing, assembly, and manufacturing of primary structures and infrastructure. MMIC-I is a battery-powered crawling robot that can travel through periodic structures such as trusses and open framework mechanical metamaterials. It does this through sequences of component extension, contraction, and gripping. This paper provides a detailed discussion of MMIC-I’s lightweight and rapidly developed firmware architecture, to enable demonstration of robot locomotion, secondary operations, and communications with a central command source. The rationale for the lightweight rapid development approach is to allow for assessment of long term system requirements in parallel with the mechatronics development, including optimization of system and subsystem power densities, to inform a future choice of flight ready software frameworks. MMIC-I system computing and I/O requirements are much lower than what is provided by proven baseline computing hardware for existing flight ready software frameworks such as the core Flight System, F prime, and the Robot Operating System. Development of earth gravity ground demonstration of the robotic systems is greatly benefited by limited power and mass factors for computing hardware. Here, we implement inter-process communication, commanding, and telemetry with the Espressif ESP32 module running the Arduino OS.

Damiana Catanoso↗
NASA NTRS1992

Space Generic Open Avionics Architecture (SGOAA): Overview

A space generic open avionics architecture created for NASA is described. It will serve as the basis for entities in spacecraft core avionics, capable of being tailored by NASA for future space program avionics ranging from small vehicles such as Moon ascent/descent vehicles to large ones such as Mars transfer vehicles or orbiting stations. The standard consists of: (1) a system architecture; (2) a generic processing hardware architecture; (3) a six class architecture interface model; (4) a system services functional subsystem architectural model; and (5) an operations control functional subsystem architectural model.

Wray, Richard B.↗
NASA NTRS2003

Shuttle Primary Reaction Control Subsystem Thruster Fuel Valve Pilot Seal Extrusion: A Failure Correlation

Pilot operated valves (POVs) are used to control the flow of hypergolic propellants monomethylhydrazine (fuel) and nitrogen tetroxide (oxidizer) to the Shuttle orbiter Primary Reaction Control Subsystem (PRCS) thrusters. The POV incorporates a two-stage design: a solenoid-actuated pilot stage, which in turn controls a pressure-actuated main stage. Isolation of propellant supply from the thruster chamber is accomplished in part by a captive polytetrafluoroethylene (PTFE) pilot seal retained inside a Custom 455.1 stainless steel cavity. Extrusion of the pilot seal restricts the flow of fuel around the pilot poppet, thus impeding or preventing the main valve stage from opening. It can also prevent the main stage from staying open with adequate force margin, particularly if there is gas in the main stage actuation cavity. During thruster operation on-orbit, fuel valve pilot seal extrusion is commonly indicated by low or erratic chamber pressure or failure of the thruster to fire upon command (Fail-Off). During ground turnaround, pilot seal extrusion is commonly indicated by slow gaseous nitrogen (GN2) main valve opening times (greater than 38 ms) or slow water main valve opening response times (greater than 33 ms). Poppet lift tests and visual inspection can also detect pilot seal extrusion during ground servicing; however, direct metrology on the pilot seat assembly provides the most quantitative and accurate means of identifying extrusion. Minimizing PRCS fuel valve pilot seal extrusion has become an important issue in the effort to improve PRCS reliability and reduce associated life cycle costs.

Waller, Jess↗
NASA NTRSDate not supplied

Lessons Learned in Systems Engineering Availability and Recommendations for Mission Technical Leaders

In spaceflight missions at Goddard Space Flight Center (GSFC), the Mission System Engineer (MSE) is the technical leader of the overall engineering team and also is the Independent Engineering Technical Authority. The responsibility of this role includes the definition of the mission design architecture, concept of operations, and mission requirements, management of risk throughout the development, and verification and validation of the final system performance and function amongst other duties. This responsibility inherently requires time management, enabling focus on a balanced development with appropriate risk. Time is the most valuable resource of the MSE. The system engineer’s availability to interact with the development team (often product or component design leads and technicians, often in different worksites) to discover and mitigate mission risks during development is key to mission success. This paper presents examples from Lunar Reconnaissance Orbiter, Landsat 9, and Neutron star Interior Composition ExploreR (NICER) which represent in-house and out-of-house hardware builds. These examples demonstrate how interactions between the Mission Systems Engineers and other project and partner engineers result in discovery of critical risks, leading to early mitigation with significant cost and performance savings. These three missions would have suffered test failures or on-orbit failures had their MSEs not set aside time to visit engineers and technicians that were working on key pieces of space flight hardware. Availability is more than just time; it is openness to listen to concerns and questions. It begins by building a level of trust in the team that it is safe to ask questions or share concerns without the fear of blame or additional workload. It also requires enabling informal conversations (over lunch, coffee, in the clean room, or at the team members desk, etc.) where key information can be exchanged, and team members may even provide an easy-to-implement mitigation idea for another subsystem. Availability is a highly valuable commodity and completely non-obvious to protect and optimize. The natural tendency of engineers is to keep themselves busy with solving problems that they know about. This paper is encouraging MSEs to resist this tendency to try and solve all the complex problems themselves and actively devote daily time to learning and solving problems that are found with informal communications with other team members.

Lessons Learned↗
NASA NTRS1990

Conceptual design for a lunar-base CELSS

Future human exploration is key to the United States National Space Policy goal of maintaining a world leadership position in space. In the past, spacecraft life support systems have used open-loop technologies that were simple and sufficiently reliable to demonstrate the feasibility of spaceflight. A critical technology area needing development in support of both long duration missions and the establishment of lunar or planetary bases is regenerative life support. The information presented in this paper describes a conceptual design of a Lunar Base Controlled Ecological Life Support System (LCELSS) which supports a crew size ranging from 4 to 100. The system includes, or incorporates interfaces with, eight primary subsystems. An initial description of the Lunar-Base CELSS subsystems is provided within the framework of the conceptual design. The system design includes both plant (algae and higher plant) and animal species as potential food sources.

Schwartzkopf, Steven H.↗
NASA NTRS2006

Periodically Discharging, Gas-Coalescing Filter

A proposed device would remove bubbles of gas from a stream of liquid (typically water), accumulate the gas, and periodically release the gas, in bulk, back into the stream. The device is intended for use in a flow system (1) in which there is a requirement to supply bubble-free water to a downstream subsystem and (2) that includes a sensor and valves, just upstream of the subsystem, for sensing bubbles and diverting the flow from the subsystem until the water stream is again free of bubbles. By coalescing the gas bubbles and then periodically releasing the accumulated gas, the proposed device would not contribute to net removal of gas from the liquid stream; nevertheless, it would afford an advantage by reducing the frequency with which the diverter valves would have to be activated. The device (see figure) would include an upper and a lower porous membrane made of a hydrophilic material. Both membranes would cover openings in a tube leading to an outlet. These membranes would allow water, but not gas bubbles, to pass through to the interior of the tube. Inside the tube, between the two membranes, there would be a flow restrictor that would play a role described below. Below both membranes there would be a relief valve. Water, possibly containing bubbles, would enter from the top and would pass through either the lower membrane or both membranes, depending how much gas had been accumulated thus far. When the volume of accumulated gas was sufficient to push the top surface of the liquid below the lower porous membrane, water could no longer flow through either membrane toward the outlet. This blockage would cause an increase in back pressure that would cause the relief valve to open. The opening of the relief valve would allow both the water and the bulk-accumulated gas to pass through to the outlet. Once the gas had been pushed out, water would once again flow through both membranes at a much lower pressure drop. The flow restrictor would maintain enough pressure drop to keep the relief valve open until gas had been cleared from both hydrophilic membranes.

Carter, Donald Layne↗
NASA NTRSDate not supplied

Aviary: An Open-Source Multidisciplinary Design, Analysis, and Optimization Tool for Modeling Aircraft with Analytic Gradients

In recent years demands on aircraft design methods have begun to require higher degrees of coupling between disciplines and optimization in order to satisfy competing objectives involving large numbers of design parameters that define unconventional configurations. These expanding requirements have amplified a need for new and improved aircraft design, analysis, and optimization codes that are capable of performing coupled design and exploiting analytic gradients to perform gradient-based optimization where possible. To address this need, a new multidisciplinary design optimization and analysis tool called Aviary is presented. This tool, built on OpenMDAO, allows for tightly coupled, simultaneous aircraft and subsystem design using analytic gradients. Aviary includes methods from two NASA developed legacy aircraft analysis tools and provides native analytically differentiated calculations for five different disciplines (weights and sizing, aerodynamics, geometry, propulsion, and mission analysis), while also allowing external discipline analysis tools to be coupled, regardless of whether those tools can provide analytic gradients. Verification and preliminary examples and modeling efforts show Aviary’s ability to effectively model novel concepts and explore large and non-intuitive design spaces. Additionally, a multi-level user interface in Aviary creates an easy entry point for users with any level of multidisciplinary design, analysis, and optimization experience.

optimization↗
NASA NTRS2019

Optimization of Lyot Coronagrah focal plane masks for improved low-order wavefront sensing

The WFIRST Coronagraph uses a Low-Order Wavefront Sensing and Control (LOWFS/C) subsystem to stabilize the stellar wavefront. This is true for the Hybrid Lyot Coronagraph (HLC), the Shaped Pupil Coronagraph (SPC) spectrograph, and the SPC wide field of view modes. For the SPC spectrograph, we have found via modeling and simulations that a focal plane mask (FPM) with an elliptical phase dimple can reduce the LOWFS errors significantly compared to the conventional, circular phase dimple. For HLC designs, we concurrently optimized the FPM parameters and deformable mirror shapes using our open-source software toolbox, the Fast Linearized Coronagraph Optimizer (FALCO). This process resulted in new FPMs with non-uniform central-area phase modulation. We have found in numerical simulations that such FPMs still provide sufficient LOWFS performance. In this paper, we will present the LOWFS performance for several new HLC and SPC FPM designs.

Riggs, A.J. Eldorado↗
NASA NTRS1989

A distributed finite-element modeling and control approach for large flexible structures

An unconventional framework is described for the design of decentralized controllers for large flexible structures. In contrast to conventional control system design practice which begins with a model of the open loop plant, the controlled plant is assembled from controlled components in which the modeling phase and the control design phase are integrated at the component level. The developed framework is called controlled component synthesis (CCS) to reflect that it is motivated by the well developed Component Mode Synthesis (CMS) methods which were demonstrated to be effective for solving large complex structural analysis problems for almost three decades. The design philosophy behind CCS is also closely related to that of the subsystem decomposition approach in decentralized control.

Young, K. D.↗
NASA NTRS1989

Summary and evaluation of the Strategic Defense Initiative Space Power Architecture Study

The Space Power Architecture Study (SPAS) identified and evaluated power subsystem options for multimegawatt electric (MMWE) space based weapons and surveillance platforms for the Strategic Defense Initiative (SDI) applications. Steady state requirements of less than 1 MMWE are adequately covered by the SP-100 nuclear space power program and hence were not addressed in the SPAS. Four steady state power systems less than 1 MMWE were investigated with little difference between them on a mass basis. The majority of the burst power systems utilized H(2) from the weapons and were either closed (no effluent), open (effluent release) or steady state with storage (no effluent). Closed systems used nuclear or combustion heat source with thermionic, Rankine, turboalternator, fuel cell and battery conversion devices. Open systems included nuclear or combustion heat sources using turboalternator, magnetohydrodynamic, fuel cell or battery power conversion devices. The steady state systems with storage used the SP-100 or Star-M reactors as energy sources and flywheels, fuel cells or batteries to store energy for burst applications. As with other studies the open systems are by far the lightest, most compact and simplist (most reliable) systems. However, unlike other studies the SPAS studied potential platform operational problems caused by effluents or vibration.

Edenburn, M.↗
NASA NTRS1977

Metabolic analyzer

The metabolic analyzer was designed to support experiment M171. It operates on the so-called open circuit method to measure a subject's metabolic activity in terms of oxygen consumed, carbon dioxide produced, minute volume, respiratory exchange ratio, and tidal volume or vital capacity. The system operates in either of two modes. (1) In Mode I, inhaled respiratory volumes are actually measured by a piston spirometer. (2) In Mode II, inhaled volumes are calculated from the exhaled volume and the measured inhaled and exhaled nitrogen concentrations. This second mode was the prime mode for Skylab. Following is a brief description of the various subsystems and their operation.

Lem, J. D.↗
NASA NTRS1993

DSS-13 - Using an OSI process control standard for monitor and control

The flexibility and robustness of a monitor and control (M&C) system are a direct result of the underlying inter-processor communications architecture. A new architecture for M&C at the Deep Space Communications Complexes has been developed based on the manufacturing message specification (MMS) process control standard of the open system interconnection (OSI) suite of protocols. This architecture has been tested both in a laboratory environment and under operational conditions at the Deep Space Network experimental station (DSS-13). The DSS-13 experience in the application of OSI standards to support M&C has been extremely successful. MMS meets the functional needs of the station and provides a level of flexibility and responsiveness previously unknown in that environment. The architecture is robust enough to meet current operational needs and flexible enough to provide a migration path for new subsystems. This paper describes the architecture of the DSS-13 M&C system, discuss how MMS was used and the requirements this imposed on other parts of the system, and provides results from systems and operational testing at DSS-13.

Heuser, W. R.↗
NASA NTRS2012

Prognostics for Microgrid Components

Prognostics is the science of predicting future performance and potential failures based on targeted condition monitoring. Moving away from the traditional reliability centric view, prognostics aims at detecting and quantifying the time to impending failures. This advance warning provides the opportunity to take actions that can preserve uptime, reduce cost of damage, or extend the life of the component. The talk will focus on the concepts and basics of prognostics from the viewpoint of condition-based systems health management. Differences with other techniques used in systems health management and philosophies of prognostics used in other domains will be shown. Examples relevant to micro grid systems and subsystems will be used to illustrate various types of prediction scenarios and the resources it take to set up a desired prognostic system. Specifically, the implementation results for power storage and power semiconductor components will demonstrate specific solution approaches of prognostics. The role of constituent elements of prognostics, such as model, prediction algorithms, failure threshold, run-to-failure data, requirements and specifications, and post-prognostic reasoning will be explained. A discussion on performance evaluation and performance metrics will conclude the technical discussion followed by general comments on open research problems and challenges in prognostics.

Saxena, Abhinav↗