Search NASA⌕ Search

SEARCH · Search NASA

Results for “COMMAND MODULE”

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 811 records · Page 45

STS-107 Crew Training Clip

The STS-107 is a Multidiscipline Microgravity and Earth Science Research Mission to conduct international scientific investigations in orbit. The crew consists of Payload Specialist Ilan Ramon, Commander Rick Husband, Pilot William McCool, and Mission Specialists David Brown, Laurel Clark, Michael Anderson, and Kalpana Chawla. The crewmembers are shown getting suited in the Pre-Launch Ingress and Egress training area. The other areas of training include Payload Experiment in Fixed Base/Spacehab, Mist Experiment Combustion Module 2, Phab 4 Experiment in CCT Mid-deck and Payload Experiment Demo-Protein Crystal Growth.

Source record↗

FPGA for Power Control of MSL Avionics

A PLGT FPGA (Field Programmable Gate Array) is included in the LCC (Load Control Card), GID (Guidance Interface & Drivers), TMC (Telemetry Multiplexer Card), and PFC (Pyro Firing Card) boards of the Mars Science Laboratory (MSL) spacecraft. (PLGT stands for PFC, LCC, GID, and TMC.) It provides the interface between the backside bus and the power drivers on these boards. The LCC drives power switches to switch power loads, and also relays. The GID drives the thrusters and latch valves, as well as having the star-tracker and Sun-sensor interface. The PFC drives pyros, and the TMC receives digital and analog telemetry. The FPGA is implemented both in Xilinx (Spartan 3- 400) and in Actel (RTSX72SU, ASX72S). The Xilinx Spartan 3 part is used for the breadboard, the Actel ASX part is used for the EM (Engineer Module), and the pin-compatible, radiation-hardened RTSX part is used for final EM and flight. The MSL spacecraft uses a FC (Flight Computer) to control power loads, relays, thrusters, latch valves, Sun-sensor, and star-tracker, and to read telemetry such as temperature. Commands are sent over a 1553 bus to the MREU (Multi-Mission System Architecture Platform Remote Engineering Unit). The MREU resends over a remote serial command bus c-bus to the LCC, GID TMC, and PFC. The MREU also sends out telemetry addresses via a remote serial telemetry address bus to the LCC, GID, TMC, and PFC, and the status is returned over the remote serial telemetry data bus.

Wang, Duo↗

STS-88 Mission Highlights Resources Tape

The STS-88 flight crew, Commander Robert D. Cabana, Pilot Frederick W. Sturckow, and Mission Specialists Nancy J. Currie, James H. Newman, Jerry L. Ross, and Sergei Krikalev present a video overview of their space flight. Tape two of three includes the installation of an S-Band to help monitor the UNITY Connecting Module, the opening of UNITY's hatch, the opening of the main compartment hatch to ZARYA Control Module, and the repair of the inflight maintenance system.

Source record↗

Three Corner Sat Communications System

Three Corner Satellite is a constellation of three nanosatellites designed and built by students. New Mexico State University has taken on the design of the communications system for this constellation. The system includes the forward link, return link, and the crosslink. Due to size, mass, power, and financial constraints, we must design a small, light, power efficient, and inexpensive communications system. This thesis presents the design of a radio system to accomplish the data transmission requirements in light of the system constraints. In addition to the hardware design, the operational commands needed by the satellite's on-board computer to control and communicate with the communications hardware will be presented. In order for the hardware to communicate with the ground stations, we will examine the link budgets derived from the radiated power of the transmitters, link distance, data modulation, and data rate for each link. The antenna design for the constellation is analyzed using software and testing the physical antennas on a model satellite. After the analysis and testing, a combination of different systems will meet and exceed the requirements and constraints of the Three Corner Satellite constellation.

Anderson, Bobby↗

STS-106 Crew News Conference

The crew of STS-106, Commander Terrence W. Wilcutt, Pilot Scott D. Altman, and Mission Specialists Daniel C. Burbank, Edward T. Lu, Richard A. Mastracchio, Yuri Ivanovich Malenchenko, and Boris V. Morukov are seen during an in-flight press conference. The crew answers questions about their mission, future work, and the Zvezda Service Module.

Source record↗

STS-108 Crew Interviews: Dom Gorie

