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 541 records · Page 30
All sourcesNASA NTRSDOE OSTI
NASA NTRS1986

A preliminary design for flight testing the FINDS algorithm

This report presents a preliminary design for flight testing the FINDS (Fault Inferring Nonlinear Detection System) algorithm on a target flight computer. The FINDS software was ported onto the target flight computer by reducing the code size by 65%. Several modifications were made to the computational algorithms resulting in a near real-time execution speed. Finally, a new failure detection strategy was developed resulting in a significant improvement in the detection time performance. In particular, low level MLS, IMU and IAS sensor failures are detected instantaneously with the new detection strategy, while accelerometer and the rate gyro failures are detected within the minimum time allowed by the information generated in the sensor residuals based on the point mass equations of motion. All of the results have been demonstrated by using five minutes of sensor flight data for the NASA ATOPS B-737 aircraft in a Microwave Landing System (MLS) environment.

Caglayan, A. K.↗
NASA NTRS1986

Vibroacoustic payload environment prediction system (VAPEPS): Data base management center remote access guide

A Vibroacoustic Data Base Management Center has been established at the Jet Propulsion Laboratory (JPL). The center utilizes the Vibroacoustic Payload Environment Prediction System (VAPEPS) software package to manage a data base of shuttle and expendable launch vehicle flight and ground test data. Remote terminal access over telephone lines to a dedicated VAPEPS computer system has been established to provide the payload community a convenient means of querying the global VAPEPS data base. This guide describes the functions of the JPL Data Base Management Center and contains instructions for utilizing the resources of the center.

Thomas, V. C.↗
NASA NTRS1990

High performance processors for real-time flight simulation

In order to meet the requirements of the NASA Langley Research Center for simulating the increased complexity and higher performance of modern aircraft, a flight simulation computing system with very high scalar performance is needed. The requirements and proposed response, probable areas of difficulty, planned implementation, and current status and plans are reviewed. A solution utilizing centralized minisupercomputers coupled with a proven real-time network technology will provide engineers and research scientists with the tools required for high-performance flight simulation. Subsequent to testing and verification of the initial simulation, general-purpose configuration management software with a nonconfiguration dependent serial highway driver software will be integrated to support any arbitrary combination of simulation sites.

Cleveland, Jeff I., II↗
NASA NTRS1997

Lessons Learned from the Clementine Mission

According to BMDO, the Clementine mission achieved many of its technology objectives during its flight to the Moon in early 1994 but, because of a software error, was unable to test the autonomous tracking of a cold target. The preliminary analyses of the returned lunar data suggest that valuable scientific measurements were made on several important topics but that COMPLEX's highest-priority objectives for lunar science were not achieved. This is not surprising given that the rationale for Clementine was technological rather than scientific. COMPLEX lists below a few of the lessons that may be learned from Clementine. Although the Clementine mission was not conceived as a NASA science mission exactly like those planned for the Discovery program, many operational aspects of the two are similar. It is therefore worthwhile to understand the strengths and faults of the Clementine approach. Some elements of the Clementine operation that led to the mission's success include the following: (1) The mission's achievements were the responsibility of a single organization and its manager, which made that organization and that individual accountable for the final outcome; (2) The sponsor adopted a hands-off approach and set a minimum number of reviews (three); (3) The sponsor accepted a reasonable amount of risk and allowed the project team to make the trade-offs necessary to minimize the mission's risks while still accomplishing all its primary objectives; and (4) The development schedule was brief and the agreed-on funding (and funding profile) was adhered to. Among the operational shortcomings of Clementine were the following: (1) An overly ambitious schedule and a slightly lean budget (meaning insufficient time for software development and testing, and leading ultimately to human exhaustion); and (2) No support for data calibration, reduction, and analysis. The principal lesson to be learned in this category is that any benefits from the constructive application of higher risk for lower cost and faster schedule will be lost if the schedule does not allow adequate time for the development of all essential systems or makes no allowance for human frailties. Another lesson to be drawn is that despite its limitations, if judged strictly as a science mission, Clementine attested that significant scientific information can be gathered during a technology-demonstration mission. In the current era of limited funds, when science missions will be infrequent, the opportunity to fly scientific instruments aboard missions whose objectives might be other than science must be seized and, indeed, encouraged. During such opportunities it would be inexcusable to do second-class science. Thus the scientific community must be actively involved in such projects from their initiation.

