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 109 records · Page 6
All sourcesNASA NTRSDOE OSTI
NASA NTRS1997

STS-85 Day 08 Highlights

On this eighth day of the STS-85 mission, the flight crew, Cmdr. Curtis L. Brown, Jr., Pilot Kent V. Rominger, Payload Cmdr. N. Jan Davis (Ph.D.), Mission Specialists Robert L. Curbeam, Jr. and Stephen K. Robinson (Ph.D.), and Payload Specialist Bjarni V. Tryggvason entered the final portion of its flight. The new Mir 24 crew of Commander Anatoly Solovyev and Flight Engineer Pavel Vinogradov, who arrived on the station the same day Discovery was launched, bid farewell to Mir 23 Commander Vasily Tsibliev and Flight Engineer Alexander Lazutkin who are returning home after 185 days in space. The Soyuz vehicle carrying the Mir 23 crew home undocked from the station. Robinson again used the Southwest Ultraviolet Imaging System (SWUIS), a 7-inch imaging telescope that is pointed out of the orbiter's middeck hatch window, to observe the Hale-Bopp comet. Curbeam continued his work with the Bioreactor Demonstration System designed to perform cell biology experiments under controlled conditions. Tryggvason spent part of his time troubleshooting a computer hard drive system that supports the Microgravity Vibration Isolation Mount experiment.

Source record↗
NASA NTRS1998

Integrated Advanced Microwave Sounding Unit-A (AMSU-A). Performance Verification Report: METSAT Phase Locked Oscillator Assembly, P/N 1334360-1, S/N's F03 and F04

Two Flight Model AMSU-A Phase Locked Oscillators (P/N 1348360-1, S/Ns F03 and F04) have been tested per AES Test Procedure AE-26758. The tests included vibration testing, thermal cycle testing, AM/FM Noise testing, and full functional testing. EMI/REO 2 Testing was not performed. (See test data for S/N F01). Both AMSU-A Phase Locked Oscillators satisfactorily passed all performance requirements of the AE-26633 Product specification. During thermal cycling of PLO serial number F03, the oven and data logger momentarily lost power, including a loss of data. The unit did not experience any thermal stress. TAR 003134 describes the corrective action. Prior to testing PLO serial number FO4, power was applied to the unit. (+15v,-15v) the unit did not display the proper phase lock. Upon test equipment check out a connector was found to be defective. TAR 003133 describes the corrective action. After completion of testing of PLO serial number F04 was installed into Receiver Assembly F02. Upon testing F02 Receiver Assembly the unit was found not to phase lock at ambient temperature. Removal of PLO Assembly F04 was required. R2 was the real issue. Solithane was secondary. Troubleshooting revealed excessive solithane on inner PLL Assembly cover inhibiting optimum grounding. Also, R2 was reselected which increased the lock range from -30 C to +60 C. TAR 002737 describes the corrective action.

Pines, D.↗
NASA NTRS1999

STS-96 FD Highlights and Crew Activities Report: Flight Day 05

On this fifth day of the STS-96 Discovery mission, the flight crew, Commander Kent V. Rominger, Pilot Rick D. Husband, and Mission Specialists Ellen Ochoa, Tamara E. Jernigan, Daniel T. Barry, Julie Payette, and Valery Ivanovich Tokarev are seen performing logistics transfer activities within the Discovery/International Space Station orbiting complex. The crew transfers supplies, equipment, and water. Payette and Tokarev perform maintenance activities on the storage batteries in the Zarya module. Barry and Tokarev install acoustic insulation around some of the fans inside Zarya. Jernigan and Husband install shelving in 2 soft stowage racks. Husband and Barry troubleshoot and perform maintenance activities on the Early Communications System. At the end of the workday, Rominger, Jernigan, and Barry discussed the progress of the mission with NBC's "Today," CBS "This Morning," and CNN.

Source record↗
NASA NTRS1999

Virtual Manufacturing Techniques Designed and Applied to Manufacturing Activities in the Manufacturing Integration and Technology Branch

