Search NASA⌕ Search

SEARCH · Search NASA

Results for “Onboard Flight Software”

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.

At least 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Benefits of using Electronic Data Sheets (EDS) with coreFlight Systems (cFS) - A Project Example

Recently there has been interest in the incorporation of core Flight Systems (cFS) with Spacecraft Onboard Interface Services (SOIS) Electronic Data Sheets (EDS) in the spaceflight software community. The Regenerative Fuel Cell project at the Glenn Research Center is using cFS architecture with EDS support for its monitoring and control software. The presentation will outline the benefits to using cFS with EDS support: First, EDS establishes a single source of truth for the definitions of data structures used throughout an entire mission that may otherwise be programmed in different languages and designed with different processor architectures. Not only does this help with inter-application communication via the software bus, but it also greatly simplifies communication between systems. An EDS Application Programming Interface (API) library allows the conversion of EDS data structures to and from native data structures. Second, bindings for other programming languages (e.g. Lua, Python, JSON) have been written to allow the creation and manipulation of EDS data objects within those languages. The RFC project uses Lua scripts to automatically generate binary configuration files at build time to be loaded into our cFS programs. We also use Python bindings in a graphical user interface (GUI) to allow an operator to send commands and view telemetry messages sent from cFS instances. Finally, using Lua scripts we can set up specific simulation scenarios to perform automatic functional testing. During the development of the RFC software, the software team put together a generic python GUI called “cFS-EDS-GroundStation” that provides a basic interface to an instance of cFS with EDS support. The GUI includes a basic telecommand and telemetry system that reads directly from the generated EDS databases. In the telecommand system, dropdown menus are populated with all user commands that are defined in EDS. In the telemetry system, telemetry messages are automatically decoded, written to the screen, and saved to a binary file. Additional Python scripts have been written to convert the binary data files into a comma separated value (CSV) format for further processing. We will demonstrate the basic use of the cFS-EDS-GroundStation software including adding additional commands and telemetry payload values in EDS and see them appear automatically in the cFS-EDS-Groundstation software. About the RFC project: The Regenerative Fuel Cell project is tasked with developing and demonstrating a power system consisting of a fuel cell and electrolyzer to provide power during a lunar day/night cycle. During the night, the fuel cell takes Hydrogen and Oxygen gasses and converts them into electricity, water, and heat. During the day, the electrolyzer takes input power (e.g. from a photovoltaic array) and converts water back into Hydrogen and Oxygen gasses.

Mathew Mccaskey↗
NASA NTRSDate not supplied

Impacts of A Scripting Engine in A CFS-Based Flight Software (FSW) Architecture

This presentation delivers a high-level overview of the Capture Containment Return System (CCRS) flight software (FSW) design and a discussion of the advantages and challenges presented by introducing an onboard scripting engine. The CCRS FSW was responsible for controlling a large number of unique mechanisms. The FSW was originally designed based on the traditional cFS paradigm in which a custom cFS application is developed for each unique type of mechanism. The introduction of a feature-rich onboard scripting engine significantly streamlined the FSW design and led to the removal of seven custom cFS applications. The scripting-based architecture was also more robust to requirements volatility within the CCRS system as a whole.

cFS↗
NASA NTRS2015

Telescience Resource Kit (TReK)

