Search NASA⌕ Search

SEARCH · Search NASA

Results for “MCC”

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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

Orbit Determination Support for the Microwave Anisotropy Probe (MAP)

The Microwave Anisotropy Probe (MAP) is a Medium Class Explorers (MIDEX) mission produced in partnership between Goddard Space Flight Center (GSFC) and Princeton University. The main science objective of the MAP mission is to produce an accurate full-sky map of the cosmic microwave background temperature fluctuations anisotropy. MAP was launched from the Cape Canaveral Air Force Station Complex 17 aboard a Delta II 7425-10 expendable launch vehicle at exactly 19:46:46.183 UTC on June 30, 2001. The spacecraft received a nominal direct insertion by the Delta into a 185 km circular orbit. MAP was then maneuvered into a sequence of phasing loops designed to set up a lunar swingby (gravity-assisted acceleration) of the spacecraft onto a transfer trajectory to a Lissajous orbit about the Earth-Sun L2 point. The mission duration is approximately 27 months with 3 to 4 months of transfer time to the final mission orbit about L2. The MAP transfer orbit consisted of 3.5 phasing loops: the first loop has a 7-day period, the second and third loops have a 9-day period, and the last half loop has a 4-day period as illustrated in Figure 1, which also indicates the placement of maneuvers. A Pfinal correction maneuver was performed 18 hours after the last perigee to more closely achieve the targeted lissajous orbit. The lunar encounter or swingby took place approximately 30 days after launch. After the lunar encounter, the spacecraft will cruise for approximately 120 days before it arrives at L2. A Mid-Course Correction (MCC) maneuver was executed seven days after the swingby to further refine the trajectory. Once the MAP satellite is injected into the L2 Lissajous orbit, it will perform occasional stationkeeping maneuvers to maintain the Lissajous orbit for a minimum of two years (and a goal of four years). Because of its complex orbital characteristics, the mission provided a unique challenge to orbit determination (OD) support in many orbital regimes. Extensive trajectory error covariance analysis was performed to predict ephemeris accuracy for the OD process using a Bayesian least-squares technique. The orbit determination error analysis is essential for maneuver planning and maneuver recovery study. Several tracking scenarios were investigated for each phase of the mission. This paper provides a summary of the premission trajectory covariance error analysis, as well as actual real-time OD results. The use and impact of the various tracking stations, systems, and measurements will be discussed. Details of the operational OD support and the inferred OD accuracy will be presented, and the results will be compared to the premission covariance analysis, In addition, there will be a discussion of the challenges presented to OD support including delta-Vs at apogee as well as perigee, and effects due to spacecraft attitude mode, in light of their implications to the OD accuracy and covariance analysis.

Truong, Son H.↗
NASA NTRS2002

An Overview of Trajectory Design Operations for the Microwave Anisotropy Probe (MAP) Mission

The main science objective of the Microwave Anisotropy Probe (MAP) mission is to produce an accurate full-sky map of the cosmic microwave background temperature fluctuations - anisotropy. MAP will collect these measurements from a lissajous orbit about the Sun-Earth/Moon L2 Lagrange Point. The NASA Goddard Space Flight Center (GSFC) Flight Dynamics Analysis Branch provided mission analysis, maneuver planning and maneuver calibration for the MAP spacecraft. This paper will provide an overview of the MAP trajectory design, a summary of the maneuvers executed. Differences from the pre-launch nominal plan will also be discussed. During the MAP phasing loops, MAP performed three calibration maneuvers in order to characterize the performance of the primary sets of thrusters - +X, +Z, and -Z. The calibration maneuvers were designed to minimize their impact on the trajectory. Four maneuvers were performed to set up the gravity assist of the Moon - required to propel MAP out to its orbit about L2. These maneuvers were performed at the three phasing loop perigees and at 18 hours after the final perigee. It became necessary to alter some of the perigee maneuvers in order to shape the gravity assist. This shaping was done to help meet some mission goals. In particular, the gravity assist was changed slightly in order to remove lunar shadows in both the cruise out to L2 and in the first revolution about L2. This amounted to a change in the phasing loop AV of less than 1 m/s. After the gravity assist, two mid-course correction (MCC) maneuvers were performed in order to fine-tune the trajectory. MCC1 was used to clean up and errors which resulted from the gravity assist. MCC2 was performed in order to mitigate a large stationkeeping maneuver following a crucial instrument calibration period during the cruise phase. MAP executed it's first stationkeeping maneuver in January 16th and is ready for a second calibration period during late Winter / early Spring. Further information concerning subsequent stationkeeping maneuver will be added as they become available.

