Search NASA⌕ Search

SEARCH · Search NASA

Results for “Mobile platform”

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Swamp Works Regolith Compaction Technologies

While the level of compaction below the lunar surface increases quickly after only a few cm of depth, in many cases during a construction mission there will be a need to excavate and transport regolith to a new location for cut-and-fill or horizontal construction of structures such as berms. In these cases to achieve high levels of bulk density, compaction must be per-formed. Additionally, in some cases surface technologies such as systems that sinter/melt the surface may desire the maximum possible compaction at the sur-face to improve melting/heating performance and the final material strength properties. Kennedy Space Center’s (KSC) Swamp Works has developed two means of compaction, lunar and mar-tian compaction. Planetary Autonomous Compaction Technology (PACT) which is part of the Multifunction End Effector for Regolith Compaction Acquisition and Transfer (MEERCAT) robotic arm end effector system’s capabilities and the Site Preparation Tooling for Operations on Mobility Platforms (STOMP) vibratory roller compactor. PACT on MEERCAT has been demonstrated to a TRL 5 and STOMP to a TRL 4 in ambient testing. The results of PACT on MEERCAT and STOMP testing will be shared with results for various simulants including BP-1, ICN-LHT-1G (aka CSM-LHT-1G), RDW-LHT-1GH (a simulant developed for the Mason Tipping Point to match characteristics of ICN-LHT-1G), and Exolith LHS-1E. This will also include discussions on methods used to verify relative density before and after compaction and means to verify density effects below depth. To calculate relative density, maximum and minimum densities for simulants were taken from literature and additional lab testing (publication in work).

redwire↗
NASA NTRS2014

Demonstration of Prognostics-Enabled Decision Making Algorithms on a Hardware Mobile Robot Test Platform

Prognostics-enabled Decision Making (PDM) is an emerging research area that aims to integrate prognostic health information and knowledge about the future operating conditions into the process of selecting subsequent actions for the system. Previous work developing and testing PDM algorithms has been done in simulation; this paper describes the effort leading to a successful demonstration of PDM algorithms on a hardware mobile robot platform. The hardware platform, based on the K11 planetary rover prototype, was modified to allow injection of selected fault modes related to the rover’s electrical power subsystem. The PDM algorithms were adapted to the hardware platform, including development of a software module framework, a new route planner, and modifications to increase the algorithms’ robustness to sensor noise and system timing issues. A set of test scenarios was chosen to demonstrate the algorithms’ capabilities. The modifications to run with a hardware platform, the test scenarios, and the test results are described in detail. The results show a successful use of PDM algorithms on a hardware test platform to optimize mission planning in the presence of electrical system faults.

Prognosis↗
NASA NTRSDate not supplied

Restoration of NASA's Mobile Analytical Lunar Platform (MALP) as a Prototype Science Exploration Device using a Public, Private, Academic (PPA) Model

A prototype 6-wheeled rover originally developed by NASA JSC for astronaut transport has been modernized and augmented to support concepts for telerobotic exploration of the lunar surface. The ongoing project has employed teams of undergraduate senior engineering students at Texas A&M University (TAMU) to retrofit the Mobile Analytical Lunar Platform (MALP) with wireless technology for telerobotic operations, and to add a robotic arm for regolith sample collection, sieving, storage and transportation.

Telerobotic Rover↗
NASA NTRS2016

ATHLETE as a Mobile ISRU and Regolith Construction Platform

The All-Terrain Hex-Limbed Extra-Terrestrial Explorer (ATHLETE) robotic mobility platform can provide precision positioning and mobility for site preparation and regolith construction needs. ATHLETE is a multi-use platform designed to use swap-out tools and implements that can be applied to any number of tasks that need precision limb manipulation or mobility. Major capabilities include off-loading habitats, transporting surface assets, robotically assembling outposts from multiple mission manifests, and supporting science and technology objectives. This paper describes conceptual approaches for supporting NASA regolith construction research, such as additive construction, modular brick and panel factory, and mobile ISRU platform.

