Search NASA⌕ Search

SEARCH · Search NASA

Results for “collaborative control”

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 541 records · Page 30
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Variable Emittance Coatings

Variable emittance coatings (VECs) can reduce thermal control system mass and power by passively changing radiator heat rejection according to spacecraft and environment heat loads. VECs make establishing a lunar presence easier since this technology helps overcome challenges with harsh thermal environments on the lunar surface and in transit. This CIF focuses on creating testing capabilities to assess VECs from collaborators in academia and industry. Two main testing capabilities were created. First, a set of temperature dependent Fourier Transform Infrared Spectroscopy (FTIR) measurement accessories were designed, fabricated, and used to measure samples received from collaborators. These accessories are capable of measuring the transmittance and reflectance of semi transparent and opaque samples. Second, a vacuum calorimetry experiment was designed and built to assess the variable heat rejection of larger coupons.

Sydney Taylor↗
NASA NTRS2012

NASA InterCenter Collaboration Increases ROI

Funding for National Aeronautics and Space Administration (NASA) space mission operations is tighter than ever in the current environment of federal government deficit reductions. Conventional wisdom would expect this environment to drive increasing competition between NASA centers for the limited available funds. However, recent inter-center activities at the Huntsville Operations Support Center (HOSC) at NASA's Marshall Space Flight Center emphasize collaboration rather than competition and demonstrate the value of partnerships to increase the return on shrinking investments. These efforts cover a variety of activities and potential returns. To facilitate sharing data from test and verification through operations without levying requirements on data format or software tools, the HOSC is working with multiple centers on an evolutionary path toward a distributed data architecture and archive. The approach reduces the required investment by allowing the partners to reuse their existing formats and tools, while facilitating gone ]stop h user visibility into and controlled access to the full complement of data regardless of user or data location. The HOSC is also working on two activities to promote sharing operations implementations and leveraging the experts and expertise across multiple NASA sites. In one, the use of Consultative Committee for Space Data Systems (CCSDS) standards for the message abstraction layer provides an interoperability layer on top of existing ground data system communication architectures. This allows missions to select the most appropriate solutions for their requirements with a minimal investment in rehosting the components in a coherent operational environment. The other emphasizes shared tools and increased remote access to minimize travel for tests and critical activities and reduce the floor space required for a dedicated operations center. This paper summarizes these and other inter-center collaboration activities at the HOSC and the benefits that each can bring, not just to the participants, but to the broader operations community.

Lankford, Kimberly↗
NASA NTRS2005

Matlab GUI for a Fluid Mixer

The Test and Engineering Directorate at NASA John C. Stennis Space Center developed an interest to study the modeling, evaluation, and control of a liquid hydrogen (LH2) and gas hydrogen (GH2) mixer subsystem of a ground test facility. This facility carries out comprehensive ground-based testing and certification of liquid rocket engines including the Space Shuttle Main engine. A software simulation environment developed in MATLAB/SIMULINK (M/S) will allow NASA engineers to test rocket engine systems at relatively no cost. In the progress report submitted in February 2004, we described the development of two foundation programs, a reverse look-up application using various interpolation algorithms, a variety of search and return methods, and self-checking methods to reduce the error in returned search results to increase the functionality of the program. The results showed that these efforts were successful. To transfer this technology to engineers who are not familiar with the M/S environment, a four-module GUI was implemented allowing the user to evaluate the mixer model under open-loop and closed-loop conditions. The progress report was based on an udergraduate Honors Thesis by Ms. Jamie Granger Austin in the Department of Electrical Engineering and Computer Science at Tulane University, during January-May 2003, and her continued efforts during August-December 2003. In collaboration with Dr. Hanz Richter and Dr. Fernando Figueroa we published these results in a NASA Tech Brief due to appear this year. Although the original proposal in 2003 did not address other components of the test facility, we decided in the last few months to extend our research and consider a related pressurization tank component as well. This report summarizes the results obtained towards a Graphical User Interface (GUI) for the evaluation and control of the hydrogen mixer subsystem model and for the pressurization tank each taken individually. Further research would combine the two components - mixer and tank, for a more realistic simulation tool.

