Reports until 14:42, Tuesday 09 August 2016
H1 ISC (ISC)
jenne.driggers@LIGO.ORG - posted 14:42, Tuesday 09 August 2016 - last comment - 19:41, Tuesday 09 August 2016(28958)
Fast shutter

[Stefan, Jenne]

We have been looking at different PD signals to see if we can set up a guardian check that the fast shutter indeed closes upon lockloss.  Right now we don't have a good way to code it in guardian yet, so Stefan has made a template for the lockloss script that we can run every lockloss. 

Note that AS_C and ASAIR_B are both before the shutter, so should not see a change in light upon shutter close.  AS_A, AS_B, and OMC_DCPD are all after the shutter, and should lose light if the shutter successfully closes. 

For now, we have some DTT snapshots.  NDS2 is under maintenence, so not all plots have the same traces, sorry.

Once NDS2 is back online, we'll post a few more plots of a few more locklosses, with both ASAIR and OMC DCPD included. 

Also, we don't want to use signals such as the OMC input pointing QPDs that are whitened for this fast information. 

Images attached to this report
Comments related to this report
jenne.driggers@LIGO.ORG - 16:16, Tuesday 09 August 2016 (28962)

NDS is back.  Here are several plots, one where the shutter failed, and 5 where it worked.  We see that this "bounce" is very repeatable. 

The problem is that the big pulse of power can come before, during or after the bounce, so it is possible that we still send high power light to the AS WFS and the OMC unintentionally.  As long as the PZT shutter has worked, the DCPDs will be protected, but the black glass dumps and AS WFS will not be.  See in particular the 28July 20:19utc plot for an example when the big pulse comes just after the fast shutter originally closes.

Rich saw this bounce behavior when testing the fast shutters (see T1400335 starting at page 8), so this is a known issue, but we need to fix it. 

Images attached to this comment
jenne.driggers@LIGO.ORG - 17:10, Tuesday 09 August 2016 (28966)

Optical way of looking every acquisition whether the shutter is moving:

The fast shutter is kept closed through DRMI lock, and only opened when we're ready to start using the AS WFS in the DHARD_WFS state.  So, we can look to see that there is some power at the ASAIR PDs, or also the AS_C diode.  Initially, there should be no light on the AS WFS or going to the OMC. However, after the shutter is requested to be opened, we should suddenly see signal on those diodes. 

Attached are 2 instances of this behavior, so it shouldn't be too hard to write a guardian check to ensure that the fast shutter is moving during every lock acquisition sequence.  If instead we see light on the AS WFS as soon as DRMI is locked, and there isn't a sudden change when the shutter is requested open, then we should get warnings so that we know the shutter is perhaps stuck open.

Images attached to this comment
peter.fritschel@LIGO.ORG - 19:41, Tuesday 09 August 2016 (28974)

Hopefully the new shutter installation will solve the problem that Jenne mentions where the shutter let light pass for about 20 msec after the original closing. We believe that the previous shutter was too low (9 mm between the beam and the top of the shutter mirror), so that the downward 'bounce' of the shutter was enough to let the beam by. The shutter is now 3 mm higher than it was, so hopefully it will continue blocking the beam even during the downward part of the shuttering cycle.