Telescience Resource Kit (TReK) is one of the Huntsville Operations Support Center (HOSC) remote operations solutions. It can be used to monitor and control International Space Station (ISS) payloads from anywhere in the world. It is comprised of a suite of software applications and libraries that provide generic data system capabilities and access to HOSC services. The TReK Software has been operational since 2000. A new cross-platform version of TReK is under development. The new software is being released in phases during the 2014-2016 timeframe. The TReK Release 3.x series of software is the original TReK software that has been operational since 2000. This software runs on Windows. It contains capabilities to support traditional telemetry and commanding using CCSDS (Consultative Committee for Space Data Systems) packets. The TReK Release 4.x series of software is the new cross platform software. It runs on Windows and Linux. The new TReK software will support communication using standard IP protocols and traditional telemetry and commanding. All the software listed above is compatible and can be installed and run together on Windows. The new TReK software contains a suite of software that can be used by payload developers on the ground and onboard (TReK Toolkit). TReK Toolkit is a suite of lightweight libraries and utility applications for use onboard and on the ground. TReK Desktop is the full suite of TReK software -most useful on the ground. When TReK Desktop is released, the TReK installation program will provide the option to choose just the TReK Toolkit portion of the software or the full TReK Desktop suite. The ISS program is providing the TReK Toolkit software as a generic flight software capability offered as a standard service to payloads. TReK Software Verification was conducted during the April/May 2015 timeframe. Payload teams using the TReK software onboard can reference the TReK software verification. TReK will be demonstrated on-orbit running on an ISS provided T61p laptop. Target Timeframe: September 2015 -2016. The on-orbit demonstration will collect benchmark metrics, and will be used in the future to provide live demonstrations during ISS Payload Conferences. Benchmark metrics and demonstrations will address the protocols described in SSP 52050-0047 Ku Forward section 3.3.7. (Associated term: CCSDS File Delivery Protocol (CFDP)).

Lippincott, Jeff↗
NASA NTRS1999

Spacecraft Software Maintenance: An Effective Approach to Reducing Costs and Increasing Science Return

Flight software is a mission critical element of spacecraft functionality and performance. When ground operations personnel interface to a spacecraft, they are typically dealing almost entirely with the capabilities of onboard software. This software, even more than critical ground/flight communications systems, is expected to perform perfectly during all phases of spacecraft life. Due to the fact that it can be reprogrammed on-orbit to accommodate degradations or failures in flight hardware, new insights into spacecraft characteristics, new control options which permit enhanced science options, etc., the on- orbit flight software maintenance team is usually significantly responsible for the long term success of a science mission. Failure of flight software to perform as needed can result in very expensive operations work-around costs and lost science opportunities. There are three basic approaches to maintaining spacecraft software--namely using the original developers, using the mission operations personnel, or assembling a center of excellence for multi-spacecraft software maintenance. Not planning properly for flight software maintenance can lead to unnecessarily high on-orbit costs and/or unacceptably long delays, or errors, in patch installations. A common approach for flight software maintenance is to access the original development staff. The argument for utilizing the development staff is that the people who developed the software will be the best people to modify the software on-orbit. However, it can quickly becomes a challenge to obtain the services of these key people. They may no longer be available to the organization. They may have a more urgent job to perform, quite likely on another project under different project management. If they havn't worked on the software for a long time, they may need precious time for refamiliarization to the software, testbeds and tools. Further, a lack of insight into issues related to flight software in its on-orbit environment, may find the developer unprepared for the challenges. The second approach is to train a member of the flight operations team to maintain the spacecraft software. This can prove to be a costly and inflexible solution. The person assigned to this duty may not have enough work to do during a problem free period and may have too much to do when a problem arises. If the person is a talented software engineer, he/she may not enjoy the limited software opportunities available in this position; and may eventually leave for newer technology computer science opportunities. Training replacement flight software personnel can be a difficult and lengthy process. The third approach is to assemble a center of excellence for on-orbit spacecraft software maintenance. Personnel in this specialty center can be managed to support flight software of multiple missions at once. The variety of challenges among a set of on-orbit missions, can result in a dedicated, talented staff which is fully trained and available to support each mission's needs. Such staff are not software developers but are rather spacecraft software systems engineers. The cost to any one mission is extremely low because the software staff works and charges, minimally on missions with no current operations issues; and their professional insight into on-orbit software troubleshooting and maintenance methods ensures low risk, effective and minimal-cost solutions to on-orbit issues.

Shell, Elaine M.↗
NASA NTRSDate not supplied

Autonomous Navigation, Guidance, and Control Software in a Low SWaP Box