Barbieri, Enrique↗
NASA NTRSDate not supplied

Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions

To achieve NASA’s Artemis program mission objectives a high level of autonomy and ubiquitous autonomy throughout the systems that are being developed will be necessary. The autonomous systems of Artemis will require a distributed autonomy capability, with autonomous systems organized functionally in a hierarchical architecture, where systems at higher levels of the hierarchy have authority over systems at lower levels. The challenge of developing autonomy technologies and concepts of operations for Artemis has been undertaken by the NASA Gateway Working Group. This group has developed requirements, architectures, concepts of operations, and interface control documents, in the context of a hierarchical distributed architecture that includes the following: a Vehicle System Manager (VSM) that autonomously manages the entire Gateway; Module System Managers (MSMs) that autonomously manage each module; and System Managers (SMs) that autonomously manage systems within a module(i.e. ECLSS).A substantially high level of autonomy needs to be achieved by each element of the hierarchy (VSM, MSM, SM)to meet requirements for uncrewed operations; this includes conditions that will have minimal and/or delayed ground intervention (i.e. requirements for sustainability for months of operation without crew or ground support). To advance an implementation of this autonomy design (Gateway Autonomy Design –GAD), a collaboration was established between the Autonomous Systems Laboratory (ASL) at NASA Stennis Space Center and Lockheed Martin. The objectives of this partnership were the following: (1)to implement autonomy at the VSM, MSM, and SM levels;(2) to implement communications among a VSM, 2 MSMs, ORION (a visiting vehicle somewhat equivalent to a module) and 1 SM (a power system), and (3) test autonomous operations with representative use cases. A SM backed by a high-fidelity simulation was created to facilitate demonstrations of use cases that originated in a system of a module. Communication between the VSM and MSMs was implemented according to Concepts of Operations and Interface Control Documents (ICDs). Demonstrations were conducted to address nominal and off-nominal operations and multi-module interactions with VSM. Additionally, user interfaces were created to provide awareness about ongoing processes and results while enhancing the demonstration. Demonstrations included the following use cases: (1)Orion as visiting vehicle registers with VSM;(2) VSM reschedules a module’s timelines when another module’s MSM task fails; and (3) a module’s Power System Manager (PSM) standalone demonstration that included component failure diagnostics, tracing component failure to effected components, which in turn, reports failure information up to the VSM for acknowledgement and display. This paper will describe the detailed technology and autonomous systems developed, and the integrated multi-module demonstrations conducted. Also, challenges that must be met to fully implement the GAD defined by Gateway will be addressed.

Autonomous Systems↗
NASA NTRSDate not supplied

Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions

To achieve NASA’s Artemis program mission objectives a high level of autonomy that is ubiquitous throughout the systems that are being developed will be necessary. The autonomous systems of Artemis will require a distributed autonomy capability, with autonomous systems organized functionally in a hierarchical architecture, where systems at higher levels of the hierarchy have authority over systems at lower levels. The challenge of developing autonomy technologies and Concepts of Operations (ConOps) for Artemis has been undertaken by the NASA Gateway Working Group. This group has developed requirements, architectures, ConOps, and interface control documents (ICDs), in the context of a hierarchical distributed architecture that includes the following: a Vehicle System Manager (VSM) that autonomously manages the entire Gateway; Module System Managers (MSMs) that autonomously manage each module; and System Managers (SMs) that autonomously manage systems within a module (i.e. ECLSS). A substantially high level of autonomy needs to be achieved by each element of the hierarchy (VSM, MSM, SM) to meet requirements for uncrewed operations; this includes conditions that will have minimal and/or delayed ground intervention (i.e. requirements for sustainability for months of operation without crew or ground support). To advance an implementation of this autonomy design (Gateway Autonomy Design – GAD), a collaboration was established between the Autonomous Systems Laboratory (ASL) at NASA Stennis Space Center and Lockheed Martin. The objectives of this partnership were the following: (1) to implement autonomy at the VSM, MSM, and SM levels; (2) to implement communications among a VSM, 2 MSMs, ORION (a visiting vehicle somewhat equivalent to a module) and 1 SM (a power system), and (3) test autonomous operations with representative use cases. A SM backed by a high-fidelity simulation was created to facilitate demonstrations of use cases that originated in a system of a module. Communication between the VSM and MSMs was implemented according to Concepts of Operations and Interface Control Documents (ICDs). Demonstrations were conducted to address nominal and off-nominal operations and multi-module interactions with the VSM. Additionally, user interfaces were created to provide awareness about ongoing processes and results while enhancing the demonstration. Demonstrations included the following use cases: (1) Orion as visiting vehicle registers with VSM; (2) VSM reschedules a module’s timelines when another module’s MSM task fails; and (3) a module’s Power System Manager (PSM) demonstration that included component failure diagnostics, tracing component failure to effected components, which in turn, reports failure information up to the VSM for acknowledgement and display. This paper will describe the detailed technology and autonomous systems developed, and the integrated multi-module demonstrations conducted. Also, challenges that must be met to fully implement the GAD defined by Gateway will be addressed.

