Search NASA⌕ Search

SEARCH · Search NASA

Results for “Engine Ground Testing”

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 1,423 records · Page 79

NASA's Space Launch System: Progress Report

After more than four decades exploring the space environment from low Earth orbit and developing long-duration spaceflight operational experience with the International Space Station (ISS), NASA is once again preparing to send explorers into deep space. Development, test and manufacturing is now underway on the launch vehicle, the crew spacecraft and the ground processing and launch facilities to support human and robotic missions to the moon, Mars and the outer solar system. The enabling launch vehicle for these ambitious new missions is the Space Launch System (SLS), managed by NASA's Marshall Space Flight Center (MSFC). Since the program began in 2011, the design has passed Critical Design Review, and extensive development, test and flight hardware has been produced by every major element of the SLS vehicle. Testing continues on engines, boosters, tanks and avionics. While the program has experienced engineering challenges typical of a new development, it continues to make steady progress toward the first SLS mission in roughly two years and a sustained cadence of missions thereafter. This paper will discuss these and other technical and SLS programmatic successes and challenges over the past year and provide a preview of work ahead before first flight.

Cook, Jerry↗

Hot gas ingestion: From model results to full scale engine testing

An overview is presented of a joint NASA Lewis McDonnell Aircraft Co. Hot Gas Ingestion (HGI) test program in NASA Lewis' 9 x 15 foot Low Speed Wind Tunnel (LSWT). Advanced short takeoff vertical landing (ASTOVL) aircraft capable of operating from remote sites, damaged runways, aircraft carriers and small air-capable ships are being pursued for deployment around the turn of the century. To achieve this goal, it is important that technologies critical to this unique class of aircraft be developed. One of the ASTOVL concepts, the vectored thrust, has as its critical technology item, the potential of hot gas ingestion (which occurs during vertical flight operation while in ground effect) as a key development issue. Recognizing this need, NASA Lewis Powered Lift Section and McAir have defined a cooperative program for testing in the Lewis 9 x 15 foot LSWT. This program is described in detail.

Johns, Albert L.↗

International Space Station Internal Thermal Control System Lab Module Simulator Build-Up and Validation

As part of the Sustaining Engineering program for the International Space Station (ISS), a ground simulator of the Internal Thermal Control System (ITCS) in the Lab Module was designed and built at the Marshall Space Flight Center (MSFC). To support prediction and troubleshooting, this facility is operationally and functionally similar to the flight system and flight-like components were used when available. Flight software algorithms, implemented using the LabVIEW(Registered Trademark) programming language, were used for monitoring performance and controlling operation. Validation testing of the low temperature loop was completed prior to activation of the Lab module in 2001. Assembly of the moderate temperature loop was completed in 2002 and validated in 2003. The facility has been used to address flight issues with the ITCS, successfully demonstrating the ability to add silver biocide and to adjust the pH of the coolant. Upon validation of the entire facility, it will be capable not only of checking procedures, but also of evaluating payload timelining, operational modifications, physical modifications, and other aspects affecting the thermal control system.

Paul Wieland↗

Data Acquisition and Control Systems Laboratory

The Data Acquisition and Control Systems (DACS) Laboratory is a facility at Stennis Space Center that provides an off test-stand capability to develop data-acquisition and control systems for rocket-engine test stands. It is also used to train new employees in state-of-the-art systems, and provides a controlled environment for troubleshooting existing systems, as well as the ability to evaluate the application of new technologies and process improvements. With the SSC propulsion testing schedules, without the DACS Laboratory, it would have been necessary to perform most of the development work on actual test systems, thereby subjecting both the rocket-engine testing and development programs to substantial interference in the form of delays, restrictions on modifications of equipment, and potentially compromising software configuration control. The DACS Laboratory contains a versatile assortment of computer hardware and software, digital and analog electronic control and data-acquisition equipment, and standard electronic bench test equipment and tools. Recently completed Control System development and software verification projects include support to the joint NASA/Air Force Integrated Powerhead Demonstration (IPD) LOX & LH2 PreBurner and Turbopump ground testing programs. In other recent activities, the DACS Laboratory equipment and expertise have supported the off-stand operation of high-pressure control valves to correct valve leak problems prior to installation on the test stand. Future plans include expanding the Laboratory's capabilities to provide cryogenic control valve characterization prior to installation, thereby reducing test stand activation time.

