SEARCH · Engineering Papers

Results for “Software Requirements”

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 649 records · Page 36

All sources NASA NTRS DOE OSTI

NASA NTRS2013

Optimal Propellant Maneuver Flight Demonstrations on ISS

In this paper, first ever flight demonstrations of Optimal Propellant Maneuver (OPM), a method of propulsive rotational state transition for spacecraft controlled using thrusters, is presented for the International Space Station (ISS). On August 1, 2012, two ISS reorientations of about 180deg each were performed using OPMs. These maneuvers were in preparation for the same-day launch and rendezvous of a Progress vehicle, also a first for ISS visiting vehicles. The first maneuver used 9.7 kg of propellant, whereas the second used 10.2 kg. Identical maneuvers performed without using OPMs would have used approximately 151.1kg and 150.9kg respectively. The OPM method is to use a pre-planned attitude command trajectory to accomplish a rotational state transition. The trajectory is designed to take advantage of the complete nonlinear system dynamics. The trajectory choice directly influences the cost of the maneuver, in this case, propellant. For example, while an eigenaxis maneuver is kinematically the shortest path between two orientations, following that path requires overcoming the nonlinear system dynamics, thereby increasing the cost of the maneuver. The eigenaxis path is used for ISS maneuvers using thrusters. By considering a longer angular path, the path dependence of the system dynamics can be exploited to reduce the cost. The benefits of OPM for the ISS include not only reduced lifetime propellant use, but also reduced loads, erosion, and contamination from thrusters due to fewer firings. Another advantage of the OPM is that it does not require ISS flight software modifications since it is a set of commands tailored to the specific attitude control architecture. The OPM takes advantage of the existing ISS control system architecture for propulsive rotation called USTO control mode1. USTO was originally developed to provide ISS Orbiter stack attitude control capability for a contingency tile-repair scenario, where the Orbiter is maneuvered using its robotic manipulator relative to the ISS. Since 2005 USTO has been used for nominal ISS operations.

Bhatt, Sagar↗

NASA NTRS2013

Swamp Works- Multiple Projects

My Surface Systems internship over the summer 2013 session covered a broad range of projects that ranged multiple aspects and fields of engineering and technology. This internship included a project to create a command center for a 120 ton regolith bin, a design and build for a blast shield to add further protection for the Surface Systems engineers, a design for a portable four monitor hyper wall that can extend as large as needed, research and programming a nano drill for a next generation robot, and social media tasks including the making of videos, posting to social networking websites and implementation of a new weekly outreach program to help spread the word about the Swamp Works laboratory. The objectives for the command center were to create a central computer controlled area for the still in production lunar regolith bin. It needed to be easy to use and the operating systems had to be Linux. The objectives for the hyper wall were to build a mobile transport of monitors that could potentially attach to one another. It needed to be light but sturdy, and have the ability to last. The objectives for the blast shield included a robust design that could withstand a small equipment malfunction, while also being convenient for use. The objectives for the nano-drill included the research and implementation of programming for vertical and horizontal movement. The hyper wall and blasts shield project were designed by me in the Pro/Engineer/Creo2 software. Each project required a meeting with the Swamp Works engineers and was declared successful.

Carelli, Jonathan M.↗

NASA NTRS2015

Radio Frequency Identification for Space Habitat Inventory and Stowage Allocation Management

To date, the most extensive space-based inventory management operation has been the International Space Station (ISS). Approximately 20,000 items are tracked with the Inventory Management System (IMS) software application that requires both flight and ground crews to update the database daily. This audit process is manually intensive and laborious, requiring the crew to open cargo transfer bags (CTBs), then Ziplock bags therein, to retrieve individual items. This inventory process contributes greatly to the time allocated for general crew tasks.

Wagner, Carole Y.↗

NASA NTRS2017

Environmental Control System Software & Hardware Development

ECS hardware: (1) Provides controlled purge to SLS Rocket and Orion spacecraft. (2) Provide mission-focused engineering products and services. ECS software: (1) NASA requires Compact Unique Identifiers (CUIs); fixed-length identifier used to identify information items. (2) CUI structure; composed of nine semantic fields that aid the user in recognizing its purpose.

