WP 11350
E1500260 - Vacuum Controls Chassis LX
E1700026 - VCMS Drawings for Hanford, VEAX

The interlock bypass to enable/disable the cryopump level controls for CP2 has been removed. Relay inside the vacuum slow controls chassis was verified to be operational (EL2624, terminal 5, CH2). Signal traced from slow controls chassis to the FLKM terminal block J, pins 3&4. The controsl were enabled/disabled and readback signal on MEDM screen verified 24V being sent to CP2.

F. Clara, G. Moreno

Per the checklist T1500386, I made a walk thru of the LVEA.

WP 11349
D1400363

A CPS timing cable was pulled from the CPS Fanout Chassis (Rack SUS-R4) to HAM7. Wiring diagram D1400363 calls for a standard male to male DB9, twisted pair, shielded cable. Used the existing HAM5 timing cable to verify pinout. When backshell was removed on the fanout chassis side, noticed resistors soldered across pins 1&6 and pins 2&7. Bill of materials calls out for 100 ohm resistors. Cabling for HAM5/HAM7 was not changed. New cable will be properly terminated next week.

Julianna Lewis, TonyS, RickS

This morning we moved the upper (inner) Pcal beam at X-end down by 5 mm at the entrance aperture of the Pcal Rx sensor to test the impact on the calibration of the Pcal system at X-end.

We expect that the impact on the calibration of the Xend Pcal will be given by the dot product of the 

The work proceedes as follows:

• Disabled all excitations for the Xend Pcal system. Rx PD output ~0.443 W. (GPS time 1375545485)
• Blocked the lower (outer) beam in the transmitter module. Rx output ~0.2206 W.  (GPS time 137554600)
• Assessed the position of the upper Pcal beam at the entrance aperture of the Rx integrating sphere.  It appeared to be well centered (see first attached photo).
• Installed a target at the entrance aperture of the Rx sensor and adjusted the roll angle so that the rows of holes in the target were aligned with the vertical and horizontal directions (see third and second attached photos.).
• Increased the Pcal AOM offset in the OFS servo from 3.33 to 5.0. (GPS time 1375547403)
• Adjusted the beam position at the Rx sensor aperture (and on the ETM) using the last steering mirror in the Tx module to optimize the sensor output voltage (and thus center the beam at the center of the Rx sensor aperture). (GPS time 1375547610)
  • The Rx sensor output level increased to about 0.301 W from about 0.295 W by tweaking the aligment. (see fourth attached photo)
• We initially moved the Pcal beam up by 5 mm, but became concerned that we might be getting close to the edge of the coating on the output vacuum window because the transmitted light level was significantly lower (few percent).
• We moved the beam down to the lower hole in the target and aligned it to optimize the transmitted level at about 0.300 W (GPS time 137549300) (see fifth attached photo).
• Removed the target from the Rx sensor.  Rx sensor level 0.33 W. With OFS offset at 5.0.  (GPS time 1375549520)
• Reduced the OFS offset to 3.33 from 5.0.  Rx sensor level 0.221 W.  (GPS time 1375549950)
• Removed block from lower (outer) beam in the Tx module.  Rx sensor level 0.4438 W. (GPS time 1375551330) (See last attached photo)

We expect that this upper beam movement will change the unintended rotation of the test mass and change the calibration of the Rx output by about 0.2 % This assumes that we have moved at roughly 45 deg. with respect to the roughly 22 mm interferometer beam offset and that the offset on the surface of the ETM is roughly half of that seen at the Rx module: - 2.5 mm / 2 x 22 mm x 0.707 x 0.94 hop / mm^2 = -18 hop (hundreths of one percent).  So we expect to see that X/Y comparison factor will change from about 1.000 to 0.9982.

WP11359 Consolidated power control IOC software

Erik:

Erik installed new IOC code for the control of Pulizzi and Tripplite network controlled power switches. No DAQ restart was needed.

WP11358 Add new end station Tripplite EPICS channels to the DAQ

Dave:

I modified H1EPICS_CDSACPWR.ini to add the new end station Tripplite control boxes. I found that this file was very much out of date, and only had the MSR Pulizzi channels. I added the missing seven units to the file. DAQ + EDC restart was needed.

WP11357 Add missing ZM4,5 SUSAUX channels to DAQ

Jeff, Rahul, Fil, Marc, Dave:

Jeff discovered that the FM4,5  M1 VOLTMON channels were missing from the SUSAUX model. In this case these are being read by h1susauxh56. It was found that the existing ZM6 channels were actually reading ZM5's channels. h1susauxh56.mdl was modified to:

Change the ADC channels being read by ZM6 from 20-23 to 24-27

Add ZM4 reading ADC channels 16-19

Add ZM5 reading ADC channels 20-23

DAQ Restart was needed.

DAQ Restart

Dave:

Another messy DAQ restart. The sequence was:

