Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “user centered design”

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 793 records · Page 44
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

Human Exploration Science Office (KX) Overview

The Human Exploration Science Office supports human spaceflight, conducts research, and develops technology in the areas of space orbital debris, hypervelocity impact technology, image science and analysis, remote sensing, imagery integration, and human and robotic exploration science. NASA's Orbital Debris Program Office (ODPO) resides in the Human Exploration Science Office. ODPO provides leadership in orbital debris research and the development of national and international space policy on orbital debris. The office is recognized internationally for its measurement and modeling of the debris environment. It takes the lead in developing technical consensus across U.S. agencies and other space agencies on debris mitigation measures to protect users of the orbital environment. The Hypervelocity Impact Technology (HVIT) project evaluates the risks to spacecraft posed by micrometeoroid and orbital debris (MMOD). HVIT facilities at JSC and White Sands Test Facility (WSTF) use light gas guns, diagnostic tools, and high-speed imagery to quantify the response of spacecraft materials to MMOD impacts. Impact tests, with debris environment data provided by ODPO, are used by HVIT to predict risks to NASA and commercial spacecraft. HVIT directly serves NASA crew safety with MMOD risk assessments for each crewed mission and research into advanced shielding design for future missions. The Image Science and Analysis Group (ISAG) supports the International Space Station (ISS) and commercial spaceflight through the design of imagery acquisition schemes (ground- and vehicle-based) and imagery analyses for vehicle performance assessments and mission anomaly resolution. ISAG assists the Multi-Purpose Crew Vehicle (MPCV) Program in the development of camera systems for the Orion spacecraft that will serve as data sources for flight test objectives that lead to crewed missions. The multi-center Imagery Integration Team is led by the Human Exploration Science Office and provides expertise in the application of engineering imagery to spaceflight. The team links NASA programs and private industry with imagery capabilities developed and honed through decades of human spaceflight, including imagery integration, imaging assets, imagery data management, and photogrammetric analysis. The team is currently supporting several NASA programs, including commercial demonstration missions. The Earth Science and Remote Sensing Team is responsible for integrating the scientific use of Earth-observation assets onboard the ISS, which consist of externally mounted sensors and crew photography capabilities. This team facilitates collaboration on remote sensing and participates in research with academic organizations and other Government agencies, not only in conjunction with ISS science, but also for planetary exploration and regional environmental/geological studies. Human exploration science focuses on science strategies for future human exploration missions to the Moon, Mars, asteroids, and beyond. This function provides communication and coordination between the science community and mission planners. ARES scientists support the operation of robotic missions (i.e., Mars Exploration Rovers and the Mars Science Laboratory), contribute to the interpretation of returned mission data, and translate robotic mission technologies and techniques to human spaceflight.

Calhoun, Tracy A.↗
NASA NTRS2016

Crowd Sourcing Approach for UAS Communication Resource Demand Forecasting

Congressional attention to Unmanned Aircraft Systems (UAS) has caused the Federal Aviation Administration (FAA) to move the National Airspace System (NAS) Integration project forward, but using guidelines, practices and procedures that are yet to be fully integrated with the FAA Aviation Management System. The real drive for change in the NAS will to come from both UAS operators and the government jointly seeing an accurate forecast of UAS usage demand data. This solid forecast information would truly get the attention of planners. This requires not an aggregate demand, but rather a picture of how the demand is spread across small to large UAS, how it is spread across a wide range of missions, how it is expected over time and where, in terms of geospatial locations, will the demand appear. In 2012 the Volpe Center performed a study of the overall future demand for UAS. This was done by aggregate classes of aircraft types. However, the realistic expected demand will appear in clusters of aircraft activities grouped by similar missions on a smaller geographical footprint and then growing from those small cells. In general, there is not a demand forecast that is tightly coupled to the real purpose of the mission requirements (e.g. in terms of real locations and physical structures such as wind mills to inspect, farms to survey, pipelines to patrol, etc.). Being able to present a solid basis for the demand is crucial to getting the attention of investment, government and other fiscal planners. To this end, Mosaic ATM under NASA guidance is developing a crowd sourced, demand forecast engine that can draw forecast details from commercial and government users and vendors. These forecasts will be vetted by a governance panel and then provide for a sharable accurate set of projection data. Our paper describes the project and the technical approach we are using to design and create access for users to the forecast system.

air traffic↗
NASA NTRS2016

The Geostationary Operational Satellite R Series SpaceWire Based Data System