Onboard autonomy is a necessity for responsive space operations. Autonomous navigation, guidance, and control (NGC) enables space missions to reduce their dependence on high demand ground assets and costly ground personnel. It also allows for in-situ decision making and higher return on mission data. A flight software and hardware system providing this capability, called “autoNGC,” is currently being developed at NASA Goddard Space Flight Center for infusion into multiple future missions. The autoNGC flight software is built on the plug-and-play architecture of the core Flight System (cFS) consisting of the standard cFS apps and newly developed autoNGC interface apps and libraries. The various apps cooperate through communication over the message-based software bus. With the plug-and-play architecture of autoNGC, cFS apps can easily be added and replaced to meet the needs of different missions, even after launch. The first flight software release of autoNGC is targeted for Summer 2024 to provide autonomous navigation at the Moon and beyond. It can perform sensor fusion of multiple measurement types including pseudo-range from a Global Navigation Satellite System (GNSS) receiver (including weak signal), 1-way and 2-way range and Doppler from ground stations (i.e., direct to Earth (DTE)), bearing and range from optical camera images, and accelerometer data. Accurate onboard navigation and timing is obtained through the Goddard Enhanced Onboard Navigation System (GEONS) software library which fuses different measurement types through an extended Kalman filter (EKF) framework. Optical measurements that are ingested in GEONS are first extracted from optical images by the cFS Goddard Image Analysis and Navigation Tool (cGIANT) app. If the imaged body is far enough away that it appears as a pixel or cluster of pixels, then bearing angles to the body centroid can be provided. If the body is close enough and the shape is known coarsely, then bearing angles and range to the body centroid can be derived from the limb. Bearing angles to individual surface features can also be extracted (i.e., terrain relative navigation (TRN)). Onboard guidance and control capabilities are being developed for a future release to perform autonomous station-keeping and trajectory correction maneuvers in multiple orbital regimes. Capabilities to enable distributed systems missions and constellations, such as crosslink measurements, and onboard time management are being developed as well. The first hardware implementation of autoNGC is a minimal size, weight, and power (SWaP) design allowing for inclusion into CubeSats and SmallSat-size buses. Advancements in miniaturized space processors, such as the SpaceCube 3.0 Mini and the SpaceCube Mini-Z are utilized for low SWaP while maintaining a high level of performance. The current enclosure design is 12 cm x 17 cm x 13.5 cm. The box mass is expected to be less than 2 kg, and the nominal power is 21 W. In order to accommodate a wide range of missions, the hardware interfaces are designed for flexibility with a variety of sensor inputs. Through comprehensive testing in the software-in-the-loop, processor-in-the-loop, and hardware-in-the-loop test beds that are concurrently being developed, autoNGC is expected to achieve TRL 6 by late 2024.

Sun Hur-Diaz↗
NASA NTRS2014

Use of Semi-Autonomous Tools for ISS Commanding and Monitoring

