Galileo (spacecraft)

The CDH subsystem was actively redundant, with two parallel data system buses running at all times.[12] Each data system bus (a.k.a. string) was composed of the same functional elements, consisting of multiplexers (MUX), high-level modules (HLM), low-level modules (LLM), power converters (PC), bulk memory (BUM), data management subsystem bulk memory (DBUM), timing chains (TC), phase locked loops (PLL), Golay coders (GC), hardware command decoders (HCD) and critical controllers (CRC).

The CDH subsystem was responsible for maintaining the following functions:

1. decoding of uplink commands
2. execution of commands and sequences
3. execution of system-level fault-protection responses
4. collection, processing, and formatting of telemetry data for downlink transmission
5. movement of data between subsystems via a data system bus

The spacecraft was controlled by six RCA 1802 COSMAC microprocessor CPUs: four on the spun side and two on the despun side. Each CPU was clocked at about 1.6 MHz, and fabricated on sapphire (silicon on sapphire), which is a radiation-and static-hardened material ideal for spacecraft operation. This microprocessor was the first low-power CMOS processor chip, quite on a par with the 8-bit 6502 that was being built into the Apple II desktop computer at that time.

The Galileo Attitude and Articulation Control System (AACSE) was controlled by two Itek Advanced Technology Airborne Computers (ATAC), built using radiation-hardened 2901s. The AACSE could be reprogrammed in flight by sending the new program through the Command and Data Subsystem. Galileo's attitude control system software was written in the HAL/S programming language,[8] also used in the Space Shuttle program.

Memory capacity provided by each BUM was 16K of RAM, while the DBUMs each provided 8K of RAM. There were two BUMs and two DBUMs in the CDH subsystem and they all resided on the spun side of the spacecraft. The BUMs and DBUMs provided storage for sequences and contain various buffers for telemetry data and interbus communication.

Every HLM and LLM was built up around a single 1802 microprocessor and 32K of RAM (for HLMs) or 16K of RAM (for LLMs). Two HLMs and two LLMs resided on the spun side while two LLMs were on the despun side.

Thus, total memory capacity available to the CDH subsystem was 176K of RAM: 144K allocated to the spun side and 32K to the despun side.

Each HLM was responsible for the following functions:

1. uplink command processing
2. maintenance of the spacecraft clock
3. movement of data over the data system bus
4. execution of stored sequences (time-event tables)
5. telemetry control
6. error recovery including system fault-protection monitoring and response

Each LLM was responsible for the following functions:

1. collect and format engineering data from the subsystems
2. provide the capability to issue coded and discrete commands to spacecraft users
3. recognize out-of-tolerance conditions on status inputs
4. perform some system fault-protection functions

The HCD received command data from the modulation/demodulation subsystem, decoded these data and transferred them to the HLMs and CRCs.

The CRC controlled the configuration of CDH subsystem elements. It also controlled access to the two data system buses by other spacecraft subsystems. In addition, the CRC supplied signals to enable certain critical events (e.g. probe separation).

The GCs provided Golay encoding of data via hardware.

The TCs and PLLs established timing within the CDH subsystem.

Galileo's propulsion module

The propulsion subsystem consisted of a 400 N main engine and twelve 10 N thrusters, together with propellant, storage and pressurizing tanks and associated plumbing. The 10 N thrusters were mounted in groups of six on two 2-meter booms. The fuel for the system was 925 kg (2,039 lb) of monomethylhydrazine and nitrogen tetroxide. Two separate tanks held another 7 kg (15 lb) of helium pressurant. The propulsion subsystem was developed and built by Messerschmitt-Bölkow-Blohm and provided by West Germany, the major international partner in Project Galileo.[13]

At the time, solar panels were not practical at Jupiter's distance from the Sun; the spacecraft would have needed a minimum of 65 square meters (700 sq ft) of panels. Chemical batteries would likewise be prohibitively large due to technological limitations. The solution was two radioisotope thermoelectric generators (RTGs) which powered the spacecraft through the radioactive decay of plutonium-238. The heat emitted by this decay was converted into electricity through the solid-state Seebeck effect. This provided a reliable and long-lasting source of electricity unaffected by the cold environment and high-radiation fields in the Jovian system.

