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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 937 records · Page 52

All sources NASA NTRS DOE OSTI

NASA NTRS2009

Desktop Application Program to Simulate Cargo-Air-Drop Tests

The DSS Application is a computer program comprising a Windows version of the UNIX-based Decelerator System Simulation (DSS) coupled with an Excel front end. The DSS is an executable code that simulates the dynamics of airdropped cargo from first motion in an aircraft through landing. The bare DSS is difficult to use; the front end makes it easy to use. All inputs to the DSS, control of execution of the DSS, and postprocessing and plotting of outputs are handled in the front end. The front end is graphics-intensive. The Excel software provides the graphical elements without need for additional programming. Categories of input parameters are divided into separate tabbed windows. Pop-up comments describe each parameter. An error-checking software component evaluates combinations of parameters and alerts the user if an error results. Case files can be created from inputs, making it possible to build cases from previous ones. Simulation output is plotted in 16 charts displayed on a separate worksheet, enabling plotting of multiple DSS cases with flight-test data. Variables assigned to each plot can be changed. Selected input parameters can be edited from the plot sheet for quick sensitivity studies.

Cuthbert, Peter↗

NASA NTRS2010

Analysis of Flash Lidar Field Test Data for Safe Lunar Landing

In May 2008, the Autonomous Landing and Hazard Avoidance Technology (ALHAT) Project conducted a helicopter field test of a commercial flash lidar to assess its applicability to safe lunar landing. The helicopter flew several flights, which covered a variety of slant ranges and viewing angles, over man-made and natural lunar-like terrains. The collected data were analyzed to assess the performance of the sensor and the performance of two algorithms: Hazard Detection (HD) and Hazard Relative Navigation (HRN). The collected flash lidar data were also used to validate a high fidelity flash lidar software model used in ALHAT Monte Carlo simulations. The field test results, combined with prior simulation results, advanced the technology readiness level of the HD algorithm to TRL 5 and the HRN algorithm to TRL 4.

hazard relative navigation↗

NASA NTRS2012

Fast Paced, Low Cost Projects at MSFC

What does an orbiting microsatellite, a robotic lander and a ruggedized camera and telescope have in common? They are all fast paced, low cost projects managed by Marshall Space Flight Center (MSFC) teamed with successful industry partners. MSFC has long been synonymous with human space flight large propulsion programs, engineering acumen and risk intolerance. However, there is a growing portfolio/product line within MSFC that focuses on these smaller, fast paced projects. While launching anything into space is expensive, using a managed risk posture, holding to schedule and keeping costs low by stopping at egood enough f were key elements to their success. Risk is defined as the possibility of loss or failure per Merriam Webster. The National Aeronautics and Space Administration (NASA) defines risk using procedural requirement 8705.4 and establishes eclasses f to discern the acceptable risk per a project. It states a Class D risk has a medium to significant risk of not achieving mission success. MSFC, along with industry partners, has created a niche in Class D efforts. How did the big, cautious MSFC succeed on these projects that embodied the antithesis of its heritage in human space flight? A key factor toward these successful projects was innovative industry partners such as Dynetics Corporation, University of Alabama in Huntsville (UAHuntsville), Johns Hopkins Applied Physics Laboratory (JHU APL), Teledyne Brown Engineering (TBE), Von Braun Center for Science and Innovation (VCSI), SAIC, and Jacobs. Fast Affordable Satellite Technology (FastSat HSV01) is a low earth orbit microsatellite that houses six instruments with the primary scientific objective of earth observation and technology demonstration. The team was comprised of Dynetics, UAHuntsvile, SAIC, Goddard Space Flight Center (GSFC) and VCSI with the United States Air Force Space Test Program as the customer. The team completed design, development, manufacturing, environmental test and integration in one year. FastSat HSV01 also deployed a Poly Picosatellite Orbital Deployer (PPOD) for a separate nano ]satellite class spacecraft (Cubesat: Nano Sail Demonstration) in partnership with Ames Research Center. The Robotic lunar lander is a MSFC JHU APL partnership that led to the development of a flexible architecture for landers to support robotic missions to a wide range of lunar and asteroid destinations. The team started with the goal of meeting NASA agency directives that led to the creation of a test bed focusing on GN&C and software to demonstrate the descent and landing on any airless body for the final 30 to 60 meters. The team created a complex technology demonstration as well as Guidance Control and Navigation (GN&C) algorithms providing autonomous control of the lander. The team uses a green propellant of 90% hydrogen peroxide and has completed 18 successful test flights. The International Space Station (ISS) SERVIR Environmental Research and Visualization System (ISERV) is a technology demonstration payload to assist the SERVIR project with environmental monitoring for disaster relief and humanitarian efforts. The ISERV project was a partnership with TBE. The ISERV payload consists of a commercial off the shelf camera, telescope, and MSFC developed power distribution box and interfaces on ISS with the Window Observational Research Facility in the US Lab. MSFC has identified three key areas that enabled the low cost mission success to include culture, partnering, and cost/schedule control. This paper will briefly discuss these three Class D efforts, FastSat HSV-01, the Robotic Lunar Lander and the ISERV camera system, the lessons learned, their successes and challenges.

