SEARCH · Search NASA

Results for “on-board estimation”

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.

257 records · Page 15

All sources NASA NTRS DOE OSTI

NASA NTRS2014

NASA 2014 The Hyperspectral Infrared Imager (HyspIRI) - Science Impact of Deploying Instruments on Separate Platforms

The Hyperspectral Infrared Imager (HyspIRI) mission was recommended for implementation by the 2007 report from the U.S. National Research Council Earth Science and Applications from Space: National Imperatives for the Next Decade and Beyond, also known as the Earth Science Decadal Survey. The HyspIRI mission is science driven and will address a set of science questions identified by the Decadal Survey and broader science community. The mission includes a visible shortwave infrared (VSWIR) imaging spectrometer, a multispectral thermal infrared (TIR) imager and an intelligent payload module (IPM). The IPM enables on-board processing and direct broadcast for those applications with short latency requirements. The science questions are organized as VSWIR-only, TIR-only and Combined science questions, the latter requiring data from both instruments. In order to prepare for the mission NASA is undertaking pre-phase A studies to determine the optimum mission implementation, in particular, cost and risk reduction activities. Each year the HyspIRI project is provided with feedback from NASA Headquarters on the pre-phase A activities in the form of a guidance letter which outlines the work that should be undertaken the subsequent year. The 2013 guidance letter included a recommendation to undertake a study to determine the science impact of deploying the instruments from separate spacecraft in sun synchronous orbits with various time separations and deploying both instruments on the International Space Station (ISS). This report summarizes the results from that study. The approach taken was to evaluate the impact on the combined science questions of time separations between the VSWIR and TIR data of <3 minutes, <1 week and a few months as well as deploying both instruments on the ISS. Note the impact was only evaluated for the combined science questions which require data from both instruments (VSWIR and TIR). The study concluded the impact of a separation of <3 minutes was minimal, e.g. if the instruments were on separate platforms that followed each other in a train. The impact of a separation of <1 week was strongly dependent on the question that was being addressed with no impact for some questions and a severe impact for others. The impact of a time separation of several months was severe and in many cases it was no longer possible to answer the sub-question. The impact of deploying the instruments on the ISS which is in a precessive (non-sun synchronous) orbit was also very question dependent, in some cases it was possible to go beyond the original question, e.g. to examine the impact of the diurnal cycle, whereas in other cases the question could not be addressed for example if the question required observations from the polar regions. As part of the study, the participants were asked to estimate, as a percentage, how completely a given sub-question could be answered with 100% indicating the question could be completely answered. These estimations should be treated with caution but nonetheless can be useful in assessing the impact. Averaging the estimates for each of the combined questions the results indicate that 97% of the questions could be answered with a separation of < 3 minutes. With a separation of < 1 week, 67% of the questions could be answered and with a separation of several months only 21% of the questions could be answered.

Turpie, Kevin↗

NASA NTRS2012

Advanced Lithium Ion Venus Explorer (ALIVE)

The COncurrent Multidisciplinary Preliminary Assessment of Space Systems (COMPASS) Team partnered with the Applied Research Laboratory to perform a NASA Innovative Advanced Concepts (NIAC) Program study to evaluate chemical based power systems for keeping a Venus lander alive (power and cooling) and functional for a period of days. The mission class targeted was either a Discovery ($500M) or New Frontiers ($750M to $780M) class mission. Historic Soviet Venus landers have only lasted on the order of 2 hours in the extreme Venus environment:temperatures of 460 degrees Centigrade and pressures of 93 bar. Longer duration missions have been studied using plutonium powered systems to operate and cool landers for up to a year. However, the plutonium load is very large. This NIAC study sought to still provide power and cooling but without the plutonium. Batteries are far too heavy but a system which uses the atmosphere (primarily carbon dioxide) and on on-board fuel to power a power generation and cooling system was sought. The resuling design was the Advanced Long-Life Lander Investigating the Venus Environment (ALIVE) Spacecraft (S/C) which burns lithium (Li) with the CO2 atmosphere to heat a Duplex Stirling to power and cool the lander for a 5-day duration (until the Li is exhausted). While it does not last years a chemical powered system surviving days eliminates the cost associated with utilizing a flyby relay S/C and allows a continuous low data rate direct to earth (DTE) link in this instance from the Ovda Regio of Venus. The five-day collection time provided by the chemical power systems also enables science personnel on earth to interact and retarget science - something not possible with an approximately 2-hour spacecraft lifetime. It also allows for contingency operations directed by the ground (reduced risk). The science package was based on that envisioned by the Venus Intrepid Tessera Lander (VITaL) Decadal Survey Study. The Li Burner within the long duration power system creates approximately 14000 W of heat. This 1300 degree Centigrade heat using Li in the bottom "ballast" tank is melted to liquid by the Venus temperature, drawn into a furnace by a wick and burned with atmospheric CO2. The Li carbonate exhaust is liquid at 1300 degrees Centigrade and being denser than Li drains into the the Li tank and solidifies. Since the exhaust product is a dense liquid no "chimney" is required which conserves the heat for the stirling power convertor. The Duplex Stirling provides about 300 W of power and removes about 300 W of heat from the avionics and heat that leaks into the 1-bar-insulated payload pressure vessel kept at 25 degrees Centigrade. The Na K radiator is run to the top of the drag flap.The ALIVE vehicle is carried to Venus via an Atlas 411 launch vehicle (LV) with a C3 of 7 km2/s2. An Aeroshell, derived from the Genesis mission, enables a direct entry into the atmosphere of Venus (-10 degrees Centigrade, 40 g max) and 6 m/s for landing (44 g) using a drag ring. For surface science and communication, a 100 WRF (WebEx Recording Format), X-Band 0.6-meter pointable DTE (Direct-to-Earth) antenna provides 2 kbps (kilobits per second) to DSN (Deep-Space Network) 34-meter antenna clusters.Table 1.1 summarizes the top-level details of each subsystem that was incorporated into the design. Cost estimates of the ALIVE mission show it at approximately $760M which puts it into the New Frontiers class.The ALIVE landed duration is only limited by the amount of Li which can be carried by the lander. Further studies are needed to investigate how additional mass can be carried, perhaps by a larger launcher and larger aeroshell.

