Search NASA⌕ Search

SEARCH · Search NASA

Results for “Distributed Spacecraft Missions”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2003

An Internet Protocol-Based Software System for Real-Time, Closed-Loop, Multi-Spacecraft Mission Simulation Applications

The paper will provide an overview of the web-based distributed simulation software system developed for end-to-end, multi-spacecraft mission design, analysis, and test at the NASA Goddard Space Flight Center (GSFC). This software system was developed for an internal research and development (IR&D) activity at GSFC called the Distributed Space Systems (DSS) Distributed Synthesis Environment (DSE). The long-term goal of the DSS-DSE is to integrate existing GSFC stand-alone test beds, models, and simulation systems to create a "hands on", end-to-end simulation environment for mission design, trade studies and simulations. The short-term goal of the DSE was therefore to develop the system architecture, and then to prototype the core software simulation capability based on a distributed computing approach, with demonstrations of some key capabilities by the end of Fiscal Year 2002 (FY02). To achieve the DSS-DSE IR&D objective, the team adopted a reference model and mission upon which FY02 capabilities were developed. The software was prototyped according to the reference model, and demonstrations were conducted for the reference mission to validate interfaces, concepts, etc. The reference model, illustrated in Fig. 1, included both space and ground elements, with functional capabilities such as spacecraft dynamics and control, science data collection, space-to-space and space-to-ground communications, mission operations, science operations, and data processing, archival and distribution addressed.

Davis, George↗
NASA NTRS2001

A Hardware-in-the-Loop Testbed for Spacecraft Formation Flying Applications

The Formation Flying Test Bed (FFTB) at NASA Goddard Space Flight Center (GSFC) is being developed as a modular, hybrid dynamic simulation facility employed for end-to-end guidance, navigation, and control (GN&C) analysis and design for formation flying clusters and constellations of satellites. The FFTB will support critical hardware and software technology development to enable current and future missions for NASA, other government agencies, and external customers for a wide range of missions, particularly those involving distributed spacecraft operations. The initial capabilities of the FFTB are based upon an integration of high fidelity hardware and software simulation, emulation, and test platforms developed at GSFC in recent years; including a high-fidelity GPS simulator which has been a fundamental component of the Guidance, Navigation, and Control Center's GPS Test Facility. The FFTB will be continuously evolving over the next several years from a too[ with initial capabilities in GPS navigation hardware/software- in-the- loop analysis and closed loop GPS-based orbit control algorithm assessment to one with cross-link communications and relative navigation analysis and simulation capability. Eventually the FFT13 will provide full capability to support all aspects of multi-sensor, absolute and relative position determination and control, in all (attitude and orbit) degrees of freedom, as well as information management for satellite clusters and constellations. In this paper we focus on the architecture for the FFT13 as a general GN&C analysis environment for the spacecraft formation flying community inside and outside of NASA GSFC and we briefly reference some current and future activities which will drive the requirements and development.

Leitner, Jesse↗
NASA NTRS1984

Coronal mass ejections observed during the solar maximum mission - Latitude distribution and rate of occurrence

Sixty-five coronal mass ejections have been identified in a systematic examination of white-light coronal images obtained between March and September 1980 by the coronagraph/polarimeter flown on the solar maximum mission spacecraft. These ejections were more uniformly distributed in position angle (or 'projected' solar latitude) than the similar events observed during the Skylab mission in 1973-1974; 27 percent of the solar maximum mission mass ejections were centered at positions more than 45 deg from the solar equator. The average rate of occurrence of the observed mass ejections for the entire solar maximum mission epoch, based on the assumption that one coronagraph image per spacecraft orbit is sufficient for detection, was 0.9 + or 0.15 per 24-hour day. Application of the same sampling assumption to the Skylab data set leads to a rate of 0.75 per 24-hour day and thus a change in this rate from the Skylab era (on the declining phase of sunspot cycle 20) to solar maximum mission (near the maximum of sunspot cycle 21) of only approximately 20 percent.

Hundhausen, A. J.↗
NASA NTRS1996

Distribution of a Generic Mission Planning and Scheduling Toolkit for Astronomical Spacecraft

Work is progressing as outlined in the proposal for this contract. A working planning and scheduling system has been documented and packaged and made available to the WIRE Small Explorer group at JPL, the FUSE group at JHU, the NASA/GSFC Laboratory for Astronomy and Solar Physics and the Advanced Planning and Scheduling Branch at STScI. The package is running successfully on the WIRE computer system. It is expected that the WIRE will reuse significant portions of the SWAS code in its system. This scheduling system itself was tested successfully against the spacecraft hardware in December 1995. A fully automatic scheduling module has been developed and is being added to the toolkit. In order to maximize reuse, the code is being reorganized during the current build into object-oriented class libraries. A paper describing the toolkit has been written and is included in the software distribution. We have experienced interference between the export and production versions of the toolkit. We will be requesting permission to reprogram funds in order to purchase a standalone PC onto which to offload the export version.

