SEARCH · Engineering Papers

Results for “evolvable hardware”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 109 records · Page 6

All sources NASA NTRS DOE OSTI

NASA NTRSDate not supplied

An Agile-Like Approach to Hardware Development: The Ejectable Data Recorder (EDR) for Orion's Ascent Abort 2 (AA-2) Test Flight

On July 2, 2019, the Ascent Abort 2 (AA-2) Flight Test Vehicle was launched from Cape Canaveral, with the goal of demonstrating the performance of Orion’s Launch Abort System (LAS) and collecting data from hundreds of sensors throughout the vehicle. The data collected during this test flight is of paramount importance, as it will be used to certify the Orion vehicle for human spaceflight. Originally, the data was to be downlinked via a single string network of antennas on the LAS, with the associated risk of potential data dropouts, as well as loss of data once the LAS was jettisoned. Thus, additional antennas were added onto the crew module (CM) to support data downlink post-LAS jettison, a buffer rebroadcast capability was added to fill in any gaps in data downlink transmissions, and an ejectable data recorder (EDR) subsystem was added to the CM as a redundant measure to collect all the instrumentation data. The EDR subsystem was added to the project about one year after the project commenced, which significantly reduced the available development time when compared with the other subsystems of the AA-2 Test Flight. The project was further accelerated by six months, around the critical design review gate. Due to the schedule compression challenge and the fact that the EDR subsystem was a backup system and not flight critical, the EDR subsystem was further challenged to find a new and more efficient way to develop hardware. Thus, the EDR subsystem experimented with different management and systems engineering processes, team sizes, communication methods, and tools. Some examples are novel uses of SharePoint as a Data-centric Project Management & Systems Engineering environment, a continuous testing approach through the lifecycle, and a Skunkworks approach to managing the team. The EDR subsystem blended Commercial Off The Shelf (COTS) hardware with in-house developed hardware and software to create a novel data retrieval capability. The capability evolved rapidly through a hardware in the loop simulation environment that enabled incremental component updates for not only the EDR subsystem but across the entire Crew Module. This paper will present an overview of how the EDR subsystem was managed and compare it to an Agile approach to managing projects. The paper will further provide a recommended approach to future Agile-like hardware development that incorporates lessons learned from the EDR experience.

Agile↗

NASA NTRS1981

Spacelab utilization for future optics technology and applications

During the timeframe from 1980 to the year 2000, optics technology and applications experiments will require spacecraft that yield the maximum benefit at minimum cost. Current NASA plans include Spacelab, Power Extension Package (PEP), 25 kW Power System (PS), and a Science Applications and Space Platform (SASP), to satisfy the user needs in low earth orbit (LEO) and geosynchronous orbit (GEO). The purpose of this paper is to acquaint the optics technology user with NASA planning applicable to his future needs. This paper identifies current NASA concepts, including Spacelab hardware, that can be utilized to achieve a broad spectrum of optics scientific and application missions. Evolving configurations of Spacelab hardware elements will be shown that can be utilized as an orbital test platform in LEO and GEO.

De Sanctis, C. E.↗

NASA NTRS2005

Environmental Conditions for Space Flight Hardware: A Survey

Interest in generalization of the physical environment experienced by NASA hardware from the natural Earth environment (on the launch pad), man-made environment on Earth (storage acceptance an d qualification testing), the launch environment, and the space environment, is ed to find commonality among our hardware in an effort to reduce cost and complexity. NASA is entering a period of increase in its number of planetary missions and it is important to understand how our qualification requirements will evolve with and track these new environments. Environmental conditions are described for NASA projects in several ways for the different periods of the mission life cycle. At the beginning, the mission manager defines survivability requirements based on the mission length, orbit, launch date, launch vehicle, and other factors . such as the use of reactor engines. Margins are then applied to these values (temperature extremes, vibration extremes, radiation tolerances, etc,) and a new set of conditions is generalized for design requirements. Mission assurance documents will then assign an additional margin for reliability, and a third set of values is provided for during testing. A fourth set of environmental condition values may evolve intermittently from heritage hardware that has been tested to a level beyond the actual mission requirement. These various sets of environment figures can make it quite confusing and difficult to capture common hardware environmental requirements. Environmental requirement information can be found in a wide variety of places. The most obvious is with the individual projects. We can easily get answers to questions about temperature extremes being used and radiation tolerance goals, but it is more difficult to map the answers to the process that created these requirements: for design, for qualification, and for actual environment with no margin applied. Not everyone assigned to a NASA project may have that kind of insight, as many have only the environmental requirement numbers needed to do their jobs but do not necessarily have a programmatic-level understanding of how all of the environmental requirements fit together.

