Reports until 06:09, Monday 03 November 2025
H1 General
oli.patane@LIGO.ORG - posted 06:09, Monday 03 November 2025 - last comment - 06:50, Monday 03 November 2025(87915)
Ops OWL Intervention: Fast Shutter Issues

Got called by H1 Manager due to the fast shutter check during CHECK_AS_SHUTTERS failing. I've been looking at the trigger power and various SYS-PROTECTION channels (medm, ndscope), and it looks like to me that the fast shutter test failed only because we lost lock right as it was checking?? You can see the trigger power oscillating along with DRMI as DRMI is right about to fail. However, It does look like the fast shutter did not fire for this test.

So it looked like just a bad coincidence to me, BUT when I went to try opening the shutter manually via the shutter controller, it wouldn't open. I ended up using the FORCE OPEN button, which did work, and after that I was ableto open and close it fine normally.

Looking back further it looks like it doesn't close&open it every time?Looking back on ndscope, it looks like the few times we got up to CHECK_AS_SHUTTERS from the past day, during that state, the fast shutter did not close/open for the test(I thought it was supposed to get opened and closed every relock during CHECK_AS_SHUTTERS??). At 11/02 14:59 UTC it had functioned correctly, but then at the next CHECK_AS_SHUTTERS, it didn't.

I wanted to go just to CHECK_AS_SHUTTERS to see if I could confirm that maybe the failure was just coincidental and based on a lockloss during the test, so I got up to CHECK_AS_SHUTTERS, and it did run the test by itself, but as it closed, it caused a lockloss(ndscope). After this test though, all of the issues on the AS_PORT_PROTECTION screen had cleared, so I went up again. I did accidentally leave the FAST_SHUTTER guardian in SHUTTER_FAILURE though(last time it got reset by my INITing), so that probably affected the next test that I tried on the next CHECK_AS_SHUTTERS. When we got there, it didn't run the test. I realilzed the FAST_SHUTTER guardian was in the wrong state and corrected it, but the test still didn't run, but the ISC_LOCK state marked itself as finished. I manually ran the test from the AS PORT PROTECTION screen, and it caused a lockloss. The test failed and the AS PORT PROTECTION screen is back to having lots of red, with the fault this time saying 'NotReopening'.

Now that it's after 6am Pacific, I'll call Fil or Marc because it definitely seems like something is wrong with the fast shutter, but I'm still a bit confused as to what it is.

P.S. MC2 watchdog just tripped while trying to relock the IMC, but it's okay now

Images attached to this report
Comments related to this report
oli.patane@LIGO.ORG - 06:50, Monday 03 November 2025 (87916)

Jenne, Fil, Oli

I INITed ISC_LOCK and decided to try CHECK_AS_SHUTTERS a third time. This time, everything worked correctly (fast shutter closed&opened) and the test passed (ndscope). I checked with Fil, who said it might have just been a logic mix-up, and Jenne, who confirmed that we should be good to power up now that the test passed. We are heading up!

Images attached to this comment