NASA Deep Space Network

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Lua error in package.lua at line 80: module 'strict' not found.

Deep Space Network
Deep space network 40th logo.svg
Organization Interplanetary Network Directorate
(NASA / JPL)
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Website deepspace.jpl.nasa.gov
Telescopes
Goldstone Deep Space Communications Complex Barstow, California, United States
Madrid Deep Space Communication Complex Robledo de Chavela, Community of Madrid, Spain
Canberra Deep Space Communication Complex Tidbinbilla, Australian Capital Territory, Australia

The NASA Deep Space Network (DSN) is a world-wide network of large antennas and communication facilities, located in the United States (California), Spain (Madrid), and Australia (Canberra), that supports interplanetary spacecraft missions. It also performs radio and radar astronomy observations for the exploration of the solar system and the universe, and supports selected Earth-orbiting missions. DSN is part of the NASA Jet Propulsion Laboratory (JPL). Similar networks are run by Europe, Russia, China, India, and Japan.

General information

Deep Space Network Operations Center

DSN currently consists of three deep-space communications facilities placed approximately 120 degrees apart around the Earth.[1][2] They are:

Each facility is situated in semi-mountainous, bowl-shaped terrain to help shield against radio frequency interference.[3] The strategic 120-degree placement permits constant observation of spacecraft as the Earth rotates, and helps to make the DSN the largest and most sensitive scientific telecommunications system in the world.[citation needed]

The DSN supports NASA's contribution to the scientific investigation of the Solar System: It provides a two-way communications link that guides and controls various NASA unmanned interplanetary space probes, and brings back the images and new scientific information these probes collect. All DSN antennas are steerable, high-gain, parabolic reflector antennas.[3] The antennas and data delivery systems make it possible to:[2]

  • acquire telemetry data from spacecraft.
  • transmit commands to spacecraft.
  • upload software modifications to spacecraft.
  • track spacecraft position and velocity.
  • perform Very Long Baseline Interferometry observations.
  • measure variations in radio waves for radio science experiments.
  • gather science data.
  • monitor and control the performance of the network.

Operations control center

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The antennas at all three DSN Complexes communicate directly with the Deep Space Operations Center (also known as Deep Space Network operations control center) located at the JPL facilities in Pasadena, California.

In the early years, the operations control center did not have a permanent facility. It was a makeshift setup with numerous desks and phones installed in a large room near the computers used to calculate orbits. In July 1961, NASA started the construction of the permanent facility, Space Flight Operations Facility (SFOF). The facility was completed in October 1963 and dedicated on May 14, 1964. In the initial setup of the SFOF, there were 31 consoles, 100 closed-circuit television cameras, and more than 200 television displays to support Ranger 6 to Ranger 9 and Mariner 4.[4]

Currently, the operations center personnel at SFOF monitor and direct operations, and oversee the quality of spacecraft telemetry and navigation data delivered to network users. In addition to the DSN complexes and the operations center, a ground communications facility provides communications that link the three complexes to the operations center at JPL, to space flight control centers in the United States and overseas, and to scientists around the world.[5]

Deep space

View from the Earth's north pole, showing the field of view of the main DSN antenna locations. Once a mission gets more than 30,000 km from earth, it is always in view of at least one of the stations.

Tracking vehicles in deep space is quite different from tracking missions in low Earth orbit (LEO). Deep space missions are visible for long periods of time from a large portion of the Earth's surface, and so require few stations (the DSN has only three main sites). These few stations, however, require huge antennas, ultra-sensitive receivers, and powerful transmitters in order to transmit and receive over the vast distances involved.

Deep space is defined in several different ways. According to a 1975 NASA report, the DSN was designed to communicate with "spacecraft traveling approximately 16,000 km (10,000 miles) from Earth."[6] JPL diagrams[7] state that at an altitude of 30,000 km, a spacecraft is always in the field of view of one of the tracking stations.

The International Telecommunications Union, which sets aside various frequency bands for deep space and near Earth use, defines "deep space" to start at a distance of 2 million km from the Earth's surface.[8]

This definition means that missions to the Moon, and the Earth–Sun Lagrangian points L1 and L2, are considered near space and cannot use the ITU's deep space bands. Other Lagrangian points may or may not be subject to this rule due to distance.

History

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The forerunner of the DSN was established in January 1958, when JPL, then under contract to the U.S. Army, deployed portable radio tracking stations in Nigeria, Singapore, and California to receive telemetry and plot the orbit of the Army-launched Explorer 1, the first successful U.S. satellite.[9] NASA was officially established on October 1, 1958, to consolidate the separately developing space-exploration programs of the US Army, US Navy, and US Air Force into one civilian organization.[10]

On December 3, 1958, JPL was transferred from the US Army to NASA and given responsibility for the design and execution of lunar and planetary exploration programs using remotely controlled spacecraft. Shortly after the transfer, NASA established the concept of the Deep Space Network as a separately managed and operated communications system that would accommodate all deep space missions, thereby avoiding the need for each flight project to acquire and operate its own specialized space communications network. The DSN was given responsibility for its own research, development, and operation in support of all of its users. Under this concept, it has become a world leader in the development of low-noise receivers; large parabolic-dish antennas; tracking, telemetry, and command systems; digital signal processing; and deep space navigation.