Fernando Figueroa↗
NASA NTRS2008

DARPA/USAF/USN J-UCAS X-45A System Demonstration Program: A Review of Flight Test Site Processes and Personnel

The Joint Unmanned Combat Air Systems (J-UCAS) program is a collaborative effort between the Defense Advanced Research Project Agency (DARPA), the US Air Force (USAF) and the US Navy (USN). Together they have reviewed X-45A flight test site processes and personnel as part of a system demonstration program for the UCAV-ATD Flight Test Program. The goal was to provide a disciplined controlled process for system integration and testing and demonstration flight tests. NASA's Dryden Flight Research Center (DFRC) acted as the project manager during this effort and was tasked with the responsibilities of range and ground safety, the provision of flight test support and infrastructure and the monitoring of technical and engineering tasks. DFRC also contributed their engineering knowledge through their contributions in the areas of autonomous ground taxi control development, structural dynamics testing and analysis and the provision of other flight test support including telemetry data, tracking radars, and communications and control support equipment. The Air Force Flight Test Center acted at the Deputy Project Manager in this effort and was responsible for the provision of system safety support and airfield management and air traffic control services, among other supporting roles. The T-33 served as a J-UCAS surrogate aircraft and demonstrated flight characteristics similar to that of the the X-45A. The surrogate served as a significant risk reduction resource providing mission planning verification, range safety mission assessment and team training, among other contributions.

Cosentino, Gary B.↗
NASA NTRS2010

International Space Station Aeromedical Support in Star City, Russia

The Space Medicine Division at Johnson Space Center works with the International Space Station s international partners (IP) to accomplish assigned health care tasks. Each IP may assign a flight surgeon to support their assigned crewmembers during all phases of training, in-flight operations, and postflight activities. Because of the extensive amount of astronaut training conducted in Star City; NASA, in collaboration with its IPs, has elected to keep a flight surgeon assigned to NASA s Star City office to provide support to the U.S., Canadian, Japanese, and European astronauts during hazardous training activities and provide support for any contingency landings of Soyuz spacecraft in Kazakhstan. The physician also provides support as necessary to the Mission Control Center in Moscow for non-Russian crew-related activities. In addition, the physician in Star City provides ambulatory medical care to the non-Russian-assigned personnel in Star City and visiting dependents. Additional work involves all medical supplies, administration, and inventory. The Star City physician assists in medical evacuation and/or in obtaining support from western clinics in Moscow when required care exceeds local resources. Overall, the Russians are responsible for operations and the medical care of the entire crew when training in Star City and during launch/landing operations. However, they allow international partner flight surgeons to care for their crewmembers as agreed to in the ISS Medical Operations Requirements Document. Medical support focuses on pressurized, monitored, and other hazardous training activities. One of the most important jobs is to act as a medical advocate for the astronauts and to reduce the threat that these hazardous activities pose. Although the Russians have a robust medical system, evacuation may be needed to facilitate ongoing medical care. There are several international medical evacuation companies that provide this care.

Cole, Richard↗
NASA NTRS2015

