Engineering Papers⌕ Search

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.

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

At least 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

The Wettzell System Monitoring Concept and First Realizations

Automated monitoring of operational system parameters for the geodetic space techniques is becoming more important in order to improve the geodetic data and to ensure the safety and stability of automatic and remote-controlled observations. Therefore, the Wettzell group has developed the system monitoring software, SysMon, which is based on a reliable, remotely-controllable hardware/software realization. A multi-layered data logging system based on a fanless, robust industrial PC with an internal database system is used to collect data from several external, serial, bus, or PCI-based sensors. The internal communication is realized with Remote Procedure Calls (RPC) and uses generative programming with the interface software generator idl2rpc.pl developed at Wettzell. Each data monitoring stream can be configured individually via configuration files to define the logging rates or analog-digital-conversion parameters. First realizations are currently installed at the new laser ranging system at Wettzell to address safety issues and at the VLBI station O Higgins as a meteorological data logger. The system monitoring concept should be realized for the Wettzell radio telescope in the near future.

Ettl, Martin↗
NASA NTRS2008

Reconfigurable HIL Testing of Earth Satellites

In recent years, hardware-in-the-loop (HIL) testing has carved a strong niche in several industries, such as automotive, aerospace, telecomm, and consumer electronics. As desktop computers have realized gains in speed, memory size, and data storage capacity, hardware/software platforms have evolved into high performance, deterministic HIL platforms, capable of hosting the most demanding applications for testing components and subsystems. Using simulation software to emulate the digital and analog I/O signals of system components, engineers of all disciplines can now test new systems in realistic environments to evaluate their function and performance prior to field deployment. Within the Aerospace industry, space-borne satellite systems are arguably some of the most demanding in terms of their requirement for custom engineering and testing. Typically, spacecraft are built one or few at a time to fulfill a space science or defense mission. In contrast to other industries that can amortize the cost of HIL systems over thousands, even millions of units, spacecraft HIL systems have been built as one-of-a-kind solutions, expensive in terms of schedule, cost, and risk, to assure satellite and spacecraft systems reliability. The focus of this paper is to present a new approach to HIL testing for spacecraft systems that takes advantage of a highly flexible hardware/software architecture based on National Instruments PXI reconfigurable hardware and virtual instruments developed using LabVIEW. This new approach to HIL is based on a multistage/multimode spacecraft bus emulation development model called Reconfigurable Hardware In-the-Loop or RHIL.

Source record↗
NASA NTRS2007

Assurance of Complex Electronics. What Path Do We Take?

Many of the methods used to develop software bare a close resemblance to Complex Electronics (CE) development. CE are now programmed to perform tasks that were previously handled in software, such as communication protocols. For instance, Field Programmable Gate Arrays (FPGAs) can have over a million logic gates while system-on-chip (SOC) devices can combine a microprocessor, input and output channels, and sometimes an FPGA for programmability. With this increased intricacy, the possibility of "software-like" bugs such as incorrect design, logic, and unexpected interactions within the logic is great. Since CE devices are obscuring the hardware/software boundary, we propose that mature software methodologies may be utilized with slight modifications to develop these devices. By using standardized S/W Engineering methods such as checklists, missing requirements and "bugs" can be detected earlier in the development cycle, thus creating a development process for CE that will be easily maintained and configurable based on the device used.

FROM↗
NASA NTRS2007

Software Process Assurance for Complex Electronics

Complex Electronics (CE) now perform tasks that were previously handled in software, such as communication protocols. Many methods used to develop software bare a close resemblance to CE development. Field Programmable Gate Arrays (FPGAs) can have over a million logic gates while system-on-chip (SOC) devices can combine a microprocessor, input and output channels, and sometimes an FPGA for programmability. With this increased intricacy, the possibility of software-like bugs such as incorrect design, logic, and unexpected interactions within the logic is great. With CE devices obscuring the hardware/software boundary, we propose that mature software methodologies may be utilized with slight modifications in the development of these devices. Software Process Assurance for Complex Electronics (SPACE) is a research project that used standardized S/W Assurance/Engineering practices to provide an assurance framework for development activities. Tools such as checklists, best practices and techniques were used to detect missing requirements and bugs earlier in the development cycle creating a development process for CE that was more easily maintained, consistent and configurable based on the device used.

Plastow, Richard A.↗
NASA NTRS2007

Software Process Assurance for Complex Electronics (SPACE)