Each GPHS-RTG, mounted on a 5-meter long (16 ft) boom, carried 7.8 kilograms (17 pounds) of 238
Pu.[14] Each RTG contained 18 separate heat source modules, and each module encased four pellets of plutonium(IV) oxide, a ceramic material resistant to fracturing. The modules were designed to survive a range of potential accidents: launch vehicle explosion or fire, re-entry into the atmosphere followed by land or water impact, and post-impact situations. An outer covering of graphite provided protection against the structural, thermal, and eroding environments of a potential re-entry. Additional graphite components provided impact protection, while iridium cladding of the fuel cells provided post-impact containment. The RTGs produced about 570 watts at launch. The power output initially decreased at the rate of 0.6 watts per month and was 493 watts when Galileo arrived at Jupiter.

As the launch of Galileo neared, anti-nuclear groups, concerned over what they perceived as an unacceptable risk to the public's safety from Galileo's RTGs, sought a court injunction prohibiting Galileo's launch. RTGs had been used for years in planetary exploration without mishap: the Lincoln Experimental Satellites 8/9, launched by the U.S. Department of Defense, had 7% more plutonium on board than Galileo, and the two Voyager spacecraft each carried 80% as much plutonium as Galileo. Activists remembered the messy crash of the Soviet Union's nuclear-powered Kosmos 954 satellite in Canada in 1978, and the 1986 Challenger accident, which did not involve nuclear fuel but raised public awareness about spacecraft failures. In addition, no RTGs had ever done a non-orbital swing past the Earth at close range and high speed, as Galileo's Venus-Earth-Earth gravity assist trajectory required it to do. This created a novel mission failure modality that might plausibly have entailed total dispersal of Galileo's plutonium in the Earth's atmosphere. Scientist Carl Sagan, for example, a strong supporter of the Galileo mission, said in 1989 that "there is nothing absurd about either side of this argument."[15]

After the Challenger accident, a study considered additional shielding but rejected it, in part because such a design significantly increased the overall risk of mission failure and only shifted the other risks around. For example, if a failure on orbit had occurred, additional shielding would have significantly increased the consequences of a ground impact.[14]

Image mosaic of Europa produced from the multiple Galileo images

Scientific instruments to measure fields and particles were mounted on the spinning section of the spacecraft, together with the main antenna, power supply, the propulsion module and most of Galileo's computers and control electronics. The sixteen instruments, weighing 118 kg (260 lb) altogether, included magnetometer sensors mounted on an 11 m (36 ft) boom to minimize interference from the spacecraft; a plasma instrument for detecting low-energy charged particles and a plasma-wave detector to study waves generated by the particles; a high-energy particle detector; and a detector of cosmic and Jovian dust. It also carried the Heavy Ion Counter, an engineering experiment to assess the potentially hazardous charged particle environments the spacecraft flew through, and an extreme ultraviolet detector associated with the UV spectrometer on the scan platform.

The despun section's instruments included the camera system; the near infrared mapping spectrometer to make multi-spectral images for atmospheric and moon surface chemical analysis; the ultraviolet spectrometer to study gases; and the photopolarimeter-radiometer to measure radiant and reflected energy. The camera system was designed to obtain images of Jupiter's satellites at resolutions 20 to 1,000 times better than Voyager's best, because Galileo flew closer to the planet and its inner moons, and because the more modern CCD sensor in Galileo's camera was more sensitive and had a broader color detection band than the vidicons of Voyager.

The following information was taken directly from NASA's Galileo legacy site.[16]

Solid-State Imager

