Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Spacecraft Telemetry”

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 685 records · Page 38

Galileo

The purpose of the Galileo missions is to make observations of Jupiter and its satellites using an orbiting spacecraft and an atmospheric entry probe. The mission will determine the chemical composition and physical state of the Jovian atmosphere and its satellites, and the topology and behavior of the magnetic field and energetic particle flux of Jupiter. The mission plan calls for a Venus Earth Earth Gravity Assist (VEEGA) trajectory having a launch to end of mission duration of approximately 8 years. The Galileo spacecraft was placed in Earth orbit by the Space Transportation System (STS) on October 18, 1989. The Inertial Upper Stage (IUS) placed the spacecraft on a trajectory to encounter Venus on February 10, 1990. Information is given in tabular form for coverage goals, Deep Space Network (DSN) support, frequency assignments, telemetry, command, and tracking support responsibility.

Ausman, N. E.↗

Programmable Pacemaker

Released in 1995, the Trilogy cardiac pacemaker is the fourth generation of a unit developed in the 1970s by NASA, Johns Hopkins Applied Physics Laboratory and St. Jude Medical's Cardiac Rhythm Management Division (formerly known as Pacesetter Systems, Inc.). The new system incorporates the company's PDx diagnostic and programming software and a powerful microprocessor that allows more functions to be fully automatic and gives more detailed information on the patient's health and the performance of the pacing systems. The pacemaker incorporates bidirectional telemetry used for space communications for noninvasive communication with the implanted pacemaker, smaller implantable pulse generators from space microminiaturization, and longer-life batteries from technology for spacecraft electrical power systems.

Source record↗

Olympus propagation experiments

A summary of the activities of the OPEX (Olympus Propagation EXperimenters) group is given and some of the recent findings are presented. OLYMPUS, a telecommunication satellite owned by the European Space Agency, was launched on 12 June 1989. After the in-orbit tests were completed (in September 1989) the first propagation experiments started. Throughout 1990 the spacecraft functioned very well and a large number of experimenters received the beacon signals. On 29 May 1991 the spacecraft became inoperational after a major technical problem. With a series of complicated procedures OLYMPUS was recovered on 15 August 1991 - the first time in history that a civilian telecommunications satellite was brought back to service after losing power and telemetry. The propagation experiments were back on track. However, the recovery had used up so much fuel that the North-South station keeping had to be abandoned, which led to a natural increase of inclination at a rate of about 0.8 deg per year. On 10 October 1992 the second 30 GHz beacon tube failed, causing a loss of this beacon signal. The other two beacon frequencies continued to deliver a stable signal for more than two years. On 12 August 1993 the spacecraft experienced another problem with the altitude control, but this time there was not enough fuel left for a recovery maneuver and thus the mission came to an end.

Arbesser-Rastburg, Bertram↗

Revamping Spacecraft Operational Intelligence with Splunk

So what is Splunk? Instead of giving the technical details, which you can find online, I'll tell you what it did for me. Splunk slapped everything into one place, with one uniform format, and gave me the ability to forget about all these annoying details of where it is, how to parse it, and all that. Instead, I only need to interact with Splunk to find the data I need. This sounds simple and obvious, but it's surprising what you can do once you all of your data is indexed in one place. By having your data organized, querying becomes much easier. Let's say that I want to search telemetry for a sensor_name gtemp_1 h and to return all data that is at most five minutes old. And because Splunk can hook into a real ]time stream, this data will always be up-to-date. Extending the previous example, I can now aggregate all types of data into one view based in time. In this picture, I've got transaction logs, telemetry, and downlinked files all in one page, organized by time. Even though the raw data looks completely than this, I've defined interfaces that transform it into this uniform format. This gives me a more complete picture for the question what was the spacecraft doing at this particular time? And because querying data is simple, I can start with a big block of data and whiddle it down to what I need, rather than hunting around for the individual pieces of data that I need. When we have all the data we need, we can begin widdling down the data with Splunk's Unix-like search syntax. These three examples highlights my trial-and-error attempts to find large temperature changes. I begin by showing the first 5 temperatures, only to find that they're sorted chronologically, rather than from highest temperatures to lowest temperatures. The next line shows sorting temperatures by their values, but I find that that fs not really what I want either. I want to know the delta temperatures between readings. Looking through Splunk's user manual, I find the delta function, which lets me dynamically generate new information to use in my query. With that extra piece of information, I can now return only the telemetry readings where the temperature changed by at least 10. One other useful feature I'll mention is that all of these queries can be run through Splunk's API. So any scripting language you can think of can plug right in and make these queries. This gives us the ability to build a lot of new tools.

operational intelligence↗

Telecommunications and data acquisition support for the Pioneer Venus Project: Pioneers 12 and 13, prelaunch through March 1984

