Search NASA⌕ Search

SEARCH · Search NASA

Results for “Evolvable Hardware”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

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

At least 217 records · Page 12

Automated Software for Crewed Spacecraft - Bridging the Gap from Sci Fi to Reality

With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.

Robert C Dempsey↗

Flight evaluation results from the general-aviation advanced avionics system program

A demonstration advanced avionics system (DAAS) for general-aviation aircraft was tested at NASA Ames Research Center to provide information required for the design of reliable, low-cost, advanced avionics systems which would make general-aviation operations safer and more practicable. Guest pilots flew a DAAS-equipped NASA Cessna 402-B aircraft to evaluate the usefulness of data busing, distributed microprocessors, and shared electronic displays, and to provide data on the DAAS pilot/system interface for the design of future integrated avionics systems. Evaluation results indicate that the DAAS hardware and functional capability meet the program objective. Most pilots felt that the DAAS representative of the way avionics systems would evolve and felt the added capability would improve the safety and practicability of general-aviation operations. Flight-evaluation results compiled from questionnaires are presented, the results of the debriefings are summarized. General conclusions of the flight evaluation are included.

Callas, G. P.↗

Flight evaluation results from the general-aviation advanced avionics system program

A demonstration advanced avionics system (DAAS) for general-aviation aircraft was tested at NASA Ames Research Center to provide information required for the design of reliable, low-cost, advanced avionics systems which would make general-aviation operations safer and more practicable. Guest pilots flew a DAAS-equipped NASA Cessna 402-B aircraft to evaluate the usefulness of data busing, distributed microprocessors, and shared electronic displays, and to provide data on the DAAS pilot/system interface for the design of future integrated avionics systems. Evaluation results indicate that the DAAS hardware and functional capability meet the program objective. Most pilots felt that the DAAS representative of the way avionics systems would evolve and felt the added capability would improve the safety and practicability of general-aviation operations. Flight-evaluation results compiled from questionnaires are presented, the results of the debriefings are summarized. General conclusions of the flight evaluation are included. Previously announced in STAR as N84-10042

Callas, G. P.↗

Spacelab dedicated discipline laboratory (DDL) utilization concept

The dedicated discipline laboratory (DDL) concept is a new approach for implementing Spacelab missions that involves the grouping of science instruments into mission complements of single or compatible disciplines. These complements are evolved in such a way that the DDL payloads can be left intact between flights. This requires the dedication of flight hardware to specific payloads on a long-term basis and raises the concern that the purchase of additional flight hardware will be required to implement the DDL program. However, the payoff is expected to result in significant savings in mission engineering and assembly effort. A study has been conducted recently to quantify both the requirements for new hardware and the projected mission cost savings. It was found that some incremental additions to the current inventory will be needed to fly the mission model assumed. Cost savings of $2M to 6.5M per mission were projected in areas analyzed in depth, and additional savings may occur in areas for which detailed cost data were not available.

Wunsch, P.↗

Development and Implementation of NASA's Lead Center for Rocket Propulsion Testing

With the new millennium, NASA's John C. Stennis Space Center (SSC) continues to develop and refine its role as rocket test service provider for NASA and the Nation. As Lead Center for Rocket Propulsion Testing (LCRPT), significant progress has been made under SSC's leadership to consolidate and streamline NASA's rocket test infrastructure and make this vital capability truly world class. NASA's Rocket Propulsion Test (RPT) capability consists of 32 test positions with a replacement value in excess of $2B. It is dispersed at Marshall Space Flight Center (MSFC), Johnson Space Center (JSC)-White Sands Test Facility (WSTF), Glenn Research Center (GRC)-Plum Brook (PB), and SSC and is sized appropriately to minimize duplication and infrastructure costs. The LCRPT also provides a single integrated point of entry into NASA's rocket test services. The RPT capability is managed through the Rocket Propulsion Test Management Board (RPTMB), chaired by SSC with representatives from each center identified above. The Board is highly active, meeting weekly, and is key to providing responsive test services for ongoing operational and developmental NASA and commercial programs including Shuttle, Evolved Expendable Launch Vehicle, and 2nd and 3rd Generation Reusable Launch Vehicles. The relationship between SSC, the test provider, and the hardware developers, like MSFC, is critical to the implementation of the LCRPT. Much effort has been expended to develop and refine these relationships with SSC customers. These efforts have met with success and will continue to be a high priority to SSC for the future. To data in the exercise of its role, the LCRPT has made 22 test assignments and saved or avoided approximately $51M. The LCRPT directly manages approximately $30M annually in test infrastructure costs including facility maintenance and upgrades, direct test support, and test technology development. This annual budges supports rocket propulsion test programs which have an annual budget in excess of $150M. As the LCRPT continues to develop, customer responsiveness and lower cost test services will be major themes. In that light, SSC is embarking on major test technology development activities ensuring long range goals of safer, more responsive, and more cost effective test services are realized. The LCRPT is also focusing on the testing requirements for advanced propulsion systems. This future planning is key to defining and fielding the ability to test these new technologies in support of the hardware developers.

