Search NASA⌕ Search

SEARCH · Search NASA

Results for “support uplink support”

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 55 records · Page 3

Planetary mission operations

A high-level overview is presented of the process through which the uplink segment of NASA's prospective planetary missions will be instituted; the overview is supplemented by suggestions as to how costs can be reduced. Uplink costs constitute two-thirds of the total cost of operations. Attention is given to 'sequence loading', which is a time-lagged set of commands and supporting information that is prepared on the ground and uplinked to the spacecraft's onboard computer. The sequence is the primary guide used by the spacecraft to accomplish its mission; sequences are supplemented by real-time commands that are executed upon reception from the ground.

Mclaughlin, W. I.↗

Future Mission Trends and their Implications for the Deep Space Network

This viewgraph presentation discusses the direction of future missions and it's significance to the Deep Space Network. The topics include: 1) The Deep Space Network (DSN); 2) Past Missions Driving DSN Evolution; 3) The Changing Mission Paradigm; 4) Assessing Future Mission Needs; 5) Link Support Trends; 6) Downlink Rate Trends; 7) Uplink Rate Trends; 8) End-to-End Link Difficulty Trends; 9) Summary: Future Mission Trend Drivers; and 10) Conclusion: Implications for the DSN.

mission trends↗

Autonomous Command Operation of the WIRE Spacecraft

This paper presents the end-to-end design architecture for an autonomous commanding capability to be used on the Wide Field Infrared Explorer (WIRE) mission for the uplink of command loads during unattended station contacts. The WIRE mission is the fifth and final mission of NASA's Goddard Space Flight Center Small Explorer (SMEX) series to be launched in March of 1999. Its primary mission is the targeting of deep space fields using an ultra-cooled infrared telescope. Due to its mission design WIRE command loads are large (approximately 40 Kbytes per 24 hours) and must be performed daily. To reduce the cost of mission operations support that would be required in order to uplink command loads, the WIRE Flight Operations Team has implemented an autonomous command loading capability. This capability allows completely unattended operations over a typical two-day weekend period.

Prior, Mike↗

Autonomous Commanding of the WIRE Spacecraft

This paper presents the end-to-end design architecture for an autonomous commanding capability to be used on the Wide Field Infrared Explorer (WIRE) mission for the uplink of command loads during unattended station contacts. The WIRE mission is the fifth and final mission of NASA's Goddard Space Flight Center Small Explorer (SMEX) series to be launched in March of 1999. Its primary mission is the targeting of deep space fields using an ultra-cooled infrared telescope. Due to its mission design WIRE command loads are large (approximately 40 Kbytes per 24 hours) and must be performed daily. To reduce the cost of mission operations support that would be required in order to uplink command loads, the WIRE Flight Operations Team has implemented an autonomous command loading capability. This capability allows completely unattended operations over a typical two- day weekend period. The key factors driving design and implementation of this capability were: 1) Integration with already existing ground system autonomous capabilities and systems, 2) The desire to evolve autonomous operations capabilities based upon previous SMEX operations experience 3) Integration with ground station operations - both autonomous and man-tended, 4) Low cost and quick implementation, and 5) End-to-end system robustness. A trade-off study was performed to examine these factors in light of the low-cost, higher-risk SMEX mission philosophy. The study concluded that a STOL (Spacecraft Test and Operations Language) based script, highly integrated with other scripts used to perform autonomous operations, was best suited given the budget and goals of the mission. Each of these factors is discussed to provide an overview of the autonomous operations capabilities implemented for the mission. The capabilities implemented on the WIRE mission are an example of a low-cost, robust, and efficient method for autonomous command loading when implemented with other autonomous features of the ground system. They can be used as a design and implementation template by other small satellite missions interested in evolving toward autonomous and lower cost operations.

Prior, Mike↗

Autonomous Command Operations of the WIRE Spacecraft

