Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Computer Operations and 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.

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

At least 973 records · Page 54

The Hopper: A Wearable Robotic Device Testbed for Micro-Gravity Bone-Loading Proof-of-Concept

Wearable robotic systems are showing increased potential for addressing crew countermeasures needs. Wearable robots offer a compactness, programmability, and eccentric loading capability not present in more conventional exercise equipment. Correspondingly, advancements in the man to machine interface has progressed, allowing for higher loads to be applied directly to the person in new and novel ways. Recently, the X1 exoskeleton, a lower extremity wearable robot originally designed for mobility assistance and rehabilitation, underwent human subject testing to assess its potential as a knee dynamometer. This was of interest to NASA physiologists because currently strength is not assessed in flight due to hardware limitations, and thus there is a poor understanding of the time course of in-flight changes to muscle strength. The study concluded that the X1 compared well with the Biodex, the "gold standard" in terrestrial dynamometry, with coefficients of variation less than 6.0%. In a following study, the X1 powered ankle was evaluated for its efficacy in exercising calf muscles. Current on-orbit countermeasures equipment does not adequately protect the calf from atrophy. The results of this study were also positive (targeted muscle activity demonstrated via comparing pre- and post-exercise magnetic resonance imaging T2 measurements), again showing the efficacy of wearable robotic devices for addressing the countermeasure needs of our astronauts. Based on these successes and lessons learned, the Grasshopper was co-developed between IHMC (Florida Institute for Human and Machine Cognition) and NASA. The Grasshopper, or the Hopper for short, is a wearable robotic device designed to address muscle and bone density loss for astronauts spending extended periods of time in micro-gravity. The Grasshopper connects to the user's torso like a hiking backpack, over the shoulders and around the waist. At the feet are footplates that strap to the user. There are two actuators, one at each "knee" joint, which are capable of high fidelity torque control. Because the Hopper uses motors instead of gravity to create the load on the user, the device is suited for use on space missions. Exercise in zero-gravity conditions is critical to maintain muscle strength and bone mass. In operation, the actuators try to fold up, or collapse, the device, putting a compressive load between the user's feet and torso. This force is similar to carrying a heavy backpack. The user then bends and extends his or her knees, replicating a weightlifting squat exercise. The applied load is precisely controlled by a computer, and can be programmed to simulate gravitation loads or any desired load prescription, such as free-weight squat exercise. It is even possible to perform eccentric exercises, or negatives, without the need for a spotter. Because the hip joints, as well as the spine and long leg bones, are in the applied load path, there is the potential to stimulate bone growth, countering the typical bone loss when astronauts return from extended duration space travel.

Beck, C. E.↗

Simulation of Mission Phases

This position with the Simulation and Graphics Branch (ER7) at Johnson Space Center (JSC) provided an introduction to vehicle hardware, mission planning, and simulation design. ER7 supports engineering analysis and flight crew training by providing high-fidelity, real-time graphical simulations in the Systems Engineering Simulator (SES) lab. The primary project assigned by NASA mentor and SES lab manager, Meghan Daley, was to develop a graphical simulation of the rendezvous, proximity operations, and docking (RPOD) phases of flight. The simulation is to include a generic crew/cargo transportation vehicle and a target object in low-Earth orbit (LEO). Various capsule, winged, and lifting body vehicles as well as historical RPOD methods were evaluated during the project analysis phase. JSC core mission to support the International Space Station (ISS), Commercial Crew Program (CCP), and Human Space Flight (HSF) influenced the project specifications. The simulation is characterized as a 30 meter +V Bar and/or -R Bar approach to the target object's docking station. The ISS was selected as the target object and the international Low Impact Docking System (iLIDS) was selected as the docking mechanism. The location of the target object's docking station corresponds with the RPOD methods identified. The simulation design focuses on Guidance, Navigation, and Control (GNC) system architecture models with station keeping and telemetry data processing capabilities. The optical and inertial sensors, reaction control system thrusters, and the docking mechanism selected were based on CCP vehicle manufacturer's current and proposed technologies. A significant amount of independent study and tutorial completion was required for this project. Multiple primary source materials were accessed using the NASA Technical Report Server (NTRS) and reference textbooks were borrowed from the JSC Main Library and International Space Station Library. The Trick Simulation Environment and User Training Materials version 2013.0 release was used to complete the Trick tutorial. Multiple network privilege and repository permission requests were required in order to access previous simulation models. The project was also an introduction to computer programming and the Linux operating system. Basic C++ and Python syntax was used during the completion of the Trick tutorial. Trick's engineering analysis and Monte Carlo simulation capabilities were observed and basic space mission planning procedures were applied in the conceptual design phase. Multiple professional development opportunities were completed in addition to project duties during this internship through the System for Administration, Training, and Education Resources for NASA (SATERN). Topics include: JSC Risk Management Workshop, CCP Risk Management, Basic Radiation Safety Training, X-Ray Radiation Safety, Basic Laser Safety, JSC Export Control, ISS RISE Ambassador, Basic SharePoint 2013, Space Nutrition and Biochemistry, and JSC Personal Protective Equipment. Additionally, this internship afforded the opportunity for formal project presentation and public speaking practice. This was my first experience at a NASA center. After completing this internship I have a much clearer understanding of certain aspects of the agency's processes and procedures, as well as a deeper appreciation from spaceflight simulation design and testing. I will continue to improve my technical skills so that I may have another opportunity to return to NASA and Johnson Space Center.

Carlstrom, Nicholas Mercury↗

The X-43A Flight Research Program: Lessons Learned on the Road to Mach 10

