Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “command and control”

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 991 records · Page 55
All sourcesNASA NTRSDOE OSTI
NASA NTRS2017

Conformal Lightweight Antenna Structures for Aeronautical Communication Technologies

This project is to develop antennas which enable beyond line of sight (BLOS) command and control for UAVs. We will take advantage of newly assigned provisional Ku-band spectrum for UAVs and use unique antenna designs to avoid interference with ground systems. This will involve designing antennas with high isotropic effective radiated power (EIRP) and ultra-low sidelobes. The antennas will be made with polymer aerogel as a substrate to both reduce weight and improve performance, as demonstrated in an Aero Seedling. In addition, designing the antennas to be conformal to the aircraft fuselage will reduce drag.

antennas↗
NASA NTRS2017

Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) Project

Over the past 5 years, the UAS integration into the NAS project has worked to reduce technical barriers to integration. A major focus of this work has been in support of RTCA SC-228. This committee has recently published the first UAS integration minimum performance standards (MOPS). This work has spanned detect and avoid (DAA) as well as command and control comm datalinks. I will discuss DAA efforts with focus on the human systems work. I will discuss how automation was discussed and addressed within this context. ICAO stood up a remotely piloted aircraft systems (RPAS) panel in 2014. They have developed an RPAS manual and are now working to revise existing annexes and standards and recommended practices. The Human In The System (HITS) has worked to infuse human factors guidelines into those documents. I will discuss that effort as well as how ICAO has defined and address autonomy. There is a great deal of interest in the control of multiple vehicles by a single operator. The UAS EXCOM Science and Research Panel (SARP) is holding a workshop on this topic in late June. I will discuss research performed on this topic when I worked for the Army and on-going work within the division and a NATO working group on Human-Autonomy Teaming.

Unmanned Aircraft Systems (UAS)↗
NASA NTRS2017

Field Programmable Gate Array Failure Rate Estimation Guidelines for Launch Vehicle Fault Tree Models

Today's launch vehicles complex electronic and avionics systems heavily utilize Field Programmable Gate Array (FPGA) integrated circuits (IC) for their superb speed and reconfiguration capabilities. Consequently, FPGAs are prevalent ICs in communication protocols such as MILSTD- 1553B and in control signal commands such as in solenoid valve actuations. This paper will identify reliability concerns and high level guidelines to estimate FPGA total failure rates in a launch vehicle application. The paper will discuss hardware, hardware description language, and radiation induced failures. The hardware contribution of the approach accounts for physical failures of the IC. The hardware description language portion will discuss the high level FPGA programming languages and software/code reliability growth. The radiation portion will discuss FPGA susceptibility to space environment radiation.

Al Hassan, Mohammad↗
NASA NTRS2017

Field Programmable Gate Array Failure Rate Estimation Guidelines for Launch Vehicle Fault Tree Models

Today's launch vehicles complex electronic and avionic systems heavily utilize the Field Programmable Gate Array (FPGA) integrated circuit (IC). FPGAs are prevalent ICs in communication protocols such as MIL-STD-1553B, and in control signal commands such as in solenoid/servo valves actuations. This paper will demonstrate guidelines to estimate FPGA failure rates for a launch vehicle, the guidelines will account for hardware, firmware, and radiation induced failures. The hardware contribution of the approach accounts for physical failures of the IC, FPGA memory and clock. The firmware portion will provide guidelines on the high level FPGA programming language and ways to account for software/code reliability growth. The radiation portion will provide guidelines on environment susceptibility as well as guidelines on tailoring other launch vehicle programs historical data to a specific launch vehicle.

Al Hassan, Mohammad↗
NASA NTRS2017

Field Programmable Gate Array Reliability Analysis Guidelines for Launch Vehicle Reliability Block Diagrams

Field Programmable Gate Arrays (FPGAs) integrated circuits (IC) are one of the key electronic components in today's sophisticated launch and space vehicle complex avionic systems, largely due to their superb reprogrammable and reconfigurable capabilities combined with relatively low non-recurring engineering costs (NRE) and short design cycle. Consequently, FPGAs are prevalent ICs in communication protocols and control signal commands. This paper will identify reliability concerns and high level guidelines to estimate FPGA total failure rates in a launch vehicle application. The paper will discuss hardware, hardware description language, and radiation induced failures. The hardware contribution of the approach accounts for physical failures of the IC. The hardware description language portion will discuss the high level FPGA programming languages and software/code reliability growth. The radiation portion will discuss FPGA susceptibility to space environment radiation.

