Applications and Experiences on Hyglac, the JPL Beowulf
(view graphs) 16 PentiumPro PCs, each with 2.5 Gbyte disk, 128 Mbyte memory, Fast Ethernet Card.
SEARCH · Engineering Papers
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.
(view graphs) 16 PentiumPro PCs, each with 2.5 Gbyte disk, 128 Mbyte memory, Fast Ethernet Card.
The valve monitoring system is a stand alone unit with network capabilities for integration into a higher level health management system. The system is designed for aiding in failure predictions of high-geared ball valves and linearly actuated valves. It performs data tracking and archiving for identifying degraded performance. The data collection types are cryogenic cycles, total cycles, inlet temperature, body temperature torsional strain, linear bonnet strain, preload position, total travel and total directional changes. Events are recorded and time stamped in accordance with the IRIG B True Time. The monitoring system is designed for use in a Class 1 Division II explosive environment. The basic configuration consists of several instrumentation sensor units and a base station. The sensor units are self contained microprocessor controlled and remotely mountable in three by three by two inches. Each unit is potted in a fire retardant substance without any cavities and limited to low operating power for maintaining safe operation in a hydrogen environment. The units are temperature monitored to safeguard against operation outside temperature limitations. Each contains 902-928 MHz band digital transmitters which meet Federal Communication Commission's requirements and are limited to a 35 foot transmission radius for preserving data security. The base-station controller correlates data from the sensor units and generates data event logs on a compact flash memory module for database uploading. The entries are also broadcast over an Ethernet network. Nitrogen purged National Electrical Manufactures Association (NEMA) Class 4 enclosures are used to house the base-station
Dual airborne imaging system networks were operated using a wireless line-of-sight telemetry system developed as part of a 2002 unmanned aerial vehicle (UAV) imaging mission over the USA s largest coffee plantation on the Hawaiian island of Kauai. A primary mission objective was the evaluation of commercial-off-the-shelf (COTS) 802.11b wireless technology for reduction of payload telemetry costs associated with UAV remote sensing missions. Predeployment tests with a conventional aircraft demonstrated successful wireless broadband connectivity between a rapidly moving airborne imaging local area network (LAN) and a fixed ground station LAN. Subsequently, two separate LANs with imaging payloads, packaged in exterior-mounted pressure pods attached to the underwing of NASA's Pathfinder-Plus UAV, were operated wirelessly by ground-based LANs over independent Ethernet bridges. Digital images were downlinked from the solar-powered aircraft at data rates of 2-6 megabits per second (Mbps) over a range of 6.5 9.5 km. An integrated wide area network enabled payload monitoring and control through the Internet from a range of ca. 4000 km during parts of the mission. The recent advent of 802.11g technology is expected to boost the system data rate by about a factor of five.
NASA-MSFC has been developing liquid metal propellant feed systems capable of delivering molten bismuth at a prescribed mass flow rate to the vaporizer of an electric thruster. The first such system was delivered to NASA-JPL as part of the Very High Isp Thruster with Anode Layer (VHITAL) program. In this system, the components pictured were placed in a vacuum chamber and heated while the control electronics were located outside the chamber. The system was successfully operated at JPL in conjunction with a propellant vaporizer, and data was obtained demonstrating a new liquid bismuth flow sensing technique developed at MSFC. The present effort is aimed at producing a feed-system for use in conjunction with a bismuth-fed Hall thruster developed by Busek Co. Developing this system is more ambitious, however, in that it is designed to self-contain all the control electronics inside the same vacuum chamber as an operating bismuth-fed thruster. Consequently, the entire system, including an on-board computer, DC-output power supplies, and a gas-pressurization electro-pneumatic regulator, must be designed to survive a vacuum environment and shielded to keep bismuth plasma from intruding on the electronics and causing a shortcircuit. In addition, the hot portions of the feed system must be thermally isolated from the electronics to avoid failure due to high heat loads. This is accomplished using a thermal protection system (TPS) consisting of multiple layers of aluminum foil. The only penetrations into the vacuum chamber are an electrically isolated (floating) 48 VDC line and a fiberoptic line. The 48 VDC provides power for operation of the power supplies and electronics co-located with the system in the vacuum chamber. The fiberoptic Ethernet connection is used to communicate user-input control commands to the on-board computer and transmit real-time data back to the external computer. The partially assembled second-generation system is shown. Before testing at Busek, a more detailed flow sensor calibration will be performed to accurately quantify the flow monitoring capabilities. This effort is funded under a Technology Innovation Program (TIP) award from NASA-MSFC's Technology Transfer office and performed under SAA8-061060.
The EXpedite the PRocessing of Experiments to Space Station or EXPRESS Rack System has provided accommodations and facilitated operations for microgravity-based research payloads for over 6 years on the International Space Station (ISS). The EXPRESS Rack accepts Space Shuttle middeck type lockers and International Subrack Interface Standard (ISIS) drawers, providing a modular-type interface on the ISS. The EXPRESS Rack provides 28Vdc power, Ethernet and RS-422 data interfaces, thermal conditioning, vacuum exhaust, and Nitrogen supply for payload use. The EXPRESS Rack system also includes payload checkout capability with a flight rack or flight rack emulator prior to launch, providing a high degree of confidence in successful operations once an-orbit. In addition, EXPRESS trainer racks are provided to support crew training of both rack systems and subrack operations. Standard hardware and software interfaces provided by the EXPRESS Rack simplify the integration processes for ISS payload development. The EXPRESS Rack is designed to accommodate multidiscipline research, allowing for the independent operation of each subrack payload within a single rack. On-orbit operations began for the EXPRESS Rack Project on April 24, 2001, with one rack operating continuously to support high-priority payloads. The other on-orbit EXPRESS Racks operate based on payload need and resource availability. Over 50 multi-discipline payloads have now been supported on-orbit by the EXPRESS Rack Program. Sustaining engineering, logistics, and maintenance functions are in place to maintain hardware, operations and provide software upgrades. Additional EXPRESS Racks are planned for launch prior to ISS completion in support of long-term operations and the planned transition of the U.S. Segment to a National Laboratory.
The Fault Detection Diagnosis and Recovery Lab (FDDR) has been developed to support development of,fault detection algorithms for the flight computer aboard the Ares I and follow-on vehicles. It consists of several workstations using Ethernet and TCP/IP to simulate communications between vehicle sensors, flight computers, and ground based support computers. Isolation of tasks between workstations was set up intentionally to limit information flow and provide a realistic simulation of communication channels within the vehicle and between the vehicle and ground station.
A document describes the Interplanetary Overlay Networking Protocol Accelerator (IONAC) an electronic apparatus, now under development, for relaying data at high rates in spacecraft and interplanetary radio-communication systems utilizing a delay-tolerant networking protocol. The protocol includes provisions for transmission and reception of data in bundles (essentially, messages), transfer of custody of a bundle to a recipient relay station at each step of a relay, and return receipts. Because of limitations on energy resources available for such relays, data rates attainable in a conventional software implementation of the protocol are lower than those needed, at any given reasonable energy-consumption rate. Therefore, a main goal in developing the IONAC is to reduce the energy consumption by an order of magnitude and the data-throughput capability by two orders of magnitude. The IONAC prototype is a field-programmable gate array that serves as a reconfigurable hybrid (hardware/ firmware) system for implementation of the protocol. The prototype can decode 108,000 bundles per second and encode 100,000 bundles per second. It includes a bundle-cache static randomaccess memory that enables maintenance of a throughput of 2.7Gb/s, and an Ethernet convergence layer that supports a duplex throughput of 1Gb/s.
Firmware for implementing a digital phasemeter within a field-programmable gate array (FPGA) has been devised. In the original application of this firmware, the phase that one seeks to measure is the difference between the phases of two nominally-equal-frequency heterodyne signals generated by two interferometers. In that application, zero-crossing detectors convert the heterodyne signals to trains of rectangular pulses, the two pulse trains are fed to a fringe counter (the major part of the phasemeter) controlled by a clock signal having a frequency greater than the heterodyne frequency, and the fringe counter computes a time-averaged estimate of the difference between the phases of the two pulse trains. The firmware also does the following: Causes the FPGA to compute the frequencies of the input signals; Causes the FPGA to implement an Ethernet (or equivalent) transmitter for readout of phase and frequency values; and Provides data for use in diagnosis of communication failures. The readout rate can be set, by programming, to a value between 250 Hz and 1 kHz. Network addresses can be programmed by the user.
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.
Using a commercial software CD and minimal up-mass, SNFM monitors the Payload local area network (LAN) to analyze and troubleshoot LAN data traffic. Validating LAN traffic models may allow for faster and more reliable computer networks to sustain systems and science on future space missions. Research Summary: This experiment studies the function of the computer network onboard the ISS. On-orbit packet statistics are captured and used to validate ground based medium rate data link models and enhance the way that the local area network (LAN) is monitored. This information will allow monitoring and improvement in the data transfer capabilities of on-orbit computer networks. The Serial Network Flow Monitor (SNFM) experiment attempts to characterize the network equivalent of traffic jams on board ISS. The SNFM team is able to specifically target historical problem areas including the SAMS (Space Acceleration Measurement System) communication issues, data transmissions from the ISS to the ground teams, and multiple users on the network at the same time. By looking at how various users interact with each other on the network, conflicts can be identified and work can begin on solutions. SNFM is comprised of a commercial off the shelf software package that monitors packet traffic through the payload Ethernet LANs (local area networks) on board ISS.
A prototype wireless data-acquisition system has been developed as a potential replacement for a wired data-acquisition system heretofore used in testing rocket engines. The traditional use of wires to connect sensors, signal-conditioning circuits, and data acquisition circuitry is time-consuming and prone to error, especially when, as is often the case, many sensors are used in a test. The system includes one master and multiple slave nodes. The master node communicates with a computer via an Ethernet connection. The slave nodes are powered by rechargeable batteries and are packaged in weatherproof enclosures. The master unit and each of the slave units are equipped with a time-modulated ultra-wide-band (TMUWB) radio transceiver, which spreads its RF energy over several gigahertz by transmitting extremely low-power and super-narrow pulses. In this prototype system, each slave node can be connected to as many as six sensors: two sensors can be connected directly to analog-to-digital converters (ADCs) in the slave node and four sensors can be connected indirectly to the ADCs via signal conditioners. The maximum sampling rate for streaming data from any given sensor is about 5 kHz. The bandwidth of one channel of the TM-UWB radio communication system is sufficient to accommodate streaming of data from five slave nodes when they are fully loaded with data collected through all possible sensor connections. TM-UWB radios have a much higher spatial capacity than traditional sinusoidal wave-based radios. Hence, this TM-UWB wireless data-acquisition can be scaled to cover denser sensor setups for rocket engine test stands. Another advantage of TM-UWB radios is that it will not interfere with existing wireless transmission. The maximum radio-communication range between the master node and a slave node for this prototype system is about 50 ft (15 m) when the master and slave transceivers are equipped with small dipole antennas. The range can be increased by changing to larger antennas and/or greater transmission power. The battery life of a slave node ranges from about six hours during operation at full capacity to as long as three days when the system is in a "sleep" mode used to conserve battery charge during times between setup and rocket-engine testing. Batteries can be added to prolong operational lifetimes. The radio transceiver dominates the power consumption.
Topics covered include: Cryogenic Flow Sensor; Multi-Sensor Mud Detection; Gas Flow Detection System; Mapping Capacitive Coupling Among Pixels in a Sensor Array; Fiber-Based Laser Transmitter for Oxygen A-Band Spectroscopy and Remote Sensing; Low-Profile, Dual-Wavelength, Dual-Polarized Antenna; Time-Separating Heating and Sensor Functions of Thermistors in Precision Thermal Control Applications; Cellular Reflectarray Antenna; A One-Dimensional Synthetic-Aperture Microwave Radiometer; Electrical Switching of Perovskite Thin-Film Resistors; Two-Dimensional Synthetic-Aperture Radiometer; Ethernet-Enabled Power and Communication Module for Embedded Processors; Electrically Variable Resistive Memory Devices; Improved Attachment in a Hybrid Inflatable Pressure Vessel; Electrostatic Separator for Beneficiation of Lunar Soil; Amorphous Rover; Space-Frame Antenna; Gear-Driven Turnbuckle Actuator; In-Situ Focusing Inside a Thermal Vacuum Chamber; Space-Frame Lunar Lander; Wider-Opening Dewar Flasks for Cryogenic Storage; Silicon Oxycarbide Aerogels for High-Temperature Thermal Insulation; Supercapacitor Electrolyte Solvents with Liquid Range Below -80 C; Designs and Materials for Better Coronagraph Occulting Masks; Fuel-Cell-Powered Vehicle with Hybrid Power Management; Fine-Water-Mist Multiple-Orientation-Discharge Fire Extinguisher; Fuel-Cell Water Separator; Turbulence and the Stabilization Principle; Improved Cloud Condensation Nucleus Spectrometer; Better Modeling of Electrostatic Discharge in an Insulator; Sub-Aperture Interferometers; Terahertz Mapping of Microstructure and Thickness Variations; Multiparallel Three-Dimensional Optical Microscopy; Stabilization of Phase of a Sinusoidal Signal Transmitted Over Optical Fiber; Vacuum-Compatible Wideband White Light and Laser Combiner Source System; Optical Tapers as White-Light WGM Resonators; EPR Imaging at a Few Megahertz Using SQUID Detectors; Reducing Field Distortion in Magnetic Resonance Imaging; Fluorogenic Cell-Based Biosensors for Monitoring Microbes; A Constant-Force Resistive Exercise Unit; GUI to Facilitate Research on Biological Damage from Radiation; On-Demand Urine Analyzer; More-Realistic Digital Modeling of a Human Body; and Advanced Liquid-Cooling Garment Using Highly Thermally Conductive Sheets.
Advancements in technology have allowed the miniaturization of systems used in aerospace vehicles. This technology is driven by the need for next-generation systems that provide reliable, responsive, and cost-effective range operations while providing increased capabilities such as simultaneous mission support, increased launch trajectories, improved launch, and landing opportunities, etc. Leveraging the newest technologies, the command and telemetry processor (CTP) concept provides for a compact, flexible, and integrated solution for flight command and telemetry systems and range systems. The CTP is a relatively small circuit board that serves as a processing platform for high dynamic, high vibration environments. The CTP can be reconfigured and reprogrammed, allowing it to be adapted for many different applications. The design is centered around a configurable field-programmable gate array (FPGA) device that contains numerous logic cells that can be used to implement traditional integrated circuits. The FPGA contains two PowerPC processors running the Vx-Works real-time operating system and are used to execute software programs specific to each application. The CTP was designed and developed specifically to provide telemetry functions; namely, the command processing, telemetry processing, and GPS metric tracking of a flight vehicle. However, it can be used as a general-purpose processor board to perform numerous functions implemented in either hardware or software using the FPGA s processors and/or logic cells. Functionally, the CTP was designed for range safety applications where it would ultimately become part of a vehicle s flight termination system. Consequently, the major functions of the CTP are to perform the forward link command processing, GPS metric tracking, return link telemetry data processing, error detection and correction, data encryption/ decryption, and initiate flight termination action commands. Also, the CTP had to be designed to survive and operate in a launch environment. Additionally, the CTP was designed to interface with the WFF (Wallops Flight Facility) custom-designed transceiver board which is used in the Low Cost TDRSS Transceiver (LCT2) also developed by WFF. The LCT2 s transceiver board demodulates commands received from the ground via the forward link and sends them to the CTP, where they are processed. The CTP inputs and processes data from the inertial measurement unit (IMU) and the GPS receiver board, generates status data, and then sends the data to the transceiver board where it is modulated and sent to the ground via the return link. Overall, the CTP has combined processing with the ability to interface to a GPS receiver, an IMU, and a pulse code modulation (PCM) communication link, while providing the capability to support common interfaces including Ethernet and serial interfaces boarding a relatively small-sized, lightweight package.
Features: Hardware: a) Xilinx Virtex-5 (GSFC Space Cube 2); b) 2 x 400MHz PPC; c) 100MHz Bus; d) 2 x 512MB SDRAM; e) Dual Gigabit Ethernet. Support Linux kernel 2.6.31 (gcc version 4.2.2). Support software running in stand alone mode for better performance. Can stream raw data up to 800 Mbps. Ready for operations. Software Application Examples: Band-stripping Algiotrhmsl:cloud, sulfur, flood, thermal, SWIL, NDVI, NDWI, SIWI, oil spills, algae blooms, etc. Corrections: geometric, radiometric, atmospheric. Core Flight System/dynamic software bus. CCSDS File Delivery Protocol. Delay Tolerant Network. CASPER /onboard planning. Fault monitoring/recovery software. S/C command and telemetry software. Data compression. Sensor Web for Autonomous Mission Operations.
At the Kennedy Space Center, I engaged in the research and development of electrical ground support equipment for NASA's Constellation Program. Timing characteristics playa crucial role in ground support communications. Latency and jitter are two problems that must be understood so that communications are timely and consistent within the Kennedy Ground Control System (KGCS). I conducted latency and jitter tests using Alien-Bradley programmable logic controllers (PLCs) so that these two intrinsic network properties can be reduced. Time stamping and clock synchronization also play significant roles in launch processing and operations. Using RSLogix 5000 project files and Wireshark network protocol analyzing software, I verified master/slave PLC Ethernet module clock synchronization, master/slave IEEE 1588 communications, and time stamping capabilities. All of the timing and synchronization test results are useful in assessing the current KGCS operational level and determining improvements for the future.
During the Genesis and Rapid Intensification Processes (GRIP) field program, a system of 6 electric field mills was flown on one of NASA's Global Hawk aircraft. We placed several mills on the aircraft to enable us to measure the vector electric field. We created a distributed, ethernet-connected system so that each sensor has its own embedded Linux system, complete with web server. This makes our current generation system fully "sensor web enabled." The Global Hawk has several unique qualities, but relevant to quality storm electric field measurements are high altitude (20 km) and long duration (20-30 hours) flights. There are several aircraft participating in the GRIP program, and coordinated measurements are happening. Lightning and electric field measurements will be used to study the relationships between lightning and other storm characteristics. It has been long understood that lightning can be used as a marker for strong convective activity. Past research and field programs suggest that lightning flash rate may serve as an indicator and precursor for rapid intensification change in tropical cyclones and hurricanes. We have the opportunity to sample hurricanes for many hours at a time and observe intensification (or de-intensification) periods. The electrical properties of hurricanes during such periods are not well known. American
NASA in collaboration with a number of partners conducted a set of individual experiments and demonstrations during SC 10 that collectively were titled "Using 100G Network Technology in Support of Petascale Science". The partners included the iCAIR, Internet2, LAC, MAX, National LambdaRail (NLR), NOAA and SCinet Research Sandbox (SRS) as well as the vendors Ciena, Cisco, ColorChip, cPacket, Extreme Networks, Fusion-io, HP and Panduit who most generously allowed some of their leading edge 40G/100G optical transport, Ethernet switch and Internet Protocol router equipment and file server technologies to be involved. The experiments and demonstrations featured different vendor-provided 40G/100G network technology solutions for full-duplex 40G and 100G LAN data flows across SRS-deployed single-node fiber-pairs among the Exhibit Booths of NASA, the National Center for Data lining, NOAA and the SCinet Network Operations Center, as well as between the NASA Exhibit Booth in New Orleans and the Starlight Communications Exchange facility in Chicago across special SC 10- only 80- and 100-Gbps wide area network links provisioned respectively by the NLR and Internet2, then on to GSFC across a 40-Gbps link. provisioned by the Mid-Atlantic Crossroads. The networks and vendor equipment were load-stressed by sets of NASA/GSFC High End Computer Network Team-built, relatively inexpensive, net-test-workstations that are capable of demonstrating greater than 100Gbps uni-directional nuttcp-enabled memory-to-memory data transfers, greater than 80-Gbps aggregate--bidirectional memory-to-memory data transfers, and near 40-Gbps uni-directional disk-to-disk file copying. This paper will summarize the background context, key accomplishments and some significances of these experiments and demonstrations.
This paper gives a description of OPC (Object Linking and Embedding for Process Control) standards for process control and outlines the experiences at JSC with using these standards to interface with I/O hardware from three independent vendors. The I/O hardware was integrated with a commercially available SCADA/HMI software package to make up the control and monitoring system for the Environmental Systems Test Stand (ESTS). OPC standards were utilized for communicating with I/O hardware and the software was used for implementing monitoring, PC-based distributed control, and redundant data storage over an Ethernet physical layer using an embedded din-rail mounted PC.