Search NASA⌕ Search

SEARCH · Search NASA

Results for “command and control”

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 271 records · Page 15
All sourcesNASA NTRSDOE OSTI
NASA NTRS1995

Weaves as an Interconnection Fabric for ASIM's and Nanosatellites

Many of the micromachines under consideration require computer support, indeed, one of the appeals of this technology is the ability to intermix mechanical, optical, analog, and digital devices on the same substrate. The amount of computer power is rarely an issue, the sticking point is the complexity of the software required to make effective use of these devices. Micromachines are the nano-technologist's equivalent of 'golden screws'. In other words, they will be piece parts in larger assemblages. For example, a nano-satellite may be composed of stacked silicon wafers where each wafer contains hundreds to thousands of micromachines, digital controllers, general purpose computers, memories, and high-speed bus interconnects. Comparatively few of these devices will be custom designed, most will be stock parts selected from libraries and catalogs. The novelty will lie in the interconnections. For example, a digital accelerometer may be a component part in an adaptive suspension, a monitoring element embedded in the wrapper of a package, or a portion of the smart skin of a launch vehicle. In each case, this device must inter-operate with other devices and probes for the purposes of command, control, and communication. We propose a software technology called 'weaves' that will permit large collections of micromachines and their attendant computers to freely intercommunicate while preserving modularity, transparency, and flexibility. Weaves are composed of networks of communicating software components. The network, and the components comprising it, may be changed even while the software, and the devices it controls, are executing. This unusual degree of software plasticity permits micromachines to dynamically adapt the software to changing conditions and allows system engineers to rapidly and inexpensively develop special purpose software by assembling stock software components in custom configurations.

Gorlick, Michael M.↗
NASA NTRS1991

Laser docking sensor engineering model

NASA JSC has been involved in the development of Laser sensors for the past ten years in order to support future rendezvous and docking missions, both manned and unmanned. Although many candidate technologies have been breadboarded and evaluated, no sensor hardware designed specifically for rendezvous and docking applications has been demonstrated on-orbit. It has become apparent that representative sensors need to be flown and demonstrated as soon as possible, with minimal cost, to provide the capability of the technology in meeting NASA's future AR&C applications. Technology and commercial component reliability have progressed to where it is now feasible to fly hardware as a detailed test objective minimizing the overall cost and development time. This presentation will discuss the ongoing effort to convert an existing in-house developed breadboard to an engineering model configuration suitable for flight. The modifications include improving the ranger resolution and stability with an in-house design, replacing the rack mounted galvanometric scanner drivers with STD-bus cards, replacing the system controlling personal computer with a microcontroller, and repackaging the subsystems as appropriate. The sensor will use the performance parameters defined in previous JSC requirements working groups as design goals and be built to withstand the space environment where fiscally feasible. Testing of the in-house ranger design is expected to be completed in October. The results will be included in the presentation. Preliminary testing of the ranging circuitry indicates a range resolution of 4mm is possible. The sensor will be mounted in the payload bay on a shelf bracket and have command, control, and display capabilities using the payload general support computer via an RS422 data line.

Dekome, Kent↗
NASA NTRS2009

Protocol for Communication Networking for Formation Flying