One of the identified goals of EM3 is to implement virtual manufacturing by the time the year 2000 has ended. To realize this goal of a true virtual manufacturing enterprise the initial development of a machinability database and the infrastructure must be completed. This will consist of the containment of the existing EM-NET problems and developing machine, tooling, and common materials databases. To integrate the virtual manufacturing enterprise with normal day to day operations the development of a parallel virtual manufacturing machinability database, virtual manufacturing database, virtual manufacturing paradigm, implementation/integration procedure, and testable verification models must be constructed. Common and virtual machinability databases will include the four distinct areas of machine tools, available tooling, common machine tool loads, and a materials database. The machine tools database will include the machine envelope, special machine attachments, tooling capacity, location within NASA-JSC or with a contractor, and availability/scheduling. The tooling database will include available standard tooling, custom in-house tooling, tool properties, and availability. The common materials database will include materials thickness ranges, strengths, types, and their availability. The virtual manufacturing databases will consist of virtual machines and virtual tooling directly related to the common and machinability databases. The items to be completed are the design and construction of the machinability databases, virtual manufacturing paradigm for NASA-JSC, implementation timeline, VNC model of one bridge mill and troubleshoot existing software and hardware problems with EN4NET. The final step of this virtual manufacturing project will be to integrate other production sites into the databases bringing JSC's EM3 into a position of becoming a clearing house for NASA's digital manufacturing needs creating a true virtual manufacturing enterprise.

Shearrow, Charles A.↗
NASA NTRS1999

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

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

Shell, Elaine M.↗
NASA NTRS2000

STS-99 Flight Day Highlights 03 and Crew Activities Report

Live footage shows the STS-99's Blue Team Pilot Dominic L. Pudwill Gorie, and Mission Specialist Mamoru Mohri speaking with Dr. Bob Ballard and fielding questions from Fox News Network. During the interviews Janet E. Voss oversees the mapping activities. The Blue Team is also seen speaking with the Launch Control Center (LCC) troubleshooting a problem with a small nitrogen thruster mounted at the tip of the radar's outboard antenna.

Source record↗
NASA NTRS2000

STS-99 Crew Activities Report / Flight Day 06 Highlights

The primary objective of the STS-99 mission was to complete high resolution mapping of large sections of the Earth's surface using the Shuttle Radar Topography Mission (STRM), a specially modified radar system. This radar system produced unrivaled 3-D images of the Earth's Surface.. The mission was launched at 12:31 on February 11, 2000 onboard the space shuttle Endeavour. The mission was led by Commander Kevin Kregel. The crew was Pilot Dominic L. Pudwill Gorie and Mission Specialists Janet L. Kavandi, Janice E. Voss, Mamoru Mohri, the National Space Development Agency (Japanese Space Agency) and Gerhard P. J. Thiele, from DARA (German Space Agency). This tape shows some of the activities on board the shuttle during day six of the mission. By the end of day six, the mission to map 32 million square miles of the Earth's surface was about 67.2 percent complete. On this video tape there is discussion about the attempts to conserve propellant, to allow for the completion of the planned mapping. There is discussion by Mamoru Mohri about the mission, and Gerhard Thiele answers questions from the German Press about the mission. New radar images from the SRTM of the Kamchatka Peninsula and northwestern Mongolia are shown. There are shots of Endeavour's 200-foot mast, which required troubleshooting due to a balky small thruster.

Source record↗
NASA NTRS1999

The Microgravity Demonstrator

The Demonstrator is a tool to create microgravity conditions in your classroom. A series of demonstrations is used to provide a dramatically visual, physical connection between free-fall and microgravity conditions and to understand why various types of experiments are performed under microgravity conditions. A wealth of back-round material on free-fall, microgravity, and micro-gravity sciences is available in two educational documents available through the NASA Teacher Resource Centers: Microgravity-Activity Guide for Science, Mathematics, and Technology Education, and The Mathematics of Microgravity. The remainder of this manual is divided into five sections. The first explains how to put the Microgravity Demonstrator together. The next section introduces the individual demonstrations and discusses the underlying physical science concepts. Following that are detailed steps for conducting each demonstration to make your use of the Demonstrator most effective. Next are some ideas on how to make your own Microgravity Demonstrator. The last section is a tips and troubleshooting guide for video connections and operations. If you have one of the NASA Microgravity Demonstrators, this entire manual should be useful. If you have a copy of the Microgravity Demonstrator Videotape and would like to use that as a teaching tool, the Demonstrations and Scientific Background section of this manual will give you insight into the science areas studied in microgravity.