Al Hassan, Mohammad↗
NASA NTRS2018

Increasing Flight Software Reuse with OpenSatKit

In January 2015 the NASA Goddard Space Flight Center (GSFC) released the Core Flight System (cFS) as open source under the NASA Open Source Agreement (NOSA) license. The cFS is based on flight software (FSW) developed for 12 spacecraft spanning nearly two decades of effort and it can provide about a third of the FSW functionality for a low-earth orbiting scientific spacecraft. The cFS is a FSW framework that is portable, configurable, and extendable using a product line deployment model. However, the components are maintained separately so the user must configure, integrate, and deploy them as a cohesive functional system. This can be very challenging especially for organizations such as universities building cubesats that have minimal experience developing FSW. Supporting universities was one of the primary motivators for releasing the cFS under NOSA. This paper describes the OpenSatKit that was developed to address the cFS deployment challenges and to serve as a cFS training platform for new users. It provides a fully functional out-of-the box software system that includes NASA's cFS, Ball Aerospaceâ€"TM"s command and control system COSMOS, and a NASA dynamic simulator called 42. The kit is freely available since all of the components have been released as open source. The kit runs on a Linux platform, includes 8 cFS applications, several kit-specific applications, and built in demos illustrating how to use key application features. It also includes the software necessary to port the cFS to a Raspberry Pi and instructions for configuring COSMOS to communicate with the target. All of the demos and test scripts can be rerun unchanged with the cFS running on the Raspberry Pi. The cFS uses a 3-tiered layered architecture including a platform abstraction layer, a Core Flight Executive (cFE) middle layer, and an application layer. Similar to smart phones, the cFS application layer is the key architectural feature for userâ€"TM"s to extend the FSW functionality to meet their mission-specific requirements. The platform abstraction layer and the cFE layers go a step further than smart phones by providing a platform-agnostic Application Programmer Interface (API) that allows applications to run unchanged on different platforms. OpenSatKit can serve two significant architectural roles that will further help the adoption of the cFS and help create a community of users that can share assets. First, the kit is being enhanced to automate the integration of applications with the goal of creating a virtual cFS 'App Store'. Second, a platform certification test suite can be developed that would allow users to verify the port of the cFS to a new platform. This paper will describe the current state of these efforts and future plans.

McComas, David↗
NASA NTRS2018

Increasing Flight Software Reuse with OpenSatKit

In January 2015 the NASA Goddard Space Flight Center (GSFC) released the Core Flight System (cFS) as open source under the NASA Open Source Agreement (NOSA) license. The cFS is based on flight software (FSW) developed for 12 spacecraft spanning nearly two decades of effort and it can provide about a third of the FSW functionality for a low-earth orbiting scientific spacecraft. The cFS is a FSW framework that is portable, configurable, and extendable using a product line deployment model. However, the components are maintained separately so the user must configure, integrate, and deploy them as a cohesive functional system. This can be very challenging especially for organizations such as universities building cubesats that have minimal experience developing FSW. Supporting universities was one of the primary motivators for releasing the cFS under NOSA. This paper describes the OpenSatKit that was developed to address the cFS deployment challenges and to serve as a cFS training platform for new users. It provides a fully functional out-of-the box software system that includes NASA's cFS, Ball Aerospace's command and control system COSMOS, and a NASA dynamic simulator called 42. The kit is freely available since all of the components have been released as open source. The kit runs on a Linux platform, includes 8 cFS applications, several kit-specific applications, and built in demos illustrating how to use key application features. It also includes the software necessary to port the cFS to a Raspberry Pi and instructions for configuring COSMOS to communicate with the target. All of the demos and test scripts can be rerun unchanged with the cFS running on the Raspberry Pi. The cFS uses a 3-tiered layered architecture including a platform abstraction layer, a Core Flight Executive (cFE) middle layer, and an application layer. Similar to smart phones, the cFS application layer is the key architectural feature for users to extend the FSW functionality to meet their mission-specific requirements. The platform abstraction layer and the cFE layers go a step further than smart phones by providing a platform-agnostic Application Programmer Interface (API) that allows applications to run unchanged on different platforms. OpenSatKit can serve two significant architectural roles that will further help the adoption of the cFS and help create a community of users that can share assets. First, the kit is being enhanced to automate the integration of applications with the goal of creating a virtual cFS "App Store".. Second, a platform certification test suite can be developed that would allow users to verify the port of the cFS to a new platform. This paper will describe the current state of these efforts and future plans.