Kleiner, Steven C.↗
NASA NTRS2002

Guidance, Navigation and Control Innovations at the NASA Goddard Space Flight Center

This presentation discusses NASA's role in sponsoring on-going research projects involving innovations in spacecraft guidance, navigation and control systems. Topics covered include: partnerships, ESE Spaceborne Missions, spacecraft systems supported and designed by NASA Goddard Flight Center, NASA's changing mission, Large Aperture Sensing Spectrum, Distributed Spacecraft Systems, Landsat-7/ Earth Observer-1 Co-observing Program, and Laser Interferometer Space Antenna program.

Ericsson, Aprille Joy↗
NASA NTRS2023

An Overview of Distributed Spacecraft Autonomy at NASA Ames

Autonomous decision-making significantly increases mission effectiveness by mitigating the effects of communication constraints, like latency and bandwidth, and mission complexity on multi-spacecraft operations. To advance the state of the art in autonomous Distributed Space Systems (DSS), the Distributed Spacecraft Autonomy (DSA) team at NASA's Ames Research Center is developing within five relevant technical areas: distributed resource and task management, reactive operations, system modeling and simulation, human-swarm interaction, and ad hoc network communications. DSA is maturing these technologies - critical for future large autonomous DSS - from concept to launch via simulation studies and orbital deployments. A 100-node heterogenous Processor-in-the-Loop (PiL) testbed aids distributed autonomy capability development and verification of multi-spacecraft missions. The DSA software payload deployed to the D-Orbit SCV-004 spacecraft demonstrates multi-agent reconfigurability and reliability as part of an ESA-sponsored in-orbit technology demonstration. Finally, DSA's primary flight mission showcases collaborative resource allocation for multipoint science data collection with four small spacecraft as a payload on NASA's Starling 1.0 satellites.

Caleb Ashmore Adams↗
NASA NTRS2005

Mars Aeronomy Explorer (MAX): Study Employing Distributed Micro-Spacecraft

An overview of a Mars Aeronomy Explorer (MAX) mission design study performed at NASA's Jet Propulsion Laboratory is presented herein. The mission design consists of ten micro-spacecraft orbiters launched on a Delta IV to Mars polar orbit to determine the spatial, diurnal and seasonal variation of the constituents of the Martian upper atmosphere and ionosphere over the course of one Martian year. The spacecraft are designed to allow penetration of the upper atmosphere to at least 90 km. This property coupled with orbit precession will yield knowledge of the nature of the solar wind interaction with Mars, the influence of the Mars crustal magnetic field on ionospheric processes, and the measurement of present thermal and nonthermal escape rates of atmospheric constituents. The mission design incorporates alternative design paradigms that are more appropriate for-and in some cases motivate-distributed micro-spacecraft. These design paradigms are not defined by a simple set of rules, but rather a way of thinking about the function of instruments, mission reliability/risk, and cost in a systemic framework.

Mars↗
NASA NTRSDate not supplied

Using Coordinated, Multi-Agent Platforms for Dynamic Ocean Worlds Science

Planetary science missions have the opportunity to enhance science return through deployment of autonomous capabilities designed to dynamically respond to new information. Future outer solar system missions to ocean worlds in particular would benefit from this technology - intelligent science payloads (ISP) - because it would allow for a coordinated, near real-time response to ephemeral ‘events’ such as plumes, tectonism, surface implantation, volatile releases, thermal and magnetic anomalies, or radiation, as well as increasing the cadence and coverage of data collection. Prioritization and decision-making frameworks from ISP could be deployed at various scales - from analysis onboard a spacecraft with multiple instruments – to coordinated analyses among separate spacecraft in an e.g., distributed systems mission (DSM) composed of multiple SmallSats. Goddard’s Intelligent Science Payload team is developing an agile autonomous architecture for an icy ocean worlds DSM concept. Our goals are to coordinate data collection and onboard data analysis, and to make autonomous decisions for new data collection and analysis based on science priorities between multiple spacecraft with variable instrumentation and orbits. We use a range of data analysis tools to coordinate the DSM response, spanning from observations of data over a specified threshold to more computationally intensive machine learning algorithms (ML). ML algorithms here currently focus on determining the composition of an ocean world using mass spectrometry, and specifically methods for understanding ‘novelties’ and potential biosignatures. These algorithms could be used to quickly process and analyze onboard data that would be significantly delayed in downlink due to long communication delays for outer solar system missions in order to make dynamic science observations. Our ocean worlds case study ISP architecture is intended as an ‘agile’ and modular framework that could be used as a whole or as particular modules based on mission needs.