Marshall Space Flight Center Faculty Fellowship Program

The Faculty Fellowship program was revived in the summer of 2015 at NASA Marshall Space Flight Center, following a period of diminished faculty research activity here since 2006 when budget cuts in the Headquarters' Education Office required realignment. Several senior Marshall managers recognized the need to involve the Nation's academic research talent in NASA's missions and projects to the benefit of both entities. These managers invested their funds required to establish the renewed Faculty Fellowship program in 2015, a 10-week residential research involvement of 16 faculty in the laboratories and offices at Marshall. These faculty engineers and scientists worked with NASA collaborators on NASA projects, bringing new perspectives and solutions to bear. This Technical Memorandum is a compilation of the research reports of the 2015 Marshall Faculty Fellowship program, along with the Program Announcement (appendix A) and the Program Description (appendix B). The research touched on seven areas-propulsion, materials, instrumentation, fluid dynamics, human factors, control systems, and astrophysics. The propulsion studies included green propellants, gas bubble dynamics, and simulations of fluid and thermal transients. The materials investigations involved sandwich structures in composites, plug and friction stir welding, and additive manufacturing, including both strength characterization and thermosets curing in space. The instrumentation projects involved spectral interfero- metry, emissivity, and strain sensing in structures. The fluid dynamics project studied the water hammer effect. The human factors project investigated the requirements for close proximity operations in confined spaces. Another team proposed a controls system for small launch vehicles, while in astrophysics, one faculty researcher estimated the practicality of weather modification by blocking the Sun's insolation, and another found evidence in satellite data of the detection of a warm-hot intergalactic medium filament. Our goal is to continue the Faculty Fellowship effort with Center funds in succeeding summers.

Six, N. F.↗
NASA NTRSDate not supplied

Pilot Study of Medications Exposed to Vacuum

Background Few studies have been conducted regarding the effects of vacuum on medications and their packaging. While relevant on the International Space Station, understanding these effects becomes even more critical as future NASA missions venture farther away from Earth. Vehicles supporting the Artemis missions will have dedicated, vehicle-specific medical kits as well as crew medical accessory kits. Although most of the kits will be stored in a pressurized, climate-controlled volume, there are specific scenarios in which they may become exposed to vacuum. These include the vehicle being brought to vacuum to enable clearance of atmospheric contaminants, and on Human Landing System (HLS), in the airlock (in which kits may be stored) during extravehicular activities. Overview The Exploration Medical Integrated Product Team (XMIPT) in collaboration with the Department of Defense is conducting a pilot study to assess the effects of vacuum on the medications and their packaging to be used in exploration missions. Phase A of this study will focus on manufacturer’s package integrity and Phase B on identifying chemical changes through active pharmaceutical ingredient (API) testing of the medications at 0, 4.5 and 9 months post exposure. Two exposure durations, 1 hour and 8 hours were selected to represent the expected time at vacuum for an Orion contaminated atmosphere vent/repress and the time at vacuum for a lunar surface EVA. The medications for this study were identified based on those currently being considered for future Artemis missions and represent the types of pharmaceuticals and formulations that are likely to comprise an exploration formulary. Discussion The results from this pilot study will aid in decision making related to the development of medical kits, medication packaging and stowage for long duration lunar and Mars missions, and inform the direction of future medication in vacuum studies.

Vacuum↗
NASA NTRS2015

Collaborating with Autonomous Agents

With the anticipated increase of small unmanned aircraft systems (sUAS) entering into the National Airspace System, it is highly likely that vehicle operators will be teaming with fleets of small autonomous vehicles. The small vehicles may consist of sUAS, which are 55 pounds or less that typically will y at altitudes 400 feet and below, and small ground vehicles typically operating in buildings or defined small campuses. Typically, the vehicle operators are not concerned with manual control of the vehicle; instead they are concerned with the overall mission. In order for this vision of high-level mission operators working with fleets of vehicles to come to fruition, many human factors related challenges must be investigated and solved. First, the interface between the human operator and the autonomous agent must be at a level that the operator needs and the agents can understand. This paper details the natural language human factors e orts that NASA Langley's Autonomy Incubator is focusing on. In particular these e orts focus on allowing the operator to interact with the system using speech and gestures rather than a mouse and keyboard. With this ability of the system to understand both speech and gestures, operators not familiar with the vehicle dynamics will be able to easily plan, initiate, and change missions using a language familiar to them rather than having to learn and converse in the vehicle's language. This will foster better teaming between the operator and the autonomous agent which will help lower workload, increase situation awareness, and improve performance of the system as a whole.

