Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “COMMAND 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 1,477 records · Page 82

The Radio Frequency Health Node Wireless Sensor System

The Radio Frequency Health Node (RFHN) wireless sensor system differs from other wireless sensor systems in ways originally intended to enhance utility as an instrumentation system for a spacecraft. The RFHN can also be adapted to use in terrestrial applications in which there are requirements for operational flexibility and integrability into higher-level instrumentation and data acquisition systems. As shown in the figure, the heart of the system is the RFHN, which is a unit that passes commands and data between (1) one or more commercially available wireless sensor units (optionally, also including wired sensor units) and (2) command and data interfaces with a local control computer that may be part of the spacecraft or other engineering system in which the wireless sensor system is installed. In turn, the local control computer can be in radio or wire communication with a remote control computer that may be part of a higher-level system. The remote control computer, acting via the local control computer and the RFHN, cannot only monitor readout data from the sensor units but can also remotely configure (program or reprogram) the RFHN and the sensor units during operation. In a spacecraft application, the RFHN and the sensor units can also be configured more nearly directly, prior to launch, via a serial interface that includes an umbilical cable between the spacecraft and ground support equipment. In either case, the RFHN wireless sensor system has the flexibility to be configured, as required, with different numbers and types of sensors for different applications. The RFHN can be used to effect realtime transfer of data from, and commands to, the wireless sensor units. It can also store data for later retrieval by an external computer. The RFHN communicates with the wireless sensor units via a radio transceiver module. The modular design of the RFHN makes it possible to add radio transceiver modules as needed to accommodate additional sets of wireless sensor units. The RFHN includes a core module that performs generic computer functions, including management of power and input, output, processing, and storage of data. In a typical application, the processing capabilities in the RFHN are utilized to perform preprocessing, trending, and fusion of sensor data. The core module also serves as the unit through which the remote control computer configures the sensor units and the rest of the RFHN.

Valencia, J. Emilio↗

Blended Buffet-Load-Alleviation System for Fighter Airplane

The capability of modern fighter airplanes to sustain flight at high angles of attack and/or moderate angles of sideslip often results in immersion of part of such an airplane in unsteady, separated, vortical flow emanating from its forebody or wings. The flows from these surfaces become turbulent and separated during flight under these conditions. These flows contain significant levels of energy over a frequency band coincident with that of low-order structural vibration modes of wings, fins, and control surfaces. The unsteady pressures applied to these lifting surfaces as a result of the turbulent flows are commonly denoted buffet loads, and the resulting vibrations of the affected structures are known as buffeting. Prolonged exposure to buffet loads has resulted in fatigue of structures on several airplanes. Damage to airplanes caused by buffeting has led to redesigns of airplane structures and increased support costs for the United States Air Force and Navy as well as the armed forces of other countries. Time spent inspecting, repairing, and replacing structures adversely affects availability of aircraft for missions. A blend of rudder-control and piezoelectric- actuator engineering concepts was selected as a basis for the design of a vertical-tail buffet-load-alleviation system for the F/A-18 airplane. In this system, the rudder actuator is used to control the response of the first tail vibrational mode (bending at a frequency near 15 Hz), while directional patch piezoelectric actuators are used to control the second tail vibrational mode (tip torsion at a frequency near 45 Hz). This blend of two types of actuator utilizes the most effective features of each. An analytical model of the aeroservoelastic behavior of the airplane equipped with this system was validated by good agreement with measured results from a full-scale ground test, flight-test measurement of buffet response, and an in-flight commanded rudder frequency sweep. The overall performance of the system was found to be characterized by reductions, ranging from 70 to 30 percent, in vertical-tail buffeting under buffet loads ranging from moderate to severe. These reductions were accomplished with a maximum commanded rudder angle of +/-2deg at 15 Hz and about 10 lb (.4.5 kg) of piezoelectric actuators attached to the vertical tail skin and operating at a peak power level of 2 kW. By meeting the design objective, this system would extend the vertical-tail fatigue life beyond two aircraft lifetimes. This system is also adaptable to other aircraft surfaces and other aircraft

Moses, Robert W.↗

New Software Architecture Options for the TCL Data Acquisition System