STS-108 Commander Dom Gorie is seen during a prelaunch interview. He answers questions about the mission's goals and significance, explaining the meaning of 'utilization flight 1' (UF-1) as opposed to an 'assembly flight'. He gives details on the payload (Starshine Satellite, Avian Development Facility, and Rafaello Multipurpose Logistics Module (MPLM)), his role in the rendezvous, docking, and undocking of the Endeavour Orbiter to the International Space Station (ISS), how he will participate in the unloading and reloading of the MPLM, and the way in which the old and new resident crews of ISS will exchanged. Gorie ends with his thoughts on the short-term and long-term future of the International Space Station.

Source record↗

STS-107 Flight Day 7 Highlights

This video shows the activities of the STS-107 crew (Rick Husband, Commander; William McCool, Pilot; Kalpana Chawla, David Brown, Michael Anderson, Laurel Clark, Mission Specialists; Ilan Ramon, Payload Specialist) during flight day 7 of the Columbia orbiter's final flight. The primary activities of flight day 7 are setting up and conducting spaceborne experiments in the SpaceHab RDM (Research Double Module) in the orbiter's payload bay. Silkworms and ants from the STARS (Space Technology and Research Students) international student experiments are shown. Footage of the Mediterranean Sea taken by the MEIDEX (Mediterranean Israeli Dust Experiment) is also shown. Canisters containing experiments attached to the SpaceHab RDM are shown in the space shuttle's payload bay. Other views include the Earth's surface, and the Earth's atmosphere, visible along its limb.

Source record↗

Technology Benefit Estimator (T/BEST): User's Manual

The Technology Benefit Estimator (T/BEST) system is a formal method to assess advanced technologies and quantify the benefit contributions for prioritization. T/BEST may be used to provide guidelines to identify and prioritize high payoff research areas, help manage research and limited resources, show the link between advanced concepts and the bottom line, i.e., accrued benefit and value, and to communicate credibly the benefits of research. The T/BEST software computer program is specifically designed to estimating benefits, and benefit sensitivities, of introducing new technologies into existing propulsion systems. Key engine cycle, structural, fluid, mission and cost analysis modules are used to provide a framework for interfacing with advanced technologies. An open-ended, modular approach is used to allow for modification and addition of both key and advanced technology modules. T/BEST has a hierarchical framework that yields varying levels of benefit estimation accuracy that are dependent on the degree of input detail available. This hierarchical feature permits rapid estimation of technology benefits even when the technology is at the conceptual stage. As knowledge of the technology details increases the accuracy of the benefit analysis increases. Included in T/BEST's framework are correlations developed from a statistical data base that is relied upon if there is insufficient information given in a particular area, e.g., fuel capacity or aircraft landing weight. Statistical predictions are not required if these data are specified in the mission requirements. The engine cycle, structural fluid, cost, noise, and emissions analyses interact with the default or user material and component libraries to yield estimates of specific global benefits: range, speed, thrust, capacity, component life, noise, emissions, specific fuel consumption, component and engine weights, pre-certification test, mission performance engine cost, direct operating cost, life cycle cost, manufacturing cost, development cost, risk, and development time. Currently, T/BEST operates on stand-alone or networked workstations, and uses a UNIX shell or script to control the operation of interfaced FORTRAN based analyses. T/BEST's interface structure works equally well with non-FORTRAN or mixed software analysis. This interface structure is designed to maintain the integrity of the expert's analyses by interfacing with expert's existing input and output files. Parameter input and output data (e.g., number of blades, hub diameters, etc.) are passed via T/BEST's neutral file, while copious data (e.g., finite element models, profiles, etc.) are passed via file pointers that point to the expert's analyses output files. In order to make the communications between the T/BEST's neutral file and attached analyses codes simple, only two software commands, PUT and GET, are required. This simplicity permits easy access to all input and output variables contained within the neutral file. Both public domain and proprietary analyses codes may be attached with a minimal amount of effort, while maintaining full data and analysis integrity, and security. T/BESt's sotware framework, status, beginner-to-expert operation, interface architecture, analysis module addition, and key analysis modules are discussed. Representative examples of T/BEST benefit analyses are shown.

Generazio, Edward R.↗

STS-106 Crew Activities Report/Flight Day 3 Highlights

On this third day of the STS-106 Atlantis mission, the flight crew, Commander Terrence W. Wilcutt, Pilot Scott D. Altman, and Mission Specialists Daniel C. Burbank, Edward T. Lu, Richard A. Mastracchio, Yuri Ivanovich Malenchenko, and Boris V. Morukov are seen as they approach the International Space Station (ISS). Also shown are views of the rendezvous taken from both the Zarya Control Module and the Atlantis spacecraft. Final preparation for the docking includes checking of tools and equipment needed to support the rendezvous and docking, as well as equipment for the scheduled space walk. After docking over Western Kazakhstan, the Zarya and Zvezda Service Module is seen from the external cameras of Atlantis. Also shown is footage of the crew before and during the rendezvous.

