Search NASA⌕ Search

SEARCH · Search NASA

Results for “communication system interfaces”

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 109 records · Page 6

CLINICAL DECISION SUPPORT: PATH TO FUNCTIONAL REQUIREMENTS

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data and crew time), limited options for evacuation and those associated with delayed or constrained communications, all of which demand greater crew autonomy. Specifically, as the communication delays intensify the further we explore space, the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will be key to mission continuation and success. To augment the requisite knowledge, skills and abilities (KSAs) of a time-constrained crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution that would facilitate, guide and inform Earth-independent medical operations, while assisting crewmembers through various clinical presentations. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit. ExMC is actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses gap Medical-701 within the Inflight Medical Conditions risk: “Enhance medical capabilities within an exploration medical system.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology continues to advance this decade and beyond. Hence, data, software and computational resources will play an essential and synergistic role in maintaining crew health, wellness and performance in deep space missions. The focus of the CDS project is to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance and medical care during exploration missions. The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/databases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that incorporate work from collaborators yet maintain a flexible platform for integrating new technology in the future. In fiscal year 2021 (FY21), the CDS project identified requirements through two primary mechanisms: (i) the development of software implementation prototypes and (ii) the application of systems engineering processes. The CDS project developed and tested a series of increasingly complex system prototypes that were based on use cases derived from the CDSS concept of operations (ConOps). These software implementations yielded insights on CDSS functionality as well as lessons learned that provided the initial requirements for CDSS capability. By applying a systems engineering (SE) approach, medical scenarios provided in the ConOps and the use cases for software implementation underwent functional decomposition to identify CDSS functionality. Also, systems-based modeling language (SysML) tools such as activity diagrams were developed from the same ConOps and use cases to identify CDSS functionality. The lessons learned from software implementation defined both specific requirements and broad areas of requirements. Within these defined broad requirement areas, further analysis of the SE products identified specific capability that resulted in the final functional requirements. In summary, the software prototypes, functional decomposition of the ConOps and use cases, and SysML diagrams provided the basis for the CDSS requirements developed in FY21. In the upcoming year, these requirements will be refined for their final ExMC baseline review in latter FY22.

clinical decision support↗

Clinical Decision Support: Path to Functional Requirements

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data and crew time), limited options for evacuation and those associated with delayed or constrained communications, all of which demand greater crew autonomy. Specifically, as the communication delays intensify the further we explore space, the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will be key to mission continuation and success. To augment the requisite knowledge, skills and abilities (KSAs) of a time-constrained crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution that would facilitate, guide and inform Earth-independent medical operations, while assisting crewmembers through various clinical presentations. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit. ExMC is actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses gap Medical-701 within the Inflight Medical Conditions risk: “Enhance medical capabilities within an exploration medical system.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology continues to advance this decade and beyond. Hence, data, software and computational resources will play an essential and synergistic role in maintaining crew health, wellness and performance in deep space missions. The focus of the CDS project is to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance and medical care during exploration missions. The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/databases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that incorporate work from collaborators yet maintain a flexible platform for integrating new technology in the future. In fiscal year 2021 (FY21), the CDS project identified requirements through two primary mechanisms: (i) the development of software implementation prototypes and (ii) the application of systems engineering processes. The CDS project developed and tested a series of increasingly complex system prototypes that were based on use cases derived from the CDSS concept of operations (ConOps). These software implementations yielded insights on CDSS functionality as well as lessons learned that provided the initial requirements for CDSS capability. By applying a systems engineering (SE) approach, medical scenarios provided in the ConOps and the use cases for software implementation underwent functional decomposition to identify CDSS functionality. Also, systems-based modeling language (SysML) tools such as activity diagrams were developed from the same ConOps and use cases to identify CDSS functionality. The lessons learned from software implementation defined both specific requirements and broad areas of requirements. Within these defined broad requirement areas, further analysis of the SE products identified specific capability that resulted in the final functional requirements. In summary, the software prototypes, functional decomposition of the ConOps and use cases, and SysML diagrams provided the basis for the CDSS requirements developed in FY21. In the upcoming year, these requirements will be refined for their final ExMC baseline review in latter FY22.

Clinical decision support↗

Clinical Decision Support Project