student↗

NASA NTRS2018

Development and Use of the SPACE Computer Code for Analyzing the Space Station Electrical Power System

This special publication tells the story of the dedicated efforts of very talented individuals to create a preeminent space electrical power system modeling and simulation tool called SPACE, short for System Power Analysis for Capability Evaluation. This computer model has evolved for 30 years, withstanding the test of time and obsolescence, and garnering international recognition for its ability to simulate complex space electrical power systems. The analytical results from this model have saved millions of dollars in hardware redesign, testing, and verification for NASA's International Space Station (ISS) and its European and Russian partners. SPACE has played a pivotal role in the station's design and development and continues to support its ongoing operation. It has also extended its reach beyond the ISS to other key NASA programs, where it guides the design and planned operation of NASA's Multi-Purpose Crew Vehicle Orion and simulates electric power system operation in a dusty atmosphere on Mars' surface. The SPACE lineage was created by a core civil servant staff, supplemented by a cadre of interns and other temporary helpers. They created a tightly integrated tool that includes all phenomena that impact a solar array and battery space power system performance. SPACE is self-contained, requiring no other software modules and associated license fees. SPACE "rings true" in that is has been extensively validated with ISS on-orbit telemetry data. This report is being released as the generation of engineers who created it are nearing retirement, passing the baton to a new generation. This next generation will carry the code into the future, no doubt further evolving it to be able to assure mission planners that newly conceived systems will successfully power NASA's next endeavors. As a previous SPACE code developer and analyst, I have worked alongside many of the people mentioned in this report. The engineers who created the code, along with those just now learning it, are among the best and brightest at NASA. It is an honor to write this foreword as the present Branch Chief under which the legacy of SPACE continues to thrive.

Electrical Power System↗

NASA NTRSDate not supplied

Lander Lighting Solution to Reduce Pilot & Autonomous Approach Errors

The south pole lighting environment will have harsh low inclination sunlight, making overhead judgement of surface features difficult. Autonomous solutions are great, however, the need for visual monitoring and independent go/no-go decisions remain. Our project proposes that lunar landing systems will be better served by including a powerful landing light system that improves visibility of surfaces from overhead by illuminating the ground at critical distances for the crew to make last minute decisions regarding an approach. The project utilized computer-based optical modeling software to predict requirements for a potential landing light system. The analysis based the lamp prediction from commercially available LED chip sets and lamp optics. The goal was to illustrate a method to raise the surface contrast of a landing site within an acceptable contrast threshold for most camera systems and human observers to recognize hazards that would not be noticed with low inclination sunlight alone. The Apollo lunar landings benefitted from overhead sun or dark conditions. The surface lighting at the Lunar South Pole is a harsh environment where surfaces are lit from a low inclination angle by the sun (from the side). This change in lighting condition precipitates a need for updated lunar landing systems that facilitate improved recognition of landing sites, and thereby increase pilot awareness of landing hazards. The reliance on LIDAR and other autonomous mechanisms alone is risky given the known usage of visual monitoring for operator concurrence on current spacecraft programs and present-day autonomous land-based vehicles. Visual monitoring via cameras or windows requires the surface contrast to be within 3 orders of magnitude for reasonable recognition of objects. Artificial overhead illumination, when sufficiently sized, provides a means to even out contrast problems created by low inclination sunlight, potentially reducing piloting errors. Current vehicle requirements do not specify this type of guidance for the purpose of increasing mission success. An optical ray-trace simulation model was developed in Zemax Optics Studio to predict the best combination of LED power, LED optics, lamp quantity, and lamp location to raise the surface contrast to within 2 orders of magnitude from 3 orders required to further increased visibility and reduce risk. The project considered the following design constraints: potential base diameter of lander, approach distance(s) for a go-no-go decision point (200 meter), solar inclination angle (2-7), lunar surface reflectance (10%), LED chip sets, LED focusing optics, LED power, lamp quantity, lamp locations, and illumination diameter of lunar surface landing zone. The results can be used to establish minimum design constraints for vehicle landing light systems. With a solar inclination angle ranging from 2-7 degrees, the horizontal illumination of the lunar surface is attenuated by about 10% when compared to overhead illumination from the Sun. This modifies the sun's maximum of 130,000 lux to 13,000 lux horizontal illuminance. The artificial lighting system was designed to provide an 18-meter-wide illumination zone, to create viewing clearances around a 6-meter-wide lander. The system provides an average illuminance of 300 lux, meeting the 2 orders of magnitude criteria. The solution utilized modern Chip On Board LEDs, that each utilized 17 watts, with focusing Total Internal Reflection (TIR) lenses. A lighting system of 300 LEDs was arrayed along the "bottom" of a “lander”. With 17 watts per LED, the system is estimated to require 5100 watts. This is a large amount of power, but it would only be needed during critical phases during the landing. LED lighting systems can be dimmed, and it is assumed that as the lander arrives closer to the landing site, the lighting system power can be adjusted as needed to produce the necessary surface illuminance. The designed reduction of contrast improves reliability of safety assessments using real time visible light camera systems and out the window viewing by the crew.