Cuevas, Osvaldo O.↗
NASA NTRS2002

STS-112 Crew Interviews: Yurchikhin

A preflight interview with mission specialist Fyodor Yurchikhin is presented. He worked for a long time in Energia in the Russian Mission Control Center (MCC). Yurchikhin discusses the main goal of the STS-112 flight, which is to install the Integrated Truss Assembly S1 (Starboard Side Thermal Radiator Truss) on the International Space Station. He also talks about the three space walks required to install the S1. After the installation of S1, work with the bolts and cameras are performed. Yurchikhin is involved in working with nitrogen and ammonia jumpers. He expresses the complexity of his work, but says that he and the other crew members are ready for the challenge.

Source record↗
NASA NTRS2003

Orbit Determination Support for the Microwave Anisotropy Probe (MAP)

THe microwave Anisotropy Probe (MAP) ia the second Medium Class Explorer (MIDEX) mission of the National Aeronautics and Space Administration (NASA). The main goal of the MAP observatory is to measure the temperature fluctuations, known as anisotropy, of the cosmic microwave background (CBG) radiation over the entire sky and to produce a map of the CMB anisotropies with an angular resolution of approximately 3 degrees. MAP was launched from the Cape Canaveral Air Force Station Complex 17 aboard a Delta II 7425-10 expendable launch vehicle at exactly 19:46:46.183 UTC on June 30, 20001. The spacecraft receiver a nominal direct insertion by the Delta expendable launch vehicle into a 185-km circular orbit with a 28.7 deg. inclination. MAP was than maneuvered into a sequence of phasing loops designed to set up a lunar gravity-assisted acceleration of the spacecraft onto a transfer trajectory to a lissajous orbit about the Earth-Sun L2 Lagrange point, about 1.5 million km from Earth. The science mission minimum lifetime is two years of observations at L2 with a desired lifetime of 4 years. The MAP transfer orbit consisted of 3.5 phasing loops.The MAP trajectory schematic all the way through L2 is shown. The first loop had a period of 7 days, the second and third loops were 10 days long, and the last half loop was 5 days. The periselene (i.e., lunar encounter or swingby) took place approximately 30 days after launch. After the periselene, the spacecraft cruised for approximately 60 days before it arrived in the vicinity of the L2 libration point. Two mid-course correction (MCC) maneuvers were performed to refine MAP's post-launch trajectory-one after periselene and one prior to arrival at vicinity of L2. Now that MAP is at its operational L2 lissajous orbit, the MAP satellite is commanded to perform occasional station-keeping (SK) maneuvers in order to maintain its orbit around L2. Because of its complex orbital characteristics, the mission provided a unique challenge to orbit determination (OD) support in many orbital regimes.

Truong, Son H.↗
NASA NTRS2003

VPS GRCop-84 Liner Development Efforts

For the past several years, NASA's Marshall Space Flight Center (MSFC) has been working with Plasma Processes, Inc. (PPI) to fabricate combustion chamber liners using the Vacuum Plasma Spray (VPS) process. Multiple liners of a variety of shapes and sizes have been created. Each liner has been fabricated with GRCop-84 (a copper alloy with chromium and niobium) and a functional gradient coating (FGC) on the hot wall. While the VPS process offers versatility and a reduced fabrication schedule, the material system created with VPS allows the liners to operate at higher temperatures, with maximum blanch resistance and improved cycle life. A subscal unit (5K lbf thrust class) is being cycle tested in a LOX/Hydrogen thrust chamber assembly at MSFC. To date, over 75 hot-fire tests have been accumulated on this article. Tests include conditions normally detrimental to conventional materials, yet the VPS GRCop-84 liner has yet to show any signs of degradation. A larger chamber (15K lbf thrust class) has also been fabricated and is being prepared for hot-fire testing at MSFC near the end of 2003. Linear liners have been successfully created to further demonstrate the versatility of the process. Finally, scale up issues for the VPS process are being tackled with efforts to fabricate a full size, engine class liner. Specifically, a liner for the SSME's Main Combustion Chamber (MCC) has recently been attempted. The SSME size was chosen for convenience, since its design was readily available and its size was sufficient to tackle specific issues. Efforts to fabricate these large liners have already provided valuable lessons for using this process for engine programs. The material quality for these large units is being evaluated with destructive analysis and these results will be available by the end of 2003.

Elam, Sandra K.↗
NASA NTRS1999

Communications and Tracking of Visiting Vehicles near ISS: The Design of the Reusable Launch Vehicle Communications