As NASA plans for exploration missions into deep space, significant challenges are realized due to the distance from Earth. Beside the effects of microgravity and radiation exposure, the astronauts face the additional constraints of isolation, lack of resupply, increasingly difficult evacuation, and delayed and disrupted communication with ground-based medical care providers. These constraints require a paradigm shift from current medical care where crews rely on the real-time communications with ground-based medical care providers toward Earth-independent medical operations for astronaut medical care. Medical expertise and decision-making are ground-based for current International Space Station and planned Lunar missions. However, a deep space exploration crew will need to autonomously perform the detection, diagnosis, treatment, and prevention of medical conditions. One approach to provide Earth-independent medical operations is to augment the requisite knowledge, skills, and abilities (KSAs) of a time-constrained crew—operating under stressful conditions, combatting fatigue, and facing a potential medical crisis—with a robust clinical decision support system (CDSS). The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/data bases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that maintain a flexible platform for integrating new technology in the future. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit by actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addressed ap Medical-701 within the Inflight Medical Conditions risk: “We need to increase inflight medical capabilities and identify new capabilities that (a) maximize benefit and/or (b) reduce “costs” on human system/mission/vehicle resources.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology advances in this decade and beyond. Hence, data, software, and computational resources will play an essential and synergistic role in maintaining crew health, wellness, and performance in deep space missions. The focus of the CDS project was to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance, and medical care during exploration missions. In fiscal year 2022 (FY22), the CDS project was chartered to baseline and/or revise all CDS project related documentation and update the CDS project model to include the revised CDSS Concept of Operations, revised systems-based modeling language (SysML) activity diagrams, and baseline requirements. The focus of this presentation will be an overview of the CDS products and CDS model content.

Decision Support↗

NASA Near Earth Network (NEN), Deep Space Network (DSN) and Space Network (SN) Support of CubeSat Communications

There has been a historical trend to increase capability and drive down the Size, Weight and Power (SWAP) of satellites and that trend continues today. Small satellites, including systems conforming to the CubeSat specification, because of their low launch and development costs, are enabling new concepts and capabilities for science investigations across multiple fields of interest to NASA. NASA scientists and engineers across many of NASAs Mission Directorates and Centers are developing exciting CubeSat concepts and welcome potential partnerships for CubeSat endeavors. From a communications and tracking point of view, small satellites including CubeSats are a challenge to coordinate because of existing small spacecraft constraints, such as limited SWAP and attitude control, low power, and the potential for high numbers of operational spacecraft. The NASA Space Communications and Navigation (SCaN) Programs Near Earth Network (NEN), Deep Space Network (DSN) and the Space Network (SN) are customer driven organizations that provide comprehensive communications services for space assets including data transport between a missions orbiting satellite and its Mission Operations Center (MOC). The NASA NEN consists of multiple ground antennas. The SN consists of a constellation of geosynchronous (Earth orbiting) relay satellites, named the Tracking and Data Relay Satellite System (TDRSS). The DSN currently makes available 13 antennas at its three tracking stations located around the world for interplanetary communication. The presentation will analyze how well these space communication networks are positioned to support the emerging small satellite and CubeSat market. Recognizing the potential support, the presentation will review the basic capabilities of the NEN, DSN and SN in the context of small satellites and will present information about NEN, DSN and SN-compatible flight radios and antenna development activities at the Goddard Space Flight Center (GSFC) and across industry. The presentation will review concepts on how the SN multiple access capability could help locate CubeSats and provide a low-latency early warning system. The presentation will also present how the DSN is evolving to maximize use of its assets for interplanetary CubeSats. The critical spectrum-related topics of available and appropriate frequency bands, licensing, and coordination will be reviewed. Other key considerations, such as standardization of radio frequency interfaces and flight and ground communications hardware systems, will be addressed as such standardization may reduce the amount of time and cost required to obtain frequency authorization and perform compatibility and end-to-end testing. Examples of standardization that exist today are the NASA NEN, DSN and SN systems which have published users guides and defined frequency bands for high data rate communication, as well as conformance to CCSDS standards. The workshop session will also seek input from the workshop participants to better understand the needs of small satellite systems and to identify key development activities and operational approaches necessary to enhance communication and navigation support using NASA's NEN, DSN and SN.