Dawson, Michael C.↗

Risk Assessment Challenges in the Ares I Upper Stage

NASA Marshall Space Flight Center (MSFC) is currently at work developing hardware and systems for the Ares I rocket that will send future astronauts into orbit. Built on cutting-edge launch technologies, evolved powerful Apollo and Space Shuttle propulsion elements, and decades of NASA spaceflight experience, Ares I is the essential core of a safe, reliable, cost-effective space transportation system -- one that will carry crewed missions back to the moon, on to Mars and out into the solar system. Ares I is an in-line, two-stage rocket configuration topped by the Orion crew vehicle and its launch abort system. In addition to the vehicle's primary mission -carrying crews of four to six astronauts to Earth orbit --Ares I may also use its 25-ton payload capacity to deliver resources and supplies to the International Space Station, or to "park" payloads in orbit for retrieval by other spacecraft bound for the moon or other destinations. Crew transportation to the International Space Station is planned to begin no later than 2014. The first lunar excursion is scheduled for the 2020 timeframe. This paper presents the challenges in designing the Ares I upper stage for reliability and safety while minimizing weight and maximizing performance.

Stott, James E.↗

Integration Process for the Habitat Demonstration Unit

The Habitat Demonstration Unit (HDU) is an experimental exploration habitat technology and architecture test platform designed for analog demonstration activities The HDU project has required a team to integrate a variety of contributions from NASA centers and outside collaborators and poses a challenge in integrating these disparate efforts into a cohesive architecture To complete the development of the HDU from conception in June 2009 to rollout for operations in July 2010, a cohesive integration strategy has been developed to integrate the various systems of HDU and the payloads, such as the Geology Lab, that those systems will support The utilization of interface design standards and uniquely tailored reviews have allowed for an accelerated design process Scheduled activities include early fit-checks and the utilization of a Habitat avionics test bed prior to equipment installation into HDU A coordinated effort to utilize modeling and simulation systems has aided in design and integration concept development Modeling tools have been effective in hardware systems layout, cable routing and length estimation, and human factors analysis Decision processes on the shell development including the assembly sequence and the transportation have been fleshed out early on HDU to maximize the efficiency of both integration and field operations Incremental test operations leading up to an integrated systems test allows for an orderly systems test program The HDU will begin its journey as an emulation of a Pressurized Excursion Module (PEM) for 2010 field testing and then may evolve to a Pressurized Core Module (PCM) for 2011 and later field tests, depending on agency architecture decisions The HDU deployment will vary slightly from current lunar architecture plans to include developmental hardware and software items and additional systems called opportunities for technology demonstration One of the HDU challenges has been designing to be prepared for the integration of presently unanticipated systems Results of the HDU field tests will influence future designs of habitat systems.

Gill, Tracy↗

Swarming Robot Design, Construction and Software Implementation

In this paper is presented an overview of the hardware design, construction overview, software design and software implementation for a small, low-cost robot to be used for swarming robot development. In addition to the work done on the robot, a full simulation of the robotic system was developed using Robot Operating System (ROS) and its associated simulation. The eventual use of the robots will be exploration of evolving behaviors via genetic algorithms and builds on the work done at the University of New Mexico Biological Computation Lab.

construction overview↗

I-deas TMG to NX Space Systems Thermal Model Conversion and Computational Performance Comparison

CAD/CAE packages change on a continuous basis as the power of the tools increase to meet demands. End -users must adapt to new products as they come to market and replace legacy packages. CAE modeling has continued to evolve and is constantly becoming more detailed and complex. Though this comes at the cost of increased computing requirements Parallel processing coupled with appropriate hardware can minimize computation time. Users of Maya Thermal Model Generator (TMG) are faced with transitioning from NX I -deas to NX Space Systems Thermal (SST). It is important to understand what differences there are when changing software packages We are looking for consistency in results.

Thermal Model Generator (TMG)↗

U.S. Spacesuit Legacy: Maintaining it for the Future