human spaceflight↗
NASA NTRS2017

Abstract - Belbas, Nicholas (EC2)

Originally, I was brought into the Design and Analysis Branch in the Crew and Thermal Systems to work on administrative tasks like archiving and scheduling. However, I ended up splitting my time between secretarial tasks and a technical project. My technical project was originally meant to be a wireless sensor package for the 20ft Spacecraft Thermal Vacuum Chamber in the B7 High Bay. I would be using a miniature wifi development board and a temperature/humidity sensor along with custom 3D modeling to accomplish this. However, after some discussion with my technical mentor, the plan was changed to a mobile autonomous self-charging sensor platform. A mobile platform will allow the sensors to be moved around without depressurizing the chamber. Also, the self-charging aspect of the package allows for almost unlimited time in the chamber. If the on-board battery runs low, the robot can easily be driven to its charging dock and continue to transmit while charging. The driving base is based around a Raspberry Pi 3 board with a 12C PMW DC Motor controller and a PWM controller driving two small gear motors. The sensor transmitter itself is a RHT03 temperature and humidity sensor and Cozir CO2 sensor connected to an ESP8266 Huzzah board. The power distribution system utilizes a pair of 3.7v 3600mah lipo batteries wired to Powerboost 500 boards. Also, the self-charging mechanism utilizes two 12v-max inductive charging coils wired into the same Powerboost boards as the battery. The Raspberry pi is running Python 3.3 for the driving base and Javascript MJPEG library for transmitting live video from the onboard camera. The sensor package is running Arduino-based C++ and the program capturing the data is running PyqtGraph Python and HTML. The shell of the robot itself is a 3D printed case that will (work in progress) snap together. The photo to the left shows the two halves separated from each other. The black shell contains the power distribution boards and connectors while the white shell contains the driving base and data systems.

Belbas, Nicholas↗
NASA NTRS2008

NASA NDE Applications for Mobile MEMS Devices and Sensors

NASA would like new devices and sensors for performing nondestructive evaluation (NDE) of aerospace vehicles. These devices must be small in size/volume, mass, and power consumption. The devices must be autonomous and mobile so they can access the internal structures of aircraft and spacecraft and adequately monitor the structural health of these craft. The platforms must be mobile in order to transport NDE sensors for evaluating structural integrity and determining whether further investigations will be required. Microelectromechanical systems (MEMS) technology is crucial to the development of the mobile platforms and sensor systems. This paper presents NASA s needs for micro mobile platforms and MEMS sensors that will enable NDE to be performed on aerospace vehicles.

Wilson, William C.↗
NASA NTRS2019

A Research Platform for Urban Air Mobility (UAM) and UAS Traffic Management (UTM) Concepts and Application

The purpose of this paper is to describe a research platform for the Urban Air Mobility (UAM) concept. UAM was conceived to enable short-range, low-altitiude service to commuters in metropolitan areas. At the NASA Ames Airspace Operations Laboratory (AOL) user interfaces have been developed to support small UAS operations for the UAS Traffic Management (UTM) project. Due to operational similarities between UAM and UTM, the UTM architecture offers a convenient starting point for research and development of UAM operations. Herein, we begin with an overview of the primary need and expectations characterizing concepts for modern air transportation systems, followed by a brief description of the UTM and UAM concepts. We then describe the UTM architecture, as well as the AOL's research platform and capabilities. The potential applications for UAM research and development are then discussed, providing some direction for future research efforts.

UAM↗
NASA NTRS2010

Ares I-X Flight Test Vehicle Modal Test