An application-layer protocol and a network architecture have been proposed for data communications among multiple autonomous spacecraft that are required to fly in a precise formation in order to perform scientific observations. The protocol could also be applied to other autonomous vehicles operating in formation, including robotic aircraft, robotic land vehicles, and robotic underwater vehicles. A group of spacecraft or other vehicles to which the protocol applies could be characterized as a precision-formation- flying (PFF) network, and each vehicle could be characterized as a node in the PFF network. In order to support precise formation flying, it would be necessary to establish a corresponding communication network, through which the vehicles could exchange position and orientation data and formation-control commands. The communication network must enable communication during early phases of a mission, when little positional knowledge is available. Particularly during early mission phases, the distances among vehicles may be so large that communication could be achieved only by relaying across multiple links. The large distances and need for omnidirectional coverage would limit communication links to operation at low bandwidth during these mission phases. Once the vehicles were in formation and distances were shorter, the communication network would be required to provide high-bandwidth, low-jitter service to support tight formation-control loops. The proposed protocol and architecture, intended to satisfy the aforementioned and other requirements, are based on a standard layered-reference-model concept. The proposed application protocol would be used in conjunction with conventional network, data-link, and physical-layer protocols. The proposed protocol includes the ubiquitous Institute of Electrical and Electronics Engineers (IEEE) 802.11 medium access control (MAC) protocol to be used in the datalink layer. In addition to its widespread and proven use in diverse local-area networks, this protocol offers both (1) a random- access mode needed for the early PFF deployment phase and (2) a time-bounded-services mode needed during PFF-maintenance operations. Switching between these two modes could be controlled by upper-layer entities using standard link-management mechanisms. Because the early deployment phase of a PFF mission can be expected to involve multihop relaying to achieve network connectivity (see figure), the proposed protocol includes the open shortest path first (OSPF) network protocol that is commonly used in the Internet. Each spacecraft in a PFF network would be in one of seven distinct states as the mission evolved from initial deployment, through coarse formation, and into precise formation. Reconfiguration of the formation to perform different scientific observations would also cause state changes among the network nodes. The application protocol provides for recognition and tracking of the seven states for each node and for protocol changes under specified conditions to adapt the network and satisfy communication requirements associated with the current PFF mission phase. Except during early deployment, when peer-to-peer random access discovery methods would be used, the application protocol provides for operation in a centralized manner.

Jennings, Esther↗
NASA NTRS2010

High-Intensity Radiated Field Fault-Injection Experiment for a Fault-Tolerant Distributed Communication System

Safety-critical distributed flight control systems require robustness in the presence of faults. In general, these systems consist of a number of input/output (I/O) and computation nodes interacting through a fault-tolerant data communication system. The communication system transfers sensor data and control commands and can handle most faults under typical operating conditions. However, the performance of the closed-loop system can be adversely affected as a result of operating in harsh environments. In particular, High-Intensity Radiated Field (HIRF) environments have the potential to cause random fault manifestations in individual avionic components and to generate simultaneous system-wide communication faults that overwhelm existing fault management mechanisms. This paper presents the design of an experiment conducted at the NASA Langley Research Center's HIRF Laboratory to statistically characterize the faults that a HIRF environment can trigger on a single node of a distributed flight control system.

Yates, Amy M.↗
NASA NTRS1990

The Copernicus project

The Copernicus spacecraft, to be launched on May 4, 2009, is designed for scientific exploration of the planet Pluto. The main objectives of this exploration is to accurately determine the mass, density, and composition of the two bodies in the Pluto-Charon system. A further goal of the exploration is to obtain precise images of the system. The spacecraft will be designed for three axis stability control. It will use the latest technological advances to optimize the performance, reliability, and cost of the spacecraft. Due to the long duration of the mission, nominally 12.6 years, the spacecraft will be powered by a long lasting radioactive power source. Although this type of power may have some environmental drawbacks, currently it is the only available source that is suitable for this mission. The planned trajectory provides flybys of Jupiter and Saturn. These flybys provide an opportunity for scientific study of these planets in addition to Pluto. The information obtained on these flybys will supplement the data obtained by the Voyager and Galileo missions. The topics covered include: (1) scientific instrumentation; (2) mission management, planning, and costing; (3) power and propulsion system; (4) structural subsystem; (5) command, control, and communication; and (6) attitude and articulation control.

Barnstable, Bob↗
NASA NTRSDate not supplied

Science Capabilities of the Common Habitat

