SEARCH · Engineering Papers

Results for “prototype specifications”

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 163 records · Page 9

All sources NASA NTRS DOE OSTI

NASA NTRS1995

Initial results for the silicon monolithically interconnected solar cell product

This proprietary technology is based on AstroPower's electrostatic bonding and innovative silicon solar cell processing techniques. Electrostatic bonding allows silicon wafers to be permanently attached to a thermally matched glass superstrate and then thinned to final thicknesses less than 25 micron. These devices are based on the features of a thin, light-trapping silicon solar cell: high voltage, high current, light weight (high specific power) and high radiation resistance. Monolithic interconnection allows the fabrication costs on a per watt basis to be roughly independent of the array size, power or voltage, therefore, the cost effectiveness to manufacture solar cell arrays with output powers ranging from milliwatts up to four watts and output voltages ranging from 5 to 500 volts will be similar. This compares favorably to conventionally manufactured, commercial solar cell arrays, where handling of small parts is very labor intensive and costly. In this way, a wide variety of product specifications can be met using the same fabrication techniques. Prototype solar cells have demonstrated efficiencies greater than 11%. An open-circuit voltage of 5.4 volts, fill factor of 65%, and short-circuit current density of 28 mA/sq cm at AM1.5 illumination are typical. Future efforts are being directed to optimization of the solar cell operating characteristics as well as production processing. The monolithic approach has a number of inherent advantages, including reduced cost per interconnect and increased reliability of array connections. These features make this proprietary technology an excellent candidate for a large number of consumer products.

Dinetta, L. C.↗

NASA NTRS2005

Safety Verification of the Small Aircraft Transportation System Concept of Operations

A critical factor in the adoption of any new aeronautical technology or concept of operation is safety. Traditionally, safety is accomplished through a rigorous process that involves human factors, low and high fidelity simulations, and flight experiments. As this process is usually performed on final products or functional prototypes, concept modifications resulting from this process are very expensive to implement. This paper describe an approach to system safety that can take place at early stages of a concept design. It is based on a set of mathematical techniques and tools known as formal methods. In contrast to testing and simulation, formal methods provide the capability of exhaustive state exploration analysis. We present the safety analysis and verification performed for the Small Aircraft Transportation System (SATS) Concept of Operations (ConOps). The concept of operations is modeled using discrete and hybrid mathematical models. These models are then analyzed using formal methods. The objective of the analysis is to show, in a mathematical framework, that the concept of operation complies with a set of safety requirements. It is also shown that the ConOps has some desirable characteristic such as liveness and absence of dead-lock. The analysis and verification is performed in the Prototype Verification System (PVS), which is a computer based specification language and a theorem proving assistant.

Carreno, Victor↗

NASA NTRS2013

Composite Design and Manufacturing Development for Human Spacecrafts

The Structural Engineering Division at the NASA Johnson Space Center (JSC) has begun work on lightweight, multi‐functional pressurized composite structures. The first candidate vehicle for technology development is the Multi‐Mission Space Exploration Vehicle (MMSEV) cabin, known as the Gen 2B cabin, which has been built at JSC by the Robotics Division. Of the habitable MMSEV vehicle prototypes designed to date, this is the first one specifically analyzed and tested to hold internal pressure and the only one made out of composite materials. This design uses a laminate base with zoned reinforcement and external stringers, intended to demonstrate certain capabilities, and to prepare for the next cabin design, which will be a composite sandwich panel construction with multi‐functional capabilities. As part of this advanced development process, a number of new technologies were used to assist in the design and manufacturing process. One of the methods, new to JSC, was to build the Gen 2B cabin with Out of Autoclave technology to permit the creation of larger parts with fewer joints. An 8‐ply pre‐preg layup was constructed to form the cabin body. Prior to lay‐up, a design optimization software called FiberSIM was used to create each ply pattern. This software is integrated with Pro/Engineer to allow for customized draping of each fabric ply over the complex tool surface. Slits and darts are made in the software model to create an optimal design that maintains proper fiber placement and orientation. The flat pattern of each ply is then exported and sent to an automated cutting table where the patterns are cut out of graphite material. Additionally, to assist in lay‐up, a laser projection system (LPT) is used to project outlines of each ply directly onto the tool face for accurate fiber placement and ply build‐up. Finally, as part of the OoA process, a large oven was procured to post‐cure each part. After manufacturing complete, the cabin underwent modal and pressure testing (currently in progress at date of writing) and will go on to be outfitted and used for further ops usage.