The history of U.S. spacesuit development and its use are rich with information on lessons learned, and constitutes a valuable legacy to those designing spacesuits for the future, as well as to educators, students, and the general public. The genesis of lessons learned is best understood by studying the evolution of past spacesuit programs - how the challenges and pressures of the times influenced the direction of the various spacesuit programs. This paper shows how the legacy of various spacesuit-related programs evolved in response to these forces. Important aspects of how this U.S. spacesuit legacy is being preserved today is described, including the archiving of spacesuit hardware, important documents, videos, oral history, and the rapidly expanding U.S. Spacesuit Knowledge Capture program.

Chullen, Cinda↗

SPHERES: From Ground Development to Operations on ISS

SPHERES (Synchronized Position Hold Engage and Reorient Experimental Satellites) is an internal International Space Station (ISS) Facility that supports multiple investigations for the development of multi-spacecraft and robotic control algorithms. The SPHERES Facility on ISS is managed and operated by the SPHERES National Lab Facility at NASA Ames Research Center (ARC) at Moffett Field California. The SPHERES Facility on ISS consists of three self-contained eight-inch diameter free-floating satellites which perform the various flight algorithms and serve as a platform to support the integration of experimental hardware. To help make science a reality on the ISS, the SPHERES ARC team supports a Guest Scientist Program (GSP). This program allows anyone with new science the possibility to interface with the SPHERES team and hardware. In addition to highlighting the available SPHERES hardware on ISS and on the ground, this presentation will also highlight ground support, facilities, and resources available to guest researchers. Investigations on the ISS evolve through four main phases: Strategic, Tactical, Operations, and Post Operations. The Strategic Phase encompasses early planning beginning with initial contact by the Principle Investigator (PI) and the SPHERES program who may work with the PI to assess what assistance the PI may need. Once the basic parameters are understood, the investigation moves to the Tactical Phase which involves more detailed planning, development, and testing. Depending on the nature of the investigation, the tactical phase may be split into the Lab Tactical Phase or the ISS Tactical Phase due to the difference in requirements for the two destinations. The Operations Phase is when the actual science is performed; this can be either in the lab, or on the ISS. The Post Operations Phase encompasses data analysis and distribution, and generation of summary status and reports. The SPHERES Operations and Engineering teams at ARC is composed of experts who can guide the Payload Developer (PD) and Principle Investigator (PI) in reaching critical milestones to make their science a reality using the SPHERES platform. From performing integrated safety and verification assessments, to assisting in developing crew procedures and operations products, to organizing, planning, and executing all test sessions, to helping manage data products, the SPHERES team at ARC is available to support microgravity research with the SPEHRES Guest Scientist Program.

ISS Research↗

An Introduction to Flight Software Development: FSW Today, FSW 2010

Experience and knowledge gained from ongoing maintenance of Space Shuttle Flight Software and new development projects including Cockpit Avionics Upgrade are applied to projected needs of the National Space Exploration Vision through Spiral 2. Lessons learned from these current activities are applied to create a sustainable, reliable model for development of critical software to support Project Constellation. This presentation introduces the technologies, methodologies, and infrastructure needed to produce and sustain high quality software. It will propose what is needed to support a Vision for Space Exploration that places demands on the innovation and productivity needed to support future space exploration. The technologies in use today within FSW development include tools that provide requirements tracking, integrated change management, modeling and simulation software. Specific challenges that have been met include the introduction and integration of Commercial Off the Shelf (COTS) Real Time Operating System for critical functions. Though technology prediction has proved to be imprecise, Project Constellation requirements will need continued integration of new technology with evolving methodologies and changing project infrastructure. Targets for continued technology investment are integrated health monitoring and management, self healing software, standard payload interfaces, autonomous operation, and improvements in training. Emulation of the target hardware will also allow significant streamlining of development and testing. The methodologies in use today for FSW development are object oriented UML design, iterative development using independent components, as well as rapid prototyping . In addition, Lean Six Sigma and CMMI play a critical role in the quality and efficiency of the workforce processes. Over the next six years, we expect these methodologies to merge with other improvements into a consolidated office culture with all processes being guided by automated office assistants. The infrastructure in use today includes strict software development and configuration management procedures, including strong control of resource management and critical skills coverage. This will evolve to a fully integrated staff organization with efficient and effective communication throughout all levels guided by a Mission-Systems Architecture framework with focus on risk management and attention toward inevitable product obsolescence. This infrastructure of computing equipment, software and processes will itself be subject to technological change and need for management of change and improvement,

Gouvela, John↗

