Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “building engineers”

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 307 records · Page 17

Systems Engineering and Reusable Avionics

One concept for future space flights is to construct building blocks for a wide variety of avionics systems. Once a unit has served its original purpose, it can be removed from the original vehicle and reused in a similar or dissimilar function, depending on the function blocks the unit contains. For example: Once a lunar lander has reached the moon's surface, an engine controller for the Lunar Decent Module would be removed and used for a lunar rover motor control unit or for a Environmental Control Unit for a Lunar Habitat. This senior design project included the investigation of a wide range of functions of space vehicles and possible uses. Specifically, this includes: (1) Determining and specifying the basic functioning blocks of space vehicles. (2) Building and demonstrating a concept model. (3) Showing high reliability is maintained. The specific implementation of this senior design project included a large project team made up of Systems, Electrical, Computer, and Mechanical Engineers/Technologists. The efforts were made up of several sub-groups that each worked on a part of the entire project. The large size and complexity made this project one of the more difficult to manage and advise. Typical projects only have 3-4 students, but this project had 10 students from five different disciplines. This paper describes the difference of this large project compared to typical projects, and the challenges encountered. It also describes how the systems engineering approach was successfully implemented so that the students were able to meet nearly all of the project requirements.

Conrad, James M.↗

Systems Engineering Tutorial with Case Studies

Due to the ever-growing number of complex technical problems facing our world, a Systems Engineering approach is needed to assist in successful design, build and implementation of solutions. The interdisciplinary technical structure of current systems, technical processes representing System Design, Technical Management and Product Realization are instrumental in the development and integration of new technologies into mainstream applications. This tutorial will demonstrate the application of Systems Engineering tools to these types of problems. Learning objectives include, understanding how to develop and engineer a conceptual system; understand the importance of teams, communication, requirements definition, interface control, and focus on deliverables; useful tools and techniques for each aspect of the System Engineering process including Model Based Systems Engineering which will be touched upon lightly. Some hands-on problems will be pursued especially in requirements development which is always key to a successful project. Case studies will be presented to assist in the learning process.

Systems Engineering↗

Additive Manufacturing of Low Cost Upper Stage Propulsion Components

NASA is currently developing Additive Manufacturing (AM) technologies and design tools aimed at reducing the costs and manufacturing time of regeneratively cooled rocket engine components. These Low Cost Upper Stage Propulsion (LCUSP) tasks are funded through NASA's Game Changing Development Program in the Space Technology Mission Directorate. The LCUSP project will develop a copper alloy additive manufacturing design process and develop and optimize the Electron Beam Freeform Fabrication (EBF3) manufacturing process to direct deposit a nickel alloy structural jacket and manifolds onto an SLM manufactured GRCop chamber and Ni-alloy nozzle. In order to develop these processes, the project will characterize both the microstructural and mechanical properties of the SLMproduced GRCop-84, and will explore and document novel design techniques specific to AM combustion devices components. These manufacturing technologies will be used to build a 25K-class regenerative chamber and nozzle (to be used with tested DMLS injectors) that will be tested individually and as a system in hot fire tests to demonstrate the applicability of the technologies. These tasks are expected to bring costs and manufacturing time down as spacecraft propulsion systems typically comprise more than 70% of the total vehicle cost and account for a significant portion of the development schedule. Additionally, high pressure/high temperature combustion chambers and nozzles must be regeneratively cooled to survive their operating environment, causing their design to be time consuming and costly to build. LCUSP presents an opportunity to develop and demonstrate a process that can infuse these technologies into industry, build competition, and drive down costs of future engines.

Protz, Christopher↗

Atmosphere of Freedom: Sixty Years at the NASA Ames Research Center

