Displaying report 1-1 of 1.
Reports until 07:27, Friday 23 June 2023
H1 PSL (ISC, PSL)
corey.gray@LIGO.ORG - posted 07:27, Friday 23 June 2023 - last comment - 10:06, Friday 23 June 2023(70754)
Increased ISS Diffracted Power, Updated ISS Second Loop Offset & Back To OBSERVING

As posted earlier, there were issues getting through the LASER NOISE SUPPRESSION step.  Luckily, Evan saw my posts on ligo.chat and gave me suggestions for stuff to check from status descriptions I posted.  In addition to the note earlier, we had various messages:

From this Evan pointed me to ISS 2nd Loop Offset alogs:

  1. Alog 66309
  2. Alog 58264 Used procedure Jenne wrote up in here to increase diffracted power to 2.5% (via REFSIGNAL) & then adjusted 2nd Loop AC Coupling Offset such that toggling the 2nd Loop would not cause a transient (see scopes for the changes & then zoomed-in shot of transient test by increasing PSL power to 10W---similar to scope Jenne posted).

Luckily, with the above changes, for the next lock attempt, LASER NOISE SUPPRESSION was not an issue.

Once at NOMINAL LOW NOISE, it took the Camera Servo about 22min before we could go to OBSERVING.

And after looking at the range forthe last hour, it appears to be lower than what we had for the last lock, so perhaps my changes were not optimal and could be improved.

Images attached to this report
Comments related to this report
corey.gray@LIGO.ORG - 07:34, Friday 23 June 2023 (70755)

Not sure if I turned "OFF" the 2nd Loop the correct way.  On the 2nd Loop Screen, I would toggle the 2nd Loop via H1:PSL-ISS_SECONDLOOP_CLOSED (on right of screen), but I'm thinking I should have been toggling H1:PSL-ISS_SECONDLOOP_ENABLE (middle of 2nd loop screen) instead.

ryan.short@LIGO.ORG - 10:06, Friday 23 June 2023 (70761)OpsInfo

Noting here for future reference... (and tagging OpsInfo)

The "cleanest" way we have to engage/disengage the secondloop is with the IMC_LOCK guardian. In the LOCKED state, the IMC is locked and the secondloop is OFF. When the ISS_ON state is requested, the guardian moves to CLOSE_ISS (which actually does the process of engaging the secondloop), and then to ISS_ON, where the secondloop is considered to be ON. The secondloop can be turned off again by requesting the LOCKED state, where the guardian will move through OPEN_ISS.

Displaying report 1-1 of 1.