The Geostationary Operational Environmental Satellite R-Series Program (GOES-R, S, T, and U) mission is a joint program between National Oceanic & Atmospheric Administration (NOAA) and National Aeronautics & Space Administration (NASA) Goddard Space Flight Center (GSFC). SpaceWire was selected as the science data bus as well as command and telemetry for the GOES instruments. GOES-R, S, T, and U spacecraft have a mission data loss requirement for all data transfers between the instruments and spacecraft requiring error detection and correction at the packet level. The GOES-R Reliable Data Delivery Protocol (GRDDP) [1] was developed in house to provide a means of reliably delivering data among various on board sources and sinks. The GRDDP was presented to and accepted by the European Cooperation for Space Standardization (ECSS) and is part of the ECSS Protocol Identification Standard [2]. GOES-R development and integration is complete and the observatory is scheduled for launch November 2016. Now that instrument to spacecraft integration is complete, GOES-R Project reviewed lessons learned to determine how the GRDDP could be revised to improve the integration process. Based on knowledge gained during the instrument to spacecraft integration process the following is presented to help potential GRDDP users improve their system designs and implementation.

Networks↗
NASA NTRS2015

Extension of an Object-Oriented Optimization Tool: User's Reference Manual

The National Aeronautics and Space Administration Armstrong Flight Research Center has developed a cost-effective and flexible object-oriented optimization (O (sup 3)) tool that leverages existing tools and practices and allows easy integration and adoption of new state-of-the-art software. This object-oriented framework can integrate the analysis codes for multiple disciplines, as opposed to relying on one code to perform analysis for all disciplines. Optimization can thus take place within each discipline module, or in a loop between the O (sup 3) tool and the discipline modules, or both. Six different sample mathematical problems are presented to demonstrate the performance of the O (sup 3) tool. Instructions for preparing input data for the O (sup 3) tool are detailed in this user's manual.

Multidisciplinary design optimization↗
NASA NTRS2010

Extracting Oxygen from Lunar Simulant Using a Transparent Furnace Pulsed Fluidized Bed

In the event that humans return to the moon, utilizing the local materials will be beneficial for extended stays. Rather than transporting resources, such as oxygen, from Earth, NASA is investigating methods of extracting it from lunar regolith. One promising process is hydrogen reduction. In the hydrogen reduction process, lunar regolith is heated to 1000 C in the presence of hydrogen. The iron oxide (Fe-O) bonds, found in lunar material, are broken and the hydrogen attracts the oxygen to produce water vapor [Allen et al., 1996]. FeO + H2 (right arrow) Fe +H2O. The water vapor is then captured, cleaned, and electrolyzed. The hydrogen is recycled back to the reduction process and the oxygen is stored until consumed by an end user (propulsion, life support, etc.). To obtain a good oxygen yield, the majority of lunar regolith must be exposed to the hydrogen gas and have a high rate of heat transfer from heat source to particle. This is achieved with good solids mixing via fluidization or mechanical agitation. In Generation II of the ROxygen program, the ROxygen Team at Johnson Space Center (JSC) investigated the feasibility of gas only pulsed fluidization as the only means to mix synthetic lunar regolith (simulant) at high temperatures. Fluidized beds have been used in industry to effectively process powders for decades. They consist of gas flowing upward through a bed of particles. The stirring action continuously moves the grains around to achieve uniform mixing of gas, solids, and heat [Geldart, 1986]. A transparent furnace unit was developed by Thoughventions Unlimited LLC (TvU) to aid in the qualitative observation of the fluidization behavior at high temperatures. Multipoint thermocouples and pressure sensors provided quantitative information regarding the quality of mixing. The water produced was measured using humidity sensors and captured using a NASA designed and built condenser. Once the simulant was processed, pneumatically transporting the 'hot' simulant out of the furnace was investigated.

Oryshchyn, L.↗
NASA NTRSDate not supplied

The Doppler Wind Temperature Sensor (DWTS) Flight Evaluation and Experiments (TES-16, 17)

