Search NASA⌕ Search

SEARCH · Search NASA

Results for “Communications and Navigation”

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 217 records · Page 12
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Ground Segment Operations Concept for the Orion Artemis-2 Optical Communications System

The ACCESS Project (formerly Space Network) will implement an optical communications ground segment to support the Orion Artemis II Optical Communications (O2O) demonstration as part of the next manned human spaceflight mission to the moon, Artemis II. O2O implements laser communication (lasercomm) technology for operational use on the Orion series of spacecraft, as a development test objective (DTO), in order to demonstrate the feasibility and operational utility of lasercomm for human spaceflight missions. O2O consists of three segments: Space Segment, Ground Segment, and Operations Segment. The Space Segment consists of the Space Terminal Element and the Orion spacecraft. The Space Terminal Element effort is managed by the GSFC Laser-Enhanced Mission Communications Navigation and Operational Services (LEMNOS) project in collaboration with MIT Lincoln Laboratory. The Ground Segment consists of an optical ground terminal (GT) at the White Sands Complex (WSC), which is being developed in collaboration with MIT Lincoln Laboratory, the Ground Segment Operations and Analysis (GSOA) element and Ground Data Element (GDE), and a second optical GT in the Optical Communications Telescope Laboratory (OCTL) at the JPL Table Mountain Facility. The Operations Segment consists of the Artemis II Mission Control Center (MCC), the Lasercomm Space Terminal Console (LSTC), and the Lasercomm Link Planning & Analysis Center (LPAC), all located at the Johnson Space Center (JSC). O2O utilizes pulse-position modulation (PPM) direct-to-earth services resulting in an 80 Mbps downlink data rate from lunar orbit. The O2O concept of operations is to provide optical services for a minimum of 1 hour per day for each day of the Artemis II mission. O2O will utilize a 10-20 Mbps uplink data rate and 40-260 Mbps downlink data rate, depending on the Artemis II mission phase. The ACCESS project will also provide a centralized mission data interface for user data distribution and storage to the MCC and perform planning and scheduling of services in coordination with the Operations Segment for the O2O Ground Segment. The O2O Ground Segment will support the following O2O mission phases: Pre-Mission Planning; Daily Operations Planning; Event Execution; and Post-Pass Reporting. O2O will be used to exchange data files between Orion and the MCC and to distribute real-time video through the optical downlink service to the MCC; which would not be possible without the high-bandwidth link that O2O will provide to Orion. In this paper, I will discuss the O2O Ground Segment development approach and how it will support these critical O2O functions: plan and schedule the contact; acquire and track the optical link; flow information bidirectionally; distribute information; and control and accommodate the system.

optical communications↗
NASA NTRS2017

Hyper-Spectral Networking Concept of Operations and Future Air Traffic Management Simulations

The NASA sponsored Hyper-Spectral Communications and Networking for Air Traffic Management (ATM) (HSCNA) project is conducting research to improve the operational efficiency of the future National Airspace System (NAS) through diverse and secure multi-band, multi-mode, and millimeter-wave (mmWave) wireless links. Worldwide growth of air transportation and the coming of unmanned aircraft systems (UAS) will increase air traffic density and complexity. Safe coordination of aircraft will require more capable technologies for communications, navigation, and surveillance (CNS). The HSCNA project will provide a foundation for technology and operational concepts to accommodate a significantly greater number of networked aircraft. This paper describes two of the HSCNA projects technical challenges. The first technical challenge is to develop a multi-band networking concept of operations (ConOps) for use in multiple phases of flight and all communication link types. This ConOps will integrate the advanced technologies explored by the HSCNA project and future operational concepts into a harmonized vision of future NAS communications and networking. The second technical challenge discussed is to conduct simulations of future ATM operations using multi-bandmulti-mode networking and technologies. Large-scale simulations will assess the impact, compared to todays system, of the new and integrated networks and technologies under future air traffic demand.

communication link modeling↗
NASA NTRS2006

