Search NASA⌕ Search

SEARCH · Search NASA

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 235 records · Page 13
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Flight Software for the LOFTID Re-Entry Vehicle

NASA’s Low-Earth Orbit Flight Test of an Inflatable Decelerator, or LOFTID, demonstrated re-entry from low-Earth orbit of a 6-meter aeroshell designed to be used as a heat shield that is larger than the rocket shroud, enabling the return of much greater mass. The LOFTID Flight Software was developed in-house and consists of three components: the Power Distribution software, the Data Recorder software, and the Camera Controller software, along with the Ground Software used for testing, operations, data integrity, and data processing. This presentation will discuss issues found in developing the Power Distribution software in cFS on a non-Linux POSIX platform, designing an efficient architecture for recording of high bandwidth data, controlling over a dozen cameras in-flight, and creating the ground support tools to verify data integrity and support the post-processing of flight data.

Paul Brewster↗
NASA NTRS2004

Modeling and Simulation of Shuttle Launch and Range Operations

The simulation and modeling test bed is based on a mockup of a space flight operations control suitable to experiment physical, procedural, software, hardware and psychological aspects of space flight operations. The test bed consists of a weather expert system to advise on the effect of weather to the launch operations. It also simulates toxic gas dispersion model, impact of human health risk, debris dispersion model in 3D visualization. Since all modeling and simulation is based on the internet, it could reduce the cost of operations of launch and range safety by conducting extensive research before a particular launch. Each model has an independent decision making module to derive the best decision for launch.

Bardina, Jorge↗
NASA NTRS2009

Modeling and Simulation of Variable Mass, Flexible Structures

The advent of the new Ares I launch vehicle has highlighted the need for advanced dynamic analysis tools for variable mass, flexible structures. This system is composed of interconnected flexible stages or components undergoing rapid mass depletion through the consumption of solid or liquid propellant. In addition to large rigid body configuration changes, the system simultaneously experiences elastic deformations. In most applications, the elastic deformations are compatible with linear strain-displacement relationships and are typically modeled using the assumed modes technique. The deformation of the system is approximated through the linear combination of the products of spatial shape functions and generalized time coordinates. Spatial shape functions are traditionally composed of normal mode shapes of the system or even constraint modes and static deformations derived from finite element models of the system. Equations of motion for systems undergoing coupled large rigid body motion and elastic deformation have previously been derived through a number of techniques [1]. However, in these derivations, the mode shapes or spatial shape functions of the system components were considered constant. But with the Ares I vehicle, the structural characteristics of the system are changing with the mass of the system. Previous approaches to solving this problem involve periodic updates to the spatial shape functions or interpolation between shape functions based on system mass or elapsed mission time. These solutions often introduce misleading or even unstable numerical transients into the system. Plus, interpolation on a shape function is not intuitive. This paper presents an approach in which the shape functions are held constant and operate on the changing mass and stiffness matrices of the vehicle components. Each vehicle stage or component finite element model is broken into dry structure and propellant models. A library of propellant models is used to describe the distribution of mass in the fuel tank or Solid Rocket Booster (SRB) case for various propellant levels. Based on the mass consumed by the liquid engine or SRB, the appropriate propellant model is coupled with the dry structure model for the stage. Then using vehicle configuration data, the integrated vehicle model is assembled and operated on by the constant system shape functions. The system mode shapes and frequencies can then be computed from the resulting generalized mass and stiffness matrices for that mass configuration. The rigid body mass properties of the vehicle are derived from the integrated vehicle model. The coupling terms between the vehicle rigid body motion and elastic deformation are also updated from the constant system shape functions and the integrated vehicle model. This approach was first used to analyze variable mass spinning beams and then prototyped into a generic dynamics simulation engine. The resulting code was tested against Crew Launch Vehicle (CLV-)class problems worked in the TREETOPS simulation package and by Wilson [2]. The Ares I System Integration Laboratory (SIL) is currently being developed at the Marshall Space Flight Center (MSFC) to test vehicle avionics hardware and software in a hardware-in-the-loop (HWIL) environment and certify that the integrated system is prepared for flight. The Ares I SIL utilizes the Ares Real-Time Environment for Modeling, Integration, and Simulation (ARTEMIS) tool to simulate the launch vehicle and stimulate avionics hardware. Due to the presence of vehicle control system filters and the thrust oscillation suppression system, which are tuned to the structural characteristics of the vehicle, ARTEMIS must incorporate accurate structural models of the Ares I launch vehicle. The ARTEMIS core dynamics simulation models the highly coupled nature of the vehicle flexible body dynamics, propellant slosh, and vehicle nozzle inertia effects combined with mass and flexible body properties that vary significant with time during the flight. All forces that act on the vehicle during flight must be simulated, including deflected engine thrust force, spatially distributed aerodynamic forces, gravity, and reaction control jet thrust forces. These forces are used to excite an integrated flexible vehicle, slosh, and nozzle dynamics model for the vehicle stack that simulates large rigid body translations and rotations along with small elastic deformations. Highly effective matrix math operations on a distributed, threaded high-performance simulation node allow ARTEMIS to retain up to 30 modes of flex for real-time simulation. Stage elements that separate from the stack during flight are propagated as independent rigid six degrees of freedom (6DOF) bodies. This paper will present the formulation of the resulting equations of motion, solutions to example problems, and describe the resulting dynamics simulation engine within ARTEMIS.