Rogers, Melissa J. B.↗
NASA NTRS2001

Smarter Software For Enhanced Vehicle Health Monitoring and Inter-Planetary Exploration

The existing philosophy for space mission control was born in the early days of the space program when technology did not exist to put significant control responsibility onboard the spacecraft. NASA relied on a team of ground control experts to troubleshoot systems when problems occurred. As computing capability improved, more responsibility was handed over to the systems software. However, there is still a large contingent of both launch and flight controllers supporting each mission. New technology can update this philosophy to increase mission assurance and reduce the cost of inter-planetary exploration. The advent of model-based diagnosis and intelligent planning software enables spacecraft to handle most routine problems automatically and allocate resources in a flexible way to realize mission objectives. The manifests for recent missions include multiple subsystems and complex experiments. Spacecraft must operate at longer distances from earth where communications delays make earthbound command and control impractical. NASA's Ames Research Center (ARC) has demonstrated the utility of onboard diagnosis and planning with the Remote Agent experiment in 1999. KSC has pioneered model-based diagnosis and demonstrated its utility for ground support operations. KSC and ARC are cooperating in research to improve the state of the art of this technology. This paper highlights model-based reasoning applications for Moon and Mars missions including in-situ resource utilization and enhanced vehicle health monitoring.

Larson, William E.↗
NASA NTRS1994

Results From The First Interactive Scientific Expert System In Space

We describe recent work on automation and support of science experiments on the Space Shuttle. PI-in-a-Box, the first interactive expert system for scientific support, was flown onboard STS-58 in October 1993. It was designed to help astronauts perform better science in space by providing expert-level advice in real-time. The system provides help with 'technician' tasks such as data acquisition, data quality monitoring, and diagnostic, troubleshooting and repair. The system also performs 'expert' reasoning on the scientific model and experiment steps scheduling. It can make scheduling recommendations based on hardware status, time available, and agreement between predictions and flight data. The system was successfully deployed and used throughout the mission. Most of the 'technician' skills of the system were used with success. The scientific model study performed correctly, but we believe the results were not exploited by the astronauts because of Spacelab operational pressures. Also, portions of the system were designed around rigid schedule constraints that were essentially relaxed during the mission. This version was tailored to a specific vestibular experiment known as the 'rotating dome'. We are currently expanding our effort in various scientific (other life and microgravity sciences experiments) and technological directions (integrated telescience, astronaut science advisor, and autonomous control).

Groleau, Nicolas↗
NASA NTRS1994

Results from the First Interactive Scientific Expert System in Space

We describe recent work on automation and support of science experiments on the Space Shuttle. PI-in-a-Box, the first interactive expert system for scientific support, was flown onboard STS-58 in October 1993. It was designed to help astronauts perform better science in space by providing expert-level advice in real-time. The system provides help with "technician" tasks such as data acquisition, data quality monitoring, and diagnostic, troubleshooting and repair. The system also performs "expert" reasoning on the scientific model and experiment steps scheduling. It can make scheduling recommendations based on hardware status, time available, and agreement between predictions and flight data. The system was successfully deployed and used throughout the mission. Most of the "technician" skills of the system were used with success. The scientific model study performed correctly, but we believe the results were not exploited by the astronauts because of Spacelab operational pressures. Also, portions of the system were designed around rigid schedule constraints that were essentially relaxed during the mission. This version was tailored to a specific vestibular experiment known as the "rotating dome". We are currently expanding our effort in various scientific (other life and microgravity sciences experiments) and technological directions (integrated telescience, astronaut science advisor, and autonomous control).

Groleau, Nicolas↗
NASA NTRS2001

B and F Signal Conditioner Checkout Unit