The Common Habitat is the primary habitable element in a conceptual architecture feasibility study for long-duration space exploration with an eight-person crew size. On lunar or planetary surfaces, the Common Habitat forms the core of a Surface Base Camp. In microgravity, the Common Habitat is the core of the Deep Space Exploration Vehicle (DSEV), an in-space transportation spacecraft. The Common Habitat employs a horizontal orientation that is divided internally into a lower deck, mid deck, and upper deck, roughly separating outfitting into individual, work, and group functions. On a planetary surface, the habitat is incorporated into a base camp, located near the south pole in the case of the Moon. The Mars base camp is currently location agnostic. Each base camp is divided into habitation, landing, resource production, and power zones. In microgravity, the habitat is incorporated into the Deep Space Exploration Vehicle, a vessel capable of transporting the crew within the inner solar system. In addition to crew and teleoperated control of external science assets, the Common Habitat employs a suite of life and physical science laboratory systems to enable it to support science investigations across a variety of destination environments, primarily featuring the Moon and Mars, along with the intervening interplanetary space. Other potential destinations include Near Earth Asteroids and Venus and Earth orbits. Located in the aft starboard section of the Common Habitat mid deck, the life science laboratory supports primarily biology and human research. In its baseline configuration, the laboratory includes horizontal work surfaces, freezers, multiple gloveboxes, sample transfer/exposure capability, large instruments, and reconfigurable ISPR-compatible payload bays. The Medical Care Facility and exercise facility can also support life science research. In the aft port section of the mid deck, the physical science laboratory supports physics, chemistry, materials science, geology, and remote sensing (including astrophysics, heliophysics, Earth science, planetary science, and meteorology). It provides a baseline of similar ISPR-compatible payload bays and adds additional freezers, including those for cryogenic sample storage, a remote sensing workstation, more gloveboxes, also with sample transfer/exposure, combustion chambers, fluid mechanics chambers, and a gas chromatograph. It leverages the Command & Control Center for teleoperations of mobile science assets. Both laboratories are highly modular, with the ability to swap out both payloads and instruments on an as-needed basis. The integrated science outfitting of the Common Habitat positions its crew to contribute to all of NASA’s Moon to Mars science objectives and extend human understanding into the inner solar system.

Lunar Suface↗
NASA NTRSDate not supplied

NextSTEP Appendix A Modular ECLSS Effort Lessons Learned

NASA’s Artemis program provides the first steps for earth-independent exploration starting with crewed habitats in cislunar space and progressing toward crewed landings on the lunar surface that will prepare systems and crews for the exploration of Mars. The Next Space Technology for Exploration Partnerships (NextSTEP) is a public-private partnership model that facilitates commercial development of deep space exploration capabilities in support of more extensive human spaceflight missions in and beyond cislunar space. NASA issued the original NextSTEP Broad Agency Announcement (BAA) to U.S. industry in late 2014 and issued the second BAA (NextSTEP-2) in April 2016. The first appendix under NextSTEP-2, Appendix A, focused on developing deep space habitation concepts, engineering design and development, and risk reduction efforts leading to a habitation capability in cislunar space. NASA solicited concepts to develop and refine the evolvable, modular architecture, functional allocation options, standards, and common interfaces required to enable interoperability of the aggregate system to provide long duration deep space transit habitation, specifically enhancements and testing of deep space Environmental Control and Life Support Systems (ECLSS). Collins Aerospace, formerly UTC Aerospace Systems (UTAS), was awarded a Phase 1 and subsequent Phase 2 contract to “develop concepts that group ECLS systems into logical modules maximizing the use of common components and the development of unique methods and design concepts that support in-flight maintenance and repair for future exploration systems.” This paper summarizes the work accomplished under this effort, the lessons that can be applied to development of forthcoming habitation elements, and the gaps remaining to achieve a more resilient, maintainable, repairable and adaptable system capable of installation on a wide variety of habitat platforms. A primary accomplishment of this effort is the development and maturation of a modular palletization concept to enable standard rack interfaces, post-launch outfitting, and decoupling of structural supports that withstand launch environments from those needed for lower on-orbit loads in order to reduce installed mass and repurposing of panels within the habitat. In the course of the effort, Collins assessed numerous architecture trades, including the use of condensing and noncondensing heat exchangers, the ability of modular units to accommodate various habitat volumes and thermal loading, and the most appropriate order of and timing of delivery of regenerative ECLSS hardware to orbital habitats. In addition to the modularity of hardware elements, Collins developed software approaches for distributed/modular command, control, and communication systems and innovative Bayesian fault detection and isolation techniques. Finally, the effort explored advanced maintainability and supportability concepts including the definition of maintenance units (MUs) in place of the traditional Orbital Replacement Units (ORUs), increasing parts commonality to reduce the number and type of spare parts, the use of augmented reality to guide crews during maintenance and repair procedures, and how crews would prepare for and recover from long durations of habitat dormancy. Now that the NextSTEP Modular ECLSS effort has come to a close, it’s important to identify the lessons learned and where they can be leveraged to improve NASA’s broader program of ECLSS technology development and demonstration and ultimately how they can increase the performance of future surface and orbital habitats.