During an aerospace engineer's undergraduate studies, he or she will attend classes in aerodynamics, thermodynamics, structures, stability and control, dynamics, design, propulsion, and computer science, along with the related courses in mathematics, physics, statistics, and chemistry required to understand the material. Upon graduation, the new engineer will have acquired a basic knowledge of how to build an aerospace vehicle. What only comes through experience, however, is the understanding of the inevitable imperfect process through which an aerospace vehicle is built. This is the adventure of turning a basic concept into functional hardware. Engineers working on a project must often deal with ambiguous situations. They are routinely asked by management to provide risk assessments of a project, yet even after careful analysis uncertainties remain. The project must be accomplished within finite limits of time and money. The question an engineer answers is whether the solution to potential problem is worth the cost and schedule delay, or if the solution might actually be worse than the problem it is meant to solve. Review protocols are established to ensure that an unknown has not been overlooked. But these cannot protect against an unknown unknown. Examples of these situations can be found in the history of the X-43A Hyper-X (Hypersonic Experiment) program. In this NASA project, a supersonic combustion ramjet (scramjet) engine was flight tested on a subscale vehicle. The X-43A Hyper-X Research Vehicle (HXRV) was launched from a B-52B mothership, then boosted to the test speed by a modified Pegasus rocket first stage, called the Hyper-X Launch Vehicle (HXLV). Once at the proper speed and altitude, the X-43A separated from the booster, stabilized itself, and then the engine test began. Although wind-tunnel scramjet engine tests had begun in the late 1950s, before the Hyper-X program there had never been an actual in-flight test of such an engine integrated with an appropriate airframe. Thus, while the scramjet had successfully operated in the artificial airflow of wind tunnels, the concept had yet to be proven in real air. These conditions meant changes in density and temperature, as well as changes in angle of attack and sideslip of a free-flying vehicle. A wind tunnel is limited in its ability to simulate these subtle factures, which have a major impact on almost any vehicle, but especially that of a scramjet's performance. The Hyper-X project was to provide a real-world benchmark of the ground test data. The full scale X-43A engine would be operated in the wind tunnel, and then flown, and the data from its operation would then be compared with projections. If these matched, the wind tunnel data would be considered a reliable design tool for future scramjet. If there were significant differences, the reasons for these would have to be identified. Until such information was available, scramjets would lack the technological maturity to be considered for future space launch or high-speed atmospheric flight vehicles.

Peebles, Curtis↗

Commercial-Off-The-Shelf Microelectromechanical Systems (MEMS) Flow-Measurement Probes Fabricated And Assembled

As an alternative to conventional tubing instrumentation for measuring airflow, designers and technicians at the NASA Glenn Research Center have been fabricating packaging components and assembling a set of unique probes using commercial-off-the-shelf microelectromechanical systems (MEMS) integrated circuits (computer chips). Using MEMS as an alternative has some compelling advantages over standard measurement devices. Sensor technologies have matured through high-production usage in industries such as automotive and aircraft manufacturers. Currently, MEMS are the choice in applications such as tire pressure monitors, altimeters, pneumatic controls, cable leak detectors, and consumer appliances. Conventional instrumentation uses tubing buried in the model aerodynamic surfaces or wind tunnel walls. The measurements are made when pressure is introduced at the tube opening. The pressure then must travel the tubing for lengths ranging from 20 to hundreds of feet before reaching an electronic signal conditioner. This condition causes a considerable amount of damping and requires measurements to be made only after the test rig has reached steady-state operation. The electronic MEMS pressure sensor is able to take readings continuously under dynamic states in nearly real time. The use of stainless steel tubing for pressure measurements requires many tubes to be cleaned, cut to length, carefully installed, and delicately deburred and spliced for use. A cluster of a few hundred 1/16-in.- (0.0625-in.-) diameter tubes (not uncommon in research testing facilities) can be several inches in diameter and may weigh enough to require two men to handle. Replacing hard tubing with electronic chips can eliminate much of the bulk. Each sensor would fit on the tip of the 1/16-in. tubing with room to spare. The P592 piezoresistive silicon pressure sensor (Lucas NovaSensor, Fremont, CA) was chosen for this project because of its cost, availability, and tolerance to extreme ambient conditions. The chip is 1 mm square by 0.6 mm thick (0.039 by 0.023 in.) with 0.12-mm (0.005-in.) wire connection tabs. Three MEMS chips were used to build the first type of flow-angularity probe. This MEMS probe will be demonstrated as an alternative to a standard tube type "Cobra Probe" now used routinely in wind tunnel and aeronautical hardware applications. The response time and accuracy would allow the probe to be translated on an actuator across a flow field, yielding precision dynamic measurements not possible with conventional instrumentation. The low profile, the minimal power requirement, the rugged construction, and the moderate cost all contribute to making MEMS sensors the enticing choice instrument in future research measurement needs. The MEMS probe efforts are a continuation of work initiated by Brian Willis, without whose foresight and efforts this project would never have been realized. This task was funded through cooperation with the NASA Electronic Parts and Packaging (NEPP) program at the Jet Propulsion Laboratory.

Redding, Chip↗

Changes in Hardware in Order to Accommodate Compliant Foil Air Bearings of a Larger Size

Compliant foil air bearings are at the forefront of the Oil-Free turbomachinery revolution of supporting gas turbine engines with air lubricated hydrodynamic bearings. Foil air bearings have existed for almost fifty years, yet their commercialization has been confined to relatively small, high-speed systems characterized by low temperatures and loads, such as in air cycle machines, turbocompressors and micro-turbines. Recent breakthroughs in foil air bearing design and solid lubricant coating technology, have caused a resurgence of research towards applying Oil-Free technology to more demanding applications on the scale of small and mid range aircraft gas turbine engines. In order to foster the transition of Oil-Free technology into gas turbine engines, in-house experiments need to be performed on foil air bearings to further the understanding of their complex operating principles. During my internship at NASA Glenn in the summer of 2003, a series of tests were performed to determine the internal temperature profile in a compliant bump- type foil journal air bearing operating at room temperature under various speeds and load conditions. From these tests, a temperature profile was compiled, indicating that the circumferential thermal gradients were negligible. The tests further indicated that both journal rotational speed and radial load are responsible for heat generation with speed playing a more significant role in the magnitude of the temperatures. As a result of the findings from the tests done during the summer of 2003, it was decided that further testing would need to be done, but with a bearing of a larger diameter. The bearing diameter would now be increased from two inches to three inches. All of the currently used testing apparatus was designed specifically for a bearing that was two inches in diameter. Thus, my project for the summer of 2004 was to focus specifically on the scatter shield put around the testing rig while running the bearings. Essentially I was to design a scatter shield that would be able to accommodate the three inch bearing and that would also meet all safety requirements. Furthermore, the new scatter shield also had to house a heater, used for high-speed and temperature testing. Using Solidworks, a computer aided modeling program, I was able to accomplish the task set out for me and designed the new scatter shield. Furthermore, I also guided the fabrication process. As a result of this containment shield being designed, the Oil-Free turbomachinery team now has the ability to test bearings of larger diameters. Finally, it is expected that these tests will provide information useful for the validation of future analytical modeling codes.

