Search NASA⌕ Search

SEARCH · Search NASA

Results for “hardware performance”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

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

At least 55 records · Page 3

A design methodology for portable software on parallel computers

This final report for research that was supported by grant number NAG-1-995 documents our progress in addressing two difficulties in parallel programming. The first difficulty is developing software that will execute quickly on a parallel computer. The second difficulty is transporting software between dissimilar parallel computers. In general, we expect that more hardware-specific information will be included in software designs for parallel computers than in designs for sequential computers. This inclusion is an instance of portability being sacrificed for high performance. New parallel computers are being introduced frequently. Trying to keep one's software on the current high performance hardware, a software developer almost continually faces yet another expensive software transportation. The problem of the proposed research is to create a design methodology that helps designers to more precisely control both portability and hardware-specific programming details. The proposed research emphasizes programming for scientific applications. We completed our study of the parallelizability of a subsystem of the NASA Earth Radiation Budget Experiment (ERBE) data processing system. This work is summarized in section two. A more detailed description is provided in Appendix A ('Programming Practices to Support Eventual Parallelism'). Mr. Chrisman, a graduate student, wrote and successfully defended a Ph.D. dissertation proposal which describes our research associated with the issues of software portability and high performance. The list of research tasks are specified in the proposal. The proposal 'A Design Methodology for Portable Software on Parallel Computers' is summarized in section three and is provided in its entirety in Appendix B. We are currently studying a proposed subsystem of the NASA Clouds and the Earth's Radiant Energy System (CERES) data processing system. This software is the proof-of-concept for the Ph.D. dissertation. We have implemented and measured the performance of a portion of this subsystem on the Intel iPSC/2 parallel computer. These results are provided in section four. Our future work is summarized in section five, our acknowledgements are stated in section six, and references for published papers associated with NAG-1-995 are provided in section seven.

Nicol, David M.↗

Thruster-Specific Force Estimation and Trending of Cassini Hydrazine Thrusters at Saturn

The Cassini spacecraft has been in orbit around Saturn since 2004 and has since been approved for both a first and second extended mission. As hardware reaches and exceeds its documented life expectancy, it becomes vital to closely monitor hardware performance. The performance of the 1-N hydrazine attitude control thrusters is especially important to study, because the spacecraft is currently operating on the back-up thruster branch. Early identification of hardware degradation allows more time to develop mitigation strategies. There is no direct measure of an individual thruster's thrust magnitude, but these values can be estimated by post-processing spacecraft telemetry. This paper develops an algorithm to calculate the individual thrust magnitudes using Euler's equation. The algorithm correctly shows the known degradation in the first thruster branch, validating the approach. Results for the current thruster branch show nominal performance as of August, 2015.

Stupik, Joan↗

Core Community Specifications for Electron Microprobe Operating Systems: Software, Quality Control, and Data Management Issues

Modem electron microprobe systems have become increasingly sophisticated. These systems utilize either UNIX or PC computer systems for measurement, automation, and data reduction. These systems have undergone major improvements in processing, storage, display, and communications, due to increased capabilities of hardware and software. Instrument specifications are typically utilized at the time of purchase and concentrate on hardware performance. The microanalysis community includes analysts, researchers, software developers, and manufacturers, who could benefit from exchange of ideas and the ultimate development of core community specifications (CCS) for hardware and software components of microprobe instrumentation and operating systems.

Fournelle, John↗

System design parameter study for Shuttle Infrared Telescope Facility (SIRTF)

SIRTF is a high-sensitivity, cooled astronomical telescope operating from 2 to 1000 microns. The techniques used in analyzing the sensitivity of the SIRTF system performance to several technical issues are presented. Lowering the telescope temperature to near 4K is found to produce margin in several areas. A refined observing requirements model relieves the hardware performance requirements, and identifies extended source size/observing strategy as an important system specification. Other major conclusions are presented.

Mord, A. J.↗

Acceptance Testing of a Satellite SCADA Photovoltaic-Diesel Hybrid System