Source record↗

STS-92 Crew Activity Report/Flight Day 10 Highlights

On this tenth day of the STS-92 mission, the flight crew, Commander Brian Duffy, Pilot Pamela A. Melroy, and Mission Specialists Koichi Wakata, Leroy Chiao, Peter J.K. Wisoff, Michael E. Lopez-Alegria, and William S. McArthur prepare for the undocking of Discovery from the International Space Station (ISS) as Lopez-Alegria is seen closing the hatch on the Unity Module. A slow sweep of the outside of the ISS shows the space station in detail against the backdrop of a dark Earth where the lights of a city shine. Lopez-Alegria closes the outer hatch and Discovery undocks from the ISS. As the two separate, the ISS is seen orbiting across a beautiful dark blue Earth.

Source record↗

SRMS Assisted Docking and Undocking for the Orbiter Repair Maneuver

As part of the Orbiter Repair Maneuver (ORM) planned for Return to Flight (RTF) operations, the Shuttle Remote Manipulator System (SRMS) must undock the Orbiter, maneuver it through a complex trajectory at extremely low rates, present it to an EVA crewman at the end of the Space Station Remote Manipulator System to perform the Thermal Protection System (TPS) repair, and then retrace back through the trajectory to dock the Orbiter with the Orbiter Docking System (ODS). The initial and final segments of this operation involve the interaction between the SRMS, ISS, Orbiter and ODS. Previously, a technique entitled "SRMS assisted docking" for installation of a payload to the ODS had been developed and was utilized for the Russian provided Docking Module on STS-74 during Shuttle-Mir missions and both the Node 1 and FGB elements on STS-88/Flight 2A. This procedure consisted of the SRMS grappling the respective payload, maneuvering it to a pre-install position inches above the ODS Androgynous Peripheral Attachment System (APAS) ring, commanding the SRMS into Test mode (which allows brakes-off motion of the joints), and then down-firing Primary Reaction Control System (PRCS) jets in order to effect a capture of the APAS latches. Once a successful capture had been achieved, then the AP AS was operated through its nominal retraction sequence to complete the mating sequence. While this technique can once again be used for the tail end docking portion of the ORM, the initial undocking of the orbiter and ISS vehicles with the assistance of the SRMS has yet to be attempted on orbit. The objective here is to determine the most efficient means to separate or extract the vehicles. Two techniques were analyzed in support of RTF: (1) the 'nominal' demating from the mated interface, and (2) the SRMS performing the operation (either in an active or passive fashion). In the first operation, the demating process would replicate standard undocking operations, with the exception that the SRMS is allowed to arrest the resulting motion. The second operation would be to extend the APAS ring to a ready to dock position, open the capture latches, and then detach the vehicles using the SRMS either actively or passively. In the active case, the APAS ring is extended and latched, and the SRMS is commanded to pull the two interfaces apart (assuming that the effective pull force of the SRMS can overcome the spec values of the combined latch resistance). In the passive case, the SRMS brakes are engaged and the AP AS mechanism is commanded to retract, pulling the two interfaces apart. Since the emphasis of both STS-74 and STS-88 had solely been on the installation operation, as opposed to the separation operation, two new models required development and incorporation within simulation tools designed to analyze those scenarios. These enhancements included: (1) a detailed demating dynamics model to characterize the pusher spring characteristics during undocking, and (2) contact and mechanical system modeling of the back side of the latches to represent unlatching dynamics. This paper first provides an overview of the Monte-Carlo screening analysis for the installation (both nominal and contingency), including the variation of separation distance, misalignment conditions, SRMS joint/brake parameter characteristics, and PRCS jet combinations and corresponding thrust durations. The resulting 'optimum' solution is presented based on trade studies between predicted capture success and integrated system loads. This paper then discusses the upgrades to the APAS math model associated with the new SRMS assisted undocking technique and reviews simulation results for various options investigated for either the active and passive separation of the ISS from the Orbiter.

Space Station Remote Manipulator System↗

A Modular Instrumentation System for NASA's Habitat Demonstration Unit