The support provided by the Telecommunications and Data Acquisition organization of the Jet Propulsion Laboratory (JPL) to the Pioneer Venus missions is described. The missions were the responsibility of the Ames Research Center (ARC). The Pioneer 13 mission and its spacecraft design presented one of the greatest challenges to the Deep Space Network (DSN) in the implementation and operation of new capabilities. The four probes that were to enter the atmosphere of Venus were turned on shortly before arrival at Venus, and the DSN had to acquire each of these probes in order to recover the telemetry being transmitted. Furthermore, a science experiment involving these probes descending through the atmosphere required a completed new data type to be generated at the ground stations. This new data type is known as the differential very long baseline interferometry. Discussions between ARC and JPL of the implementation requirements involved trade-offs in spacecraft design and led to a very successful return of science data. Specific implementation and operational techniques are discussed, not only for the prime mission, but also for the extended support to the Pioneer 12 spacecraft (in orbit around Venus) with its science instruments including that for radar observations of the planet.

Miller, R. B.↗

Proposed data compression schemes for the Galileo S-band contingency mission

The Galileo spacecraft is currently on its way to Jupiter and its moons. In April 1991, the high gain antenna (HGA) failed to deploy as commanded. In case the current efforts to deploy the HGA fails, communications during the Jupiter encounters will be through one of two low gain antenna (LGA) on an S-band (2.3 GHz) carrier. A lot of effort has been and will be conducted to attempt to open the HGA. Also various options for improving Galileo's telemetry downlink performance are being evaluated in the event that the HGA will not open at Jupiter arrival. Among all viable options the most promising and powerful one is to perform image and non-image data compression in software onboard the spacecraft. This involves in-flight re-programming of the existing flight software of Galileo's Command and Data Subsystem processors and Attitude and Articulation Control System (AACS) processor, which have very limited computational and memory resources. In this article we describe the proposed data compression algorithms and give their respective compression performance. The planned image compression algorithm is a 4 x 4 or an 8 x 8 multiplication-free integer cosine transform (ICT) scheme, which can be viewed as an integer approximation of the popular discrete cosine transform (DCT) scheme. The implementation complexity of the ICT schemes is much lower than the DCT-based schemes, yet the performances of the two algorithms are indistinguishable. The proposed non-image compression algorith is a Lempel-Ziv-Welch (LZW) variant, which is a lossless universal compression algorithm based on a dynamic dictionary lookup table. We developed a simple and efficient hashing function to perform the string search.

Cheung, Kar-Ming↗

Analysis of the Artemis I Orion Spacecraft Power System Performance

NASA successfully completed an uncrewed test flight of the Orion spacecraft during the 26-day Artemis I mission in November and December 2022. The Artemis I mission profile included several potentially stressing features for Orion electrical power system (EPS) performance, including eclipse duration, multiple propulsive or navigational maneuvers which constrained positioning of the solar array wings (SAWs), and the proximity and phasing of various events together. All of these features vary significantly with Earth-sun-moon geometry, providing a unique challenge for predicting EPS performance before an exact launch date is known. This presentation will provide a brief mission overview, discuss the different computer models with varying levels of fidelity used to analyze Orion EPS performance, as well as the screening process developed to incorporate EPS performance as a consideration for launch epoch selection. Final preflight model predictions of EPS performance will be compared to in-flight telemetry measurements, and several EPS anomalies observed will be briefly discussed.

Orion↗

Plasma Effects

Radio communication with space probes requires sending signals through the Earth's ionosphere and usually the solar wind. During planetary flybys, the signal may also pass through the ionosphere of another planet. These ionized media can perturb the radio signal in a variety of ways. Examples of these perturbations are variations in the electrical length between the spacecraft and the ground station, Faraday rotation of linearly polarized signals, amplitude and phase scintillations, and spectral and angular broadening. These plasma effects can have undesirable influences on telemetry performance and thus need to be understood from a communications engineering viewpoint. The plasma effects are, however, useful from a scientific viewpoint, since the effects on the communications link can often be inverted to estimate the physical conditions in the plasma.

Armstrong, J. W.↗

The Small Explorer power system

A direct-energy-transfer (DET) power system design with the battery connected directly to the bus was selected as the generic power system to satisfy the various Small Explorer spacecraft missions. The power system electronics (PSE) are designated to handle power levels up to a 250-W load with minimum changes in the electronics. The command and telemetry interface is through an optical MIL-STD-1773 interface that is contained in the PSE. The system provides high performance, low weight, and low EMI (electromagnetic interference) generation. The design and performance of the power system have been verified through analysis and extensive tests on a breadboard.

Dakermanji, George↗

Deep Space Network (DSN), Network Operations Control Center (NOCC) computer-human interfaces