Computer Programming and Software↗
NASA NTRS2018

Database Tool for Master Console Operators

The Spaceport Command and Control System (SCCS) is the National Aeronautics and Space Administration's (NASA) launch control system for the Orion capsule and Space Launch System, the next generation manned rocket currently in development. This large system requires highly trained and knowledgeable personnel. Master Console Operators (MCO) are currently working on familiarizing themselves with any possible scenario that they may encounter. An intern was recruited to help assist them with creating a tool to use for the process.

Ferrell, Sean↗
NASA NTRS2018

FPGA Reliability and Failure Rate Analysis for Launch and Space Vehicles Environments

Field Programmable Gate Arrays (FPGAs) integrated circuits (IC) are one of the key electronic components in today's sophisticated launch and space vehicle complex avionic systems, largely due to their superb reprogrammable and reconfigurable capabilities combined with relatively low non-recurring engineering costs (NRE) and short design cycle. Consequently, FPGAs are prevalent ICs in communication protocols and control signal commands. This paper will demonstrate guidelines to estimate FPGA failure rates for ascent and in space operations. The guidelines will account for hardware and radiation-induced failures, as well as Bayesian updates to failure rates. The hardware contribution of the approach accounts for physical failures of the FPGA IC. The radiation portion will expand on FPGA susceptibility to different space radiation environments.

Al Hassan, Mohammad↗
NASA NTRS2018

Estimating Software Reliability for Space Launch Vehicles in Probabilistic Risk Assessment (PRA)

It is acutely recognized in the Probabilistic Risk assessment (PRA) field that software plays a defining role in overall system reliability for all modern systems across a wide variety of industries. Regardless if the software is embedded firmware for working components or elements, part of a Human-Machine-Interface, or automated command and control logic, the success of the software to fulfill its function under nominal and off-nominal environments will be a dominant contributor to system reliability. It is also recognized that software reliability prediction and estimation is one of the more challenging and questionable aspects of any PRA or system analyses due to the nature of software and its integration with physics based systems. Irrespective of this dichotomy, any incorporation of software reliability methods requires that the contributions are accountable, quantitative, and tractable. This paper provides a brief overview of software reliability methods, establishes some minimum requirements that the methods should incorporate for completeness, and provides a logic structure for applying software reliability. Model resolution will be discussed that supports current testing plans and trade studies. We will provide initial recommendations for use in the NASA PRA and present a future dynamic option for software and PRA. Space Launch Vehicle Software is recognized to be reliable in static conditions, yet relatively vulnerable to a set of failure modes in changing environments/flight phases. Two quantitative methods were chosen to incorporate software reliability into a Space Launch Vehicle PRA accounting for phase adjustments. One method predicts latent software failure using statistical methods, and the second provides estimates of coding errors and software operating system failures based on test and historical data, respectively. Software uncertainty will also be discussed. We determined that recommendations for PRA software reliability should be modeled at the software module level where multiple software components compose a module and combinations of the software architecture can lead to a functional failure.

Novack, Steven↗
NASA NTRS2018

Estimating Software Reliability for Space Launch Vehicles in Probabilistic Risk Assessment (PRA)

It is acutely recognized in the Probabilistic Risk Assessment (PRA) field that software plays a defining role in overall system reliability for all modern systems across a wide variety of industries. Regardless of whether the software is embedded firmware for working components or elements, part of a Human-Machine-Interface, or automated command and control logic, the success of the software to fulfill its function under nominal and off-nominal environments will be a dominant contributor to system reliability. It is also recognized that software reliability prediction and estimation is one of the more challenging and questionable aspects of any PRA or system analyses due to the nature of software and its integration with physics based systems. Irrespective of this dichotomy, any incorporation of software reliability methods requires that the contributions are accountable, quantitative, and tractable. This paper provides a brief overview of software reliability methods, establishes some minimum requirements that the methods should incorporate for completeness, and provides a logic structure for applying software reliability. Model resolution will be discussed that supports current testing plans and trade studies. We will provide initial recommendations for use in the National Aeronautics and Space Administration (NASA) PRA and present a future dynamic option for software and PRA. Space Launch Vehicle software is recognized to be reliable in static conditions, yet relatively vulnerable to a set of failure modes in changing environments/flight phases. Two quantitative methods were chosen to incorporate software reliability into a Space Launch Vehicle PRA accounting for phase adjustments. One method predicts latent software failure using statistical methods, and the second provides estimates of coding errors and software operating system failures based on test and historical data. Software uncertainty will also be discussed. It is determined that recommendations for PRA software reliability should be modeled at the software module level where multiple software components compose a module and combinations of the software architecture can lead to a functional failure.

