Initial indications revealed a potential issue with the memory module, so the first attempt to restore the Hubble involved attempting to switch to one of the backups. Switching to the backup controller also stopped working to fix the problem; no matter which mix of controller and memory module was used, Hubble could not write or check out to the memory.
Its still possible to switch to the backup controller and memory, but the series of the treatment will differ based on exactly what is at fault.

On June 13, the Hubble Space Telescope took itself offline due to a fault in its payload computer, which manages the telescopes clinical instruments. Since then, NASA has been doing the sort of troubleshooting thats familiar to a lot of us– with the included pressure of the hardware being irreplaceable, in area, and about the same vintage as a Commodore 64.
Up until now, controllers have actually managed to figure out a number of things that are not at fault, based upon attempted repairs that have not worked. The workers have actually narrowed the problem down, however they havent identified it. And at this point, the next actions will depend on the precise nature of the problem, so getting a diagnosis is the top concern.
If at first you do not succeed …
The hardware at issue is part of the payload computer system, which consists of a control processor, a communications bus, a memory module, and a processor that formats data and commands so that the controller can “speak” to all the individual science instruments (the system likewise converts the data that the instruments produce into a standard format for transmission to Earth). Theres also a power supply that is expected to keep everything operating at the proper voltage.
Advertisement

Bewaring sorts, individuals who developed Hubble supplied a backup controller and 3 backup memory modules.
Initial indications showed a potential issue with the memory module, so the first attempt to bring back the Hubble involved trying to switch to one of the backups. That fix failed, recommending that the odd memory habits was just a sign of problems elsewhere. Switching to the backup controller also failed to repair the issue; no matter which combination of controller and memory module was utilized, Hubble could not compose or read to the memory.
Given that info, the controllers have actually turned their attention elsewhere. Prime prospects are now the power supply, the information bus, and the information format processor. Its still possible to switch to the backup controller and memory, however the series of the procedure will vary based on precisely what is at fault. In a news release, NASA referred to this process as “more complex and riskier.”
We also have reason for optimism: a data formatter failed in 2008, and NASA effectively changed to backups, which operated till a maintenance mission changed the stopped working hardware.
Given that NASA no longer has access to an automobile created for those sorts of maintenance objectives, getting a practical backup in place will be vital if we wish to squeeze more years out of this distinctive observatory.