(Corey, Elenna [remote], Tony)

Recent Backstory Alogs:  

• JUN 1st:  (Corey, Craig, Georgia) HAM6 HV PZT Kepco Power Supply was stuck in the Constant Current ("CC") state (alog84698)
• JUN 13th:  (Keita, RyanC) Output Voltage was 0V and it was also in the Constant Current ("CC") state (alog85030)

Today, while locking H1 noticed that we were stuck in PREP_DC_READOUT_TRANSITION.  DIAG_MAIN was mentioning an OMC issue.  OMC_LOCK guardian was in a loop of trying to sweep the PZT to FIND_CARRIER, but Elenna noticed that the PZT was not sweeping.  Then she remmebered the previous issues!  

(I was on the wrong trail, because I had assumed the SR3 change I made somehow was the cause of the issue---it was NOT.)

• Went out to the CER and went upstairs to the rack which has the HAM6 HV OMC PZT power supply....
• It was OFF!  (see 1st photo) The rocker switch was in the OFF state.  (This is different from both cases noted above from last month.)
• Read up on Craig's and Keita's alogs
• Turned the Power Supply ON
• But had 0.0V and 0.0mA + it also was stuck in the CC state (didn't take a photo, but basically it looked like THIS from Keita's alog)
• Checked the "V SET" and saw that it was 0 V, so took this to 110V (which is also noted on the sticker on the front of the Power Supply).  Went to "I SET" and saw that it was 0.0 mA, and did not change this value.
• Still had the Constant Current .
• Eventually did another Power Cycle via the front rocker switch and this time the Power Supply came up in the Constant Voltage ("CV")--which we wanted.  (Is there an easier way to transition to this state?  I went through the MENU and did not find anything.
• WE BACK!:  At this point, we had:  CV, 110V, and a non-zero Current.  (see 2nd photo for photo of the power supply display)
• Elenna took the OMC_LOCK guardian from MANAGED  --to--> AUTO, and started moving the PZT2 in 1.0 count steps.  She saw this working on her medm and I saw the Current changing on the front display of the Power Supply.
• At this point, we were back in business and returned to the Control Room.
• ISC_LOCK was continuing on (because the OMC had locked).

We still had the OMC_LOCK in a non-ISC_LOCK-managed AUTO state and we were not totally sure of how to have ISC_LOCK remanage OMC_LOCK.  Tony found a 2015 alog from Patrick which we used to get OMC_LOCK managed again.  H1 continued on and has been in OBSERVING.