Complex Electronics (CE) are now programmed to perform tasks that were previously handled in software, such as communication protocols. Many of the methods used to develop software bare a close resemblance to CE development. For instance, Field Programmable Gate Arrays (FPGAs) can have over a million logic gates while system-on-chip (SOC) devices can combine a microprocessor, input and output channels, and sometimes an FPGA for programmability. With this increased intricacy, the possibility of software-like bugs such as incorrect design, logic, and unexpected interactions within the logic is great. Since CE devices are obscuring the hardware/software boundary, we propose that mature software methodologies may be utilized with slight modifications in the development of these devices. Software Process Assurance for Complex Electronics (SPACE) is a research project that looks at using standardized S/W Assurance/Engineering practices to provide an assurance framework for development activities. Tools such as checklists, best practices and techniques can be used to detect missing requirements and bugs earlier in the development cycle creating a development process for CE that will be more easily maintained, consistent and configurable based on the device used.

Plastow, Richard A.↗
NASA NTRS1992

Virtual environment display for a 3D audio room simulation

The development of a virtual environment simulation system integrating a 3D acoustic audio model with an immersive 3D visual scene is discussed. The system complements the acoustic model and is specified to: allow the listener to freely move about the space, a room of manipulable size, shape, and audio character, while interactively relocating the sound sources; reinforce the listener's feeling of telepresence in the acoustical environment with visual and proprioceptive sensations; enhance the audio with the graphic and interactive components, rather than overwhelm or reduce it; and serve as a research testbed and technology transfer demonstration. The hardware/software design of two demonstration systems, one installed and one portable, are discussed through the development of four iterative configurations.

Chapin, William L.↗
NASA NTRS1985

A high-speed, large-capacity, 'jukebox' optical disk system

Two optical disk 'jukebox' mass storage systems which provide access to any data in a store of 10 to the 13th bits (1250G bytes) within six seconds have been developed. The optical disk jukebox system is divided into two units, including a hardware/software controller and a disk drive. The controller provides flexibility and adaptability, through a ROM-based microcode-driven data processor and a ROM-based software-driven control processor. The cartridge storage module contains 125 optical disks housed in protective cartridges. Attention is given to a conceptual view of the disk drive unit, the NASA optical disk system, the NASA database management system configuration, the NASA optical disk system interface, and an open systems interconnect reference model.

Ammon, G. J.↗
NASA NTRS1987

Tethered satellite system

The Tethered Satellite System (TSS) will operate from the Space Shuttle as an earth-orbiting facility that will permit tethered deployment of numerous types of payloads to altitudes both above and below that of the Shuttle. The TSS has evolved from initial studies, beginning in the sixties, to a cooperative development program that is currently being carried out by NASA and the National Space Plan of Italy's CNR. This cooperative agreement between NASA and CNR includes system development and science instrumentation for the first mission, and planning for two additional missions. This paper will (1) discuss predevelopment activities, (2) review the development approach and management relationships between NASA and CNR, (3) describe the current hardware/software configuration and functional interfaces, (4) discuss the mission profile and flight operations planning, and (5) overview science experiment status/plans for the first TSS mission.

Laue, Jay H.↗
NASA NTRS1993

Cooperative GN&C development in a rapid prototyping environment

The Navigation, Control and Aeronautics Division (NCAD) at NASA-JSC is exploring ways of producing Guidance, Navigation and Control (GN&C) flight software faster, better, and cheaper. To achieve these goals NCAD established two hardware/software facilities that take an avionics design project from initial inception through high fidelity real-time hardware-in-the-loop testing. Commercially available software products are used to develop the GN&C algorithms in block diagram form and then automatically generate source code from these diagrams. A high fidelity real-time hardware-in-the-loop laboratory provides users with the capability to analyze mass memory usage within the targeted flight computer, verify hardware interfaces, conduct system level verification, performance, acceptance testing, as well as mission verification using reconfigurable and mission unique data. To evaluate these concepts and tools, NCAD embarked on a project to build a real-time 6 DOF simulation of the Soyuz Assured Crew Return Vehicle flight software. To date, a productivity increase of 185 percent has been seen over traditional NASA methods for developing flight software.

Bordano, Aldo↗
NASA NTRS1984

Level of effort

The generation of a planar model of the ground test experiment structure is examined. This was done by adapting an in-house modal analysis code (Gimbalflex) to allow placement of sensors and actuators at certain locations on the structure. The next step in the development of this model was to adapt if for use with the control pole placement algorithm. The uncontrollable rigid body mode was removed from the model. This uncontrollable mode was due to the pointing of the gimbal. Control system design for the planar model was also initiated. A digital controller was planned utilizing the Control Pole Placement technique. The existence of rate of state feedback was assumed. Once this controller and other control algorithms were developed, it became necessary to conduct speed tests. A study was then made of additional hardware/software necessary to meet the speed requirement.