Watson-Morgan, Lisa↗

NASA NTRS2011

Parametric Testing of Launch Vehicle FDDR Models

For the safe operation of a complex system like a (manned) launch vehicle, real-time information about the state of the system and potential faults is extremely important. The on-board FDDR (Failure Detection, Diagnostics, and Response) system is a software system to detect and identify failures, provide real-time diagnostics, and to initiate fault recovery and mitigation. The ERIS (Evaluation of Rocket Integrated Subsystems) failure simulation is a unified Matlab/Simulink model of the Ares I Launch Vehicle with modular, hierarchical subsystems and components. With this model, the nominal flight performance characteristics can be studied. Additionally, failures can be injected to see their effects on vehicle state and on vehicle behavior. A comprehensive test and analysis of such a complicated model is virtually impossible. In this paper, we will describe, how parametric testing (PT) can be used to support testing and analysis of the ERIS failure simulation. PT uses a combination of Monte Carlo techniques with n-factor combinatorial exploration to generate a small, yet comprehensive set of parameters for the test runs. For the analysis of the high-dimensional simulation data, we are using multivariate clustering to automatically find structure in this high-dimensional data space. Our tools can generate detailed HTML reports that facilitate the analysis.

Schumann, Johann↗

NASA NTRS2003

Experiences with Testing the Largest Ground System NASA Has Ever Built

In the 1980s, the National Aeronautics and Space Administration (NASA) embarked upon a major Earth-focused program called Mission to Planet Earth. The Goddard Space Flight Center (GSFC) was selected to manage and develop a key component - the Earth Observing System (EOS). The EOS consisted of four major missions designed to monitor the Earth. The missions included 4 spacecraft. Terra (launched December 1999), Aqua (launched May 2002), ICESat (Ice, Cloud, and Land Elevation Satellite, launched January 2003), and Aura (scheduled for launch January 2004). The purpose of these missions was to provide support for NASA s long-term research effort for determining how human-induced and natural changes affect our global environment. The EOS Data and Information System (EOSDIS), a globally distributed, large-scale scientific system, was built to support EOS. Its primary function is to capture, collect, process, and distribute the most voluminous set of remotely sensed scientific data to date estimated to be 350 Gbytes per day. The EOSDIS is composed of a diverse set of elements with functional capabilities that require the implementation of a complex set of computers, high-speed networks, mission-unique equipment, and associated Information Technology (IT) software along with mission-specific software. All missions are constrained by schedule, budget, and staffing resources, and rigorous testing has been shown to be critical to the success of each mission. This paper addresses the challenges associated with the planning, test definition. resource scheduling, execution, and discrepancy reporting involved in the mission readiness testing of a ground system on the scale of EOSDIS. The size and complexity of the mission systems supporting the Aqua flight operations, for example, combined with the limited resources available, prompted the project to challenge the prevailing testing culture. The resulting success of the Aqua Mission Readiness Testing (MRT) program was due in no small measure to re-structuring the traditional programmatic and technical approach to a more efficient and robust program. Programmatically, it meant gaining the endorsement, commitment, and cooperation of the numerous subsystem element managers and other stakeholder organizations. Technically, it required an MRT program that was agile, could rapidly adapt to requirements changes, and was flexible in its overall approach. Furthermore, this paper addresses the following questions: 1. What are the key ingredients (e.g., test tools, organization) needed to conduct a successful MRT program? 2. What distinguishes EOS MRT from the traditional system testing approach? 3. Where should the focus of testing be since it is infeasible to test every element or subsystem? 4. How can MRT be applied effectively to other systems or missions? To provide answers to these questions, this paper relies heavily on real-life, hands-on experiences ("lessons learned") gained during mission readiness testing of the Terra ground system and, most recently, the Aqua and ICESat missions. Moreover, this paper explores how lessons learned were turned into lessons applied for the upcoming Aura mission. Although derived from the EOS missions, MRT techniques and strategies can be applied to enhance the testing of other missions.