Telecommunication↗

Interface Provides Standard-Bus Communication

Microprocessor-controlled interface (IEEE-488/LVABI) incorporates service-request and direct-memory-access features. Is circuit card enabling digital communication between system called "laser auto-covariance buffer interface" (LVABI) and compatible personal computer via general-purpose interface bus (GPIB) conforming to Institute for Electrical and Electronics Engineers (IEEE) Standard 488. Interface serves as second interface enabling first interface to exploit advantages of GPIB, via utility software written specifically for GPIB. Advantages include compatibility with multitasking and support of communication among multiple computers. Basic concept also applied in designing interfaces for circuits other than LVABI for unidirectional or bidirectional handling of parallel data up to 16 bits wide.

Culliton, William G.↗

Advanced information processing system: Input/output system services

The functional requirements and detailed specifications for the Input/Output (I/O) Systems Services of the Advanced Information Processing System (AIPS) are discussed. The introductory section is provided to outline the overall architecture and functional requirements of the AIPS system. Section 1.1 gives a brief overview of the AIPS architecture as well as a detailed description of the AIPS fault tolerant network architecture, while section 1.2 provides an introduction to the AIPS systems software. Sections 2 and 3 describe the functional requirements and design and detailed specifications of the I/O User Interface and Communications Management modules of the I/O System Services, respectively. Section 4 illustrates the use of the I/O System Services, while Section 5 concludes with a summary of results and suggestions for future work in this area.

Masotto, Tom↗

Shuttle Ku-band and S-band communications implementations study

The interfaces between the Ku-band system and the TDRSS, between the S-band system and the TDRSS, GSTDN and SGLS networks, and between the S-band payload communication equipment and the other Orbiter avionic equipment were investigated. The principal activities reported are: (1) performance analysis of the payload narrowband bent-pipe through the Ku-band communication system; (2) performance evaluation of the TDRSS user constraints placed on the S-band and Ku-band communication systems; (3) assessment of the shuttle-unique S-band TDRSS ground station false lock susceptibility; (4) development of procedure to make S-band antenna measurements during orbital flight; (5) development of procedure to make RFI measurements during orbital flight to assess the performance degradation to the TDRSS S-band communication link; and (6) analysis of the payload interface integration problem areas.

Huth, G. K.↗

Common data buffer system

A high speed common data buffer system is described for providing an interface and communications medium between a plurality of computers utilized in a distributed computer complex forming part of a checkout, command and control system for space vehicles and associated ground support equipment. The system includes the capability for temporarily storing data to be transferred between computers, for transferring a plurality of interrupts between computers, for monitoring and recording these transfers, and for correcting errors incurred in these transfers. Validity checks are made on each transfer and appropriate error notification is given to the computer associated with that transfer.

Byrne, F.↗

Benefits of using Electronic Data Sheets (EDS) with coreFlight Systems (cFS) - A Project Example

Recently there has been interest in the incorporation of core Flight Systems (cFS) with Spacecraft Onboard Interface Services (SOIS) Electronic Data Sheets (EDS) in the spaceflight software community. The Regenerative Fuel Cell project at the Glenn Research Center is using cFS architecture with EDS support for its monitoring and control software. The presentation will outline the benefits to using cFS with EDS support: First, EDS establishes a single source of truth for the definitions of data structures used throughout an entire mission that may otherwise be programmed in different languages and designed with different processor architectures. Not only does this help with inter-application communication via the software bus, but it also greatly simplifies communication between systems. An EDS Application Programming Interface (API) library allows the conversion of EDS data structures to and from native data structures. Second, bindings for other programming languages (e.g. Lua, Python, JSON) have been written to allow the creation and manipulation of EDS data objects within those languages. The RFC project uses Lua scripts to automatically generate binary configuration files at build time to be loaded into our cFS programs. We also use Python bindings in a graphical user interface (GUI) to allow an operator to send commands and view telemetry messages sent from cFS instances. Finally, using Lua scripts we can set up specific simulation scenarios to perform automatic functional testing. During the development of the RFC software, the software team put together a generic python GUI called “cFS-EDS-GroundStation” that provides a basic interface to an instance of cFS with EDS support. The GUI includes a basic telecommand and telemetry system that reads directly from the generated EDS databases. In the telecommand system, dropdown menus are populated with all user commands that are defined in EDS. In the telemetry system, telemetry messages are automatically decoded, written to the screen, and saved to a binary file. Additional Python scripts have been written to convert the binary data files into a comma separated value (CSV) format for further processing. We will demonstrate the basic use of the cFS-EDS-GroundStation software including adding additional commands and telemetry payload values in EDS and see them appear automatically in the cFS-EDS-Groundstation software. About the RFC project: The Regenerative Fuel Cell project is tasked with developing and demonstrating a power system consisting of a fuel cell and electrolyzer to provide power during a lunar day/night cycle. During the night, the fuel cell takes Hydrogen and Oxygen gasses and converts them into electricity, water, and heat. During the day, the electrolyzer takes input power (e.g. from a photovoltaic array) and converts water back into Hydrogen and Oxygen gasses.

