Search NASA⌕ Search

SEARCH · Search NASA

Results for “Flight Control System Verification”

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 361 records · Page 20

Surface Landing Site Weather Analysis for NASA's Constellation Program

Weather information is an important asset for NASA's Constellation Program in developing the next generation space transportation system to fly to the International Space Station, the Moon and, eventually, to Mars. Weather conditions can affect vehicle safety and performance during multiple mission phases ranging from pre-launch ground processing of the Ares vehicles to landing and recovery operations, including all potential abort scenarios. Meteorological analysis is art important contributor, not only to the development and verification of system design requirements but also to mission planning and active ground operations. Of particular interest are the surface weather conditions at both nominal and abort landing sites for the manned Orion capsule. Weather parameters such as wind, rain, and fog all play critical roles in the safe landing of the vehicle and subsequent crew and vehicle recovery. The Marshall Space Flight Center (MSFC) Natural Environments Branch has been tasked by the Constellation Program with defining the natural environments at potential landing zones. This paper wiI1 describe the methodology used for data collection and quality control, detail the types of analyses performed, and provide a sample of the results that cab be obtained.

Altino, Karen M.↗

Tropospheric Airborne Meteorological Data Reporting (TAMDAR) Sensor Validation and Verification on National Oceanographic and Atmospheric Administration (NOAA) Lockheed WP-3D Aircraft

As part of the National Aeronautics and Space Administration's Aviation Safety and Security Program, the Tropospheric Airborne Meteorological Data Reporting project (TAMDAR) developed a low-cost sensor for aircraft flying in the lower troposphere. This activity was a joint effort with support from Federal Aviation Administration, National Oceanic and Atmospheric Administration, and industry. This paper reports the TAMDAR sensor performance validation and verification, as flown on board NOAA Lockheed WP-3D aircraft. These flight tests were conducted to assess the performance of the TAMDAR sensor for measurements of temperature, relative humidity, and wind parameters. The ultimate goal was to develop a small low-cost sensor, collect useful meteorological data, downlink the data in near real time, and use the data to improve weather forecasts. The envisioned system will initially be used on regional and package carrier aircraft. The ultimate users of the data are National Centers for Environmental Prediction forecast modelers. Other users include air traffic controllers, flight service stations, and airline weather centers. NASA worked with an industry partner to develop the sensor. Prototype sensors were subjected to numerous tests in ground and flight facilities. As a result of these earlier tests, many design improvements were made to the sensor. The results of tests on a final version of the sensor are the subject of this report. The sensor is capable of measuring temperature, relative humidity, pressure, and icing. It can compute pressure altitude, indicated air speed, true air speed, ice presence, wind speed and direction, and eddy dissipation rate. Summary results from the flight test are presented along with corroborative data from aircraft instruments.

Tsoucalas, George↗

Orion Backup Flight Software (BFS)

Orion Backup Flight Software (BFS) is a joint NASA/Lockheed Martin effort designed to prevent the loss of the Orion crew. BFS will only take over in the event the primary flight software (PFSW) fails to operate properly due to either hardware or software failures. Since the PFSW runs identical software on identical hardware, it is conceivable that a single issue could simultaneously bring down all the PFSW. To minimize the likelihood BFS would be affected by the same issue, BFS was specifically designed to be as different as possible from PFSW: BFS runs on different hardware, a separate operating system, a different compiler, does not share software libraries, and is written by a different team of programmers. This presentation will provide a high-level overview of the Artemis missions and the Orion vehicle, as well as provide additional details of the BFS system (including how BFS is different than the PFSW). The overall BFS capability evolution and timeline (milestones reached as well as work remaining) through the Artemis III mission will be discussed. Additionally, the verification and validation plans for BFS will be presented, describing how we ensure that only validated configuration data is loaded onto the flight vehicle. Finally, the presentation will close with lessons learned and future plans for Orion BFS.

CFS↗

Intelligent Change Detection System: Autonomous Intelligent Machine Agent Model Development

