Search NASA⌕ Search

SEARCH · Search NASA

Results for “software specification”

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,387 records · Page 77

Tug rendezvous and docking with a spacecraft - A remote manned approach

The development and use of a visual simulator for remote-manned rendezvous and docking utilizing frame-by-frame, slow-scan, low-light-level TV (LLLTV) was conceived and initiated in mid-1974. The effort was limited to modification, checkout, and validation of simulator hardware specific to this task, to the development of simulation (digital computer) software, and technical support to several rendezvous and docking simulation studies. Analysis and simulation has shown that LLLTV, such as would be required for satellite inspection, could provide a suitable acquisition sensor for a remote manned rendezvous/docking subsystem. A manned, remote simulation has demonstrated its feasibility during the terminal rendezvous and docking phases. Should this approach prove fully adequate in subsequent detailed simulation studies and tests, an order-of-magnitude cost savings can be obtained for early rendezvous and docking operations.

Hurley, M. J.↗

A comparative study of the Unified System for Orbit Computation and the Flight Design System

The Flight Design System (FDS) and the Unified System for Orbit Computation (USOC) are compared and described in relation to mission planning for the shuttle transportation system (STS). The FDS is designed to meet the requirements of a standardized production tool and the USOC is designed for rapid generation of particular application programs. The main emphasis in USOC is put on adaptability to new types of missions. It is concluded that a software system having a USOC-like structure, adapted to the specific needs of MPAD, would be appropriate to support planning tasks in the area unique to STS missions.

Maag, W.↗

Simulations used in the development and flight test of the HiMAT vehicle

Real-time simulations have been essential in the flight-test program of the highly maneuverable aircraft technology (HiMAT) remotely piloted research vehicle at the Dryden Flight Research Facility of NASA Ames Research Center. The HiMAT project makes extensive use of simulations in design, development, and qualification for flight, pilot training, and flight planning. Four distinct simulations, each with varying amounts of hardware in the loop, were developed for the HiMAT project. The use of simulations has been the key to flight qualification of the HiMAT vehicle. Specifically, they are useful in detecting anomalous behavior of the flight software and hardware at the various stages of development, verification, and validation.

Evans, M. B.↗

Analytical redundancy management mechanization and flight data analysis for the F-8 digital fly-by-wire aircraft flight control sensors

The details are presented of an onboard digital computer algorithm designed to reliably detect and isolate the first failure in a duplex set of flight control sensors aboard the NASA F-8 digital fly-by-wire aircraft. The algorithm's successful flight test program is summarized, and specific examples are presented of algorithm behavior in response to software-induced signal faults, both with and without aircraft parameter modeling errors.

Deckert, J. C.↗

Calibrated Ancillary System (CAS) user's guide, volume 8

The Calibrated Ancillary System (CAS) provides real-time calibrated parameters from the orbiter downlink (ancillary data) to the Goddard Space Flight Center (GSFC). This user's guide contains the introduction to the equipment, operation, general procedures, and specific procedures of CAS. Volume 8 describes procedures for invoking checkout software, file maintenance procedures, system manager procedures.

Source record↗

Design and validation of fault-tolerant flight systems

Flight systems must be validated to show that they are consistent with the requirements of their intended applications. While high reliability is difficult to validate, the additional complexity of fault tolerance further compounds the validation problem. The objective of NASA’s research is to develop a methodology for designing validatable fault-tolerant systems. Under the design-for-validation philosophy, emphasis is placed on developing validation methods that can be incorporated into the design process right from the start and design methods and guidance which, while incorporating fault tolerance, can assure validatability. This paper examines the statistical issues of validating highly reliable, fault tolerant system. There are many problems associated with traditional methods of designing and validating these potentially complex hardware and software systems. Useful design-for-validation methods, which include structured specification and design methodologies, mathematical proof techniques, analytical modeling, simulation and emulation, and physical testing, are discussed. Important design issues associated with fault tolerance are presented along with the related validation concerns which must be addressed. Experience has shown that synchronization and Byzantine resilience must accompany fault tolerance. Other design attributes associated with fault tolerance may be used by a designer on the basis of cost, weight, performance, and validation considerations.

