J. Kissel, G. Mansell Georgia has found that ETMX optical lever was reporting unpleasantly large ~0.5 Hz motion. While I warned her against the on-going issues with ETMX's excessive RX /RY motion (LHO aLOG 42711, FRS Ticket 11021), I also was reminded of earlier today when Fil and Ken were at the end stations killing electronics, which drove Jim to turn off all sensor correction. I've restored the SEI_CONFIG manager to WINDY. All platforms except for ETMY went to "CONFIG_FIR" which I think is right, browsing through the platforms. ETMY failed because it suggests BRSY is at fault. BRSY says it's at fault because its FILTERS [are] NOT READY. I don't know what this means, so I'll leave it for team SEI to debug tomorrow.
The BRS C code had crashed, so the channels were dead. This happened yesterday as well after the power at EY was restored. Was the power interrupted or the Beckhoff at EY restarted again later in the day? When this happens the CBIT (H1:ISI-GND_BRS_ETMY_CBIT) goes to zero (not accurately reflected on the overview, the modbit is shown twice and doesn't change for a C crash, I'll try to fix that), and all of the "live" signals go flat as well (1 day of second trends attached, the CBIT goes to zero several times, VEL, RX_IN and DRIFT all go zero or flat). The fix is simple enough, I logged in to the EY brs machine ( rdesktop -T 'h1brsey' -g 2048x1280 -x l h1brsey ) and killed the old code (which gave an error, I had to hit cancel a few times, error shown in second image) and restarted from the C# link on the desktop. I think Michael Ross has some updates that will allow automated emails to be sent when this happens, would be nice to set this up here.