SEARCH · Search NASA

Results for “Data control 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.

SourceResearch connectionFrom yearThrough year

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

At least 451 records · Page 25

All sources NASA NTRS DOE OSTI

NASA NTRS1976

A microprocessor controlled pressure scanning system

A microprocessor-based controller and data logger for pressure scanning systems is described. The microcomputer positions and manages data from as many as four 48-port electro-mechanical pressure scanners. The maximum scanning rate is 80 pressure measurements per second (20 ports per second on each of four scanners). The system features on-line calibration, position-directed data storage, and once-per-scan display in engineering units of data from a selected port. The system is designed to be interfaced to a facility computer through a shared memory. System hardware and software are described. Factors affecting measurement error in this type of system are also discussed.

Anderson, R. C.↗

NASA NTRS1976

A microprocessor controlled pressure scanning system

Anderson, R. C.↗

NASA NTRS1983

Qualification testing for a central station

Qualification testing for a Central Station Photovoltaic (PV) Facility depends to a great extent on the system design, (fixed versus tracking), and the level of data acquisition/control which is incorporated into the system. The basic elements which require qualification tests include: dc power production/collection; tracker conversion systems; ac utility interface; system level control; and data acquisition/reporting. The qualification tests from the Lungo (ARCO) 1 MW Facility which were completed in January 1983 are discussed. The philosophy and many of the procedures are applicable to any central station PV facility.

Forrester, D. L.↗

NASA NTRS2001

Data Synchronization Discrepancies in a Formation Flight Control System

Aircraft hardware-in-the-loop simulation is an invaluable tool to flight test engineers; it reveals design and implementation flaws while operating in a controlled environment. Engineers, however, must always be skeptical of the results and analyze them within their proper context. Engineers must carefully ascertain whether an anomaly that occurs in the simulation will also occur in flight. This report presents a chronology illustrating how misleading simulation timing problems led to the implementation of an overly complex position data synchronization guidance algorithm in place of a simpler one. The report illustrates problems caused by the complex algorithm and how the simpler algorithm was chosen in the end. Brief descriptions of the project objectives, approach, and simulation are presented. The misleading simulation results and the conclusions then drawn are presented. The complex and simple guidance algorithms are presented with flight data illustrating their relative success.

Ryan, Jack↗

NASA NTRS2020

Investigation of a Helicopter Individual Blade Control (IBC) System in Two Full-Scale Wind Tunnel Tests: Volume II—Tabulated Data

This volume presents the tabulated data acquired during the testing of an individual blade control (IBC) system for a full-scale BO-105 helicopter rotor in the NASA Ames 40- by 80-Foot Wind Tunnel. The data are divided into appendices according to the data type. Table 6 in Volume I presents a summary of the data acquired during the 1993 and 1994 IBC wind tunnel tests. The data have been tabulated according to test year, run number, and point number (e.g., 1993 IBC Test, Run 20, pt. 3). The 1993 and 1994 IBC tests were each started with a run number of 1. A new run number was assigned each time the wind tunnel and rotor were restarted, even if no data were acquired during the previous run. For this reason, some run numbers appear to be missing, yet all of the IBC data is included in the tabulated data, with one notable exception. The Fourier series data presented in Appendices H, L, and N are provided only for the data points identified with the ”•“ symbol in the last column of Table 6 in Volume I. This was done to keep the physical size of the data tables reasonable. The table below shows which data were included in these appendices; the data encompass the majority of the IBC inputs tested in the wind tunnel. Data for the points not included in Appendices H, L, and N have been retained in the BO-105 IBC database and are electronically available from NASA Ames Research Center.

Investigation↗

NASA NTRS1992

Program Handles Environmental-Test Data

S3 Data Acquisition and Control System, (S3DACS) monitors, controls, and records information acquired during tests and presents it in various formats for easy access by large number of users. Results automatically stored. Data used in computations, and selectively presented in tabular, graphical, or electronic form. Reports show current or historical events. Network software written in FoxPro/LAN 1.02 and 80386 Assembler.

De Freitas Bart, Frances↗

NASA NTRS1992

How to handle 6GBytes a night and not get swamped