The technical challenges, engineering solutions, and results of the NOCC computer-human interface design are presented. The use-centered design process was as follows: determine the design criteria for user concerns; assess the impact of design decisions on the users; and determine the technical aspects of the implementation (tools, platforms, etc.). The NOCC hardware architecture is illustrated. A graphical model of the DSN that represented the hierarchical structure of the data was constructed. The DSN spacecraft summary display is shown. Navigation from top to bottom is accomplished by clicking the appropriate button for the element about which the user desires more detail. The telemetry summary display and the antenna color decision table are also shown.

Ellman, Alvin↗

Fast Plasma Instrument for MMS: Data Compression Simulation Results

Magnetospheric Multiscale (MMS) mission will study small-scale reconnection structures and their rapid motions from closely spaced platforms using instruments capable of high angular, energy, and time resolution measurements. To meet these requirements, the Fast Plasma Instrument (FPI) consists of eight (8) identical half top-hat electron sensors and eights (8) identical ion sensors and an Instrument Data Processing Unit (IDPU). The sensors (electron or ion) are grouped into pairs whose 6 deg x 180 deg fields-of-view (FOV) are set 90 deg apart. Each sensor is equipped with electrostatic aperture steering to allow the sensor to scan a 45 deg x 180 deg fan about its nominal viewing (0 deg deflection) direction. Each pair of sensors, known as the Dual Electron Spectrometer (DES) and the Dual Ion Spectrometer (DIS), occupies a quadrant on the MMS spacecraft and the combination of the eight electron/ion sensors, employing aperture steering, image the full-sky every 30-ms (electrons) and 150-ms (ions), respectively. To probe the results in the DES complement of a given spacecraft generating 6.5-Mbs(exp -1) of electron data while the DIS generates 1.1-Mbs(exp -1) of ion data yielding an FPI total data rate of 6.6-MBs(exp -1). The FPI electron/ion data is collected by the IDPU then transmitted to the Central Data Instrument Processor (CIDP) on the spacecraft for science interest ranking. Only data sequences that contain the greatest amount of temporal/spatial structure will be intelligently down-linked by the spacecraft. Currently, the FPI data rate allocation to the CIDP is 1.5-Mbs(exp -1). Consequently, the FPI-IDPU must employ data/image compression to meet this CIDP telemetry allocation. Here, we present simulations of the CCSDS 122.0-B-1 algorithm-based compression of the FPI-DES electron data. Compression analysis is based upon a seed of re-processed Cluster/PEACE electron measurements. Topics to be discussed include: review of compression algorithm; data quality; data formatting/organization; and, implications for data/matrix pruning. To conclude a presentation of the base-lined FPI data compression approach is provided.

Barrie, A.↗

Planetary Image Geometry Library

The Planetary Image Geometry (PIG) library is a multi-mission library used for projecting images (EDRs, or Experiment Data Records) and managing their geometry for in-situ missions. A collection of models describes cameras and their articulation, allowing application programs such as mosaickers, terrain generators, and pointing correction tools to be written in a multi-mission manner, without any knowledge of parameters specific to the supported missions. Camera model objects allow transformation of image coordinates to and from view vectors in XYZ space. Pointing models, specific to each mission, describe how to orient the camera models based on telemetry or other information. Surface models describe the surface in general terms. Coordinate system objects manage the various coordinate systems involved in most missions. File objects manage access to metadata (labels, including telemetry information) in the input EDRs and RDRs (Reduced Data Records). Label models manage metadata information in output files. Site objects keep track of different locations where the spacecraft might be at a given time. Radiometry models allow correction of radiometry for an image. Mission objects contain basic mission parameters. Pointing adjustment ("nav") files allow pointing to be corrected. The object-oriented structure (C++) makes it easy to subclass just the pieces of the library that are truly mission-specific. Typically, this involves just the pointing model and coordinate systems, and parts of the file model. Once the library was developed (initially for Mars Polar Lander, MPL), adding new missions ranged from two days to a few months, resulting in significant cost savings as compared to rewriting all the application programs for each mission. Currently supported missions include Mars Pathfinder (MPF), MPL, Mars Exploration Rover (MER), Phoenix, and Mars Science Lab (MSL). Applications based on this library create the majority of operational image RDRs for those missions. A Java wrapper around the library allows parts of it to be used from Java code (via a native JNI interface). Future conversions of all or part of the library to Java are contemplated.

Deen, Robert C.↗

Science Enabling ASICs and FEEs for the JUICE and JEO Missions