Tobbe, Patrick A.↗
NASA NTRS1998

Ascent, Transition, Entry, and Abort Guidance Algorithm Design for the X-33 Vehicle

One of the primary requirements for X-33 is that it be capable of flying autonomously. That is, onboard computers must be capable of commanding the entire flight from launch to landing, including cases where a single engine failure abort occurs. Guidance algorithms meeting these requirements have been tested in simulation and have been coded into prototype flight software. These algorithms must be sufficiently robust to account for vehicle and environmental dispersions, and must issue commands that result in the vehicle operating, within all constraints. Continual tests of these algorithms (and modifications as necessary) will occur over the next year as the X-33 nears its first flight. This paper describes the algorithms in use for X-33 ascent, transition, and entry flight, as well as for the powered phase of PowerPack-out (PPO) aborts (equivalent in thrust impact to losing an engine). All following discussion refers to these phases of flight when discussing guidance. The paper includes some trajectory results and results of dispersion analysis.

Hanson, John M.↗
NASA NTRS1987

Flight test of a digital controller used in a helicopter autoland system

This paper describes the flight test evaluation of an advanced digital helicopter flight control system. The controller was designed using an optimal control design procedure for a fully coupled lateral and longitudinal vehicle model. Explicit integrals of the guidance error were included to produce a type 1 characteristic. Gain scheduling was used to account for changes in the vehicle dynamics. The digital controller was exercised by combining it with state estimators, a trajectory generator, and a closed-loop guidance algorithm to form a helicopter autoland system. A CH-47 tandem rotor helicopter was equipped with sensors, on-board digital flight computers, and electrohydraulic actuators. The system was exercised by automatically flying straight-in descending decelerating trajectories typcial of VFR manual landing approaches. A description of the test-ground facilities, the flight hardware and software, and the velocity and position tracking performance is included.

Downing, David R.↗
NASA NTRS1991

Optical studies in the holographic ground station

The Holographic Group System (HGS) Facility in rooms 22 & 123, Building 4708 has been developed to provide for ground based research in determining pre-flight parameters and analyzing the results from space experiments. The University of Alabama, Huntsville (UAH) has researched the analysis aspects of the HGS and reports their findings here. Some of the results presented here also occur in the Facility Operating Procedure (FOP), which contains instructions for power up, operation, and powerdown of the Fluid Experiment System (FES) Holographic Ground System (HGS) Test Facility for the purpose of optically recording fluid and/or crystal behavior in a test article during ground based testing through the construction of holograms and recording of videotape. The alignment of the optical bench components, holographic reconstruction and and microscopy alignment sections were also included in the document for continuity even though they are not used until after optical recording of the test article) setup of support subsystems and the Automated Holography System (AHS) computer. The HGS provides optical recording and monitoring during GCEL runs or development testing of potential FES flight hardware or software. This recording/monitoring can be via 70mm holographic film, standard videotape, or digitized images on computer disk. All optical bench functions necessary to construct holograms will be under the control of the AHS personal computer (PC). These include type of exposure, time intervals between exposures, exposure length, film frame identification, film advancement, film platen evacuation and repressurization, light source diffuser introduction, and control of realtime video monitoring. The completed sequence of hologram types (single exposure, diffuse double exposure, etc.) and their time of occurrence can be displayed, printed, or stored on floppy disk posttest for the user.