Throughout Ames History, four themes prevail: a commitment to hiring the best people; cutting-edge research tools; project management that gets things done faster, better and cheaper; and outstanding research efforts that serve the scientific professions and the nation. More than any other NASA Center, Ames remains shaped by its origins in the NACA (National Advisory Committee for Aeronautics). Not that its missions remain the same. Sure, Ames still houses the world's greatest collection of wind tunnels and simulation facilities, its aerodynamicists remain among the best in the world, and pilots and engineers still come for advice on how to build better aircraft. But that is increasingly part of Ames' past. Ames people have embraced two other missions for its future. First, intelligent systems and information science will help NASA use new tools in supercomputing, networking, telepresence and robotics. Second, astrobiology will explore lore the prospects for life on Earth and beyond. Both new missions leverage Ames long-standing expertise in computation and in the life sciences, as well as its relations with the computing and biotechnology firms working in the Silicon Valley community that has sprung up around the Center. Rather than the NACA missions, it is the NACA culture that still permeates Ames. The Ames way of research management privileges the scientists and engineers working in the laboratories. They work in an atmosphere of freedom, laced with the expectation of integrity and responsibility. Ames researchers are free to define their research goals and define how they contribute to the national good. They are expected to keep their fingers on the pulse of their disciplines, to be ambitious yet frugal in organizing their efforts, and to always test their theories in the laboratory or in the field. Ames' leadership ranks, traditionally, are cultivated within this scientific community. Rather than manage and supervise these researchers, Ames leadership merely guided them, represents them to NASA headquarters and the world outside, then steps out of the way before they get run over.

Bugos, Glenn E.↗

NASA Extreme Environment Mission Operations: Science Operations Development for Human Exploration

The purpose of NASA Extreme Environment Mission Operations (NEEMO) mission 16 in 2012 was to evaluate and compare the performance of a defined series of representative near-Earth asteroid (NEA) extravehicular activity (EVA) tasks under different conditions and combinations of work systems, constraints, and assumptions considered for future human NEA exploration missions. NEEMO 16 followed NASA's 2011 Desert Research and Technology Studies (D-RATS), the primary focus of which was understanding the implications of communication latency, crew size, and work system combinations with respect to scientific data quality, data management, crew workload, and crew/mission control interactions. The 1-g environment precluded meaningful evaluation of NEA EVA translation, worksite stabilization, sampling, or instrument deployment techniques. Thus, NEEMO missions were designed to provide an opportunity to perform a preliminary evaluation of these important factors for each of the conditions being considered. NEEMO 15 also took place in 2011 and provided a first look at many of the factors, but the mission was cut short due to a hurricane threat before all objectives were completed. ARES Directorate (KX) personnel consulted with JSC engineers to ensure that high-fidelity planetary science protocols were incorporated into NEEMO mission architectures. ARES has been collaborating with NEEMO mission planners since NEEMO 9 in 2006, successively building upon previous developments to refine science operations concepts within engineering constraints; it is expected to continue the collaboration as NASA's human exploration mission plans evolve.

Bell, Mary S.↗

Critical Low-Noise Technologies Being Developed for Engine Noise Reduction Systems Subproject

NASA's previous Advanced Subsonic Technology (AST) Noise Reduction Program delivered the initial technologies for meeting a 10-year goal of a 10-dB reduction in total aircraft system noise. Technology Readiness Levels achieved for the engine-noise-reduction technologies ranged from 4 (rig scale) to 6 (engine demonstration). The current Quiet Aircraft Technology (QAT) project is building on those AST accomplishments to achieve the additional noise reduction needed to meet the Aerospace Technology Enterprise's 10-year goal, again validated through a combination of laboratory rig and engine demonstration tests. In order to meet the Aerospace Technology Enterprise goal for future aircraft of a 50- reduction in the perceived noise level, reductions of 4 dB are needed in both fan and jet noise. The primary objectives of the Engine Noise Reduction Systems (ENRS) subproject are, therefore, to develop technologies to reduce both fan and jet noise by 4 dB, to demonstrate these technologies in engine tests, and to develop and experimentally validate Computational Aero Acoustics (CAA) computer codes that will improve our ability to predict engine noise.

Grady, Joseph E.↗

Engineering the System and Technical Integration

Approximately 80% of the problems encountered in aerospace systems have been due to a breakdown in technical integration and/or systems engineering. One of the major challenges we face in designing, building, and operating space systems is: how is adequate integration achieved for the systems various functions, parts, and infrastructure? This Contractor Report (CR) deals with part of the problem of how we engineer the total system in order to achieve the best balanced design. We will discuss a key aspect of this question - the principle of Technical Integration and its components, along with management and decision making. The CR will first provide an introduction with a discussion of the Challenges in Space System Design and meeting the challenges. Next is an overview of Engineering the System including Technical Integration. Engineering the System is expanded to include key aspects of the Design Process, Lifecycle Considerations, etc. The basic information and figures used in this CR were presented in a NASA training program for Program and Project Managers Development (PPMD) in classes at Georgia Tech and at Marshall Space Flight Center (MSFC). Many of the principles and illustrations are extracted from the courses we teach for MSFC.

