Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “buses”

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 37 records · Page 2

Performance evaluation of Platform Data ManagementSystem under various degrees of protocol implementation

The Platform Data Management System (DMS) collects Housekeeping (H/K), Payload (P/L) Engineering, and Payload Science data from various subsystems and payloads on the platform for transmission to the ground through the downlink via TDRSS. The DMS also distributes command data received from the ground to various subsystems and payloads. In addition, DMS distributes timing and safemode data. The function of collection and distribution of various types of data is performed by the Command and Data Handling (C&DH) subsystem of DMS. The C&DH subsystem uses for this purpose a number of data buses namely, Housekeeping, Payload Engineering, Payload Science, and Time and Safemode buses. Out of these buses, the H/K, P/L Engineering, and P/L Science buses are planned to be implemented by using MIL-STD 1553 bus. Most of the period covered was spent in developing a queue theoretic model of the 1553 Bus as used in the DMS. The aim is to use this model to test the performance and suitability of the 1553 Bus to the DMS under a number of alternative design scenarios.

Arozullah, Mohammed↗

A Comparison of Bus Architectures for Safety-Critical Embedded Systems

We describe and compare the architectures of four fault-tolerant, safety-critical buses with a view to deducing principles common to all of them, the main differences in their design choices, and the tradeoffs made. Two of the buses come from an avionics heritage, and two from automobiles, though all four strive for similar levels of reliability and assurance. The avionics buses considered are the Honeywell SAFEbus (the backplane data bus used in the Boeing 777 Airplane Information Management System) and the NASA SPIDER (an architecture being developed as a demonstrator for certification under the new DO-254 guidelines); the automobile buses considered are the TTTech Time-Triggered Architecture (TTA), recently adopted by Audi for automobile applications, and by Honeywell for avionics and aircraft control functions, and FlexRay, which is being developed by a consortium of BMW, DaimlerChrysler, Motorola, and Philips.

Rushby, John↗

Reusable Rack Interface Controller Common Software for Various Science Research Racks on the International Space Station

The purpose of the EXPRESS (Expedite the PRocessing of Experiments to Space Station) rack project is to provide a set of predefined interfaces for scientific payloads which allow rapid integration into a payload rack on International Space Station (ISS). VxWorks' was selected as the operating system for the rack and payload resource controller, primarily based on the proliferation of VME (Versa Module Eurocard) products. These products provide needed flexibility for future hardware upgrades to meet everchanging science research rack configuration requirements. On the International Space Station, there are multiple science research rack configurations, including: 1) Human Research Facility (HRF); 2) EXPRESS ARIS (Active Rack Isolation System); 3) WORF (Window Observational Research Facility); and 4) HHR (Habitat Holding Rack). The RIC (Rack Interface Controller) connects payloads to the ISS bus architecture for data transfer between the payload and ground control. The RIC is a general purpose embedded computer which supports multiple communication protocols, including fiber optic communication buses, Ethernet buses, EIA-422, Mil-Std-1553 buses, SMPTE (Society Motion Picture Television Engineers)-170M video, and audio interfaces to payloads and the ISS. As a cost saving and software reliability strategy, the Boeing Payload Software Organization developed reusable common software where appropriate. These reusable modules included a set of low-level driver software interfaces to 1553B. RS232, RS422, Ethernet buses, HRDL (High Rate Data Link), video switch functionality, telemetry processing, and executive software hosted on the FUC computer. These drivers formed the basis for software development of the HRF, EXPRESS, EXPRESS ARIS, WORF, and HHR RIC executable modules. The reusable RIC common software has provided extensive benefits, including: 1) Significant reduction in development flow time; 2) Minimal rework and maintenance; 3) Improved reliability; and 4) Overall reduction in software life cycle cost. Due to the limited number of crew hours available on ISS for science research, operational efficiency is a critical customer concern. The current method of upgrading RIC software is a time consuming process; thus, an improved methodology for uploading RIC software is currently under evaluation.

Lu, George C.↗

Large Satellite Bus Reliability

NASA is proposing to build a small space station in Cis-lunar orbit called Deep Space Gateway (DSG). At the heart of the DSG is the Power and Propulsion Element (PPE) which is conceptually similar to previously designed and operated satellite buses. A satellite bus is composed of the satellite spacecraft infrastructure minus the payload, and generally includes power, propulsion, avionics, and guidance, navigation and control. In November of 2017, five companies were awarded contracts by NASA to research PPE designs. In order to better understand the reliability of large satellite buses which may be the starting point of the PPE, NASA used Weibull analysis to evaluate spacecraft with similar masses and design life to the PPE. In addition, a subset of the large satellites which had satellite buses manufactured by any one of the five companies was also evaluated. This paper provides the results of the reliability analysis and compares the reliability of the general population of large satellites to the reliability associated with large satellite buses manufactured by the five companies currently studying PPE options.