The Doppler Wind and Temperature Sounder instrument (DWTS), developed by Global Atmospheric Technologies and Sciences (GATS), is a simple but powerful tool that has the potential to become a new window through which to study the dynamics of the upper atmosphere. Based around a defense-grade infrared camera peering through a static gas cell used as a scanning spectral filter, the DWTS instrument infers wind velocities and kinetic temperatures through the stratosphere and lower thermosphere. The DWTS achieves this scanning by measuring the induced Doppler shift and Doppler broadening of emissions as they pass through the DWTS field of view (Gordley, et al., 2011). The DWTS holds promise in improving accuracy in weather determination , and the core technology can be adapted to study other planetary atmospheres. In partnership with GATS, NOAA, and other collaborators, NASA Ames and the Nano Orbital Workshop group have been working to evaluate the DWTS instrument on orbit and optimize it as a flexible nanosatellite payload. The first mission selected for DWTS evaluation is preparing for flight in early 2024, which will be followed by a more capable science mission in 2025, with both missions being part of the TES-n/NOW heritage flight series. The first rapid technology demonstration flight, TES-16/DWTS-A, will demonstrate a single DWTS instrument in an approximately 2U payload volume with the imaging aperture perpendicular to the flight velocity vector. With an estimated power consumption of 50 watts, supplied via a custom NOW-designed DC-DC converter, the instrument will maintain the imaging sensor plane at 80K during instrument evaluation periods using an integrated pulse-tube cryocooler. Data from DWTS will be captured and processed via a NOW-designed custom data interface unit before being transmitted via S-band radio back to select ground stations, with instrument command and control operated via L-band global-coverage radio. The subsequent TES-17/DWTS-B mission will be a dedicated science mission to obtain full altitude coverage from 20 to 200 km during both day and night, all from a single small-satellite equipped with three DWTS instruments, each hosting a different gas cell chemistry. The intention of this flight series, and one of NASA’s interests in this instrument, is to advance a Martian atmospheric instrument (Colaprete, Gordley, et al) which, if successful, would greatly further understanding of Martian atmospheric behavior. The proposed paper will review the flight series in detail, including challenges facing the TES-16 flight tests and the projected challenges and application to Mars study. Additional detail regarding the possible applications of a Cognitive Communication technique in current flight development by NOW collaborators at the NASA Glenn Research Center will also be discussed, including the implications of using an automated User Initiated Service (UIS) protocol to maximize the data collected per orbit.

nanosatellite↗
NASA NTRS2005

Java-based Graphical User Interface for MAVERIC-II

A computer program entitled "Marshall Aerospace Vehicle Representation in C II, (MAVERIC-II)" is a vehicle flight simulation program written primarily in the C programming language. It is written by James W. McCarter at NASA/Marshall Space Flight Center. The goal of the MAVERIC-II development effort is to provide a simulation tool that facilitates the rapid development of high-fidelity flight simulations for launch, orbital, and reentry vehicles of any user-defined configuration for all phases of flight. MAVERIC-II has been found invaluable in performing flight simulations for various Space Transportation Systems. The flexibility provided by MAVERIC-II has allowed several different launch vehicles, including the Saturn V, a Space Launch Initiative Two-Stage-to-Orbit concept and a Shuttle-derived launch vehicle, to be simulated during ascent and portions of on-orbit flight in an extremely efficient manner. It was found that MAVERIC-II provided the high fidelity vehicle and flight environment models as well as the program modularity to allow efficient integration, modification and testing of advanced guidance and control algorithms. In addition to serving as an analysis tool for techno logy development, many researchers have found MAVERIC-II to be an efficient, powerful analysis tool that evaluates guidance, navigation, and control designs, vehicle robustness, and requirements. MAVERIC-II is currently designed to execute in a UNIX environment. The input to the program is composed of three segments: 1) the vehicle models such as propulsion, aerodynamics, and guidance, navigation, and control 2) the environment models such as atmosphere and gravity, and 3) a simulation framework which is responsible for executing the vehicle and environment models and propagating the vehicle s states forward in time and handling user input/output. MAVERIC users prepare data files for the above models and run the simulation program. They can see the output on screen and/or store in files and examine the output data later. Users can also view the output stored in output files by calling a plotting program such as gnuplot. A typical scenario of the use of MAVERIC consists of three-steps; editing existing input data files, running MAVERIC, and plotting output results.

Seo, Suk Jai↗
NASA NTRS2006

JSC Orbital Debris Website Description