NASA’s significant role in facilitating the harmonious integration of unmanned aircraft systems (UAS), with other aerial vehicles operating in the National Airspace System (NAS), has revealed a need for more advanced technological tools than are being utilized currently. This technology would lend itself to significantly assisting Direct-Action Aviation Personnel (DAAP) with the ingress and egress of UAS operations within the NAS. Providing research findings that would reduce technical barriers, associated with UAS-NAS integration, has been a persistent effort by both NASA and the FAA. One such research effort, pursued by NASA’s Transformative Tools and Technologies – Revolutionary Aviation Mobility (T3-RAM) project, is the development of an autonomous intelligent machine (AIM) agent that would aid DAAP functioning as implemented in remote ground control stations (RGCS). This evolution of the “human-machine” symbiosis, within the aviation environment, is necessary for many reasons. For example, there are projections of large increases to the 864,000 registered UAS and 45,000 aviation operations taking place in the NAS each day. With a data output range from 1 to 20 terabytes per flight or each aerial vehicle, which is projected to have proportional rate increase to that of registered UASs. It is evident, that due to the projected increase of UASs and their generated data, the human-agent’s data managing capabilities will be quickly overwhelmed by the enormous amounts of data emanating in the NAS. The research efforts presented in this paper puts forward results from the development, assessment, and verification of a previously conceptualized AIM-Agent that combats actionable-data (information) errors resulting from the visual perception phenomenon known as “change blindness” (CB). CB has been identified as one of the main culprits of information erroring encountered within the ground control station operator (GCSO) community.

Change Blindness↗

Test Telemetry And Command System (TTACS)

The Jet Propulsion Laboratory has developed a multimission Test Telemetry and Command System (TTACS) which provides a multimission telemetry and command data system in a spacecraft test environment. TTACS reuses, in the spacecraft test environment, components of the same data system used for flight operations; no new software is developed for the spacecraft test environment. Additionally, the TTACS is transportable to any spacecraft test site, including the launch site. The TTACS is currently operational in the Galileo spacecraft testbed; it is also being provided to support the Cassini and Mars Surveyor Program projects. Minimal personnel data system training is required in the transition from pre-launch spacecraft test to post-launch flight operations since test personnel are already familiar with the data system's operation. Additionally, data system components, e.g. data display, can be reused to support spacecraft software development; and the same data system components will again be reused during the spacecraft integration and system test phases. TTACS usage also results in early availability of spacecraft data to data system development and, as a result, early data system development feedback to spacecraft system developers. The TTACS consists of a multimission spacecraft support equipment interface and components of the multimission telemetry and command software adapted for a specific project. The TTACS interfaces to the spacecraft, e.g., Command Data System (CDS), support equipment. The TTACS telemetry interface to the CDS support equipment performs serial (RS-422)-to-ethernet conversion at rates between 1 bps and 1 mbps, telemetry data blocking and header generation, guaranteed data transmission to the telemetry data system, and graphical downlink routing summary and control. The TTACS command interface to the CDS support equipment is nominally a command file transferred in non-real-time via ethernet. The CDS support equipment is responsible for metering the commands to the CDS; additionally for Galileo, TTACS includes a real-time-interface to the CDS support equipment. The TTACS provides the basic functionality of the multimission telemetry and command data system used during flight operations. TTACS telemetry capabilities include frame synchronization, Reed-Solomon decoding, packet extraction and channelization, and data storage/query. Multimission data display capabilities are also available. TTACS command capabilities include command generation verification, and storage.

Fogel, Alvin J.↗

NASA Tech Briefs, July 2013

