Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “block diagram”

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 415 records · Page 23
All sourcesNASA NTRSDOE OSTI
NASA NTRS2009

ARTEMIS: Ares Real Time Environments for Modeling, Integration, and Simulation

This slide presentation reviews the use of ARTEMIS in the development and testing of the ARES launch vehicles. Ares Real Time Environment for Modeling, Simulation and Integration (ARTEMIS) is the real time simulation supporting Ares I hardware-in-the-loop (HWIL) testing. ARTEMIS accurately models all Ares/Orion/Ground subsystems which interact with Ares avionics components from pre-launch through orbit insertion The ARTEMIS System integration Lab, and the STIF architecture is reviewed. The functional components of ARTEMIS are outlined. An overview of the models and a block diagram is presented.

Hughes, Ryan↗
NASA NTRS2009

Electrically Variable or Programmable Nonvolatile Capacitors

Electrically variable or programmable capacitors based on the unique properties of thin perovskite films are undergoing development. These capacitors show promise of overcoming two important deficiencies of prior electrically programmable capacitors: Unlike in the case of varactors, it is not necessary to supply power continuously to make these capacitors retain their capacitance values. Hence, these capacitors may prove useful as components of nonvolatile analog and digital electronic memories. Unlike in the case of ferroelectric capacitors, it is possible to measure the capacitance values of these capacitors without changing the values. In other words, whereas readout of ferroelectric capacitors is destructive, readout of these capacitors can be nondestructive. A capacitor of this type is a simple two terminal device. It includes a thin film of a suitable perovskite as the dielectric layer, sandwiched between two metal or metal oxide electrodes (for example, see Figure 1). The utility of this device as a variable capacitor is based on a phenomenon, known as electrical-pulse-induced capacitance (EPIC), that is observed in thin perovskite films and especially in those thin perovskite films that exhibit the colossal magnetoresistive (CMR) effect. In EPIC, the application of one or more electrical pulses that exceed a threshold magnitude (typically somewhat less than 1 V) gives rise to a nonvolatile change in capacitance. The change in capacitance depends on the magnitude duration, polarity, and number of pulses. It is not necessary to apply a magnetic field or to cool the device below (or heat it above) room temperature to obtain EPIC. Examples of suitable CMR perovskites include Pr(1-x)Ca(x)MnO3, La(1-x)S-r(x)MnO3,and Nb(1-x)Ca(x)MnO3. Figure 2 is a block diagram showing an EPIC capacitor connected to a circuit that can vary the capacitance, measure the capacitance, and/or measure the resistance of the capacitor.

Shangqing, Liu↗
NASA NTRS2007

An Array of Optical Receivers for Deep-Space Communications

An array of small optical receivers is proposed as an alternative to a single large optical receiver for high-data-rate communications in NASA s Deep Space Network (DSN). Because the telescope for a single receiver capable of satisfying DSN requirements must be greater than 10 m in diameter, the design, building, and testing of the telescope would be very difficult and expensive. The proposed array would utilize commercially available telescopes of 1-m or smaller diameter and, therefore, could be developed and verified with considerably less difficulty and expense. The essential difference between a single-aperture optical-communications receiver and an optical-array receiver is that a single-aperture receiver focuses all of the light energy it collects onto the surface of an optical detector, whereas an array receiver focuses portions of the total collected energy onto separate detectors, optically detects each fractional energy component, then combines the electrical signal from the array of detector outputs to form the observable, or "decision statistic," used to decode the transmitted data. A conceptual block diagram identifying the key components of the optical-array receiver suitable for deep-space telemetry reception is shown in the figure. The most conspicuous feature of the receiver is the large number of small- to medium-size telescopes, with individual apertures and number of telescopes selected to make up the desired total collecting area. This array of telescopes is envisioned to be fully computer- controlled via the user interface and prediction-driven to achieve rough pointing and tracking of the desired spacecraft. Fine-pointing and tracking functions then take over to keep each telescope pointed toward the source, despite imperfect pointing predictions, telescope-drive errors, and vibration caused by wind.

Vilnrotter, Chi-Wung↗
NASA NTRS2007

"Smart" Sensor Module

