Search NASA⌕ Search

SEARCH · Search NASA

Results for “Space 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 127 records · Page 7

NASA GSFC Avionics Architectures and Future Directions

NASA Goddard Spaceflight Center (GSFC) employs standard avionics hardware and software architectures. Hardware architectures include GMSA (Goddard Modular Smallsat Architecture), MUSTANG (Modular Unified Space Technology Avionics for Next Generation), SpaceCube. The spaceflight software architecture is based on cFS (Core Flight System). Future driving requirements for avionics architectures include increase sensor data rates, increased onboard processing, autonomous applications, and distributed space missions. Architectural concepts that can meet these requirements include the use of the High Performance Spaceflight Computing (HPSC) Chiplet, employing hybrid computing architectures, and increasing network bandwidths.

architectures↗

Kedalion: NASA's Adaptable and Agile Hardware/Software Integration and Test Lab

NASA fs Kedalion engineering analysis lab at Johnson Space Center is on the forefront of validating and using many contemporary avionics hardware/software development and integration techniques, which represent new paradigms to heritage NASA culture. Kedalion has validated many of the Orion hardware/software engineering techniques borrowed from the adjacent commercial aircraft avionics solution space, with the intention to build upon such techniques to better align with today fs aerospace market. Using agile techniques, commercial products, early rapid prototyping, in-house expertise and tools, and customer collaboration, Kedalion has demonstrated that cost effective contemporary paradigms hold the promise to serve future NASA endeavors within a diverse range of system domains. Kedalion provides a readily adaptable solution for medium/large scale integration projects. The Kedalion lab is currently serving as an in-line resource for the project and the Multipurpose Crew Vehicle (MPCV) program.

Mangieri, Mark L.↗

Vehicle health management technology needs

Background material on vehicle health management (VHM) and health monitoring/control is presented. VHM benefits are described and a list of VHM technology needs that should be pursued is presented. The NASA funding process as it impacts VHM technology funding is touched upon, and the VHM architecture guidelines for generic launch vehicles are described. An example of a good VHM architecture, design, and operational philosophy as it was conceptualized for the National Launch System program is presented. Consideration is given to the Strategic Avionics Technology Working Group's role in VHM, earth-to-orbit, and space vehicle avionics technology development considerations, and some actual examples of VHM benefits for checkout are given.

Hammond, Walter E.↗

Update of the Development of a Low Cost Data Acquisition System for the Space Shuttle Solid Rocket Booster Program

The space shuttle solid rocket boosters (SRBs) experience a severe environment during their brief flight. During the last few years several SRB's have sustained noticeable structural damage. The environmental characteristics (vibration, structure, and thermal) encountered by the SRB's during ascent, descent and water impact are in most cases unknown. A developmental flight instrumentation (DFI) system collected data from the SRBs' first four flights in the early 1980's, and after the first three flights during the shuttle return-to-flight phase after the Challenger accident. However, the DFI data collected are of low fidelity and do not correlate well with cases of observed structural damage. The DFI system was evaluated for reuse, but the cost to fly it was prohibitive. The space shuttle is presently scheduled to fly until 2030. To support the shuttle flight schedule, avionics on the SRB's will be upgraded. The environments on the different sections of the SRB will need to be defined more completely to properly qualify the avionics for multiple flights. The DFI data previously gathered do not provide enough information to properly qualify the avionics. Marshall Space Flight Center's (MSFC) SRB Project Office requested the Science and Engineering (S&E) Directorate to develop a stand-alone data acquisition system that could collect data from any area of the booster. In answer to this requirement, S&E developed the Enhanced Data Acquisition System (EDAS). To minimize development time and cost, the development team used state-of-the-art commercial off the shelf (COTS) equipment. The first two flights of this system occurred on shuttle mission STS-91 in June 1998 and STS-95 in October 1998. Twenty-one measurements were successfully recorded on the STS-91 right hand booster, providing new accelerometer, strain, temperature, and heating rate data to analysts. Twenty-four measurements were successfully recorded on the STS-95 left hand booster, providing data from the booster and the external tank. This paper summarizes the effort to develop, test, qualify and fly the EDAS to meet SRB flight and data collection requirements.

Crawford, Kevin↗

Using a Commerical off the Shelf Data Acquisition System for the Space Shuttle Solid Rocket Booster Program