ATK Thiokol Propulsion, Test Services uses B&F Signal Conditioning units to provide excitation power and shunt calibration information to the data recording systems. Gage measurements such as force, temperature, pressure, strain, etc. are recorded using this equipment. Approximately 2500 reusable instrumentation B&F Signal Conditioning units were purchased over an interval from 1978 to 1988 at a cost of around $1000 each. Through use and over time, the relay contacts on the signal conditioning mode cards have become corroded, resulting in excessive contact resistance. This causes inaccurate and inconsistent calibration data and could jeopardize the test results. These signal conditioning cards are needed for product testing for an estimated five more years, therefore, it is necessary to develop a solution to isolate the malfunctioning units for repair. The current screening method requires Test Area technicians to check cards manually, however the connections and measurements required for this process are inefficient and time consuming. To resolve this problem, funding was approved to design and build two B&F Signal Conditioner Checkout Units. Each unit will allow technicians to test relay contact resistance on signal conditioning mode cards before they are installed for data collection procedures. This tool will allow Test Area to resolve calibration accuracy problems and extend the life of the data acquisition equipment, as well as save troubleshooting time for the technicians.

Magleby, Alyssa↗
NASA NTRS2001

A Genuine TEAM Player

Qualtech Systems, Inc. developed a complete software system with capabilities of multisignal modeling, diagnostic analysis, run-time diagnostic operations, and intelligent interactive reasoners. Commercially available as the TEAMS (Testability Engineering and Maintenance System) tool set, the software can be used to reveal unanticipated system failures. The TEAMS software package is broken down into four companion tools: TEAMS-RT, TEAMATE, TEAMS-KB, and TEAMS-RDS. TEAMS-RT identifies good, bad, and suspect components in the system in real-time. It reports system health results from onboard tests, and detects and isolates failures within the system, allowing for rapid fault isolation. TEAMATE takes over from where TEAMS-RT left off by intelligently guiding the maintenance technician through the troubleshooting procedure, repair actions, and operational checkout. TEAMS-KB serves as a model management and collection tool. TEAMS-RDS (TEAMS-Remote Diagnostic Server) has the ability to continuously assess a system and isolate any failure in that system or its components, in real time. RDS incorporates TEAMS-RT, TEAMATE, and TEAMS-KB in a large-scale server architecture capable of providing advanced diagnostic and maintenance functions over a network, such as the Internet, with a web browser user interface.

Source record↗
NASA NTRS1998

Effectiveness of an Expert System for Astronaut Assistance on a Sleep Experiment

Principal Investigator-in-a-Box ([PI]) is an expert system designed to train and assist astronauts with the performance of an experiment outside their field of expertise, particularly when contact with the Principal Investigators on the ground is limited or impossible. In the current case, [PI] was designed to assist with the calibration and troubleshooting procedures of the Neurolab Sleep and Respiration Experiment during the pre-sleep period of no ground contact. It displays physiological signals in real time during the pre-sleep instrumentation period, and alerts the astronauts when a poor signal quality is detected. Results of the first study indicated a beneficial effect of [PI] and training in reducing anomaly detection time and the number of undetected anomalies. For the in-flight performance, excluding the saturated signals, the expert system had an 84.2% detection accuracy, and the questionnaires filled out by the astronauts showed positive crew reactions to the expert system.

Heher, Dennis↗
NASA NTRS2002

A Scalable, Out-of-Band Diagnostics Architecture for International Space Station Systems Support

The computational infrastructure of the International Space Station (ISS) is a dynamic system that supports multiple vehicle subsystems such as Caution and Warning, Electrical Power Systems and Command and Data Handling (C&DH), as well as scientific payloads of varying size and complexity. The dynamic nature of the ISS configuration coupled with the increased demand for payload support places a significant burden on the inherently resource constrained computational infrastructure of the ISS. Onboard system diagnostics applications are hosted on computers that are elements of the avionics network while ground-based diagnostic applications receive only a subset of available telemetry, down-linked via S-band communications. In this paper we propose a scalable, out-of-band diagnostics architecture for ISS systems support that uses a read-only connection for C&DH data acquisition, which provides a lower cost of deployment and maintenance (versus a higher criticality readwrite connection). The diagnostics processing burden is off-loaded from the avionics network to elements of the on-board LAN that have a lower overall cost of operation and increased computational capacity. A superset of diagnostic data, richer in content than the configured telemetry, is made available to Advanced Diagnostic System (ADS) clients running on wireless handheld devices, affording the crew greater mobility for troubleshooting and providing improved insight into vehicle state. The superset of diagnostic data is made available to the ground in near real-time via an out-of band downlink, providing a high level of fidelity between vehicle state and test, training and operational facilities on the ground.