Workman, Gary L.↗
NASA NTRS1999

Position Estimation Verification Testing for the Video Guidance Sensor and Dynamic Overhead Target Simulator

The Video Guidance Sensor, part of the Automated Rendezvous and Capture mechanism, is due to undergo formal qualification testing at Marshall Space Flight Center. Before it undergoes this qualification, a test was needed to verify repeatability of the sensor, and to allow different sensor configurations to be compared. This test was developed at the Flight Robotics Laboratory. The test uses a software script to drive the sensor target to the same position and thus allows sensor runs to be compared. The sensor target is the Dynamic Overhead Target Simulator. The simulator uses encoders as its position indicator. Distance Measuring Device's were used to independently verify the software script, the sensor reading, and the target position. The test area, sensor, and other test equipment are briefly described. The actual data is tabulated and will serve as a baseline for future tests. The software script was found to be adequate for the test. Position repeatability was acceptable for all the equipment. The system test is now ready to be used in formal qualification testing.

Gaines, Joseph↗
NASA NTRS2001

Life Testing of the Hollow Cathode Plasma Contactor for the ProSEDS Mission

The Propulsive Small Expendable Deployer System (ProSEDS) mission is designed to provide an on-orbit demonstration of the electrodynamic propulsion capabilities of tethers in space. The ProSEDS experiment will be a secondary payload on a Delta 11 unmanned expendable booster. A 5-km conductive tether is attached to the Delta 11 second stage and collects current from the low Earth orbit (LEO) plasma. A hollow cathode plasma contactor emits the collected electrons from the Delta II, completing the electrical circuit with the ambient plasma. The current flowing through the tether generates thrust based on the Lorentz Force Law. The thrust will be generated opposite to the velocity vector, slowing down the spacecraft and causing it to de-orbit in approximately 14 days compared to the normal 6 months. A 10-km non-conductive tether is between the conductive tether and an endmass containing several scientific instruments. The ProSEDS mission lifetime was set at I day because most of the primary objectives can be met in that time. The extended ProSEDS mission will be for as many days as possible, until the Delta 11 second stage burns up or the tether is severed by a micrometeoroid or space debris particle. The Hollow Cathode Plasma Contactor (HCPC) unit has been designed for a 12-day mission. Because of the science requirements to measure the background ambient plasma, the HCPC must operate on a duty cycle. Later in the ProSEDS mission, the HCPC is operated in a manner to allow charging of the secondary battery. Due to the unusual operating requirements by the ProSEDS mission, a development unit of the HCPC was built for thorough testing. This developmental unit was tested for a simulated ProSEDS mission, with measurements of the ability to start and stop during the duty cycle. These tests also provided valuable data for the ProSEDS software requirements. Qualification tests of the HCPC flight hardware are also discussed.

Vaughn, Jason A.↗
NASA NTRS2012

Spacecraft Avionics Software Development Then and Now: Different but the Same

