Search NASA⌕ Search

SEARCH · Search NASA

Results for “spacecraft data interfaces”

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 919 records · Page 51

Flight Support System (FSS) docking and umbilical services systems

The Satellite Servicing Project at GSFC in the early 80's developed a facility for servicing observatories in orbit when docked on the shuttle. The facility includes a three point docking ring and one or two umbilicals to provide power, data and command capability to docked payloads. This facility was used in the 1984 repair of the Solar Maximum satellite. It will be used for the Hubble repair mission in 1993, and it is planned to be used on the Explorer Platform retrieval mission in 1995 and for servicing AXAF in the late 90's. The basic three point docking mechanisms and umbilical interfaces were adopted by the OMU Project for that vehicle's remote rendezvous and docking mission capability. This would have assured a common interface for a serviceable payload for either shuttle based or remote servicing, i.e., HST. For OMU remote servicing, quick reaction docking latches were under development when that Project was cancelled. Although there is no remote servicing capability being funded at present, the EOS spacecraft configuration does include three pins compatible with the FSS latches as a contingency planning measure.

Falkenhayn, Edward↗

Radical is Temporary

I suspect that even if Ken had stayed on, we would have evolved to the state we're in right now. In terms of the nature of the work that we're doing, we've gone from development to maintenance, and so the project team needed to evolve to reflect that change. The analogy I use to describe Hubble is a data factory, and we provide the factory controller. The telescope takes in light and produces pictures, and we're the ones sending all of the control signals and monitoring the temperature, power, and voltages in the factory to make sure the production line is doing its job and that it's not reaching some sort of a stress point. That's basically it. We maintain the Hubble command and control system. I think we're still putting out a good quality product. We still meet our schedule and cost milestones. Every time we make a change to the ground system, we run a suite of tests to make sure that the system still runs as expected, and that it correctly controls the spacecraft. Other than that, provided the interfaces are controlled, everything is okay.

Barrett, Larry↗

Multiple crossings of a very thin plasma sheet in the Earth's magnetotail

High resolution magnetic field, plasma and energetic particle data from the IMP-8 spacecraft were studied for multiple crossings of the Earth's magnetotail plasma sheet when it becomes thin during magnetospheric substorms. Traversals recur on a time scale of several minutes and they are associated with high velocity plasma flows that are usually directed tailward but are occasionally directed earthward for brief intervals. Observations are explained by rapid oscillations of a plasma sheet that is only a few thousand km thick, a dimension comparable to the gyroradius of energetic protons. Differences in the angular distributions of the two energies indicate that the higher energy protons are preferentially located on field lines deeper in the tail lobe. A neutral line acceleration model is supported tailward streaming energetic electrons which are occasionally present at the lobe plasma sheet interface.

Fairfield, D. H.↗

Mission telemetry system monitor: A real-time knowledge-based system

The Galileo Mission Telemetry System (MTS) has a cluster of computer subsystems configured as a star network. The MTS handles the real-time processing of spacecraft telemetry and ground monitor data. Large volumes of status and fault messages are generated as a result of changes in the system environment. These messages are triggered by the conditions that exist on any one particular subsystem or device. The order of message generation is in time sequence and does not always correlate to the function sequence of active processes. A significant number of messages provide context with varying degrees of uncertainty. As such, highly skilled telemetry controllers are required to regularly go through high volumes of messages generated by the MTS to identify, diagnose, and isolate faults. A knowledge-based system prototype is being developed to monitor the Galileo Mission Telemetry System performance. The system design approach features temporal reasoning, uncertainty management, and intelligent graphic user interfaces.

Mouneimne, Samih A.↗

Time Analyzer for Time Synchronization and Monitor of the Deep Space Network

A software package has been developed to measure, monitor, and archive the performance of timing signals distributed in the NASA Deep Space Network. Timing signals are generated from a central master clock and distributed to over 100 users at distances up to 30 kilometers. The time offset due to internal distribution delays and time jitter with respect to the central master clock are critical for successful spacecraft navigation, radio science, and very long baseline interferometry (VLBI) applications. The instrument controller and operator interface software is written in LabView and runs on the Linux operating system. The software controls a commercial multiplexer to switch 120 separate timing signals to measure offset and jitter with a time-interval counter referenced to the master clock. The offset of each channel is displayed in histogram form, and "out of specification" alarms are sent to a central complex monitor and control system. At any time, the measurement cycle of 120 signals can be interrupted for diagnostic tests on an individual channel. The instrument also routinely monitors and archives the long-term stability of all frequency standards or any other 1-pps source compared against the master clock. All data is stored and made available for