Steven D. Novack↗
NASA NTRS2018

Air Traffic Management Technology Demonstration - 3 (ATD-3) Multi-Flight Common Route (MFCR) Concept of Operations Version 1.0

NASA's Multi Flight Common Route (MFCR) automation represents one element of those technologies focusing primarily on delay recovery in the en route phase of flight. Delay recovery is an attenuation of flight-time delay, accomplished by periodically revising weather-avoidance routing as the convective weather system evolves. MFCR is intended for use by Traffic Management Coordinators (TMCs) in Air Route Traffic Control Centers (ARTCCs, or Centers) and traffic management specialists (TMSs) in the Air Traffic Control System Command Center (ATCSCC). MFCR leverages existing weather, airspace, and traffic data, as well as improvements in navigation, surveillance, communication, and digital information technologies, to build on existing ATM automation and address some of the shortcomings associated with strategic traffic flow management initiatives and weather forecasting uncertainties. These capabilities provide significant potential benefits in the form of time, fuel, and cost savings. The concept of operations described in this document describes MFCR functionality as delivered by NASA to the FAA in December 2017, including a list of potential enhancements that may be realized when the system is fielded.

conops↗
NASA NTRS2018

Development of an Optical Slice for an RF and Optical Software Defined Radio

A key component in the Integrated Radio and Optical Communications project at the National Aeronautics and Space Administration's (NASA) Glenn Research Center (GRC) is the radio frequency (RF) and optical software defined radio (SDR). A NASA RF SDR might consist of a general purpose processor to run the Space Telecommunications Radio System (STRS) Architecture for radio command and control, a reconfigurable signal processing device such as a field programmable gate array (FPGA) which houses the waveform, and a digital to analog converter for (DAC) transmitting data. Prior to development, SDR architecture trades on how to combine the RF and optical elements were studied. A modular architecture with physically separate RF and optical hardware slices was chosen and the optical slice of an SDR was designed and developed. The Harris AppSTAR("TM") platform, which consists of an FPGA processing platform with a mezzanine card targeted for RF communications, was used as the base platform in prototyping the optical slice. A serially concatenated pulse position modulation (SCPPM) optical waveform was developed. The waveform follows the standard described in the Consultative Committee for Space Data Systems (CCSDS) Optical Communions Coding and Synchronization Red Book. A custom optical mezzanine printed circuit board card was developed at NASA GRC for optical transmission. The optical mezzanine card replaces the DAC, which is used in the transmission of RF signals. This paper describes RF and optical SDR architecture trades, the Harris AppSTAR("TM") platform, the design of the SCPPM waveform, and the development of the optical mezzanine card.

optical communications↗
NASA NTRS2018

Assessing C2 Communications for UAS Traffic Management

The National Aeronautics and Space Administration's (NASA) Unmanned Aircraft Systems (UAS) Traffic Management (UTM) project works to develop tools and technologies essential for safely enabling civilian low-altitude UAS operations. Currently there is no established infrastructure to enable and safely manage the widespread use of low-altitude airspace and UAS operations, regardless of the type of UAS. The UTM technical challenge will develop comprehensive and validated airspace operations and integration requirements to safely enable large-scale persistent access to visual line of sight and autonomous beyond visual line of sight small UAS in low-altitude airspace. Within the UTM project, a number of communications technologies to support UTM command and control (C2) are under investigation. In particular, commercial networked cellular systems are being tested and assessed for their ability to meet the reliability, scalability, cybersecurity and redundancy required. NASA Glenn Research Center is studying some of the aspects of employing such networks for UTM C2 communications. This includes the development of a test platform for sensing and characterizing the airborne C2 communications environment at various altitudes and in various terrains and topologies, measuring such aspects as received signal strength and interference. System performance aspects such as latency in the link, handover performance, packet error loss rate, drop outs, coverage gaps and other aspects impacting UTM operation will also be assessed. In this paper we explore some of the C2 approaches being proposed and demonstrated in the UTM project, the reliability, availability and other general C2 performance requirements, and approaches to evaluating and analyzing UTM C2 links based on commercial cellular networks.

air traffic control↗
NASA NTRS2018

Phased Array Antenna for the Mitigation of UAS Interference