The Macho Project has undertaken a 5 year effort to search for dark matter in the halo of the Galaxy by scanning the Magellanic Clouds for micro-lensing events. Each evening's raw image data will be reduced in real-time into the observed stars' photometric measurements. The actual search for micro-lensing events will be a post-processing operation. The theoretical prediction of the rate of such events necessitates the collection of a large number of repeated exposures. The project designed camera subsystem delivers 64 Mbytes per exposure with exposures typically occurring every 500 seconds. An ideal evening's observing will provide 6 Gbytes of raw image data and 40 Mbytes of reduced photometric measurements. Recognizing the difficulty of digging out from a snowballing cascade of raw data, the project requires the real-time reduction of each evening's data. The software team's implementation strategy centered on this non-negotiable mandate. Accepting the reality that 2 full time people needed to implement the core real-time control and data management system within 6 months, off-the-shelf vendor components were explored to provide quick solutions to the classic needs for file management, data management, and process control. Where vendor solutions were lacking, state-of-the-art models were used for hand tailored subsystems. In particular, petri nets manage process control, memory mapped bulletin boards provide interprocess communication between the multi-tasked processes, and C++ class libraries provide memory mapped, disk resident databases. The differences between the implementation strategy and the final implementation reality are presented. The necessity of validating vendor product claims are explored. Both the successful and hindsight decisions enabling the collection and processing of the nightly data barrage are reviewed.

Allsman, R.↗

NASA NTRS2018

RESTful CFDP: Managing GDS Complexity with Microservices

NASA's Advanced Multi-Mission Operations System (AMMOS) is currently adding capability to support the CCSDS File Delivery Protocol (CFDP). This feature is being added as part of the AMMOS Mission Data Processing and Control System (AMPCS). In order to address the system’s increasing complexity, AMPCS has recently been re-architected to break down its monolithic applications into smaller, individually deployable microservices. The CFDP capability is the first new AMPCS feature to leverage this new architecture. The CFDP microservice provides a web-based Representational State Transfer (REST) application programming interface (API) for complete monitor and control of its operations, and this enables it to be decoupled from other AMPCS microservices. This also results in better scalability for redundancy and load balancing. AMPCS's CFDP microservice is designed to support generic CFDP operations, agnostic to AMPCS's legacy concept of Downlink Products. An optional runtime plug-in allows the CFDP microservice to simulate CFDP artifacts as Downlink Products. Applying the microservices software architecture pattern both in the latest release of AMPCS and in providing the new CFDP capability has resulted in a more flexible system with improved extensibility and maintainability. System complexity has also become more manageable.

Choi, Joshua S.↗

NASA NTRS1967

Performance measures for compressed and coded space telemetry systems.

Data compression and error control coding in space telemetry analyzed, using performance measures similar to distortion function

ERROR DETECTING CODE↗

NASA NTRS2015

Framework and Method for Controlling a Robotic System Using a Distributed Computer Network

A robotic system for performing an autonomous task includes a humanoid robot having a plurality of compliant robotic joints, actuators, and other integrated system devices that are controllable in response to control data from various control points, and having sensors for measuring feedback data at the control points. The system includes a multi-level distributed control framework (DCF) for controlling the integrated system components over multiple high-speed communication networks. The DCF has a plurality of first controllers each embedded in a respective one of the integrated system components, e.g., the robotic joints, a second controller coordinating the components via the first controllers, and a third controller for transmitting a signal commanding performance of the autonomous task to the second controller. The DCF virtually centralizes all of the control data and the feedback data in a single location to facilitate control of the robot across the multiple communication networks.

Sanders, Adam M.↗

NASA NTRS1987

Advanced communications, tracking, robotic vision technology for space applications

Recent advancements in the areas of tracking, communications, and robotics vision sensors being pursued within NASA, as applicable to space programs, are presented. Optical and laser-based communications and tracking systems and applications to space programs are discussed. Communication systems for multiple access, broadband, high data rate, and efficient operations are given. Current efforts at 20/30 GHz and millimeter wave bands are summarized. The use of optical data processing in control system applications for rendezvous and docking is presented. Robotics vision, based on television, laser, and microwave sensors for space applications, is discussed. The fusion of these technologies for remote control, station keeping, tracking, inspection, and satellite repair is detailed.

Krishen, Kumar↗

NASA NTRS1987

Knowledge-based monitoring of the pointing control system on the Hubble space telescope

A knowledge-based system for the real time monitoring of telemetry data from the Pointing and Control System (PCS) of the Hubble Space Telescope (HST) that enables the retention of design expertise throughout the three decade project lifespan by means other than personnel and documentation is described. The system will monitor performance, vehicle status, success or failure of various maneuvers, and in some cases diagnose problems and recommend corrective actions using a knowledge base built using mission scenarios and the more than 4,500 telemetry monitors from the HST.

Dunham, Larry L.↗

NASA NTRS1978

Water sample-collection and distribution system

Collection and distribution system samples water from six designated stations, filtered if desired, and delivers it to various analytical sensors. System may be controlled by Water Monitoring Data Acquisition System or operated manually.

Brooks, R. R.↗

NASA NTRS2018

Unit Testing for Command and Control Systems

