SEARCH · Engineering Papers
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.
Digitally controlled oscillator in phased-locked loop may be useful for data communications systems, or may be modified to serve as information extraction component of microwave or optical system for collision avoidance or automatic braking. Instrument is frequency-synthesizing device with output specified precisely by digital number programmed into frequency register.
Adaptive, parallel, discrete-event-simulation-synchronization algorithm, Breathing Time Buckets, developed in Synchronous Parallel Environment for Emulation and Discrete Event Simulation (SPEEDES) operating system. Algorithm allows parallel simulations to process events optimistically in fluctuating time cycles that naturally adapt while simulation in progress. Combines best of optimistic and conservative synchronization strategies while avoiding major disadvantages. Algorithm processes events optimistically in time cycles adapting while simulation in progress. Well suited for modeling communication networks, for large-scale war games, for simulated flights of aircraft, for simulations of computer equipment, for mathematical modeling, for interactive engineering simulations, and for depictions of flows of information.
For 11 years the Department of Defense has cooperated with a diverse array of other Federal agencies including the National Institute of Standards and Technology, the Jet Propulsion Laboratory, and the Department of Energy, to develop robotics technology for unmanned ground systems. These activities have addressed control system architectures supporting sharing of tasks between the system operator and various automated subsystems, man-machine interfaces to intelligent vehicles systems, video compression supporting vehicle driving in low data rate digital communication environments, multiple simultaneous vehicle control by a single operator, path planning and retrace, and automated obstacle detection and avoidance subsystem. Performance metrics and test facilities for robotic vehicles were developed permitting objective performance assessment of a variety of operator-automated vehicle control regimes. Progress in these areas will be described in the context of robotic vehicle testbeds specifically developed for automated vehicle research. These initiatives, particularly as regards the data compression, task sharing, and automated mobility topics, also have relevance in the space environment. The intersection of technology development interests between these two communities will be discussed in this paper.
A new mission concept is introduced for future astrophysical observatories. This concept is to use a solar orbit that remains bounded to the Earth at a large distance on the order of several million kilometers. These orbits are termed here distant Retrograde Orbits (DRO's). This type of orbit is ideal for a space telescope that needs to be separated from the Earth by a large distance to avoid the near-Earth environmental effects, yet needs to remain bounded within some pre-defined distance for communication purposes. Another application is for a solar storm warning system that can provide warning times greater than those available from a similar system at the interior libration point of the Sun-Earth/Moon system. Several classes of DRO's in the Sun-Earth/Moon system are presented. The associated launch and insertion energies for impulsive and continuous thrust transfers from a low Earth parking orbit are investigated.
The methods and experiences from the Apollo Program are fundamental building blocks for the development of lunar landing strategies for the Constellation Program. Each of the six lunar landing Apollo missions landed under near ideal lighting conditions. The astronauts visually performed terrain relative navigation while looking out of windows, and were greatly aided by external communication and well lit scenes. As the LM approached the landing site, the astronauts performed visual hazard detection and avoidance, also under near-ideal lighting conditions. The astronauts were looking out of the windows trying to the best of their ability to avoid rocks, slopes, and craters and find a safe landing location. NASA has expressed a desire for global lunar access for both crewed and robotic sortie lunar exploration missions (Cook, 2007) (Dale, 2006). Early NASA architecture studies have identified the lunar poles as desirable locations for early lunar missions. These polar missions have less than ideal lighting conditions and will significantly affect the way a crewed vehicle plans to land at such locales. Consequently, a variety of hazard identification methods should be considered for use by the crew to ensure a high degree of safety. This paper discusses such identification methods applicable to the poorly lit polar lunar environment, better ensuring global access for the soon to be designed Lunar Lander Vehicle (LLV).
Researchers at the National Aeronautics and Space Administration Armstrong Flight Research Center in Edwards, California and Vigilant Aerospace Systems collaborated for the flight-test demonstration of an Automatic Dependent Surveillance-Broadcast based collision avoidance technology on a small unmanned aircraft system equipped with the uAvionix Automatic Dependent Surveillance-Broadcast transponder. The purpose of the testing was to demonstrate that National Aeronautics and Space Administration / Vigilant software and algorithms, commercialized as the FlightHorizon UAS"TM", are compatible with uAvionix hardware systems and the DJI Phantom 4 small unmanned aircraft system. The testing and demonstrations were necessary for both parties to further develop and certify the technology in three key areas: flights beyond visual line of sight, collision avoidance, and autonomous operations. The National Aeronautics and Space Administration and Vigilant Aerospace Systems have developed and successfully flight-tested an Automatic Dependent Surveillance-Broadcast Detect and Avoid system on the Phantom 4 small unmanned aircraft system. The Automatic Dependent Surveillance-Broadcast Detect and Avoid system architecture is especially suited for small unmanned aircraft systems because it integrates: 1) miniaturized Automatic Dependent Surveillance-Broadcast hardware; 2) radio data-link communications; 3) software algorithms for real-time Automatic Dependent Surveillance-Broadcast data integration, conflict detection, and alerting; and 4) a synthetic vision display using a fully-integrated National Aeronautics and Space Administration geobrowser for three dimensional graphical representations for ownship and air traffic situational awareness. The flight-test objectives were to evaluate the performance of Automatic Dependent Surveillance-Broadcast Detect and Avoid collision avoidance technology as installed on two small unmanned aircraft systems. In December 2016, four flight tests were conducted at Edwards Air Force Base. Researchers in the ground control station looking at displays were able to verify the Automatic Dependent Surveillance-Broadcast target detection and collision avoidance resolutions.
Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.
Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.
This paper offers a comprehensive view of flight system integration and test (I&T) lessons learned related to mishaps and close calls, focusing on what can be done to improve the I&T process to avoid recurrence. Specific areas within the realm of I&T that are covered in this paper include: I&T team communication and training; design of flight and ground systems for I&T; planning and scheduling; configuration management and process documentation; ground support equipment and tools; cleanrooms and contamination; mechanical integration, handling, and deployments; electrical integration and electrostatic discharge; functional testing and troubleshooting; environmental testing and facilities; and launch site operations. To illustrate "real-world" lessons learned for I&T, examples from throughout the history of the U.S. space program are presented. Also presented are some best practices for I&T that can help mitigate mishaps and close calls on the ground or during flight.
High-performance computing (HPC) applications have traditionally relied on parallel file systems and file transfer services to manage data movement and storage. Alternative approaches have been proposed that use direct communications between application components, trading persistence and fault tolerance for speed. Event-driven architectures, as popularized in enterprise contexts, present a compelling middle ground, avoiding the performance cost and API constraints of parallel file systems while retaining persistence and offering impedance matching between application components. However, adapting streaming frameworks to HPC workloads requires addressing challenges unique to HPC systems. This paper investigates the potential for a streaming framework designed for HPC infrastructures and use cases. We introduce Mofka, a persistent event-streaming framework designed specifically for HPC environments. Mofka combines the capabilities of a traditional streaming service with optimizations tailored to the HPC context, such as support for massively multicore nodes, efficient scaling for large producer-consumer workflows, RDMA-enabled high-performance network communications, specialized network fabrics with multiple links per node, and efficient handling of large scientific data payloads. Built using the Mochi suite of HPC data service components, Mofka provides a lightweight, modular, and high-performance solution for persistent streaming in HPC systems. We present the architecture of Mofka and evaluate its performance against Kafka and Redpanda using benchmarks on diverse platforms, including Argonne's Polaris and Oak Ridge's Frontier supercomputers, showing up to 8× improvement in throughput in some scenarios. We then demonstrate its utility in several real-world applications: a tomographic reconstruction pipeline, a workflow for the discovery of metal-organic frameworks for carbon capture, and the instrumentation of Dask workflows for provenance tracking and performance analysis.
Program Managers (PM) can protect program resources and improve chances of success by anticipating, understanding and managing risks. Understanding the range of potential risks helps one to avoid or manage the risks. A PM must choose which risks to accept to reduce fire fighting, must meet the expectations of stakeholders consistently, and avoid falling into costly "black holes" that may open. A good risk management process provides the PM more confidence to seize opportunities save money, meet schedule, even improve relationships with people important to the program. Evidence of managing risk and sound internal controls can mean better support from superiors for the program by building a trust and reputation from being on top of issues. Risk managers have an obligation to provide the PM with the best information possible to allow the benefits to be realized (Small Business Consortium, 2004). The Institute for Chartered Accountants in England and Wales sees very important benefits for companies in providing better information about what they do to assess and manage key business risks. Such information will: a) provide practical forward-looking information; b) reduce the cost of capital; c) encourage better risk management; and d) improve accountability for stewardship, investor protection and the usefulness of financial reporting. We are particularly convinced that enhanced risk reporting will help listed companies obtain capital at the lowest possible cost (The Institute of Chartered Accountants in England &Wales, June 2002). Risk managers can take a significant role in quantifying the success of their department and communicating those figures to executive (program) management levels while pushing for a broader risk management role. Overall, risk managers must show that risk management work matters in the most crucial place-the bottom line- as they prove risk management can be a profit center (Sullivan, 2004).
A relatively new area of interest in aerospace systems survivability is the growing threat of spacecraft penetration by orbital debris. Orbital debris, or "space junk", is composed of the man-made remnants of non-functioning spacecraft still orbiting the Earth. NASA estimates that there are currently over 100,000 orbital debris particles 1 centimeter in diameter or larger that cannot be tracked by existing radar, with the population growing at approximately 4% per year in low earth orbits. With an average velocity of over 8.7 km/sec, these projectiles can penetrate and disable many vulnerable spacecraft systems. Since the likelihood of spacecraft penetration increases with spacecraft surface area, large spacecraft (such as the International Space Station) and communication satellite fleets (such as Iridium) have begun to adopt survivability enhancement strategies similar to those employed by combat aircraft. Collision avoidance maneuvers are commonly practiced by the Space Shuttle and are planned by the International Space Station to decrease their susceptibility to impact by trackable orbital debris; likewise, improved shielding, internal equipment placement, and improved crew operations following penetration can reduce the vulnerability of spacecraft to loss following orbital debris impact. Computer simulations such as the Manned Spacecraft and Crew Survivability (MSCSurv) program at the NASA-Marshall Space Flight Center have recently been developed to quantify and reduce the likelihood of crew or spacecraft loss following orbital debris penetration. The AIAA Survivability Technical Committee is working to enable the transfer of military-developed survivability technologies to help the aerospace industry cope with this growing threat.
This presentation will explore the results of a recent NASA Life-Cycle Cost study and how project managers can use the findings and recommendations to improve planning and coordination early in the formulation cycle and avoid common pitfalls resulting in cost overruns. The typical NASA space science mission will exceed both the initial estimated and the confirmed life-cycle costs by the end of the mission. In a fixed-budget environment, these overruns translate to delays in starting or launching future missions, or in the worst case can lead to cancelled missions. Some of these overruns are due to issues outside the control of the project; others are due to the unpredictable problems (unknown unknowns) that can affect any development project. However, a recent study of life-cycle cost growth by the Discovery and New Frontiers Program Office identified a number of areas that are within the scope of project management to address. The study also found that the majority of the underlying causes for cost overruns are embedded in the project approach during the formulation and early design phases, but the actual impacts typically are not experienced until late in the project life cycle. Thus, project management focus in key areas such as integrated schedule development, management structure and contractor communications processes, heritage and technology assumptions, and operations planning, can be used to validate initial cost assumptions and set in place management processes to avoid the common pitfalls resulting in cost overruns.
This research was conducted by the National Renewable Energy Laboratory (NREL) in collaboration with the S&C Electric Inc. through funding provided by the ESTCP. The project demonstrates use of cybersecure Automated Demand Response (ADR) technology to effectively manage microgrid loads during grid-independent, also known as "islanded," operation. When military microgrids become isolated from the main electrical grid, they are required to balance electricity supply and demand locally. Given that local generation may be constrained, the prevailing strategy involves shedding all but the most critical loads by tripping smart circuit breakers, which then necessitate manual resetting. This approach is generally implemented at the building level, which means that the buildings with mission-critical activities are exempt from load management and remain fully powered, whereas those deemed non-critical can experience a complete loss of service. In this research we developed a method that allows building automation systems to selectively control their assets in response to load shedding request from a microgrid controller, avoiding total loss of service in contrast to the conventional control approach. A commercial OpenADR client server by GridFabric is used for communication between the microgrid controller and the building management system (BMS). The microgrid controller monitors both generation capacity and various assets within the microgrid and issues a demand reduction request when necessary. This request is communicated to the OpenADR server via Modbus. Upon receiving the request, the OpenADR server forwards it to the BMS utilizing the OpenADR protocol. The BMS is pre-configured with various levels of load reduction strategies based on the controllable assets available, allowing for a nuanced approach to demand reduction. Both lab and field tests were performed that considered load shedding needed to achieve closed transition into island mode and to accommodate changing loads and power source availability while islanded. A commercial microgrid controller was used for these tests with normal programming within the expected constraints of the system capabilities. That is, the solution did not require any specialized modification to the code base of the controller. Given the latency of the round-trip communication path between the microgrid controller and the various devices involved with the load shed processes, there are certain scenarios for which the demonstrated solution are appropriate and some which are not. The methods described in this report can be used for load shedding/restoration during transitions between islanded and grid-tied modes of operation, as well as accommodating normal variations in load and the need to remove a power source from operation for maintenance. These methods should not be used for scenarios that require load shedding within a second or two such as sudden and unanticipated significant load increases or loss of power sources through equipment faults.
Knowledge of limitations of the Air Traffic Control system in conflict avoidance capabilities is discussed. Assumptions and expectations held by by airmen regarding the capabilities of the system are presented. Limitations related to communication are described and problems associated with visual approaches, airspace configurations, and airport layouts are discussed. A number of pilot and controller reports illustrative of three typical problem types: occurrences involving pilots who have limited experience; reports describing inflight calls for assistance; and flights in which pilots have declined to use available radar services are presented. Examples of Alert Bulletins and the FAA responses to them are included.
A pressurized lunar rover is necessary for future long-term habitation of the moon. The rover must be able to safely perform many tasks, ranging from transportation and reconnaissance to exploration and rescue missions. Numerous designs were considered in an effort to maintain a low overall mass and good mobility characteristics. The configuration adopted consists of two cylindrical pressure hulls passively connected by a pressurized flexible passageway. The vehicle has an overall length of 11 meters and a total mass of seven metric tons. The rover is driven by eight independently powered two meter diameter wheels. The dual-cylinder concept allows a combination of articulated frame and double Ackermann steering for executing turns. In an emergency, the individual drive motors allow the option of skid steering as well. Two wheels are connected to either side of each cylinder through a pinned bar which allows constant ground contact. Together, these systems allow the rover to easily meet its mobility requirements. A dynamic isotope power system (DIPS), in conjunction with a closed Brayton cycle, supplied the rover with a continuous supply of 8.5 kW. The occupants are all protected from the DIPS system's radiation by a shield of tantalum. The large amount of heat produced by the DIPS and other rover systems is rejected by thermal radiators. The thermal radiators and solar collectors are located on the top of the rear cylinder. The solar collectors are used to recharge batteries for peak power periods. The rover's shell is made of graphite-epoxy coated with multi-layer insulation (MLI). The graphite-epoxy provides strength while the thermally resistant MLI gives protection from the lunar environment. An elastomer separates the two materials to compensate for the thermal mismatch. The communications system allows for communication with the lunar base with an option for direct communication with earth via a lunar satellite link. The various links are combined into one signal broadcast in the S-band at 2.3 GHz. The rover is fitted with a parabolic reflector disk for S-band transmission, and an omnidirectional antenna for local extravehicular activity (EVA) communication. The rover's guidance, navigation, and control subsystem consists of an inertial guidance system, an orbiting lunar satellite, and an obstacle avoidance system. In addition, the rover is equipped with a number of external fixtures including two telerobotic arms, lights, cameras, EVA storage, manlocks, a docking fixture, solar panels, thermal radiators, and a scientific airlock. In conclusion, this rover meets all of the design requirements and clearly surpasses them in the areas of mobility and maneuverability.
Topics covered include: Fully Integrated, Miniature, High-Frequency Flow Probe Utilizing MEMS Leadless SOI Technology; Nanoscale Surface Plasmonics Sensor With Nanofluidic Control; Advanced Dispersed Fringe Sensing Algorithm for Coarse Phasing Segmented Mirror Telescopes; Neural Network Back-Propagation Algorithm for Sensing Hypergols; Bulk Moisture and Salinity Sensor; Change-Based Satellite Monitoring Using Broad Coverage and Targetable Sensing; Circularly Polarized Microwave Antenna Element with Very Low Off-Axis Cross-Polarization; Ultra-Low Heat-Leak, High-Temperature Superconducting Current Leads for Space Applications; Flash Cracking Reactor for Waste Plastic Processing; An Automated Safe-to-Mate (ASTM) Tester; Wireless Chalcogenide Nanoionic-Based Radio-Frequency Switch; Compute Element and Interface Box for the Hazard Detection System; DOT Transmit Module; Composite Aerogel Multifoil Protective Shielding; Li-Ion Electrolytes with Improved Safety and Tolerance to High-Voltage Systems; Polymer-Reinforced, Non-Brittle, Lightweight Cryogenic Insulation; Controlled, Site-Specific Functionalization of Carbon Nanotubes with Diazonium Salts; Regenerable Sorbent for CO2 Removal; Sprayable Aerogel Bead Compositions With High Shear Flow Resistance and High Thermal Insulation Value; Lexan Linear Shaped Charge Holder with Magnets and Backing Plate; Robotic Ankle for Omnidirectional Rock Anchors; Wind, Wave, and Tidal Energy Without Power Conditioning; An Active Heater Control Concept to Meet IXO Type Mirror Module Thermal-Structural Distortion Requirement; Waterless Clothes-Cleaning Machine; Integrated Electrical Wire Insulation Repair System; LVGEMS Time-of-Flight Mass Spectrometry on Satellites; Surface Inspection Tool for Optical Detection of Surface Defects; Per-Pixel, Dual-Counter Scheme for Optical Communications; Certification-Based Process Analysis; Surface Navigation Using Optimized Waypoints and Particle Swarm Optimization; Smart-Divert Powered Descent Guidance to Avoid the Backshell Landing Dispersion Ellipse; Estimating Foreign-Object-Debris Density from Photogrammetry Data; Adaptive Sampling of Spatiotemporal Phenomena with Optimization Criteria; Building a 2.5D Digital Elevation Model From 2D Imagery; Eyes on the Earth 3D; Target Trailing With Safe Navigation for Maritime Autonomous Surface Vehicles; Adams-Based Rover Terramechanics and Mobility Simulator - ARTEMIS; ISTP CDF Skeleton Editor; Uplink Summary Generator (ULSGEN) Version 1.0; Robotics On-Board Trainer (ROBoT); Software Engineering Tools for Scientific Models; Automatic Data Filter Customization Using a Genetic Algorithm; Tracker Toolkit; Towards Efficient Scientific Data Management Using Cloud Storage; On a Formal Tool for Reasoning About Flight Software Cost Analysis; A Nanostructured Composites Thermal Switch Controls Internal and External Short Circuit in Lithium Ion Batteries; Spacecraft Crew Cabin Condensation Control; and Functional Near-Infrared Spectroscopy Signals Measure Neuronal Activity in the Cortex.
Atmospheric turbulence has significant impairments on the operation of Free-Space Optical (FSO) communication systems, in particular temporal and spatial intensity fluctuations at the receiving aperture resulting in power surges and fades, changes in angle of arrival, spatial coherence degradation, etc. The refractive index structure parameter Cn2 is a statistical measure of the strength of turbulence in the atmosphere and is highly dependent upon vertical height. Therefore to understand atmospheric turbulence effects on vertical FSO communication links such as space-to-ground links, it is necessary to specify Cn2 profiles along the atmospheric propagation path. To avoid the limitations on the applicability of classical approaches, propagation simulation through geometrical ray tracing is applied. This is achieved by considering the atmosphere along the optical propagation path as a spatial distribution of spherical bubbles with varying relative refractive index deviations representing turbulent eddies. The relative deviations of the refractive index are statistically determined from altitude-dependent and time-varying temperature fluctuations, as measured by a microwave profiling radiometer. For each representative atmosphere ray paths are analyzed using geometrical optics, which is particularly advantageous in situations of strong turbulence where there is severe wavefront distortion and discontinuity. The refractive index structure parameter is then determined as a function of height and time.