Trujillo, Anna C.↗
NASA NTRS2014

Exploration Technologies for Operations

Although the International Space Station (ISS) assembly has been completed, the Operations support teams continue to seek more efficient and effective ways to prepare for and conduct the ISS operations and future exploration missions beyond low earth orbit. This search for improvement has led to a significant collaboration between the NASA research and advanced software development community at NASA Ames Research Center and the Mission Operations community at NASA Johnson Space Center. Since 2001, NASA Ames Research Center has been developing and applying its advanced intelligent systems and human systems integration research to mission operations tools for several of the unmanned Mars missions operations. Since 2006, NASA Ames Research Center has also been developing and applying its advanced intelligent systems and human systems integration research to mission operations tools for manned operations support with the Mission Operations Directorate at NASA Johnson Space Center. This paper discusses the completion of the development and deployment of a variety of intelligent and human systems technologies adopted for manned mission operations. The technologies associated with the projects include advanced software systems for operations and human-centered computing. Human-centered computing looks to the processes and procedures that people do to perform any given job, then attempts to identify opportunities to improve these processes and procedures. In particular, for mission operations, improvements are quantified by specifically identifying how a tool can increase a persons efficiency, enhance a persons functional capability, andor improve the assurance of a persons decisions. The Ames development team has collaborated with the Mission Operations team to identify areas of efficiencies through technology infusion applications in support of the Plan, Train, and Fly activities of human-spaceflight mission operations. The specific applications discussed in this paper are in the areas of mission planning systems, mission operations design modeling and workflow automation, advanced systems monitoring, mission control technologies, search tools, training management tools, spacecraft solar array management, spacecraft power management, and spacecraft attitude planning. We discuss these specific projects between the Ames Research Center and the Johnson Space Centers Mission Operations Directorate, and how these technologies and projects are enhancing the mission operations support for the International Space Station. We also discuss the challenges, problems, and successes associated with long-distance and multi-year development projects between the research team at Ames and the Mission Operations customers at Johnson Space center. Finally, we discuss how these technology infusion applications and underlying technologies might be used in the future to support on-board operations of the crew and spacecraft systems as human exploration expands beyond low earth orbit to destinations in the solar system where communications delays will require more on-board autonomy and planning by the crew. Longer communications delays will require that the ground mission operations support will be primarily strategic in nature, while the tactical level of planning, systems monitoring and control, and failure analysisisolationrecovery will be the responsibility of both the spacecraft autonomous systems and the crew. Our expectation is that the technologies

mission operations↗
NASA NTRSDate not supplied

Firmware Architecture of the ARMADAS Bolting Robot