HSI Guidelines Outline for the Air Vehicle Control Station. Version 2

This document provides guidance to the FAA and manufacturers on how to develop UAS Pilot Vehicle Interfaces to safely and effectively integrate UASs into the NAS. Preliminary guidelines are provided for Aviate, Communicate, Navigate and Avoid Hazard functions. The pilot shall have information and control capability so that pilot-UA interactions are not adverse, unfavorable, nor compromise safety. Unfavorable interactions include anomalous aircraft-pilot coupling (APC) interactions (closed loop), pilot-involved oscillations (categories I, II or III), and non-oscillatory APC events (e.g., divergence). - Human Systems Integration Pilot-Technology Interface Requirements for Command, Control, and Communications (C3)

Source record↗
NASA NTRS2006

AERCam Autonomy: Intelligent Software Architecture for Robotic Free Flying Nanosatellite Inspection Vehicles

The NASA Johnson Space Center has developed a nanosatellite-class Free Flyer intended for future external inspection and remote viewing of human spacecraft. The Miniature Autonomous Extravehicular Robotic Camera (Mini AERCam) technology demonstration unit has been integrated into the approximate form and function of a flight system. The spherical Mini AERCam Free Flyer is 7.5 inches in diameter and weighs approximately 10 pounds, yet it incorporates significant additional capabilities compared to the 35-pound, 14-inch diameter AERCam Sprint that flew as a Shuttle flight experiment in 1997. Mini AERCam hosts a full suite of miniaturized avionics, instrumentation, communications, navigation, power, propulsion, and imaging subsystems, including digital video cameras and a high resolution still image camera. The vehicle is designed for either remotely piloted operations or supervised autonomous operations, including automatic stationkeeping, point-to-point maneuvering, and waypoint tracking. The Mini AERCam Free Flyer is accompanied by a sophisticated control station for command and control, as well as a docking system for automated deployment, docking, and recharge at a parent spacecraft. Free Flyer functional testing has been conducted successfully on both an airbearing table and in a six-degree-of-freedom closed-loop orbital simulation with avionics hardware in the loop. Mini AERCam aims to provide beneficial on-orbit views that cannot be obtained from fixed cameras, cameras on robotic manipulators, or cameras carried by crewmembers during extravehicular activities (EVA s). On Shuttle or International Space Station (ISS), for example, Mini AERCam could support external robotic operations by supplying orthogonal views to the intravehicular activity (IVA) robotic operator, supply views of EVA operations to IVA and/or ground crews monitoring the EVA, and carry out independent visual inspections of areas of interest around the spacecraft. To enable these future benefits with minimal impact on IVA operators and ground controllers, the Mini AERCam system architecture incorporates intelligent systems attributes that support various autonomous capabilities. 1) A robust command sequencer enables task-level command scripting. Command scripting is employed for operations such as automatic inspection scans over a region of interest, and operator-hands-off automated docking. 2) A system manager built on the same expert-system software as the command sequencer provides detection and smart-response capability for potential system-level anomalies, like loss of communications between the Free Flyer and control station. 3) An AERCam dynamics manager provides nominal and off-nominal management of guidance, navigation, and control (GN&C) functions. It is employed for safe trajectory monitoring, contingency maneuvering, and related roles. This paper will describe these architectural components of Mini AERCam autonomy, as well as the interaction of these elements with a human operator during supervised autonomous control.

Fredrickson, Steven E.↗
NASA NTRS2006

Airport Surface Network Architecture Definition