Mathew Mccaskey↗

Surface Systems and Interface Standardization

Space exploration on planetary surfaces will require the use of various surface systems which will likely need to interface with one another. These systems must communicate and share data, as well as distribute power and transfer fluids for sustainable surface operations. Such systems can range from landers, surface habitats, mobility systems, cargo, and In-Situ Resource Utilizations (ISRUs). Previous and current programs have developed space interoperability standards that help aid in reducing potential risks of interface integration. One example of this is the International Deep Space Interoperability Standards (IDSIS) which focuses on deep space exploration. A goal of the Artemis program is to develop a sustained human presence on the lunar surface that would be a training ground for future Mars exploration. Therefore, it will be beneficial to identify interface standards between the surface assets which will help mitigate risk and reduce complexity in the harsh environments of space exploration. A key contribution to sustainability is commonality between hardware and software interfaces. Generic interfaces for data, power, and fluids will reduce risk, promote interoperability, and define standard interfaces across surface exploration projects and programs. Standardized interfaces would be advantageous for improving efficiency and reducing overall complexity, which are critical considerations for future space exploration. Furthermore, it will provide cost reductions to the Artemis programs over their life cycle (in Operations & Maintenance (O&M) and Logistics). Unique proprietary interfaces if considered or allowed would not only increase complexity but also add cost to the programs. Of course, understanding what will work and not work effectively in these unique environments such as the lunar surface is important. These unique environments require much needed intelligent design, prototyping, comprehensive testing, and field experience, utilizing consensus on common interface solutions.

Jaime Gomez↗

pnnl/oedisi_dopf

OpenEDI - System Integration (OEDI-SI) - PNNL Distributed Optimal Power Flow (DOPF)

Slay, Tylor↗

Data management system technology discipline

Viewgraphs on data management system technology discipline for Space Station Freedom are presented. Topics covered include: systems technology area needs; storage technology area needs; processor technology area needs; communications technology area needs; software system technology area needs; human interface technology area needs; software development and verification; and onboard communications.

Benz, Harry F.↗

A Case for Application Oblivious Energy-Efficient MPI Runtime

Power has become the major impediment in designing large scale high-end systems. Message Passing Interface (MPI) is the {\em de facto} communication interface used as the back-end for designing applications, programming models and runtime for these systems. Slack --- the time spent by an MPI process in a single MPI call --- provides a potential for energy and power savings, if an appropriate power reduction technique such as core-idling/Dynamic Voltage and Frequency Scaling (DVFS) can be applied without perturbing application's execution time. Existing techniques that exploit slack for power savings assume that application behavior repeats across iterations/executions. However, an increasing use of adaptive, data-dependent workloads combined with system factors (OS noise, congestion) makes this assumption invalid. This paper proposes and implements Energy Aware MPI (EAM) --- an application-oblivious energy-efficient MPI runtime. EAM uses a combination of communication models of common MPI primitives (point-to-point, collective, progress, blocking/non-blocking) and an online observation of slack for maximizing energy efficiency. Each power lever incurs time overhead, which must be amortized over slack to minimize degradation. When predicted communication time exceeds a lever overhead, the lever is used {\em as soon as possible} --- to maximize energy efficiency. When mis-prediction occurs, the lever(s) are used automatically at specific intervals for amortization. We implement EAM using MVAPICH2 and evaluate it on ten applications using up to 4096 processes. Our performance evaluation on an InfiniBand cluster indicates that EAM can reduce energy consumption by 5--41\% in comparison to the default approach, with negligible (less than 4\% in all cases) performance loss.