Blair, J. C.↗

Host turbine heat transfer overview

Improved methods of predicting airfoil local metal temperatures require advances in the understanding of the physics and methods of analytically predicting the following four aerothermal loads: hot gas flow over airfoils, heat transfer rates on the gas-side of airfoils, cooling air flow inside airfoils, and heat transfer rates on the coolant-side of airfoils. A systematic building block research approach is being pursued to investigate these four areas of concern from both the experimental and analytical sides. Experimental approaches being pursued start with fundamental experiments using simple shapes and flat plates in wind tunnels, progress to more realistic cold and hot cascade tests using airfoils, continue to progress in large low-speed rigs and turbines and warm turbines, and finally, combine all the interactive effects in tests using real engines or real engine type turbine rigs. Analytical approaches being pursued also build from relatively simple steady two dimensional inviscid flow and boundary layer heat transfer codes to more advanced steady two and three dimensional viscous flow and heat transfer codes. These advanced codes provide more physics to model better the interactive effects and the true real-engine environment.

Rohde, J. E.↗

To whomsoever will read in order to build

Rocket flight equations, spacecraft construction, interplanetary exploration, solar energy, human engineering, and instrumentation for space flight

PLANETARY EXPLORATION↗

"Smart" Sensor Module

An assembly that contains a sensor, sensor-signal-conditioning circuitry, a sensor-readout analog-to-digital converter (ADC), data-storage circuitry, and a microprocessor that runs special-purpose software and communicates with one or more external computer(s) has been developed as a prototype of "smart" sensor modules for monitoring the integrity and functionality (the "health") of engineering systems. Although these modules are now being designed specifically for use on rocket-engine test stands, it is anticipated that they could also readily be designed to be incorporated into health-monitoring subsystems of such diverse engineering systems as spacecraft, aircraft, land vehicles, bridges, buildings, power plants, oilrigs, and defense installations. The figure is a simplified block diagram of the "smart" sensor module. The analog sensor readout signal is processed by the ADC, the digital output of which is fed to the microprocessor. By means of a standard RS-232 cable, the microprocessor is connected to a local personal computer (PC), from which software is downloaded into a randomaccess memory in the microprocessor. The local PC is also used to debug the software. Once the software is running, the local PC is disconnected and the module is controlled by, and all output data from the module are collected by, a remote PC via an Ethernet bus. Several smart sensor modules like this one could be connected to the same Ethernet bus and controlled by the single remote PC. The software running in the microprocessor includes driver programs for operation of the sensor, programs that implement self-assessment algorithms, programs that implement protocols for communication with the external computer( s), and programs that implement evolutionary methodologies to enable the module to improve its performance over time. The design of the module and of the health-monitoring system of which it is a part reflects the understanding that the main purpose of a health-monitoring system is to detect damage and, therefore, the health-monitoring system must be able to function effectively in the presence of damage and should be capable of distinguishing between damage to itself and damage to the system being monitored. A major benefit afforded by the self-assessment algorithms is that in the output of the module, the sensor data indicative of the health of the engineering system being monitored are coupled with a confidence factor that quantifies the degree of reliability of the data. Hence, the output includes information on the health of the sensor module itself in addition to information on the health of the engineering system being monitored.

Mahajan, Ajay↗

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.↗

Lessons Learned in Systems Engineering Availability and Recommendations for Mission Technical Leaders

In spaceflight missions at Goddard Space Flight Center (GSFC), the Mission System Engineer (MSE) is the technical leader of the overall engineering team and also is the Independent Engineering Technical Authority. The responsibility of this role includes the definition of the mission design architecture, concept of operations, and mission requirements, management of risk throughout the development, and verification and validation of the final system performance and function amongst other duties. This responsibility inherently requires time management, enabling focus on a balanced development with appropriate risk. Time is the most valuable resource of the MSE. The system engineer’s availability to interact with the development team (often product or component design leads and technicians, often in different worksites) to discover and mitigate mission risks during development is key to mission success. This paper presents examples from Lunar Reconnaissance Orbiter, Landsat 9, and Neutron star Interior Composition ExploreR (NICER) which represent in-house and out-of-house hardware builds. These examples demonstrate how interactions between the Mission Systems Engineers and other project and partner engineers result in discovery of critical risks, leading to early mitigation with significant cost and performance savings. These three missions would have suffered test failures or on-orbit failures had their MSEs not set aside time to visit engineers and technicians that were working on key pieces of space flight hardware. Availability is more than just time; it is openness to listen to concerns and questions. It begins by building a level of trust in the team that it is safe to ask questions or share concerns without the fear of blame or additional workload. It also requires enabling informal conversations (over lunch, coffee, in the clean room, or at the team members desk, etc.) where key information can be exchanged, and team members may even provide an easy-to-implement mitigation idea for another subsystem. Availability is a highly valuable commodity and completely non-obvious to protect and optimize. The natural tendency of engineers is to keep themselves busy with solving problems that they know about. This paper is encouraging MSEs to resist this tendency to try and solve all the complex problems themselves and actively devote daily time to learning and solving problems that are found with informal communications with other team members.