Source record↗
NASA NTRS2005

Integration of an Autopilot for a Micro Air Vehicle

Two autopilots providing autonomous flight capabilities are presented herein. The first is the Pico-Pilot, demonstrated for the 12-inch size class of micro air vehicles. The second is the MicroPilot MP2028(sup g), where its integration into a 36-inch Zagi airframe (tailless, elevons only configuration) is investigated and is the main focus of the report. Analytical methods, which include the use of the Advanced Aircraft Analysis software from DARCorp, were used to determine the stability and control derivatives, which were then validated through wind tunnel experiments. From the aerodynamic data, the linear, perturbed equations of motion from steady-state flight conditions may be cast in terms of these derivatives. Using these linear equations, transfer functions for the control and navigation systems were developed and feedback control laws based on Proportional, Integral, and Derivative (PID) control design were developed to control the aircraft. The PID gains may then be programmed into the autopilot software and uploaded to the microprocessor of the autopilot. The Pico-Pilot system was flight tested and shown to be successful in navigating a 12-inch MAV through a course defined by a number of waypoints with a high degree of accuracy, and in 20 mph winds. The system, though, showed problems with control authority in the roll and pitch motion of the aircraft: causing oscillations in these directions, but the aircraft maintained its heading while following the prescribed course. Flight tests were performed in remote control mode to evaluate handling, adjust trim, and test data logging for the Zagi with integrated MP2028(sup g). Ground testing was performed to test GPS acquisition, data logging, and control response in autonomous mode. Technical difficulties and integration limitations with the autopilot prevented fully autonomous flight from taking place, but the integration methodologies developed for this autopilot are, in general, applicable for unmanned air vehicles within the 36-inch size class or larger that use a PID control based autopilot.

Platanitis, George↗
NASA NTRS2010

Automation of Cassini Support Imaging Uplink Command Development

"Support imaging" is imagery requested by other Cassini science teams to aid in the interpretation of their data. The generation of the spacecraft command sequences for these images is performed by the Cassini Instrument Operations Team. The process initially established for doing this was very labor-intensive, tedious and prone to human error. Team management recognized this process as one that could easily benefit from automation. Team members were tasked to document the existing manual process, develop a plan and strategy to automate the process, implement the plan and strategy, test and validate the new automated process, and deliver the new software tools and documentation to Flight Operations for use during the Cassini extended mission. In addition to the goals of higher efficiency and lower risk in the processing of support imaging requests, an effort was made to maximize adaptability of the process to accommodate uplink procedure changes and the potential addition of new capabilities outside the scope of the initial effort.

Ly-Hollins, Lisa↗
NASA NTRSDate not supplied

Integrated Design Results for the MSR DAC-0.0 Mars Ascent Vehicle

The NASA Mars Sample Return (MSR) Campaign endeavors to return Martian regolith, rock, and atmospheric samples to Earth for scientific study. One of many significant challenges to overcome in the return of these samples lies in transporting them from the Martian surface to space. In order to surmount this challenge, the Campaign has conceptualized the need for a Mars Ascent Vehicle (MAV) to perform this function and deliver Martian samples to orbit. There, the samples will be ejected and captured by a separate spacecraft for return to Earth. Many concepts for a MAV have existed in the past, but it has not been until now that an integrated, detailed design solution has been developed and analyzed. Preliminary assessments of the initial architecture examined multiple methods of propulsion. The team ultimately determined that a Two Stage to Orbit (TSTO) solid propulsion vehicle would provide the most effective performance and be the most technologically ready to support this mission. Following the decision to adopt a TSTO solid propelled vehicle, the first official Design Analysis Cycle, DAC-0.0, was performed in Spring 2020 to formally advance the fidelity of the vehicle to a maturity level acceptable for NASA Key Decision Point A (KDP-A). This paper describes the resultant MAV design concept developed as part of the DAC-0.0 study by the NASA Marshall Space Flight Center (MSFC), in association with the NASA Jet Propulsion Laboratory (JPL). The TSTO vehicle features two solid rocket motors, one powering each stage. Their thrust vectors are controlled with Thrust Vector Control (TVC) systems consisting of independent electromechanical actuators acting on gimballed nozzles. The vehicle is designed to deliver up to 0.47kg of Martian samples to a Mars circular orbit of 343km at 27° inclination. Due to the unique environmental conditions that this vehicle is required to operate in, the subsystem design teams were compelled to develop creative and unorthodox designs to ensure a successful mission. The detailed design and analysis of these subsystems are discussed in this paper and include topics on the MAV Guidance, Navigation, and Control (GNC); structures and mechanisms; integrated vehicle thermal; avionics and flight software; a hydrazine-based Reaction Control System (RCS); aerosciences; and vehicle assembly, integration, and test (AI&T) considerations, among others. Following the conclusion of the MAV DAC-0.0, additional alternative architecture concepts were also studied to further reduce the mass of the overall system. The results of these studies will also be examined in this paper.

