Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “GROUND TRACK”

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 559 records · Page 31
All sourcesNASA NTRSDOE OSTI
NASA NTRS1985

Trajectory reconstruction and aerodynamic results from the first Discovery flight, STS-14(41-D)

Trajectory reconstruction results for the first Discovery flight are presented. Spacecraft dynamic measurements from IMU2 were utilized in conjunction with the ground based tracking data from two S-band stations, eight C-band, and five cameras at Edwards Air Force Base to determine the spacecraft trajectory from epoch through roll-out on Runway 17. Specifics as to the trajectory reconstruction are discussed in Section 1. The final inertial profile is BT14NO2/UN=169750N. Merging of this file with the final LAIRS atmosphere is discussed in Section 2. The final Extended BET is ST14BET/UN=274885C. Section 3 presents plots of relevant parameters from the AEROBET as well as aerodynamic performance comparison results. High frequency files for maneuver extraction were also generated as discussed in Section 4. Appendices are attached which contain: (1) spacecraft and physical parameters utilized, (2) final residuals obtained from the data fitting process, (3) listing of trajectory parameters, and (4) archival information.

Kelly, G. M.↗
NASA NTRS1987

Network functions and facilities

The objectives, functions, and organization of the Deep Space Network (DSN) are summarized: tracking complexes, ground communications, and network operations control capabilities are described.

Amorose, R. J.↗
NASA NTRS1989

REDEX: The ranging equipment diagnostic expert system

REDEX, an advanced prototype expert system that diagnoses hardware failures in the Ranging Equipment (RE) at NASA's Ground Network tracking stations is described. REDEX will help the RE technician identify faulty circuit cards or modules that must be replaced, and thereby reduce troubleshooting time. It features a highly graphical user interface that uses color block diagrams and layout diagrams to illustrate the location of a fault. A semantic network knowledge representation technique was used to model the design structure of the RE. A catalog of generic troubleshooting rules was compiled to represent heuristics that are applied in diagnosing electronic equipment. Specific troubleshooting rules were identified to represent additional diagnostic knowledge that is unique to the RE. Over 50 generic and 250 specific troubleshooting rules have been derived. REDEX is implemented in Prolog on an IBM PC AT-compatible workstation. Block diagram graphics displays are color-coded to identify signals that have been monitored or inferred to have nominal values, signals that are out of tolerance, and circuit cards and functions that are diagnosed as faulty. A hypertext-like scheme is used to allow the user to easily navigate through the space of diagrams and tables. Over 50 graphic and tabular displays have been implemented. REDEX is currently being evaluated in a stand-alone mode using simulated RE fault scenarios. It will soon be interfaced to the RE and tested in an online environment. When completed and fielded, REDEX will be a concrete example of the application of expert systems technology to the problem of improving performance and reducing the lifecycle costs of operating NASA's communications networks in the 1990's.

Luczak, Edward C.↗
NASA NTRS1989

Gravity field determination and error assessment techniques

Linear estimation theory, along with a new technique to compute relative data weights, was applied to the determination of the Earth's geopotential field and other geophysical model parameters using a combination of satellite ground-based tracking data, satellite altimetry data, and the surface gravimetry data. The relative data weights for the inhomogeneous data sets are estimated simultaneously with the gravity field and other geophysical and orbit parameters in a least squares approach to produce the University of Texas gravity field models. New techniques to perform calibration of the formal covariance matrix for the geopotential solution were developed to obtain a reliable gravity field error estimate. Different techniques, which include orbit residual analysis, surface gravity anomaly residual analysis, subset gravity solution comparisons and consider covariance analysis, were applied to investigate the reliability of the calibration.

Yuan, D. N.↗
NASA NTRS1989

REDEX - The ranging equipment diagnostic expert system

REDEX, an advanced prototype expert system that diagnoses hardware failures in the Ranging Equipment (RE) at NASA's Ground Network tracking stations is described. REDEX will help the RE technician identify faulty circuit cards or modules that must be replaced, and thereby reduce troubleshooting time. It features a highly graphical user interface that uses color block diagrams and layout diagrams to illustrate the location of a fault. A semantic network knowledge representation technique was used to model the design structure of the RE. A catalog of generic troubleshooting rules was compiled to represent heuristics that are applied in diagnosing electronic equipment. Specific troubleshooting rules were identified to represent additional diagnostic knowledge that is unique to the RE. Over 50 generic and 250 specific troubleshooting rules have been derived. REDEX is implemented in Prolog on an IBM PC AT-compatible workstation. Block diagram graphics displays are color-coded to identify signals that have been monitored or inferred to have nominal values, signals that are out of tolerance, and circuit cards and functions that are diagnosed as faulty. A hypertext-like scheme is used to allow the user to easily navigate through the space of diagrams and tables. Over 50 graphic and tabular displays have been implemented. REDEX is currently being evaluated in a stand-alone mode using simulated RE fault scenarios. It will soon be interfaced to the RE and tested in an online environment. When completed and fielded, REDEX will be a concrete example of the application of expert systems technology to the problem of improving performance and reducing the lifecycle costs of operating NASA's communications networks in the 1990s.