Bus↗

System data communication structures for active-control transport aircraft, volume 1

Candidate data communication techniques are identified, including dedicated links, local buses, broadcast buses, multiplex buses, and mesh networks. The design methodology for mesh networks is then discussed, including network topology and node architecture. Several concepts of power distribution are reviewed, including current limiting and mesh networks for power. The technology issues of packaging, transmission media, and lightning are addressed, and, finally, the analysis tools developed to aid in the communication design process are described. There are special tools to analyze the reliability and connectivity of networks and more general reliability analysis tools for all types of systems.

Hopkins, A. L.↗

Digital system bus integrity

This report summarizes and describes the results of a study of current or emerging multiplex data buses as applicable to digital flight systems, particularly with regard to civil aircraft. Technology for pre-1995 and post-1995 timeframes has been delineated and critiqued relative to the requirements envisioned for those periods. The primary emphasis has been an assured airworthiness of the more prevalent type buses, with attention to attributes such as fault tolerance, environmental susceptibility, and problems under continuing investigation. Additionally, the capacity to certify systems relying on such buses has been addressed.

Eldredge, Donald↗

Design Description of the X-33 Avionics Architecture

In this paper, we provide a design description of the X-33 avionics architecture. The X-33 is an autonomous Single Stage to Orbit (SSTO) launch vehicle currently being developed by Lockheed Martin for NASA as a technology demonstrator for the VentureStar Reusable Launch Vehicle (RLV). The X-33 avionics provides autonomous control of die vehicle throughout takeoff, ascent, descent, approach, landing, rollout, and vehicle safing. During flight the avionics provides communication to the range through uplinked commands and downlinked telemetry. During pre-launch and post-safing activities, the avionics provides interfaces to ground support consoles that perform vehicle flight preparations and maintenance. The X-33 Avionics is a hybrid of centralized and distributed processing elements connected by three dual redundant Mil-Std 1553 data buses. These data buses are controlled by a central processing suite located in the avionics bay and composed of triplex redundant Vehicle Mission Computers (VMCs). The VMCs integrate mission management, guidance, navigation, flight control, subsystem control and redundancy management functions. The vehicle sensors, effectors and subsystems are interfaced directly to the centralized VMCs as remote terminals or through dual redundant Data Interface Units (DIUs). The DIUs are located forward and aft of the avionics bay and provide signal conditioning, health monitoring, low level subsystem control and data interface functions. Each VMC is connected to all three redundant 1553 data buses for monitoring and provides a complete identical data set to the processing algorithms. This enables bus faults to be detected and reconfigured through a voted bus control configuration. Data is also shared between VMCs though a cross channel data link that is implemented in hardware and controlled by AlliedSignal's Fault Tolerant Executive (FTE). The FTE synchronizes processors within the VMC and synchronizes redundant VMCs to each other. The FTE provides an output-voting plane to detect, isolate and contain faults due to internal hardware or software faults and reconfigures the VMCs to accommodate these faults. Critical data in the 1553 messages are scheduled and synchronized to specific processing frames in order to minimize data latency. In order to achieve an open architecture, military and commercial off-the-shelf equipment is incorporated using common processors, standard VME backplanes and chassis, the VxWorks operating system, and MartixX for automatic code generation. The use of off-the-shelf tools and equipment helps reduce development time and enables software reuse. The open architecture allows for technology insertion, while the distributed modular elements allow for expansion to increased redundancy levels to meet the higher reliability goals of future RLVs.

Reichenfeld, Curtis J.↗

CCSDS Time-Critical Onboard Networking Service

The Consultative Committee for Space Data Systems (CCSDS) is developing recommendations for communication services onboard spacecraft. Today many different communication buses are used on spacecraft requiring software with the same basic functionality to be rewritten for each type of bus. This impacts on the application software resulting in custom software for almost every new mission. The Spacecraft Onboard Interface Services (SOIS) working group aims to provide a consistent interface to various onboard buses and sub-networks, enabling a common interface to the application software. The eventual goal is reusable software that can be easily ported to new missions and run on a range of onboard buses without substantial modification. The system engineer will then be able to select a bus based on its performance, power, etc and be confident that a particular choice of bus will not place excessive demands on software development. This paper describes the SOIS Intra-Networking Service which is designed to enable data transfer and multiplexing of a variety of internetworking protocols with a range of quality of service support, over underlying heterogeneous data links. The Intra-network service interface provides users with a common Quality of Service interface when transporting data across a variety of underlying data links. Supported Quality of Service (QoS) elements include: Priority, Resource Reservation and Retry/Redundancy. These three QoS elements combine and map into four TCONS services for onboard data communications: Best Effort, Assured, Reserved, and Guaranteed. Data to be transported is passed to the Intra-network service with a requested QoS. The requested QoS includes the type of service, priority and where appropriate, a channel identifier. The data is de-multiplexed, prioritized, and the required resources for transport are allocated. The data is then passed to the appropriate data link for transfer across the bus. The SOIS supported data links may inherently provide the quality of service support requested by the intra-network layer. In the case where the data link does not have the required level of support, the missing functionality is added by SOIS. As a result of this architecture, re-usable software applications can be designed and used across missions thereby promoting common mission operations. In addition, the protocol multiplexing function enables the blending of multiple onboard networks. This paper starts by giving an overview of the SOIS architecture in section 11, illustrating where the TCONS services fit into the overall architecture. It then describes the quality of service approach adopted, in section III. The prototyping efforts that have been going on are introduced in section JY. Finally, in section V the current status of the CCSDS recommendations is summarized.