Dielectrophoresis-Based Particle Sensor Using Nanoelectrode Arrays; Multi-Dimensional Damage Detection for Surfaces and Structures; ULTRA: Underwater Localization for Transit and Reconnaissance Autonomy; Autonomous Cryogenic Leak Detector for Improving Launch Site Operations; Submillimeter Planetary Atmospheric Chemistry Exploration Sounder; Method for Reduction of Silver Biocide Plating on Metal Surfaces; Silicon Micromachined Microlens Array for THz Antennas; Forward-Looking IED Detector Ground Penetrating Radar; Fully Printed, Flexible, Phased Array Antenna for Lunar Surface Communication, Battery Charge Equalizer with Transformer Array; An Efficient, Highly Flexible Multi-Channel Digital Downconverter Architecture; Dimmable Electronic Ballast for a Gas Discharge Lamp; Conductive Carbon Nanotube Inks for Use with Desktop Inkjet Printing Technology; Enhanced Schapery Theory Software Development for Modeling Failure of Fiber-Reinforced Laminates; High-Performance, Low-Temperature-Operating, Long-Lifetime Aerospace Lubricants; Carbon Nanotube Microarrays Grown on Nanoflake Substrates; Differential Muon Tomography to Continuously Monitor Changes in the Composition of Subsurface Fluids; Microgravity Drill and Anchor System; 20 Granular Media-Based Tunable Passive Vibration Suppressor; 21 Miga Aero Actuator and 2D Machined Mechanical Binary Latch; Micro-XRF for In Situ Geological Exploration of Other Planets; Hydrogen-Enhanced Lunar Oxygen Extraction and Storage Using Only Solar Power; Uplift of Ionospheric Oxygen Ions During Extreme Magnetic Storms; Miniaturized, High-Speed, Modulated X-Ray Source; Hollow-Fiber Spacesuit Water Membrane Evaporator 25 High-Power Single-Mode 2.65-micrometers InGaAsSb/AlInGaAsSb Diode Lasers; Optical Device for Converting a Laser Beam Into Two Co-aligned but Oppositely Directed Beams; A Hybrid Fiber/Solid-State Regenerative Amplifier with Tunable Pulse Widths for Satellite Laser Ranging; X-Ray Diffractive Optics; SynGenics Optimization System (SynOptSys); 29 CFD Script for Rapid TPS Damage Assessment; radEq Add-On Module for CFD Solver Loci-CHEM; Science Opportunity Analyzer (SOA) Version 8; 30 Autonomous Byte Stream Randomizer; Distributed Engine Control Empirical/Analytical Verification Tools; Dynamic Server-Based KML Code Generator Method for Level-of-Detail Traversal of Geospatial Data; Automated Planning of Science Products Based on Nadir Overflights and Alerts for Onboard and Ground Processing; Linked Autonomous Interplanetary Satellite Orbit Navigation; Risk-Constrained Dynamic Programming for Optimal Mars Entry, Descent, and Landing; Scheduling Operations for Massive Heterogeneous Clusters; Deepak Condenser Model (DeCoM); Flight Software Math Library; Recirculating 1-K-Pot for Pulse-Tube Cryostats; 35 Method for Processing Lunar Regolith Using Microwaves; Wells for In Situ Extraction of Volatiles from Regolith (WIEVR); and Estimating the Backup Reaction Wheel Orientation Using Reaction Wheel Spin Rates Flight Telemetry from a Spacecraft.

Source record↗

Investigation of Multi-Input, Multi-Output (MIMO) Random Control Applied to Direct Field Acoustic Testing

Direct Field Acoustic Testing (DFAT) offers potential cost and time savings over reverberant chamber acoustic testing of spacecraft. The NASA Multi-Purpose Crew Vehicle (MPCV) Program recently directed a series of acoustic tests on Orion structural test articles comparing DFAT and reverberant testing of the same test article with a view to qualifying DFAT for manned space flight vehicles. The verification process compared four parameters noise level compliance with the one third octave test specification, spatial uniformity of the acoustic field, spatial correlation of the acoustic field and vibration response of vehicle structure, including representative solar array panels. While the results of the verification were encouraging, MPCV Loads and Dynamics engaged Quartus Engineering to investigate whether alternative MIMO random control strategies might improve the spatial uniformity and/or the spatial correlation of the DFAT acoustic field. This paper presents the results of acoustic field simulations of the DFAT test and provides a better understanding of how MIMO random control systems originally developed for vibration and structural durability testing can be expected to perform in DFAT testing.

Direct Field↗

A PCR Based Microbial Monitoring Alternative Method of Detection and Identification of Microbes Aboard ISS

