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 631 records · Page 35

STS-114 Flight Day 10 Highlights

On Flight Day 10 of the STS-114 mission the International Space Station (ISS) is seen in low lighting while the Space Station Remote Manipulator System (SSRMS), also known as Canadarm 2 grapples the Raffaello Multipurpose Logistics Module (MPLM) in preparation for its undocking the following day. Members of the shuttle crew (Commander Eileen Collins, Pilot James Kelly, Mission Specialists Soichi Noguchi, Stephen Robinson, Andrew Thomas, Wendy Lawrence, and Charles Camarda) and the Expedition 11 crew (Commander Sergei Krikalev and NASA ISS Science Officer and Flight Engineer John Phillips) of the ISS read statements in English and Russian in a ceremony for astronauts who gave their lives. Interview segments include one of Collins, Robinson, and Camarda, wearing red shirts to commemorate the STS-107 Columbia crew, and one of Collins and Noguchi on board the ISS, which features voice over from an interpreter translating questions from the Japanese prime minister. The video also features a segment showing gap fillers on board Discovery after being removed from underneath the orbiter, and another segment which explains an experimental plug for future shuttle repairs being tested onboard the mid deck.

Source record↗

Firmware Architecture of the ARMADAS Bolting Robot

The Automated Reconfigurable Mission Adaptive Digital Assembly Systems (ARMADAS) project, under development at NASA Ames Research Center, has demonstrated on-ground autonomous robotic assembly of extensive digital structures, and it is now moving forward towards in-space demonstration. The ARMADAS system comprises of the operation software, the operation user interface (opsUI), and a swarm of robots. The robotic system consists of a multitude of collaborative agents specifically designed to transport, place and bolt the building blocks, called voxels (volumetric pixels). This paper focuses on the bolting robot, referred to as Mobile Metamaterial Internal Co-Integrator (MMIC-I). MMIC-I is a battery-powered crawling robot. It navigates the structure through extension, contraction and gripping. Two distinct controller boards operate the robot's two symmetric modules, referred to as module A and B. Board A is the master board: it coordinates motion planning and motion primitives execution, hosts the WiFi client, performs periodic self-assessment and system idle check and triggers faults if anomalies are detected. Board B periodically sends a heartbeat to board A, through a wired communication channel that uses the Serial protocol. Additionally, board A's WiFi client receives heartbeat packet requests or motion/bolting commands from a dedicated server board, and acknowledges reception sending back a response heartbeat packet containing information about the overall robot status, e. g. electrical current and voltage values, target and actual angles, operating mode, fault status. Whenever a motion command is sent, the motion planning section of the firmware determines the current robot configuration, using Inertial Measurement Unit readings and the motors Pulse Width Modulation values. Afterwards, it calculates the list of primitives needed to reach the target state, and controls their execution in the proper order. MMIC-I can receive and execute motion and bolting commands only when it is in operational mode. MMIC-I has three operating modes: standby, operational and safed. Standby mode is automatically entered upon startup. While in standby mode, all motors are powered off, and the only accepted commands are the ones relative to a change of mode and heartbeat packet request. Fault detection causes the robot to automatically enter safed or standby mode. Whenever the detected fault occurs within a motion and requires immediate intervention, e. g. an over-current situation, the robot enters safed mode. Safed mode powers off all motors except for the locomotion module, thus preventing the robot from collapsing. Conversely, when the detected fault doesn't require immediate intervention (low battery warning, for instance), the robot enters standby mode after completing the ongoing motion. This paper provides a detailed discussion of MMIC-I's firmware architecture. It accurately describes the implementation approach for each module: sensor data reading, motor control and actuation, WiFi server-client communication, intra-boards Serial communication, operating modes and autonomous fault detection, motion planning, coordination and execution, etc. Moreover, in support of the software description, this paper includes a thorough characterization of MMIC-I's hardware and avionics.

In-space assembly↗

Updates on HRF Payloads Operations in Columbus ATCS

