J. Kissel Upon carefully reviewing the results of the BnK hammering (LHO:90493) of the SPI Pathfinder's HAM2 ISIJ Reflector's Shroud (D2500030 on the assembly D240010-v6) I've decided to remove the ISIJ shroud from the assembly for now. (Honestly, I made the decision to remove it right after hearing it; LHO:90544, but my desicion was supported by the BnK results). Here's why: - The resonances are high-Q and below the required 150 Hz. Thus, if left as is, its frequency response would likely impact the force-to-displacement transfer function of the ISI, and limit the band-width of the ISI feedback control loops. - The argument the SPI team came up with for this shroud serving any "prevent scattered light into / from the SPI" purpose is weak, given that the very small solid-angle of possible reflection of 1064 [nm] light into/out the SPI system or the main IFO system (we guess that the tube would need to be ~meters long; but we haven't done any quantitative calculation). - The SLIC team has already looked at the HAM2 and HAM3 system enough to decide that carving out some portion of a circle on the existing, middle ISI table panel above the ISIJ reflector works for them. Similarly on the other end in HAM3 over the ISIK transceiver, the panel collection is enough. I hope they've done a what quantitative estimate they can; it's likely way more that the SPI team was capable of. - The arguments for this should as an "in-chamber work" protection mechanism is weak: Rarely (as in once every 5-to-10 years) do any humans find themselves *in* the mode-cleaner beam tube, +X of the HAM2 ISI, and it's with great intent. In addition, the ISIJ reflector assembly doesn't protrude that much that one's appendage would "get caught" on it. Finally, even if contacted, it's a very robust assembly. You'd need to soccer-punt it to move anything, and it's more likely you'd destroy your foot/shin than even cause an alignment shift in the components. - At least upon first attempt at path-finding, we want to minimize any use of damping material like viton to prevent any unwanted drift. But even if we damped the resonance, there would still remain a resonance, just lower Q, thus it might still be bad for the HAM2 ISI loops. Eventually, we want to re-design this shroud to, say, add an end-cap. And eventually we can easily can hose-clamp a bit of viton like we've done for the, say, the ISI's GS13 vacuum cans. We'll do that ... next time, if at all.
The EndX BRS was stuck in a damping loop (I'm assuming caused by the power outage). Usually when this happens increasing the damping thresholds temperately fixes the issue, so we went ahead and did that. It seems to only be effecting the ETMX BRS, so we left the ETMY one alone Jim and I increased the damping thresholds from: H1:ISI-GND_BRS_ETMX_HIGHTHRESHOLD: 2000-->4000 H1:ISI-GND_BRS_ETMX_LOWTHRESHOLD: 800-->2000 It also looks like the ETMX BRS drifted out of range (maybe due to the heater losing power and not returning to the original level?) so I've increased the voltage going to the heating plates and will check back in tomorrow to see if it's been restored
ETMX BRS has returned to normal, I am going to increase to drift control voltage slightly (2-->3) to hopefully get it more in range (currently 1.5e4 counts) and change the thresholds back H1:ISI-GND_BRS_ETMX_HIGHTHRESHOLD: 4000-->2000 H1:ISI-GND_BRS_ETMX_LOWTHRESHOLD: 2000-->800
J. Kissel
In prep for the eminent install and alignment of the SPI pathfinder, I've added and turned on calibration to convert all PD signals (which come off the ADC as [ADC counts]) into ADC input voltage, like we've been using on the o-scopes in the optics lab.
The "filter," really just a gain is
Module Name Design String Units
FM1 cts2V gain(0.0061035) [(ADC V) / (ADC ct)]
as the ADC has a 40 [V_pp] (differential) range, spread over 2^16 [ADC ct], hence 40 / 2^16 = 0.00061035156, which I've rounded to 4 significant digits as is typical (see T1100538).
This FM1 module has been copied and loaded into every relevant PD input filter bank, the module is turned ON, and the gain of the bank has been set to +1.0 such that the output of the bank is calibrated. Those calibrated channels (in the order they appear off of the ADC; LHO:89775) are:
IFO REF A :: H1:SPI-H23_IFO_REF_A_DEMOD_SIG_OUT_DQ :: 2^15 (32768, or "32k")
IFO REF B :: H1:SPI-H23_IFO_REF_B_DEMOD_SIG_OUT_DQ :: 2^15 (32768, or "32k")
IFO MEAS A :: H1:SPI-H23_IFO_MEAS_A_DEMOD_SIG_OUT_DQ :: 2^15 (32768, or "32k")
IFO MEAS B :: H1:SPI-H23_IFO_MEAS_B_DEMOD_SIG_OUT_DQ :: 2^15 (32768, or "32k")
QPD B SEG 1 :: H1:SPI-H23_OL_QPD_B_SEG1_OUT_DQ :: 2^11 (2048, or "2k")
QPD B SEG 2 :: H1:SPI-H23_OL_QPD_B_SEG2_OUT_DQ :: 2^11 (2048, or "2k")
QPD B SEG 3 :: H1:SPI-H23_OL_QPD_B_SEG3_OUT_DQ :: 2^11 (2048, or "2k")
QPD B SEG 4 :: H1:SPI-H23_OL_QPD_B_SEG4_OUT_DQ :: 2^11 (2048, or "2k")
FBR PWRIN REF :: H1:SPI-H23_FBR_PWRIN_REF_OUT_DQ :: 2^11 (2048, or "2k")
FBR PWRIN MEAS :: H1:SPI-H23_MEAS_PWRIN_REF_OUT_DQ :: 2^11 (2048, or "2k")
QPD A SEG 1 :: H1:SPI-H23_OL_QPD_A_SEG1_OUT_DQ :: 2^11 (2048, or "2k")
QPD A SEG 2 :: H1:SPI-H23_OL_QPD_A_SEG1_OUT_DQ :: 2^11 (2048, or "2k")
QPD A SEG 3 :: H1:SPI-H23_OL_QPD_A_SEG1_OUT_DQ :: 2^11 (2048, or "2k")
QPD A SEG 4 :: H1:SPI-H23_OL_QPD_A_SEG1_OUT_DQ :: 2^11 (2048, or "2k")
I've made ndscope templates for these channels, which live in (hopefully self-explanatory names):
/opt/rtcds/userapps/release/spi/h1/ndscope/
FBR_PWRIN.yaml
IFOs_Raw_Ts.yaml
QPDA.yaml
QPDB.yaml
The settings have been saved to the SDF system and committed to the userapps repo under
/opt/rtcds/userapps/release/spi/h1/burtfiles/
h1spih23_safe.snap
Also, for the record, Erik just helped me convert the target area .snap files to be softlinks to this one userapps file for now,
/opt/rtcds/lho/h1/target/h1spih23/h1spih23epics/burt/
safe.snap -> /opt/rtcds/userapps/release/spi/h1/burtfiles/h1spih23_safe.snap
OBSERVE.snap -> /opt/rtcds/userapps/release/spi/h1/burtfiles/h1spih23_safe.snap
Checked the baffles for the CRS on the constructed unit, everything fit fine. Spent time doing alignment for the other two constructed HoQIs. 01-SN008 aligned with 87% fringe visibility, this required the retroreflector on the baseplate to be rotated a bit as it wasn't quite in the correct position. 01-SN007 spent a long time trying to align (this was also worked on the other day with limited success), couldn't get above 60% FV so we decided to take it apart and redo it with the dowel pins in place. After taking it apart we found that the QWP was damaged by the metal screw, honestly quite impressive that it was still seeing 60% FV! See photos. The sin PD cable is also damaged and will need to be fixed before we use this HoQI. Assembled the remaining HoQIs including the dowel pins. Need to clean the final HWPs to finish this assembly. Additionally, 01-SN006 has no PDs as it is using the faulty assembly from before, 02-SN006 connector needs to be flipped. Current HoQI status: 2 aligned on CRS, 1 aligned, 2 with faults, 3 (mostly) constructed waiting to be aligned. pic 1 - broken sin pd pic 2 - broken QWP pic 3 - serial number for broken sin pd assembly
A set of spare cables was fabricated and will be sent to replace the one mentioned here, and the one mentioned in this alog: 90495
Shipping FRS: https://services1.ligo-la.caltech.edu/FRS/show_bug.cgi?id=38287
J. Oberling, R. Crouch
Yesterday we measured the initial position of the BBSS in the WBSC2 chamber, results shown in the 1st picture. Our goal is to match the position deviations we had on the test stand for the BBS SUS cage, as that was the SUS cage position we aligned the BBS optic with; all alignment moves after the SUS cage were positioned were done with the SUS chain itself, the cage did not move again, so matching the cage deviations should correctly position the BBS optic. As a reminder, the test stand deviations are shown in the 2nd attachment.
Based on this we will move the cartridge assembly with HEPI by approximately +2.5 mm along the X axis, +0.5 mm along the Y axis, and a CW rotation of ~500 µrad.
Shiela, Begum, Camilla, Madi E2600157
Morning:
Starting at FC alignment from Friday, 90527.
Tried to make the beam the correct ~5.5” height at ZM2 with A:M1 and then use ZM2 to get correct height at ZM3 (~6.25") but ZM2 did not have enough range. We railed it by only going halfway. Instead, we used A:M3 for beam height at ZM3 and then ZM3 for retroreflected beam. Did this only in PITCH (used YAW offset to help check retro-refection). Took height measurements (~6.25" at FC1 and ZM3, 5.85") This is not perfect at ZM2 but we'll check for any astigmatism when beam profiling. Attached alignments.
Tried to use B:M1 and BM4 to realign to ZM4 iris. However, beam could not be near centered on B:L1 aperture and fully transmit SFI2 (was a clipped after SFI2).
Realized beam height wasn’t level after OPO. High at A:L1 and low at A:DC2. We then used A:M1 pitch to center art A:L1 and then SFI1 aperture. And A:M2 to center on A:L2 aperture. We again checked if we could now get the correct height at ZM2 without railing ZM2 to get bean to ZM3, no. So adjusted A:M3 in PIT. After this was done, we realized PIT and YAW must be cross coupled as the beam was yaw'ed towards +X at the ZM3 iris. Paused.
Afternoon:
Looked again at the beam through A:L2 aperture and Sheila thought it was high. Begum and I then counted turns of the A:M1 and A:M2 mirror knobs before the beam clipped on the SFI1 and A:L2 apertures (checked that's where it was clipping with power meter) and then centered on each aperture.
Once we were happy with this. We again used A:M3 for beam height at ZM3 and then ZM3 for retroreflected beam. Did this only in PITCH (used YAW offset to help check retro-refection). The beam is still off in yaw at the ZM1 iris. Think this is from our initial A:M1 and A:M2 PIT moves.
We weren't 100% happy with our height measurements as think the beam was a little low at ZM3 <6.25", ZM2 5.8", FC1 6.25". We also think that the beam isn't centered on ZM2, photo. Another reason to think this is that when we try to move the retrofection to each side of the outgoing beam, it only moves to one side.
Beam scans:
We then stopped alignments to think about what to do with yaw and took beam profile measurement before and after ZM2 with the Phasics camera and TCS FLIR laptop. Took profiles and three locations between ZM1-ZM2 and two locations ZM2-ZM3. In one of the locations between ZM2-ZM3 we adjusted the ZM2 PSAMS from 3.15V (nominal) to 1.15V (minimum), 6.05V (maximum) and 4.51V (somewhere else in the middle).
TITLE: 06/09 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: MAINTENANCE
Wind: 28mph Gusts, 21mph 3min avg
Primary useism: 0.06 μm/s
Secondary useism: 0.19 μm/s
QUICK SUMMARY:
BBSS in-chamber + SEI work is in full swing, ITMy in-chamber First Contacting this morning, ISS PD Array alignment continues, CRS work continues, HAM7 in-chamber work for SQZ, and SPI is on deck at HAM3. CEBEX has brick walls which look over 10'.
Have had a windy morning with starting at around 2am locally and gusts up to 45mph.
Today:
Up next:
Start HEPI spring loading, recheck FARO shots, move per what FARO says we need to move
Suspend the BBSS, take Top TFs, then work on M2 and M3 stage OSEMs.
Erik V, Jennie W, Tony S
Summary: Jeff and I need a solution for SPI installation in order to communicate offsite to team members about alignment. Erik and Tony found a solution using the Blueman application. Just now we have this working on
TITLE: 06/08 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
ISS PD Array alignment continued, ITMy First Contact prep (for 3hr First-Contact-ing tomorrow), some FARO work for BBSS, cabling in BSC2, etc.
LOG:
J. Kissel, F. Clara WP:13296 %%%%%%%%%%%%%%% Executive Summary: Following up after last week's completion of SUS-R2 (LHO:90500), all HAM3 in-air electronics cables and optical fiber patch cords to/from SUS-R2 or TCSY to the chamber have been "pulled," i.e. routed fully to each end of their connections. This leaves *only* the HAM2 ISIJ QPD connection to its transimpedance amplifier in SUS-R1 as the last cable to be landed in the ex-vacuo part of the SPI electronics wiring and optical fiber network. %%%%%%%%%%%%%%% Details Here's the status summary of each of the HAM3 cables and patch cords Fil and I pulled today. SPI Picomotor Cable SPI_HAM3_013 Description :: This cable connects drive CHs 5, 6, 7, and 8 of the TCSY / CO2Y Picomotor Controller "G" (driven by Corner 2 ECAT Chassis) to the HAM3 D6 12x D25 feedthru into port F11. Status :: Now connected at controller and at flange. Strain relief at flange is not yet final. SPI PD Concentrator Cable SPI_HAM3_015 Description :: This cable bus routes the SPI HAM3 ISIK Transceiver PD and QPD signals (IFO_REF_A, IFO_REF_B, IFO_MEAS_A, FBR_PWRIN_REF, FBR_PWRIN_MEAS, IFO_MEAS_B, QPDB_Q1, QPDB_Q2, QPDB_Q3, QPDB_Q4) from HAM3 D6 port F10 to the "PD Input" port of the S2500712 D1002481-v4 "Variant 2" of the SPI transimpedance amplifier (TIA) chassis in SUS-R2 U4. Status :: Now connected at TIA and at flange. Strain relief at flange is not yet final. SPI_PSL_001 Optical Fiber Patch Cord Description :: This optical fiber patch cord connects the fiber collimator SPI-FC1 fiber output of the SPI Pick-off Path in the PSL to the "PSL IN" fiber input port on the front-panel of S2500058 D2400156 SPI Laser Prep Chassis in SUS-R2 U6+U7. Status :: NOT ENERGIZED (thanks to newly installed Uniblitz Shutter; LHO:90490). BUT -- shielded with standard orange protective tubing and now brought down from the cable tray (2nd story of "high" tray running above the input arm) and landed at the Laser Prep Chassis. Neither strain relief nor routing through rack is final. SPI_REF_001 and SPI_MEAS_001 Optical Fiber Patch Cords Description :: This pair of optical fiber patch cords connect the modulated at 80.0 MHz [MEAS] and (80.0 MHz - 4096 Hz) = 79.995904 MHz = "80- MHz" [REF] light from the SUS-R2 U6+7 Laser Prep Chassis fiber output ports to the HAM3 D4-1J1 [S3228003 MEAS] and D4-1J2 [S3228002 REF] fiber feedthrus (D2500175). Status :: NOT ENERGIZED (no laser input from PSL, nor are the AOMs being driven with any RF). BUT -- shielded with standard orange protective tubing and routed in the "low" cable tray system that runs from SUS-R2 to the feedthrus underneath the -X side of the chamber. They're connected at the SUS-R2 U6+7 Laser Prep Chassis fiber output ports, but they're dangling at the feedthru end because we haven't finished upgrading the feedthrus (see LHO:90511). References The SPI Pathfinder has been integrated into lots of different subsystems, so there's a ton of disparate systems drawings that are need to follow its signals from "soup to nuts." Optical Fiber [1] D1300348 As-built PSL/IO Table Layout [2] D2400110 Optical Fiber Routing Diagram RF electronics and PD Electronics [3] D2400111 SPI Wiring Diagram [4] D1002874 HAM3 Flange Layout [5] G2401479 Systems-level Slides for HAM3D4_12xD25 and HAM3D6_FiberFeedthru plans [6] SUS-R2 Rack Layout w.r.t. SPI [7] E1100591 (Heliax) RF Signal Distribution System Picomotor Drive [8] E1100892 TCS Wiring Diagram [9] D1900511 ISC Wiring Diagram [10] D1100683 EtherCAT (Beckhoff) System Diagram [11] E1200072 Picomotor Channel Inventory [[Very-out-of-date -- see unresolved IIET:32610]]
Pictures of SPI Picomotor Cable SPI_HAM3_013
Pictures of SPI PD Concentrator Cable SPI_HAM3_015.
Pictures of SPI_PSL_001 Optical Fiber Patch Cord, SPI_REF_001 and SPI_MEAS_001 Optical Fiber Patch Cords
Ibrahim, Anamaria
This morning we:
- set up the FC fabric on the drum;
- lowered the ITMX ACB to take its wedge, and then used it to swing the ITMY ACB out of the way;
- inserted the peek "Kurt fingers" between ITMY and its CP in preparation for installing the FC jig this afternoon.
This afternoon we:
- set up the jig around the test mass;
- tightened the drum with the fabric onto the test mass while watching the fibers on camera;
- added the grid+mesh for pressing, as well as picos on the ring of the drum;
- added the funnel and hose setup, connected to the spigot.
We will add more details and photos later. For now we are dumping photos in the common FC google drive. Folders named by date and activity.
First attachment shows that the ISS array PDs suddenly lost the beam (bottom left) right after the IM1 LL OSEM jumped (top left) on Friday, meaning that the problem was not just the OSEM sensing, somehow the alignment was affected by this.
This morning Rahul physically inspected IM1 and checked cables and electronics but nothing was wrong. He pulled the LL OSEM and nothing was wrong either. He put it back on, centered the OSEM depth (only for LL) and everything looked normal.
We locked JAC and suddenly we got the flashes on ISS array back, see the second attachment.
Though this is good, it's also frustrating that we don't understand what happened. My theory is that somehow something (OSEM bobbin thing?) was charged and pulled the closest metal electrostatically, changing the DC alignment.
We'll see if we can center REFL ASC sensors as well as ISS QPD. If we can, we'll proceed to close out.
FYI, following is the IM1 OSEMINF before the jump, right after the jump and now. UR experienced 500 counts jump and clearly got back after Rahul's job. Changes for UL and LR were much smaller but they got closer to the pre-jump position, too. Don't pay much attention to the 1000 counts difference for LL now VS pre-jump because it was reset.
| Before the jump on Friday | After the jump on Friday | After Rahul reset the OSEM | |
| UL | 16647 | 16577 | 16695 |
| LL | 9032 | 2492 | 10709 |
| UR | 14790 | 15292 | 14798 |
| LR | 7154 | 7022 | 7169 |
To investigate the issue on IM1 (LL AOSEM inmons dropped to 2000 counts from 9k approximately) I did the following things,
1. In HAM2 chamber, at first I thoroughly inspected IM1 for any signs of rubbing - found none and the pendulum looked free. The suspension was set to SAFE state during this time.
2. Unplugged LL AOSEM and connected healthy UL AOSEM cable to check for inmons - was still reading 2k. Hence, this ruled out any issue with LL in vacuum cable.
3. Took the AOSEM out of the suspension, visually inspected the LED and PD - looked all healthy. I also inspected the magnet on the optics for any damage - found none, everything looked fine.
4. As a backup I had spare AOSEM in hand for replacement.
5. I took open light counts of the LL AOSEM (now that it was plugged out of IM1) - the reading shows 19k counts which was good. This meant that there was nothing wrong with the LL AOSEM or the electronics chain.
6. I plugged that LL AOSEM back into IM1 and centered the flag/magnet to around 10k counts (50% open light).
7. Took chamber side transfer function measurements - all three dof. looked healthy, peaks and magnitude were good. The coherence was not so great due to the noisy environment.
Then I declared that IM1 is healthy and back in action.
What could have happened? - I think the flag magnet on LL could have been faintly touching or stuck and then set free, thus leading to a sudden drop in the inmon values. The second theory is that the AOSEM itself moved very slightly - its only held by a single set screw and does not have rails for moving them in and out.
Friday June 5th we completed the assembly for the CRS that is going in HAM3. First thing we checked the alignment of the HoQIs, Fringe visibility: SN005 86% SN007 85% We swapped out the photodiodes and cables in SN007 due to damage in one of the cables which meant the wire was exposed risking grounding issues should this touch any of the metal parts. The fringe visibility after this was at 72%. The HoQIs were completed with the baffles and top cover. SN007 cover is incorrect and the correct parts were not out of C&B so the wrong cover is on it at the moment this will be switched when we have the clean part. They were fixed to the CRS and aligned to it. SN007 is on the right and SN005 is on the left. Fringe visibility with the CRS fixed was as follows SN007 sin 82% cos 80% mcos 82% SN 005 sin 83% cos 75% mcos 83% The CRS was released and the fringe visibility for both left and right was checked, they were >80%, not all PDs were recorded but eg SN007 mcos was 82%
Begum, Ryosuke, Camilla, Madi
Summary: Were able to retroflect the beam off FC1 (when placed at O4 sliders) with ZM2 and ZM3 but the beam height is incorrect, as expected, VOPO optics will need to be moved to fix this.
Attached alignment for good alignment towards IFO, on ZM4 iris and SQZT7 IR PD irises. Both when OPOs is unlcoked and locked. When OPOS is locked beam doesn't go though closed irirses so isn't perfectly aligned but it is close enough.
Our Friday's alignment for FC retrorefection (with non-ideal) beam height:
When I hammered the below table "beard" baffle on May 26 (alog90335), something wasn't correct with the way I saved the data or my configuration or something else. Either way, Jeff and went in today and hit that as well as the SPI ISIJ assembly with and without the cylindrical shroud (D2500030). Preliminary results are looking much better, so I'll clean those up and post them soon with a whole writeup.
J Kissel, T Shaffer
All plots are in the accelerometer axis as defined below for each test. The measurement numbers were just for my own organization within the B&K software.
We did this in two stages, one set with the D2500030 cylindrical shroud and one set without. The accelerometer was mounted on a bolt hole below the ISIJ on the HAM face (photo).
| Hit location (on shroud or reflector) | With Shroud | Without | Comparison plots |
| -Y IFO (+Y acc) | Meas 5 | Meas 9 | Attachment 1 |
| +Z IFO (-Z acc) | Meas 6 | Meas 10 | Attachment 2 |
| -X IFO (+X acc) | Meas 8 | Meas 11 | Attachment 3 |
The shroud has clear resonant peaks at 137, 196, 314Hz. It was ultimately decided to leave this piece off for now.
Measuring the central below table baffle (D2600042) with the accelerometer mounted on the L bracket (D1700264) on the outermost bolt hole (photo). The accelerometer axis X,Y,Z = IFO -Z,Y,X.
Meas 1 - First hit IFO +X (+Z acc) bottom of L bracket - attachment 4
Meas 2 - hit in -Y IFO (-Y acc) on L bracket - attachment 5
Meas 3 - hit in +Z IFO (-X acc) L bracket bottom. Note that the bracket is tilted in the IFO -X direction. - attachment 6
There is a small peak at 87Hz.
Here's video evidence of the resonance -- see https://www.youtube.com/watch?v=bgA-cGWJSbg. (Video is sadly too large for posting to aLOG.)