Search NASA⌕ Search

SEARCH · Search NASA

Results for “uplink planning systems”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

A Roadmap for using Agile Development in a Traditional System

I. Ensemble Development Group: a) Produces activity planning software for in spacecraft; b) Built on Eclipse Rich Client Platform (open source development and runtime software); c) Funded by multiple sources including the Mars Technology Program; d) Incorporated the use of Agile Development. II. Next Generation Uplink Planning System: a) Researches the Activity Planning and Sequencing Subsystem for Mars Science Laboratory (APSS); b) APSS includes Ensemble, Activity Modeling, Constraint Checking, Command Editing and Sequencing tools plus other uplink generation utilities; c) Funded by the Mars Technology Program; d) Integrates all of the tools for APSS.

uplink planning systems↗
NASA NTRS2014

Adding "Missed" Science to Cassini's Ops Plan

The phenomenal success of the Cassini Mission at Saturn is largely due to flagship instruments, in a target rich environment, for a long period of time, executing almost error free complex mission operations. A smooth transition from cruise operations through the prime science mission and extended science (Equinox) mission culminating in the currently executing Solstice mission has folded in necessary procedural alterations due to improved understanding of the spacecraft, instruments, uplink and planning systems as well as additional science objectives. These have come with the maturation of the mission along with management of workforce reductions. One important set of operational changes has been initiated due to scientific findings highlighting "missed" science opportunities. This is the case for the Titan Meteorology Campaigns and Saturn Storm Watch Campaigns. These observations involve long term monitoring of the atmospheres of Titan and Saturn while the spacecraft and science teams are focused on other high priority targets of opportunity (like Enceladus). Our objective in this paper is to emphasize how a non-invasive strategy to get additional remarkable science was conceived and implemented in a mission with an already well defined operational plan. To illustrate this we will detail Titan Meteorology Campaign and Saturn Storm Watch Campaign integration and implementation strategies as well as the scientific goals and achievements of both.

Roy, Mou↗
NASA NTRS2014

Adding "Missed" Science to Cassini's Ops Plan

The phenomenal success of the Cassini Mission at Saturn is largely due to flagship instruments, in a target rich environment, for a long period of time, executing almost error free complex mission operations. A smooth transition from cruise operations through the prime science mission and extended science (Equinox) mission culminating in the currently executing Solstice mission has folded in necessary procedural alterations due to improved understanding of the spacecraft, instruments, uplink and planning systems as well as additional science objectives. These have come with the maturation of the mission along with management of workforce reductions. One important set of operational changes has been initiated due to scientific findings highlighting "missed" science opportunities. This is the case for the Titan Meteorology Campaigns and Saturn Storm Watch Campaigns. These observations involve long term monitoring of the atmospheres of Titan and Saturn while the spacecraft and science teams are focused on other high priority targets of opportunity (like Enceladus). Our objective in this paper is to emphasize how a non-invasive strategy to get additional remarkable science was conceived and implemented in a mission with an already well defined operational plan. To illustrate this we will detail Titan Meteorology Campaign and Saturn Storm Watch Campaign integration and implementation strategies as well as the scientific goals and achievements of both.

Roy, Mou↗
NASA NTRS2004

Collaborative Planning of Robotic Exploration

The Science Activity Planner (SAP) software system includes an uplink-planning component, which enables collaborative planning of activities to be undertaken by an exploratory robot on a remote planet or on Earth. Included in the uplink-planning component is the SAP-Uplink Browser, which enables users to load multiple spacecraft activity plans into a single window, compare them, and merge them. The uplink-planning component includes a subcomponent that implements the Rover Markup Language Activity Planning format (RML-AP), based on the Extensible Markup Language (XML) format that enables the representation, within a single document, of planned spacecraft and robotic activities together with the scientific reasons for the activities. Each such document is highly parseable and can be validated easily. Another subcomponent of the uplink-planning component is the Activity Dictionary Markup Language (ADML), which eliminates the need for two mission activity dictionaries - one in a human-readable format and one in a machine-readable format. Style sheets that have been developed along with the ADML format enable users to edit one dictionary in a user-friendly environment without compromising

