SEARCH · Engineering Papers

Results for “Hardware/Software Development”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

117 records · Page 7

All sources NASA NTRS DOE OSTI

NASA NTRS1993

GE networked mass storage solutions supporting IEEE network mass storage model

The General Electric Government Communications Systems Department (GE/GCSD) has developed a near real time digital data storage and retrieval system that extends the capabilities currently available in today's marketplace. This system called DuraStore uses commercially available rotary tape drive technology with ANSI/IEEE standards for automated magnetic tape based data storage. It uses a nonproprietary approach to satisfy a wide range of data rates and storage capabilities requirements and is compliant with the IEEE Network Storage Model. Rotary tape drives, standard interfaces, application specific hardware/software, networked automated tape libraries, library administrator, write protection, volume/physical media linkages, and maximum resource utilization are addressed.

Herzog, Donald↗

NASA NTRS1984

NASA's satellite relay tracking and data acquisition program

The Tracking and Data Acquisition System (TDAS) is currently being planned to support NASA missions and the Space Station and will serve as a replacement to the present Tracking and Data Relay Satellite System (TDRSS). Its operational date is currently projected for the late 1990s. Near term objectives involve the definition of a TDAS architecture, the development of functional and performance specifications and implementation of a TDRSS-to-TDAS transition plan. The present paper provides an overview of the baseline TDAS architecture and summarizes key ingredients of system and technology studies in progress. In particular, this paper addresses a summary of projected mission requirements for the TDAS era; a characterization of the space segment constellation; use of lasers, 60 GHz, and multibeam 30/20 GHz technologies; ground architecture and operational interfaces; a distributed hardware/software processing concept for more flexible and reliable interfaces, signal processing and operations. Also included is a status summary of the TDAS program plan for the 1984-1990 time frame. Finally, an overview is presented of NASA's current plans to augment the TDRSS to meet the Space Station IOC requirements in the time period 1993-2000.

Schwartz, J. J.↗

NASA NTRS1994

A force-controllable macro-micro manipulator and its application to medical robots

This paper describes an 8-degrees-of-freedom macro-micro robot. This robot is capable of performing tasks that require accurate force control, such as polishing, finishing, grinding, deburring, and cleaning. The design of the macro-micro mechanism, the control algorithms, and the hardware/software implementation of the algorithms are described in this paper. Initial experimental results are reported. In addition, this paper includes a discussion of medical surgery and the role that force control may play. We introduce a new class of robotic systems collectively called Robotic Enhancement Technology (RET). RET systems introduce the combination of robotic manipulation with human control to perform manipulation tasks beyond the individual capability of either human or machine. The RET class of robotic systems offers new challenges in mechanism design, control-law development, and man/machine interface design. We believe force-controllable mechanisms such as the macro-micro structure we have developed are a necessary part of RET. Work in progress in the area of RET systems and their application to minimally invasive surgery is presented, along with future research directions.

Marzwell, Neville I.↗

NASA NTRS1986

Developing tools for digital radar image data evaluation

The refinement of radar image analysis methods has led to a need for a systems approach to radar image processing software. Developments stimulated through satellite radar are combined with standard image processing techniques to create a user environment to manipulate and analyze airborne and satellite radar images. One aim is to create radar products for the user from the original data to enhance the ease of understanding the contents. The results are called secondary image products and derive from the original digital images. Another aim is to support interactive SAR image analysis. Software methods permit use of a digital height model to create ortho images, synthetic images, stereo-ortho images, radar maps or color combinations of different component products. Efforts are ongoing to integrate individual tools into a combined hardware/software environment for interactive radar image analysis.

Domik, G.↗

NASA NTRS2007

Cardiac Repolarization Abnormalities and Potential Evidence for Loss of Cardiac Sodium Currents on ECGs of Patients with Chagas' Heart Disease