Plante, Jeannette↗

NASA NTRS2010

History and Benefits of Engine Level Testing Throughout the Space Shuttle Main Engine Program

Rocket engine testing is important throughout a program s life and is essential to the overall success of the program. Space Shuttle Main Engine (SSME) testing can be divided into three phases: development, certification, and operational. Development tests are conducted on the basic design and are used to develop safe start and shutdown transients and to demonstrate mainstage operation. This phase helps form the foundation of the program, demands navigation of a very steep learning curve, and yields results that shape the final engine design. Certification testing involves multiple engine samples and more aggressive test profiles that explore the boundaries of the engine to vehicle interface requirements. The hardware being tested may have evolved slightly from that in the development phase. Operational testing is conducted with mature hardware and includes acceptance testing of flight assets, resolving anomalies that occur in flight, continuing to expand the performance envelope, and implementing design upgrades. This paper will examine these phases of testing and their importance to the SSME program. Examples of tests conducted in each phase will also be presented.

VanHooser, Katherine↗

NASA NTRS1993

Brief summary of the evolution of high-temperature creep-fatigue life prediction models for crack initiation

The evolution of high-temperature, creep-fatigue, life-prediction methods used for cyclic crack initiation is traced from inception in the late 1940's. The methods reviewed are material models as opposed to structural life prediction models. Material life models are used by both structural durability analysts and by material scientists. The latter use micromechanistic models as guidance to improve a material's crack initiation resistance. Nearly one hundred approaches and their variations have been proposed to date. This proliferation poses a problem in deciding which method is most appropriate for a given application. Approaches were identified as being combinations of thirteen different classifications. This review is intended to aid both developers and users of high-temperature fatigue life prediction methods by providing a background from which choices can be made. The need for high-temperature, fatigue-life prediction methods followed immediately on the heels of the development of large, costly, high-technology industrial and aerospace equipment immediately following the second world war. Major advances were made in the design and manufacture of high-temperature, high-pressure boilers and steam turbines, nuclear reactors, high-temperature forming dies, high-performance poppet valves, aeronautical gas turbine engines, reusable rocket engines, etc. These advances could no longer be accomplished simply by trial and error using the 'build-em and bust-em' approach. Development lead times were too great and costs too prohibitive to retain such an approach. Analytic assessments of anticipated performance, cost, and durability were introduced to cut costs and shorten lead times. The analytic tools were quite primitive at first and out of necessity evolved in parallel with hardware development. After forty years more descriptive, more accurate, and more efficient analytic tools are being developed. These include thermal-structural finite element and boundary element analyses, advanced constitutive stress-strain-temperature-time relations, and creep-fatigue-environmental models for crack initiation and propagation. The high-temperature durability methods that have evolved for calculating high-temperature fatigue crack initiation lives of structural engineering materials are addressed. Only a few of the methods were refined to the point of being directly useable in design. Recently, two of the methods were transcribed into computer software for use with personal computers.

Halford, Gary R.↗

NASA NTRS2017

New Development in NASA's Rodent Research Hardware for Conducting Long Duration Biomedical and Basic Research in Space