Cole, Steven↗

CoNNeCT Baseband Processor Module Boot Code SoftWare (BCSW)

This software provides essential startup and initialization routines for the CoNNeCT baseband processor module (BPM) hardware upon power-up. A command and data handling (C&DH) interface is provided via 1553 and diagnostic serial interfaces to invoke operational, reconfiguration, and test commands within the code. The BCSW has features unique to the hardware it is responsible for managing. In this case, the CoNNeCT BPM is configured with an updated CPU (Atmel AT697 SPARC processor) and a unique set of memory and I/O peripherals that require customized software to operate. These features include configuration of new AT697 registers, interfacing to a new HouseKeeper with a flash controller interface, a new dual Xilinx configuration/scrub interface, and an updated 1553 remote terminal (RT) core. The BCSW is intended to provide a "safe" mode for the BPM when initially powered on or when an unexpected trap occurs, causing the processor to reset. The BCSW allows the 1553 bus controller in the spacecraft or payload controller to operate the BPM over 1553 to upload code; upload Xilinx bit files; perform rudimentary tests; read, write, and copy the non-volatile flash memory; and configure the Xilinx interface. Commands also exist over 1553 to cause the CPU to jump or call a specified address to begin execution of user-supplied code. This may be in the form of a real-time operating system, test routine, or specific application code to run on the BPM.

Yamamoto, Clifford K.↗

Reflector surface distortion analysis techniques (thermal distortion analysis of antennas in space)

A group of large computer programs are used to predict the farfield antenna pattern of reflector antennas in the thermal environment of space. Thermal Radiation Analysis Systems (TRASYS) is a thermal radiation analyzer that interfaces with Systems Improved Numerical Differencing Analyzer (SINDA), a finite difference thermal analysis program. The programs linked together for this analysis can now be used to predict antenna performance in the constantly changing space environment. They can be used for very complex spacecraft and antenna geometries. Performance degradation caused by methods of antenna reflector construction and materials selection are also taken into consideration. However, the principal advantage of using this program linkage is to account for distortions caused by the thermal environment of space and the hygroscopic effects of the dry-out of graphite/epoxy materials after the antenna is placed into orbit. The results of this type of analysis could ultimately be used to predict antenna reflector shape versus orbital position. A phased array antenna distortion compensation system could then use this data to make RF phase front corrections. That is, the phase front could be adjusted to account for the distortions in the antenna feed and reflector geometry for a particular orbital position.

Sharp, R.↗

Space Induced Discharge Model to Be Used on Interface Circuit Vulnerability Assessment

Charging can occur in space due to plasma and high energy particles. Charging is especially severe in certain earth orbits such as geostationary orbit, medium earth orbit and highly inclined orbit. A spacecraft that travels to other planets such as Jupiter also encounters high level of charging due to Jupiter’s radiation belt. The major concern for spacecraft operation due to charging is the survival of sensitive electrical circuits. Dielectrics and floating metal can charge up and discharge onto interface circuits. The electrical circuits need to be evaluated for survival from the electrostatic-discharge (ESD) threat. Both ESD induced upset and damage need to be assessed. The interface circuits are often located inside a shielded unit in the spacecraft structure or a shielded vault with sufficient radiation shielding to avoid surface and internal charging. The materials external to the highly shielded area can charge up and discharge onto wires that can directly dissipate the ESD onto the interface circuits. Figure 1 shows a possible discharge mechanism onto the interfacing circuits. If the wire has an external shield or a coaxial line, some or most of the discharge can flow on the shield to chassis ground. There is always coupling from external discharge. If the wire has no shield, the discharge flows onto the interface circuit. Fig. 1 Possible discharge paths onto the interface circuits. The purpose of this article is to address how to model the ESD threat to be used as the discharge source onto the interface circuit based on the electron beam test data. Different models are needed for different impedances associated with the interface circuits. Once those models are derived, one needs to analyze the interface circuit with the corresponding model using an electrical simulation tool. Then, the circuit’s front-end components can be assessed for damage and upset. Upset is highly dependent on the circuit operation and system requirements, and thus it is not addressed any further. Damage of electrical parts is often rated under Human-Body-Model (HBM) ESD. One can utilize this industry-wide available information to assess the damage vulnerability due to space discharges. However, the HBM waveform does not always match the discharge waveform. To estimate the damage vulnerability of the circuit and set margin, one needs to compare the equivalent energy delivered to the victim between a HBM discharge and the results from an ESD source model based on actual discharges. This paper presents such a comparison for a few select cases.

