Search NASA⌕ Search

SEARCH · Search NASA

Results for “contingency 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 163 records · Page 9

Skylab experiment performance evaluation manual. Appendix R: Experiment T020 foot controlled maneuvering unit (MSFC)

A series of analyses for experiment T020, foot controlled maneuvering unit (MSFC), to be used for evaluating the performance of the Skylab corollary experiments under preflight, inflight and post-flight conditions is reported. Experiment contingency plan procedure and malfunction analyses are presented in order to assist in making the experiment operationally successful.

Tonetti, B. B.↗

Experiences with neutral buoyance testing mockups

Contingency operations with neutral bouyancy simulation on a space platform is considered. Some task simulated are aft payload port deployment and retraction, removal and replacement of the control moment cyro, and deployment of the manual hand crank appendage. It is decided that crewmen can perform fine motor activities when simple aids are provided, certain tasks can be accomplished with less efforts when the crewman is afforded additional mobility, manual translation of large mass items is feasible, and that during the installation of replaceable units application of alignment indicators provide significant assistance to crewmen.

Dellacamera, B.↗

Development of a Two-Wheel Contingency Mode for the MAP Spacecraft

The Microwave Anisotropy Probe (MAP) is a follow-on mission to the Cosmic Background Explorer (COBE), and is currently collecting data from its orbit near the second Sun-Earth libration point. Due to limited mass, power, and financial resources, a traditional reliability concept including fully redundant components was not feasible for MAP. Instead, the MAP design employs selective hardware redundancy in tandem with contingency software modes and algorithms to improve the odds of mission success. One direction for such improvement has been the development of a two-wheel backup control strategy. This strategy would allow MAP to position itself for maneuvers and collect science data should one of its three reaction wheels fail. Along with operational considerations, the strategy includes three new control algorithms. These algorithms would use the remaining attitude control actuators-thrusters and two reaction wheels-in ways that achieve control goals while minimizing adverse impacts on the functionality of other subsystems and software.

Starin, Scott R.↗

An Autonomous Onboard Targeting Algorithm Using Finite Thrust Maneuvers

In earlier investigations, the adaptation and implementation of a modified two-level corrections process as the onboard targeting algorithm for the Trans-Earth Injection phase of Orion is presented. The objective of that targeting algorithm is to generate the times of ignition and magnitudes of the required maneuvers such that the desired state at entry interface is achieved. In an actual onboard flight software implementation, these times of ignition and maneuvers are relayed onto Flight Control for command and execution. Although this process works well when the burn durations or burn arcs are small, this might not be the case during a contingency situation when lower thrust engines are employed to perform the maneuvers. Therefore, a new version of the modified two-level corrections process is formulated to handle the case of finite burn arcs. This paper presents the development and formulation of that finite burn modified two-level corrections process which can again be used as an onboard targeting algorithm for the Trans-Earth Injection phase of Orion. Additionally, performance results and a comparison between the two methods are presented. The finite burn two-level corrector formulation presented here ensures the entry constraints at entry interface are still met without violating the available fuel budget, while still accounting for much longer burn times in its design.

Scarritt, Sara K.↗

An Autonomous Onboard Targeting Algorithm Using Finite Thrust Maneuvers

In earlier investigations, the adaptation and implementation of a modified two-level corrections (or targeting) process as the onboard targeting algorithm for the Trans-Earth Injection phase of Orion is presented. The objective of that targeting algorithm is to generate the times of ignition and magnitudes of the required maneuvers such that the desired state at entry interface is achieved. In an actual onboard flight software implementation, these times of ignition and maneuvers are relayed onto Flight Control for command and execution. Although this process works well when the burn durations or burn arcs are small, this might not be the case during a contingency situation when lower thrust engines are employed to perform the maneuvers. Therefore, a new model for the two-level corrections process is formulated here to accommodate finite burn arcs. This paper presents the development and formulation of the finite burn two-level corrector, used as an onboard targeting algorithm for the Trans-Earth Injection phase of Orion. A performance comparison between the impulsive and finite burn models is also presented. The present formulation ensures all entry constraints are met, without violating the available fuel budget, while allowing for low-thrust scenarios with long burn durations.

Scarritt, Sara K.↗

Airspace Automation Flight Tabletop Exercise

