Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Backup power”

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.

152 records · Page 9

NASA Tech Briefs, July 2013

Dielectrophoresis-Based Particle Sensor Using Nanoelectrode Arrays; Multi-Dimensional Damage Detection for Surfaces and Structures; ULTRA: Underwater Localization for Transit and Reconnaissance Autonomy; Autonomous Cryogenic Leak Detector for Improving Launch Site Operations; Submillimeter Planetary Atmospheric Chemistry Exploration Sounder; Method for Reduction of Silver Biocide Plating on Metal Surfaces; Silicon Micromachined Microlens Array for THz Antennas; Forward-Looking IED Detector Ground Penetrating Radar; Fully Printed, Flexible, Phased Array Antenna for Lunar Surface Communication, Battery Charge Equalizer with Transformer Array; An Efficient, Highly Flexible Multi-Channel Digital Downconverter Architecture; Dimmable Electronic Ballast for a Gas Discharge Lamp; Conductive Carbon Nanotube Inks for Use with Desktop Inkjet Printing Technology; Enhanced Schapery Theory Software Development for Modeling Failure of Fiber-Reinforced Laminates; High-Performance, Low-Temperature-Operating, Long-Lifetime Aerospace Lubricants; Carbon Nanotube Microarrays Grown on Nanoflake Substrates; Differential Muon Tomography to Continuously Monitor Changes in the Composition of Subsurface Fluids; Microgravity Drill and Anchor System; 20 Granular Media-Based Tunable Passive Vibration Suppressor; 21 Miga Aero Actuator and 2D Machined Mechanical Binary Latch; Micro-XRF for In Situ Geological Exploration of Other Planets; Hydrogen-Enhanced Lunar Oxygen Extraction and Storage Using Only Solar Power; Uplift of Ionospheric Oxygen Ions During Extreme Magnetic Storms; Miniaturized, High-Speed, Modulated X-Ray Source; Hollow-Fiber Spacesuit Water Membrane Evaporator 25 High-Power Single-Mode 2.65-micrometers InGaAsSb/AlInGaAsSb Diode Lasers; Optical Device for Converting a Laser Beam Into Two Co-aligned but Oppositely Directed Beams; A Hybrid Fiber/Solid-State Regenerative Amplifier with Tunable Pulse Widths for Satellite Laser Ranging; X-Ray Diffractive Optics; SynGenics Optimization System (SynOptSys); 29 CFD Script for Rapid TPS Damage Assessment; radEq Add-On Module for CFD Solver Loci-CHEM; Science Opportunity Analyzer (SOA) Version 8; 30 Autonomous Byte Stream Randomizer; Distributed Engine Control Empirical/Analytical Verification Tools; Dynamic Server-Based KML Code Generator Method for Level-of-Detail Traversal of Geospatial Data; Automated Planning of Science Products Based on Nadir Overflights and Alerts for Onboard and Ground Processing; Linked Autonomous Interplanetary Satellite Orbit Navigation; Risk-Constrained Dynamic Programming for Optimal Mars Entry, Descent, and Landing; Scheduling Operations for Massive Heterogeneous Clusters; Deepak Condenser Model (DeCoM); Flight Software Math Library; Recirculating 1-K-Pot for Pulse-Tube Cryostats; 35 Method for Processing Lunar Regolith Using Microwaves; Wells for In Situ Extraction of Volatiles from Regolith (WIEVR); and Estimating the Backup Reaction Wheel Orientation Using Reaction Wheel Spin Rates Flight Telemetry from a Spacecraft.

Source record↗

GPM Mission's Best Practices: PERP