The Automated Reconfigurable Mission Adaptive Digital Assembly Systems (ARMADAS) project, under development at NASA Ames Research Center, has demonstrated on-ground autonomous robotic assembly of extensive digital structures, and it is now moving forward towards in-space demonstration. The ARMADAS system comprises of the operation software, the operation user interface (opsUI), and a swarm of robots. The robotic system consists of a multitude of collaborative agents specifically designed to transport, place and bolt the building blocks, called voxels (volumetric pixels). This paper focuses on the bolting robot, referred to as Mobile Metamaterial Internal Co-Integrator (MMIC-I). MMIC-I is a battery-powered crawling robot. It navigates the structure through extension, contraction and gripping. Two distinct controller boards operate the robot's two symmetric modules, referred to as module A and B. Board A is the master board: it coordinates motion planning and motion primitives execution, hosts the WiFi client, performs periodic self-assessment and system idle check and triggers faults if anomalies are detected. Board B periodically sends a heartbeat to board A, through a wired communication channel that uses the Serial protocol. Additionally, board A's WiFi client receives heartbeat packet requests or motion/bolting commands from a dedicated server board, and acknowledges reception sending back a response heartbeat packet containing information about the overall robot status, e. g. electrical current and voltage values, target and actual angles, operating mode, fault status. Whenever a motion command is sent, the motion planning section of the firmware determines the current robot configuration, using Inertial Measurement Unit readings and the motors Pulse Width Modulation values. Afterwards, it calculates the list of primitives needed to reach the target state, and controls their execution in the proper order. MMIC-I can receive and execute motion and bolting commands only when it is in operational mode. MMIC-I has three operating modes: standby, operational and safed. Standby mode is automatically entered upon startup. While in standby mode, all motors are powered off, and the only accepted commands are the ones relative to a change of mode and heartbeat packet request. Fault detection causes the robot to automatically enter safed or standby mode. Whenever the detected fault occurs within a motion and requires immediate intervention, e. g. an over-current situation, the robot enters safed mode. Safed mode powers off all motors except for the locomotion module, thus preventing the robot from collapsing. Conversely, when the detected fault doesn't require immediate intervention (low battery warning, for instance), the robot enters standby mode after completing the ongoing motion. This paper provides a detailed discussion of MMIC-I's firmware architecture. It accurately describes the implementation approach for each module: sensor data reading, motor control and actuation, WiFi server-client communication, intra-boards Serial communication, operating modes and autonomous fault detection, motion planning, coordination and execution, etc. Moreover, in support of the software description, this paper includes a thorough characterization of MMIC-I's hardware and avionics.

In-space assembly↗
NASA NTRS2003

The Fizeau Interferometer Testbed

The Fizeau Interferometer Testbed (FIT) is a collaborative effort between NASA's Goddard Space Flight Center, the Naval Research Laboratory, Sigma Space Corporation, and the University of Maryland. The testbed will be used to explore the principles of and the requirements for the full, as well as the pathfinder, Stellar Imager mission concept. It has a long term goal of demonstrating closed-loop control of a sparse array of numerous articulated mirrors to keep optical beams in phase and optimize interferometric synthesis imaging. In this paper we present the optical and data acquisition system design of the testbed, and discuss the wavefront sensing and control algorithms to be used. Currently we have completed the initial design and hardware procurement for the FIT. The assembly and testing of the Testbed will be underway at Goddard's Instrument Development Lab in the coming months.

OPTICS DESIGN↗
NASA NTRS2014

RECOVER: An Automated Cloud-Based Decision Support System for Post-fire Rehabilitation Planning

RECOVER is a site-specific decision support system that automatically brings together in a single analysis environment the information necessary for post-fire rehabilitation decision-making. After a major wildfire, law requires that the federal land management agencies certify a comprehensive plan for public safety, burned area stabilization, resource protection, and site recovery. These burned area emergency response (BAER) plans are a crucial part of our national response to wildfire disasters and depend heavily on data acquired from a variety of sources. Final plans are due within 21 days of control of a major wildfire and become the guiding document for managing the activities and budgets for all subsequent remediation efforts. There are few instances in the federal government where plans of such wide-ranging scope and importance are assembled on such short notice and translated into action more quickly. RECOVER has been designed in close collaboration with our agency partners and directly addresses their high-priority decision-making requirements. In response to a fire detection event, RECOVER uses the rapid resource allocation capabilities of cloud computing to automatically collect Earth observational data, derived decision products, and historic biophysical data so that when the fire is contained, BAER teams will have a complete and ready-to-use RECOVER dataset and GIS analysis environment customized for the target wildfire. Initial studies suggest that RECOVER can transform this information-intensive process by reducing from days to a matter of minutes the time required to assemble and deliver crucial wildfire-related data.

cloud computing↗
NASA NTRSDate not supplied

Quiet Spacecraft Cabin Ventilation Fan Development: Motivation and Context

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

Christopher S. Allen↗
NASA NTRS2001

Hall Thruster Plume Measurements On-Board the Russian Express Satellites