Interconnections of new systems are needed for airspace automation capabilities required in Urban Air Mobility (UAM). FAA Concept of Operations (CONOPS) V1.0 shows Provider of Services for UAM (PSU) at the center of the notional architecture; however, the functional role of the PSU in data exchange and the path to get there is unclear. In partnership with Wisk Aero, Avision, ANRA, Collins Aerospace, OneSky, SkyGrid, and AURA, the NASA National Campaign held discussions and tabletop exercises to test the functional allocations and work flows between an aircraft operator, airspace providers, Command and Control Communication Service Providers (C2CSP), and FAA air traffic in a real-world scenario. The exercise included preplanning and execution of a passenger mission with nominal, contingency, and conflict management scenarios for initial UAM operations. This working paper describes initial conditions for the flight tabletop exercise, exercise summaries, lessons learned, and recommendations for future work.

National Campaign↗

On-demand Command and Control of ASTERIA with Cloud-based Ground Station Services

ASTERIA (Arcsecond Space Telescope Enabling Research in Astrophysics) was a 6-unit CubeSat technology demonstration mission that deployed from the International Space Station on November 20th, 2017. After successfully completing its 90-day primary mission that demonstrated arcsecond-level line-of-sight pointing and focal plane thermal stability for exoplanet detection, it entered an extended mission performing onboard software demonstrations to mature technology both in space and on the ground. One of the technologies was a completely cloud-based ground system leveraging Amazon Web Services (AWS) Ground Station service. Announced in December 2018 and launched in May 2019, AWS Ground Station is a fully managed ground station service that aims to reduce the overhead associated with developing and maintaining ground system infrastructure throughout the mission lifecycle. AWS Ground Station makes available the suite of features required for any ground system in support of low-Earth orbit (LEO) and medium-Earth Orbit (MEO) satellite operations on-demand and without setting up or maintaining long-term contracts. Charges are incurred on a per-minute basis for antenna usage during scheduled tracks. Support is available for S-band uplink and downlink, along with X-band narrowband and wideband downlink. Missions that use the service may reserve tracks with any licensed AWS Ground Station antennas located across each service region and have direct access to any AWS services in support of mission operations. The cloud-based architecture built around the AWS Ground Station service greatly enhanced ASTERIA mission operations by enabling end-to-end pass automation, on-demand contact scheduling and contingency planning, along with more efficient data downlink through station availability and station-tostation handovers. It incorporated open-source software, particularly NASA's AMMOS Instrument Toolkit (AIT) and Open Mission Control Technologies (OpenMCT), along with the AWS application programming interfaces (API) to the Ground Station, Elastic Compute Cloud (EC2) and Simple Storage Service (S3) services. After showcasing operability in August 2019, the team continued using and improving this novel ground system architecture until the end of mission in December 2019. This paper describes the cloud-based ground system, how it was designed, tested, and evaluated with an inorbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

Solar-B X-ray Telescope (XRT) Concept Study Report

The X-ray observations from the Yohkoh SXT provided the greatest step forward in our understanding of the solar corona in nearly two decades. Expanding on the accomplishments of Yohkoh, we believe that the scientific objectives of the Solar-B mission are achieved with a significantly improved X-ray telescope (XRT) similar to the SXT. The Solar-B XRT will have twice the spatial resolution and a broader temperature response, while building on the knowledge gained from the successful Yohkoh mission. We present the scientific justification for this view, discuss the instrumental requirements that flow from the scientific objectives, and describe the instrumentation to meet these requirements. We then provide a detailed discussion of the design activities carried out during Phase A, noting the conclusions that were reached in terms of their implications for the detailed design activities which are now commencing. Details of the instrument that have changed as a result of the Phase A studied are specifically noted, and areas of concern going into Phase B are highlighted. XRT is a grazing-incidence (GI) modified Wolter I X-ray telescope, of 35cm inner diameter and 2.7m focal length. The 2048x2048 back-illuminated CCD (now an ISAS responsibility) has 13.5 micron pixels, corresponding to 1.0 arcsec and giving full Sun field of view. This will be the highest resolution GI X-ray telescope ever flown for Solar coronal studies, and it has been designed specifically to observe both the high and low temperature coronal plasma. A small optical telescope provides visible light images for co-alignment with the Solar-B optical and EUV instruments. The XRT science team is working in close cooperation with our Japanese colleagues in the design and construction of this instrument. All of the expertise and resources of the High Energy and Solar/Stellar Divisions of the Center for Astrophysics are being made available to this program, and our team will carry its full share of responsibility for mission operations, data reduction and education and public outreach. All aspects of the XRT design were reviewed during Phase A. The study focussed particularly on those aspects that have the greatest affect on instrument performance and extended lifetime, on the image quality error budget, and on the camera (mechanical and electrical) interface and the instrument mounting interfaces. The present instrument design differs in some details from that originally proposed. Selection of the XRT for Phase A study was contingent upon the removal of the camera and its associated electronics, and the acceptance of a stringent cost cap. The removal of the electronics left the XRT without control electronics for the instrument mechanisms. A mechanism controller was therefore added. The removal of the camera resulted in major complications to the integration and test plan. After many discussions, it was decided that the system would be less expensive, and the risk of unacceptable performance lower, if we include a focus mechanism. The remainder of the XRT design baseline matches the proposed configuration. Data requirements for the XRT are driven by the science plans, which are based on the physical processes in the solar outer atmosphere. Discussions to date of the XRT observing plan, both alone and in conjunction with the other Solar-B instruments, shows that the XRT needs 2 Gbits of on-board storage, at least one circulating buffer of 640 Mbits, and twelve 10- minute downlinks per day in order to carry out its required programs.