Litteken, Douglas↗

NASA NTRS2024

Advanced Pressure Garment Space Suit Sizing Considerations

Fitting a space suit to a person could be considered an art form. Establishing a repeatable fitcheck process to accommodate the full anthropometric range of test subjects for a single suit design is a critical process to be able to prove suit functionality. Suited test subjects can have different preferences on how they fit inside a suit, and different suited test environments can lead to differences in certain suit sizing accommodations. Throughout this paper, the process of achieving an acceptable suit fit for test subjects will be discussed, along with sizing considerations for changes in suit design and test environments. Lessons learned from the Exploration Extravehicular Mobility Unit (xEMU) will be used to describe specific examples, along with key takeaways from additional NASA prototype mobility space suits. The suit fitcheck process starts with utilizing the anthropometric measurements of a test subject to evaluate their relation to the dimensions of space suit hardware in creating a predicted suit sizing configuration. From here, subjective comments and test team observations drive iterations to the suit sizing configuration to culminate in an acceptable suit fit for performance of further test evaluations. Understanding the relation of subjective comments to their impact on altering suit sizing is critical in establishing an acceptable suit fit.

spacesuit↗

NASA NTRSDate not supplied

Advanced Space Suit Sizing Considerations

spacesuit↗

NASA NTRS1992

A process for prototyping onboard payload displays for Space Station Freedom

Significant advances have been made in the area of Human-Computer Interface design. However, there is no well-defined process for going from user interface requirements to user interface design. Developing and designing a clear and consistent user interface for medium to large scale systems is a very challenging and complex task. The task becomes increasingly difficult when there is very little guidance and procedures on how the development process should flow from one stage to the next. Without a specific sequence of development steps each design becomes difficult to repeat, to evaluate, to improve, and to articulate to others. This research contributes a process which identifies the phases of development and products produced as a result of each phase for a rapid prototyping process to be used to develop requirements for the onboard payload displays for Space Station Freedom. The functional components of a dynamic prototyping environment in which this process can be carried out is also discussed. Some of the central questions which are answered here include: How does one go from specifications to an actual prototype? How is a prototype evaluated? How is usability defined and thus measured? How do we use the information from evaluation in redesign of an interface? and Are there techniques which allow for convergence on a design?

Moore, Loretta A.↗

NASA NTRS1986

PS: A nonprocedural language with data types and modules

The Problem Specification (PS) nonprocedural language is a very high level language for algorithm specification. PS is suitable for nonprogrammers, who can specify a problem using mathematically-oriented equations; for expert programmers, who can prototype different versions of a software system for evaluation; and for those who wish to use specifications for portions (if not all) of a program. PS has data types and modules similar to Modula-2. The compiler generates C code. PS is first shown by example, and then efficiency issues in scheduling and code generation are discussed.

Gokhale, M. B.↗

NASA NTRS2009

From Verified Models to Verifiable Code

Declarative specifications of digital systems often contain parts that can be automatically translated into executable code. Automated code generation may reduce or eliminate the kinds of errors typically introduced through manual code writing. For this approach to be effective, the generated code should be reasonably efficient and, more importantly, verifiable. This paper presents a prototype code generator for the Prototype Verification System (PVS) that translates a subset of PVS functional specifications into an intermediate language and subsequently to multiple target programming languages. Several case studies are presented to illustrate the tool's functionality. The generated code can be analyzed by software verification tools such as verification condition generators, static analyzers, and software model-checkers to increase the confidence that the generated code is correct.

Lensink, Leonard↗

NASA NTRS1985

KSC Space Station Operations Language (SSOL)