Norris, Jeffrey↗
NASA NTRS1990

Weather data dissemination to aircraft

Documentation exists that shows weather to be responsible for approximately 40 percent of all general aviation accidents with fatalities. Weather data products available on the ground are becoming more sophisticated and greater in number. Although many of these data are critical to aircraft safety, they currently must be transmitted verbally to the aircraft. This process is labor intensive and provides a low rate of information transfer. Consequently, the pilot is often forced to make life-critical decisions based on incomplete and outdated information. Automated transmission of weather data from the ground to the aircraft can provide the aircrew with accurate data in near-real time. The current National Airspace System Plan calls for such an uplink capability to be provided by the Mode S Beacon System data link. Although this system has a very advanced data link capability, it will not be capable of providing adequate weather data to all airspace users in its planned configuration. This paper delineates some of the important weather data uplink system requirements, and describes a system which is capable of meeting these requirements. The proposed system utilizes a run-length coding technique for image data compression and a hybrid phase and amplitude modulation technique for the transmission of both voice and weather data on existing aeronautical Very High Frequency (VHF) voice communication channels.

Mcfarland, Richard H.↗
NASA NTRS2006

Uplink Coding

This viewgraph presentation reviews uplink coding. The purpose and goals of the briefing are (1) Show a plan for using uplink coding and describe benefits (2) Define possible solutions and their applicability to different types of uplink, including emergency uplink (3) Concur with our conclusions so we can embark on a plan to use proposed uplink system (4) Identify the need for the development of appropriate technology and infusion in the DSN (5) Gain advocacy to implement uplink coding in flight projects Action Item EMB04-1-14 -- Show a plan for using uplink coding, including showing where it is useful or not (include discussion of emergency uplink coding).

flight projects↗
NASA NTRS2011

An Examination of Selected Datacom Options for the Near-Term Implementation of Trajectory Based Operations

A primary feature of the Next Generation Air Transportation System (NextGen) is trajectory based operations (TBO). Under TBO, aircraft flight plans are known to computer systems on the ground that aid in scheduling and separation. The Future Air Navigation System (FANS) was developed to support TBO, but relatively few aircraft in the US are FANSequipped. Thus, any near-term implementation must provide TBO procedures for non-FANS aircraft. Previous research has explored controller clearances, but any implementation must also provide procedures for aircraft requests. The work presented here aims to surface issues surrounding TBO communication procedures for non-FANS aircraft and for aircraft requesting deviations around weather. Three types of communication were explored: Voice, FANS, and ACARS,(Aircraft Communications Addressing and Reporting System). ACARS and FANS are datacom systems that differ in that FANS allows uplinked flight plans to be loaded into the Flight Management System (FMS), while ACARS delivers flight plans as text that must be entered manually via the Control Display Unit (CDU). Sixteen pilots (eight two-person flight decks) and four controllers participated in 32 20-minute scenarios that required the flight decks to navigate through convective weather as they approached their top of descents (TODs). Findings: The rate of non-conformance was higher than anticipated, with aircraft off path more than 20% of the time. Controllers did not differentiate between the ACARS and FANS datacom, and were mixed in their preference for Voice vs. datacom (ACARS and FANS). Pilots uniformly preferred Voice to datacom, particularly ACARS. Much of their dislike appears to result from the slow response times in the datacom conditions. As a result, participants frequently resorted to voice communication. These results imply that, before implementing TBO in environments where pilots make weather deviation requests, further research is needed to develop communication procedures that integrate voice and datacom.

trajectory based operations↗
NASA NTRS2001

A science-based executive for autonomous planetary vehicles

If requests for scientific observations, rather than specific plans, are uplinked to an autonomous execution system on the vehicle, it would be able to adjust its execution based upon actual performance. Such a science-based executive control system had been developed and demonstrated for the Rocky7 research rover.

robotic vehicle rover autonomy intelligent executi↗
NASA NTRS1984

X-band Uplink Technology Demonstration at DSS-13