An assembly that contains a sensor, sensor-signal-conditioning circuitry, a sensor-readout analog-to-digital converter (ADC), data-storage circuitry, and a microprocessor that runs special-purpose software and communicates with one or more external computer(s) has been developed as a prototype of "smart" sensor modules for monitoring the integrity and functionality (the "health") of engineering systems. Although these modules are now being designed specifically for use on rocket-engine test stands, it is anticipated that they could also readily be designed to be incorporated into health-monitoring subsystems of such diverse engineering systems as spacecraft, aircraft, land vehicles, bridges, buildings, power plants, oilrigs, and defense installations. The figure is a simplified block diagram of the "smart" sensor module. The analog sensor readout signal is processed by the ADC, the digital output of which is fed to the microprocessor. By means of a standard RS-232 cable, the microprocessor is connected to a local personal computer (PC), from which software is downloaded into a randomaccess memory in the microprocessor. The local PC is also used to debug the software. Once the software is running, the local PC is disconnected and the module is controlled by, and all output data from the module are collected by, a remote PC via an Ethernet bus. Several smart sensor modules like this one could be connected to the same Ethernet bus and controlled by the single remote PC. The software running in the microprocessor includes driver programs for operation of the sensor, programs that implement self-assessment algorithms, programs that implement protocols for communication with the external computer( s), and programs that implement evolutionary methodologies to enable the module to improve its performance over time. The design of the module and of the health-monitoring system of which it is a part reflects the understanding that the main purpose of a health-monitoring system is to detect damage and, therefore, the health-monitoring system must be able to function effectively in the presence of damage and should be capable of distinguishing between damage to itself and damage to the system being monitored. A major benefit afforded by the self-assessment algorithms is that in the output of the module, the sensor data indicative of the health of the engineering system being monitored are coupled with a confidence factor that quantifies the degree of reliability of the data. Hence, the output includes information on the health of the sensor module itself in addition to information on the health of the engineering system being monitored.

Mahajan, Ajay↗
NASA NTRS2010

LDCM Ground System. Network Lesson Learned

This slide presentation reviews the Landsat Data Continuity Mission (LDCM) and the lessons learned in implementing the network that was assembled to allow for the acquisition, archiving and distribution of the data from the Landsat mission. The objective of the LDCM is to continue the acquisition, archiving, and distribution of moderate-resolution multispectral imagery affording global, synoptic, and repetitive coverage of the earth's land surface at a scale where natural and human-induced changes can be detected, differentiated, characterized, and monitored over time. It includes a review of the ground network, including a block diagram of the ground network elements (GNE) and a review of the RF design and testing. Also included is a listing of the lessons learned.

Gal-Edd, Jonathan↗
NASA NTRS2010

Modeling and Simulation of an UAS Collision Avoidance Systems

This paper describes a Modeling and Simulation of an Unmanned Aircraft Systems (UAS) Collision Avoidance System, capable of representing different types of scenarios for UAS collision avoidance. Commercial and military piloted aircraft currently utilize various systems for collision avoidance such as Traffic Alert and Collision A voidance System (TCAS), Automatic Dependent Surveillance-Broadcast (ADS-B), Radar and ElectroOptical and Infrared Sensors (EO-IR). The integration of information from these systems is done by the pilot in the aircraft to determine the best course of action. In order to operate optimally in the National Airspace System (NAS) UAS have to work in a similar or equivalent manner to a piloted aircraft by applying the principle of "detect-see and avoid" (DSA) to other air traffic. Hence, we have taken these existing sensor technologies into consideration in order to meet the challenge of researching the modeling and simulation of an approximated DSA system. A Schematic Model for a UAS Collision Avoidance System (CAS) has been developed ina closed loop block diagram for that purpose. We have found that the most suitable software to carry out this task is the Satellite Tool Kit (STK) from Analytical Graphics Inc. (AGI). We have used the Aircraft Mission Modeler (AMM) for modeling and simulation of a scenario where a UAS is placed on a possible collision path with an initial intruder and then with a second intruder, but is able to avoid them by executing a right tum maneuver and then climbing. Radars have also been modeled with specific characteristics for the UAS and both intruders. The software provides analytical, graphical user interfaces and data controlling tools which allow the operator to simulate different conditions. Extensive simulations have been carried out which returned excellent results.

Oliveros, Edgardo V.↗
NASA NTRS2011

Human Factors Operability Timeline Analysis to Improve the Processing Flow of the Orion Spacecraft

This slide presentation reviews the use of Human factors and timeline analysis to have a more efficient and effective processing flow. The solution involved developing a written timeline of events that included each activity within each functional flow block. Each activity had computer animation videos and pictures of the people involved and the hardware. The Human Factors Engineering Analysis Tool (HFEAT) was improved by modifying it to include the timeline of events. The HFEAT was used to define the human factors requirements and design solutions were developed for these requirements. An example of a functional flow block diagram is shown, and a view from one of the animations (i.e., short stack pallet) is shown and explained.

Stambolian, Damon B.↗
NASA NTRS2011