The first test flight of NASA's Ares I crew launch vehicle, called Ares I-X, was launched on October 28, 2009. Ares I-X used a 4-segment reusable solid rocket booster from the Space Shuttle heritage with mass simulators for the 5th segment, upper stage, crew module and launch abort system. Flight test data will provide important information on ascent loads, vehicle control, separation, and first stage reentry dynamics. As part of hardware verification, a series of modal tests were designed to verify the dynamic finite element model (FEM) used in loads assessments and flight control evaluations. Based on flight control system studies, the critical modes were the first three free-free bending mode pairs. Since a test of the free-free vehicle was not practical within project constraints, modal tests for several configurations during vehicle stacking were defined to calibrate the FEM. Test configurations included two partial stacks and the full Ares I-X flight test vehicle on the Mobile Launcher Platform. This report describes the test requirements, constraints, pre-test analysis, test execution and results for the Ares I-X flight test vehicle modal test on the Mobile Launcher Platform. Initial comparisons between pre-test predictions and test data are also presented.

Buehrle, Ralph D.↗
NASA NTRS2005

Common Cause Case Study: An Estimated Probability of Four Solid Rocket Booster Hold-down Post Stud Hang-ups

Until Solid Rocket Motor ignition, the Space Shuttle is mated to the Mobil Launch Platform in part via eight (8) Solid Rocket Booster (SRB) hold-down bolts. The bolts are fractured using redundant pyrotechnics, and are designed to drop through a hold-down post on the Mobile Launch Platform before the Space Shuttle begins movement. The Space Shuttle program has experienced numerous failures where a bolt has "hung-up." That is, it did not clear the hold-down post before liftoff and was caught by the SRBs. This places an additional structural load on the vehicle that was not included in the original certification requirements. The Space Shuttle is currently being certified to withstand the loads induced by up to three (3) of eight (8) SRB hold-down post studs experiencing a "hang-up." The results af loads analyses performed for four (4) stud-hang ups indicate that the internal vehicle loads exceed current structural certification limits at several locations. To determine the risk to the vehicle from four (4) stud hang-ups, the likelihood of the scenario occurring must first be evaluated. Prior to the analysis discussed in this paper, the likelihood of occurrence had been estimated assuming that the stud hang-ups were completely independent events. That is, it was assumed that no common causes or factors existed between the individual stud hang-up events. A review of the data associated with the hang-up events, showed that a common factor (timing skew) was present. This paper summarizes a revised likelihood evaluation performed for the four (4) stud hang-ups case considering that there are common factors associated with the stud hang-ups. The results show that explicitly (i.e. not using standard common cause methodologies such as beta factor or Multiple Greek Letter modeling) taking into account the common factor of timing skew results in an increase in the estimated likelihood of four (4) stud hang-ups of an order of magnitude over the independent failure case.

Cross, Robert↗
NASA NTRS2005

Common Cause Case Study: An Estimated Probability of Four Solid Rocket Booster Hold-Down Post Stud Hang-ups

Until Solid Rocket Motor ignition, the Space Shuttle is mated to the Mobil Launch Platform in part via eight (8) Solid Rocket Booster (SRB) hold-down bolts. The bolts are fractured using redundant pyrotechnics, and are designed to drop through a hold-down post on the Mobile Launch Platform before the Space Shuttle begins movement. The Space Shuttle program has experienced numerous failures where a bolt has hung up. That is, it did not clear the hold-down post before liftoff and was caught by the SRBs. This places an additional structural load on the vehicle that was not included in the original certification requirements. The Space Shuttle is currently being certified to withstand the loads induced by up to three (3) of eight (8) SRB hold-down experiencing a "hang-up". The results of loads analyses performed for (4) stud hang-ups indicate that the internal vehicle loads exceed current structural certification limits at several locations. To determine the risk to the vehicle from four (4) stud hang-ups, the likelihood of the scenario occurring must first be evaluated. Prior to the analysis discussed in this paper, the likelihood of occurrence had been estimated assuming that the stud hang-ups were completely independent events. That is, it was assumed that no common causes or factors existed between the individual stud hang-up events. A review of the data associated with the hang-up events, showed that a common factor (timing skew) was present. This paper summarizes a revised likelihood evaluation performed for the four (4) stud hang-ups case considering that there are common factors associated with the stud hang-ups. The results show that explicitly (i.e. not using standard common cause methodologies such as beta factor or Multiple Greek Letter modeling) taking into account the common factor of timing skew results in an increase in the estimated likelihood of four (4) stud hang-ups of an order of magnitude over the independent failure case.