NextSTEP↗
NASA NTRSDate not supplied

NextSTEP Appendix A Modular ECLSS Effort Lessons Learned

NASA’s Artemis program provides the first steps for earth-independent exploration starting with crewed habitats in cislunar space and progressing toward crewed landings on the lunar surface that will prepare systems and crews for the exploration of Mars. The Next Space Technology for Exploration Partnerships (NextSTEP) is a public-private partnership model that facilitates commercial development of deep space exploration capabilities in support of more extensive human spaceflight missions in and beyond cislunar space. NASA issued the original NextSTEP Broad Agency Announcement (BAA) to U.S. industry in late 2014 and issued the second BAA (NextSTEP-2) in April 2016. The first appendix under NextSTEP-2, Appendix A, focused on developing deep space habitation concepts, engineering design and development, and risk reduction efforts leading to a habitation capability in cislunar space. NASA solicited concepts to develop and refine the evolvable, modular architecture, functional allocation options, standards, and common interfaces required to enable interoperability of the aggregate system to provide long duration deep space transit habitation, specifically enhancements and testing of deep space Environmental Control and Life Support Systems (ECLSS). Collins Aerospace, formerly UTC Aerospace Systems (UTAS), was awarded a Phase 1 and subsequent Phase 2 contract to “develop concepts that group ECLS systems into logical modules maximizing the use of common components and the development of unique methods and design concepts that support in-flight maintenance and repair for future exploration systems.” This paper summarizes the work accomplished under this effort, the lessons that can be applied to development of forthcoming habitation elements, and the gaps remaining to achieve a more resilient, maintainable, repairable and adaptable system capable of installation on a wide variety of habitat platforms. A primary accomplishment of this effort is the development and maturation of a modular palletization concept to enable standard rack interfaces, post-launch outfitting, and decoupling of structural supports that withstand launch environments from those needed for lower on-orbit loads in order to reduce installed mass and repurposing of panels within the habitat. In the course of the effort, Collins assessed numerous architecture trades, including the use of condensing and noncondensing heat exchangers, the ability of modular units to accommodate various habitat volumes and thermal loading, and the most appropriate order of and timing of delivery of regenerative ECLSS hardware to orbital habitats. In addition to the modularity of hardware elements, Collins developed software approaches for distributed/modular command, control, and communication systems and innovative Bayesian fault detection and isolation techniques. Finally, the effort explored advanced maintainability and supportability concepts including the definition of maintenance units (MUs) in place of the traditional Orbital Replacement Units (ORUs), increasing parts commonality to reduce the number and type of spare parts, the use of augmented reality to guide crews during maintenance and repair procedures, and how crews would prepare for and recover from long durations of habitat dormancy. Now that the NextSTEP Modular ECLSS effort has come to a close, it’s important to identify the lessons learned and where they can be leveraged to improve NASA’s broader program of ECLSS technology development and demonstration and ultimately how they can increase the performance of future surface and orbital habitats.