As the International Space Station (ISS) has moved into a utilization phase, operations have shifted to become more ground-based with fewer mission control personnel monitoring and commanding multiple ISS systems. This shift to fewer people monitoring more systems has prompted use of semi-autonomous console tools in the ISS Mission Control Center (MCC) to help flight controllers command and monitor the ISS. These console tools perform routine operational procedures while keeping the human operator "in the loop" to monitor and intervene when off-nominal events arise. Two such tools, the Pre-positioned Load (PPL) Loader and Automatic Operators Recorder Manager (AutoORM), are used by the ISS Communications RF Onboard Networks Utilization Specialist (CRONUS) flight control position. CRONUS is responsible for simultaneously commanding and monitoring the ISS Command & Data Handling (C&DH) and Communications and Tracking (C&T) systems. PPL Loader is used to uplink small pieces of frequently changed software data tables, called PPLs, to ISS computers to support different ISS operations. In order to uplink a PPL, a data load command must be built that contains multiple user-input fields. Next, a multiple step commanding and verification procedure must be performed to enable an onboard computer for software uplink, uplink the PPL, verify the PPL has incorporated correctly, and disable the computer for software uplink. PPL Loader provides different levels of automation in both building and uplinking these commands. In its manual mode, PPL Loader automatically builds the PPL data load commands but allows the flight controller to verify and save the commands for future uplink. In its auto mode, PPL Loader automatically builds the PPL data load commands for flight controller verification, but automatically performs the PPL uplink procedure by sending commands and performing verification checks while notifying CRONUS of procedure step completion. If an off-nominal condition occurs during procedure execution, PPL Loader notifies CRONUS through popup messages, allowing CRONUS to examine the situation and choose an option of how PPL loader should proceed with the procedure. The use of PPL Loader to perform frequent, routine PPL uplinks offloads CRONUS to better monitor two ISS systems. It also reduces procedure performance time and decreases risk of command errors. AutoORM identifies ISS communication outage periods and builds commands to lock, playback, and unlock ISS Operations Recorder files. Operation Recorder files are circular buffer files of continually recorded ISS telemetry data. Sections of these files can be locked from further writing, be played back to capture telemetry data that occurred during an ISS loss of signal (LOS) period, and then be unlocked for future recording use. Downlinked Operation Recorder files are used by mission support teams for data analysis, especially if failures occur during LOS. The commands to lock, playback, and unlock Operations Recorder files are encompassed in three different operational procedures and contain multiple user-input fields. AutoORM provides different levels of automation for building and uplinking the commands to lock, playback, and unlock Operations Recorder files. In its automatic mode, AutoORM automatically detects ISS LOS periods, then generates and uplinks the commands to lock, playback, and unlock Operations Recorder files when MCC regains signal with ISS. AutoORM also features semi-autonomous and manual modes which integrate CRONUS more into the command verification and uplink process. AutoORMs ability to automatically detect ISS LOS periods and build the necessary commands to preserve, playback, and release recorded telemetry data greatly offloads CRONUS to perform more high-level cognitive tasks, such as mission planning and anomaly troubleshooting. Additionally, since Operations Recorder commands contain numerical time input fields which are tedious for a human to manually build, AutoORM's ability to automatically build commands reduces operational command errors. PPL Loader and AutoORM demonstrate principles of semi-autonomous operational tools that will benefit future space mission operations. Both tools employ different levels of automation to perform simple and routine procedures, thereby offloading human operators to perform higher-level cognitive tasks. Because both tools provide procedure execution status and highlight off-nominal indications, the flight controller is able to intervene during procedure execution if needed. Semi-autonomous tools and systems that can perform routine procedures, yet keep human operators informed of execution, will be essential in future long-duration missions where the onboard crew will be solely responsible for spacecraft monitoring and control.

Brzezinski, Amy S.↗
NASA NTRS2012

Orion Absolute Navigation System Progress and Challenge

The absolute navigation design of NASA's Orion vehicle is described. It has undergone several iterations and modifications since its inception, and continues as a work-in-progress. This paper seeks to benchmark the current state of the design and some of the rationale and analysis behind it. There are specific challenges to address when preparing a timely and effective design for the Exploration Flight Test (EFT-1), while still looking ahead and providing software extensibility for future exploration missions. The primary onboard measurements in a Near-Earth or Mid-Earth environment consist of GPS pseudo-range and delta-range, but for future explorations missions the use of star-tracker and optical navigation sources need to be considered. Discussions are presented for state size and composition, processing techniques, and consider states. A presentation is given for the processing technique using the computationally stable and robust UDU formulation with an Agee-Turner Rank-One update. This allows for computational savings when dealing with many parameters which are modeled as slowly varying Gauss-Markov processes. Preliminary analysis shows up to a 50% reduction in computation versus a more traditional formulation. Several state elements are discussed and evaluated, including position, velocity, attitude, clock bias/drift, and GPS measurement biases in addition to bias, scale factor, misalignment, and non-orthogonalities of the accelerometers and gyroscopes. Another consideration is the initialization of the EKF in various scenarios. Scenarios such as single-event upset, ground command, and cold start are discussed as are strategies for whole and partial state updates as well as covariance considerations. Strategies are given for dealing with latent measurements and high-rate propagation using multi-rate architecture. The details of the rate groups and the data ow between the elements is discussed and evaluated.

