Search NASA⌕ Search

SEARCH · Search NASA

Results for “relay orbit”

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 523 records · Page 29

Preliminary design for a Zero Gravity Test Facility (ZGTF). Volume 1: Technical

The functional requirements and best conceptual design of a test facility that simulates weightless operating conditions for a high gain antenna systems (HGAS), that will broadcast to the Tracking Data Relay Satellites were defined. The typical HGAS defined is mounted on a low Earth orbiting satellite, and consists of an antenna with a double gimbal pointing system mounted on a 13 foot long mast. Typically, the gimbals are driven by pulse modulated dc motors or stepper motors. These drivers produce torques on the mast, with jitter that excites the satellite and may cause disturbances to sensitive experiments. The dynamic properties of the antenna support structure (mast), including flexible mode characteristics were defined. The torque profile induced on the spacecraft by motion of the high gain antenna was estimated. Gain and phase margins of the servo control loop of the gimbal drive electronics was also verified.

Germain, A.↗

Orbiter attitude design for the Astro-1 Spacelab mission

The methods utilized to design orbiter attitudes that satisfied the various Space Shuttle program and payload constraints of the Astro-1 Spacelab astronomy mission are described. The premission methods developed for attitude design and how those methods were applied to accomplish the large amount of real-time replanning required during the flight are presented. Some of the attitude concerns for Astro-1 included orbiter window thermal constraints, two separate telescope fields-of-view, tracking and data relay satellite Ku-band access, and telescope sun avoidance.

Olsen, C. D.↗

Return to the Red Planet

In November 1996, NASA and the Jet Propulsion Laboratory will begin America's return to Mars after a 20-year absence by launching the Mars Global Surveyor (MGS) spacecraft. This mission will usher in a new and exciting era of scientific missions to study the red planet.

Altimeter Thermal Emission Spectrometer Magnetomet↗

NASA Lunar Exploration – Gateway’s Power and Propulsion Element Communications Links

As a key part of NASA’s Artemis program to return to the moon, the Lunar Gateway will provide a platform for staging lunar missions, for gaining experience in operations beyond earth orbit, and for creating sustainable infrastructure. Of specific interest, the Lunar Gateway will provide communications support to landers, orbiters, and surface systems, including in the South Polar Region where direct line of sight (LOS) to Earth is limited or non-existent. A foundational segment of the Gateway is the Power and Propulsion Element (PPE), which will carry: solar arrays to provide power to the Gateway; electric propulsion to maintain the Gateway in its operational orbit; and communication links between the Earth and Gateway, the Moon and Gateway, and relays from the Moon to the Earth. PPE Communication Links include an X-band link to Earth for Command, Ranging, and Telemetry (CR&T), which also carries low to medium rate data; a Ka-band Direct to Earth(DTE) link for high rate data transmissions; and a Ka-band Lunar link for high data rate connections to lunar systems. This paper describes the PPE communication links from a technical perspective. Other Gateway links supported by other modules are outside the scope of this paper.

ARTEMIS↗

Solar Dynamics Observatory Guidance, Navigation, and Control System Overview