Lehtonen, Ken↗

NASA NTRS2011

Ares I-X First Stage Separation Loads and Dynamics Reconstruction

The Ares I-X flight test provided NASA with the opportunity to test hardware and gather critical data to ensure the success of future Ares I flights. One of the primary test flight objectives was to evaluate the environment during First Stage separation to better understand the conditions that the J-2X second stage engine will experience at ignition [1]. A secondary objective was to evaluate the effectiveness of the stage separation motors. The Ares I-X flight test vehicle was successfully launched on October 29, 2009, achieving most of its primary and secondary test objectives. Ground based video camera recordings of the separation event appeared to show recontact of the First Stage and the Upper Stage Simulator followed by an unconventional tumbling of the Upper Stage Simulator. Closer inspection of the videos and flight test data showed that recontact did not occur. Also, the motion during staging was as predicted through CFD analysis performed during the Ares I-X development. This paper describes the efforts to reconstruct the vehicle dynamics and loads through the staging event by means of a time integrated simulation developed in TREETOPS, a multi-body dynamics software tool developed at NASA [2]. The simulation was built around vehicle mass and geometry properties at the time of staging and thrust profiles for the first stage solid rocket motor as well as for the booster deceleration motors and booster tumble motors. Aerodynamic forces were determined by models created from a combination of wind tunnel testing and CFD. The initial conditions such as position, velocity, and attitude were obtained from the Best Estimated Trajectory (BET), which is compiled from multiple ground based and vehicle mounted instruments. Dynamic loads were calculated by subtracting the inertial forces from the applied forces. The simulation results were compared to the Best Estimated Trajectory, accelerometer flight data, and to ground based video.

Demory, Lee↗

NASA NTRS1985

Study of fault tolerant software technology for dynamic systems

The major aim of this study is to investigate the feasibility of using systems-based failure detection isolation and compensation (FDIC) techniques in building fault-tolerant software and extending them, whenever possible, to the domain of software fault tolerance. First, it is shown that systems-based FDIC methods can be extended to develop software error detection techniques by using system models for software modules. In particular, it is demonstrated that systems-based FDIC techniques can yield consistency checks that are easier to implement than acceptance tests based on software specifications. Next, it is shown that systems-based failure compensation techniques can be generalized to the domain of software fault tolerance in developing software error recovery procedures. Finally, the feasibility of using fault-tolerant software in flight software is investigated. In particular, possible system and version instabilities, and functional performance degradation that may occur in N-Version programming applications to flight software are illustrated. Finally, a comparative analysis of N-Version and recovery block techniques in the context of generic blocks in flight software is presented.

Caglayan, A. K.↗

NASA NTRS1989

Ada compiler evaluation on the Space Station Freedom Software Support Environment project

This paper describes the work in progress to select the Ada compilers for the Space Station Freedom Program (SSFP) Software Support Environment (SSE) project. The purpose of the SSE Ada compiler evaluation team is to establish the criteria, test suites, and benchmarks to be used for evaluating Ada compilers for the mainframes, workstations, and the realtime target for flight- and ground-based computers. The combined efforts and cooperation of the customer, subcontractors, vendors, academia and SIGAda groups made it possible to acquire the necessary background information, benchmarks, test suites, and criteria used.

Badal, D. L.↗

NASA NTRS2011

Development of a Smart Release Algorithm for Mid-Air Separation of Parachute Test Articles

