DOCSLIB.ORG

Modeling Spacecraft Safe Mode Events

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Modeling Spacecraft Safe Mode Events Modeling Spacecraft Safe Mode Events Travis Imken Thomas Randolph Jet Propulsion Laboratory Jet Propulsion Laboratory California Institute of Technology California Institute of Technology 4800 Oak Grove Dr. 4800 Oak Grove Dr. Pasadena, CA 91109 Pasadena, CA 91109 818-354-5608 818-354-4871 [email protected] [email protected] Michael DiNicola Austin Nicholas Jet Propulsion Laboratory Jet Propulsion Laboratory California Institute of Technology California Institute of Technology 4800 Oak Grove Dr. 4800 Oak Grove Dr. Pasadena, CA 91109 Pasadena, CA 91109 818-354-2558 818-354-5608 [email protected] [email protected] Abstract — Spacecraft enter a ‘safe mode’ to protect the vehicle failsafe mode. These ‘safe modes’ are architected to when a potentially harmful anomaly occurs. This minimally- guarantee a vehicle can wait in a safe operating state until functioning state isolates faults, establishes contact with Earth, ground operators can recover and restore nominal operations. and orients the vehicle into a power positive attitude until The characteristics of this safe state are common across operators intervene. Though ‘safings’ are inherently missions: isolate faults to prevent further propagation, unpredictable, mission teams build in time margin during operations to determine root causes and restore functionality. establish and maintain communications with Earth, orient the Planning and managing this margin is both critical and enabling vehicle in a power-positive and thermally stable on mission architectures dependent on near-continuous configuration, and be able to maintain this state indefinitely. operability – such as a low-thrust electric propulsion mission. Though some in-flight safe mode entries are planned, such as a reboot to initialize a flight software update, the majority of To better quantify the occurrences and severity of safe mode ‘safings’ are unpredicted events or conditions that trigger a anomalies, the Jet Propulsion Laboratory (JPL) has assembled system-level fault protection response. a database of safings from past and active missions. Currently nearly 240 records are captured from 21 beyond-Earth This research considers the subset of anomalies that result in missions, stemming from a collaboration between teams at JPL, safe mode entries. Spacecraft fault management is designed Ames Research Center, Goddard Space Flight Center, and the Johns Hopkins University Applied Physics Laboratory. This to handle a spectrum of faults and anomalies seen across paper discusses the event database, explores a statistical software, hardware, and payloads. When an anomaly is approach in modeling the occurrences and severity of safing detected, fault protection will first work to isolate the issue at events, presents a simulation technique, and details the component level. If the fault persists, subsystems or recommendations and future work to benefit future concepts. instruments can be isolated and marked as ‘sick’. At this tier, the issue will be noted in the next communications pass and the vehicle will continue with nominal operations. However, TABLE OF CONTENTS further fault containment failures will trigger a system-level response, often leading to a safe mode entry. Safing events 1. INTRODUCTION AND MOTIVATION ...................... 1 stand apart from other flight anomalies because of the 2. SAFE MODE EVENT DATABASE ............................ 2 technical investigation and engineering and management 3. MODELING OCCURRENCES AND RECOVERIES ... 3 team effort involved in the recovery process. The significant 4. APPLICABILITY TO FUTURE MISSIONS ................ 7 time spent to recover from each safing culminates into a 5. RECOMMENDATIONS AND FORWARD WORK ...... 9 significant impact on overall spacecraft rates of operability. 6. CONCLUSIONS ..................................................... 10 Each safing event requires a coordinated and methodical ACKNOWLEDGEMENTS ............................................ 11 response to recover the spacecraft. Spacecraft teams work to REFERENCES............................................................. 11 diagnose and understand the issue, ensuring that the anomaly BIOGRAPHY .............................................................. 11 is not persistent and the planned operations can be resumed. The cumulative impacts of safing events are realized when the vehicle is in flight. To manage this, margins for 1. INTRODUCTION AND MOTIVATION operational outages are prepared throughout the development phases when designing trajectories, planning critical events, Since the development of the Galileo mission1, spacecraft and developing science campaigns. To better quantify these designers have implemented an onboard, self-detecting 1 Galileo has the first recorded (and located) event on November 28, 1989. 978-1-5386-2014-4/18/$31.00 ©2018 IEEE 1 margins on future mission concepts, a statistical approach is 1. 196 of the records are from anomalous events throughout applied to safing data from past and present missions to a mission’s primary and extended phases. 12 of these records model event occurrences and recovery durations. are ‘cascading’ events, where the spacecraft re-entered safe mode before recovery from the previous event was complete. Motivation Of these 196, 151 of the events have sufficient details and Initial research into modeling safing events was funded by context to reconstruct the diagnosis and recovery timeline. the proposed Asteroid Robotic Redirect Mission (ARRM). Ancillary data is also recorded for each event including ARRM’s concept baselined a 40 KW solar electric mission phase, vehicle location, and anecdotal information propulsion (EP) system to reach asteroid 2008 EV5. [1] Low- from the recovery process. Root causes, as specified and thrust EP technologies are uniquely enabling compared to recorded by each mission team, are captured and binned into chemical propulsion systems because they allow the flight software, hardware, operations, space environments, or system to achieve large changes in spacecraft velocity on a unknown categories. Unknown events are anomalies where comparatively small propellant mass. JPL has flown EP root cause is undeterminable by the mission team. technologies on the Deep Space 1 (DS1) and Dawn missions, The event database has been collected through a and has baselined their use on the planned Psyche mission collaboration between JPL, NASA’s Goddard Space Flight and the Next Mars Orbiter (NeMO) mission concept. [2] [3] Center, NASA’s Ames Research Center, and the Johns EP engines produce low thrust levels, requiring near- Hopkins University Applied Physics Lab – please see the continuous periods of operability for maneuvers. Trajectories Acknowledgements section. Research is ongoing to capture may require weeks or months of thrusting at a time, additional details and to locate records for missions not yet increasing the likelihood that a safing anomaly will interrupt included in the database. the planned maneuver. For example, Dawn arrived at Ceres Table 1. The safe mode database captures events from 26 days late from a four day safing event and thrust outage. 168 years of cumulative flight time on missions [4] Similar to DS1 and Dawn, ARRM trajectory designers throughout the solar system. performed ‘missed thrust analyses’ to build robustness into maneuvers. This robustness is essential due to the non- Mission Launch Destination linearity of low thrust trajectories. These analyses model the impact of anomalies by injecting multi-day thrust outages Galileo 1989 Jupiter into the planned trajectory and recalculating new solutions. Mars Global Surveyor 1996 Mars While the missed thrust analyses give confidence a vehicle Cassini 1997 Saturn will reach the final destination, the flight system may realize lower system-level margins, such as requiring more Deep Space 1 1998 9969 Braille propellant or increasing the time-of-flight. [5] [6] Mars Climate Orbiter2 1998 Mars 2 EP missions are not the only architectures sensitive to safing Mars Polar Lander 1999 Mars events. Time-constrained missions, such as Europa Clipper, Stardust 1999 81P/Wild could be impacted by missed maneuver opportunities and Genesis 2001 Earth Sun L1 brief science windows. Clipper will complete up to 45 flybys Mars Odyssey 2001 Mars of Europa on a 14.2 day orbit cadence. The mission uses a chemical propulsion system to adjust the trajectory as the Spitzer (Telescope) 2003 Earth Trailing spacecraft travels within 25 km of the icy moon’s surface. A Deep Impact 2005 Tempel 1 safe mode entry could cause missed maneuvers, introducing Mars Reconnaissance Obiter 2005 Mars a non-zero probability that Clipper could impact Europa, require a redesign of its trajectory, or miss science New Horizons 2006 Pluto observations over a region of the icy moon that may not be Dawn 2007 Vesta, Ceres revisited within the mission’s lifetime. [7] Phoenix2 2007 Mars Missed thrust analyses on DS1 and Dawn were done using Kepler (Telescope) 2009 Earth Trailing engineering best estimates for periods of inoperability. [6] To Lunar Reconnaissance Orbiter 2009 Moon improve on this, ARRM sought to leverage nearly thirty years Juno 2011 Jupiter of beyond-Earth flight data. However, no comprehensive 2 database, literature, or analysis of events was located. Thus Mars Science Laboratory 2011 Mars began the task to create and explore this database. Mars Atmosphere and 2013 Mars Volatile Evolution OSIRIS-REx 2016 Bennu 2. SAFE MODE EVENT DATABASE The
Load more