The Solar Dynamics Observatory (SDO) was designed and built at the Goddard Space Flight Center, launched from Cape Canaveral on February 11, 2010, and reached its final geosynchronous science orbit on March 16, 2010. The purpose of SDO is to observe the Sun and continuously relay data to a dedicated ground station. SDO remains Sun-pointing throughout most of its mission for the instruments to take measurements of the Sun. The SDO attitude control system (ACS) is a single-fault tolerant design. Its fully redundant attitude sensor complement includes sixteen coarse Sun sensors (CSSs), a digital Sun sensor (DSS), three two-axis inertial reference units (IRUs), and two star trackers (STs). The ACS also makes use of the four guide telescopes included as a part of one of the science instruments. Attitude actuation is performed using four reaction wheels assemblies (RWAs) and eight thrusters, with a single main engine used to provide velocity-change thrust for orbit raising. The attitude control software has five nominal control modes, three wheel-based modes and two thruster-based modes. A wheel-based Safehold running in the attitude control electronics box improves the robustness of the system as a whole. All six modes are designed on the same basic proportional-integral-derivative attitude error structure, with more robust modes setting their integral gains to zero. This paper details the final overall design of the SDO guidance, navigation, and control (GN&C) system and how it was used in practice during SDO launch, commissioning, and nominal operations. This overview will include the ACS control modes, attitude determination and sensor calibration, the high gain antenna (HGA) calibration, and jitter mitigation operation. The Solar Dynamics Observatory mission is part of the NASA Living With a Star program, which seeks to understand the changing Sun and its effects on the Solar System, life, and society. To this end, the SDO spacecraft carries three Sun-observing instruments: Helioseismic and Magnetic Imager (HMI), led by Stanford University; Atmospheric Imaging Assembly (AIA), led by Lockheed Martin Space and Astrophysics Laboratory; and Extreme Ultraviolet Variability Experiment (EVE), led by the University of Colorado. The basic mission is to observe the Sun for a very high percentage of the 5-year mission (10-year goal) with long stretches of uninterrupted observations and with constant, high-data-rate transmission to a dedicated ground station to be located in White Sands, New Mexico. These goals guided the design of the spacecraft bus that will carry and service the three-instrument payload. Overarching design goals for the bus are geosynchronous orbit, near-constant Sun observations with the ability to fly through eclipses, and constant HGA contact with the dedicated ground station. A three-axis stabilized ACS is needed both to point at the Sun accurately and to keep the roll about the Sun vector correctly positioned with respect to the solar north pole. This roll control is especially important for the magnetic field imaging of HM I. The mission requirements have several general impacts on the ACS design. Both the AIA and HMI instruments are very sensitive to the blurring caused by jitter. Each has an image stabilization system (ISS) with some ability to filter out high frequency motion, but below the bandwidth of the ISS the control system must compensate for disturbances within the ACS bandwidth or avoid exciting jitter at higher frequencies. Within the ACS bandwidth, the control requirement imposed by AIA is to place the center of the solar disk no more than 2 arc sec, 3 , from a body-defined target based on one of the GTs that accompany the instrument. This body-defined target, called the science reference boresight (SRB), was determined from the postlaunch orientation of the GTs by averaging the bounding telescope boresights for pitch to get a pitch SRB coordinate, and by averaging the bounding boresights for yaw toet the yaw SRB coordinate. The location of this SRB in the 0.5-deg field-of-view for each GT then becomes the central target for each telescope; one GT is selected for use as the ACS controlling guide telescope (CGT) at any given time. Fine Sun-pointing is effected based on this SRB for all three instruments when the Sun is within the linear range of the CGT. In addition to limiting jitter, HMI science requires averaging several observations, making the instrument sensitive to low frequency motion that induces differential motion between each observation. This requires the spacecraft attitude to be stable about the roll axis to approximately 10 arcsec over a ten-minute period. Instrument calibrations require that the spacecraft point the SRB up to 2.5 degrees in pitch and yaw away from the center of the Sun, placing the Sun outside the field-of-view of the guide telescopes. In such instances, when the GTs cannot provide the definitive target for the ACS, on-board attitude determination combined with ephemeris prediction of the Sun direction must provide the definitive target. EVE is capable of observing the Sun with less dependence on attitude control. However, the ground data processing needs for calibrations result in the most strict attitude knowledge requirements for the mission: [35,70,70] arcsec, 3 , of knowledge with respect to the center of the solar disk. In addition to driving the ACS sensor selection, the knowledge requirements, which have their effect primarily during Inertial mode calibrations, drive the accuracy requirements for the solar ephemeris. The need to achieve and maintain geosynchronous orbit (GEO) drove the need for high-efficiency propulsive systems and appropriate attitude control. The main engine provided high specific impulse for the maneuvers to attain GEO, while the smaller ACS thrusters managed the disturbance torques of the larger engine and provided the capability for much smaller adjustment burns on orbit. SDO s large solar profile means that solar radiation pressure is a large torque disturbance, and the momentum buildup from this disturbance and the GEO altitude drives the ACS to use thrusters to manage vehicle momentum. The demanding data capture budget for the mission, however, requires SDO to avoid frequent thruster maneuvers, while concerns about on-orbit jitter restrict the maximum desired wheel speeds desired from the RWAs. The plan for on-orbit wheel speed and momentum management will be discussed as well as what is now being done in operation after the jitter environment was characterized. The SDO ACS hardware complement is single-fault tolerant. Two main processors carry virtually identical copies of the command and data handling and ACS software, and two identical attitude control electronics (ACE) boxes carry Coldfire processors with contingency ACS software and other hardware interface cards; the ACE structure allows reaction wheels to be commanded by the Sun-pointing Safehold independent of the Mil Std 1553 data bus. The sixteen Adcole CSSs are grouped into primary and backup sets of eight sensors, each set providing the ability to calculate a sun vector. Each set of eight eyes provides full 4 -steradian coverage. The Adcole DSS comprises an optics head and a separate electronics box providing a 1553 data interface. The electronics box is mounted inside the Faraday cage created by the spacecraft bus module. The DSS head with its 32- deg square FOV is mounted on the instrument module with its boresight along the spacecraft X axis, nearly aligned with the Sun during observations. Adcole has designed the DSS calibration parameters so that the accuracy is 0.24 arcminutes within 10 deg of the boresight, and diminishes to 3 arcminutes as the Sun moves towards the edges of its FOV . This DSS calibration scheme provides higher accuracy attitude determination over the range of the instrument calibration maneuvers.