Xie, Julie↗

Efficient development and processing of thermal math models of very large space truss structures

As the spacecraft moves along the orbit, the truss members are subjected to direct and reflected solar, albedo and planetary infra-red (IR) heating rates, as well as IR heating and shadowing from other spacecraft components. This is a transient process with continuously changing heating loads and the shadowing effects. The resulting nonuniform temperature distribution may cause nonuniform thermal expansion, deflection and stress in the truss elements, truss warping and thermal distortions. There are three challenges in the thermal-structural analysis of the large truss structures. The first is the development of the thermal and structural math models, the second - model processing, and the third - the data transfer between the models. All three tasks require considerable time and computer resources to be done because of a very large number of components involved. To address these challenges a series of techniques of automated thermal math modeling and efficient processing of very large space truss structures were developed. In the process the finite element and finite difference methods are interfaced. A very substantial reduction of the quantity of computations was achieved while assuring a desired accuracy of the results. The techniques are illustrated on the thermal analysis of a segment of the Space Station main truss.

Warren, Andrew H.↗

Automated and Adaptive Mission Planning for Orbital Express

The Orbital Express space mission was a Defense Advanced Research Projects Agency (DARPA) lead demonstration of on-orbit satellite servicing scenarios, autonomous rendezvous, fluid transfers of hydrazine propellant, and robotic arm transfers of Orbital Replacement Unit (ORU) components. Boeing's Autonomous Space Transport Robotic Operations (ASTRO) vehicle provided the servicing to the Ball Aerospace's Next Generation Serviceable Satellite (NextSat) client. For communication opportunities, operations used the high-bandwidth ground-based Air Force Satellite Control Network (AFSCN) along with the relatively low-bandwidth GEO-Synchronous space-borne Tracking and Data Relay Satellite System (TDRSS) network. Mission operations were conducted out of the RDT&E Support Complex (RSC) at the Kirtland Air Force Base in New Mexico. All mission objectives were met successfully: The first of several autonomous rendezvous was demonstrated on May 5, 2007; autonomous free-flyer capture was demonstrated on June 22, 2007; the fluid and ORU transfers throughout the mission were successful. Planning operations for the mission were conducted by a team of personnel including Flight Directors, who were responsible for verifying the steps and contacts within the procedures, the Rendezvous Planners who would compute the locations and visibilities of the spacecraft, the Scenario Resource Planners (SRPs), who were concerned with assignment of communications windows, monitoring of resources, and sending commands to the ASTRO spacecraft, and the Mission planners who would interface with the real-time operations environment, process planning products and coordinate activities with the SRP. The SRP position was staffed by JPL personnel who used the Automated Scheduling and Planning ENvironment (ASPEN) to model and enforce mission and satellite constraints. The lifecycle of a plan began three weeks outside its execution on-board. During the planning timeframe, many aspects could change the plan, causing the need for re-planning. These variable factors, ranging from shifting contact times to ground-station closures and required maintenance times, are discussed along with the flexibility of the ASPEN tool to accommodate changes to procedures and the daily or long-range plan, which contributed to the success of the mission. This paper will present an introduction to ASPEN, a more in-depth discussion on its use on the Orbital Express mission, and other relative work. A description of ground operations after the SRP deliveries were made is included, and we briefly discuss lessons learned from the planning perspective and future work.

scheduling↗

Trade-Space Analysis Tool for Constellations (TAT-C)

Traditionally, space missions have relied on relatively large and monolithic satellites, but in the past few years, under a changing technological and economic environment, including instrument and spacecraft miniaturization, scalable launchers, secondary launches as well as hosted payloads, there is growing interest in implementing future NASA missions as Distributed Spacecraft Missions (DSM). The objective of our project is to provide a framework that facilitates DSM Pre-Phase A investigations and optimizes DSM designs with respect to a-priori Science goals. In this first version of our Trade-space Analysis Tool for Constellations (TAT-C), we are investigating questions such as: How many spacecraft should be included in the constellation? Which design has the best costrisk value? The main goals of TAT-C are to: Handle multiple spacecraft sharing a mission objective, from SmallSats up through flagships, Explore the variables trade space for pre-defined science, cost and risk goals, and pre-defined metrics Optimize cost and performance across multiple instruments and platforms vs. one at a time.This paper describes the overall architecture of TAT-C including: a User Interface (UI) interacting with multiple users - scientists, missions designers or program managers; an Executive Driver gathering requirements from UI, then formulating Trade-space Search Requests for the Trade-space Search Iterator first with inputs from the Knowledge Base, then, in collaboration with the Orbit Coverage, Reduction Metrics, and Cost Risk modules, generating multiple potential architectures and their associated characteristics. TAT-C leverages the use of the Goddard Mission Analysis Tool (GMAT) to compute coverage and ancillary data, streamlining the computations by modeling orbits in a way that balances accuracy and performance.TAT-C current version includes uniform Walker constellations as well as Ad-Hoc constellations, and its cost model represents an aggregate model consisting of Cost Estimating Relationships (CERs) from widely accepted models. The Knowledge Base supports both analysis and exploration, and the current GUI prototype automatically generates graphics representing metrics such as average revisit time or coverage as a function of cost.

