Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Troubleshooting”

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 253 records · Page 14

Particle Streak Velocimetry of Supersonic Nozzle Flows

A novel velocimetry technique to probe the exhaust flow of a laboratory scale combustor is being developed. The technique combines the advantages of standard particle velocimetry techniques and the ultra-fast imaging capabilities of a streak camera to probe high speed flows near continuously with improved spatial and velocity resolution. This "Particle Streak Velocimetry" technique tracks laser illuminated seed particles at up to 236 picosecond temporal resolution allowing time-resolved measurement of one-dimensional flows exceeding 2000 m/s as are found in rocket nozzles and many other applications. Developmental tests with cold nitrogen have been performed to validate and troubleshoot the technique with supersonic flows of much lower velocity and without background noise due to combusting flow. Flow velocities on the order of 500 m/s have been probed with titanium dioxide particles and a continuous-wave laser diode. Single frame images containing multiple streaks are analyzed to find the average slope of all incident particles corresponding to the centerline axial flow velocity. Long term objectives for these tests are correlation of specific impulse to theoretical combustion predictions and direct comparisons between candidate green fuels and the industry standard, monomethylhydrazine, each tested under identical conditions.

Willits, J. D.↗

Designing for Reliability and Robustness

Long duration spaceflight has a negative effect on the human body, and exercise countermeasures are used on-board the International Space Station (ISS) to minimize bone and muscle loss, combatting these effects. Given the importance of these hardware systems to the health of the crew, this equipment must continue to be readily available. Designing spaceflight exercise hardware to meet high reliability and availability standards has proven to be challenging throughout the time the crewmembers have been living on ISS beginning in 2000. Furthermore, restoring operational capability after a failure is clearly time-critical, but can be problematic given the challenges of troubleshooting the problem from 220 miles away. Several best-practices have been leveraged in seeking to maximize availability of these exercise systems, including designing for robustness, implementing diagnostic instrumentation, relying on user feedback, and providing ample maintenance and sparing. These factors have enhanced the reliability of hardware systems, and therefore have contributed to keeping the crewmembers healthy upon return to Earth. This paper will review the failure history for three spaceflight exercise countermeasure systems identifying lessons learned that can help improve future systems. Specifically, the Treadmill with Vibration Isolation and Stabilization System (TVIS), Cycle Ergometer with Vibration Isolation and Stabilization System (CEVIS), and the Advanced Resistive Exercise Device (ARED) will be reviewed, analyzed, and conclusions identified so as to provide guidance for improving future exercise hardware designs. These lessons learned, paired with thorough testing, offer a path towards reduced system down-time.

Svetlik, Randall G.↗

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.↗

Monitoring of the Atmosphere on the International Space Station with the Air Quality Monitor

During the early years of human spaceflight, short duration missions allowed for monitoring of the spacecraft environment to be performed via archival sampling, in which samples were returned to Earth for analysis. With the construction of the International Space Station (ISS) and the accompanying extended mission durations, the need for enhanced, real-time monitors became apparent. The Volatile Organic Analyzer (VOA) operated on ISS for 7 years, where it assessed trace volatile organic compounds in the cabin air. The large and fixed-position VOA was eventually replaced with the smaller Air Quality Monitor (AQM). Since March 2013, the atmosphere of the U.S. Operating Segment (USOS) has been monitored in near real-time by a pair of AQMs. These devices consist of a gas chromatograph (GC) coupled with a differential mobility spectrometer (DMS) and currently target detection list of 22 compounds. These targets are of importance to both crew health and the Environmental Control and Life Support Systems (ECLSS) on ISS. Data is collected autonomously every 73 hours, though the units can be controlled remotely from mission control to collect data more frequently during contingency or troubleshooting operations. Due to a nominal three-year lifetime on-orbit, the initial units were replaced in February 2016. This paper will focus on the preparation and use of the AQMs over the past several years. A description of the technical aspects of the AQM will be followed by lessons learned from the deployment and operation of the first set of AQMs. These lessons were used to improve the already-excellent performance of the instruments prior to deployment of the replacement units. Data trending over the past several years of operation on ISS will also be discussed, including data obtained during a survey of the USOS modules. Finally, a description of AQM use for contingency and investigative studies will be presented.

