WP13096 Add missing h1lsc ALS DIFF PLL channel to DAQ

Jonathan, Erik, EJ, Dave:

The missing H1:ALS-C_DIFF_PLL_CTRL_OUT_DQ channel was added to the h1lsc model's DAQ Block.

We initially just restarted h1lsc, but this caused a DAC error in h1ioplsc0 (similar to h1ascimc and h1iopasc0) which meant we had to restart all the models on h1lsc0.

A DAQ restart was required.

WP13078 Add pending slow controls and h1sush6 to DAQ

WP13094 Add JAC CAM EPICS and CHETA slow chans to DAQ

Jonathan, Erik, EJ, Dave:

A new H1EDC.ini was created with the following changes:

H1EPICS_DIGVIDEO.ini Regenerated with JAC CAM (cam38) added (+25)

H1EPICS_ECATTCSCS.ini Added CHETA laser pwr chans (+2)

H1EPICS_ECATAUXCS.ini Added C_PZT_SHUTTER chans (+11)

H1EPICS_FEC.ini Added h1sush6 models (+97)

H1EPICS_SDF.ini Added h1sush6 models (+160)

H1EPICS_DAQ.ini Added h1sush6 models (+32)

total +327. Num chans increased from 60582 to 60909.

Erik ran puppet to officially add all the new h1sush6 models to the system (I had done some hand-editing last week). He also determined the DAQ time slot h1sush6 should used.

Jonathan got the DAQ ready for the new front end and models. He also plugged the DAQ ethernet cable into the back of h1sush6 (the Dolphin cable remains unplugged for now).

We rebooted h1sush6 to get the DAQ sending started.

Jonathan then restarted the DAQ, starting with the 0-leg. I restarted the EDC at this time.

A second 0-leg restart was required to complete the configuration.

When this was stable, the 1-leg was restarted with no issues. 

We saw two spontaneous restarts of FW0 around this time, which had been seen before. At time of writing, FW0 has been up for 90 minutes.

FAMIS 28560

pH of PSL chiller water was measured to be between 10.0 and 10.5 according to the color of the test strip.

Tue Mar 17 10:19:48 2026 INFO: Fill completed in 19min 44secs

Gap in plot is due to DAQ restart.

The well pump was remotely activated on Friday 3/13 for approximately 18 minutes beginning at 8:45am PT for the purpose of ground water sampling.

T. Guidry

TITLE: 03/17 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 16mph Gusts, 10mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.29 μm/s 
QUICK SUMMARY:

IFO is in IDLE and ENGINEERING

Plan is to continue comissioning.

AS_B_RF_45 was rephased +90% yesterday and EVE OPS reports that this was not making things better. Thye tried both +-90% phase and reported that -90% worked better.

Workstations updated and rebooted.  This was an os packages update.  Conda packages were not updated.

TITLE: 03/17 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY: I'm not convinced that the +90 phasing was correct for AS_B_RF45, the non-stellar alignment is making it tough to tell. PRMI locked fairly easily althought I can't seem to fix the Pitch misalignment, DRMI isn't so kind. It struggles to lock for more than ~7 seconds at the end of the shift.
LOG:                                                                                                                                                                                                    

