SEARCH · Engineering Papers

Results for “software compatibility”

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.

At least 235 records · Page 13

All sources NASA NTRS DOE OSTI

NASA NTRS1980

Monitoring and control requirement definition study for Dispersed Storage and Generation (DSG). Volume 2, appendix A: Selected DSG technologies and their general control requirements

A consistent approach was sought for both hardware and software which will handle the monitoring and control necessary to integrate a number of different DSG technologies into a common distribution dispatch network. It appears that the control of each of the DSG technologies is compatible with a supervisory control method of operation that lends itself to remote control from a distribution dispatch center.

Source record↗

NASA NTRS1990

ISIS and META projects

ISIS and META are two distributed systems projects at Cornell University. The ISIS project, has developed a new methodology, virtual synchrony, for writing robust distributed software. This approach is directly supported by the ISIS Toolkit, a programming system that is distributed to over 300 academic and industrial sites. Several interesting applications that exploit the strengths of ISIS, including an NFS-compatible replicated file system, are being developed. The META project, is about distributed control in a soft real time environment incorporating feedback. This domain encompasses examples as diverse as monitoring inventory and consumption on a factory floor and performing load-balancing on a distributed computing system. One of the first uses of META is for distributed application management: the tasks of configuring a distributed program, dynamically adapting to failures, and monitoring its performance. Recent progress and current plans are presented. This approach to distributed computing, a philosophy that is believed to significantly distinguish the work from that of others in the field, is explained.

Birman, Kenneth↗

NASA NTRS1994

Pyrolaser Operating System

Software provides for control and acquisition of data from optical pyrometer. There are six individual programs in PYROLASER package. Provides quick and easy way to set up, control, and program standard Pyrolaser. Temperature and emisivity measurements either collected as if Pyrolaser in manual operating mode or displayed on real-time strip charts and stored in standard spreadsheet format for posttest analysis. Shell supplied to allow macros, which are test-specific, added to system easily. Written using Labview software for use on Macintosh-series computers running System 6.0.3 or later, Sun Sparc-series computers running Open-Windows 3.0 or MIT's X Window System (X11R4 or X11R5), and IBM PC or compatible computers running Microsoft Windows 3.1 or later.

Roberts, Floyd E., III↗

NASA NTRSDate not supplied

Development of Acoustic Mufflers for Cabin Noise Reduction in Orion Spacecraft

Controlling cabin acoustic noise levels in the Crew Module (CM) of the Orion spacecraft is critical to ensure adequate speech intelligibility, to avoid fatigue, and prevent any possibility of temporary and permanent hearing loss to the crew. The primary source of cabin noise for the on-orbit phase of the mission is from the Environmental Control and Life Support System (ECLSS) which recycles and conditions breathing air and maintains cabin pressurization through its duct network and components. Unfortunately, as a side effect, noise from the ECLSS fans propagates through theses ducts and emanate into the cabin habitable volume via the ECLSS inlet and outlets. To mitigate excessive duct-borne noise, two ECLSS mufflers have been designed to provide significant acoustic transmission loss (TL) so that the cabin noise requirements can be met. Each muffler is meant to be installed in the ducting of the ECLSS air inlet and outlet sides, respectively. Packaging constraints and tight volume requirements necessitated the mufflers to be of complex geometry and compatible with the bends of the ECLSS duct layout. To design and characterize the acoustic performance of the inlet and outlet mufflers, computational acoustic models were developed using the Finite Element Method (FEM) with 𝑤𝑎𝑣𝑒଺ vibroacoustic software. Characterization of the acoustic material and perforations in the mufflers were addressed with poroelastic theory. Once the mufflers were designed on paper and its TL predicted, prototypes of these mufflers were created using additive manufacturing. The muffler prototypes were subsequently tested for acoustic TL in the laboratory with various con-figurations of acoustic materials. Comparing the analytical predictions to the test performance yielded excellent correlation for acoustic TL and demonstrated significant broadband noise attenuation. The ECLSS mufflers are currently scheduled to be installed on the Artemis II Crew Module (CM) of the Orion spacecraft and will provide significant cabin comfort to crew during the mission.

Indranil Dandaroy↗