Distributed Systems↗
NASA NTRS1973

Planetary quarantine. Space research and technology

The impact of satisfying satellite quarantine constraints on outer planet missions and spacecraft design are studied by considering the effects of planetary radiation belts, solar wind radiation, and space vacuum on microorganism survival. Post launch recontamination studies evaluate the effects of mission environments on particle distributions on spacecraft surfaces and effective cleaning and decontamination techniques.

Source record↗
NASA NTRS2000

Autonomy Architectures for a Constellation of Spacecraft

Until the past few years, missions typically involved fairly large expensive spacecraft. Such missions have primarily favored using older proven technologies over more recently developed ones, and humans controlled spacecraft by manually generating detailed command sequences with low-level tools and then transmitting the sequences for subsequent execution on a spacecraft controller. This approach toward controlling a spacecraft has worked spectacularly on previous missions, but it has limitations deriving from communications restrictions - scheduling time to communicate with a particular spacecraft involves competing with other projects due to the limited number of deep space network antennae. This implies that a spacecraft can spend a long time just waiting whenever a command sequence fails. This is one reason why the New Millennium program has an objective to migrate parts of mission control tasks onboard a spacecraft to reduce wait time by making spacecraft more robust. The migrated software is called a "remote agent" and has 4 components: a mission manager to generate the high level goals, a planner/scheduler to turn goals into activities while reasoning about future expected situations, an executive/diagnostics engine to initiate and maintain activities while interpreting sensed events by reasoning about past and present situations, and a conventional real-time subsystem to interface with the spacecraft to implement an activity's primitive actions. In addition to needing remote planning and execution for isolated spacecraft, a trend toward multiple-spacecraft missions points to the need for remote distributed planning and execution. The past few years have seen missions with growing numbers of probes. Pathfinder has its rover (Sojourner), Cassini has its lander (Huygens), and the New Millenium Deep Space 3 (DS3) proposal involves a constellation of 3 spacecraft for interferometric mapping. This trend is expected to continue to progressively larger fleets. For example, one mission proposed to succeed DS3 would have 18 spacecraft flying in formation in order to detect earth-sized planets orbiting other stars. A proposed magnetospheric constellation would involve 5 to 500 spacecraft in Earth orbit to measure global phenomena within the magnetosphere. This work describes and compares three autonomy architectures for a system that continuously plans to control a fleet of spacecraft using collective mission goals instead of goals or command sequences for each spacecraft. A fleet of self-commanding spacecraft would autonomously coordinate itself to satisfy high level science and engineering goals in a changing partially-understood environment making feasible the operation of tens or even a hundred spacecraft (such as for interferometry or plasma physics missions). The easiest way to adapt autonomous spacecraft research to controlling constellations involves treating the constellation as a single spacecraft. Here one spacecraft directly controls the others as if they were connected. The controlling "master" spacecraft performs all autonomy reasoning, and the slaves only have real-time subsystems to execute the master's commands and transmit local telemetry/observations. The executive/diagnostics module starts actions and the master's real-time subsystem controls the action either locally or remotely through a slave. While the master/slave approach benefits from conceptual simplicity, it relies on an assumption that the master spacecraft's executive can continuously monitor the slaves' real-time subsystems, and this relies on high-bandwidth highly-reliable communications. Since unintended results occur fairly rarely, one way to relax the bandwidth requirements involves only monitoring unexpected events in spacecraft. Unfortunately, this disables the ability to monitor for unexpected events between spacecraft and leads to a host of coordination problems among the slaves. Also, failures in the communications system can result in losing slaves. The other two architectures improve robustness while reducing communications by progressively distributing more of the other three remote agent components across the constellation. In a teamwork architecture, all spacecraft have executives and real-time subsystems - only the leader has the planner/scheduler and mission manager. Finally, distributing all remote agent components leads to a peer-to-peer approach toward constellation control.

Barrett, Anthony↗
NASA NTRS1993

Distributed science operations for JPL planetary missions

Advances in spacecraft, flight instruments, and ground systems provide an impetus and an opportunity for scientific investigation teams to take direct control of their instruments' operations and data collection while at the same time, providing a cost effective and flexible approach in support of increasingly complex science missions. Operations of science instruments have generally been integrated into planetary flight and ground systems at a very detailed level. That approach has been successful, but the cost of incorporating instrument expertise into the central mission operations system has been high. This paper discusses an approach to simplify planetary science operations by distributing instrument computing and data management tasks from the central mission operations system to each investigator's home center of observational expertise. Some early results of this operations concept will be presented based on the Mars Observer (MO) Project experience and Cassini Project plans.