Science Data Processing↗

CLINICAL DECISION SUPPORT: PATH TO FUNCTIONAL REQUIREMENTS

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data and crew time), limited options for evacuation and those associated with delayed or constrained communications, all of which demand greater crew autonomy. Specifically, as the communication delays intensify the further we explore space, the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will be key to mission continuation and success. To augment the requisite knowledge, skills and abilities (KSAs) of a time-constrained crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution that would facilitate, guide and inform Earth-independent medical operations, while assisting crewmembers through various clinical presentations. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit. ExMC is actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses gap Medical-701 within the Inflight Medical Conditions risk: “Enhance medical capabilities within an exploration medical system.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology continues to advance this decade and beyond. Hence, data, software and computational resources will play an essential and synergistic role in maintaining crew health, wellness and performance in deep space missions. The focus of the CDS project is to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance and medical care during exploration missions. The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/databases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that incorporate work from collaborators yet maintain a flexible platform for integrating new technology in the future. In fiscal year 2021 (FY21), the CDS project identified requirements through two primary mechanisms: (i) the development of software implementation prototypes and (ii) the application of systems engineering processes. The CDS project developed and tested a series of increasingly complex system prototypes that were based on use cases derived from the CDSS concept of operations (ConOps). These software implementations yielded insights on CDSS functionality as well as lessons learned that provided the initial requirements for CDSS capability. By applying a systems engineering (SE) approach, medical scenarios provided in the ConOps and the use cases for software implementation underwent functional decomposition to identify CDSS functionality. Also, systems-based modeling language (SysML) tools such as activity diagrams were developed from the same ConOps and use cases to identify CDSS functionality. The lessons learned from software implementation defined both specific requirements and broad areas of requirements. Within these defined broad requirement areas, further analysis of the SE products identified specific capability that resulted in the final functional requirements. In summary, the software prototypes, functional decomposition of the ConOps and use cases, and SysML diagrams provided the basis for the CDSS requirements developed in FY21. In the upcoming year, these requirements will be refined for their final ExMC baseline review in latter FY22.

clinical decision support↗

Clinical Decision Support: Path to Functional Requirements

Long-duration, deep-space exploration missions present significant challenges to crew health and performance. These challenges include the individual and combined effects of microgravity, radiation exposure, isolation, limited resources (mass, volume, power, data and crew time), limited options for evacuation and those associated with delayed or constrained communications, all of which demand greater crew autonomy. Specifically, as the communication delays intensify the further we explore space, the unqualified need for Earth-independent medical operations focused on autonomous diagnosis, treatment and prevention will be key to mission continuation and success. To augment the requisite knowledge, skills and abilities (KSAs) of a time-constrained crew operating under stressful conditions, combatting fatigue, and facing a potential medical crisis, a robust clinical decision support system (CDSS) is a probable solution that would facilitate, guide and inform Earth-independent medical operations, while assisting crewmembers through various clinical presentations. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit. ExMC is actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addresses gap Medical-701 within the Inflight Medical Conditions risk: “Enhance medical capabilities within an exploration medical system.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology continues to advance this decade and beyond. Hence, data, software and computational resources will play an essential and synergistic role in maintaining crew health, wellness and performance in deep space missions. The focus of the CDS project is to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance and medical care during exploration missions. The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/databases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that incorporate work from collaborators yet maintain a flexible platform for integrating new technology in the future. In fiscal year 2021 (FY21), the CDS project identified requirements through two primary mechanisms: (i) the development of software implementation prototypes and (ii) the application of systems engineering processes. The CDS project developed and tested a series of increasingly complex system prototypes that were based on use cases derived from the CDSS concept of operations (ConOps). These software implementations yielded insights on CDSS functionality as well as lessons learned that provided the initial requirements for CDSS capability. By applying a systems engineering (SE) approach, medical scenarios provided in the ConOps and the use cases for software implementation underwent functional decomposition to identify CDSS functionality. Also, systems-based modeling language (SysML) tools such as activity diagrams were developed from the same ConOps and use cases to identify CDSS functionality. The lessons learned from software implementation defined both specific requirements and broad areas of requirements. Within these defined broad requirement areas, further analysis of the SE products identified specific capability that resulted in the final functional requirements. In summary, the software prototypes, functional decomposition of the ConOps and use cases, and SysML diagrams provided the basis for the CDSS requirements developed in FY21. In the upcoming year, these requirements will be refined for their final ExMC baseline review in latter FY22.

