Search NASA⌕ Search

SEARCH · Search NASA

Results for “consumer off the shelf”

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.

63 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS2013

Intravenous Fluid Generation System

The ability to stabilize and treat patients on exploration missions will depend on access to needed consumables. Intravenous (IV) fluids have been identified as required consumables. A review of the Space Medicine Exploration Medical Condition List (SMEMCL) lists over 400 medical conditions that could present and require treatment during ISS missions. The Intravenous Fluid Generation System (IVGEN) technology provides the scalable capability to generate IV fluids from indigenous water supplies. It meets USP (U.S. Pharmacopeia) standards. This capability was performed using potable water from the ISS; water from more extreme environments would need preconditioning. The key advantage is the ability to filter mass and volume, providing the equivalent amount of IV fluid: this is critical for remote operations or resource- poor environments. The IVGEN technology purifies drinking water, mixes it with salt, and transfers it to a suitable bag to deliver a sterile normal saline solution. Operational constraints such as mass limitations and lack of refrigeration may limit the type and volume of such fluids that can be carried onboard the spacecraft. In addition, most medical fluids have a shelf life that is shorter than some mission durations. Consequently, the objective of the IVGEN experiment was to develop, design, and validate the necessary methodology to purify spacecraft potable water into a normal saline solution, thus reducing the amount of IV fluids that are included in the launch manifest. As currently conceived, an IVGEN system for a space exploration mission would consist of an accumulator, a purifier, a mixing assembly, a salt bag, and a sterile bag. The accumulator is used to transfer a measured amount of drinking water from the spacecraft to the purifier. The purifier uses filters to separate any air bubbles that may have gotten trapped during the drinking water transfer from flowing through a high-quality deionizing cartridge that removes the impurities in the water before entering the salt bag and mixing with the salt to create a normal saline solution.

McQuillen, John↗
NASA NTRS2017

Lunar Advanced Volatile Analysis Subsystem: Pressure Transducer Trade Study

In Situ Resource Utilization (ISRU) is a key factor in paving the way for the future of human space exploration. The ability to harvest resources on foreign astronomical objects to produce consumables and propellant offers potential reduction in mission cost and risk. Through previous missions, the existence of water ice at the poles of the moon has been identified, however the feasibility of water extraction for resources remains unanswered. The Resource Prospector (RP) mission is currently in development to provide ground truth, and will enable us to characterize the distribution of water at one of the lunar poles. Regolith & Environment Science and Oxygen & Lunar Volatile Extraction (RESOLVE) is the primary payload on RP that will be used in conjunction with a rover. RESOLVE contains multiple instruments for systematically identifying the presence of water. The main process involves the use of two systems within RESOLVE: the Oxygen Volatile Extraction Node (OVEN) and Lunar Advanced Volatile Analysis (LAVA). Within the LAVA subsystem, there are multiple calculations that depend on accurate pressure readings. One of the most important instances where pressure transducers (PT) are used is for calculating the number of moles in a gas transfer from the OVEN subsystem. As a critical component of the main process, a mixture of custom and commercial off the shelf (COTS) PTs are currently being tested in the expected operating environment to eventually down select an option for integrated testing in the LAVA engineering test unit (ETU).

Kang, Edward Shinuk↗
NASA NTRS2022

Recommendations for Developing Space Suit Integrated Food Systems and Delivering Nutrition Before, During, and After Lunar EVA