Cross, Robert↗
NASA NTRS2009

Robots Save Soldiers' Lives Overseas (MarcBot)

Marshall Space Flight Center mobile communications platform designs for future lunar missions led to improvements to fleets of tactical robots now being deployed by U.S. Army. The Multi-function Agile Remote Control Robot (MARCbot) helps soldiers search out and identify improvised explosive devices. NASA used the MARCbots to test its mobile communications platform, and in working with it, made the robot faster while adding capabilities -- upgrading to a digital camera, encrypting the controllers and video transmission, as well as increasing the range and adding communications abilities. They also simplified the design, providing more plug-and-play sensors and replacing some of the complex electronics with more trouble-free, low-cost components. Applied Geo Technology, a tribally-owned corporation in Choctaw, Mississippi, was given the task of manufacturing the modified robots. The company is now producing 40 units per month, 300 of which have already been deployed overseas.

Source record↗
NASA NTRS2022

Turning Limitations into Opportunities in the Development of the Orion Medical System: Incorporation of mHealth Devices

INTRODUCTION: Selection of medical devices for the Orion medical system is a complex task which is dependent on the current state of terrestrial technology. In this work we review the interplay between NASA requirements, constraints, and opportunities for synergy during the development of the Orion medical system. METHODS: The “plan to treat” list of conditions, and subsequently the medical resource list for the Orion Artemis II lunar flyby mission was completed using semi-quantitative methods. During this process, some medical resources were excluded to comply with mass and volume limits, while other resources applicable to multiple medical requirements were prioritized for inclusion. Choices were also examined considering NASA level of care standards for the Artemis design reference missions. As a means to optimize capabilities in spite of mass and volume constraints, ideas for integration of multiple devices into a single platform were explored, including a ‘hackathon’ challenge which was conducted to generate and evaluate concepts for combining medical devices into a single app-based mobile device (ultrasound, ECG, etc.). RESULTS: The Orion team identified 128 medical conditions that we “plan to treat”, with 139 unique medical resources to address these conditions, including 5 digital diagnostic devices (ECG, otoscope, stethoscope, pulse oximeter, and blood pressure monitor). During selection of these digital devices the team noted that miniaturized medical devices often use mobile device platforms (mHealth), some displaying and transmitting data exclusively via mobile device. Of the 5 initially selected devices, all are capable of mobile connection, one which cannot function without a mobile device (ECG). Furthermore, only one of these devices connects natively to a Windows platform, which is currently the only operating system available on Orion. DISCUSSION: Significant savings in mass and volume as well as training and usability improvements can be achieved by leveraging mHealth technologies. However, the platform presents significant challenges for deployment within the Artemis Program including lack of internet connectivity, incompatible operating systems, and radiation concerns. Each of these drawbacks are surmountable with investment in the supporting vehicle architecture, which may become necessary to support the technology trends seen in commercially available medical devices today. Objective: Learn about the opportunities and challenges of leveraging mHealth devices in the development of medical capabilities for austere environments. Learn about the constraints of the NASA spaceflight environment with regards to digital medical device integration.

Douglas Ebert↗
NASA NTRSDate not supplied

Space Transformation -- Localizing the Remote and Connecting the Isolated