Currently, airport surface communications are fragmented across multiple types of systems. These communication systems for airport operations at most airports today are based dedicated and separate architectures that cannot support system-wide interoperability and information sharing. The requirements placed upon the Communications, Navigation, and Surveillance (CNS) systems in airports are rapidly growing and integration is urgently needed if the future vision of the National Airspace System (NAS) and the Next Generation Air Transportation System (NGATS) 2025 concept are to be realized. To address this and other problems such as airport surface congestion, the Space Based Technologies Project s Surface ICNS Network Architecture team at NASA Glenn Research Center has assessed airport surface communications requirements, analyzed existing and future surface applications, and defined a set of architecture functions that will help design a scalable, reliable and flexible surface network architecture to meet the current and future needs of airport operations. This paper describes the systems approach or methodology to networking that was employed to assess airport surface communications requirements, analyze applications, and to define the surface network architecture functions as the building blocks or components of the network. The systems approach used for defining these functions is relatively new to networking. It is viewing the surface network, along with its environment (everything that the surface network interacts with or impacts), as a system. Associated with this system are sets of services that are offered by the network to the rest of the system. Therefore, the surface network is considered as part of the larger system (such as the NAS), with interactions and dependencies between the surface network and its users, applications, and devices. The surface network architecture includes components such as addressing/routing, network management, network performance and security.

Nguyen, Thanh C.↗
NASA NTRS2017

Considerations for an Integrated UAS CNS Architecture

The National Aeronautics and Space Administration (NASA) Glenn Research Center (GRC) is investigating revolutionary and advanced universal, reliable, always available, cyber secure and affordable Communication, Navigation, Surveillance (CNS) options for all altitudes of UAS operations. In Spring 2015, NASA issued a Call for Proposals under NASA Research Announcements (NRA) NNH15ZEA001N, Amendment 7 Subtopic 2.4. Boeing was selected to conduct a study with the objective to determine the most promising candidate technologies for Unmanned Air Systems (UAS) air-to-air and air-to-ground data exchange and analyze their suitability in a post-NextGen NAS environment. The overall objectives are to develop UAS CNS requirements and then develop architectures that satisfy the requirements for UAS in both controlled and uncontrolled air space. This contract is funded under NASAs Aeronautics Research Mission Directorates (ARMD) Aviation Operations and Safety Program (AOSP) Safe Autonomous Systems Operations (SASO) project and proposes technologies for the Unmanned Air Systems Traffic Management (UTM) service.There is a need for accommodating large-scale populations of Unmanned Air Systems (UAS) in the national air space. Scale obviously impacts capacity planning for Communication, Navitation, and Surveillance (CNS) technologies. For example, can wireless communications data links provide the necessary capacity for accommodating millions of small UASs (sUAS) nationwide? Does the communications network provide sufficient Internet Protocol (IP) address space to allow air traffic control to securely address both UAS teams as a whole as well as individual UAS within each team? Can navigation and surveillance approaches assure safe route planning and safe separation of vehicles even in crowded skies?Our objective is to identify revolutionary and advanced CNS alternatives supporting UASs operating at all altitudes and in all airspace while accurately navigating in the absence of navigational aids. These CNS alternatives must be reliable, redundant, always available, cyber-secure, and affordable for all types of vehicles including small UAS to large transport category aircraft. The approach will identify CNS technology candidates that can meet the needs of the range of UAS missions to specific air traffic management applications where they will be most beneficial and cost effective.

Templin, Fred L.↗
NASA NTRS2006

Lunar Relay Satellite Network for Space Exploration: Architecture, Technologies and Challenges

NASA is planning a series of short and long duration human and robotic missions to explore the Moon and then Mars. A key objective of these missions is to grow, through a series of launches, a system of systems infrastructure with the capability for safe and sustainable autonomous operations at minimum cost while maximizing the exploration capabilities and science return. An incremental implementation process will enable a buildup of the communication, navigation, networking, computing, and informatics architectures to support human exploration missions in the vicinities and on the surfaces of the Moon and Mars. These architectures will support all space and surface nodes, including other orbiters, lander vehicles, humans in spacesuits, robots, rovers, human habitats, and pressurized vehicles. This paper describes the integration of an innovative MAC and networking technology with an equally innovative position-dependent, data routing, network technology. The MAC technology provides the relay spacecraft with the capability to autonomously discover neighbor spacecraft and surface nodes, establish variable-rate links and communicate simultaneously with multiple in-space and surface clients at varying and rapidly changing distances while making optimum use of the available power. The networking technology uses attitude sensors, a time synchronization protocol and occasional orbit-corrections to maintain awareness of its instantaneous position and attitude in space as well as the orbital or surface location of its communication clients. A position-dependent data routing capability is used in the communication relay satellites to handle the movement of data among any of multiple clients (including Earth) that may be simultaneously in view; and if not in view, the relay will temporarily store the data from a client source and download it when the destination client comes into view. The integration of the MAC and data routing networking technologies would enable a relay satellite system to provide end-to-end communication services for robotic and human missions in the vicinity, or on the surface of the Moon with a minimum of Earth-based operational support.