The International Space Station (ISS) will provide for the visitation of various vehicles such as the Shuttle, Automated Transfer Vehicle (ATV), H-II Transfer Vehicle (HTV), Crew Return Vehicle (CRV), Reusable Launch Vehicle (RLV) and Soyuz. These vehicles will provide for crew replacement, consumables resupply, and equipment delivery. In order for these vehicles to approach and eventually dock with the ISS, there must be near continuous communications coverage between the visiting vehicle and the ISS, as well as communications between the vehicle and a Mission Control Center (MCC). Since the ISS communications systems are already designed and scheduled for ISS activation, the vehicles must either utilize these communications systems or provide their own. There are two means of two-way communications with the ISS. These are (1) S-Band communications using TDRSS, and (2) UHF communications using some form of the Space to Space Station Radio (SSSR) link. The RLV utilizes ISS compatible communications systems to communicate with both the ISS and a Mission Control Center. Since all vehicles must adhere to the Visiting Vehicle Interface requirements given in reference 1, the RLV communications system design must meet these requirements during entry into the ISS Approach Ellipsoid (AE) and during Proximity Operations. Included in this paper are descriptions of these communications approaches as well as their potential utilization in the ISS communications system.

Stillwagen, Frederic H.↗
NASA NTRS2008

Planning for the Future, a Look from Apollo to the Present

Future missions out of low Earth orbit, returning to the moon and Mars, will be some of the most complicated endeavors ever attempted by mankind. It will require the wealth of nations and the dedicated efforts of thousand of individuals working in a concerted effort to take man to the moon, Mars and beyond. These missions will require new equipment and new approaches to optimize our limited resources and time in space. This daily planning and optimization which currently is being performed by scores of people in MCC Houston and around the world will need to adapt to the challenges faced far from Earth. By studying the processes, methodologies, and tools employed from Apollo, Skylab, Shuttle, ISS, and other programs such as NEEMO, we can learn from the past to plan for the future. This paper will explore the planning process used from Apollo onward and will discuss their relevancy in future applications.

Segrera, David↗
NASA NTRS2005

Introduction and Mission Response Team (MRT)

On February 1, 2003 the Space Shuttle Columbia, returning to Earth with a crew of seven astronauts, disintegrated along a track extending from California to Louisiana. Observers on the ground filmed breakup of the spacecraft. Debris fell along a 567 statute mile track from Littlefield, Texas to Fort Polk, Louisiana; the largest ever recorded debris field. At the time of the accident the National Aeronautics and Space Administration (NASA) flight surgeon on-duty at the Mission Control Center (MCC) in Houston, Texas initiated the medical contingency response. The DOD surgeon at Patrick Air Force Base was notified, NASA medical personnel were recalled and the services of Armed Forces Institute of Pathology (AFIP) were requested. Subsequent to the accident the NASA flight surgeons that had supported the crew on orbit now provided medical support to the crewmember s families. Federal Emergency Management Agency (FEMA), the National Transportation Safety Board (NTSB), the Federal Bureau of Investigation (FBI) and numerous other federal, state and local agencies along with the citizens of Texas and Louisiana responded to the disaster. Search and recovery was managed from a Disaster Field Office (DFO) established in Lufkin, Texas. Mishap Investigation Team (MIT) medical operations were managed from Barksdale Air Force Base, Louisiana. Accident investigation teams (Columbia Accident Investigation Task Force (CAITF) and Columbia Accident Investigation Board (CAIB)) appointed immediately after the disaster included current and former authorities in space medicine. In August 2003, the CAIB concluded its investigation and released its findings in a report published in February 2004.

Pool, Sam↗
NASA NTRS2009

Human Factors in Training

Future space missions will be significantly longer than current shuttle missions and new systems will be more complex than current systems. Increasing communication delays between crews and Earth-based support means that astronauts need to be prepared to handle the unexpected on their own. As crews become more autonomous, their potential span of control and required expertise must grow to match their autonomy. It is not possible to train for every eventuality ahead of time on the ground, or to maintain trained skills across long intervals of disuse. To adequately prepare NASA personnel for these challenges, new training approaches, methodologies, and tools are required. This research project aims at developing these training capabilities. By researching established training principles, examining future needs, and by using current practices in space flight training as test beds, both in Flight Controller and Crew Medical domains, this research project is mitigating program risks and generating templates and requirements to meet future training needs. Training efforts in Fiscal Year 08 (FY08) strongly focused on crew medical training, but also began exploring how Space Flight Resource Management training for Mission Operations Directorate (MOD) Flight Controllers could be integrated with systems training for optimal Mission Control Center (MCC) operations. The Training Task addresses Program risks that lie at the intersection of the following three risks identified by the Project: (1) Risk associated with poor task design (2) Risk of error due to inadequate information (3) Risk associated with reduced safety and efficiency due to poor human factors design