Comparison Modeling of System Reliability for Future NASA Projects

A National Aeronautics and Space Administration (NASA) supported Reliability, Maintainability, and Availability (RMA) analysis team developed a unique RMA analysis methodology using cut set and importance measure analysis in order to comparison model proposed avionics computing architectures. In this paper we will present this efficient application of the RMA analysis methodology for importance measures that includes Reliability Block Diagram (RED) Analysis, Comparison modeling, Cut Set Analysis, and Importance Measure Analysis. We will also demonstrate that integrating RMA early in the system design process as a key to success by providing a fundamental decision metric supporting design selection. The RMA analysis methodology presented in this paper and applied to the avionics architectures enhances the usual way of predicting the need for redundancy based on failure rates or subject matter expert opinion. Using the REDs and the minimal cut sets, along with the Fussell-Vesely (FV) factors, importance measures are calculated for each functional element in the architectures. This paper presents an application of the FV importance measures and presents an improved methodology for using importance measures in success space (instead of failure space) to compare architectures. These importance measures are used to determine which functional element would be most likely to cause a system failure, thus, quickly identifying the path to increase the overall system reliability by either procuring more reliable functional elements or adding redundancy. This application of the RMA analysis methodology, using RBD analysis, cut set analysis, and the importance measure analysis, allows the avionics design team to better understand and compare the vulnerabilities in each of the architectures, enabling them to address the deficiencies in the design architectures more efficiently, while balancing the need to design for optimum weight and space allocations.

Gillespie, Amanda M.↗
NASA NTRS2011

Kennedy Space Center Orion Processing Team Planning for Ground Operations

Topics in this presentation are: Constellation Ares I/Orion/Ground Ops Elements Orion Ground Operations Flow Orion Operations Planning Process and Toolset Overview, including: 1 Orion Concept of Operations by Phase 2 Ops Analysis Capabilities Overview 3 Operations Planning Evolution 4 Functional Flow Block Diagrams 5 Operations Timeline Development 6 Discrete Event Simulation (DES) Modeling 7 Ground Operations Planning Document Database (GOPDb) Using Operations Planning Tools for Operability Improvements includes: 1 Kaizen/Lean Events 2 Mockups 3 Human Factors Analysis

Letchworth, Gary↗
NASA NTRS2004

Stroboscope Controller for Imaging Helicopter Rotors

A versatile electronic timing-and-control unit, denoted a rotorcraft strobe controller, has been developed for use in controlling stroboscopes, lasers, video cameras, and other instruments for capturing still images of rotating machine parts especially helicopter rotors. This unit is designed to be compatible with a variety of sources of input shaftangle or timing signals and to be capable of generating a variety of output signals suitable for triggering instruments characterized by different input-signal specifications. It is also designed to be flexible and reconfigurable in that it can be modified and updated through changes in its control software, without need to change its hardware. Figure 1 is a block diagram of the rotorcraft strobe controller. The control processor is a high-density complementary metal oxide semiconductor, singlechip 8-bit microcontroller. It is connected to a 32K x 8 nonvolatile static random-access memory (RAM) module. Also connected to the control processor is a 32K 8 electrically programmable read-only-memory (EPROM) module, which is used to store the control software. Digital logic support circuitry is implemented in a field-programmable gate array (FPGA). A 240 x 128-dot, 40- character 16-line liquid-crystal display (LCD) module serves as a graphical user interface; the user provides input through a 16-key keypad mounted next to the LCD. A 12-bit digital-to-analog converter (DAC) generates a 0-to-10-V ramp output signal used as part of a rotor-blade monitoring system, while the control processor generates all the appropriate strobing signals. Optocouplers are used to isolate all input and output digital signals, and optoisolators are used to isolate all analog signals. The unit is designed to fit inside a 19-in. (.48-cm) rack-mount enclosure. Electronic components are mounted on a custom printed-circuit board (see Figure 2). Two power-conversion modules on the printedcircuit board convert AC power to +5 VDC and 15 VDC, respectively.

Jensen, Scott↗
NASA NTRS2004

Reduction of Phase Ambiguity in an Offset-QPSK Receiver