Holland, Randy↗

An Analysis of Model Scale Data Transformation to Full Scale Flight Using Chevron Nozzles

Ground-based model scale aeroacoustic data is frequently used to predict the results of flight tests while saving time and money. The value of a model scale test is therefore dependent on how well the data can be transformed to the full scale conditions. In the spring of 2000, a model scale test was conducted to prove the value of chevron nozzles as a noise reduction device for turbojet applications. The chevron nozzle reduced noise by 2 EPNdB at an engine pressure ratio of 2.3 compared to that of the standard conic nozzle. This result led to a full scale flyover test in the spring of 2001 to verify these results. The flyover test confirmed the 2 EPNdB reduction predicted by the model scale test one year earlier. However, further analysis of the data revealed that the spectra and directivity, both on an OASPL and PNL basis, do not agree in either shape or absolute level. This paper explores these differences in an effort to improve the data transformation from model scale to full scale.

Brown, Clifford↗

Lessons for Future In-Space Telerobotic Servicing from Robotic Refueling Mission

The Robotic Refueling Mission (RRM) was a multi-phased technology development effort by the National Aeronautics & Space Administration (NASA) and the Canadian Space Agency (CSA). The program leveraged the existing robotic systems and expertise of the International Space Station (ISS) program and the tool design and satellite servicing expertise of NASA’s Exploration & In-space Services (NExIS) Projects Division at Goddard Space Flight Center (GSFC) to evaluate new hardware and techniques for on-orbit telerobotic servicing. Between 2011 and 2021, two external ISS payloads housed over a dozen robotic tools and adapters designed to service a variety of existing and novel satellite interfaces. Robot operators at NASA’s Johnson Space Center (JSC) and CSA used the Special Purpose Dexterous Manipulator (SPDM) to retrieve and operate these tools for tasks such as cutting wires or multi-layer insulation blanketing, removing valve caps, mating electrical connectors, transferring fluids, and performing visual inspections inside a vehicle. Each phase of RRM involved years of preparation. Tool and interface designs were prototyped and evaluated using both NASA and Canadian ground robotic systems. Procedures were developed by GSFC engineers and vetted in partnership with JSC and CSA robot operators. GSFC engineers were trained to provide real-time support during on-orbit operations. These preparatory efforts and the successful on-orbit evaluations yielded an array of lessons for future in-space telerobotic missions. Designing robotic tools for the space environment requires special consideration of materials, indicators, and differences between ground and flight use cases and environments. When there is a limited window for on-orbit operations, devoting time and high-fidelity hardware to ground testing can be critical. Needs during potential troubleshooting are more essential to camera view quality, frame rate, and position requirements more than nominal operations. Detailed hardware manuals, nominal and contingency procedures, along with clearly defined operations team roles and protocols are vital for efficiency. RRM also demonstrated how the ISS can be utilized to increase the technology readiness levels required for future missions and led to additional technology partnerships between NExIS and the ISS program. The lessons from RRM are currently being applied to designs, operations concepts, and ground test methodology for missions such as On-orbit Servicing, Assembly, and Manufacturing1(OSAM-1)and Mars Sample Return.

Zakiya Tomlinson↗

A Simulation Architecture for Air Traffic Over Urban Environments Supporting Autonomy Research in Advanced Air Mobility

