SEARCH · Engineering Papers

Results for “open data format”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

312 records · Page 18

All sources NASA NTRS DOE OSTI

NASA NTRS1994

Theoretical, observational, and isotopic estimates of the lifetime of the solar nebula

There are a variety of isotopic data for meteorites which suggest that the protostellar nebula existed and was involved in making planetary materials for some 10(exp 7) yr or more. Many cosmochemists, however, advocate alternative interpretations of such data in order to comply with a perceived constraint, from theoretical considerations, that the nebula existed only for a much shorter time, usually stated as less than or equal to 10(exp 6) yr. In this paper, we review evidence relevant to solar nebula duration which is available through three different disciplines: theoretical modeling of star formation, isotopic data from meteorites, and astronomical observations of T Tauri stars. Theoretical models based on observations of present star-forming regions indicate that stars like the Sun form by dynamical gravitational collapse of dense cores of cold molcular clouds in the interstellar clouds in the interstellar medium. The collapse to a star and disk occurs rapidly, on a time scale of the order 10(exp 5) yr. Disks evolve by dissipating energy while redistributing angular momentum, but it is difficult to predict the rate of evolution, particularly for low mass (compared to the star) disks which nonetheless still contain enough material to account for the observed planetary system. There is no compelling evidence, from available theories of disk structure and evolution, that the solar nebula must have evolved rapidly and could not have persisted for more than 1 Ma. In considering chronoloically relevant isotopic data for meteorites, we focus on three methodologies: absolute ages by U-Pb/Pb-Pb, and relative ages by short-lived radionuclides (especially Al-26) and by evolution of Sr-87/Sr-86. Two kinds of meteoritic materials-refractory inclusions such as CAIs and differential meteorites (eucrites and augrites) -- appear to have experienced potentially dateable nebular events. In both cases, the most straightforward interpretations of the available data indicate nebular events spanning several Ma. We also consider alternative interpretations, particularly the hypothesis of radically heterogeneous distribution of Al-26, which would avoid these chronological interpretations. The principal impetus for such alternative interpretations seems to be precisely the obviation of the chronological interpretation (i.e., the presumption rather than the inference of a short (less than or equal to 1 Ma) lifetime of the nebula). Astronomical observations of T Tauri stars indicate that the presence of dusty disks is a common if not universal feature, that the disks are massive enough to accomodate a planetary system such as ours, and that at least some persist for 110(exp 7) yr or more. The results are consistent with the time scales inferred from the meteoritic isotopic data. They cannot be considered conclusive with regard to solar nebula time scales, however, in part because it is difficult to relate disk observations to processes that affect meteorites, and in part because the ages assigned for these stars could be wrong by a factor of several in either direction. We conclude that the balance of available evidence favors the view that the nebula existed and was active for at least several Ma. However, because the evidence is not definitive, it is important that the issue be perceived to be an open question, whose answer should be sought rather than presumed.

Podosek, Frank A.↗

NASA NTRS2016

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗

NASA NTRS2016

Reliability and Maintainability Analysis for the Amine Swingbed Carbon Dioxide Removal System

