Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “building prototypes”

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.

569 records · Page 32
All sourcesNASA NTRSDOE OSTI
NASA NTRS1994

Accommodating Heterogeneity in a Debugger for Distributed Computations

In an ongoing project at NASA Ames Research Center, we are building debugger for distributed computations running on a heterogeneous set of machines. Historically, such debuggers have been built as front-ends to existing source-level debuggers on the target platforms. In effect, these back-end debuggers are providing a collection of debugger services to a client. The major drawback is that because of inconsistencies among the back-end debuggers, the front-end must use a different protocol when talking to each back-end debugger. This can make the front-end quite complex. We have avoided this complexity problem by defining the client-server debugger protocol. While it does require vendors to adapt their existing debugger code to meet the protocol, vendors are generally interested in doing so because the approach has several advantages. In addition to solving the heterogenous platform debugging problem, it will be pos~sible to write interesting debugger user interfaces that can be easily ported across a variety of machines. This will likely encourage investment in application-domain specific debuggers. In fact, the user interface of our debugger will be geared to scientists developing computational fluid dynamics codes. This paper describes some of the problems encountered in developing a portable debugger for heterogenous, distributed computing and how the architecture of our debugger avoids them. It then provides a detailed description of the debugger client-server protocol. Some of the more interesting attributes of the protocol are: (1) It is object-oriented; (2) It uses callback functions to capture the asynchronous nature of debugging in a procedural fashion; (3) It contains abstractions, such as in-line instrumentation, for the debugging of computationally intensive programs; (4) For remote debugging, it has operations that enable the implementor to optimize message passing traffic between client and server. The soundness of the protocol is being tested through the implementation of a prototype client and server pair.

Hood, Robert↗
NASA NTRS2010

Radiation Beamline Testbeds for the Simulation of Planetary and Spacecraft Environments for Human and Robotic Mission Risk Assessment

The Center for Radiation Engineering and Science for Space Exploration (CRESSE) at Prairie View A&M University, Prairie View, Texas, USA, is establishing an integrated, multi-disciplinary research program on the scientific and engineering challenges faced by NASA and the international space community caused by space radiation. CRESSE focuses on space radiation research directly applicable to astronaut health and safety during future long term, deep space missions, including Martian, lunar, and other planetary body missions beyond low earth orbit. The research approach will consist of experimental and theoretical radiation modeling studies utilizing particle accelerator facilities including: 1. NASA Space Radiation Laboratory (NSRL) at Brookhaven National Laboratory; 2. Proton Synchrotron at Loma Linda University Medical Center; and 3. Los Alamos Neutron Science Center (LANSCE) at Los Alamos National Laboratory. Specifically, CRESSE investigators are designing, developing, and building experimental test beds that simulate the lunar and Martian radiation environments for experiments focused on risk assessment for astronauts and instrumentation. The testbeds have been designated the Bioastronautics Experimental Research Testbeds for Environmental Radiation Nostrum Investigations and Education (BERT and ERNIE). The designs of BERT and ERNIE will allow for a high degree of flexibility and adaptability to modify experimental configurations to simulate planetary surface environments, planetary habitats, and spacecraft interiors. In the nominal configuration, BERT and ERIE will consist of a set of experimental zones that will simulate the planetary atmosphere (Solid CO2 in the case of the Martian surface.), the planetary surface, and sub-surface regions. These experimental zones can be used for dosimetry, shielding, biological, and electronic effects radiation studies in support of space exploration missions. BERT and ERNIE are designed to be compatible with the experimental areas associated with the above facilities. CRESSE has broad expertise in space radiation in the areas of space radiation environment modeling, Monte-Carlo radiation transport modeling, space radiation instrumentation and dosimetry, radiation effects on electronics, and multi-functional composite shielding materials. The BERT and ERNIE testbeds will be utilized in individual and collaborative research incorporating this expertise. The research goal is to maximize the technical readiness level (TRL) of radiation instrumentation for human and robotic missions, optimizing the return value of CRESSE for NASA exploration and international co-operative missions. Outcomes and knowledge from research utilizing BERT and ERNIE will be applied to a variety of scientific and engineering disciplines vital for safe and reliable execution of future space exploration missions, which can be negatively impacted by the space radiation environment. The testbeds will be central to a variety of university educational activities and educational goals of NASA. Specifically, BERT and ERNIE will enhance educational opportunities in science, technology, engineering and mathematics (STEM) disciplines for engineering and science students at PVAMU, a historically black college/university. Preliminary data on prototype testbed configurations, including simulated lunar regolith (JSC-1A stimulant based on Apollo 11 samples), regolith/polyethylene composites, and dry ice, will be presented to demonstrate the usefulness of BERT and ERNIE in radiation beam line experiments.