Morgenstern, Wendy M.↗

Measurement of the Earth-Observer-1 Satellite X-Band Phased Array

The recent launch and successful orbiting of the EO-1 Satellite has provided an opportunity to validate the performance of a newly developed X-Band transmit-only phased array aboard the satellite. This paper will compare results of planar near-field testing before and after spacecraft installation as well as on-orbit pattern characterization. The transmit-only array is used as a high data rate antenna for relaying scientific data from the satellite to earth stations. The antenna contains distributed solid-state amplifiers behind each antenna element that cannot be monitored except for radiation pattern measurements. A unique portable planar near-field scanner allows both radiation pattern measurements and also diagnostics of array aperture distribution before and after environmental testing over the ground-integration and prelaunch testing of the satellite. The antenna beam scanning software was confirmed from actual pattern measurements of the scanned beam positions during the spacecraft assembly testing. The scanned radiation patterns on-orbit were compared to the near-field patterns made before launch to confirm the antenna performance. The near-field measurement scanner has provided a versatile testing method for satellite high gain data-link antennas.

Perko, Kenneth↗

MarCO: Interplanetary Mission Development on a CubeSat Scale

Shortly after JPL’s Interior Exploration using Seismic Investigations, Geodesy and Heat Transport (InSight) mission launches, separates, and commences its cruise phase, two CubeSats will deploy from the launch vehicle’s upper stage and begin independent flight to Mars (Fig. 1). During InSight’s entry, descent, and landing (EDL) sequence, these twin Mars Cube One (MarCO) spacecraft will fly 3,500 km above the Martian surface, recording and relaying InSight UHF radio data to the Deep Space Network (DSN) on Earth1. MarCO is a twin CubeSat mission developed by the NASA Jet Propulsion Laboratory (JPL) to accompany the InSight (Interior Exploration using Seismic Investigations, Geodesy and Heat Transport) Mars mission lander. MarCO's primary mission objective is to launch with InSight and independently fly to Mars to serve as a communications relay during InSight's entry, descent, and landing (EDL) phase. MarCO represents a new type of deep space mission: CubeSats at Mars. Building on the development of JPL's first interplanetary CubeSat project, the Interplanetary Nano-Spacecraft Pathfinder in Relevant Environment (INSPIRE), MarCO further refined the approach to hardware, software, and ground architecture development to solve the challenges of quickly building low-budget spacecraft to fly to Mars. The greatest constraint, beyond others typical of CubeSat missions, was time. The duration between MarCO's conception to completion of spacecraft assembly was less than two years - an unprecedented schedule for any planetary mission to date. Through necessity, MarCO has built on previous experience, procedures, systems, and development methodologies, defining a new niche for supporting larger primary missions. The MarCO spacecraft are poised to write a new chapter in deep space exploration. Originally slated to launch and reach Mars in 2016, the InSight mission schedule subsequently slipped to 2018. During the original landing of InSight, Earth would not be in view, and no orbiter around Mars would have been in position to both receive UHF EDL data and simultaneously relay it back to Earth. It was from this obstacle that MarCO was conceived. Regardless of any changes to InSight’s 2018 EDL configuration geometry, MarCO is still expected to fly and serve in the same capacity as originally designed: the first CubeSat mission to Mars. CubeSats have historically been firmly in the domain of universities and small companies. As first conceived, they served as a platform upon which to teach all aspects of the space mission lifecycle. JPL took on this mission type with Interplanetary Nano-Spacecraft Pathfinder in Relevant Environment2 (INSPIRE), moving the concept into a new domain: deep space. Building from the INSPIRE platform and lessons learned, MarCO addressed new challenges in the domain of planetary missions: independent interplanetary flight and navigation, integration with a large-scale mission, long-distance and long-delay communication, short development time, and a small development team. Of these, the greatest constraint was schedule: only 18 months passed from conception of mission concept until delivery of fully assembled and tested flight hardware. Careful selection of mission team, along with extensive use of off-the-shelf equipment, and streamlining automated processes, was essential. This achievement represents the next step in the evolution of CubeSats beyond low-Earth orbit.