Hardware Evolution of Analog Speed Controllers for a DC Motor

This viewgraph presentation provides information on the design of analog speed controllers for DC motors on aerospace systems. The presentation includes an overview of controller evolution, evolvable controller configuration, an emphasis on proportion integral (PI) controllers, schematic diagrams, and experimental results.

Gwaltney, David A.↗

Design Tools for Reconfigurable Hardware in Orbit (RHinO)

The Reconfigurable Hardware in Orbit (RHinO) project is focused on creating a set of design tools that facilitate and automate design techniques for reconfigurable computing in space, using SRAM-based field-programmable-gate-array (FPGA) technology. These tools leverage an established FPGA design environment and focus primarily on space effects mitigation and power optimization. The project is creating software to automatically test and evaluate the single-event-upsets (SEUs) sensitivities of an FPGA design and insert mitigation techniques. Extensions into the tool suite will also allow evolvable algorithm techniques to reconfigure around single-event-latchup (SEL) events. In the power domain, tools are being created for dynamic power visualiization and optimization. Thus, this technology seeks to enable the use of Reconfigurable Hardware in Orbit, via an integrated design tool-suite aiming to reduce risk, cost, and design time of multimission reconfigurable space processors using SRAM-based FPGAs.

French, Mathew↗

Automated microbial metabolism laboratory

The labeled release concept was advanced to accommodate a post- Viking mission designed to extend the search, to confirm the presence of, and to characterize any Martian life found, and to obtain preliminary information on control of the life detected. The advanced labeled release concept utilizes four test chambers, each of which contains either an active or heat sterilized sample of the Martian soil. A variety of C-14 labeled organic substrates can be added sequentially to each soil sample and the resulting evolved radioactive gas monitored. The concept can also test effects of various inhibitors and environmental parameters on the experimental response. The current Viking '75 labeled release hardware is readily adaptable to the advanced labeled release concept.

Source record↗

Motivational contracting in space programs - Government and industry prospectives

NASA's Marshall Space Flight Center has used incentive-free policies in contracting for Apollo's Saturn Launch vehicle hardware, as well as award-fee contracts for major development and early production programs in the case of the Space Shuttle Program. These programs have evolved to a point at which multiple incentive fees are useful in motivating cost reductions and assuring timely achievement of delivery requirements and flight mission goals. An examination is presently conducted of the relative success of these motivation-oriented techniques, drawing on the comments of both government and industry personnel.

Clough, D. R.↗

Growing the Space Station's electrical power plant

For over a decade NASA LeRC has been defining, demonstrating, and evaluating power electronic components and multi-kilowatt, multiply redundant, electrical power systems as part of OAST charter. Whether one considers aircraft (commercial transport/military), Space Station Freedom, growth station, launch vehicles, or the new Human Exploration Initiative, the conclusions remain the same: high frequency AC power distribution and control is superior to all other approaches for achieving a fast, smart, safe, versatile, and growable electrical power system that will meet a wide range of mission options. To meet the cost and operability goals of future aerospace missions that require significantly higher electrical power and longer durations, we must learn to integrate multiple technologies in ways that enhance overall system synergisms. The way NASA is doing business in space electric power is challenged and some approaches for evolving large space vehicles and platforms in well constructed steps to provide safe, ground testable, growable, smart systems that provide simple, replicative logic structures, which enable hardware and software verification, validation, and implementation are proposed. Viewgraphs are included.

Sundberg, Gale R.↗

NASA's Space Launch System Program Update

Hardware and software for the world's most powerful launch vehicle for exploration is being welded, assembled, and tested today in high bays, clean rooms and test stands across the United States. NASA's Space Launch System (SLS) continued to make significant progress in the past year, including firing tests of both main propulsion elements, manufacturing of flight hardware, and the program Critical Design Review (CDR). Developed with the goals of safety, affordability, and sustainability, SLS will deliver unmatched capability for human and robotic exploration. The initial Block 1 configuration will deliver more than 70 metric tons (t) (154,000 pounds) of payload to low Earth orbit (LEO). The evolved Block 2 design will deliver some 130 t (286,000 pounds) to LEO. Both designs offer enormous opportunity and flexibility for larger payloads, simplifying payload design as well as ground and on-orbit operations, shortening interplanetary transit times, and decreasing overall mission risk. Over the past year, every vehicle element has manufactured or tested hardware, including flight hardware for Exploration Mission 1 (EM-1). This paper will provide an overview of the progress made over the past year and provide a glimpse of upcoming milestones on the way to a 2018 launch readiness date.

May, Todd↗