Similar to other missions, the Global Precipitation Measurement (GPM) Core Observatory's Command and Data Handling (C&DH) subsystem is critical for operations of the spacecraft. The onboard C&DH system comprises of two fully redundant boxes - a primary and a cold backup. Within each box, amongst other components, is a Single Board Computer (SBC) that hosts the flight software (FSW) system. In the event of an SBC reset, the Flight Operations Team (FOT) is poised with a lengthy task of restoring the SBC to nominal configuration. Due to the complexity of the C&DH system, this may take many days at a time to complete. The spacecraft's FSW applications are located in Electronically Erasable Programmable Read-Only Memory (EEPROM) and are copied into Random Access Memory (RAM) upon SBC initialization/reset. Each SBC has two banks of EEPROM, with each bank containing a copy of the FSW. Since launch, there have been many configuration changes to tables and applications that have been loaded into just RAM. Unfortunately, these changes are vulnerable to being wiped during a SBC initialization/reset, when the RAM is overwritten by the EEPROM. Although the EEPROM loads the default FSW configurations, the process to command non-default individual table and application changes is very cumbersome and time consuming. This consequentially increases the time until the spacecraft is back into nominal Mission Science Mode (MSM) drastically. The GPM Power-On Reset (POR) Expedited Recovery Process (PERP) Design introduces a method of consolidating commands into a single file load which the SBC can process independently of the ground - decreasing recovery time, the level of TDRS support reliance, and human error. This tested design can be implemented across many other missions that utilize a similar core Flight Executive (cFE) platform; hence providing an easy-to-follow, safe, and efficient process that can be applied across the board.

recovery↗

Tools Ensure Reliability of Critical Software

In November 2006, after attempting to make a routine maneuver, NASA's Mars Global Surveyor (MGS) reported unexpected errors. The onboard software switched to backup resources, and a 2-day lapse in communication took place between the spacecraft and Earth. When a signal was finally received, it indicated that MGS had entered safe mode, a state of restricted activity in which the computer awaits instructions from Earth. After more than 9 years of successful operation gathering data and snapping pictures of Mars to characterize the planet's land and weather communication between MGS and Earth suddenly stopped. Months later, a report from NASA's internal review board found the spacecraft's battery failed due to an unfortunate sequence of events. Updates to the spacecraft's software, which had taken place months earlier, were written to the wrong memory address in the spacecraft's computer. In short, the mission ended because of a software defect. Over the last decade, spacecraft have become increasingly reliant on software to carry out mission operations. In fact, the next mission to Mars, the Mars Science Laboratory, will rely on more software than all earlier missions to Mars combined. According to Gerard Holzmann, manager at the Laboratory for Reliable Software (LaRS) at NASA's Jet Propulsion Laboratory (JPL), even the fault protection systems on a spacecraft are mostly software-based. For reasons like these, well-functioning software is critical for NASA. In the same year as the failure of MGS, Holzmann presented a new approach to critical software development to help reduce risk and provide consistency. He proposed The Power of 10: Rules for Developing Safety-Critical Code, which is a small set of rules that can easily be remembered, clearly relate to risk, and allow compliance to be verified. The reaction at JPL was positive, and developers in the private sector embraced Holzmann's ideas.

Source record↗

Gear Crack Propagation Investigation

Reduced weight is a major design goal in aircraft power transmissions. Some gear designs incorporate thin rims to help meet this goal. Thin rims, however, may lead to bending fatigue cracks. These cracks may propagate through a gear tooth or into the gear rim. A crack that propagates through a tooth would probably not be catastrophic, and ample warning of a failure could be possible. On the other hand, a crack that propagates through the rim would be catastrophic. Such cracks could lead to disengagement of a rotor or propeller from an engine, loss of an aircraft, and fatalities. To help create and validate tools for the gear designer, the NASA Lewis Research Center performed in-house analytical and experimental studies to investigate the effect of rim thickness on gear-tooth crack propagation. Our goal was to determine whether cracks grew through gear teeth (benign failure mode) or through gear rims (catastrophic failure mode) for various rim thicknesses. In addition, we investigated the effect of rim thickness on crack propagation life. A finite-element-based computer program simulated gear-tooth crack propagation. The analysis used principles of linear elastic fracture mechanics, and quarter-point, triangular elements were used at the crack tip to represent the stress singularity. The program had an automated crack propagation option in which cracks were grown numerically via an automated remeshing scheme. Crack-tip stress-intensity factors were estimated to determine crack-propagation direction. Also, various fatigue crack growth models were used to estimate crack-propagation life. Experiments were performed in Lewis' Spur Gear Fatigue Rig to validate predicted crack propagation results. Gears with various backup ratios were tested to validate crack-path predictions. Also, test gears were installed with special crack-propagation gages in the tooth fillet region to measure bending-fatigue crack growth. From both predictions and tests, gears with backup ratios (rim thickness divided by tooth height) of 3.3 and 1.0 produced tooth fractures, whereas a backup ratio of 0.3 produced rim fractures. For a backup ratio of 0.5, the experiments produced rim fractures and the predictions produced both rim and tooth fractures, depending on the initial geometry of the crack. Good correlation between predicted and measured crack growth was achieved when the fatigue crack-closure concept was introduced into the analysis. As the gear rim thickness decreased, the compressive cyclic stress in the gear-tooth fillet region increased. This retarded crack growth and increased the number of crack-propagation cycles to failure.

