Mirko and Den are measuring MC_F, which they will report about later, but I noticed that MC2 is totally crazy right now. It shouldn't matter that they are doing things (like unplugging the feedback to the PSL's PZT), because we actuate on the laser, not on the MC. I disabled the MC autolocker before they started working.
Anyhow, somehow MC2 got kicked up (whatever, that happens), but it won't re-damp. I think it's the WFS. The yaw output from the WFS is truely crazy.
I have disabled the WFS output / ASC input on the MC SUS screens, and MC2 was then able to damp. My disabling only the MC2 WFS input at first kicked up MC1 and 3, so I disabled all of the WFS stuff, and all 3 MC mirrors are again happy.
SURESH: FIX ME! (signed, The WFS)
Turning off the WFS servo loops usually should be done using the 'mcwfsoff' script. The script takes care of switching off the integrators and Clears the History.
'mcdown' and 'mcup' scripts run the 'mcwfsoff' and 'mcwfson' scripts so when the MC unlocks the WFS servos are shutdown and restarted properly. However if the MC autolocker script is suspended by pressing the Enable/Disable switch in the LOCKMC screen and then the MC unlocks, it results in the WFS servo integrators accumulating large values. If these values are passed through the ASC filter banks the optic will get a pretty huge kick.
I have added some indicators which will let us know if the WFS Servo Filter outputs are larger than +/-1000. When engaging the WFS loops the user has to take care to Clear History in the servo filter banks if these indicators are steadily Red. before engaging the WFS Servo loops ensure that the servo filter outputs are zeroes.
Koji and I discussed whether it would be useful to run the 'mcwfsoff' script when the Disable button is pressed in the autolocker. His recommendation is that we should keep the autolocker script simple and that user has to be cautious when switching on the WFS servos and when directing the ASC outputs to the suspensions.