Lessons Learned↗

The X-43A Flight Research Program: Lessons Learned on the Road to Mach 10

During an aerospace engineer's undergraduate studies, he or she will attend classes in aerodynamics, thermodynamics, structures, stability and control, dynamics, design, propulsion, and computer science, along with the related courses in mathematics, physics, statistics, and chemistry required to understand the material. Upon graduation, the new engineer will have acquired a basic knowledge of how to build an aerospace vehicle. What only comes through experience, however, is the understanding of the inevitable imperfect process through which an aerospace vehicle is built. This is the adventure of turning a basic concept into functional hardware. Engineers working on a project must often deal with ambiguous situations. They are routinely asked by management to provide risk assessments of a project, yet even after careful analysis uncertainties remain. The project must be accomplished within finite limits of time and money. The question an engineer answers is whether the solution to potential problem is worth the cost and schedule delay, or if the solution might actually be worse than the problem it is meant to solve. Review protocols are established to ensure that an unknown has not been overlooked. But these cannot protect against an unknown unknown. Examples of these situations can be found in the history of the X-43A Hyper-X (Hypersonic Experiment) program. In this NASA project, a supersonic combustion ramjet (scramjet) engine was flight tested on a subscale vehicle. The X-43A Hyper-X Research Vehicle (HXRV) was launched from a B-52B mothership, then boosted to the test speed by a modified Pegasus rocket first stage, called the Hyper-X Launch Vehicle (HXLV). Once at the proper speed and altitude, the X-43A separated from the booster, stabilized itself, and then the engine test began. Although wind-tunnel scramjet engine tests had begun in the late 1950s, before the Hyper-X program there had never been an actual in-flight test of such an engine integrated with an appropriate airframe. Thus, while the scramjet had successfully operated in the artificial airflow of wind tunnels, the concept had yet to be proven in real air. These conditions meant changes in density and temperature, as well as changes in angle of attack and sideslip of a free-flying vehicle. A wind tunnel is limited in its ability to simulate these subtle factures, which have a major impact on almost any vehicle, but especially that of a scramjet's performance. The Hyper-X project was to provide a real-world benchmark of the ground test data. The full scale X-43A engine would be operated in the wind tunnel, and then flown, and the data from its operation would then be compared with projections. If these matched, the wind tunnel data would be considered a reliable design tool for future scramjet. If there were significant differences, the reasons for these would have to be identified. Until such information was available, scramjets would lack the technological maturity to be considered for future space launch or high-speed atmospheric flight vehicles.

Peebles, Curtis↗

High-Temperature Magnetic Bearings for Gas Turbine Engines

Magnetic bearings are the subject of a new NASA Lewis Research Center and U.S. Army thrust with significant industry participation, and coordination with other Government agencies. The NASA/Army emphasis is on high-temperature applications for future gas turbine engines. Magnetic bearings could increase the reliability and reduce the weight of these engines by eliminating the lubrication system. They could also increase the DN (diameter of the bearing times rpm) limit on engine speed and allow active vibration cancellation systems to be used--resulting in a more efficient, "more electric" engine. Finally, the Integrated High-Performance Turbine Engine Technology (IHPTET) Program, a joint Department of Defense/industry program, identified a need for a hightemperature (as high as 1200 F) magnetic bearing that could be demonstrated in a phase III engine. This magnetic bearing is similar to an electric motor. It has a laminated rotor and stator made of cobalt steel. Wound around the stator are a series of electrical wire coils that form a series of electric magnets around the circumference. The magnets exert a force on the rotor. A probe senses the position of the rotor, and a feedback controller keeps it in the center of the cavity. The engine rotor, bearings, and case form a flexible structure that contains a large number of modes. The bearing feedback controller, which could cause some of these modes to become unstable, could be adapted to varying flight conditions to minimize seal clearances and monitor the health of the system. Cobalt steel has a curie point greater than 1700 F, and copper wire has a melting point beyond that. Therefore, practical limitations associated with the maximum magnetic field strength in the cobalt steel and the stress in the rotating components limit the temperature to about 1200 F. The objective of this effort is to determine the limits in temperature and speed of a magnetic bearing operating in an engine. Our approach is to use our in-house experience in magnets, mechanical components, high-temperature materials, and surface lubrication to build and test a magnetic bearing in both a rig and an engine. Testing will be done at Lewis or through cooperative programs in industrial facilities.

