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 541 records · Page 30

Rapid Lightweight Firmware Architecture of the Mobile Metamaterial Internal Co-Integrator Robot

The Mobile Metamaterial Internal Co-Integrator (MMIC-I) is a structure assembly and servicing robot for in-space servicing, assembly, and manufacturing of primary structures and infrastructure. MMIC-I is a battery-powered crawling robot that can travel through periodic structures such as trusses and open framework mechanical metamaterials. It does this through sequences of component extension, contraction, and gripping. This paper provides a detailed discussion of MMIC-I’s lightweight and rapidly developed firmware architecture, to enable demonstration of robot locomotion, secondary operations, and communications with a central command source. The rationale for the lightweight rapid development approach is to allow for assessment of long term system requirements in parallel with the mechatronics development, including optimization of system and subsystem power densities, to inform a future choice of flight ready software frameworks. MMIC-I system computing and I/O requirements are much lower than what is provided by proven baseline computing hardware for existing flight ready software frameworks such as the core Flight System, F prime, and the Robot Operating System. Development of earth gravity ground demonstration of the robotic systems is greatly benefited by limited power and mass factors for computing hardware. Here, we implement inter-process communication, commanding, and telemetry with the Espressif ESP32 module running the Arduino OS.

Damiana Catanoso↗

YADA: Yet Another Distributed Architecture for Real-Time Robotic Control Systems

This paper presents YADA, a new software architecture for real-time robotic control systems that is minimal, modular, and fully transparent. YADA divides control software into decoupled behavior, user-interface, and hardware-level bus modules. This decoupling at the module level is accomplished by auto-generating human-readable message types that are tailored to the hardware topology oft he current system. These message types provide modules with a common framework for exchanging state information and relaying commands to devices while being agnostic to the communication protocol itself. We also detail how to structure behavior and bus modules to facilitate modularity and flexibility with third party software. YADA has been used with success on several technology development testbeds at JPL, an example of which is given in this paper, and has proven to provide developers a light-weight and highly reconfigurable system for efficient debugging and practical code sharing

Godart, Peter↗

Power User Interface

Power User Interface 5.0 (PUI) is a system of middleware, written for expert users in the Earth-science community, PUI enables expedited ordering of data granules on the basis of specific granule-identifying information that the users already know or can assemble. PUI also enables expert users to perform quick searches for orderablegranule information for use in preparing orders. PUI 5.0 is available in two versions (note: PUI 6.0 has command-line mode only): a Web-based application program and a UNIX command-line- mode client program. Both versions include modules that perform data-granule-ordering functions in conjunction with external systems. The Web-based version works with Earth Observing System Clearing House (ECHO) metadata catalog and order-entry services and with an open-source order-service broker server component, called the Mercury Shopping Cart, that is provided separately by Oak Ridge National Laboratory through the Department of Energy. The command-line version works with the ECHO metadata and order-entry process service. Both versions of PUI ultimately use ECHO to process an order to be sent to a data provider. Ordered data are provided through means outside the PUI software system.

Pfister, Robin↗

Command and telemetry systems

The command and telemetry portions of the Telstar system provide necessary support functions for the basic communications experiment and the radiation experiment. By means of the command system, the states of 9 magnetic latching relays in the satellite are controlled from the ground. Commands are sent to the satellite by coded signals modulated on a carrier in the VHF band. The telemetry system also uses a VHF carrier to transmit encoded information from the satellite. Data on 112 items are provided once each minute. This paper discusses the over-all command and telemetry systems and considers the general objectives, system aspects and detailed implementation.

TELEMETRY↗

The Software Design for the Wide-Field Infrared Explorer Attitude Control System