Clinical decision support↗

A Low-Cost Clustered Archive Approach for Storing Remote Sensing Data

As part of NASA's Earth Observing System (EOS) Data and Information System (EOSDIS), the Moderate Resolution Imaging Spectrometer (MODIS) Data Processing System (MODAPS) is now processing data from two instruments on the EOS flag ship spacecraft Terra and Aqua. Between the two, MODAPS is generating over 1 Terrabyte of data per day and has surpassed 3 Petabytes of total data. The bulk of the data is stored near-line in StorageTek Powerhorn tape jukeboxes. Accessing data that has been moved to tape involves submitting an order, scheduling the tape, and waiting for the data to become available. I am developing a low cost clustered archive that could enable storing a very large amount of data such as the MODIS data described above in an organized fashion on a cluster of commodity hardware using low cost SATA hard drives such that the files are directly available online. The system takes full advantage of Open Source software, using the GNULinux operating system, PostgreSQL relational database and the Apache HTTP Server. This poster session will depict my approach, the interface to the archive, a brief discussion of the internals of the system and some performance numbers from my prototyping. I will also describe various costs and benefits of this approach versus the traditional large tape jukebox approach currently in use in the EOSDIS.

Tilmes, Curt↗

A system architecture for a planetary rover

Each planetary mission requires a complex space vehicle which integrates several functions to accomplish the mission and science objectives. A Mars Rover is one of these vehicles, and extends the normal spacecraft functionality with two additional functions: surface mobility and sample acquisition. All functions are assembled into a hierarchical and structured format to understand the complexities of interactions between functions during different mission times. It can graphically show data flow between functions, and most importantly, the necessary control flow to avoid unambiguous results. Diagrams are presented organizing the functions into a structured, block format where each block represents a major function at the system level. As such, there are six blocks representing telecomm, power, thermal, science, mobility and sampling under a supervisory block called Data Management/Executive. Each block is a simple collection of state machines arranged into a hierarchical order very close to the NASREM model for Telerobotics. Each layer within a block represents a level of control for a set of state machines that do the three primary interface functions: command, telemetry, and fault protection. This latter function is expanded to include automatic reactions to the environment as well as internal faults. Lastly, diagrams are presented that trace the system operations involved in moving from site to site after site selection. The diagrams clearly illustrate both the data and control flows. They also illustrate inter-block data transfers and a hierarchical approach to fault protection. This systems architecture can be used to determine functional requirements, interface specifications and be used as a mechanism for grouping subsystems (i.e., collecting groups of machines, or blocks consistent with good and testable implementations).

Smith, D. B.↗

Exploring Space on the Computer

For the past year Dennis Stocker has been in the process of developing pencil and paper games, which are fun, challenging, and educational for middle school and high school students. The latest version of these pencil and paper games is Spaceship Commander. The objective of the game is to earn points by plotting the flight path of a spaceship so astronauts can perform microgravity experiments, and make short-range measurements of other planets. During my ten weeks here at the GRC my goal is to create a computer based version of Spaceship commander. During the development of this game the primary focus has been on making it as educational and fun for the student as possible. The main educational objective of this game is to give students an understanding of forces and motion, including gravity. This is done by incorporating Newton's laws into the game. For example a spacecraft in the video game experiences a gravitational force applied to it by planets. The software I am using to create this game is a freeware application called Game Maker. Game Maker allows novice computer programmers like me to create arcade style games using a visual drag and drop interface. By using functions provided by Game Maker and a few I have written myself, I have been able to create a few simple computer games. Currently the computer game allows the student to navigate a space ship around planets, and asteroids by using the arrow keys on the numeric keypad. Each time an arrow key is pressed by the student the corresponding acceleration of the space ship is seen on the screen. Points are earned by navigating the space ship close enough to planets to gather scientific data. However the game encourages the student to plan his or her course carefully, because if the student gets too close to a planet they may not be able to escape the planet s gravity, and crash into the planet. The next step in the game development is to include a launch sequence which allows the student to launch from their home planet at a speed and direction determined by the student. Additional information is included in the original extended abstract.