Previous research has shown that microorganisms and potential human pathogens have been detected on the International Space Station (ISS) with additional introduction of new microflora occurring with every exchange of crew or addition of equipment and supplies. These microbes are readily transferred between crew and subsystems (i.e. ECLSS, environmental control and life support systems). As this can be detrimental to astronaut health and optimal performance of ISS systems, monitoring of systems such as ECLSS to include identification of microbial contaminants could prevent adverse effects on human health and life support systems. Current monitoring on ISS is laborious and utilizes culture based methods followed by sample return to Earth for complete analysis. Future, long-distance spaceflight missions will require real-time monitoring capabilities that enable efficient and rapid assessments of the microbial environment allowing for expedited decisions and more targeted response to cope with anomalies. Polymerase chain reaction (PCR), a molecular microbial monitoring method was chosen and numerous PCR instruments investigated for their potential to perform in microgravity conditions. Using ISS as a test bed for PCR verification in microgravity will enable NASA to assess whether molecular based microbiological sensors may be components of reliable, closed-loop life support and habitation systems in spacecraft, enhancing infrastructure capabilities through increased efficiency, reliability, and time savings by enabling sample analysis on orbit. NASA selected the Water Monitoring Suite as one of the rapid spaceflight hardware demonstration activities utilizing a streamlined process to minimize the time required to fly experimental flight hardware. The RAZOR EX (BioFire Defense, Salt Lake City, UT) system was part of the water monitoring suite and is a commercial off-the-shelf (COTS) real-time PCR instrument designed for field work. The RAZOR EX was originally designed for Department of Defense (DoD) under a small business innovative research (SBIR) grant and is ruggedized, compact and provides a rapid, sample to answer in less than an hour. PCR assays using a fluorescent probe were optimized and spiked with known concentrations of DNA (Pseudomonas aeruginosa) ranging from 0.002 to 20 ng. PCR reagents were lyophilized and configured in customized pouches and tested for flight readiness. Three types of water were used to rehydrate the reagents and demonstrate the fidelity of the PCR reaction in microgravity. Molecular grade deionized water served as a control while filtered and unfiltered ISS potable water served to test for chemical or biological inhibitors. All three types were compared to parallel ground test results. Nine tests were run on ISS (3 of each water type) and the critical threshold cycle (Ct) was compared to parallel ground tests completed at Kennedy Space Center, FL and Johnson Space Center, TX. All concentrations of Pseudomonas aeruginosa DNA were detected. A comparison of the Ct produced in real time PCR indicated similarity between flight and ground samples. There appeared to be no significant difference between flight or ground PCR reactions or between any of the three water types. This testing demonstrated the ability to perform molecular testing during spaceflight operations with similar sensitivity. It will allow for future ground development of molecular protocols and minimize the need for spaceflight testing. Future testing will include development of additional targets including environmental and health related organisms.

Christina Khodadad↗

Collaborative Systems Engineering in the Ascent Abort-2 Crew Module/Separation Ring Project

Generally speaking, systems engineering (SE) tool-sets face a dilemma balancing power and accessibility. High-powered SE tools (MagicDraw, Cradle, Core, etc.) tend to be specialized and are available only to highly trained Systems Engineers, and/or through the use of a 'back room' developer team making the output products available to the broader team. On the other hand, highly accessible tools (MS Word, Excel, etc.) do not have the power to implement SE in a rigorous manner. NASA has to test all aspects of the new human-rated Orion Multi-Purpose Crew Vehicle spacecraft prior to its first crewed mission. The test program includes uncrewed launch abort flight tests to demonstrate the capability to save the crew in the event that a launch failure occurs. Orion's second abort flight test will be a low-altitude flight test known as "Ascent Abort 2 (AA-2)." This test is currently scheduled to be carried out at Cape Canaveral Air Force Station's Space Launch Complex 46 (SLC-46) in Florida in 2019. NASA's in-house AA-2 Crew Module and Separation Ring (CSR) Team is producing the crew module and separation ring. Operating jointly as both an Advanced Exploration Systems (AES) Project and an Orion Project, the CSR project charter includes development of innovative, streamlined and generally more efficient practices for creation of flight hardware and software. One result of this tasking has been development of a collaborative and data-centric systems engineering environment within the team's shared web environment (Microsoft SharePoint). Through the use of built-in, 'out of the box capabilities' present in MS SharePoint, the CSR Systems Engineering team has created (with some limited developer support) a data-centric architecture for the project's SE implementation, including functional and interface analysis, requirements development and management, risk management, verification planning and management, test results, and end item management. Data elements are linked between data structures so as to define and control relationships between item types, link requirements to parents and children, and link tests to the requirements that they verify. The overall project team integration is increased by also linking SE content to project management content over the project life cycle, including team communication, action items, configuration management, decisional and meeting materials, and life cycle reviews. This presentation will provide an overview of the collaborative SE environment, showing how it provides the power for a number of SE tasks while still providing the accessibility and transparency to allow the full project team to collaborate and succeed. Given the project phase, we'll be able to present a nearly full lifecycle discussion, from concept through verification and approaching delivery.