Wilkins, Richard↗
NASA NTRS2005

Crane-Load Contact Sensor

An electronic instrument has been developed as a prototype of a portable crane-load contact sensor. Such a sensor could be helpful in an application in which the load rests on a base in a horizontal position determined by vertical alignment pins (see Figure 1). If the crane is not positioned to lift the load precisely vertically, then the load can be expected to swing once it has been lifted clear of the pins. If the load is especially heavy, large, and/or fragile, it could hurt workers and/or damage itself and nearby objects. By indicating whether the load remains in contact with the pins when it has been lifted a fraction of the length of the pins, the crane-load contact sensor helps the crane operator determine whether it is safe to lift the load clear of the pins: If there is contact, then the load is resting against the sides of the pins and, hence, it may not be safe to lift; if contact is occasionally broken, then the load is probably not resting against the pins, so it should be safe to lift. It is assumed that the load and base, or at least the pins and the surfaces of the alignment holes in the load, are electrically conductive, so the instrument can use electrical contact to indicate mechanical contact. However, DC resistance cannot be used as an indicator of contact for the following reasons: The load and the base are both electrically grounded through cables (the load is grounded through the lifting cable of the crane) to prevent discharge of static electricity. In other words, the DC resistance between the load and the pins is always low, as though they were always in direct contact. Therefore, instead of DC resistance, the instrument utilizes the AC electrical impedance between the pins and the load. The signal frequency used in the measurement is high enough (.1 MHz) that the impedance contributed by the cables and the electrical ground network of the building in which the crane and the base are situated is significantly greater than the contact impedance between the pins and the load. The instrument includes a signal generator and voltage-measuring circuitry, and is connected to the load and the base as shown in Figure 2. The output of the signal generator (typically having amplitude of the order of a volt) is applied to the load via a 50-resistor, and the voltage between the load and the pins is measured. When the load and the pins are not in contact, the impedance between them is relatively high, causing the measured voltage to exceed a threshold value. When the load and the pins are in contact, the impedance between them falls to a much lower value, causing the voltage to fall below the threshold value. The voltage-measuring circuitry turns on a red light-emitting diode (LED) to indicate the lower-voltage/ contact condition. Whenever the contact has been broken and the non-contact/higher-voltage condition has lasted for more than 2 ms, the voltage-measuring circuitry indicates this condition by blinking a green LED.

Youngquist, Robert↗
NASA NTRS2002

ISAIA: Interoperable Systems for Archival Information Access

The ISAIA project was originally proposed in 1999 as a successor to the informal AstroBrowse project. AstroBrowse, which provided a data location service for astronomical archives and catalogs, was a first step toward data system integration and interoperability. The goals of ISAIA were ambitious: '...To develop an interdisciplinary data location and integration service for space science. Building upon existing data services and communications protocols, this service will allow users to transparently query hundreds or thousands of WWW-based resources (catalogs, data, computational resources, bibliographic references, etc.) from a single interface. The service will collect responses from various resources and integrate them in a seamless fashion for display and manipulation by the user.' Funding was approved only for a one-year pilot study, a decision that in retrospect was wise given the rapid changes in information technology in the past few years and the emergence of the Virtual Observatory initiatives in the US and worldwide. Indeed, the ISAIA pilot study was influential in shaping the science goals, system design, metadata standards, and technology choices for the virtual observatory. The ISAIA pilot project also helped to cement working relationships among the NASA data centers, US ground-based observatories, and international data centers. The ISAIA project was formed as a collaborative effort between thirteen institutions that provided data to astronomers, space physicists, and planetary scientists. Among the fruits we ultimately hoped would come from this project would be a central site on the Web that any space scientist could use to efficiently locate existing data relevant to a particular scientific question. Furthermore, we hoped that the needed technology would be general enough to allow smaller, more-focused community within space science could use the same technologies and standards to provide more specialized services. A major challenge to searching for data across a broad community is that information that describe some data products are either not relevant to other data or not applicable in the same way. Some previous metadata standard development efforts (e.g., in the earth science and library communities) have produced standards that are very large and difficult to support. To address this problem, we studied how a standard may be divided into separable pieces. Data providers that wish to participate in interoperable searches can support only those parts of the standard that are relevant to them. We prototyped a top-level metadata standard that was small and applicable to all space science data.