Source record↗

Design and Performance Improvements of the Prototype Open Core Flywheel Energy Storage System

A prototype magnetically suspended composite flywheel energy storage (FES) system is operating at the University of Maryland. This system, designed for spacecraft applications, incorporates recent advances in the technologies of composite materials, magnetic suspension, and permanent magnet brushless motor/generator. The current system is referred to as an Open Core Composite Flywheel (OCCF) energy storage system. This paper will present design improvements for enhanced and robust performance. Initially, when the OCCF prototype was spun above its first critical frequency of 4,500 RPM, the rotor movement would exceed the space available in the magnetic suspension gap and touchdown on the backup mechanical bearings would occur. On some occasions it was observed that, after touchdown, the rotor was unable to re-suspend as the speed decreased. Additionally, it was observed that the rotor would exhibit unstable oscillations when the control system was initially turned on. Our analysis suggested that the following problems existed: (1) The linear operating range of the magnetic bearings was limited due to electrical and magnetic saturation; (2) The inductance of the magnetic bearings was affecting the transient response of the system; (3) The flywheel was confined to a small movement because mechanical components could not be held to a tight tolerance; and (4) The location of the touchdown bearing magnifies the motion at the pole faces of the magnetic bearings when the linear range is crucial. In order to correct these problems an improved design of the flywheel energy storage system was undertaken. The magnetic bearings were re-designed to achieve a large linear operating range and to withstand load disturbances of at least 1 g. The external position transducers were replaced by a unique design which were resistant to magnetic field noise and allowed cancellation of the radial growth of the flywheel at high speeds. A central rod was utilized to ensure the concentricity of the magnetic bearings, the motor/generator, and the mechanical touchdown bearings. In addition, the mechanical touchdown bearings were placed at two ends of the magnetic bearing stack to restrict the motion at pole faces. A composite flywheel was made using a multi-ring interference assembled design for a high specific energy density. To achieve a higher speed and better efficiency, a permanent magnet DC brushless motor was specially designed and fabricated. A vacuum enclosure was constructed to eliminate windage losses for testing at high speeds. With the new improvements the OCCF system was tested to 20,000 RPM with a total stored energy of 15.9 WH and an angular momentum of 54.8 N-m-s (40.4 lb-ft-s). Motor current limitation, caused by power loss in the magnetic bearings, was identified as causing the limit in upper operating speed.

Pang, D.↗

Quiet Spacecraft Cabin Ventilation Fan Development: Motivation and Context