Werne, Thomas↗

Real-Time Multimission Event Notification System for Mars Relay

As the Mars Relay Network is in constant flux (missions and teams going through their daily workflow), it is imperative that users are aware of such state changes. For example, a change by an orbiter team can affect operations on a lander team. This software provides an ambient view of the real-time status of the Mars network. The Mars Relay Operations Service (MaROS) comprises a number of tools to coordinate, plan, and visualize various aspects of the Mars Relay Network. As part of MaROS, a feature set was developed that operates on several levels of the software architecture. These levels include a Web-based user interface, a back-end "ReSTlet" built in Java, and databases that store the data as it is received from the network. The result is a real-time event notification and management system, so mission teams can track and act upon events on a moment-by-moment basis. This software retrieves events from MaROS and displays them to the end user. Updates happen in real time, i.e., messages are pushed to the user while logged into the system, and queued when the user is not online for later viewing. The software does not do away with the email notifications, but augments them with in-line notifications. Further, this software expands the events that can generate a notification, and allows user-generated notifications. Existing software sends a smaller subset of mission-generated notifications via email. A common complaint of users was that the system-generated e-mails often "get lost" with other e-mail that comes in. This software allows for an expanded set (including user-generated) of notifications displayed in-line of the program. By separating notifications, this can improve a user's workflow.

Wallick, Michael N.↗

The Earth Based Ground Stations Element of the Lunar Program

The Lunar Architecture Team (LAT) is responsible for developing a concept for building and supporting a lunar outpost with several exploration capabilities such as rovers, colonization, and observatories. The lunar outpost is planned to be located at the Moon's South Pole. The LAT Communications and Navigation Team (C&N) is responsible for defining the network infrastructure to support the lunar outpost. The following elements are needed to support lunar outpost activities: A Lunar surface network based on industry standard wireless 802.xx protocols, relay satellites positioned 180 degrees apart to provide South Pole coverage for the half of the lunar 28-day orbit that is obscured from Earth view, earth-based ground stations deployed at geographical locations 120 degrees apart. This paper will focus on the Earth ground stations of the lunar architecture. Two types of ground station networks are discussed. One provides Direct to Earth (DTE) support to lunar users using Kaband 23/26Giga-Hertz (GHz) communication frequencies. The second supports the Lunar Relay Satellite (LRS) that will be using Ka-band 40/37GHz (Q-band). This paper will discuss strategies to provide a robust operational network in support of various lunar missions and trades of building new antennas at non-NASA facilities, to improve coverage and provide site diversification for handling rain attenuation.

Gal-Edd, Jonathan↗

Advanced solar-propelled cargo spacecraft for Mars missions

