Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “subsystems”

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 1,459 records · Page 81

Integrated Advanced Microwave Sounding Unit-A(AMSU-A). Performance Verification Report: METSAT AMSU-A2 Receiver Assembly, (P/N 1356441-1, S.N F04) S/N 107

The AMSU-A receiver subsystem comprises two separated receiver assemblies; AMSU-Al and AMSU-A2(PN1356441-1). The AMSU-A1 receiver contains 13 channels and the AMSU-A2 receiver 2 channels. The AMSU-AL receiver assembly is further divided into two parts; AMSU-A 1-1 (P/N 1356429-1) and AMSU-A 1-2 (P/N 1356409-1), which contain 9 and 4 channels, respectively. The AMSU-A receiver subsystem stands in between the antenna and signal processing subsystems of the AMSU-A instrument and comprises the RF and IF components from RF isolators to IF attenuators. It receives the RF signals from the antenna subsystem, down-converts the RF signals to IF signals, amplifies and defines the IF signals to proper power level and frequency bandwidth as specified for each channel, and inputs the IF signals to the signal processing subsystem. The test reports for the METSAT AMSU-A receiver subsystem are prepared separately for the A1 and A2 receivers so that each receiver stands alone during integration of instruments into the spacecraft. This test report presents the test data of the METSAT AMSU-A2 Flight Model No.4 (FM4) receiver. The tests are performed per the Acceptance Test Procedure for the AMSU-A Receiver Subsystem, AE-26002/6A. The functional performance tests are conducted either at the component or subsystem level. While the component-level tests are performed over the entire operating temperature range predicted by thermal analysis, the subsystem-level tests are conducted at ambient temperature only.

Kapper, R.↗

Wireless Avionics Packet to Support Fault Tolerance for Flight Applications

In this protocol and packet format, data traffic is monitored by all network interfaces to determine the health of transmitter and subsystems. When failures are detected, the network inter face applies its recover y policies to provide continued service despite the presence of faults. The protocol, packet format, and inter face are independent of the data link technology used. The current demonstration system supports both commercial off-the-shelf wireless connections and wired Ethernet connections. Other technologies such as 1553 or serial data links can be used for the network backbone. The Wireless Avionics packet is divided into three parts: a header, a data payload, and a checksum. The header has the following components: magic number, version, quality of service, time to live, sending transceiver, function code, payload length, source Application Data Interface (ADI) address, destination ADI address, sending node address, target node address, and a sequence number. The magic number is used to identify WAV packets, and allows the packet format to be updated in the future. The quality of service field allows routing decisions to be made based on this value and can be used to route critical management data over a dedicated channel. The time to live value is used to discard misrouted packets while the source transceiver is updated at each hop. This information is used to monitor the health of each transceiver in the network. To identify the packet type, the function code is used. Besides having a regular data packet, the system supports diagnostic packets for fault detection and isolation. The payload length specifies the number of data bytes in the payload, and this supports variable-length packets in the network. The source ADI is the address of the originating interface. This can be used by the destination application to identify the originating source of the packet where the address consists of a subnet, subsystem class within the subnet, a subsystem unit, and the local ADI number. The destination ADI is used to route the packet to its ultimate destination. At each hop, the sending interface uses the destination address to determine the next node for the data. The sending node is the node address of the interface that is broadcasting the packet. This field is used to determine the health of the subsystem that is sending the packet. In the case of a packet that traverses several intermediate nodes, it may be the node address of the intermediate node. The target node is the node address of the next hop for the packet. It may be an intermediate node, or the final destination for the packet. The sequence number is used to identify duplicate packets. Because each interface has multiple transceivers, the same packet will appear at both receivers. The sequence number allows the interface to correlate the reception and forward a single, unique packet for additional processing. The subnet field allows data traffic to be partitioned into segregated local networks to support large networks while keeping each subnet at a manageable size. This also keeps the routing table small enough so routing can be done by a simple table lookup in an FPGA device. The subsystem class identifies members of a set of redundant subsystems, and, in a hot standby configuration, all members of the subsystem class will receive the data packets. Only the active subsystem will generate data traffic. Specific units in a class of redundant units can be identified and, if the hot standby configuration is not used, packets will be directed to a specific subsystem unit.

Block, Gary L.↗

Coastal Research Imaging Spectrometer

