Displaying report 1-1 of 1.
Reports until 20:06, Wednesday 26 June 2019
H1 AOS
corey.gray@LIGO.ORG - posted 20:06, Wednesday 26 June 2019 - last comment - 11:21, Thursday 27 June 2019(50222)
ALSx Issue:

After the storm was passing through, ALS x & y were obviously flashing all over the place.  Unfortunately, within a few minutes the green spot for ALSx disappeared (and we had the error:  "ReflPD A; Green input align").

1)  Looking at ETMx, TMSx, & ITMx

Saw shifts for all of these guys, so I returned them to where they were during the lock, but no change for the spot on video.

2) ENDx Overview:  No spot for Green WFS (& offcenter spots for Green QPDs)

3) PDH Locking screen: 

Attached is a screenshot of the issue.  Since the power is low I'm wondering if this is still an alignment issue & I just need to sweep optics to get something on the camera.  But I don't really know where to start and where to go.  This is something I can try next.

For the GREEN WFS, I'd prefer to not touch picomotors to get a spot on them, but I'm wondering if ETMX/ITMx/TMSx alignment sweeps could help this?

...........Oh Darn........

As I was going through the Troubleshooting wiki, there is mention of:  If one has symptoms as above (i.e. no power for XARM Green ReflA), one should check the shutters.  I just saw that the ISCTEX green shutter was CLOSED.  I opened it and I atleast now see light (ugly light, but light).  Why would this shutter close on me???

OK, now that I'm not blind, going to try and find the spot for Green X-arm!

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 20:16, Wednesday 26 June 2019 (50223)

5 Min Later:   

Ugh.  That did the trick.  Unlocked ALSx & tweaked ETMx & (mostly) TMSx to get flashing from 0.1 up to 1.0.  Now will move on...hopefully an alignment is not needed for the touching I did to the ITMx.

corey.gray@LIGO.ORG - 20:31, Wednesday 26 June 2019 (50224)

PRMI Flashes look like garbage (no flashing at all with PRM tweaks after BS tweaks from CHECK MICH FRINGES).  Going for an alignment.

thomas.shaffer@LIGO.ORG - 11:21, Thursday 27 June 2019 (50244)FRS

The ALSX shutter closing does not seem to be caused by the enabling of the picomotors, as seen with FRS 11354.

It was closed when the ALS_XARM node set H1:SYS-MOTION_X_SHUTTER_A_OPEN => 1 when it was starting to lock. I'm not sure why asking it to open actually closed it. Filed FRS 13154

 

2019-06-27_01:26:00.954991Z ALS_XARM executing state: LOCKING (-20)
2019-06-27_01:26:00.960283Z ALS_XARM [LOCKING.main] ezca: H1:SYS-MOTION_X_SHUTTER_A_OPEN => 1
2019-06-27_01:26:00.962242Z ALS_XARM [LOCKING.main] ezca: H1:ALS-C_LOCK_REQUESTX => End Locked
2019-06-27_01:26:00.963586Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_SWITCH => OFF
2019-06-27_01:26:00.964060Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_DOF_1_P_RSET => 2
2019-06-27_01:26:00.964461Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_DOF_2_P_RSET => 2
2019-06-27_01:26:00.964862Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_DOF_3_P_RSET => 2
2019-06-27_01:26:00.965275Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_DOF_1_Y_RSET => 2
2019-06-27_01:26:00.965644Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_DOF_2_Y_RSET => 2
2019-06-27_01:26:00.966066Z ALS_XARM [LOCKING.main] ezca: H1:ALS-X_WFS_DOF_3_Y_RSET => 2

(Changed tag to CDS, FRS)

Images attached to this comment
Displaying report 1-1 of 1.