Purpose: The website provides information about the NASA Orbital Debris Program Office at JSC, which is the lead NASA center for orbital debris research. It is recognized world-wide for its leadership in addressing orbital debris issues. The NASA Orbital Debris Program Office has taken the international lead in conducting measurements of the environment and in developing the technical consensus for adopting mitigation measures to protect users of the orbital environment. Work at the center continues with developing an improved understanding of the orbital debris environment and measures that can be taken to control its growth. Major Contents: Orbital Debris research is divided into the following five broad efforts. Each area of research contains specific information as follows: 1) Modeling - NASA scientists continue to develop and upgrade orbital debris models to describe and characterize the current and future debris environment. Evolutionary and engineering models are described in detail. Downloadable items include a document in PDF format and executable software. 2) Measurements - Measurements of near-Earth orbital debris are accomplished by conducting ground-based and space-based observations of the orbital debris environment. The data from these sources provide validation of the environment models and identify the presence of new sources. Radar, optical and surface examinations are described. External links to related topics are provided. 3) Protection - Orbital debris protection involves conducting hypervelocity impact measurements to assess the risk presented by orbital debris to operating spacecraft and developing new materials and new designs to provide better protection from the environment with less weight penalty. The data from this work provides the link between the environment defined by the models and the risk presented by that environment to operating spacecraft and provides recommendations on design and operations procedures to reduce the risk as required. These data also help in the analysis and interpretation of impact features on returned spacecraft surfaces. 4) Mitigation - Controlling the growth of the orbital debris population is a high priority for NASA, the United States, and the major space-faring nations of the world to preserve near-Earth space for future generations. Mitigation measures can take the form of curtailing or preventing the creation of new debris, designing satellites to withstand impacts by small debris, and implementing operational procedures ranging from utilizing orbital regimes with less debris, adopting specific spacecraft attitudes, and even maneuvering to avoid collisions with debris. Downloadable items include several documents in PDF format and executable software.and 5) Reentry - Because of the increasing number of objects in space, NASA has adopted guidelines and assessment procedures to reduce the number of non-operational spacecraft and spent rocket upper stages orbiting the Earth. One method of postmission disposal is to allow reentry of these spacecraft, either from orbital decay (uncontrolled entry) or with a controlled entry. Orbital decay may be achieved by firing engines to lower the perigee altitude so that atmospheric drag will eventually cause the spacecraft to enter. However, the surviving debris impact footprint cannot be guaranteed to avoid inhabited landmasses. Controlled entry normally occurs by using a larger amount of propellant with a larger propulsion system to drive the spacecraft to enter the atmosphere at a steeper flight path angle. It will then enter at a more precise latitude, longitude, and footprint in a nearly uninhabited impact region, generally located in the ocean.

Johnson, Nicholas L.↗
NASA NTRS2013

Multi-User Space Link Extension (SLE) System

The Multi-User Space (MUS) Link Extension system, a software and data system, provides Space Link Extension (SLE) users with three space data transfer services in timely, complete, and offline modes as applicable according to standards defined by the Consultative Committee for Space Data Systems (CCSDS). MUS radically reduces the schedule, cost, and risk of implementing a new SLE user system, minimizes operating costs with a lights-out approach to SLE, and is designed to require no sustaining engineering expense during its lifetime unless changes in the CCSDS SLE standards, combined with new provider implementations, force changes. No software modification to MUS needs to be made to support a new mission. Any systems engineer with Linux experience can begin testing SLE user service instances with MUS starting from a personal computer (PC) within five days. For flight operators, MUS provides a familiar-looking Web page for entering SLE configuration data received from SLE. Operators can also use the Web page to back up a space mission's entire set of up to approximately 500 SLE service instances in less than five seconds, or to restore or transfer from another system the same amount of data from a MUS backup file in about the same amount of time. Missions operate each MUS SLE service instance independently by sending it MUS directives, which are legible, plain ASCII strings. MUS directives are usually (but not necessarily) sent through a TCP-IP (Transmission Control Protocol Internet Protocol) socket from a MOC (Mission Operations Center) or POCC (Payload Operations Control Center) system, under scripted control, during "lights-out" spacecraft operation. MUS permits the flight operations team to configure independently each of its data interfaces; not only commands and telemetry, but also MUS status messages to the MOC. Interfaces can use single- or multiple-client TCP/IP server sockets, TCP/IP client sockets, temporary disk files, the system log, or standard in, standard out, or standard error as applicable. By defining MUS templates in ASCII, the flight operations team can include any MUS system variable in telemetry or command headers or footers, and/or in status messages. Data fields can be arranged within messages in different sequences, according to the mission s needs. The only constraints imposed are on the format of MUS directive strings, and some bare minimum logical requirements that must be met in order for MUS to read the mission control center's spacecraft command inputs. The MUS system imposes no limits or constraints on the numbers and combinations of missions and SLE service instances that it will support simultaneously. At any time, flight operators may add, change, delete, bind, connect, or disconnect.

Perkins, Toby↗
NASA NTRSDate not supplied

Lunar Search & Rescue Applications of Lunar GNSS

