Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 559 records · Page 31

Cyber Framework for Steering and Measurements Collection Over Instrument-Computing Ecosystems

We propose a framework to develop cyber solutions to support the remote steering of science instruments and measurements collection over instrument-computing ecosystems. It is based on provisioning separate data and control connections at the network level, and developing software modules consisting of Python wrappers for instrument commands and Pyro server-client codes that make them available across the ecosystem network. We demonstrate automated measurement transfers and remote steering operations in a microscopy use case for materials research over an ecosystem of Nion microscopes and computing platforms connected over site networks. The proposed framework is currently under further refinement and being adopted to science workflows with automated remote experiments steering for autonomous chemistry laboratories and smart energy grid simulations.

Al Najjar, Anees↗

Integrated source and channel encoded digital communications system design study

Studies on the digital communication system for the direct communication links from ground to space shuttle and the links involving the Tracking and Data Relay Satellite (TDRS). Three main tasks were performed:(1) Channel encoding/decoding parameter optimization for forward and reverse TDRS links,(2)integration of command encoding/decoding and channel encoding/decoding; and (3) modulation coding interface study. The general communication environment is presented to provide the necessary background for the tasks and to provide an understanding of the implications of the results of the studies.

Huth, G. K.↗

Autonomy Architectures for a Constellation of Spacecraft

Until the past few years, missions typically involved fairly large expensive spacecraft. Such missions have primarily favored using older proven technologies over more recently developed ones, and humans controlled spacecraft by manually generating detailed command sequences with low-level tools and then transmitting the sequences for subsequent execution on a spacecraft controller. This approach toward controlling a spacecraft has worked spectacularly on previous missions, but it has limitations deriving from communications restrictions - scheduling time to communicate with a particular spacecraft involves competing with other projects due to the limited number of deep space network antennae. This implies that a spacecraft can spend a long time just waiting whenever a command sequence fails. This is one reason why the New Millennium program has an objective to migrate parts of mission control tasks onboard a spacecraft to reduce wait time by making spacecraft more robust. The migrated software is called a "remote agent" and has 4 components: a mission manager to generate the high level goals, a planner/scheduler to turn goals into activities while reasoning about future expected situations, an executive/diagnostics engine to initiate and maintain activities while interpreting sensed events by reasoning about past and present situations, and a conventional real-time subsystem to interface with the spacecraft to implement an activity's primitive actions. In addition to needing remote planning and execution for isolated spacecraft, a trend toward multiple-spacecraft missions points to the need for remote distributed planning and execution. The past few years have seen missions with growing numbers of probes. Pathfinder has its rover (Sojourner), Cassini has its lander (Huygens), and the New Millenium Deep Space 3 (DS3) proposal involves a constellation of 3 spacecraft for interferometric mapping. This trend is expected to continue to progressively larger fleets. For example, one mission proposed to succeed DS3 would have 18 spacecraft flying in formation in order to detect earth-sized planets orbiting other stars. A proposed magnetospheric constellation would involve 5 to 500 spacecraft in Earth orbit to measure global phenomena within the magnetosphere. This work describes and compares three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals or command sequences for each spacecraft. A fleet of self-commanding spacecraft would autonomously coordinate itself to satisfy high level science and engineering goals in a changing partially-understood environment making feasible the operation of tens or even a hundred spacecraft (such as for interferometry or plasma physics missions). The easiest way to adapt autonomous spacecraft research to controlling constellations involves treating the constellation as a single spacecraft. Here one spacecraft directly controls the others as if they were connected. The controlling "master" spacecraft performs all autonomy reasoning, and the slaves only have real-time subsystems to execute the master's commands and transmit local telemetry/observations. The executive/diagnostics module starts actions and the master's real-time subsystem controls the action either locally or remotely through a slave. While the master/slave approach benefits from conceptual simplicity, it relies on an assumption that the master spacecraft's executive can continuously monitor the slaves' real-time subsystems, and this relies on high-bandwidth highly-reliable communications. Since unintended results occur fairly rarely, one way to relax the bandwidth requirements involves only monitoring unexpected events in spacecraft. Unfortunately, this disables the ability to monitor for unexpected events between spacecraft and leads to a host of coordination problems among the slaves. Also, failures in the communications system can result in losing slaves. The other two architectures improve robustness while reducing communications by progressively distributing more of the other three remote agent components across the constellation. In a teamwork architecture, all spacecraft have executives and real-time subsystems - only the leader has the planner/scheduler and mission manager. Finally, distributing all remote agent components leads to a peer-to-peer approach toward constellation control.

Barrett, Anthony↗

STS-98 Crew Activity Report/Flight Day 9 Highlights

On this ninth day of the STS-98 mission, Expedition 1 crewmember Bill Shepherd gives a tour of the Density Laboratory Module, describing the equipment and functions. Mission Specialists Bob Curbeam and Tom Jones answer questions about their spacewalks and the Destiny Module. The rest of the Atlantis crew (Commander Kenneth D. Cockrell, Pilot Mark L. Polansky, and Mission Specialist Marsha S. Ivins) and the Expedition 1 crew (William M. Shepherd, Yuri P. Gidzenko, and Sergei K. Krikalev) join Curbeam and Jones to answer questions about the mission.

Source record↗

STS-102 Crew Activity Report/Flight Day 9 Highlights

On this ninth day of the STS-102 mission, three crews are on the International Space Station: (1) STS-102 (Commander James Wetherbee, Pilot James Kelly, and Mission Specialists Andrew Thomas and Paul Richards); (1) Expedition 1 (William Shepherd, Yuri Gidzenko, and Sergei Krikalev); and (3) Expedition 2 (James Voss, Susan Helms, and Yuriy Usachev). Mission Specialist Thomas, Commander Shepherd, and Commander Usachev are seen in the Leonardo Module stowing items for the trip home on Discovery. Then the three crews are seen together answering questions about the mission during an in-flight interview.

Source record↗

STS-112 Flight Day 9 Highlights

The ninth day of the STS-112 mission begins with Pilot Pamela Melroy and Commander Jeff Ashby inside the Quest Airlock Module in the International Space Station. NASA ISS Science Officer Peggy Whitson is removing one of the Extravehicular Mobility Space Suits to reach a malfunctioning humidity separator. Also, a live shot of a treadmill being used that crewmembers use to keep fit in space is shown. Internet questions are then being answered by the crewmembers.

Source record↗

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↗

CMEC driver

CMEC driver is a command line tool that runs earth system evaluation modules.

Ordonez, AnaC.↗

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.↗