The NASA developed Human Research Facility 1 (HRF1) and Human Research Facility (HRF2) experiment racks have been operating in the European Space Agency (ESA) Columbus module of the International Space Station (ISS) since Summer 2008. The two racks are of the same design. Since the start of operations, unexpected pressure spikes were observed in the Columbus module's thermal-hydraulic system during the racks activation sequence. The root cause of these spikes was identified in the activation command sequence in the Rack Interface Controller (RIC), which controls the flow of thermal-hydraulic system fluid through the rack. A new Common RIC Software (CRS) release fixed the bug and was uploaded on both racks in late 2009. This paper gives a short introduction to the topic, describes the Columbus module countermeasures to mitigate the spikes, describes the ground validation test of the new software, and describes the flight checks performed before and after the final upload. Finally, the new on-orbit test designed to further simplify the racks hydraulic management is presented.

DePalo, Savino↗

Update on Rover Sequencing and Visualization Program

The Rover Sequencing and Visualization Program (RSVP) has been updated. RSVP was reported in Rover Sequencing and Visualization Program (NPO-30845), NASA Tech Briefs, Vol. 29, No. 4 (April 2005), page 38. To recapitulate: The Rover Sequencing and Visualization Program (RSVP) is the software tool to be used in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (robotic arm) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities.

Cooper, Brian↗

International Space Station (ISS) Payload Autonomous Operations Past, Present and Future

Draper Laboratorys Timeliner is a scripting and automation system that runs onboard computers in the International Space Station (ISS). Timeliner is fully integrated with ISS and can be used to automate ISS operations tasks. Some of the most challenging aspects of operating a payload in low earth orbit are communication delays, ground equipment failures, and human errors. How does a Payload Developer (PD) know their equipment is operating nominally and collecting science in the most efficient way possible or even powered at any given time? During a ground Loss of Signal (LOS) data outage, PDs have no insight into their experiments state, and benefit greatly from Timeliner scripts executing on ISS to perform telemetry monitoring and commanding operations. This paper will discuss current software designs, and new operational uses for Timeliner. Existing Timeliner capabilities discussed will include: autonomous EXPRESS Rack activation and deactivation; autonomous science data downlinks; Minus Eighty Degree Freezer (MELFI) Dewar autonomous safing; JAXA and ESA module autonomous payload facility safing; as well as many others. New operational concepts discussed will include allowing Timeliner on the payload computer to issue core commands (Thermal, Power, Fire Detection), creation of new ground tools that will monitor the current status of Payload Racks as well as all the messaging from autonomous scripts executing, decreasing approval time for Timeliner bundles, and opening up the Payload MDM Enhanced Processor Integrated Communications Card (EPIC) interface. The EPIC interface could provide a new crew interface for PL Timeliner execution. The new interface could operate on either a Payload Computer System (PCS) or a Station Support Computer (SSC) that is plugged into either the Payload LAN or the Operations LAN which will make communicating to the PL MDM more flexible and greatly increase band width for communication.

Space Mission Automation↗

Electrical Pressurization Concept for the Orion MPCV European Service Module Propulsion System

The paper presents the design of the pressurization system of the European Service Module (ESM) of the Orion Multi-Purpose Crew Vehicle (MPCV). Being part of the propulsion subsystem, an electrical pressurization concept is implemented to condition propellants according to the engine needs via a bang-bang regulation system. Separate pressurization for the oxidizer and the fuel tank permits mixture ratio adjustments and prevents vapor mixing of the two hypergolic propellants during nominal operation. In case of loss of pressurization capability of a single side, the system can be converted into a common pressurization system. The regulation concept is based on evaluation of a set of tank pressure sensors and according activation of regulation valves, based on a single-failure tolerant weighting of three pressure signals. While regulation is performed on ESM level, commanding of regulation parameters as well as failure detection, isolation and recovery is performed from within the Crew Module, developed by Lockheed Martin Space System Company. The overall design and development maturity presented is post Preliminary Design Review (PDR) and reflects the current status of the MPCV ESM pressurization system.

Helium↗

Optimal control of the Shuttle-Tethered-Subsatellite system