The Crew Exploration Vehicle Parachute Assembly System (CPAS) project is currently developing an autonomous method to separate a capsule-shaped parachute test vehicle from an air-drop platform for use in the test program to develop and validate the parachute system for the Orion spacecraft. The CPAS project seeks to perform air-drop tests of an Orion-like boilerplate capsule. Delivery of the boilerplate capsule to the test condition has proven to be a critical and complicated task. In the current concept, the boilerplate vehicle is extracted from an aircraft on top of a Type V pallet and then separated from the pallet in mid-air. The attitude of the vehicles at separation is critical to avoiding re-contact and successfully deploying the boilerplate into a heatshield-down orientation. Neither the pallet nor the boilerplate has an active control system. However, the attitude of the mated vehicle as a function of time is somewhat predictable. CPAS engineers have designed an avionics system to monitor the attitude of the mated vehicle as it is extracted from the aircraft and command a release when the desired conditions are met. The algorithm includes contingency capabilities designed to release the test vehicle before undesirable orientations occur. The algorithm was verified with simulation and ground testing. The pre-flight development and testing is discussed and limitations of ground testing are noted. The CPAS project performed a series of three drop tests as a proof-of-concept of the release technique. These tests helped to refine the attitude instrumentation and software algorithm to be used on future tests. The drop tests are described in detail and the evolution of the release system with each test is described.

Moore, James W.↗

NASA NTRS2020

Command and Control System Automated Testing

To support the National Aeronautics and Space Administration’s (NASA) Space Launch System (SLS) rocket and the Orion capsule, designed to take humans back to the moon in 2024, Kennedy Space Center (KSC) has developed the Spaceport Command and Control System (SCCS) to monitor and control the launch. Within SCCS, the Launch Control System (LCS) is designed to allow console engineers to control and monitor the status of the launch and flight hardware, as well as issue commands to ground control systems and launch vehicles. The messaging software of LCS is responsible for handling the various data types that can be sent between the hardware and software components of the LCS. Since this system is interacting with numerous devices, controllers, and viewports in real time, the distribution of data across the system must be fast, but also reliable and accurate. To verify the accuracy and reliability of the system, developers on the project have created a set of tests to be performed that covers all operations allowed by the system. Given the extensive Application Programming Interface(API) provided by the messaging software, these unit tests are rather time-consuming and costly (in terms of man-hours) to perform. Therefore, an automated testing framework is used to perform supplemental tests automatically when updates are made to the code base.

Rebecca McFadden↗

NASA NTRS2017

Computational Design and Analysis of a Transonic Natural Laminar Flow Wing for a Wind Tunnel Model

A natural laminar flow (NLF) wind tunnel model has been designed and analyzed for a wind tunnel test in the National Transonic Facility (NTF) at the NASA Langley Research Center. The NLF design method is built into the CDISC design module and uses a Navier-Stokes flow solver, a boundary layer profile solver, and stability analysis and transition prediction software. The NLF design method alters the pressure distribution to support laminar flow on the upper surface of wings with high sweep and flight Reynolds numbers. The method addresses transition due to attachment line contamination/transition, Gortler vortices, and crossflow and Tollmien-Schlichting modal instabilities. The design method is applied to the wing of the Common Research Model (CRM) at transonic flight conditions. Computational analysis predicts significant extents of laminar flow on the wing upper surface, which results in drag savings. A 5.2 percent scale semispan model of the CRM NLF wing will be built and tested in the NTF. This test will aim to validate the NLF design method, as well as characterize the laminar flow testing capabilities in the wind tunnel facility.

Lynde, Michelle N.↗

NASA NTRS1990

What FM can offer DFCS design

The results of aircrafts and spacecrafts flight tests are reported. It is shown that the problems of Digital Flight Control Systems (DFCS) are the problems of systems whose complexity has exceeded the reach of the intellectual tools employed. It is also shown that intuition, experience, and techniques derived from mechanical and analog systems are insufficient for complex, integrated, digital systems. Formal Methods (FM) of computer science can offer DFCS systematic techniques for the construction of trustworthy software, including: techniques for the precise specification of requirements and the development of designs; systematic approaches to the design and structuring of distributed and concurrent systems; fault tolerance algorithms; and systematic methods of testing and analytic methods of verification.

Rushby, John↗

NASA NTRS2004

NASA Langley Research Center's Simulation-To-Flight Concept Accomplished through the Integration Laboratories of the Transport Research Facility

The Flight Simulation and Software Branch (FSSB) at NASA Langley Research Center (LaRC) maintains the unique national asset identified as the Transport Research Facility (TRF). The TRF is a group of facilities and integration laboratories utilized to support the LaRC's simulation-to-flight concept. This concept incorporates common software, hardware, and processes for both groundbased flight simulators and LaRC s B-757-200 flying laboratory identified as the Airborne Research Integrated Experiments System (ARIES). These assets provide Government, industry, and academia with an efficient way to develop and test new technology concepts to enhance the capacity, safety, and operational needs of the ever-changing national airspace system. The integration of the TRF enables a smooth continuous flow of the research from simulation to actual flight test.