Proposed modifications of an offset-quadri-phase-shift keying (offset-QPSK) transmitter and receiver would reduce the amount of signal processing that must be done in the receiver to resolve the QPSK fourfold phase ambiguity. Resolution of the phase ambiguity is necessary in order to synchronize, with the received carrier signal, the signal generated by a local oscillator in a carrier-tracking loop in the receiver. Without resolution of the fourfold phase ambiguity, the loop could lock to any of four possible phase points, only one of which has the proper phase relationship with the carrier. The proposal applies, more specifically, to an offset-QPSK receiver that contains a carrier-tracking loop like that shown in Figure 1. This carrier-tracking loop does not resolve or reduce the phase ambiguity. A carrier-tracking loop of a different design optimized for the reception of offset QPSK could reduce the phase ambiguity from fourfold to twofold, but would be more complex. Alternatively, one could resolve the fourfold phase ambiguity by use of differential coding in the transmitter, at a cost of reduced power efficiency. The proposed modifications would make it possible to reduce the fourfold phase ambiguity to twofold, with no loss in power efficiency and only relatively simple additional signal-processing steps in the transmitter and receiver. The twofold phase ambiguity would then be resolved by use of a unique synchronization word, as is commonly done in binary phase-shift keying (BPSK). Although the mathematical and signal-processing principles underlying the modifications are too complex to explain in detail here, the modifications themselves would be relatively simple and are best described with the help of simple block diagrams (see Figure 2). In the transmitter, one would add a unit that would periodically invert bits going into the QPSK modulator; in the receiver, one would add a unit that would effect different but corresponding inversions of bits coming out of the QPSK demodulator. The net effect of all the inversions would be that depending on which lock point the carrier-tracking loop had selected, all the output bits would be either inverted or non-inverted together; hence, the ambiguity would be reduced from fourfold to twofold, as desired.

Berner, Jeff↗
NASA NTRS2004

Updated System-Availability and Resource-Allocation Program

A second version of the Availability, Cost and Resource Allocation (ACARA) computer program has become available. The first version was reported in an earlier tech brief. To recapitulate: ACARA analyzes the availability, mean-time-between-failures of components, life-cycle costs, and scheduling of resources of a complex system of equipment. ACARA uses a statistical Monte Carlo method to simulate the failure and repair of components while complying with user-specified constraints on spare parts and resources. ACARA evaluates the performance of the system on the basis of a mathematical model developed from a block-diagram representation. The previous version utilized the MS-DOS operating system and could not be run by use of the most recent versions of the Windows operating system. The current version incorporates the algorithms of the previous version but is compatible with Windows and utilizes menus and a file-management approach typical of Windows-based software.

Viterna, Larry↗
NASA NTRS2011

NASA Planning for Orion Multi-Purpose Crew Vehicle Ground Operations

The NASA Orion Ground Processing Team was originally formed by the Kennedy Space Center (KSC) Constellation (Cx) Project Office's Orion Division to define, refine and mature pre-launch and post-landing ground operations for the Orion human spacecraft. The multidisciplined KSC Orion team consisted of KSC civil servant, SAIC, Productivity Apex, Inc. and Boeing-CAPPS engineers, project managers and safety engineers, as well as engineers from Constellation's Orion Project and Lockheed Martin Orion Prime contractor. The team evaluated the Orion design configurations as the spacecraft concept matured between Systems Design Review (SDR), Systems Requirement Review (SRR) and Preliminary Design Review (PDR). The team functionally decomposed prelaunch and post-landing steps at three levels' of detail, or tiers, beginning with functional flow block diagrams (FFBDs). The third tier FFBDs were used to build logic networks and nominal timelines. Orion ground support equipment (GSE) was identified and mapped to each step. This information was subsequently used in developing lower level operations steps in a Ground Operations Planning Document PDR product. Subject matter experts for each spacecraft and GSE subsystem were used to define 5th - 95th percentile processing times for each FFBD step, using the Delphi Method. Discrete event simulations used this information and the logic network to provide processing timeline confidence intervals for launch rate assessments. The team also used the capabilities of the KSC Visualization Lab, the FFBDs and knowledge of the spacecraft, GSE and facilities to build visualizations of Orion pre-launch and postlanding processing at KSC. Visualizations were a powerful tool for communicating planned operations within the KSC community (i.e., Ground Systems design team), and externally to the Orion Project, Lockheed Martin spacecraft designers and other Constellation Program stakeholders during the SRR to PDR timeframe. Other operations planning tools included Kaizen/Lean events, mockups and human factors analysis. The majority of products developed by this team are applicable as KSC prepares 21st Century Ground Systems for the Orion Multi-Purpose Crew Vehicle and Space Launch System.

Letchworth, Gary↗
NASA NTRS2015

NASA Manufacturing and Test Requirements for Normally Closed Pyrovalves for Hazardous Flight Systems Applications

