Update on attempts to bring Hubble back to life
Engineers have released an update on their attempts to bring Hubble out of safe mode that are indicating that they are honing in on the cause of the problem.
After performing tests on several of the computer’s memory modules, the results indicate that a different piece of computer hardware may have caused the problem, with the memory errors being only a symptom. The operations team is investigating whether the Standard Interface (STINT) hardware, which bridges communications between the computer’s Central Processing Module (CPM) and other components, or the CPM itself is responsible for the issue. The team is currently designing tests that will be run in the next few days to attempt to further isolate the problem and identify a potential solution.
This step is important for determining what hardware is still working properly for future reference. If the problem with the payload computer can’t be fixed, the operations team will be prepared to switch to the STINT and CPM hardware onboard the backup payload computer. The team has conducted ground tests and operations procedure reviews to verify all the commanding required to perform that switch on the spacecraft.
It appears that no matter what solution they arrive at, they will still require several days to test the solution to make sure it works. This update however is very hopeful, as it does appear they are locating the cause and have avenues for fixing it.
Hubble went into safe mode on June 13, which means it has now been out of operation for more than ten days.
Engineers have released an update on their attempts to bring Hubble out of safe mode that are indicating that they are honing in on the cause of the problem.
After performing tests on several of the computer’s memory modules, the results indicate that a different piece of computer hardware may have caused the problem, with the memory errors being only a symptom. The operations team is investigating whether the Standard Interface (STINT) hardware, which bridges communications between the computer’s Central Processing Module (CPM) and other components, or the CPM itself is responsible for the issue. The team is currently designing tests that will be run in the next few days to attempt to further isolate the problem and identify a potential solution.
This step is important for determining what hardware is still working properly for future reference. If the problem with the payload computer can’t be fixed, the operations team will be prepared to switch to the STINT and CPM hardware onboard the backup payload computer. The team has conducted ground tests and operations procedure reviews to verify all the commanding required to perform that switch on the spacecraft.
It appears that no matter what solution they arrive at, they will still require several days to test the solution to make sure it works. This update however is very hopeful, as it does appear they are locating the cause and have avenues for fixing it.
Hubble went into safe mode on June 13, which means it has now been out of operation for more than ten days.