Animal models, particularly rodents, are the foundation of pre-clinical research to understand human diseases and evaluate new therapeutics, and play a key role in advancing biomedical discoveries both on Earth and in space. The National Research Councils Decadal survey emphasized the importance of expanding NASAs life sciences research to perform long duration, rodent experiments on the International Space Station (ISS). To accomplish this objective, flight hardware, operations, and science capabilities were developed at NASA Ames Research Center (ARC) to enhance science return for both commercial (CASIS) and government-sponsored rodent research. The Rodent Research program at NASA ARC has pioneered a new research capability on the International Space Station and has progressed toward translating research to the ISS utilizing commercial rockets, collaborating with academia and science industry, while training crewmembers to assist in performing research on orbit. Throughout phases of these missions, our practices, hardware and operations have evolved from tested to developed standards, and we are able to modify and customize our procedure and operations for mission specific requirements. The Rodent Research Habitat is capable of providing a living environment for animals on ISS according to standard animal welfare requirements. Using the cameras in the Habitat, the Rodent Research team has the ability to perform daily health checks on animals, and further analyze the collected videos for behavioral studies. A recent development of the Rodent Research hardware is inclusion of enrichment, to provide the animals the ability to rest and huddle. The Enrichment Hut is designed carefully for adult mice (up to 35 week old) within animal welfare, engineering, and operations constraints. The Hut is made out of the same stainless steel mesh as the cage interior, it has an ingress and an egress to allow animals move freely, and a hinge door to allow crewmembers remove the animals easily. The Rodent Research team has also developed Live Animal Return (LAR) capability, which will be implemented during Rodent Research-5 mission for the first time. The animals will be transported from the Habitat to a Transporter, which will return on the Dragon capsule and splashes down in the Pacific Ocean. Once SpaceX retrieves the Dragon, all powered payloads will be transferred to a SeaVan and transferred to the Long Beach pier. The NASA team then receives the transporter and delivers to a PI-designated laboratory within 120 mile radius of Long Beach. This is a significant improvement allowing researchers to examine animals within 72 hrs. of reentry or to conduct recovery experiments. Together, the hardware improvements and experience that the Rodent Research team has gained working with principal investigators and ISS crew to conduct complex experiments on orbit are expanding capabilities for long duration rodent research on the ISS to achieve both basic science and biomedical objectives.

ISS↗

NASA NTRS1976

Atmospheric, Magnetospheric and Plasmas in Space (AMPS) spacelab payload definition study - program analysis and planning for phase C/D document - Volume 7

Typical missions identified for AMPS flights in the arly 1980's are described. Experiment objectives and typical scientific instruments selected to accomplish these objectives are discussed along with mission requirements and shuttle and Spacelab capabilities assessed to determine any AMPS unique requirements. Preliminary design concepts for the first two AMPS flights form the basis for the Phase C/D program plan. This plan implements flights 1 and 2 and indicates how both the scientific and flight support hardware can be systematically evolved for future AMPS flights.

Keeley, J. T.↗

NASA NTRS1993

An evaluation of software tools for the design and development of cockpit displays

The use of all-glass cockpits at the NASA Langley Research Center (LaRC) simulation facility has changed the means of design, development, and maintenance of instrument displays. The human-machine interface has evolved from a physical hardware device to a software-generated electronic display system. This has subsequently caused an increased workload at the facility. As computer processing power increases and the glass cockpit becomes predominant in facilities, software tools used in the design and development of cockpit displays are becoming both feasible and necessary for a more productive simulation environment. This paper defines LaRC requirements of a display software development tool and compares two available applications against these requirements. As a part of the software engineering process, these tools reduce development time, provide a common platform for display development, and produce exceptional real-time results.

Ellis, Thomas D., Jr.↗

NASA NTRS1998

Evolvable Electronic Systems

Explore the source record for details and available documents.

Evolvable Systems hardware engineered electronics ↗

NASA NTRS2007

Microbiological Monitoring for the Constellation Program: Current Requirements and Future Considerations

Microbiological requirements for spaceflight are based on assessments of infectious disease risk which could impact crew health or mission success. The determination of risk from infectious disease is composed of several factors including (1) crew susceptibility, (2) crew exposure to the infectious disease agent, (3) the concentration of the infectious agent, and (4) the characteristics of the infectious agent. As a result of the Health Stabilization Program, stringent monitoring, and cleaning protocols, in-flight environmental microbial monitoring is not necessary for short-duration spaceflights. However, risk factors change for long-duration missions, as exemplified by the presence of medically significant organisms in the environments of both the Mir and International Space Station (ISS). Based upon this historical evidence, requirements for short duration usage aboard the Orion Crew Exploration Vehicle and Lunar Lander Vehicle will not require in-flight monitoring; however, as mission duration increases with a Lunar Outpost, an ability to detect microbial hazard will be necessary. The nature of the detection requirements will depend on the maturity of technology in a rapidly evolving marketplace. Regardless, the hardware will still need to maximize information to discipline experts and the crew, while minimizing the size, mass, power consumption, and crew time usage. The refinement of these monitors will be a major goal in our efforts to travel successfully to Mars.

Ott, C. Mark↗

DOE OSTI2024

Approaches for Autonomous Peer to Peer Communication: For Resilient Community Microgrids