Source record↗

Fast Track Lunar NTR Systems Assessment for NASA's First Lunar Outpost and Its Evolvability to Mars

Integrated systems and missions studies are presented for an evolutionary lunar-to-Mars space transportation system (STS) based on nuclear thermal rocket (NTR) technology. A 'standardized' set of engine and stage components are identified and used in a 'building block' fashion to configure a variety of piloted and cargo, lunar and Mars vehicles. The reference NTR characteristics include a thrust of 50 thousand pounds force (klbf), specific impulse (I(sub sp)) of 900 seconds, and an engine thrust-to-weight ratio of 4. 3. For the National Aeronautics and Space Administrations (NASA) First Lunar Outpost (FLO) mission, and expendable NTR stage powered by two such engines can deliver approximately 96 metric tonnes (t) to trans-lunar injection (TLI) conditions for an initial mass in low Earth orbit (IMLEO) of approximately 198 t compared to 250 t for a cryogenic chemical system. The stage liquid hydrogen (LH2) tank has a diameter, length, and capacity of 10 m, 14.5 m and 66 t, respectively. By extending the stage length and LH2 capacity to approximately 20 m and 96 t, a single launch Mars cargo vehicle could deliver to an elliptical Mars parking orbit a 63 t Mars excursion vehicle (MEV) with a 45 t surface payload. Three 50 klbf engines and the two standardized LH2 tanks developed for the lunar and Mars cargo vehicles are used to configure the vehicles supporting piloted Mars missions as early as 2010. The 'modular' NTR vehicle approach forms the basis for an efficient STS able to handle the needs of a wide spectrum of lunar and Mars missions.

Borowski, Stanley K.↗

Next Generation Flight Displays Using HTML5

The Human Integrated Vehicles and Environments (HIVE) lab at Johnson Space Center (JSC) is focused on bringing together inter-disciplinary talent to design and integrate innovative human interface technologies for next generation manned spacecraft. As part of this objective, my summer internship project centered on an ongoing investigation in to building flight displays using the HTML5 standard. Specifically, the goals of my project were to build and demo "flight-like" crew and wearable displays as well as create a webserver for live systems being developed by the Advanced Exploration Systems (AES) program. In parallel to my project, a LabVIEW application, called a display server, was created by the HIVE that uses an XTCE (XML (Extensible Markup Language) Telemetry and Command Exchange) parser and CCSDS (Consultative Committee for Space Data System) space packet decoder to translate telemetry items sent by the CFS (Core Flight Software) over User Datagram Protocol (UDP). It was the webserver's job to receive these UDP messages and send them to the displays. To accomplish this functionality, I utilized Node.js and the accompanying Express framework. On the display side, I was responsible for creating the power system (AMPS) displays. I did this by using HTML5, CSS and JavaScript to create web pages that could update and change dynamically based on the data they received from the webserver. At this point, I have not started on the commanding, being able to send back to the CFS, portion of the displays but hope to have this functionality working by the completion of my internship. I also created a way to test the webserver's functionality without the display server by making a JavaScript application that read in a comma-separate values (CSV) file and converted it to XML which was then sent over UDP. One of the major requirements of my project was to build everything using as little preexisting code as possible, which I accomplished by only using a handful of JavaScript libraries. As a side project, I created a model of the HIVE lab and Building 29 using SketchUp. I obtained the floorplans of the building from the JSC Geographic Information Systems (GIS), which were computer-aided design (CAD) files, and imported them into SketchUp. I then took those floorplans and created a 3D model of the building from them. Working in conjunction with the Hybrid Reality lab in Building 32, the SketchUp model was imported into Unreal Engine for use with the HTC Vive. Using the Vive, I was able to interact with the model I created in virtual reality (VR). The purpose of this side project was to be able to visualize potential lab layouts and mockup designs as they are in development in order to finalize design decisions. Pending approval, the model that I created will be used in the Build-As-You-Test: Can Hybrid Reality Improve the SE/HSI Design Process project in the fall. Getting the opportunity to work at NASA has been one of the most memorable experiences of my life. Over the course of my internship, I improved my programming and web development abilities substantially. I will take all the skills and experiences I have had while at NASA back to school with me in the fall and hope to pursue a career in the aerospace industry after graduating in the spring.