Venkatesh, Akshay↗

Update - The Earth Observing System (EOS) forward and return link data processing and communications services

An overview is presented of the EOS ground support services in order to identify interfaces to and drivers of the data processing and communication systems. Generic system requirements are compared with those specifically needed for EOS, including processing requirements for forward link and return link data. Communications requirements for transporting the forward link data from the EOS Operations Center and for the transfer of level zero data to the EOS Data and Information System (EOSDIS) Distributed Active Archive Centers are specified. The forward and return link processing requirements of the EOS instruments from the international partners are also addressed. The overall context of EOSDIS in the Mission to Planet Earth Program is addressed.

Ramapriyan, H. K.↗

Saturn Facility Oil Transfer Automation System

The Saturn accelerator, owned by Sandia National Laboratories, has been in operation since the early 1980s and still has many of the original systems. A critical legacy system is the oil transfer system which transfers 250,000 gallons of transformer oil from outside storage tanks to the Saturn facility. The oil transfer system was identified for upgrade to current technology standards. Using the existing valves, pumps, and relay controls, the system was automated using the National Instruments cRIO FGPA platform. Engineered safety practices, including a failure mode effects analysis, were used to develop error handling requirements. The uniqueness of the Saturn Oil Automated Transfer System (SOATS) is in the graphical user interface. The SOATS uses an HTML interface to communicate to the cRIO, creating a platform independent control system. The SOATS was commissioned in April 2013.

02 PETROLEUM↗

Eye-voice-controlled interface

The Ocular Attention-Sensing Interface System (OASIS) is an innovative human-computer interface which utilizes eye movement and voice commands to communicate messages between the operator and the system. This report initially describes some technical issues relevant to the development of such an interface. The results of preliminary experiments which evaluate alternative eye processing algorithms and feedback techniques are presented. Candidate interface applications are also discussed.

Glenn, Floyd A., III↗

Communications and Tracking of Visiting Vehicles near ISS: The Design of the Reusable Launch Vehicle Communications

The International Space Station (ISS) will provide for the visitation of various vehicles such as the Shuttle, Automated Transfer Vehicle (ATV), H-II Transfer Vehicle (HTV), Crew Return Vehicle (CRV), Reusable Launch Vehicle (RLV) and Soyuz. These vehicles will provide for crew replacement, consumables resupply, and equipment delivery. In order for these vehicles to approach and eventually dock with the ISS, there must be near continuous communications coverage between the visiting vehicle and the ISS, as well as communications between the vehicle and a Mission Control Center (MCC). Since the ISS communications systems are already designed and scheduled for ISS activation, the vehicles must either utilize these communications systems or provide their own. There are two means of two-way communications with the ISS. These are (1) S-Band communications using TDRSS, and (2) UHF communications using some form of the Space to Space Station Radio (SSSR) link. The RLV utilizes ISS compatible communications systems to communicate with both the ISS and a Mission Control Center. Since all vehicles must adhere to the Visiting Vehicle Interface requirements given in reference 1, the RLV communications system design must meet these requirements during entry into the ISS Approach Ellipsoid (AE) and during Proximity Operations. Included in this paper are descriptions of these communications approaches as well as their potential utilization in the ISS communications system.

Stillwagen, Frederic H.↗

Network device interface for digitally interfacing data channels to a controller via a network

A communications system and method are provided for digitally connecting a plurality of data channels, such as sensors, actuators, and subsystems, to a controller using a network bus. The network device interface interprets commands and data received from the controller and polls the data channels in accordance with these commands. Specifically, the network device interface receives digital commands and data from the controller, and based on these commands and data, communicates with the data channels to either retrieve data in the case of a sensor or send data to activate an actuator. Data retrieved from the sensor is converted into digital signals and transmitted to the controller. Network device interfaces associated with different data channels can coordinate communications with the other interfaces based on either a transition in a command message sent by the bus controller or a synchronous clock signal.

Ellerbrock, Philip J.↗