Wallace William T.↗

Development of a 13 kW Hall Thruster Propulsion System Performance Model for AEPS

The Advanced Electric Propulsion System (AEPS) program will develop a flight 13kW Hall thruster propulsion system based on NASA's HERMeS thruster. The AEPS system includes the Hall Thruster, the Power Processing Unit (PPU) and the Xenon Flow Controller (XFC). These three primary components must operate together to ensure that the system generates the required combinations of thrust and specific impulse at the required system efficiencies for the desired system lifetime. At the highest level, the AEPS system will be integrated into the spacecraft and will receive power, propellant, and commands from the spacecraft. Power and propellant flow rates will be determined by the throttle set points commanded by the spacecraft. Within the system, the major control loop is between the mass flow rate and thruster current, with time-dependencies required to handle all expected transients, and additional, much slower interactions between the thruster and cathode temperatures, flow controller and PPU. The internal system interactions generally occur on shorter timescales than the spacecraft interactions, though certain failure modes may require rapid responses from the spacecraft. The AEPS system performance model is designed to account for all these interactions in a way that allows evaluation of the sensitivity of the system to expected changes over the planned mission as well as to assess the impacts of normal component and assembly variability during the production phase of the program. This effort describes the plan for the system performance model development, correlation to NASA test data, and how the model will be used to evaluate the critical internal and external interactions. The results will ensure the component requirements do not unnecessarily drive the system cost or overly constrain the development program. Finally, the model will be available to quickly troubleshoot any future unforeseen development challenges.

Stanley, Steven↗

Position Paper - pFLogger: The Parallel Fortran Logging framework for HPC Applications

In the context of high performance computing (HPC), software investments in support of text-based diagnostics, which monitor a running application, are typically limited compared to those for other types of IO. Examples of such diagnostics include reiteration of configuration parameters, progress indicators, simple metrics (e.g., mass conservation, convergence of solvers, etc.), and timers. To some degree, this difference in priority is justifiable as other forms of output are the primary products of a scientific model and, due to their large data volume, much more likely to be a significant performance concern. In contrast, text-based diagnostic content is generally not shared beyond the individual or group running an application and is most often used to troubleshoot when something goes wrong. We suggest that a more systematic approach enabled by a logging facility (or logger) similar to those routinely used by many communities would provide significant value to complex scientific applications. In the context of high-performance computing, an appropriate logger would provide specialized support for distributed and shared-memory parallelism and have low performance overhead. In this paper, we present our prototype implementation of pFlogger a parallel Fortran-based logging framework, and assess its suitability for use in a complex scientific application.

Fortran↗

POSITION PAPER - pFLogger: The Parallel Fortran Logging Framework for HPC Applications

In the context of high performance computing (HPC), software investments in support of text-based diagnostics, which monitor a running application, are typically limited compared to those for other types of IO. Examples of such diagnostics include reiteration of configuration parameters, progress indicators, simple metrics (e.g., mass conservation, convergence of solvers, etc.), and timers. To some degree, this difference in priority is justifiable as other forms of output are the primary products of a scientific model and, due to their large data volume, much more likely to be a significant performance concern. In contrast, text-based diagnostic content is generally not shared beyond the individual or group running an application and is most often used to troubleshoot when something goes wrong. We suggest that a more systematic approach enabled by a logging facility (or 'logger') similar to those routinely used by many communities would provide significant value to complex scientific applications. In the context of high-performance computing, an appropriate logger would provide specialized support for distributed and shared-memory parallelism and have low performance overhead. In this paper, we present our prototype implementation of pFlogger - a parallel Fortran-based logging framework, and assess its suitability for use in a complex scientific application.

Clune, Thomas L.↗

Implementing Reliability Centered Maintenance (RCM) with State of the Art PT&I Technologies

