Results for “operations spacecraft control” — Page 9

NASA NTRS1994

Economics of Automation in Space: Implications of Automated Versus Manned Operations on the High Cost of On-Orbit Assembly, Control and Servicing of Spacecraft

The continued high cost and risk of placing astronauts in space has placed considerable burden on NASA to cut costs and consider other means of achieving mission goals both effectively and safely. Additionally, future science missions which might place a tremendous burden on Shuttle availability, or require extended vehicle duty cycles on the Lunar surface and Mars surface, might preclude the presence of astronauts altogether.

Mars surface↗

NASA NTRS2011

Cassini Attitude Control Operations - Guidelines Levied on Science to Extend Reaction Wheel Life

The Cassini spacecraft was launched on October 15, 1997 and arrived at Saturn on June 30, 2004. It has performed detailed observations and remote sensing of Saturn, its rings, and its satellites since that time. Cassini deployed the European-built Huygens probe, which descended through the Titan atmosphere (Saturn's largest moon) and landed on its surface on January 14, 2005. The Cassini mission has recently been approved by NASA to continue through September of 2017. This 7-year extension is called the Solstice mission and it presents challenges to the spacecraft operations team and its ability to maintain the health of the spacecraft. To keep the spacecraft healthy for 7 more years, the spacecraft team must carefully manage hydrazine use (about 48% of the 132 kg launch load remains as of January 2011). A vital part of conserving hydrazine is to use the reaction wheel assembly (RWA) control system for precise pointing and slews wherever possible. In any given week, the Cassini spacecraft is commanded to use RWA control about 99% of the time, with about 1% of the time requiring reaction control system (RCS) thruster control (to perform Delta V course corrections or to bias the RWA momentum). Such extensive use of the RWA hardware throughout the mission requires that the RWAs be operated in a way that minimizes degradation in the RWA electronics, DC motor, and spin bearing for each reaction wheel. Three consumables in particular have been identified for the RWAs: (1) Total number of revolutions for each RWA. (2) Time spent at very low wheel speeds. At these low speeds, good elasto-hydrodynamic (EHD) film lubrication may be compromised. (3) Total number of on/off power cycles. The second of these consumables, minimizing the time spent at very low wheel speeds, is especially important to keep the spin bearing healthy and well-lubricated. These consumables are actively managed by the attitude control operations team throughout the mission. One vital management technique is to predict individual RWA momentum (given the pointing and slews that are needed to collect the best science) and to bias the RWA momentum in a way that reduces both the total number of revolutions as well as the time spent below EHD wheel speed. Another strategy to protect RWA health is to alter the planned pointing of the spacecraft (which can affect science collection) so that the RWA consumables are conserved. This paper focuses on why this second technique is needed, and discusses how guidelines have been developed by the attitude control team which affects the planned science pointing, so that science data can be most optimally collected while still minimizing RWA consumable usage.

interplanetary trajectory↗

NASA NTRS2014

The Use of Software Agents for Autonomous Control of a DC Space Power System

In order to enable manned deep-space missions, the spacecraft must be controlled autonomously using on-board algorithms. A control architecture is proposed to enable this autonomous operation for an spacecraft electric power system and then implemented using a highly distributed network of software agents. These agents collaborate and compete with each other in order to implement each of the control functions. A subset of this control architecture is tested against a steadystate power system simulation and found to be able to solve a constrained optimization problem with competing objectives using only local information.

autonomous control↗

NASA NTRS1991

The Generic Spacecraft Analyst Assistant (GenSAA): A tool for automating spacecraft monitoring with expert systems

Flight Operations Analysts (FOAs) in the Payload Operations Control Center (POCC) are responsible for monitoring a satellite's health and safety. As satellites become more complex and data rates increase, FOAs are quickly approaching a level of information saturation. The FOAs in the spacecraft control center for the COBE (Cosmic Background Explorer) satellite are currently using a fault isolation expert system named the Communications Link Expert Assistance Resource (CLEAR), to assist in isolating and correcting communications link faults. Due to the success of CLEAR and several other systems in the control center domain, many other monitoring and fault isolation expert systems will likely be developed to support control center operations during the early 1990s. To facilitate the development of these systems, a project was initiated to develop a domain specific tool, named the Generic Spacecraft Analyst Assistant (GenSAA). GenSAA will enable spacecraft analysts to easily build simple real-time expert systems that perform spacecraft monitoring and fault isolation functions. Lessons learned during the development of several expert systems at Goddard, thereby establishing the foundation of GenSAA's objectives and offering insights in how problems may be avoided in future project, are described. This is followed by a description of the capabilities, architecture, and usage of GenSAA along with a discussion of its application to future NASA missions.

Hughes, Peter M.↗

NASA NTRS1994

Attempt of automated space network operations at ETS-VI experimental data relay system

National Space Development Agency of Japan (NASDA) is to perform experimental operations to acquire necessary technology for the future inter-satellite communications configured with a data relay satellite. This paper intends to overview functions of the experimental ground system which NASDA has developed for the Engineering Test Satellite VI (ETS-VI) Data Relay and Tracking Experiment, and to introduce Space Network System Operations Procedure (SNSOP) method with an example of Ka-band Single Access (KSA) acquisition sequence. To reduce operational load, SNSOP is developed with the concept of automated control and monitor of both ground terminal and data relay satellite. To perform acquisition and tracking operations fluently, the information exchange with user spacecraft controllers is automated by SNSOP functions.

Ishihara, Kiyoomi↗

NASA NTRS2004

Environmental Test Program for the Mars Exploration Rover Project

On June 10 and July 7, 2003 the National Aeronautics and Space Administration (NASA) launched two spacecraft from Cape Canaveral, Florida for a six (6) months flight to the Red Planet, Mars. The two Mars Exploration Rover spacecraft landed safely on the planet in January 2004. Prior to the successful launch, both of the spacecraft were involved in a comprehensive test campaign that included development, qualification, and protoflight test programs. Testing was performed to simulate the environments associated with launch, inter-planetary cruise, landing on the planet and Mars surface operations. Unique test requirements included operating the spacecraft while the chamber pressure was controlled to simulate the decent to the planet from deep space, high impact landing loads and rover operations on the surface of the planet at 8 Torr and -130 C. This paper will present an overview of the test program that included vibration, pyro-shock, landing loads, acoustic noise, thermal vacuum and solar simulation testing at the Jet Propulsion Laboratory (JPL) Environmental Test Laboratory facilities in Pasadena, California.

Fisher, Terry C.↗

NASA NTRS1994

Customizing the JPL Multimission Ground Data System: Lessons Learned

This paper will describe lessons learned in adapting JPL's Multimission Ground Data System (MGDS) to fly the Voyager, Galileo, and Mars Observer missions. We will explain how powerful, existing ground data systems can be adapted and packaged in a cost effective way for operations of small and large planetary missions. We will also describe how the MGDS was adapted to support operations within the Galileo Spacecraft Testbed. The Galileo testbed provided a unique opportunity to adapt MGDS to support command and control operations for a small autonomous operations team with a handful of engineers flying the Galileo Spacecraft flight system model.

ground↗

NASA NTRS1987

Using a horizon sensor for Mars observer spacecraft attitude control

A modified earth horizon sensor design is proposed for the Mars Observer mission. The horizon sensor modification are based on Mars horizon radiance profiles. Attention is given to the Mars Observer's attitude control system, whose primary mode is horizon sensor-based and therefore obviates the use of an onboard spacecraft ephemeris; control accuracy of the order of 10 mrad 3sigma/axis is achieved. The attitude control system's second, celestial-backup mode, wich requires greater operational effort, employs an onboard celestial sensor as the spacecraft ephemeris; its control accuracy is of the order of 8 mrad 3sigma/axis.

Langmaier, J. K.↗

NASA NTRSDate not supplied

Automated Software for Manned Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C Dempsey↗

NASA NTRSDate not supplied

Automated Software for Manned Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C. Dempsey↗

NASA NTRSDate not supplied

Automated Software for Crewed Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C Dempsey↗

NASA NTRS1973

Periodic attitude control of a slowly spinning spacecraft.

A periodic attitude control system is presented which permits control of secular errors of a slowly spinning spacecraft operating in a high disturbance environment. Attitude errors of the spin-axis are detected by sun sensors (or rate gyros) and are controlled by a periodic control law which modulates external control torques generated by mass expulsion torquers. Attitude stability during the uncontrolled periods is obtained passively via the vehicle spin momentum. Equations of motion, a system block diagram, and design parameters are presented for a typical spacecraft application. Simulation results are included which demonstrate the feasibility of the novel control concept. Salient features of the periodic control approach are implementation simplicity, excellent response, and a propellant utilization efficiency greater than 75 percent.

Todosiev, E. P.↗

NASA NTRS2004

Assessment of in-flight anomalies of long life outer plant mission

Thee unmanned planetary spacecraft to the outer planets have been controlled and operated successfully in space for an accumulated total of 66 years. The Voyager 1 and 2 spacecraft each have been in space for more than 26 years. The Galileo spacecraft was in space for 14 years, including eight years in orbit about Jupiter. During the flight operations for these missions, anomalies for the ground data system and the flight systems have been tracked using the anomaly reporting tool at the Jet Propulsion Laboratory. A total of 3300 incidents, surprises, and anomaly reports have been recorded in the database. This paper describes methods and results for classifying and identifying trends relative to ground system vs. flight system, software vs. hardware, and corrective actions. There are several lessons learned from these assessments that significantly benefit the design and planning for long life missions of the future. These include the necessity for having redundancy for successful operation of the spacecraft, awareness that anomaly reporting is dependent on mission activity not the age of the spacecraft, and the need for having a program to maintain and transfer operation knowledge and tools to replacement flight team members.

anomalies↗

NASA NTRS2005

MODEL CORRELATION STUDY OF A RETRACTABLE BOOM FOR A SOLAR SAIL SPACECRAFT

To realize design concepts, predict dynamic behavior and develop appropriate control strategies for high performance operation of a solar-sail spacecraft, we developed a simple analytical model that represents dynamic behavior of spacecraft with various sizes. Since motion of the vehicle is dominated by retractable booms that support the structure, our study concentrates on developing and validating a dynamic model of a long retractable boom. Extensive tests with various configurations were conducted for the 30 Meter, light-weight, retractable, lattice boom at NASA MSFC that is structurally and dynamically similar to those of a solar-sail spacecraft currently under construction. Experimental data were then compared with the corresponding response of the analytical model. Though mixed results were obtained, the analytical model emulates several key characteristics of the boom. The paper concludes with a detailed discussion of issues observed during the study.

Adetona, O.↗

NASA NTRS1990

A new environment for multiple spacecraft power subsystem mission operations

The engineering analysis subsystem environment (EASE) is being developed to enable fewer controllers to monitor and control power and other spacecraft engineering subsystems. The EASE prototype has been developed to support simultaneous real-time monitoring of several spacecraft engineering subsystems. It is being designed to assist with offline analysis of telemetry data to determine trends, and to help formulate uplink commands to the spacecraft. An early version of the EASE prototype has been installed in the JPL Space Flight Operations Facility for online testing. The EASE prototype is installed in the Galileo Mission Support Area. The underlying concept, development, and testing of the EASE prototype and how it will aid in the ground operations of spacecraft power subsystems are discussed.

Bahrami, K. A.↗

NASA NTRSDate not supplied

Hall Magnetohydrodynamic Power Generation and Drag Augmentation Using A Coaxial-Electrode Configuration During Hypersonic Entry

For interplanetary missions, a spacecraft must reduce its relative velocity from orbital speeds of multiple kilometers per second to zero in order to safely land on the surface of a planetary body. During this phase known as planetary reentry, the spacecraft undergoes high speed above Mach 5 up to Mach 30. This hyper-sonic flight regime imposes a strong bow shock in front of the vehicle that imparts extreme aerodynamic and thermal effects. In addition, during portions of this regime, a plasma is formed in the post-shock flow-field around the vehicle due to these high temperatures. Interaction between an applied magnetic field with this electrically conductive fluid, or magnetohydrodynamic (MHD) interaction, can be utilized to convert kinetic energy from the flow into storable electrical energy. Onboard MHD energy generation can benefit the spacecraft by increasing the power of active thermal control components and vehicle control systems during reentry. MHD interaction also exerts a Lorentz body force on the plasma flow that can be manipulated to act as an additional drag force through the vehicle body. MHD drag augmentation can benefit the spacecraft with an additional control mechanism that operates without moving parts. This can be utilized at higher altitudes and subsequently reduce convective heat transfer to the vehicle. MHD interaction with plasma flow suggests that both power generation and drag augmentation can be integrated together in one design. Modern numerical studies have only demonstrated the viability and potential of MHD energy generation and drag modulation separately for implementation into future spacecraft designs [1] [2] [3]. Steeves et. al. presented one possible generator design specifically for reentry vehicles that utilized a modular panel with two embedded electromagnets and two extruding electrodes for air plasma to flow between. Fujino et. al. presented results that indicated increased total drag with a permanent magnet embedded in the blunt body of the Orbital Reentry Experiment (OREX) trajectory. Furthermore, experimental investigations of these two MHD applications have been limited and separate due to the difficult technical nature of experimental de-sign and analysis. For MHD energy generation, there have been two designs which used a cylindrical fore-body with two embedded permanent magnets and two outward facing curved electrodes for tangency to an artificially ionized plasma that flowed along the body length [4] [5]. The first design was studied using an air microwave (MW) ionized supersonic plasma wind tunnel and the second design used radio frequency (RF) ionization of Argon, but both physically demonstrated the feasibility of MHD energy generation in reentry plasma conditions. For MHD drag modulation, one study involved a small-scale cylindrical blunt body embedded with permanent magnets immersed in plasma flow in an arcjet tunnel [6], and another utilized a spherical permanent magnet enclosed with a spherical forebody that was evaluated in a shock expansion tunnel [7]. Both experimental studies provided physical evidence of drag augmentation due to MHD interactions. Therefore, because of the multi-faceted effects of MHD along with both applications having been deemed feasible and beneficial during reentry, this indicates that a coupled power generation and drag modulation design could be achievable. The axi-symmetric nature of blunt bodies for reentry suggests that a spherical set of two ring electrodes near the nose along the body axis. Based on first principles, flow along the walls of the spherical body can then produce MHD interactions between the electrodes. As a result, two currents are generated: a Hall current that produces power and a primary inductive current that augments the drag force. The goal of this work is to provide a simulated design of a coaxial-electrode con-figuration for power generation and drag modulation for experimental testing.

E. Leong↗

NASA NTRS2005

Robust Load-Sharing Control of Spacecraft Formations

This paper focuses on the design of autonomous and collaborative control strategies to govern the relative distances among multiple spacecraft in formation with no ground intervention. A coordinate load-sharing control structure for formation flying and a methodology to control their dynamic models with slow time-varying and uncertain parameters are the main objectives of this work. The method is applied to a deep space formation example, where the uncertainty in spacecraft fuel masses is also considered.

multi spacecraft↗

NASA NTRS2010

Lunar Reconnaissance Orbiter (LRO) Sun Safe Mode

The Lunar Reconnaissance Orbiter (LRO), a spacecraft designed and built at the National Aeronautics and Space Administration s (NASA) Goddard Space Flight Center (GSFC) in Greenbelt, MD, was launched on June 18, 2009 from Cape Canaveral. It is currently in orbit about the Moon taking detailed science measurements and providing a highly accurate mapping of the suface in preparation for the future return of astronauts to a permanent moon base. Onboard the spacecraft is a complex set of algorithms designed by the attitude control engineers at GSFC to control the pointig for all operational events, including anomalies that require the spacecraft to be put into a well known attitude configuration for a sufficiently long duration to allow for the investigation and correction of the anomaly. GSFC level requirements state that each spacecraft s control system design must include a configuration for this pointing and lso be able to maintain a thermally safe and power positive attitude. This stable control algorithm for anomalous events is commonly referred to as the safe mode and consists of control logic thatwill put the spacecraft in this safe configuration defined by the spacecraft s hardware, power and environment capabilities and limitations. The LRO Sun Safe mode consists of a coarse sun-pointing set of algorithms that puts the spacecraft into this thermally safe and power positive attitude and can be achieved wihin a required amount of time from any initial attitude, provided that the system momentum is within the momentum capability of the reaction wheels. On LRO the Sun Safe mode makes use of coarse sun sensors (CSS), an inertial reference unit (IRU) and reaction wheels (RW) to slew the spacecraft to a solar inertial pointing. The CSS and reaction wheels have some level of redundancy because of their numbers. However, the IRU is a single-point-failure piece of hardware. Without the rate information provided by the IRU, the Sun Safe control algorithms could not maintain the required pointing, so a sub-mode of the Sun Safe mode that does not use the IRU was designed. This submode, referred to as the Sun Safe Gyroless control mode, consists of an algorithm that estimates rate information from the CSS and the RW measurements. RW momentum information is used to estimate the body rate parallel to the target sunline, which CSS alone would not be able to observe. Sun Safe can be autonomously, or via ground command, entered from any other control mode and in the event the IRU is not providing rate information, the control mode is switched to the gyroless submode. This paper looks at the design of the Sun Safe modes and discusses the constraints placed on the algorithm and how the mode wored around these constraints. Items of particular interest include CSS placement on the Solar Array (SA) and its implications to design, estimation of body rate information for the Sun Safe Gyroless control mode, and the effect of solar eclipse on each of the Sun Safe modes. Placing CSS on the SA was necessary for the means to put the Sun along the targeted sun-line, nominally normal to the SA panels, for all operational considerations. This had design implications for determining a sun vector during normal SA operations, if one or both gimbals become inoperable and when the SA is in a stowed configuration. The ability of body rate estimation in Sun Safe Gyroless not only uses CSS sun vector data but requires RW momentum measuremens to estimate rates parallel to the sun-line. LRO encounters solar eclipses of some length for most of its orbits about the Moon. With the lack of CSS measurement data a design was implemented in both Sun Safe and Sun Safe Gyroless, they differ because of having or not having IRU measurement data, to carry the spacecraft through these eclipse periods. This paper also includes some discussion of sun avoidance and how it affected design decisions during nominal and eclipse perids for each of the Sun Safe modes.

Garrick, Joseph↗