Satellite Supervisory Control and Data Acquisition (SCADA) of a Photovoltaic (PV)/diesel hybrid system was tested using NASA's Advanced Communication Technology Satellite (ACTS) and Ultra Small Aperture Terminal (USAT) ground stations. The setup consisted of a custom-designed PV/diesel hybrid system, located at the Florida Solar Energy Center (FSEC), which was controlled and monitored at a "remote" hub via Ka-band satellite link connecting two 1/4 Watt USATs in a SCADA arrangement. The robustness of the communications link was tested for remote monitoring of the health and performance of a PV/diesel hybrid system, and for investigating load control and battery charging strategies to maximize battery capacity and lifetime, and minimize loss of critical load probability. Baseline hardware performance test results demonstrated that continuous two-second data transfers can be accomplished under clear sky conditions with an error rate of less than 1%. The delay introduced by the satellite (1/4 sec) was transparent to synchronization of satellite modem as well as to the PV/diesel-hybrid computer. End-to-end communications link recovery times were less than 36 seconds for loss of power and less than one second for loss of link. The system recovered by resuming operation without any manual intervention, which is important since the 4 dB margin is not sufficient to prevent loss of the satellite link during moderate to heavy rain. Hybrid operations during loss of communications link continued seamlessly but real-time monitoring was interrupted. For this sub-tropical region, the estimated amount of time that the signal fade will exceed the 4 dB margin is about 10%. These results suggest that data rates of 4800 bps and a link margin of 4 dB with a 1/4 Watt transmitter are sufficient for end-to-end operation in this SCADA application.

Kalu, A.↗

Technical Consultation of the International Space Station (ISS) Internal Active Thermal Control System (IATCS) Cooling Water Chemistry

The Internal Active Thermal Control System (IATCS) coolant exhibited unexpected chemical changes during the first year of on-orbit operation following the launch and activation in February 2001. The coolant pH dropped from 9.3 to below the minimum specification limit of 9.0, and re-equilibrated between 8.3 and 8.5. This drop in coolant pH was shown to be the result of permeation of CO2 from the cabin into the coolant via Teflon flexible hoses which created carbonic acid in the fluid. This unexpected diffusion was the result of having a cabin CO2 partial pressure higher than the ground partial pressure (average 4.0 mmHg vs. less than 0.2 mmHg). This drop in pH was followed by a concurrent increasing coolant nickel concentration. No other metal ions were observed in the coolant and based on previous tests, the source of nickel ion was thought to be the boron nickel (BNi) braze intermetallics used in the construction of HXs and cold plates. Specifically, BNi2 braze alloy was used for the IATCS IFHX and BNi3 braze alloy was used for the IATCS Airlock Servicing and Performance Checkout Unit (SPCU) HX and cold plates. Given the failure criticality of the HXs, a Corrosion Team was established by the IATCS CWG to determine the impact of the nickel corrosion on hardware performance life.

Gentz, Steven J.↗

An Overview of the Guided Parafoil System Derived from X-38 Experience

The NASA Johnson Space Center built a 4200 sq ft parafoil for the U.S. Army Natick Soldier Center to demonstrate autonomous flight using a guided parafoil system to deliver 10,000 lbs of useable payload. The parafoil's design was based upon that developed during the X-38 program. The drop test payload consisted of a standard 20-foot Type V airdrop platform, a standard 12-foot weight tub, a 60 ft drogue parachute, a 4200 ft2 parafoil, an instrumentation system, and a Guidance, Navigation, and Control (GN&C) system. Instrumentation installed on the load was used to gather data to validate simulation models and preflight loads predictions and to perform post flight trajectory and performance reconstructions. The GN&C system, developed during NASA's X-38 program, consisted of a flight computer, modems for uplink commands and downlink data, a compass, laser altimeter, and two winches. The winches were used to steer the parafoil and to perform the dynamic flare maneuver for a soft landing. The laser was used to initiate the flare. The GN&C software was originally provided to NASA by the European Space Agency. NASA incorporated further software refinements based upon the X-38 flight test results. Three full-scale drop tests were conducted, with the third being performed during the Precision Airdrop Technology Conference and Demonstration (PATCAD) Conference at the U.S. Army Yuma Proving Ground (YPG) in November of 2003. For the PATCAD demonstration, the parafoil and GN&C software and hardware performed well, concluding with a good flare and the smallest miss distance ever experienced in NASA's parafoil drop test program. This paper describes the 4200 sq ft parafoil system, simulation results, and the results of the drop tests.