Alternate control laws based on an application of the linear regulator problem are developed for possible use in the operation of the Shuttle-Tethered-Subsatellite system. Control is assumed to be provided only by modulating the tension level in the tether as a function of the difference between actual and commanded tether line length, length rate, in (orbital) plane swing angle and swing angle rate. Necessary and sufficient conditions for stability of the (linear) system motion in the vicinity of its nominal local vertical orientation are developed. By proper selection of the state and control penalty matrices it is possible to obtain faster responses with no increase in maximum power levels for use in station keeping when compared with alternate control strategies. The weighting matrices are adjusted in a piecewise adaptive manner to provide control law gains in order to achieve a smooth deployment history. Successful retrieval is dependent mainly on the initial conditions and the rate at which the commanded length is reduced.

Bainum, P. M.↗

An adaptive guidance algorithm for an aerodynamically assisted orbital plane change maneuver

Using analysis results from the post trajectory optimization program, an adaptive guidance algorithm is developed to compensate for density, aerodynamic and thrust perturbations during an atmospheric orbital plane change maneuver. The maneuver offers increased mission flexibility along with potential fuel savings for future reentry vehicles. Although designed to guide a proposed NASA Entry Research Vehicle, the algorithm is sufficiently generic for a range of future entry vehicles. The plane change analysis provides insight suggesting a straight-forward algorithm based on an optimized nominal command profile. Bank angle, angle of attack, and engine thrust level, ignition and cutoff times are modulated to adjust the vehicle's trajectory to achieve the desired end-conditions. A performance evaluation of the scheme demonstrates a capability to guide to within 0.05 degrees of the desired plane change and five nautical miles of the desired apogee altitude while maintaining heating constraints. The algorithm is tested under off-nominal conditions of + or -30% density biases, two density profile models, + or -15% aerodynamic uncertainty, and a 33% thrust loss and for various combinations of these conditions.

Blissit, J. A.↗

Design and application of electromechanical actuators for deep space missions

The annual report Design and Application of Electromechanical Actuators for Deep Space Missions is presented. The reporting period is 16 Aug. 1992 to 15 Aug. 1993. However, the primary focus will be work performed since submission of our semi-annual progress report in Feb. 1993. Substantial progress was made. We currently feel confident in providing guidelines for motor and control strategy selection in electromechanical actuators to be used in thrust vector control (TVC) applications. A small portion was presented in the semi-annual report. At this point, we have implemented highly detailed simulations of various motor/drive systems. The primary motor candidates were the brushless dc machine, permanent magnet synchronous machine, and the induction machine. The primary control implementations were pulse width modulation and hysteresis current control. Each of the two control strategies were applied to each of the three motor choices. With either pulse width modulation or hysteresis current control, the induction machine was always vector controlled. A standard test position command sequence for system performance evaluation is defined. Currently, we are gathering all of the necessary data for formal presentation of the results. Briefly stated for TVC application, we feel that the brushless dc machine operating under PWM current control is the best option. Substantial details on the topic, with supporting simulation results, will be provided later, in the form of a technical paper prepared for submission and also in the next progress report with more detail than allowed for paper publication.

Haskew, Tim A.↗

Modeling ESA's TT/C systems

After a brief introduction on the need for simulation packages for the analysis and design of satellite communications systems, the software tool developed for the European Space Agency (ESA), its main objectives and the design choices made during the development are presented. A very concise description of the available communications and measurement block follows. The ESA standard Telemetry, Tracking and Command (TT&C) system simulator is then introduced along with a description of the ESA standard modulation and coding schemes. As an example, the simulation of the ranging system which is a non-standard communications block, is described in details. Several examples of TT&C simulations outputs are given and compared with measurement results or theoretical approximations, when available. Finally, future developments like the support of advanced modulation schemes and the dynamic satellite link simulation are presented.

Vassallo, Enrico↗

STS-108 Flight Day 3 Highlights