I have performed a reliability & maintainability analysis for the Amine Swingbed payload system. The Amine Swingbed is a carbon dioxide removal technology that has gone through 2,400 hours of International Space Station on-orbit use between 2013 and 2016. While the Amine Swingbed is currently an experimental payload system, the Amine Swingbed may be converted to system hardware. If the Amine Swingbed becomes system hardware, it will supplement the Carbon Dioxide Removal Assembly (CDRA) as the primary CO2 removal technology on the International Space Station. NASA is also considering using the Amine Swingbed as the primary carbon dioxide removal technology for future extravehicular mobility units and for the Orion, which will be used for the Asteroid Redirect and Journey to Mars missions. The qualitative component of the reliability and maintainability analysis is a Failure Modes and Effects Analysis (FMEA). In the FMEA, I have investigated how individual components in the Amine Swingbed may fail, and what the worst case scenario is should a failure occur. The significant failure effects are the loss of ability to remove carbon dioxide, the formation of ammonia due to chemical degradation of the amine, and loss of atmosphere because the Amine Swingbed uses the vacuum of space to regenerate the Amine Swingbed. In the quantitative component of the reliability and maintainability analysis, I have assumed a constant failure rate for both electronic and nonelectronic parts. Using this data, I have created a Poisson distribution to predict the failure rate of the Amine Swingbed as a whole. I have determined a mean time to failure for the Amine Swingbed to be approximately 1,400 hours. The observed mean time to failure for the system is between 600 and 1,200 hours. This range includes initial testing of the Amine Swingbed, as well as software faults that are understood to be non-critical. If many of the commercial parts were switched to military-grade parts, the expected mean time to failure would be 2,300 hours. Both calculated mean times to failure for the Amine Swingbed use conservative failure rate models. The observed mean time to failure for CDRA is 2,500 hours. Working on this project and for NASA in general has helped me gain insight into current aeronautics missions, reliability engineering, circuit analysis, and different cultures. Prior my internship, I did not have a lot knowledge about the work being performed at NASA. As a chemical engineer, I had not really considered working for NASA as a career path. By engaging in interactions with civil servants, contractors, and other interns, I have learned a great deal about modern challenges that NASA is addressing. My work has helped me develop a knowledge base in safety and reliability that would be difficult to find elsewhere. Prior to this internship, I had not thought about reliability engineering. Now, I have gained a skillset in performing reliability analyses, and understanding the inner workings of a large mechanical system. I have also gained experience in understanding how electrical systems work while I was analyzing the electrical components of the Amine Swingbed. I did not expect to be exposed to as many different cultures as I have while working at NASA. I am referring to both within NASA and the Houston area. NASA employs individuals with a broad range of backgrounds. It has been great to learn from individuals who have highly diverse experiences and outlooks on the world. In the Houston area, I have come across individuals from different parts of the world. Interacting with such a high number of individuals with significantly different backgrounds has helped me to grow as a person in ways that I did not expect. My time at NASA has opened a window into the field of aeronautics. After earning a bachelor's degree in chemical engineering, I plan to go to graduate school for a PhD in engineering. Prior to coming to NASA, I was not aware of the graduate Pathways program. I intend to apply for the graduate Pathways program as positions are opened up. I would like to pursue future opportunities with NASA, especially as my engineering career progresses.

Dunbar, Tyler↗

NASA NTRSDate not supplied

Thermodynamic constraints on the textural evolution of eucrite, EET 90020