The status of the X-band uplink development program is examined from a systems' viewpoint. The hardware, designed and built under the program, is now in place at DSS-13. System stability testing is underway. An X-band receive capability is being implemented on both the Galileo and the Venus Radar Mapper spacecraft. Experiments are planned to demonstrate the capabilities of the X-band uplink system and to permit performance of the gravitational wave experiment on the Galileo orbiter and obtain a more detailed gravity map of Venus.

Meeker, J. G.↗
NASA NTRS1986

An expert system prototype for aiding in the development of software functional requirements for NASA Goddard's command management system: A case study and lessons learned

At NASA Goddard, the role of the command management system (CMS) is to transform general requests for spacecraft opeerations into detailed operational plans to be uplinked to the spacecraft. The CMS is part of the NASA Data System which entails the downlink of science and engineering data from NASA near-earth satellites to the user, and the uplink of command and control data to the spacecraft. Presently, it takes one to three years, with meetings once or twice a week, to determine functional requirements for CMS software design. As an alternative approach to the present technique of developing CMS software functional requirements, an expert system prototype was developed to aid in this function. Specifically, the knowledge base was formulated through interactions with domain experts, and was then linked to an existing expert system application generator called 'Knowledge Engineering System (Version 1.3).' Knowledge base development focused on four major steps: (1) develop the problem-oriented attribute hierachy; (2) determine the knowledge management approach; (3) encode the knowledge base; and (4) validate, test, certify, and evaluate the knowledge base and the expert system prototype as a whole. Backcasting was accomplished for validating and testing the expert system prototype. Knowledge refinement, evaluation, and implementation procedures of the expert system prototype were then transacted.

Liebowitz, Jay↗
NASA NTRS2006

Lessons Learned from Daily Uplink Operations during the Deep Impact Mission

The daily preparation of uplink products (commands and files) for Deep Impact was as problematic as the final encounter images were spectacular. The operations team was faced with many challenges during the six-month mission to comet Tempel One of the biggest difficulties was that the Deep Impact Flyby and Impactor vehicles necessitated a high volume of uplink products while also utilizing a new uplink file transfer capability. The Jet Propulsion Laboratory (JPL) Multi-Mission Ground Systems and Services (MGSS) Mission Planning and Sequence Team (MPST) had the responsibility of preparing the uplink products for use on the two spacecraft. These responsibilities included processing nearly 15,000 flight products, modeling the states of the spacecraft during all activities for subsystem review, and ensuring that the proper commands and files were uplinked to the spacecraft. To guarantee this transpired and the health and safety of the two spacecraft were not jeopardized several new ground scripts and procedures were developed while the Deep Impact Flyby and Impactor spacecraft were en route to their encounter with Tempel-1. These scripts underwent several adaptations throughout the entire mission up until three days before the separation of the Flyby and Impactor vehicles. The problems presented by Deep Impact's daily operations and the development of scripts and procedures to ease those challenges resulted in several valuable lessons learned. These lessons are now being integrated into the design of current and future MGSS missions at JPL.

uplink↗
NASA NTRS2005

Analyzing MER Uplink Reports

The MER project includes two rovers working simultaneously on opposite sides of Mars each receiving commands only once a day. Creating this uplink is critical, since a failed uplink means a lost day and a waste of money. Examining the process of creating this uplink, I tracked the use of the system developed for requesting observations as well as the development, from stage to stage, in forming an activity plan. I found the system for requesting observations was commonly misused, if used at all. There are half a dozen reports to document the creation of the uplink plan and often there are discrepancies among them. Despite this, the uplink process worked very well and MER has been one of the most successful missions for NASA in recent memory. Still it is clear there is room for improvement.

Savin, Stephen C.↗
NASA NTRS2022

“Just Do It” Mission Operations Training in a COVID World