NASA NTRSDate not supplied

VIPER Lunar Rover Agile Mission Systems

Agile development methods, which have gone from outlier to mainstream in software development, are poised to expand into all aspects of space mission development. Modern software development operates on a principle of continuous deployment, where progress is verified not with conventional metrics, but with a continuous build, available to key stakeholders, enabling direct examination of the state of the code base, and assessment of progress through demonstration of capability. Delivery times are measured in weeks, not months. Stakeholders are part of the process on an ongoing basis. The cost of change is comparatively low and requirements, which often are not precisely defined at the start of a project, may be iteratively refined in a series of agile development cycles. Agile methods are compatible with traditional system engineering methods and may be tailored to the space operations environment. The low cost of change and iterative development cycles of agile enable requirements to be defined as outcomes and constraints, with design details to be refined during the development cycle. We are now at a point where agile methods may be extended beyond software, to Mission Systems, including the Mission Operations System and the Ground Data System. For NASA’s VIPER Lunar Rover Mission, scheduled to land at a lunar pole in late 2023, we are developing the Mission System using agile methods. As in agile software, where the measure of progress is working code, in agile mission system development, the measure of capability is what we can demonstrate. Demonstrations over presentations. We demonstrate mission system capability using simulations. The concept of operations, from commanding, to driving the rover, to how we downlink images for evaluation for a near-real time command cycle, will be tested and proven in simulation, years before we begin the traditional simulation cycle for training. “Say it then simulate it.” We develop and refine our designs using simulations, with an emphasis on new components of the system that are not well known early. For example, the required duration of a mission planning cycle for a lunar surface asset such as VIPER, that operates twenty-four hours a day, seven days a week, with continuous communications and a unique set of constraints based on the physics of the lunar poles and the line of site to Earth, is a unique problem in mission planning that is unlikely to be solved in a series of meetings. A small number of requirements specifying the outcomes may serve as the jumping off point to an agile development cycle, with demonstration in simulations. We have already demonstrated this process with simulations of rover driver decision time. VIPER is driven using near-real time command and control to waypoints. The driver decision time between waypoints is a fundamental enabling unit of productivity to accomplish the mission timeline. We have validated driver decision time in simulations of rover driving at the lunar South Pole, using the prototype mission tools for driving, command and control. The capability to develop and refine designs using simulations as part of agile Mission System development cycle changes the nature of team interactions, creating a focus on doing, rather than analyzing and documenting. Waterfall development cycles were, in part, a product of the significant cost of change in the early days of spaceflight. When the cost of change is high, it is vital to get your requirements right at the outset, because the system will be built to those specifications, and, when change is expensive, you better get it right early. However, modern technology has greatly lowered the cost of change, enabling iterative, rapid development cycles, in which key operations concepts may be tested and refined during development. Extending agile development to the Mission System for VIPER is a significant step in moving agile development methods for space operations beyond software, to the Mission System.

Agile↗

NASA NTRS1975

Remote Sensing Application to Land Use Classification in a Rapidly Changing Agricultural/Urban Area: City of Virginia Beach, Virginia

Remote sensing data on computer-compatible tapes of LANDSAT 1 multispectral scanner imager were analyzed to generate a land use map of the City of Virginia Beach. All four bands were used in both the supervised and unsupervised approaches with the LAYSYS software system. Color IR imagery of a U-2 flight of the same area was also digitized and two sample areas were analyzed via the unsupervised approach. The relationships between the mapped land use and the soils of the area were investigated. A land use land cover map at a scale of 1:24,000 was obtained from the supervised analysis of LANDSAT 1 data. It was concluded that machine analysis of remote sensing data to produce land use maps was feasible; that the LAYSYS software system was usable for this purpose; and that the machine analysis was capable of extracting detailed information from the relatively small scale LANDSAT data in a much shorter time without compromising accuracy.

Odenyo, V. A. O.↗

NASA NTRS1983

The Galileo spacecraft system design