Parkes, Steve↗

X-57 Mod II Avionics Power Analysis

The X-57 Mod II Avionics Power Analysis was developed to provide the design requirements for the X-57 Avionics Power System. In the Mod II configuration, the two stock Tecnam P2006T Rotax engines are replaced with two electric motors. A high voltage traction battery (460 VDC nominal) supplies power for the motors. The Mod II avionics power design uses the stock Tecnam avionics power architecture as a baseline. The stock Tecnam power system utilizes three 12 VDC power sources, a battery and two alternators, to provided redundant avionics power. This redundancy was preserved in the X-57 avionics power architecture. A block diagram of the X-57 avionics system can be found in the “Mod II Architecture” worksheet of this documents. Since the X-57 electric motors do not have alternators or generators, two 13.8V DC Converters were added to replace the stock Tecnam alternators. Input power to these DC Converters is provide by the high voltage traction battery. The Tecnam stock lead acid battery was replaced with a Lithium Iron Phosphate (LiFePO4) battery. The Mod II Avionics Power Analysis provided the power requirements for the two 13.8V DC converters and the Lithium Iron Phosphate battery. Power requirement estimates for each subsystem used in this analysis were provided by manufacturer specifications, measured in the laboratory or provided by the subsystem design engineer. Typical power requirements and maximum power requirements were provided for each subsystem. The Mod II Avionics Power Systems consists of seven 13.8 VDC buses, two 28 VDC Buses and two 23 VDC buses. The avionics power requirements for Mod III configuration are the same as Mod II. The Mod III configuration replaces the stock Tecnam wing with a carbon fiber wing that is optimized for cruise conditions. The motors are located on the wingtips. The Mod IV Avionics Power Analysis is a separate analysis and is document number ANLYS-CEPT-032.

Keith Harris↗

Study of passenger subjective response to ideal and real-vehicle vibration environments

The stimulus received by subjects tested on the passenger ride quality apparatus (PRQA) is defined. Additional analyses on the data collected from field tests using buses, were conducted to assess the relation between subjective ratings of ride quality and vibrations measured on the buses, and to better define the vibration stimulus measured in the field. The relation of subjective evaluation of simulations of bus rides produced by the DRQA to subjective evaluations of the actual bus rides is discussed. The relative contribution of the seat and floor vibration to human comfort in a simulated aircraft ride environment is discussed along with the determination of equal comfort curves through magnitude estimation.

Kirby, R. H.↗

Analysis of payload bay magnetic fields due to dc power multipoint and single point ground configurations

An analysis of magnetic fields in the Orbiter Payload Bay resulting from the present grounding configuration (structure return) was presented and the amount of improvement that would result from installing wire returns for the three dc power buses was determined. Ac and dc magnetic fields at five points in a cross-section of the bay are calculated for both grounding configurations. Y and Z components of the field at each point are derived in terms of a constant coefficient and the current amplitude of each bus. The dc loads assumed are 100 Amperes for each bus. The ac noise current used is a spectrum 6 db higher than the Orbiter equipment limit for narrowband conducted emissions. It was concluded that installing return wiring to provide a single point ground for the dc Buses in the Payload Bay would reduce the ac and dc magnetic field intensity by approximately 30 db.

Lawton, R. M.↗

Microprocessor systems for industrial process control

Six computers operate synchronously and are interconnected by three independent data buses. Processors control one subsystem. Some can control buses to transfer data at 1 megabit per second. Every 2.5 msec each processor examines list of things to do during next interval. This spacecraft control system could be adapted for controlling complex industrial processes.

Lesh, F. H.↗

Fault-tolerant computer study

A set of building block circuits is described which can be used with commercially available microprocessors and memories to implement fault tolerant distributed computer systems. Each building block circuit is intended for VLSI implementation as a single chip. Several building blocks and associated processor and memory chips form a self checking computer module with self contained input output and interfaces to redundant communications buses. Fault tolerance is achieved by connecting self checking computer modules into a redundant network in which backup buses and computer modules are provided to circumvent failures. The requirements and design methodology which led to the definition of the building block circuits are discussed.