“No”- “not”- “can’t do it” – these words don’t fly in M2020 Mission Operations. The M2020 Surface Mission Operations Team trained for landing the Perseverance Rover under COVID-19 remote work/mandatory stay-at-home conditions. Training activities included presenting Flight Schools to the team via video conferencing, training COVID personal safety requirements to on-premises staff, and constantly updating and communicating COVID restrictions to the team as safety requirements changed. This paper explores the impact of COVID on the Mission System Training for M2020 Mission Operations. The layers of COVID, aptly named the “COVID Tax” by team management, affected project roles, communications, personnel interactions, operations facility usage and training exercises practiced by the team. Flight Schools and Operational Readiness Tests (ORTs) are driving forces behind the surface mission operations training. These activities work hand-in-hand to prepare the team for landing day, surface operations that transition from cruise to nominal operations, and nominal operations. Under normal training conditions, Flight Schools and ORTs are only concerned with tactical operations for the Uplink (Command) Downlink (Analysis) and Campaign Implementation (Planning) Teams of scientists and system engineers. Due to COVID, and the necessity to maintain physical distance between people, training for the landing team needed to include the new category of COVID personal safety. COVID also necessitated remote teams and video conferencing of the entirety of Flight Schools. This reliance on distance learning had not been done on previous missions. We will explore the advantages and disadvantages of video conferencing as a training platform; training effectiveness in communicating and practicing the multiple changes to the COVID safety protocols; and the timing in which we received and responded to COVID directives. Additionally, this paper will review the practical measures taken by the on-premises team and how the team adapted during the readiness tests, landing, and early mission operations, as well as how the team responded to the post-vaccine ramping down of COVID Protocols. The M2020 Surface Mission Operations Team responded very well to the challenges of COVID. All pre-landing operational and COVID-related training was completed. Post-landing COVID Training was provided as needed to new on-premises personnel. Training presented on COVID for the first operational readiness test (ORT) consisted of 2.5 hours of training. Each ORT had COVID Training. A person who had participated in all of the ORTs from September 2020 – February 2021 would have received over 7 hours of COVID Training. By ORT-12 (approximately 8 weeks after the first ORT), the Training team consolidated the original COVID training to a one-hour COVID Basic Training course, with additional recommended training. The Basic training course was updated after landing, as vaccines became available. COVID Training had multiple Flight Schools in the self-directed Blackboard Learning system, as well as a Quick Reference Wiki for Onboarding of new on-premises personnel and keeping on-premises personnel up-to-date. COVID Training covered many topics including practical methods of 6-foot distancing, how to interact with an IT professional when help was needed at a workstation, and challenging indoor meal-eating protocols. COVID Training continued to be updated, as the lab and the project respond to the virus variants and federal, state and local ordinances.

Rosette, Theresa↗
NASA NTRS2020

Solar Cruiser Technology Maturation Plans

The NASA Marshall Space Flight Center (MSFC) developed the Solar Cruiser mission concept to mature solar sail technology for use in future Heliophysics missions, as well as missions of interest across a broad user community (e.g., space weather and Earth polar observatories). Solar Cruiser will serve as a pathfinder for missions that observe the solar environment from unique vantage points such as a high inclination solar mission opening a fundamentally new range of observational capabilities for the Heliophysics Program and for space weather monitoring. Sustained observations away from the Sun-Earth line (SEL) present unique opportunities for answering the outstanding science questions of Heliophysics, improving space-weather monitoring and prediction, and revealing new information about our Sun and solar system. Propellantless solar sails can be used to create artificial equilibria and maintain indefinite station-keeping at locations sunward of L1 along the SEL, or at any desired offset from the SEL leading or trailing the Earth in its orbit. They can change the heliocentric inclination of a spacecraft from the ecliptic to as high as solar polar, stopping and remaining at any intermediate inclination orbit in between. Sails can be used to hover over the Earth’s poles, using solar photon pressure to offset the Earth’s gravitational attraction, creating functional equivalents of geostationary earth orbits. The Solar Cruiser mission would fly a small spacecraft with a large (>1,600 square meter) solar sail containing embedded reflectivity control devices (RCDs) and photovoltaic cells. The mission concept includes successful deployment of the solar sail, validation of all sail subsystems, controlled station-keeping inside of the Sun-Earth L1 point, attitude control of the sail with the RCDs (including spinning and de-spinning), demonstration of pointing performance for science imaging, and an increase in heliocentric inclination (out of the ecliptic). To demonstrate the requisite sail technology, the Solar Cruiser project will design, fabricate, deploy, and fly the Solar Sail Propulsion Element (SSPE). The SSPE incorporates the following three systems: • The Solar Sail System (SSS) provides the large propulsive surface required for acceleration and smaller reflectivity-changing surfaces for roll control. • The Active Mass Translator System (AMT) provides SSPE motion with respect to the sailcraft bus for pitch and yaw control. • The Solar Sail Attitude Determination and Control System (SSADCS) consists of embedded software to 1) provide autonomous sailcraft attitude estimation, attitude pointing control, and reaction wheel momentum management following sail deployment and 2) execute the uplinked inertial attitude pointing commands to maintain the desired sailcraft trajectory. The plans for maturing each of these technology systems to TRL 5 and beyond are described herein.