The SSI was an 800-by-800-pixel solid state camera consisting of an array of silicon sensors called a charge-coupled device (CCD). Galileo was one of the first spacecraft to be equipped with a CCD camera. The optical portion of the camera was built as a Cassegrain telescope. Light was collected by the primary mirror and directed to a smaller secondary mirror that channeled it through a hole in the center of the primary mirror and onto the CCD. The CCD sensor was shielded from radiation, a particular problem within the harsh Jovian magnetosphere. The shielding was accomplished by means of a 10 mm (0.4 in) thick layer of tantalum surrounding the CCD except where the light enters the system. An eight-position filter wheel was used to obtain images at specific wavelengths. The images were then combined electronically on Earth to produce color images. The spectral response of the SSI ranged from about 400 to 1100 nm. The SSI weighed 29.7 kg (65 lb) and consumed, on average, 15 watts of power.[17][18]

Near-Infrared Mapping Spectrometer

The NIMS instrument was sensitive to 0.7-to-5.2-micrometer wavelength infrared light, overlapping the wavelength range of the SSI. The telescope associated with NIMS was all reflective (using only mirrors and no lenses) with an aperture of 229 mm (9 in). The spectrometer of NIMS used a grating to disperse the light collected by the telescope. The dispersed spectrum of light was focused on detectors of indium, antimonide and silicon. The NIMS weighed 18 kg (40 lb) and used 12 watts of power on average.[19][20]

Ultraviolet Spectrometer

The Cassegrain telescope of the UVS had a 250 mm (9.8 in) aperture and collected light from the observation target. Both the UVS and EUV instruments used a ruled grating to disperse this light for spectral analysis. This light then passed through an exit slit into photomultiplier tubes that produced pulses or "sprays" of electrons. These electron pulses were counted, and these count numbers constituted the data that were sent to Earth. The UVS was mounted on Galileo's scan platform and could be pointed to an object in inertial space. The EUV was mounted on the spun section. As Galileo rotated, EUV observed a narrow ribbon of space perpendicular to the spin axis. The two instruments combined weighed about 9.7 kg (21 lb) and used 5.9 watts of power.[21][22]

The PPR had seven radiometry bands. One of these used no filters and observed all incoming radiation, both solar and thermal. Another band allowed only solar radiation through. The difference between the solar-plus-thermal and the solar-only channels gave the total thermal radiation emitted. The PPR also measured in five broadband channels that spanned the spectral range from 17 to 110 micrometers. The radiometer provided data on the temperatures of Jupiter's atmosphere and satellites. The design of the instrument was based on that of an instrument flown on the Pioneer Venus spacecraft. A 100 mm (4 in) aperture reflecting telescope collected light and directed it to a series of filters, and, from there, measurements were performed by the detectors of the PPR. The PPR weighed 5.0 kg (11.0 lb) and consumed about 5 watts of power.[23][24]

Dust Detector Subsystem

The Dust Detector Subsystem (DDS) was used to measure the mass, electric charge, and velocity of incoming particles. The masses of dust particles that the DDS could detect go from 10⁻¹⁶ to 10⁻⁷ grams. The speed of these small particles could be measured over the range of 1 to 70 kilometers per second (0.6 to 43.5 mi/s). The instrument could measure impact rates from 1 particle per 115 days (10 megaseconds) to 100 particles per second. Such data was used to help determine dust origin and dynamics within the magnetosphere. The DDS weighed 4.2 kg (9.3 lb) and used an average of 5.4 watts of power.[25][26]

The Energetic Particles Detector (EPD) was designed to measure the numbers and energies of ions and electrons whose energies exceeded about 20 keV (3.2 fJ). The EPD could also measure the direction of travel of such particles and, in the case of ions, could determine their composition (whether the ion is oxygen or sulfur, for example). The EPD used silicon solid-state detectors and a time-of-flight detector system to measure changes in the energetic particle population at Jupiter as a function of position and time. These measurements helped determine how the particles got their energy and how they were transported through Jupiter's magnetosphere. The EPD weighed 10.5 kg (23 lb) and used 10.1 watts of power on average.[27][28]

Heavy Ion Counter

The HIC was, in effect, a repackaged and updated version of some parts of the flight spare of the Voyager Cosmic Ray System. The HIC detected heavy ions using stacks of single crystal silicon wafers. The HIC could measure heavy ions with energies as low as 6 MeV (1 pJ) and as high as 200 MeV (32 pJ) per nucleon. This range included all atomic substances between carbon and nickel. The HIC and the EUV shared a communications link and, therefore, had to share observing time. The HIC weighed 8.0 kg (17.6 lb) and used an average of 2.8 watts of power.[29][30]