Zeszotek, Michelle↗

IT Security Support for the Spaceport Command Control Systems Development Ground Support Development Operations

Security is one of the most if not the most important areas today. After the several attacks on the United States, security everywhere was heightened from Airports to the communication among the military branches legionnaires. With advanced persistent threats (APTs) on the rise following Stuxnet, government branches and agencies are required, more than ever, to follow several standards, policies and procedures to reduce the likelihood of a breach. Attack vectors today are very advanced and are going to continue to get more and more advanced as security controls advance. This creates a need for networks and systems to be in an updated and secured state in a launch control system environment. FISMA is a law that is mandated by the government to follow when government agencies secure networks and devices. My role on this project is to ensure network devices and systems are in compliance with NIST, as outlined in FISMA. I will achieve this by providing assistance with security plan documentation and collection, system hardware and software inventory, malicious code and malware scanning and configuration of network devices i.e. routers and IDSsIPSs. In addition I will be completing security assessments on software and hardware, vulnerability assessments and reporting, conducting patch management and risk assessments. A guideline that will help with compliance with NIST is the SANS Top 20 Critical Controls. SANS Top 20 Critical Controls as well as numerous security tools, security software and the conduction of research will be used to successfully complete the tasks given to me. This will ensure compliance with FISMA and NIST, secure systems and a secured network. By the end of this project, I hope to have carried out stated above as well as gain an immense knowledge about compliance, security tools, networks and network devices, policies and procedures.

computer information security↗

Spacecraft Software Maintenance: An Effective Approach to Reducing Costs and Increasing Science Return

Flight software is a mission critical element of spacecraft functionality and performance. When ground operations personnel interface to a spacecraft, they are typically dealing almost entirely with the capabilities of onboard software. This software, even more than critical ground/flight communications systems, is expected to perform perfectly during all phases of spacecraft life. Due to the fact that it can be reprogrammed on-orbit to accommodate degradations or failures in flight hardware, new insights into spacecraft characteristics, new control options which permit enhanced science options, etc., the on- orbit flight software maintenance team is usually significantly responsible for the long term success of a science mission. Failure of flight software to perform as needed can result in very expensive operations work-around costs and lost science opportunities. There are three basic approaches to maintaining spacecraft software--namely using the original developers, using the mission operations personnel, or assembling a center of excellence for multi-spacecraft software maintenance. Not planning properly for flight software maintenance can lead to unnecessarily high on-orbit costs and/or unacceptably long delays, or errors, in patch installations. A common approach for flight software maintenance is to access the original development staff. The argument for utilizing the development staff is that the people who developed the software will be the best people to modify the software on-orbit. However, it can quickly becomes a challenge to obtain the services of these key people. They may no longer be available to the organization. They may have a more urgent job to perform, quite likely on another project under different project management. If they havn't worked on the software for a long time, they may need precious time for refamiliarization to the software, testbeds and tools. Further, a lack of insight into issues related to flight software in its on-orbit environment, may find the developer unprepared for the challenges. The second approach is to train a member of the flight operations team to maintain the spacecraft software. This can prove to be a costly and inflexible solution. The person assigned to this duty may not have enough work to do during a problem free period and may have too much to do when a problem arises. If the person is a talented software engineer, he/she may not enjoy the limited software opportunities available in this position; and may eventually leave for newer technology computer science opportunities. Training replacement flight software personnel can be a difficult and lengthy process. The third approach is to assemble a center of excellence for on-orbit spacecraft software maintenance. Personnel in this specialty center can be managed to support flight software of multiple missions at once. The variety of challenges among a set of on-orbit missions, can result in a dedicated, talented staff which is fully trained and available to support each mission's needs. Such staff are not software developers but are rather spacecraft software systems engineers. The cost to any one mission is extremely low because the software staff works and charges, minimally on missions with no current operations issues; and their professional insight into on-orbit software troubleshooting and maintenance methods ensures low risk, effective and minimal-cost solutions to on-orbit issues.

Shell, Elaine M.↗

Holodeck Testbed Project

The main objective of the Holodeck Testbed is to create a cost effective, realistic, and highly immersive environment that can be used to train astronauts, carry out engineering analysis, develop procedures, and support various operations tasks. Currently, the Holodeck testbed allows to step into a simulated ISS (International Space Station) and interact with objects; as well as, perform Extra Vehicular Activities (EVA) on the surface of the Moon or Mars. The Holodeck Testbed is using the products being developed in the Hybrid Reality Lab (HRL). The HRL is combining technologies related to merging physical models with photo-realistic visuals to create a realistic and highly immersive environment. The lab also investigates technologies and concepts that are needed to allow it to be integrated with other testbeds; such as, the gravity offload capability provided by the Active Response Gravity Offload System (ARGOS). My main two duties were to develop and animate models for use in the HRL environments and work on a new way to interface with computers using Brain Computer Interface (BCI) technology. On my first task, I was able to create precise computer virtual tool models (accurate down to the thousandths or hundredths of an inch). To make these tools even more realistic, I produced animations for these tools so they would have the same mechanical features as the tools in real life. The computer models were also used to create 3D printed replicas that will be outfitted with tracking sensors. The sensor will allow the 3D printed models to align precisely with the computer models in the physical world and provide people with haptic/tactile feedback while wearing a VR (Virtual Reality) headset and interacting with the tools. Getting close to the end of my internship the lab bought a professional grade 3D Scanner. With this, I was able to replicate more intricate tools at a much more time-effective rate. The second task was to investigate the use of BCI to control objects inside the hybrid reality ISS environment. This task looked at using an Electroencephalogram (EEG) headset to collect brain state data that could be mapped to commands that a computer could execute. On this Task, I had a setback with the hardware, which stopped working and was returned to the vendor for repair. However, I was still able to collect some data, was able to process it, and started to create correlation algorithms between the electrical patterns in the brain and the commands we wanted the computer to carry out. I also carried out a test to investigate the comfort of the headset if it is worn for a long time. The knowledge gained will benefit me in my future career. I learned how to use various modeling and programming tools that included Blender, Maya, Substance Painter, Artec Studio, Github, and Unreal Engine 4. I learned how to use a professional grade 3D scanner and 3D printer. On the BCI Project I learned about data mining and how to create correlation algorithms. I also supported various demos including a live demo of the hybrid reality lab capabilities at ComicPalooza. This internship has given me a good look into engineering at NASA. I developed a more thorough understanding of engineering and my overall confidence has grown. I have also realized that any problem can be fixed, if you try hard enough, and as an engineer it is your job to not only fix problems but to embrace coming up with solutions to those problems.