In motivating the Space Transformation theme for this year’s 4S symposium, the organizers provided the following context, “Transformation of economies are driven by a change in values and accelerated by new technologies.” These words rang particularly true when I read them at the beginning of the holiday season. Like so many others, I was in the early phases of my Christmas shopping procrastination campaign, and I’d just been reflecting on how Amazon Prime was the transformational tool I’d been waiting for. Basic limiting principles of time and space, supply and demand, were all but erased by the Amazon Prime phenomenon. Coupled with emerging 3D printing and other adaptive manufacturing technologies, a transformation from deliberate planning to “think it … have it” had occurred, empowering me to procrastinate longer than I’d ever dreamed possible. The organizers went on to ponder, “Will space transformation also affect society?”, just as our team at the Air Force Research Lab’s (AFRL) Center for Rapid Innovation (CRI) were working alongside partners within our larger Integrated Capabilities Directorate, NASA’s Flight Opportunities and Small Spacecraft Technology programs, and DARPA’s Luna-10 program to develop technologies and execute demonstration missions that leverage the space domain to genuinely connect even the most remote and austere domains on the timeline of need. Picking apart the miracle that is Amazon prime, where does the model fail, and why? More relevantly to the theme of this year’s symposium, how can the space domain be used to overcome its limitations and minimize its weaknesses? Perhaps it is best assessed in the context of Use Cases. What are the Amazon delivery cost, schedule, and cargo limiters to the Amundsen-Scott South Pole Research Station, or the Lunar South Pole Research Station? This paper will explore enabling infrastructure that allows Amazon prime to thrive and assess the transformational enabling technologies that would be necessary to extend that miracle to the truly remote or the truly austere. Localizing the Remote • First, it will evaluate the ability of the on-going AFRL Rocket Cargo and Space Initiatives Ringside Seats systems, coupled with Astrobotic’s Xodiak and Xogdor capabilities, developed to support the NASA Flight Opportunities Program (FOP), to supply orbital/suborbital delivery to both improved and austere sites on the Earth and Moon. • Then, it will add the surface terminal distribution leg, with an examination of Lunar Outpost’s Mobile Autonomous Prospecting Platform (MAPP), equipped with Mobile Autonomous Robotic Swarm (MARS) software, and Intuitive Machine’s Hopper, developed with support of AFRL and NASA’s Commercial Lunar Payload Services (CLPS) program. Connecting the Isolated From there, it will focus on the destination, asking what implied destination services are required to support highly assured autonomous delivery. • Specifically, it will highlight Astrobotic’s Skymage mesh-networked publish and subscribe communication and navigation service, as well as AFRL’s on-going developments of radioisotope and reactor nuclear-sourced thermoelectric power generation and distribution systems under development under the Joint Emergent Technology Supplying On-orbit Nuclear Power (JETSON) program by Lockheed Martin, Westinghouse, Intuitive Machines, and Zeno Power, to provide the power service to locations well off the grid. • Finally, the paper will connect to the “human machine”. What connects the remote or in-situ human consumer to the remote domain? What connects the diverse international government and commercial services to each other? The former will focus on AFRL’s OraCloud feeding their Space Defense Control and Characterization System (SDCCS) and Lunar Station’s MoonHacker systems, while the latter will focus on the BlueHalo/Tensor LunX Technology Platform for the Cislunar Commodity Marketplace. In 1984, Krafft Ehricke famously remarked that, “If God wanted man to become a spacefaring species, He would have given man a Moon.” This paper is not about the Moon, but is about humans as a spacefaring species, shedding the pesky land/air limitations of the Amazon Prime model … so that we can all live a procrastinator’s “think it … have it” existence.

Charles Finley↗
NASA NTRS2005

STS-114: Discovery Return to Flight Imagery Briefing

