[Sheila, Eric, Jim, Kar Meng, Daniel D.]
When we started working this morning, the particle counts were 20/10/10 per cubic foot
It looked like the old cable for the PZT that needs to be replaced was routed to back into the chamber to a cable bracket which was far from reach. Before we can remove it, we need to find the cable harness plan for HAM7.
In the mean time, we were able to re-route the TEC cable using photos from this alog.
### Broke for lunch ###
Over lunch, we determined the correct connector for the PZT/translation stage was on CB5 in HAM7. It's labeled cable #4 according to the wiring diagram. We also verified the correct operation of the TEC controller and the oven from CDS
After we returned, the particle counts were 0/0/0 per cubic foot and we uncovered the chamber to finish replacing the cables.
Unfortunately, cable #4 between CB5 (see image) and the OPO is terminated in a male molded connector, which is screwed into the connector bracket. This meant that we needed to remove the female cable (from the flange) from the rear of the connector and then remove the male connector (to OPO) from the cable bracket. Jim came in to help us reach the connector and he decided that it would be easier to remove the top and second-from-top connectors (3rd and 4th on CB5 in the wiring plan) from the bracket to make it easier to reach the ones for cable #4. Jim was able to remove the old cable and replace it with the new one in the bracket.
After Jim left, we were able to continue reinstalling the new cable. The longest DB-9 tentacle on the new cable is for the VOPO PZTs, the DB-15 is for the stage control, and the short DB-9 is a spare which was coiled to the side. We were then able to connect the piezo and stage control connectors to the OPO and roughly re-route the cabling on the ISI table. Final routing and securing of these new cables/checking for mistakes is still required.
A 5 dB attenuator was added at the input of the RF doubler for the JAC 43 MHz generation. This brought the input level to a nominal 10 dBm.
Checked the 43MHz RF distribution from the CER to ISC-R2 and the WFS demodulators. The demod for the length sensor is shared with the IMC demod. All slow comtrols readbacks are now working.
Added the cabling for the new whitening concentrators. This also required a software upgrade.
The following QPD whitening channels were affected:
Instead of 4 x 8-bits, only 1 x 8 bits are used and all 4 segments are switched simulatanously. There is no change in the whitening interface for these QPDs, since the software already tied the segments together. The only change is in the readnback bits where only the last 8-bits are still significant.
This allowed us to add the whitening for the JAC WFS as well as dewhitening for the JAC PZT driver.
F. Clara, J. Figueroa, J. Kissel, M. Pirello ECR E2400409 and E2500296 (IIET 35739 and 35706, respectively) WP 12901 DWG D0902810-v12 DCN E2500341 Today we've gone forward with merging the sush2a and sush2b IO chassis, facilitated by upgrading those SUS's DAC cards to 32 CH, 28- bit DACs (D2200368). This entry covers the analog electronics and cabling that were impacted by the change, covering that all of the suspensions in, or soon to be in HAM1 and HAM2 -- MC1, MC3, PRM, PR3, IM1, IM2, IM3, IM4, RM1, RM2, PM1, JM1, and JM3. We followed changes outlined in E2500341 which highlights the changes in the sush12 SUS electronics system drawing from D0902810-v11 to D0902810-v12. That required - disconnecting all affected AI output cables in SUS-C3 and SUS-C4, - Removing the existing 6x 2x 8CH DAC AI chassis (D1000305), - modifying them to become D2500353 1x 32CH AI chassis . replacing the 2x 8CH AI rear panel with WD relays (D1000551) with 1x 32CH AI rear panel without WD relays (D2500097) . replacing the 2x 8CH back panel (https://dcc.ligo.org/LIGO-D1000552 with 1x 32CH back panel (D2400308) - re-installing, then - cabling everything up according to the D0902810-v12 version of the wiring diagram. Here's the list of modified AI chassis serial numbers and assignment: D1000305 > D2500353 D2500097 SUS Chain Rack / Position Chassis S/N Rear Board S/N 32CH DAC Card / IO Slot Channels (Counting from 0) MC1, MC3, PRM TOPs SUS-C4 / U30 S1104370 S2501311 DAC0 / #2 0-15 PRM, PR3 TOPs MC1 MID BOT SUS-C4 / U29 S1104374 S2501315 DAC0 / #2 16-31 MC3, PRM MID/BOT SUS-C4 / U22 S1104375 S2501310 DAC1 / #4 0-15 PR3 MID/BOT, RM1, RM2 SUS-C4 / U21 S1104378 S2501312 DAC1 / #4 16-31 IM1, IM2, IM3, IM4 SUS-C4 / U10 S1104377 S2501314 DAC2 / #5 0-15 PM1, JM1, and JM3 SUS-C4 / U2 S1102760** S2501313 DAC2 / #5 16-31 ** Technically, the (now) PM1, JM1, and JM3 AI chassis S1102760 was a 16-bit DAC AI chassis (D1101521) instead of a D1000305 at the start of today, and it didn't *need* the additional 16CH pass-through SCSI connection, but in the spirit of making everything the same, we elected to make it a full "new normal" D2500353 chassis.
Pictures of the now-D2500353 AI chassis rear boards and their connections. They're attached in the order of rear board serial numbers; the corresponding chassis number is listed above.
Updated H1-SUSH12 Timing FPGA code to latest firmware version 1589 V5
Updated H1-SUSH2AUX timing FPGA code to latest firmware version 1589 V5
Rebooted both chassis and they are now reporting correctly according to Dave.
For reference: The 16-chn/16-bit AI chassis with interface boards D070101 are not compatible with the new 32-chn DACs. Both have a 68-pin SCSI connector but the pinout isn't compatible.
While I was checking the suspensions this morning I noticed that the OPO sus guardian was in SAFE but there was still output going to the suspension. Trending the channels it looks like SDF revert was reverting the channels that the node had set in its SAFE state. I unmonitored these channels, see attached.
It looks like all other suspensions on this model are in a similar situation, but I'll wait to do those when the SQZ team isn't actively working in HAM7
Because CDS got an early start on SUSH12 work, we had to bypass the IOP wd to reisolate HAM1 HEPI to lock. Otherwise this went as normal. Angular deviations are all still <5 urad, location deviations are all slightly larger, still below 10um though.
Jennie W
I made a mistake in naming the block for the JAC LSC PD. It should be "REFL_A" and instead I named it "RF43" since there is also a RF43 block inside the "REFL_A block", this made the channel names "H1:JAC-REFL_A_RF43_RF43" which is unwieldy. Fixed it in the h1lsc model, built it on the h1build computer and not its committed to the svn at userapps/lsc/h1/models/
The RFPD block is shown in this picture with its new name. and the contents of this block is shown here.
J. Kissel After offloading the IMC WFS (LHO:88510), and saving alignment offsets in respective safe.snaps (LHO:88511 and LHO:88512), I've brought all SUS on the h1sush2a and hsush2b computers to SAFE (that's MC1, MC3, PRM, PR3 and IM1, IM2, IM3, IM4, RM1, RM2, PM1, respectively). I've also brought the HAM1 and HAM2 SEI systems to ISI_DAMPED_HEPI_OFFLINE. This is all in prep for the h1sush2a and h1sush2b merge into h1sush12, which is coincident with the DACs in these chassis getting upgraded to 32 CH 28-bit DACs per ECRs E2400409 and E2500296 scheduled via WP 12901.
J. Kissel
Saved opticalign alignment sliders for SUS on the h1sush2b computer in the h1susim and h1sushtts models;
h1susim
H1SUSIM1
H1SUSIM1
H1SUSIM1
H1SUSIM1
h1sushtts (which will become h1susham1)
H1SUSRM1
H1SUSRM2
H1SUSPM1
Ready for the h1sush2a + h1sush2b = h1sush12 IO chassis merge!
J. Kissel Saved opticalign alignment sliders in H1SUSMC1, MC3, PRM, and PR3 models. In particular, after I offloaded the IMC WFS (see LHO:88510).
J. Kissel In prep for for the sush12 upgrade, I've offloaded the IMC WFS to the MC1, MC2, and MC3 OPTICALIGN sliders. This was done with the built in "MCWFS_OFFLOADED" state in the IMC_LOCK guardian. There wasn't too much alignment change requested by the WFS's control signal; just ~5 counts on MC1 and MC3. I'll now save the alignment offsets into the SUS safe.snaps.
TITLE: 12/15 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: MAINTENANCE
Wind: 25mph Gusts, 19mph 3min avg
Primary useism: 0.05 μm/s
Secondary useism: 0.44 μm/s
QUICK SUMMARY: Gate valves 5 & 7 closed, plan is to vent the CS and start the SUS CDS upgrade. Vent meeting at 830 in the control room today to coordinate.
Noting the current state of the select systems:
Full into Vent Mode now, here is the current plan for the next few days.
Sun Dec 14 10:06:15 2025 INFO: Fill completed in 6min 11secs
Sat Dec 13 10:01:33 2025 INFO: Fill completed in 1min 32secs
Quick fill, has been burping LN2 over past day.
[Keita, Daniel, Karmeng]
Particle counter acting up (black screen when we move the stand, and high particle count for the first three measurement). Picture for comparison with hand held counter.
We remove all three cables connected to the old OPO, the PZT cable is wrapped with a foil as a marker.
The old OPO is removed, wrapped and kept in the bag used to store the new OPO. New OPO is placed in the chamber, but not bolted on.
The trick to disconnecting the OPO cables was to install one flat dog on the front-right side of the OPO base, then remove the flat dog we had placed on the rear-left side of the OPO assembly earlier this week. This allowed us to slide the OPO back a bit and angle it up slightly so that the connectors were accesible and could be removed. Keita was able to hold the OPO in this position with one hand and loosen the jacking screws with the other (we thought this would be safer than trying to hold the OPO vertically above the VIP). We have a photo of this that Kar Meng may post later.
I first tried to undo the screws for the PZT cable connector on the OPO without lifting the OPO, but managed to hit the SFI1 (the one close to the -Y door) with a steel allen key twice. The wrench is tiny but we didn't want to repeat it many times.
Initially the OPO posotion was VERY tightly constrained in all directions (like within 0.5mm range). In addition to the dog clamps installed as the position reference that restricted the motion in -X and +Y direction, there was no room to move in +X and -Y (end not much in +Z) either because the metal ferrule thing at the back of the PZT connector hit the SFI1. Lifting OPO means that the PZT cable will be badly kinked. That's why we changed the position references of the OPO from (one left, one back) to (one left, two front).
After that, I was able to push OPO in +Y direction and lift the entire thing (with the cables still attached). I thought about the second person undoing connectors while I'm holding the OPO mid-air, but Daniel came up with the idea that I will only lift the front edge of the OPO to tilt it just enough so the cable connectors and the allen key stay safely above the SFI1. I didn't have to bear the load of the OPO while undoing the connectors, it was much safer than my alternative.