NASA's human spaceflight program is focused on developing technologies to expand the reaches of human exploration and science activities beyond low earth orbit. A critical aspect of living in space or on planetary surfaces is habitation, which provides a safe and comfortable space in which humans can live and work. NASA is seeking out the best option for habitation by exploring several different concepts through the Habitat Demonstration Unit (HDU) project. The purpose of this HDU is to develop a fully autonomous habitation system that enables human exploration of space. One critical feature of the HDU project that helps to accomplish its mission of autonomy is the instrumentation system that monitors key subsystems operating within a Habitat configuration. The following paper will discuss previous instrumentation systems used in analog habitat concepts and how the current instrumentation system being implemented on the HDU1-PEM, or pressurized excursion module, is building upon the lessons learned of those previous systems. Additionally, this paper will discuss the benefits and the limitations of implementing a wireless sensor network (WSN) as the basis for data transport in the instrumentation system. Finally, this paper will address the experiences and lessons learned with integration, testing prior to deployment, and field testing at the JSC rock yard. NASA is developing the HDU1-PEM as a step towards a fully autonomous habitation system that enables human exploration of space. To accomplish this purpose, the HDU project is focusing on development, integration, testing, and evaluation of habitation systems. The HDU will be used as a technology pull, testbed, and integration environment in which to advance NASA's understanding of alternative mission architectures, requirements, and operations concepts definition and validation. This project is a multi-year effort. In 2010, the HDU1-PEM will be in a pressurized excursion module configuration, and in 2011 the module will be reconfigured for a pressurized core module configuration. Each year the HDU configurations will undergo testing at NASA's Desert Research and Technology Studies (D-RaTS) in Arizona [1]. As part of this project, a modular instrumentation system is developed to meet the monitoring needs of the HDU subsystems and to integrate with the current command and data handling infrastructure that has been developed for the project. The main objective of this study is to provide for the monitoring needs of the HDU. The requirements necessary to meet this objective are developed by working with the subsystem managers of the HDU to understand their monitoring needs. Additionally, the instrumentation system design leverages knowledge and lessons learned from previous studies, such as the inflatable habitat health monitoring system that was deployed in Antarctica [2], the integrated health monitoring system developed for NASA's Microhab [3], and the JSC Lunar Habitat Wireless Testbed to demonstrate a "standardsbased" approach to a wireless instrumentation system [4]. The HDU also requires flexibility in reconfiguration options, and it is necessary to demonstrate and evaluate a modular approach to an instrumentation system. Thus, the instrumentation system is designed in two parts: the primary system employs a standard WSN configuration, and the secondary system employs a wired USB hub. The WSN design provides for reconfiguration or replacement of sensors due to malfunctions or upgrades by using a wireless node that accepts ten instrument inputs and wirelessly transmits the data to the command and data handling system. The USB hub is necessary for those instruments that operate using a wired USB connection, although the design attempts to limit the amount of sensors that need to be wired connections.

Rojdev, Kristina↗

A flexible CAMAC based data system for Space Shuttle scientific instruments

An effort has been made within NASA to produce a low-cost modular system for implementation of Shuttle payloads based on the CAMAC standards for packaging and data transfer. A key element of such a modular system is a means for controlling the data system, collecting and processing the data for transmission to the ground, and issuing commands to the instrument either from the ground or based on the data collected. A description is presented of such a means based on a network of digital processors and CAMAC crate controllers, which allows for the implementation of instruments ranging from those requiring only a single CAMAC crate of functional modules and no data processing to ones requiring multiple crates and multiple data processors.

Ehrmann, C. H.↗

Chemical release module facility

The chemical release module provides the capability to conduct: (1) thermite based metal vapor releases; (2) pressurized gas releases; (3) dispersed liquid releases; (4) shaped charge releases from ejected submodules; and (5) diagnostic measurements with pi supplied instruments. It also provides a basic R-F and electrical system for: (1) receiving and executing commands; (2) telemetering housekeeping data; (3) tracking; (4) monitoring housekeeping and control units; and (5) ultrasafe disarming and control monitoring.

Reasoner, D. L.↗

STS-93 Post Flight Presentation