It is important to control acoustical noise aboard crewed space vehicles and space habitats to provide a satisfactory environment for voice communications, alarm audibility, and restful sleep, and to minimize the risk for hearing loss and annoyance. As with most noise control efforts, it is best to control the noise at the source, and for spaceflight vehicles these are typically the fans associated with the Environmental Control and Life Support (ECLS) system. These include air ventilation fans, such as the main air conditioning fan (the ‘cabin fan’), intermodule ventilation (IMV) fans, air revitalization fans (for removal of carbon dioxide and trace contaminates), and thermal cooling fans. Thermal cooling pumps that circulate cooling fluid are another significant noise source in spaceflight vehicles, but these are outside of the scope of this paper. Throughout the history of crewed spaceflight, there have been issues with noise from ECLS ventilation fans. In the Apollo Command Module (CM) the crew would turn off the CM cabin fan once in orbit and use the backup suit-loop fan for ventilation because noise from the cabin fan interfered with communications and was an annoyance. On the Space Shuttle the ventilation system underwent significant redesign, including the addition of ventilation system mufflers, with resulting noise levels that were still too-high for long-duration missions. In the early years of International Space Station (ISS) operations, acoustical noise was one of the top two habitability issues, resulting in significant noise controls (along with significant cost and crew-time impacts) being implemented on-orbit on many fans, with significant noise reductions realized only after replacing noisy fans with fans of a quieter design, funded by the ISS Program. And, with the spaceflight vehicles and habitats currently being developed, there are again concerns with noise levels from ventilation fans. In the Orion vehicle, additional duct mufflers needed to be added to address the cabin fan noise. The Gateway’s Habitation and Logistics Outpost (HALO) module and low-Earth orbit (LEO) Freeflyer habitats are currently working to solve this problem. This will also be an issue for lunar and Mars spaceflight vehicles, space suits, and surface habitats. In an effort to address this problem, NASA is working to leverage the technology developed in its Aeronautics Research Mission Directorate (ARMD), specifically at the Glenn Research Center (GRC), to design highly efficient and quiet fans for reducing community noise levels from civilian aircraft. This technology was created over decades of research and development, and was proven to be effective at reducing aircraft noise levels. The current collaboration across NASA Centers, including HQ, GRC, and the Johnson Space Center (JSC) in this area is the first effort at re-purposing these tools, i.e. design codes and techniques, developed for high Reynolds number fans to spaceflight vehicle and habitat, low Reynolds number, fans. This paper will discuss the need for transfer of aeronautics fan design technology to spaceflight use. This paper will also discuss the potential benefits from this, which are significant, including 1) volume and mass savings from noise controls that are no longer as large or needed at all, 2) reduced system pressure loss from mufflers and silencers (that don’t need to be as restrictive) for better ventilation, 3) reduced power draw because of the reduced system pressure loss and the highly efficient fan design, and 4) satisfying spaceflight vehicle acoustic requirements to provide a safe and habitable acoustic environment for astronaut crewmembers. All of these benefits will be crucial for the successful development and operations of future spaceflight vehicles, space suits, and habitats.

Christopher S. Allen↗

Thomas Leps Internship Abstract

An optical navigation system is being flown as the backup system to the primary Deep Space Network telemetry for navigation and guidance purposes on Orion. This is required to ensure Orion can recover from a loss of communication, which would simultaneously cause a loss of DSN telemetry. Images taken of the Moon and Earth are used to give range and position information to the navigation computer for trajectory calculations and maneuver execution. To get telemetry data from these images, the size and location of the moon need to be calculated with high accuracy and precision. The reentry envelope for the Orion EM-1 mission requires the centroid and radius of the moon images to be determined within 1/3 of a pixel 3 sigma. In order to ensure this accuracy and precision can be attained, I was tasked with building precise dot grid images for camera calibration as well as building a hardware in the loop test stand for flight software and hardware proofing. To calibrate the Op-Nav camera a dot grid is imaged with the camera, the error between the image dot location and the actual dot location can be used to build a distortion map of the camera and lens system so that images can be fixed to display truth locations. To build the dot grid images I used the Electro Optics Lab optical bench Bright Object Simulator System, and gimbal. The gimbal was slewed to a series of elevations and azimuths. An image of the collimated single point light source was then taken at each position. After a series of 99 images were taken at different locations the single light spots were extracted from each image and added to a composite image containing all 99 points. During the development of these grids it was noticed that an intermittent error in the artificial "star" locations occurred. Prior to the summer this error was attributed to the gimbal having glitches in it's pointing direction and was going to be replaced, however after further examining the issue I determined it to be a software issue. I have since narrowed the likely source of the error down to a Software Development Kit released by the camera supplier PixeLink. I have since developed a workaround in order to build star grids for calibration until the software bug can be isolated and fixed. I was also tasked with building a Hardware in the Loop test stand in order to test the full Op-Nav system. A 4k screen displays simulated Lunar and Terrestrial images from a possible Orion trajectory. These images are then projected through a collimator and then captured with an Op-Nav camera controlled by an Intel NUC computer running flight software. The flight software then analyzes the images to determine attitude and position, this data is then reconstructed into a trajectory and matched to the simulated trajectory in order to determine the accuracy of the attitude and position estimates. In order for the system to work it needs to be precisely and accurately aligned. I developed an alignment procedure that allows the screen, collimator and camera to be squared, centered and collinear with each other within a micron spatially and 5 arcseconds in rotation. I also designed a rigid mount for the screen that was machined on site in Building 10 by another intern. While I was working in the EOL we received a $500k Orion startracker for alignment procedure testing. Due to my prior experience in electronics development, as an ancillary duty, I was tasked with building the cables required to operate and power the startracker. If any errors are made building these cables the startracker would be destroyed, I was honored that the director of the lab entrusted such a critical component with me. This internship has cemented my view on public space exploration. I always preferred public sector to privatization because, as a scientist, the most interesting aspects of space for me are not necessarily the most profitable. I was concerned that the public sector was faltering however, and that in order to improve human space exploration I would be forced into private sector. I now know that, at least at JSC, human spaceflight is still progressing, and exciting work is still being done. I am now actively seeking employment at JSC after I complete my Ph.D and have met with my branch chiefs and mentor to discuss transitioning to a grad Co-op position.