Stein, Jenny M.↗

Redundancy management of inertial systems.

The paper reviews developments in failure detection and isolation techniques applicable to gimballed and strapdown systems. It examines basic redundancy management goals of improved reliability, performance and logistic costs, and explores mechanizations available for both input and output data handling. The meaning of redundant system reliability in terms of available coverage, system MTBF, and mission time is presented and the practical hardware performance limitations of failure detection and isolation techniques are explored. Simulation results are presented illustrating implementation coverages attainable considering IMU performance models and mission detection threshold requirements. The implications of a complete GN&C redundancy management method on inertial techniques are also explored.

Mckern, R. A.↗

Phase 2 program on ground test of refanned JT8D turbofan engines and nacelles for the 727 airplane. Volume 3: Ground tests

The NASA Refan Program included full-scale performance and noise ground tests of both a current production (JT8D-15) and a refanned (JT8D-115) engine. A description of the two ground tests including detailed propulsion, noise, and structural test results is presented. The primary objectives of the total test program were comparison of JT8D-15 and JT8D-115 overall propulsion system performance and noise characteristics and determination of incremental component noise levels. Other objectives of the test program included: (1) determination of acoustic treatment effectiveness; (2) measurement of internal sound pressure levels; (3) measurement of inlet and exhaust hardware performance; (4) determination of center-engine surge margin; and (5) evaluation of certain structural characteristics associated with the 727 refan center-engine inlet duct and JT8D refan engine exhaust system. The JT8D-15 and -115 tests were conducted during September 1974 and January to March 1975, respectively. Analyses of the test data indicated that the JT8D-115, as compared to the JT8D-15, demonstrates a 12.5 percent to 13.2 percent reduction in static specific fuel consumption, and a reduction of 6 to 7 PNdB in a weighted average value of static tone corrected perceived noise level. Separated into noise components, a significant reduction was shown for the inlet fan, aft fan, exhaust duct flow, turbine, and jet noises. However, core noise was increased. Photographs of test stands and test equipment are shown.

Source record↗

Constellation's First Flight Test: Ares I-X

On October 28, 2009, NASA launched Ares I-X, the first flight test of the Constellation Program that will send human beings to the Moon and beyond. This successful test is the culmination of a three-and-a-half-year, multi-center effort to design, build, and fly the first demonstration vehicle of the Ares I crew launch vehicle, the successor vehicle to the Space Shuttle. The suborbital mission was designed to evaluate the atmospheric flight characteristics of a vehicle dynamically similar to Ares I; perform a first stage separation and evaluate its effects; characterize and control roll torque; stack, fly, and recover a solid-motor first stage testing the Ares I parachutes; characterize ground, flight, and reentry environments; and develop and execute new ground hardware and procedures. Built from existing flight and new simulator hardware, Ares I-X integrated a Shuttle-heritage four-segment solid rocket booster for first stage propulsion, a spacer segment to simulate a five-segment booster, Peacekeeper axial engines for roll control, and Atlas V avionics, as well as simulators for the upper stage, crew module, and launch abort system. The mission leveraged existing logistical and ground support equipment while also developing new ones to accommodate the first in-line rocket for flying astronauts since the Saturn IB last flew from Kennedy Space Center (KSC) in 1975. This paper will describe the development and integration of the various vehicle and ground elements, from conception to stacking in KSC s Vehicle Assembly Building; hardware performance prior to, during, and after the launch; and preliminary lessons and data gathered from the flight. While the Constellation Program is currently under review, Ares I-X has and will continue to provide vital lessons for NASA personnel in taking a vehicle concept from design to flight.

Davis, Stephan R.↗