Holt, Greg N.↗
NASA NTRS2016

Global Positioning System Navigation Above 76,000 km for NASA's Magnetospheric Multiscale Mission

NASA's Magnetospheric Multiscale (MMS) mission, launched in March of 2015, consists of a controlled formation of four spin-stabilized spacecraft in similar highly elliptic orbits reaching apogee at radial distances of 12 and 25 Earth radii (RE) in the first and second phases of the mission. Navigation for MMS is achieved independently on-board each spacecraft by processing Global Positioning System (GPS) observables using NASA Goddard Space Flight Center (GSFC)'s Navigator GPS receiver and the Goddard Enhanced Onboard Navigation System (GEONS) extended Kalman filter software. To our knowledge, MMS constitutes, by far, the highest-altitude operational use of GPS to date and represents a high point of over a decade of high-altitude GPS navigation research and development at GSFC. In this paper we will briefly describe past and ongoing high-altitude GPS research efforts at NASA GSFC and elsewhere, provide details on the design of the MMS GPS navigation system, and present on-orbit performance data from the first phase. We extrapolate these results to predict performance in the second phase orbit, and conclude with a discussion of the implications of the MMS results for future high-altitude GPS navigation, which we believe to be broad and far-reaching.

GPS↗
NASA NTRS2017

Global Positioning System Navigation Above 76,000 km for NASA's Magnetospheric Multiscale Mission

NASA's Magnetospheric Multiscale (MMS) mission, launched in March of 2015, consists of a controlled formation of four spin-stabilized spacecraft in similar highly elliptic orbits reaching apogee at radial distances of 12 and 25 Earth radii (RE) in the first and second phases of the mission. Navigation for MMSis achieved independently on-board each spacecraft by processing Global Positioning System (GPS) observables using NASA Goddard Space Flight Center (GSFC)'s Navigator GPS receiver and the Goddard Enhanced Onboard Navigation System (GEONS) extended Kalman filter software. To our knowledge, MMS constitutes, by far, the highest-altitude operational use of GPS to date and represents a high point of over a decade of high-altitude GPS navigation research and development at GSFC. In this paper we will briefly describe past and ongoing high-altitude GPS research efforts at NASA GSFC and elsewhere, provide details on the design of the MMS GPS navigation system, and present on-orbit performance data from the first phase. We extrapolate these results to predict performance in the second phase orbit, and conclude with a discussion of the implications of the MMS results for future high-altitude GPS navigation, which we believe to be broad and far-reaching.

navigation↗
NASA NTRSDate not supplied

Flow Boiling and Condensation Experiment: Flow Boiling in a Rectangular Channel with Subcooled Inlet Conditions in Microgravity