Source record↗
NASA NTRS2004

Case Study of Risk Mitigation Based on Hardware/Software Integration (HSI) Testing for the International Space Station (ISS) Node 2 Module

Within the pressurized elements of the International Space Station (ISS), requirements exist to ensure a safe, habitable environment for the crew. In order to provide this environment, thermal control components work in conjunction with software controls to provide heat rejection for subsystem avionics equipment, for the environmental control system and for experiment payloads. It is essential to ISS operations, mission success and crew safety that necessary testing incorporates the extreme conditions to ensure proper performance. This paper provides a general description and methodology applied to thermal related Hardware/Software Integration (HSI) tests for the ISS Node 2 module. A detailed test plan was developed and implemented with two objectives: the first was for risk mitigation of the thermal control algorithms and software qualification, and the second was for data collection which will substantiate thermalhydraulic models of the Internal Active Thermal Control System (IATCS). Analytical models are utilized to determine on-orbit performance for conditions and scenarios where the simulation of actual on-orbit system performance is limited by test configuration constraints. Node 2 IATCS HSI activities were performed at the Alenia Spazio facility in Torino, Italy with participation from the National Aeronautics and Space Administration (NASA), Alenia Spazio, Jacobs Engineering Sverdrup (JE Sverdrup) and Boeing.

Holt, James Mike↗
NASA NTRS1987

Shuttle orbit flight control design lessons - Direction for Space Station

The Space Shuttle orbit flight control system, which operates during all exo-atmospheric flight phases, has successfully met operational requirements. Many design integration and operational issues that required resolution during development and testing provide an experience base that will benefit the development of future space systems, particularly the Space Station. To this end, the applicable Shuttle and Space Station hardware/software is reviewed with some perspective provided on how current design groundrules were derived and how issues that affected the Shuttle orbit control system design are a pathway for the Space Station. Some of the most significant lessons learned from the Shuttle are summarized, with a discussion of the effect of performance and design of hardware, including the data processing system on software structures and usage procedures. Crew interface issues and important results from man-in-the-loop tests are summarized. Problems resulting from trying to meet difficult orbital operational objectives, including some sophisticated payload operations are characterized. Several proposed Shuttle flight control design improvements, developed in response to some of the lessons learned so far, are identified. Potential application of the Shuttle design lessons and new control technologies to the Space Station are discussed.

Cox, Kenneth J.↗
NASA NTRS1991

The role of reliability graph models in assuring dependable operation of complex hardware/software systems

The complexity of computer systems currently being designed for critical applications in the scientific, commercial, and military arenas requires the development of new techniques for utilizing models of system behavior in order to assure 'ultra-dependability'. The complexity of these systems, such as Space Station Freedom and the Air Traffic Control System, stems from their highly integrated designs containing both hardware and software as critical components. Reliability graph models, such as fault trees and digraphs, are used frequently to model hardware systems. Their applicability for software systems has also been demonstrated for software safety analysis and the analysis of software fault tolerance. This paper discusses further uses of graph models in the design and implementation of fault management systems for safety critical applications.

Patterson-Hine, F. A.↗
NASA NTRS2010

Heritage and Advanced Technology Systems Engineering Lessons Learned from NASA Deep Space Missions

In the design and development of complex spacecraft missions, project teams frequently assume the use of advanced technology systems or heritage systems to enable a mission or reduce the overall mission risk and cost. As projects proceed through the development life cycle, increasingly detailed knowledge of the advanced and heritage systems within the spacecraft and mission environment identifies unanticipated technical issues. Resolving these issues often results in cost overruns and schedule impacts. The National Aeronautics and Space Administration (NASA) Discovery & New Frontiers (D&NF) Program Office at Marshall Space Flight Center (MSFC) recently studied cost overruns and schedule delays for 5 missions. The goal was to identify the underlying causes for the overruns and delays, and to develop practical mitigations to assist the D&NF projects in identifying potential risks and controlling the associated impacts to proposed mission costs and schedules. The study found that optimistic hardware/software inheritance and technology readiness assumptions caused cost and schedule growth for four of the five missions studied. The cost and schedule growth was not found to result from technical hurdles requiring significant technology development. The projects institutional inheritance and technology readiness processes appear to adequately assess technology viability and prevent technical issues from impacting the final mission success. However, the processes do not appear to identify critical issues early enough in the design cycle to ensure project schedules and estimated costs address the inherent risks. In general, the overruns were traceable to: an inadequate understanding of the heritage system s behavior within the proposed spacecraft design and mission environment; an insufficient level of development experience with the heritage system; or an inadequate scoping of the system-wide impacts necessary to implement an advanced technology for space flight applications. The paper summarizes the study's lessons learned in more detail and offers suggestions for improving the project's ability to identify and manage the technology and heritage risks inherent in the design solution.