Independent Orbiter Assessment (IOA): Analysis of the electrical power distribution and control subsystem, volume 1

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. The IOA approach features a top-down analysis of the hardware to determine failure modes, criticality, and potential critical items. To preserve independence, this analysis was accomplished without reliance upon the results contained within the NASA FMEA/CIL documentation. This report documents the independent analysis results corresponding to the Orbiter Electrical Power Distribution and Control (EPD and C) hardware. The EPD and C hardware performs the functions of distributing, sensing, and controlling 28 volt DC power and of inverting, distributing, sensing, and controlling 117 volt 400 Hz AC power to all Orbiter subsystems from the three fuel cells in the Electrical Power Generation (EPG) subsystem. Each level of hardware was evaluated and analyzed for possible failure modes and effects. Criticality was assigned based upon the severity of the effect for each failure mode. Of the 1671 failure modes analyzed, 9 single failures were determined to result in loss of crew or vehicle. Three single failures unique to intact abort were determined to result in possible loss of the crew or vehicle. A possible loss of mission could result if any of 136 single failures occurred. Six of the criticality 1/1 failures are in two rotary and two pushbutton switches that control External Tank and Solid Rocket Booster separation. The other 6 criticality 1/1 failures are fuses, one each per Aft Power Control Assembly (APCA) 4, 5, and 6 and one each per Forward Power Control Assembly (FPCA) 1, 2, and 3, that supply power to certain Main Propulsion System (MPS) valves and Forward Reaction Control System (RCS) circuits.

Schmeckpeper, K. R.↗

Space life support engineering program

This report covers the first six months of work performed under the NASA University Grant awarded to Iowa State University to perform research on two topics relating to the development of closed-loop long-term life support systems. A comprehensive study to develop software to simulate the dynamic operation of water reclamation systems in long-term closed-loop life support systems is being carried out as part of an overall program for the design of systems for a Mars voyage. This project is being done in parallel with a similar effort in the Department of Chemistry to develop durable accurate low-cost sensors for monitoring of trace chemical and biological species in recycled water supplies. Aspen-Plus software is being used on a group of high-performance workstations to develop the steady state descriptions for a number of existing technologies. Following completion, a dynamic simulation package will be developed for determining the response of such systems to changes in the metabolic needs of the crew and to upsets in system hardware performance.

Seagrave, Richard C.↗

Space life support engineering program

A comprehensive study to develop software to simulate the dynamic operation of water reclamation systems in long-term closed-loop life support systems is being carried out as part of an overall program for the design of systems for a moon station or a Mars voyage. This project is being done in parallel with a similar effort in the Department of Chemistry to develop durable accurate low-cost sensors for monitoring of trace chemical and biological species in recycled water supplies. Aspen-Plus software is being used on a group of high-performance work stations to develop the steady state descriptions for a number of existing technologies. Following completion, a dynamic simulation package will be developed for determining the response of such systems to changes in the metabolic needs of the crew and to upsets in system hardware performance.

Seagrave, Richard C.↗

Study of advanced atmospheric entry systems for Mars

Entry system designs are described for various advanced Mars missions including sample return, hard lander, and Mars airplane. The Mars exploration systems for sample return and the hard lander require decleration from direct approach entry velocities of about 6 km/s to terminal velocities consistent with surface landing requirements. The Mars airplane entry system is decelerated from orbit at 4.6 km/s to deployment near the surface. Mass performance characteristics of major elements of the Mass performance characteristics are estimated for the major elements of the required entry systems using Viking technology or logical extensions of technology in order to provide a common basis of comparison for the three entry modes mission mode approaches. The entry systems, although not optimized, are based on Viking designs and reflect current hardware performance capability and realistic mass relationships.

Source record↗

Reusable Solid Rocket Motor - Accomplishments, Lessons, and a Culture of Success