The Wide-Field Infrared Explorer (WIRE), currently scheduled for launch in September 1998, is the fifth of five spacecraft in the NASA/Goddard Small Explorer (SMEX) series. This paper presents the design of WIRE's Attitude Control System flight software (ACS FSW). WIRE is a momentum-biased, three-axis stabilized stellar pointer which provides high-accuracy pointing and autonomous acquisition for eight to ten stellar targets per orbit. WIRE's short mission life and limited cryogen supply motivate requirements for Sun and Earth avoidance constraints which are designed to prevent catastrophic instrument damage and to minimize the heat load on the cryostat. The FSW implements autonomous fault detection and handling (FDH) to enforce these instrument constraints and to perform several other checks which insure the safety of the spacecraft. The ACS FSW implements modules for sensor data processing, attitude determination, attitude control, guide star acquisition, actuator command generation, command/telemetry processing, and FDH. These software components are integrated with a hierarchical control mode managing module that dictates which software components are currently active. The lowest mode in the hierarchy is the 'safest' one, in the sense that it utilizes a minimal complement of sensors and actuators to keep the spacecraft in a stable configuration (power and pointing constraints are maintained). As higher modes in the hierarchy are achieved, the various software functions are activated by the mode manager, and an increasing level of attitude control accuracy is provided. If FDH detects a constraint violation or other anomaly, it triggers a safing transition to a lower control mode. The WIRE ACS FSW satisfies all target acquisition and pointing accuracy requirements, enforces all pointing constraints, provides the ground with a simple means for reconfiguring the system via table load, and meets all the demands of its real-time embedded environment (16 MHz Intel 80386 processor with 80387 coprocessor running under the VRTX operating system). The mode manager organizes and controls all the software modules used to accomplish these goals, and in particular, the FDH module is tightly coupled with the mode manager.

Anderson, Mark O.↗

Space vehicle onboard command encoder

A flexible onboard encoder system was designed for the space shuttle. The following areas were covered: (1) implementation of the encoder design into hardware to demonstrate the various encoding algorithms/code formats, (2) modulation techniques in a single hardware package to maintain comparable reliability and link integrity of the existing link systems and to integrate the various techniques into a single design using current technology. The primary function of the command encoder is to accept input commands, generated either locally onboard the space shuttle or remotely from the ground, format and encode the commands in accordance with the payload input requirements and appropriately modulate a subcarrier for transmission by the baseband RF modulator. The following information was provided: command encoder system design, brassboard hardware design, test set hardware and system packaging, and software.

Source record↗

Space experiments with particle accelerators

The purpose of space experiments with particle accelerators (SEPAC) is to carry out active and interactive experiments on and in the Earth's ionosphere and magnetosphere. It is also intended to make an initial performance test for an overall program of Spacelab/SEPAC experiments. The instruments to be used are an electron beam accelerator, magnetoplasma dynamic arcjet, and associated diagnostic equipment. The accelerators are installed on the pallet, with monitoring and diagnostic observations being made by the gas plume release, beam-monitor TV, and particle-wave measuring instruments also mounted on the pallet. Command and display systems are installed in the module. Three major classes of investigations to be performed are vehicle charge neutralization, beam plasma physics, and beam atmosphere interactions. The first two are mainly onboard plasma physics experiments to measure the effect of phenomena in the vicinity of Spacelab. The last one is concerned with atmospheric modification and is supported by other Spacelab 1 investigations as well as by ground-based, remote sensing observations.

Obayashi, T.↗

NASA Goddard Space Flight Center Robotic Processing System Program Automation Systems, volume 2

Topics related to robot operated materials processing in space (RoMPS) are presented in view graph form. Some of the areas covered include: (1) mission requirements; (2) automation management system; (3) Space Transportation System (STS) Hitchhicker Payload; (4) Spacecraft Command Language (SCL) scripts; (5) SCL software components; (6) RoMPS EasyLab Command & Variable summary for rack stations and annealer module; (7) support electronics assembly; (8) SCL uplink packet definition; (9) SC-4 EasyLab System Memory Map; (10) Servo Axis Control Logic Suppliers; and (11) annealing oven control subsystem.

Dobbs, M. E.↗

Space Applications Industrial Laser System (SAILS)