Benson, Richard D.↗
NASA NTRS2002

Searching for life with the Terrestrial Planet Finder: Lagrange point options for a formation flying interferometer

In this paper, we describe the mission design for TPF assuming a distributed spacecraft concept using formation flight around both a halo orbit around L2 as well as a heliocentric orbit. Although the mission architecture is still under study, the next two years will include study of four design cncepts and a downselect to two concepts around 2005.

TPF Terrestrial Planet Finder extrasolar system li↗
NASA NTRSDate not supplied

The Distributed Spacecraft Autonomy (DSA)

NASA’s Distributed Spacecraft Autonomy (DSA) Project developed and demonstrated software to enhance multi-spacecraft mission adaptability, efficiently allocate tasks between spacecraft using ad-hoc networking, and enable human-swarm commanding of Distributed Space Missions.

Autonomy Distributed Space Missions↗
NASA NTRS1982

High voltage distribution and grounding in high power spacecraft

Many space missions proposed for the time period from 1985 to 2000 will require large spacecraft to support the onboard loads. In some cases, large electrical power systems will be needed to supply the electrical/electronic equipment loads. These electronic systems will be used for communications, radar, and experimental equipment for aid to earth's overcrowded communication systems, exploration of new energy resources, space exploration, and eventually to supplement terrestrial electric power utilities. For the near term (1985-1990), some of these systems have power levels to 50 kW. The long-term programs, 1990 to post-2000, could possibly have demands in the order of multimegawatts. The problems which have to be solved to construct the required high-voltage power supply systems are considered. Data and conceptual designs generated are found to indicate that grounding and bonding for high power systems can be accomplished in spacecraft by using either manual or automatic joining of the structural members.

Dunbar, W. G.↗
NASA NTRS2006

Internet Distribution of Spacecraft Telemetry Data

Remote Access Multi-mission Processing and Analysis Ground Environment (RAMPAGE) is a Java-language server computer program that enables near-real-time display of spacecraft telemetry data on any authorized client computer that has access to the Internet and is equipped with Web-browser software. In addition to providing a variety of displays of the latest available telemetry data, RAMPAGE can deliver notification of an alarm by electronic mail. Subscribers can then use RAMPAGE displays to determine the state of the spacecraft and formulate a response to the alarm, if necessary. A user can query spacecraft mission data in either binary or comma-separated-value format by use of a Web form or a Practical Extraction and Reporting Language (PERL) script to automate the query process. RAMPAGE runs on Linux and Solaris server computers in the Ground Data System (GDS) of NASA's Jet Propulsion Laboratory and includes components designed specifically to make it compatible with legacy GDS software. The client/server architecture of RAMPAGE and the use of the Java programming language make it possible to utilize a variety of competitive server and client computers, thereby also helping to minimize costs.

Specht, Ted↗
NASA NTRS2003

An Internet Protocol-Based Software System for Real-Time, Closed-Loop, Multi-Spacecraft Mission Simulation Applications

A mission simulation prototype for Distributed Space Systems has been constructed using existing developmental hardware and software testbeds at NASA s Goddard Space Flight Center. A locally distributed ensemble of testbeds, connected through the local area network, operates in real time and demonstrates the potential to assess the impact of subsystem level modifications on system level performance and, ultimately, on the quality and quantity of the end product science data.

Burns, Richard D.↗
NASA NTRS1994

Operations automation

This is truly the era of 'faster-better-cheaper' at the National Aeronautics and Space Administration/Jet Propulsion Laboratory (NASA/JPL). To continue JPL's primary mission of building and operating interplanetary spacecraft, all possible avenues are being explored in the search for better value for each dollar spent. A significant cost factor in any mission is the amount of manpower required to receive, decode, decommutate, and distribute spacecraft engineering and experiment data. The replacement of the many mission-unique data systems with the single Advanced Multimission Operations System (AMMOS) has already allowed for some manpower reduction. Now, we find that further economies are made possible by drastically reducing the number of human interventions required to perform the setup, data saving, station handover, processed data loading, and tear down activities that are associated with each spacecraft tracking pass. We have recently adapted three public domain tools to the AMMOS system which allow common elements to be scheduled and initialized without the normal human intervention. This is accomplished with a stored weekly event schedule. The manual entries and specialized scripts which had to be provided just prior to and during a pass are now triggered by the schedule to perform the functions unique to the upcoming pass. This combination of public domain software and the AMMOS system has been run in parallel with the flight operation in an online testing phase for six months. With this methodology, a savings of 11 man-years per year is projected with no increase in data loss or project risk. There are even greater savings to be gained as we learn other uses for this configuration.

Boreham, Charles Thomas↗