Luczak, Edward C.↗
NASA NTRS1994

Application of the GEM-T2 gravity field to altimetric satellite orbit computation

As part of a continuing effort to provide improved orbits for use with existing altimeter data, we have recomputed ephemerides for both the Seasat and Geosat Exact Repeat altimeter missions. The orbits were computed in a consistent fashion, using the Goddard Earth Model T2 (GEM-T2) gravity field along with available ground-based tracking data. Such an approach allows direct comparisons of sea level between the two altimeter systems. Evaluation of the resulting ephemerides indicates that root-mean-square accuracies of 30-50 cm have been achieved for the radial component of the orbits for both satellites. An exception occurs for the last year of the Geosat Exact Repeat Mission, when the rms radial orbit accuracy degrades to the 1-m level at times owing to the inability to adequately model the drag force arising from the increased solar activity.

Haines, Bruce J.↗
NASA NTRS1995

Lunar Telecommunications

This paper reviews the telecommunications needs of future lunar orbiters and rovers and considers ways in which these needs can be met with ground-based tracking resources.

Lunar Prospector↗
NASA NTRS2010

Formal Verification of Air Traffic Conflict Prevention Bands Algorithms

In air traffic management, a pairwise conflict is a predicted loss of separation between two aircraft, referred to as the ownship and the intruder. A conflict prevention bands system computes ranges of maneuvers for the ownship that characterize regions in the airspace that are either conflict-free or 'don't go' zones that the ownship has to avoid. Conflict prevention bands are surprisingly difficult to define and analyze. Errors in the calculation of prevention bands may result in incorrect separation assurance information being displayed to pilots or air traffic controllers. This paper presents provably correct 3-dimensional prevention bands algorithms for ranges of track angle; ground speed, and vertical speed maneuvers. The algorithms have been mechanically verified in the Prototype Verification System (PVS). The verification presented in this paper extends in a non-trivial way that of previously published 2-dimensional algorithms.

Narkawicz, Anthony J.↗
NASA NTRS2007

MILA Antenna Control Unit Replacement Project

The Air to Ground Subsystem (AGS) Antenna Control Units at the MILA Ground Network Tracking Station are at end-of-life and are being replaced. AGS consists of two antennas at MILA (Quad-Helix and Teltrac). Software was taken from the existing Subsystem Controller and modified for the Antenna Control Unit (ACU). The software is capable of receiving and sending commands to and from the ACU. Moving the azimuth clockwise, counterclockwise, moving the elevation up or down, turning servo power on and off, and inputting azimuth and elevation angles are commands that the antenna can receive.

Bresette, Jeremy↗
NASA NTRS2012

Locating the LCROSS Impact Craters

The Lunar CRater Observations and Sensing Satellite (LCROSS) mission impacted a spent Centaur rocket stage into a permanently shadowed region near the lunar south pole. The Sheperding Spacecraft (SSC) separated approx. 9 hours before impact and performed a small braking maneuver in order to observe the Centaur impact plume, looking for evidence of water and other volatiles, before impacting itself. This paper describes the registration of imagery of the LCROSS impact region from the mid- and near-infrared cameras onboard the SSC, as well as from the Goldstone radar. We compare the Centaur impact features, positively identified in the first two, and with a consistent feature in the third, which are interpreted as a 20 m diameter crater surrounded by a 160 m diameter ejecta region. The images are registered to Lunar Reconnaisance Orbiter (LRO) topographical data which allows determination of the impact location. This location is compared with the impact location derived from ground-based tracking and propagation of the spacecraft's trajectory and with locations derived from two hybrid imagery/trajectory methods. The four methods give a weighted average Centaur impact location of −84.6796 deg, −48.7093 deg, with a 1σ uncertainty of 115 m along latitude, and 44 m along longitude, just 146 m from the target impact site. Meanwhile, the trajectory-derived SSC impact location is −84.719 deg, −49.61 deg, with a 1 alpha uncertainty of 3 m along the Earth vector and 75 m orthogonal to that, 766 m from the target location and 2.803 km south-west of the Centaur impact. We also detail the Centaur impact angle and SSC instrument pointing errors. Six high-level LCROSS mission requirements are shown to be met by wide margins. We hope that these results facilitate further analyses of the LCROSS experiment data and follow-up observations of the impact region

LCROSS↗
NASA NTRS2014

DUKSUP: A Computer Program for High Thrust Launch Vehicle Trajectory Design and Optimization