The space shuttle solid rocket boosters (SRBs) experience a severe environment during their brief flight. During the last few years several SRB's have sustained noticeable structural damage. The environmental characteristics (vibration, structure, and thermal) encountered by the SRB's during ascent, descent and water impact are in most cases unknown. A developmental flight instrumentation (DFI) system collected data from the SRBs' first four flights in the early 1980's, and after the first three flights during the shuttle return-to-flight phase after the Challenger accident. However, the DFI data collected are of low fidelity and do not correlate well with cases of observed structural damage. The DFI system was evaluated for reuse, but the cost to fly it was prohibitive. The space shuttle is presently scheduled to fly until 2030. To support the shuttle flight schedule, avionics on the SRB's will be upgraded. The environments on the different sections of the SRB will need to be defined more completely to properly qualify the avionics for multiple flights. The DFI data previously gathered do not provide enough information to properly qualify the avionics. Marshall Space Flight Center's (MSFC) SRB Project Office requested the Science and Engineering (S&E) Directorate to develop a stand-alone data acquisition system that could collect data from any area of the booster. In answer to this requirement, S&E developed the Enhanced Data Acquisition System (EDAS). To minimize development time and cost, the development team used state-of-the-art commercial off the shelf (COTS) equipment. The first two flights of this system occurred on shuttle mission STS-91 in June 1998 and STS-95 in October 1998. Twenty-one measurements were successfully recorded on the STS-91 right hand booster, providing new accelerometer, strain, temperature, and heating rate data to analysts. Twenty-four measurements were successfully recorded on the STS-95 left hand booster, providing data from the booster and the external tank. This paper summarizes the effort to develop, test, qualify and fly the EDAS to meet SRB flight and data collection requirements.

Crawford, Kevin↗

Space shuttle main engine definition (phase B). Volume 2: Avionics

The advent of the space shuttle engine with its requirements for high specific impulse, long life, and low cost have dictated a combustion cycle and a closed loop control system to allow the engine components to run close to operating limits. These performance requirements, combined with the necessity for low operational costs, have placed new demands on rocket engine control, system checkout, and diagnosis technology. Based on considerations of precision environment, and compatibility with vehicle interface commands, an electronic control, makes available many functions that logically provide the information required for engine system checkout and diagnosis.

Source record↗

Simulation/Emulation Techniques: Compressing Schedules With Parallel (HW/SW) Development

NASA has always been in the business of balancing new technologies and techniques to achieve human space travel objectives. NASA's Kedalion engineering analysis lab has been validating and using many contemporary avionics HW/SW development and integration techniques, which represent new paradigms to NASA's heritage culture. Kedalion has validated many of the Orion HW/SW engineering techniques borrowed from the adjacent commercial aircraft avionics solution space, inserting new techniques and skills into the Multi - Purpose Crew Vehicle (MPCV) Orion program. Using contemporary agile techniques, Commercial-off-the-shelf (COTS) products, early rapid prototyping, in-house expertise and tools, and extensive use of simulators and emulators, NASA has achieved cost effective paradigms that are currently serving the Orion program effectively. Elements of long lead custom hardware on the Orion program have necessitated early use of simulators and emulators in advance of deliverable hardware to achieve parallel design and development on a compressed schedule.

Mangieri, Mark L.↗

Payload deployment systems and advanced manipulators

The results of discussions on future development of avionics to support payload deployment systems and advanced manipulators are discussed. The discussions summarized here were held during the Space Transportation Avionics Technology Symposium in Williamsburg, Virginia on November 7 to 9, 1989. Symposium participants agreed that this subpanel would have benefitted from more participation by users. It was suggested that inputs from Shuttle payload users should be incorporated, either by direct discussions with users or by incorporating comments from users as kept by Payload Accommodations. The Jet Propulsion Laboratory (JPL), Goddard, and Langley, as builders of payloads, and the Space Station Utilization Office could also provide useful inputs. Other potential users for future systems should also be identified as early as possible to determine what they anticipate their needs to be. Symposium participants also recognized that payload deployment is normally not a safety critical area, and as such, is vulnerable to budget cuts that defer costs from development to operations. This does give opportunities for upgrades of operational systems, but these must be very cost effective to compete with vehicle requirements that enhance safety or increase lifetime.

Source record↗

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↗

1998 Digital Avionics Highlights

This article summarizes the highlights of recent events and developments in digital avionics in space, aircraft, and weapons. The article is about 1,200 words long. Information for the article was collected from members of the Digital Avionics Technical Committee of the American Institute of Aeronautics and Astronautics. This information was previously cleared by the members' parent organization. Information for the article was also gathered from Aviation Week and Space Technology and similar sources.

Polites, Michael E.↗

The NASA Radiation Hardness Assurance (RHA) Process Standard

This paper presents status on the upcoming NASA Agency-level RHA Process Standard. Based on recommendations provided by the NASA Engineering and Safety Center (NESC), the NASA Electronic Parts and Packaging (NEPP) Program has led development of an agency-level standard for space flight avionics and electronics RHA. The standard introduces a novel RHA taxonomy and prescribes the process required by NASA programs and projects to baseline their RHA programs consistent with the MEAL (Mission, Environment, Application, and Lifetime) criteria including the risk tolerance posture. The standard also provides requirements for the RHA schedule integration in the program or project lifecycle and requirements for data deliverables content. Additional non-prescriptive technical content is provided in the standard appendices to guide development of RHA programs for NASA missions.