Darius Yaghoubi↗
NASA NTRSDate not supplied

Integrated Design Results for the MSR DAC-0.0 Mars Ascent Vehicle

The NASA Mars Sample Return (MSR) Campaign endeavors to return Martian regolith, rock, and atmospheric samples to Earth for scientific study. One of many significant challenges to overcome in the return of thesesamples lies in transporting them from the Martian surface to space. In order to surmount this challenge, the Campaign has conceptualized the need for a Mars Ascent Vehicle (MAV) to perform this function and deliver Martian samples to orbit. There, the samples will be ejected and captured by a separate spacecraft for return to Earth. Many concepts for a MAV have existed in the past, but it has not been until now that an integrated, detailed design solution has been developed and analyzed. Preliminary assessments of the initial architecture examined multiple methods of propulsion. The team ultimately determined that a Two Stage to Orbit (TSTO) solid propulsion vehicle would provide the most effective performance and be the most technologically ready to support this mission. Following the decision to adopt a TSTO solid propelled vehicle, the first official Design Analysis Cycle, DAC-0.0, was performed in Spring 2020 to formally advance the fidelity of the vehicle to a maturity level acceptable for NASA Key Decision Point A (KDP-A). This paper describes the resultant MAV design concept developed as part of the DAC-0.0 study by the NASA Marshall Space Flight Center (MSFC), in association with the NASA Jet Propulsion Laboratory (JPL). The TSTO vehicle features two solid rocket motors, one powering each stage. Their thrust vectors are controlled with Thrust Vector Control (TVC) systems consisting of independent electromechanical actuators acting on gimballed nozzles. The vehicle is designed to deliver up to 0.47kg of Martian samples to a Mars circular orbit of 343km at 27° inclination. Due to the unique environmental conditions that this vehicle is required to operate in, the subsystem design teams were compelled to develop creative and unorthodox designs to ensure a successful mission. The detailed design and analysis of these subsystems are discussed in this paper and include topics on the MAV Guidance, Navigation, and Control (GNC); structures and mechanisms; integrated vehicle thermal; avionics and flight software; a hydrazine-based Reaction Control System (RCS); aerosciences; and vehicle assembly, integration, and test (AI&T) considerations, among others. Following the conclusion of the MAV DAC-0.0, additional alternative architecture concepts were also studied to further reduce the mass of the overall system.

Mars↗
NASA NTRS1995

Propulsion Controlled Aircraft design and development

This paper describes the design, development, and ground testing of the propulsion controlled aircraft (PCA) flight control system. A backup flight control system which uses only engine thrust, the PCA system utilizes collective and differential thrust changes to steer an aircraft that experiences partial or complete failure of the hydraulically actuated control surfaces. The objective of the program was to investigate, in flight, the throttles-only control capability of the F-15, using manual control, and also an augmented PCA mode in which computer-controlled thrust was used for flight control. The objective included PCA operation in up-and-away flight and, if performance was adequate, a secondary objective to make actual PCA landings. The PCA design began with a feasibility study which evaluated many control law designs. The study was done using off-line control analysis, simulation, and on-line manned flight simulator tests. Control laws, cockpit displays, and cockpit controls were evaluated by NASA test pilots. A flight test baseline configuration was selected based on projected flight performance, applicability to transport and fighter aircraft, and funding costs. During the PCA software and hardware development, the initial design was updated as data became available from throttle-only flight experiments conducted by NASA on the F-15. This information showed basic airframe characteristics that were not observed in the F-15 flight simulator and resulted in several design changes. After the primary objectives of the PCA flight testing were accomplished, additional PCA modes of operation were developed and implemented. The evolution of the PCA system from the initial feasibility study, control law design, simulation, hardware-in-the-loop tests, pilot-in-the-loop tests, and ground tests is presented.