The concept of providing hydration and nutrition during extravehicular activity (EVA) is nearly as old as the space program itself. Astronauts currently have access to 32 ounces of water through a disposable in-suit drink bag (DIDB) while they are confined to their space suit. During the Apollo program, methods for providing food/nutrition to crewmembers in space suits were included as contingency solutions (1) but were eventually abandoned. The main reasons that provision of in-suit nutrition beyond water was discontinued after Apollo were the complicated engineering requirements, the additional mass and volume that was required for the applicable food formulations, hardware needed for a suit-specialized food system, and because the perceived need for in-suit nutrition during EVAs was not sufficient during the Space Shuttle and the International Space Station (ISS) eras. A custom-made 165-kcal fruit bar was fitted into the EVA suit during the Space Shuttle program, but crewmembers rarely consumed it during the EVA and rather chose to consume it before or after suited activities (2). Since 2011, between 4 and 13 EVAs have been conducted from the ISS each year, with durations ranging from 1:32 to 8:17 hours (https://www.nasa.gov/mission_pages/station/spacewalks ). It has been acceptable for the crewmembers to schedule food intake around these relatively infrequent suited activities. Because upcoming Artemis missions will include nominal 8-hour lunar exploration EVAs that are expected to increase in frequency to several (4 to 5) sorties per week (3), the desire for an in-suit nutrition system has increased. In preparation for these missions, requirements to provide in-suit nutrition has been outlined in the most recent NASA Human Spaceflight Standards documents (4). Establishing general recommendations for in-suit nutrition systems precedes the selection of a lunar EVA pressure suit system. The current document is intended to define the rationale for nutrition to support EVA (whether in-suit or from the pantry in the habitat), document the requirements, constraints, and crewmember preferences, and recommend necessary next steps for developing an in-suit EVA nutrition system. Assessments presented in this report include a review of commercial off-the-shelf (COTS) food products as potential in-suit formulations, a comparison of conceptual designs for delivering nutrition to a crewmember while confined to a space suit, an evaluation of space suit volume constraints for the placement of in-suit nutrition systems, and feedback from astronauts regarding preferences for nutrition support during EVA. Based on these assessments, recommendations were formulated that can be used to help develop a method to deliver nutrition safely and acceptably to a crewmember while they are confined to a space suit for an EVA duration of up to 8 hours, and a total time in the suit of up to 12 hours.

space suit↗
NASA NTRS2016

Space Suit Portable Life Support System (PLSS) 2.0 Unmanned Vacuum Environment Testing

For the first time in more than 30 years, an advanced space suit Portable Life Support System (PLSS) design was operated inside a vacuum chamber representative of the flight operating environment. The test article, PLSS 2.0, was the second system-level integrated prototype of the advanced PLSS design, following the PLSS 1.0 Breadboard that was developed and tested throughout 2011. Whereas PLSS 1.0 included five technology development components with the balance the system simulated using commercial-off-the-shelf items, PLSS 2.0 featured first generation or later prototypes for all components less instrumentation, tubing and fittings. Developed throughout 2012, PLSS 2.0 was the first attempt to package the system into a flight-like representative volume. PLSS 2.0 testing included an extensive functional evaluation known as Pre-Installation Acceptance (PIA) testing, Human-in-the-Loop testing in which the PLSS 2.0 prototype was integrated via umbilicals to a manned prototype space suit for 19 two-hour simulated EVAs, and unmanned vacuum environment testing. Unmanned vacuum environment testing took place from 1/9/15-7/9/15 with PLSS 2.0 located inside a vacuum chamber. Test sequences included performance mapping of several components, carbon dioxide removal evaluations at simulated intravehicular activity (IVA) conditions, a regulator pressure schedule assessment, and culminated with 25 simulated extravehicular activities (EVAs). During the unmanned vacuum environment test series, PLSS 2.0 accumulated 378 hours of integrated testing including 291 hours of operation in a vacuum environment and 199 hours of simulated EVA time. The PLSS prototype performed nominally throughout the test series, with two notable exceptions including a pump failure and a Spacesuit Water Membrane Evaporator (SWME) leak, for which post-test failure investigations were performed. In addition to generating an extensive database of PLSS 2.0 performance data, achievements included requirements and operational concepts verification, as well as demonstration of vehicular interfaces, consumables sizing and recharge, and water quality control.

Watts, Carly↗
NASA NTRSDate not supplied

Genesis Solar Wind Sample Curation Documentation

Introduction: A scientist with experience as a sample science analyst, provider of flight hardware for multiple missions, and senior engineer in an ISO 2000-rated manufacturing plant has described the timeline of key participants in any PI-led sample return mission, the breadth of the organizations involved [1,2], and, of interest to this meeting, choosing the types of data to preserve and issues of future data accessibility. This work broadens that perspective by giving similar lessons from Genesis sample curation point-of-view. Curation participation regarding data gathering was part of the mission review process from the beginning. Genesis’ story illustrates outcome of several choices about types of data to record and preserve. Precision analysis of solar wind atoms captured in pure, ultraclean substrates is the driving science goal; therefore, detailed documentation was captured from all mission and curation phases and from investigator laboratories because these processes affect the final analytical results [3]. Pre-flight: Design and fabrication of the spacecraft. Like many modern small sample return missions, Genesis was a tightly managed team integrated across science, engineering and curation. Communication across the team was excellent, and, for the most part, the hands-on engineering technicians understood the impacts of “small choices” they routinely make, and the eyes-on oversight of manufacturing processes by scientists was mindful of details. The payload was designed by the Jet Propulsion Laboratory and the spacecraft by Lockheed Martin. Solar wind collectors and instruments were fabricated by multiple vendors and laboratories. The main portion of the payload was assembled at JSC. Fabrication procedures and contamination-control data (with witness coupons) were stored primarily at JSC. The original composition, dimensions and configuration of components, results of thermal testing, etc. are still needed for interpretation of analytical data. At times, these must be estimated from secondary information acquired pre-flight. Moreover, some files (e.g., original 3-D models and early Powerpoint) cannot be opened using software. Archived curation data includes 2-D drawings, material usage lists, QA documentation and analyses of consumables used during fabrication. Important chemical information still resides in archived hardware, paints and lubricants, material coupons, cleaning coupons, environmental witness plates and reference materials from manufacturing facilities. Purity and cleanliness of collector substrates. Semi-conductor vendors provided surface cleanliness data and some purity data. Purity for specific elements of interest was verified by science team members in their laboratories [4]. Curation archived procurement and shipping records, analysis reports, and non-proprietary fabrication data. A physical archive of flight collector reference materials is maintained for future use so additional data can be collected as analytical techniques improve. These are of increased value due to the hard landing upon re-entry. Cleaning and cleanliness assessments of flight hardware. Cleaning of the science canister payload was performed at JSC in a dedicated ISO 4 cleanroom using ultrapure water (UPW). The cleanliness of this UPW was monitored throughout processing. The archive for the clean lab also includes airborne particle counts, airborne molecular and inorganic contamination measurements as well as cleanroom construction material coupons and witness coupons. Hardware cleanliness was assessed by particle counts in rinse water batches. This information is recorded in batch cleaning forms and logbooks, and are, perhaps, of decreased value due to the hard landing. Post-flight: Curation-generated data. The curation handling history of each Genesis sample is documented in a typical astromaterials sample database which captures sample location, physical description and characterization data. Samples have a “shelf life”. Crucial to the preservation of samples is ongoing documentation of the sample environment, initially under curatorial control but is now a separate facility function with requires coordination. PI-generated data. Data on sample characterization and cleaning techniques continues to be generated by sample users [5]. These are often captured in LPSC abstracts, but these “engineering” results often are not publishable as stand-alone papers. We are actively looking for ways to make this information more accessible to users. Ion implants into samples have aided science return and can be shared among investigators. These (and similar) materials should be added to the curatorial collection with appropriate process and characterization data generated externally. Summary: Complete data archives for returned astromaterial samples must be broad in types and formats, and inclusive of environmental monitoring.

Genesis↗
NASA NTRS2001

Deep Space 1 Ion Engine Completed a 3-Year Journey

A xenon ion engine and power processor system, which was developed by the NASA Glenn Research Center in partnership with the Jet Propulsion Laboratory and Boeing Electron Dynamic Devices, completed nearly 3 years of operation aboard the Deep Space 1 spacecraft. The 2.3-kW ion engine, which provided primary propulsion and two-axis attitude control, thrusted for more than 16,000 hr and consumed more than 70 kg of xenon propellant. The Deep Space 1 spacecraft was launched on October 24, 1998, to validate 12 futuristic technologies, including the ion-propulsion system. After the technology validation process was successfully completed, the Deep Space 1 spacecraft flew by the small asteroid Braille on July 29, 1999. The final objective of this mission was to encounter the active comet Borrelly, which is about 6 miles long. The ion engine was on a thrusting schedule to navigate the Deep Space 1 spacecraft to within 1400 miles of the comet. Since the hydrazine used for spacecraft attitude control was in short supply, the ion engine also provided two-axis attitude control to conserve the hydrazine supply for the Borrelly encounter. The comet encounter took place on September 22, 2001. Dr. Marc Rayman, project manager of Deep Space 1 at the Jet Propulsion Laboratory said, "Deep Space 1 plunged into the heart of the comet Borrelly and has lived to tell every detail of its spinetingling adventure! The images are even better than the impressive images of comet Halley taken by Europe's Giotto spacecraft in 1986." The Deep Space 1 mission, which successfully tested the 12 high-risk, advanced technologies and captured the best images ever taken of a comet, was voluntarily terminated on December 18, 2001. The successful demonstration of the 2-kW-class ion propulsion system technology is now providing mission planners with off-the-shelf flight hardware. Higher power, next generation ion propulsion systems are being developed for large flagship missions, such as outer planet explorers and sample-return missions.

Sovey, James S.↗
NASA NTRS2016

Computational Modeling to Limit the Impact Displays and Indicator Lights Have on Habitable Volume Operational Lighting Constraints

The goal of this investigation is to determine design limitations and architectural solutions that limit the impact light from displays and indicator lamps have on the operational environment task lighting and lighting countermeasure spectrum constraints. It is concerning that this innovative architectural lighting system, could be compromised by spectrums from display systems, architectural materials, and structures that are not considered as part a full system design implementation. The introduction of many Commercial Off the Shelf (COTS) products to the spacecraft volume that contain LEDs, without consideration to the human factors and biological constraints, is another problem. Displays and indicators are a necessary part of the spacecraft and it is the goal of this research project to determine constraints and solutions that allow these systems to be integrated while minimizing how the lighting environment is modified by them. Due to the potentially broad scope of this endeavor, the project team developed constraints for the evaluation. The evaluation will be on a set of tasks that required significant exposure in the same environment while having a large chance of impacting the light spectrum the crew is expected to receive from the architectural lighting system. The team plans to use recent HRP research on "Net Habitable Volume" [1] to provide the boundary conditions for volume size. A Zemax ® lighting model was developed of a small enclosure that had high intensity overhead lighting and a standard intensity display with LED indicator arrays. The computer model demonstrated a work surface illuminated at a high level by the overhead light source compared to displays and indicators whose light is parallel to the work plane. The overhead lighting oversaturated spectral contributions from the display and indicator at the task work surface. Interestingly, when the observer looked at the displays and LEDs within the small enclosure, their spectral contribution was significant but could be reduced by reflecting overhead light from the wall(s) to the observer. Direct observation of displays and LEDs are an issue because the user's viewing area is a display, not an illuminated work surface. Since avionics command centers consume significant crew time, the tasks that seemed at higher risk for unwanted spectral contributions as an operational volume with significant quantity of displays and indicators that were either under direct observation of the crew or impacting a volume the crew may be required to sleep in.

Clark, T. E.↗
NASA NTRS2011

Standards and Specifications for Ground Processing of Space Vehicles: From an Aviation-Based Shuttle Project to Global Application

Proprietary or unique designs and operations are expected early in any industry's development, and often provide a competitive early market advantage. However, there comes a time when a product or industry requires standardization for the whole industry to advance...or survive. For the space industry, that time has come. Here, we will focus on standardization of ground processing for space vehicles and their ground systems. With the retirement of the Space Shuttle, and emergence of a new global space race, affordability and sustainability are more important now than ever. The growing commercialization of the space industry and current global economic environment are driving greater need for efficiencies to save time and money. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability not achievable with traditional ELV's (Expendable Launch Vehicles). More crew/passenger vehicles are also being developed. All of this calls for more attention needed for ground processing-repeatedly before launch and after landing/recovery. RLV's should provide more efficiencies than ELV's, as long as MRO (Maintenance, Repair, and Overhaul) is well-planned-even for the unplanned problems. NASA's Space Shuttle is a primary example of an RLV which was supposed to thrive on reusability savings with efficient ground operations, but lessons learned show that costs were (and still are) much greater than expected. International standards and specifications can provide the commonality needed to simplify design and manufacturing as well as to improve safety, quality, maintenance, and operability. There are standards organizations engaged in the space industry, but ground processing is one of the areas least addressed. Challenges are encountered due to various factors often not considered during development. Multiple vehicle elements, sites, customers, and contractors pose various functional and integration difficulties. Resulting technical publication structures and methods are incongruent. Some processing products are still done on paper, some electronic, and many being converted in between. Business systems then are not fully compatible, and paper as well as electronic conversions are time-consuming and costly. NASA and its Shuttle contractors setup rules and systems to handle what has produced over 130 RLV launches, but they have had many challenges. Attempts have been made to apply aviation industry specifications to make the Shuttle more efficient with its ground processing. One efficiency project example was to make a Shuttle Maintenance Manual (SMM) based on the commercial ATA (Air Transport Association of America) Spec 100 for technical publications. This industry standard, along with others, has been a foundation for efficient global MRO of commercial airlines for years. A modified version was also made for some military aircraft. The SMM project found many similarities in Spec 100 which apply to the Shuttle, and room for expansion for space systems/structures not in aircraft. The SMM project team met with the ATA and representatives from NASA's X-33 and X-34 programs to discuss collaboration on a national space standard based on Spec 100. A pilot project was enabled for a subset of Shuttle systems. Full implementation was not yet achieved, X-33 and X-34 were cancelled, and the Shuttles were then designated for retirement. Nonetheless, we can learn from this project how to expand this concept to all space vehicle products. Since then, ATA has joined with ASD (AeroSpace and Defence Industries Association of Europe) and AIA (Aerospace Industries Association) to form a much-enhanced and expanded international specification: Sl000D, International Specification for Technical Publications. It includes air, land, and sea vehicles, missiles, support equipment, ordnance, and communications. It is used by a growing number of countries for commercial and government products. Its modular design is supported by a Common Source Dabase (CSDB), and COTS (commercial off-the-shelf) software is available for production of IETP's (Interactive Electronic Technical Publications). A few space industry products in Europe have begun to apply Sl000D already. Also, there are other related standards/specifications which have global implications. We have an opportunity to adapt Sl000D and possibly other standards for use with space vehicles and ground systems. Sl000D has plenty of flexibility to apply to any product needed. To successfully grow the viability of the space industry, all members, commercial and government, will need to engage cooperatively in developing and applying standards to move toward interoperability. If we leverage and combine the best existing space standards and specifications, develop new ones to address known gaps, and adapt the best applicable features from other industries, we can establish an infrastructure to not only accelerate current development, but also build longevity for a more cohesive international space community.

Ingalls, John↗
NASA NTRS2019

A Delay Tolerant Networking-Based Approach to a High Data Rate Architecture for Spacecraft

Historically, it has been the case that SWaP (Size, Weigh a lot, And consume Power) placed such severe constraints on radios that the links between spacecraft and the ground were relatively slow. This meant that the radio link was normally a significant bottleneck in returning scientific data. Over recent years, however, a combination of more efficient radio design, intelligent waveforms, and highly directed, high-frequency RF / optical systems have led to a rapid increase in the amount of data that can be pushed through radio and optical links. This has led to some cases where the radio links are capable of moving data much more quickly than the spacecraft and instruments are capable of actually generating it! In some instances, scientific data can therefore be lost not because the downlink is too slow to support the data rate, but instead because the spacecraft was not designed in a way that would let it fully utilize both the radio and the networking services available to it. The High Data Rate Architecture (HiDRA) project describes a packet-based approach to building modern, distributed spacecraft systems. It presents a means for spacecraft and other assets to participate in both present and future Delay Tolerant Networks (DTN), while simultaneously ensuring that the asset is able to fully utilize the new, high-speed links that have been seeing more widespread development and deployment in recent years. With this in mind, this paper begins with a discussion regarding HiDRA's evolution. Next, it discusses the capabilities and limitations of NASA's present DTN-enabled networks. Of particular note is the way in which principles of network designate the terrestrial level (e.g., use of programmable networks / software-defined networks, separation between data and control plane, infusion of COTS (Commercial Off-The-Shelf) Ethernet switch chips, etc.) can all be translated into the space environment as well. After this, the paper discusses the design and implementation of a present prototype reference implementation of High-Rate DTN (HDTN),which is intended to demonstrate future high-rate networking concepts as part of a coherent demonstration on the International Space Station (ISS). The goal, of both the research and of this implementation, is to help develop a ready-made toolbox of ideas, approaches, and examples from which mission designers can draw when putting together new missions. Assuming all goes as planned, this should not only work to reduce the cost of individual mission design, but also improve the rate at which science data can be returned for mission participants to review.

Hylton, Alan↗