SEARCH · Engineering Papers
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.
An inflatable, rigidizable shelter system was developed based on Rigi dization on Command (ROC) technology incorporating not only the requ ired low-stowage volume and lightweight character achieved from an i nflatable/rigidizable system, but also a self-healing foam system inc orporated between the rigidizable layers of the final structure to m inimize the damage caused by any punctures to the structure.
In future tokamak reactors like ITER and the Fusion Pilot Plant (FPP), real-time feedback control of heat flux to the plasma-facing components (PFC) will be critical for steady-state operation. This work presents the first experimental demonstration of real-time divertor heat flux estimation with infrared thermography and feedback control with impurity seeding on the DIII-D tokamak. The flexible infrastructure of the Plasma Control System (PCS) on DIII-D makes this new capability possible. The PCS software runs on a gateway computer system, and five real-time compute nodes. An array of low latency streaming digitizers from D-TACQ Solutions connects to these real-time computers to collect and process data, and send commands to actuators during plasma discharges. This system handles the signal IO from the tokamak and allows the PCS to utilize the diagnostic data necessary to perform control in real-time. Feedback control on heat flux was accomplished by feeding infrared camera data from the “Infrared TV” (IRTV) camera to a custom-developed User Datagram Protocol (UDP) server. This server transmits infrared data to a newly developed PCS algorithm that estimates the heat flux to PFC. Here, a proportional integral derivative (PID) controller minimizes the error between a heat flux reference and the real-time estimate by injecting nitrogen gas into the divertor.
The Communications and Tracking System on board Space Station Freedom (SSF) provides space-to-ground, space-to-space, audio, and video communications, as well as tracking data reception and processing services. Each major category of service is provided by a communications subsystem which is controlled and monitored by software. Among these subsystems, the Assembly/Contingency Subsystem (ACS) and the Space-to-Ground Subsystem (SGS) provide communications with the ground via the Tracking and Data Relay Satellite (TDRS) System. The ACS is effectively SSF's command link, while the SGS is primarily intended as the data link for SSF payloads. The research activities of this project focused on the ACS and SGS antenna management algorithms identified in the Flight System Software Requirements (FSSR) documentation, including: (1) software modeling and evaluation of antenna management (positioning) algorithms; and (2) analysis and investigation of selected variables and parameters of these antenna management algorithms i.e., descriptions and definitions of ranges, scopes, and dimensions. In a related activity, to assist those responsible for monitoring the development of this flight system software, a brief summary of software metrics concepts, terms, measures, and uses was prepared.
Several proposed space missions include precision reflectors that are larger in diameter than any current or proposed launch vehicle. Most of these reflectors will require a truss structure to accurately position the reflector panels and these reflectors will likely require assembly in orbit. A research program has been conducted at the NASA Langley Research Center to develop the technology required for the robotic assembly of truss structures. The focus of this research has been on hardware concepts, computer software control systems, and operator interfaces necessary to perform supervised autonomous assembly. A special facility was developed and four assembly and disassembly tests of a 102-strut tetrahedral truss have been conducted. The test procedures were developed around traditional 'pick-and-place' robotic techniques that rely on positioning repeatability for successful operation. The data from two of the four tests were evaluated and are presented in this report. All operations in the tests were controlled by predefined sequences stored in a command file, and the operator intervened only when the system paused because of the failure of an actuator command. The tests were successful in identifying potential pitfalls in a telerobotic system, many of which would not have been readily anticipated or incurred through simulation studies. Addressing the total integrated task, instead of bench testing the component parts, forced all aspects of the task to be evaluated. Although the test results indicate that additional developments should be pursued, no problems were encountered that would preclude automated assembly in space as a viable construction method.
A novel trajectory control system concept was implemented to provide manual control of a conventional jet aircraft. This concept, called Total Aircraft Flight Control System (TAFCOS), utilizes an inverse model of the aerodynamic and propulsion characteristics and employs feedforward control to provide the required acceleration command. The concept requires on-board digital computations which can easily be handled by a modern airborne computer. The system was studied in a piloted simulation of the carrier approach and landing task with primarily visual flight and guidance cues. The principal modes of vertical flight-path control investigated were vertical velocity command and vertical acceleration command. The study included manual carrier approaches with and without moderate ship motion and associated air disturbances, and tests of the effects of discrete gusts. Manual control of flight path through this new concept was shown to be feasible as an addition to an automatic control system and to have potential as an improved mode of control over conventional control for the carrier approach task.
The Transformation expert system (TRANS) converts proposals for astronomical observations with the Hubble Space Telescope (HST) into detailed observing plans. It encodes expert knowledge to solve problems faced in planning and commanding HST observations to enable their processing by the Science Operations Ground System (SOGS). Among these problems are determining an acceptable order of executing observations, grouping of observations to enhance efficiency and schedulability, inserting extra observations when necessary, and providing parameters for commanding HST instruments. TRANS is currently an operational system and plays a critical role in the HST ground system. It was originally designed using forward-chaining provided by the OPS5 expert system language, but has been reimplemented using a procedural knowledge base. This reimplementation was forced by the explosion in the amount of OPS5 code required to specify the increasingly complicated situations requiring expert-level intervention by the TRANS knowledge base. This problem was compounded by the difficulty of avoiding unintended interaction between rules. To support the TRANS knowledge base, XCL, a small but powerful extension to Commom Lisp was implemented. XCL allows a compact syntax for specifying assignments and references to object attributes. XCL also allows the capability to iterate over objects and perform keyed lookup. The reimplementation of TRANS has greatly diminished the effort needed to maintain and enhance it. As a result of this, its functions have been expanded to include warnings about observations that are difficult or impossible to schedule or command, providing data to aid SPIKE, an intelligent planning system used for HST long-term scheduling, and providing information to the Guide Star Selection System (GSSS) to aid in determination of the long range availability of guide stars.
The MSFC Payload Operations Integration Center (POIC) is the focal point for International Space Station (ISS) payload operations. The POIC contains the facilities, hardware, software and communication interface necessary to support payload operations. ISS ground system support for processing and display of real-time spacecraft and telemetry and command data has been operational for several years. The hardware components were reaching end of life and vendor costs were increasing while ISS budgets were becoming severely constrained. Therefore it has been necessary to migrate the Unix portions of our ground systems to commodity priced Intel-based Linux servers. hardware architecture including networks, data storage, and highly available resources. This paper will concentrate on the Linux migration implementation for the software portion of our ground system. The migration began with 3.5 million lines of code running on Unix platforms with separate servers for telemetry, command, Payload information management systems, web, system control, remote server interface and databases. The Intel-based system is scheduled to be available for initial operational use by August 2004 The overall migration to Intel-based Linux servers in the control center involves changes to the This paper will address the Linux migration study approach including the proof of concept, criticality of customer buy-in and importance of beginning with POSlX compliant code. It will focus on the development approach explaining the software lifecycle. Other aspects of development will be covered including phased implementation, interim milestones and metrics measurements and reporting mechanisms. This paper will also address the testing approach covering all levels of testing including development, development integration, IV&V, user beta testing and acceptance testing. Test results including performance numbers compared with Unix servers will be included. need for a smooth transition while maintaining real-time support. An important aspect of the paper will involve challenges and lessons learned. product compatibility, implications of phasing decisions and tracking of dependencies, particularly non- software dependencies. The paper will also discuss scheduling challenges providing real-time flight support during the migration and the requirement to incorporate in the migration changes being made simultaneously for flight support. This paper will also address the deployment approach including user involvement in testing and the , This includes COTS product compatibility, implications of phasing decisions and tracking of dependencies, particularly non- software dependencies. The paper will also discuss scheduling challenges providing real-time flight support during the migration and the requirement to incorporate in the migration changes being made simultaneously for flight support.
This paper presents an analysis of a guidance method which uses a reference trajectory. The four state variables needed to prescribe the trajectory are used as follows : Velocity is made the independent variable, and the errors in the rate-of-climb, acceleration, and range variables away from the reference are used to govern the lift. A linearized form of the motion equations is used to show that this represents a third-order control system. First- and second- order control terms (rate of climb and acceleration inputs) are shown to determine the entry corridor depth by stabilizing the trajectory so that the vehicle does not skip back out of the atmosphere or does not exceed a specified acceleration limit. The destabilizing effect that range input (the third-order control term) can have is illustrated and the results indicate that a low value of range input gain must be used at the high supercircular velocities while larger values of range input gain can be used at lower velocities. The usable corridor depth and range capability with this guidance system are demonstrated for a lifting capsule (L/D = 0.5). The practical applications of this system are illustrated with a fixed trim configuration wherein roll angle is used to command the desired lift. The results show that the guidance system requires only one reference trajectory for abort entry conditions as well as for entry conditions near the design values.
The development of requirements for an approach control system and example applications to a jet transport aircraft are presented. The material is divided into a general discussion of approach control requirements, and a specific application resulting in the design of three alternative longitudinal controllers. The point of view taken is that the essential features of the system structure are the feedbacks themselves, their equalization, and their combinations to create control commands. Use is made of the fact that for sucessful systems the possible feedback structures are very limited. They derive primarily from guidance, control, and regulation demands; and secondarily from dynamic response characteristics desired by the pilot. From the systems view it is the satisfaction of these requirements that is important rather than the means automatic, manual, or hygrid manual/automatic approach systems.
The design procedure of feedback controllers was described and the considerations for the selection of the design parameters were given. The frequency domain properties of single-input single-output systems using state feedback controllers are analyzed, and desirable phase and gain margin properties are demonstrated. Special consideration is given to the design of controllers for tracking systems, especially those designed to track polynomial commands. As an example, a controller was designed for a tracking telescope with a polynomial tracking requirement and some special features such as actuator saturation and multiple measurements, one of which is sampled. The resulting system has a tracking performance comparing favorably with a much more complicated digital aided tracker. The parameter sensitivity reduction was treated by considering the variable parameters as random variables. A performance index is defined as a weighted sum of the state and control convariances that sum from both the random system disturbances and the parameter uncertainties, and is minimized numerically by adjusting a set of free parameters.
The design of the remote site of a local-remote telerobot control system is described which addresses the constraints of limited computational power available at the remote site control system while providing a large range of control capabilities. The Modular Telerobot Task Execution System (MOTES) provides supervised autonomous control, shared control and teleoperation for a redundant manipulator. The system is capable of nominal task execution as well as monitoring and reflex motion. The MOTES system is minimized while providing a large capability by limiting its functionality to only that which is necessary at the remote site and by utilizing a unified multi-sensor based impedance control scheme. A command interpreter similar to one used on robotic spacecraft is used to interpret commands received from the local site. The system is written in Ada and runs in a VME environment on 68020 processors and initially controls a Robotics Research K1207 7 degree of freedom manipulator.
This paper describes an electric vertical takeoff and landing (eVTOL) aircraft system identification method applied using three degree-of-freedom (3DOF) free motion wind-tunnel testing. The approach, similar to flight-test system identification, allows for efficient mathematical model development of the aero-propulsive moments applied on an eVTOL vehicle, including aerodynamic damping effects. The approach is demonstrated using a subscale tiltrotor eVTOL aircraft mounted on a new 3DOF wind-tunnel apparatus. To execute the test, a model-based 3DOF control system is designed to track attitude commands and transition the aircraft based on the freestream dynamic pressure. While the flight controller is active, orthogonal phase-optimized multisine inputs are injected into the attitude command and control effector command signals to enable collection of informative data for model identification. Aero-propulsive models are then identified at several reference conditions in the transition flight envelope using the equation-error method in the frequency domain. The identified models are shown to have a good fit to the modeling data and good prediction capability of data not used for model identification. The method yields aerodynamic damping estimates using less wind-tunnel test time compared to traditional forced oscillation experiments and supplements static wind-tunnel testing to produce a comprehensive transition aero-propulsive model suitable for use in flight dynamics simulations.
A prototype Generic Payload Operations Control System (GPOCC) is being developed at the NASA Jet Propulsion Laboratory to provide a low-cost command and control processing center for science instruments and small payloads. The GPOCC supports the difficult transition from integration and test to flight operations. The prototype will incorporate four expert systems to perform telemetry, command, and mission planning functions as well as telecommunications scheduling. The first of these expert systems to be developed will perform telemetry data analysis and fault isolation, as well as propose corrective action. This Data Analysis Module (DAM) will monitor telemetry data and perform continual data monitoring and trend analysis based on a knowledge base and historic data archived on an optical disk storage device. The system maintains a continuous knowledge database of past system performance characteristics. The goal of the Data Analysis Module is to achieve consistent, dependable and validatable performance, to demonstrate thorough, reliable and fast reasoning, and to reduce the concentration demanded of flight analysis personnel.
The City of Tallahassee's Innovative Energy Initiatives program sought, first, to evaluate customer response and acceptance to in-home Smart Meter-enabled technologies that allow customers intelligent control of their energy usage. Additionally, this project is in furtherance of the City of Tallahassee's ongoing efforts to expand and enhance the City's Smart Grid capacity and give consumers more tools with which to effectively manage their energy consumption. This enhancement would become possible by establishing an "operations or command center" environment that would be designed as a dual use facility for the City's employees - field and network staff - and systems responsible for a Smart Grid network. A command center would also support the City's Office of Electric Delivery and Energy Reliability's objective to overcome barriers to the deployment of new technologies that will ensure a truly modern and robust grid capable of meeting the demands of the 21 st century.
The NASA Ames-Dryden Flight Research Facility developed a computerized aircraft battery servicing facility called the Aerospace Energy Systems Laboratory (AESL). This system employs distributed processing with communications provided by a 2.4-megabit BITBUS local area network. Customized handlers provide real time status, remote command, and file transfer protocols between a central system running the iRMX-II operating system and ten slave stations running the iRMX-I operating system. The hardware configuration and software components required to implement this BITBUS application are required.
Presented here is the Spacecraft Command Language (SCL) concept of the unification of ground and space operations using a distributed approach. SCL is a hybrid software environment borrowing from expert system technology, fifth generation language development, and multitasking operating system environments. Examples of potential uses for the system and current distributed applications of SCL are given.
Distributed Spacecraft Systems are a type of multi-spacecraft mission architecture that can not only provide improved resolution, coverage, and availability of existing missions, but also enable missions that would be previously infeasible using traditional approaches. Distributed Spacecraft Autonomy (DSA) is a project developed by the National Aeronautics and Space Administration that enables distributed spacecraft systems. In previous science swarm missions, the spacecraft involved have not been able to communicate with each other without utilizing a ground station. Now that the spacecraft can perform inter-satellite communication, the spacecraft can be treated as a collective. Swarm autonomy is critical for a growing number of satellites which means novel ways of displaying swarm data needs to be implemented. Such systems introduce unique challenges to traditional approaches for command and control of these spacecraft, due to the large number of spacecraft and the complexity of the interactions between them. The ground data system for DSA addresses these challenges through the creation of a custom user interface that allows a single operator to orchestrate a multi-spacecraft swarm in a scalable way. This plenary describes the details of the autonomy demonstration being performed, the requirements of those using the interface to analyze the spacecraft telemetry to assess demonstration success, and the approach taken by the ground systems team to create an interface that satisfies these requirements. This approach involves the creation of several distinct components that correspond to the level of detail presented to the user. These components are based on conventional user roles in human-robot interaction, including supervisor, operator, and mechanic, extended to accommodate the additional overhead of coordinating actions between agents. One main feature of the interface is the listenability matrix component which will represent inter-satellite communications in a heat mapped matrix. The above work described will enable users to command and interact with the spacecraft as a collective.
The incorporation of remote operations into reactor operations is a topic of high interest among advanced and small modular reactor (A/SMR) vendors, with some considering it essential to the success of their business models. However, remote operations are a concept novel to the nuclear industry. While various technical aspects of remote operations have been explored, a significant gap remains in understanding the security implications of integrating remote operations into reactor designs, particularly concerning the security requirements for remote-operations facilities and infrastructure. This report aims to address this gap by first defining classes of remote operation based on the extent of remote access to reactor control systems and grounded in the existing regulatory framework with compatible terminology. Secondly, the report outlines the physical and cybersecurity requirements applicable to remote-operations facilities and infrastructure at each defined class. These requirements are based on existing licensing frameworks provided by 10 Code of Federal Regulations (CFR) Part 50 and 10 CFR Part 52, as well as the upcoming A/SMR licensing framework in the proposed Part 53. The assessment focuses specifically on security regulations, such as 10 CFR Part 73, which includes provisions for both cybersecurity (§ 73.54) and physical security (§ 73.55). This report proposes five classes of remote reactor operations. Class 1 involves remote monitoring only, with no control over reactor systems. Class 2 allows for the remote issuance of allowlisted commands to the reactor facility. Class 3 extends control to non-safety-significant, non-safety-related, or not important to safety systems and equipment. Class 4 permits remote control of safety-significant systems. Finally, Class 5 allows remote control of safety-related systems. It is important to note that these classes were defined purely with functionality in mind, without considering the practicality or feasibility of implementation for each class under current or upcoming regulatory guidance. The intention behind this approach is to enable an assessment of which security requirements apply to each class, allowing readers to evaluate the implementation possibilities for their specific use cases. Following the definition of remote-operation classes, the report assesses the specific physical and cybersecurity requirements applicable to the remote-operations facility and infrastructure within each defined class. This includes defining the types and locations of operators that are possible at each class of operation and, based on operator type and location, as well as functionality within each class, outlining the physical and cybersecurity requirements. By detailing the security requirements by class, the report provides readers with the information needed to determine the type of security program they may need to implement for their desired concept of operation. The next contribution of this report was to assess the practicality of implementing each proposed class of remote operations based upon the security requirement assessment. In short, three of the five proposed remote-operation classes were found to possibly have a practical path forward to implementation under the U.S. regulatory framework. Class 1 remote operations are currently in use in the U.S. while Class 2 and 3 remote operations may be logistically possible to implement under the U.S. regulatory framework. The final two Classes, 4 and 5, would likely be logistically difficult, if not infeasible to implement within the current U.S. physical- and cybersecurity regulatory framework. Given the results of the feasibility assessment, an example architecture is proposed for both Class 2, remote allowlisted commands, and Class 3, remote control of non-safety systems as well as security implication assessments of each architecture. These example implementations are not meant to be prescriptive in terms of how Class 2 or Class 3 remote operations should be deployed; instead, they are intended to be informative to stakeholders on how Class 2 or Class 3 could potentially be applied in order to inform their system design. An example architecture for Class 1 remote monitoring was not provided as Class 1 in already in use in U.S. nuclear operations. Example architectures for Class 4 and Class 5 were not provided due to their assessment of being likely infeasible to implement. The final contribution is an assessment of the physical- and cybersecurity implications of introducing autonomous operations into an A/SMR. What was found was that the security implications can be separated into two cases. Autonomous operations supported by SSCs located only at the reactor site, and autonomous operations supported by SSCs outside of the reactor site. For the first case, the introduction of autonomous systems will likely not change the facility’s requirement to comply with existing cyber and physical security regulation