Accurate lunar navigation and timing knowledge provides for the development of safety-critical services in the cislunar and lunar surface domain. Currently under development, the Goddard Space Flight Center’s (GSFC) Search and Rescue Mission Office is investigating and integrating search and rescue (SAR) capability into planned and future lunar communication and navigation interfaces. Lunar Search and Rescue (LunaSAR) development has a stated end-goal for assured, reliable, and timely indication of distress events for a wide variety of lunar surface users, including government-sponsored, commercial, and international users. LunaSAR performance requirements are modelled after the current terrestrial Cospas-Sarsat distress notification system, leveraging an internationally robust global navigation satellite system (GNSS) ecosystem as a core element of survivor locating capability. This presentation will discuss NASA’s work to develop user-focused distress messaging capabilities including infusion of example sensor data for triggering of automated distress alerts coupled with location-tagging. Additionally, the presentation will examine overall message structures, rotating fields for use in bi-directional distress messaging, and specific use cases based on NASA’s lunar exploration and lunar communication relay architectures. Modelling and simulation of LunaSAR use by individual lunar explorers will be discussed, based on notional industry and government design reference missions and mission considerations. Results from GSFC-funded Internal Research and Development (IRAD) efforts will be detailed, including successful distress message formulation simulating the ingestion of example legacy space suit telemetry fields. Hardware-in-the-loop testing using high-reliability software defined radio (SDR) modules serve as an example of IRAD successes and the framework for technical requirements. Architectural development and technical evolution from 2020 to 2021 included alignment of LunaSAR distress waveforms with ongoing NASA LunaNet interoperability development, as well as engagement with NASA Lunar Spectrum authorities for allocation of UHF-band distress frequencies on the lunar surface. S-Band and UHF-band transmission characteristics will be detailed, along with band-specific applications of each emission type. Additionally, examples of ingestion and formatting of GNSS signals (using historical terrestrial National Marine Electronics Association-formatted GNSS data) will be detailed, underscoring lunar user needs for a common lunar GNSS receiver output message framework. Maturity and ability to support evolving lunar exploration goals has been demonstrated and will be detailed, with maturity gaps such as position, navigation, and timing (PNT) and lunar reference frames identified within the context of distress message generation. Provision of LunaSAR services for lunar surface users represents a new era of ensured safety for lunar explorers and builds off of forty years of the Cospas-Sarsat program, underscoring the importance of lunar GNSS for safety-critical applications and growing interest in safe, reliable lunar surface operations. Enabled by new GNSS systems being developed by government and industry partners, NASA will continue to evolve and integrate lunar GNSS types into distress message generation, with a focus on compact and efficient message transmission over various lunar communication links. When fielded, LunaSAR will be the first dedicated search and rescue notification system employed on another celestial body. Robust lunar navigation and timing services form the core of LunaSAR capabilities, allowing for system syncing with time-dominant sensors, and high-accuracy location of those in distress while engaged in lunar surface activities.

Search and Rescue↗
NASA NTRS2003

X-Ray Testing Constellation-X Optics at MSFC's 100-m Facility

In addition to the 530-m-long X-Ray Calibration Facility (XRCF), NASA's Marshall Space Flight Center (MSFC) operates a 104-m-long (source-to-detector) X-ray-test facility. Originally developed and still occasionally used for stray-light testing of visible-fight optical systems, the so-called "Stray-Light Facility" now serves primarily as a convenient and inexpensive facility for performance evaluation and calibration of X-ray optics and detectors. The facility can accommodate X-ray optics up to about 1-m diameter and 12-m focal length. Currently available electron-impact sources at the facility span the approximate energy range 0.2 to 100 keV, thus supporting testing of soft- and hard-X-ray optics and detectors. Available MSFC detectors are a front-illuminated CCD (charge-coupled device) and a scanning CZT (cadmium--zinc--telluride) detector, with low-energy cut-offs of about 0.8 and 3 keV, respectively. In order to test developmental optics for the Constellation-X Project, led by NASA's Goddard Space Flight Center (GSFC), MSFC undertook several enhancements to the facility. Foremost among these was development and fabrication of a five-degree-of-freedom (5-DoF) optics mount and control system, which translates and tilts the user-provided mirror assembly suspended from its interface plate. Initial Constellation-X tests characterize the performance of the Optical Alignment Pathfinder Two (OAP2) for the large Spectroscopy X-ray Telescope (SXT) and of demonstration mirror assemblies for the Hard X-ray Telescope (HXT). With the Centroid Detector Assembly (CDA), used for precision alignment of the Chandra (nee AXAF) mirrors, the Constellation-X SXT Team optically aligned the individual mirrors of the OAPZ at GSFC. The team then developed set-up and alignment procedures, including transfer of the alignment from the optical alignment facility at GSFC to the X-ray test facility at MSFC, using a reference flat and fiducials. The OAPZ incorporates additional ancillary features --- fixed aperture mask and movable sub-aperture mask --- to facilitate X-ray characterization of the optics. Although the OAPZ was designed to- have low sensitivity to temperature offsets and gradients, analyses showed the necessity of active temperature control for the X-ray performance testing. Thus, the Smithsonian Astrophysical Observatory (SAO) implemented a thermal control and monitoring system, designed to hold the OAP2 close to its assembly.

O'Dell, Stephen↗
NASA NTRS2007