The final phase of the Islandable Communications task of the SECURE project consisted of integrating the islandable communications network into a microgrid simulation at NREL. Initially integration was planned for a microgrid implemented as a mix of simulation and physical hardware. As the project evolved, the microgrid became fully simulated. The simulation environment was structured to break out the communication paths that would pass over a communication network in a field demonstration. The Islandable Communication network was integrated into the simulation environment, allowing both a commercial cellular carrier and a Private LTE network to be evaluated. The microgrid simulation showed differences in performance and behavior when operating over the wireless networks (compared to operating over wired Ethernet in the lab). These differences point to further research opportunities to better understand how microgrid communication carried over real-world or impaired networks affects the microgrid system behavior.

24 POWER TRANSMISSION AND DISTRIBUTION↗

DOE OSTI2024

Modernizing Fermilab's Accelerator Control Hardware

Modernizing the Fermilab accelerator control system is essential to future operations of the laboratory's accelerator complex. The existing control system has evolved over four decades and uses hardware that is no longer available.The Accelerator Controls Operations Research Network (ACORN) Project will modernize the control system and replace end-of-life power supplies to enable future accelerator complex operations with megawatt particle beams. The ACORN project is planning to replace Fermilab s obsolete CAMAC crate-and-card controls hardware with modern MicroTCA hardware. There are over 2,000 CAMAC cards and over 250 CAMAC crates serving various functions in Fermilab s control system. We will review the existing CAMAC hardware and provide updates on the status of the ACORN project, which includes the conceptual design of the MicroTCA replacement hardware and software tools for supporting the installation of hundreds of MicroTCA crates.

43 PARTICLE ACCELERATORS↗

NASA NTRS2011

Solid Rocket Booster (SRB) Flight System Integration at Its Best

The Solid Rocket Booster (SRB) element integrates all the subsystems needed for ascent flight, entry, and recovery of the combined Booster and Motor system. These include the structures, avionics, thrust vector control, pyrotechnic, range safety, deceleration, thermal protection, and retrieval systems. This represents the only human-rated, recoverable and refurbishable solid rocket ever developed and flown. Challenges included subsystem integration, thermal environments and severe loads (including water impact), sometimes resulting in hardware attrition. Several of the subsystems evolved during the program through design changes. These included the thermal protection system, range safety system, parachute/recovery system, and others. Because the system was recovered, the SRB was ideal for data and imagery acquisition, which proved essential for understanding loads, environments and system response. The three main parachutes that lower the SRBs to the ocean are the largest parachutes ever designed, and the SRBs are the largest structures ever to be lowered by parachutes. SRB recovery from the ocean was a unique process and represented a significant operational challenge; requiring personnel, facilities, transportation, and ground support equipment. The SRB element achieved reliability via extensive system testing and checkout, redundancy management, and a thorough postflight assessment process. However, the in-flight data and postflight assessment process revealed the hardware was affected much more strongly than originally anticipated. Assembly and integration of the booster subsystems required acceptance testing of reused hardware components for each build. Extensive testing was done to assure hardware functionality at each level of stage integration. Because the booster element is recoverable, subsystems were available for inspection and testing postflight, unique to the Shuttle launch vehicle. Problems were noted and corrective actions were implemented as needed. The postflight assessment process was quite detailed and a significant portion of flight operations. The SRBs provided fully redundant critical systems including thrust vector control, mission critical pyrotechnics, avionics, and parachute recovery system. The design intent was to lift off with full redundancy. On occasion, the redundancy management scheme was needed during flight operations. This paper describes some of the design challenges and technical issues, how the design evolved with time, and key areas where hardware reusability contributed to improved system level understanding.

Wood, T. David↗

NASA NTRS2011

Solid Rocket Booster (SRB) - Evolution and Lessons Learned During the Shuttle Program