The Coastal Research Imaging Spectrometer (CRIS) is an airborne remote sensing system designed specifically for research on the physical, chemical, and biological characteristics of coastal waters. The CRIS includes a visible-light hyperspectral imaging subsystem for measuring the color of water, which contains information on the biota, sediment, and nutrient contents of the water. The CRIS also includes an infrared imaging subsystem, which provides information on the temperature of the water. The combination of measurements enables investigation of biological effects of both natural and artificial flows of water from land into the ocean, including diffuse and point-source flows that may contain biological and/or chemical pollutants. Temperature is an important element of such measurements because temperature contrasts can often be used to distinguish among flows from different sources: for example, a sewage outflow could manifest itself in spectral images as a local high-temperature anomaly. Both the visible and infrared subsystems scan in pushbroom mode: that is, an aircraft carrying the system moves along a ground track, the system is aimed downward, and image data are acquired in across-track linear arrays of pixels. Both subsystems operate at a frame rate of 30 Hz. The infrared and visible-light optics are adjusted so that both subsystems are aimed at the same moving swath, which has across-track angular width of 15 . Data from the infrared and visible imaging subsystems are stored in the same file along with aircraft- position data acquired by a Global Positioning System receiver. The combination of the three sets of data is used to construct infrared and hyperspectral maps of scanned areas (see figure). The visible subsystem is based on a grating spectrograph and a rapid-readout charge-coupled-device camera. Images of the swatch are acquired in 256 spectral bands at wavelengths from 400 to 800 nm. The infrared subsystem, which is sensitive in a single wavelength band of 8 to 10 m, is based on a focal-plane array of HgCdTe photodetectors that are cooled to an operating temperature of 77 K by use of a closed-Stirling-cycle mechanical cooler. The nonuniformities of the HgCdTe photodetector array are small enough that the raw pixel data from the infrared subsystem can be used to recognize temperature differences on the order of 1 C. By use of a built-in blackbody calibration source that can be switched into the field of view, one can obtain bias and gain offset terms for individual pixels, making it possible to offset the effects of nonuniformities sufficiently to enable the measurement of temperature differences as small as 0.1 C.

Lucey, Paul G.↗

An Agile-Like Approach to Hardware Development: The Ejectable Data Recorder (EDR) for Orion's Ascent Abort 2 (AA-2) Test Flight

On July 2, 2019, the Ascent Abort 2 (AA-2) Flight Test Vehicle was launched from Cape Canaveral, with the goal of demonstrating the performance of Orion’s Launch Abort System (LAS) and collecting data from hundreds of sensors throughout the vehicle. The data collected during this test flight is of paramount importance, as it will be used to certify the Orion vehicle for human spaceflight. Originally, the data was to be downlinked via a single string network of antennas on the LAS, with the associated risk of potential data dropouts, as well as loss of data once the LAS was jettisoned. Thus, additional antennas were added onto the crew module (CM) to support data downlink post-LAS jettison, a buffer rebroadcast capability was added to fill in any gaps in data downlink transmissions, and an ejectable data recorder (EDR) subsystem was added to the CM as a redundant measure to collect all the instrumentation data. The EDR subsystem was added to the project about one year after the project commenced, which significantly reduced the available development time when compared with the other subsystems of the AA-2 Test Flight. The project was further accelerated by six months, around the critical design review gate. Due to the schedule compression challenge and the fact that the EDR subsystem was a backup system and not flight critical, the EDR subsystem was further challenged to find a new and more efficient way to develop hardware. Thus, the EDR subsystem experimented with different management and systems engineering processes, team sizes, communication methods, and tools. Some examples are novel uses of SharePoint as a Data-centric Project Management & Systems Engineering environment, a continuous testing approach through the lifecycle, and a Skunkworks approach to managing the team. The EDR subsystem blended Commercial Off The Shelf (COTS) hardware with in-house developed hardware and software to create a novel data retrieval capability. The capability evolved rapidly through a hardware in the loop simulation environment that enabled incremental component updates for not only the EDR subsystem but across the entire Crew Module. This paper will present an overview of how the EDR subsystem was managed and compare it to an Agile approach to managing projects. The paper will further provide a recommended approach to future Agile-like hardware development that incorporates lessons learned from the EDR experience.

Agile↗

Integrated system for investigating sub-surface features of a rock formation

