Engineering topics
Publications and source records attributed to Vandermey, Nancy.
Examples of how toolset selection criteria and capabilities havehelped or hindered MSL planning will be presented. Ongoingimprovements to MSL toolsets and processes, as well as to sharedrelay tools such as Mars Relay Operations Service (MaROS) andGeneral Telecom Predictor (GTP) are also discussed in this paper.
The Mars Science Laboratory (MSL) strategic communications planning toolset selects orbiter relay opportunities that the rover will use for transmitting data back to Earth. The toolset was extensively reworked in preparation for the Interior Exploration using Seismic Investigations, Geodesy and Heat Transport's (InSight) arrival at Mars in November 2018 and the regular use of Mars Atmosphere and Volatile Evolution (MAVEN) and Trace Gas Orbiter (TGO) orbiters as relay assets in addition to Mars Reconnaissance Orbiter (MRO) and 2001 Mars Odyssey (ODY). Overflight selection criteria was automated in the new toolset to take into account overflight deconfliction and down-selection as well as tactical timeline planning impacts and total data return. This was done while remaining flexible and configurable for changing mission priorities. As the Curiosity rover ages, the MSL planning team must overcome issues such as reduced budgets, memory bank anomalies, and reduced power availability. These are some examples of factors that affect the strategic communications planning toolset. In addition to adapting to evolving internal mission needs, the toolset must also be flexible to changes in the relay planning interface with other landers. The concept of shared relay or “split passes” was introduced when InSight began operating on Mars just 600 kilometers away and at the same longitude as MSL. This proximity meant that orbiters could now communicate with two landers during the same relay session. Over time, this new operational use-case became common practice as InSight and MSL settled into relay planning negotiations. Today, many TGO relay sessions are shared between MSL and InSight. As more orbiters pursue integrating this capability into nominal relay operations, and more landers arrive on Mars, the strategic communications process and toolsets increases in complexity. Development of a single tool that schedules relay sessions for all orbiters and landers simultaneously may become necessary as the number of Martian spacecraft increases. Examples of how toolset selection criteria and capabilities have helped or hindered MSL planning will be presented. Ongoing improvements to MSL toolsets and processes, as well as to shared relay tools such as Mars Relay Operations Service (MaROS) and General Telecom Predictor (GTP) are also discussed in this paper. Examples of how toolset selection criteria and capabilities have helped or hindered MSL planning will be presented. Ongoing improvements to MSL toolsets and processes, as well as to shared relay tools such as Mars Relay Operations Service (MaROS) and General Telecom Predictor (GTP) are also discussed in this paper.
The Cassini F-Ring & Proximal Orbits (FRPO) is a new and unique mission; to ensure the highest priority science gets implemented, the POST (Proximal Orbit Science Team) was created to pre-allocate the time around periapse for all 22 proximal orbits. The F-ring orbits, and proximal time outside of POST, were handled similar to Cassini’s Solstice Mission using the Pre-Integrated Event (PIE) process. The new and unique properties of the spacecraft’s trajectory required much forethought to be flown safely while still planning for the most and best science return possible. Some ring-plane crossings (RPX) will be protected against dust impacts by turning the high gain antenna (HGA) to the dust RAM direction (HGA2RAM). If on the first proximal RPX higher than expected dust readings are seen then the Project Office may choose to require more (all) subsequent RPX to be HGA2RAM, implemented via a real-time command overlay for uplinked sequences. The pointing uncertainties will be larger than usual after the final targeted flyby; some of the process changes to address this include adding extra orbit trim maneuvers (OTMs) (fuel permitting) to resync to the reference trajectory and reduce pointing uncertainties; and movable blocks of commands to be used for some periapses where atmospheric drag may cause large timing shifts Changes made for FRPO to address perceptions that these sequences will be hard to implement include requiring early pointing designs (during integration) for certain types of observations, requiring teams to check early on that they can turn to and from their observation attitude, and that their attitude is safe, and adjusting the Implementation process to give more time for science observation designers. This paper will discuss these process changes and lessons learned so far.
The Cassini Solstice Mission (CSM) is the second extended mission phase of the highly successful Cassini/Huygens mission to Saturn. Conducted at a much-reduced funding level, operations for the CSM have been streamlined and simplified significantly. Integration of the science timeline, which involves allocating observation time in a balanced manner to each of the five different science disciplines (with representatives from the twelve different science instruments), has long been a labor-intensive endeavor. Lessons learned from the prime mission (2004-2008) and first extended mission (Equinox mission, 2008-2010) were utilized to design a new process involving PIEs (Pre-Integrated Events) to ensure the highest priority observations for each discipline could be accomplished despite reduced work force and overall simplification of processes. Discipline-level PIE lists were managed by the Science Planning team and graphically mapped to aid timeline deconfliction meetings prior to assigning discrete segments of time to the various disciplines. Periapse segments are generally discipline-focused, with the exception of a handful of PIEs. In addition to all PIEs being documented in a spreadsheet, allocated out-of-discipline PIEs were entered into the Cassini Information Management System (CIMS) well in advance of timeline integration. The disciplines were then free to work the rest of the timeline internally, without the need for frequent interaction, debate, and negotiation with representatives from other disciplines. As a result, the number of integration meetings has been cut back extensively, freeing up workforce. The sequence implementation process was streamlined as well, combining two previous processes (and teams) into one. The new Sequence Implementation Process (SIP) schedules 22 weeks to build each 10-week-long sequence, and only 3 sequence processes overlap. This differs significantly from prime mission during which 5-week-long sequences were built in 24 weeks, with 6 overlapping processes.
The Cassini orbiter is an international science mission to the Saturnian system with 12 science instruments onboard. The Cassini spacecraft lacks a scan platform, which means the entire spacecraft must be rotated to control pointing of any one instrument's boresight. The resulting complex sequences of commands are built beginning many months before execution onboard. Late ephemeris updates from improved navigation data (i.e. after an orbital trim maneuver) often result in pointing commands in the sequence no longer being accurate enough to obtain the desired science observation. This paper will provide an overview of how Cassini uses live updates to address this potential loss of data, including the software developed for this process.
The Cassini-Huygens Program is an international science mission to the Saturnian system. Three space agencies and seventeen nations contributed to building the Cassini spacecraft and Huygens probe. The Cassini orbiter is managed and operated by NASA's Jet Propulsion Laboratory. The Huygens probe was built and operated by the European Space Agency. The mission design for Cassini-Huygens calls for a four-year orbital survey of Saturn, its rings, magnetosphere, and satellites, and the descent into Titan's atmosphere of the Huygens probe. The Cassini orbiter tour consists of 76 orbits around Saturn with 45 close Titan flybys and 8 targeted icy satellite flybys. The Cassini orbiter spacecraft carries twelve scientific instruments that are performing a wide range of observations on a multitude of designated targets. The Huygens probe carried six additional instruments that provided in-situ sampling of the atmosphere and surface of Titan. The multi-national nature of this mission poses significant challenges in the area of flight operations. This paper will provide an overview of the mission, spacecraft, organization and flight operations environment used for the Cassini-Huygens Mission. It will address the operational complexities of the spacecraft and the science instruments and the approach used by Cassini-Huygens to address these issues.