NextSTEP↗
NASA NTRS2010

Operational Lessons Learned from the Ares I-X Flight Test

The Ares I-X flight test, launched in 2009, is the first test of the Ares I crew launch vehicle. This development flight test evaluated the flight dynamics, roll control, and separation events, but also provided early insights into logistical, stacking, launch, and recovery operations for Ares I. Operational lessons will be especially important for NASA as the agency makes the transition from the Space Shuttle to the Constellation Program, which is designed to be less labor-intensive. The mission team itself comprised only 700 individuals over the life of the project compared to the thousands involved in Shuttle and Apollo missions; while missions to and beyond low-Earth orbit obviously will require additional personnel, this lean approach will serve as a model for future Constellation missions. To prepare for Ares I-X, vehicle stacking and launch infrastructure had to be modified at Kennedy Space Center's Vehicle Assembly Building (VAB) as well as Launch Complex (LC) 39B. In the VAB, several platforms and other structures designed for the Shuttle s configuration had to be removed to accommodate the in-line, much taller Ares I-X. Vehicle preparation activities resulted in delays, but also in lessons learned for ground operations personnel, including hardware deliveries, cable routing, transferred work and custodial paperwork. Ares I-X also proved to be a resource challenge, as individuals and ground service equipment (GSE) supporting the mission also were required for Shuttle or Atlas V operations at LC 40/41 at Cape Canaveral Air Force Station. At LC 39B, several Shuttle-specific access arms were removed and others were added to accommodate the in-line Ares vehicle. Ground command, control, and communication (GC3) hardware was incorporated into the Mobile Launcher Platform (MLP). The lightning protection system at LC 39B was replaced by a trio of 600-foot-tall towers connected by a catenary wire to account for the much greater height of the vehicle. Like Shuttle, Ares I-X will be stacked on a MLP and rolled out to the pad on a Saturn-era crawler-transporter. While Ares I-X was only held in place by the four hold-down posts on its aft skirt during rollout, a new vehicle stabilization system (VSS) attached to the vertical service structure kept the vehicle from undue swaying prior to launch at the pad, LC 39B. Following the launch, the flight test vehicle first stage was recovered with the aid of new parachutes resized to accommodate the five-segment-long first stage, which had a much greater length and mass than the Shuttle s reusable solid rocket boosters. After splashdown, recovery divers exercised extra care when handling the first stage to ensure that the flight data recorders in the fifth segment simulator were not damaged by exposure to sea water. The data recovered from the Ares I-X flight test will be very valuable in verifying the predicted environments and models used to design the vehicle. Lessons learned from Ares I-X will be shared with the Ares Projects through written and verbal reports and through integration of mission team members into the Project workforce.

Davis, Stephan R.↗
NASA NTRS2006

A Case for Developing a Ground Based Replication of the Earth, Moon and Mars Spaceflight Infrastructure