A system for investigating non-linear properties of a rock formation around a borehole is provided. The system includes a first sub-system configured to perform data acquisition, control and recording of data; a second subsystem in communication with the first sub-system and configured to perform non-linearity and velocity preliminary imaging; a third subsystem in communication with the first subsystem and configured to emit controlled acoustic broadcasts and receive acoustic energy; a fourth subsystem in communication with the first subsystem and the third subsystem and configured to generate a source signal directed towards the rock formation; and a fifth subsystem in communication with the third subsystem and the fourth subsystem and configured to perform detection of signals representative of the non-linear properties of the rock formation.

58 GEOSCIENCES↗

ERTS-1, the spacecraft and its sensors

The basic objectives of the ERTS-1 mission are defined as follows: (1) to determine what data can be acquired from an orbiting satellite on the natural and cultural resources and on the environment; and (2) to develop and demonstrate the combination of data-acquisition procedures and interpretative techniques which can make this new knowledge available for use in the many facets of man's life. A general description of the satellite's observatory system and its sensors is given, including the thermal control subsystem, the power subsystem, the attitude control subsystem, the orbit adjust subsystem, the telemetry and tracking systems, the communications and data handling subsystem, the return beam vidicon subsystem, the multispectral scanner subsystem, the two wideband video tape recorders, and the data collection subsystem.

Weiland, S.↗

Real time computer data system for the 40 x 80 ft wind tunnel facility at Ames Research Center

The wind tunnel realtime computer system is a distributed data gathering system that features a master computer subsystem, a high speed data gathering subsystem, a quick look dynamic analysis and vibration control subsystem, an analog recording back-up subsystem, a pulse code modulation (PCM) on-board subsystem, a communications subsystem, and a transducer excitation and calibration subsystem. The subsystems are married to the master computer through an executive software system and standard hardware and FORTRAN software interfaces. The executive software system has four basic software routines. These are the playback, setup, record, and monitor routines. The standard hardware interfaces along with the software interfaces provide the system with the capability of adapting to new environments.

Cambra, J. M.↗

Earth Observatory Satellite system definition study. Report 5: System design and specifications. Volume 3: General purpose spacecraft segment and module specifications

The specifications for the Earth Observatory Satellite (EOS) general purpose aircraft segment are presented. The satellite is designed to provide attitude stabilization, electrical power, and a communications data handling subsystem which can support various mission peculiar subsystems. The various specifications considered include the following: (1) structures subsystem, (2) thermal control subsystem, (3) communications and data handling subsystem module, (4) attitude control subsystem module, (5) power subsystem module, and (6) electrical integration subsystem.

Source record↗

Electric propulsion system design and development for primary propulsion applications

An electric thrust subsystem technology development program to demonstrate the readiness of primary electric propulsion for flight applications is described. The development program is based on a subsystem design sufficiently flexible to be applicable to a broad range of mission requirements with minimum impact on the subsystem elements or interface designs. The effort includes development and qualification testing of new subsystem elements, the assembly and test of subsystem models to verify the physical and functional interfaces of the subsystem with other spacecraft subsystems, and the investigation of the effects of thrust subsystem operation on all aspects of spacecraft performance. The present status of this effort and some of the results so far obtained are presented.

Kerrisk, D. J.↗

LANDSAT-1 flight evaluation report

Flight performance analysis for the tenth quarter of operation orbit 11467 to 12745 of LANDSAT 1 are presented. Payload subsystems discussed include: power subsystem; attitude control subsystem; telemetry subsystem; electrical interface subsystem; narrowband tape recorders; wideband telemetry subsystem; return beam vidicon subsystem; multispectral scanner subsystem; and data collection system.

Source record↗

Comet rendezvous - The next stage in cometary exploration

NASA's Comet Rendezvous Asteroid Flyby (CRAF) mission to P/Tempel 2 is described with attention given to CRAF spacecraft design. Infrared/visible spectrometers, dust counters, magnetometers, and plasma-wave analyzers are an integral part of the CRAF payload. CRAF's subsystems consist of the following: (1) a structure subsystem, (2) a temperature control subsystem, (3) a propulsion module subsystem, (4) an attitude control subsystem, (5) a command and data subsystem, (6) a radio frequency subsystem, and (7) a power and pyrotechnics subsystem. It is concluded that the CRAF mission will enable the first detailed study of the cometary nucleus.

Collins, D. H.↗

DeMAID: A Design Manager's Aide for Intelligent Decomposition user's guide