A family of science enabling radiation hard Application Specific Integrated Circuits (ASICs), Front End Electronics (FEEs) and Event Processing Systems, with flight heritage on many NASA missions, is presented. These technologies play an important role in the miniaturization of instruments -and spacecraft systems- at the same time increasing performance and reducing power. The technologies target time of flight, position sensing, and energy measurements as well as standard housekeeping and telemetry functions for particle and fields instruments, but find applications in other instrument categories too. More specifically the technologies include: the TOF chip, 1D and 2D Delay Lines with MCP detectors, for high precision fast and low power time of flight and position sensing; the Energy chip for multichannel SSD readout with time over threshold and standard voltage read out for TDC and ADC digitization; Fast multi channel read out chip with commandable thresholds; the TRIO chip for multiplexed ADC and housekeeping etc. It should be mentioned that the ASICs include basic trigger capabilities to enable random event processing in a heavy background of penetrators and UV foreground. Typical instruments include time of flight versus energy and look angle particle analyzers such as: plasma composition, energetic particle, neutral atom imaging as well as fast plasma and deltaE/E ion/electron telescopes. Flight missions include: Cassini/LEMMS, IMAGE/HENA, MESSENGER/EPPS/MLA/X-ray/MLA, STEREO, PLUTO-NH/PEPSSI/LORI, IBEX-Lo, JUNO/JEDI, RBSP/RBSPICE, MMS/HPCA/EPD, SO/SIS. Given the proven capability on heavy radiation missions such as JUNO, MMS and RBSB, as well diverse long duration missions such as MESSENGER, PLUTO and Cassini, it is expected that these technologies will play an important role in the particle and fields (at least) instruments on the upcoming JUICE and JEO missions.

Paschalidis, Nicholas↗

Pre-Flight Assessment of Xenon Propellant Usage and Usage Uncertainty for the Psyche Mission

NASA’s Psyche mission will launch in 2022 and begin a 3.6-year cruise to the metallic asteroid Psyche, the largest metal asteroid in the solar system. All primary propulsion will be done with the flight-proven SPT-140 electric propulsion subsystem. The Psyche mission will feature the first use of Hall thrusters for a NASA mission, and the first use of Hall thrusters beyond cis-lunar space, which has presented some unique challenges. In this paper we describe the Psyche propellant feed system architecture, expected propellant usage for the mission, propellant gauging requirements, and challenges associated with propellant gauging. Data from two recent Maxar electric orbit-raising missions with SPT-140 thrusters are reviewed and used to assess in-flight performance. We develop a pressure-volume-temperature gauging method that incorporates the propellant temperature distributions observed in the flight data, and use this method to provide an improved quantitative understanding of in-flight propellant consumption rates and their uncertainties. The results are in excellent agreement with the results of standard Maxar gauging methods and we determine a propellant usage uncertainty of ± 7.1% 3σ based on flight telemetry. Additionally, we demonstrate that the bookkeeping method of propellant gauging accurately predicts the tank pressure flight data. This work has led to design changes in the Psyche spacecraft avionics that will further improve propellant gauging uncertainties, which is particularly important for later phases of the mission. Finally, we statistically combine the predicted propellant mass uncertainties from the two gauging methods and demonstrate that the system will meet the mission requirements for propellant uncertainty. Together, all of this work provides confidence that the Psyche mission can be successfully completed within the existing propellant budget and propellant tank capacity.

Baldwin, Jeff↗

James Webb Space Telescope Fuel Slosh Estimation

The mitigation of fuel slosh in microgravity environments is a pressing matter for the control of both manned and unmanned spacecraft. Recent work has investigated negative mass modeling of fuel slosh using Lie Group SE(3) . This paper applies Lie group SE(3) to the full body problem of spacecraft dynamics to investigate attitude perturbations caused by fuel slosh aboard the James Webb Space Telescope (JWST). We develop a dynamical model to parse these perturbations from slew telemetry data via residuals analysis. This model uses a novel, N-body Runge-Kutta integrator in the special Euclidean group SE(3). The enhanced ability to validate fuel slosh models reduces settling time after slew operations and, accordingly, maximizes available science time.

GN&C↗

Orbiting Deep Space Relay Station (ODSRS). Volume 1: Requirement determination

The deep space communications requirements of the post-1985 time frame are described and the orbiting deep space relay station (ODSRS) is presented as an option for meeting these requirements. Under current conditions, the ODSRS is not yet cost competitive with Earth based stations to increase DSN telemetry performance, but has significant advantages over a ground station, and these are sufficient to maintain it as a future option. These advantages include: the ability to track a spacecraft 24 hours per day with ground stations located only in the USA; the ability to operate at higher frequencies that would be attenuated by Earth's atmosphere; and the potential for building very large structures without the constraints of Earth's gravity.

Hunter, J. A.↗

Generic telemetry processing

The Space Flight Operations Center (SFOC) is a generic suite of ground data systems software. One main subsystem of SFOC is the Telemetry Input Subsystem (TIS). Utilizing techniques for the abstract representation of data, the TIS has provided a flexible software base that can be used as a baseline for multiple spacecraft missions.

Pettit, Richard L., Jr.↗