Arias, Adriel↗

Modeling and Analysis of Stirling Power Convertors

Modeling and Analysis of Stirling Power Convertors Luis A. Rodriguez1 Steven M. Geng, Terry V. Reid, Scott D. Wilson NASA Glenn Research Center, Cleveland, OH, 44135, USA NASA Glenn’s Thermal Energy Conversion Branch is supporting the development of the next generation free-piston Stirling power convertors. American Superconductor (AMSC) and Sunpower Inc. are the two firms under contract to develop the Flexure Isotope Stirling Convertor (FISC) and the Sunpower Robust Stirling Convertor (SRSC), respectively. To comprehend and forecast convertor performance, Sage, ANSYS® Maxwell, and ANSYS® Fluent were used to model the Stirling thermodynamic cycle, alternator electromagnetics, and piston and displacer dynamics. I. Introduction Stirling convertors are being developed by NASA as a potential steady source of electrical power for NASA’s future scientific space missions. Currently, NASA Glenn Research Center has two corporations under contract, American Superconductor (AMSC) and Sunpower Inc., for the development of the next generation of free-piston Stirling convertors for dynamic radioisotope power systems. AMSC is developing the Flexure Isotope Stirling Convertor (FISC), which uses flexures to prevent side motion and rubbing of the piston. Similarly, Sunpower Inc, is developing the Sunpower Robust Stirling Convertor (SRSC). The SRSC uses gas bearings to prevent radial contact of the moving piston. As convertor development continues, it is increasingly important to understand and predict the interactions of components in the system, how they respond to one another, and how they perform as a response to changes in operating conditions. A suitable and enlightening way to demonstrate and foresee these interactions is with the use of accurate modeling software. Sage, ANSYS® Maxwell, and ANSYS® Fluent are the current modeling tools used by NASA to analytically determine convertor performance. Sage is a one-dimensional object-oriented commercial software package used for modeling and optimizing Stirling convertors for Dynamic Radioisotope Power Systems (DRPS) and it is one of the most accurate Stirling convertor codes in use by NASA. This code is the successor to GLIMPS (Globally-Implicit Stirling Cycle Simulation) and GLOP (GLIMPS Optimization) software created by Gedeon Associates [1]. Model input parameters are typically material/gas type, component physical dimensions, temperatures, frequency, charge pressure, and number of time/space nodes. Sage is used to model both the FISC’s and SRSC’s Stirling cycle thermodynamics and piston/displacer dynamics. Performance maps were created and analyzed for both power systems to better understand the relationship between the following conditions: cold-end temperature, hot-end temperature, piston/displacer amplitudes, pressure drop, and thermal input power. The synergy between these conditions will help determine parameter sensitivity. ANSYS® Maxwell was used to create a three-dimensional (3-D) axisymmetric model for both FISC and SRSC alternators. The significant physical components included in each model are the magnets, magnet carrier, outer/inner laminations, and the coil. Inputs to the model are piston amplitude, piston frequency, alternator load, coil resistance, tuning capacitance, and specific material properties. The alternator models calculate terminal voltage, current, piston/current phase, voltage/current phase, coil inductance, terminal power and efficiency. The RI2 losses, core (hysteresis and eddy) losses, and magnet/can eddy losses are also a part of the final results. ANSYS® Fluent is used to build 3-D computational fluid dynamic (CFD) models to examine the Stirling cycle thermodynamics for both the FISC and SRSC systems. Three-dimensional Computer Aided Design (CAD) models were used to create the physical components of each convertor. Steady-state simulations were conducted for hardware testing, prediction of environmental losses during testing, and generation of radiation look-up tables. The model inputs to the aforementioned analysis are the material properties and boundary thermal conditions. The steady-state model calculates temperature and heat flow distributions. Transient 3-D calculations were also part of the CFD analysis. In this study a physically reduced version of the FISC is used to obtain a prediction of available engine power. For the gas bearing SRSC, the transient effort is used to obtain a prediction of bearing pad performance and its sensitivity to micro-channel geometric variation. The model inputs to the transient simulations are the piston amplitude, displacer amplitude, frequency, displacer/piston phase angle, dynamic deforming CFD grid, temperature boundary conditions, and user defined files describing motion profile of piston/displacer. The results of the model are temperature distributions, heat distributions, and PV power produced at pre-determined conditions.

Luis A Rodriguez↗

Lunar Reconnaissance Orbiter (LRO) Guidance, Navigation and Control (GN&C) Overview