Martinez, Debbie↗

NASA NTRS2007

Flight Testing an Iced Business Jet for Flight Simulation Model Validation

A flight test of a business jet aircraft with various ice accretions was performed to obtain data to validate flight simulation models developed through wind tunnel tests. Three types of ice accretions were tested: pre-activation roughness, runback shapes that form downstream of the thermal wing ice protection system, and a wing ice protection system failure shape. The high fidelity flight simulation models of this business jet aircraft were validated using a software tool called "Overdrive." Through comparisons of flight-extracted aerodynamic forces and moments to simulation-predicted forces and moments, the simulation models were successfully validated. Only minor adjustments in the simulation database were required to obtain adequate match, signifying the process used to develop the simulation models was successful. The simulation models were implemented in the NASA Ice Contamination Effects Flight Training Device (ICEFTD) to enable company pilots to evaluate flight characteristics of the simulation models. By and large, the pilots confirmed good similarities in the flight characteristics when compared to the real airplane. However, pilots noted pitch up tendencies at stall with the flaps extended that were not representative of the airplane and identified some differences in pilot forces. The elevator hinge moment model and implementation of the control forces on the ICEFTD were identified as a driver in the pitch ups and control force issues, and will be an area for future work.

Ratvasky, Thomas P.↗

NASA NTRS2017

UAV Inspection of Electrical Transmission Infrastructure with Path Conformance Autonomy and Lidar-Based Geofences NASA Report on UTM Reference Mission Flights at Southern Company Flights November 2016

Flights at low altitudes in close proximity to electrical transmission infrastructure present serious navigational challenges: GPS and radio communication quality is variable and yet tight position control is needed to measure defects while avoiding collisions with ground structures. To advance unmanned aerial vehicle (UAV) navigation technology while accomplishing a task with economic and societal benefit, a high voltage electrical infrastructure inspection reference mission was designed. An integrated air-ground platform was developed for this mission and tested in two days of experimental flights to determine whether navigational augmentation was needed to successfully conduct a controlled inspection experiment. The airborne component of the platform was a multirotor UAV built from commercial off-the-shelf hardware and software, and the ground component was a commercial laptop running open source software. A compact ultraviolet sensor mounted on the UAV can locate 'hot spots' (potential failure points in the electric grid), so long as the UAV flight path adequately samples the airspace near the power grid structures. To improve navigation, the platform was supplemented with two navigation technologies: lidar-to-polyhedron preflight processing for obstacle demarcation and inspection distance planning, and trajectory management software to enforce inspection standoff distance. Both navigation technologies were essential to obtaining useful results from the hot spot sensor in this obstacle-rich, low-altitude airspace. Because the electrical grid extends into crowded airspaces, the UAV position was tracked with NASA unmanned aerial system traffic management (UTM) technology. The following results were obtained: (1) Inspection of high-voltage electrical transmission infrastructure to locate 'hot spots' of ultraviolet emission requires navigation methods that are not broadly available and are not needed at higher altitude flights above ground structures. (2) The sensing capability of a novel airborne UV detector was verified with a standard ground-based instrument. Flights with this sensor showed that UAV measurement operations and recording methods are viable. With improved sensor range, UAVs equipped with compact UV sensors could serve as the detection elements in a self-diagnosing power grid. (3) Simplification of rich lidar maps to polyhedral obstacle maps reduces data volume by orders of magnitude, so that computation with the resultant maps in real time is possible. This enables real-time obstacle avoidance autonomy. Stable navigation may be feasible in the GPS-deprived environment near transmission lines by a UAV that senses ground structures and compares them to these simplified maps. (4) A new, formally verified path conformance software system that runs onboard a UAV was demonstrated in flight for the first time. It successfully maneuvered the aircraft after a sudden lateral perturbation that models a gust of wind, and processed lidar-derived polyhedral obstacle maps in real time. (5) Tracking of the UAV in the national airspace using the NASA UTM technology was a key safety component of this reference mission, since the flights were conducted beneath the landing approach to a heavily used runway. Comparison to autopilot tracking showed that UTM tracking accurately records the UAV position throughout the flight path.

Moore, Andrew J.↗

NASA NTRS1996

Parallelization of Rocket Engine System Software (Press)