The growing demand for Unmanned Aerial Systems (UAS) operating beyond the line of sight (BLOS) has resulted in an increased interest in using existing commercial satellite communication capabilities for UAS command and control (C2) communications. The World Radiocommunication Conference in 2015 designated portions of Ku-Band and Ka-Band fixed satellite service (FSS) spectrum to support UAS C2 communications, provided that potential interference with existing co-allocated users in these bands is addressed. As the user base in this new spectrum allocation expands, there is an increased potential for interference with existing terrestrial communication systems operating under fixed service (FS) allocations. The portion of Ka-Band spectrum allocated for UAS C2 avoids significant interference issues, but the Ku-Band allocation contains a co-primary FS allocation, creating potential interference problems. Therefore, UAS must identify solutions to avoid interfering with these existing FS ground sites while maintaining good links with satellite constellations. UAS operating with conventional fixed feed parabolic antennas will have difficulty in meeting interference thresholds, especially at high latitudes where the antennas will operate with low elevation angles. As a means of addressing this limitation, NASA is investigating the use of a phased array antenna to enable mitigation of interference into ground-based FS receivers. In this paper, a novel lightweight conformal phased array antenna will be presented that can use null-steering and/or beam shaping to avoid ground interference while simultaneously providing strong satellite microwave links for communications. The reduced weight of this design and ability to integrate into the fuselage of smaller UAS platforms will also be discussed as a potential solution to provide BLOS operation via spectrum sharing for an expanding user base. This paper will review design aspects of the conformal phased array antenna, describe the intended benefits in reducing interference with FS ground stations, and describe phased array development and test plans.

Phased Array↗
NASA NTRS2018

Development of an Optical Slice for an RF and Optical Software Defined Radio

A key component in the Integrated Radio and Optical Communications project at the National Aeronautics and Space Administration's (NASA) Glenn Research Center (GRC) is the radio frequency (RF) and optical software defined radio (SDR). A NASA RF SDR might consist of a general purpose processor to run the Space Telecommunications Radio System (STRS) Architecture for radio command and control, a reconfigurable signal processing device such as a field programmable gate array (FPGA) which houses the waveform, and a digital to analog converter (DAC) for transmitting data. Prior to development, SDR architecture trades on how to combine the RF and optical elements were studied. A modular architecture with physically separate RF and optical hardware slices was chosen and the optical slice of an SDR was designed and developed. The Harris AppSTARTM platform, which consists of an FPGA processing platform with a mezzanine card targeted for RF communications, was used as the base platform in prototyping the optical slice. A serially concatenated pulse position modulation (SCPPM) optical waveform was developed. The waveform follows the standard described in the Consultative Committee for Space Data Systems (CCSDS) Optical Communications Coding and Synchronization Red Book. A custom optical mezzanine printed circuit board card was developed at NASA GRC for optical transmission. The optical mezzanine card replaces the DAC, which is used in the transmission of RF signals. This paper describes RF and optical SDR architecture trades, the Harris AppSTAR platform, the design of the SCPPM waveform, and the development of the optical mezzanine card.

Nappier, Jennifer M.↗
NASA NTRS2018

Assessing C2 Communications

The National Aeronautics and Space Administration's (NASA) Unmanned Aircraft Systems (UAS) Traffic Management (UTM) project works to develop tools and technologies essential for safely enabling civilian low-altitude UAS operations. Currently there is no established infrastructure to enable and safely manage the widespread use of low-altitude airspace and UAS operations, regardless of the type of UAS. The UTM technical challenge will develop comprehensive and validated airspace operations and integration requirements to safely enable large-scale persistent access to visual line of sight and autonomous beyond visual line of sight small UAS in low-altitude airspace. Within the UTM project, a number of communications technologies to support UTM command and control (C2) are under investigation. In particular, commercial networked cellular systems are being tested and assessed for their ability to meet the reliability, scalability, cybersecurity and redundancy required. NASA Glenn Research Center is studying some of the aspects of employing such networks for UTM C2 communications. This includes the development of a test platform for sensing and characterizing the airborne C2 communications environment at various altitudes and in various terrains and topologies, measuring such aspects as received signal strength and interference. System performance aspects such as latency in the link, handover performance, packet error loss rate, drop outs, coverage gaps and other aspects impacting UTM operation will also be assessed. In this paper we explore some of the C2 approaches being proposed and demonstrated in the UTM project, the reliability, availability and other general C2 performance requirements, and approaches to evaluating and analyzing UTM C2 links based on commercial cellular networks.

aircraft communications↗