Some individuals with Chagas disease develop right precordial lead ST segment elevation in response to an ajmaline challenge test, and the prevalence of right bundle branch block (RBBB) is also high in Chagas disease. Because these same electrocardiographic abnormalities occur in the Brugada syndrome, which involves genetically defective cardiac sodium channels, acquired damage to cardiac sodium channels may also occur in Chagas disease. We studied several conventional and advanced resting 12-lead/derived Frank-lead ECG parameters in 34 patients with Chagas -related heart disease (mean age 39 14 years) and in 34 age-/gender-matched healthy controls. All ECG recordings were of 5-10 min duration, obtained in the supine position using high fidelity hardware/software (CardioSoft, Houston, TX). Even after excluding those Chagas patients who had resting BBBs, tachycardia and/or pathologic arrhythmia (n=8), significant differences remained in multiple conventional and advanced ECG parameters between the Chagas and control groups (n=26/group), especially in their respective QT interval variability indices, maximal spatial QRS-T angles and low frequency HRV powers (p=0.0006, p=0.0015 and p=0.0314 respectively). In relation to the issue of potential damage to cardiac sodium channels, the Chagas patients had: 1) greater than or equal to twice the incidence of resting ST segment elevation in leads V1-V3 (n=10/26 vs. n=5/26) and of both leftward (n=5/26 versus n=0/26) and rightward (n=7/26 versus n=3/26) QRS axis deviation than controls; 2) significantly increased filtered (40-250 Hz) QRS interval durations (92.1 8.5 versus 85.3 plus or minus 9.0 ms, p=0.022) versus controls; and 3) significantly decreased QT and especially JT interval durations versus controls (QT interval: 387.5 plus or minus 26.4 versus 408.9 plus or minus 34.6 ms, p=0.013; JT interval: 290.5 plus or minus 26.3 versus 314.8 plus or minus 31.3 ms; p=0.0029). Heart rates and Bazett-corrected QTc/JTc intervals were not significantly different between groups. Patients with Chagas heart disease have increased cardiac repolarization abnormalities, especially by advanced ECG. Moreover, as a group, they have decreased uncorrected JT and QT interval durations and increased filtered QRS interval durations (versus age/gender-matched controls), all suggesting a potential loss of cardiac sodium channel function that might be mediated, in part, by cardiac autonomic damage. Overall findings support Brugada et al's recent hypothesis that the pathway leading to sudden death may often be similar in Chagas' disease and Brugada syndrome i.e., damage to the sodium channel (infectious/immunologic/autonomic in Chagas' genetic in Brugada) with consequent loss of sodium currents may facilitate a phase II-reentry based arrhythmic substrate for ventricular fibrillation in both conditions. In general, JT interval-related results have been underreported in the Chagas literature.

Schlegel, T. T.↗

NASA NTRS2012

mREST Interface Specification

mREST is an implementation of the REST architecture specific to the management and sharing of data in a system of logical elements. The purpose of this document is to clearly define the mREST interface protocol. The interface protocol covers all of the interaction between mREST clients and mREST servers. System-level requirements are not specifically addressed. In an mREST system, there are typically some backend interfaces between a Logical System Element (LSE) and the associated hardware/software system. For example, a network camera LSE would have a backend interface to the camera itself. These interfaces are specific to each type of LSE and are not covered in this document. There are also frontend interfaces that may exist in certain mREST manager applications. For example, an electronic procedure execution application may have a specialized interface for configuring the procedures. This interface would be application specific and outside of this document scope. mREST is intended to be a generic protocol which can be used in a wide variety of applications. A few scenarios are discussed to provide additional clarity but, in general, application-specific implementations of mREST are not specifically addressed. In short, this document is intended to provide all of the information necessary for an application developer to create mREST interface agents. This includes both mREST clients (mREST manager applications) and mREST servers (logical system elements, or LSEs).

McCartney, Patrick↗

NASA NTRS1998

The Design and Development of the SMEX-Lite Power System

This paper describes the design and development of a 250W orbit average electrical power system electronic Power Node and software for use in Low Earth Orbit missions. The mass of the Power Node is 3.6 Kg (8 lb.). The dimensions of the Power Node are 30cm x 26cm x 7.9cm (11 in. x 10.25 in x 3.1 in.) The design was realized using software, Field Programmable Gate Array (FPGA) digital logic and surface mount technology. The design is generic enough to reduce the non-recurring engineering for different mission configurations. The Power Node charges one to five, low cost, 22-cell 4 AH D-cell battery packs independently. The battery charging algorithms are executed in the power software to reduce the mass and size of the power electronic. The Power Node implements a peak-power tracking algorithm using an innovative hardware/software approach. The power software task is hosted on the spacecraft processor. The power software task generates a MIL-STD-1553 command packet to update the Power Node control settings. The settings for the battery voltage and current limits, as well as minimum solar array voltage used to implement peak power tracking are contained in this packet. Several advanced topologies are used in the Power Node. These include synchronous rectification in the bus regulators, average current control in the battery chargers and quasi-resonant converters for the Field Effect Transistor (FET) transistor drive electronics. Lastly, the main bus regulator uses a feed-forward topology with the PWM implemented in an FPGA.

Rakow, Glenn P.↗

NASA NTRS2015

SOAREX-8 Suborbital Experiments 2015 - A New Paradigm for Small Spacecraft Communication

In 2015 NASA plans to launch a payload to 280 Km altitude on a sounding rocket from the Wallops Flight Facility. This payload will contain several novel technologies that work together to demonstrate methodologies for space sample return missions and for nanosatellite communications in general. The payload will deploy and test an Exo-Brake, which slows the payload aerodynamically, providing eventual de-orbit and recovery of future ISS samples through a Small Payload Quick Return project. In addition, this flight addresses future Mars mission entry technology, space-to-space communications using the Iridium Short Messaging Service (SMS), GPS tracking, and wireless sensors using the ZigBee protocol. SOAREX-8 is being assembled and tested at Ames Research Center (ARC) and the NASA Engineering and Safety Center (NESC) is funding sensor and communications work. Open source Arduino technology and software are used for system control. The ZigBee modules used are XBee units that connect analog sensors for temperature, air pressure and acceleration measurement wirelessly to the payload telemetry system. Our team is developing methods for power distribution and module mounting, along with software for sensor integration, data assembly and downlink. We have demonstrated relaying telemetry to the ground using the Iridium satellite constellation on a previous flight, but the upcoming flight will be the first time we integrate useful flight test data from a ZigBee wireless sensor network. Wireless sensor data will measure the aerodynamic efficacy of the Exo-Brake permitting further on orbit flight tests of improved designs. The Exo-Brake is 5 sq m in area and will be stored in a container and deployed during ascent once the payload is jettisoned from the launch vehicle. We intend to further refine the hardware and continue testing on balloon launches, future sounding rocket flights and on nanosatellite missions. The use of standards-based and open source hardware/software has allowed for this project to be completed with a very modest budget and a challenging schedule. There is a wealth of hardware and software available for both the Arduino platform and the XBee, all low-cost or open-source. Along with the Exo-Brake hardware and deployment discussion, this paper will describe in detail the system architecture emphasizing the successful use of open source hardware and software to minimize effort and cost. Testing procedures, radio frequency interference (RFI) mitigation, success criteria and expected results will also be discussed. The use of Iridium short messaging capability for space-to-space links, standards-based wireless sensor networks, and other innovative communications technology are also presented.

aerobrake↗

NASA NTRS2013

Spaceport Processing System Development Lab

The Spaceport Processing System Development Lab (SPSDL), developed and maintained by the Systems Hardware and Engineering Branch (NE-C4), is a development lab with its own private/restricted networks. A private/restricted network is a network with restricted or no communication with other networks. This allows users from different groups to work on their own projects in their own configured environment without interfering with others utilizing their resources in the lab. The different networks being used in the lab have no way to talk with each other due to the way they are configured, so how a user configures his software, operating system, or the equipment doesn't interfere or carry over on any of the other networks in the lab. The SPSDL is available for any project in KSC that is in need of a lab environment. My job in the SPSDL was to assist in maintaining the lab to make sure it's accessible for users. This includes, but is not limited to, making sure the computers in the lab are properly running and patched with updated hardware/software. In addition to this, I also was to assist users who had issues in utilizing the resources in the lab, which may include helping to configure a restricted network for their own environment. All of this was to ensure workers were able to use the SPSDL to work on their projects without difficulty which would in turn, benefit the work done throughout KSC. When I wasn't working in the SPSDL, I would instead help other coworkers with smaller tasks which included, but wasn't limited to, the proper disposal, moving of, or search for essential equipment. I also, during the free time I had, used NASA's resources to increase my knowledge and skills in a variety of subjects related to my major as a computer engineer, particularly in UNIX, Networking, and Embedded Systems.

Systems Engineering↗