1. Restart the 1-leg
2. Restart the EDC to include the power control channels
3. gds1 needed a second restart
4. When fw1 was back up and had written its first full frame:
5. Restart the 0-leg
6. gds0 needed a second restart
7. After fw0 had written its first full frame, fw1 spontaneously crashed!

This was an interesting data point, last week I restarted the DAQ in the opposite order of 0-leg then 1-leg, and as fw1 was coming back fw0 spontaneously crashed, which in that case resulted in some full frame files not being written by either fw.

Could it be that starting the second fw impacts the first fw's disk access speed (perhaps LDAS gap checker switching between file systems)?

As we have found to be always the case, once the errant fw has crashed once, it does not crash again.

Naoki, Sheila

There is beckhoff code to check that a pll is locking on the correct side of the PSL, which can be used or skipped by selecting H1:SQZ-FIBR_LOCK_LOGIC_SKIPINITIALIZATION.  The TTFSS was not locking because the laser frequency was far off today, so I switched this to skip, and reset the frequency, and the TTFSS is locked.  I accepted in SDF skipping this initialization.

Dave, Rahul

This morning we made changes to h1susauxh56 model and added the missing ZM4, ZM5 M1 VOLTMON readback and corrected it for ZM6 - I am attaching a screenshot of the latest model which was successfully installed and restarted. This was an oversight from O4 installation of the HXDS and was discovered by Jeff (while he was going through O5 SUS electronics layout). The details of the wiring diagram is shown in D2000202_v12 for ZM4, ZM5 (see page6, look at ADC5) and D1002740_V10 (page6, ADC5). The details of the new ADC channels (added 8 new fast channels) for each suspension on h1susauxh56 model is given below,

ZM4 ADC5 CH16-CH19 
ZM5 ADC5 CH20-CH23
ZM6 ADC5 CH24-CH27 (changed from CH21-CH24) 

h1susauxh56.mdl has been committed on the SVN (located at cd /opt/rtcds/userapps/release/sus/h1/models) and Dave has successfully performed a DAQ restart.

The VOLTMON for ZM4 and ZM5 were showing zero reading, which meant we had to switch ON the filters and apply a Gain a 1.0 to all four quadrants for both the suspensions. The filters were located at

cd /opt/rtcds/lho/h1/medm/h1susauxh56

and using the Command "medm -x H1SUSAUXH56_ZM4_M1_VOLTMON_LL.adl" we switched ON the filters and applied the Gain.

I am attaching a screenshot of ZM4 and ZM5 and the VOLTMON readouts on both the suspensions are fully functional.

WP 11357 is now complete and I am closing it.

FAMIS tasks 24866 and 24842

Procedure checklist for both stations completed.  No issues were identified at this time.

MX: Scroll pump hours: 203.0

       Crash bearings: 100%

EX: Scroll pump hours: 6309.5

       Crash bearings: 100%

TonyS, RickS

To recover the Pcal's ladder and another ladder, we took down Robert's setup that was used to test damping of the manifold section near the manifold cryo-baffle (see photo).  The components: lab jacks, long aluminum bars, and damping material were left on the VEA floor near the termination slab.

We discussed this setup with RoberS a few weeks ago and he indicated that we could disassemble it if necessary to recover the ladders used in the improvised setup.

Tue Aug 08 10:13:34 2023 INFO: Fill completed in 13min 30secs

Gerardo confirmed a good fill curbside

TITLE: 08/08 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 5mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY:

IFO Status: Unlocked for the past hour and a half.
I have a message from Corey in the Reservation System that says the ALS_X is in FAULT state.

H1 went down at 1327utc (627amPT), and it definitely had ALSX issues---ALS_XARM guardian node was in a FAULT state.

The camera flashes & ALS x Transmitted channel looked noisy.

Tried a few items on the PLL / ALS_CUST_LASER_LOCKING.adl screen, but none made any changes for the better.  What I tried:

• taking beatnote RF min from -10 to -15 (and other values)
• took crystal frequency to -200 (and other values)
• Toggle the Force & No Force buttons for the autolocker

Due to automation, I also was also fighting an INITIAL ALIGNMENT at some point.  Taking H1 to DOWN for the morning crew.

Workstations were updated and rebooted.  The updated included OS packages and some Conda packages.  The conda updates include the following:

Ndscope -> version 0.18.0

• Fixes issue where data was shown at the wrong time
• New feature to set Alpha for grid-lines
• New feature to set plot title and labels for channels

cdsutils -> version 1.6.1, minor fixes

python-ezca -> version 1.5.0

• when EZCA_CA=NOFAIL, ignore missing switches when trying to switch filters

Looks like this was a quick and local earthquake:  M4.0 between Snoqualmie Pass & Seattle.  You can also see it on Seismic FOMs and the Picket Fence.

H1 already past DRMI locking.