Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “flight software testing”

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 901 records · Page 50

Performance Analysis of Terrain Relative Navigation Using Blue Origin New Shepard Suborbital Flight Telemetry

As part of a NASA Tipping Point Partnership with Blue Origin to mature precision lunar landing technologies, two test flights of the Blue Origin New Shepard vehicle carrying a NASA-developed sensor suite were conducted on 10/13/2020 and 08/26/2021 at the West Texas Launch Site (LS-1). Part of the acquired datasets, comprising data from an inertial measurement unit and a downward facing camera, was postprocessed through a JPL-developed prototype Visual Odometry and Map Relative Localization software (TRNVOSIM), and compared against ground truth acquired by the host vehicle navigation system. In this paper, we provide a description of the algorithms, the test setup, and the processed results.

Pedrotty, Samuel M.↗

Actuator and Motor Control End-to-End V&V on the Mars 2020 Rover

The Mars 2020 Perseverance rover is the most advanced robotic exploration system ever sent to another planet. To support the complex scientific and mobility needs of the mission, the rover utilizes 33 actuators, three multi-degree-of-freedom force-torque sensors, fifteen single or dual-speed resolvers, two solenoid valves, and twelve contact switches. The control for these actuators and sensors is achieved by several levels of flight software, coordinated between two computers with varying bandwidth control loops. Furthermore, the actuators and sensors were integrated into multiple larger robotic mechanisms that were delivered by different organizations at various points in the Integration and Test (I&T) timeline. All of this created a very complex Verification and Validation (V&V) scenario involving multiple subsystems and teams, several hardware and software testbeds with varying levels of fidelity, and significant systems engineering to ensure the overall I&T schedule could be maintained while ensuring system hardware safety.This paper details the integrated V&V effort across multiple teams and venues to provide full coverage of all necessary functionality, performance, and fault protection. First, it provides an overview of how the V&V campaign was subdivided among teams and venues and provides descriptions of the various hardware configurations used to support the testing. The Mars 2020 implementation of the plan incorporates many of the lessons learned from Mars Science Laboratory’s test campaign, and these value-added modifications are discussed here. Also included in this section is the system-level environmental testing approach used for mechanisms. Second, the paper describes the phased approach used by the teams to support new hardware and software deliveries to testbed and Systems I&T. In this approach the test campaign was built upon higher-level mechanism needs for performance, functionality, and safety at specific times in the campaign. Finally, the paper discusses lessons learned from the V&V campaign that should be applied to future large-scale motion control testing efforts.

Borne, Davis↗

Results from the First Two Flights of the Static Computer Memory Integrity Testing Experiment

This paper details the scientific objectives, experiment design, data collection method, and post flight analysis following the first two flights of the Static Computer Memory Integrity Testing (SCMIT) experiment. SCMIT is designed to detect soft-event upsets in passive magnetic memory. A soft-event upset is a change in the logic state of active or passive forms of magnetic memory, commonly referred to as a "Bitflip". In its mildest form a soft-event upset can cause software exceptions, unexpected events, start spacecraft safeing (ending data collection) or corrupted fault protection and error recovery capabilities. In it's most severe form loss of mission or spacecraft can occur. Analysis after the first flight (in 1991 during STS-40) identified possible soft-event upsets to 25% of the experiment detectors. Post flight analysis after the second flight (in 1997 on STS-87) failed to find any evidence of soft-event upsets. The SCMIT experiment is currently scheduled for a third flight in December 1999 on STS-101.

Hancock, Thomas M., III↗

Solar Sail Torque Model Characterization for the Near Earth Asteroid Scout Mission