Hanisch, Robert J.↗
NASA NTRSDate not supplied

Enabling a Voice Management System for Space Applications

The sustainable missions beyond Low Earth Orbit (LEO) envisioned for NASA’s Artemis program will require autonomous capabilities. Moreover, Artemis mission crews will need a means to efficiently interact with a spacecraft’s autonomous systems. This interaction can be facilitated by voice and speech communications because voice-based controls enable users to interact hands- and eyes-free, allowing the user to better focus on critical tasks. The goal of our project was to explore the knowledge and technology needed to successfully design effective Voice User Interfaces (VUIs) for autonomous systems utilizing Human Centered Design (HCD) principles. The focus of the human factors’ aspect of engineering, pays close attention to psychological and physiological principles in the development of autonomous crew operation systems. A main objective was to understand how a crew member, through voice interaction, could efficiently and intuitively communicate with a notional autonomous vehicle system manager. This project was a part of the NASA Moon to Mars eXploration Systems and Habitation (M2M X-Hab) 2020 Academic Innovation Challenge. The work from the BLiSS Team, at the University of Michigan, resulted in the design of a system persona, Diego, to which an astronaut may quickly build trust with autonomous systems, to alleviate known stressors on mental health expected during long duration space missions. Optimal software to facilitate integration of the system persona into a reference Lunar orbiting Gateway station was defined. Additionally, a Speech to Text (STT) system and a Graphical User Interface (GUI) that could be implemented in future missions was developed on an Internet of Things (IOT) platform. The Voice User Interface (VUI) design for the M2M X-Hab 2020 project leveraged previous technology developed by the BLiSS team to incorporate a voice-based interface into NASA’s Platform for Autonomous Systems (NPAS) software. This required technologies to convert voice to text, conduct semantic interpretations, and convert responses from the autonomous system to text and to speech; additionally, the spacecraft background noise environment was assessed, a noise mitigation technique was developed, and a relatable personality for the autonomous system was developed in order to facilitate human-like conversations. The success of our effort was largely due to the diversity of the team that included expertise in Space Systems Engineering, Human Computer Interaction, Aerospace Engineering, Computer Science, Biomedical Engineering, and Applied Physics. The diverse perspectives fostered elaborate discussions, resulting in the conception of three main subsystems: (1) User-System, (2) NPAS-System, and (3) Environment-System. The VUI was unique and had to be efficient and intuitive. For this project, 5 subteams were formed, each with a separate objective, Voice Design team, Background Noise Mitigation team, Software Integration team and Graphical User Interface team. The BLiSS team crafted a personality for the VUI to enable human-like conversation and drive user adoption and trust. User surveys were completed and used to help determine the required VUI system personality traits by capturing perspectives and expectations of prospective “Artemis Generation Astronauts”. To further simulate human-like conversations, the system had to be able to quickly interpret user speech and be able to integrate with NASA’s NPAS platform for quick and reliable information transfer. The outcomes of our research were: (1) a working prototype user interface, that is compatible with NASA’s NPAS platform; (2) software that demonstrates the ability of the VUI system to interpret user requests and respond appropriately; (3) the capability to implement fully expanded conversations between user and system using intuitive communication in four request categories; and (4) software and hardware recommendations that optimize the system’s ability to operate in a noisy environment. Our research has laid the foundation for the development of VUI’s for autonomy, and provides a baseline for future VUI developments.

Voice user interface↗
NASA NTRS2011

Lunabotics Mining Competition: Inspiration Through Accomplishment

