Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Avionics”

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 649 records · Page 36

Adapting the Reconfigurable SpaceCube Processing System for Multiple Mission Applications

This paper will detail the use of SpaceCube in multiple space flight applications including the Hubble Space Telescope Servicing Mission 4 (HST-SM4), an International Space Station (ISS) radiation test bed experiment, and the main avionics subsystem for two separate ISS attached payloads. Each mission has had varying degrees of data processing complexities, performance requirements, and external interfaces. We will show the methodology used to minimize the changes required to the physical hardware, FPGA designs, embedded software interfaces, and testing.This paper will summarize significant results as they apply to each mission application. In the HST-SM4 application we utilized the FPGA resources to accelerate portions of the image processing algorithms more than 25 times faster than a standard space processor in order to meet computational speed requirements. For the ISS radiation on-orbit demonstration, the main goal is to show that we can rely on the commercial FPGAs and processors in a space environment. We describe our FPGA and processor radiation mitigation strategies that have resulted in our eight PowerPCs being available and error free for more than 99.99 of the time over the period of four years. This positive data and proven reliability of the SpaceCube on ISS resulted in the Department of Defense (DoD) selecting SpaceCube, which is replacing an older and slower computer currently used on ISS, as the main avionics for two upcoming ISS experiment campaigns. This paper will show how we quickly reconfigured the SpaceCube system to meet the more stringent reliability requirements

SpaceCube↗

Ethernet for Aerospace Applications - Ethernet Heads for the Skies

One of the goals of aerospace applications is to reduce the cost and complexity of avionic systems. Ethernet is a highly scalable, flexible, and popular protocol. The aerospace market is large, with a forecasted production of over 50,000 turbine-powered aircraft valued at $1.7 trillion between 2012 and 2022. Boeing estimates demand for commercial aircraft by 2033 to total over 36,000 with a value of over $5 trillion. In 2014 US airlines served over 750 million passengers and this is growing over 2% yearly. Electronic fly-by-wire is now used for all airliners and high performance aircraft. Although Ethernet has been widely used for four decades, its use in aerospace applications is just beginning to become common. Ethernet is the universal solution in commercial networks because of its high bandwidths, lower cost, openness, reliability, maintainability, flexibility, and interoperability. However, when Ethernet was designed applications with time-critical, safety relevant and deterministic requirements were not given much consideration. Many aerospace applications use a variety of communication architectures that add cost and complexity. Some of them are SpaceWire, MIL-STD-1553, Avionics Full Duplex Switched Ethernet (AFDX), and Time-Triggered Ethernet (TTE). Aerospace network designers desire to decrease the number of networks to reduce cost and effort while improving scalability, flexibility, openness, maintainability, and reliability. AFDX and TTE are being considered more for critical aerospace systems because they provide redundancy, failover protection, guaranteed timing, and frame priority and are based on Ethernet IEEE 802.3. This paper explores the use of AFDX and TTE for aerospace applications.

Ethernet↗

Adapting the SpaceCube v2.0 Data Processing System for Mission-Unique Application Requirements

The SpaceCubeTM v2.0 system is a superior high performance, reconfigurable, hybrid data processing system that can be used in a multitude of applications including those that require a radiation hardened and reliable solution. This paper provides an overview of the design architecture, flexibility, and the advantages of the modular SpaceCube v2.0 high performance data processing system for space applications. The current state of the proven SpaceCube technology is based on nine years of engineering and operations. Five systems have been successfully operated in space starting in 2008 with four more to be delivered for launch vehicle integration in 2015. The SpaceCube v2.0 system is also baselined as the avionics solution for five additional flight projects and is always a top consideration as the core avionics for new instruments or spacecraft control. This paper will highlight how this multipurpose system is currently being used to solve design challenges of three independent applications. The SpaceCube hardware adapts to new system requirements by allowing for application-unique interface cards that are utilized by reconfiguring the underlying programmable elements on the core processor card. We will show how this system is being used to improve on a heritage NASA GPS technology, enable a cutting-edge LiDAR instrument, and serve as a typical command and data handling (CDH) computer for a space robotics technology demonstration.

Xilinx FPGA↗

SpaceVPX Interoperability Assessment