As part of its research, NASA investigates concepts, aircraft, and operations related to Advanced Air Mobility (AAM). One of the most challenging scenarios for AAM will be enabling safe routine access near densely populated urban centers. AAM flight operations over a regional area require a moderately high-fidelity simulation capability to develop and evaluate autonomy technologies in the urban environment. This paper aims to describe a system to simulate flight operations around regions such as the San Francisco-Oakland Bay area at a moderately-high scale (tens to hundreds of flights) that incorporates detailed vehicle models and control necessary to support research in airborne autonomy. The flight vehicle utilizes NASA AAM concept vehicle dynamics integrated with a custom flight management system and flight control system to simulate all flight phases accurately. The simulation incorporates a detailed simulated urban environment and includes glass cockpit displays to monitor aircraft operations. Simulation models integrate to simulate air and ground-based sensors, such as Radar and LiDAR. As a commercially available rendering engine, X-Plane 11 is used as the renderer to simulate vision-based sensors (such as onboard and ground-based cameras) with a detailed graphical model of a city at different times of the day and weather conditions. This paper presents the simulation and software architecture used for simulating AAM traffic over this urban region. This system enables the evaluation of NASA research concepts in autonomy for urban AAM operations on the path toward flight test evaluation.

distributed sensing↗

A Simulation Architecture for Air Traffic Over Urban Environments Supporting Autonomy Research in Advanced Air Mobility

As part of its research, NASA investigates concepts, aircraft, and operations related to Advanced Air Mobility (AAM). One of the most challenging scenarios for AAM will be enabling safe routine access near densely populated urban centers. AAM flight operations over a regional area require a moderately high-fidelity simulation capability to develop and evaluate autonomy technologies in the urban environment. This paper aims to describe a system to simulate flight operations around regions such as the San Francisco-Oakland Bay area at a moderately-high scale (tens to hundreds of flights) that incorporates detailed vehicle models and control necessary to support research in airborne autonomy. The flight vehicle utilizes NASA AAM concept vehicle dynamics integrated with a custom flight management system and flight control system to simulate all flight phases accurately. The simulation incorporates a detailed simulated urban environment and includes glass cockpit displays to monitor aircraft operations. Simulation models integrate to simulate air and ground-based sensors, such as Radar and LiDAR. As a commercially available rendering engine, X-Plane 11 is used as the renderer to simulate vision-based sensors (such as onboard and ground-based cameras) with a detailed graphical model of a city at different times of the day and weather conditions. This paper presents the simulation and software architecture used for simulating AAM traffic over this urban region. This system enables the evaluation of NASA research concepts in autonomy for urban AAM operations on the path toward flight test evaluation.

Distributed sensing↗

Ground Test Validations for Uncrewed Dormancy Preparation and Recovery

In future long duration space flight and habitation missions, periods of uncrewed dormancy where life support systems are shutdown or in low power-modes will occur. To examine the impacts of these dormant periods, along with potential pre- and post-dormancy procedures, Marshall Space Flight Center has been building an uncrewed dormancy test stand. The uncrewed dormancy test stand will include a urine separator from the Universal Waste Management System, a condensate separator, urine filter, brine filter and distillate filter. In conjunction to the test stand, the Center for Biofilm Engineering (CBE) has ongoing long-term dormancy experiments to assess microbial survival in a variety of simulated shutdown procedures including shut-in, flushing with and without biocide, and dry-out conditions. This publication will serve as a discussion of dormancy considerations, criteria for success, and experimental designs for testing dormancy conditions and shutdown procedures. It will include an update of ongoing test stand construction, including a description of the current lower-fidelity versions of the urine and condensate separators being produced. It will also examine dormancy work being conducted by the CBE and discuss how this may factor into procedures tested on the uncrewed dormancy test stand.

Eric Beitle↗

Man-vehicle systems research facility advanced aircraft flight simulator throttle mechanism