Greenwood, Brian↗

Telerobotic Excavator Designed to Compete in NASA's Lunabotics Mining Competition

The second annual NASA Lunabotics Mining competition is to be held in May 23-28, 2011. The goal of the competition is for teams of university level students to design, build, test and compete with a fully integrated lunar excavator on a simulated lunar surface. Our team, named Lunar Solutions I, will be representing Temple University's College of Engineering in the competition. The team's main goal was to build a robot which is able to compete with other teams, and ultimately win the competition. The main challenge of the competition was to build a wireless robot that can excavate and collect a minimum of 10 kilograms of the regolith material within 15 minutes. The robot must also be designed to operate in conditions similar to those found on the lunar surface. The design of the lunar excavator is constrained by a set of requirements determined by NASA and detailed in the competition's rulebook. The excavator must have the ability to communicate with the "main base" wirelessly, and over a Wi-Fi network. Human operators are located at a remote site approximately 60 meters away from the simulated lunar surface upon which the robot must excavate the lunar regolith surface. During the competition, the robot will operate in a separate area from the control room in an area referred to as the "Lunarena." From the control room, the operators will have to control the robot using visual feedback from cameras placed both within the arena and on the robot. Using this visual feedback the human operators control the robots movement using both keyboard and joystick commands. In order to place in the competition, a minimum of 10 kg of regolith material has to be excavated, collected, and dumped into a specific location. For that reason, the robot must be provided with an effective and powerful excavation system. Our excavator uses tracks for the drive system. After performing extensive research and trade studies, we concluded that tracks would be the most effective method for transporting the excavator. When designing the excavation system, we analyzed several design options from the previous year's competition. We decided to use a front loader to collect the material, rather than a conveyer belt system or auger. Many of the designs from last year's competition used a conveyer belt mechanism to mine regolith and dump it into a temporary storage bin place on the robot. Using the front end loader approach allowed us to combine the scooping system and storage unit, which meant that the excavation system required less space.

Nash, Rodney↗

2012 Alabama Lunabotics Systems Engineering Paper

Excavation will hold a key role for future lunar missions. NASA has stated that "advances in lunar regolith mining have the potential to significantly contribute to our nation's space vision and NASA space exploration operations." [1]. The Lunabotics Mining Competition is an event hosted by NASA that is meant to encourage "the development of innovative lunar excavation concepts from universities which may result in clever ideas and solutions which could be applied to an actual lunar excavation device or payload." [2]. Teams entering the competition must "design and build a remote controlled or autonomous excavator, called a lunabot, that can collect and deposit a minimum of 10 kilograms of lunar simulant within 10 minutes." [2]. While excavation will play an important part in lunar missions, there will still be many other tasks that would benefit from robotic assistance. An excavator might not be as well suited for these tasks as other types of robots might be. For example a lightweight rover would do well with reconnaissance, and a mobile gripper arm would be fit for manipulation, while an excavator would be comparatively clumsy and slow in both cases. Even within the realm of excavation it would be beneficial to have different types of excavators for different tasks, as there are on Earth. The Alabama Lunabotics Team at the University of Alabama has made it their goal to not only design and build a robot that could compete in the Lunabotics Mining Competition, but would also be a multipurpose tool for future NASA missions. The 2010-2011 resulting robot was named the Modular Omnidirectional Lunar Excavator (MOLE). Using the Systems Engineering process and building off of two years of Lunabotics experience, the 20ll-2012 Alabama Lunabotics team (Team NASACAR) has improved the MOLE 1.0 design and optimized it for the 2012 Lunabotics Competition rules [I]. A CAD model of MOLE 2.0 can be seen below in Fig. 1.

Baker, Justin↗