An Analysis of Peak Wind Speed Data from Collocated Mechanical and Ultrasonic Anemometers

This study compared peak wind speeds reported by mechanical and ultrasonic anemometers at Cape Canaveral Air Force Station and Kennedy Space Center (CCAFS/KSC) on the east central coast of Florida and Vandenberg Air Force Base (VAFB) on the central coast of California. Launch Weather Officers, forecasters, and Range Safety analysts need to understand the performance of wind sensors at CCAFS/KSC and VAFB for weather warnings, watches, advisories, special ground processing operations, launch pad exposure forecasts, user Launch Commit Criteria (LCC) forecasts and evaluations, and toxic dispersion support. The legacy CCAFS/KSC and VAFB weather tower wind instruments are being changed from propeller-and-vane (CCAFS/KSC) and cup-and-vane (VAFB) sensors to ultrasonic sensors under the Range Standardization and Automation (RSA) program. Mechanical and ultrasonic wind measuring techniques are known to cause differences in the statistics of peak wind speed as shown in previous studies. The 45th Weather Squadron (45 WS) and the 30th Weather Squadron (30 WS) requested the Applied Meteorology Unit (AMU) to compare data between the RSA ultrasonic and legacy mechanical sensors to determine if there are significant differences. Note that the instruments were sited outdoors under naturally varying conditions and that this comparison was not designed to verify either technology. Approximately 3 weeks of mechanical and ultrasonic wind data from each range from May and June 2005 were used in this study. The CCAFS/KSC data spanned the full diurnal cycle, while the VAFB data were confined to 1000-1600 local time. The sample of 1-minute data from numerous levels on five different towers on each range totaled more than 500,000 minutes of data (482,979 minutes of data after quality control). The ten towers were instrumented at several levels, ranging from 12 ft to 492 ft above ground level. The ultrasonic sensors were collocated at the same vertical levels as the mechanical sensors and typically within 15 ft horizontally of each another. Data from a total of 53 RSA ultrasonic sensors, collocated with mechanical sensors were compared. The 1- minute average wind speed/direction and the 1-second peak wind speed/direction were compared.

Short, David A.↗
NASA NTRS2024

Forced Response Aeromechanics Analysis in MATLAB®-Based Environment Code With Application to Distortion-Tolerant Fan R24 Blade Geometry

Researchers at the NASA Glenn Research Center have developed a research-level code for forced response analysis for turbomachinery that provides a streamlined framework for aeromechanics analysis, as well as for generating Goodman diagrams. The Forced Response Aeromechanics Analysis in a MATLAB-Based Environment (FRAAME, Version 1) code is designed to accept blade surface unsteady pressure time histories generated by three-dimensional (3D) Unsteady Reynolds-Averaged Navier-Stokes (URANS) code TURBO and modal displacements, modal stresses, and static stresses generated via expanded ANSYS® (Ansys, Inc.) cyclic symmetry analysis. The code’s looping structure allows for largescale analyses, including many blade surface pressure files, modal displacements, and modal stress files for full annulus forced response analysis, including a modal summation method for multiple engine orders and modes. This code is applied to the R24 fan geometry for the Boundary Layer Ingesting Inlet/Distortion-Tolerant Fan (BLI2DTF) project, a propulsion system being developed to increase the fuel efficiency of future aircraft, to serve as validation of experimental data as well as external simulation results. This tool’s functional, modular form is intended to allow users to make modifications easily. Those modifications can include requests for information for any step in the analysis process, as well as adding various functions to compute additional information of interest. It is also written, given sufficient input information, as a general blade geometry forced response solver that is not necessarily specific to the R24 geometry but is used here for verification of code functionality and accuracy. Although forced response analysis tools are also available in commercially available code packages, the post-processing FRAAME code offers reliable, fast, and scalable forced response analysis and Goodman diagram generation for large cases utilizing, specifically, TURBO and ANSYS® results information in an effort to streamline forced response and high cycle fatigue analyses.

Aeromechanics↗
NASA NTRS1993

Automated system function allocation and display format: Task information processing requirements