Two-phase thermal management subsystems that take advantage of both the sensible and latent heat of a working fluid can potentially yield significant enhancements in overall performance by adopting heat transfer processes that are based on phase transition like boiling and condensation. Performance of terrestrial two-phase flow systems may be predictable because the hydrodynamic and body forces are understood, however, in microgravity, which is predominant during planetary space travel, forces that are masked by the strong body force on Earth (gravitational or buoyancy force) reappear with different magnitude and influence. The need arose for a facility that provides for two-phase flow with phase transition testing in microgravity. The Flow Boiling and Condensation Experiment (FBCE) is a facility that was launched to the International Space Station in August of 2021 and is in operation since February of 2022. This facility enables investigators to perform two-phase flow and phase transition research in flow boiling and condensation. Along with the test module that is experiment specific, the FBCE system consists of the fluid, avionics, and software subsystems. Currently two test modules, namely, the Flow Boiling Module (FBM) and the Condensation Module for Heat Transfer (CM-HT) are available. A third module, the Transfer Line test Module (TL) is being developed. The fluid subsystem conditions and delivers the fluid at the desired thermodynamic state to the test module. It consists of two fluid modules and a heater module that are connected by flex hoses for fluid circulation and by data and electrical cables for control and data acquisition. Two avionics modules acquire pressure and temperature data from various sensors in the flow loop. For FBM, a high-speed camera is available to acquire images of the boiling process. Experiments are operated autonomously by software and are based on an Experiment Parameters Master Table (EPMT) that is uploaded to ISS and is executed by the FBCE flight software. This presentation briefly introduces the objectives of FBCE and provides a system description of the experiment onboard of the ISS/Fluid Integrated Rack (FIR). Results of the test campaign carried out using the FBM are presented. Specifically, microgravity flow boiling of n-perfluorohexane (test fluid) is discussed with subcooled inlet conditions in a single-side-heated rectangular channel of dimensions 114.6-mm heated length, 2.5-mm heated width, and 5.0-mm height. Key operating parameters investigated are mass velocity (199.90 – 3200.13 kg/m2s), inlet subcooling (0.10 – 45.76°C), and inlet pressure (113.30 – 164.29 kPa). Image sequences acquired via high-speed-video are shown to elucidate the interfacial flow physics. The effects of various parameters on flow boiling heat transfer in microgravity, from the onset of boiling to the critical heat flux are discussed. Heat transfer results are presented in terms of flow boiling curves, streamwise profiles of wall temperature and heat transfer coefficient, and parametric trends of local and averaged heat transfer coefficient, and the critical heat flux.

Two-phase flow and phase transition↗
NASA NTRS1997

Knowledge Acquisition for the Onboard Planner of an Autonomous Spacecraft

This paper discusses the knowledge acquisition issues involved in transitioning their novel technology in to space flight software, developing the planer in the context of a large software projet and completing the work under a compressed development schedule.

Knowledge Aquisition Deep Space↗
NASA NTRS2012

Space Software Defined Radio Characterization to Enable Reuse

NASA's Space Communication and Navigation Testbed is beginning operations on the International Space Station this year. The objective is to promote new software defined radio technologies and associated software application reuse, enabled by this first flight of NASA's Space Telecommunications Radio System architecture standard. The Space Station payload has three software defined radios onboard that allow for a wide variety of communications applications; however, each radio was only launched with one waveform application. By design the testbed allows new waveform applications to be uploaded and tested by experimenters in and outside of NASA. During the system integration phase of the testbed special waveform test modes and stand-alone test waveforms were used to characterize the SDR platforms for the future experiments. Characterization of the Testbed's JPL SDR using test waveforms and specialized ground test modes is discussed in this paper. One of the test waveforms, a record and playback application, can be utilized in a variety of ways, including new satellite on-orbit checkout as well as independent on-board testbed experiments.

Mortensen, Dale J.↗
NASA NTRS2016

Deploying a Route Optimization EFB Application for Commercial Airline Operational Trials

The Traffic Aware Planner (TAP), developed for NASA Langley Research Center to support the Traffic Aware Strategic Aircrew Requests (TASAR) project, is a flight-efficiency software application developed for an Electronic Flight Bag (EFB). Tested in two flight trials and planned for operational testing by two commercial airlines, TAP is a real-time trajectory optimization application that leverages connectivity with onboard avionics and broadband Internet sources to compute and recommend route modifications to flight crews to improve fuel and time performance. The application utilizes a wide range of data, including Automatic Dependent Surveillance Broadcast (ADS-B) traffic, Flight Management System (FMS) guidance and intent, on-board sensors, published winds and weather, and Special Use Airspace (SUA) schedules. This paper discusses the challenges of developing and deploying TAP to various EFB platforms, our solutions to some of these challenges, and lessons learned, to assist commercial software developers and hardware manufacturers in their efforts to implement and extend TAP functionality in their environments. EFB applications (such as TAP) typically access avionics data via an ARINC 834 Simple Text Avionics Protocol (STAP) server hosted by an Aircraft Interface Device (AID) or other installed hardware. While the protocol is standardized, the data sources, content, and transmission rates can vary from aircraft to aircraft. Additionally, the method of communicating with the AID may vary depending on EFB hardware and/or the availability of onboard networking services, such as Ethernet, WIFI, Bluetooth, or other mechanisms. EFBs with portable and installed components can be implemented using a variety of operating systems, and cockpits are increasingly incorporating tablet-based technologies, further expanding the number of platforms the application may need to support. Supporting multiple EFB platforms, AIDs, avionics datasets, and user interfaces presents a challenge for software developers and the management of their code baselines. Maintaining multiple baselines to support all deployment targets can be extremely cumbersome and expensive. Certification also needs to be considered when developing the application. Regardless of whether the software is itself destined to be certified, data requirements in support of the application and user interface elements may introduce certification requirements for EFB manufacturers and the airlines. The example of TAP, the challenges faced, solutions implemented, and lessons learned will give EFB application and hardware developers insight into future potential requirements in deploying TAP or similar flight-deck EFB applications.

