Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “trigger concepts”

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.

114 records · Page 7

Multifunctional Inflatable Structure Being Developed for the PowerSphere Concept

NASA has funded a collaborative team of The Aerospace Corporation, ILC Dover, Lockheed Martin, and NASA Glenn Research Center to develop the Multifunctional Inflatable Structure (MIS) for a "PowerSphere" concept through a NASA Research Announcement. This power system concept has several advantages, including a high collection area, low weight and stowage volume, and the elimination of all solar array pointing mechanisms. The current 3-year effort will culminate with the fabrication and testing of a fully functional engineering development unit. The baseline design of the Power-Sphere consists of two opposing semispherical domes connected to a central spacecraft. Each semispherical dome consists of hexagonal and pentagonal solar cell panels that together form a geodetic sphere. Inflatable ultraviolet (UV) rigidizable tubular hinges between the solar cell panels and UV rigidizable isogrid center columns with imbedded flex circuitry form the MIS. The reference configuration for the PowerSphere is a 0.6-m-diameter (fully deployed) spacecraft with a total mass budget of 4 kg (1 kg for PowerSphere, 3 kg for spacecraft) capable of producing 29 W of electricity with 10-percent-efficient thin-film solar cells. In a stowed configuration, the solar cell panels will be folded sequentially to the outside of the instrument decks. The center column will be z-folded between the instrument decks and the spacecraft housing for packaging. The instrument panel will secure the z-folded stack with launch ties. After launch, once the release tie is triggered, the center column and hinge tubes will inflate and be rigidized in their final configurations by ultraviolet radiation. The overall PowerSphere deployment sequence is shown pictorially in the following illustration.

Peterson, Todd T.↗

Using Open Standards and NASA Open Source Simulation Tools to Model Artemis Base Camp Mission Timelines

The United States’ National Aeronautics and Space Administration (NASA) has announced that the Artemis Program will return humans to the Moon, establishing a persistent presence with the Artemis Base Camp (ABC), and extend human exploration to Mars. The NASA Exploration Systems Simulations (NExSyS) team at NASA’s Johnson Space Center is using internationally developed simulation interoperability standards and NASA open source simulation tools to support Artemis concept, analysis, designs, development, training, and ultimately operations. The NExSyS team has been tasked to support early ABC architecture and mission analysis using mission time lines developed by the crew operations mission planning team. The NExSyS team is developing a distributed simulation framework with initial Artemis element implementations to model the ABC mission timelines using the international simulation interoperability standard High Level Architecture (HLA), the Simulation Interoperability Standards Organization’s Space Reference Federation Object Model (SpaceFOM), the NASA open source Trick Simulation Environment, and another NASA open source interface package called TrickHLA. The ABC architecture is composed of a number of key surface elements and resources. Some examples of modeled elements (also known as entities) are landers, habitats, rovers, logistics carriers, and astronauts. Some examples of modeled transferable and consumable resources are power, water, oxygen, nitrogen, scientific samples, and food. These entities and resources are modeled in a collection of individual simulations called Federates. A coordinated collection of interoperable federates is called a Federation and when these federates are tied together in a coordinated simulation run, it is referred to as a Federation Execution. The federates communicate through HLA using data exchange formats defined by a collection of machine readable files called Federation Object Models (FOMs). These FOM files are based on extensions to the SpaceFOM. This enables the instantiation and sharing of objects and interactions between federates in the federation. These provide for entity and resource tracking, object transfer, and data collection. Federate interactions are used to trigger events and notify federates of entity or resource transfers. For the initial implementation, the constituent federates are Trick-based simulations that use TrickHLA to provide the required HLA-base interoperability. These Trick-based simulations provide the required modeling for the individual Artemis elements along with the associated element resources. These federates provide a means to explore traverses between surface elements and exploration sites as scheduled in a mission timeline and explore the affects traverse times have on the overall mission timeline. The mission time lines are modeled using a Trick input file event handling capabilities. Each timeline operation is handled as individual simulation events, and triggered based on previous event status, time of operation, and simulated task completions. In addition, the ABC Federation can be used to perform Monte Carlo analysis. The Monte Carlo tool can vary the inputs, timings, and malfunctions to show how various contingencies in the mission can affect the mission timeline.