The National Aeronautics and Space Administration s (NASA) Lunar Reconnaissance Orbiter (LRO) launched on June 18, 2009 from the Cape Canaveral Air Force Station aboard an Atlas V launch vehicle and into a direct insertion trajectory to the oon. LRO, which was designed, built, and operated by the NASA Goddard Space Flight Center in Greenbelt, MD, is gathering crucial data on the lunar environment that will help astronauts prepare for long-duration lunar expeditions. The mission has a nominal life of 1 year as its seven instruments find safe landing sites, locate potential resources, characterize the radiation environment, and test new technology. To date, LRO has been operating well within the bounds of its requirements and has been collecting excellent science data images taken from the LRO Camera Narrow Angle Camera of the Apollo landing sites appeared on cable news networks. A significant amount of information on LRO s science instruments is provided at the LRO mission webpage. LRO s Guidance, Navigation and Control (GN&C) subsystem is made up of an onboard attitude control system (ACS) and a hardware suite of sensors and actuators. The LRO onboard ACS is a collection of algorithms based on high level and derived requirements, and reflect the science and operational events throughout the mission lifetime. The primary control mode is the Observing mode, which maintains the lunar pointing orientation and any offset pointing from this baseline. It is within this mode that all science instrument calibrations, slews and science data is collected. Because of a high accuracy requirement for knowledge and pointing, the Observing mode makes use of star tracker (ST) measurement data to determine an instantaneous attitude pointing. But even the star trackers alone do not meet the tight requirements, so a six-state Kalman Filter is employed to improve the noisy measurement data. The Observing mode obtains its rate information from an inertial reference unit (IRU) and in the event of an IRU failure, the rate data is be derived from the star tracker, but with degraded pointing performance. The Delta-V control mode responsibility is to maintain attitude pointing during the cruise trajectory, insertion burns and lunar orbit maintenance by adjustments made to the spacecraft s velocity magnitude and vector direction. The ACS also provides for a thruster based system momentum management algorithm (known as Delta-H) to maintain the system and wheel momentum to within acceptable levels. In the event an anomaly causes the LRO spacecraft to lose the ability to maintain its current attitude pointing, a Sun Safe mode is included in the ACS for the purpose of providing a known power and thermally safe coarse inertial sun attitude for an indefinite period of time, within the manageable limits of the reaction wheels. The Sun Safe mode is also the initial spacecraft control mode off of the launch vehicle and provides for a means to null tip-off rates immediately after separation. The nominal configuration is to use the IRU for rate information in the controller. In the event of a gyro failure a gyroless control mode was developed that computes rate information from the CSS data.

Garrick, Joseph↗

IT Security Support for the Spaceport Command Control Systems Development Ground Support Development Operations