Basaltic eucrites, which are possibly parts of the Vestan crust, formed as either lava flows or intrusions, and can offer insights into early crust formation. However most eucrites have experienced thermal metamorphism, which exacerbates the challenges of understanding these samples. A variety of petrogenetic models such as, partial melting of a primitive source, fractional crystallization of magmas emplaced in a primitive crust, and/or partial melting of a eucritic source coupled with melt mixing and assimilation have been proposed in order to explain observed petrologic and chemical characteristics of eucrites. EET 90020 is an unbrecciated eucrite that has experienced significant thermal metamorphism, with temperatures of metamorphic equilibration calculated to be ~840-1040°C. Its petrologic history remains contentious, in part due to differences in trace element analyses [10,17, this work], which has led to multiple metamorphic interpretations [8,10-11]. Here, we combined petrologic observations, chemical analyses, and thermodynamic modeling, to interpret micro-domain textures identified in EET 90020 and better constrain its petrologic history. Ultimately, the development of such textures is a direct result of the geologic processes operating on a young Vesta or similar asteroid. Sample description: We identified three textural domains in EET 90020 (Figure 1); (I) A coarse grain domain with granoblastic plagioclase and pyroxene, (II) a medium grain domain with curved grain boundaries between plagioclase and pyroxene, and (III) a fine grain domain dominated by tridymite that fills in interstitial space between spherical plagioclase. Major element chemistry in phases is consistent across domains. Pyroxene have distinctive high Ca lamellae (Wo40.92En28.1Fs31.0) forming from the low-Ca pigeonite host (Wo3.5En33.7Fs62.8). There are small amounts of fayalitic olivine along pyroxene/oxide grain boundaries, where pyroxenes have reacted with ilmenite/chromite clasts. Plagioclase is anorthitic (Avg ~An88), with little variation (An86-92.5). Trace element bulk rock analyses were collected via ICP-MS and individual mineral analyses with LA-ICP-MS (Figure 2). The bulk sample has an observable enrichment in light rare earth elements, with a notable depletion in Eu. Plagioclase is enriched in LREEs, depleted in HREEs, and has a positive Eu anomaly while pyroxene is enriched in HREEs with a negative Eu anomaly. Variations in trace element analyses is likely influenced by the presence of phosphates because are highly enriched in REEs and have a dramatic effect on the bulk domain compositions. Thermodynamic modeling: The software package, Perple_X, was used to calculate mineral phase equilibria over a range of conditions using a Gibbs free energy minimization approach [12]. Models used all major/minor elements except P2O5. Thermodynamic properties from [13] were used to constrain endmember phase stabilities. Activity models were used to describe mixing in phases with solid solution. Isochemical P-T phase diagrams were constructed for the bulk thin section, and the coarse, medium and fine grain domain compositions. Domain compositions were determined using microprobe analyses of phases identified in each domain and observed modal mineral abundancies. Thermodynamically stable pyroxene compositions were extracted from model results and compared to pyroxene compositions collected via EMPA, allowing us to calculate temperatures for metamorphic equilibrium. Results: Results that use the coarse domain composition (Fig. 3a) demonstrate overlap at T ~ 1020°C indicating high T equilibration. There was no overlap for the medium and fine grain domains, or the bulk composition (e.g., Fig. 3b) indicating that these are not equilibrium assemblages. These results were replicated using data from [8,20]. Discussion: The disequilibrium results from the bulk rock, fine grain and medium grain models imply that EET 90020 was modified during and/or after peak metamorphism (open system behavior). However, this is in contrast to the coarse domain where it appears as if equilibrium was maintained. We suggest that this conflict is explained by highly localized equilibrium occurring at millimeter length-scales, which has been observed in terrestrial metamorphism where aqueous fluid infiltrate [14] or melt loss occurs [15]. It is unlikely that aqueous alteration was significant in modifying the bulk composition of EET 90020, because it lacks hydrated minerals. However, the presence of melt is supported by the presence of an abundance of curved grain boundaries and spherical grains in the medium and fine grain domains This contrasts the coarse domain, where grain boundaries are angular. Given the evidence for disequilibrium in the medium and fine grain domains, it would be inappropriate to draw additional conclusions about textural evolution using thermodynamic models of those domains. However, modeling results of the coarse grain domain, where equilibrium was maintained, can provide useful insights into the geologic evolution of EET 90020. We approximate maximum metamorphic temperatures, using the Ca component in pyroxene, at ~1020°C (Fig. 4), which is consistent with previous two-pyroxene thermometry [11]. At this temperature, up to 10 vol % melt can be produced in the coarse grain domain, which is at the boundary of minimum melt needed in order to segregate and form a melt network [16]. Tridymite and plagioclase would be the first minerals to melt out during heating starting ~990°C. This is consistent with the observed melt textures formed by tridymite and plagioclase in the fine grain domain. We suggest that a partial melting model best explains the textural development of EET 90020. Upon heating, melt generated was either trapped, resulting in no net change in the localized rock composition, or migrated, resulting in disequilibrium between pyroxene and the surrounding matrix. A positive Eu anomaly in plagioclase indicates that all of the plagioclase was melted previously. This is consistent with previous studies that have suggested that EET 90020 represents a residual eucrite that experienced partial melting and subsequent melt loss [8]. We speculate that partial melting could have occurred when EET 90020 was heated in the asteroid’s lower crust or adjacent to an intrusion [7]. Future work will study other, texturally heterogeneous samples to see if EET 90020 presents a unique circumstance or whether crustal partial melting was ubiquitous on the eucrite asteroid.

Eucrites↗

NASA NTRS1998

Deep Basalt Aquifers in Orcus Patera, Elysium Basin Mars: Perspectives for Exobiology Exploration