NASA's Lunabotics Mining Competition is designed to promote the development of interest in space activities and STEM (Science, Technology, Engineering, and Mathematics) fields. The competition uses excavation, a necessary first step towards extracting resources from the regolith and building bases on the moon. The unique physical properties of lunar regolith and the reduced 1/6th gravity, vacuum environment make excavation a difficult technical challenge. Advances in lunar regolith mining have the potential to significantly contribute to our nation's space vision and NASA space exploration operations. The competition is conducted annually by NASA at the Kennedy Space Center Visitor Complex. The teams that can use telerobotic or autonomous operation to excavate a lunar regolith geotechnical simulant, herein after referred to as Black Point-1 (or BP-1) and score the most points (calculated as an average of two separate 10-minute timed competition attempts) will eam points towards the Joe Kosmo Award for Excellence and the scores will reflect ranking in the on-site mining category of the competition. The minimum excavation requirement is 10.0 kg during each competition attempt and the robotic excavator, referred to as the "Lunabot", must meet all specifications. This paper will review the achievements of the Lunabotics Mining Competition in 2010 and 2011, and present the new rules for 2012. By providing a framework for robotic design and fabrication, which culminates in a live competition event, university students have been able to produce sophisticated lunabots which are tele-operated. Multi-disciplinary teams are encouraged and the extreme sense of accomplishment provides a unique source of inspiration to the participating students, which has been shown to translate into increased interest in STEM careers. Our industrial sponsors (Caterpillar, Newmont Mining, Harris, Honeybee Robotics) have all stated that there is a strong need for skills in the workforce related to robotics and automated machines. In 2010, 22 United States (US) universities competed, and in May 2011 the competition was opened to international participation, with 46 Universities attending. There were 12 international teams and 34 US teams. This combined total directly inspired an estimated 544 university students. More students and the public were engaged via internet broadcasting and social networking media. This is expected to be of value for actual future space missions, as knowledge is gained from testing many innovative prototypes in simulated lunar regolith. More information is available at www.nasa.gov/lunabotics/.

Mueller, Robert P.↗
NASA NTRS2000

NASA's Design and Development of a Field Goniometer Instrument Using Solid Works

With NASA suffering severe funding cutbacks, engineers at NASA are required to produce state-of-the-art hardware with limited personnel and financial resources. In light of these constraints, the new NASA mandate is to build better, faster and cheaper. In April of 1998, Stennis Space Center's Commercial Remote Sensing Program contracted to the Systems Engineering Division at NASA Ames Research Center to develop a device known as a Field Goniometer. A Field Goniometer is a device that measures bi-directional reflectance of a target, such as vegetation, relative to the sun and an imaging system in an aircraft or spacecraft. The device is able to provide a spectral fingerprint of the surface it is measuring in wavelengths from 350nm-2500nm using a hyperspectral imager. To accomplish this project, several obstacles had to be overcome. First, the design had to be completed in less than four months. Second, due to the complexity of the design, the use of solid modeling was highly desirable but most of the group's solid modelers were assigned to other jobs. Third, the amount of funding available from the customer was one half to one third the funding typically expended for a job of this nature. Our choices for this project were to design with standard 2-D CAD systems currently used in-house or train additional engineers on our existing solids package or purchase a new solid model package. The use of a 2D CAD system was very undesirable due to the complexity of the design. Using our existing solids modeler would have required a learning curve for our engineers that would be incompatible with our schedule. Prior to this project, a member of our design group researched the solid modeling industry and decided to purchase SolidWorks. After examining the product for ease of use, modeling capability, training time required and cost, we decided our highest probability of success would be to design with Solidworks. During the design phase, our fabrication group was able to provide input at the very early stages, which added significant benefit to the final product. Fabrication cost and schedule savings have been realized by having complex part geometries translated directly from the SolidWorks design models to Surfcam and other computer-aided manufacturing (CAM) software. This direct model translation capability optimized the fabrication processes. The end result was that we were able to successfully complete the project on time and on budget. Other advantages of using SolidWorks, as cited by the design team, include a rapid negotiation of the initial learning curve, the ability to develop solid model hardware prototypes (used to communicate the design intent to both the customer and the fabricator), and the ability to work as a team collaborating on a large, complex model. These types of tools and efforts represent our response to NASA's challenge to produce higher quality products within shorter design and fabrication times.

Turner, Mark↗
NASA NTRSDate not supplied

VIPER Lunar Rover Agile Mission Systems