The Galileo Orbiter differs markedly from its Mariner, Viking and Voyager predecessors in many aspects of its design, as dictated by its unique mission characteristics. Novel design features include a dual spin configuration, long life bipropellant propulsion, radioisotope thermoelectric generators, and a star scanner. Other major changes are related to Space Shuttle Orbiter compatibility. The selection of a distributed data system employing a high speed data bus represents a major advance over Voyager systems. The command, control and data handling functions for the Orbiter are merged into a single software-controlled subsystem. The paramount importance of software development in the design of Galileo subsystems is noted, in view of the requirement for total engineering and science data acquisition process reprogrammability.

Jones, C. P.↗

NASA NTRS1993

Automated Estimation Of Software-Development Costs

COSTMODL is automated software development-estimation tool. Yields significant reduction in risk of cost overruns and failed projects. Accepts description of software product developed and computes estimates of effort required to produce it, calendar schedule required, and distribution of effort and staffing as function of defined set of development life-cycle phases. Written for IBM PC(R)-compatible computers.

Roush, George B.↗

NASA NTRS2023

Harnessing the Digital Transformation for Development of Electrified Aircraft Propulsion Control Systems

Hybrid electric aircraft propulsion is an emerging technology that presents a variety of potential benefits along with technical integration challenges. Developing these new propulsion architectures with their complex control systems, and ultimately proving their benefit, is a multistep process. This process includes concept development and analysis, dynamic simulation, hardware-in-the-loop testing, full-scale testing, and so on. This effort is being revolutionized and indeed enabled by new digital tools that support increasing the technology readiness level throughout the maturation process. As part of this Digital Transformation, NASA has developed a suite of publicly available digital tools that facilitate the path from concept to implementation. This paper describes the NASA-developed tools and puts them in the context of control system development for hybrid electric aircraft propulsion. The three MATLAB®-based software packages are the Toolbox for the Modeling and Analysis of Thermodynamic Systems (T-MATS), the Electrical Modeling and Thermal Analysis Toolbox (EMTAT), and the Thermal Systems Analysis Toolbox (TSAT). These tools are interactive, complementary, and compatible with each other. T-MATS is a modular thermodynamic modeling framework designed for creating custom component level models of jet engines. EMTAT is a modeling framework used to simulate a variety of power electronic devices, using both physics-based and power flow calculations. TSAT is a framework for modeling and analysis of dynamic heat transfer. These packages all consist of graphical, drag-and-drop, parameterizable building blocks representing various components of the system to be modeled, e.g., compressors, turbines, motors, energy storage devices, etc. They are designed to enable the user to model and simulate the end-to-end dynamic operation of a hybrid electric gas turbine engine powertrain at the timescale of the turbomachinery, capturing mechanical, electrical, and thermal interactions. This paper demonstrates through multiple examples how these tools have been used successfully in a variety of applications, including several of the early stages of hybrid electric gas turbine engine propulsion system development, from the initial system modeling to real-time interactive pilot-in-the-loop simulation to physical hardware-in-the-loop testing, each step bringing the technology closer to fruition.

hybrid electric propulsion↗

NASA NTRS2005

Modular Software Interfaces for Revolutionary Flexibility in Space Operations