Direct indicators of shorelines, spillways, and terraces allowed to determine the extent of the Elysium Paleolake between the contour-lines 1000 and 500 m below the Martian datum. The Elysium Paleolake is bordered north by Orcus Patera (14N/181W), which lies west of the Tartarus Montes and Tartarus Colles. The Orcus Patera displays an ellipse-shaped collapsed caldera of 360-km long and 100-km wide. Viking topographic data show that the bottom of the caldera is located at 2500 below the Martian datum, and surrounded by a steep-walled ram art which crest is located at about 0 m elevation. Considering the localization of Orcus Patera in the Elysium paleolake, its altimetry, and the magmatic origin of this caldera, we propose the existence of a paleolake in Orcus Patera generated (a) by juvenile water from magma during the Noachian period, and (b) by intermittent influx of the Elysium Basin from Hesperian to Amazonian. Results are encouraging to consider this site as a potential high-energy source environment for microbial communities. are circumscribed by a 50-km wide lava field mapped as Noachian material. The structure of Orcus Patera represents the record of material erupted from a magmatic reservoir. The caldera is enclosed by steep inner walls (25% measured from topographic data), values which could be in agreement with the presence of a deep magmatic reservoir, as suggested by the typology of Crumpler et.al. The depth of the caldera might be due to the collapse of the magma reservoir, and the release of gases accompanying the magma thermal evolution. Origins of water for the paleolake(s): The water that generated a paleolake in Orcus Patera may have come from two origins: (1) Juvenile water: Plescia and Crips estimated a magma H20 content by weight between 0.5% and 1.5% using for the first value a comparison with terrestrial basalt, and for the second values from a Martian meteorite. The amount of H20 can be estimated by the volume of erupted lava, and the lava content of the caldera. In this study, we adopt a water content of 1%. The total volume of magma that has been contained in the caldera, and the volume of lava contained in the observed lava field is about 110 x 10(exp 6) cubic km, that gives a total volume of 1.10 x 10(exp 6) cubic km of water. The juvenile water expelled by the overpressure within the magma chamber charged with desolved water-vapor may have moved into the crust. The decrease in overburden pressure led to bubble formation. The ascent of these bubbles generated a pressurization of the magma, which was sufficient to fracture the overlaying magma layer, (2) Water from Elysium paleolake. During the Amazonian, the rise of the Elysium paleolake level generated an overspilling that supplied the caldera with water. The southern portion of the crest shows a deep gap 12-km wide at -1500 m elevation, locating the gap between 500 to 1000 in below the assumed water of Elysium paleolake, thus facilitating the influx of Elysium paleolake water into Orcus Patera. Bathymetric calculations give a floor area of 25,500 sq km at -2000 m elevation, and a water volume of 42,000 cubic km, with a lake-level at -1500 m. A substantial amount of water may have percolated through the fractured lava, and part of the volume may have overspilled the northern crest of Orcus Patera to debouch in the Tartarus Montes region. We envision the formation of a subsurface aqueous environment in basaltic rocks at the contact of the two water-source origins, possibly the percolating surface lake water, and more likely the juvenile water. Similarly to terrestrial calderas, Orcus Patera might be surrounded by ring-fractures caused by the collapse of the magma chamber that followed the release of gases. These ring-fractures may have been covered later by sedimentation in the caldera (lacustrine, aeolian, and volcanic), and by mass wasting. The detumescence of the magma in the caldera, and the vesiculation of the juvenile water may have operated simultaneously. Comparatively to terrestrial melts, Martian iron-rich melts are denser. This greater density implies greater effusion rates (eight-times terrestrial values), and larger fissuration widths (two-times terrestrial ones). With increasing vesiculation of magma, the bubbles interact with one-another because there are of similar pressure. They make a magma froth at the contact with the caldera surface, and on the walls of the fractures. In the saturated magma, froth, where the volume ratio of gases-to-liquid is about 4:1, the bubbles form a huge surface area of interconnected spaces. Bubbles near the caldera surface disrupt the magma, and fragmentation takes place, which moves downward through the magma column. On Earth, the bubbles are likely to grow between 1 and 50 mm in diameter due to the difference between the magma surface tension, and the bubble supersaturation pressure. The Martian low-pressure at surface level is likely to accelerate the expansion of the bubbles, and increase their final diameter and number, creating more voids in the magma. The strong magma froth with enclosed juvenile water bubbles interconnected with exsolved gas bubbles constitute a potential geothermal environment for geochemical energy production from basalt and water that does not require excessive temperatures. This process can start at +20C. Similar types of environments have been shown on Earth as potential energy sources for microbial metabolism, and could have provided deep aqueous basaltic niches for possible Martian microorganisms, even geologically recently. During the Amazonian, combination of volcanism and water activity still existed on Mars. Moreover, this type of potential niches open ways for investigation of possible oases of extinct or extant life, not only on paleolakes, and surface hydrothermalism spring areas, but also all large systems of fossae, which combine hydrologic and volcanic activities, and which provide an energy source, and an underground shelter to prevent surface UV bombardment. Additional information contained in the original.

Grin, E. A.↗

NASA NTRS2015

Hardware in the Loop Testing of an Iodine-Fed Hall Thruster