Bhasin, Kul B.↗
NASA NTRS2020

New Flight Rules to Enable the Era of Aerial Mobility in the National Airspace System

In the 21st Century, new aviation markets, vehicle types, and technologies are fast emerging, inspiring new operational concepts for the National Airspace System such as Unmanned Aircraft Systems Traffic Management and Urban Air Mobility. These novel operations envision a dramatic increase in aerial mobility, or the ability to navigate freely through the airspace with unprecedented access and operational flexibility. Implementing these concepts presents a major challenge to the existing operational modes of Visual Flight Rules (VFR) and Instrument Flight Rules (IFR), developed under the limitations of early 20th Century technology and procedures to ensure safe navigation and separation from traffic. To meet this challenge and to support the needs of operators in the 21st Century and beyond, this paper proposes that VFR and IFR be augmented by new flight rules – Digital Flight Rules (DFR) – that leverage modern and emerging technologies and are not bound by restrictions borne of the state of technology 75-100 years ago. The objective of DFR is to provide safe and unfettered access to the airspace to all participating vehicle operators under all visibility conditions without incurring the limitations in operational flexibility inherent to IFR and even VFR. Advancements in communications, navigation, surveillance, aircraft connectivity, information access, automation technology, and supporting ground infrastructure provide the opportunity for the vehicle operator to engage at an unprecedented level in managing their flights regardless of flight visibility. Under DFR, these advancements enable the vehicle operator to assume full responsibility for traffic separation and therefore full trajectory management authority in all visibility conditions and airspace regions. The changes in roles and responsibilities are expected to enable greater airspace access and operational flexibility than afforded by IFR and VFR, thus enabling the emergence of new operations and a new era of advanced aerial mobility.

Mobility↗
NASA NTRSDate not supplied

Digital Flight: Enabling the Era of Scalable Mobility in the National Airspace System

In the 21st Century, new aviation markets, vehicle types, and technologies are fast emerging, inspiring new operational concepts for the National Airspace System such as Unmanned Aircraft Systems Traffic Management and Urban Air Mobility. These novel operations envision a dramatic increase in aerial mobility, or the ability to navigate freely through the airspace with unprecedented access and operational flexibility. Implementing these concepts presents a major challenge to the existing operational modes of Visual Flight Rules (VFR) and Instrument Flight Rules (IFR), developed under the limitations of early 20th Century technology and procedures to ensure safe navigation and separation from traffic. To meet this challenge and to support the needs of operators in the 21st Century and beyond, this paper proposes that VFR and IFR be augmented by new flight rules – Digital Flight Rules (DFR) – that leverage modern and emerging technologies and are not bound by restrictions borne of the state of technology 75-100 years ago. The objective of DFR is to provide safe and unfettered access to the airspace to all participating vehicle operators under all visibility conditions without incurring the limitations in operational flexibility inherent to IFR and even VFR. Advancements in communications, navigation, surveillance, aircraft connectivity, information access, automation technology, and supporting ground infrastructure provide the opportunity for the vehicle operator to engage at an unprecedented level in managing their flights regardless of flight visibility. Under DFR, these advancements enable the vehicle operator to assume full responsibility for traffic separation and therefore full trajectory management authority in all visibility conditions and airspace regions. The changes in roles and responsibilities are expected to enable greater airspace access and operational flexibility than afforded by IFR and VFR, thus enabling the emergence of new operations and a new era of advanced aerial mobility.