Computer systems↗

Experience with the CAIS

Intermetrics' experience is that the Ada package construct, which allows separation of specification and implementation allows specification of a CAIS that is transportable across varying hardware and software bases. Additionally, the CAIS is an excellent basis for providing operating system functionality to Ada applications. By allowing the Byron APSE to be moved easily from system to system, and allowing significant re-writes of underlying code. Ada and the CAIS provide portability as well as transparency to change at the application operating system interface level.

Tighe, Michael F.↗

Tubular space truss structure for SKITTER 2 robot

The Skitter 2 is a three legged transport vehicle designed to demonstrate the principle of a tripod walker in a multitude of environments. The tubular truss model of Skitter 2 is a proof of principal design. The model will replicate the operational capabilities of Skitter 2 including its ability to self-right itself. The project's focus was on the use of light weight tubular members in the final structural design. A strong design for the body was required as it will undergo the most intense loading. Triangular geometry was used extensively in the body, providing the required structural integrity and eliminating the need for cumbersome shear panels. Both the basic femur and tibia designs also relied on the strong geometry of the triangle. An intense literature search aided in the development of the most suitable weld techniques, joints, linkages, and materials required for a durable design. The hinge design features the use of spherical rod end bearings. In order to obtain a greater range of mobility in the tibia, a four-bar linkage was designed which attaches both to the femur and the tibia. All component designs, specifically the body, femur, and the tibia were optimized using the software package IDEAS 3.8A Supertab. The package provided essential deformation and stress analysis information on each component's design. The final structure incurred only a 0.0544 inch deflection in a maximum (worst case) loading situation. The highest stress experienced by any AL6061-T6 tubular member was 1920 psi. The structural integrity of the final design facilitated the use of Aluminum 6061-T6 tubing. The tubular truss structure of Skitter 2 is an effective and highly durable design. All facets of the design are structurally sound and cost effective.

Beecham, Richard↗

The NASA-IGES geometry data exchange standard

Described here are the data exchange efforts and plans supported by the NASA Steering Committee for Surface Modeling and Grid Generation. Current methods for geometry data exchange between computer aided design (CAD) systems and NASA computational fluid dynamics (CFD) analysis systems are tedious and induce errors. A Geometry Data Exchange Standard is proposed, utilizing a subset of an existing national standard titled Initial Graphic Exchange Standard (IGES). Future plans for data exchange standardization include all aspects of CFD data. Software systems to utilize this NASA-IGES Geometry Data Exchange Specification are under development.

Blake, Matthew W.↗

NASA TileWorld Simulator Program

NASA TileWorld (NTW) computer program formulated to further research on planning, scheduling, and control problems. Designed to focus on three particular attributes of real-world problems: exogenous events, uncertain outcomes of actions, and metric time. Written specifically for use by NASA, NTW modified easily to act as software base for other simulated environments. Written in Allegro Common Lisp for Sun-3-(TM) and Sun-4-series(TM) computers running SunOS(TM).

Philips, Andrew↗

Rotating rake design for unique measurement of fan-generated spinning acoustic modes

In light of the current emphasis on noise reduction in subsonic aircraft design, NASA has been actively studying the source of and propagation of noise generated by subsonic fan engines. NASA/LeRC has developed and tested a unique method of accurately measuring these spinning acoustic modes generated by an experimental fan. This mode measuring method is based on the use of a rotating microphone rake. Testing was conducted in the 9 x 15 Low-speed Wind Tunnel. The rotating rake was tested with the Advanced Ducted Propeller (ADP) model. This memorandum discusses the design and performance of the motor/drive system for the fan-synchronized rotating acoustic rake. This novel motor/drive design approach is now being adapted for additional acoustic mode studies in new test rigs as baseline data for the future design of active noise control for subsonic fan engines. Included in this memorandum are the research requirements, motor/drive specifications, test performance results, and a description of the controls and software involved.

Konno, Kevin E.↗

How well does voice interaction work in space?