The Advanced Aircraft Flight Simulator is equipped with a motorized mechanism that simulates a two engine throttle control system that can be operated via a computer driven performance management system or manually by the pilots. The throttle control system incorporates features to simulate normal engine operations and thrust reverse and vary the force feel to meet a variety of research needs. While additional testing to integrate the work required is principally now in software design, since the mechanical aspects function correctly. The mechanism is an important part of the flight control system and provides the capability to conduct human factors research of flight crews with advanced aircraft systems under various flight conditions such as go arounds, coupled instrument flight rule approaches, normal and ground operations and emergencies that would or would not normally be experienced in actual flight.

Kurasaki, S. S.↗

The X-38 Spacecraft Fault-Tolerant Avionics System

In 1995 NASA began an experimental program to develop a reusable crew return vehicle (CRV) for the International Space Station. The purpose of the CRV was threefold: (i) to bring home an injured or ill crewmember; (ii) to bring home the entire crew if the Shuttle fleet was grounded; and (iii) to evacuate the crew in the case of an imminent Station threat (i.e., fire, decompression, etc). Built at the Johnson Space Center, were two approach and landing prototypes and one spacecraft demonstrator (called V201). A series of increasingly complex ground subsystem tests were completed, and eight successful high-altitude drop tests were achieved to prove the design concept. In this program, an unprecedented amount of commercial-off-the-shelf technology was utilized in this first crewed spacecraft NASA has built since the Shuttle program. Unfortunately, in 2002 the program was canceled due to changing Agency priorities. The vehicle was 80% complete and the program was shut down in such a manner as to preserve design, development, test and engineering data. This paper describes the X-38 V201 fault-tolerant avionics system. Based on Draper Laboratory's Byzantine-resilient fault-tolerant parallel processing system and their "network element" hardware, each flight computer exchanges information on a strict timescale to process input data, compare results, and issue voted vehicle output commands. Major accomplishments achieved in this development include: (i) a space qualified two-fault tolerant design using mostly COTS (hardware and operating system); (ii) a single event upset tolerant network element board, (iii) on-the-fly recovery of a failed processor; (iv) use of synched cache; (v) realignment of memory to bring back a failed channel; (vi) flight code automatically generated from the master measurement list; and (vii) built in-house by a team of civil servants and support contractors. This paper will present an overview of the avionics system and the hardware implementation, as well as the system software and vehicle command & telemetry functions. Potential improvements and lessons learned on this program are also discussed.

Kouba,Coy↗

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto- Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner-TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders.

Plattsmier, George↗

Autonomous Real Time Requirements Tracing

One of the more challenging aspects of software development is the ability to verify and validate the functional software requirements dictated by the Software Requirements Specification (SRS) and the Software Detail Design (SDD). Insuring the software has achieved the intended requirements is the responsibility of the Software Quality team and the Software Test team. The utilization of Timeliner-TLX(sup TM) Auto-Procedures for relocating ground operations positions to ISS automated on-board operations has begun the transition that would be required for manned deep space missions with minimal crew requirements. This transition also moves the auto-procedures from the procedure realm into the flight software arena and as such the operational requirements and testing will be more structured and rigorous. The autoprocedures would be required to meet NASA software standards as specified in the Software Safety Standard (NASASTD- 8719), the Software Engineering Requirements (NPR 7150), the Software Assurance Standard (NASA-STD-8739) and also the Human Rating Requirements (NPR-8705). The Autonomous Fluid Transfer System (AFTS) test-bed utilizes the Timeliner-TLX(sup TM) Language for development of autonomous command and control software. The Timeliner- TLX(sup TM) system has the unique feature of providing the current line of the statement in execution during real-time execution of the software. The feature of execution line number internal reporting unlocks the capability of monitoring the execution autonomously by use of a companion Timeliner-TLX(sup TM) sequence as the line number reporting is embedded inside the Timeliner-TLX(sup TM) execution engine. This negates I/O processing of this type data as the line number status of executing sequences is built-in as a function reference. This paper will outline the design and capabilities of the AFTS Autonomous Requirements Tracker, which traces and logs SRS requirements as they are being met during real-time execution of the targeted system. It is envisioned that real time requirements tracing will greatly assist the movement of autoprocedures to flight software enhancing the software assurance of auto-procedures and also their acceptance as reliable commanders