Near Earth Asteroid Scout (NEA Scout) was a mission to test solar sail propulsion for orbital transfer from cislunar space to flyby and image an asteroid. Had it succeeded, one of the mission goals was to characterize the solar torque on the sail to ensure successful attitude control for the orbit transfer and imaging the asteroid. The simulation used to develop the flight attitude control software uses the generalized model for solar sails, a tensor equation of the forces and torques on sails of arbitrary shape. Rios-Reyes and Scheeres developed a general process to update the torque tensor coefficients using estimates of sail torque over a range of directions to the sun. Their process was adapted and implemented for the specific case of NEA Scout using spacecraft telemetry collected during sail characterization maneuvers in combination with simulation models and parameters. The NEA Scout maneuvers were limited to the operating range of the mission and constraints of the control hardware and allowed safe testing of each attitude before proceeding to the next. The NEA Scout reaction wheel speeds are used to measure accumulated momentum, while the Active Mass Translator (AMT) position is used to subtract out the torque from the center of mass crossed with the sail force and isolate the torque from only the sail shape. The process was tested by running attitude control simulations of the characterization maneuvers, generating simulated telemetry, estimating the solar torques, then using a least squares estimating the solar torque coefficients using least-squares and then performing a least-squares fit to the solar torque tensor coefficients. These estimated coefficients were tested by evaluating the solar torques under the same conditions as the simulated telemetry and comparing to the true simulated torques. Solar force model updates can be performed separately by observing the effect of the sail on the trajectory, and the torque model can be refined using those solar force updates. This process met the needs of the NEA Scout mission and can be adapted to characterize the solar torque for other missions with different sails.

solar sail↗

Parachute Testing for the NASA X-38 Crew Return Vehicle

NASA's X-38 program was an in-house technology demonstration program to develop a Crew Return Vehicle (CRV) for the International Space Station capable of returning seven crewmembers to Earth when the Space Shuttle was not present at the station. The program, managed out of NASA's Johnson Space Center, was started in 1995 and was cancelled in 2003. Eight flights with a prototype atmospheric vehicle were successfully flown at Edwards Air Force Base, demonstrating the feasibility of a parachute landing system for spacecraft. The intensive testing conducted by the program included testing of large ram-air parafoils. The flight test techniques, instrumentation, and simulation models developed during the parachute test program culminated in the successful demonstration of a guided parafoil system to land a 25,000 Ib spacecraft. The test program utilized parafoils of sizes ranging from 750 to 7500 p. The guidance, navigation, and control system (GN&C) consisted of winches, laser or radar altimeter, global positioning system (GPS), magnetic compass, barometric altimeter, flight computer, and modems for uplink commands and downlink data. The winches were used to steer the parafoil and to perform the dynamic flare maneuver for a soft landing. The laser or radar altimeter was used to initiate the flare. In the event of a GPS failure, the software navigated by dead reckoning using the compass and barometric altimeter data. The GN&C test beds included platforms dropped from cargo aircraft, atmospheric vehicles released from a 8-52, and a Buckeye powered parachute. This paper will describe the test program and significant results.

Stein, Jenny M.↗

Supporting Real-Time Operations and Execution through Timeline and Scheduling Aids

Since 2003, the NASA Ames Research Center has been actively involved in researching and advancing the state-of-the-art of planning and scheduling tools for NASA mission operations. Our planning toolkit SPIFe (Scheduling and Planning Interface for Exploration) has supported a variety of missions and field tests, scheduling activities for Mars rovers as well as crew on-board International Space Station and NASA earth analogs. The scheduled plan is the integration of all the activities for the day/s. In turn, the agents (rovers, landers, spaceships, crew) execute from this schedule while the mission support team members (e.g., flight controllers) follow the schedule during execution. Over the last couple of years, our team has begun to research and validate methods that will better support users during realtime operations and execution of scheduled activities. Our team utilizes human-computer interaction principles to research user needs, identify workflow processes, prototype software aids, and user test these. This paper discusses three specific prototypes developed and user tested to support real-time operations: Score Mobile, Playbook, and Mobile Assistant for Task Execution (MATE).

scheduling↗

Simulation and Flight Test Capability for Testing Prototype Sense and Avoid System Elements