Agile development methods, which have gone from outlier to mainstream in software development, are poised to expand into all aspects of space mission development. Modern software development operates on a principle of continuous deployment, where progress is verified not with conventional metrics, but with a continuous build, available to key stakeholders, enabling direct examination of the state of the code base, and assessment of progress through demonstration of capability. Delivery times are measured in weeks, not months. Stakeholders are part of the process on an ongoing basis. The cost of change is comparatively low and requirements, which often are not precisely defined at the start of a project, may be iteratively refined in a series of agile development cycles. Agile methods are compatible with traditional system engineering methods and may be tailored to the space operations environment. The low cost of change and iterative development cycles of agile enable requirements to be defined as outcomes and constraints, with design details to be refined during the development cycle. We are now at a point where agile methods may be extended beyond software, to Mission Systems, including the Mission Operations System and the Ground Data System. For NASA’s VIPER Lunar Rover Mission, scheduled to land at a lunar pole in late 2023, we are developing the Mission System using agile methods. As in agile software, where the measure of progress is working code, in agile mission system development, the measure of capability is what we can demonstrate. Demonstrations over presentations. We demonstrate mission system capability using simulations. The concept of operations, from commanding, to driving the rover, to how we downlink images for evaluation for a near-real time command cycle, will be tested and proven in simulation, years before we begin the traditional simulation cycle for training. “Say it then simulate it.” We develop and refine our designs using simulations, with an emphasis on new components of the system that are not well known early. For example, the required duration of a mission planning cycle for a lunar surface asset such as VIPER, that operates twenty-four hours a day, seven days a week, with continuous communications and a unique set of constraints based on the physics of the lunar poles and the line of site to Earth, is a unique problem in mission planning that is unlikely to be solved in a series of meetings. A small number of requirements specifying the outcomes may serve as the jumping off point to an agile development cycle, with demonstration in simulations. We have already demonstrated this process with simulations of rover driver decision time. VIPER is driven using near-real time command and control to waypoints. The driver decision time between waypoints is a fundamental enabling unit of productivity to accomplish the mission timeline. We have validated driver decision time in simulations of rover driving at the lunar South Pole, using the prototype mission tools for driving, command and control. The capability to develop and refine designs using simulations as part of agile Mission System development cycle changes the nature of team interactions, creating a focus on doing, rather than analyzing and documenting. Waterfall development cycles were, in part, a product of the significant cost of change in the early days of spaceflight. When the cost of change is high, it is vital to get your requirements right at the outset, because the system will be built to those specifications, and, when change is expensive, you better get it right early. However, modern technology has greatly lowered the cost of change, enabling iterative, rapid development cycles, in which key operations concepts may be tested and refined during development. Extending agile development to the Mission System for VIPER is a significant step in moving agile development methods for space operations beyond software, to the Mission System.

Agile↗
NASA NTRS2000

Information Power Grid: Distributed High-Performance Computing and Large-Scale Data Management for Science and Engineering