Mobility↗
NASA NTRS2013

Test Waveform Applications for JPL STRS Operating Environment

This software demonstrates use of the JPL Space Telecommunications Radio System (STRS) Operating Environment (OE), tests APIs (application programming interfaces) presented by JPL STRS OE, and allows for basic testing of the underlying hardware platform. This software uses the JPL STRS Operating Environment ["JPL Space Tele com - munications Rad io System Operating Environment,"(NPO-4776) NASA Tech Briefs, commercial edition, Vol. 37, No. 1 (January 2013), p. 47] to interact with the JPL-SDR Software Defined Radio developed for the CoNNeCT (COmmunications, Navigation, and Networking rEconfigurable Testbed) Project as part of the SCaN Testbed installed on the International Space Station (ISS). These are the first applications that are compliant with the new NASA STRS Architecture Standard. Several example waveform applications are provided to demonstrate use of the JPL STRS OE for the JPL-SDR platform used for the CoNNeCT Project. The waveforms provide a simple digitizer and playback capability for the SBand RF slice, and a simple digitizer for the GPS slice [CoNNeCT Global Positioning System RF Module, (NPO-47764) NASA Tech Briefs, commercial edition, Vol. 36, No. 3 (March 2012), p. 36]. These waveforms may be used for hardware test, as well as for on-orbit or laboratory checkout. Additional example waveforms implement SpaceWire and timer modules, which can be used for time transfer and demonstration of communication between the two Xilinx FPGAs in the JPLSDR. The waveforms are also compatible with ground-based use of the JPL STRS OE on radio breadboards and Linux.

Lux, James P.↗
NASA NTRS2005

A Framework for Integration of IVHM Technologies for Intelligent Integration for Vehicle Management

As a part of the overall goal of developing Integrated Vehicle Health Management (IVHM) systems for aerospace vehicles, the NASA Faculty Fellowship Program (NFFP) at Marshall Space Flight Center has performed a pilot study on IVHM principals which integrates researched IVHM technologies in support of Integrated Intelligent Vehicle Management (IIVM). IVHM is the process of assessing, preserving, and restoring system functionality across flight and ground systems (NASA NGLT 2004). The framework presented in this paper integrates advanced computational techniques with sensor and communication technologies for spacecraft that can generate responses through detection, diagnosis, reasoning, and adapt to system faults in support of IIVM. These real-time responses allow the IIVM to modify the effected vehicle subsystem(s) prior to a catastrophic event. Furthermore, the objective of this pilot program is to develop and integrate technologies which can provide a continuous, intelligent, and adaptive health state of a vehicle and use this information to improve safety and reduce costs of operations. Recent investments in avionics, health management, and controls have been directed towards IIVM. As this concept has matured, it has become clear the IIVM requires the same sensors and processing capabilities as the real-time avionics functions to support diagnosis of subsystem problems. New sensors have been proposed, in addition, to augment the avionics sensors to support better system monitoring and diagnostics. As the designs have been considered, a synergy has been realized where the real-time avionics can utilize sensors proposed for diagnostics and prognostics to make better real-time decisions in response to detected failures. IIVM provides for a single system allowing modularity of functions and hardware across the vehicle. The framework that supports IIVM consists of 11 major on-board functions necessary to fully manage a space vehicle maintaining crew safety and mission objectives: Guidance and Navigation; Communications and Tracking; Vehicle Monitoring; Information Transport and Integration; Vehicle Diagnostics; Vehicle Prognostics; Vehicle mission Planning; Automated Repair and Replacement; Vehicle Control; Human Computer Interface; and Onboard Verification and Validation. Furthermore, the presented framework provides complete vehicle management which not only allows for increased crew safety and mission success through new intelligence capabilities, but also yields a mechanism for more efficient vehicle operations. The representative IVHM technologies for IIVH includes: 1) robust controllers for use in re-usable launch vehicles, 2) scaleable/flexible computer platform using heterogeneous communication, 3) coupled electromagnetic oscillators for enhanced communications, 4) Linux-based real-time systems, 5) genetic algorithms, 6) Bayesian Networks, 7) evolutionary algorithms, 8) dynamic systems control modeling, and 9) advanced sensing capabilities. This paper presents IVHM technologies developed under NASA's NFFP pilot project. The integration of these IVHM technologies forms the framework for IIVM.