T A Clark↗

NASA NTRSDate not supplied

Interactive Mars: A Direct-Experience Mission

As NASA prepares to explore Mars, we describe an innovative architecture that could be based on public-private partnerships to offset the costs of such a mission, while demonstrating many of the key technologies—propulsion, communications, autonomy, and landing systems—that will be needed for future human exploration. We propose that NASA could use this capability to deliver dozens of small rovers to several sites on Mars to enable the creation of interactive games that would be operated commercially and sponsored privately. NASA would get a reduced cost to demonstrate a portion of the infrastructure needed for human exploration, and the private sector would get access to a new market and sponsorship opportunities for a broadly popular activity. In addition, our proposed architecture could enable a new, intuitive means for scientists to interpret data and conduct ground operations. This proposal is to broadly develop the overall concept, while focusing on the design of the novel communications system, developing requirements for the software architecture needed to control the rovers and implement gaming, and developing gaming concepts.

Carolyn R. Mercer↗

NASA NTRSDate not supplied

Formal Verification, Distributed Computing, and Path Planning Algorithms

The safety- and mission-critical nature of much of the work done at NASA requires algorithms and software to be exceedingly reliable. Formal methods techniques are one way of ensuring this high level of robustness. This talk will discuss the development and formal verification of autonomous aircraft path planning algorithms related to the Bellman-Ford shortest path algorithm, including consideration of distributed computation of the algorithm.

Formal Methods↗

NASA NTRS1998

The Implementation of Satellite Attitude Control System Software Using Object Oriented Design

NASA established the Small Explorer (SNMX) program in 1988 to provide frequent opportunities for highly focused and relatively inexpensive space science missions. The SMEX program has produced five satellites, three of which have been successfully launched. The remaining two spacecraft are scheduled for launch within the coming year. NASA has recently developed a prototype for the next generation Small Explorer spacecraft (SMEX-Lite). This paper describes the object-oriented design (OOD) of the SMEX-Lite Attitude Control System (ACS) software. The SMEX-Lite ACS is three-axis controlled and is capable of performing sub-arc-minute pointing. This paper first describes high level requirements governing the SMEX-Lite ACS software architecture. Next, the context in which the software resides is explained. The paper describes the principles of encapsulation, inheritance, and polymorphism with respect to the implementation of an ACS software system. This paper will also discuss the design of several ACS software components. Specifically, object-oriented designs are presented for sensor data processing, attitude determination, attitude control, and failure detection. Finally, this paper will address the establishment of the ACS Foundation Class (AFC) Library. The AFC is a large software repository, requiring a minimal amount of code modifications to produce ACS software for future projects.

Reid, W. Mark↗

NASA NTRS2004

FPGA-Based, Self-Checking, Fault-Tolerant Computers