We use the term "Grid" to refer to distributed, high performance computing and data handling infrastructure that incorporates geographically and organizationally dispersed, heterogeneous resources that are persistent and supported. This infrastructure includes: (1) Tools for constructing collaborative, application oriented Problem Solving Environments / Frameworks (the primary user interfaces for Grids); (2) Programming environments, tools, and services providing various approaches for building applications that use aggregated computing and storage resources, and federated data sources; (3) Comprehensive and consistent set of location independent tools and services for accessing and managing dynamic collections of widely distributed resources: heterogeneous computing systems, storage systems, real-time data sources and instruments, human collaborators, and communications systems; (4) Operational infrastructure including management tools for distributed systems and distributed resources, user services, accounting and auditing, strong and location independent user authentication and authorization, and overall system security services The vision for NASA's Information Power Grid - a computing and data Grid - is that it will provide significant new capabilities to scientists and engineers by facilitating routine construction of information based problem solving environments / frameworks. Such Grids will knit together widely distributed computing, data, instrument, and human resources into just-in-time systems that can address complex and large-scale computing and data analysis problems. Examples of these problems include: (1) Coupled, multidisciplinary simulations too large for single systems (e.g., multi-component NPSS turbomachine simulation); (2) Use of widely distributed, federated data archives (e.g., simultaneous access to metrological, topological, aircraft performance, and flight path scheduling databases supporting a National Air Space Simulation systems}; (3) Coupling large-scale computing and data systems to scientific and engineering instruments (e.g., realtime interaction with experiments through real-time data analysis and interpretation presented to the experimentalist in ways that allow direct interaction with the experiment (instead of just with instrument control); (5) Highly interactive, augmented reality and virtual reality remote collaborations (e.g., Ames / Boeing Remote Help Desk providing field maintenance use of coupled video and NDI to a remote, on-line airframe structures expert who uses this data to index into detailed design databases, and returns 3D internal aircraft geometry to the field); (5) Single computational problems too large for any single system (e.g. the rotocraft reference calculation). Grids also have the potential to provide pools of resources that could be called on in extraordinary / rapid response situations (such as disaster response) because they can provide common interfaces and access mechanisms, standardized management, and uniform user authentication and authorization, for large collections of distributed resources (whether or not they normally function in concert). IPG development and deployment is addressing requirements obtained by analyzing a number of different application areas, in particular from the NASA Aero-Space Technology Enterprise. This analysis has focussed primarily on two types of users: the scientist / design engineer whose primary interest is problem solving (e.g. determining wing aerodynamic characteristics in many different operating environments), and whose primary interface to IPG will be through various sorts of problem solving frameworks. The second type of user is the tool designer: the computational scientists who convert physics and mathematics into code that can simulate the physical world. These are the two primary users of IPG, and they have rather different requirements. The results of the analysis of the needs of these two types of users provides a broad set of requirements that gives rise to a general set of required capabilities. The IPG project is intended to address all of these requirements. In some cases the required computing technology exists, and in some cases it must be researched and developed. The project is using available technology to provide a prototype set of capabilities in a persistent distributed computing testbed. Beyond this, there are required capabilities that are not immediately available, and whose development spans the range from near-term engineering development (one to two years) to much longer term R&D (three to six years). Additional information is contained in the original.

Johnston, William E.↗
NASA NTRS2013

Kennedy Space Center: Swamp Works

When I began my internship with the Granular Mechanics and Regolith Operations laboratory (GMRO), also known as Swamp Works, I was given the unique opportunity to shadow many teams working on various projects, and decide what projects I wanted to take part in. Before I go into details of my experiences at Swamp Works, I would like to take a moment to explain what I discovered Swamp Works to be. Swamp Works is a family of hardworking, dedicated, and driven people from various backgrounds and skill sets. These people all work to advance technologies and make science fiction science fact through means of rapid prototyping. They support and encourage failure as an option when learning new things, as long as lesson learned from said failure. In fact, their motto states "Fail, Fast, Forward." What this means is, not if but when one fails he or she must do so quickly and spring forward from the failure so that his or her progress is not delayed. With this acceptance, it provided me the confidence to dive into a multitude of projects working in various fields and with a wide range of skill sets. The first project I joined was Badger. My motivation for taking on this project was the opportunity I would have to obtain valuable experience working with 3D modeling and 3D printing technologies. Badger was a digging apparatus to be used in a highly dusty environment in a material known as Regolith. Regolith is a scientific term for the dirt or top soil found on planetary bodies. Regolith contains a large quantity of sediments less than lOppm and as a result poses a challenge of keeping it out of any cracks and crevices. Furthermore, regolith can create high levels of electrostatic energy, which can prove damaging to sensitive electrical hardware. With these characteristics in mind, I decided to take on the task of designing and manufacturing a dust proof cover for the sensitive electrical hardware. When I began this project, I did not have the slightest idea as to how to use 3D modeling software or a means of manufacturing a viable product. As I went along with variants of the design, I became very proficient with a 3D modeling program known as CREO 2.0. Upon completion of my 3D design, I then had the task of manufacturing and having, in my hands, a usable model. To do this I had to work with additive printing technologies also known as 3D printing. Through my experiences working with Badger, I realized that 3D modeling is the focal point in much of engineering. With this in mind, I have embraced this fact and decided to further my experience with this software so that I may become a more valuable asset to any firm later in my career. Mid-way through work with Badger, I picked up another project in which I found much interest. I ha~ the opportunity to work side by side with a materials and composites guru in manufacturing carbon composite coupons (test strips) for performing stress, strain, and sheer analysis on. Being from a surfing, kiteboarding, and other water sport background I have always been interested in board design. With this in mind, it is no wonder why I found interest in such a project. I had the opportunity to refine Mold preparatory, composite layup, and composite curing techniques. Following manufacturing of these composite strips, I then performed various stress tests and logged my results. With these results, future teams could create lighter, stronger, and more cost effective composite structures for use in varieties of applications. After my experiences with materials and composites testing, I have obtained crucial appreciation for detailed documentation and analysis that material sciences involve. However, as interesting as composite materials testing has been, I do not feel this is where my future career lies. Another, more on the side, project I have been involved in is building a 626 cubic foot regolith containment chamber for doing full scale testing of robotic systems. This chamber is built of high strength aluminum scaffold materials, 80/20, and massive panels of Lexan. Once the chamber is completed, it is be filled with 120 tons of regolith and dubbed the largest regolith test chamber in the world. Through my experiences with building "Big Bin" as we called it, I discovered my demand for engaging and hands on activities. Through all of my incredible experiences working with the Swamp Works at Kennedy Space Center; I have obtained crucial knowledge, insights, and experiences that have fuelled, shaped, and will continue to drive me toward my ultimate goal of obtaining not only a degree in Engineering, but obtaining a job that I can call a career. I want to give much thanks to all of those who mentored me along my journey, and to all who made this opportunity a reality.