Keaton Craig Dodd↗

Using the cFS Command and Data Dictionary (CCDD) to Automate Software Development on Habulous

Final paper is attached. The NASA developed Core Flight System (cFS) is a reusable software architecture that has been used on multiple spaceflight missions. By using this framework, missions are able to reuse code from other missions, as well as leverage deployment onto similar computer architectures (i.e. not "reinvent the wheel" on each new mission). The success in the cFS concept can be seen in the large number of projects using cFS at FSW-2018. The Habulous project is an Earth-based testbed, used for hardware and software that may one day be used on a future space habitat unit, with many participating groups from various NASA centers and aerospace organizations around the country. The distributed nature of the various teams mean that defining (and following) an interface definition is critical on the project. Additionally, since various groups use various types of computer hardware (32/64-bit, big/little endian, Linux/VxWorks/Windows) many additional complications exist in interfacing all the various components into a final integrated system. cFS is used on the majority the flight software (FSW) in running in Habulous. But some subsystems have elected to not use cFS, and use a software bridge (called SBN_lib) to interact with the other cFS nodes in Habulous. In order to most efficiently develop the FSW, a central database is used to define and store each message sent by cFS. A Command and Data Dictionary (CDD) is something nearly universal on spacecraft, but as a team we worked to develop the CDD before the SW development was complete, and not treat it like "as built" documentation. To manage the CDD, the cFS Command and Data Dictionary (CCDD) tool was chosen (available from NASA as open source software). The CCDD tool has successfully been used to automate/autocode a large amount of software used on Habulous, as we are hoping to use it to define even more items in the future (time-triggered Ethernet (TTE) network maps, CPU scheduling). Additionally, Habulous has been exploring the use of cFS on wildly heterogeneous CPUs, and how to coordinate all those various machines using/extending the software bus – network (SBN) application in cFS, as well as TTE to coordinate message passing between various synchronized machines. The major topics to be covered in the presentation are: (1) Updating to the CCSDS_v2 extended headers (and using CPU# as subsystem ID). (2) Managing all the message identification numbers for each cFS message sent/received on any of the various CPUs. (3) Using the CCDD information to automatically generate the C-header files that define the structure for all software bus (SB) commands/telemetry messages. (4) Using the CCDD to automatically generate XML Telemetry and Command Exchange (XTCE) files, which streams display production/integration/testing in a web based display architecture (5) Extending/customizing SBN to pass messages among computers on multiple networks. (6) Using "Protobetter" inside SBN to manage different endian-ness/architectures. (7) Using SBN_lib to allow non-cFS node to communicate with cFS nodes. (8) Developing TTE network and schedule tables for all the various CPUs to use.

Hirsh, Robert L.↗

Analysis of Proposed 2007-2008 Revisions to the Lightning Launch Commit Criteria for United States Space Launches

Ascending space vehicles are vulnerable to both natural and triggered lightning. Launches under the jurisdiction of the United States are generally subject to a set of rules called the Lightning Launch Commit Criteria (LLCC). The LLCC protect both the vehicle and the public by assuring that the launch does not take place in conditions posing a significant risk of a lightning strike to the ascending vehicle. Such a strike could destroy the vehicle and its payload, thus causing failure of the mission while releasing both toxic materials and debris. To assure safety, the LLCC are conservative and sometimes they may seriously limit the ability of the launch operator to fly as scheduled even when conditions are benign. In order to safely reduce the number of launch scrubs and delays attributable to the LLCC, the Airborne Field Mill (ABFM) program was undertaken in 2000 - 2001. The effort was directed to collecting detailed high-quality data on the electrical, microphysical, radar and meteorological properties of thunderstorm-associated clouds. The expectation was that this additional knowledge would provide a better physical basis for the LLCC and allow them to be revised to be both safer and less restrictive. That expectation was fulfilled, leading to significant revisions to the LLCC in 2003 and 2005. The 2005 revisions included the application of a new radar-derived quantity called the Volume Averaged Height Integrated Radar Reflectivity (VAHIRR) in the rules governing flight through anvil clouds. Analysis of the ABFM data has continued, and two additional revisions to the LLCC were proposed in late 2006 for adoption in 2007 or 2008. One proposal was to apply the VAHIRR concept to debris clouds, and the other was to reduce the "stand-off distances" in the rules for anvil and/or debris clouds. The stand-off distance is the clearance (out side of the cloud) required between the flight path of the vehicle and the edge of a cloud that it is not permissible to fly through. This paper will discuss these proposed changes in the LLCC and the scientific rationale for adopting or rejecting them based on ABFM data.

Dye, J. E.↗

Loss-of-Control-Inhibitor Systems for Aircraft

Systems to provide improved tactile feedback to aircraft pilots are being developed to help the pilots maintain harmony between their control actions and the positions of aircraft control surfaces, thereby helping to prevent loss of control. A system of this type, denoted a loss-of-control-inhibitor system (LOCIS) can be implemented as a relatively simple addition to almost any pre-existing flight-control system. The LOCIS concept offers at least a partial solution to the problem of (1) keeping a pilot aware of the state of the control system and the aircraft and (2) maintaining sufficient control under conditions that, as described below, have been known to lead to loss of control. Current commercial aircraft exhibit uneven responses of primary flight-control surfaces to aggressive pilot control commands, leading to deterioration of pilots ability to control their aircraft. In severe cases, this phenomenon can result in loss of control and consequent loss of aircraft. For an older aircraft equipped with a purely mechanical control system, the loss of harmony between a pilot s command action and the control- surface response can be attributed to compliance in the control system (caused, for example, by stretching of control cables, flexing of push rods, or servo-valve distortion). In a newer aircraft equipped with a fly-by-wire control system, the major contributions to loss of harmony between the pilot and the control surfaces are delays attributable to computer cycle time, control shaping, filtering, aliasing, servo-valve distortion, and actuator rate limiting. In addition, a fly-by-wire control system provides no tactile feedback that would enable the pilot to sense such features of the control state as surface flutter, surface jam, position limiting, actuator rate limiting, and control limiting imposed by the aircraft operational envelope. Hence, for example, when a pilot is involved in aggressive closed-loop maneuvering, as when encountering a wake-vortex upset on final landing approach, the control-surface delay can lead to loss of control. Aggressive piloting can be triggered and exacerbated by control-system anomalies, which the pilot cannot diagnose because of the lack of symptoms caused by the absence of feedback through the controls. The purpose served by a LOCIS is to counteract these adverse effects by providing real-time feedback that notifies the pilot that the aircraft is tending to lag the pilot s commands. A LOCIS (see figure) includes cockpit control input-position sensors, control-surface output-position sensors, variable dampers (for example, shock absorbers containing magneto-rheological fluids such that the damping forces can be varied within times of the order of milliseconds by varying applied magnetic fields) attached to the cockpit control levers, electromagnet coils to apply the magnetic fields, and feedback control circuits to drive the electromagnet coils. The feedback control gains are chosen so that the current applied to each electromagnet coil results in a damping force that increases in a suitable nonlinear manner (e.g., exponentially) with the difference between the actual and commanded positions of the affected control surface. The increasing damping force both alerts the pilot to the onset of a potentially dangerous situation and resists the pilot s effort to command a control surface to change position at an excessive rate

AHarrah, Ralph C.↗

Three Paradigms of Lunar Regolith Evolution

Integration of diverse datasets on the Moon may render some paradigms of lunar science either better-defended or vulnerable. We will consider three paradigms commonly used for understanding the processes of lunar regolith evolution in light of new and accumulated data. Our premise is that all data-sets should converge to a single interpretation if a concept or model is to be accepted as a paradigm. If a convergence is lacking, the paradigm needs fresh scrutiny. SteadyState: Lunar regolith evolution is currently understood in terms of comminution, agglutination, and replenishment as described by McKay and coworkers). Briefly, the model envisages continued micrometeoritic bombardment to comminute exposed soil particles to finer sizes while continued agglutination consumes finer sizes to produce larger constructional particles. Eventually, a balance between these two opposing processes achieves a steady state; soils at steady state maintain their mean grain size (M(sub z)). Episodic higher-energy impacts excavate fresh coarse material from below the soil cover, disturb the steady state, and restart the process to achieve a new steady state. It follows that the thickness of the regolith at any site would control the frequency of replenishment; indeed, the thickness of the regolith at Apollo landing sites was predicted by McKay et al. from the average M(sub z) of local soils. However, replenishment may come also from disintegrating boulders and cobbles at the lunar surface, and rates of comminution and agglutination may depend on the properties of target material. Regression between M(sub z) and I(sub s)/Fe(sup 0) (a measure of maturity or total surface exposure) of Apollo soils at different sites shows the following relations and estimated M(sub z) at a high maturity of I(sub s)/Fe(sup 0)= 100. It is possible that Apollo 12 and 15 sites have the thickest regolith and the Apollo 16 site has the thinnest. It is also possible that Apollo 12 and 15 basalts are comminuted faster than Apollo 16 highland rocks and Apollo 14 and 17 soils are products of mixed parentage. If a soil becomes continually finer as it matures until agglutination catches up, and if comminution is differential-dependent on the physical properties of the constituents, then the composition of the bulk soil has to match the composition of some "fulcrum" grain size fraction, say X Grain size fractions >X and <X will complement each other; their mass balance is the bulk soil. It appears that the 10-20-micron size fraction may be the fulcrum. In general, trace-element chemistry and IR reflectance spectra of this size fraction are closest to that of the bulk soil, regardless of maturity that is surprising. Disaggregated products of regolith breccias may also show similar relationships. If the 10-20 gm is the fulcrum (i.e., X as above) for many soil properties (e.g., major element composition, FMR, solar-wind-implanted elements), then this may be the ultimate mean grain size of lunar soils at steady state. However, different properties of soils may find steady states at different grain size fractions. The steady state of solar-wind-implanted elements, on the other hand, will climb up the grain-size scale as agglutinates transfer surface-correlated components into volume correlated components until a saturation level is reached or the rates of replenishment and implantation become equal. The same will be the case with vapor-deposited reduced metals as they too are incorporated inside constructional particles. Properties that are directly affected by soil-maturation processes will thus have different pathways of achieving steady states. Maturity, i.e., cumulative surface exposure, of lunar soils is best quantified by the amount of nanophase superparamagnetic Fe(sup 0) (np-Fe(sup 0)) normalized to Fe content (=I(sub s)/Fe(sup 0). The majority consensus (paradigm?) for the production of np-Fe(sup 0) is associated with the production of agglutinates. Because large doses of solar-wind H are implanted in all lunar soils upon exposure, any melting (e.g., during agglutinate production) triggers a chemical reduction of Fe-bearing minerals resulting in np-Fe(sup 0) production. The quantity of np-Fe(sup 0) is thus dependent on melting events, (i.e., exposure), and limited by the Fe content of the soil. All freshly produced np-Fe(sup 0) resides in agglutinitic glass, as new TEM images show. Apparently, the correction procedure developed by Lucey et al. to estimate the Fe content of the lunar surface from IR-reflectance spectra depends on accepting the above. However, the process of producing np-Fe(sup 0) may be physical rather than chemical. All np-Fe(sup 0) could be deposits from a vapor produced by micrometeoritic impact on lunar soils. If metal-O bonds in target phases are broken, O being "most volatile" will escape leaving an O-deficient vapor to facilitate the production of np-Fe(sup 0). If so, the quantity of np-Fe(sup 0) is dependent on the vaporizing events, (i.e., exposure), and limited by the efficiency of breaking metal-O bonds and the escape of 0. To the extent that strengths of metal-O bonds are dependent on the local crystal field, production of np-Fe(sup 0) may be limited by the mineral composition of target soils and not by their total Fe content. According to this model, vapor-deposited np-Fe(sup 0) should be found at any retentive sites on lunar soil grains. Indeed, TEM images show np-Fe(sup 0) on plagioclase and ilmenite. Incorporation of such pre-irradiated np-Fe(sup 0)-bearing grains into agglutinates may account for eventual increased emplacement of np-Fe(sup 0) in agglutinates. Such a paradigm shift in understanding the origin of np-Fe(sup 0) will raise questions ranging from the unquestionable use of Is/FeO as the universal maturity parameter of lunar soils to global elemental maps of the Moon from remote-sensing data. Additional information is contained in the original.

Basu, A.↗