To make revolutionary improvements in exploration, space systems need to be flexible, realtime reconfigurable, and able to trade data transparently among themselves and mission operations. Onboard operations systems, space assembly coordination and EVA systems in exploration and construction all require real-time modular reconfigurability and data sharing. But NASA's current exploration systems are still largely legacies from hastily-developed, one-off Apollo-era practices. Today's rovers, vehicles, spacesuits, space stations, and instruments are not able to plug-and-play, Lego-like: into different combinations. Point-to-point dominates - individual suit to individual vehicle, individual instrument to rover. All are locally optimized, all unique, each of the data interfaces has been recoded for each possible combination. This will be an operations and maintenance nightmare in the much larger Project Constellation system of systems. This legacy approach does not scale to the hundreds of networked space components needed for space construction and for new, space-based approaches to Earth-Moon operations. By comparison, battlefield information management systems, which are considered critical to military force projection, have long since abandoned a point-to-point approach to systems integration. From a system-of-systems viewpoint, a clean-sheet redesign of the interfaces of all exploration systems is a necessary prerequisite before designing the interfaces of the individual exploration systems. Existing communications and Global Information Grid and middleware technologies are probably sufficient for command and control and information interfaces, with some hardware and time-delay modifications for space environments. NASA's future advanced space operations must also be information and data compatible with aerospace operations and surveillance systems being developed by other US Government agencies such as the Department of Homeland Security, Federal Aviation Administration and Department of Defense. This paper discusses fundamental system-of-systems infrastructure: approaches and architectures for modular plug-and-play software interfaces for revolutionary improvements in flexibility, modularity, robustness, ease of maintenance, reconfigurability, safety and productivity. Starting with middleware, databases, and mobile communications technologies, our technical challenges will be to apply these ideas to the requirements of constellations of space systems and to implement them initially on prototype space hardware. This is necessary to demonstrate an integrated information sharing architecture and services. It is a bottom-up approach, one that solves the problem of space operations data integration. Exploration demands uniform software mechanisms for application information interchange, and the corresponding uniformly available software services to enhance these mechanisms. We will examine the issues in plug-and-play, real-time-configurable systems, including common definition and management and tracking of data and information among many different space systems. Different field test approaches are discussed, including the use of the International Space Station and terrestrial analog mission operations at field sites.

Glass, Brian↗

NASA NTRS1988

Dynamic Replanning System

Artificial-intelligence computer program for planning automatically changes plan when conditions warrant. System uses planning software called SWITCH. Contains replanning input generator. Replanning done only for situations in which SWITCH has made plan but goals have changed. System assumes original knowledge base correct, which often is not the case. Future development aimed at compatibility with changing knowledge bases.

Porta, Harry J.↗

NASA NTRSDate not supplied

Thermodynamic and Diffusion Model Estimates on Metamorphic Temperatures and Timescales for Basaltic Eucrite GRA 98098