This paper presents operational innovations which will be introduced on NASA's Wide Field Infrared Explorer (WIRE) mission. These innovations include an end-to-end design architecture for an autonomous commanding capability for the uplink of command loads during unattended station contacts. The WIRE mission is the fifth and final mission of NASA's Goddard Space Flight Center Small Explorer (SMEX) series to be launched in March of 1999. Its primary mission is the targeting of deep space fields using an ultra-cooled infrared telescope. Due to its mission design WIRE command loads are large (approximately 40 Kbytes per 24 hours) and must be performed daily. To reduce the cost of mission operations support that would be required in order to uplink command loads, the WIRE Flight Operations Team has implemented all autonomous command loading capability. This capability allows completely unattended operations over a typical two-day weekend period. The key factors driving design and implementation of this capability were: 1) integration with already existing ground system autonomous capabilities and systems, 2) the desire to evolve autonomous operations capabilities based upon previous SMEX operations experience - specifically the TRACE mission, 3) integration with ground station operations - both autonomous and man-tended, 4) low cost and quick implementation, and 5) end-to-end system robustness. A trade-off study was performed to examine these factors in light of the low-cost, higher-risk SMEX mission philosophy. The study concluded that a STOL (Spacecraft Test and Operations Language) based script, highly integrated with other scripts used to perform autonomous operations, was best suited given the budget and goals of the mission. Each of these factors is discussed in addition to use of the TRACE mission as a testbed for autonomous commanding prior to implementation on WIRE. The capabilities implemented on the WIRE mission are an example of a low-cost, robust, and efficient method for autonomous command loading when implemented with other autonomous features of the ground system. They call be used as a design and implementation template by other missions interested in evolving toward autonomous and lower cost operations. Additionally, the WIRE spacecraft will be used as an operational testbed upon completion of its nominal mission later in 1999. One idea being studied is advanced on-board modeling. Advanced on-board modeling techniques will be used to more efficiently display the spacecraft state. This health and safety information could be used by engineers on the ground or could be used by tile spacecraft for its own assessments. Additionally, this same state information could also be input into the event-driven scheduling system, as the scheduling system will need to assess the spacecraft state before undertaking a new activity. Advanced modeling techniques are being evaluated for a number of NASA missions including The Next Generation Space Telescope (NGST), which is scheduled to launch in 2007.

Walyus, Keith↗

Data system overview

The data system architecture design philosophy for 'SFOC', which is a large-scale distributed system for support of current and future space missions at the JPL, stresses 'design for change' standardization that will permit software-reuse, periodic hardware-changeout, and network-configuration evolution. Multimission capabilities are supported through a buildup of the baseline system with a minimum of special-purpose adaptations. SFOC can accommodate multiple users representing multiple disciplines, and is capable of furnishing near-real time and nonrealtime support to end-users for downlink (telemetry) and uplink (command) functions.

Kahr, Joseph R.↗

Enabling Affordable Communications for the Burgeoning Deep Space Cubesat Fleet

The low costs of development and launch, coupled with new propulsive technologies, have made CubeSats increasingly popular for use in science investigations beyond geosynchronous orbit. As this deep space CubeSat fleet grows in size, the challenge of trying to provide affordable communications for it grows commensurately. The mass, power, and volume constraints inherent to CubeSats limit the antenna size and transmit power that they can use to close the deep space link. As a consequence, CubeSats need to rely more heavily on ground antennas that are characterized by large aperture, low noise temperatures, and relatively high-power transmitters. Such antennas are not in great abundance, nor are they inexpensive to build. For this reason, NASA’s Deep Space Network has been advocating a three-pronged approach to meeting anticipated CubeSat demand: development of simultaneous, shared-beam multi-spacecraft communications capabilities, development of large-antenna cross-support arrangements with other agencies and universities, and development of less uplink-intensive navigation techniques. This paper focuses on the pursuit of simultaneous, shared-beam multi-spacecraft communications capabilities. While the Multiple Spacecraft per Antenna (MSPA) technique has existed for over a decade, it has generally been limited to supporting downlink for just two in-beam spacecraft at a time. This limitation has largely been a function of the number and cost of available receivers. A relatively new technique that potentially overcomes this limitation is Opportunistic MSPA (OMSPA). Instead of relying on additional receivers, OMSPA makes use of a digital recorder at each ground station that is capable of capturing the intermediate frequency (IF) signals from every spacecraft in the antenna beam within the frequency bands of interest. When CubeSat projects see one or more opportunities for their CubeSat(s) to intercept the traditionally scheduled antenna beam of a “host” spacecraft, they can arrange for the CubeSat(s) to transmit open loop during those opportunities. Via a secure Internet site, the CubeSat mission operators can then retrieve the time- and frequency-relevant portions of the digital recording for subsequent demodulation and decoding, or subscribe to a service that does it for them. This “opportunistic” use of a host spacecraft’s ground antenna beam potentially enables CubeSat projects to make use of large ground antennas for downlink without having to compete with bigger, better-funded missions for antenna time in the formal scheduling process. In so doing, it also potentially enables CubeSat projects to avoid the aperture fees associated with formally scheduled downlink time - fees that factor into the “bottom-line” of competitively-bid NASA missions and that actually get charged to non-NASA missions. Taking advantage of these potential OMSPA benefits, however, will require CubeSat projects to pursue mission designs that ensure at least periodic in-beam operations relative to a “host” spacecraft. In the case of a constellation of CubeSats with inter-spacecraft distances that do not extend outside of the beam-width of the desired ground antenna at the given range, one CubeSat can serve as the “host” and have a formally scheduled downlink while the rest of the CubeSats can downlink essentially for “free” via OMSPA. Deep space CubeSats, of course, will need uplink in addition to downlink. Beyond commanding, this need is driven by the use of two-way ranging and Doppler for navigation. While OMSPA may not directly facilitate uplink, it does have the potential to free up antennas for those spacecraft that periodically require formally scheduled links for commanding and two-way radio metrics. NASA is also exploring the physical feasibility of an in-beam, simultaneous multi-spacecraft uplink technique. As with OMSPA, if successful, it will require little new equipment, further enabling affordable deep space CubeSat communications.