Magnetometer

The magnetometer (MAG) used two sets of three sensors. The three sensors allowed the three orthogonal components of the magnetic field section to be measured. One set was located at the end of the magnetometer boom and, in that position, was about 11 m (36 ft) from the spin axis of the spacecraft. The second set, designed to detect stronger fields, was 6.7 m (22 ft) from the spin axis. The boom was used to remove the MAG from the immediate vicinity of Galileo to minimize magnetic effects from the spacecraft. However, not all these effects could be eliminated by distancing the instrument. The rotation of the spacecraft was used to separate natural magnetic fields from engineering-induced fields. Another source of potential error in measurement came from the bending and twisting of the long magnetometer boom. To account for these motions, a calibration coil was mounted rigidly on the spacecraft to generate a reference magnetic field during calibrations. The magnetic field at the surface of the Earth has a strength of about 50,000 nT. At Jupiter, the outboard (11 m) set of sensors could measure magnetic field strengths in the range from ±32 to ±512 nT, while the inboard (6.7 m) set was active in the range from ±512 to ±16,384 nT. The MAG experiment weighed 7.0 kg (15.4 lb) and used 3.9 watts of power.[31][32]

Plasma Wave Subsystem

The PLS used seven fields of view to collect charged particles for energy and mass analysis. These fields of view covered most angles from 0 to 180 degrees, fanning out from the spin axis. The rotation of the spacecraft carried each field of view through a full circle. The PLS measured particles in the energy range from 0.9 to 52,000 eV (0.14 to 8,300 aJ). The PLS weighed 13.2 kg (29 lb) and used an average of 10.7 watts of power.[33][34]

An electric dipole antenna was used to study the electric fields of plasmas, while two search coil magnetic antennas studied the magnetic fields. The electric dipole antenna was mounted at the tip of the magnetometer boom. The search coil magnetic antennas were mounted on the high-gain antenna feed. Nearly simultaneous measurements of the electric and magnetic field spectrum allowed electrostatic waves to be distinguished from electromagnetic waves. The PWS weighed 7.1 kg (16 lb) and used an average of 9.8 watts.[35][36]

Galileo image of Earth, taken in December 1990

The astronomer Carl Sagan, pondering the question of whether life on Earth could be easily detected from space, devised a set of experiments in the late 1980s using Galileo's remote sensing instruments during the mission's first Earth flyby in December 1990. After data acquisition and processing, Sagan et al. published a paper in Nature in 1993 detailing the results of the experiment. Galileo had indeed found what are now referred to as the "Sagan criteria for life". These included strong absorption of light at the red end of the visible spectrum (especially over continents) which was caused by absorption by chlorophyll in photosynthesizing plants, absorption bands of molecular oxygen which is also a result of plant activity, infrared absorption bands caused by the ~1 micromole per mole (µmol/mol) of methane in Earth's atmosphere (a gas which must be replenished by either volcanic or biological activity), and modulated narrowband radio wave transmissions uncharacteristic of any known natural source. Galileo's experiments were thus the first ever controls in the newborn science of astrobiological remote sensing.[39]

An image of Earth taken by Galileo during the GOPEX test, showing laser pulses coming from a transmitting telescope on the night side. Galileo's imager was panned downward during the exposure to separate the pulses, thus blurring Earth's image on the right.