NASA Langley Research Center (LaRC) and The MITRE Corporation (MITRE) have developed, and successfully demonstrated, an integrated simulation-to-flight capability for evaluating sense and avoid (SAA) system elements. This integrated capability consists of a MITRE developed fast-time computer simulation for evaluating SAA algorithms, and a NASA LaRC surrogate unmanned aircraft system (UAS) equipped to support hardware and software in-the-loop evaluation of SAA system elements (e.g., algorithms, sensors, architecture, communications, autonomous systems), concepts, and procedures. The fast-time computer simulation subjects algorithms to simulated flight encounters/ conditions and generates a fitness report that records strengths, weaknesses, and overall performance. Reviewed algorithms (and their fitness report) are then transferred to NASA LaRC where additional (joint) airworthiness evaluations are performed on the candidate SAA system-element configurations, concepts, and/or procedures of interest; software and hardware components are integrated into the Surrogate UAS research systems; and flight safety and mission planning activities are completed. Onboard the Surrogate UAS, candidate SAA system element configurations, concepts, and/or procedures are subjected to flight evaluations and in-flight performance is monitored. The Surrogate UAS, which can be controlled remotely via generic Ground Station uplink or automatically via onboard systems, operates with a NASA Safety Pilot/Pilot in Command onboard to permit safe operations in mixed airspace with manned aircraft. An end-to-end demonstration of a typical application of the capability was performed in non-exclusionary airspace in October 2011; additional research, development, flight testing, and evaluation efforts using this integrated capability are planned throughout fiscal year 2012 and 2013.

Howell, Charles T.↗

Autonomous Flight Safety System September 27, 2005, Aircraft Test

This report describes the first aircraft test of the Autonomous Flight Safety System (AFSS). The test was conducted on September 27, 2005, near Kennedy Space Center (KSC) using a privately-owned single-engine plane and evaluated the performance of several basic flight safety rules using real-time data onboard a moving aerial vehicle. This test follows the first road test of AFSS conducted in February 2005 at KSC. AFSS is a joint KSC and Wallops Flight Facility (WEF) project that is in its third phase of development. AFSS is an independent subsystem intended for use with Expendable Launch Vehicles that uses tracking data from redundant onboard sensors to autonomously make flight termination decisions using software-based rules implemented on redundant flight processors. The goals of this project are to increase capabilities by allowing launches from locations that do not have or cannot afford extensive ground-based range safety assets, to decrease range costs, and to decrease reaction time for special situations. The mission rules are configured for each operation by the responsible Range Safety authorities and can be loosely categorized in four major categories: Parameter Threshold Violations, Physical Boundary Violations present position and instantaneous impact point (TIP), Gate Rules static and dynamic, and a Green-Time Rule. Examples of each of these rules were evaluated during this aircraft test.

Simpson, James C.↗

Robust Multivariable Optimization and Performance Simulation for ASIC Design

Application-specific-integrated-circuit (ASIC) design for space applications involves multiple challenges of maximizing performance, minimizing power, and ensuring reliable operation in extreme environments. This is a complex multidimensional optimization problem, which must be solved early in the development cycle of a system due to the time required for testing and qualification severely limiting opportunities to modify and iterate. Manual design techniques, which generally involve simulation at one or a small number of corners with a very limited set of simultaneously variable parameters in order to make the problem tractable, are inefficient and not guaranteed to achieve the best possible results within the performance envelope defined by the process and environmental requirements. What is required is a means to automate design parameter variation, allow the designer to specify operational constraints and performance goals, and to analyze the results in a way that facilitates identifying the tradeoffs defining the performance envelope over the full set of process and environmental corner cases. The system developed by the Mixed Signal ASIC Group (MSAG) at the Goddard Space Flight Center is implemented as a framework of software modules, templates, and function libraries. It integrates CAD tools and a mathematical computing environment, and can be customized for new circuit designs with only a modest amount of effort as most common tasks are already encapsulated. Customization is required for simulation test benches to determine performance metrics and for cost function computation.

DuMonthier, Jeffrey↗

GPS interferometric attitude and heading determination: Initial flight test results

Attitude and heading determination using GPS interferometry is a well-understood concept. However, efforts have been concentrated mainly in the development of robust algorithms and applications for low dynamic, rigid platforms (e.g., shipboard). This paper presents results of what is believed by the authors to be the first realtime flight test of a GPS attitude and heading determination system. The system is installed in Ohio University's Douglas DC-3 research aircraft. Signals from four antennas are processed by an Ashtech 3DF 24-channel GPS receiver. Data from the receiver are sent to a microcomputer for storage and further computations. Attitude and heading data are sent to a second computer for display on a software generated artificial horizon. Demonstration of this technique proves its candidacy for augmentation of aircraft state estimation for flight control and navigation as well as for numerous other applications.

Vangraas, Frank↗