Plattsmier, George I.↗

Smashing the Stovepipe: Leveraging the GMSEC Open Architecture and Advanced IT Automation to Rapidly Prototype, Develop and Deploy Next-Generation Multi-Mission Ground Systems

Satellite/Payload Ground Systems - Typically highly-customized to a specific mission's use cases - Utilize hundreds (or thousands!) of specialized point-to-point interfaces for data flows / file transfers Documentation and tracking of these complex interfaces requires extensive time to develop and extremely high staffing costs Implementation and testing of these interfaces are even more cost-prohibitive, and documentation often lags behind implementation resulting in inconsistencies down the road With expanding threat vectors, IT Security, Information Assurance and Operational Security have become key Ground System architecture drivers New Federal security-related directives are generated on a daily basis, imposing new requirements on current / existing ground systems - These mandated activities and data calls typically carry little or no additional funding for implementation As a result, Ground System Sustaining Engineering groups and Information Technology staff continually struggle to keep up with the rolling tide of security Advancing security concerns and shrinking budgets are pushing these large stove-piped ground systems to begin sharing resources - I.e. Operational / SysAdmin staff, IT security baselines, architecture decisions or even networks / hosting infrastructure Refactoring these existing ground systems into multi-mission assets proves extremely challenging due to what is typically very tight coupling between legacy components As a result, many "Multi-Mission" ops. environments end up simply sharing compute resources and networks due to the difficulty of refactoring into true multi-mission systems Utilizing continuous integration / rapid system deployment technologies in conjunction with an open architecture messaging approach allows System Engineers and Architects to worry less about the low-level details of interfaces between components and configuration of systems GMSEC messaging is inherently designed to support multi-mission requirements, and allows components to aggregate data across multiple homogeneous or heterogeneous satellites or payloads - The highly-successful Goddard Science and Planetary Operations Control Center (SPOCC) utilizes GMSEC as the hub for it's automation and situational awareness capability Shifts focus towards getting GS to a final configuration-managed baseline, as well as multi-mission / big-picture capabilities that help increase situational awareness, promote cross-mission sharing and establish enhanced fleet management capabilities across all levels of the enterprise.

GMSEC↗

Strategy for Developing Technologies for Megawatt-class Nuclear Electric Propulsion Systems

