12.07.2015 Views

GP-B Post-Flight Analysis—Final Report - Gravity Probe B - Stanford ...

GP-B Post-Flight Analysis—Final Report - Gravity Probe B - Stanford ...

GP-B Post-Flight Analysis—Final Report - Gravity Probe B - Stanford ...

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Figure 8-44. Location of Multi-Bit Errors during the first year of on-orbit operationsBuilt-in safemode protection against multiple CCCA MBEs in the same memory scrub cycle was exercised morethan once on-orbit. When activated, this safemode response resulted in either a B-side “block switch”, with theredundant B-side CCCA / C&DH system taking over for the A-side equipment, or a reboot of the B-side CCCA.While disruptive to any ongoing activities, including science data taking, this response resulted in theautonomous clearing of any MBEs in the system, ensuring vehicle safety. The first time this safemode responseactivated, during IOC, the software team successfully recovered the spacecraft back to the A-side equipment.Per plan, when this safing action occurred during science data collection, the CCCA was kept on the B-side forthe remainder of the mission. Figure 8-45 shows the cumulative MBE count (in the CCCA only) from launchthrough the end of May 2005. The pink shaded regions represent operation on the B-side CCCA.Figure 8-45. Cumulative CCCA MBE count from launch through end of May 2005.<strong>Gravity</strong> <strong>Probe</strong> B — <strong>Post</strong> <strong>Flight</strong> Analysis • Final <strong>Report</strong> March 2007 253

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!