Unit tests were created to evaluate the functionality of a Data Generation and Publication tool for a command and control system. These unit tests are developed to constantly evaluate the tool and ensure it functions properly as the command and control system grows in size and scope. Unit tests are a crucial part of testing any software project and are especially instrumental in the development of a command and control system. They save resources, time and costs associated with testing, and catch issues before they become increasingly difficult and costly. The unit tests produced for the Data Generation and Publication tool to be used in a command and control system assure the users and stakeholders of its functionality and offer assurances which are vital in the launching of spacecraft safely.

testing↗

DOE OSTI2026

Data-Driven Voltage Regulation of Distribution Grid Using Nonlinear Autoregressive Model with Exogenous Inputs (NARX)

This article proposes data-driven control via a nonlinear autoregressive model with exogenous inputs (NARX) for real-time voltage regulation of a modified feeder using reactive power sources. Traditional voltage control strategies rely on rule-based heuristics or optimization techniques, which often require detailed system models and extensive computational resources. The NARX-based controller learns system dynamics from historical data and predicts optimal reactive power dispatch in real-time for voltage correction. The proposed approach is evaluated on a power system feeder model under varying load and network conditions. Simulation results demonstrate that the NARX-based controller achieves improved voltage regulation, offering higher adaptability to system fluctuations. This study highlights the potential of data-driven control for enhancing the reliability of power distribution networks.

Donge, Vrushabh [ORNL] (ORCID:0000000306062803)↗

NASA NTRS2008

Moving Away from Ones and Zeros, Designing a Ground Data System Based on Higher Levels of Abstraction

Previous JPL ground systems have been designed with the Ground Data System (GDS) engineer in mind. The focus on these systems has been on packaging and delivery of low level information (frames, packets, telemetry values) to the end user. It was not that long ago when project teams would be huddled over a workstation, examining crude displays of telemetry bits organized in various ways, trying to determine the status of a spacecraft. Understanding the data often required additional levels of GDS expertise, or worse, transformation of the raw data into alternative formats followed by ingestion into other tools so that the data became meaningful. The primary focus was often to answer these types of questions: "Why did this particular frame fail Reed-Solomon decode? Why did this packet get marked as invalid? Why am I missing a block of telemetry from my query?" -- which are completely valid questions to ask from a GDS Engineer's point of view, and large families of tools have been designed to help answer these questions. But these are not the questions that most users care about - which are more like: "Why is the battery state of charge trending down? Show me a summary image report for the last traverse to the target. Show me a data accountability summary for the last DSN pass." Answers to these questions, which are what users are looking for, requires a higher level of abstraction and supporting tools than mining through ones and zeros. JPL has created a next generation capability called the Mission Data Processing and Control System (MPCS) which is designed to support this higher level of abstraction by providing customizable views of the ground system combining collections of lower level information into more meaningful ways. Instead of examining frames, packets, and individual telemetry data points -- MPCS is capable of providing comprehensive summary reports, product status, overall flight/ground event status, as well as payload health summaries. Based on these higher level views, end users can make tactical or strategic decisions, or drop into detailed analysis as needed. System designers need to continue building systems that support low level GDS troubleshooting - but the basic design of a GDS should be geared towards what end users actually need to see. This paper will describe the capabilities of MPCS that directly support these higher levels of abstraction, and which are being used today in missions such as the Mars Science Laboratory and other NASA missions.

MPCS↗

NASA NTRS1981

IECM calibration and data reduction requirements

The induced environment contamination monitor (IECM) tape recorder format, as it relates to the ouput of meaningful data from the IECM instrument, is explained. Eight-bit words (or bytes) generate numbers that represent voltage levels of electronic detection probes for each experiment. This information is amalgamated by the IECM Data Acquisition and Control System (DACS). In some cases bits represent certain status situations concerning an experiment, such as whether a valve is opened or closed. Voltages are transformed into meaningful physical phenomena through equations of calibration. Data formats and plots are generated as requested for each IECM experimenter.

Wills, F. D.↗

NASA NTRS1988

An automated ozone photometer

A photometer capable of automatically measuring ozone concentration data to very high resolution during scientific research flights in the Earth's atmosphere was developed at NASA Ames Research Center. This instrument was recently deployed to study the ozone hole over Antarctica. Ozone is detected by absorbing 253.7-nm radiation from an ultraviolet lamp which shines through the sample of air and impinges on a vacuum phototube. A lower output from the phototube indicates more ozone present in the air sample. The photometer employs a CMOS Z80 microprocessor with an STD bus system for experiment control, data collection, and storage. Data are collected and stored in nonvolatile memory for experiments lasting up to 8 hr. Data are downloaded to a portable ground-support computer and processed after the aircraft lands. An independent single-board computer in the STD bus also calculates ozone concentration in real time with less resolution than the CMOS Z80 system, and sends this value to a cockpit meter to aid the pilot in navigation.

Lavelle, Joseph R.↗