In late fiscal year 2020, the Space Nuclear Propulsion (SNP) project began the process of formulating an investment strategy to support development of the technologies required for a high-power (megawatt-class) nuclear electric propulsion (NEP) system capable of performing human-scale missions. This activity was initiated concurrent with several high-level studies and assessments were either under way or had just concluded. Studies of human-scale Mars missions have been performed several times over the past two decades. One of the most recent studies examined opposition-class human Mars missions to occur in the late 2030s timeframe [1,2]. The mission architecture assumed a hybrid NEP/chem-propelled vehicle that used a high specific impulse (Isp) NEP-system and a liquid oxygen (LOx)-liquid methane high thrust chemical stage (two 110 kN (25 klbf) thrust, 365 s Isp engines) for maneuvers performed to enter and exit gravity wells. Trajectory analyses performed in this study showed that such a mission could be performed with 2-4 MWe directed into the electric propulsion system (operating for 20,000+ hours), with the large range representing different opposition-class Mars mission opportunities and permutations on the trajectory design, concept of operations, and technology choices. In 2020, the NASA Engineering and Safety Center (NESC) performed a study to evaluate the maturity of the different technologies required for nuclear propulsion systems [3]. The executive summary of this report provided the following top-level conclusions: • “The majority of critical technologies for… NEP/Chem… systems are relatively immature” • “TRLs [technology readiness levels] in the literature are often overestimated” • “The majority of critical technologies… for NEP/Chem… systems are at a relatively high level of advancement degree of difficulty (AD2 > 4) for maturation, requiring a dual development approach” • “The proper assessment of baseline TRL and AD2 values and the estimation of requirements and resources required for advancement have been consistent issues for NEP,” • “Non-advocate reviews should occur at the start of a technology program and at all key milestones.” In 2021, the National Academies of Science, Engineering, and Medicine (NASEM) issued a separate report [4] identifying the “primary technical and programmatic challenges, merits, and risks for maturing space nuclear propulsion technologies of interest to a future human Mars exploration mission.” That work contained several important findings, including: • “Developing a MWe-class NEP system for the baseline mission would require increasing power by orders of magnitude relative to NEP system flight- or ground-based technology demonstrations completed to date.” • “Subscale in-space flight testing of NEP systems cannot address many of the risks and potential failure modes associated with the baseline mission NEP system. With sufficient M&S [modeling & simulation] and ground testing, including modular subsystem tests at full scale and power, flight qualification requirements can be met by the cargo missions that will precede the first crewed mission to Mars. Fully integrated ground testing may not be required.” • “As a result of low and intermittent investment over the past several decades, it is unclear if even an aggressive program would be able to develop an NEP system capable of executing the baseline mission in 2039.” These efforts motivated the SNP project to investigate the technologies available for a megawatt-class high power nuclear electric propulsion system. That system is illustrated schematically in Figure 1 and is comprised of five separate top-level critical technology elements (CTEs). 1. Nuclear Reactor – Thermal power source for the system, utilizing high-assay low enriched uranium (HALEU) as the nuclear fuel. Reactor radiation shielding is also included in this CTE. 2. Power Conversion – Operates as a thermodynamic cycle, accepting nuclear reactor thermal power as an input and converting it to mechanical power. 3. Power Management and Distribution (PMAD) – Accepts as an input mechanical power from the power conversion system, which is used to generate electrical power. The PMAD system also distributes the generated electrical power to all other parts of the spacecraft, including the high-power EP system. The PMAD system may also perform duties such as isolation, fault detection, and power transformation/rectification for different spacecraft systems, including the thrusters. 4. Electric Propulsion (EP) – Accepts as an input electrical power, which is used to accelerate a propellant to high speeds to produce thrust. This system includes the power processing unit (PPU), which converts the power it receives to the correct current and voltage required by the thrusters, and the propellant storage and feed systems, which contain and meter the flow of propellant to the thrusters. 5. Thermal Management (Radiators/Heat Rejection) – The cold side of the thermodynamic power conversion cycle, accepts thermal power from the power conversion system and radiatively rejects that heat to space. In this paper, we describe the SNP project formulation and investment strategy that aims to accomplish the research and development required to advance the technology readiness for each CTE. The strategy relies heavily upon experimental testing supported by modeling and simulation to yield realistic assessments of the technologies, which in turn will be used to inform future NEP system-level design decisions and any potential technology downselects.

Kurt A Polzin↗

Soil mechanics surface sampler - Lunar surface test and results

After the success of Surveyor I in meeting the objectives of the engineering flight series, selection from among candidate experiments led to the inclusion of the Soil Mechanics Surface Sampler (SMSS) on the payload. Though originally planned for later Surveyors, the SMSS design was modified to fit the reduced telemetry and commanding capability of the earlier spacecraft. These modifications included removal of the strain-, acceleration-, and position-measuring systems originally planned, and incorporation of a means for measuring current drawn by the motors during operation. A description of the modified device, its performance on Surveyor III, and some conclusions regarding the lunar surface material drawn from the experiment are presented.

Ground test↗

Engineering study for pallet adapting the Apollo laser altimeter and photographic camera system for the Lidar Test Experiment on orbital flight tests 2 and 4