CUBESATS are relatively new spacecraft platforms that are typically deployed from a launch vehicle as a secondary payload,1 providing low-cost access to space for a wide range of end-users. These satellites are comprised of building blocks having dimensions of 10x10x10 cm cu and a mass of 1.33 kg (a 1-U size). While providing low-cost access to space, a major operational limitation is the lack of a propulsion system that can fit within a CubeSat and is capable of executing high delta v maneuvers. This makes it difficult to use CubeSats on missions requiring certain types of maneuvers (i.e. formation flying, spacecraft rendezvous). Recently, work has been performed investigating the use of iodine as a propellant for Hall-effect thrusters (HETs) 2 that could subsequently be used to provide a high specific impulse path to CubeSat propulsion. Iodine stores as a dense solid at very low pressures, making it acceptable as a propellant on a secondary payload. It has exceptionally high ρIsp (density times specific impulse), making it an enabling technology for small satellite near-term applications and providing the potential for systems-level advantages over mid-term high power electric propulsion options. Iodine flow can also be thermally regulated, subliming at relatively low temperature ( less than100 C) to yield I2 vapor at or below 50 torr. At low power, the measured performance of an iodine-fed HET is very similar to that of a state-of-the-art xenon-fed thruster. Just as importantly, the current-voltage discharge characteristics of low power iodine-fed and xenon-fed thrusters are remarkably similar, potentially reducing development and qualifications costs by making it possible to use an already-qualified xenon-HET PPU in an iodine-fed system. Finally, a cold surface can be installed in a vacuum test chamber on which expended iodine propellant can deposit. In addition, the temperature doesn't have to be extremely cold to maintain a low vapor pressure in the vacuum chamber (it is under 10(exp -6) torr at -75 C), making it possible to 'cryopump' the propellant with lower-cost recirculating refrigerant-based systems as opposed to using liquid nitrogen or low temperature gaseous helium cryopanels. In the present paper, we describe testing performed using an iodine-fed 200 W Hall thruster mounted to a thrust stand and operated in conjunction with MSFCs Small Projects Rapid Integration and Test Environment (SPRITE) Portable Hardware In the Loop (PHIL) hardware. This work is performed in support of the iodine satellite (iSAT) project, which aims to fly a 200-W iodine-fed thruster on a 12-U CubeSat. The SPRITE PHIL hardware allows a given vehicle to do a checkout of its avionics algorithm by allowing it to monitor and feed data to simulated sensors and effectors in a digital environment. These data are then used to determine the attitude of the vehicle and a separate computer is used to interpret the data set and visualize it using a 3D graphical interface. The PHIL hardware allows the testing of the vehicles bus by providing 'real' hardware interfaces (in the case of this test a real RS422 bus) and specific components can be modeled to show their interactions with the avionics algorithm (e.g. a thruster model). For the iSAT project the PHIL is used to visualize the operating cycle of the thruster and the subsequent effect this thrusting has on the attitude of the satellite over a given period of time. The test is controlled using software running on an Andrews Space Cortex 160 flight computer. This computer is the current baseline for a full iSAT mission. While the test could be conducted with a lab computer and software, the team chose to exercise the propulsion system with a representative CubeSat-class computer. For purposes of this test, the "flight" software monitored the propulsion and PPU systems, controlled operation of the thruster, and provided thruster state data to the PHIL simulation. Commands to operate the thruster were initiated from an operator's workstation outside the vacuum chamber and passed through the Cortex 160 to exercise portions of the flight avionics. Two custom-designed pieces of electronics hardware have been designed to operate the propellant feed system. One piece of hardware is an auxiliary board that controls a latch valve, proportional flow control valves (PFCVs) and valve heaters as well as measuring pressures, temperatures and PFCV feedback voltage. An onboard FPGA provides a serial link for issuing commands and manages all lower level input-output functions. The other piece of hardware is a power distribution board, which accepts a standard bus voltage input and converts this voltage into all the different current-voltage types required to operate the auxiliary board. These electronics boards are located in the vacuum chamber near the thruster, exposing this hardware to both the vacuum and plasma environments they would encounter during a mission, with these components communicating to the flight computer through an RS-422 interface. The auxiliary board FPGA provides a 28V MOSFET switch circuit with a 20ms pulse to open or close the iodine propellant feed system latch valve. The FPGA provides a pulse width modulation (PWM) signal to a DC/DC boost converter to produce the 12-120V needed for control of the proportional flow control valve. There are eight MOSFET-switched heating circuits in the system. Heaters are 28V and located in the latch valve, PFCV, propellant tank and propellant feed lines. Both the latch valve and PFCV have thermistors built into them for temperature monitoring. There are also seven resistance temperature device (RTD) circuits on the auxiliary board that can be used to measure the propellant tank and feedline temperatures. The signals are conditioned and sent to an analog to digital converter (ADC), which is directly commanded and controlled by the FPGA.

Polzin, Kurt A.↗