The Turbulent Combustion Laboratory (TCL) conducts research on combustion in turbulent flow environments. To conduct this research, the TCL utilizes several pulse lasers, a traversable wind tunnel, flow controllers, scientific grade CCD cameras, and numerous other components. Responsible for managing these different data-acquiring instruments and data processing components is the Data Acquisition (DAQ) software. However, the current system is constrained to running through VXI hardware—an instrument-computer interface—that is several years old, requiring the use of an outdated version of the visual programming language, LabVIEW. A new Acquisition System is being programmed which will borrow heavily from either a programming model known as the Current Value Table (CVT) System or another model known as the Server-Client System. The CVT System model is in essence, a giant spread sheet from which data or commands may be retrieved or written to, and the Server-Client System is based on network connections between a server and a client, very much like the Server-Client model of the Internet. Currently, the bare elements of a CVT DAQ Software have been implemented, consisting of client programs in addition to a server program that the CVT will run on. This system is being rigorously tested to evaluate the merits of pursuing the CVT System model and to uncover any potential flaws which may result in further implementation. If the CVT System is chosen, which is likely, then future work will consist of build up the system until enough client programs have been created to run the individual components of the lab. The advantages of such a System will be flexibility, portability, and polymorphism. Additionally, the new DAQ software will allow the Lab to replace the VXI with a newer instrument interface—the PXI—and take advantage of the capabilities of current and future versions of LabVIEW.

97 MATHEMATICS AND COMPUTING↗

A conceptual design for an integrated data base management system for remote sensing data

The requirements of potential users were considered in the design of an integrated data base management system, developed to be independent of any specific computer or operating system, and to be used to support investigations in weather and climate. Ultimately, the system would expand to include data from the agriculture, hydrology, and related Earth resources disciplines. An overview of the system and its capabilities is presented. Aspects discussed cover the proposed interactive command language; the application program command language; storage and tabular data maintained by the regional data base management system; the handling of data files and the use of system standard formats; various control structures required to support the internal architecture of the system; and the actual system architecture with the various modules needed to implement the system. The concepts on which the relational data model is based; data integrity, consistency, and quality; and provisions for supporting concurrent access to data within the system are covered in the appendices.

Maresca, P. A.↗

The SAMPEX Data Processing Unit

The paper discusses salient features of the SAMPEX Data Processing Unit (DPU), the primary function of which is to collect sensor data to create telemetry packets for transmission to the solid-state recorder located within the Small Explorer Data System. Particular attention is given to the sensor interface electronics, the space command interface, the spacecraft telemetry interface, and the memory mapper of the DPU system; the task scheduling concept; and system reconfiguring. A block diagram of the DPU system is included.

Mabry, D. J.↗

Adapting a Large-Scale Multi-Mission Ground System for Low-Cost CubeSats

The majority of today's CubeSat fleet consists of Earth-orbiting missions that mostly use existing ground systems developed by universities because of availability, simplicity, and low-cost. The Interplanetary NanoSpacecraft Pathfinder In Relevant Environment (INSPIRE) mission is a revolutionary CubeSat mission that will launch a pair of CubeSats into deep space to study the feasibility of CubeSats beyond low-Earth orbit. This uncovers a new set of systems and software engineering challenges to the development of a robust and reliable ground system in a low-cost environment. In this paper, we discuss the approach to these challenges by using the Jet Propulsion Laboratory's (JPL) Advanced Multimission Operation System (AMMOS) Ground Data System (GDS) as well as the methodologies used to engineer the flight system to work with an existing ground system developed for large-scale missions. Specifically we will focus on the command and telemetry subsystem of AMMOS, the Multimission Data Processing and Control System. We conclude with a retrospective on the challenges encountered and a brief discussion on our efforts to provide AMMOS to support future deep space CubeSat missions.

Quach, William L.↗

General purpose simulation system of the data management system for Space Shuttle mission 18

A simulation program for the flow of data through the Data Management System of Spacelab and Space Shuttle was presented. The science, engineering, command and guidance, navigation and control data were included. The programming language used was General Purpose Simulation System V (OS). The science and engineering data flow was modeled from its origin at the experiments and subsystems to transmission from Space Shuttle. Command data flow was modeled from the point of reception onboard and from the CDMS Control Panel to the experiments and subsystems. The GN&C data flow model handled data between the General Purpose Computer and the experiments and subsystems. Mission 18 was the particular flight chosen for simulation. The general structure of the program is presented, followed by a user's manual. Input data required to make runs are discussed followed by identification of the output statistics. The appendices contain a detailed model configuration, program listing and results.

Bengtson, N. M.↗

Assured crew return vehicle post landing configuration design and test