Introduction: HED meteorites are thought to rep-resent igneous rocks from Vesta’s basaltic crust and preserve evidence of early crustal metamorphism. Determining the temperatures and timescales of thermal metamorphism is important for reconstructing crustal evolution in the early solar system. Here, we study basaltic eucrite Graves Nunataks (GRA) 98098, which has been identified as a highly metamorphosed eucrite [1]. We present new estimates on metamorphic temperatures determined via thermodynamic modeling as well as the initial results from diffusion models constraining timescales of thermal metamorphism. Sample Description: GRA 98098 is an unbrecciated eucrite with a granoblastic plagioclase and pyroxene mineralogy. Millimeter to cm-long lathes of tridymite cross-cut and poikilitically enclose plagioclase and pyroxene [1,this work]. Pyroxene grains have exsolved into Ca-rich (~Wo38En29Fs33) and Ca-poor (~Wo4.5En36Fs59.5) lamellae. Both unzoned and zoned plagioclase grains are observed. Unzoned plagioclase grains are found solely with tridymite laths. These grains have ~An92 compositions. The cores of the zoned plagioclase grains have the same composition and thin, relatively sodic rims (~An67), (Fig. 1). The bulk sample is unusually enriched in highly in-compatible elements and has one of the most fractionated REE patterns reported [1]. Maximum metamorphic temperatures of 985±78°C have been estimated using two-pyroxene thermometry [2]. Methods: Thermodynamic modeling. Thermodynamic models were constructed using the software Perple_X, which employs a Gibbs free energy minimization in order to determine the most stable phase assemblage for a given bulk rock composition [3]. Bulk composition was calculated using mineral com-positions acquired via EMPA (this study) and the observed abundancies present in the thin section. Two bulk compositions were estimated; 1) includes all phases present in the thin section, (assumes that all phases are present during metamorphism), 2) excludes tridymite from the bulk calculation (assumes that tridymite was not present during metamorphism). In order to determine whether metamorphic equilibria was achieved and estimate temperatures of metamorphism, we compared measured pyroxene compositions with thermodynamically predicted compositions [4, Fig. 2]. Diffusion Modeling. Several time-temperature de-pendent diffusion profiles were calculated in order to determine the best match for XAn chemical profiles observed at the edges of the zoned plagioclase (Fig. 3). We assumed that the start condition was a stepwise gradient at the plagioclase/pyroxene interface. We also assumed an average diffusion coefficient (D) and a constant temperature using the equation in [5]. D was determined for two temperatures (T = 1060ºC; near eucrite solidus [6] and T = 985ºC; metamorphism reported in [4]) and then XAn was calculated as a function of distance from plagioclase core to rim using an error function solution to Fick’s second law. Results: Thermodynamic model results are summarized in Fig. 2. For a bulk composition that includes all phases in the thin section, pyroxene endmember compositions plot in the following temperature ranges: Fs ~660-860ºC, En~1000ºC & 1150ºC, and Wo~760-900ºC (Fig. 2a). For a bulk composition that excludes tridymite from the peak metamorphic assemblage (i.e., the bulk composition minus the contribution from tridymite), a temperature range could not be determined for the Fs component of pyroxene. For Wo, T~760-900ºC and En, T~1000ºC & 1150ºC (Fig. 2b). Fig. 3 summarizes the diffusion model results. For T = 1060°C & 985°C, the most appropriate time interval was estimated based on which diffusion curve most matched (solid lines, Fig. 3) the EMPA data. For T = 1060°C, the best looking match was t = 500 ka. For T = 985°C, the best match was t = 7 Ma. Discussion and future work: Temperature estimates from thermodynamic models are not conclusive because the temperature ranges determined for pyroxene endmember stability do not overlap (colored fields in Fig. 2), thus implying that there is disequilibrium between pyroxene crystals and the bulk composition considered [4]. Thus, additional exploration is needed to define a metamorphically equilibrated do-main that accurately records peak temperature. The utility of defining metamorphically equilibrated do-mains to improve the accuracy and level of detail elucidated regarding the petrogenetic history of metamorphose samples has been demonstrated previously [4,7]. We suggest that in the case of Fig. 2a, the thin section composition is not representative of the length scales over which metamorphic equilibrium was achieve and in the case of Fig. 2b, the assumption that tridymite was not present during metamorphism was incorrect. However, results from thermodynamic models can provide insight into the relative timing of mineral and compositional textures. For example from texture alone, it is unclear whether tridymite was igneous in origin and represents the last bits of melt in a crystallizing magma chamber, or if it formed during (and possibly initiated) open system thermal metamorphism. The latter could be consistent with a partial melt hypothesis [8,9] while the former implies that simple fractional crystallization can yield the textures present in GRA 98098. The lack of coincidence be-tween pyroxene endmember compositions in Fig. 2b suggest that the bulk composition minus tridymite was not the assemblage in equilibrium with the pyroxene, suggesting that tridymite was present during metamorphism and formed during igneous crystallization. We conclude that the development of the Na-rich plagioclase rims likely occurred during or immediately after peak thermal metamorphism, because eucrites of similar metamorphic grade and texture have unzoned plagioclase (~An92) [2,4,8], and Na zoning is only observed in the plagioclase not included in the tridymite. This suggests that the zoning formed after tridymite formation, and therefore after igneous crystallization. Thus, the timescales calculated via diffusion modeling possibly represent the time interval over which thermal metamorphism occurred. Cooling rates approximated for the Vestan crust predict that the crust cooled below 300°C around 35-40 Ma after formation[10]. This is consistent with our modeling results that predict formation of the Na rich plagioclase rims occurring at higher temperatures over a period of 0.5 to 7 Ma years. Future work. Additional thermodynamic modeling work will focus on selecting an equilibrated bulk rock domain in which to elucidate metamorphic conditions. Diffusion models currently provide a minimum time-scale, since diffusion slows down as the system cools. Future work with will focus on integrating cooling into the diffusion models and constraining the depth at which thermal metamorphism occurs because it could be used to determine whether the range of time-scales calculated for thermal metamorphism are consistent with the geologic environment.

J S Gorce↗

NASA NTRS1977

A regional land use survey based on remote sensing and other data: A report on a LANDSAT and computer mapping project, volume 2

The author has identified the following significant results. The project mapped land use/cover classifications from LANDSAT computer compatible tape data and combined those results with other multisource data via computer mapping/compositing techniques to analyze various land use planning/natural resource management problems. Data were analyzed on 1:24,000 scale maps at 1.1 acre resolution. LANDSAT analysis software and linkages with other computer mapping software were developed. Significant results were also achieved in training, communication, and identification of needs for developing the LANDSAT/computer mapping technologies into operational tools for use by decision makers.