An important consideration when designing the interface to an intelligent system concerns function allocation between the system and the user. The display of information could be held constant, or 'fixed', leaving the user with the task of searching through all of the available information, integrating it, and classifying the data into a known system state. On the other hand, the system, based on its own intelligent diagnosis, could display only relevant information in order to reduce the user's search set. The user would still be left the task of perceiving and integrating the data and classifying it into the appropriate system state. Finally, the system could display the patterns of data. In this scenario, the task of integrating the data is carried out by the system, and the user's information processing load is reduced, leaving only the tasks of perception and classification of the patterns of data. Humans are especially adept at this form of display processing. Although others have examined the relative effectiveness of alphanumeric and graphical display formats, it is interesting to reexamine this issue together with the function allocation problem. Currently, Johnson Space Center is the test site for an intelligent Thermal Control System (TCS), TEXSYS, being tested for use with Space Station Freedom. Expert TCS engineers, as well as novices, were asked to classify several displays of TEXSYS data into various system states (including nominal and anomalous states). Three different display formats were used: fixed, subset, and graphical. The hypothesis tested was that the graphical displays would provide for fewer errors and faster classification times by both experts and novices, regardless of the kind of system state represented within the display. The subset displays were hypothesized to be the second most effective display format/function allocation condition, based on the fact that the search set is reduced in these displays. Both the subset and the graphic display conditions were hypothesized to be processed more efficiently than the fixed display conditions.

Czerwinski, Mary P.↗
NASA NTRSDate not supplied

The Doppler Wind Temperature Sensor (DWTS) Flight Evaluation and Experiments (TES-16,17)

The Doppler Wind Temperature Sensor instrument (DWTS), developed by Global Atmospheric Technologies and Sciences (GATS), is a powerful yet simple tool with the potential of becoming a new window to upper atmosphere dynamics. Based around a defense-grade infrared camera peering through a static gas cell used as a scanning spectral filter, the DWTS is designed to measure the fingerprints of wind and thermal waves as they propagate to the mesosphere and lower thermosphere. DWTS achieves this scanning by measuring the induced change in the doppler shift of the emission as it passes through the DWTS field of view. DWTS holds promise to aid in more accurate weather determination (Gordley, et al), and the core technology can be easily adapted to study other atmospheres of interest. In partnership with GATS, NOAA, and other collaborators, NASA Ames and the Nano Orbital Workshop group have been working to evaluate the DWTS instrument on orbit and optimize it as a flexible cube satellite payload. The first mission selected for DWTS evaluation is preparing for flight in early 2024, followed by a more capable science mission in 2025, with both missions part of the TES-n/NOW flight series. The first flight, TES-16/DWTS-A, will incorporate a single DWTS instrument in an approximately 2U payload volume with the imaging aperture perpendicular to the flight velocity vector. With an estimated power consumption of 20 watts, supplied via a custom NOW-designed GaN converter, the instrument will maintain the imaging sensor plane at 80K using an integrated pulse-tube cryocooler during instrument evaluation periods. Data from DWTS will be captured via a NOW-designed custom data processor before being transmitted via S-band radio back to select ground stations, with instrument command and control operated via L-band global-coverage radio. After the TES-16/DWTS-A initial demonstration mission, the subsequent TES-17/DWTS-B mission will be a dedicated science mission equipped with three DWTS instruments, each hosting a different gas cell to obtain full altitude coverage from 20 to 200 km both day and night from a single cube satellite. The intention of the flight series, and one of NASA’s interests in the instrument, is to advance a Martian atmospheric instrument (Colaprete, Gordley, et al) which, if successful, would greatly further understanding of Martian atmospheric behavior. The proposed paper will review the flight series in detail, including challenges from the TES-16 flight tests and the projected challenges and application to Mars study. Additional detail regarding the possible applications of a Cognitive Communication technique in current flight development by NOW collaborators at the NASA Glenn Research Center will also be discussed, including the implications of using an automated User Initiated Service (UIS) protocol to maximize the data collected per orbit.

Doppler Wind Temperature Sensor↗
NASA NTRS2007

A One Chip Hardened Solution for High Speed SpaceWire System Implementations. Session: Components

An Application Specific Integrated Circuit (ASIC) that implements the SpaceWire protocol has been developed in a radiation hardened 0.25 micron CMOS technology. This effort began in March 2003 as a joint development between the NASA Goddard Space Flight Center (GSFC) and BAE Systems. The BAE Systems SpaceWire ASIC is comprised entirely of reusable core elements, many of which are already flight-proven. It incorporates a router with 4 SpaceWire ports and two local ports, dual PC1 bus interfaces, a microcontroller, 32KB of internal memory, and a memory controller for additional external memory use. The SpaceWire cores are also reused in other ASICs under development. The SpaceWire ASIC is planned for use on the Geostationary Operational Environmental Satellites (GOES)-R, the Lunar Reconnaissance Orbiter (LRO) and other missions. Engineering and flight parts have been delivered to programs and users. This paper reviews the SpaceWire protocol and those elements of it that have been built into the current and next SpaceWire reusable cores and features within the core that go beyond the current standard and can be enabled or disabled by the user. The adaptation of SpaceWire to BAE Systems' On Chip Bus (OCB) for compatibility with the other reusable cores will be reviewed and highlighted. Optional configurations within user systems and test boards will be shown. The physical implementation of the design will be described and test results from the hardware will be discussed. Application of this ASIC and other ASICs containing the SpaceWire cores and embedded microcontroller to Plug and Play and reconfigurable implementations will be described. Finally, the BAE Systems roadmap for SpaceWire developments will be updated, including some products already in design as well as longer term plans.