The 1991-1992 senior Mechanical and Aerospace Engineering Design class continued work on the post landing configurations for the Assured Crew Return Vehicle (ACRV) and the Emergency Egress Couch (EEC). The ACRV will be permanently docked to Space Station Freedom fulfilling NASA's commitment of Assured Crew Return Capability in the event of an accident or illness aboard Space Station Freedom. The EEC provides medical support and a transportation surface for an incapacitated crew member. The objective of the projects was to give the ACRV Project Office data to feed into their feasibility studies. Four design teams were given the task of developing models with dynamically and geometrically scaled characteristics. Groups one and two combined efforts to design a one-fifth scale model for the Apollo Command Module derivative, an on-board flotation system, and a lift attachment point system. This model was designed to test the feasibility of a rigid flotation and stabilization system and to determine the dynamics associated with lifting the vehicle during retrieval. However, due to priorities, it was not built. Group three designed a one-fifth scale model of the Johnson Space Center (JSC) benchmark configuration, the Station Crew Return Alternative Module (SCRAM) with a lift attachment point system. This model helped to determine the flotation and lifting characteristics of the SCRAM configuration. Group four designed a full scale EEC with changeable geometric and geometric and dynamic characteristics. This model provided data on the geometric characteristics of the EEC and on the placement of the CG and moment of inertia. It also gave the helicopter rescue personnel direct input to the feasibility study. Section 1 describes in detail the design of a one-fifth scale model of the Apollo Command Module Derivative (ACMD) ACRV. The objective of the ACMD Configuration Model Team was to use geometric and dynamic constraints to design a one-fifth scale working model of the Apollo Command Module Derivative (ACMD) configuration with a Lift Attachment Point (LAP) System. This model was required to incorporate a rigidly mounted flotation system and the egress system designed the previous academic year. The LAP system was to be used to determine the dynamic effects of locating the lifting points at different locations on the vehicle. The team was then to build and test the model; however, due to priorities, this did not occur. To better simulate the ACMD after a water landing, the nose cone section was removed and the deck area exposed. The areas researched during the design process were construction, center of gravity and moment of inertia, and lift attachment points.

Source record↗

Automation study for space station subsystems and mission ground support

An automation concept for the autonomous operation of space station subsystems, i.e., electric power, thermal control, and communications and tracking are discussed. To assure that functions essential for autonomous operations are not neglected, an operations function (systems monitoring and control) is included in the discussion. It is recommended that automated speech recognition and synthesis be considered a basic mode of man/machine interaction for space station command and control, and that the data management system (DMS) and other systems on the space station be designed to accommodate fully automated fault detection, isolation, and recovery within the system monitoring function of the DMS.

Source record↗

Preliminary Design, Testing, and Performance of the LOFTID Navigation System

The Low Earth Orbit Flight Test of an Inflatable Decelerator (LOFTID) involves the first orbital test of an inflatable decelerator. This test involves the LOFTID re-entry vehicle using an inflatable decelerator to re-enter the atmosphere after flying to orbit as a secondary payload. Due to system constraints, including spin stabilization, unknown time of day, a limited space available for antennas, and a heat shield which blocks magnetic fields, the navigation system includes only an inertial measurement unit and a single GPS receiver. As the vehicle is turned off for the first part of the mission and will not receive commands or data from the ground, the navigation system will not have accurate initialization, and will in-stead rely on pre-flight estimates or first measurement estimation. This could result in significant unknown error in the initial state, resulting in needing to initialize the state on-orbit and requires using the single GPS antenna for attitude updates. These design considerations led to using an Extended Kalman filter, modified to perform with these design constraints. A streamlined testing approach, including tests with flight-like rotations, is being used to limit the time and resources needed to test the navigation system while still fully testing the performance and robustness of the navigation system. This testing approach follows the NASA test-as-you-fly principle and allows for early detection of errors and changes that are needed in the software. This results in a navigation system that, even within the design constraints of the mission architecture, will provide the performance and robustness needed of the mission.

Joel Amert↗

Infrared Sensor on Unmanned Aircraft Transmits Time-Critical Wildfire Data