Golub, Leon↗

Medical countermeasures for extraterrestrial environments: Current status and future prospects with focus on acute injuries

In all space exploratory activities involving humans there are associated risks to health and well-being. Exposure to ionizing radiation represents one of the more serious health concerns. Although medical issues can arise shortly following the rare acute exposures, the more likely radiation-associated injuries will manifest in a delayed fashion following sub-acute exposures or protracted exposures to relatively low radiation doses. The radiological conditions that present these health risks during extraterrestrial space travel are presented in this article, along with current physical and medical countermeasures for such exposure contingencies. The aim of this article is to discuss radiation medical countermeasures that may be considered for future space exploration and travel. Biomedical advances have occurred toward the control and minimization of acute, sub-acute, and fractionated radiation exposure injuries, whether they stem from intentional application of radio-therapeutic procedures or unintentional, accidental terrestrial-based exposures. Those advances, based largely on novel bioengineering, genetic, and combinatorial pharmaceutical strategies, are briefly reviewed here, along with the promising prospects of additional, new and improved medical countering systems/agents that will be forthcoming with additional research and development efforts.

Acute/chronic radiation injuries↗

On-demand Command and Control of ASTERIA with Cloud-based Ground Station Services

ASTERIA (Arcsecond Space Telescope Enabling Research in Astrophysics) was a 6-unit CubeSat technology demonstration mission that deployed from the International Space Station on November 20th, 2017. After successfully completing its 90-day primary mission that demonstrated arcsecond-level line-of-sight pointing and focal plane thermal stability for exoplanet detection, it entered an extended mission performing onboard software demonstrations to mature technology both in space and on the ground. One of the technologies was a completely cloud-based ground system leveraging Amazon Web Services (AWS) Ground Station service.Announced in December 2018 and launched in May 2019, AWS Ground Station is a fully managed ground station service that aims to reduce the overhead associated with developing and maintaining ground system infrastructure throughout the mission lifecycle. AWS Ground Station makes available the suite of features required for any ground system in support of low-Earth orbit (LEO) and medium-Earth Orbit (MEO) satellite operations on-demand and without setting up or maintaining long-term contracts. Charges are incurred on a per-minute basis for antenna usage during scheduled tracks. Support is available for S-band uplink and downlink, along with X-band narrowband and wideband downlink. Missions that use the service may reserve tracks with any licensed AWS Ground Station antennas located across each service region and have direct access to any AWS services in support of mission operations.The cloud-based architecture built around the AWS Ground Station service greatly enhanced ASTERIA mission operations by enabling end-to-end pass automation, on-demand contact scheduling and contingency planning, along with more efficient data downlink through station availability and station-to-station handovers. It incorporated open-source software, particularly NASA's AMMOS Instrument Toolkit (AIT) and Open Mission Control Technologies (OpenMCT), along with the AWS application programming interfaces (API) to the Ground Station, Elastic Compute Cloud (EC2) and Simple Storage Service (S3) services. After showcasing operability in August 2019, the team continued using and improving this novel ground system architecture until the end of mission in December 2019. This paper describes the cloud-based ground system, how it was designed, tested, and evaluated with an in-orbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

ATS-6 engineering performance report. Volume 2: Orbit and attitude controls