A design problem is viewed as a complex system divisible into modules. Before the design of a complex system can begin, the couplings among modules and the presence of iterative loops is determined. This is important because the design manager must know how to group the modules into subsystems and how to assign subsystems to design teams so that changes in one subsystem will have predictable effects on other subsystems. Determining these subsystems is not an easy, straightforward process and often important couplings are overlooked. Moreover, the planning task must be repeated as new information become available or as the design specifications change. The purpose of this research is to develop a knowledge-based tool called the Design Manager's Aide for Intelligent Decomposition (DeMAID) to act as an intelligent advisor for the design manager. DeMaid identifies the subsystems of a complex design problem, orders them into a well-structured format, and marks the couplings among the subsystems to facilitate the use of multilevel tools. DeMAID also provides the design manager with the capability of examining the trade-offs between sequential and parallel processing. This type of approach could lead to a substantial savings or organizing and displaying a complex problem as a sequence of subsystems easily divisible among design teams. This report serves as a User's Guide for the program.

Rogers, James L.↗

Independent Orbiter Assessment (IOA): CIL issues resolution report, volume 1

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) are presented. This report contains IOA assessment worksheets showing resolution of outstanding IOA CIL issues that were summarized in the IOA FMEA/CIL Assessment Interim Report, dated 9 March 1988. Each assessment worksheet has been updated with CIL issue resolution and rationale. The NASA and Prime Contractor post 51-L FMEA/CIL documentation assessed is believed to be technically accurate and complete. No assessment issues remain that has safety implications. Volume 1 contain worksheets for the following sybsystems: Landing and Deceleration Subsystem; Purge, Vent and Drain Subsystem; Active Thermal Control and Life Support Systems; Crew Equipment Subsystem; Instrumentation Subsystem; Data Processing Subsystem; Atmospheric Revitalization Pressure Control Subsystem; Hydraulics and Water Spray Boiler Subsystem; and Mechanical Actuation Subsystem.

Urbanowicz, Kenneth J.↗

Independent Orbiter Assessment (IOA): CIL issues resolution report, volume 2

The results of the Independent Orbiter Assessment (IOA) of the Failure Modes And Effects Analysis (FMEA) and Critical Items List (CIL) are presented. This report contains IOA assessment worksheets showing resolution of outstanding IOA CIL issues that were summarized in the IOA FMEA/CIL Assessment Interim Report, dated 9 March 1988. Each assessment worksheet has been updated with CIL issue resolution and rationale. Volume 2 contains the worksheets for the following subsystems: Nose Wheel Steering Subsystem; Remote Manipulator Subsystem; Atmospheric Revitalization Subsystem; Extravehicular Mobility Unit Subsystem; Power Reactant Supply and Distribution Subsystem; Main Propulsion Subsystem; and Orbital Maneuvering Subsystem.

Source record↗

SDI satellite autonomy using AI and Ada

The use of Artificial Intelligence (AI) and the programming language Ada to help a satellite recover from selected failures that could lead to mission failure are described. An unmanned satellite will have a separate AI subsystem running in parallel with the normal satellite subsystems. A satellite monitoring subsystem (SMS), under the control of a blackboard system, will continuously monitor selected satellite subsystems to become alert to any actual or potential problems. In the case of loss of communications with the earth or the home base, the satellite will go into a survival mode to reestablish communications with the earth. The use of an AI subsystem in this manner would have avoided the tragic loss of the two recent Soviet probes that were sent to investigate the planet Mars and its moons. The blackboard system works in conjunction with an SMS and a reconfiguration control subsystem (RCS). It can be shown to be an effective way for one central control subsystem to monitor and coordinate the activities and loads of many interacting subsystems that may or may not contain redundant and/or fault-tolerant elements. The blackboard system will be coded in Ada using tools such as the ABLE development system and the Ada Production system.

Fiala, Harvey E.↗

Analysis of cache for streaming tape drive