When the systems are developed and in place to provide the services needed to operate en route and on the Lunar and Martian surfaces, an Earth based replication will need to be in place for the safety and protection of mission success. The replication will entail all aspects of the flight configuration end to end but will not include any closed loop systems. This would replicate the infrastructure from Lunar and Martian robots, manned surface excursions, through man and unmanned terrestrial bases, through the various types of communication systems and technologies, manned and un-manned space vehicles (large and small), to Earth based systems and control centers. An Earth based replicated infrastructure will enable checkout and test of new technologies, hardware, software updates and upgrades and procedures without putting humans and missions at risk. Analysis of events, what ifs and trouble resolution could be played out on the ground to remove as much risk as possible from any type of proposed change to flight operational systems. With adequate detail, it is possible that failures could be predicted with a high probability and action taken to eliminate failures. A major factor in any mission to the Moon and to Mars is the complexity of systems, interfaces, processes, their limitations, associated risks and the factor of the unknown including the development by many contractors and NASA centers. The need to be able to introduce new technologies over the life of the program requires an end to end test bed to analyze and evaluate these technologies and what will happen when they are introduced into the flight system. The ability to analyze system behaviors end to end under varying conditions would enhance safety e.g. fault tolerances. This analysis along with the ability to mine data from the development environment (e.g. test data), flight ops and modeling/simulations data would provide a level of information not currently available to operations and astronauts. In this paper we will analyze the beginnings of such a replication and what it could do in terms of reducing risk in the near term for development. We will analyze the Space Shuttle Main Engine (SSME) test lab which has to a large extent accomplished this replication for the SSME and has been highly successful in analyzing hardware and software problems and changes. The cost of replicating the flight system as proposed here could be very high if attempted as an afterthought. We will describe the initial steps for the development of a replication of this infrastructure starting with the communication infrastructure. The Constellation of Labs (CofL) under the Command, Control, Communication and Information (C3I) project for the NASA Exploration Initiative will provide the initial foundation upon which to base this replication. Simply put, there is very little margin for error in high latency situations e.g. en-route to/from Mars or in an autonomous process on the Lunar far side. Any thought out approach to reduce risk and increase safety needs to be accomplished end to end with the actual systems configuration.

Bradford, Robert N.↗
DOE OSTI2024

A full-scope, high-fidelity simulator-based hardware-in-the-loop testbed for comprehensive nuclear power plant cybersecurity research

Nuclear power plant (NPP) cybersecurity research often relies on hardware-in-the-loop (HIL) testbeds that integrate real hardware components into simulated environments. These testbeds allow researchers to identify vulnerabilities, evaluate attack impacts, and test security measures in a controlled setting. Furthermore, previous HIL testbeds lacked fidelity to accurately represent real nuclear systems, limiting the scope of cybersecurity analysis. This study presents the creation of a HIL testbed, devised upon a full-scope, high-fidelity NPP simulator, to facilitate realistic and comprehensive cybersecurity research. To demonstrate its capabilities, the control logic for the steam generator water level was migrated from the simulator to an external programmable logic controller. As a practical application of the developed testbed, supply chain attack scenarios were simulated by injecting malicious code into the controller logic, and the effects of manipulating sensor inputs and control commands were observed. While this HIL testbed provides more detailed simulations, enhanced realism, and wider applicability compared to other options utilizing a less complex simulator, it is also more intricate and costly. For this reason, we include a detailed comparison with some alternative architectures to aid fellow researchers and practitioners in the selection of a suitable HIL architecture based on specific research objectives.

47 OTHER INSTRUMENTATION↗
NASA NTRS1962

Use of an Inertia Sphere to Damp the Angular Motions of Spinning Space Vehicles

A theoretical study was made of a device which might be used to damp the angular motions of spin-stabilized space vehicles with constant moments of inertia. the device was assumed to consist of a rate gyro, a servo control, and a rotor mounted in a single gimbal. The investigation was conducted by considering the general equations of motion of the vehicle-damper system and noting that simplification would result if the damper had a spherical inertia distribution. Such a distribution was assumed thereafter, and a control command was defined so that the gimbal angle would be proportional to the angular velocity of the vehicle about the gimbal axis. The resulting equations were linearized, and the Routh-Hurwitz criterion was applied to determine the conditions for stability. The study included two numerical examples showing possible application of inertia-sphere rate dampers. The general conditions for stability were found to be feasible for practical applications. A simplified stability criterion covers a large class of practical problems.

SPHERE↗
NASA NTRS1971

The programming language HAL: A specification

HAL accomplishes three significant objectives: (1) increased readability, through the use of a natural two-dimensional mathematical format; (2) increased reliability, by providing for selective recognition of common data and subroutines, and by incorporating specific data-protect features; (3) real-time control facility, by including a comprehensive set of real-time control commands and signal conditions. Although HAL is designed primarily for programming on-board computers, it is general enough to meet nearly all the needs in the production, verification and support of aerospace, and other real-time applications.

Source record↗