Barshi, Immanuel↗
NASA NTRS2008

OTF CCSDS SM and C Interoperability Prototype

A presentation is provided to demonstrate the interoperability between two space flight Mission Operation Centers (MOCs) and to emulate telemetry, actions, and alert flows between the two centers. One framework uses a COTS C31 system that uses CORBA to interface to the local OTF data network. The second framework relies on current Houston MCC frameworks and ad hoc clients. Messaging relies on SM and C MAL, Core and Common Service formats, while the transport layer uses AMS. A centralized SM and C Registry uses HTTP/XML for transport/encoding. The project's status and progress are reviewed.

Reynolds, Walter F.↗
NASA NTRS2009

OTF CCSDS Mission Operations Prototype Parameter Service. Phase I: Exit Presentation

This slide presentation reviews the prototype of phase 1 of the parameter service design of the CCSDS mission operations. The project goals are to: (1) Demonstrate the use of Mission Operations standards to implement the Parameter Service (2) Demonstrate interoperability between Houston MCC and a CCSDS Mission Operations compliant mission operations center (3) Utilize Mission Operations Common Architecture. THe parameter service design, interfaces, and structures are described.

Reynolds, Walter F.↗
NASA NTRS2009

J-2X Upper Stage Engine: Hardware and Testing 2009

Mission: Common upper stage engine for Ares I and Ares V. Challenge: Use proven technology from Saturn X-33, RS-68 to develop the highest Isp GG cycle engine in history for 2 missions in record time . Key Features: LOX/LH2 GG cycle, series turbines (2), HIP-bonded MCC, pneumatic ball-sector valves, on-board engine controller, tube-wall regen nozzle/large passively-cooled nozzle extension, TEG boost/cooling . Development Philosophy: proven hardware, aggressive schedule, early risk reduction, requirements-driven.

Buzzell, James C.↗
NASA NTRS2010

Human Factors in Training

Future space missions will be significantly longer than current shuttle missions and new systems will be more complex than current systems. Increasing communication delays between crews and Earth-based support means that astronauts need to be prepared to handle the unexpected on their own. As crews become more autonomous, their potential span of control and required expertise must grow to match their autonomy. It is not possible to train for every eventuality ahead of time on the ground, or to maintain trained skills across long intervals of disuse. To adequately prepare NASA personnel for these challenges, new training approaches, methodologies, and tools are required. This research project aims at developing these training capabilities. By researching established training principles, examining future needs, and by using current practices in space flight training as test beds, both in Flight Controller and Crew Medical domains, this research project is mitigating program risks and generating templates and requirements to meet future training needs. Training efforts in Fiscal Year 09 (FY09) strongly focused on crew medical training, but also began exploring how Space Flight Resource Management training for Mission Operations Directorate (MOD) Flight Controllers could be integrated with systems training for optimal Mission Control Center (MCC) operations. The Training Task addresses Program risks that lie at the intersection of the following three risks identified by the Project: 1) Risk associated with poor task design; 2) Risk of error due to inadequate information; and 3) Risk associated with reduced safety and efficiency due to poor human factors design.

Barshi, Immanuel↗
NASA NTRS2010

Display Sharing: An Alternative Paradigm

The current Johnson Space Center (JSC) Mission Control Center (MCC) Video Transport System (VTS) provides flight controllers and management the ability to meld raw video from various sources with telemetry to improve situational awareness. However, maintaining a separate infrastructure for video delivery and integration of video content with data adds significant complexity and cost to the system. When considering alternative architectures for a VTS, the current system's ability to share specific computer displays in their entirety to other locations, such as large projector systems, flight control rooms, and back supporting rooms throughout the facilities and centers must be incorporated into any new architecture. Internet Protocol (IP)-based systems also support video delivery and integration. IP-based systems generally have an advantage in terms of cost and maintainability. Although IP-based systems are versatile, the task of sharing a computer display from one workstation to another can be time consuming for an end-user and inconvenient to administer at a system level. The objective of this paper is to present a prototype display sharing enterprise solution. Display sharing is a system which delivers image sharing across the LAN while simultaneously managing bandwidth, supporting encryption, enabling recovery and resynchronization following a loss of signal, and, minimizing latency. Additional critical elements will include image scaling support, multi -sharing, ease of initial integration and configuration, integration with desktop window managers, collaboration tools, host and recipient controls. This goal of this paper is to summarize the various elements of an IP-based display sharing system that can be used in today's control center environment.

Brown, Michael A.↗
NASA NTRS2010

