Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Mars Relay Network”

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.

113 records · Page 7
All sourcesNASA NTRSDOE OSTI
DOE OSTI2021

Enabling Realistic Communications Evaluations for ADMS

Increasing penetration levels of inverter-based distributed energy resources (DERs) in distribution systems are creating challenges in system operation. Currently, wired or proprietary wireless communications are used by advanced distribution management systems (ADMS) to detect the state of the system and control the DERs for optimal operation. Wireless communications are an alternative solution that can enable connectivity between the dispersed assets used in distribution system applications. As demand for the seamless integration of distributed energy resources (DERs) continues to increase, proper networking and communications systems are becoming important to support the DER infrastructure. This report summarizes validation of a private wireless LTE network in a laboratory environment. The purpose of this work is to 1) demonstrate the effectiveness of private wireless LTE communication for grid applications and 2) provide a means of evaluating latency and overall performance of wireless communication in grid applications. First, private wireless LTE communication was validated in a direct transfer trip relaying scenario as an example of one-way communications using grid equipment. This study provided a baseline understanding of the variation in latency for seven different kinds of wireless scenarios shown in Figure A below. As expected, weak (attenuated) wireless signal-based communication yielded the widest ranges in latency. When higher priority was set for the trip signal communication, this resulted in lower latency in communication timing. In the final phase of this project, the private wireless LTE network was validated using two-way communications in an advanced distribution management system (ADMS) testbed which was developed in the ESIF at NREL. The purpose of this was to study the impact of wireless communication on grid performance.

24 POWER TRANSMISSION AND DISTRIBUTION↗
NASA NTRSDate not supplied

NASA’s Approach to Lunar Communication and Navigation: Artemis and Beyond

NASA’s Space Communications and Navigation (SCaN) program is developing a support structure of networks, partners, and technologies to provide communication, position, navigation, and timing services at the Moon. In this paper, we describe the progress and status of these diverse efforts and the ways in which they will be used during NASA’s crewed lunar exploration program, Artemis. We provide an update on developments at NASA which are targeted to cislunar space, including the Orion Artemis II Optical Communications System (O2O) demonstration mission, planned Lunar Exploration Ground Sites (LEGS) that will offer a dedicated Direct to Earth (DTE) capability servicing the cislunar region, and a recently released RFP for commercial Lunar Communications Relay and Navigation Services as well as Direct to Earth communications capabilities. We also describe the current status and key role of the LunaNet Interoperability Specification (LNIS), a collaborative standards framework developed by NASA, international partner agencies, and commercial stakeholders. A common thread, weaving these efforts together, is the support of commercial enterprises that can meet the Artemis challenge. Together, these projects and activities will enable safe, robust, and reliable communications and position, navigation, and timing (PNT) services for both crewed and uncrewed missions across cislunar space. SCaN and NASA, with our partners, are helping to build the foundation for a long term, sustainable human presence at the Moon –one that will set the stage for similar efforts at Mars.

LunaNet↗
NASA NTRS2018

Recommendations Emerging from an Analysis of NASA's Deep Space Communications Capacity

During 2016-2017, NASA’s Space Communications and Navigation (SCaN) Office chartered a study of Deep Space Network (DSN) communications capacity relative to projected future-mission demand over the next 30 years. In this paper, we briefly describe the methodology used to analyze capacity vs. demand over such a broad timeframe, summarize key findings emerging from the analysis, and discuss the associated recommendations. Performing the analysis entailed: identifying key factors shaping the anticipated future mission set, identifying several alternative future mission set scenarios consistent with these factors, and then analyzing each mission set scenario in terms of required antenna capacity, downlink and uplink capabilities, and spectrum as a function of time. On the basis of these aggregate requirements, DSN loading simulations were then conducted that examined how well each of the postulated mission sets could load up onto the the DSN’s “in-plan” architecture. To the extent that capacity shortfalls emerged during these baseline simulations, architectural solutions to the shortfalls were then postulated and tested via additional simulations. In general, the trend analyses and baseline loading simulations indicated a significant progression in challenges over the next three decades. In the current decade, the DSN appeared to be operating very close to capacity. The first human exploration mission and its secondary payload launch opportunities for cubesats traveling beyond GEO contributed to this loading. As a consequence, the main challenge appeared to be managing peak assetcontention periods. In the next decade, the DSN continued to operate close to capacity but also began transitioning to more frequent human mission support. Upgrading for, and operating, a human-rated system while continuing to meet robotic mission customer requirements emerged as the key challenge. In the 2030’s and beyond, simulations suggested a need for fundamentally new capability and capacity. The high data rates and long link distances characteristic of human Mars exploration drove requirements far beyond what is currently “in plan.” The key challenge then became determining the most cost-effective combination of RF and optical assets for communicating with the postulated human Mars assets while still providing for the needs of all the other missions across the solar system. Various link budget, visibility, and loading analyses ultimately suggested that the human Mars exploration demands of the 2030’s could best be addressed with two cross-linked RF-optical areostationary relays (or an areostationary relay and deep space habitat) providing a dual “trunk link” to an array of 2-to-3 additional 34m beam waveguide antennas and an ~8.5m optical antenna at each DSN Complex. The dual “trunk link” would enable the same amount of total data return to Earth as a single trunk link at twice the data rate, but with only half the required array size on the ground, assuming use of Multiple Spacecraft Per Antenna (MSPA) techniques. MSPA techniques, including a Multiple Uplink Per Antenna (MUPA) technique currently under investigation, also showed promise for reducing asset contention in the decades prior to human Mars exploration.

Lee, Carlyn-Ann↗
NASA NTRSDate not supplied

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↗
NASA NTRSDate not supplied

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↗