The Space Station Operations Language (SSOL) will serve a large community of diverse users dealing with the integration and checkout of Space Station modules. Kennedy Space Center's plan to achieve Level A specification of the SSOL system, encompassing both its language and its automated support environment, is presented in the format of a briefing. The SSOL concept is a collection of fundamental elements that span languages, operating systems, software development, software tools and several user classes. The approach outlines a thorough process that combines the benefits of rapid prototyping with a coordinated requirements gathering effort, yielding a Level A specification of the SSOL requirements.

Source record↗

NASA NTRS1998

Scaling of Ion Thrusters to Low Power

Analyses were conducted to examine ion thruster scaling relationships in detail to determine performance limits, and lifetime expectations for thruster input power levels below 0.5 kW. This was motivated by mission analyses indicating the potential advantages of high performance, high specific impulse systems for small spacecraft. The design and development status of a 0.1-0.3 kW prototype small thruster and its components are discussed. Performance goals include thruster efficiencies on the order of 40% to 54% over a specific impulse range of 2000 to 3000 seconds, with a lifetime in excess of 8000 hours at full power. Thruster technologies required to achieve the performance and lifetime targets are identified.

Patterson, Michael J.↗

NASA NTRS2008

Generating Safety-Critical PLC Code From a High-Level Application Software Specification

The benefits of automatic-application code generation are widely accepted within the software engineering community. These benefits include raised abstraction level of application programming, shorter product development time, lower maintenance costs, and increased code quality and consistency. Surprisingly, code generation concepts have not yet found wide acceptance and use in the field of programmable logic controller (PLC) software development. Software engineers at Kennedy Space Center recognized the need for PLC code generation while developing the new ground checkout and launch processing system, called the Launch Control System (LCS). Engineers developed a process and a prototype software tool that automatically translates a high-level representation or specification of application software into ladder logic that executes on a PLC. All the computer hardware in the LCS is planned to be commercial off the shelf (COTS), including industrial controllers or PLCs that are connected to the sensors and end items out in the field. Most of the software in LCS is also planned to be COTS, with only small adapter software modules that must be developed in order to interface between the various COTS software products. A domain-specific language (DSL) is a programming language designed to perform tasks and to solve problems in a particular domain, such as ground processing of launch vehicles. The LCS engineers created a DSL for developing test sequences of ground checkout and launch operations of future launch vehicle and spacecraft elements, and they are developing a tabular specification format that uses the DSL keywords and functions familiar to the ground and flight system users. The tabular specification format, or tabular spec, allows most ground and flight system users to document how the application software is intended to function and requires little or no software programming knowledge or experience. A small sample from a prototype tabular spec application is shown.

Source record↗

NASA NTRS2010

TPSAS-NF1676L-9990-DND

PVS (Prototype Veri cation System)1 is an interactive environment for the specification and verification of systems. PVS provides a strongly typed specification language, which is based on Higher-Order Logic. The type system of PVS supports: sub-typing, dependent-types, abstract data types, parametric types, records, unions, and tuples. The PVS theorem prover includes decision procedures for a variety of theories such as linear arithmetic, propositional logic, and temporal logic. This seminar will provide a gentle introduction to the basic and advanced features of PVS, including: theory interpretations, real number proving, batch proving, rapid prototyping, and strategy development. All these features are illustrated with simple examples and exercises.

César Muñoz↗

NASA NTRS1987

Performance analysis of parallel branch and bound search with the hypercube architecture

With the availability of commercial parallel computers, researchers are examining new classes of problems which might benefit from parallel computing. This paper presents results of an investigation of the class of search intensive problems. The specific problem discussed is the Least-Cost Branch and Bound search method of deadline job scheduling. The object-oriented design methodology was used to map the problem into a parallel solution. While the initial design was good for a prototype, the best performance resulted from fine-tuning the algorithm for a specific computer. The experiments analyze the computation time, the speed up over a VAX 11/785, and the load balance of the problem when using loosely coupled multiprocessor system based on the hypercube architecture.

Mraz, Richard T.↗

NASA NTRS2008

Automated Translation of Safety Critical Application Software Specifications into PLC Ladder Logic