From the late 1960's through 1997, the leadership of NASA's Intermediate and Large class unmanned expendable launch vehicle projects resided at the NASA Lewis (now Glenn) Research Center (LeRC). One of LeRC's primary responsibilities --- trajectory design and performance analysis --- was accomplished by an internally-developed analytic three dimensional computer program called DUKSUP. Because of its Calculus of Variations-based optimization routine, this code was generally more capable of finding optimal solutions than its contemporaries. A derivation of optimal control using the Calculus of Variations is summarized including transversality, intermediate, and final conditions. The two point boundary value problem is explained. A brief summary of the code's operation is provided, including iteration via the Newton-Raphson scheme and integration of variational and motion equations via a 4th order Runge-Kutta scheme. Main subroutines are discussed. The history of the LeRC trajectory design efforts in the early 1960's is explained within the context of supporting the Centaur upper stage program. How the code was constructed based on the operation of the Atlas/Centaur launch vehicle, the limits of the computers of that era, the limits of the computer programming languages, and the missions it supported are discussed. The vehicles DUKSUP supported (Atlas/Centaur, Titan/Centaur, and Shuttle/Centaur) are briefly described. The types of missions, including Earth orbital and interplanetary, are described. The roles of flight constraints and their impact on launch operations are detailed (such as jettisoning hardware on heating, Range Safety, ground station tracking, and elliptical parking orbits). The computer main frames on which the code was hosted are described. The applications of the code are detailed, including independent check of contractor analysis, benchmarking, leading edge analysis, and vehicle performance improvement assessments. Several of DUKSUP's many major impacts on launches are discussed including Intelsat, Voyager, Pioneer Venus, HEAO, Galileo, and Cassini.

high thrust trajectory design↗
NASA NTRS2015

DUKSUP: A Computer Program for High Thrust Launch Vehicle Trajectory Design and Optimization

From the late 1960s through 1997, the leadership of NASAs Intermediate and Large class unmanned expendable launch vehicle projects resided at the NASA Lewis (now Glenn) Research Center (LeRC). One of LeRCs primary responsibilities --- trajectory design and performance analysis --- was accomplished by an internally-developed analytic three dimensional computer program called DUKSUP. Because of its Calculus of Variations-based optimization routine, this code was generally more capable of finding optimal solutions than its contemporaries. A derivation of optimal control using the Calculus of Variations is summarized including transversality, intermediate, and final conditions. The two point boundary value problem is explained. A brief summary of the codes operation is provided, including iteration via the Newton-Raphson scheme and integration of variational and motion equations via a 4th order Runge-Kutta scheme. Main subroutines are discussed. The history of the LeRC trajectory design efforts in the early 1960s is explained within the context of supporting the Centaur upper stage program. How the code was constructed based on the operation of the AtlasCentaur launch vehicle, the limits of the computers of that era, the limits of the computer programming languages, and the missions it supported are discussed. The vehicles DUKSUP supported (AtlasCentaur, TitanCentaur, and ShuttleCentaur) are briefly described. The types of missions, including Earth orbital and interplanetary, are described. The roles of flight constraints and their impact on launch operations are detailed (such as jettisoning hardware on heating, Range Safety, ground station tracking, and elliptical parking orbits). The computer main frames on which the code was hosted are described. The applications of the code are detailed, including independent check of contractor analysis, benchmarking, leading edge analysis, and vehicle performance improvement assessments. Several of DUKSUPs many major impacts on launches are discussed including Intelsat, Voyager, Pioneer Venus, HEAO, Galileo, and Cassini.

Launch vehicle performance optimization↗
NASA NTRS2016

The Orion Exploration Flight Test Post Flight Solid Particle Flight Environment Inspection and Analysis

Orbital debris in the millimeter size range can pose a hazard to current and planned spacecraft due to the high relative impact speeds in Earth orbit. Fortunately, orbital debris has a relatively short life at lower altitudes due to atmospheric effects; however, at higher altitudes orbital debris can survive much longer and has resulted in a band of high flux around 700 to 1,500 km above the surface of the Earth. While large orbital debris objects are tracked via ground based observation, little information can be gathered about small particles except by returned surfaces, which until the Orion Exploration Flight Test number one (EFT-1), has only been possible for lower altitudes (400 to 500 km). The EFT-1 crew module backshell, which used a porous, ceramic tile system with surface coatings, has been inspected post-flight for potential micrometeoroid and orbital debris (MMOD) damage. This paper describes the pre- and post-flight activities of inspection, identification and analysis of six candidate MMOD impact craters from the EFT-1 mission.

Miller, Joshua E.↗
NASA NTRSDate not supplied

Science Objectives and Investigations for the Lunar GNSS Receiver Experiment (LuGRE)

A resurgence in lunar activity is taking place, and the pace of Moon-bound launches is only expected to increase. While a dozen missions have already launched to the Moon in this new era, there are now more than 80 government space agencies and an increasing number of private space companies, many of which are planning missions to the Moon. From a navigation perspective, the goals of these future missions are ambitious (e.g., the 2018 Global Exploration Roadmap identified 100-meter position accuracy as a performance target for precision landing) but will not all be able to rely on a human-in-the-loop approach—and the sheer volume of planned missions makes ground-based tracking impractical.

Lauren Konitzer↗