Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “timing system”

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 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRS2001

Self-Timed Digital System Design

A timing and control strategy that can be used to realize synchronous systems with a level of performance that approaches that of asynchronous circuits or systems was developed in this work. This approach is based upon a single-phase synchronous circuit/system architecture with a variable period clock. The handshaking signals required for asynchronous self-timed circuits are not needed. Dynamic power supply current monitoring is used to generate the timing information, that is comparable to the completion signal found in self-timed circuits; this timing information is used to modify the circuit clock period.

Walker, Alvernon↗
NASA NTRS1979

Mikhailov Stability Criterion for Time-delayed Systems

The valid and invalid application of the Mikhailov criterion to linear, time-invariant systems with time delays is discussed. The Mikhailov criterion is a graphical procedure which was developed to examine the stability of linear, time-invariant systems with no time delays. Two equivalent formulations of the criterion are discussed. Results indicate that the first formulation remains valid for time-delayed systems of the retared type, with the understanding that the Mikhailov curve need not necessarily always rotate in the counterclockwise direction for a stable system. Erroneous results in the second formulation are formed when there are time delays in the systems.

Barker, L. K.↗
NASA NTRS1980

Severe storms measurement system real time data processing and displays

The objectives of the system are to provide the system operator with real time system performance check and to provide data recording of all SSMS data. Meteorologists are provided with real time indication of meteorological data measurements including aid for directing flight profiles in real time and aid for directing SSMS operations. A day-to-day feedback is provided to meteorologists, system operators, and flight crews for flight planning on subsequent flight tests days.

Jeffreys, H. B.↗
NASA NTRS1983

Time-critical multirate scheduling using contemporary real-time operating system services

Although real-time operating systems provide many of the task control services necessary to process time-critical applications (i.e., applications with fixed, invariant deadlines), it may still be necessary to provide a scheduling algorithm at a level above the operating system in order to coordinate a set of synchronized, time-critical tasks executing at different cyclic rates. The scheduling requirements for such applications and develops scheduling algorithms using services provided by contemporary real-time operating systems.

Eckhardt, D. E., Jr.↗
NASA NTRS1973

Low cost automated precise time measurement system

The Aerospace Guidance and Metrology Center (AGMC) has the responsibility for the dissemination of Precise Time and Time Interval (PTTI) to Air Force timing systems requiring microsecond time. In order to maintain traceability to the USNO Master Clock in Washington D.C., and accomplish efficient logging of time and frequency data on individual precision clocks, a simple automatic means of acquiring precise time has been devised. The Automatic Time Interval Measurement System (ATIMS) consists of a minicomputer (8K Memory), teletype terminal, electronic counter, Loran C receiver, time base generator and locally-manufactured relay matrix panel. During the measurement process, the computer controls the relay matrix which selects for comparison 13 atomic clocks against a reference clock and the reference versus Loran C. Through use of the system teletype, the operator is able to set the system clock (hours, minutes and seconds), examine and/or modify all clock data and constants, and set measurement intervals. This is done in a conversational manner. A logic flow diagram, system schematic, source listing and software components are included in the presentation.

Alpert, A.↗
NASA NTRS1983

On Why It Is Impossible to Prove that the BDX90 Dispatcher Implements a Time-sharing System

The Software Implemented Fault Tolerance SIFT system, is written in PASCAL except for about a page of machine code. The SIFT system implements a small time sharing system in which PASCAL programs for separate application tasks are executed according to a schedule with real time constraints. The PASCAL language has no provision for handling the notion of an interrupt such as the B930 clock interrupt. The PASCAL language also lacks the notion of running a PASCAL subroutine for a given amount of time, suspending it, saving away the suspension, and later activating the suspension. Machine code was used to overcome these inadequacies of PASCAL. Code which handles clock interrupts and suspends processes is called a dispatcher. The time sharing/virtual machine idea is completely destroyed by the reconfiguration task. After termination of the reconfiguration task, the tasks run by the dispatcher have no relation to those run before reconfiguration. It is impossible to view the dispatcher as a time-sharing system implementing virtual BDX930s running concurrently when one process can wipe out the others.

Boyer, R. S.↗
NASA NTRS1990

Making real-time reactive systems reliable

A reactive system is characterized by a control program that interacts with an environment (or controlled program). The control program monitors the environment and reacts to significant events by sending commands to the environment. This structure is quite general. Not only are most embedded real time systems reactive systems, but so are monitoring and debugging systems and distributed application management systems. Since reactive systems are usually long running and may control physical equipment, fault tolerance is vital. The research tries to understand the principal issues of fault tolerance in real time reactive systems and to build tools that allow a programmer to design reliable, real time reactive systems. In order to make real time reactive systems reliable, several issues must be addressed: (1) How can a control program be built to tolerate failures of sensors and actuators. To achieve this, a methodology was developed for transforming a control program that references physical value into one that tolerates sensors that can fail and can return inaccurate values; (2) How can the real time reactive system be built to tolerate failures of the control program. Towards this goal, whether the techniques presented can be extended to real time reactive systems is investigated; and (3) How can the environment be specified in a way that is useful for writing a control program. Towards this goal, whether a system with real time constraints can be expressed as an equivalent system without such constraints is also investigated.

Marzullo, Keith↗
NASA NTRS2010

A Comparison and Evaluation of Real-Time Software Systems Modeling Languages

A model-driven approach to real-time software systems development enables the conceptualization of software, fostering a more thorough understanding of its often complex architecture and behavior while promoting the documentation and analysis of concerns common to real-time embedded systems such as scheduling, resource allocation, and performance. Several modeling languages have been developed to assist in the model-driven software engineering effort for real-time systems, and these languages are beginning to gain traction with practitioners throughout the aerospace industry. This paper presents a survey of several real-time software system modeling languages, namely the Architectural Analysis and Design Language (AADL), the Unified Modeling Language (UML), Systems Modeling Language (SysML), the Modeling and Analysis of Real-Time Embedded Systems (MARTE) UML profile, and the AADL for UML profile. Each language has its advantages and disadvantages, and in order to adequately describe a real-time software system's architecture, a complementary use of multiple languages is almost certainly necessary. This paper aims to explore these languages in the context of understanding the value each brings to the model-driven software engineering effort and to determine if it is feasible and practical to combine aspects of the various modeling languages to achieve more complete coverage in architectural descriptions. To this end, each language is evaluated with respect to a set of criteria such as scope, formalisms, and architectural coverage. An example is used to help illustrate the capabilities of the various languages.

Evensen, Kenneth D.↗