The existing VMEbus (VersaModular Eurocard bus) International Trade Association (VITA)-78 industry standard, also known as SpaceVPX, is an avionics board- and chassis-level standard derived from the OpenVPX standard as defined in VITA-65. While VITA-65 defines backplane and board-level profiles from COTS vendors to ensure interoperability of products used in developing systems and subsystems, the VITA-78 standard defines SpaceVPX to incorporate fault tolerance features that are required by many spaceflight systems. However, VITA-78 allows so much flexibility that interoperability between modules cannot be assured. This assessment provides guidelines on the use of, and extensions to, the VITA-78 standard to enable avionics interoperability for future NASA missions. The assessment team was comprised of subject matter experts (SMEs) from Goddard Space Flight Center (GSFC), the Jet Propulsion Laboratory (JPL), Johnson Space Center (JSC), and Langley Research Center (LaRC). The team included valuable external consulting support from a SME who was a key participant in the development of the VITA-78 standard. The team had extensive collaboration with the NASA Space Technology Mission Directorate (STMD) High Performance Spaceflight Computing (HPSC) project, specifically in the development of SpaceVPX interconnect findings, observations, and NESC recommendations. To provide an understanding of the breadth of implementations that SpaceVPX must accommodate, multiple NASA use cases were analyzed to assess the requirements for SpaceVPX implementations across a wide range of NASA missions (Appendix C). Applications included crewed missions, science missions, and orbital and surface robotic systems. Product surveys were conducted to assess the level of industry support for SpaceVPX, applications, and the variations in their implementations (Appendix D). In-depth analysis was conducted in the areas of: (a) power management and distribution, (b) form factors and daughtercards, (c) interconnect, and (d) fault tolerance. Leveraging the use cases, product surveys, and SMEs from multiple NASA Centers, these areas were analyzed to determine the range of implementations permitted by the VITA-78 standard and potential interoperability issues. Applicable findings and NESC recommendations were provided for each area. During this assessment, there were multiple opportunities to engage with other agencies to learn about their interest in SpaceVPX, their strategies for implementing SpaceVPX-based systems, and their internal development efforts. These engagements also generated findings and NESC recommendations. Based on this assessment analysis, NESC recommendations were made regarding the feature set and module profiles to support NASA SpaceVPX implementations. This feature set includes restrictions on features in VITA-78, and extensions to the standard. Key recommendations in this area include the use of 10 Gigabit Ethernet and Peripheral Component Interconnect Express (PCIe) as high bandwidth interconnect on the backplane, the retention of SpaceWire interconnect for control functions, and support for 3U (unit) and 6U, form factors for NASA systems. Restrictions were proposed on the usage of user-defined signals to promote interoperability, and specific power managements and distribution schemes for 3U systems. Beyond the technical implementation of SpaceVPX, recommendations were made on areas that warrant further investigation. Primary among these is the recommendation for NASA to collaborate with other space-going agencies and industry to incorporate recommendations into a future ‘dot spec’ of VITA-78. This would ensure wide adoption and availability of the modules that comply with the specification. The assessment includes appendices with candidate module profiles that can be considered as a starting point for this activity, and example systems based on the recommendations. Follow-on studies are recommended for architectures beyond SpaceVPX to address potential enhancements including condensed set of interconnect, software required to implement protocol layers on the interconnect (and other features), alternative power architectures, and system-level testability.

SpaceVPX↗

Advanced Software Techniques for Data Management Systems. Volume 2: Space Shuttle Flight Executive System: Functional Design

A functional design of software executive system for the space shuttle avionics computer is presented. Three primary functions of the executive are emphasized in the design: task management, I/O management, and configuration management. The executive system organization is based on the applications software and configuration requirements established during the Phase B definition of the Space Shuttle program. Although the primary features of the executive system architecture were derived from Phase B requirements, it was specified for implementation with the IBM 4 Pi EP aerospace computer and is expected to be incorporated into a breadboard data management computer system at NASA Manned Spacecraft Center's Information system division. The executive system was structured for internal operation on the IBM 4 Pi EP system with its external configuration and applications software assumed to the characteristic of the centralized quad-redundant avionics systems defined in Phase B.

Pepe, J. T.↗

Development of STOLAND, a versatile navigation, guidance and control system

STOLAND has been developed to perform navigation, guidance, control, and flight management experiments in advanced V/STOL aircraft. The experiments have broad requirements and have dictated that STOLAND be capable of providing performance that would be realistic and equivalent to a wide range of current and future avionics systems. An integrated digital concept using modern avionics components was selected as the simplest approach to maximizing versatility and growth potential. Unique flexibility has been obtained by use of a single, general-purpose digital computer for all navigation, guidance, control, and displays computation.

Young, L. S.↗