Paris, Deidre E.↗
NASA NTRS2005

Intelligent Vehicle Health Management

As a part of the overall goal of developing Integrated Vehicle Health Management systems for aerospace vehicles, the NASA Faculty Fellowship Program (NFFP) at Marshall Space Flight Center has performed a pilot study on IVHM principals which integrates researched IVHM technologies in support of Integrated Intelligent Vehicle Management (IIVM). IVHM is the process of assessing, preserving, and restoring system functionality across flight and ground systems (NASA NGLT 2004). The framework presented in this paper integrates advanced computational techniques with sensor and communication technologies for spacecraft that can generate responses through detection, diagnosis, reasoning, and adapt to system faults in support of INM. These real-time responses allow the IIVM to modify the affected vehicle subsystem(s) prior to a catastrophic event. Furthermore, the objective of this pilot program is to develop and integrate technologies which can provide a continuous, intelligent, and adaptive health state of a vehicle and use this information to improve safety and reduce costs of operations. Recent investments in avionics, health management, and controls have been directed towards IIVM. As this concept has matured, it has become clear the INM requires the same sensors and processing capabilities as the real-time avionics functions to support diagnosis of subsystem problems. New sensors have been proposed, in addition, to augment the avionics sensors to support better system monitoring and diagnostics. As the designs have been considered, a synergy has been realized where the real-time avionics can utilize sensors proposed for diagnostics and prognostics to make better real-time decisions in response to detected failures. IIVM provides for a single system allowing modularity of functions and hardware across the vehicle. The framework that supports IIVM consists of 11 major on-board functions necessary to fully manage a space vehicle maintaining crew safety and mission objectives: Guidance and Navigation; Communications and Tracking; Vehicle Monitoring; Information Transport and Integration; Vehicle Diagnostics; Vehicle Prognostics; Vehicle mission Planning; Automated Repair and Replacement; Vehicle Control; Human Computer Interface; and Onboard Verification and Validation. Furthermore, the presented framework provides complete vehicle management which not only allows for increased crew safety and mission success through new intelligence capabilities, but also yields a mechanism for more efficient vehicle operations. The representative IVHM technologies for computer platform using heterogeneous communication, 3) coupled electromagnetic oscillators for enhanced communications, 4) Linux-based real-time systems, 5) genetic algorithms, 6) Bayesian Networks, 7) evolutionary algorithms, 8) dynamic systems control modeling, and 9) advanced sensing capabilities. This paper presents IVHM technologies developed under NASA's NFFP pilot project and the integration of these technologies forms the framework for IIVM.

Paris, Deidre E.↗
NASA NTRS2005

IVHM Framework for Intelligent Integration for Vehicle Health Management