In December 1992, during Galileo's second gravity-assist planetary flyby of Earth, another groundbreaking experiment was performed. Optical communications in space were assessed by detecting light pulses from powerful lasers with Galileo's CCD. The experiment, dubbed Galileo Optical Experiment or GOPEX,[40] used two separate sites to beam laser pulses to the spacecraft, one at Table Mountain Observatory in California and the other at the Starfire Optical Range in New Mexico. The Table Mountain site used a frequency doubled neodymium-yttrium-aluminium garnet (Nd:YAG) laser operating at 532 nm with a repetition rate of ~15 to 30 Hz and a pulse power (FWHM) in the tens of megawatts range, which was coupled to a 0.6 m (2.0 ft) Cassegrain telescope for transmission to Galileo. The Starfire range site used a similar setup with a larger, 1.5 m (4.9 ft), transmitting telescope. Long exposure (~0.1 to 0.8 s) images using Galileo's 560 nm centered green filter produced images of Earth clearly showing the laser pulses even at distances of up to 6 million km (3.7 million mi). Adverse weather conditions, restrictions placed on laser transmissions by the U.S. Space Defense Operations Center (SPADOC) and a pointing error caused by the scan platform acceleration on the spacecraft being slower than expected (which prevented laser detection on all frames with less than 400 ms exposure times) all contributed to the reduction of the number of successful detections of the laser transmission to 48 of the total 159 frames taken. Nonetheless, the experiment was considered a resounding success and the data acquired will likely be used in the future to design laser "downlinks" which will send large volumes of data very quickly from spacecraft to Earth. The scheme was already being studied (as of 2004) for a data link to a future Mars orbiting spacecraft.[41]

• 
  Showing Mare Orientale
• 
  Galileo shot of Earth's Moon
• 
  False color mosaic by Galileo showing compositional variations of the Moon's surface

Galileo's star scanner was a small optical telescope that provided an absolute attitude reference. It also made several scientific discoveries serendipitously.[42] In the prime mission, it was found that the star scanner was able to detect high-energy particles as a noise signal. This data was eventually calibrated to show the particles were predominantly >2 MeV (0.32 pJ) electrons that were trapped in the Jovian magnetic belts, and released to the Planetary Data System.

A second discovery occurred in 2000. The star scanner was observing a set of stars which included the second magnitude star Delta Velorum. At one point, this star dimmed for 8 hours below the star scanner's detection threshold. Subsequent analysis of Galileo data and work by amateur and professional astronomers showed that Delta Velorum is the brightest known eclipsing binary, brighter at maximum than even Algol.[43] It has a primary period of 45 days and the dimming is just visible with the naked eye.

A final discovery occurred during the last two orbits of the mission. When the spacecraft passed the orbit of Jupiter's moon Amalthea, the star scanner detected unexpected flashes of light that were reflections from moonlets. None of the individual moonlets were reliably sighted twice, hence no orbits were determined and the moonlets did not meet the International Astronomical Union requirements to receive designations.[44] It is believed that these moonlets most likely are debris ejected from Amalthea and form a tenuous, and perhaps temporary, ring.[45]

On October 29, 1991, two months after entering the asteroid belt, Galileo performed the first asteroid encounter by a spacecraft, passing approximately 1,600 kilometers (990 mi) from 951 Gaspra at a relative speed of about 8 kilometers per second (5.0 mi/s). Several pictures of Gaspra were taken, along with measurements using the NIMS instrument to indicate composition and physical properties. The last two images were relayed back to Earth in November 1991 and June 1992. The imagery revealed a cratered and very irregular body, measuring about 19 by 12 by 11 kilometers (11.8 by 7.5 by 6.8 miles). The remainder of data taken, including low-resolution images of more of the surface, were transmitted in late November 1992.[46]

On August 28, 1993, Galileo flew within 2,400 kilometers (1,500 mi) of the asteroid 243 Ida. The probe discovered that Ida had a small moon, dubbed Dactyl, measuring around 1.4 kilometers (0.87 mi) in diameter; this was the first asteroid moon discovered. Measurements using Galileo's Solid State Imager, Magnetometer and NIMS instrument were taken. From subsequent analysis of this data, Dactyl appears to be an SII-subtype S-type asteroid, and is spectrally different from 243 Ida. It is hypothesized that Dactyl may have been produced by partial melting within a Koronis parent body, while the 243 Ida region escaped such igneous processing.

Jupiter's inner magnetosphere and radiation belts