• RyanS and I saw MICH ASC seem (it didn't finish offloading and lost lock due to ALS locklosses) to work twice with a +90 phase on AS_B_RF45, later when I was trying alone it clearly took it in the wrong direction every time. I tried a -90 phase as well, which seemed to be working until it eventually pulls in the wrong direction and doesn't stop till it loses lock. The power is low so it doesn't have that much room for error. I tried touching up both PRM and the BS before engaging MICH_ASC with both -/+ 90 phases (and no phase) which did not work. -90 was more successful
• After maximizing PRMI as much as I could I moved on to struggling to lock DRMI, after it would lock I would try to max by hand then it would get unstable and shake sometimes as I was adjusting optics
• DRMI really didn't want to lock, the few times it did it lock for a few seconds it looked OK, a decent amount of pitch, it was also seemed unstable, the BS glitching wasn't helping.
• The alignment isn't great, it's definitely worse than it was on Friday, I haven't been able to touch it up enough
• NUC5 bottom monitor is having trouble connecting/seeing its display, NUC20 is really dim and so are some of NUCs on the left wall

TITLE: 03/17 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 17mph Gusts, 14mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.25 μm/s 
QUICK SUMMARY:

• Testing MICH ASC, so far it seems to be working for PRMI
  • We rephased AS_B_RF45 by +90
• I'm trying to get up to CARM_OFFSET_REDUCTION

TITLE: 03/17 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:

17:13 UTC GRB -Short E630194 H1 was in Idle.  
ITMX was moved to get better X arm light earlier today. Since then we have been able to Lock PRMI.
Sheila and Gabriele went and took some pictures of inside the HAM1 chamber, so keep an eye out for cool HAM1 pic filled alog.   
We can consistantly get PRMI to lock. The Ryans are currently working on getting mich ACS to work.

LOG:                                                                                                                                                                                                                                                                                        

J. Freed

For the build of SPI, I measured the expected power output from a dual source Keysight 33600A through SPI's 2W amp D2500004. These measurements were taken with a E4418A EPM power meter using the HP 8484A 30dB attenuator attachment. After analyzing the data it is hard to say that the power meter power readings were accurate but the power the AOMs are receiving should be below the damage threshold of 33dBm.

I measured the power at 2 points in the chain from Keysight -> 2W  -> SPI prep, for both channels. (SPI_Build_RF_Diagram.png) The first point is just before the 2W amp, and the second point is just before the SPI prep for both channels. Then I compared that with what the output monitor voltage was showing on SPI prep for both channels.

Power_Before_2W_Amp.png Is the data collected from power measurements just before the 2W amplifier. The limit of 22dBm is the limit of the keysight. From this it can be seen that there is not a 1-1 measurement between what the keysight says it is outputting and what the HP 8484A sensor is measuring. This difference is also changing based on the input power itself. With lower power overestimating what the keysight says its outputting, and higher power underestimating what the keysight says its outputting. This is a problem with the probe as switching out the probe to an E-series gives a relatively consistent error of -0.2dB between what the keysight says its outputting and what is being measured. Unfortunately the HP 8484A sensor is the only probe that can measure up to the 32-32.5dBm needed for SPI. Interpolating the results of the HP 8484A sensor up to 32 dBm gives approximately a 0.4dB underestimation of the power.

Then I took a measurement of the power after the 2W amp at the end of the cable that would plug into SPI prep. Namely I adjusted the power from Keysight, such that the output measured on the probe was 32dBm which is what SPI prep is expecting accounting for any possible underestimation of the power. Note that power past the 2W amp decreases over time (by about 0.5dB total) as the device warms up so I had to wait a couple of hours after start-up to take this measurement. The results were:

AMP 1 (Which goes into the ref path) measured 32dBm when the keysight displayed: -1.7dBm

AMP 2 (Which goes into the Meas path) measured 32dBm when the keysight displayed: -0.3dBm

Be aware that that 32dBm has an error of +/- 0.5dB due to the factors listed above. 

Then using the fact above, I found that the whole AMP 1 chain has a gain of 33.7 dBm from what the keysight displays. And AMP 2 chain has a total gain of 32.3dBm from what the keysight displays. Using this fact I could find the voltage associated with each of the monitor channels of SPI prep.

Monitor_read_AMP1_REF.png and Monitor_read_AMP2_MEAS.png show the monitor reading voltage vs the approximate input RF power into SPI prep. for both channels. Interpolating the results gives a calibration equation between RF power and monitor voltage of: 

AMP 1 (REF):  [V] = -0.0249*[dBm] + 1.5480

AMP 2 (MEAS):  [V] = -0.0246*[dBm] + 1.5387

With both channels reaching 32dBm around 0.75V on the monitor channel this gives an easy target for controling the power.

Betsy, Sheila, Jennie W, 

This morning Betsy and I removed the viewport cover on the -Y, -X upper port of HAM1.  We pointed a laser pointer at REFL WFS A and B, and saw similar DC counts on each of them, with WFS A channels responding when I pointed the laser pointer at the +X diode and WFS B responding to the the -X diode.  We were also able to point the laser pointer at LSC REFL B and LSC POP, and both responded.  We can't reach LSC REFL A, but we know that diode is responding.  POP X is not easily accessible this way, although we might be able to reflect off PM1 to hit that diode.  

Jennie W and I went back with the Nikon D810 from Keita's office.  We expirimented with different settings on the camera, and taking photos with illuminators and table lights on and off.  A few photos are attached, you can see IR light on the barrel of the beamsplitter that splits the beam between WFS A and WFS B.  There is also a glint on the mount of the second lens on the sled. 

Upgraded the main slow controls software to add some calibration features for CHETA. 

I've reworked the CDS Overvew MEDM for the HAM6 changes.

The additional corner station SUS models have increased the SUS column's height (first column). To accomodate I've moved the WATCHDOG section over to the second (SEI) column, below the consolidated SUSAUX section.

The DAQ section has been moved to the 3rd column (ISC).

The new h1sush6 front end, highlighted in WHITE, is not currently in the DAQ, hence the grey'ed DAQ status.

Placeholders for the LO12, LO3 and SUSAUXH6 models are highlighted in ORANGE.

I think this overview contains all the additional parts needed for IR1.

Mon Mar 16 10:10:45 2026 INFO: Fill completed in 10min 42secs

[Tom R, Ibrahim]

We glued 6x of the QOSEM flags, attaching the lens (D2500277) to the aluminium body (D2500253). This was done using a jig (D2600054) to ensure the lenses were aligned to the body of the flag. We used EP30.

Only a tiny drop of glue is required, and was applied directly to the lip of the body using a thin wire. The flags will be left to dry overnight before another batch of 6 will be glued.

I did the monthly wind fence inspection yesterday. No new issues. Damage to the one panel at EY seems stable, no damage noted at EX. 

Yesterday, ground loop checks revealed a new and random ground loop issue on the LR BOSEM of the Tip Tilt PM1 suspension (which has been installed and used in vac for a long while now).  This morning I worked to swap the BOSEM for a new one, reset the medm offset/gains and recentered.  Fil confirmed that the ground loop situation is now resolved on PM1.  In Corey's absence, I took a bunch of photos (won't be as good as his but here for posterity) of the chamber components as we see them before closing up.  I wiped down some of the under table surface as I could.  Jim and I both inspected for left behind items on and under the table.
BOSEM SN 263 is the problem OSEM removed, SN 229 was swapped in with OLV 28860.