Wells, Edward A.↗
NASA NTRS1990

System testing of a production Ada (trademark) project: The GRODY study

The use of the Ada language and design methodologies that utilize its features has a strong impact on all phases of the software development project lifecycle. At the National Aeronautics and Space Administration/Goddard Space Flight Center (NASA/GSFC), the Software Engineering Laboratory (SEL) conducted an experiment in parallel development of two flight dynamics systems in FORTRAN and Ada. The teams found some qualitative differences between the system test phases of the two projects. Although planning for system testing and conducting of tests were not generally affected by the use of Ada, the solving of problems found in system testing was generally facilitated by Ada constructs and design methodology. Most problems found in system testing were not due to difficulty with the language or methodology but to lack of experience with the application.

Seigle, Jeffrey↗
NASA NTRS2015

Flight Testing of Terrain-Relative Navigation and Large-Divert Guidance on a VTVL Rocket

Since 2011, the Autonomous Descent and Ascent Powered-Flight Testbed (ADAPT) has been used to demonstrate advanced descent and landing technologies onboard the Masten Space Systems (MSS) Xombie vertical-takeoff, vertical-landing suborbital rocket. The current instantiation of ADAPT is a stand-alone payload comprising sensing and avionics for terrain-relative navigation and fuel-optimal onboard planning of large divert trajectories, thus providing complete pin-point landing capabilities needed for planetary landers. To this end, ADAPT combines two technologies developed at JPL, the Lander Vision System (LVS), and the Guidance for Fuel Optimal Large Diverts (G-FOLD) software. This paper describes the integration and testing of LVS and G-FOLD in the ADAPT payload, culminating in two successful free flight demonstrations on the Xombie vehicle conducted in December 2014.

ADAPT↗
NASA NTRS1987

Guidance simulation and test support for differential GPS flight experiment

Three separate tasks which supported the test preparation, test operations, and post test analysis of the NASA Ames flight test evaluation of the differential Global Positioning System (GPS) are presented. Task 1 consisted of a navigation filter design, coding, and testing to optimally make use of GPS in a differential mode. The filter can be configured to accept inputs from external censors such as an accelerometer and a barometric or radar altimeter. The filter runs in real time onboard a NASA helicopter. It processes raw pseudo and delta range measurements from a single channel sequential GPS receiver. The Kalman filter software interfaces are described in detail, followed by a description of the filter algorithm, including the basic propagation and measurement update equations. The performance during flight tests is reviewed and discussed. Task 2 describes a refinement performed on the lateral and vertical steering algorithms developed on a previous contract. The refinements include modification of the internal logic to allow more diverse inflight initialization procedures, further data smoothing and compensation for system induced time delays. Task 3 describes the TAU Corp participation in the analysis of the real time Kalman navigation filter. The performance was compared to that of the Z-set filter in flight and to the laser tracker position data during post test analysis. This analysis allowed a more optimum selection of the parameters of the filter.

Geier, G. J.↗
NASA NTRS1983

Real-time flutter analysis of an active flutter-suppression system on a remotely piloted research aircraft

Flight flutter-test results of the first aeroelastic research wing (ARW-1) of NASA's drones for aerodynamic and structural testing program are presented. The flight-test operation and the implementation of the active flutter-suppression system are described as well as the software techniques used to obtain real-time damping estimates and the actual flutter testing procedure. Real-time analysis of fast-frequency aileron excitation sweeps provided reliable damping estimates. The open-loop flutter boundary was well defined at two altitudes; a maximum Mach number of 0.91 was obtained. Both open-loop and closed-loop data were of exceptionally high quality. Although the flutter-suppression system provided augmented damping at speeds below the flutter boundary, an error in the implementation of the system resulted in the system being less stable than predicted. The vehicle encountered system-on flutter shortly after crossing the open-loop flutter boundary on the third flight and was lost. The aircraft was rebuilt. Changes made in real-time test techniques are included.