Nez, G.↗

NASA NTRS1989

Fortran Program for X-Ray Photoelectron Spectroscopy Data Reformatting

A FORTRAN program has been written for use on an IBM PC/XT or AT or compatible microcomputer (personal computer, PC) that converts a column of ASCII-format numbers into a binary-format file suitable for interactive analysis on a Digital Equipment Corporation (DEC) computer running the VGS-5000 Enhanced Data Processing (EDP) software package. The incompatible floating-point number representations of the two computers were compared, and a subroutine was created to correctly store floating-point numbers on the IBM PC, which can be directly read by the DEC computer. Any file transfer protocol having provision for binary data can be used to transmit the resulting file from the PC to the DEC machine. The data file header required by the EDP programs for an x ray photoelectron spectrum is also written to the file. The user is prompted for the relevant experimental parameters, which are then properly coded into the format used internally by all of the VGS-5000 series EDP packages.

Abel, Phillip B.↗

NASA NTRS2016

Compatibility Assessment Tool

In support of ground system development for the Space Launch System (SLS), engineers are tasked with building immense engineering models of extreme complexity. The various systems require rigorous analysis of pneumatics, hydraulic, cryogenic, and hypergolic systems. There are certain standards that each of these systems must meet, in the form of pressure vessel system (PVS) certification reports. These reports can be hundreds of pages long, and require many hours to compile. Traditionally, each component is analyzed individually, often utilizing hand calculations in the design process. The objective of this opportunity is to perform these analyses in an integrated fashion with the parametric CADCAE environment. This allows for systems to be analyzed on an assembly level in a semi-automated fashion, which greatly improves accuracy and efficiency. To accomplish this, component specific parameters were stored in the Windchill database to individual Creo Parametric models based on spec control drawings. These parameters were then accessed by using the Prime Analysis within Creo Parametric. MathCAD Prime spreadsheets were created that automatically extracted these parameters, performed calculations, and generated reports. The reports described component compatibility based on local conditions such as pressure, temperature, density, and flow rates. The reports also determined component pairing compatibility, such as properly sizing relief valves with regulators. The reports stored the input conditions that were used to determine compatibility to increase traceability of component selection. The desired workflow for using this tool would begin with a Creo Schematics diagram of a PVS system. This schematic would store local conditions and locations of components. The schematic would then populate an assembly within Creo Parametric, using Windchill database parts. These parts would have their attributes already assigned, and the MathCAD spreadsheets could begin running through database parts to determine which components would be suited for specific locations within the assembly. This eliminates a significant amount of time from the design process, and makes initial analysis assessments more accurate. Each component that would be checked for a location within the assembly would generate a report, showing whether the component was compatible. These reports could be used to generate the PVS report without the need to perform the same analysis multiple times. This process also has the potential to be expanded upon to further automate PVS reports. The integration of software codes or macros could be used to automatically check through hundreds of parts for each location on the schematic. If the software could recognize which type of component would be necessary for each location, it is possible that simply starting the macro could completely choose all the components needed for the schematic, and in turn the system. This would save many hours of work initially selecting components, which could end up saving money. Overall, this process helps to automate initial component selections for PVS systems to fit local design specifications. These selections will automatically generate reports showing how the design criteria are met by the specific component that was chosen. These reports will contribute to easier compilation of the PVS certification reports, which currently take a great amount of time and effort to produce.

Egbert, James Allen↗

NASA NTRS2022

Lunar Communications Services with Emphasis on Commercialization