The methods and results of an evaluation of the Voice Navigator software package are discussed. The first phase or ground phase of the study consisted of creating, or training, computer voice files of specific commands. This consisted of repeating each of six commands eight times. The files were then tested for recognition accuracy by the software aboard the microgravity aircraft. During the second phase, both voice training and testing were performed in microgravity. Inflight training was done due to problems encountered in phase one which were believed to be caused by ambient noise levels. Both quantitative and qualitative data were collected. Only one of the commands was found to offer consistently high recognition rates across subjects during the second phase.

Morris, Randy B.↗

Pre-Flight Dark Forward Electrical Testing of the Mir Cooperative Solar Array

The Mir Cooperative Solar Array (MCSA) was developed jointly by the United States (US) and Russia to provide approximately 6 kW of photovoltaic power to the Russian space station Mir. After final assembly in Russia, the MCSA was shipped to the NASA Kennedy Space Center (KSC) in the summer of 1995 and launched to Mir in November 1995. Program managers were concerned of the potential for MCSA damage during the transatlantic shipment and the associated handling operations. To address this concern, NASA Lewis Research Center (LERC) developed an innovative dark-forward electrical test program to assess the gross electrical condition of each generator following shipment from Russia. The use of dark test techniques, which allow the array to remain in the stowed configuration, greatly simplifies the checkout of large area solar arrays. MCSA dark electrical testing was successfully performed at KSC in July 1995 following transatlantic shipment. Data from this testing enabled engineers to quantify the effects of potential MCSA physical damage that would degrade on-orbit electrical performance. In this paper, an overview of the principles and heritage of photovoltaic array dark testing is given. The specific MCSA dark test program is also described including the hardware, software, testing procedures and test results. The current-voltage (4) response of both solar cell circuitry and by-pass diode circuitry was obtained. To guide the development of dark test hardware, software and procedures, a dedicated FORTRAN computer code was developed to predict the dark 4 responses of generators with a variety of feasible damage modes. By comparing the actual test data with the predictions, the physical condition of the generator could be inferred. Based on this data analysis, no electrical short-circuits or open-circuits were detected. This suggested the MCSA did not sustain physical damage that affected electrical performance during handling and shipment from Russia to the US. Good agreement between the test data and computational predictions indicated MCSA electrical performance was amenable to accurate analysis and was well understood.

Kerslake, Thomas W.↗

FPGA Based Reconfigurable ATM Switch Test Bed

Various issues associated with "FPGA Based Reconfigurable ATM Switch Test Bed" are presented in viewgraph form. Specific topics include: 1) Network performance evaluation; 2) traditional approaches; 3) software simulation; 4) hardware emulation; 5) test bed highlights; 6) design environment; 7) test bed architecture; 8) abstract sheared-memory switch; 9) detailed switch diagram; 10) traffic generator; 11) data collection circuit and user interface; 12) initial results; and 13) the following conclusions: Advances in FPGA make hardware emulation feasible for performance evaluation, hardware emulation can provide several orders of magnitude speed-up over software simulation; due to the complexity of hardware synthesis process, development in emulation is much more difficult than simulation and requires knowledge in both networks and digital design.

Chu, Pong P.↗

Autonomous Satellite Command and Control through the World Wide Web: Phase 3