Abraham, Douglas S.↗

Nasa's Launch Communications Ground Segment for the 21st Century Florida Spaceport

The National Aeronautics and Space Administration (NASA) Near Earth Network (NEN) Project is implementing a new launch communications ground segment to provide services for the next generation of human and robotic space exploration systems. It will deliver unique and advanced capabilities to accelerate the transformation of Kennedy Space Center into a multi-user spaceport in cooperation with the United States Air Force (USAF). The project has leveraged commercial technologies and remote operations concepts matured in NASAs orbiting satellite ground systems to achieve dramatic lifecycle cost efficiencies as compared to the space shuttle-era ground segment. The purpose of this paper is to discuss the development history, capabilities and anticipated use cases of the NEN Launch Communications Segment (NEN LCS).The NASA Kennedy Space Center is co-located with the USAF Eastern Launch Range at Cape Canaveral, Florida. The USAF operates two launch communications ground stations, but they are not designed to transmit voice, commands or other data to the launch vehicle or astronauts. The bi-directional uplink-downlink communications responsibility for human missions has historically resided with the Goddard Space Flight Center in Greenbelt, Maryland. Several market analyses and feasibility studies investigating concepts to provide NASAs next generation launch communications services were performed during the Constellation Program prior to its cancellation in 2009, and as part of the Kennedy Space Centers follow-on efforts to transform itself into a 21st century multi-user spaceport. In 2012, the Kennedy Space Center and the USAF 45th Space Wing jointly led a study to analyze the market needs of current and future launch systems and assess the operational deficiencies of the Eastern Range infrastructure. The study team issued several recommendations, two of which ultimately became driving operational capability requirements for the NEN LCS: increased telemetry data rates of at least 20 Mbps, and S-band uplink capability. Additional capabilities identified in the requirements development process include spread spectrum modulation support, LDPC 12 and 78 error correction codes, support for IRIG-106 and CCSDS data formats, automated best source selection, and Space Link Extension (SLE) services for data distribution. The NEN LCS is comprised of two permanent ground stations, the new Kennedy Uplink Station (KUS) and refurbished Ponce de Leon (PDL) station. Both stations are remotely operated from the Global Monitor and Control Center at Wallops Flight Facility. This core architecture is extensible through host-tenant arrangements with the U.S. Air Force and deployable assets, enabling agile, tailored and robust solutions to meet the needs of civil, commercial or military customers. The NEN LCS has three use cases:1.To provide agile, tailored and robust launch communications solutions to Florida spaceport customers2.To provide orbital communications services to near-earth customers 3.To provide an experimental proving ground for Space Mobile Network concepts and technologies The NEN LCS driving mission is to support the bi-directional link with the Orion crew capsule and two 20 Mbps telemetry links from the Space Launch System core stage on Exploration Mission-1, the first integrated flight of NASAs flagship human exploration systems.

Roberts, Christopher J.↗

ISEE-3 Microwave Filter Requirements

The 64 m subnet is committed to support the International Sun Earth Explorer (ISEE-3) spacecraft. The uplink and one of the downlink frequencies will be respectively, 2090 and 2217 MHz. As these two frequencies fall outside the normal DSN transmit and receive bands, the 64-m antennas present new filter requirements, which are analyzed.

Galvez, J. L.↗

Plans for a STRV-2 to AMOS High Data Rate Bi-Directional Optical Communications Link