A proposed computer architecture would exploit the capabilities of commercially available field-programmable gate arrays (FPGAs) to enable computers to detect and recover from bit errors. The main purpose of the proposed architecture is to enable fault-tolerant computing in the presence of single-event upsets (SEUs). [An SEU is a spurious bit flip (also called a soft error) caused by a single impact of ionizing radiation.] The architecture would also enable recovery from some soft errors caused by electrical transients and, to some extent, from intermittent and permanent (hard) errors caused by aging of electronic components. A typical FPGA of the current generation contains one or more complete processor cores, memories, and highspeed serial input/output (I/O) channels, making it possible to shrink a board-level processor node to a single integrated-circuit chip. Custom, highly efficient microcontrollers, general-purpose computers, custom I/O processors, and signal processors can be rapidly and efficiently implemented by use of FPGAs. Unfortunately, FPGAs are susceptible to SEUs. Prior efforts to mitigate the effects of SEUs have yielded solutions that degrade performance of the system and require support from external hardware and software. In comparison with other fault-tolerant- computing architectures (e.g., triple modular redundancy), the proposed architecture could be implemented with less circuitry and lower power demand. Moreover, the fault-tolerant computing functions would require only minimal support from circuitry outside the central processing units (CPUs) of computers, would not require any software support, and would be largely transparent to software and to other computer hardware. There would be two types of modules: a self-checking processor module and a memory system (see figure). The self-checking processor module would be implemented on a single FPGA and would be capable of detecting its own internal errors. It would contain two CPUs executing identical programs in lock step, with comparison of their outputs to detect errors. It would also contain various cache local memory circuits, communication circuits, and configurable special-purpose processors that would use self-checking checkers. (The basic principle of the self-checking checker method is to utilize logic circuitry that generates error signals whenever there is an error in either the checker or the circuit being checked.) The memory system would comprise a main memory and a hardware-controlled check-pointing system (CPS) based on a buffer memory denoted the recovery cache. The main memory would contain random-access memory (RAM) chips and FPGAs that would, in addition to everything else, implement double-error-detecting and single-error-correcting memory functions to enable recovery from single-bit errors.

Some, Raphael↗

NASA NTRS2020

Bridging the Gap Between Requirements and Simulink Model Analysis

Formal verification and simulation are powerful tools for the verification of requirements against complex systems. Requirements are developed in early stages of the software lifecycle and are typically expressed in natural language. There is a gap between such requirements and their software implementations.We present a framework that bridges this gap by supporting a tight integration and feedback loop between high-level requirements and their analysis against software artifacts. Our framework implements an analysis portal within the fret requirements elicitation tool, thus forming an end-to-end, open-source environment where requirements are written in an intuitive, structured natural language, and are verified automatically against Simulink models.

Mavridou, Anastasia↗

NASA NTRSDate not supplied

Bridging the Gap Between Requirements and Simulink Model Analysis

Formal veri fication and simulation are powerful tools for the veri fication of requirements against complex systems. Requirements are developed in early stages of the software lifecycle and are typically expressed in natural language. There is a gap between such requirements and their software implementations. We present a framework that bridges this gap by supporting a tight integration and feedback loop between high-level requirements and their analysis against software artifacts. Our framework implements an analysis portal within the fret requirements elicitation tool, thus forming an end-to-end, open-source environment where requirements are written in an intuitive, structured natural language, and are veri fied automatically against Simulink models.

FRET↗

NASA NTRS1973

Development of simulation computer complex specification

The Training Simulation Computer Complex Study was one of three studies contracted in support of preparations for procurement of a shuttle mission simulator for shuttle crew training. The subject study was concerned with definition of the software loads to be imposed on the computer complex to be associated with the shuttle mission simulator and the development of procurement specifications based on the resulting computer requirements. These procurement specifications cover the computer hardware and system software as well as the data conversion equipment required to interface the computer to the simulator hardware. The development of the necessary hardware and software specifications required the execution of a number of related tasks which included, (1) simulation software sizing, (2) computer requirements definition, (3) data conversion equipment requirements definition, (4) system software requirements definition, (5) a simulation management plan, (6) a background survey, and (7) preparation of the specifications.

Source record↗

NASA NTRS1978

Fault-tolerant software for aircraft control systems

