SEARCH · Engineering Papers
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.
This presentation covers top-level total ionizing dose (TID) testing and evaluation of commercial CubeSat hardware modules from Arduino and RaspberryPi.
Controlling carbon dioxide in spacecraft cabin air may be accomplished using algal photobioreactors (PBRs). The purpose of this project was to evaluate the use of a commercial microcontroller, the Arduino Mega 2560, for measuring key phot~ioreactor variables: dissolved oxygen, pH, temperature, light, and carbon dioxide. The Arduino platform is an opensource physical computing platform composed of a compact microcontroller board and a C++/C computer language (Arduino 1.0.5). The functionality of the Arduino platform can be expanded by the use of numerous add-ons or 'shields'. The Arduino Mega 2560 was equipped with the following shields: datalogger, BNC shield for reading pH sensor, a Mega Moto shield for controlling CO2 addition, as well as multiple sensors. The dissolved oxygen (DO) probe was calibrated using a nitrogen bubbling technique and the pH probe was calibrated via an Omega pH simulator. The PBR was constructed using a 2 L beaker, a 66 L box for addition of CO2, a micro porous membrane, a diaphragm pump, four 25 watt light bulbs, a MasterFiex speed controller, and a fan. The algae (wild type Synechocystis PCC6803) was grown in an aerated flask until the algae was dense enough to used in the main reactor. After the algae was grown, it was transferred to the 2 L beaker where CO2 consumption and O2 production was measured using the microcontroller sensor suite. The data was recorded via the datalogger and transferred to a computer for analysis.
Wearable technology projects, to be useful, in the future, must be seamlessly integrated with the Flight Deck of the Future (F.F). The lab contains mockups of space vehicle cockpits, habitat living quarters, and workstations equipped with novel user interfaces. The Flight Deck of the Future is one element of the Integrated Power, Avionics, and Software (IPAS) facility, which, to a large extent, manages the F.F network and data systems. To date, integration with the Flight Deck of the Future has been limited by a lack of tools and understanding of the Flight Deck of the Future data handling systems. To remedy this problem it will be necessary to learn how data is managed in the Flight Deck of the Future and to develop tools or interfaces that enable easy integration of WEAR Lab and EV3 products into the Flight Deck of the Future mockups. This capability is critical to future prototype integration, evaluation, and demonstration. This will provide the ability for WEAR Lab products, EV3 human interface prototypes, and technologies from other JSC organizations to be evaluated and tested while in the Flight Deck of the Future. All WEAR Lab products must be integrated with the interface that will connect them to the Flight Deck of the Future. The WEAR Lab products will primarily be programmed in Arduino. Arduino will be used for the development of wearable controls and a tactile communication garment. Arduino will also be used in creating wearable methane detection and warning system.
The National Aeronautics and Space Administration (NASA) at the Johnson Space Center (JSC) is developing a new extra-vehicular activity (EVA) suit known as the Advanced EVA Z2 Suit. All of the improvements to the EVA Suit provide the opportunity to update the technology of the video imagery. My summer internship project involved improving the video streaming capabilities of the cameras that will be used on the Z2 Suit for data acquisition. To accomplish this, I familiarized myself with the architecture of the camera that is currently being tested to be able to make improvements on the design. Because there is a lot of benefit to saving space, power, and weight on the EVA suit, my job was to use Altium Design to start designing a much smaller and simplified interface board for the camera's microprocessor and external components. This involved checking datasheets of various components and checking signal connections to ensure that this architecture could be used for both the Z2 suit and potentially other future projects. The Orion spacecraft is a specific project that may benefit from this condensed camera interface design. The camera's physical placement on the suit also needed to be determined and tested so that image resolution can be maximized. Many of the options of the camera placement may be tested along with other future suit testing. There are multiple teams that work on different parts of the suit, so the camera's placement could directly affect their research or design. For this reason, a big part of my project was initiating contact with other branches and setting up multiple meetings to learn more about the pros and cons of the potential camera placements we are analyzing. Collaboration with the multiple teams working on the Advanced EVA Z2 Suit is absolutely necessary and these comparisons will be used as further progress is made for the overall suit design. This prototype will not be finished in time for the scheduled Z2 Suit testing, so my time was also spent creating a case for the original interface board that is already being used. This design is being done by use of Creo 2. Due to time constraints, I may not be able to complete the 3-D printing portion of this design, but I was able to use my knowledge of the interface board and Altium Design to help in the task. As a side project, I assisted another intern in selecting and programming a microprocessor to control linear actuators. These linear actuators will be used to move various increments of polyethylene for controlled radiation testing. For this, we began the software portion of the project using the Arduino's coding environment to control an Arduino Due and H-Bridge components. Along with the obvious learning of computer programs such as Altium Design and Creo 2, I also acquired more skills with networking and collaborating with others, being able to multi-task because of responsibilities to work on various projects, and how to set realistic goals in the work place. Like many internship projects, this project will be continued and improved, so I also had the chance to improve my organization and communication skills as I documented all of my meetings and research. As a result of my internship at JSC, I desire to continue a career with NASA, whether that be through another internship or possibly a co-op. I am excited to return to my university and continue my education in electrical engineering because of all of my experiences at JSC.
As an intern project for NASA Johnson Space Center (JSC), my job was to familiarize myself and operate a Robotics Operating System (ROS). The project outcome will convert existing software assets into ROS using nodes, enabling a robotic Hexapod to communicate and to be functional and controlled by an existing PlayStation 3 (PS3) controller. Existing control algorithms and current libraries have no ROS capabilities within the Hexapod C++ source code. Conversion of C++ codes to ROS will enable existing code to be compatible with ROS, and will be controlled using existing PS3 controller. Furthermore, my job description is to design ROS messages and script programs which will enable assets to participate in the ROS ecosystem. In addition, an open source software (IDE) Arduino board will be integrated in the ecosystem with designing circuitry on a breadboard to add additional behavior with push buttons, potentiometers and other simple elements in the electrical circuitry. Other projects with the Arduino will be a GPS module digital clock that will run off 22 satellites to show accurate real time using a GPS signal and internal patch antenna to communicate with satellites.
This summer I was given the opportunity to work at the Habitability Design Center (HDC). NASA Johnson Space Center's HDC is currently developing Cislunar and Mars spacecraft mockups. I contributed to this effort by designing from scratch low cost, functional translational hand controllers (THCs) that will be used in spacecraft mission simulation in low to medium fidelity exploration spacecraft mockups. This project fell under the category of mechatronics, a combination of mechanical, electrical, and computer engineering. Being an aerospace engineering student, I was out of my comfort zone. And that was a wonderful thing. The autonomy that my mentor, Dr. Robert Howard, allowed me gave me the opportunity to learn by trying, failing, and trying again. This project was not only a professional success for me, but a significant learning experience. I appreciated the freedom that I had to take the time to learn new things for myself rather than blindly follow instructions. I was the sole person working on this project, and was required to work independently to solve the many hardware and software challenges that the project entailed. I researched THCs that have been used on the ISS, the Space Shuttle, and the Orion MPVC and based my design off of these. I worked through many redesigns before finding an optimal configuration of the necessary mechanisms and electrical components for the THC. Once I had a functional hardware design, I dove into the challenge of getting an Arduino Uno, an extremely low cost and easily programmable microcontroller, to behave as a human interface device. The THCs I built needed to be able to integrate to a mission simulation designed by NASA's Graphics and Visualization Lab. This proved to be the most challenging aspect of the project. To accomplish this I learned how to change the firmware of the USB serial converter microcontroller. The process was very complicated as it involved multiple software programs and manual flashing of pins on the Arduino itself. When I successfully achieved the goal I wrote an instructions manual for the process so that the HDC will be able to do this easily in the future for any human interface device they may want to create. I also created a detailed CAD model of my THC design with construction instructions. My THC utilizes three ultrasonic sensors, one for each axis of motion. I wrote a code that stimulates these sensors continuously and feeds back values from each axis ranging from -%100 to %100 of the min/max position in relation to the neutral position of each axis. This was the data that the Graphics and Visualization Lab required to interface with their simulation. I truly enjoyed working in the HDC surrounded by passionate, proactive, and brilliantly creative people. I felt valued and respected as a part of their team. I was given the time and support of my mentor whenever I asked for it. Beyond my positive project experience, I was fortunate enough to be able to take advantage of many of the extra activities that JSC has to offer. I took Russian Phase One during my lunch break every day and can now read Russian and accomplish basic verbal communication. I was heavily involved with the co-tern music video, which led to numerous incredible experiences and friendships. I saw every facility, attended every lecture, and met everyone that I could. I had coffee with Lauri Hansen. I played on an intern volleyball team at the Gilruth. I traveled to Michoud, Stennis, NOLA, and Big Bend National Park. I had the time of my life and I fell in love with JSC. In the next month I will return to Maryland and start my senior year of my undergraduate degree. As I work through it I will remember that all of the studying I do, all of the concentration I give, and all of the sacrifices that I make for school are so that I can work at a place like JSC where I am proud and excited to go into work every day. This internship was an invaluable experience for me, both professionally and personally.
As an intern project for NASA Johnson Space Center (JSC), my job was to familiarize myself and operate a Robotics Operating System (ROS). The project outcome converted existing software assets into ROS using nodes, enabling a robotic Hexapod to communicate to be functional and controlled by an existing PlayStation 3 (PS3) controller. Existing control algorithms and current libraries have no ROS capabilities within the Hexapod C++ source code when the internship started, but that has changed throughout my internship. Conversion of C++ codes to ROS enabled existing code to be compatible with ROS, and is now controlled using an existing PS3 controller. Furthermore, my job description was to design ROS messages and script programs that enabled assets to participate in the ROS ecosystem by subscribing and publishing messages. Software programming source code is written in directories using C++. Testing of software assets included compiling code within the Linux environment using a terminal. The terminal ran the code from a directory. Several problems occurred while compiling code and the code would not compile. So modifying code to where C++ can read the source code were made. Once the code was compiled and ran, the code was uploaded to Hexapod and then controlled by a PS3 controller. The project outcome has the Hexapod fully functional and compatible with ROS and operates using the PlayStation 3 controller. In addition, an open source software (IDE) Arduino board will be integrated into the ecosystem with designing circuitry on a breadboard to add additional behavior with push buttons, potentiometers and other simple elements in the electrical circuitry. Other projects with the Arduino will be a GPS module, digital clock that will run off 22 satellites to show accurate real time using a GPS signal and an internal patch antenna to communicate with satellites. In addition, this internship experience has led me to pursue myself to learn coding more efficiently and effectively to write, subscribe and publish my own source code in different programming languages. With some familiarity with software programming, it will enhance my skills in the electrical engineering field. In contrast, my experience here at JSC with the Simulation and Graphics Branch (ER7) has led me to take my coding skill to be more proficient to increase my knowledge in software programming, and also enhancing my skills in ROS. This knowledge will be taken back to my university to implement coding in a school project that will use source coding and ROS to work on the PR2 robot which is controlled by ROS software. My skills learned here will be used to integrate messages to subscribe and publish ROS messages to a PR2 robot. The PR2 robot will be controlled by an existing PS3 controller by changing C++ coding to subscribe and publish messages to ROS. Overall the skills that were obtained here will not be lost, but increased.
Experimental evolution (EE) exposes microbial communities to ecological stressors, simulating dynamics up to near-extinction events. Combined with comparative sequencing and other molecular tools, such data can inform the genetic and other biological mechanisms underlying extremophile adaptation, and other observed effects. Automating this type of experiment using biofluidics can mitigate many traditional obstacles, including delays in assay results and environment adjustment and the need for many replicates. A first-generation device for automating EE procedures, the Automated Adaptive Directed Evolution Chamber (AADEC), was developed at NASA Ames. UV-C radiation was the stressor, an LED-photodiode array measured optical density, magnetic agitation and peristaltic pump systems ensured nutrient availability, and Arduino microcontrollers provided control. Escherichia coli in LB kanamycin media was used for testing and performance verification. A manual laboratory procedure with timed exposure to UV-C was performed to typify tolerance acquisition. Approximately a 106 factor increase in survival ratio was recorded over multiple iterations. Currently, a second-generation device is being developed integrating more real-time sensors: redox potential (ORP), indicating available/consumed metabolic energy; dissolved oxygen (DO), indicating aerobic/anaerobic growth; pH, indicating metabolic products; and electrical conductivity (EC), another indicator of metabolic products. The EC sensor system was constructed and calibrated in-house and matched commercial sensors in the required range. A Raspberry Pi computer automated the electrical system, allowing real-time data acquisition. The fluidics card was made of CNC-milled polycarbonate for biocompatibility. Each sensor parameter can also be used as a selection pressure alone or in combination with others to create extreme microbial environments. As a proof of concept, this work demonstrated sensor operation in one pair of growth-sensor chambers. It can be expanded to a multi-chamber system to enable inter-culture comparisons and multi-population studies. The prior Arduino system will be ported to the RPi system. Future stressors to be added include thermal, reactive oxygen species, and varying nutrient availability.
In 2015 NASA plans to launch a payload to 280 Km altitude on a sounding rocket from the Wallops Flight Facility. This payload will contain several novel technologies that work together to demonstrate methodologies for space sample return missions and for nanosatellite communications in general. The payload will deploy and test an Exo-Brake, which slows the payload aerodynamically, providing eventual de-orbit and recovery of future ISS samples through a Small Payload Quick Return project. In addition, this flight addresses future Mars mission entry technology, space-to-space communications using the Iridium Short Messaging Service (SMS), GPS tracking, and wireless sensors using the ZigBee protocol. SOAREX-8 is being assembled and tested at Ames Research Center (ARC) and the NASA Engineering and Safety Center (NESC) is funding sensor and communications work. Open source Arduino technology and software are used for system control. The ZigBee modules used are XBee units that connect analog sensors for temperature, air pressure and acceleration measurement wirelessly to the payload telemetry system. Our team is developing methods for power distribution and module mounting, along with software for sensor integration, data assembly and downlink. We have demonstrated relaying telemetry to the ground using the Iridium satellite constellation on a previous flight, but the upcoming flight will be the first time we integrate useful flight test data from a ZigBee wireless sensor network. Wireless sensor data will measure the aerodynamic efficacy of the Exo-Brake permitting further on orbit flight tests of improved designs. The Exo-Brake is 5 sq m in area and will be stored in a container and deployed during ascent once the payload is jettisoned from the launch vehicle. We intend to further refine the hardware and continue testing on balloon launches, future sounding rocket flights and on nanosatellite missions. The use of standards-based and open source hardware/software has allowed for this project to be completed with a very modest budget and a challenging schedule. There is a wealth of hardware and software available for both the Arduino platform and the XBee, all low-cost or open-source. Along with the Exo-Brake hardware and deployment discussion, this paper will describe in detail the system architecture emphasizing the successful use of open source hardware and software to minimize effort and cost. Testing procedures, radio frequency interference (RFI) mitigation, success criteria and expected results will also be discussed. The use of Iridium short messaging capability for space-to-space links, standards-based wireless sensor networks, and other innovative communications technology are also presented.
Major changes in salinity (approx.14 ppt.) and temperature (approx.40C) were continuously registered by two prototype NASA DRIFTERs, surface moored floaters, that NASA's Applied Science and Technology Project Office (ASTPO) has developed. The DRIFTER floating sensor module is equipped with an Arduino open-source electronics prototyping platform and programming language (http://www.arduino.cc), a GPS (Global Positioning System) module with antenna, a cell phone SIM (Subscriber Identity Module) card and a cellular antenna which is used to transmit data, and a probe to measure temperature and conductivity (from which salinity can be derived). The DRIFTER is powered by a solar cell panel and all the electronic components are mounted and sealed in [ waterproof encasement. Position and measurement data are transmitted via short message service (SMS) messaging to a Twitter site (DRIFTER 002@NASADRIFTER_002 and DRIFTER 004@NASADRIFTER_004), which provides a live feed. These data are the imported into a Google spreadsheet where conductivity is converted to salinity, and graphed in real-time. The spreadsheet data will be imported into a webpage maintained by ASTPO, where it will be displayed available for dO\\1lload.
Plant Habitat (PH) is an experiment to be taken to the International Space Station (ISS) in 2016. It is critical that ground support computers have the ability to uplink commands to control PH, and that ISS computers have the ability to downlink PH telemetry data to ground support. This necessitates communication software that can send, receive, and process, PH specific commands and telemetry. The objective of the Plant Habitat Telemetry/ Command Interface is to provide this communication software, and to couple it with an intuitive Graphical User Interface (GUI). Initial investigation of the project objective led to the decision that code be written in C++ because of its compatibility with existing source code infrastructures and robustness. Further investigation led to a determination that multiple Ethernet packet structures would need to be created to effectively transmit data. Setting a standard for packet structures would allow us to distinguish these packets that would range from command type packets to sub categories of telemetry packets. In order to handle this range of packet types, the conclusion was made to take an object-oriented programming approach which complemented our decision to use the C++ programming language. In addition, extensive utilization of port programming concepts was required to implement the core functionality of the communication software. Also, a concrete understanding of a packet processing software was required in order to put aU the components of ISS-to-Ground Support Equipment (GSE) communication together and complete the objective. A second project discussed in this paper is Exposing Microbes to the Stratosphere (EMIST). This project exposes microbes into the stratosphere to observe how they are impacted by atmospheric effects. This paper focuses on the electrical and software expectations of the project, specifically drafting the printed circuit board, and programming the on-board sensors. The Eagle Computer-Aided Drafting (CAD) software was used to draft the E-MIST circuit. This required several component libraries to be created. Coding the sensors and obtaining sensor data involved using the Arduino Uno developmental board and coding language, and properly wiring peripheral sensors to the microcontroller (the central control unit of the experiment).
During the course of the Kennedy Space Center Summer Internship, two main experiments were performed: The Vacuum-Compacted Regolith Gripping Mechanism and Unmanned Flights via Quad-copters. The objectives of the Vacuum-Compacted Regolith Gripping Mechanism, often abbreviated as the Granular Gripper, are to exhibit Space Technology, such as a soft robotic hand, lift different apparatuses used to excavate regolith, and conserve energy while executing its intended task. The project is being conducted to test how much weight the Granular Gripper can hold. With the use of an Animatronic Robotic Hand, Arduino Uno, and other components, the system was calibrated before actually conducting the intended weight test. The maximum weight each finger could hold with the servos running, in the order of pinky, ring, middle, and index fingers, are as follows: 1.340N, 1.456 N, 0.9579 N, and 1.358 N. Using the small vacuum pump system, the maximum weight each finger could hold, in the same order, was: 4.076 N, 6.159 N, 5.454 N, and 4.052 N. The maximum torques on each of the fingers when the servos were running, in the same respective order, was: 0.0777 Nm, 0.0533 Nm, 0.0648 Nm, and 0.0532 Nm. The maximum torques on the individual fingers, when the small vacuum pump was in effect, in the same order as above, was: 0.2318 Nm, 0.3032 Nm, 0.2741 Nm, and 0.1618 Nm. In testing all the fingers with the servos running, the total weight was 5.112 N and the maximum torque on the all the fingers was 0.2515 Nm. However, when the small vacuum pump system was used, the total weight was 19.741 N and the maximum torque on the all the fingers was 0.9713 Nm. The conclusion that was drawn stated that using the small vacuum pump system proved nearly 4 times more effective when testing how much weigh the hand could hold. The resistance provided by the compacted sand in the glove allowed more weight to be held by the hand and glove. Also, when the servos turned off and the hand still retaining its position, energy is being saved because the vacuum created the same resistance the running servos did without using power. The Unmanned Flights via Quad-rotors are built because multi-rotor dynamics are an important starting point and fair analog for space craft control systems and they make good terrestrial development platforms for various aspects of control for space crafts. The project is being conducted to see what the thrust response is going to be when a pulse width modulation command is sent to the control system since the quad-rotors are PWM controlled. A simulation environment in constructed so that one can quickly iterate and test different designs such as control systems, PID control vs. LDR control, and state estimation. Using two DIY Quad Kits, APM 2.6, testing apparatus (called a data acquisition system) to test the quad-rotors, and a simulation program such as Simulink, two quad-rotors are built and controlled via a simulation program, which is designed to be as realistic as possible and not idealistic. Due to the quad-rotors not being completely built nor ready for testing, there are no results or conclusions to report.
This fall I worked in EV3 within NASA's Johnson Space Center in The HIVE (Human Integrated Vehicles & Environments). The HIVE is responsible for human in the loop testing, getting new technologies in front of astronauts, operators, and users early in the development cycle to make the interfaces more human friendly. Some projects the HIVE is working on includes user interfaces for future spacecraft, wearables to alert astronauts about important information, and test beds to simulate mock missions. During my internship I created a prototype for T-38 aircraft displays using LabVIEW, learned how to use microcontrollers, and helped out with other small tasks in the HIVE. The purpose of developing a prototype for T-38 Displays in LabVIEW is to analyze functions of the display such as navigation in a cost and time effective manner. The LabVIEW prototypes allow Ellington Field AOD to easily make adjustments to the display before hardcoding the final product. LabVIEW was used to create a user interface for simulation almost identical to the real aircraft display. Goals to begin the T-38 PFD (Primary Flight Display) prototype included creating a T-38 PFD hardware display in a software environment, designing navigation for the menu's, incorporating vertical and horizontal navigation bars, and to add a heading bug for compass controls connected to the HSI (Horizontal Situation Indicator). To get started with the project, measurements of the entire display were taken. This enabled an accurate model of the hardware display to be created. Navigation of menu's required some exploration of different buttons on the display. The T-38 simulator and aircraft were used for examining the display. After one piece of the prototype was finished, another trip of to the simulator took place. This was done until all goals for the prototype were complete. Some possible integration ideas for displays in the near future are autopilot selection, touch screen displays, and crew member preferences. Complete navigation, control, and function customization will be achievable once a display is fully developed. Other than the T-38 prototyping, I spent time learning how to design small circuits and write code for them to function. This was done by adding electronic circuit components to breadboard and microcontroller then writing code to speak to those components through the microcontroller. I went through an Arduino starter kit to build circuits and code software that allowed the hardware to act. This work was planned to assist in a lighting project this fall but another solution was discovered for the lighting project. Other tasks that I assisted with, included hands on work such as mock-up construction/removal, logic analyzer repairs, and soldering with circuits. The unique opportunity to be involved work with NASA has significantly changed my educational and career goals. This opportunity has only opened the door to my career with engineering. I have learned over the span of this internship that I am fascinated by the type of work that NASA does. My desire to work in the aerospace industry has increased immensely. I hope to return to NASA to be more involved in the advancement of science, engineering, and spaceflight. My interests for my future education and career lie in NASA’s work - pioneering the future in space exploration, scientific discovery and aeronautics research.
The Human Interface Branch - EV3 - is evaluating Organic lighting-emitting diodes (OLEDs) as an upgrade for current displays on future spacecraft. OLEDs have many advantages over current displays. Conventional displays require constant backlighting which draws a lot of power, but with OLEDs they generate light themselves. OLEDs are lighter, and weight is always a concern with space launches. OLEDs also grant greater viewing angles. OLEDs have been in the commercial market for almost ten years now. What is not known is how they will perform in a space-like environment; specifically deep space far away from the Earth's magnetosphere. In this environment, the OLEDs can be expected to experience vacuum and galactic radiation. The intern's responsibility has been to prepare the OLED for a battery of tests. Unfortunately, it will not be ready for testing at the end of the internship. That being said much progress has been made: a) Developed procedures to safely disassemble the tablet. b) Inventoried and identified critical electronic components. c) 3D printed a testing apparatus. d) Wrote software in Python that will test the OLED screen while being radiated. e) Built circuits to restart the tablet and the test pattern, and ensure it doesn't fall asleep during radiation testing. f) Built enclosure that will house all of the electronics Also, the intern has been working on a way to take messages from a simulated Caution and Warnings system, process said messages into packets, send audio packets to a multicast address that audio boxes are listening to, and output spoken audio. Currently, Cautions and Warnings use a tone to alert crew members of a situation, and then crew members have to read through their checklists to determine what the tone means. In urgent situations, EV3 wants to deliver concise and specific alerts to the crew to facilitate any mitigation efforts on their part. Significant progress was made on this project: a) Open channel with the simulated Caution and Warning system to acquire messages. b) Configure audio boxes. c) Grab pre-recorded audio files. d) Packetize the audio stream. A third project that was assigned to implement LED indicator modules for an Omnibus project. The Omnibus project is investigating better ways designing lighting for the interior of spacecraft-both spacecraft lighting and avionics box status lighting indication. The current scheme contains too much of the blue light spectrum that disrupts the sleep cycle. The LED indicator modules are to simulate the indicators running on a spacecraft. Lighting data will be gathered by human factors personal and use in a model underdevelopment to model spacecraft lighting. Significant progress was made on this project: Designed circuit layout a) Tested LEDs at LETF. b) Created GUI for the indicators. c) Created code for the Arduino to run that will illuminate the indicator modules.
This report is a Master's Thesis in Aerospace Engineering, performed at the NASA Ames Research Center. It describes the development of the CubeSub, a submersible testbed compatible with the CubeSat form factor. The CubeSub will be used to mature technology and operational procedures to be used in space exploration, and possibly also as a tool for exploration of Earthly environments. CubeSats are carried as payloads, either containing technology to be tested or experiments and sensors for scientific use. The CubeSub is designed to be built up by modules, which can be assembled in different configurations to fulfill different needs. Each module is powered individually and intermodular communication is wireless, reducing the need for wiring. The inside of the hull is flooded with ambient water to simplify the interaction between payloads and surrounding environment. The overall shape is similar to that of a conventional AUV, slender and smooth. This is to make for a low drag, reduce the risk of snagging on surrounding objects and make it possible to deploy through an ice sheet via a narrow borehole. Rapid prototyping is utilized to a large extent, with full-scale prototypes being constructed through 3D-printing and with COTS (Commercial Off-The-Shelf) components. Arduino boards are used for control and internal communication. Modules required for basic operation have been designed, manufactured and tested. Each module is described with regards to its function, design and manufacturability. By performing tests in a pool it was found that the basic concept is sound and that future improvements include better controllability, course stability and waterproofing of electrical components. Further development is needed to make the CubeSub usable for its intended purposes. The largest gains are expected to be found by developing the software and improving controllability.
This presentation introduces and discusses the development of the CubeSub submersible concept, an Autonomous Underwater Vehicle (AUV) designed around the CubeSat satellite form factor. The presented work is part of the author's MSc thesis in Aerospace Engineering at the Royal Institute of Technology, Stockholm, Sweden, and was performed during an internship at the Mission Design Division of the NASA Ames Research Center, Moffett Field, CA. Still in the early stages of its development, the CubeSub is to become a submersible test-bed for technology qualified for underwater and space environments. With the long-term goal of exploring the underwater environments in outer space, such as the alleged subsurface ocean of Jupiter's moon Europa, a number of technology and operational procedures must be developed and matured. To assist in this, the CubeSub platform is introduced as a tool to allow engineers and scientists to easily test qualified technology underwater. A CubeSat is a class of miniaturized satellite built to a standardized size. The base size is 1U (U for unit), corresponding to a 100 x 100 x 113.5 cu mm cube. A 1U CubeSat can in other words easily be held in one hand. Stacking units give larger satellite sizes such as the also commonly used 1.5U, 2U and 3U. The CubeSat standard is in itself already well established and hundreds of CubeSats have to date been launched into space. Compatible technology is readily available and the know-how exists in the space industry, all of which makes it a firm ground to stand on for the CubeSub. The rationale behind using the CubeSat form factor is to make use of this pre-existing foundation, making the CubeSub easy to develop, modular and readily available. It will thereby aid in the process of maturing the concept of a fully space qualified submersible headed for outer space. As a further clarification, the CubeSub is itself not meant for outer space, but to facilitate development of such a vessel. Along with its uses as a testbed, the CubeSub also holds the potential to become a useful tool for exploration and experimentation here on Earth. A highly standardized system utilizing well-known hardware can reduce the cost and required work load for researchers wishing to perform experiments and exploration. Users could design sensors and experiments to comply with the already well established CubeSat standard, which are then carried by the CubeSub to the region of interest. This in turn means that the end users can focus more on formulating the experiment itself and less about how to get it where they want it. The CubeSub is designed to be built up by modules, which can be assembled in different configurations to fulfill different needs. Each module will be powered individually and intermodular communication will be wireless, removing the need for wiring. The inside of the cylindrical hull will be flooded with ambient water to enhance the interaction between payloads and surrounding environment. The overall torpedo-like shape is similar to that of a conventional AUV, slender and smooth. This is to make for a low drag, reduce the risk of snagging on surrounding objects and make it possible to deploy through an ice sheet via a narrow borehole or navigate in tight areas. To keep costs low and further accelerate development, rapid prototyping is utilized wherever possible. Full-scale prototypes are being constructed through 3D-printing and using COTS (Commercial Off-The-Shelf) components. 3D-printing is used both for the largest hull components and the relatively small and delicate propellers. Arduino boards are used for control and internal communication
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.
The PISCES instrument is a portable, miniature, modular instrument designed to analyze organic molecular signatures of life. PISCES uses microcapillary electrophoresis (μCE) with laser-induced fluorescence detection (LIFD) to analyze fluorescently-labeled analytes prepared on a multi-layer microfluidic chip. As a modular instrument composed of five independently functioning units, each module can be easily detached from the system and used for subsystem testing in different environments, e.g. low temperature. The pneumatic module contains mechanical and electrical components necessary to control pneumatically-actuated valves for on-chip sample processing. A prototype LabVIEW program and two custom printed circuit boards (PCBs) operate the pneumatics module using an Arduino microcontroller, and a tentative design for the module’s housing has been developed. The high-voltage module contains circuitry required to apply varying electrical potentials to the electrophoretic channel of the microdevice. Work is currently being done to design the circuit and PCB for this module in collaboration with our SBIR partners at Los Gatos Research. The optical electronics module contains the spectrometer, laser, and laser power supply. The mounting components for the electronics and housing for the module have been designed, assembled, and tested. The optical module contains optical components to focus the laser to a 20μm spot in the center of the electrophoretic channel.The housing for this module has been designed and assembled with the aligned optical components inside.