The Ballistic Missile Defense Organization has developed a high-data rate (155 Mbps - 1 Gbps) optical communications terminal that will be flown on the STRV-2 satellite. The satellite is scheduled for launch in November 1999, and NASA/JPL has been asked to investigate the use of the AMOS facility as a backup ground terminal to a small transportable terminal constructed by Astroterra Corporation of San Diego. The ground terminal built by Astroterra is designed to support a links out to 2000 km, and will be located at the Table Mountain Facility in Wrightwood, California. Subject to BMDO approval, the demonstration from AMOS will begin in early 2000. For the demonstration, the beam-director tracker will serve as the uplink transmitter, and the 1.6-m telescope as the downlink receiver. It will support bi-directional links out to the 3500-km maximum slant range of the satellite's pass.

Wilson, K. E.↗

Automatic Command Sequence Generation

Automatic Sequence Generator (Autogen) Version 3.0 software automatically generates command sequences for the Mars Reconnaissance Orbiter (MRO) and several other JPL spacecraft operated by the multi-mission support team. Autogen uses standard JPL sequencing tools like APGEN, ASP, SEQGEN, and the DOM database to automate the generation of uplink command products, Spacecraft Command Message Format (SCMF) files, and the corresponding ground command products, DSN Keywords Files (DKF). Autogen supports all the major multi-mission mission phases including the cruise, aerobraking, mapping/science, and relay mission phases. Autogen is a Perl script, which functions within the mission operations UNIX environment. It consists of two parts: a set of model files and the autogen Perl script. Autogen encodes the behaviors of the system into a model and encodes algorithms for context sensitive customizations of the modeled behaviors. The model includes knowledge of different mission phases and how the resultant command products must differ for these phases. The executable software portion of Autogen, automates the setup and use of APGEN for constructing a spacecraft activity sequence file (SASF). The setup includes file retrieval through the DOM (Distributed Object Manager), an object database used to store project files. This step retrieves all the needed input files for generating the command products. Depending on the mission phase, Autogen also uses the ASP (Automated Sequence Processor) and SEQGEN to generate the command product sent to the spacecraft. Autogen also provides the means for customizing sequences through the use of configuration files. By automating the majority of the sequencing generation process, Autogen eliminates many sequence generation errors commonly introduced by manually constructing spacecraft command sequences. Through the layering of commands into the sequence by a series of scheduling algorithms, users are able to rapidly and reliably construct the desired uplink command products. With the aid of Autogen, sequences may be produced in a matter of hours instead of weeks, with a significant reduction in the number of people on the sequence team. As a result, the uplink product generation process is significantly streamlined and mission risk is significantly reduced. Autogen is used for operations of MRO, Mars Global Surveyor (MGS), Mars Exploration Rover (MER), Mars Odyssey, and will be used for operations of Phoenix. Autogen Version 3.0 is the operational version of Autogen including the MRO adaptation for the cruise mission phase, and was also used for development of the aerobraking and mapping mission phases for MRO.

Fisher, Forest↗

Replacing the CCSDS Telecommand Protocol with the Next Generation Uplink (NGU)

The current CCSDS Telecommand (TC) Recommendations 1-3 have essentially been in use since the early 1960s. The purpose of this paper is to propose a successor protocol to TC. The current CCSDS recommendations can only accommodate telecommand rates up to approximately 1 mbit/s. However today's spacecraft are storehouses for software including software for Field Programmable Gate Arrays (FPGA) which are rapidly replacing unique hardware systems. Changes to flight software occasionally require uplinks to deliver very large volumes of data. In the opposite direction, high rate downlink missions that use acknowledged CCSDS File Delivery Protocol (CFDP)4 will increase the uplink data rate requirements. It is calculated that a 5 mbits/s downlink could saturate a 4 kbits/s uplink with CFDP downlink responses: negative acknowledgements (NAKs), FINISHs, End-of-File (EOF), Acknowledgements (ACKs). Moreover, it is anticipated that uplink rates of 10 to 20 mbits/s will be required to support manned missions. The current TC recommendations cannot meet these new demands. Specifically, they are very tightly coupled to the Bose-Chaudhuri-Hocquenghem (BCH) code in Ref. 2. This protocol requires that an uncorrectable BCH codeword delimit the TC frame and terminate the randomization process. This method greatly limits telecom performance since only the BCH code can support the protocol. More modern techniques such as the CCSDS Low Density Parity Check (LDPC)5 codes can provide a minimum performance gain of up to 6 times higher command data rates as long as sufficient power is available in the data. This paper will describe the proposed protocol format, trade-offs, and advantages offered, along with a discussion of how reliable communications takes place at higher nominal rates.