Roscoe, David A.↗
NASA NTRS1985

Designing a configuration control mechanism for a flight software validation facility

Embedded computer systems and supporting operating systems have recently enabled the automation of many time-critical flight functions. This automation requires the integration of computer hardware and software, aircraft hardware, and the flight application. To properly integrate and control these critical functions requires a real-time environment that is provided by the onboard flight computer, a real-time operating system, and a real-time flight application that supplies the input commands to the aircraft and responds to the resulting actions. The increased complexity of developing and testing such real-time applications can best be supported by a separate test facility that provides the processing visibility and control which is virtually impossible in the actual real-time operating environment. Such a flight software validation facility has been developed at the NASA Langley Research Center to support applications using the Shuttle real-time language HAL/S. The development and control of this facility are described. Some of the management techniques used were project schedules, status monitoring, code walk-throughs, configuration control, phased releases, validation suites, and modern programming techniques.

Smith-Taylor, R.↗
NASA NTRS2006

Flight-Tested Prototype of BEAM Software

Researchers at JPL have completed a software prototype of BEAM (Beacon-based Exception Analysis for Multi-missions) and successfully tested its operation in flight onboard a NASA research aircraft. BEAM (see NASA Tech Briefs, Vol. 26, No. 9; and Vol. 27, No. 3) is an ISHM (Integrated Systems Health Management) technology that automatically analyzes sensor data and classifies system behavior as either nominal or anomalous, and further characterizes anomalies according to strength, duration, and affected signals. BEAM (see figure) can be used to monitor a wide variety of physical systems and sensor types in real time. In this series of tests, BEAM monitored the engines of a Dryden Flight Research Center F-18 aircraft, and performed onboard, unattended analysis of 26 engine sensors from engine startup to shutdown. The BEAM algorithm can detect anomalies based solely on the sensor data, which includes but is not limited to sensor failure, performance degradation, incorrect operation such as unplanned engine shutdown or flameout in this example, and major system faults. BEAM was tested on an F-18 simulator, static engine tests, and 25 individual flights totaling approximately 60 hours of flight time. During these tests, BEAM successfully identified planned anomalies (in-flight shutdowns of one engine) as well as minor unplanned anomalies (e.g., transient oil- and fuel-pressure drops), with no false alarms or suspected false-negative results for the period tested. BEAM also detected previously unknown behavior in the F- 18 compressor section during several flights. This result, confirmed by direct analysis of the raw data, serves as a significant test of BEAM's capability.

Mackey, Ryan↗
NASA NTRSDate not supplied

Autonomous Navigation of a Lunar Relay Using GNSS and Other Measurements