DeFilippo, Anthony Robert↗
NASA NTRS2007

Diaphragm Pump With Resonant Piezoelectric Drive

A diaphragm pump driven by a piezoelectric actuator is undergoing development. This pump is intended to be a prototype of lightweight, highly reliable pumps for circulating cooling liquids in protective garments and high-power electronic circuits, and perhaps for some medical applications. The pump would be highly reliable because it would contain no sliding seals or bearings that could wear, the only parts subject to wear would be two check valves, and the diaphragm and other flexing parts could be designed, by use of proven methods, for extremely long life. Because the pump would be capable of a large volumetric flow rate and would have only a small dead volume, its operation would not be disrupted by ingestion of gas, and it could be started reliably under all conditions. The prior art includes a number piezoelectrically actuated diaphragm pumps. Because of the smallness of the motions of piezoelectric actuators (typical maximum strains only about 0.001), the volumetric flow rates of those pumps are much too small for typical cooling applications. In the pump now undergoing development, mechanical resonance would be utilized to amplify the motion generated by the piezoelectric actuator and thereby multiply the volumetric flow rate. The prime mover in this pump would be a stack of piezoelectric ceramic actuators, one end of which would be connected to a spring that would be part of a spring-and-mass resonator structure. The mass part of the resonator structure would include the pump diaphragm (see Figure 1). Contraction of the spring would draw the diaphragm to the left, causing the volume of the fluid chamber to increase and thereby causing fluid to flow into the chamber. Subsequent expansion of the spring would push the diaphragm to the right, causing the volume of the fluid chamber to decrease, and thereby expelling fluid from the chamber. The fluid would enter and leave the chamber through check valves. The piezoelectric stack would be driven electrically to make it oscillate at the resonance frequency of the spring and- mass structure. This frequency could be made high enough (of the order of 400 Hz) that the masses of all components could be made conveniently small. The resonance would amplify the relatively small motion of the piezoelectric stack (a stroke of the order of 10 m) to a diaphragm stroke of the order of 0.5 mm. The exact amplification factor would depend on the rate of damping of oscillations; this, in turn, would depend on details of design and operation, including (but not limited to) the desired pressure rise and volumetric flow rate. In order to obtain resonance with large displacement, the damping rate must be low enough that the energy imparted to the pumped fluid on each stroke is much less than the kinetic and potential energy exchanged between the mass and spring during each cycle of oscillation. To minimize the power demand of the pump, a highly efficient drive circuit would be used to excite the piezoelectric stack. This circuit (see Figure 2) would amount to a special-purpose regenerative, switching power supply that would operate in a power-source mode during the part of an oscillation cycle when the excitation waveform was positive and in a power-recovery mode during the part of the cycle when the excitation waveform was negative. The circuit would include a voltage-boosting dc-to-dc converter that would convert between a supply potential of 24 Vdc and the high voltage needed to drive the piezoelectric stack. Because of the power-recovery feature, the circuit would consume little power. It should be possible to build the circuit as a compact unit, using readily available components.

Izenson, Michael G.↗