Consultative Committee for Space Data Systems (CCS↗

An application of computer aided requirements analysis to a real time deep space system

The entire procedure of incorporating the requirements and goals of a space flight project into integrated, time ordered sequences of spacecraft commands, is called the uplink process. The Uplink Process Control Task (UPCT) was created to examine the uplink process and determine ways to improve it. The Problem Statement Language/Problem Statement Analyzer (PSL/PSA) designed to assist the designer/analyst/engineer in the preparation of specifications of an information system is used as a supporting tool to aid in the analysis. Attention is given to a definition of the uplink process, the definition of PSL/PSA, the construction of a PSA database, the value of analysis to the study of the uplink process, and the PSL/PSA lessons learned.

Farny, A. M.↗

Safe Laser Beam Propagation for Interplanetary Links

Ground-to-space laser uplinks to Earth–orbiting satellites and deep space probes serve both as a beacon and an uplink command channel for deep space probes and Earth-orbiting satellites. An acquisition and tracking point design to support a high bandwidth downlink from a 20-cm optical terminal on an orbiting Mars spacecraft typically calls for 2.5 kW of 1030-nm uplink optical power in 40 micro-radians divergent beams.2 The NOHD (nominal ocular hazard distance) of the 1030nm uplink is in excess of 2E5 km, approximately half the distance to the moon. Recognizing the possible threat of high power laser uplinks to the flying public and to sensitive Earth-orbiting satellites, JPL developed a three-tiered system at its Optical Communications Telescope Laboratory (OCTL) to ensure safe laser beam propagation through navigational and near-Earth space.

Optical communications↗

Modeling the Deep Space Network costs for future space missions by using major cost drivers

This paper develops a cost model to do long range planning cost estimates for Deep Space Network (DSN) support of future space missions. The model is a function of eight major mission cost drivers such as uplink frequency upgrade, telemetry upgrade, and antenna gain/noise temperature upgrade. This paper focuses on the costs required to modify and/or enhance the DSN to prepare for supporting future space missions. Two models are derived from actual cost data from three space missions: Voyager (Uranus), Voyager (Neptune), and Magellan. Model A makes it possible to estimate the total cost, and Model B makes it possible to estimate the time profile cost and total cost for DSN support of a similar future space mission. The models were back tested against the total cost and the time profile cost for DSN support of the three projects, and gave cost estimates which range from 17 percent below to 19 percent above actual costs for Model A, and 22.5 percent below to 17.5 percent above for Model B. The total cost Model A was also applied to estimate the total costs for DSN support of two other independent projects: Mariner Jupiter/Saturn (MJS later became Voyager), and Viking. This model gave total cost estimates for DSN support which range from 15 percent to 4 percent above actual total costs for MJS and Viking, respectively.

Remer, Donald S.↗

DSN Aperture Enhancement Project Office

All contracts are underway for antennas, associated facilities modifications and new transmitters. High risk CPI 100kW klystron and JPL high power uplink microwave components have been designed, prototyped and successfully tested at GDSCC to support the 80kW transmitter implementation and testing at vendor facility. Open issues, which might affect project delivery date, have plans in place or are being created, to maintain DSS-35 Operational Date. There are no known open issues that affect performance. Overall good progress has been made in all areas (procurements, contracts, design and development) and the project is confident that DSS-35 & 36 antennas and the three 80kW Uplink systems will be delivered according to plan.

DSN Aperture Enhancement Project (DAEP)↗

Ka-Band High-Rate Telemetry System Upgrade for the NASA Deep Space Network

The NASA Deep Space Network (DSN) has a new requirement to support high-data-rate Category A (Cat A) missions (within 2 million kilometers of Earth) with simultaneous S-band uplink, S-band downlink and Ka-band downlink. The S-band links are required for traditional TT&C (Telemetry, Tracking, and Command) support to the spacecraft, while the Ka-band link is intended for high-data-rate science returns. The new Ka-band system combines the use of proven DSN cryogenic designs, for low system temperature, and high data rate capability using commercial telemetry receivers. The initial Cat A support is required for the James Webb Space Telescope (JWST) in 2013 and possibly other missions. The upgrade has been implemented into 3 different 34-meter Beam Waveguide (BWG) antennas in the DSN, one at each of the complexes in Canberra (Australia), Goldstone (California) and Madrid (Spain). System test data is presented to show that the requirements were met and the DSN is ready for Cat A Ka-band operational support.

space communications↗