Expendable Second Stage Reusable Space Shuttle Booster. Volume 10: Technology Requirements

Technology requirements for the expendable second stage of the space shuttle booster system are discussed. The primary objective of the expendable second stage (ESS) program is to define a low-cost system for placing large payloads, such as the space station or reusable nuclear shuttle, into low earth orbit. The proposed concept is to utilize a modified Saturn 5 second stage (S-2) in conjunction with the space shuttle reusable booster. The ESS retains the major S-2 structure, modified for attachment to the space shuttle booster, and incorporates both Saturn and shuttle developed propulsion and avionics hardware. No major technology breakthroughs are required to develop this ESS system. Technology application and implementation efforts in selected areas, however, should be conducted in support of the ESS detail design and development phase. The selected ESS system incorporates recovery of propulsion and avionics hardware by the shuttle orbiter for ESS reuse to minimize cost.

Source record↗

Effectiveness evaluation of STOL transport operations (phase 2)

A computer simulation program which models a commercial short-haul aircraft operating in the civil air system was developed. The purpose of the program is to evaluate the effect of a given aircraft avionics capability on the ability of the aircraft to perform on-time carrier operations. The program outputs consist primarily of those quantities which can be used to determine direct operating costs. These include: (1) schedule reliability or delays, (2) repairs/replacements, (3) fuel consumption, and (4) cancellations. More comprehensive models of the terminal area environment were added and a simulation of an existing airline operation was conducted to obtain a form of model verification. The capability of the program to provide comparative results (sensitivity analysis) was then demonstrated by modifying the aircraft avionics capability for additional computer simulations.

Welp, D. W.↗

Description and flight performance of two systems for two-segment approach

This paper describes two different avionic systems which were designed and developed to provide guidance and control for two-segment noise abatement approaches. The concept of a low-cost retrofit avionic system evolved into a special-purpose two-segment computer which required a DME collocated with the ILS glide-slope transmitter. This system was evaluated in a Boeing 727-200 aircraft. The second system is an area navigation (RNAV) system modified to include the two-segment approach. This system is more sophisticated than the first system and does not restrict usage to any specific navigation ground aid. The modified RNAV system is a Collins ANS-70A and is currently being evaluated in a DC-8-61 aircraft.

Wehrend, W. R.↗

Fuel conservation capability and effort by commercial air carriers

Computer capability weather input data, performance data, and ATC interface are discussed in terms of their role in preflight and inflight planning for commercial flights. The effect of preflight and inflight planning on fuel efficient operation was evaluated along with the impact of avionics. It was found that there is a potential for saving fuel through use of avionics, especially in the area of vertical guidance in all phases of flight. Other results of the study indicate: (1) preflight planning as it now stands is adequate with the exception that more accurate and up-to-date weather information is desirable; (2) better inflight information about existing weather conditions is needed; and (3) ATC can aid in fuel conservation.

Source record↗

The 4D area navigation system description and flight test results

A 4D area navigation system was designed to guide aircraft along a prespecified flight path (reference path) such that the aircraft would arrive at the approach gate at a time specified by the ATC controller. Key components to achieve this requirement were: (1) stored reference trajectories; (2) a continuously recomputed capture trajectory to a selected waypoint on the reference trajectory so as to achieve the desired time of arrival; (3) electronic situation displays; and (4) a control system to follow the overall trajectory in space and time. The system was implemented in a digital integrated avionics system (STOLAND) installed on a CV-340 airplane. Although the 4D system was designed primarily for automatic operation, it was flight tested in a flight director mode (the pilot follows the flight director commands), because the CV-340 autopilot servos were not tied to the avionics system. The flight test showed that, even in the flight director mode, the pilot did achieve the objectives of path tracking and time of arrival control with only moderate workload. The system also permitted controlled delay of the time of arrival by path stretching, which takes advantage of the continuously changing capture trajectory to predict the time of arrival. Simulations in the automatic and manual modes were used to complement the flight data.

Lee, H. Q.↗

The shuttle orbiter cabin atmospheric revitalization systems

The Orbiter Atmospheric Revitalization Subsystem (ARS) and Pressure Control Subsystem (ARPCS) are designed to provide the flight crew and passengers with a pressurized environment that is both life-supporting and within crew comfort limitations. The ARPCS is a two-gas (oxygen-nitrogen) system that obtains oxygen from the Power Reactant Supply and Distribution (PRSD) subsystem and nitrogen from the nitrogen storage tanks. The ARS includes the water coolant loop; cabin CO2, odor, humidity and temperature control; and avionics cooling. Baseline ARPCS and ARS changes since 1973 include removal of the sublimator from the water coolant loop, an increase in flowrates to accommodate increased loads, elimination of the avionics bay isolation from the cabin, a decision to have an inert vehicle during ferry flight, elimination of coldwall tubing around windows and hatches, and deletion of the cabin heater.