Exploration↗

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 NTRS1980

Second year technical report on-board processing for future satellite communications systems

Advanced baseband and microwave switching techniques for large domestic communications satellites operating in the 30/20 GHz frequency bands are discussed. The nominal baseband processor throughput is one million packets per second (1.6 Gb/s) from one thousand T1 carrier rate customer premises terminals. A frequency reuse factor of sixteen is assumed by using 16 spot antenna beams with the same 100 MHz bandwidth per beam and a modulation with a one b/s per Hz bandwidth efficiency. Eight of the beams are fixed on major metropolitan areas and eight are scanning beams which periodically cover the remainder of the U.S. under dynamic control. User signals are regenerated (demodulated/remodulated) and message packages are reformatted on board. Frequency division multiple access and time division multiplex are employed on the uplinks and downlinks, respectively, for terminals within the coverage area and dwell interval of a scanning beam. Link establishment and packet routing protocols are defined. Also described is a detailed design of a separate 100 x 100 microwave switch capable of handling nonregenerated signals occupying the remaining 2.4 GHz bandwidth with 60 dB of isolation, at an estimated weight and power consumption of approximately 400 kg and 100 W, respectively.

Brandon, W. T.↗

NASA NTRS2021

Lunar Asset Messaging and On Orbit Navigation

NASA has titled its 2020 thrust for the Moon, Artemis. The increased focus on the Moon as a destination for future human and robotic expeditions necessitates general purpose navigational and communications infrastructure reducing their complexity to help establish a sustained presence. A framework through which Lunar missions can relay communications and localize their positions shifts the burden from the individual mission and enables resource allocation tailored to mission-specific goals. During the summer of 2020, student interns under the Innovation to Flight (i2F) program at the National Aeronautics and Space Administration’s (NASA) Jet Propulsion Laboratory (JPL) in collaboration with the University of Colorado Boulder designed, built, and tested a prototype framework capable of providing surface assets with communication and positioning services. The team utilized the existing i2F CubeSat bus in addition to developing several CubeSat engineering development units (EDUs), a ground vehicle, and a ground station to simulate a scenario in which a lunar surface mission is supported by these services. A primary goal of the summer was to develop a method for localizing the ground vehicle through trilateration. Distances are inferred from the round-trip time of flight (ToF) of radio signals between an asset and several elements. Signals were sent and received using LimeSDR software defined radios on-board both the ground vehicle and the EDUs; ToF and trilateration were calculated on a Qualcomm Snapdragon development board located within the LA MOON payload data system. The ModalAI chipset on the Qualcomm was instrumental in executing visual based position estimation. Communications was facilitated through a bent-pipe approach addressing the NASA requirement to provide solutions for in communication denied locations. The ground vehicle relayed information to other surface assets in addition to its ground station through the supporting constellation. This project demonstrates the feasibility of a lunar CubeSat constellation for the support of surface assets and explores packaging and operations of the components critical to trilateration and bent-pipe communication into a standard CubeSat form factor. When implemented, this framework will open a door for new surface missions designed with lower power requirements and increased operational access.

Huang, Calvin↗