Avionics↗

Flight elements: Advanced avionics systems architectures

Space transportation objectives are associated with transporting material from Earth to orbit, interplanetary travel, and planetary landing. The objectives considered herein are associated with Earth to orbit transportation. Many good avionics architectural features will support all phases of space transportation, but interplanetary transportation poses significantly different problems such as long mission time with high reliability, unattended operation, and many different opportunities such as long nonoperational flight segments that can be used for equipment fault diagnosis and repair. Fault tolerance can be used to permit continued operation with faulty units, not only during launch but also, and perhaps with more impact, during prelaunch activities. Avionics systems are entering a phase of development where the traditional approaches to satisfactory systems based on engineering judgement and thorough testing will alone no longer be adequate to assure that the required system performance can be obtained. A deeper understanding will be required to make the effects of obscure design decisions clear at a level where their impact can be properly judged.

Source record↗

Redundant Strapdown Laser Gyro Navigation System

For the last several years, NASA has pursued the development of low-cost high-reliability inertial navigation systems that would satisfy a broad spectrum of future space and avionics missions. Two specific programs have culminated in the construction of a Redundant Strapdown Laser Gyro Navigation System. These two programs were for development of a space ultrareliable modular computer (SUMC) and a redundant laser gyro inertial measurement unit (IMU). The SUMC is a digital computer that employs state-of-the-art large-scale integrated circuits configured in a functional modular breakdown. The redundant laser gyro IMU is a six-pack strapdown sensor package in a dodecahedron configuration which uses six laser gyros to provide incremental angular positions and six accelerometers for linear velocity outputs. The sensor arrangement allows automatic accommodation of two failures; a third failure can be tolerated provided it can be determined. The navigation system also includes redundant power supplies, built-in test-equipment (BITE) circuits for failure detection, and software which provides for navigation, redundancy management, and automatic calibration and alignment.

Mcpherson, B. W.↗

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.↗

Payload accommodations. Satellite servicing support

The proposed technology studies discussed at the Space Transportation Avionics Symposium in Williamsburg, VA on 7 to 9 November 1989, are discussed. The discussions and findings of the Payload Accommodations Subpanel are also summarized. The major objective of the proposed focused technology development is to develop and demonstrate (ground and flight) autonomous rendezvous, proximity operations, and docking/berthing capabilities to support satellite servicing. It is expected that autonomous rendezvous and docking (AR and D) capabilities will benefit both the users (e.g., satellite developers and operators) and the transportation system developers and operators. AR and D will provide increased availability of rendezvous and docking services by reducing the operational constraints associated with current capabilities. These constraints include specific lighting conditions, continuous space-to-ground communications, and lengthy ground tracking periods. AR and D will provide increased cost efficiency with the potential for reduced propellant expenditures and workloads (flight and/or ground crews). The AR and D operations will be more consistent, allowing more flexibility in the design of the satellite control system and docking/berthing mechanisms.

Lee, Roscoe↗

Development of a Low Cost Data Acquisition System for the Solid Rocket Booster Program

The Space Transportation System's (STS) Solid Rocket Boosters (SRBs) experience a severe environment during their brief flight. During the last few years several SRB's have sustained noticeable structural damage. The environmental characteristics (vibration, structure, and thermal) encountered by the SRB's during ascent, descent and water impact are in most cases unknown. A developmental flight instrumentation (DFI) system collected data from the SRB's first four flights in the early 1980's, and after the first three flights during the shuttle return-to-flight phase after the Challenger accident. However, the DFI data collected are of low fidelity and do not correlate well with the observed structural damage. The DFI system was evaluated for reuse, but the cost to fly it was prohibitive. The STS is presently scheduled to fly until 2030. To support the STS schedule the avionics on SRB's will be upgraded. The environments on the different sections of the SRB will need to be defined to properly qualify the avionics for multiple flights. The DFI data previously gathered does not provide enough information to properly qualify the avionics. Marshall Space Flight Centers (MSFC) SRB Project Office requested the Science and Engineering Directorate to develop a self contained data acquisition system that could collect data from any area of the booster. This paper summarizes the effort to develop, test, qualify and fly an Enhanced Data Acquisition System (EDAS) using state-of-the-art commercial off the shelf (COTS) equipment. The first flight of this system occurred on shuttle mission STS-91 in June 1998.

Crawford, Kevin↗

Multiplex data bus techniques

Multiplex data bus subsystem for improving reliability and reducing weight of space shuttle avionics system

Frost, W. O.↗