An overview of Flight STS-93 is presented. The primary objective of the STS-93 mission was to deploy the Advanced X-Ray Astrophysics Facility (AXAF), also known as the Chandra X-ray Observatory. The mission flew on the Columbia Shuttle, on July 22, 1999. This facility is the most sophisticated X-ray observatory ever built. Other payloads on STS-93 were: (1) the Midcourse Space Experiment (MSX), (2) Shuttle Ionospheric Modification with Pulsed Local Exhaust (SIMPLEX), (3) Southwest Ultraviolet Imaging System (SWUIS), (4) Gelation of Sols: Applied Microgravity Research (GOSAMR), Space Tissue Loss-B (STL-B), (5) Light Weight Flexible Solar Array Hinge (LFSAH), (6) Cell Culture Module (CCM), and (7) the Shuttle Amateur Radio Experiment-II (SAREX-II), (8) EarthKam, (9) Plant Growth Investigations in Microgravity (PGIM), (10) Commercial Generic Bioprocessing Apparatus (CGBA), (11) Micro-Electrical Mechanical System (MEMS), and (12) the Biological Research in Canisters (BRIC). The crew was: Eileen M. Collins, Mission Commander, the first female shuttle commander; Jeffrey S. Ashby, Pilot; Steven A. Hawley , Mission Specialist; Catherine G. Coleman, Mission Specialist; Michel Tognini (CNES), Mission Specialist. The video contains views of life aboard the space shuttle. This mission featured both a night launching and a night landing at the Kennedy Space Center.

Source record↗

STS-106 Crew Activities Report/Flight Day 10 Highlights

On this tenth day of the STS-106 Atlantis mission, the flight crew, Commander Commander Terrence W. Wilcutt, Pilot Scott D. Altman, and Mission Specialists Daniel C. Burbank, Edward T. Lu, Richard A. Mastracchio, Yuri Ivanovich Malenchenko, and Boris V. Morukov are shown preparing for their departure from the International Space Station (ISS). Crewmembers are shown closing the hatches of the Zarya, Unity and Zvezda modules. They are also shown packing up trash and packing materials into the Russian Progress ship.

Source record↗

Configurable Multi-Purpose Processor

Advancements in technology have allowed the miniaturization of systems used in aerospace vehicles. This technology is driven by the need for next-generation systems that provide reliable, responsive, and cost-effective range operations while providing increased capabilities such as simultaneous mission support, increased launch trajectories, improved launch, and landing opportunities, etc. Leveraging the newest technologies, the command and telemetry processor (CTP) concept provides for a compact, flexible, and integrated solution for flight command and telemetry systems and range systems. The CTP is a relatively small circuit board that serves as a processing platform for high dynamic, high vibration environments. The CTP can be reconfigured and reprogrammed, allowing it to be adapted for many different applications. The design is centered around a configurable field-programmable gate array (FPGA) device that contains numerous logic cells that can be used to implement traditional integrated circuits. The FPGA contains two PowerPC processors running the Vx-Works real-time operating system and are used to execute software programs specific to each application. The CTP was designed and developed specifically to provide telemetry functions; namely, the command processing, telemetry processing, and GPS metric tracking of a flight vehicle. However, it can be used as a general-purpose processor board to perform numerous functions implemented in either hardware or software using the FPGA s processors and/or logic cells. Functionally, the CTP was designed for range safety applications where it would ultimately become part of a vehicle s flight termination system. Consequently, the major functions of the CTP are to perform the forward link command processing, GPS metric tracking, return link telemetry data processing, error detection and correction, data encryption/ decryption, and initiate flight termination action commands. Also, the CTP had to be designed to survive and operate in a launch environment. Additionally, the CTP was designed to interface with the WFF (Wallops Flight Facility) custom-designed transceiver board which is used in the Low Cost TDRSS Transceiver (LCT2) also developed by WFF. The LCT2 s transceiver board demodulates commands received from the ground via the forward link and sends them to the CTP, where they are processed. The CTP inputs and processes data from the inertial measurement unit (IMU) and the GPS receiver board, generates status data, and then sends the data to the transceiver board where it is modulated and sent to the ground via the return link. Overall, the CTP has combined processing with the ability to interface to a GPS receiver, an IMU, and a pulse code modulation (PCM) communication link, while providing the capability to support common interfaces including Ethernet and serial interfaces boarding a relatively small-sized, lightweight package.

Valencia, J. Emilio↗

ISS GN and C - First Year Surprises

Assembly of the International Space Station (ISS) began in late 1998 with the joining of the first two US and Russ ian elements. For more than two years, the outpost was served by two Russian Guidance, Navigation, and Control (GN&C) systems. The station requires orbital translation and attitude control functions for its 100+ configurations, from the nascent two-module station to the half million kilogram completed station owned and operated by seventeen nations. With the launch of the US Laboratory module in February 2001, the integration of the US GN&C system with its Russian counterpart laid the foundation for such a robust system. In its first year of combined operation, the ISS GN&C system has performed admirably, even better than many expected, but there have been surprises. Loss of command capability, loss of communication between segments, a control system force-fight, and "non-propulsive vents" that weren't - such events have repeatedly underscored the importance of thorough program integration, testing, and operation, both across subsystem boundaries and across international borders.

Begley, Michael↗