On this third day of the STS-108 mission, the Endeavour Orbiter is seen docking with the International Space Station. The crew of STS-108 (Commander Dominic Gorie, Pilot Mark Kelly, and Mission Specialists Linda Godwin and Daniel Tani) and Expedition 4 (Commander Yuri Onufrienko and Flight Engineers Carl Walz and Daniel Bursch) greet the Expedition 3 crew (Commander Frank Culbertson, Jr. and Flight Engineers Mikhail Turin and Vladimir Dezhurov) in the Destiny Laboratory Module.

Source record↗

STS-108 Mission Highlights Resource Tape

This video is a continuation of 'STS-108 Mission Highlights Resource Tape: Part 1 of 3' (Internal ID 2002049331). Flight day four footage continues with a video tour of the International Space Station (ISS). During flight day five, an exterior view of the Multipurpose Logistics Module (MPLM) is seen, followed by the crew unloading the supplies and equipment from the MPLM. Commander Dominic Gorie and Mission Specialist Linda Godwin are seen making preparations for the Extravehicular Activity (EVA) scheduled for the following day. Footage of an exterior view of the ISS is also shown. Flight day six footage includes Godwin and Mission Specialist Daniel Tani suiting up for their EVA and the installation of thermal blankets around the solar array wings of the ISS. Expedition 3 Commander Frank Culbertson is seen working in the ISS laboratory during flight day seven. Views are shown of Saudi Arabia and the Red Sea, the western coast of Australia, Cuba and Florida, and Switzerland and Northern Italy. During flight day eight, the crew is seen stowing objects in the MPLM for return to earth. The video concludes with footage of the treadmill used by the astronauts for physical exercise. Flight days nine through twelve are included in 'STS-108 Mission Highlights Resource Tape: Part 3 of 3' (Internal ID 2002049329).

Source record↗

Orion MPCV GN and C End-to-End Phasing Tests

End-to-end integration tests are critical risk reduction efforts for any complex vehicle. Phasing tests are an end-to-end integrated test that validates system directional phasing (polarity) from sensor measurement through software algorithms to end effector response. Phasing tests are typically performed on a fully integrated and assembled flight vehicle where sensors are stimulated by moving the vehicle and the effectors are observed for proper polarity. Orion Multi-Purpose Crew Vehicle (MPCV) Pad Abort 1 (PA-1) Phasing Test was conducted from inertial measurement to Launch Abort System (LAS). Orion Exploration Flight Test 1 (EFT-1) has two end-to-end phasing tests planned. The first test from inertial measurement to Crew Module (CM) reaction control system thrusters uses navigation and flight control system software algorithms to process commands. The second test from inertial measurement to CM S-Band Phased Array Antenna (PAA) uses navigation and communication system software algorithms to process commands. Future Orion flights include Ascent Abort Flight Test 2 (AA-2) and Exploration Mission 1 (EM-1). These flights will include additional or updated sensors, software algorithms and effectors. This paper will explore the implementation of end-to-end phasing tests on a flight vehicle which has many constraints, trade-offs and compromises. Orion PA-1 Phasing Test was conducted at White Sands Missile Range (WSMR) from March 4-6, 2010. This test decreased the risk of mission failure by demonstrating proper flight control system polarity. Demonstration was achieved by stimulating the primary navigation sensor, processing sensor data to commands and viewing propulsion response. PA-1 primary navigation sensor was a Space Integrated Inertial Navigation System (INS) and Global Positioning System (GPS) (SIGI) which has onboard processing, INS (3 accelerometers and 3 rate gyros) and no GPS receiver. SIGI data was processed by GN&C software into thrust magnitude and direction commands. The processing changes through three phases of powered flight: pitchover, downrange and reorientation. The primary inputs to GN&C are attitude position, attitude rates, angle of attack (AOA) and angle of sideslip (AOS). Pitch and yaw attitude and attitude rate responses were verified by using a flight spare SIGI mounted to a 2-axis rate table. AOA and AOS responses were verified by using a data recorded from SIGI movements on a robotic arm located at NASA Johnson Space Center. The data was consolidated and used in an open-loop data input to the SIGI. Propulsion was the Launch Abort System (LAS) Attitude Control Motor (ACM) which consisted of a solid motor with 8 nozzles. Each nozzle has active thrust control by varying throat area with a pintle. LAS ACM pintles are observable through optically transparent nozzle covers. SIGI movements on robot arm, SIGI rate table movements and LAS ACM pintle responses were video recorded as test artifacts for analysis and evaluation. The PA-1 Phasing Test design was determined based on test performance requirements, operational restrictions and EGSE capabilities. This development progressed during different stages. For convenience these development stages are initial, working group, tiger team, Engineering Review Team (ERT) and final.