Systems Engineering environments↗

Operator procedure verification with a rapidly reconfigurable simulator

Generating and testing procedures for controlling spacecraft subsystems composed of electro-mechanical and computationally realized elements has become a very difficult task. Before a spacecraft can be flown, mission controllers must envision a great variety of situations the flight crew may encounter during a mission and carefully construct procedures for operating the spacecraft in each possible situation. If, despite extensive pre-compilation of control procedures, an unforeseen situation arises during a mission, the mission controller must generate a new procedure for the flight crew in a limited amount of time. In such situations, the mission controller cannot systematically consider and test alternative procedures against models of the system being controlled, because the available simulator is too large and complex to reconfigure, run, and analyze quickly. A rapidly reconfigurable simulation environment that can execute a control procedure and show its effects on system behavior would greatly facilitate generation and testing of control procedures both before and during a mission. The How Things Work project at Stanford University has developed a system called DME (Device Modeling Environment) for modeling and simulating the behavior of electromechanical devices. DME was designed to facilitate model formulation and behavior simulation of device behavior including both continuous and discrete phenomena. We are currently extending DME for use in testing operator procedures, and we have built a knowledge base for modeling the Reaction Control System (RCS) of the space shuttle as a testbed. We believe that DME can facilitate design of operator procedures by providing mission controllers with a simulation environment that meets all these requirements.

Iwasaki, Yumi↗

Some instrumentation requirement issues for the Space Station structural characterization experiment

The Space Station will provide unique opportunities to the research and technology community as a national in-space research facility. Opportunities will exist for technology experiments in a variety of disciplines, including dynamics and control of large space structures (LSS). The Space Station Structural Characterization Experiment (SSSCE) is an early space station technology experiment now under development. The objective of the experiment is to instrument and use the Space Station as a generic research test article, in support of research and technology activities in the areas of structural dynamics and control/structure interaction (CSI). Tests will be conducted, potentially, on each assembly flight configuration, as well as on the phase 1 configuration. Structural dynamic response data will be measured and transferred to the ground for analysis. These measurements will support the development and in-space verification of system identification and analytical modeling techniques for future LSS, including the evolutionary Space Station. The paper begins by restating the principal objective of SSSCE, along with the basic approach that will be used. The body of the paper deals with instrumentation requirement issues. The paper closes with several questions concerning modal-testing objectives and limitations, a brief review of a previous on-orbit experiment, the Solar Array Flight Experiment, and concluding remarks.

Pappa, Richard S.↗

Pre-Installation Acceptance (PIA) Functional Performance of the Design Verification Test (DVT) Exploration Extra-vehicular Mobility Unit (xEMU)