At the University of Washington, three concepts for an unmanned, solar powered, cargo spacecraft for Mars-support missions have been investigated. These spacecraft are designed to carry a 50,000 kg payload from a low Earth orbit to a low Mars orbit. Each design uses a distinctly different propulsion system: a solar radiation absorption (SRA) system, a solar-pumped laser (SPL) system, and a solar powered mangetoplasmadynamic (MPD) arc system. The SRA directly converts solar energy to thermal energy in the propellant through a novel process developed at the University of Washington. A solar concentrator focuses sunlight into an absorption chamber. A mixture of hydrogen and potassium vapor absorbs the incident radiation and is heated to approximately 3700 K. The hot propellant gas exhausts through a nozzle to produce thrust. The SRA has an I(sub sp) of approximately 1000 sec and produces a thrust of 2940 N using two thrust chambers. In the SPL system, a pair of solar-pumped, multi-megawatt, CO2 lasers in sun-synchronous Earth orbit converts solar energy to laser energy. The laser beams are transmitted to the spacecraft via laser relay satellites. The laser energy heats the hydrogen propellant through a plasma breakdown process in the center of an absorption chamber. Propellant flowing through the chamber, heated by the plasma core, expands through a nozzle to produce thrust. The SPL has an I(sub sp) of 1285 sec and produces a thrust of 1200 N using two thrust chambers. The MPD system uses indium phosphide solar cells to convert sunlight to electricity, which powers the propulsion system. In this system, the argon propellant is ionized and electromagnetically accelerated by a magnetoplasmadynamic arc to produce thrust. The MPD spacecraft has an I(sub sp) of 2490 sec and produces a thrust of 100 N. Various orbital transfer options are examined for these concepts. In the SRA system, the mother ship transfers the payload into a very high Earth orbit and a small auxiliary propulsion system boosts the payload into a Hohmann transfer to Mars. The SPL spacecraft releases the payload as the spacecraft passes by Mars. Both the SRA-powered spacecraft and the SPL-powered spacecraft return to Earth for subsequent missions. The MPD-propelled spacecraft, however, remains at Mars as an orbiting space station. A patched conic approximation was used to determine a heliocentric interplanetary transfer orbit for the MPD propelled spacecraft. All three solar-powered spacecraft use an aerobrake procedure to place the payload into a low Mars parking orbit. The payload delivery times range from 160 days to 873 days (2.39 years).

Auziasdeturenne, J.↗

Cosmic background explorer (COBE) navigation with TDRSS one-way return-link Doppler in the post-helium-venting phase

A navigation experiment was performed which establishes Ultra-Stable Oscillator (USO) frequency stabilized one way return link Doppler TDRSS tracking data as a feasible option for mission orbit determination support at the Goddard Space Center Flight Dynamics Facility. The study was conducted using both one way and two way Tracking and Data Relay Satellite System (TDRSS) tracking measurements for the Cosmic Background Explorer (COBE) spacecraft. Tracking data for a 4 week period immediately follow the depletion of the helium supply was used. The study showed that, for both definitive orbit solution and short term orbit prediction (up to 4 weeks), orbit determination results based on one way return link Doppler tracking measurements are comparable to orbit determination results based on two way range and two way Doppler tracking measurements.

Nemesure, M.↗

Automation of orbit determination functions for National Aeronautics and Space Administration (NASA)-supported satellite missions

The Flight Dynamics Facility (FDF) at Goddard Space Flight Center (GSFC) provides spacecraft trajectory determination for a wide variety of National Aeronautics and Space Administration (NASA)-supported satellite missions, using the Tracking Data Relay Satellite System (TDRSS) and Ground Spaceflight and Tracking Data Network (GSTDN). To take advantage of computerized decision making processes that can be used in spacecraft navigation, the Orbit Determination Automation System (ODAS) was designed, developed, and implemented as a prototype system to automate orbit determination (OD) and orbit quality assurance (QA) functions performed by orbit operations. Based on a machine-resident generic schedule and predetermined mission-dependent QA criteria, ODAS autonomously activates an interface with the existing trajectory determination system using a batch least-squares differential correction algorithm to perform the basic OD functions. The computational parameters determined during the OD are processed to make computerized decisions regarding QA, and a controlled recovery process isactivated when the criteria are not satisfied. The complete cycle is autonomous and continuous. ODAS was extensively tested for performance under conditions resembling actual operational conditions and found to be effective and reliable for extended autonomous OD. Details of the system structure and function are discussed, and test results are presented.