Building on the work that was started two decades ago, Jacobs Space Operations Group has utilized state of the art PTI technologies to assess the current condition of the assets they manage under the Test and Operations Support Contract (TOSC). Specifically, the Asset Management department leveraged the benefits of ultrasound technology to quantify a motor issue in the Liquid Oxygen Storage Area, and troubleshoot the sources prior to loading the tank to perform Verification and Validation (VV) activities. This technology was efficient, easy to implement, and provided system engineers with data on a possible source of the problem. In situations where legacy motors are exhibiting unexpected noises, it may seem easier to remove and refurbish the motor and replace the bearings because that solution resolves most of the common causes of the noise. However, that solution would have involved additional spending and may not have solved issues stemming from the foundation, if those existed. By utilizing the ultrasound equipment provided by UE Systems, the sound profiles allowed Jacobs TOSC team to determine that the issue resembled a faulty bearing. After replacing the bearing, the unexpected noise ceased.

Reliability Centered Maintenance↗

pFlogger: The Parallel Fortran Logging Utility

In the context of high performance computing (HPC), software investments in support of text-based diagnostics, which monitor a running application, are typically limited compared to those for other types of IO. Examples of such diagnostics include reiteration of configuration parameters, progress indicators, simple metrics (e.g., mass conservation, convergence of solvers, etc.), and timers. To some degree, this difference in priority is justifiable as other forms of output are the primary products of a scientific model and, due to their large data volume, much more likely to be a significant performance concern. In contrast, text-based diagnostic content is generally not shared beyond the individual or group running an application and is most often used to troubleshoot when something goes wrong. We suggest that a more systematic approach enabled by a logging facility (or 'logger)' similar to those routinely used by many communities would provide significant value to complex scientific applications. In the context of high-performance computing, an appropriate logger would provide specialized support for distributed and shared-memory parallelism and have low performance overhead. In this paper, we present our prototype implementation of pFlogger - a parallel Fortran-based logging framework, and assess its suitability for use in a complex scientific application.

Clune, Tom↗

Flight Systems Integration & Test: Lessons Learned for Future Success

This paper offers a comprehensive view of flight system integration and test (I&T) lessons learned related to mishaps and close calls, focusing on what can be done to improve the I&T process to avoid recurrence. Specific areas within the realm of I&T that are covered in this paper include: I&T team communication and training; design of flight and ground systems for I&T; planning and scheduling; configuration management and process documentation; ground support equipment and tools; cleanrooms and contamination; mechanical integration, handling, and deployments; electrical integration and electrostatic discharge; functional testing and troubleshooting; environmental testing and facilities; and launch site operations. To illustrate "real-world" lessons learned for I&T, examples from throughout the history of the U.S. space program are presented. Also presented are some best practices for I&T that can help mitigate mishaps and close calls on the ground or during flight.

Integration & Test↗

Streamlining Ground Station Network Compatibility Test for Small Satellites

A team of eight subject matter experts at NASA Goddard Space Flight Center (GSFC) completed a Lean Six Sigma project to identify process improvements for the compatibility test process for small satellites planning to use the NASA Near Earth Network (NEN). Ground station network compatibility testing is designed to reduce the risk to missions by resolving issues between the spacecraft's flight communication and navigation components and the ground systems prior to launch. Compatibility testing, which consists of a series of tests performed over a period of months and documented in reports, is an important step meant to prevent post-launch anomalies that could lead to expensive troubleshooting or mission failure. Compared to traditional missions, small satellite missions typically have a smaller budget and compressed schedules, which can result in small satellite projects' willingness to accept the risk associated with less comprehensive compatibility testing. Optimization and or refinement of the compatibility test process for small satellite missions could alleviate some of the pressures inherent with these factors. The goal of the Lean Six Sigma project was to develop alternative scalable methods of compatibility testing for small satellites. The Lean Six Sigma approach and the results of the project are reviewed in this paper.

Streamlining↗

The Evolution of Payload Data Capabilities on the Commercial Visiting Vehicles that Service the International Space Station

For over 10 years, NASA has been working with U.S.-based commercial companies to support the design, development, and operations of new commercial space vehicles. The purpose of these vehicles is to provide cargo and crew transportation services to the International Space Station (ISS) and to stimulate the commercial space transportation industry to Low-Earth Orbit (LEO). Along with the ability to provide a couple tons of cargo to the ISS each mission, the commercial visiting vehicles also provide the ability to transfer NASA payloads to and from the ISS in an active, powered state. To take advantage of this capability, NASA requirements for the data services that payloads need while they are integrated into the visiting vehicles have grown with each set of commercial contracts. Today, NASA desires for payload data services encompass a variety of capabilities including payload health and status (H&S) telemetry monitoring, visiting vehicle environment data monitoring, and payload commanding. The intent of these capabilities is to provide payload developers with situational awareness and the ability to quickly diagnose any problems with payload operations prior to vehicle docking or post-landing to support immediate troubleshooting response. As new requirements for payload data services have emerged over the years, the ISS Payload Operations Integration Center (POIC) at the NASA Marshall Space Flight Center (MSFC) has established ground segment interfaces to the visiting vehicle control centers to enable payload developers to use these services. Many technical and programmatic challenges have been faced while establishing these interfaces. The most significant challenge faced has been in finding the right balance amongst providing interfaces to payloads that are compatible with the ISS so that payload hardware or software changes are not necessary to ensure compatibility with the visiting vehicles; keeping POIC ground system development costs low by standardizing implementation approaches across commercial vehicle partners; and fostering commercialization through supporting vendor-unique implementations that are commercially economical. This paper will first detail the data services that will be available to payload users under each commercial visiting vehicle contract. Secondly, this paper will offer discussion of the most significant technical and programmatic challenges faced to-date in offering these new data services to payload developers.

Wiggins, Lindsay M.↗

Adaptive Problem Solving and Mitigation

This presentation examines how problem solving was done on the NEEMO 22 Mission and whether human autonomy teaming would be able to assist in the type of troubleshooting that was conducted by Mission Control.

human autonomy↗

Vegetable Production Systems Component Tests

As long-term spaceflight missions become ever more imminent, astronaut nutrition and diet require further investigation and development. Dehydrated or stabilized food sources are currently used for spaceflight, but growing fresh produce aboard spacecraft can potentially supplement the astronauts’ diets. Further, having astronauts work with plants while in space can provide psychological benefits by serving as a tangible passage of time and representing a living component aboard an otherwise mechanical environment. As spaceflight duration will lengthen as missions head back to the Moon and to Mars, having the ability and knowledge to grow fresh produce will become even more vital. The following experiments were conducted in the late summer and fall of 2018. The purpose of these studies were to examine potential off-gas from a system component that could potentially inhibit plant germination, optimizing lighting methods and protocol for mizuna production, determining a fertilizer method that best promotes healthy mizuna yields, and troubleshooting tomato production for the next generation of the Vegetable Production System.

international space station↗

Labor Estimation and Trending in an Operations Environment

Accurate cost estimation for future work is important for ensuring that organizations have the personnel and resources needed to complete a task successfully. Operations support in particular provides additional challenges for estimating cost. Unlike manufacturing-based work, it may be difficult to derive a "cost per product," and projects that appear to be similar may have drastically different underlying assumptions. In addition, for critical operations, a certain level of adaptability to changing circumstances is expected. Responding to contingencies or anomalies requires additional support and troubleshooting, and could result in increases to project cost. Labor estimation is one of the most important inputs for estimating the cost of an operations-based project, especially in a pre-established facility. Various methods are needed to develop reliable estimates. These methods include a bottom-up summarization of known or expected work items, and a top-down estimate generated by trending and scaling actual labor from past analogous operations support.

Laing, Jason↗

The International Space Station (ISS) Port 1 (P1) External Active Thermal Control System (EATCS) Ammonia Leak

From 2011 to 2017, the crew onboard the International Space Station (ISS) was at risk of dire consequences due to an external ammonia leak. Ammonia is used in the External Active Thermal Control System (EATCS) to cool the pressurized modules and external electrical systems. Engineers at NASA's Johnson Space Center (JSC) initially detected the leak in one of two cooling loops by monitoring the system ammonia inventory decay over time. White flakes seen on High Definition (HD) cameras were also thought to be associated with the leakage but not confirmed. Initially, the leak was small enough that the ammonia inventory and system operations were not in jeopardy. However, the leak began to accelerate to the point where troubleshooting and corrective action were vital to the sustainability of the ISS. Therefore, it became imperative that the leak be located and repaired for ISS operations to continue. No tools were readily available on the ISS to locate such a leak when it was initially detected, however NASA engineers were already in the process of developing a new device for this purpose called the Robotic External Leak Locator (RELL). The RELL is a robotic instrument package with a mass spectrometer and an ion pressure gauge. Initial checkout operations with RELL happened to coincide with the increasing leak, and ammonia vapors were measured around the P1 EATCS Radiator #3 flexible jumper hoses. The leak stopped after the radiator and its flexible hoses were remotely isolated from the loop and the ammonia from the isolated segment was vented to space. Astronauts conducted a spacewalk that successfully removed the hoses, which were returned to ground for further investigation. The purpose of this paper is to review the leak detection and isolation efforts, investigation results, lessons learned and the recovery plan.

Cowan, Darnell T.↗

The International Space Station (ISS) Port 1 (P1) External Active Thermal Control System (EATCS) Ammonia Leak

From 2011 to 2017, the crew onboard the International Space Station (ISS) was at risk of dire consequences due to an external ammonia leak. Ammonia is used in the External Active Thermal Control System (EATCS) to cool the pressurized modules and external electrical systems. Engineers at NASA's Johnson Space Center (JSC) initially detected the leak in one of two cooling loops by monitoring the system ammonia inventory decay over time. White flakes seen on High Definition (HD) cameras were also thought to be associated with the leakage but not confirmed. Initially, the leak was small enough that the ammonia inventory and system operations were not in jeopardy. However, the leak began to accelerate to the point where troubleshooting and corrective action were vital to the sustainability of the ISS. Therefore, it became imperative that the leak be located and repaired for ISS operations to continue. No tools were readily available on the ISS to locate such a leak when it was initially detected, however NASA engineers were already in the process of developing a new device for this purpose called the Robotic External Leak Locator (RELL). The RELL is a robotic instrument package with a mass spectrometer and an ion pressure gauge. Initial checkout operations with RELL happened to coincide with the increasing leak, and ammonia vapors were measured around the P1 EATCS Radiator #3 flexible jumper hoses. The leak stopped after the radiator and its flexible hoses were remotely isolated from the loop and the ammonia from the isolated segment was vented to space. Astronauts conducted a spacewalk that successfully removed the hoses, which were returned to ground for further investigation. The purpose of this paper is to review the leak detection and isolation efforts, investigation results, lessons learned and the recovery plan.

Cowan, Darnell T.↗

The RELAMPAGO Lightning Mapping Array: Preliminary Scientific Results and Application to GLM Calibration and Validation

During November 2018 through April 2019, an 11-station NASA lightning mapping array (LMA) was installed in the Cordoba region of Argentina, in support of GOES-16 Geostationary Lightning Mapper (GLM) calibration and validation, as well as the Remote sensing of Electrification, Lightning, And Mesoscale/microscale Processes with Adaptive Ground Observations (RELAMPAGO) field campaign. This region of Argentina is well known for frequent, intense thunderstorms and severe weather. The LMA was monitored remotely via the Internet throughout its deployment, but due to bandwidth limitations no real-time data were available. Custom GOES-16 imagery provided by NASA SPoRT assisted with monitoring of thunderstorm cases. Occasional site visits were done to obtain data disks, perform routine maintenance, and troubleshoot problems. During the deployment the network captured lightning in a variety of storm modes, including ordinary and severe multicells, supercells, and mesoscale convective systems. Many examples of normal-polarity thunderstorms, as well as a few examples of anomalously charged thunderstorms, were observed. Long (100+ km) horizontally stratified lightning flashes, as well as lightning in overshooting tops, also were frequently observed. Supporting research radar observations were available through January 2019, with operational radar coverage available after that time. Some cases featured supporting ABI meso scanning. This presentation will report on the LMA deployment in context with the RELAMPAGO field campaign, show results from some representative case studies, and will provide initial comparisons to GLM observations.

Lang, Timothy J.↗