Fletcher, Daryl P.↗
NASA NTRS2002

Console Log Keeping Made Easier - Tools and Techniques for Improving Quality of Flight Controller Activity Logs

At the Marshall Space Flight Center's (MSFC) Payload Operations Integration Center (POIC) for International Space Station (ISS), each flight controller maintains detailed logs of activities and communications at their console position. These logs are critical for accurately controlling flight in real-time as well as providing a historical record and troubleshooting tool. This paper describes logging methods and electronic formats used at the POIC and provides food for thought on their strengths and limitations, plus proposes some innovative extensions. It also describes an inexpensive PC-based scheme for capturing and/or transcribing audio clips from communications consoles. Flight control activity (e.g. interpreting computer displays, entering data/issuing electronic commands, and communicating with others) can become extremely intense. It's essential to document it well, but the effort to do so may conflict with actual activity. This can be more than just annoying, as what's in the logs (or just as importantly not in them) often feeds back directly into the quality of future operations, whether short-term or long-term. In earlier programs, such as Spacelab, log keeping was done on paper, often using position-specific shorthand, and the other reader was at the mercy of the writer's penmanship. Today, user-friendly software solves the legibility problem and can automate date/time entry, but some content may take longer to finish due to individual typing speed and less use of symbols. File layout can be used to great advantage in making types of information easy to find, and creating searchable master logs for a given position is very easy and a real lifesaver in reconstructing events or researching a given topic. We'll examine log formats from several console position, and the types of information that are included and (just as importantly) excluded. We'll also look at when a summary or synopsis is effective, and when extensive detail is needed.

Scott, David W.↗
NASA NTRS2002

STS-113 Flight Day 9 Highlights

This video shows the activities of the STS-113 (Jim Wetherbee, Commander; Paul Lockhart, Pilot; Michael Lopez-Alegria, John Herrington, Mission Specialists) crew during flight day 9. Also seen are the outgoing Expedition 5 (Valeri Korzun, Commander; Peggy Whitsun, ISS Science Officer/Flight Engineer; Sergei Treschev, Flight Engineer) and incoming Expedition 6 (Kenneth Bowersox, Commander; Donald Pettit, Nikolai Budarin, Flight Engineers) crews of the ISS (International Space Station). Flight day 9 is a relatively inactive day, with some off-time scheduled for crew bonding and enjoying views. Seven of the joint crew members, including Lopez-Alegria, Wetherbee, Herrington, and Whitsun, pose together and answer questions. Footage shows ISS Science Officers Whitsun and Pettit troubleshooting equipment. The video also contains a clear view of southern South America, a cloudy view of the South Pacific, and external footage of the ISS including the Canadarm robotic arm. The payload bay of the shuttle Endeavour is also shown.

Source record↗
NASA NTRS2003

Space Station Power Generation in Support of the Beta Gimbal Anomaly Resolution

The International Space Station (ISS) is the largest and most complex spacecraft ever assembled and operated in orbit. The first U.S. photovoltaic (PV) module, containing two solar arrays, was launched, installed, and activated in early December 2000. After the first week of continuously rotating the U.S. solar arrays, engineering personnel in the ISS Mission Evaluation Room (MER) observed higher than expected electrical currents on the drive motor in one of the Beta Gimbal Assemblies (BGA), the mechanism used to maneuver a U.S. solar array. The magnitude of the motor currents continued to increase over time on both BGA's, creating concerns about the ability of the gimbals to continue pointing the solar arrays towards the sun, a function critical for continued assembly of the ISS. A number of engineering disciplines convened in May 2001 to address this on-orbit hardware anomaly. This paper reviews the ISS electrical power system (EPS) analyses performed to develop viable operational workarounds that would minimize BGA use while maintaining sufficient solar array power to continue assembly of the ISS. Additionally, EPS analyses performed in support of on-orbit BGA troubleshooting exercises is reviewed. EPS capability analyses were performed using SPACE, a computer code developed by NASA Glenn Research Center (GRC) for the ISS program office.

Delleur, Ann M.↗