Computer Software Configuration Item-Specific Flight Software Image Transfer Script Generator

A K-shell UNIX script enables the International Space Station (ISS) Flight Control Team (FCT) operators in NASA s Mission Control Center (MCC) in Houston to transfer an entire or partial computer software configuration item (CSCI) from a flight software compact disk (CD) to the onboard Portable Computer System (PCS). The tool is designed to read the content stored on a flight software CD and generate individual CSCI transfer scripts that are capable of transferring the flight software content in a given subdirectory on the CD to the scratch directory on the PCS. The flight control team can then transfer the flight software from the PCS scratch directory to the Electronically Erasable Programmable Read Only Memory (EEPROM) of an ISS Multiplexer/ Demultiplexer (MDM) via the Indirect File Transfer capability. The individual CSCI scripts and the CSCI Specific Flight Software Image Transfer Script Generator (CFITSG), when executed a second time, will remove all components from their original execution. The tool will identify errors in the transfer process and create logs of the transferred software for the purposes of configuration management.

Bolen, Kenny↗
NASA NTRS2006

Java Mission Evaluation Workstation System

The Java Mission Evaluation Workstation System (JMEWS) is a collection of applications designed to retrieve, display, and analyze both real-time and recorded telemetry data. This software is currently being used by both the Space Shuttle Program (SSP) and the International Space Station (ISS) program. JMEWS was written in the Java programming language to satisfy the requirement of platform independence. An object-oriented design was used to satisfy additional requirements and to make the software easily extendable. By virtue of its platform independence, JMEWS can be used on the UNIX workstations in the Mission Control Center (MCC) and on office computers. JMEWS includes an interactive editor that allows users to easily develop displays that meet their specific needs. The displays can be developed and modified while viewing data. By simply selecting a data source, the user can view real-time, recorded, or test data.

Pettinger, Ross↗
NASA NTRS2010

SPOT Program

A Spacecraft Position Optimal Tracking (SPOT) program was developed to process Global Positioning System (GPS) data, sent via telemetry from a spacecraft, to generate accurate navigation estimates of the vehicle position and velocity (state vector) using a Kalman filter. This program uses the GPS onboard receiver measurements to sequentially calculate the vehicle state vectors and provide this information to ground flight controllers. It is the first real-time ground-based shuttle navigation application using onboard sensors. The program is compact, portable, self-contained, and can run on a variety of UNIX or Linux computers. The program has a modular objec-toriented design that supports application-specific plugins such as data corruption remediation pre-processing and remote graphics display. The Kalman filter is extensible to additional sensor types or force models. The Kalman filter design is also strong against data dropouts because it uses physical models from state and covariance propagation in the absence of data. The design of this program separates the functionalities of SPOT into six different executable processes. This allows for the individual processes to be connected in an a la carte manner, making the feature set and executable complexity of SPOT adaptable to the needs of the user. Also, these processes need not be executed on the same workstation. This allows for communications between SPOT processes executing on the same Local Area Network (LAN). Thus, SPOT can be executed in a distributed sense with the capability for a team of flight controllers to efficiently share the same trajectory information currently being computed by the program. SPOT is used in the Mission Control Center (MCC) for Space Shuttle Program (SSP) and International Space Station Program (ISSP) operations, and can also be used as a post -flight analysis tool. It is primarily used for situational awareness, and for contingency situations.

Smith, Jason T.↗
NASA NTRS2010

Human Spaceflight Recent Conjunctions of Interest

I. During each nine-hour shift (or upon request), the Orbital Safety Analyst (OSA) at JSpOC updates the entire tracked catalog with the latest tracking data from the SSN and screens this catalog against NASA s assets. a) For ISS operations, a 72-hour advance screening is performed. b) For Shuttle orbit operations, a 36-hour advance screening is performed. c) If a vehicle is performing a maneuver during the screening period, OSA uses post-reboost-trajectory data supplied by Mission Control Center-Houston (MCC-H) for screening. II. An automated process is used to detect any conjunctions within 10 x 40 x 40 km box (centered on the vehicle) using Special Perturbation (SP) processing: a) Box dimensions are Radial x Downtrack x Crosstrack. b) Any object found within this box has the tracking tasking level increased to improve (hopefully) its uncertainty in its current and predicted orbital trajectory. c) OSA informs NASA if any object is found inside a 2 x 25 x 25 km box then creates and sends an Orbital Conjunction Message (OCM) to NASA which contains detailed information about the conjunction. d) For Shuttle, the box size used for screening and reporting is altered for special operations (day of rendezvous, launch screening, etc.).

Browns, Ansley C.↗