Jupiter's uniquely harsh radiation environment caused over 20 anomalies over the course of Galileo's mission, in addition to the incidents expanded upon below. Despite having exceeded its radiation design limit by at least a factor of three, the spacecraft survived all these anomalies. Work-arounds were found eventually for all of these problems, and Galileo was never rendered entirely non-functional by Jupiter's radiation. The radiation limits for Galileo's computers were based on data returned from Pioneers 10 and 11, since much of the design work was underway before the two Voyagers arrived at Jupiter in 1979.[47]

A typical effect of the radiation was that several of the science instruments suffered increased noise while within about 700,000 km (430,000 mi) of Jupiter. The SSI camera began producing totally white images when the spacecraft was hit by the exceptional 'Bastille Day' coronal mass ejection in 2000, and did so again on subsequent close approaches to Jupiter. The quartz crystal used as the frequency reference for the radio suffered permanent frequency shifts with each Jupiter approach. A spin detector failed, and the spacecraft gyro output was biased by the radiation environment.

The most severe effect of the radiation were current leakages somewhere in the spacecraft's power bus, most likely across brushes at a spin bearing connecting rotor and stator sections of the orbiter. These current leakages triggered a reset of the onboard computer and caused it to go into safe mode. The resets occurred when the spacecraft was either close to Jupiter or in the region of space magnetically downstream of the Jupiter. A change to the software was made in April 1999 that allowed the onboard computer to detect these resets and autonomously recover, so as to avoid safe mode.[48]

Proposed configuration of antenna problem

Galileo's high-gain antenna failed to fully deploy after its first flyby of Earth.[49] The antenna had 18 ribs, like an umbrella and when the driver motor started and put pressure on the ribs, they were supposed to pop out of the cup their tips were held in. Only 15 popped out, leaving the antenna looking like a lop-sided, half-open umbrella. Investigators concluded that during the 4.5 years that Galileo spent in storage after the 1986 Challenger disaster, the lubricants between the tips of the ribs and the cup were eroded and worn away from vibration during three cross-country journeys by truck between California and Florida for the spacecraft.[50] The failed ribs were those closest to the flat-bed trailers carrying Galileo on these trips, which were used instead of air transport to cut costs. The antenna lubricants were not checked or replaced before launch.

To fix this malfunction, engineers tried thermal-cycling the antenna, rotating the spacecraft up to its maximum spin rate of 10.5 rpm, and "hammering" the antenna deployment motor—turning it on and off repeatedly—over 13,000 times, but all attempts failed to open the high-gain antenna.

Illustration of Galileo with antenna not fully deployed

The associated problem mission managers faced was if one rib popped free, there would be increased pressure on the remaining two, and if one of them popped out the last would be under so much pressure it would never release. The second part of the problem was due to Galileo's revised flight plan. The probe had never been intended to approach the Sun any closer than the orbit of Earth, but sending it to Venus would expose it to temperatures at least 50 degrees higher than at Earth distance. So the probe had to be protected from that extra heat, part of which involved adapting some of the computer functions. Forty-one device drivers had been programmed into the computer, but with no room for any more, the mission planners had to decide which driver they could use in association with the heat protection. They chose the antenna motor reverse driver.

Fortunately, Galileo possessed an additional low-gain antenna that was capable of transmitting information back to Earth, although since it transmitted a signal isotropically, the low-gain antenna's bandwidth was significantly less than what the high-gain antenna's would have been; the high-gain antenna was to have transmitted at 134 kilobits per second, whereas the low-gain antenna was only intended to transmit at about 8 to 16 bits per second. Galileo's low-gain antenna transmitted with a power of about 15 to 20 watts, which, by the time it reached Earth and had been collected by one of the large aperture (70 m) NASA Deep Space Network antennas, had a total power of about −170 dBm or 10 zeptowatts (10⁻²⁰ watts).[51] Through the implementation of sophisticated technologies, the arraying of several Deep Space Network antennas and sensitivity upgrades to the receivers used to listen to Galileo's signal, data throughput was increased to a maximum of 160 bits per second.[49][52] By further using data compression, the effective data rate could be raised to 1,000 bits per second.[52][53] The data collected on Jupiter and its moons was stored in the spacecraft's onboard tape recorder, and transmitted back to Earth during the long apoapsis portion of the probe's orbit using the low-gain antenna. At the same time, measurements were made of Jupiter's magnetosphere and transmitted back to Earth. The reduction in available bandwidth reduced the total amount of data transmitted throughout the mission, although 70% of Galileo's science goals could still be met.[49][54]