Increasing Flight Software Reuse with OpenSatKit

In January 2015 the NASA Goddard Space Flight Center (GSFC) released the Core Flight System (cFS) as open source under the NASA Open Source Agreement (NOSA) license. The cFS is based on flight software (FSW) developed for 12 spacecraft spanning nearly two decades of effort and it can provide about a third of the FSW functionality for a low-earth orbiting scientific spacecraft. The cFS is a FSW framework that is portable, configurable, and extendable using a product line deployment model. However, the components are maintained separately so the user must configure, integrate, and deploy them as a cohesive functional system. This can be very challenging especially for organizations such as universities building cubesats that have minimal experience developing FSW. Supporting universities was one of the primary motivators for releasing the cFS under NOSA. This paper describes the OpenSatKit that was developed to address the cFS deployment challenges and to serve as a cFS training platform for new users. It provides a fully functional out-of-the box software system that includes NASA's cFS, Ball Aerospace's command and control system COSMOS, and a NASA dynamic simulator called 42. The kit is freely available since all of the components have been released as open source. The kit runs on a Linux platform, includes 8 cFS applications, several kit-specific applications, and built in demos illustrating how to use key application features. It also includes the software necessary to port the cFS to a Raspberry Pi and instructions for configuring COSMOS to communicate with the target. All of the demos and test scripts can be rerun unchanged with the cFS running on the Raspberry Pi. The cFS uses a 3-tiered layered architecture including a platform abstraction layer, a Core Flight Executive (cFE) middle layer, and an application layer. Similar to smart phones, the cFS application layer is the key architectural feature for users to extend the FSW functionality to meet their mission-specific requirements. The platform abstraction layer and the cFE layers go a step further than smart phones by providing a platform-agnostic Application Programmer Interface (API) that allows applications to run unchanged on different platforms. OpenSatKit can serve two significant architectural roles that will further help the adoption of the cFS and help create a community of users that can share assets. First, the kit is being enhanced to automate the integration of applications with the goal of creating a virtual cFS "App Store".. Second, a platform certification test suite can be developed that would allow users to verify the port of the cFS to a new platform. This paper will describe the current state of these efforts and future plans.

Computer Programming and Software↗

Microbial load monitor

Design analysis of a microbial load monitor system flight engineering model was presented. Checkout of the card taper and media pump system was fabricated as well as the final two incubating reading heads, the sample receiving and card loading device assembly, related sterility testing, and software. Progress in these areas was summarized.

Caplin, R. S.↗

NASA's approach to flight confidence

NASA's confidence in the flight readiness of aerospace hardware and software is achieved by a thorough integration of safety activities into every program facet, from concept through the mission. This involves technical and administrative personnel, organizations that specify requirements, design, manufacturing, test and the operators. Reviews by inhouse and external specialists form an integral part of the assurance process. Examples of safety issues and their resolution for some power and propulsion functions are given (lithium cells, autoignition/fretting in high pressure oxygen environments, ignition sources from auxiliary power unit, and low thrust rocket engines). Finally, some comments on NASA's integrated safety activities and the Aerospace Safety Advisory Panel's role in the NASA review and assessment process all of which provides added confidence in achieving a high level of mission safety and success.

Roth, G. L.↗

Can space station software be specified through Ada?

Programming of the space station is to be done in the Ada programming language. A breadboard of selected parts of the work package for Marshall Space Flight Center is to be built, and programming this small part will be a good testing ground for Ada. One coding of the upper levels of the design brings out several problems with top-down design when it is to be carried out strictly within the language. Ada is evaluated on the basis of this experience, and the points raised are compared with other experience as related in the literature. Rapid prototyping is another approach to the initial programming; several different types of prototypes are discussed, and compared with the art of specification. Some solutions are proposed and a number of recommendations presented.

Knoebel, Arthur↗

A strip chart recorder pattern recognition tool kit for Shuttle operations