Mardirossian, H.↗

Automation of orbit determination functions for National Aeronautics and Space Administration (NASA)-supported satellite missions

The Flight Dynamics Facility (FDF) at Goddard Space Flight Center (GSFC) provides spacecraft trajectory determination for a wide variety of National Aeronautics and Space Administration (NASA)-supported satellite missions, using the Tracking Data Relay Satellite System (TDRSS) and Ground Spaceflight and Tracking Data Network (GSTDN). To take advantage of computerized decision making processes that can be used in spacecraft navigation, the Orbit Determination Automation System (ODAS) was designed, developed, and implemented as a prototype system to automate orbit determination (OD) and orbit quality assurance (QA) functions performed by orbit operations. Based on a machine-resident generic schedule and predetermined mission-dependent QA criteria, ODAS autonomously activates an interface with the existing trajectory determination system using a batch least-squares differential correction algorithm to perform the basic OD functions. The computational parameters determined during the OD are processed to make computerized decisions regarding QA, and a controlled recovery process is activated when the criteria are not satisfied. The complete cycle is autonomous and continuous. ODAS was extensively tested for performance under conditions resembling actual operational conditions and found to be effective and reliable for extended autonomous OD. Details of the system structure and function are discussed, and test results are presented.

Mardirossian, H.↗

Lessons Learned from Coordinating Relay Activities at Mars

The Mission Management Office at the Jet Propulsion Laboratory was tasked with coordinating the relay of data between multiple spacecraft at Mars in support of the Mars Exploration Rover Missions in early 2004. The confluence of three orbiters (Mars Global Surveyor, Mars Odyssey, and Mars Express), two rovers (Spirit and Opportunity), and one lander (Beagle 2) has provided a challenging operational scenario that required careful coordination between missions to provide the necessary support and to avoid potential interference during simultaneous relay sessions. As these coordination efforts progressed, several important lessons were learned that should be applied to future Mars relay activities.

coordination↗

Results of GEOS 3/ATS 6 satellite-to-satellite tracking orbit determination experiment

The purpose of the Geos 3/ATS 6 satellite-to-satellite tracking experiment was to develop, test, and evaluate methods of deriving orbit estimates from satellite-to-satellite tracking data. The results of the form of conventional orbit overlap tests, and a comparison of a Geos 3 orbit estimate obtained from satellite-to-satellite (SST) tracking data with an orbit estimate derived form C-band data. The method recommeded for estimating orbits from SST data is a Bayesian least squares procedure utilizing independent ranging to the relay satellite.

Argentiero, P.↗

OPS bench navigation program user's manual

Operational information is detailed for a single-vehicle weighted least squares orbit determination program with the capability of generating and storing emphemerides for three tracking Data Relay Satellites. The tape and card inputs and input format, input tape unit assignments, a program deck setup for a program run, and sample cases illustrating the output of typical runs are described.

Wannamaker, T. H.↗

Network command processing system overview

The Network Command Processing System (NCPS) developed for the National Aeronautics and Space Administration (NASA) Ground Network (GN) stations is a spacecraft command system utilizing a MULTIBUS I/68030 microprocessor. This system was developed and implemented at ground stations worldwide to provide a Project Operations Control Center (POCC) with command capability for support of spacecraft operations such as the LANDSAT, Shuttle, Tracking and Data Relay Satellite, and Nimbus-7. The NCPS consolidates multiple modulation schemes for supporting various manned/unmanned orbital platforms. The NCPS interacts with the POCC and a local operator to process configuration requests, generate modulated uplink sequences, and inform users of the ground command link status. This paper presents the system functional description, hardware description, and the software design.

Nam, Yon-Woo↗