Leps, Thomas↗

The CCSDS Next Generation Space Data Link Protocol (NGSLP)

The CCSDS space link protocols i.e., Telemetry (TM), Telecommand (TC), Advanced Orbiting Systems (AOS) were developed in the early growth period of the space program. They were designed to meet the needs of the early missions, be compatible with the available technology and focused on the specific link environments. Digital technology was in its infancy and spacecraft power and mass issues enforced severe constraints on flight implementations. Therefore the Telecommand protocol was designed around a simple Bose, Hocquenghem, Chaudhuri (BCH) code that provided little coding gain and limited error detection but was relatively simple to decode on board. The infusion of the concatenated Convolutional and Reed-Solomon codes5 for telemetry was a major milestone and transformed telemetry applications by providing them the ability to more efficiently utilize the telemetry link and its ability to deliver user data. The ability to significantly lower the error rates on the telemetry links enabled the use of packet telemetry and data compression. The infusion of the high performance codes for telemetry was enabled by the advent of digital processing, but it was limited to earth based systems supporting telemetry. The latest CCSDS space link protocol, Proximity-1 was developed in early 2000 to meet the needs of short-range, bi-directional, fixed or mobile radio links characterized by short time delays, moderate but not weak signals, and short independent sessions. Proximity-1 has been successfully deployed on both NASA and ESA missions at Mars and is planned to be utilized by all Mars missions in development. A new age has arisen, one that now provides the means to perform advanced digital processing in spacecraft systems enabling the use of improved transponders, digital correlators, and high performance forward error correcting codes for all communications links. Flight transponders utilizing digital technology have emerged and can efficiently provide the means to make the next leap in performance for space link communications. Field Programmable Gate Arrays (FPGAs) provide the capability to incorporate high performance forward error correcting codes implemented within software transponders providing improved performance in data transfer, ranging, link security, and time correlation. Given these synergistic technological breakthroughs, the time has come to take advantage of them in applying them to both on going (e.g., command, telemetry) and emerging (e.g., space link security, optical communication) space link applications. However one of the constraining factors within the Data Link Layer in realizing these performance gains is the lack of a generic transfer frame format and common supporting services amongst the existing CCSDS link layer protocols. Currently each of the four CCSDS link layer protocols (TM, TC, AOS, and Proximity-1) have unique formats and services which prohibits their reuse across the totality of all space link applications of CCSDS member space agencies. For example, Mars missions. These missions implement their proximity data link layer using the Proximity-1 frame format and the services it supports but is still required to support the direct from Earth (TC) protocols and the Direct To Earth (AOS/TM) protocols. The prime purpose of this paper, is to describe a new general purpose CCSDS Data Link layer protocol, the NGSLP that will provide the required services along with a common transfer frame format for all the CCSDS space links (ground to/from space and space to space links) targeted for emerging missions after a CCSDS agency-wide coordinated date. This paper will also describe related options that can be included for the Coding and Synchronization sub-layer of the Data Link layer to extend the capacities of the link and additionally provide an independence of the transfer frame sub-layer from the coding sublayer. This feature will provide missions the option of running either the currently performed synchronous coding and transfer frame data link or an asynchronous coding/frame data link, in which the transfer frame length is independent of the block size of the code. The benefits from the elimination of this constraint (frame synchronized to the code block) will simplify the interface between the transponder and the data handling equipment and reduce implementation costs and complexities. The benefits include: inclusion of encoders/decoders into transmitters and receivers without regard to data link protocols, providing the ability to insert latency sensitive messages into the link to support launch, landing/docking, telerobotics. and Variable Coded Modulation (VCM). In addition the ability to transfer different sized frames can provide a backup for delivering stored anomaly engineering data simultaneously with real time data, or relaying of frames from various sources onto a trunk line for delivery to Earth.

Kazz, Greg J.↗