The main goal is to assess parallelization requirements for the Rocket Engine Numeric Simulator (RENS) project which, aside from gathering information on liquid-propelled rocket engines and setting forth requirements, involve a large FORTRAN based package at NASA Lewis Research Center and TDK software developed by SUBR/UWF. The ultimate aim is to develop, test, integrate, and suitably deploy a family of software packages on various aspects and facets of rocket engines using liquid-propellants. At present, all project efforts by the funding agency, NASA Lewis Research Center, and the HBCU participants are disseminated over the internet using world wide web home pages. Considering obviously expensive methods of actual field trails, the benefits of software simulators are potentially enormous. When realized, these benefits will be analogous to those provided by numerous CAD/CAM packages and flight-training simulators. According to the overall task assignments, Hampton University's role is to collect all available software, place them in a common format, assess and evaluate, define interfaces, and provide integration. Most importantly, the HU's mission is to see to it that the real-time performance is assured. This involves source code translations, porting, and distribution. The porting will be done in two phases: First, place all software on Cray XMP platform using FORTRAN. After testing and evaluation on the Cray X-MP, the code will be translated to C + + and ported to the parallel nCUBE platform. At present, we are evaluating another option of distributed processing over local area networks using Sun NFS, Ethernet, TCP/IP. Considering the heterogeneous nature of the present software (e.g., first started as an expert system using LISP machines) which now involve FORTRAN code, the effort is expected to be quite challenging.

Cezzar, Ruknet↗

NASA NTRS2017

Dynamic Control System Mode Performance of the Space Technology-7 Disturbance Reduction System

The Space Technology-7 (ST-7) Disturbance Reduction System (DRS) is an experiment package aboard the European Space Agency (ESA) LISA Pathfinder spacecraft, launched on December 3, 2015. DRS consists of three primary components: Colloidal MicroNewton Thrusters (CMNTs), an Integrated Avionics Unit (IAU), and flight-software implementing the Command and Data Handling (C&DH) and Dynamic Control System (DCS) algorithms. The CMNTs were designed to provide thrust from 5 to 30 micro Newton, with thrust controllability and resolution of 0.1 micro Newton and thrust noise of 0.1 micro Newton/(square root of (Hz)) in the measurement band from 1-30 mHz. The IAU hosts the C&DH and DCS flight software, as well as interfaces with both the CMNT electronics and the LISA Pathfinder spacecraft. When in control, the DCS uses star tracker attitude data and capacitive or optically-measured position and attitude information from LISA Pathfinder and the LISA Technology Package (LTP) to control the attitude and position of the spacecraft and the two test masses inside the LTP. After completion of the nominal ESA LISA Pathfinder mission, the DRS experiment was commissioned followed by its nominal mission. DRS operations extended over the next five months, interspersed with station keeping, anomaly resolution, and periods where control was handed back to LISA Pathfinder for them to conduct further experiments. The primary DRS mission ended on December 6, 2016, with the experiment meeting all of its Level 1 requirements. The DCS, developed at the NASA Goddard Space Flight Center, consists of five spacecraft control modes and six test mass control modes, combined into six 'DRS Mission Modes'. Attitude Control and Zero-G were primarily used to control the spacecraft during initial handover and during many of the CMNT characterization experiments. The other Mission Modes, Drag Free Low Force, 18-DOF Transitional, and 18-DOF, were used to provide drag-free control of the spacecraft about the test masses. This paper will discuss the performance of these DCS spacecraft and test mass control modes. Flight data will be shown from each mode throughout the mission, both from nominal operations and during various flight experiments. The DCS team also made some changes to controller, filter, and limit parameters during operations; the motivation and results of these changes will be shown and discussed.

O'Donnell, James R., Jr.↗

NASA NTRS2004

Automated Attitude Sensor Calibration: Progress and Plans

This paper describes ongoing work a NASA/Goddard Space Flight Center to improve the quality of spacecraft attitude sensor calibration and reduce costs by automating parts of the calibration process. The new calibration software can autonomously preview data quality over a given time span, select a subset of the data for processing, perform the requested calibration, and output a report. This level of automation is currently being implemented for two specific applications: inertial reference unit (IRU) calibration and sensor alignment calibration. The IRU calibration utility makes use of a sequential version of the Davenport algorithm. This utility has been successfully tested with simulated and actual flight data. The alignment calibration is still in the early testing stage. Both utilities will be incorporated into the institutional attitude ground support system.

Sedlak, Joseph↗