Ward, C. F.↗

Forecast of the general aviation air traffic control environment for the 1980's

The critical information required for the design of a reliable, low cost, advanced avionics system which would enhance the safety and utility of general aviation is stipulated. Sufficient data is accumulated upon which industry can base the design of a reasonably priced system having the capability required by general aviation in and beyond the 1980's. The key features of the Air Traffic Control (ATC) system are: a discrete address beacon system, a separation assurance system, area navigation, a microwave landing system, upgraded ATC automation, airport surface traffic control, a wake vortex avoidance system, flight service stations, and aeronautical satellites. The critical parameters that are necessary for component design are identified. The four primary functions of ATC (control, surveillance, navigation, and communication) and their impact on the onboard avionics system design are assessed.

Hoffman, W. C.↗

Space Shuttle Program Progress Report

A status report is presented on progress in the design, manufacturing and testing of components of the space transportation system (STS), and primarily the Space Shuttle vehicles. Project landmarks from 1969 to 1981 are indicated, fabrication of the Shuttle Orbiter and rollout of the first prototype are described, fabrication and assembly of some Orbiter parts are sketched, and some of the subsystems (thermal protection, avionics, maneuvering aids, reaction control, remote manipulator) are described. Also discussed are: Orbiter carrier aircraft, Shuttle main engine and tests, external fuel tank, solid rocket booster, launch and landing facilities. A separate section is devoted to ground tests (vibration, propulsion, electronics, avionics integration), trainers and simulators, and flight tests (captive flight, free flight, landing and approach, orbital flight).

Thompson, R. F.↗

Approach and landing simulation

Computer program integrates avionics research in navigation, guidance, controls, and displays with realistic aircraft model. Program gives researchers capability of evaluating avionics area independently from other research areas and thus allows more flexibility in time schedules. Program comprises many independent modules that represent specific hardware onboard actual aircraft.

Ostroff, A. J.↗

Airborne navigation system performance during RNAV/MLS transition

Aircraft position error sensitivity to sensor errors and flight path geometry is analyzed during RNAV/MLS transition using a digital computer simulation. The avionics sensitivity data provides information necessary to establish requirements for additional guidance law design and to establish airspace requirements for maneuvering to null out any residual RNAV errors upon MLS transition. The data base is also beneficial as planning information for subsequent flight testing. The parameters varied during the generation of the data base include flight profile, error source content and magnitude, ground facility location, runway/flight path orientation and navigation mode. The avionics, autopilots and aircraft dynamics correspond to the existing NASA Terminal Configured Vehicle. Significant transients were observed during MLS transition, primarily in the vertical channel. These transients have a significant impact on airspace requirements and operational procedures in the RNAV/MLS environment.

Heine, W.↗

Implementation of an optimum profile guidance system on STOLAND

The implementation on the STOLAND airborne digital computer of an optimum profile guidance system for the augmentor wing jet STOL research aircraft is described. Major tasks were to implement the guidance and control logic to airborne computer software and to integrate the module with the existing STOLAND navigation, display, and autopilot routines. The optimum profile guidance system comprises an algorithm for synthesizing mimimum fuel trajectories for a wide range of starting positions in the terminal area and a control law for flying the aircraft automatically along the trajectory. The avionics software developed is described along with a FORTRAN program that was constructed to reflect the modular nature and algorthms implemented in the avionics software.

Flanagan, P. F.↗

Shuttle payload S-band communications study

The work to identify, evaluate, and make recommendations concerning the functions and interfaces of those orbiter avionic subsystems which are dedicated to, or play some part in, handling communication signals (telemetry and command) to/from payloads (spacecraft) that will be carried into orbit by the shuttle is reported. Some principal directions of the research are: (1) analysis of the ability of the various avionic equipment to interface with and appropriately process payload signals; (2) development of criteria which will foster equipment compatibility with diverse types of payloads and signals; (3) study of operational procedures, especially those affecting signal acquisition; (4) trade-off analysis for end-to-end data link performance optimization; (5) identification of possible hardware design weakness which might degrade signal processing performance.

Springett, J. C.↗