Attitude control is reviewed, encompassing the attitude control subsystem, spacecraft attitude precision pointing and slewing adaptive control experiment, and RF interferometer experiment. The spacecraft propulsion system (SPS) is discussed, including subsystem, SPS design description and validation, orbital operations and performance, in-orbit anomalies and contingency operations, and the cesium bombardment ion engine experiment. Thruster failure due to plugging of the propellant feed passages, a major cause for mission termination, are considered among the critical generic failures on the satellite.

Wales, R. O.↗

Mathematical models for space shuttle ground systems

Math models are a series of algorithms, comprised of algebraic equations and Boolean Logic. At Kennedy Space Center, math models for the Space Shuttle Systems are performed utilizing the Honeywell 66/80 digital computers, Modcomp II/45 Minicomputers and special purpose hardware simulators (MicroComputers). The Shuttle Ground Operations Simulator operating system provides the language formats, subroutines, queueing schemes, execution modes and support software to write, maintain and execute the models. The ground systems presented consist primarily of the Liquid Oxygen and Liquid Hydrogen Cryogenic Propellant Systems, as well as liquid oxygen External Tank Gaseous Oxygen Vent Hood/Arm and the Vehicle Assembly Building (VAB) High Bay Cells. The purpose of math modeling is to simulate the ground hardware systems and to provide an environment for testing in a benign mode. This capability allows the engineers to check out application software for loading and launching the vehicle, and to verify the Checkout, Control, & Monitor Subsystem within the Launch Processing System. It is also used to train operators and to predict system response and status in various configurations (normal operations, emergency and contingent operations), including untried configurations or those too dangerous to try under real conditions, i.e., failure modes.

Tory, E. G.↗

Tell Me about Your Lemonade Stand

At STARSYS, we execute many Firm Fixed Price (FFP) programs for the development of mechanical systems for spacecraft. Contracting this way pre-suppose that we have the ability to establish and hold scope for a system that has yet to be defined. To do FFP, it is critical that we have program managers who are masters at cost control. Fortunately, we have some "masters" in our company. They just seem to have a knack for driving to a financial target. Doesn't matter if the program has contingency or not. Doesn't seem to matter if they use MS Project, Excel spread-sheets, or the back of an envelope. Doesn't even seem to matter whether the program is set up as a financial challenge or a winner.

Tibbitts, Scott↗

Streamlining Tactical Operator Handoffs During Multi-Vehicle Operations

Increased automation has shifted the operator control paradigm from a single operator controlling a single vehicle, to multiple operators collaborating to control multiple vehicles; this paradigm is known as m:N. Many questions remain unanswered in this new operational paradigm about the division of assets as workload for individual operators varies over time. This paper explores the management of workload by enabling operators to temporarily handoff vehicles among each other. A study was conducted to explore both a manual and assisted method for performing handoffs during manipulated contingency scenarios. The assisted handoff method allowed subjects to easily choose and group nominal and/or contingency vehicles. The number of contingencies was also manipulated to determine the effect workload had on how pilots utilized the ability to handoff vehicles. Results show subjects performed handoffs more often when there were more contingencies and when the assisted handoff tool was available. In addition, the assisted tool made subjects feel more comfortable, enabling them to feel like they could take longer to resolve contingency situations. Lastly, even during contingencies, subjects were able to successfully complete secondary tasks.

m:N operations↗

NASA CEV On-Orbit GN&C Analysis

The Orion spacecraft orbit GN&C system will be required to perform both ISS servicing missions and Lunar sortie and outpost crew transportation. While certain aspects of these two missions are complementary, the two missions are also distinct in many ways. Common between the missions is a Low Earth Orbit (LEO) rendezvous, one with the ISS And the other with the LSAM/EDS stack prior to trans-lunar insertion. The lunar missions will additionally require Orion to perform orbit maintenance in LLO, perform contingency lunar orbit operations including RPOD with the LSAM, perform the TEI maneuver sequence, and execute the trans-Earth cruise. The NASA-led team developed a reference configuration orbit GN&C system capable of executing all of these activities with the same navigation sensor suite and control effectors while fully meeting the requirements being developed for System Requirements Review in advance of prime contractor selection. This paper will present an overview of the analyses performed to support system trade studies, demonstrate the feasibility of the NASA reference configuration, and validate the Orion system requirements. These analyses include linear covariance techniques, 3-DOF Monte Carlo simulations, 6-DOF Monte Carlo simulations, and analytical evaluations of GN&C systems performed by the NASA-led Orion team to characterize the sensitivities of Orion s various missions and assess the unique challenges of each. The first part of this paper will describe the trade studies that were performed in order to characterize the RPOD system performance for both the ISS and the lunar missions including development of an RPOD operations concept, RPOD trajectories, contingency scenarios, docking mechanism and associated contact conditions, post-contact thrust issues, relative navigation sensors, relative navigation sensor target infrastructure. The paper will also discuss concepts for both manually-piloted and automatically executed scenarios, as well as the remotely-piloted contingency scenario in LLO. The second part of the paper will discuss the analyses performed for lunar and cislunar GN&C performance including the accuracy of the post-insertion lunar orbit, the ability of Orion to hit a particular Earth return entry corridor, attitude control solutions for long-duration surface operations, and autonomous navigation in support of TEI without ground tracking.

