[widar-wg] WIDAR status 31may11
Bruce Rowen
browen at nrao.edu
Wed Jun 1 09:53:43 EDT 2011
On May 31, 2011, at 4:54 PM, Michael Rupen wrote:
> Sonja put in a new version of the CM (2011-05-31 20:34 UT) which
> purports
> to solve the first-scan problem, and also sends alert messages
> (currently
> blocked at the CM however). We have seen no sign that this causes
> problems & so propose running with the new version overnight.
>
> C_quad* shows several BlB problems:
>
> * b104-t-4 is still bad, as expected
>
> * b106-b-4: The X2Y5 LTA claims the CC is flagging all the data,
> altho'
> the CC itself seems perfectly happy (claims no errors). This is
> true
> regardless of the input streams.
Alert messages show that this CC has been having 'issues' since
2011-05-31T05:10:50.60Z.
The Zombie trigger* has been forcing CC resets.
*Not all 32 data lines from the CC to LTA are toggling, CC is in use,
CC power reports OK, no 'frame abort' indicators.
>
> * b108-b-5 has no power.
> This led the CBE to complain: Failed to convert blb hostname b108-
> b-5
> to serial number.
> - so far so good!
>
> But, when the CM tries to configure b108-b-5, it hangs waiting for
> the CBE to respond. Martin & Sonja should get together to be sure
> something sensible happens in this case.
>
> * b107-t-2: upper RXP showed lots of errors on wafer 31 (ea06-BD)
> although b107-t-3 looked fine.
> The CTRL LED showed HM lock YELLOW rather than the hoped-for GREEN.
> A few minutes later this spontaneously cleared up. Some sort of
> synchronization issue???
b107-t-3 shows a burst of RXP errors at that time.
-Bruce
>
> For now I propose we avoid these BlBs for scientific observation and
> check on them again tomorrow.
>
> Michael
>
> ________________________________________________________________________________
> There is a web page, used as a document repository, associated with
> this list.
> The URL for the web page is:
> http://listmgr.cv.nrao.edu/pipermail/widar-wg/
More information about the widar-wg
mailing list