Since 2006, NASA fs Dryden Flight Research Center (DFRC) and Ames Research Center have been perfecting and demonstrating a new capability for geolocation of wildfires and the real-time delivery of data to firefighters. Managed for the Western States Fire Mission, the Ames-developed Autonomous Modular Scanner (AMS), mounted beneath a wing of DFRC fs MQ-9 Ikhana remotely piloted aircraft, contains an infrared sensor capable of discriminating temperatures within 0.5 F (approx. = 0.3 C), up to 1,000 F (approx. = 540 C). The AMS operates like a digital camera with specialized filters to detect light energy at visible, infrared, and thermal wavelengths. By placing the AMS aboard unmanned aircraft, one can gather information and imaging for thousands of square miles, and provide critical information about the location, size, and terrain around fires to commanders in the field. In the hands of operational agencies, the benefits of this NASA research and development effort can support nationwide wildfire fighting efforts. The sensor also provides data for post-burn and vegetation regrowth analyses. The MQ-9 Unmanned Aircraft System (UAS), a version of the Predator-B, can operate over long distances, staying aloft for over 24 hours, and controlled via a satellite-linked command and control system. This same link is used to deliver the fire location data directly to fire incident commanders, in less than 10 minutes from the time of overflight. In the current method, similarly equipped short-duration manned aircraft, with limited endurance and range, must land, hand-carry, and process data, and then deliver information to the firefighters, sometimes taking several hours in the process. Meanwhile, many fires would have moved over great distances and changed direction. Speed is critical. The fire incident commanders must assess a very dynamic situation, and task resources such as people, ground equipment, and retardant-dropping aircraft, often in mountainous terrain obscured by dense smoke.

Pestana, Mark↗

The SAS-3 programmable telemetry system

Basic concept, system design and operation principles of the telemetry system developed for the Small Astronomy Satellite-3 (SAS-3) are analyzed. The concept of programmable format selected for the SAS-3 represents an optical combination of the fixed format system of SAS-1 and SAS-2, and the adaptive format concept. The programmable telemetry system permits a very wide range of changes in the data sampling order by a ground control station, depending on the experimental requirements, so that the maximal amount of useful data can be returned from orbit. The programmable system also allows the data format to differ from one spacecraft to another without changing hardware. Attention is given to the command requirements and redundancy of the SAS-3 telemetry system.

Peterson, M. R.↗

Method and apparatus for operating a powertrain system upon detecting a stuck-closed clutch

A powertrain system includes a multi-mode transmission having a plurality of torque machines. A method for controlling the powertrain system includes identifying all presently applied clutches including commanded applied clutches and the stuck-closed clutch upon detecting one of the torque-transfer clutches is in a stuck-closed condition. A closed-loop control system is employed to control operation of the multi-mode transmission accounting for all the presently applied clutches.

42 ENGINEERING↗

Simplifying operations with an uplink/downlink integration toolkit

The Operations Engineering Lab (OEL) at JPL has developed a simple, generic toolkit to integrate the uplink/downlink processes, (often called closing the loop), in JPL's Multimission Ground Data System. This toolkit provides capabilities for integrating telemetry verification points with predicted spacecraft commands and ground events in the Mission Sequence Of Events (SOE) document. In the JPL ground data system, the uplink processing functions and the downlink processing functions are separate subsystems that are not well integrated because of the nature of planetary missions with large one-way light times for spacecraft-to-ground communication. Our new closed-loop monitoring tool allows an analyst or mission controller to view and save uplink commands and ground events with their corresponding downlinked telemetry values regardless of the delay in downlink telemetry and without requiring real-time intervention by the user. An SOE document is a time-ordered list of all the planned ground and spacecraft events, including all commands, sequence loads, ground events, significant mission activities, spacecraft status, and resource allocations. The SOE document is generated by expansion and integration of spacecraft sequence files, ground station allocations, navigation files, and other ground event files. This SOE generation process has been automated within the OEL and includes a graphical, object-oriented SOE editor and real-time viewing tool running under X/Motif. The SOE toolkit was used as the framework for the integrated implementation. The SOE is used by flight engineers to coordinate their operations tasks, serving as a predict data set in ground operations and mission control. The closed-loop SOE toolkit allows simple, automated integration of predicted uplink events with correlated telemetry points in a single SOE document for on-screen viewing and archiving. It automatically interfaces with existing real-time or non real-time sources of information, to display actual values from the telemetry data stream. This toolkit was designed to greatly simplify the user's ability to access and view telemetry data, and also provide a means to view this data in the context of the commands and ground events that are used to interpret it. A closed-loop system can prove especially useful in small missions with limited resources requiring automated monitoring tools. This paper will discuss the toolkit implementation, including design trade-offs and future plans for enhancing the automated capabilities.

Murphy, Susan C.↗