Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.stsci.edu/ops/swat/safing/11335/notification.txt Дата изменения: Fri Dec 2 19:55:10 2011 Дата индексирования: Sun Mar 2 02:54:31 2014 Кодировка: Поисковые слова: http astrokuban.info astrokuban

Date: Thu, 1 Dec 2011 18:29:47 -0500
From: Ken Sembach
To: opm
Subject: Fwd: SSR3 still locked



Begin forwarded message:

From: "Burley, Richard J. (GSFC-4410)"
Date: December 1, 2011 6:10:34 PM EST
Subject: SSR3 still locked

When reading the SSR3 Remote Terminal 10, sub-address 8, we got a different value 'e005' than we expected '8001' which was based on
the SSR1 event.

The reason for the difference it not completely understood at this point, and investigation is ongoing.

For this reason I've directed the team to configure for a single logical recorder (on SSR1) while we prep the team to conduct some
VEST testing tomorrow. б 

I've directed the FOT to run on ACE overnight once the SSR3 pointers are properly set, and to prepare for staggered shifts tomorrow
so that we can run into the evening if necessary.

We will not be able to induce the RS error on the VEST, so the testing will not be 100% conclusive, but there are some differences
between SSR1 and SSR3 that I feel need to be better understood before proceeding.

We will meet tomorrow morning, time currently TBD, when we expect to have some testing results available.

The likely next step will be a SSR software reset (COP 7.78) that will require some memory patches to be loaded (this is another
area where SSR1 and SSR3 differ), but I wasn't prepared to proceed this this step tonight, until we had more time to investigate and
consider our options.

RB

-- Richard J. Burley
б б HST Operations Manager б NASA/GSFC/441