Rennels, D. A.↗

High voltage systems (tube-type microwave)/low voltage system (solid-state microwave) power distribution

SPS satellite power distribution systems are described. The reference Satellite Power System (SPS) concept utilizes high-voltage klystrons to convert the onboard satellite power from dc to RF for transmission to the ground receiving station. The solar array generates this required high voltage and the power is delivered to the klystrons through a power distribution subsystem. An array switching of solar cell submodules is used to maintain bus voltage regulation. Individual klystron dc voltage conversion is performed by centralized converters. The on-board data processing system performs the necessary switching of submodules to maintain voltage regulation. Electrical power output from the solar panels is fed via switch gears into feeder buses and then into main distribution buses to the antenna. Power also is distributed to batteries so that critical functions can be provided through solar eclipses.

Nussberger, A. A.↗

On-board communication for active-control transport aircraft

An investigation of active control communications sponsored by the NASA Langley Research Center is summarized. Particular attention is given to comparative architectures, for which a common set of requirements is generated as a baseline. Most of the requirements are aircraft functional in nature, such as stability and command augmentation, structural load relief, flight path control, flight control linkage, flight monitoring, management, navigation, engine control, and ground communication; the time element, the hazard environment, and the communications capacity estimation are also important factors. The architectures involve several communication technologies, including dedicated links, broadcast busing, and multiplex busing. The multiplex bus system provides the greatest flexibility and installation efficiency. A future homogeneous network system is also proposed, which would be fault and damage tolerant and would, with advanced technology, avoid the problems of designing a very large and flight critical multiplex bus system.

Brock, L. D.↗

A historical overview of the electrical power systems in the US manned and some US unmanned spacecraft

A historical overview of electrical power systems used in the U.S. manned spacecraft and some of the U.S. unmanned spacecraft is presented in this investigation. A time frame of approximately 25 years, the period for 1959 to 1984, is covered in this report. Results indicate that the nominal bus voltage was 28 volts dc in most spacecraft and all other voltage levels were derived from this voltage through such techniques as voltage inversion or rectification, or a combination. Most spacecraft used solar arrays for the main source of power except for those spacecraft that had a relatively short flight duration, or deep spaceprobes that were designed for very long flight duration. Fuel cells were used on Gemini, Apollo, and Space Shuttle (short duration flights) while radioisotope thermoelectric generators were employed on the Pioneer, Jupiter/Saturn, Viking Lander, and Voyager spacecraft (long duration flights). The main dc bus voltage was unregulated on the manned spacecraft with voltage regulation provided at the user loads. A combination of regulated, semiregulated, and unregulated buses were used on the unmanned spacecraft depending on the type of load. For example, scientific instruments were usually connected to regulated buses while fans, relays, etc. were energized from an unregulated bus. Different forms of voltage regulation, such as shunt, buck/boot, and pulse-width modulated regulators, were used. This report includes a comprehensive bibliography on spacecraft electrical power systems for the space programs investigated.

Maisel, J. E.↗

Avionics/crew station integration

The U.S. Navy has been encouraging advanced development concepts aimed at increasing the aircraft instrumentation performance for multi-platform applications of 1990's weapons systems. The three areas covered by the Navy's research and development effort are: System Integration, Technology, and Human Factors. The System Integration objectives are to produce a system architecture easily adaptable to many platforms. Technology objectives are to determine the state of the art for displays, electronics, and controls. The Human Factors objectives are to determine the proper human-machine interfaces so that the ultimate crew station will be capable of providing the pilot with the proper display and controls performance to satisfy the diverse requirements of a fighter, attack, ASW, fixed-wing, rotary-wing, and V/STOL platforms in both a one-man crew or two-man crew matrix. All data/control interface among units of this crew station and other platform subsystems will be via digital data buses and video multiplex buses. No individual discrete signal, data, or control lines will be needed. This paper discusses the six interfaces necessary to ensure the optimum development of this crew station, the predicted platform mission improvements, and the requisite life-cycle cost considerations. This concept will serve as a basis for planning the integration of the necessary hardware and software features in current and future weapons systems.

Mulley, W. G.↗

Some Protocols For Optical-Fiber Digital Communications

One works best in heavy traffic, another, in light traffic. Three protocols proposed for digital communications among stations connected by passive taps to pair of uni-directional optical-fiber buses. Mediate round-robin, bounded-delay access to buses by all stations and particularly suited to fast transmission. Partly because transmission medium passive (no relay stations) and partly because protocols distribute control of network among all stations with provision for addition and deletion of stations (no control stations), communication network able to resist and recover from failures. Implicit token propagates in one direction on one bus and in opposite direction on other bus, minimizing interval of silence between end of one round and beginning of next.

Yeh, Cavour↗