In mid-2020 Lockheed Marin Space (LM) and NASA’s Jet Propulsion Laboratory (JPL) formed a working group to study and address the need for a lunar communications network to service a growing lunar economy, beginning with the initial crewed and robotic mission needs in 2024. Multiple commercial relay architectures were studied and evaluated for platform requirements, communications capabilities, and commercial business viability in a growing ecosystem. The evolution of communications needs around the Moon were mapped to infrastructure build out. Trade studies were performed to evaluate reliability and lifetime requirements, and the viability of various data protocols. Mission concepts and operations plans were developed for both initial mission support and future autonomous network support. This work has led to Lockheed Martin and JPL to evaluate a single dedicated relay satellite in a frozen lunar orbit, with simultaneous coverage of the far-side and south pole landing sites for over 10 hours per day as a first step towards a comprehensive solution to lunar connectivity. This first satellite is compatible with an ESPA Grande launch volume and would be capable of launching on a rideshare into a variety of orbits and trajectories. The satellite is equipped with both high- and low-rate communications relay payloads with software-defined radios and a delay/disruption tolerant networking protocol. The system is designed to service initial and future mission needs in a commercialized manner, enabling a new class of missions to the Moon. The relay satellite leverages prior spacecraft platform work with on-orbit heritage in a lunar environment expected by 2023.

Davarian, Faramaz↗

NASA NTRS2023

Development of Two High-Energy Bus ‘Cores’ for Rapid Support of Low-TRL and Educational Payloads: A Software-Configured EPS Combined with Flexible C&DH

For several years the TechEdSat flight series (TES-n), developed by the Nano Orbital Workshop (NOW) group at NASA Ames, has relied upon an in-house developed unit to serve both EPS (Electrical Power System) and C&DH (Command and Data Handling) roles along with low data-rate telemetry functions, i.e., serving as the ‘core’ of the spacecraft bus. This ‘core’ has a considerable task given the rapid cadence of the TES program and the typically low-TRL of payloads; configurability and compatibility are key to prevent mission-specific hardware. However, at only 15 watts the current core has become insufficient to support the program’s growing missions and increasingly demanding payloads. To this end, the NOW program is developing new cores to support two TES mission classes: a single-PCB ‘MiniCore’ designed to support 80-watt missions 6U or smaller in LEO, and a three-PCB, radiation-tolerant ‘StackCore’ designed to support 6U and larger missions over 500 watts in LEO and beyond. The ‘MiniCore’ design consists of three main segments: a processor-agnostic C&DH, a software-configured EPS, and a backup low data-rate radio. The design philosophy was to enable rapid-manufacture in a turbulent supply chain, hence the design consists of COTS parts with a focus on those able to be drop-in replaced with radiation-tolerant versions when demanded by the mission. As a single PC-104 sized circuit board, power density and ease of integration also dominated design, demanding the use of modern features such as single-point USB-C for easy charging and monitoring of the spacecraft on the ground. The ‘MiniCore’ can support 80 watts of load, 140 watt-hours of storage, and over 20 watts of optimized solar generation with extensive power monitoring throughout. The ‘MiniCore’ supports one battery pack, six solar-panels, six loads, five actuators, Iridium SBD, and an internal 802.15.4 network. Additionally, the processor-agnostic design can accept any PJRC Teensy 3.x or Adafruit Feather microcontroller unit to enable processor scaling with mission requirements or environment. It is expected a development unit of this design will be completed before conference. The ‘StackCore’ design consists of three stacked PC-104 sized circuit boards: one dedicated to power generation and storage, one dedicated to power distribution, and one dedicated to C&DH tasks. This delineation is necessary to support the transition from highly integrated ICs to discrete analog circuitry, enabling a primarily analog control power system able to operate without software in a radiation environment with finer monitoring compared to the ‘MiniCore’ design. The planned base architecture supports over 500 watts of load, 250 watt-hours of storage, and over 80 watts of optimized solar generation. The power distribution board allows for the use of daughter cards hosting custom converters or interfaces for payloads, in addition to the software-configured supplies used on the ‘MiniCore’. This core stack will be managed by a Vorago ARM M4 microcontroller and support the same wireless communications as the ‘MiniCore’, with optional integration of a NOW S-band radio and attitude determination sensors for ‘black box’ functionality. It is expected the prototype will still be in development during conference.

Spacecraft↗

NASA NTRSDate not supplied

Development of Two High-Energy Bus ‘Cores’ for Rapid Support of Low-TRL and Educational Payloads: A Software-Configured EPS Combined with Flexible C&DH

Spacecraft↗