Jim then removed the septum viewport covers (all 4)and unlocked the ISI.  Oli ran the final closeout TFs for PM1 (JM1 and JM3 were yesterday).  I revisited the closeout check sheet and we launched the door crew (Jordan, Randy, and FAC - thanks for jumping in due to others absences!).  1 door is on now and we are about to check that the JAC Refl beam goes through the viewport on the door as anticipated given the inaccuracy of the viewport simulator fixture.

We installed JM1, balanced it and aligned it. A beam dump was placed behind it though we could not see the transmission with 1W input.

After this, JAC locked with RF without any problem though the input was wobbly when the purge was up.

We searched for unexpected ghost beams (also with 1W input) and didn't find any.

We uninstalled many (but not all) temporary dog clamps and irises.

We revisited the IMC alignment because it's been off in PIT since Thursday or Friday. We locked JAC using dither (because we wanted to turn down the purge air). We enabled the IMC WFS just for MC optics and steered JM3, but weren't able to center the MC2 trans. Steering JM3 just made the IMC transmission worse while making not much impact on the desired degree of freedon (JM3 PIT -> MC2 trans YAW, JAM3 YAW -> MC2 trans PIT).

Tomorrow, we'll revisit the IMC alignment. We'll also measure the power coming into JAC TRANS PD as well as the actual transmission of JAC while locking it with RF so we can use JAC trans PD as the measure of the power into HAM1.