In an effort that began with technology investment by NASA in a few key components during the Constellation Program and then evolved to demonstrate a packaged Portable Life Support System (PLSS) as part of the Advanced Exploration Systems (AES) Program, the next evolution of the PLSS is now a key component of the Exploration Extra-vehicular Mobility Unit (xEMU) and is assembled as a Design Verification Test (DVT) unit. The xEMU has been detailed with respect to completing a demonstration on the International Space Station (ISS) with support of units for initial lunar capability. The xEMU completed the Preliminary Design Review (PDR) with subsequent Safety Review Panel (SRP) Phase I reviews in 2019-2020. The objectives for DVT are to validate requirements, train the team, learn how to fabricate the hardware with appropriate process controls, assemble the hardware, test the hardware, determine the failure mechanisms/limits of the hardware design and buy down the most risk possible for the qualification and flight phases of the development. With completion of the assembly and initial functional testing of the DVT PLSS in laboratory ambient conditions and vacuum conditions the xEMU has progressed significantly into the DVT objectives. A key part of the test sequences for DVT and all future phases is the Pre-Installation Acceptance (PIA) functional testing which validates the performance of integrated systems including: primary thermal control, auxiliary thermal control, suit ventilation, primary oxygen, secondary oxygen, power distribution, as well as caution and warning all with respect to the applied requirements. This discussion will include an overview of the assembly, summary of the PIA functional testing, lessons learned, and corrective actions implemented moving forward into the remainder of the DVT phase for xEMU.

Colin Campbell↗

Ion Thruster and Power Processor Developed for the Deep Space 1 Mission

The NASA Solar Electric Propulsion Technology Applications Readiness (NSTAR) Program has provided a single-string primary propulsion system to NASA's Deep Space 1 spacecraft. This spacecraft will carry about 81 kg of xenon propellant for the ion thruster, which can be throttled down from 2.3 to 0.5 kW as the spacecraft moves away from the Sun. The propellant load will provide about 20 months of propulsion at the one-half power throttle setpoint of 1.2 kW. This mission will validate the 2.5-kW ion propulsion system and will fly by the asteroid 1992 KD in 1999. If funding permits, Deep Space 1 also will encounter comets Wilson-Harrington and Borrelly in 2001. NASA Lewis Research Center's On-Board Propulsion Branch was responsible for the development of the 30-cm-diameter ion thruster, the 2.5-kW power processor unit (PPU), and the Digital Control and Interface Unit (DCIU) that controls the PPU/thruster/feed system and provides data and recovery from fault conditions. Lewis transferred the thruster and PPU technologies to the Hughes Electron Dynamics Division, which was selected to build two sets of flight thrusters, as well as the PPU's and DCIU's. Hughes subcontracted the DCIU development to Spectrum Astro Incorporated. The Jet Propulsion Laboratory (JPL) was primarily responsible for the NSTAR project management, thruster lifetests, the feed system, diagnostics, and the propulsion subsystem integration. A total of four engineering model thrusters and three breadboard PPU's were built, integrated, and tested. More than 50 development tests were conducted along with thruster design verification tests of 2000 and 1000 hours. In addition, an 8000-hr life demonstration test was successfully completed and demonstrated wear-rates consistent with full-power lifetimes in excess of 12,000 hours.

Sovey, James S.↗

Microthruster Propulsion for the Space Technology 7 (ST7) Technology Demonstration Mission

For future applications to precision formation flying missions, NASA's New Millennium Program is scheduled to test colloid micro-Newton thrusters (CMNTs) on the ST7 technology demonstration mission. These CMNTs are part of a disturbance reduction system (DRS) on the ESA SMART-2 Spacecraft or LISA Pathfinder. The goal of the ST7 DRS is to demonstrate technologies necessary to meet the nanometer precision positioning control requirements of the LISA mission. In order to achieve these goals, the CMNTs are required to demonstrate a thrust resolution of less than 0.1 micro-N and a thrust noise of less than 0.1 micro-N/[square root]Hz for thrust levels between 5 and 30 micro-N. Developed by Busek Co. with support from JPL in testing an design, the CMNT has been developed over the last four years into a flight-ready microthrust system. The development, validation testing, and flight unit production of the CMNTs are described. Development tests and analysis include preliminary wear tests, propellant loading process verification, flow testing, and performance verification. Validation and flight unit verification includes thermal and structural analysis, life testing, thermal and dynamic load testing, and performance verification. Final delivery of the units is planned in 2007 with and planned launch and flight demonstration 2009.

microthruster↗

The Environmental Control and Life Support System (ECLSS) advanced automation project