The operation of North-South and East-West station-keeping Hall thruster propulsion systems on-board two Russian Express-A geosynchronous communication satellites were investigated through a collaborative effort with the manufacturer of the spacecraft. Over 435 firings of 16 different thrusters with a cumulative run time of over 550 hr were reported with no thruster failures. Momentum transfer due to plume impingement was evaluated based on reductions in the effective thrust of the SPT-100 thrusters and induced disturbance torques determined based on attitude control system data and range data. Hall thruster plasma plume effects on the transmission of C-band and Ku-band communication signals were shown to be negligible. On-orbit ion current density measurements were made and subsequently compared to predictions and ground test data. Ion energy, total pressure, and electric field strength measurements were also measured on-orbit. The effect of Hall thruster operation on solar array performance over several months was investigated. A subset of these data is presented.

Manzella, David↗
NASA NTRS2014

CEO Sites Mission Management System (SMMS)

Late in fiscal year 2011, the Crew Earth Observations (CEO) team was tasked to upgrade its science site database management tool, which at the time was integrated with the Automated Mission Planning System (AMPS) originally developed for Earth Observations mission planning in the 1980s. Although AMPS had been adapted and was reliably used by CEO for International Space Station (ISS) payload operations support, the database structure was dated, and the compiler required for modifications would not be supported in the Windows 7 64-bit operating system scheduled for implementation the following year. The Sites Mission Management System (SMMS) is now the tool used by CEO to manage a heritage Structured Query Language (SQL) database of more than 2,000 records for Earth science sites. SMMS is a carefully designed and crafted in-house software package with complete and detailed help files available for the user and meticulous internal documentation for future modifications. It was delivered in February 2012 for test and evaluation. Following acceptance, it was implemented for CEO mission operations support in April 2012. The database spans the period from the earliest systematic requests for astronaut photography during the shuttle era to current ISS mission support of the CEO science payload. Besides logging basic image information (site names, locations, broad application categories, and mission requests), the upgraded database management tool now tracks dates of creation, modification, and activation; imagery acquired in response to requests; the status and location of ancillary site information; and affiliations with studies, their sponsors, and collaborators. SMMS was designed to facilitate overall mission planning in terms of site selection and activation and provide the necessary site parameters for the Satellite Tool Kit (STK) Integrated Message Production List Editor (SIMPLE), which is used by CEO operations to perform daily ISS mission planning. The CEO team uses the SMMS for three general functions - database queries of content and status, individual site creation and updates, and mission planning. The CEO administrator of the science site database is able to create or modify the content of sites and activate or deactivate them based on the requirements of the sponsors. The administrator supports and implements ISS mission planning by assembling, reporting, and activating mission-specific site selections for management; deactivating sites as requirements are met; and creating new sites, such as International Charter sites for disasters, as circumstances warrant. In addition to the above CEO internal uses, when site planning for a specific ISS mission is complete and approved, the SMMS can produce and export those essential site database elements for the mission into XML format for use by onboard Earth-location systems, such as Worldmap. The design, development, and implementation of the SMMS resulted in a superior database management system for CEO science sites by focusing on the functions and applications of the database alone instead of integrating the database with the multipurpose configuration of the AMPS. Unlike the AMPS, it can function and be modified within the existing Windows 7 environment. The functions and applications of the SMMS were expanded to accommodate more database elements, report products, and a streamlined interface for data entry and review. A particularly elegant enhancement in data entry was the integration of the Google Earth application for the visual display and definition of site coordinates for site areas defined by multiple coordinates. Transfer between the SMMS and Google Earth is accomplished with a Keyhole Markup Language (KML) expression of geographic data (see figures 3 and 4). Site coordinates may be entered into the SMMS panel directly for display in Google Earth, or the coordinates may be defined on the Google Earth display as a mouse-controlled polygonal definition and transferred back into the SMMS as KML input. This significantly reduces the possibility of errors in coordinate entries and provides visualization of the scale of the site being defined. CEO now has a powerful tool for managing and defining sites on the Earth's surface for both targets of astronaut photography or other onboard remote sensing systems. It can also record and track results by sponsor, collaborator, or type of study.

Trenchard, Mike↗