A program is underway to develop a YAG laser based materials processing workstation to fly in the cargo bay of the Space Shuttle. This workstation, called Space Applications Industrial Laser System (SAILS), will be capable of cutting and welding steel, aluminum, and Inconel alloys of the type planned for use in constructing the Space Station Freedom. As well as demonstrating the ability of a YAG laser to perform remote (fiber-optic delivered) repair and fabrication operations in space, fundamental data will be collected on these interactions for comparison with terrestrial data and models. The flight system, scheduled to fly in 1996, will be constructed as three modules using standard Get-Away-Special (GAS) canisters. The first module holds the laser head and cooling system, while the second contains a high peak power electrical supply. The third module houses the materials processing workstation and the command and data acquisition subsystems. The laser head and workstation cansisters are linked by a fiber-optic cable to transmit the laser light. The team assembled to carry out this project includes Lumonics Industrial Products (laser), Tennessee Technological University (structural analysis and fabrication), Auburn University Center for Space Power (electrical engineering), University of Waterloo (low-g laser process consulting), and CSTAR/UTSI (data acquisition, control, software, integration, experiment design). This report describes the SAILS program and highlights recent activities undertaken at CSTAR.

Mccay, T. D.↗

STS-105 Flight Day 3 Highlights

On this third day of the STS-105 mission, footage shows Discovery docking with the International Space Station (ISS). The Expedition 2 crewmembers, Yuriy Usachev, James Voss, and Susan Helms, are seen as they work in the Destiny Laboratory Module on the ISS. The STS-105 crew (Commander Scott Horowitz, Pilot Frederick Sturckow, and Mission Specialists Daniel Barry and Patrick Forrester), Expedition 2 crew, and Expedition 3 crew (Frank Culbertson, Jr., Mikhail Turin, and Vladimir Dezhurov) are seen as the connecting hatches are opened between the ISS and Discovery and the crews meet.

Source record↗

STS-105 Flight Day 8 Highlights

On this eighth day of the STS-105 mission, Expedition 2 crewmember Susan Helms and Expedition 3 crewmember Vladimir Dezhurov are seen working in the Destiny Laboratory Module. The three crews gather (STS-105 crew Commander Scott Horowitz, Pilot Fred Sturckow, and Mission Specialists Dan Barry and Pat Forrester, Expedition 2 crew Commander Yuriy Usachev and Flight Engineers James Voss and Susan Helms, and Expedition 3 crew Frank Culbertson, Jr., Mikhail Turin, and Vladimir Dezhurov) for the change of command ceremony, where the Expedition 3 crew officially takes control of the International Space Station from the Expedition 2 crew, and the three crews answer questions about the mission in an on-orbit interview. Footage shows Hawaii from space.

Source record↗

Development of Poincare Software to Predict Arrythmias

The most distressing types of heart malfunction occur because of an abnormal rhythm of the heart. Cardiac arrythmias can be caused by abnormal rhythmicity of the pacemaker, electrolyte disturbances, blockage of the transmission of the electric impulse through the heart, and other abnormalities. There is strong evidence that space flight is associated with decreased cardiac electrical stability that may pose a life threatening risk to astronauts. For example, during the Skylab missions, a crewmember had a five beat run of ventricular tachycardia during lower body negative pressure. Also, analysis of nine 24-hour Holter monitor recordings obtained during long term spaceflight on Mir revealed one 14-beat run of ventricular tachycardia. A Mir cosmonaut was replaced in 1986 because of cardiac dysrhythmias. Most recently, in July of 1997, a Mir commander was unable to participate in the Spektr module repair due to complaints of an irregular heart rhythm. Despite these examples, possible mechanisms of arrhythmias and countermeasure strategies have barely been addressed. The Poincare method has been proposed as a technique that might potentially predict life-threatening arrhythmias before they occur. According to this method, each RR interval obtained from an EKG recording is plotted sequentially vs. the previous RR interval. Several studies using the method have demonstrated a strong correlation between the shape of the Poincare plot and ventricular arrhythmia. Our purpose was to develop an automated software program that detects the R peaks from an EKG recording while simultaneously displaying the Poincare plot and other related parameters.