Integrated Vehicle Health Management (IVHM) systems for aerospace vehicles, is the process of assessing, preserving, and restoring system functionality across flight and techniques with sensor and communication technologies for spacecraft that can generate responses through detection, diagnosis, reasoning, and adapt to system faults in support of Integrated Intelligent Vehicle Management (IIVM). These real-time responses allow the IIVM to modify the affected vehicle subsystem(s) prior to a catastrophic event. Furthermore, this framework integrates technologies which can provide a continuous, intelligent, and adaptive health state of a vehicle and use this information to improve safety and reduce costs of operations. Recent investments in avionics, health management, and controls have been directed towards IIVM. As this concept has matured, it has become clear that IIVM requires the same sensors and processing capabilities as the real-time avionics functions to support diagnosis of subsystem problems. New sensors have been proposed, in addition to augment the avionics sensors to support better system monitoring and diagnostics. As the designs have been considered, a synergy has been realized where the real-time avionics can utilize sensors proposed for diagnostics and prognostics to make better real-time decisions in response to detected failures. IIVM provides for a single system allowing modularity of functions and hardware across the vehicle. The framework that supports IIVM consists of 11 major on-board functions necessary to fully manage a space vehicle maintaining crew safety and mission objectives. These systems include the following: Guidance and Navigation; Communications and Tracking; Vehicle Monitoring; Information Transport and Integration; Vehicle Diagnostics; Vehicle Prognostics; Vehicle Mission Planning, Automated Repair and Replacement; Vehicle Control; Human Computer Interface; and Onboard Verification and Validation. Furthermore, the presented framework provides complete vehicle management which not only allows for increased crew safety and mission success through new intelligence capabilities, but also yields a mechanism for more efficient vehicle operations.

Paris, Deidre↗
NASA NTRS2024

Testing of Advanced Capabilities to Enable In-time Safety Management and Assurance for Future Flight Operations

In order to refine an initial Concept of Operations, explore Concepts of Use, and expose/validate requirements for future In-Time Aviation Safety Management Systems (IASMS), testing architectures were created, along with a set of capabilities and underlying information exchange protocols. These systems were conceived and developed based on hazards associated with two envisioned urban area flight domains: (1) highly autonomous small uncrewed aerial systems (sUAS) operating at low altitudes, and (2) highly autonomous air taxis. The initial scope of this development is described in [1]; this report provides an update, focusing on the subsequent developments and test activities. As stated in [1], it is important to note that there are many capabilities already in use by the industry (or soon to be in use) that will play critical roles in future IASMS designs. Those reported here were developed to address a gap in the current state-of-the-art regarding specific hazards/risks, and/or to allow for investigation of the interplay between and across hazard types — particularly regarding how overall safety risk can be reduced or managed effectively. Results of testing and development activities are organized by the operational phase wherein a particular capability would be employed (i.e., preflight, in-flight, and post-flight/off-line). Pre-flight: A set of capabilities were developed to help mitigate safety risk prior to flight (e.g., during flight and mission planning). Results of testing summarize (1) validation activities to raise the Technology Readiness Level (TRL) and (2) evaluation activities where the capabilities were applied to flight/mission planning procedures and used by operators/pilots. For the latter, flight plans were automatically assessed, and operators/pilots were notified of hazardous flight segments so as to enable adjustment of the flight plan and re-evaluation, and/or to better inform go/no-go decisions. Capabilities addressed hazards associated with power consumption, third-party risk, wind, navigation system performance, radiofrequency interference, and proximity to geo-spatial threats (e.g., buildings, trees, and no-fly zones). In-flight: Flight experiments tested capabilities that detect and respond to hazards encountered during flight. In the first series, safety hazards were monitored and assessed onboard, and system-generated mitigation maneuvers were recorded (but not acted upon by the vehicle). In the second series, mitigation maneuver commands directed the aircraft in response to safety hazards (i.e., auto-mitigation). The sUAS used for testing is described in full, as is the test architecture, which included commercial avionics, research avionics, and onboard software designed to detect, assess, and respond to hazards. The onboard system was designed as a run-time assurance framework, consistent with [2] and supportive of both supervisory and automated modes. The primary functions included: real-time risk assessment (RTRA), auto-pilot monitoring, constraint monitoring, and contingency select/triggering. RTRA performs integrated risk assessment considering data from several hazard-related monitors (e.g., battery, motors, navigation, communications, population density, and loss-of-control). Post-flight/off-line: Data monitored and recorded during flights can enable IASMS capabilities that execute after flights have completed (or “off-line”). These include: (1) the ability to identify anomalies and trends that may only be observable when comparing data spanning a number of similar flights; (2) the ability to update and validate pre-flight and in-flight capabilities and any underlying models to improve their performance; (3) the ability to report anomalies/off-nominals that may indicate design changes or maintenance actions are needed; and (4) the ability for humans involved in operations to report safety-relevant observations to help in understanding the flight data and/or the operational context of a flight. Progress on three such capabilities is summarized; the first investigates anomaly detection given a limited set of flight logs and applies an approach previously used for space operations. The second explores what could be identified using a larger set of flight logs, including from web-based forums where flight logs are posted by sUAS autopilot users. The third creates a new means of collecting information on UAS incidents and accidents via the Aviation Safety Reporting System (ASRS).