A Laser Altimeter and Mapping Camera System was included in the Apollo Lunar Orbital Experiment Missions. The backup system, never used in the Apollo Program, is available for use in the Lidar Test Experiments on the STS Orbital Flight Tests 2 and 4. Studies were performed to assess the problem associated with installation and operation of the Mapping Camera System in the STS. They were conducted on the photographic capabilities of the Mapping Camera System, its mechanical and electrical interface with the STS, documentation, operation and survivability in the expected environments, ground support equipment, test and field support.

Kuebert, E. J.↗

Modifying a Commercial Centrifuge to Reduce Electromagnetic Interference and Evaluating Functionality of Ultrasound Equipment

The Project Management and Engineering Branch (SF4) supports the Human Health and Performance Directorate (HH&P) and is responsible for developing and supporting human systems hardware for the International Space Station (ISS). When a principal investigator's (PI) medical research project on the ISS is accepted, SF4 develops the necessary hardware and software to transport to the ISS. The two projects I primarily worked on were the centrifuge and ultrasound projects. Centrifuge: One concern with spacecraft such as the ISS is electromagnetic interference (EMI) from onboard equipment, typically from radio waves (frequencies of ~3 kHz to ~300 GHz), which can negatively affect nearby circuitry. Standard commercial centrifuges produce EMI above safety limits, so my task was to help reduce EMI production from this equipment. Two centrifuges were tested: one unmodified as a control and one modified. To reduce EMI below safety limits, one centrifuge was modified to become a Faraday shield, in which significant electrical contact was made between all regions of the centrifuge housing. This included removing non-conductive paint, applying conductive fabric to the lid and foam sealer, adding a 10,000 μF decoupling capacitor across the power supply, and adding copper adhesive-mount gaskets to the housing interior. EMI testing of both centrifuges was performed in the EMI/EMC Control Test and Measurement Facility. EMI for both centrifuges was below safety limits for frequencies between 10 MHz and 15 GHz (pass); however, between 14 kHz and 10 MHz, EMI for the unmodified centrifuge exceeded safety limits (fail) as expected. Alternatively, for the modified centrifuge with the Faraday shield, EMI was below the safely limit of 55 dBμV/m for electromagnetic frequencies between 14 kHz and 10 MHz. This result indicates our modifications were successful. The successful EMI test allowed us to communicate with the vendor what modifications they needed to make to their commercial unit to meet our specifications and to understand what needs to be done in lab to the new centrifuge. Our modifications will provide a standard for readying centrifuges for future missions. Once the new modified centrifuge arrives by the vendor, it will need to undergo EMI testing again for validation. The centrifuge is also in the process of compatibility testing with a custom stowage drawer, which is an ongoing project in SF4. Both of these items will be payloads on future missions to the ISS for various research purposes. Ultrasound: ISS currently has an onboard ultrasound (Ultrasound 2 system) for research and medical purposes. Every piece of medical flight hardware has an equivalent ground-unit so instrumentation can be routinely evaluated and transported to the ISS if necessary. The ground-unit ultrasound equipment must be evaluated every six months using a task performance sheet (TPS). A TPS is a document, written by the appropriate scientists and engineers, which describes how to run equipment and is written in such a way that astronauts with unspecialized training can follow the tasks. I was responsible for performing six TPSs on a combination of three ultrasounds and two video power converters (VPCs). Performing a TPS involves checking out and computationally documenting each piece of equipment removed from storage locations, setting up hardware and software, performing tasks to verify functionality, returning equipment, and logging items back into the computerized system. My work revealed all ground-unit ultrasounds were functioning properly. Because of proper function, a discrepancy report (DR) did not have to be opened. The TPS was then passed along to the Quality Engineering (QE) for review and ultimately given to Quality Assurance (QA). Other projects: In addition to my main projects, I participated in other tasks including troubleshooting an EEG headband, volunteering for an ultrasound training research study, and conformal coating printed circuit boards. My internship at SF4 has helped me understand how space systems hardware development for the ISS fits into NASA's mission and vision.

Greening, Gage J.↗