NASA's New Millenium Program (NMP) has identified a variety of revolutionary technologies that will support orders of magnitude improvements in the capabilities of spacecraft missions. This program's Autonomy team has focused on science and engineering automation technologies. In doing so, it has established a clear development roadmap specifying the experiments and demonstrations required to mature these technologies. The primary developmental thrusts of this roadmap are in the areas of remote agents, PI/operator interface, planning/scheduling fault management, and smart execution architectures. Phases 1 and 2 of the ASSET Project (previously known as the WebSat project) have focused on establishing World Wide Web-based commanding and telemetry services as an advanced means of interfacing a spacecraft system with the PI and operators. Current automated capabilities include Web-based command submission, limited contact scheduling, command list generation and transfer to the ground station, spacecraft support for demonstrations experiments, data transfer from the ground station back to the ASSET system, data archiving, and Web-based telemetry distribution. Phase 2 was finished in December 1996. During January-December 1997 work was commenced on Phase 3 of the ASSET Project. Phase 3 is the subject of this report. This phase permitted SSDL and its project partners to expand the ASSET system in a variety of ways. These added capabilities included the advancement of ground station capabilities, the adaptation of spacecraft on-board software, and the expansion of capabilities of the ASSET management algorithms. Specific goals of Phase 3 were: (1) Extend Web-based goal-level commanding for both the payload PI and the spacecraft engineer; (2) Support prioritized handling of multiple PIs as well as associated payload experimenters; (3) Expand the number and types of experiments supported by the ASSET system and its associated spacecraft; (4) Implement more advanced resource management, modeling and fault management capabilities that integrate the space and ground segments of the space system hardware; (5) Implement a beacon monitoring test; (6) Implement an experimental blackboard controller for space system management; (7) Further define typical ground station developments required for Internet-based remote control and for full system automation of the PI-to-spacecraft link. Each of those goals is examined in the next section. Significant sections of this report were also published as a conference paper.

Cantwell, Brian↗

Autonomous Satellite Command and Control Through the World Wide Web

The Automated Space System Experimental Testbed (ASSET) system is a simple yet comprehensive real-world operations network being developed. Phase 3 of the ASSET Project was January-December 1997 and is the subject of this report. This phase permitted SSDL and its project partners to expand the ASSET system in a variety of ways. These added capabilities included the advancement of ground station capabilities, the adaptation of spacecraft on-board software, and the expansion of capabilities of the ASSET management algorithms. Specific goals of Phase 3 were: (1) Extend Web-based goal-level commanding for both the payload PI and the spacecraft engineer. (2) Support prioritized handling of multiple (PIs) Principle Investigators as well as associated payload experimenters. (3) Expand the number and types of experiments supported by the ASSET system and its associated spacecraft. (4) Implement more advanced resource management, modeling and fault management capabilities that integrate the space and ground segments of the space system hardware. (5) Implement a beacon monitoring test. (6) Implement an experimental blackboard controller for space system management. (7) Further define typical ground station developments required for Internet-based remote control and for full system automation of the PI-to-spacecraft link. Each of those goals are examined. Significant sections of this report were also published as a conference paper. Several publications produced in support of this grant are included as attachments. Titles include: 1) Experimental Initiatives in Space System Operations; 2) The ASSET Client Interface: Balancing High Level Specification with Low Level Control; 3) Specifying Spacecraft Operations At The Product/Service Level; 4) The Design of a Highly Configurable, Reusable Operating System for Testbed Satellites; 5) Automated Health Operations For The Sapphire Spacecraft; 6) Engineering Data Summaries for Space Missions; and 7) Experiments In Automated Health Assessment And Notification For The Sapphire Microsatellite.

Cantwell, Brian↗

A Flexible Statechart-to-Model-Checker Translator

Many current-day software design tools offer some variant of statechart notation for system specification. We, like others, have built an automatic translator from (a subset of) statecharts to a model checker, for use to validate behavioral requirements. Our translator is designed to be flexible. This allows us to quickly adjust the translator to variants of statechart semantics, including problem-specific notational conventions that designers employ. Our system demonstration will be of interest to the following two communities: (1) Potential end-users: Our demonstration will show translation from statecharts created in a commercial UML tool (Rational Rose) to Promela, the input language of Holzmann's model checker SPIN. The translation is accomplished automatically. To accommodate the major variants of statechart semantics, our tool offers user-selectable choices among semantic alternatives. Options for customized semantic variants are also made available. The net result is an easy-to-use tool that operates on a wide range of statechart diagrams to automate the pathway to model-checking input. (2) Other researchers: Our translator embodies, in one tool, ideas and approaches drawn from several sources. Solutions to the major challenges of statechart-to-model-checker translation (e.g., determining which transition(s) will fire, handling of concurrent activities) are retired in a uniform, fully mechanized, setting. The way in which the underlying architecture of the translator itself facilitates flexible and customizable translation will also be evident.

Rouquette, Nicolas↗