The Reusable Solid Rocket Motor represents the largest solid rocket motor ever flown and the only human rated solid motor. Each Reusable Solid Rocket Motor (RSRM) provides approximately 3-million lb of thrust to lift the integrated Space Shuttle vehicle from the launch pad. The motors burn out approximately 2 minutes later, separate from the vehicle and are recovered and refurbished. The size of the motor and the need for high reliability were challenges. Thrust shaping, via shaping of the propellant grain, was needed to limit structural loads during ascent. The motor design evolved through several block upgrades to increase performance and to increase safety and reliability. A major redesign occurred after STS-51L with the Redesigned Solid Rocket Motor. Significant improvements in the joint sealing systems were added. Design improvements continued throughout the Program via block changes with a number of innovations including development of low temperature o-ring materials and incorporation of a unique carbon fiber rope thermal barrier material. Recovery of the motors and post flight inspection improved understanding of hardware performance, and led to key design improvements. Because of the multidecade program duration material obsolescence was addressed, and requalification of materials and vendors was sometimes needed. Thermal protection systems and ablatives were used to protect the motor cases and nozzle structures. Significant understanding of design and manufacturing features of the ablatives was developed during the program resulting in optimization of design features and processing parameters. The project advanced technology in eliminating ozone-depleting materials in manufacturing processes and the development of an asbestos-free case insulation. Manufacturing processes for the large motor components were unique and safety in the manufacturing environment was a special concern. Transportation and handling approaches were also needed for the large hardware segments. The reusable solid rocket motor achieved significant reliability via process control, ground test programs, and postflight assessment. Process control is mandatory for a solid rocket motor as an acceptance test of the delivered product is not feasible. Process control included process failure modes and effects analysis, statistical process control, witness panels, and process product integrity audits. Material controls and inspections were maintained throughout the sub tier vendors. Material fingerprinting was employed to assess any drift in delivered material properties. The RSRM maintained both full scale and sub-scale test articles. These enabled continuous improvement of design and evaluation of process control and material behavior. Additionally RSRM reliability was achieved through attention to detail in post flight assessment to observe any shift in performance. The postflight analysis and inspections provided invaluable reliability data as it enables observation of actual flight performance, most of which would not be available if the motors were not recovered. These unique challenges, features of the reusable solid rocket motor, materials and manufacturing issues, and design improvements will be discussed in the paper.

Moore, Dennis R.↗

Enabling Reliable, Fault-Tolerant Autonomous Lunar Habitats with High-Performance Spaceflight Computing

The lunar surface presents unfavorable constraints and harsh living conditions. To address these challenges, autonomous habitats will require complex integrated systems that combine advanced software, high-performance hardware, and cutting-edge sensors to ensure sustainability, safety, and operational efficiency. Consequently, maintaining a sustainable presence on the Moon requires reliable infrastructure and efficient development, precise monitoring, and utilization of resources within a lunar installation. These elements are essential not only to ensure that lunar settlement can be long-term, self-sustaining, and resource-efficient, but also to serve as a foundation for future missions and eventual human habitation on Mars. Humans are not native to the Moon; therefore, our survival and ability to thrive will depend on autonomous systems that can foster safety and resilience through high-availability architectures, graceful degradation, and highly fault-tolerant spaceflight hardware capable of continuing operation during failures. This requires advanced human-rated distributed systems architectures with specialized electronics, scalable capabilities, and an integrated design approach. Unlike current practices focused on short-term missions and regularly maintained components, permanent lunar compute systems must be designed for extended operations beyond mission durations. This paper explores the necessity of transitioning toward fault- tolerant, highly autonomous hardware systems designed for multi-year missions. It also identifies critical subsystems that require high levels of autonomy, supported by radiation-hardened processors and extreme thermal loads, which are essential to mitigate long-term degradation and ensure sustainable lunar habitation. Finally, the paper aligns with NASA’s identified Civil Space Shortfalls, particularly in high-performance onboard computing, advanced data acquisition, extreme-environment avionics, radiation monitoring and countermeasures, and autonomous health management. It proposes NASA’s new High-Performance Spaceflight Computing (HPSC) processor as a turnkey solution, delivering 100 times the performance-per-watt of legacy rad-hard CPUs and enabling onboard AI, edge computing, and fault-tolerant features essential for sustained lunar autonomy and beyond.

Sarkis S Mikaelian↗

Automated Software for Manned Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C Dempsey↗

Automated Software for Manned Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C. Dempsey↗