Concepts for software to implement real time aircraft control systems on a centralized digital computer were discussed. A fault tolerant software structure employing functionally redundant routines with concurrent error detection was proposed for critical control functions involving safety of flight and landing. A degraded recovery block concept was devised to allow collocation of critical and noncritical software modules within the same control structure. The additional computer resources required to implement the proposed software structure for a representative set of aircraft control functions were discussed. It was estimated that approximately 30 percent more memory space is required to implement the total set of control functions. A reliability model for the fault tolerant software was described and parametric estimates of failure rate were made.

Source record↗

NASA NTRS1996

Explicit and Implicit Resources: A Simplified Approach to User Requirements Modeling

The International Space Station (ISS) program is dependent on the concept of distributed planning, which places a large responsibility in the hands of the science users. The users assume the responsibility in submitting the operations scheduling requirements in the format required by the scheduling software. The concept of explicit and implicit resources, developed to facilitate the operations scheduling of ISS by non-scheduling experts, is presented. The proposed concepts are defined and examples of scheduling requirements, implemented using explicit and implicit resources, are described together with the requirements modeling and scheduler formatting functions. The software developed to support the implicit and explicit resources concept is discussed.

Hagopian, Jeff↗

NASA NTRS2013

Ensemble Eclipse: A Process for Prefab Development Environment for the Ensemble Project

This software simplifies the process of having to set up an Eclipse IDE programming environment for the members of the cross-NASA center project, Ensemble. It achieves this by assembling all the necessary add-ons and custom tools/preferences. This software is unique in that it allows developers in the Ensemble Project (approximately 20 to 40 at any time) across multiple NASA centers to set up a development environment almost instantly and work on Ensemble software. The software automatically has the source code repositories and other vital information and settings included. The Eclipse IDE is an open-source development framework. The NASA (Ensemble-specific) version of the software includes Ensemble-specific plug-ins as well as settings for the Ensemble project. This software saves developers the time and hassle of setting up a programming environment, making sure that everything is set up in the correct manner for Ensemble development. Existing software (i.e., standard Eclipse) requires an intensive setup process that is both time-consuming and error prone. This software is built once by a single user and tested, allowing other developers to simply download and use the software

Wallick, Michael N.↗

NASA NTRS1991

The advanced software development workstation project

The Advanced Software Development Workstation (ASDW) task is researching and developing the technologies required to support Computer Aided Software Engineering (CASE) with the emphasis on those advanced methods, tools, and processes that will be of benefit to support all NASA programs. Immediate goals are to provide research and prototype tools that will increase productivity, in the near term, in projects such as the Software Support Environment (SSE), the Space Station Control Center (SSCC), and the Flight Analysis and Design System (FADS) which will be used to support the Space Shuttle and Space Station Freedom. Goals also include providing technology for development, evolution, maintenance, and operations. The technologies under research and development in the ASDW project are targeted to provide productivity enhancements during the software life cycle phase of enterprise and information system modeling, requirements generation and analysis, system design and coding, and system use and maintenance. On-line user's guides will assist users in operating the developed information system with knowledge base expert assistance.

Fridge, Ernest M., III↗

NASA NTRS1986

Choosing a software design method for real-time Ada applications: JSD process inversion as a means to tailor a design specification to the performance requirements and target machine

The validity of real-time software is determined by its ability to execute on a computer within the time constraints of the physical system it is modeling. In many applications the time constraints are so critical that the details of process scheduling are elevated to the requirements analysis phase of the software development cycle. It is not uncommon to find specifications for a real-time cyclic executive program included to assumed in such requirements. It was found that prelininary designs structured around this implementation abscure the data flow of the real world system that is modeled and that it is consequently difficult and costly to maintain, update and reuse the resulting software. A cyclic executive is a software component that schedules and implicitly synchronizes the real-time software through periodic and repetitive subroutine calls. Therefore a design method is sought that allows the deferral of process scheduling to the later stages of design. The appropriate scheduling paradigm must be chosen given the performance constraints, the largest environment and the software's lifecycle. The concept of process inversion is explored with respect to the cyclic executive.

Withey, James V.↗