The largest antennas of the DSN are often called on during spacecraft emergencies. Almost all spacecraft are designed so normal operation can be conducted on the smaller (and more economical) antennas of the DSN, but during an emergency the use of the largest antennas is crucial. This is because a troubled spacecraft may be forced to use less than its normal transmitter power, attitude control problems may preclude the use of high-gain antennas, and recovering every bit of telemetry is critical to assessing the health of the spacecraft and planning the recovery. The most famous example is the Apollo 13 mission, where limited battery power and inability to use the spacecraft's high-gain antennas reduced signal levels below the capability of the Manned Space Flight Network, and the use of the biggest DSN antennas (and the Australian Parkes Observatory radio telescope) was critical to saving the lives of the astronauts. While Apollo was also a US mission, DSN provides this emergency service to other space agencies as well, in a spirit of inter-agency and international cooperation. For example, the recovery of the Solar and Heliospheric Observatory (SOHO) mission of the European Space Agency (ESA) would not have been possible without the use of the largest DSN facilities.

DSN and the Apollo program

Although normally tasked with tracking unmanned spacecraft, the Deep Space Network (DSN) also contributed to the communication and tracking of Apollo missions to the Moon, although primary responsibility was held by the Manned Space Flight Network. The DSN designed the MSFN stations for lunar communication and provided a second antenna at each MSFN site (the MSFN sites were near the DSN sites for just this reason). Two antennas at each site were needed both for redundancy and because the beam widths of the large antennas needed were too small to encompass both the lunar orbiter and the lander at the same time. DSN also supplied some larger antennas as needed, in particular for television broadcasts from the Moon, and emergency communications such as Apollo 13.[11]

Excerpt from a NASA report describing how the DSN and MSFN cooperated for Apollo:[12]

<templatestyles src="Template:Blockquote/styles.css" />

Another critical step in the evolution of the Apollo Network came in 1965 with the advent of the DSN Wing concept. Originally, the participation of DSN 26-m antennas during an Apollo Mission was to be limited to a backup role. This was one reason why the MSFN 26-m sites were collocated with the DSN sites at Goldstone, Madrid, and Canberra. However, the presence of two, well-separated spacecraft during lunar operations stimulated the rethinking of the tracking and communication problem. One thought was to add a dual S-band RF system to each of the three 26-m MSFN antennas, leaving the nearby DSN 26-m antennas still in a backup role. Calculations showed, though, that a 26-m antenna pattern centered on the landed Lunar Module would suffer a 9-to-12 db loss at the lunar horizon, making tracking and data acquisition of the orbiting Command Service Module difficult, perhaps impossible. It made sense to use both the MSFN and DSN antennas simultaneously during the all-important lunar operations. JPL was naturally reluctant to compromise the objectives of its many unmanned spacecraft by turning three of its DSN stations over to the MSFN for long periods. How could the goals of both Apollo and deep space exploration be achieved without building a third 26-m antenna at each of the three sites or undercutting planetary science missions?

<templatestyles src="Template:Blockquote/styles.css" />

The solution came in early 1965 at a meeting at NASA Headquarters, when Eberhardt Rechtin suggested what is now known as the "wing concept". The wing approach involves constructing a new section or "wing" to the main building at each of the three involved DSN sites. The wing would include a MSFN control room and the necessary interface equipment to accomplish the following:

  1. Permit tracking and two-way data transfer with either spacecraft during lunar operations.
  2. Permit tracking and two-way data transfer with the combined spacecraft during the flight to the Moon.
  3. Provide backup for the collocated MSFN site passive track (spacecraft to ground RF links) of the Apollo spacecraft during trans-lunar and trans-earth phases.

With this arrangement, the DSN station could be quickly switched from a deep-space mission to Apollo and back again. GSFC personnel would operate the MSFN equipment completely independently of DSN personnel. Deep space missions would not be compromised nearly as much as if the entire station's equipment and personnel were turned over to Apollo for several weeks.

The details of this cooperation and operation are available in a two-volume technical report from JPL.[13][14]

Management

The network is a NASA facility and is managed and operated for NASA by JPL, which is part of the California Institute of Technology (Caltech). The Interplanetary Network Directorate (IND) manages the program within JPL and is charged with the development and operation of it. The IND is considered to be JPL's focal point for all matters relating to telecommunications, interplanetary navigation, information systems, information technology, computing, software engineering, and other relevant technologies. While the IND is best known for its duties relating to the Deep Space Network, the organization also maintains the JPL Advanced Multi-Mission Operations System (AMMOS) and JPL's Institutional Computing and Information Services (ICIS).[15][16]

ITT Systems is under a 5-year contract to JPL for the DSN Operations and Maintenance. ITT has responsibility for managing the Goldstone complex, operating the DSOC, and for DSN Operations, Mission Planning, Operations Engineering, and Logistics.[17]