Recommended publications
  • Mars Reconnaissance Orbiter
    Chapter 6 Mars Reconnaissance Orbiter Jim Taylor, Dennis K. Lee, and Shervin Shambayati 6.1 Mission Overview The Mars Reconnaissance Orbiter (MRO) [1, 2] has a suite of instruments making observations at Mars, and it provides data-relay services for Mars landers and rovers. MRO was launched on August 12, 2005. The orbiter successfully went into orbit around Mars on March 10, 2006 and began reducing its orbit altitude and circularizing the orbit in preparation for the science mission. The orbit changing was accomplished through a process called aerobraking, in preparation for the “science mission” starting in November 2006, followed by the “relay mission” starting in November 2008. MRO participated in the Mars Science Laboratory touchdown and surface mission that began in August 2012 (Chapter 7). MRO communications has operated in three different frequency bands: 1) Most telecom in both directions has been with the Deep Space Network (DSN) at X-band (~8 GHz), and this band will continue to provide operational commanding, telemetry transmission, and radiometric tracking. 2) During cruise, the functional characteristics of a separate Ka-band (~32 GHz) downlink system were verified in preparation for an operational demonstration during orbit operations. After a Ka-band hardware anomaly in cruise, the project has elected not to initiate the originally planned operational demonstration (with yet-to-be­ used redundant Ka-band hardware). 201 202 Chapter 6 3) A new-generation ultra-high frequency (UHF) (~400 MHz) system was verified with the Mars Exploration Rovers in preparation for the successful relay communications with the Phoenix lander in 2008 and the later Mars Science Laboratory relay operations.
    [Show full text]
  • FDIR Variability and Impacts on Avionics
    FDIR variability and impacts on avionics : Return of Experience and recommendations for the future Jacques Busseuil Antoine Provost-Grellier Thales Alenia Space ADCSS 2011- FDIR - 26/10/2011 All rights reserved, 2007, Thales Alenia Space Presentation summary Page 2 • Survey of FDIR main features and in-flight experience if any for various space domains and missions Earth Observation (Meteosat Second Generation - PROTEUS) Science missions (Herschel/Planck) Telecommunication (Spacebus – constellations) • FDIR main features for short term ESA programs and trends (if any!) Exploration missions (Exomars) Meteosat Third Generation (MTG) The Sentinels Met-OP Second Generation • Conclusion and possible recommendations From in-flight experience and trends Thales Alenia Spacs ADCSS 2011- FDIR - 26/10/11 All rights reserved, 2007, Thales Alenia Space MSG (1) – FDIR Specification Page 3 The MeteoSat 2nd Generation has a robust concept : Spin stabilised in GEO : no risk of loss of attitude control 360° solar array : solar power available in most satellite attitudes on-board autonomy requirements : GEO - normal operations : 24 hours autonomous survival after one single failure occurrence. LEOP - normal operations : 13 hours autonomous survival after one single failure occurrence (one eclipse crossing max.) GEO & LEOP - critical operations : ground reaction within 2 minutes FDIR implementation to cover autonomy requirement Time criticality (in GEO normal ops) criticality < 5 sec handled at unit H/W level criticality > 5sec & < 24hours handled at S/W level criticality > 24hours handled by the ground segment On-board autonomous actions classification level A: handled internally to CDMU / DHSW: transparent wrt mission impacts. (e.g. single bit correction) level B: action limited to a few units reconfiguration or switch-off.
    [Show full text]
  • Jpl Anomaly Issues
    National Aeronautics and Space Administration Jet Propulsion Laboratory California Institute of Technology JPL ANOMALY ISSUES Henry B. Garrett Jet Propulsion Laboratory California Institute of Technology Pasadena, CA, 91109 National Aeronautics and Space Administration Jet Propulsion Laboratory California Institute of Technology Space Weather Anomaly Concerns for JPL Robotic Mission AGENDA Overview of Space Weather Anomalies on JPL Missions Space Weather Products used by JPL Ops for Anomaly Mitigation and Resolution Suggested Improvements in Anomaly Mitigation Procedures for JPL Missions Summary National Aeronautics and Space Administration Jet Propulsion Laboratory California Institute of Technology Overview of Space Weather Anomalies on JPL Missions National Aeronautics and Space Administration Jet Propulsion Laboratory Space Weather Effects on Ops California Institute of Technology Some Examples of Space Weather Effects on JPL Spacecraft Ops National Aeronautics and Space Administration Solar Proton Event (SPE) Jet Propulsion Laboratory California Institute of Technology Effects on Cassini Lessons Learned: Real Time SPE Observations can Predict Effects on Ops (Cassini Solid State Recorder Upsets) National Aeronautics and Space Administration Space Weather Anomalies on JPL Ops Jet Propulsion Laboratory California Institute of Technology During the 2003 Halloween Storms Oct 23: Genesis at L1 entered safe mode. Normal operations resumed on Nov. 3 Oct 24: Midori-2 Polar satellite failed (Spacecraft Charging…) Stardust comet mission went into safe mode; recovered. Oct 28: ACE lost plasma observations. Mars Odyssey entered Safe mode Oct 29: During download Mars Odyssey had a memory error MARIE instrument powered off (has NOT recovered) Oct 30: Both MER entered “Sun Idle” mode due to excessive star tracker events Two UV experiments on GALEX had excess charge so high voltages turned off.
    [Show full text]
  • Amazing Discoveries Satellite Schedule
    Amazing Discoveries Satellite Schedule Thatch is starred: she pullulating serially and mail her bow. Devoted Jacques sometimes compromises his sax unpoetically and jollying so temporarily! Hindu and loosest Grover denominates her limits forsaking laudably or kiboshes ripely, is Aldric tangential? It is now on a collision course with Earth. With their computer codes using a technique called machine learning the researchers in Bern and Seattle were able to calibrate the Kepler data within record time working day and night. Astronomy has seen so much progress and change in the last decade. Circumbinary planets are those that orbit two stars. The images we returned, built, astronomers and engineers devised a way to repurpose and save the space telescope by changing its field of view periodically. The hotter it gets, the star and the planet. Five, or after all that planning, smartest opinion takes of the week. This is similar to a normal safe mode configuration, NASA calibrates the data of the Kepler Space Telescope in a lengthy procedure before public release, sunlight is one hundred times weaker. Supercomputers are changing the way scientists explore the evolution of our universe, but generally orbit so close to their parent stars that they are hot, to understand its deep history and explore its rings. The water that now lies frozen within its interior was once liquid. At the end of the mission the spacecraft was low on fuel and it had suffered a lot of radiation damage, except for Venus and Uranus, such as its size and how long it takes to orbit. Lyra region in the northern sky was chosen for its rich field of stars somewhat richer than a southern field.
    [Show full text]
  • Mars Reconnaissance Orbiter Aerobraking Daily Operations and Collision Avoidance†
    MARS RECONNAISSANCE ORBITER AEROBRAKING DAILY † OPERATIONS AND COLLISION AVOIDANCE Stacia M. Long1, Tung-Han You2, C. Allen Halsell3, Ramachand S. Bhat4, Stuart W. Demcak4, Eric J. Graat4, Earl S. Higa4, Dr. Dolan E. Highsmith4, Neil A. Mottinger4, Dr. Moriba K. Jah5 NASA Jet Propulsion Laboratory, California Institute of Technology Pasadena, California 91109 The Mars Reconnaissance Orbiter reached Mars on March 10, 2006 and performed a Mars orbit insertion maneuver of 1 km/s to enter into a large elliptical orbit. Three weeks later, aerobraking operations began and lasted about five months. Aerobraking utilized the atmospheric drag to reduce the large elliptical orbit into a smaller, near circular orbit. At the time of MRO aerobraking, there were three other operational spacecraft orbiting Mars and the navigation team had to minimize the possibility of a collision. This paper describes the daily operations of the MRO navigation team during this time as well as the collision avoidance strategy development and implementation. 1.0 Introduction The Mars Reconnaissance Orbiter (MRO) launched on August 12, 2005, onboard an Atlas V-401 from Cape Canaveral Air Station. Upon arrival at Mars on March 10, 2006, a Mars orbit insertion (MOI) maneuver was performed which placed MRO into a highly elliptical orbit around the planet. This initial orbit had a 35 hour period with an approximate apoapsis altitude of 45,000 km and a periapsis altitude of 430km. In order to establish the desired science orbit, MRO needed to perform aerobraking while minimizing the risk of colliding with other orbiting spacecraft. The focus of this paper is on the daily operations of the navigation team during aerobraking and the collision avoidance strategy developed and implemented during that time.
    [Show full text]
  • In-Flight Validation of Akatsuki X-Band Deep Space Telecommunication Technologies
    Trans. JSASS Aerospace Tech. Japan Vol. 10, No. ists28, pp. To_3_7-To_3_12, 2012 Topics In-FlightIn-Flight Validation Validation of Akatsuki of Akatsuki X-Band X-Band Deep SpaceDeep SpaceTelecommu- Telecommunicationnication Technologies Technologies By Tomoaki TODA and Nobuaki ISHII Japan Aerospace Exploration Agency, Institute of Space and Astronautical Science, Sagamihara, Japan (Received June 24th, 2011) Akatsuki is the Japanese first Venus exploration program. The spacecraft was successfully launched in May 21st 2010 from Tanegashima Space Center via H II-A vehicle. One of her missions is a flight demonstration of her telecommunication system developed for supporting Japanese future deep space missions. During her half-year cruising phase heading for Venus, we had conducted checkouts of the system. The key technologies are a deep space transponder, a set of onboard antennas, and power amplifiers. They all were newly introduced into Akatsuki. Their performances had been tested through the half-year operations and been investigated by using collective data obtained in the experiments. Our regenerative ranging was also demonstrated in these activities. We proved that the newly introduced telecommunication system worked exactly as we had designed and that the system performances were the same as evaluated on the ground. In this paper, we will summarize these in-flight validations for the Akatsuki telecommunication system. Key Words: Akatsuki, PLANET-C, Deep Space Telecommunications, Regenerative Ranging 1. Introduction block diagram of Akatsuki. The redundancy is given to TRPs and 10 W solid-state power amplifiers (SSPAs). The TWTA is Akatsuki is the Venus exploration program of Japan Aero- provided for the increase of scientific data acquisition.
    [Show full text]
  • Mars Express
    Report to Solar System and Exploration Working Group (SSEWG) on Solar System Missions in Operation - February 2010 Gerhard Schwehm, Head of Solar System Science Operations Division/SRE-OS For SOHO, the Solar and Heliospheric Observatory, the spacecraft status continues to be nominal, with the High Gain Antenna (HGA) Z-axis in a fixed position. All 12 instruments continue to provide data. However, in SUMER the central (KBr coated) part of detector B did suffer a dramatic loss of gain. Only the "bare" side parts of the detector remain usable. Science will still be possible, but the use of the instrument will be more complicated. Future observing programs will have to be revised and adapted to the new configuration. The SOHO long term science archive, that has been implemented as part of the science archive infrastructure at ESAC has been opened for access to the wide scientific community. Due to orbit perturbations by the Sun and the moon, the apogee of the Cluster spacecraft has been slowly drifting away from Earth and reached an altitude above 300000 km. To keep a good communication link with the ground stations, the apogee of the four Cluster spacecraft was lowered in November 2009 by about 5000 km. Still the fuel remaining in the spacecraft ranges from 6 and 8 kg which is enough for a few more years of operations since less than 1 kg is usually consumed per year. In November 2009 the ion detector (CIS) on spacecraft 3 experienced an anomaly. Attempts to switch it on again were not successful. The PI team is investigating the cause of the anomaly.
    [Show full text]
  • A Year in the Life of the Cassini-Huygens Mission
    A Year in the Life of the Cassini-Huygens Mission Kim Steadman & Trina Ray Jet Propulsion Laboratory, California Institute of Technology National Aeronautics and Space Administration Jet Propulsion Laboratory California Institute of Technology The year is 2010… 2010 in context… Science Planning Three things that make Science Planning Hard… • Distributed operations – Additional and more complex interfaces – Extensive collection of planning rules to enforce – Substantial investment in complying with ITAR restrictions – Remoteness and time zones – Small distributed team supporting a concurrent and overlapping and iterative uplink development process Three things that make Science Planning Hard… • Distributed operations – Mismatch between spacecraft design and operations environment – Additional and more complex interfaces – Extensive collection of planning rules to enforce – Substantial investment in complying with ITAR restrictions – Remoteness and time zones Three things that make Science Planning Hard… • Distributed operations – Mismatch between spacecraft design and operations environment – Additional and more complex• Managinginterfaces the shared spacecraft resources – Extensive collection of planning– rulesSpacecraft pointing to enforce – Instrument data collection rates – Substantial investment in complying– Power with ITAR restrictions – Solid-state recorder storage – Remoteness and time zones – Deep Space Network scheduling – Reaction Wheels Three things that make Science Planning Hard… • Distributed operations – Mismatch between
    [Show full text]
  • MEXEC: an ONBOARD INTEGRATED PLANNING and EXECUTION APPROACH for SPACECRAFT COMMANDING Virtual Conference 19–23 October 2020 M
    i-SAIRAS2020-Papers (2020) 5048.pdf MEXEC: AN ONBOARD INTEGRATED PLANNING AND EXECUTION APPROACH FOR SPACECRAFT COMMANDING Virtual Conference 19–23 October 2020 M. Troesch1, F. Mirza1, K. Hughes1, A. Rothstein-Dowden1, R. Bocchino1, A. Donner1, M. Feather1, B. Smith1, L. Fesq1, B. Barker1, and B. Campuzano1 1Jet Propulsion Laboratory, California Institute of Technology, 4800 Oak Grove Drive, Pasadena, CA 91109, USA, E-mail: [email protected] Ó 2020. California Institute of Technology. Government Sponsorship Acknowledged. Appeared in Troesch, M.; Mirza, F.; Hughes, K.; Rothstein-Dowden, A.; Bocchino, R.; Donner, A.; Feather, M.; Smith, B.; Fesq, L.; Barker, B.; and Campuzano, B. MEXEC: An Onboard Integrated Planning and Execution Ap- proach for Spacecraft Commanding. In Workshop on Integrated Execution (IntEx) / Goal Reasoning (GR), Interna- tional Conference on Automated Planning and Scheduling (ICAPS IntEx/GR 2020), October 2020. EXTENDED ABSTRACT Agent, which was demonstrated on Deep Space One (DS1) [4]. Remote Agent flew on DS1 for 48 hours The preValent form of spacecraft commanding is and used model-based programming and onboard through the use of sequences. Sequences generally search with goal-based, closed-loop commanding to define a sequence of commands to execute at abso- achieve more autonomous behavior. lute or relative times, but they contain no information about why a specific command is needed or why a The Autonomous Sciencecraft Experiment (ASE) on command is scheduled in a particular way to achieVe Earth ObserVing One (EO-1) [5] on goals with robust a desired effect [1]. Although some sequences allow execution by responding to events and anomalies at for control logic, such as if statements or loops, and execution time.
    [Show full text]
  • Curiosity Rover Exits 'Safe Mode' 20 March 2013, by Guy Webster
    Curiosity rover exits 'safe mode' 20 March 2013, by Guy Webster Engineers quickly diagnosed the software issue that prompted the safe mode on March 16 and know how to prevent it from happening again. Other upcoming activities include preparations for a moratorium on transmitting commands to Curiosity during most of April, when Mars will be passing nearly directly behind the sun from Earth's perspective. The moratorium is a precaution against interference by the sun corrupting a command sent to the rover. NASA's Mars Science Laboratory project is using Curiosity and the rover's 10 science instruments to investigate environmental history within Gale Crater, a location where the project has found that conditions were long ago favorable for microbial life This self-portrait of NASA's Mars rover Curiosity . JPL, a division of the California Institute of combines 66 exposures taken by the rover's Mars Hand Technology in Pasadena, manages the project for Lens Imager (MAHLI) during the 177th Martian day, or NASA's Science Mission Directorate in sol, of Curiosity's work on Mars (Feb. 3, 2013). Credit: Washington. NASA/JPL-Caltech/MSSS More information: More information about Curiosity is online at www.jpl.nasa.gov/msl , www.nasa.gov/msl and mars.jpl.nasa.gov/msl/ . (Phys.org) —NASA's Mars rover Curiosity has returned to active status and is on track to resume science investigations, following two days in a precautionary standby status, "safe mode." Provided by NASA Next steps will include checking the rover's active computer, the B-side computer, by commanding a preliminary free-space move of the arm.
    [Show full text]
  • Lost in Space ? Support, ESOC, Darmstadt, Germany - ESOC Always Comes to the Rescue
    ESOC-RESCUE 2/26/04 2:59 PM Page 54 Technical and Operational Support The Main Control Room at ESA’s European Space Operations Centre (ESOC) in Darmstadt, Germany 54 esa bulletin 117 - february 2004 www.esa.int ESOC-RESCUE 2/26/04 2:59 PM Page 55 ESOC to the Rescue A. Smith, R. Muench, W. Wimmer, D. Heger, X. Marc, F. Bosquillon de Freschville, M. Rosengren, T. Morley, S.Pallashke, B. Smeds, C. Sollazzo & A. McDonald (Logica) ESA Directorate of Technical and Operational Lost in Space ? Support, ESOC, Darmstadt, Germany - ESOC Always Comes to the Rescue Since supporting its first launch in 1968, ESA’s European Space Operations Centre (ESOC) in Darmstadt, Germany, has supported 51 spacecraft during the critical launch and early orbit phases of their missions, and nearly all of them throughout their subsequent operational phases. The great diversity of these missions has given ESOC a well-justified reputation as one of the world’s leading control centres for unmanned spacecraft. Perhaps less well known is the contribution that ESOC has made to the rescue of many missions that have suffered major anomalies and would otherwise have had to be abandoned or would have failed to achieve their mission goals. www.esa.int esa bulletin 117 - february 2004 55 ESOC-RESCUE 2/26/04 2:59 PM Page 56 Technical and Operational Support Background When called upon, ESOC has been able to respond immediately, exploiting the In-orbit equipment malfunctions or facilities, experience and expertise that it failures are a fact of life for all space has at its disposal to effect a rescue.
    [Show full text]
  • Examples of Space Environment Effects on Satellites
    Space Weather Bootcamp 2018 Examples of Space Environment Effects on Satellites 1 Space Weather Bootcamp 2018 2003 Halloween Storm Impacts on Spacecraft (1) • Oct 23: • Genesis satellite at L1 entered safe mode, normal operations resumed on Nov. 3. • Midori-2(ADEOS-2) Earth-observing satellite power system failed, safe mode, telemetry lost (23:55), spacecraft lost • Oct 24: • Stardustcomet mission went into safe mode due to read errors; recovered. • Chandra X-ray Observatory astronomy satellite observations halted due to high radiation levels (09:34EDT), restarted Oct. 25 • GOES-9, 10 and 12 had high bit error rates (9 and 10), magnetic torquers disabled due to geomagnetic activity • Oct 25: • RHESSI solar satellite had spontaneous CPU reset (10:42) • Oct 26: • SMART-1had auto shutdown of engine due to increased radiation level in lunar transfer orbit (19:23) • Oct 27: • NOAA-17AMSU-A1 lost scanner • GOES-8 X-ray sensor turned itself off and could not be recovered • Oct 28-30: • Astronauts on Intl. Space Station went into service module for radiation protection • Instrument on Integral satellite went into safe mode because of increased radiation • Chandra observations halted again autonomously, resumed Nov 1 2 Space Weather Bootcamp 2018 Major indices during 2003 Dst, Kp, F10.7 DOY 296: Oct 23 3 Space Weather Bootcamp 2018 2003 Halloween Storm Impacts on Spacecraft (2) • Oct 28: • DMSP F16 SSIES sensor lost data twice, on Oct. 28 and Nov. 3; recovered. microwave sounder lost oscillator; switched to redundant system • SIRTF, in orbit drifting behind Earth, turned off science experiments and went to Earth pointing due to high proton fluxes, 4 days of operations lost • Microwave Anisotropy Probe spacecraft star tracker reset and backup tracker autonomously turned on, prime tracker recovered • Oct 29: • Kodamadata relay satellite in GEO; safe mode, signals noisy, recovery unknown • RHESSIsatellite had 2 more spontaneous resets of CPU (28, 17:40; 29, 03:32).
    [Show full text]