Marshall, Joseph R.↗
NASA NTRS2001

LabHEART: an interactive computer model of rabbit ventricular myocyte ion channels and Ca transport

An interactive computer program, LabHEART, was developed to simulate the action potential (AP), ionic currents, and Ca handling mechanisms in a rabbit ventricular myocyte. User-oriented, its design allows switching between voltage and current clamp and easy on-line manipulation of key parameters to change the original formulation. The model reproduces normal rabbit ventricular myocyte currents, Ca transients, and APs. We also changed parameters to simulate data from heart failure (HF) myocytes, including reduced transient outward (I(to)) and inward rectifying K currents (I(K1)), enhanced Na/Ca exchange expression, and reduced sarcoplasmic reticulum Ca-ATPase function, but unaltered Ca current density. These changes caused reduced Ca transient amplitude and increased AP duration (especially at lower frequency) as observed experimentally. The model shows that the increased Na/Ca exchange current (I(NaCa)) in HF lowers the intracellular [Ca] threshold for a triggered AP from 800 to 540 nM. Similarly, the decrease in I(K1) reduces the threshold to 600 nM. Changes in I(to) have no effect. Combining enhanced Na/Ca exchange with reduced I(K1) (as in HF) lowers the threshold to trigger an AP to 380 nM. These changes reproduce experimental results in HF, where the contributions of different factors are not readily distinguishable. We conclude that the triggered APs that contribute to nonreentrant ventricular tachycardia in HF are due approximately equally (and nearly additively) to alterations in I(NaCa) and I(K1). A free copy of this software can be obtained at http://www.meddean.luc.edu/lumen/DeptWebs/physio/bers.html.

NASA Discipline Cardiopulmonary↗
NASA NTRS2015

T-38 Primary Flight Display Prototyping and HIVE Support Abstract & Summary

This fall I worked in EV3 within NASA's Johnson Space Center in The HIVE (Human Integrated Vehicles & Environments). The HIVE is responsible for human in the loop testing, getting new technologies in front of astronauts, operators, and users early in the development cycle to make the interfaces more human friendly. Some projects the HIVE is working on includes user interfaces for future spacecraft, wearables to alert astronauts about important information, and test beds to simulate mock missions. During my internship I created a prototype for T-38 aircraft displays using LabVIEW, learned how to use microcontrollers, and helped out with other small tasks in the HIVE. The purpose of developing a prototype for T-38 Displays in LabVIEW is to analyze functions of the display such as navigation in a cost and time effective manner. The LabVIEW prototypes allow Ellington Field AOD to easily make adjustments to the display before hardcoding the final product. LabVIEW was used to create a user interface for simulation almost identical to the real aircraft display. Goals to begin the T-38 PFD (Primary Flight Display) prototype included creating a T-38 PFD hardware display in a software environment, designing navigation for the menu's, incorporating vertical and horizontal navigation bars, and to add a heading bug for compass controls connected to the HSI (Horizontal Situation Indicator). To get started with the project, measurements of the entire display were taken. This enabled an accurate model of the hardware display to be created. Navigation of menu's required some exploration of different buttons on the display. The T-38 simulator and aircraft were used for examining the display. After one piece of the prototype was finished, another trip of to the simulator took place. This was done until all goals for the prototype were complete. Some possible integration ideas for displays in the near future are autopilot selection, touch screen displays, and crew member preferences. Complete navigation, control, and function customization will be achievable once a display is fully developed. Other than the T-38 prototyping, I spent time learning how to design small circuits and write code for them to function. This was done by adding electronic circuit components to breadboard and microcontroller then writing code to speak to those components through the microcontroller. I went through an Arduino starter kit to build circuits and code software that allowed the hardware to act. This work was planned to assist in a lighting project this fall but another solution was discovered for the lighting project. Other tasks that I assisted with, included hands on work such as mock-up construction/removal, logic analyzer repairs, and soldering with circuits. The unique opportunity to be involved work with NASA has significantly changed my educational and career goals. This opportunity has only opened the door to my career with engineering. I have learned over the span of this internship that I am fascinated by the type of work that NASA does. My desire to work in the aerospace industry has increased immensely. I hope to return to NASA to be more involved in the advancement of science, engineering, and spaceflight. My interests for my future education and career lie in NASA’s work - pioneering the future in space exploration, scientific discovery and aeronautics research.

Boniface, Andrew↗