The objective of the environmental control and life support system (ECLSS) Advanced Automation Project is to influence the design of the initial and evolutionary Space Station Freedom Program (SSFP) ECLSS toward a man-made closed environment in which minimal flight and ground manpower is needed. Another objective includes capturing ECLSS design and development knowledge future missions. Our approach has been to (1) analyze the SSFP ECLSS, (2) envision as our goal a fully automated evolutionary environmental control system - an augmentation of the baseline, and (3) document the advanced software systems, hooks, and scars which will be necessary to achieve this goal. From this analysis, prototype software is being developed, and will be tested using air and water recovery simulations and hardware subsystems. In addition, the advanced software is being designed, developed, and tested using automation software management plan and lifecycle tools. Automated knowledge acquisition, engineering, verification and testing tools are being used to develop the software. In this way, we can capture ECLSS development knowledge for future use develop more robust and complex software, provide feedback to the knowledge based system tool community, and ensure proper visibility of our efforts.

Dewberry, Brandon S.↗

Mars Science Laboratory Entry Descent and Landing Simulation Using DSENDS

The most recent planetary science mission to Mars is Mars Science Laboratory (MSL) with the Curiosity rover, launched November 26, 2011 and landed at Gale Crater on August 6, 2012. This spacecraft was the first use at Mars of a complete closed-loop Guidance Navigation and Control (GN&C) system, including guided entry with a lifting body that greatly reduces dispersions during the Entry, Descent and Landing (EDL) phase to achieve a 25 km x 20 km landing error relative to the selected Gale Crater landing target. In order to confirm meeting the above landing criteria, high-fidelity simulation of the EDL phase is required. The tool used for 6DOF EDL trajectory verification analysis is Dynamics Simulator for Entry, Descent and Surface landing (DSENDS), which is a high-fidelity simulation tool from JPLs Dynamics and Real-Time Simulation Laboratory for the development, test and operations of aero-flight vehicles. DSENDS inherent capability is augmented for MSL with project-specific models of atmosphere, aerodynamics, sensors and thrusters along with GN&C flight software to enable high-fidelity trajectory simulation. This paper will present the model integration and independent verification experience of the JPL EDL trajectory analysis team.

Mars↗

Mars Science Laboratory Entry Descent and Landing Simulation Using DSENDS

The most recent planetary science mission to Mars was Mars Science Laboratory (MSL) with the Curiosity rover, launched November 26, 2011 and landed at Gale Crater on August 6, 2012. This spacecraft was the first use at Mars of a complete closed-loop Guidance Navigation and Control (GN&C) system, including guided entry with a lifting body that greatly reduces dispersions during the Entry, Descent and Landing (EDL) phase to achieve a 25 km X 20 km landing error relative to the selected Gale Crater landing target. In order to confirm meeting the above landing criteria, high-fidelity simulation of the EDL phase is required. The tool used for 6DOF EDL trajectory verification analysis is Dynamics Simulator for Entry, Descent and Surface landing (DSENDS), which is a high-fidelity simulation tool from JPLs Dynamics and Real-Time Simulation Laboratory for the development, test and operations of aero-flight vehicles. DSENDS inherent capability is augmented for MSL with project-specific models of atmosphere, aerodynamics, sensors and thrusters along with GN&C flight software to enable high-fidelity trajectory simulation. This paper will present the model integration and independent verification experience of the JPL EDL trajectory analysis team.

Burkhart, P. Daniel↗

An innovative design for autonomous backup attitude control of the Gamma Ray Observatory

The Gamma Ray Observatory is a NASA funded three-axis stabilized spacecraft which will carry four scientific instruments to observe gamma ray phenomena. The requirement to protect the scientific mission from system failures led to the attitude control and determination system design described in this paper. The design employs nine control modes with error detection, hardware substitution, and autonomous mode switching. The system architecture evolved to eliminate cross-dependence between the primary on-board computer (OBC) and the backup control processor electronics. Cross strapping of sensors and actuators and separation of the input/output electronics ensure that a reliable set of sensors and actuators will be available for backup mode operation. The OBC software includes failure detection, hardware reconfiguration, and mode switching logic which provide the ability to autonomously transfer, upon anomaly, to a reliable backup mode. Verification of this mode transition design is done in four test programs: at the unit level, by analytical simulation, by a hybrid breadboard electronics-simulation setup, and by a flight hardware-simulation test.

Tai, F.↗