Gilyard, G. B.↗
NASA NTRS1977

Data processing system and interfacing elements time base analysis

The processing of time in the Orbiter System Services software and the associated facilities provided to the user community are described. The descriptions are directed toward showing the functional intent of the design rather than the actual implementation. Simplified flow diagrams are included. Based upon detailed analysis of a preliminary review copy of the Approach and Landing Test (ALT) System Software Detailed Design Specification and the Program Listings for Version 17 Prime, the processing of time has the potential for error free operations. The processing of time is not expected to change between ALT and the Operational Flight Test (OFT) other than differences in value of some constants for control and limit checking. Due to the dynamic nature of onboard time processing and its criticality to the successful operation of the orbiter, it is recommended that a comprehensive list of external variables, their locations, initial values, and a 'where used' listing be produced, as a by-product of the link edit process, for all non-HAL coding. In addition, a careful review of the verification test procedures for the System Services time-related software is recommended.

Blackburn, J. D.↗
NASA NTRS2003

The Successful Development of an Automated Rendezvous and Capture (AR&C) System for the National Aeronautics and Space Administration

During the 1990's, the Marshall Space Flight Center (MSFC) conducted pioneering research in the development of an automated rendezvous and capture/docking (AR&C) system for U.S. space vehicles. Development and demonstration of a rendezvous sensor was identified early in the AR&C Program as the critical enabling technology that allows automated proximity operations and docking. A first generation rendezvous sensor, the Video Guidance Sensor (VGS), was developed and successfully flown on STS-87 and STS-95, proving the concept of a video- based sensor. A ground demonstration of the entire system and software was successfully tested. Advances in both video and signal processing technologies and the lessons learned from the two successful flight experiments provided a baseline for the development, by the MSFC, of a new generation of video based rendezvous sensor. The Advanced Video Guidance Sensor (AGS) has greatly increased performance and additional capability for longer-range operation with a new target designed as a direct replacement for existing ISS hemispherical reflectors.

Roe, Fred D.↗
NASA NTRS1981

F-8C adaptive control law refinement and software development

An explicit adaptive control algorithm based on maximum likelihood estimation of parameters was designed. To avoid iterative calculations, the algorithm uses parallel channels of Kalman filters operating at fixed locations in parameter space. This algorithm was implemented in NASA/DFRC's Remotely Augmented Vehicle (RAV) facility. Real-time sensor outputs (rate gyro, accelerometer, surface position) are telemetered to a ground computer which sends new gain values to an on-board system. Ground test data and flight records were used to establish design values of noise statistics and to verify the ground-based adaptive software.

Hartmann, G. L.↗
NASA NTRS1996

Lessons learned: DC-X

The DC-X was conceived and developed specifically to lay the ground work for significantly lowering the cost of space operations. The system design was based on an initial set of program goals and a finite, limited set of resources. The goal in its simplest terms was to demonstrate vertical landing after rotation of the vehicle from a nose-first to an engines-first altitude. Finite resources actually drove the selection of a robust design to reduce fabrication and preflight testing costs. The result was a system with a large amount of flexibility which allowed expansion of the test goals as the system, and test program, evolved. The use of the vehicle flight computer interfacing with the ground control system for flight crew training was also not an initial concept. However, by defining an architecture for the system control modes which allowed additions and modifications as learning progressed, the 6 DOF codes used for flight controls software development were transported to the operating system to be used in a simulated flight mode. Flight data reduction was also greatly improved as the program progressed, and the data needs and presentation were refined. The software, avionics hardware, and the FOCC system development proceeded ahead of the vehicle, primarily because most of the hardware elements were existing at the outset of the program. The Built-in-Test (BIT) for avionics and propulsion systems were adequate. Particularly the flight readiness system which verified the vehicle health after engine start and before throttle-up for flight.

Steinmeyer, D. A.↗