SEARCH · Search NASA
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.
Space transportation avionics technology operational efficiency issues are presented in viewgraph form. Information is given on ascent flight design, autonomous spacecraft control, operations management systems, advanced mission control, telerobotics/telepresence, advanced software integration, advanced test/checkout systems, advanced training systems, and systems monitoring.
The Microcomputer Spacecraft Thermal Analysis Routines (MSTAR) software package is being developed for NASA/Goddard Space Flight Center by Swales and Associates, Inc. (S&AI). In December 1992, S&AI was awarded a phase I Small Business Inovative Research contract fronm NASA to develop a microcomputer based thermal analysis program to replace the current SSPTA and TRASYS programs. Phase I consists of a six month effort which will focus on developing geometric model generation and visualization capabilities using a graphical user interface (GUI). The information contained in this paper encompasses the work performed during the Phase I development cycle; with emphasis on the development of the graphical user interface (GUI). This includes both the theory behind and specific examples of how the MSTAR GUI was implemented. Furthermore, this report discusses new applications and enhancements which will improve the capabilities and commercialization of the MSTAR program.
Code to estimate position and attitude of a spacecraft or aircraft belongs to the most safety-critical parts of flight software. The complex underlying mathematics and abundance of design details make it error-prone and reliable implementations costly. AutoFilter is a program synthesis tool for the automatic generation of state estimation code from compact specifications. It can automatically produce additional safety certificates which formally guarantee that each generated program individually satisfies a set of important safety policies. These safety policies (e.g.. array-bounds, variable initialization) form a core of properties which are essential for high-assurance software. Here we describe the AutoFilter system and its certificate generator and compare our approach to the static analysis tool PolySpace.
For fifteen years, the science mission of the Hubble Space Telescope (HST) required using at least three of the six on-board rate gyros for attitude control. Failed gyros were eventually replaced through Space Shuttle Servicing Missions. The tragic loss of the Space Shuttle Columbia has resulted in the cancellation of all planned Shuttle based missions to HST. While a robotic servicing mission is currently being planned instead, controlling with alternate sensors to replace failed gyros can extend the HST science gathering until a servicing mission can be performed, and also extend science at HST's end of life. Additionally, sufficient performance may allow a permanent transition to operations with less than 3 gyros (by intentionally turning off working gyros saving them for later use) allowing for an even greater science mission extension. To meet this need, a Two Gyro Science (TGS) mode has been designed and implemented using magnetometers (Magnetic Sensing System - MSS), Fixed Head Star Trackers (FHSTs), and Fine Guidance Sensors (FGSs) to control vehicle rate about the missing gyro input axis. The development of the TGS capability is the largest re-design of HST operations undertaken, since it affects several major spacecraft subsystems, the most heavily being the Pointing Control System (PCS) and Flight Software (FSW). Additionally, and equally important, are the extensive modifications and enhancements of the Planning and Scheduling system which must now be capable of scheduling science observations while taking into account several new constraints imposed by the TGS operational modes (such as FHST availability and magnetic field geometry) that will impact science gathering efficiency and target availability. This paper discusses the systems engineering design, development, and performance of the TGS mode, now in its final stages of completion.
For fifteen years, the science mission of the Hubble Space Telescope (HST) required using at least three of the six on-board rate gyros for attitude control. Failed gyros were eventually replaced through Space Shuttle Servicing Missions. The tragic loss of the Space Shuttle Columbia has resulted in the cancellation of all planned Shuttle based missions to HST. While a robotic servicing mission is currently being planned instead, controlling with alternate sensors to replace failed gyros can extend the HST science gathering until a servicing mission can be performed, and also extend science at HST s end of life. Additionally, sufficient performance may allow a permanent transition to operations with less than 3 gyros (by intentionally turning off working gyros saving them for later use) allowing for an even greater science mission extension. To meet this need, a Two Gyro Science (TGS) mode has been designed and implemented using magnetometers (Magnetic Sensing System - MSS), Fixed Head Star Trackers (FHSTs), and Fine Guidance Sensors (FGSs) to control vehicle rate about the missing gyro input axis. The development of the TGS capability is the largest re-design of HST operations undertaken, since it affects several major spacecraft subsystems, the most heavily being the Pointing Control System (PCS) and Flight Software (FSW). Additionally, and equally important, are the extensive modifications and enhancements of the Planning and Scheduling system which must now be capable of scheduling science observations while taking into account several new constraints imposed by the TGS operational modes (such as FHST availability and magnetic field geometry) that will impact science gathering efficiency and target availability. This paper discusses the systems engineering design, development, and performance of the TGS mode, now in its final stages of completion.
The Hubble Space Telescope (HST) was launched on April 24 1990, with an expected lifespan of 15 years. Central to the spacecraft design was the concept of a series of on-orbit shuttle servicing missions permitting astronauts to replace failed equipment, update the scientific instruments and keep the HST at the forefront of astronomical discoveries. One key to the success of the Hubble mission has been the robust Safing systems designed to monitor the performance of the observatory and to react to keep the spacecraft safe in the event of equipment anomaly. The spacecraft Safing System consists of a range of software tests in the primary flight computer that evaluate the performance of mission critical hardware, safe modes that are activated when the primary control mode is deemed inadequate for protecting the vehicle, and special actions that the computer can take to autonomously reconfigure critical hardware. The HST Safing System was structured to autonomously detect electrical power system, data management system, and pointing control system malfunctions and to configure the vehicle to ensure safe operation without ground intervention for up to 72 hours. There is also a dedicated safe mode computer that constantly monitors a keep-alive signal from the primary computer. If this signal stops, the safe mode computer shuts down the primary computer and takes over control of the vehicle, putting it into a safe, low-power configuration. The HST Safing system has continued to evolve as equipment has aged, as new hardware has been installed on the vehicle, and as the operation modes have matured during the mission. Along with the continual refinement of the limits used in the safing tests, several new tests have been added to the monitoring system, and new safe modes have been added to the flight software. This paper will focus on the evolution of the HST Safing System and Safing tests, and the importance of this evolution to prolonging the science operations of the telescope.
Space Technology 7 Disturbance Reduction System (ST7-DRS) is a NASA technology demonstration payload as part of the ESA LISA Pathfinder (LPF) mission, which launched on December 3, 2015. The ST7-DRS payload includes colloid microthrusters as part of a drag-free dynamic control system (DCS) hosted on an integrated avionics unit (IAU) with spacecraft attitude and test mass position provided by the LPF spacecraft computer and the highly sensitive gravitational reference sensor (GRS) as part of the LISA Technology Package (LTP). The objective of the DRS was to validate two technologies: colloid micro-Newton thrusters (CMNT) to provide low-noise control capability of the spacecraft, and drag-free flight control. The CMNT were developed by Busek Co., Inc., in a partnership with NASA Jet Propulsion Laboratory (JPL), and the DCS algorithms and flight software were developed at NASA Goddard Space Flight Center (GSFC). ST7-DRS demonstrated drag-free operation with 10nmHz level precision spacecraft position control along the primary axis of the LTP using eight CMNTs that provided 5-30 N each with 0.1 N precision. The DCS and CMNTs performed as required and as expected from ground test results, meeting all Level 1 requirements based on on-orbit data and analysis. DRS microthrusters operated for 2400 hours in flight during commissioning activities, a 90-day experiment and the extended mission. This mission represents the first validated demonstration of electrospray thrusters in space, providing precision spacecraft control and drag-free operation in a flight environment with applications to future gravitational wave observatories like LISA.
Ever since Explorer-1, the United States' first Earth satellite, was developed and launched in 1958, JPL has developed many more spacecraft, including landers and orbiters. While these spacecraft vary greatly in their missions, capabilities,and destination, they all have something in common. All of the components of these spacecraft had to be comprehensively tested. While thorough testing is important to mitigate risk, it is also a very expensive and time consuming process. Thankfully,since virtually all of the software testing procedures for SMAP are computer controlled, these procedures can be automated. Most people testing SMAP flight software (FSW) would only need to write tests that exercise specific requirements and then check the filtered results to verify everything occurred as planned. This gives developers the ability to automatically launch tests on the testbed, distill the resulting logs into only the important information, generate validation documentation, and then deliver the documentation to management. With many of the steps in FSW testing automated, developers can use their limited time more effectively and can validate SMAP FSW modules quicker and test them more rigorously. As a result of the various benefits of automating much of the testing process, management is considering this automated tools use in future FSW validation efforts.
As part of its effort to develop the flight dynamics distributed system (FDDS), NASA established a program for the continual monitoring of the developments in computer and software technologies, and for assessing the significance of constructing and operating spacecraft ground data systems. In relation to this, technology trends in the computing industry are reviewed, exploring their significance for the spacecraft ground support industry. The technologies considered are: hardware; object computing; Internet; automation, and software development. The ways in which these technologies have affected the industry are considered.
The Swift spacecraft has three Two-Axis-Rate-Assemblies (TARAs) (designated as TARA 1, TARA 2, and TARA 3, and generically referred to as gyros) which until March of 2024 were all used in rate estimation as an operational workaround (dubbed “corrector-gyro”) of a software defect discovered in 2007. TARA 1 performance degraded throughout 2023 and 2024, making it an unreliable rate source. It was determined that shifting TARA 1 to be the corrector-gyro and using mainly TARAs 2 and 3, with the existing flight software (FSW) defect, would not meet performance requirements for science operations. Rather the FSW was patched to remove the defect found in 2007. This patch was delivered by the vendor in 2009, but was not fully tested or installed at that time. A decision was made in 2024 to install the patch despite limited simulation and testing capabilities. The problem facing the team was to come up with a set of alignment parameters that would work with the new patch, using data from the spacecraft operating normally in the old configuration. Calibration activities would have been possible in either the old or new FSW configuration, but were ultimately deemed unnecessary, saving staff time and pre-serving time on the spacecraft for science data collection. This paper describes the old and new FSW configurations related to gyro processing and alignment, and how the raw gyro and star tracker data from normal operation were used with a multidimensional unconstrained nonlinear minimization in MATLAB (Nelder-Mead1) to produce a fully calibrated set of gyro alignment parameters compatible with the patched FSW. Flight data is presented showing that not only did the process work, it improved performance significantly, rivaling the best slew performance of the mission to date.
The Adaptive Instrument Module (AIM) will be the first true demonstration of reconfigurable computing with field-programmable gate arrays (FPGAs) in space, enabling the 'brain' of the system to evolve or adapt to changing requirements. In partnership with NASA Goddard Space Flight Center and the Australian Cooperative Research Centre for Satellite Systems (CRC-SS), APL has built the flight version to be flown on the Australian university-class satellite FEDSAT. The AIM provides satellites the flexibility to adapt to changing mission requirements by reconfiguring standardized processing hardware rather than incurring the large costs associated with new builds. This ability to reconfigure the processing in response to changing mission needs leads to true evolveable computing, wherein the instrument 'brain' can learn from new science data in order to perform state-of-the-art data processing. The development of the AIM is significant in its enormous potential to reduce total life-cycle costs for future space exploration missions. The advent of RAM-based FPGAs whose configuration can be changed at any time has enabled the development of the AIM for processing tasks that could not be performed in software. The use of the AIM enables reconfiguration of the FPGA circuitry while the spacecraft is in flight, with many accompanying advantages. The AIM demonstrates the practicalities of using reconfigurable computing hardware devices by conducting a series of designed experiments. These include the demonstration of implementing data compression, data filtering, and communication message processing and inter-experiment data computation. The second generation is the Adaptive Processing Template (ADAPT) which is further described in this paper. The next step forward is to make the hardware itself adaptable and the ADAPT pursues this challenge by developing a reconfigurable module that will be capable of functioning efficiently in various applications. ADAPT will take advantage of radiation tolerant RAM-based field programmable gate array (FPGA) technology to develop a reconfigurable processor that combines the flexibility of a general purpose processor running software with the performance of application specific processing hardware for a variety of high performance computing applications.
Orbital Operations Simulator, OOS, computer program developed to implement mathematical models of complex outer-space vehicular systems and be "testbed" for new flight software. Has multi-vehicular-simulation capability to model on-orbit proximity and docking operations. Version 1.0, with its Prepare Processor and User Interface Shell designed to be true multivehicle dynamic simulator with capability to change mathematical models of spacecraft subsystems easily. Written in K & R standard C, LEX, and YACC languages and operates under System V shell.
The results of the first phase of Research on an Expert System for Database Operation of Simulation/Emulation Math Models, is described. Techniques from artificial intelligence (AI) were to bear on task domains of interest to NASA Marshall Space Flight Center. One such domain is simulation of spacecraft attitude control systems. Two related software systems were developed to and delivered to NASA. One was a generic simulation model for spacecraft attitude control, written in FORTRAN. The second was an expert system which understands the usage of a class of spacecraft attitude control simulation software and can assist the user in running the software. This NASA Expert Simulation System (NESS), written in LISP, contains general knowledge about digital simulation, specific knowledge about the simulation software, and self knowledge.
Cooperative missions in Earth orbit can be facilitated by developing a strategy to regulate the manner in which vehicles interact in orbit. One means of implementing such a strategy is to utilize a control zones technique that assigns different types of orbital operations to specific regions of space surrounding a vehicle. Considered here are issues associated with developing a control zones technique to regulate the interactions of spacecraft in proximity to a manned vehicle. Technical and planning issues, flight hardware and software issues, mission management parameter, and other constraints are discussed. Also covered are manned and unmanned vehicle operations, and manual versus automated flight control. A review of the strategies utilized by the Apollo Soyuz Test Project and the Space Station Freedom Program is also presented.
Cooperative missions in earth orbit can be facilitated by developing a strategy to regulate the manner in which vehicles interact in orbit. One means of implementing such a strategy is to utilize a control zones technique that assigns different types of orbital operations to specific regions of space surrounding a vehicle. Considered here are issues associated with developing a control zones technique to regulate the interactions of spacecraft in proximity to a manned vehicle. Technical and planning issues, flight hardware and software issues, mission management parameter, and other constraints are discussed. Also covered are manned and unmanned vehicle operations, and manual versus automated flight control. A review of the strategies utilized by the Apollo Soyuz Test Project and the Space Station Freedom Program is also presented.
Mars Global Surveyor (MGS) avionics system architecture comprises much of the electronics on board the spacecraft: electrical power, attitude and articulation control, command and data handling, telecommunications, and flight software. Schedule and cost constraints dictated a mix of new and inherited designs, especially hardware upgrades based on findings of the Mars Observer failure review boards.
Scheduling the coverage of a planet by scientific instruments on board spacecrafts under observational constraints is central in a significant number of current and future missions for the exploration of the solar system. In this paper, we describe the components and algorithms of a software used to study early-phase mission design or to schedule daily operations of currently in-flight spacecraft. The scheduling problem at hand is usually a large combinatorial problem. A discretization process is described and several ordering algorithms are designed and compared. Experiments show that high-quality schedules can be produced by approaches combining reasoning about rolling, coverage and priorities.
This paper discusses the knowledge acquisition issues involved in transitioning their novel technology in to space flight software, developing the planer in the context of a large software projet and completing the work under a compressed development schedule.