A tape subsystem consists of a controller and a tape drive. Tapes are used for backup, data interchange, and software distribution. The backup operation is addressed. During a backup operation, data is read from disk, processed in CPU, and then sent to tape. The processing speeds of a disk subsystem, CPU, and a tape subsystem are likely to be different. A powerful CPU can read data from a fast disk, process it, and supply the data to the tape subsystem at a faster rate than the tape subsystem can handle. On the other hand, a slow disk drive and a slow CPU may not be able to supply data fast enough to keep a tape drive busy all the time. The backup process may supply data to tape drive in bursts. Each burst may be followed by an idle period. Depending on the nature of the file distribution in the disk, the input stream to the tape subsystem may vary significantly during backup. To compensate for these differences and optimize the utilization of a tape subsystem, a cache or buffer is introduced in the tape controller. Most of the tape drives today are streaming tape drives. A streaming tape drive goes into reposition when there is no data from the controller. Once the drive goes into reposition, the controller can receive data, but it cannot supply data to the tape drive until the drive completes its reposition. A controller can also receive data from the host and send data to the tape drive at the same time. The relationship of cache size, host transfer rate, drive transfer rate, reposition, and ramp up times for optimal performance of the tape subsystem are investigated. Formulas developed will also show the advantages of cache watermarks to increase the streaming time of the tape drive, maximum loss due to insufficient cache, tradeoffs between cache and reposition times and the effectiveness of cache on a streaming tape drive due to idle times or interruptions due in host transfers. Several mathematical formulas are developed to predict the performance of the tape drive. Some examples are given illustrating the usefulness of these formulas. Finally, a summary and some conclusions are provided.

Chinnaswamy, V.↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASAs Space Launch System

The engineering development of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS) requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The nominal and off-nominal characteristics of SLS's elements and subsystems must be understood and matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex systems engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model-based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model-based algorithms and their development lifecycle from inception through FSW certification are an important focus of SLS's development effort to further ensure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. To test and validate these M&FM algorithms a dedicated test-bed was developed for full Vehicle Management End-to-End Testing (VMET). For addressing fault management (FM) early in the development lifecycle for the SLS program, NASA formed the M&FM team as part of the Integrated Systems Health Management and Automation Branch under the Spacecraft Vehicle Systems Department at the Marshall Space Flight Center (MSFC). To support the development of the FM algorithms, the VMET developed by the M&FM team provides the ability to integrate the algorithms, perform test cases, and integrate vendor-supplied physics-based launch vehicle (LV) subsystem models. Additionally, the team has developed processes for implementing and validating the M&FM algorithms for concept validation and risk reduction. The flexibility of the VMET capabilities enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS, GNC, and others. One of the principal functions of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software test and validation processes. In any software development process there is inherent risk in the interpretation and implementation of concepts from requirements and test cases into flight software compounded with potential human errors throughout the development and regression testing lifecycle. Risk reduction is addressed by the M&FM group but in particular by the Analysis Team working with other organizations such as S&MA, Structures and Environments, GNC, Orion, Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission (LOM) and Loss of Crew (LOC) probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses to be tested in VMET to ensure reliable failure detection, and confirm responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - the ARINC 6535-partitioned Operating System, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by FSW. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure their effectiveness and performance in the exterior FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗

Alssat Development Status and Its Applications in Trade Studies

The development of the Advanced Life Support (ALS) Sizing Analysis Tool (ALSSAT) using Microsoft® Excel was initiated by the Crew and Thermal Systems Division (CTSD) of Johnson Space Center (JSC) in 1997 to support the ALS and Exploration Offices in Environmental Control and Life Support System (ECLSS) design and studies. It aids the user in performing detailed sizing of the ECLSS based on suggested default values or user inputs for different combinations of the ALS regenerative system technologies (Ref. 1, 2). This analysis tool will assist the user in performing ECLSS preliminary design and trade studies as well as system optimization efficiently and economically. Since ALSSAT's latest publication in ICES 2001 (Ref. 1) describing the development of ALSSAT with its Air Revitalization Subsystem (ARS), Water Management Subsystem (WMS), and Biomass Subsystem (Biomass) mass balance sheets, ALSSAT has been expanded to include mass balance and sizing models for the remaining three ALS subsystems, namely, the Solid Waste Management Subsystem (SWMS), the Food Management Subsystem (FMS), and the Thermal Control Subsystem (TCS). The external interfaces, including the Extravehicular Activities (EVA) and Human Accommodations (HA), were implemented into ALSSAT in 2002. The overall mass balance sheet, which integrates the six ALS subsystems and the external interfaces applicable to the ECLSS, was also developed. In 2003, ALSSAT was upgraded to include the consideration of redundancy and contingency options in the ECLSS, as well as more ALS regenerative technology selections. ALSSAT has been used for the Metric Calculation for FY02 and FY03 (Ref. 3). Several trade studies were conducted in 2003. The analytical results will be presented in this paper.

Yeh, H. Y. (Jannivine)↗