Maaliki, Samer↗

PPC750 Performance Monitor

The PPC750 Performance Monitor (Perfmon) is a computer program that helps the user to assess the performance characteristics of application programs running under the Wind River VxWorks real-time operating system on a PPC750 computer. Perfmon generates a user-friendly interface and collects performance data by use of performance registers provided by the PPC750 architecture. It processes and presents run-time statistics on a per-task basis over a repeating time interval (typically, several seconds or minutes) specified by the user. When the Perfmon software module is loaded with the user s software modules, it is available for use through Perfmon commands, without any modification of the user s code and at negligible performance penalty. Per-task run-time performance data made available by Perfmon include percentage time, number of instructions executed per unit time, dispatch ratio, stack high water mark, and level-1 instruction and data cache miss rates. The performance data are written to a file specified by the user or to the serial port of the computer

Meyer, Donald↗

CoNNeCT Baseband Processor Module Boot Code SoftWare (BCSW)

This software provides essential startup and initialization routines for the CoNNeCT baseband processor module (BPM) hardware upon power-up. A command and data handling (C&DH) interface is provided via 1553 and diagnostic serial interfaces to invoke operational, reconfiguration, and test commands within the code. The BCSW has features unique to the hardware it is responsible for managing. In this case, the CoNNeCT BPM is configured with an updated CPU (Atmel AT697 SPARC processor) and a unique set of memory and I/O peripherals that require customized software to operate. These features include configuration of new AT697 registers, interfacing to a new HouseKeeper with a flash controller interface, a new dual Xilinx configuration/scrub interface, and an updated 1553 remote terminal (RT) core. The BCSW is intended to provide a "safe" mode for the BPM when initially powered on or when an unexpected trap occurs, causing the processor to reset. The BCSW allows the 1553 bus controller in the spacecraft or payload controller to operate the BPM over 1553 to upload code; upload Xilinx bit files; perform rudimentary tests; read, write, and copy the non-volatile flash memory; and configure the Xilinx interface. Commands also exist over 1553 to cause the CPU to jump or call a specified address to begin execution of user-supplied code. This may be in the form of a real-time operating system, test routine, or specific application code to run on the BPM.

Yamamoto, Clifford K.↗

Display of Flight Interval Management Data

A system for providing flight interval management (FIM) instructions to a pilot of an aircraft includes a module coupled to a display device and configured to communicate with a FIM avionics device. The module generates a first output when input data from the FIM avionics device indicates that the aircraft is within 30 nautical miles of another aircraft, and a second input when a lack of valid input data indicates that the module has lost connectivity to the FIM avionics device. The first input is to the display device to present at least an indication of a paired mode of the module with the FIM avionics device, and a commanded speed reported by the FIM avionics device. The second output is to remove any information presented by the display device and present a blank screen, and then present a status message indicating the lost connectivity to the FIM avionics device.

Wilber, George↗

Gateway Command and Data Handling Network Implementation and Validation

As initial Lunar Gateway modules approach design maturity, the Artemis Network Validation and Integration Lab (ANVIL) has begun demonstrations to validate avionics network dataflows. The flight architecture design includes utilizing Time-Triggered Ethernet (TTE) and layer-3 switching capabilities to enable greater automation and flexibility of critical and best effort traffic. Critical traffic is considered as Time-Triggered (TT), Rate Constrained (RC) and prioritized Best Effort (BE) traffic classes. End systems, such as mission computers, power control, and robotics, use three planes and all traffic classes while other devices interface via Best Effort. Typical best effort devices include video, laptops, wireless access points, and payloads. Other devices have a various hybrid approach of interfaces including alarms, telemetry/logging, and communication units. In the paper, we will present an update of the Gateway network architecture and how the system will operate nominally and during a stack topology reconfiguration. We will also discuss the network risks, and trade-offs of performance, flexibility, and redundancy. Finally, we will show the process for validation, demonstration, and verification approaches to the vehicle network.

Gateway↗