The numerous benefits of automatic application code generation are widely accepted within the software engineering community. A few of these benefits include raising the abstraction level of application programming, shorter product development time, lower maintenance costs, and increased code quality and consistency. Surprisingly, code generation concepts have not yet found wide acceptance and use in the field of programmable logic controller (PLC) software development. Software engineers at the NASA Kennedy Space Center (KSC) recognized the need for PLC code generation while developing their new ground checkout and launch processing system. They developed a process and a prototype software tool that automatically translates a high-level representation or specification of safety critical application software into ladder logic that executes on a PLC. This process and tool are expected to increase the reliability of the PLC code over that which is written manually, and may even lower life-cycle costs and shorten the development schedule of the new control system at KSC. This paper examines the problem domain and discusses the process and software tool that were prototyped by the KSC software engineers.

Leucht, Kurt W.↗

NASA NTRS1992

Seamless transitions from early prototypes to mature operational software - A technology that enables the process for planning and scheduling applications

New and innovative software technology is presented that provides a cost effective bridge for smoothly transitioning prototype software, in the field of planning and scheduling, into an operational environment. Specifically, this technology mixes the flexibility and human design efficiency of dynamic data typing with the rigor and run-time efficiencies of static data typing. This new technology provides a very valuable tool for conducting the extensive, up-front system prototyping that leads to specifying the correct system and producing a reliable, efficient version that will be operationally effective and will be accepted by the intended users.

Hornstein, Rhoda S.↗

NASA NTRS2015

NASA Controller Acceptability Study 1(CAS-1) Experiment Description and Initial Observations

This paper describes the Controller Acceptability Study 1 (CAS-1) experiment that was conducted by NASA Langley Research Center personnel from January through March 2014 and presents partial CAS-1 results. CAS-1 employed 14 air traffic controller volunteers as research subjects to assess the viability of simulated future unmanned aircraft systems (UAS) operating alongside manned aircraft in moderate-density, moderate-complexity Class E airspace. These simulated UAS were equipped with a prototype pilot-in-the-loop (PITL) Detect and Avoid (DAA) system, specifically the Self-Separation (SS) function of such a system based on Stratway+ software to replace the see-and-avoid capabilities of manned aircraft pilots. A quantitative CAS-1 objective was to determine horizontal miss distance (HMD) values for SS encounters that were most acceptable to air traffic controllers, specifically HMD values that were assessed as neither unsafely small nor disruptively large. HMD values between 0.5 and 3.0 nautical miles (nmi) were assessed for a wide array of encounter geometries between UAS and manned aircraft. The paper includes brief introductory material about DAA systems and their SS functions, followed by descriptions of the CAS-1 simulation environment, prototype PITL SS capability, and experiment design, and concludes with presentation and discussion of partial CAS-1 data and results.

Chamberlain, James P.↗

NASA NTRS1990

An expert system based software sizing tool, phase 2

A software tool was developed for predicting the size of a future computer program at an early stage in its development. The system is intended to enable a user who is not expert in Software Engineering to estimate software size in lines of source code with an accuracy similar to that of an expert, based on the program's functional specifications. The project was planned as a knowledge based system with a field prototype as the goal of Phase 2 and a commercial system planned for Phase 3. The researchers used techniques from Artificial Intelligence and knowledge from human experts and existing software from NASA's COSMIC database. They devised a classification scheme for the software specifications, and a small set of generic software components that represent complexity and apply to large classes of programs. The specifications are converted to generic components by a set of rules and the generic components are input to a nonlinear sizing function which makes the final prediction. The system developed for this project predicted code sizes from the database with a bias factor of 1.06 and a fluctuation factor of 1.77, an accuracy similar to that of human experts but without their significant optimistic bias.

Friedlander, David↗

NASA NTRS1974

Six-man, self-contained carbon dioxide concentrator system

A six man, self contained electrochemical carbon dioxide concentrating subsystem was successfully designed and fabricated. It was a preprototype engineering model designed to nominally remove 6.0 kg (13.2 lb) CO2/day with an inlet air CO2 partial pressure of 400 N/sq m (3 mm Hg) and an overcapacity removal capability of 12.0 kg (26.4 lb) CO2/day. The design specifications were later expanded to allow operation at space station prototype CO2 collection subsystem operating conditions.

Powell, J. D.↗