Was logged on checking health from the earlier invasive work. Everything was working fine so I closed (pushed X) on the remote desktop shell. The BRS output went to never never land and the ISI tripped. This of course did nothing useful for the the IFO or Observation mode.
When I logged back onto the BRSY, it was still running but giving some errors and the output was still very rung up. I am not sure which was causing which though. Following the BRS2 Manual (T1600103), restarted the TwinCat code, killed the old occurance and restarted the C#, and finally the EPICS. Exited the session the same way and this time it survived. Yikes!
The amplitude is still a bit large with the camera image swinging into the reference image on the edge. When that stays off the edge during its cycle, the BRS will be useful again.
The BRSY is now damping itself down and is no longer swinging out of range. But it is still getting itself under control. It is coming down quickly but may be some time. Operators should feel free to contact me if they aren't sure if it can be returned to service.
It is strongly advised to not login to the BRS machines when they are being used. This is because the spike in CPU-use disrupts the autocollimator fitting routine. This causes ~seconds long delays in the tilt output which affects the tilt-subtraction and so on.