Security is one of the most if not the most important areas today. After the several attacks on the United States, security everywhere has heightened from airports to the communication among the military branches legionnaires. With advanced persistent threats (APT's) on the rise following Stuxnet, government branches and agencies are required, more than ever, to follow several standards, policies and procedures to reduce the likelihood of a breach. Attack vectors today are very advanced and are going to continue to get more and more advanced as security controls advance. This creates a need for networks and systems to be in an updated and secured state in a launch control system environment. FISMA is a law that is mandated by the government to follow when government agencies secure networks and devices. My role on this project is to ensure network devices and systems are in compliance with NIST, as outlined in FISMA. I will achieve this by providing assistance with security plan documentation and collection, system hardware and software inventory, malicious code and malware scanning, and configuration of network devices i.e. routers and IDS's/IPS's. In addition, I will be completing security assessments on software and hardware, vulnerability assessments and reporting, and conducting patch management and risk assessments. A guideline that will help with compliance with NIST is the SANS Top 20 Critical Controls. SANS Top 20 Critical Controls as well as numerous security tools, security software and the conduction of research will be used to successfully complete the tasks given to me. This will ensure compliance with FISMA and NIST, secure systems and a secured network. By the end of this project, I hope to have carried out the tasks stated above as well as gain an immense knowledge about compliance, security tools, networks and network devices, as well as policies and procedures.

security↗

Analysis of Launch Vehicle Liftoff Debris: Historical Perspective from Space Shuttle and Application to Artemis I

Human exploration-class launch vehicles are inherently prone to debris due to the extreme environments generated during pre-launch operations, liftoff, and flight. The use of cryogenic propellants often requires thermal protection system (TPS) coatings, typically foam, to maintain the propellant conditions in the tank and prevent an accumulation ice on the external surface of the vehicle. Some ice growth is to be expected at umbilical interfaces, vents, flanges, or brackets where it is difficult to apply TPS. This ice may come loose at any time due to wind on the launch pad, structural vibration and acoustics after rocket ignition, or aerodynamic forces during flight. This phenomena is especially apparent on vehicles with no TPS, such as the Saturn V rockets used in the Apollo Program, see Figure 1. During propellant tanking, the thermal contraction of the underlying substrate may generate cracks in the TPS (Figure 1). Chunks of TPS can release due to the expansion of ingested gas from cryopumping or from aerodynamic forces if the crack creates an offset surface. Most foams will also have a certain amount of “popcorning” where small pieces of foam will pop off during flight because of the differential between the static surface pressure and the pressure of the gas trapped in the foam cell structure. There are a number of other coating or closeout materials that may be shed from the vehicle and become debris. During pre-launch operations and liftoff, the vehicle may also be exposed to debris originating from the launch pad or ground support equipment. This debris is separate from foreign object debris, or FOD, which is not intended to be present and is strictly controlled through operations and maintenance procedures. In this case, debris is generated from hardware and materials that are necessary for launch and are subject to the intense vibration, acoustics, and direct plume impingement of the launch environment. Examples include ice from umbilicals, tape and tie wraps that protect cables, and rust or corrosion from the launch platform. While NASA has historically been aware of debris as a potential issue that could cause a failure resulting in loss of mission, loss of vehicle, or loss of crew, the likelihood and severity of that risk was not always well understood or given sufficient weight in program and flight decisions. After the Space Shuttle Columbia accident (STS-107), the investigation found that foam TPS debris shed from the external tank was the proximate cause of the damage to the orbiter wing. Six previous observations of debris released from the foam ramp that covered the bipod connecting the forward end of the orbiter to the external tank resulted in minor changes or were determined to be accepted flight risks. Two occurrences of bipod ramp foam loss were not identified until the STS-107 investigation. Despite the damage inflicted by these debris strikes, the Shuttle Program Requirements Control Board deemed the vehicle safe to fly. During the Return to Flight effort following the Columbia disaster, NASA Engineering developed a process for the assessment of debris transport, impact, and damage tolerance to support independent assessments of risk by NASA Safety and Mission Assurance (S&MA). Under this system, each element (vehicle or ground system) defines a catalog of all expected debris based on launch history, component testing, or analysis. Debris transport analysis (DTA) is conducted using the debris catalog characteristics and potential flow transport mechanisms (e.g., vehicle aerodynamics, gravity, wind, plume-driven). The predicted debris impact locations and velocities are provided to the hardware owners, who use available test data and analysis to determine whether each component can withstand the impacts. In cases where the element hardware may be severely damaged or fail, the options are to mitigate the debris source through some change in design or operation, or to work with S&MA to try to characterize the probability of the impact and damage for program risk acceptance. Because of the differences in debris characteristics and transport, the DTA has been divided between the Liftoff and Ascent regimes. The development and application of Liftoff DTA methodology from the Shuttle Program to the current Artemis Program is the subject of this paper. Liftoff DTA covers the time from the start of pre-launch operations at the launch pad, up until the vehicle clears the launch tower and there is no longer any interaction with ground systems. Debris transport during this period is broadly classified as either gravity, wind, and plume-entrained (GWPE) or plume driven (PD). GWPE debris is generally lower speed, travelling in a forward-to-aft direction. PD transport includes flow features from the rocket ignition transient, as well as plume impingement and recirculation that occur as the vehicle lifts off the launch platform. In these cases, the debris typically moves in an aft-to-forward direction at higher speeds. The applicable transport mechanisms must be considered for each piece of debris depending on the material, and release location and time. For example, rust or metallic debris from the tower could fall (GWPE) and impact the vehicle before landing on the launch platform deck where it could be also be transported by plume impingement (PD). However, falling ice (GWPE) from an umbilical is unlikely to survive impact with the vehicle or launch platform and be available for PD transport. Modeling of debris transport is accomplished using a set of DTA tools which simulate debris trajectories subject to a reference frame acceleration (i.e., gravity) and aerodynamic drag. Where the trajectory encounters a solid surface, the debris is allowed to rebound with a specified coefficient of restitution. The drag is calculated by interpolating the fluid state at each point in the debris trajectory from high-fidelity computational fluid dynamics (CFD) simulations of the launch vehicle and pad. The CFD data may either be static (steady state or time averaged), typically for GWPE transport, or dynamic (time-accurate) for PD flow features like the ignition transient. Examples of the CFD flow field solutions for the Space Launch System (SLS) rocket and launch pad are shown in Figure 2. Typical SLS debris trajectory predictions from DTA are illustrated in Figure 3. The final version of this paper will include a more detailed examination of the Liftoff DTA process developed during the Shuttle Program, and how it has been augmented and applied to the SLS rocket under the Artemis Program. Comparisons with debris observations from the Artemis I launch will demonstrate validation of the tools and methodology.

Debris↗

Evaluation of Open-Source Hard Real Time Software Packages

Reliable software is, at times, hard to find. No piece of software can be guaranteed to work in every situation that may arise during its use here at Glenn Research Center or in space. The job of the Software Assurance (SA) group in the Risk Management Office is to rigorously test the software in an effort to ensure it matches the contract specifications. In some cases the SA team also researches new alternatives for selected software packages. This testing and research is an integral part of the department of Safety and Mission Assurance. Real Time operation in reference to a computer system is a particular style of handing the timing and manner with which inputs and outputs are handled. A real time system executes these commands and appropriate processing within a defined timing constraint. Within this definition there are two other classifications of real time systems: hard and soft. A soft real time system is one in which if the particular timing constraints are not rigidly met there will be no critical results. On the other hand, a hard real time system is one in which if the timing constraints are not met the results could be catastrophic. An example of a soft real time system is a DVD decoder. If the particular piece of data from the input is not decoded and displayed to the screen at exactly the correct moment nothing critical will become of it, the user may not even notice it. However, a hard real time system is needed to control the timing of fuel injections or steering on the Space Shuttle; a delay of even a fraction of a second could be catastrophic in such a complex system. The current real time system employed by most NASA projects is Wind River's VxWorks operating system. This is a proprietary operating system that can be configured to work with many of NASA s needs and it provides very accurate and reliable hard real time performance. The down side is that since it is a proprietary operating system it is also costly to implement. The prospect of replacing this somewhat costly implementation is the focus of one of the SA group s current research projects. The explosion of open source software in the last ten years has led to the development of a multitude of software solutions which were once only produced by major corporations. The benefits of these open projects include faster release and bug patching cycles as well as inexpensive if not free software solutions. The main packages for hard real time solutions under Linux are Real Time Application Interface (RTAI) and two varieties of Real Time Linux (RTL), RTLFree and RTLPro. During my time here at NASA I have been testing various hard real time solutions operating as layers on the Linux Operating System. All testing is being run on an Intel SBC 2590 which is a common embedded hardware platform. The test plan was provided to me by the Software Assurance group at the start of my internship and my job has been to test the systems by developing and executing the test cases on the hardware. These tests are constructed so that the Software Assurance group can get hard test data for a comparison between the open source and proprietary implementations of hard real time solutions.

Mattei, Nicholas S.↗

Novel Engineering and Fabrication Techniques Tested in Low-Noise- Research Fan Blades

A major source of fan noise in commercial turbofan engines is the interaction of the wake from the fan blades with the stationary vanes (stators) directly behind them. The Trailing Edge Blowing (TEB) project team at the NASA Glenn Research Center designed and fabricated new fan blades to study the effects of fan trailing edge blowing as a potential noise-reduction concept. The intent is to fill the rotor wake by supplying air to the rotor blade trailing edge at the proper conditions to minimize the wake deficit, and thus generate less noise. The TEB hardware is designed for the Active Noise Control Fan (ANCF) test rig in Glenn's Aeroacoustic Propulsion Laboratory. For this test, the air is fed from an external supply through the shaft of the rig. It is distributed to the base of each blade through an impeller, where it is forced into a plenum at the core of each blade. In actual engine configuration, air would most likely be bled from the compressor, but only at times when noise is an issue, such as takeoffs and landings. Glenn researchers designed and manufactured the blades in-house, using new techniques and concepts. The skins, which were designed for maximum strength in the directions of highest stress, were molded from multiple layers of carbon fiber. Considerable use was made of rapid prototyping techniques, such as laser sintering. The core was sintered from a lightweight polymer, and the retainer was CNC-machined (computer numerical control machined) from aluminum. All the components were joined with a cold-cure aerospace adhesive. These techniques and processes reduced the overall cost and allowed the new concept to be studied much sooner than would be possible using traditional fabrication methods. Since this test rig did not support the use of blade-monitoring techniques such as strain gauges, extensive bench testing was required to qualify the design. The blades were examined using a variety of methods including holography, pull tests (cyclic and failure), shake tests, rap tests, and nondestructive inspection. Acoustic testing of the ANCF fan using TEB has been ongoing since January of 2001. The fan has completed about 100 hr of testing with no structural, vibrational, or fatigue problems. Far-field acoustic measurements, in-duct mode measurements, precise hot wire surveys, and detailed performance measurements are providing data for evaluating the concept. The far-field noise data show that tone noise was reduced significantly with the initial ANCF TEB fan design. In addition, a significant reduction in unsteady stator loading has been measured, indicating the potential for stator broadband noise reduction. The acoustic benefits will be assessed and important design parameters identified to improve the ability to fully exploit any benefit provided by this technique. On the basis of the success of trailing edge blowing, Glenn plans to continue this research with a higher speed, higher pressure ratio fan operating in an acoustic wind tunnel to simulate flight conditions.

Cunningham, Cameron C.↗

XRF Characterization of MMOD Impact Damage

Introduction The Hypervelocity Impact Technology (HVIT) Group at the NASA Johnson Space Center (JSC) has performed over 150 post flight MMOD inspections on returned space-ex-posed hardware and collected over 1,600 samples. Determination of the impactor source typically requires an analysis of the projectile residue in the damage feature. At this time, about 20% of the samples have been processed. Types of Samples Samples in the HVIT group collection can be classified into two types. Indirect (non-destructive) samples are produced when a pliable material (e.g., adhesive tape or dental mold) is inserted into an impact feature. With this type of sampling technique, crater material and (hopefully) projectile residue material is embedded in the sample media and can detected using further chemical characterizing techniques. Direct (destructive) sampling involves the in-tact extraction of material from the spacecraft and is done in a manner that the entire impact feature can be excised intact. This technique provides the greatest chance of successfully determining impactor source due to the entirety of the projectile remnants being present within the collected sample. Updated Projectile Residue Detection Techniques Previous assessments of projectile provenance have involved the use of samples that are first mounted in epoxy, sectioned to expose the crater interior, imaged with a scanning electron microscope (SEM), then any observed impactor residue was then analyzed using an energy dispersive spectrometer (EDS). This technique, while proven, may be supplemented with other types of elemental analysis techniques that can observe major element chemistry, in order to improve throughput of sample analysis. The Astromaterials Research and Exploration Science (ARES) Division at JSC, for example, operates a Bruker M4 Tornado micro-X-Ray fluorescence (XRF) spectrometer, capable of creating elemental maps of areas around these small impact features in a couple of hours, with a spot size <20 μm. The potential advantage with this technique lies in sample preparation, as no polishing or conductive coatings are needed. Early trials attempted to deter-mine impactor composition by collecting spectra from intact samples by aiming the X-Rays directly into the impact feature, but the signal:noise ratio was too low for confident material identification. Sample preparation for XRF then relies on sectioning the samples parallel to the impactor trajectory in order to expose the largest area of subsurface damage possible, thus maximizing the signal from any small impactor remnants. Complementary to the use of XRF for sample analysis, ARES also houses a Nikon XTH 320 micro-X-Ray computed tomography (XCT). This instrument can be used to create 3D visualizations of impact damage for the determination of crater volumes and dimensions, as well as for the determination of the best place to section each sample for the subsequent XRF analysis.

J L Hyde↗

Advanced Signal Conditioners for Data-Acquisition Systems

Signal conditioners embodying advanced concepts in analog and digital electronic circuitry and software have been developed for use in data-acquisition systems that are required to be compact and lightweight, to utilize electric energy efficiently, and to operate with high reliability, high accuracy, and high power efficiency, without intervention by human technicians. These signal conditioners were originally intended for use aboard spacecraft. There are also numerous potential terrestrial uses - especially in the fields of aeronautics and medicine, wherein it is necessary to monitor critical functions. Going beyond the usual analog and digital signal-processing functions of prior signal conditioners, the new signal conditioner performs the following additional functions: It continuously diagnoses its own electronic circuitry, so that it can detect failures and repair itself (as described below) within seconds. It continuously calibrates itself on the basis of a highly accurate and stable voltage reference, so that it can continue to generate accurate measurement data, even under extreme environmental conditions. It repairs itself in the sense that it contains a micro-controller that reroutes signals among redundant components as needed to maintain the ability to perform accurate and stable measurements. It detects deterioration of components, predicts future failures, and/or detects imminent failures by means of a real-time analysis in which, among other things, data on its present state are continuously compared with locally stored historical data. It minimizes unnecessary consumption of electric energy. The design architecture divides the signal conditioner into three main sections: an analog signal section, a digital module, and a power-management section. The design of the analog signal section does not follow the traditional approach of ensuring reliability through total redundancy of hardware: Instead, following an approach called spare parts tool box, the reliability of each component is assessed in terms of such considerations as risks of damage, mean times between failures, and the effects of certain failures on the performance of the signal conditioner as a whole system. Then, fewer or more spares are assigned for each affected component, pursuant to the results of this analysis, in order to obtain the required degree of reliability of the signal conditioner as a whole system. The digital module comprises one or more processors and field-programmable gate arrays, the number of each depending on the results of the aforementioned analysis. The digital module provides redundant control, monitoring, and processing of several analog signals. It is designed to minimize unnecessary consumption of electric energy, including, when possible, going into a low-power "sleep" mode that is implemented in firmware. The digital module communicates with external equipment via a personal-computer serial port. The digital module monitors the "health" of the rest of the signal conditioner by processing defined measurements and/or trends. It automatically makes adjustments to respond to channel failures, compensate for effects of temperature, and maintain calibration.

Lucena, Angel↗

PCR Based Microbial Monitor for Analysis of Recycled Water Aboard the ISSA: Issues and Prospects

The monitoring of spacecraft life support systems for the presence of health threatening microorganisms is paramount for crew well being and successful completion of missions. Development of technology to monitor spacecraft recycled water based on detection and identification of the genetic material of contaminating microorganisms and viruses would be a substantial improvement over current NASA plans to monitor recycled water samples that call for the use of conventional microbiology techniques which are slow, insensitive, and labor intensive. The union of the molecular biology techniques of DNA probe hybridization and polymerase chain reaction (PCR) offers a powerful method for the detection, identification, and quantification of microorganisms and viruses. This technology is theoretically capable of assaying samples in as little as two hours with specificity and sensitivity unmatched by any other method. A major advance in probe-hybridization/PCR has come about in a technology called TaqMan(TM), which was invented by Perkin Elmer. Instrumentation using TaqMan concepts is evolving towards devices that could meet NASA's needs of size, low power use, and simplicity of operation. The chemistry and molecular biology needed to utilize these probe-hybridization/PCR instruments must evolve in parallel with the hardware. The following issues of chemistry and biology must be addressed in developing a monitor: Early in the development of a PCR-based microbial monitor it will be necessary to decide how many and which organisms does the system need the capacity to detect. We propose a set of 17 different tests that would detect groups of bacteria and fungus, as well as specific eukaryotic parasites and viruses; In order to use the great sensitivity of PCR it will be necessary to concentrate water samples using filtration. If a lower limit of detection of 1 microorganism per 100 ml is required then the microbes in a 100 ml sample must be concentrated into a volume that can be added to a PCR assay; There are not likely to be contaminants in ISSA recycled water that would inhibit PCR resulting in false-negative results; The TaqMan PCR product detection system is the most promising method for developing a rapid, highly automated gene-based microbial monitoring system. The method is inherently quantitative. NASA and other government agencies have invested in other technologies that, although potentially could lead to revolutionary advances, are not likely to mature in the next 5 years into working systems; PCR-based methods cannot distinguish between DNA or RNA of a viable microorganism and that of a non-viable organism. This may or may not be an important issue with reclaimed water on the ISSA. The recycling system probably damages the capacity of the genetic material of any bacteria or viruses killed during processing to serve as a template in a PCR desinged to amplify a large segment of DNA (less than 650 base pairs). If necessary, vital dye staining could be used in addition to PCR, to enumerate the viable cells in a water sample; The quality control methods have been developed to insure that PCR's are working properly, and that reactions are not contaminated with PCR carryover products which could lead to the generation of false-positive results; and The sequences of the small rRNA subunit gene for a large number of microorganisms are known, and they consititue the best database for rational development of the oligonucleotide reagents that give PCR its great specificity. From those gene sequences, sets of oligonucleotide primers for PCR and Taqman detection that could be used in a NASA microbial monitor were constructed using computer based methods. In addition to space utilization, a microbial monitior will have tremendous terrestrial applications. Analysis of patient samples for microbial pathogens, testing industrial effluent for biofouling bacteria, and detection biological warfare agents on the battlefield are but a few of the diverse potential uses for this technology. Once fully developed, gene-based microbial monitors will become the fundamental tool in every lab that tests for microbial contaminants, and serve as a powerful weapon in mankind's war with the germ world.

Cassell, Gail H.↗

Algorithms for High-Speed Noninvasive Eye-Tracking System

Two image-data-processing algorithms are essential to the successful operation of a system of electronic hardware and software that noninvasively tracks the direction of a person s gaze in real time. The system was described in High-Speed Noninvasive Eye-Tracking System (NPO-30700) NASA Tech Briefs, Vol. 31, No. 8 (August 2007), page 51. To recapitulate from the cited article: Like prior commercial noninvasive eyetracking systems, this system is based on (1) illumination of an eye by a low-power infrared light-emitting diode (LED); (2) acquisition of video images of the pupil, iris, and cornea in the reflected infrared light; (3) digitization of the images; and (4) processing the digital image data to determine the direction of gaze from the centroids of the pupil and cornea in the images. Most of the prior commercial noninvasive eyetracking systems rely on standard video cameras, which operate at frame rates of about 30 Hz. Such systems are limited to slow, full-frame operation. The video camera in the present system includes a charge-coupled-device (CCD) image detector plus electronic circuitry capable of implementing an advanced control scheme that effects readout from a small region of interest (ROI), or subwindow, of the full image. Inasmuch as the image features of interest (the cornea and pupil) typically occupy a small part of the camera frame, this ROI capability can be exploited to determine the direction of gaze at a high frame rate by reading out from the ROI that contains the cornea and pupil (but not from the rest of the image) repeatedly. One of the present algorithms exploits the ROI capability. The algorithm takes horizontal row slices and takes advantage of the symmetry of the pupil and cornea circles and of the gray-scale contrasts of the pupil and cornea with respect to other parts of the eye. The algorithm determines which horizontal image slices contain the pupil and cornea, and, on each valid slice, the end coordinates of the pupil and cornea. Information from multiple slices is then combined to robustly locate the centroids of the pupil and cornea images. The other of the two present algorithms is a modified version of an older algorithm for estimating the direction of gaze from the centroids of the pupil and cornea. The modification lies in the use of the coordinates of the centroids, rather than differences between the coordinates of the centroids, in a gaze-mapping equation. The equation locates a gaze point, defined as the intersection of the gaze axis with a surface of interest, which is typically a computer display screen (see figure). The expected advantage of the modification is to make the gaze computation less dependent on some simplifying assumptions that are sometimes not accurate

Talukder, Ashit↗