The Solid Rocket Booster (SRB) element integrates all the subsystems needed for ascent flight, entry, and recovery of the combined Booster and Motor system. These include the structures, avionics, thrust vector control, pyrotechnic, range safety, deceleration, thermal protection, and retrieval systems. This represents the only human-rated, recoverable and refurbishable solid rocket ever developed and flown. Challenges included subsystem integration, thermal environments and severe loads (including water impact), sometimes resulting in hardware attrition. Several of the subsystems evolved during the program through design changes. These included the thermal protection system, range safety system, parachute/recovery system, and others. Obsolescence issues occasionally required component recertification. Because the system was recovered, the SRB was ideal for data and imagery acquisition, which proved essential for understanding loads and system response. The three main parachutes that lower the SRBs to the ocean are the largest parachutes ever designed, and the SRBs are the largest structures ever to be lowered by parachutes. SRB recovery from the ocean was a unique process and represented a significant operational challenge; requiring personnel, facilities, transportation, and ground support equipment. The SRB element achieved reliability via extensive system testing and checkout, redundancy management, and a thorough postflight assessment process. Assembly and integration of the booster subsystems was a unique process and acceptance testing of reused hardware components was required for each build. Extensive testing was done to assure hardware functionality at each level of stage integration. Because the booster element is recoverable, subsystems were available for inspection and testing postflight, unique to the Shuttle launch vehicle. Problems were noted and corrective actions were implemented as needed. The postflight assessment process was quite detailed and a significant portion of flight operations. The SRBs provided fully redundant critical systems including thrust vector control, mission critical pyrotechnics, avionics, and parachute recovery system. The design intent was to lift off with full redundancy. On occasion, the redundancy management scheme was needed during flight operations. This paper describes some of the design challenges, how the design evolved with time, and key areas where hardware reusability contributed to improved system level understanding.

Kanner, Howard S.↗

NASA NTRS1985

Solid rocket booster retrieval operations

Solid Rocket Booster Retrieval operations are discussed in detail. The recovery of expended boosters and associated hardware without damage attributable to retrieval procedures is the main goal. The retrieval force consists tof ship's personnel and retrieval team members, each of whom has been trained and is highly skilled in multi-faceted operations. The retrieval force is equipped with two specially-built, highly maneuverable ships outfitted with parachute reels, retrieval cranes, towing winches, large volume-low pressure air compressors, SCUBA diving gear, inflatable boats with outboard motors and diver-operated SRB dewatering devices. The two ships are deployed in sufficient time to conduct an electronic and visual search of the impact area prior to launch. Upon search completeion, each ship takes station a safe distance from the predetermined impact point initiating both visual and electronic search in the direction of flight path, ensuring SRB acquisition at splashdown. When safe, the ships enter the impact area and commence recovery of all floating flight hardware which is subsequently returned to the Disassembly Facility for refurbishment and reuse. Retrieval techniques have evolved in parallel with equipment and flight hardware configuration changes. Additional changes have been initiated to improve personnel safety.

Rasmussen, A. M.↗

NASA NTRS1978

A comparison of hardware description languages

Several high level languages which evolved over the past few years for describing and simulating the structure and behavior of digital systems, on digital computers are assessed. The characteristics of the four prominent languages (CDL, DDL, AHPL, ISP) are summarized. A criterion for selecting a suitable hardware description language for use in an automatic integrated circuit design environment is provided.

Shiva, S. G.↗

NASA NTRS2002

Evolving circuits in seconds: experiments with a stand-alone board-level evolvable system

The purpose of this paper is twofold: first, to illustrate a stand-alone board-level evolvable system (SABLES) and its performance, and second to illustrate some problems that occur during evolution with real hardware in the loop, or when the intention of the user is not completely reflected in the fitness function.

evolvable hardware FPTA DSP evolutionary algorithm↗

DOE OSTI2025

A distributed voltage inference framework for cyber-physical attacks detection and localization in active distribution grids

The transition to active distribution grids with real-time monitoring and control depends on the proliferation of advanced communication networks and devices. This paradigm shift towards a cyber-physical architecture also introduces new vulnerabilities for adversaries to exploit and launch sophisticated cyber-physical attacks targeting grid observability. Current research highlights the challenges in distinguishing attacks on voltage phasor or nodal injection measurements and isolating multi-source attack locations in a multiphase distribution grid. The attack detection and localization methods in literature face accuracy issues, applications across diverse attack scenarios, or scalability limits. Here, to bridge these gaps, this paper proposes a distributed Voltage Inference framework for real-time detection and localization of cyber-physical attacks, addressing scalability, adaptability, and accuracy challenges in state-of-the-art methods. The proposed methodology leverages the distributed nature of the Voltage Inference framework through a two-step process of prediction and correction, together with a tractable graph partitioning approach, providing a reliable solution to identify compromised measurement sources and facilitate isolation. Extensive testing on IEEE 13 and 123-node distribution feeders underscores the algorithm’s efficacy, enhancing the security and resilience of active distribution grids against evolving cyber threats. Additionally, Hardware-in-the-Loop (HIL) implementation validates the proposed strategy’s practical applicability in real-world scenarios.

active distribution grids↗