sUAS↗
NASA NTRS2011

Deep Space Networking Experiments on the EPOXI Spacecraft

NASA's Space Communications & Navigation Program within the Space Operations Directorate is operating a program to develop and deploy Disruption Tolerant Networking [DTN] technology for a wide variety of mission types by the end of 2011. DTN is an enabling element of the Interplanetary Internet where terrestrial networking protocols are generally unsuitable because they rely on timely and continuous end-to-end delivery of data and acknowledgments. In fall of 2008 and 2009 and 2011 the Jet Propulsion Laboratory installed and tested essential elements of DTN technology on the Deep Impact spacecraft. These experiments, called Deep Impact Network Experiment (DINET 1) were performed in close cooperation with the EPOXI project which has responsibility for the spacecraft. The DINET 1 software was installed on the backup software partition on the backup flight computer for DINET 1. For DINET 1, the spacecraft was at a distance of about 15 million miles (24 million kilometers) from Earth. During DINET 1 300 images were transmitted from the JPL nodes to the spacecraft. Then, they were automatically forwarded from the spacecraft back to the JPL nodes, exercising DTN's bundle origination, transmission, acquisition, dynamic route computation, congestion control, prioritization, custody transfer, and automatic retransmission procedures, both on the spacecraft and on the ground, over a period of 27 days. The first DINET 1 experiment successfully validated many of the essential elements of the DTN protocols. DINET 2 demonstrated: 1) additional DTN functionality, 2) automated certain tasks which were manually implemented in DINET 1 and 3) installed the ION SW on nodes outside of JPL. DINET 3 plans to: 1) upgrade the LTP convergence-layer adapter to conform to the international LTP CL specification, 2) add convergence-layer "stewardship" procedures and 3) add the BSP security elements [PIB & PCB]. This paper describes the planning and execution of the flight experiment and the validation results.

automated data communication↗
NASA NTRS1971

Environmental statement for Applications Technology Satellite program

The experiments, environmental impact, and applications of data collected by ATS are discussed. Data cover communications, navigation, meteorology, data collection (including data from small unattended remote stations such as buoys, seismology and hydrology monitors, etc.), geodesy, and scientific experiments to define the environment at synchronous orbit, and to monitor emissions from the sun.

Source record↗
NASA NTRS1972

Applications Technology Satellites -F and -G.

The objectives of the Applications Technology Satellite (ATS) Program are to advance space technology in areas of importance to mankind. A brief description of the planned satellites and experiments is presented. The experiments include instructional television, communications, navigation, meteorology, spacecraft technology and science. The ATS-F and -G satellites will have 30-foot deployable antennas and will serve as three-axis stabilized platforms in geostationary orbit with 0.1 degree pointing accuracy.

Gerwin, H. L.↗
NASA NTRS1972

The deep space network, volume 12

Progress in the development of the DSN is reported along with TDA research and technology, network engineering, hardware, and software implementation. Included are descriptions of the DSN function and facilities, Helios mission support, Mariner Venus/Mercury 1973 mission support, Viking mission support, tracking and ground-based navigation, communications, network control and data processing, and deep space stations.

Source record↗