NASA has always been in the business of balancing new technologies and techniques to achieve human space travel objectives. NASA s historic Software Production Facility (SPF) was developed to serve complex avionics software solutions during an era dominated by mainframes, tape drives, and lower level programming languages. These systems have proven themselves resilient enough to serve the Shuttle Orbiter Avionics life cycle for decades. The SPF and its predecessor the Software Development Lab (SDL) at NASA s Johnson Space Center (JSC) hosted flight software (FSW) engineering, development, simulation, and test. It was active from the beginning of Shuttle Orbiter development in 1972 through the end of the shuttle program in the summer of 2011 almost 40 years. NASA s Kedalion engineering analysis lab is on the forefront of validating and using many contemporary avionics HW/SW development and integration techniques, which represent new paradigms to NASA s heritage culture in avionics software engineering. Kedalion has validated many of the Orion project s HW/SW engineering techniques borrowed from the adjacent commercial aircraft avionics environment, inserting new techniques and skills into the Multi-Purpose Crew Vehicle (MPCV) Orion program. Using contemporary agile techniques, COTS products, early rapid prototyping, in-house expertise and tools, and customer collaboration, NASA has adopted a cost effective paradigm that is currently serving Orion effectively. This paper will explore and contrast differences in technology employed over the years of NASA s space program, due largely to technological advances in hardware and software systems, while acknowledging that the basic software engineering and integration paradigms share many similarities.

Mangieri, Mark L.↗
NASA NTRS2013

Direct-to-Earth Communications with Mars Science Laboratory During Entry, Descent, and Landing

Mars Science Laboratory (MSL) undergoes extreme heating and acceleration during Entry, Descent, and Landing (EDL) on Mars. Unknown dynamics lead to large Doppler shifts, making communication challenging. During EDL, a special form of Multiple Frequency Shift Keying (MFSK) communication is used for Direct-To-Earth (DTE) communication. The X-band signal is received by the Deep Space Network (DSN) at the Canberra Deep Space Communication complex, then down-converted, digitized, and recorded by open-loop Radio Science Receivers (RSR), and decoded in real-time by the EDL Data Analysis (EDA) System. The EDA uses lock states with configurable Fast Fourier Transforms to acquire and track the signal. RSR configuration and channel allocation is shown. Testing prior to EDL is discussed including software simulations, test bed runs with MSL flight hardware, and the in-flight end-to-end test. EDA configuration parameters and signal dynamics during pre-entry, entry, and parachute deployment are analyzed. RSR and EDA performance during MSL EDL is evaluated, including performance using a single 70-meter DSN antenna and an array of two 34-meter DSN antennas as a back up to the 70-meter antenna.

Direct-to-Earth (DTE)↗
NASA NTRS2015

Automated Test for NASA CFS

The core Flight System (cFS) is a flight software (FSW) product line developed by the Flight Software Systems Branch (FSSB) at NASA's Goddard Space Flight Center (GSFC). The cFS uses compile-time configuration parameters to implement variable requirements to enable portability across embedded computing platforms and to implement different end-user functional needs. The verification and validation of these requirements is proving to be a significant challenge. This paper describes the challenges facing the cFS and the results of a pilot effort to apply EXB Solution's testing approach to the cFS applications.

Flight software↗
NASA NTRS1981

A method of testing attitude control systems during the development phase

A technique, utilized on the Space Telescope Program, and used for testing satellite attitude pointing and control systems during the engineering and development phases is presented. The technique verifies the hardware models used in design phase computer simulations, verifies the interface between the flight hardware and flight software, and uncovers hardware/software switching or mode logic problems. The testing is accomplished in two phases: a dynamic hardware simulator phase using hardware electronic simulators and an electronic vehicle motion simulator; and a second real hardware phase utilizing engineering model gyros and reaction wheels on an airbearing table. Both phases use an engineering model of the flight computer, flight algorithms and software, and a breadboard data management and computer hardware interface for timing simulations. The purpose of each test and the test phases are described, and examples of closed loop test results for both attitude hold and maneuvering models are given.

Besonis, A.↗
NASA NTRS2000

Intelligence Applied to Air Vehicles

The exponential growth in information technology has provided the potential for air vehicle capabilities that were previously unavailable to mission and vehicle designers. The increasing capabilities of computer hardware and software, including new developments such as neural networks, provide a new balance of work between humans and machines. This paper will describe several NASA projects, and review results and conclusions from ground and flight investigations where vehicle intelligence was developed and applied to aeronautical and space systems. In the first example, flight results from a neural network flight control demonstration will be reviewed. Using, a highly-modified F-15 aircraft, a NASA/Dryden experimental flight test program has demonstrated how the neural network software can correctly identify and respond to changes in aircraft stability and control characteristics. Using its on-line learning capability, the neural net software would identify that something in the vehicle has changed, then reconfigure the flight control computer system to adapt to those changes. The results of the Remote Agent software project will be presented. This capability will reduce the cost of future spacecraft operations as computers become "thinking" partners along with humans. In addition, the paper will describe the objectives and plans for the autonomous airplane program and the autonomous rotorcraft project. Technologies will also be developed.

