Solar System Exploration Architecture for Revolutionary Science (SSEARS)
No abstract available
heliopause↗
SEARCH · Search NASA
Results for “spacecraft architecture”
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.
An advanced environment for spacecraft engineering subsystem mission operations
The Engineering Analysis Subsystem Environment (EASE) is under development at the JPL with a view to prospective small and large space missions. EASE is a modular multimission/multisystem architecture for spacecraft analysis that encompases monitoring and sequence support; its collection of software analysis modules is specific to a given mission, thereby easily accommodating mission scale. An EASE subsystem analysis module can be developed in modular program sets or packages, and a level of automation can then be introduced within such sets to achieve intramodule automation.
Bahrami, K. A.↗
Software Architecture for a Highly Autonomous Spacecraft Control System
Future space missions will continue to be scientifically and technically more ambitious, and will demand more autonomy to accomplish complex tasks in uncertain environments and in close proximity to extraterrestrial bodies.
software architecture smaller missions science obj↗
Creating an Interface to view Multi-Spacecraft Swarm Telemetry
Distributed Spacecraft Systems are a type of multi-spacecraft mission architecture that can not only provide improved resolution, coverage, and availability of existing missions, but also enable missions that would be previously infeasible using traditional approaches. Distributed Spacecraft Autonomy (DSA) is a project developed by the National Aeronautics and Space Administration that enables distributed spacecraft systems. In previous science swarm missions, the spacecraft involved have not been able to communicate with each other without utilizing a ground station. Now that the spacecraft can perform inter-satellite communication, the spacecraft can be treated as a collective. Swarm autonomy is critical for a growing number of satellites which means novel ways of displaying swarm data needs to be implemented. Such systems introduce unique challenges to traditional approaches for command and control of these spacecraft, due to the large number of spacecraft and the complexity of the interactions between them. The ground data system for DSA addresses these challenges through the creation of a custom user interface that allows a single operator to orchestrate a multi-spacecraft swarm in a scalable way. This plenary describes the details of the autonomy demonstration being performed, the requirements of those using the interface to analyze the spacecraft telemetry to assess demonstration success, and the approach taken by the ground systems team to create an interface that satisfies these requirements. This approach involves the creation of several distinct components that correspond to the level of detail presented to the user. These components are based on conventional user roles in human-robot interaction, including supervisor, operator, and mechanic, extended to accommodate the additional overhead of coordinating actions between agents. One main feature of the interface is the listenability matrix component which will represent inter-satellite communications in a heat mapped matrix. The above work described will enable users to command and interact with the spacecraft as a collective.
human-swarm interaction↗
Considerations and Architectures for Inter-Satellite Communications in Distributed Spacecraft Systems
This paper will identify the important characteristics and requirements necessary for inter-satellite communications in distributed spacecraft systems and present analysis results focusing on architectural and protocol comparisons. Emerging spacecraft systems plan to deploy multiple satellites in various "distributed" configurations ranging from close proximity formation flying to widely separated constellations. Distributed spacecraft configurations provide advantages for science exploration and operations since many activities useful for missions may be better served by distributing them between spacecraft. For example, many scientific observations can be enhanced through spatially separated platforms, such as for deep space interferometry. operating multiple distributed spacecraft as a mission requires coordination that may be best provided through inter-satellite communications. For example, several future distributed spacecraft systems envision autonomous operations requiring relative navigational calculations and coordinated attitude and position corrections. To conduct these operations, data must be exchanged between spacecraft. Direct cross-links between satellites provides an efficient and practical method for transferring data and commands. Unlike existing "bent-pipe" relay networks supporting space missions, no standard or widely-used method exists for cross-link communications. Consequently, to support these future missions, the characteristics necessary for inter-satellite communications need to be examined. At first glance, all of the missions look extremely different. Some missions call for tens to hundreds of nano-satellites in constant communications in close proximity to each other. Other missions call for a handful of satellites communicating very slowly over thousands to hundreds of thousands of kilometers. The paper will first classify distributed spacecraft missions to help guide the evaluation and definition of cross-link architectures and approaches. Based on this general classification, the paper will examine general physical layer parameters, such as frequency bands and data rates, necessary to support the missions. The paper will also identify classes of communication architectures that may be employed, ranging from fully distributed to centralized topologies. Numerous factors, such as number of spacecraft, must be evaluated when attempting to pick a communications architecture. Also important is the stability of the formation from a communications standpoint. For example, do all of the spacecraft require equal bandwidth and are spacecraft allowed to enter and leave a formation? The type of science mission being attempted may also heavily influence the communications architecture. In addition, the paper will assess various parameters and characteristics typically associated with the data link layer. The paper will analyze the performance of various multiple access techniques given the operational scenario, requirements, and communication topologies envisioned for missions. This assessment will also include a survey of existing standards and their applicability for distributed spacecraft systems. An important consideration includes the interoperability of the lower layers (physical and data link) examined in this paper with the higher layer protocols(network) envisioned for future space internetworking. Finally, the paper will define a suggested path, including preliminary recommendations, for defining and developing a standard for intersatellite communications based on the classes of distributed spacecraft missions and analysis results.
Edwards, Bernard↗
Integrated Vehicle and Trajectory Design of Small Spacecraft with Electric Propulsion for Earth and Interplanetary Missions
This paper investigates the feasibility of Earth-transfer and interplanetary mission architectures for miniaturized spacecraft using emerging small solar electric propulsion technologies. Emerging small SEP thrusters offer significant advantages relative to existing technologies and will enable U-class systems to perform trajectory maneuvers with significant Delta V requirements. The approach in this paper is unique because it integrates trajectory design with vehicle sizing and accounts for the system and operational constraints of small U-class missions. The modeling framework includes integrated propulsion, orbit, energy, and external environment dynamics and systems-level power, energy, mass, and volume constraints. The trajectory simulation environment models orbit boosts in Earth orbit and flyby and capture trajectories to interplanetary destinations. A family of small spacecraft mission architectures are studied, including altitude and inclination transfers in Earth orbit and trajectories that escape Earth orbit and travel to interplanetary destinations such as Mercury, Venus, and Mars. Results are presented visually to show the trade-offs between competing performance objectives such as maximizing available mass and volume for payloads and minimizing transfer time. The results demonstrate the feasibility of using small spacecraft to perform significant Earth and interplanetary orbit transfers in less than one year with reasonable U-class mass, power, volume, and mission durations.
Spangelo, Sara↗
X2000 Advanced Avionics Project development of a new generation of avionics for space applications
This paper will describe the system architecture, the avionics components, the key performance and reliability requirements, and the current development status of the X2000 Avionics.
avionics spacecraft architecture↗
SCARES: A Spacecraft Control Anomaly Resolution Expert System
The current pace of technological development is reflected in the increased mission lifetime of each new generation of satellite. Coupled with this has come a reduced availability of experts to provide technical assistance in satellite operation on a day to day basis. Given such an environment, an expert system is discussed based on architecture for spacecraft anomaly resolution. By capturing deep knowledge about a spacecraft, the system is able to detect and diagnose fault better than previous conventional approaches. A prototype expert system named SCARES (applied only to spacecraft attitude control system) is discussed. Extension of the prototype to handle anomalies in other systems of the satellite is also discussed.
Hamilton, Marc↗
Swarm Mentality: Toward Automatic Swarm State Awareness with Runtime Verification
Cyber-Physical Systems (CPSs) already exhibit impressive performance in all areas of human life, and swarms of CPSs promise to increase their capabilities even further. However, to effectively utilize CPS swarms their complexity of operation has to scale sub-linearly with the number of swarm members. Presenting the swarm to an operator as a single entity almost eliminates the additional per-member overhead entirely. To operate a swarm as one entity, and/or to increase the swarm’s autonomy, the operator and the swarm members need to reason and communicate at the same level of abstraction, i.e. the swarm needs a sense of “self.” Therefore, we require the ability to specify whole swarm properties yet monitor them at the member level. We examine one architecture for achieving this awareness by: 1) Defining a taxonomy for comparing techniques that synthesize this belief-state 2) Propose use of the Runtime Verification formal method to fill this role 3) Present preliminary designs for extending and embedding such a system in the Distributed Spacecraft Autonomy architecture to generate per-member monitors from swarm level specification.
Runtime Verification↗
An Autonomous Spacecraft Agent Prototype
This paper describes the New Millennium Remote Agent (NMRA) architecture for autonomous spacecraft control systems. This architecture integrates traditional real-time monitoring and control with constraint-based planning and scheduling, robust multi-threaded execution, and model-based diagnosis and reconfiguration.
New Millennium Remote Agent↗
Thermal design trades for SAFIR architecture concepts
SAFIR is a IO-meter, 4 K space telescope optimized for wavelengths between 20 microns and 1 mm. The combination of aperture diameter and telescope temperature will provide a raw sensitivity improvement of more than a factor of 1000 over presently-planned missions. The sensitivity will be comparable to that of the JWST and ALMA, but at the critical far-IR wavelengths where much of the universe's radiative energy has emerged since the origin of stars and galaxies. We examine several of the critical technologies for SAFIR which enable the large cold aperture, and present results of studies examining the telescope optics and the spacecraft thermal architecture. Both the method by which the aperture is filled, and the overall optical design for the telescope can impact the potential scientific return of SAFIR. Thermal architecture that goes far beyond the sunshades developed for the James Webb Space Telescope will be necessary to achieve the desired sensitivity of SAFIR. By combining active and passive cooling at critical points within the observatory, a significant reduction of the required level of active cooling can be obtained.
infrared telescopes↗
Feasibility Study of Two Candidate Reaction Wheel/thruster Hybrid Control Architecture Designs for the Cassini Spacecraft
As the first spacecraft to achieve orbit at Saturn in 2004, Cassini has collected science data throughout its four-year prime mission (2004-08), and has since been approved for a first and second extended mission through 2017. Cassini carries a set of three "fixed" reaction wheels and a backup reaction wheel (reaction wheel #4) is mounted on top of an articulable platform. If necessary, this platform could be articulated to orient the backup reaction wheel with the degraded wheel. The reaction wheels are used primarily for attitude control when precise and stable pointing of a science instrument such as the narrow angle camera is required. In 2001-02, reaction wheel #3 exhibited signs of bearing cage instability. As a result, reaction wheel #4 was articulated to align with reaction wheel #3. Beginning in July 2003, Cassini was controlled using wheel #1, #2, and #4. From their first use in the spring of 2000 until today, reaction wheels #1 and #2 have accumulated more than3.5 billions revolutions each. As such, in spite of very carefully management of the wheel spin rates by the mission operation team, there are some observed increases in the drag torque of the wheels' bearings. Hence, the mission operations team must prepare for the contingency scenario in which the reaction wheel #1 (in addition to wheel #3) had degraded. In this hypothetical fault scenario, the two remaining reaction wheels (#2 and #4) will not be able to provide precise and stable three-axis control of the spacecraft. In this study, we evaluate the feasibility of controlling Cassini using the two remaining reaction wheels and four thrusters to meet the science pointing requirements for two key science operational modes: the Optical Remote Sensing and Downlink, Fields, Particles, & Waves operation modes. The performance (e.g., pointing control error, pointing stability, hydrazine consumption rate, etc.) of the hybrid controllers in both operations scenarios will be compared with those achieved using an all-thruster controller design. Strength and weaknesses of the hybrid control architecture are assessed quantitatively.
Cassini↗
An Architecture to Enable Autonomous Control of Spacecraft
Autonomy is required for manned spacecraft missions distant enough that light-time communication delays make ground-based mission control infeasible. Presently, ground controllers develop a complete schedule of power modes for all spacecraft components based on a large number of factors. The proposed architecture is an early attempt to formalize and automate this process using on-vehicle computation resources. In order to demonstrate this architecture, an autonomous electrical power system controller and vehicle Mission Manager are constructed. These two components are designed to work together in order to plan upcoming load use as well as respond to unanticipated deviations from the plan. The communication protocol was developed using "paper" simulations prior to formally encoding the messages and developing software to implement the required functionality. These software routines exchange data via TCP/IP sockets with the Mission Manager operating at NASA Ames Research Center and the autonomous power controller running at NASA Glenn Research Center. The interconnected systems are tested and shown to be effective at planning the operation of a simulated quasi-steady state spacecraft power system and responding to unexpected disturbances.
space power systems↗
Space Assembly of Large Structural System Architectures (SALSSA)
Developing a robust capability for Space Assembly of Large Spacecraft Structural System Architectures (SALSSA) has the potential to drastically increase the capabilities and performance of future space missions and spacecraft while significantly reducing their cost. Currently, NASA architecture studies and space science decadal surveys identify new missions that would benefit from SALSSA capabilities, and the technologies that support SALSSA are interspersed throughout the fourteen NASA Technology Roadmaps. However, a major impediment to the strategic development of cross-cutting SALSSA technologies is the lack of an integrated and comprehensive compilation of the necessary information. This paper summarizes the results of a small study that used an integrated approach to formulate a SALSSA roadmap and associated plan for developing key SALSSA technologies.
Dorsey, John T.↗
Development and Testing of a Vehicle Management System for Autonomous Spacecraft Habitat Operations
As the increased distance between Earth-based mission control and the spacecraft results in increasing communication delays, small crews cannot take on all functions performed by ground today, and so vehicles must be more automated to reduce the crew workload for such missions. In addition, both near-term and future missions will feature significant periods when crew is not present, meaning the vehicles will need to operate themselves autonomously. NASA's Advanced Exploration Systems Program pioneers new approaches for rapidly developing prototype systems, demonstrating key capabilities, and validating operational concepts for future human missions beyond low-Earth orbit. Under this program, NASA has developed and demonstrated multiple technologies to enable the autonomous operation of a dormant space habitat. These technologies included a fault-tolerant avionics architecture, novel spacecraft power system and power system controller, and autonomy software to control the habitat. The demonstration involved simulation of the habitat and multiple spacecraft sub-systems (power storage and distribution, avionics, and air-side life-support) during a multi-day test at NASA's Johnson Space Center. The foundation of the demonstration was ‘quiescent operations' of a habitat during a 55 minute eclipse period. For this demonstration, the spacecraft power distribution system and air-side life support system were simulated at a high level of fidelity; additional systems were managed, but with lower fidelity operational constraints and system behavior. Operational constraints for real and simulated loads were developed by analyzing on-orbit hardware and evaluating future Exploration capable technology. A total of 13 real and simulated loads were used during the test. Eight scenarios including both nominal and off-nominal conditions were performed. Over the course of the test, every application performed its desired functions successfully during the simulated tests. The results will inform both future tests, as well as provide insight to NASA's domestic and international partners, as they construct the next generation of space habitats to be used on beyond-Earth missions.
Autonomous Systems and Operations↗
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↗
Gateway Autonomy for Enabling Deep Space Exploration
The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.
Molly Anderson↗
Gateway Autonomy for Enabling Deep Space Exploration
The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.
Molly Anderson↗