Antennas

70 m antenna at Goldstone

Each complex consists of at least four deep space terminals equipped with ultra-sensitive receiving systems and large parabolic-dish antennas. There are:

  • One 34-meter (112 ft) diameter High Efficiency antenna (HEF).
  • Two or more 34-meter (112 ft) Beam waveguide antennas (BWG) (three operational at the Goldstone Complex, two at the Robledo de Chavela complex (near Madrid), and two at the Canberra Complex).
  • One 26-meter (85 ft) antenna.
  • One 70-meter (230 ft) antenna (70M).

Five of the 34-meter (112 ft) beam waveguide antennas were added to the system in the late 1990s. Three were located at Goldstone, and one each at Canberra and Madrid. A second 34-meter (112 ft) beam waveguide antenna (the network's sixth) was completed at the Madrid complex in 2004.

In order to meet the current and future needs of deep space communication services, a number of new Deep Space Station antennas need to be built at the existing Deep Space Network sites. At the Canberra Deep Space Communication Complex the first of these was completed October 2014, and a second has begun construction and is scheduled to be complete in 2016.[18]

Current signal processing capabilities

The Canberra Deep Space Communication Complex in 2008

The general capabilities of the DSN have not substantially changed since the beginning of the Voyager Interstellar Mission in the early 1990s. However, many advancements in digital signal processing, arraying and error correction have been adopted by the DSN.

The ability to array several antennas was incorporated to improve the data returned from the Voyager 2 Neptune encounter, and extensively used for the Galileo spacecraft, when the high-gain antenna did not deploy correctly.[19]

The DSN array currently available since the Galileo mission can link the 70-meter (230 ft) dish antenna at the Deep Space Network complex in Goldstone, California, with an identical antenna located in Australia, in addition to two 34-meter (112 ft) antennas at the Canberra complex. The California and Australia sites were used concurrently to pick up communications with Galileo.

Arraying of antennas within the three DSN locations is also used. For example, a 70-meter (230 ft) dish antenna can be arrayed with a 34-meter dish. For especially vital missions, like Voyager 2, the Canberra 70-meter (230 ft) dish can be arrayed with the Parkes Radio Telescope in Australia; and the Goldstone 70-meter dish can be arrayed with the Very Large Array of antennas in New Mexico. Also, two or more 34-meter (112 ft) dishes at one DSN location are commonly arrayed together.

All the stations are remotely operated from a centralized Signal Processing Center at each complex. These Centers house the electronic subsystems that point and control the antennas, receive and process the telemetry data, transmit commands, and generate the spacecraft navigation data. Once the data is processed at the complexes, it is transmitted to JPL for further processing and for distribution to science teams over a modern communications network.

Network limitations and challenges

70m antenna in Robledo de Chavela, Community of Madrid, Spain

There are a number of limitations to the current DSN, and a number of challenges going forward.

  • The Deep Space Network is something of a misnomer, as there are no current plans, nor future plans, for exclusive communication satellites anywhere in space to handle multiparty, multi-mission use. All the transmitting and receiving equipment are Earth-based. Therefore data transmission rates from/to any and all spacecrafts and space probes are severely constrained due to the distances from Earth.
  • The need to support "legacy" missions that have remained operational beyond their original lifetimes but are still returning scientific data. Programs such as Voyager have been operating long past their original mission termination date. They also need some of the largest antennas.
  • Replacing major components can cause problems as it can leave an antenna out of service for months at a time.
  • The older 70M & HEF antennas are reaching the end of their lives. At some point these will need to be replaced. The leading candidate for 70M replacement had been an array of smaller dishes,[20][21] but more recently the decision was taken to expand the provision of 34-meter (112 ft) BWG antennas at each complex to a total of 4.[22]
  • By 2020, the DSN may be required to support twice the number of missions it was supporting in 2005. The financial crisis of 2007–08 has limited the number of new missions somewhat[citation needed]. However, due to decay and lack of replacement of the existing antennas increased mission support will continue to be an ongoing problem. New spacecraft intended for missions beyond geocentric orbits are being equipped to use the beacon mode service, which allows such missions to operate without the DSN most of the time.

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found. p. 25
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Uplink-Downlink: A History of the Deep Space Network, 1957–1997 (NASA SP-2001-4227), page 5
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found. 100MB PDF file. Explicitly non-copyrighted.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. IND Technology Program Overview
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Uplink-Downlink, Chapter 5, The Galileo Era – 1986–1996.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
Notes
  1. Ulysses' extended mission operation terminated June 30, 2009. The extension permitted a third flyby over the Sun's poles in 2007–2008.
  2. The two Voyager spacecraft continue to operate, with some loss in subsystem redundancy, but retain the capability of returning science data from a full complement of VIM science instruments. Both spacecraft also have adequate electrical power and attitude control propellant to continue operating until around 2020, when the available electrical power will no longer support science instrument operation. At this time, science data return and spacecraft operations will cease.

External links and further reading