DSouza, Chris↗

Demonstration of Two Extended Visual Line of Sight Methods for Urban UAV Operations

This report describes two extended visual line of sight (EVLOS) methods developed and utilized during two flight campaigns over the campus of NASA Langley Research Center (LaRC): a chase vehicle method and a radio controlled (RC) pilot handoff method. These campaigns were performed to (a) evaluate small unmanned aerial system (sUAS) flight beyond the visual line of sight (BVLOS) of the ground control station operator and (b) test technologies under development to enable a transition from EVLOS to BVLOS operations. While an autonomous waypoint-based operational approach enabled minimal pilot intervention in both methods, range containment was enforced (a) manually via continual pilot visual monitoring and (b) autonomously via on-board contingency landing autonomy triggerable at the boundary of stay-in geofences. In the thirty-nine flights which utilized the chase vehicle, the pilot followed the sUAS flying a 1.2 km path at 40m altitude over urban streets. In the fifteen flights which utilized pilot handoff, a pilot at one end of a 1.5 km path initiated the flight at 120m altitude over buildings and trees, and at the midway point of the path transferred radio control to a pilot at the other end. In comparison, the chase vehicle method requires less ground crew and simpler avionics, while the pilot handoff method avoids schedule risk arising from street traffic congestion but better replicates actual direct routing for BVLOS flights. Collision risk with another aircraft was introduced in both campaigns and mitigated with the same manual and autonomous methods. Results from these campaigns serve as a basis for planned BVLOS operations at NASA LaRC.

Nicholas Rymer↗

CFD Simulations in Support of Shuttle Orbiter Contingency Abort Aerodynamic Database Enhancement

Modern Computational Fluid Dynamics (CFD) techniques were used to compute aerodynamic forces and moments of the Space Shuttle Orbiter in specific portions of contingency abort trajectory space. The trajectory space covers a Mach number range of 3.5-15, an angle-of-attack range of 20deg-60deg, an altitude range of 100-190 kft, and several different settings of the control surfaces (elevons, body flap, and speed brake). Presented here are details of the methodology and comparisons of computed aerodynamic coefficients against the values in the current Orbiter Operational Aerodynamic Data Book (OADB). While approximately 40 cases have been computed, only a sampling of the results is provided here. The computed results, in general, are in good agreement with the OADB data (i.e., within the uncertainty bands) for almost all the cases. However, in a limited number of high angle-of-attack cases (at Mach 15), there are significant differences between the computed results, especially the vehicle pitching moment, and the OADB data. A preliminary analysis of the data from the CFD simulations at Mach 15 shows that these differences can be attributed to real-gas/Mach number effects. The aerodynamic coefficients and detailed surface pressure distributions of the present simulations are being used by the Shuttle Program in the evaluation of the capabilities of the Orbiter in contingency abort scenarios.

Papadopoulos, Periklis E.↗

Demonstration of automated proximity and docking technologies

An autodock was demonstrated using straightforward techniques and real sensor hardware. A simulation testbed was established and validated. The sensor design was refined with improved optical performance and image processing noise mitigation techniques, and the sensor is ready for production from off-the-shelf components. The autonomous spacecraft architecture is defined. The areas of sensors, docking hardware, propulsion, and avionics are included in the design. The Guidance Navigation and Control architecture and requirements are developed. Modular structures suitable for automated control are used. The spacecraft system manager functions including configuration, resource, and redundancy management are defined. The requirements for autonomous spacecraft executive are defined. High level decisionmaking, mission planning, and mission contingency recovery are a part of this. The next step is to do flight demonstrations. After the presentation the following question was asked. How do you define validation? There are two components to validation definition: software simulation with formal and vigorous validation, and hardware and facility performance validated with respect to software already validated against analytical profile.

Anderson, Robert L.↗