Pyrovalves (figure 1, Basic Pyrovalve Design and Features,) are typically lighter, more reliable, and in most cases less expensive than other types of valves. They also consume less electrical power. They are single-use devices that are used in propulsion systems to isolate propellants or pressurant gases. These fluids may be hazardous because of their toxicity, reactivity, temperature, or high pressure. Note that in the simplified block diagram below not all detail features are shown so that those of major interest are more prominent. The diagram is provided to point out the various features that are discussed in this Specification. Features of some NC parent metal valve designs may differ. In 2013, the NESC concluded an extensive study of the reliability and safety of NC parent metal valves used in payloads carried aboard ELVs. The assessment successfully evaluated technical data to determine the risk of NC parent metal valve leakage or inadvertent activation in ELV payloads. The study resulted in numerous recommendations to ensure personnel and hardware/facility safety during ground processing of ELV payloads. One of those recommendations was to establish a NASA specification for NC parent metal valves. This Specification is a result of that recommendation, which is documented in NESC-RP-10-00614.

McDougle, Stephen H.↗
NASA NTRS2009

Spreadsheets in Team X: Preserving Order in an Inherently Chaotic Environment

JPL is NASA's prime center for deep space missions. In response to the need to reduce the cost and time to complete early concept studies and proposals JPL created the first concurrent engineering team in the aerospace industry: Team X. Started in 1995, Team X has carried out over 800 studies, dramatically reducing the time and cost involved, and has been the model for other concurrent engineering teams both within NASA and throughout the larger aerospace community. Since its inception, the software backbone of this highly successful design team - engaged in examining some of NASA's cutting edge concepts - has been the unassuming spreadsheet. Over the years the Team X spreadsheet-based tools have evolved from simple standalone engineering models into a networked spreadsheet intensive system with real time parameter updating. Recent new capabilities include stochastic cost estimation and a graphical drag and drop block diagram that automatically populates the related spreadsheet parameters of cost, mass and power. This paper describes how the spreadsheet functions within Team X: its history, architecture, current capabilities, enabling strengths and persistent weaknesses. In addition, the verification methods and institutional oversight that have evolved as the Team X products became increasingly critical to Laboratory success are also discussed.

concurrent engineering↗
NASA NTRS2018

Mission Configuration Tree for the James Webb Space Telescope (JWST)

The GSFC Mission Configuration web-based application is a means of documenting the structure of the many elements used in building each mission that NASA launches, as well as archiving the documents associated with each of these elements and keeping track of suppliers. This includes all available drawings, engineering orders, parts lists, block diagrams, and photos of each system, subsystem, and component. While the information for several of NASA's missions is being input into Mission Configuration, the ten weeks of this project focused on collecting information for the instrument systems of the James Webb Space Telescope. Documents were collected from a database called the Next Generation Integrated Network (NGIN) so that they can eventually be uploaded into the application. From these documents, including drawings and parts lists, a configuration tree was created in Microsoft Visio which showed the relationships between each system, subsystem, and component. When both these documents and the configuration tree are input into Mission Configuration, they will be place into a drill down tree structure, from which drawings and documents can be accessed directly. Mission Configuration also includes search functions that make all parts searchable by keywords such as vendor, part number, taxonomy, and alternate nomenclature. This application is an important resource for providing access to documents related to the components used on each mission. It has created a central repository for information which can be used to benefit Safety & Mission Assurance, but may also be useful across codes. The process of collecting the information and documents to put into Mission Configuration is also allowing for a concise breakdown of information from diverse formats, creating standardization which makes information more readily accessible, while retaining project-specific information that makes it more easily searchable.

Cain, Mary C.↗
NASA NTRSDate not supplied

Applying the System Complexity Metric (SCM)

A fundamental cause of difficulty in larger engineering projects is their inherent complexity. An impression of complexity occurs if a system is simply difficult to understand, so that there is no obvious mental model that correctly predicts its behavior. Higher complexity is usually associated with higher cost and higher failure rate. Complexity is indicated by a system having more and diverse components, multiple interactions and feedback loops, transients and dynamic behavior, and often the emergence of unanticipated failure modes. Identifying and removing these signs of complexity should reduce complexity and improve performance. Here we limit complexity measurement to the number of components and their interactions. A System Complexity Metric (SCM) is defined as equal to the sum of the number of parts in a system, N, plus the sum of the one-way interconnections between them, I. SCM = N + I. The SCM is easily determined by direct inspection of system block diagrams. Previous work found that life support system cost was directly proportional to SCM and that failure rate increased faster than SCM squared. SCM can be used to compare systems or to guide their redesign to reduce cost and failure rate. Carbon dioxide removal systems will be analyzed using SCM, cost, and failure rate.

Harry W Jones↗