Rosen, Robert↗
NASA NTRS2007

Enhanced Master Controller Unit Tester

The Enhanced Master Controller Unit Tester (EMUT) software is a tool for development and testing of software for a master controller (MC) flight computer. The primary function of the EMUT software is to simulate interfaces between the MC computer and external analog and digital circuitry (including other computers) in a rack of equipment to be used in scientific experiments. The simulations span the range of nominal, off-nominal, and erroneous operational conditions, enabling the testing of MC software before all the equipment becomes available.

Benson, Patricia↗
NASA NTRS2008

Workstation-Based Avionics Simulator to Support Mars Science Laboratory Flight Software Development

The Mars Science Laboratory developed the WorkStation TestSet (WSTS) to support flight software development. The WSTS is the non-real-time flight avionics simulator that is designed to be completely software-based and run on a workstation class Linux PC. This provides flight software developers with their own virtual avionics testbed and allows device-level and functional software testing when hardware testbeds are either not yet available or have limited availability. The WSTS has successfully off-loaded many flight software development activities from the project testbeds. At the writing of this paper, the WSTS has averaged an order of magnitude more usage than the project's hardware testbeds.

WSTS↗
NASA NTRS1982

Advanced flight control system study

A fly by wire flight control system architecture designed for high reliability includes spare sensor and computer elements to permit safe dispatch with failed elements, thereby reducing unscheduled maintenance. A methodology capable of demonstrating that the architecture does achieve the predicted performance characteristics consists of a hierarchy of activities ranging from analytical calculations of system reliability and formal methods of software verification to iron bird testing followed by flight evaluation. Interfacing this architecture to the Lockheed S-3A aircraft for flight test is discussed. This testbed vehicle can be expanded to support flight experiments in advanced aerodynamics, electromechanical actuators, secondary power systems, flight management, new displays, and air traffic control concepts.

Hartmann, G. L.↗
NASA NTRS2015

Flight Testing of Guidance, Navigation and Control Systems on the Mighty Eagle Robotic Lander Testbed

During 2011 a series of progressively more challenging flight tests of the Mighty Eagle autonomous terrestrial lander testbed were conducted primarily to validate the GNC system for a proposed lunar lander. With the successful completion of this GNC validation objective the opportunity existed to utilize the Mighty Eagle as a flying testbed for a variety of technologies. In 2012 an Autonomous Rendezvous and Capture (AR&C) algorithm was implemented in flight software and demonstrated in a series of flight tests. In 2012 a hazard avoidance system was developed and flight tested on the Mighty Eagle. Additionally, GNC algorithms from Moon Express and a MEMs IMU were tested in 2012. All of the testing described herein was above and beyond the original charter for the Mighty Eagle. In addition to being an excellent testbed for a wide variety of systems the Mighty Eagle also provided a great learning opportunity for many engineers and technicians to work a flight program.

Hannan, Mike↗
NASA NTRS2004

Data Management for Mars Exploration Rovers

Data Management for the Mars Exploration Rovers (MER) project is a comprehensive system addressing the needs of development, test, and operations phases of the mission. During development of flight software, including the science software, the data management system can be simulated using any POSIX file system. During testing, the on-board file system can be bit compared with files on the ground to verify proper behavior and end-to-end data flows. During mission operations, end-to-end accountability of data products is supported, from science observation concept to data products within the permanent ground repository. Automated and human-in-the-loop ground tools allow decisions regarding retransmitting, re-prioritizing, and deleting data products to be made using higher level information than is available to a protocol-stack approach such as the CCSDS File Delivery Protocol (CFDP).

Mars missions↗