Barley, Bryan↗
NASA NTRS2010

Heritage Systems Engineering Lessons from NASA Deep Space Missions

In the design and development of complex spacecraft missions, project teams frequently assume the use of advanced technology systems or heritage systems to enable a mission or reduce the overall mission risk and cost. As projects proceed through the development life cycle, increasingly detailed knowledge of the advanced and heritage systems within the spacecraft and mission environment identifies unanticipated technical issues. Resolving these issues often results in cost overruns and schedule impacts. The National Aeronautics and Space Administration (NASA) Discovery & New Frontiers (D&NF) Program Office at Marshall Space Flight Center (MSFC) recently studied cost overruns and schedule delays for 5 missions. The goal was to identify the underlying causes for the overruns and delays, and to develop practical mitigations to assist the D&NF projects in identifying potential risks and controlling the associated impacts to proposed mission costs and schedules. The study found that optimistic hardware/software inheritance and technology readiness assumptions caused cost and schedule growth for all five missions studied. The cost and schedule growth was not found to be the result of technical hurdles requiring significant technology development. The projects institutional inheritance and technology readiness processes appear to adequately assess technology viability and prevent technical issues from impacting the final mission success. However, the processes do not appear to identify critical issues early enough in the design cycle to ensure project schedules and estimated costs address the inherent risks. In general, the overruns were traceable to: an inadequate understanding of the heritage system s behavior within the proposed spacecraft design and mission environment; an insufficient level of development experience with the heritage system; or an inadequate scoping of the systemwide impacts necessary to implement an advanced technology for space flight applications. The paper summarizes the study s lessons learned in more detail and offers suggestions for improving the project s ability to identify and manage the technology and heritage risks inherent in the design solution.

Barley, Bryan↗
NASA NTRS1980

Computer controlled tooling for Space Shuttle external tank

Implementation of the thermal protection system on the external tank used with the Space Shuttle requires application of various materials over large areas, to well-defined tolerances. This paper describes a minicomputer-based system developed to control the process tooling used for this task. The process requirements and the resultant hardware/software system are discussed. The results to date and plans for future expansion are outlined.

Meyer, R. A.↗
NASA NTRS1987

Real-time analysis of telemetry data

This paper descibes a knowledge-based system for performing real-time monitoring and analysis of telemetry data from the NASA Hubble Space Telescope (HST). In order to handle asynchronous inputs and perform in real time the system consists of three or more separate processes, which run concurrently and communicate via a message passing scheme. The data management process gathers, compresses, and scales the incoming telemetry data befoe sending it to the other tasks. The inferencing process uses the incoming data to perform a real-time analysis of the state and health of the Space Telescope. The I/O process receives telemetry monitors from the data management process, updates its graphical displays in real time, and acts as the interface to the console operator. The three processes may run on the same or different computers. This system is currently under development and is being used to monitor testcases produced by the Bass Telemetry System in the Hardware/Software Integration Facility at Lockheed Missile and Space Co. in Sunnyvale, California.

Kao, Simon A.↗
NASA NTRS1993

A fault-tolerant intelligent robotic control system

This paper describes the concept, design, and features of a fault-tolerant intelligent robotic control system being developed for space and commercial applications that require high dependability. The comprehensive strategy integrates system level hardware/software fault tolerance with task level handling of uncertainties and unexpected events for robotic control. The underlying architecture for system level fault tolerance is the distributed recovery block which protects against application software, system software, hardware, and network failures. Task level fault tolerance provisions are implemented in a knowledge-based system which utilizes advanced automation techniques such as rule-based and model-based reasoning to monitor, diagnose, and recover from unexpected events. The two level design provides tolerance of two or more faults occurring serially at any level of command, control, sensing, or actuation. The potential benefits of such a fault tolerant robotic control system include: (1) a minimized potential for damage to humans, the work site, and the robot itself; (2) continuous operation with a minimum of uncommanded motion in the presence of failures; and (3) more reliable autonomous operation providing increased efficiency in the execution of robotic tasks and decreased demand on human operators for controlling and monitoring the robotic servicing routines.

Marzwell, Neville I.↗