Solar Sail↗
NASA NTRS1985

Testing of 30-GHz low noise receivers

NASA-sponsored studies of the growth in communications traffic have indicated that the frequency spectrum allocated to fix-service satellites at the C and Ku bands will reach saturation by the early 1990's. The next higher frequency bands allocated for communications satellties are 27.5 to 30 GHz for the uplink and 17.7 to 20.2 GHz for the downlink. Current plans for developing satellite systems that use these bands include a NASA demonstration satellite (ACTS). One of the components identified as critical to the success of that mission is a 27.5 to 30 GHz satellite receiver. In response to that identification, NASA has sponsored the development of such a receiver to the proof-of-concept (POC) level. Design and fabrication of such POC model receivers was carried out under parallel contracts awarded to LNR Communications, Inc. of Hauppauge, New York and to ITT Defense Communications Division of Nutley, New Jersey. The most significant of the performance goals were a 5 db maximum noise figure, a 2.5 GHz passband, and e0 dB Rf to If gain. Following delivery of hardware from each of the contractors, an in-house test program was undertaken at NASA's Lewis Research Center in order to verify the contractor-reported performance and to provide a comparison of the two receivers under identical test conditions. The present paper reports the results of those tests.

Conroy, M. J.↗
NASA NTRS1986

Testing of 30-GHz low noise receivers

NASA-sponsored studies of the growth in communications traffic have indicated that the frequency spectrum allocated to fix-service satellites at the C and Ku bands will reach saturation by the early 1990's. The next higher frequency bands allocated for communications satellites are 27.5 to 30 GHz for the uplink and 17.7 to 20.2 GHz for the downlink. Current plans for developing satellite systems that use these bands include a NASA demonstration satellite (ACTS). One of the components identified as critical to the success of that mission is a 27.5 to 30 GHz satellite receiver. In response to that identification, NASA has sponsored the development of such a receiver to the proof-of-concept (POC) level. Design and fabrication of such POC model receivers was carried out under parallel contracts awarded to LNR Communications, Inc. of Hauppauge, New York and to ITT Defense Communications Division of Nutley, New Jersey. The most significant of the performance goals were a 5 dB maximum noise figure, a 2.5 GHz passband, and 20 dB RF to IF gain. Following delivery of hardware from each of the contractors, an in-house test program was undertaken at NASA's Lewis Research Center in order to verify the contractor-reported performance and to provide a comparison of the two receivers under identical test conditions. The present paper reports the results of those tests.

Conroy, M. J.↗
NASA NTRS1988

A new multi-mission data system for space flight support through the 1990's

The Space Flight Operations Center (SFOC) is described with attention given to historical and technical aspects. The SFOC is designed to support each new JPL mission with all of its mission-unique processing as a ready adaptation of some set of baseline capabilities. Another goal of the SFOC is to allow the migration of current older JPL missions from their current systems that use aging and costly hardware and software to newer systems with similar functionality. Upon its completion, the planned support includes both downlink and uplink processing for a projected six mission set.

Gainsborough, A. J.↗