Many of the highest priority destinations at the Moon lack a continuous view of Earth, such as the lunar poles or lunar far side. Exploration of these sites will require spacecraft in cislunar space to relay communications and provide position, navigation, and timing (PNT) services. Accurate knowledge of relay position, velocity, and time is essential to these services. This paper describes a concept for a PNT Instrument being developed for the Lunar Communications Relay and Navigation Systems (LCRNS) Project. The instrument is intended as a payload that would enable autonomous, on-board, real-time navigation and timing using Global Navigation Satellite System (GNSS), optical navigation, and one-way measurements from Earth-based ground stations. Hardware-in-the-loop simulations using flight software are used to realistically characterize performance on hardware platforms with a path to flight. These results provide preliminary validation of the proposed PNT Instrument, demonstrate the benefits of augmenting GNSS with other measurements, and serve as an insightful reference for the design of future lunar missions, including those that will operate within the LunaNet framework of standards. This instrument concept relies on several technologies developed at NASA Goddard Space Flight Center (GSFC). For GNSS observables, the instrument relies on the high-altitude NavCube 3 mini (NC3m) GNSS receiver specifically designed for cislunar applications. The autoNGC system, which consists of flight software and a hardware platform, is responsible for fusing the observables using its extended Kalman filter, the Goddard Enhanced Onboard Navigation System (GEONS). Optical navigation observables are processed within autoNGC (“autonomous Navigation, Guidance, and Control”) using the Goddard Image Analysis & Navigation Tool (GIANT) which is also responsible for simulating high-fidelity images for test and analysis. In addition to describing the PNT Instrument and its components, the paper will present predicted performance based on simulation results. As a baseline, it will present GNSS-only hardware-in-the loop results using a NC3m test unit to process Spirent-simulated GPS signals in a potential lunar relay trajectory: a 12-hour elliptical frozen lunar orbit (ELFO). GEONS then processes the GPS pseudorange and time differenced carrier phase measurements to estimate and propagate the relay state (position, velocity, and time). These results extend previously published work that showed preliminary ELFO performance. Previous work has shown the importance of other measurement types, so additional simulations are performed which augment GNSS with ground station observables and several methods of optical navigation, including celestial navigation, limb-finding (e.g., observations of the lunar horizon), and terrain relative navigation (TRN). TRN involves correlating simulated predicted images of the lunar surface with actual imagery; misalignments of landmarks identified in each image are translated into relay state updates. TRN is valuable as a measurement of the relay’s state relative to the Moon, especially during GNSS outages or after maneuvers. One-way Pseudorange and Doppler measurements from Earth-based ground stations are also simulated. The full set of observables is processed using autoNGC. These simulations make use of autoNGC and NC3m test units, a lab atomic clock, and a pulse-per-second (PPS) generation and distribution system. This combination of subsystems, and the hardware platforms used in this analysis, represents a PNT Instrument that could be flown on a lunar relay. Results from the hardware-in-the-loop simulations presented in this paper provide a preliminary assessment of the achievable navigation performance of this instrument concept. PNT Instrument performance is compared to the GPS-only performance, and a discussion is provided on the apparent merits and challenges of each measurement type.

Ben Ashman↗
NASA NTRS2023

CFD Modeling of Bi-Directional PMD inside Cryogenic Propellant Tanks Onboard Parabolic Flights

Future cryogenic propulsion systems will require efficient methods with which to transfer cryogenic propellants from a depot storage tank to a customer receiver tank to minimize cost and maximize reusability. The Reduced Gravity Cryogenic Transfer project is currently developing advanced cryogenic fluid management technology and developing and validating new numerical models for three phases of transfer: line chilldown, tank chilldown, and tank fill. Additionally, multiple liquid nitrogen (LN 2 ) parabolic flight transfer rigs are being designed by universities and NASA to investigate the gravitational sensitivities that exist in these three technologies. In order to maximize the collection of low-g data during flights, it is required to extract as much (LN 2 as possible from the supply tank, despite variable gravity levels. The purpose of this paper is to present computational fluid dynamics (CFD) volume of fluid simulations of (LN 2 behavior in the supply tank onboard parabolic flights to validate the optimal design of a bi-directional propellant management device (PMD) using the commercial software FLOW-3D. A parametric study is conducted on the effects of gravity level, fill level, pore size, open area, thickness, and type of baffle on PMD performance. Based on results, the PMD as designed exceeds the targeted expulsion efficiency.

Jason Hartwig↗