During Space Shuttle operations, Mission Control personnel monitor numerous mission-critical systems such as electrical power; guidance, navigation, and control; and propulsion by means of paper strip chart recorders. For example, electrical power controllers monitor strip chart recorder pen traces to identify onboard electrical equipment activations and deactivations. Recent developments in pattern recognition technologies coupled with new capabilities that distribute real-time Shuttle telemetry data to engineering workstations make it possible to develop computer applications that perform some of the low-level monitoring now performed by controllers. The number of opportunities for such applications suggests a need to build a pattern recognition tool kit to reduce software development effort through software reuse. We are building pattern recognition applications while keeping such a tool kit in mind. We demonstrated the initial prototype application, which identifies electrical equipment activations, during three recent Shuttle flights. This prototype was developed to test the viability of the basic system architecture, to evaluate the performance of several pattern recognition techniques including those based on cross-correlation, neural networks, and statistical methods, to understand the interplay between an advanced automation application and human controllers to enhance utility, and to identify capabilities needed in a more general-purpose tool kit.

Hammen, David G.↗

Reengineering legacy software to object-oriented systems

NASA has a legacy of complex software systems that are becoming increasingly expensive to maintain. Reengineering is one approach to modemizing these systems. Object-oriented technology, other modem software engineering principles, and automated tools can be used to reengineer the systems and will help to keep maintenance costs of the modemized systems down. The Software Technology Branch at the NASA/Johnson Space Center has been developing and testing reengineering methods and tools for several years. The Software Technology Branch is currently providing training and consulting support to several large reengineering projects at JSC, including the Reusable Objects Software Environment (ROSE) project, which is reengineering the flight analysis and design system (over 2 million lines of FORTRAN code) into object-oriented C++. Many important lessons have been learned during the past years; one of these is that the design must never be allowed to diverge from the code during maintenance and enhancement. Future work on open, integrated environments to support reengineering is being actively planned.

Pitman, C.↗

Commercial Modular Aero-Propulsion System Simulation 40k

The Commercial Modular Aero-Propulsion System Simulation 40k (CMAPSS40k) software package is a nonlinear dynamic simulation of a 40,000-pound (approximately equals 178-kN) thrust class commercial turbofan engine, written in the MATLAB/Simulink environment. The model has been tuned to capture the behavior of flight test data, and is capable of running at any point in the flight envelope [up to 40,000 ft (approximately equals 12,200 m) and Mach 0.8]. In addition to the open-loop engine, the simulation includes a controller whose architecture is representative of that found in industry. C-MAPSS40k fills the need for an easy-to-use, realistic, transient simulation of a medium-size commercial turbofan engine with a representative controller. It is a detailed component level model (CLM) written in the industry-standard graphical MATLAB/Simulink environment to allow for easy modification and portability. At the time of this reporting, no other such model exists in the public domain.

Guo, Ten-Huei↗

Thermal System Verification and Model Validation for NASA's Cryogenic Passively Cooled James Webb Space Telescope

A thorough and unique thermal verification and model validation plan has been developed for NASA s James Webb Space Telescope. The JWST observatory consists of a large deployed aperture optical telescope passively cooled to below 50 Kelvin along with a suite of several instruments passively and actively cooled to below 37 Kelvin and 7 Kelvin, respectively. Passive cooling to these extremely low temperatures is made feasible by the use of a large deployed high efficiency sunshield and an orbit location at the L2 Lagrange point. Another enabling feature is the scale or size of the observatory that allows for large radiator sizes that are compatible with the expected power dissipation of the instruments and large format Mercury Cadmium Telluride (HgCdTe) detector arrays. This passive cooling concept is simple, reliable, and mission enabling when compared to the alternatives of mechanical coolers and stored cryogens. However, these same large scale observatory features, which make passive cooling viable, also prevent the typical flight configuration fully-deployed thermal balance test that is the keystone to most space missions thermal verification plan. JWST is simply too large in its deployed configuration to be properly thermal balance tested in the facilities that currently exist. This reality, when combined with a mission thermal concept with little to no flight heritage, has necessitated the need for a unique and alternative approach to thermal system verification and model validation. This paper describes the thermal verification and model validation plan that has been developed for JWST. The plan relies on judicious use of cryogenic and thermal design margin, a completely independent thermal modeling cross check utilizing different analysis teams and software packages, and finally, a comprehensive set of thermal tests that occur at different levels of JWST assembly. After a brief description of the JWST mission and thermal architecture, a detailed description of the three aspects of the thermal verification and model validation plan is presented.

Cleveland, Paul E.↗