Neumann, Brian C.↗

Rover Sequencing and Visualization Program

The Rover Sequencing and Visualization Program (RSVP) is the software tool for use in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight-code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover-predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (IDD) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities. Thus, RSVP, being highly data driven, may be tailored to other missions with minimal effort. In addition, RSVP uses a distributed, message-passing architecture to allow multitasking, and collaborative visualization and sequence development by scattered team members.

Cooper, Brian↗

Comparison of bit synchronization schemes using AM and summed clocks

This paper considers bit synchronization through the use of a separate clock signal which is either amplitude modulated onto or summed with the data signal. For continuous data transmission, such schemes are known to be inferior, in the sense of efficient use of power, to schemes which derive synchronization directly from the data signal. However, these techniques have application in burst systems such as spacecraft command systems, and in systems where receiver simplicity is more important than power conservation. For systems in which the composite data-clock signal subsequently modulates an RF carrier, it is shown that the summed clock signal performs slightly better than the AM clock signal, and that for both signal types, the optimum allocation of power between data and clock is approximately 9:1.

Geist, J. M.↗

Apollo 15 and 16 ground-commanded television assembly.

During the Apollo 15 and 16 missions, a special camera provided the scientific community and the home viewer with real-time coverage of the lunar exploration. The lunar blast-off of the Apollo 16 ascent module was tracked by the mission controller at NASA's Manned Space Center and watched 250,000 miles away on earth. The operation of this television camera and the remote control unit are described and block diagrams given. Ground-command capability from the Mission Control Center permitted versatility and optimization of the TV coverage, without diverting the astronauts from their primary role of lunar exploration.

Soltoff, B. M.↗

Design of power electronics for TVC EMA systems

The Composite Development Division of the Propulsion Laboratory at Marshall Space Flight Center (MSFC) is currently developing a class of electromechanical actuators (EMA's) for use in space transportation applications such as thrust vector control (TVC) and propellant control valves (PCV). These high power servomechanisms will require rugged, reliable, and compact power electronic modules capable of modulating several hundred amperes of current at up to 270 volts. MSFC has selected the brushless dc motor for implementation in EMA's. This report presents the results of an investigation into the applicability of two new technologies, MOS-controlled thyristors (MCT's) and pulse density modulation (PDM), to the control of brushless dc motors in EMA systems. MCT's are new power semiconductor devices, which combine the high voltage and current capabilities of conventional thyristors and the low gate drive requirements of metal oxide semiconductor field effect transistors (MOSFET's). The commanded signals in a PDM system are synthesized using a series of sinusoidal pulses instead of a series of square pulses as in a pulse width modulation (PWM) system. A resonant dc link inverter is employed to generate the sinusoidal pulses in the PDM system. This inverter permits zero-voltage switching of all semiconductors which reduces switching losses and switching stresses. The objectives of this project are to develop and validate an analytical model of the MCT device when used in high power motor control applications and to design, fabricate, and test a prototype electronic circuit employing both MCT and PDM technology for controlling a brushless dc motor.

Nelms, R. Mark↗

A spacecraft computer repairable via command.

The MULTIPAC is a central data system developed for deep-space probes with the distinctive feature that it may be repaired during flight via command and telemetry links by reprogramming around the failed unit. The computer organization uses pools of identical modules which the program organizes into one or more computers called processors. The interaction of these modules is dynamically controlled by the program rather than hardware. In the event of a failure, new programs are entered which reorganize the central data system with a somewhat reduced total processing capability aboard the spacecraft. Emphasis is placed on the evolution of the system architecture and the final overall system design rather than the specific logic design.

Fimmel, R. O.↗