George Diller, from NASA Public Affairs, introduces Bob Page who is the chairman of the NASA Intercenter Photo Working Group. Page discusses the purpose of the group which is to perform an analysis of all imagery captured of spacecraft launches. He presents charts to discuss return to flight optics. The charts consist of: 1) Overall Shuttle Imagery Plan; 2) Baseline Configuration Imagery; 3) Upgraded Operational Television (OTV) Cameras; 4) Mobile Launch Platform Cameras; 5) Fixed Service Structure Cameras; 6) Kimeto Tracking Mount (KMT); 7) MOTS (Mobile Optical Tracking System); 8) Intermediate Focal Length Optical Tracker (IFLOT); 9) Distant Object Attitude Measurement System (DOAMS); 10) Advanced Transportable Optical Tracking System (ATOTS); 11) STS-114 Pad Fixed Tracker Camera Configuration; 12) STS-114 Camera Medium and Long Range Tracker Configuration; 13) WB-57 Ascent Visualization Experiment (WAVE); 14) WAVE Profile, Plan View, CAD Flight Training, and Test Flight; 15) Minimum STS-114 Flight Cameras Configuration; 16) External Tank (ET) Separation Cameras; 17) ET Imagery; Umbilical and Handheld; 18) On-Orbit Imagery; and 19) Imagery Data Distribution Plan. The presentation ends with a brief question and answer period.

Source record↗
NASA NTRS2012

Methods for Improving Long-Range Wireless Communication Between Extreme Terrain Vehicles

Axel is an extreme terrain, two-wheeled rover designed to traverse rocky surface and sub-surface landscapes in order to conduct remote science experiments in hard-to-reach locations. The rover's design meets many requirements for a mobile research platform capable of reaching water seeps on Martian cliff sides. Axel was developed by the Mobility and Robotic Systems section at the Caltech Jet Propulsion Laboratory. Unique design criteria associated with extreme terrain mobility led to a unique rover solution, consisting of a central module, which provides long-term energy storage and space for large-scale science payloads, and two detachable Axels that can detach and explore extreme terrain locations that are inaccessible to conventional rovers. The envisioned mission could involve a four-wheeled configuration of Axel called 'DuAxel' that is able to traverse the benign, flattened terrain of a landing site and approach the edge of the targeted crater or cave where it would deploy anchoring legs and detach one of the Axel rovers [1]. A tether provides a secure link between the Axel rover and the central module, acting as an anchor to allow Axel to descend along steep crater walls to collect data from the scientifically relevant sites along the water seeps or crater ledges. After completing its scientific mission Axel would hoist itself up to the central module and dock autonomously (using its on-board stereo cameras), allowing the once-again recombined DuAxel to travel to another location to repeat data collection.

wireless communication↗
NASA NTRSDate not supplied

Astrobee On-Orbit Commissioning Manuscript and Presentation

The Astrobee free flying robots operate autonomously inside the International Space Station (ISS) with oversight from a ground operator or ISS crew. They replace the Synchronized Position Hold Engage and Reorient Experimental Satellites (SPHERES) as research platforms for zero-g free-flying robotics. Astrobee can also serve as a mobile camera/sensor platform for flight and payload controllers to improve ISS operations. Development began in late 2014, and flight hardware deployed to the ISS on several launches starting from November 2018 to October 2019. Shortly after the first two robots arrived in April 2019, we began a series of commissioning activities to validate the Astrobee robots. This paper reviews the Astrobee system and describes the on-orbit commissioning activities and results.

ISS↗
NASA NTRSDate not supplied

Astrobee On-Orbit Commissioning

The Astrobee free flying robots operate autonomously inside the International Space Station (ISS) with oversight from a ground operator or ISS crew. They replace the Synchronized Position Hold Engage and Reorient Experimental Satellites (SPHERES) as research platforms for zero-g free-flying robotics. Astrobee can also serve as a mobile camera/sensor platform for flight and payload controllers to improve ISS operations. Development began in late 2014, and flight hardware deployed to the ISS on several launches starting from November 2018 to October 2019. Shortly after the first two robots arrived in April 2019, we began a series of commissioning activities to validate the Astrobee robots. This paper reviews the Astrobee system and describes the on-orbit commissioning activities and results.

ISS↗