SNAP: Small Next-generation Atmospheric Probe: Enabling Future Multi-Probe Missions
Explore the source record for details and available documents.
Kunio Sayanagi↗
SEARCH · Search NASA
Results for “multi mission”
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.
A Novel High-Performance Mission-Enabling Multi-Purpose Radioisotope Heat Source
Recent studies indicate science mission concepts targeting access to the sub-surface oceans of icy moons require ice-penetrating cryobots powered by advanced Radioisotope Power Systems (RPS). These systems would deliver waste heat for ice-melting in the range of 10 kW. Minimizing the transit time through the kilometers-thick ice shells to just a few years requires these RPS to utilize heat sources having a higher thermal energy volumetric density than the existing flight-qualified General-Purpose Heat Source (GPHS). A Compact Heat Source (CPHS)has been conceptualized in which the graphite impact shells(GIS) of the existing GPHS are rearranged in a hexagonal aeroshell containing seven GIS per module, as opposed to the standard two per module; offering a thermal energy density of 0.57 W/cm3versus 0.29 W/cm3 offered by the GPHS simply from the repackaging of Technology Readiness Level (TRL)9 subassemblies. Preliminary thermal modeling of the CPHS integrated into a notional radioisotope thermoelectric generator(RTG) structure further suggests that centerline temperatures are well within allowable limits during nominal operation. Given the need for the CPHS for a subset of missions, it is worth exploring the applicability of the CPHS for more general RTG purposes. We discuss herein how the CPHS may be implemented with either heritage or in-development thermoelectric converter technologies into a Next-Generation RTG concept. Due to a higher energy density, the legacy heat rejection fin arrangement must be modified to permit a sufficiently low cold-side temperature. Preliminary finite element analysis suggests fin-root temperatures can be kept as low as 520 K while allowing the generator to fit within the usable dimensions of currently available United States Department of Energy shipping containers. Such temperatures would certainly be compatible with the use of high temperature thermoelectric converter technologies.. A prime candidate is the heritage silicon-germanium (SiGe) unicouple, whose design could be adapted by approximately halving the leg-length, but without changes in hot and cold junction interfaces, which are features critical to the proven performance and reliability of these devices. The estimated Beginning of Life power for a SiGe-based CPHS-RTG using 12 CPHS for a thermal inventory of 10.5 kW is greater than 600 W under deep space operating conditions. Using higher performance segmented couples currently in development that are based on skutterudite,La3−xTe4and 14-1-11 Zintl thermoelectric materials in lieu of the SiGe unicouples would increase the power level to more than1 kW. The high specific power (We/kg) attribute of CPHS-RTGs found in this study could potentially enable Radioisotope Electric Propulsion (REP) mission concepts. Past NASA REP mission concept studies identified specific power needs in excess of 6to 8 We/kg. Based on a GPHS-RTG-like system configuration, we show that at fin root temperatures between 530 K and 570K (deep space environment), specific powers exceeding 10 We/kg are achievable using high performance segmented thermoelectric converters. The compact sizing and power density of the CPHS-RTG would constitute a significant step upgrade in specific power when compared to heritage GPHS-RTG (approximately5.1 We/kg) and off-the-shelf Multi-Mission RTG (approximately 2.6 We/kg).
Nesmith, Bill J.↗
Cislunar Near Rectilinear Halo Orbit for Human Space Exploration
In order to conduct sustained human exploration beyond Low Earth Orbit (LEO), spacecraft systems are designed to operate in a series of missions of increasing complexity. Regardless of the destination, Moon, Mars, asteroids or beyond, there is a substantial set of common objectives that must be met. Many orbit characterization studies have endeavored to evaluate the potential locations in cislunar space that are favorable for meeting common human exploration objectives in a stepwise approach. Multiple studies, by both NASA and other international space agencies, have indicated that Earth-‐moon libration point orbits are attractive candidates for staging operations in the proving ground and beyond. In particular, the Near Rectilinear Orbit (NRO) has been demonstrated to meet multi-‐mission and multi-‐destination architectural constraints. However, a human mission to a selected NRO presents a variety of new challenges for mission planning. While a growing number of robotic missions have completed successful operations to various specific libration point orbits, human missions have never been conducted to orbits of this class. Human missions have unique challenges that differ significantly from robotic missions, including a lower tolerance for mission risk and additional operational constraints that are associated only with human spacecraft. In addition, neither robotic nor human missions have been operated in the NRO regime specifically, and NROs exhibit dynamical characteristics that can differ significantly as compared to other halo orbits. Finally, multi-‐body orbits, such as libration point orbits, are identified to exist in a simplified orbit model known as the Circular Restricted Three Body Problem (CRTBP) and must then be re-‐solved in the full ephemeris model. As a result, the behavior of multi-‐body orbits cannot be effectively characterized within the classical two-‐body orbit dynamics framework more familiar to the human spaceflight community. In fact, a given NRO is not identified by a set of Keplerian orbit parameters, and a valid epoch specific state vector must be first obtained from a multi-body dynamical model. In this paper, the significant performance and operational challenges of conducting human missions to the NRO are evaluated. First, a systematic process for generating full ephemeris based ballistic NROs of various families is outlined to demonstrate the relative ease in which a multi-‐revolution orbit can be found for any epoch and for various orbit geometries. In the Earth-‐Moon system, NROs, which are halo orbits with close passage over a lunar pole, can exist with respect to libration point 1 (L1) or libration point 2 (L2) and are either from a North or South family orbit class with respect to the ecliptic. Second, the ability to maintain the orbit over the lifetime of a habitat mission by applying a reliable station-keeping strategy is investigated. The NRO, while similar to the quasi-‐halo orbits that the Artemis mission flew, requires an updated station keeping strategy. This is due to several dynamical differences such as the increased relative stability of the NRO compared to other halo orbits and the close passage over the lunar surface as shown in Figure 1. Multiple station-keeping strategies are being investigated to ensure a human spacecraft remains on a predictable path. As the NRO is not described in simple two-‐body parameters, analysis must determine the best strategy for targeting a reference NRO as well as how closely a future state should be constrained. In addition, costs will be minimized by determining maneuver directionality based on an identified pattern in the optimal station-keeping solutions or an analytically derived relationship. The candidate station-keeping algorithm must be stable and robust to environmental and vehicle uncertainties as well to navigation estimation and flight control execution errors. To that end, navigation accuracies, the impact on the station-keeping execution errors as well as other vehicle uncertainties need to be assessed. Starting with Orion, current navigation accuracies are evaluated and then navigation requirements are derived assuming a desired station-keeping propellant budget. Third, the performance requirements to and from the NRO are evaluated. Important parameters for developing expected propellant costs include epoch of operation, size and type of NRO, Earth departure and return constraints, as well as abort or early-‐return capability. Finally, rendezvous and proximity operations are vital aspects of multi-‐mission human exploration endeavors. The ability to conduct rendezvous and the associated propellant costs are assessed as well as the impacts of various profile assumptions including the location within the NRO the rendezvous is performed. The results of these studies will influence plans for international cooperation on both nearer term proving ground missions and beyond.
Whitley, Ryan↗
Vibration Fixture Design and Testing for Rigid - Y Cable Mount on MMRTG F4
INL is responsible for the fueling and testing of Radioisotope Thermoelectric Generators for NASA space missions. For the upcoming NASA mission "DRAGONFLY," INL is tasked with fueling and testing the Multi-Mission Radioisotope Thermoelectric Generator F4 (MMRTG F4). This involves conducting various tests, such as vibration testing and mass properties testing. For these tests, an interface is required between the MMRTG and the testing equipment, provided by cables mounted on a legacy bracket. Due to design changes in the cooling lines, a new cable – the Rigid Y cable – is to be used. The test described in this poster was to verify if the Rigid Y cable would survive the vibration tests. The results will determine the procedure for conducting the vibration tests on the MMRTG F4.
42 - ENGINEERING↗
Standardized Modular Power Interfaces for Future Space Explorations Missions
Earlier studies show that future human explorations missions are composed of multi-vehicle assemblies with interconnected electric power systems. Some vehicles are often intended to serve as flexible multi-purpose or multi-mission platforms. This drives the need for power architectures that can be reconfigured to support this level of flexibility. Power system developmental costs can be reduced, program wide, by utilizing a common set of modular building blocks. Further, there are mission operational and logistics cost benefits of using a common set of modular spares. These benefits are the goals of the Advanced Exploration Systems (AES) Modular Power System (AMPS) project. A common set of modular blocks requires a substantial level of standardization in terms of the Electrical, Data System, and Mechanical interfaces. The AMPS project is developing a set of proposed interface standards that will provide useful guidance for modular hardware developers but not needlessly constrain technology options, or limit future growth in capability. In 2015 the AMPS project focused on standardizing the interfaces between the elements of spacecraft power distribution and energy storage. The development of the modular power standard starts with establishing mission assumptions and ground rules to define design application space. The standards are defined in terms of AMPS objectives including Commonality, Reliability-Availability, Flexibility-Configurability and Supportability-Reusability. The proposed standards are aimed at assembly and sub-assembly level building blocks. AMPS plans to adopt existing standards for spacecraft command and data, software, network interfaces, and electrical power interfaces where applicable. Other standards including structural encapsulation, heat transfer, and fluid transfer, are governed by launch and spacecraft environments and bound by practical limitations of weight and volume. Developing these mechanical interface standards is more difficult but an essential part of defining physical building blocks of modular power. This presentation describes the AMPS projects progress towards standardized modular power interfaces.
Spacecraft Power↗
The Mars Science Laboratory (MSL) MMRTG In-Flight: A Power Update
The MSL Multi-Mission Radioisotope Thermoelectric Generator (MMRTG) was fueled on October 28, 2008 by the Department Of Energy (DOE) in preparation for a late 2009 launch. Shortly after, the MSL launch was delayed approximately 2 years until 2011. The fueled MMRTG was placed in storage to await the new date for liftoff. Occasional measurements of the MMRTG's power output were taken and compared with power predictions that pre-dated fueling. An error in the predictive models was quickly recognized and remedied. The predictions, while improved, carried significant uncertainty. This uncertainty did not deter the launch of MSL, but did alter the planned mission on the surface of Mars. Once launched, the MSL spacecraft provided a hi-fidelity telemetry stream measuring the generator's electrical and thermal performance. These data were used to update the predictive models and a new prediction of the performance of the MMRTG on the surface of Mars was run just before Entry, Descent, and Landing (EDL) at Mars. The MSL MMRTG is working extremely well, providing power above predictions and operating within its flight allowable temperature limits. The generator was producing approximately 114 W at the beginning of the surface mission. This paper will elaborate on power modeling for the MSL MMRTG along with a review of some of the data recorded from the MSL cruise to Mars, EDL, and the early days of the surface mission.
thermoelectric generator↗
MPST Software: grl_pef_check
This innovation is a tool used to verify and validate spacecraft sequences at the predicted events file (PEF) level for the GRAIL (Gravity Recovery and Interior Laboratory, see http://www.nasa. gov/mission_pages/grail/main/index. html) mission as part of the Multi-Mission Planning and Sequencing Team (MPST) operations process to reduce the possibility for errors. This tool is used to catch any sequence related errors or issues immediately after the seqgen modeling to streamline downstream processes. This script verifies and validates the seqgen modeling for the GRAIL MPST process. A PEF is provided as input, and dozens of checks are performed on it to verify and validate the command products including command content, command ordering, flight-rule violations, modeling boundary consistency, resource limits, and ground commanding consistency. By performing as many checks as early in the process as possible, grl_pef_check streamlines the MPST task of generating GRAIL command and modeled products on an aggressive schedule. By enumerating each check being performed, and clearly stating the criteria and assumptions made at each step, grl_pef_check can be used as a manual checklist as well as an automated tool. This helper script was written with a focus on enabling the user with the information they need in order to evaluate a sequence quickly and efficiently, while still keeping them informed and active in the overall sequencing process. grl_pef_check verifies and validates the modeling and sequence content prior to investing any more effort into the build. There are dozens of various items in the modeling run that need to be checked, which is a time-consuming and errorprone task. Currently, no software exists that provides this functionality. Compared to a manual process, this script reduces human error and saves considerable man-hours by automating and streamlining the mission planning and sequencing task for the GRAIL mission.
Call, Jared A.↗
Detailed Design of an Earth Entry Vehicle for Comet Surface Sample Return
The 2013 Decadal Survey for New Frontiers missions identifies several high-value science missions, including Comet Surface Sample Return (CSSR). A CSSR mission will advance the scientific community's fundamental understanding of the origin of the solar system and the contribution of comets to the volatile inventory of the Earth. An entry capsule, or earth entry vehicle (EEV), is be required to protect the scientific payload from the extreme conditions of atmospheric entry, descent, and landing. The Decadal Survey Mission Concept Study along with an APL (Johns Hopkins University Applied Physics Lab) 2007-2008 Comet Surface Sample Mission Study details several of the driving requirements for a CSSR EEV; these include a payload volume and mass and inertial entry velocity of 9 kilometers per second. The mission concept study selected a Multi-Mission Earth Entry Vehicle (MMEEV) design concept derived from the Mars Sample Return (MSR) entry capsule design because of its increased reliability over a parachute-based vehicle. This presentation will explore detailed design of a CSSR-capable Earth Entry Vehicle, including trajectories, aeroheating predictions and associated thermal protection system masses, and onboard instrumentation for entry science.
Trajectory Analysis↗
Rapid Spacecraft Payload Development: In-Orbit Demonstration of Flight Software Reuse, Scalability, and Dependability
As space mission design trends towards shared, multi-mission platforms and high-performance onboard computing architectures, the number of spacecraft launched into operation is also steadily rising. Through ridesharing, spacecraft miniaturization, and other cost-reduction measures, the barriers to space are lowering, resulting in compounded growth in the amount of flight software being deployed. To meet the needs of both the growing quantity and evolving nature of spacecraft, flight software design must accordingly adapt to support more efficient development, solutions to computational resource-sharing, and software reusability. This paper focuses on a software payload demonstrating several core technologies that improve the state-of-the-art in these identified areas. Launched into low-earth orbit in January 2022, our software payload was conceived, designed, and delivered in a span of merely two months. It was developed on top of the NASA core Flight System (cFS) framework and the Distributed Spacecraft Autonomy (DSA) Comm cFS application, which translates cFS software bus messages across a Data Distribution Service (DDS) network. The flight software, packaged in Linux container images, was deployed as one of 18 flight applications managed through the Unibap SpaceCloud Framework. The applications were run on a Unibap iX5-102 radiation-tolerant payload computer, hosted on the D-Orbit SCV-004 spacecraft as part of an ESA-sponsored in-orbit technology test. Our payload, referred to as the DSA D-Orbit software, demonstrates the reusability of the DSA Comm app in a substantially different context and purpose as its original mission. Comm’s original design goal was to reliably distribute messages between spacecraft swarms of arbitrary size and dynamic network topology. However, we leverage this same functionality to introduce redundancy and opportunistic parallel data processing in the context of a representative onboard image processing workload. This adaptive mission architecture was enabled in part by the SpaceCloud Framework’s use of container virtualization as the payload integration interface. By using a base container image with common high-level language runtimes and libraries, we were able to rapidly design, develop, and validate our image processing application without many of the technological barriers common to flight software development. We present details the goals, approach, results, and lessons learned through this technology demonstration experiment and contextualize those observations against present and future challenges in spacecraft software development.
computer programming↗
Moving Toward Space Internetworking via DTN: Its Operational Challenges, Benefits, and Management
The international space community has begun to recognize that the established model for management of communications with spacecraft - commanded data transmission over individual pair-wise contacts - is operationally unwieldy and will not scale in support of increasingly complex and sophisticated missions such as NASA's Constellation project. Accordingly, the international Inter-Agency Operations Advisory Group (IOAG) ichartered a Space Internetworking Strategy Group (SISG), which released its initial recommendations in a November 2008 report. The report includes a recommendation that the space flight community adopt Delay-Tolerant Networking (DTN) to address the problem of interoperability and communication scaling, especially in mission environments where there are multiple spacecraft operating in concert. This paper explores some of the issues that must be addressed in implementing, deploying, and operating DTN as part of a multi-mission, multi-agency space internetwork as well as benefits and future operational scenarios afforded by DTN-based space internetworking.
Delay Tolerant Networking↗
Mission Design & Operations Approach for the HelioSwarm Mission
HelioSwarm: The Nature of Turbulence in Space Plasmas is a transformational mission to explore the dynamic three-dimensional mechanisms controlling the physics of plasma turbulence, a ubiquitous process occurring in the heliosphere and plasmas throughout the universe. Turbulence is the process by which energy contained in fluctuating magnetic fields and plasma motion cascades from large to smaller spatial scales. HelioSwarm achieves its science goals by making simultaneous measurements across a wide range of measurement baselines, spanning magnetohydrodynamic scales (1000’s of km) to sub-ion heating scales (10’s of km), using a novel nine-spacecraft swarm. The swarm operates in a high-altitude lunar resonant Earth orbit (two-week period, ~63 RE apogee, ~13 RE perigee), giving it access to both the pristine solar wind and regions of strongly driven turbulence (specifically the magnetosphere and foreshock), and utilizes customized relative orbital motion of the swarm members to produce the range of measurement baselines and configurations. The swarm comprises eight “node” spacecraft, manufactured by Blue Canyon Technologies, and a “hub” spacecraft produced by Northrop Grumman Corp. The hub serves as a communications relay, with all communications between the ground and the nodes flowing through it. Mission operations are conducted within the Multi-Mission Operations Center at the NASA Ames Research Center and science operations at the University of New Hampshire, Durham. HelioSwarm was selected in 2022 as one of NASA’s newest Heliophysics Explorer missions to proceed from mission concept into mission implementation, with a target launch in 2029. This paper provides an overview of the mission’s science goals and objectives, the mission design, and the concept of operations, with an emphasis on how the swarm aspects of the mission both enable the science measurements and present unique operational challenges. The paper then describes the proposed development approach for the mission operations system and ground data system which relies on a selective combination of scaling strategies to meet the challenges.
HelioSwarm↗
Adaptive Independent Verification and Validation (IV&V) Reduces Risk of Software Impacting Safety in Artemis Missions
The National Aeronautics and Space Administration (NASA) is asking more of its human spaceflight programs than ever before through the collective Artemis Missions. The NASA Independent Verification and Validation (IV&V) Program contributes to NASA’s human spaceflight goals by providing IV&V services for NASA’s critical spacecraft and ground software. The IV&V Program is tasked with providing assurance from both individual and integrated mission software perspectives. The Artemis IV&V organization is actively supporting six distinct development efforts: Orion, the Space Launch System (SLS), Exploration Ground Systems (EGS), Mission Control Center (MCC), the Lunar Gateway, and the Human Landing System (HLS), representing a wide diversity of developer organizations, management structures, and development approaches. With much of this extremely complex flight and ground software being essential to human safety both on the ground and in space, Artemis IV&V is likewise challenged to provide more value-added assurance to future Artemis missions within a constrained budget. To meet this challenge, Artemis IV&V employs a variety of novel and evolving “Adaptive IV&V” approaches for planning and executing IV&V analysis to increase both the efficiency and effectiveness of the IV&V Program’s assurance activities, and to address the difficulties imposed by assuring software for a large, highly integrated, multi-mission enterprise managed and executed by physically and organizationally distinct programs. Instilling agile principles like iterative planning cycles, self-organizing teams, and regular retrospectives, into IV&V planning and execution has led to a more rapid turnaround of a minimum viable assurance product and allowed for increased alignment of assurance activities with development progress. Adopting an assurance case methodology has led to greater consistency and clearer communication of assurance design and provided a foundation for long-term maintenance of assurance plans, products, and results across missions. The IV&V-developed Assurance / Safety Case Analytical Network (A-SCAN) framework and tool has enabled the quantification and tracking of system/software risk and confidence. These confidence measures provide a means to repeatedly express the impact of planned and completed assurance work and the remaining residual risk. Applied as part of a “Follow-the-Risk” organizational ethos, this allows consistent rightsizing of analysis rigor and intensity commensurate with the perceived risk of defects, as well as appropriate targeting of the highest risk areas of the software to find safety issues before they can manifest. Finally, the development of the IV&V Advanced Risk Reduction Integrated Software Test and Operations Tri-program Lightweight Environment (ARRISTOTLE), an integrated software-only simulation of Orion, SLS, and EGS systems, has made it possible to independently test integrated pad and flight scenarios and inject faults to observe how the Artemis multi-program, mission software behaves in degraded modes and in response to hazards. These adaptive IV&V investments have enabled Artemis IV&V to become more efficient and effective in IV&V planning and execution and respond more readily to changes in the risk landscape, increasing the breadth and depth of risk reduction possible within the available resources. Residual risk tracking allows IV&V to communicate more effectively with stakeholders, both internal and external at all levels, and inform key decision-making personnel. This evolving assurance design approach provides IV&V surety that work is performed in the highest risk, most value-added areas of the software, to keep our astronauts and ground crews safe and ensure mission success.
Gerek A Whitman↗
Adaptive Independent Verification and Validation (IV&V) Reduces Risk of Software Impacting Safety in Artemis Missions
The National Aeronautics and Space Administration (NASA) is asking more of its human spaceflight programs than ever before through the collective Artemis Missions. The NASA Independent Verification and Validation (IV&V) Program contributes to NASA’s human spaceflight goals by providing IV&V services for NASA’s critical spacecraft and ground software. The IV&V Program is tasked with providing assurance from both individual and integrated mission software perspectives. The Artemis IV&V organization is actively supporting six distinct development efforts: Orion, the Space Launch System (SLS), Exploration Ground Systems (EGS), Mission Control Center (MCC), the Lunar Gateway, and the Human Landing System (HLS), representing a wide diversity of developer organizations, management structures, and development approaches. With much of this extremely complex flight and ground software being essential to human safety both on the ground and in space, Artemis IV&V is likewise challenged to provide more value-added assurance to future Artemis missions within a constrained budget. To meet this challenge, Artemis IV&V employs a variety of novel and evolving “Adaptive IV&V” approaches for planning and executing IV&V analysis to increase both the efficiency and effectiveness of the IV&V Program’s assurance activities, and to address the difficulties imposed by assuring software for a large, highly integrated, multi-mission enterprise managed and executed by physically and organizationally distinct programs. Instilling agile principles like iterative planning cycles, self-organizing teams, and regular retrospectives, into IV&V planning and execution has led to a more rapid turnaround of a minimum viable assurance product and allowed for increased alignment of assurance activities with development progress. Adopting an assurance case methodology has led to greater consistency and clearer communication of assurance design and provided a foundation for long-term maintenance of assurance plans, products, and results across missions. The IV&V-developed Assurance / Safety Case Analytical Network (A-SCAN) framework and tool has enabled the quantification and tracking of system/software risk and confidence. These confidence measures provide a means to repeatedly express the impact of planned and completed assurance work and the remaining residual risk. Applied as part of a “Follow-the-Risk” organizational ethos, this allows consistent rightsizing of analysis rigor and intensity commensurate with the perceived risk of defects, as well as appropriate targeting of the highest risk areas of the software to find safety issues before they can manifest. Finally, the development of the IV&V Advanced Risk Reduction Integrated Software Test and Operations Tri-program Lightweight Environment (ARRISTOTLE), an integrated software-only simulation of Orion, SLS, and EGS systems, has made it possible to independently test integrated pad and flight scenarios and inject faults to observe how the Artemis multi-program, mission software behaves in degraded modes and in response to hazards. These adaptive IV&V investments have enabled Artemis IV&V to become more efficient and effective in IV&V planning and execution and respond more readily to changes in the risk landscape, increasing the breadth and depth of risk reduction possible within the available resources. Residual risk tracking allows IV&V to communicate more effectively with stakeholders, both internal and external at all levels, and inform key decision-making personnel. This evolving assurance design approach provides IV&V surety that work is performed in the highest risk, most value-added areas of the software, to keep our astronauts and ground crews safe and ensure mission success.
Gerek Whitman↗
Artificial intelligence techniques for scheduling Space Shuttle missions
Planning and scheduling of NASA Space Shuttle missions is a complex, labor-intensive process requiring the expertise of experienced mission planners. We have developed a planning and scheduling system using combinations of artificial intelligence knowledge representations and planning techniques to capture mission planning knowledge and automate the multi-mission planning process. Our integrated object oriented and rule-based approach reduces planning time by orders of magnitude and provides planners with the flexibility to easily modify planning knowledge and constraints without requiring programming expertise.
Henke, Andrea L.↗
Enabling Space Science and Exploration
This viewgraph presentation on enabling space science and exploration covers the following topics: 1) Today s Deep Space Network; 2) Next Generation Deep Space Network; 3) Needed technologies; 4) Mission IT and networking; and 5) Multi-mission operations.
industry day↗
Sequencing System Building Blocks: Using a Component Architecture for Sequencing Software
Over the last few years software engineering has made significant strides in making more flexible architectures and designs possible. However, at the same time, spacecraft have become more complex and flight software has become more sophisticated. Typically spacecraft are often one-of-a-kind entities that have different hardware designs, different capabilities, different instruments, etc. Ground software has become more complex and operations teams have had to learn a myriad of tools that all have different user interfaces and represent data in different ways. At Jet Propulsion Laboratory (JPL) these themes have collided to require a new approach to producing ground system software. Two different groups have been looking at tackling this particular problem. One group is working for the JPL Mars Technology Program in the Mars Science Laboratory (MSL) Focused Technology area. The other group is the JPL Multi-Mission Planning and Sequencing Group. The major concept driving these two approaches on a similar path is to provide software that can be a more cohesive flexible system that provides a set of planning and sequencing system of services. This paper describes the efforts that have been made to date to create a unified approach from these disparate groups.
multi mission planning↗
Mars Science Laboratory Launch Pad Thermal Control
This paper will describe the challenges faced in accommodating the warm Multi Mission Radioisotope Thermoelectric Generator (MMRTG) during the pre-launch phases of integration, launch pad operations as well as during launch. Predictions of temperatures during these phases will be presented when all the cooling systems (HRS and A/C) are operational. In-air tests conducted on the spacecraft in December 2008 to simulate the launch conditions were very successful and showed that all components would be within their allowable limits during these phases. Results of these tests will be shared in this paper.
Radioisotope Thermoelectric Generator (RTG)↗
Towards a Cradle-to-Grave, Mission-Wide Simulation System
We articulate a vision for a multi-mission simulation framework capable of servicing a Space Mission over its entire lifetime, from early formulation to end-of-mission phases. Our vision adopts and extends the APGen-based simulation methodology used by NASA’s planned Europa Clipper mission to examine key spacecraft trades, assess impacts to operability, and quantify how well the scientific objectives of the mission can be achieved. The simulation framework we propose will provide Europa Clipper and future missions with unprecedented high-fidelity, integrated, system-level capabilities with the potential to dramatically improve design, performance, science return and operability.
Wissler, S.S.↗