The failure of Galileo's high-gain antenna meant that data storage to the tape recorder for later compression and playback was absolutely crucial in order to obtain any substantial information from the flybys of Jupiter and its moons. In October 1995, Galileo's four-track, 114-megabyte digital tape recorder,[55] which was manufactured by Odetics Corporation, remained stuck in rewind mode for 15 hours before engineers learned what had happened and were able to send commands to shut it off. Though the recorder itself was still in working order, the malfunction possibly damaged a length of tape at the end of the reel. This section of tape was subsequently declared "off limits" to any future data recording, and was covered with 25 more turns of tape to secure the section and reduce any further stresses, which could tear it. Because it happened only weeks before Galileo entered orbit around Jupiter, the anomaly prompted engineers to sacrifice data acquisition of almost all of the Io and Europa observations during the orbit insertion phase, in order to focus solely on recording data sent from the Jupiter probe descent.[56]

Wind tunnel test of the atmospheric probe's parachute

In November 2002, after the completion of the mission's only encounter with Jupiter's moon Amalthea, problems with playback of the tape recorder again plagued Galileo. About 10 minutes after the closest approach of the Amalthea flyby, Galileo stopped collecting data, shut down all of its instruments, and went into safe mode, apparently as a result of exposure to Jupiter's intense radiation environment. Though most of the Amalthea data was already written to tape, it was found that the recorder refused to respond to commands telling it to play back data.[57] After weeks of troubleshooting of an identical flight spare of the recorder on the ground, it was determined that the cause of the malfunction was a reduction of light output in three infrared Optek OP133 light-emitting diodes located in the drive electronics of the recorder's motor encoder wheel. The GaAs LEDs had been particularly sensitive to proton-irradiation-induced atomic lattice displacement defects, which greatly decreased their effective light output and caused the drive motor's electronics to falsely believe the motor encoder wheel was incorrectly positioned. Galileo's flight team then began a series of "annealing" sessions, where current was passed through the LEDs for hours at a time to heat them to a point where some of the crystalline lattice defects would be shifted back into place, thus increasing the LED's light output. After about 100 hours of annealing and playback cycles, the recorder was able to operate for up to an hour at a time. After many subsequent playback and cooling cycles, the complete transmission back to Earth of all recorded Amalthea flyby data was successful.

The atmospheric probe deployed its parachute fifty-three seconds later than anticipated, resulting in a small loss of upper atmospheric readings. This was attributed to wiring problems with an accelerometer that determined when to begin the parachute deployment sequence.[58]

NASA's Juno spacecraft, launched in 2011 and planned for a two-year tour of the Jovian system, successfully completed Jupiter orbital insertion on July 4, 2016.[64]

There was a spare Galileo spacecraft that was considered by the NASA-ESA Outer Planets Study Team in 1983 for a mission to Saturn, but it was passed over in favor of a newer design which became Cassini–Huygens.[65] Even before Galileo concluded, NASA considered the Europa Orbiter,[66] which was a mission to Jupiter's moon Europa, but it was canceled in 2002.[67]

ESA also is planning to return to the Jovian system with the Jupiter Icy Moons Explorer (JUICE), which is designed to orbit Ganymede in the 2020s.[68] There have been several other attempts at missions that were dedicated to, or included, the Jupiter system as part of their mission plan but did not make it out of the planning stages.

Following the cancellation of Europa Orbiter, a lower-cost version was studied. This led to the Europa Clipper being approved in 2015; it is currently planned for launch in the mid-2020s.

A lander concept, simply called Europa Lander is being assessed by the Jet Propulsion Laboratory. As of 2019, this lander mission to Europa remains a concept, and some funds have been released for instrument development and maturation.[69][70]