Bozym, Patrick↗

Mars Science Laboratory Navigation Results

The Mars Science Laboratory (MSL), carrying the Curiosity rover to Mars, was launched on November 26, 2011, from Cape Canaveral, Florida. The target for MSL was selected to be Gale Crater, near the equator of Mars, with an arrival date in early August 2012. The two main interplanetary navigation tasks for the mission were to deliver the spacecraft to an entry interface point that would allow the rover to safely reach the landing area, and to tell the spacecraft where it entered the atmosphere of Mars, so it could guide itself accurately to close proximity of the landing target. MSL used entry guidance as it slowed down from the entry speed to a speed low enough to allow for a successful parachute deployment, and this guidance allowed shrinking the landing ellipse to a 99% conservative estimate of 7 by 20 kilometers. Since there is no global positioning system in Mars, achieving this accuracy was predicated on flying a trajectory that closely matched the reference trajectory used to design the guidance algorithm, and on initializing the guidance system with an accurate Mars-relative entry state that could be used as the starting point to integrate the inertial measurement unit data during entry and descent. The pre-launch entry flight path angle (EFPA) delivery requirement was +/- 0.20 deg, but after launch a smaller threshold of +/- 0.05 deg was used as the criteria for late trajectory correction maneuver (TCM) decisions. The pre-launch requirement for entry state knowledge was 2.8 kilometers in position error and 2 meters per second in velocity error, but also smaller thresholds were defined after launch to evaluate entry state update opportunities. The biggest challenge for the navigation team was to accurately predict the trajectory of the spacecraft, so the estimates of the entry conditions could be stable, and late trajectory correction maneuvers or entry parameter updates could be waved off. As a matter of fact, the prediction accuracy was such that the last TCM performed was a small burn executed eight days before landing, and the entry state that was calculated just 36 hours after that TCM, and that was uploaded to the spacecraft the same day, did not need to be updated. The final EFPA was 0.013 deg shallower than the -15.5 deg target, and the on-board entry state was just 200 meters in position and 0.11 meters per second in velocity from the post-landing reconstructed entry state. Overall the entry delivery and knowledge requirements were fulfilled with a margin of more than 90% with respect to the pre-launch thresholds. This excellent accuracy contributed to a very successful and accurate entry, descent, and landing, and surface mission.

navigation↗

Small Stirling Technology Exploration Power for Future Space Science Missions

High efficiency dynamic Radioisotope Power Systems (RPS) could be mission enabling for low power space applications such as small probes, landers rovers, and communication repeaters. These applications would contain science instruments and be distributed across planetary surfaces or near objects of interest where solar flux is insufficient for using solar cells. Small RPS could be used to provide power for sensing radiation, temperature, pressure, seismic activity, and other measurements of interest to planetary scientists. Small RPS would use fractional versions of the General Purpose Heat Source (GPHS) or Light Weight Radioisotope Heater Units (LWRHU), to heat power conversion technologies. Dynamic power systems are capable of three to four times higher conversion efficiency compared to static power conversion technologies, and would provide an equal amount of power using less fuel or more power using an equal amount of fuel. Providing spacecraft with more power could decrease duty cycling of basic functions and, therefore, increase the quality and abundance of science data. NASA GRC is developing a low power dynamic RPS that would convert heat from multiple LWRHU to one watt of usable direct current electric power for spacecraft instrumentation and communication. The power system could be used to charge batteries or capacitors for higher power burst usage. The initial design, called Small Stirling Technology Exploration Power (smallSTEP), is around 3 kg, 11 cm diameter X 32 cm long, and converts 8 watts of heat to one watt of electricity using a Stirling convertor. This low power conversion system represents a new class of RPS with power levels two orders of magnitude lower than prototypes currently being developed for space applications under NASA contracts. Development of the 1-watt RPS includes maturation of convertor and controller designs, performance evaluation of an evacuated metal foil insulation, and development of system interfaces. Initial demonstration of the subsystems has been completed in a laboratory environment and a higher fidelity system is being pursued for demonstration in relevant environments for use on small spacecraft needed to carry out future space science missions.

Wilson, Scott D.↗