40m QIL Cryo_Lab CTN SUS_Lab CAML OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 1 of 350  Not logged in ELOG logo
New entries since:Wed Dec 31 16:00:00 1969
IDdown Date Author Type Category Subject
  17625   Wed Jun 7 17:05:36 2023 yutaSummaryLSCRF FPMI recovered after c1sus DAC card replacement

[Paco, Yuta]

RF FPMI is recovered after c1sus DAC-0 card replacement

 - We wanted to check if FPMI locks after DAC-0 card relacement (40m/17620).
 - 60 Hz noise similar to what we saw in February prevented us from locking FPMI stably, but fixed it by turning off FM9 of coil output filters in MC1 and MC3 (40m/17462).
 - There are slight changes in locking gains, but it now locks reliably.

FPMI locking:
 - MICH: 1 for REFL55_Q, MICH_GAIN=18 (used to be 11) gives UGF of 45 Hz
 - DARM: 1 for AS55_Q, DARM_GAIN=0.044 (used to be 0.04) gives UGF of 134 Hz
 - CARM: 0.567 (used to be 0.496) for REFL55_I, CARM_GAIN=0.011 gives UGF of 224 Hz
 - Attachment #1 shows all the OLTFs.

60 Hz noise:
 - FPMI locking was not stable, and we moved back to YARM locking to see if 60 Hz noise is higher or not.
 - Attachment #2 shows 60 Hz noise measured with MC_F and YARM. The noise was actually similar to what we saw in 40m/17461, so we checked MC1 and MC3 dewhitening
 - FM9 of coil output filters was turned on for some reason (probably because of burts we were doing when fixing c1sus). MC1 and MC3 FM9 ELP28 filters should be off.
 - This made FPMI locking stable and 60 Hz noise lower by more than an order of magnitude (Attachment #3).

Attachment 1: Screenshot_2023-06-07_16-17-15_OLTFs_FPMI.png
Attachment 2: Screenshot_2023-06-07_15-51-09_MC1MC3_FM9_OFF.png
Attachment 3: Screenshot_2023-06-07_17-04-18_FPMI60Hznoise_AFTERFIX.png
  17624   Wed Jun 7 15:51:47 2023 KojiUpdateCalibrationITMY calibration with ALS and swept line

Can you make this flat by compensating the gain bump due to the UGF of the phase tracker?


  17623   Wed Jun 7 10:35:42 2023 RadhikaUpdateDaily ProgressT&R measurement setup for PR2

[Radhika, Aaron, Mayank, Paco]

Here I'll describe the setup for T&R measurements of a PR2 replacement, using the Lightwave NPRO laser located at the S/E corner of the PSL table. Our transmittivity prior for this optic is ~20-30 ppm. Aaron and I outlined the setup for measuring the transmittivity of p- and s-polarizations using a chopper wheel for lock-in detection [Attachment 1]. 

JC found a Lightwave laser controller (in cabinet along YARM). Mayank and Paco helped start it up and adjust the current such that we can align with low power. I used the power meter sitting on PSL to record a quick laser calibration up to 160 mW (plot in Attachment 2 - I can go up to 500 mW in the future). Attachment 3 shows the location of the power meter when these points were collected. For alignment, I set the laser current to 0.94 A (~33 mW). 

I removed most optics in the existing setup downstream of the Faraday isolator. I reused 2 PBS cubes and a HWP from the old setup (I still need a QWP). My progress as of 6/6 can be seen in Attachment 4.


- Acquire QWP
- Set up chopper with lock-in amplifier (SR830 or Moku:Go?)
- Align TRANS and REF PDs (using 2 Thorlabs PDA-100A)
Attachment 1: IMG_4916.PNG
Attachment 2: lightwaveNPRO.pdf
Attachment 3: IMG_4908.JPG
Attachment 4: IMG_4912.PNG
  17622   Tue Jun 6 21:23:37 2023 advaitUpdatePEMEarly heater prototype

Paco suggested I start putting together the beginnings of a heating system so that I can get a better idea of what parts and equipment we need and can order them ASAP. This is also to try and match the real data with simulation models for the basic system and then add complexities like insulation foam (which is also currently not in hand) later. This should give insights into loopholes in the models and also into the estimation of parameters like the convective transfer factor (h) which aren't trivial to accurately constrain in simulation according to what I've read.

I will edit in a circuit schematic by tomorrow (done), but the circuit is quite similar to the new one made by Kevin and Kira which I linked in a previous elog. For now, I have used a makeshift and messy combination of resistors (there are very few high wattage ones that we could find in both 40m and the EE shop) which manages to achieve a max current of around 0.25A through a resistive element of 50 ohms, leading to a peak power output of 3.22 W which is good enough for the puck. This resistor comes in a nice brass housing (visible below the puck in image) which makes it convenient to attach to the puck and pump heat into it relatively efficiently. I tested this circuit by turning it on for 30 minutes and the puck did warm up a bit. I will work on calibrating and attaching the old temperature sensor to this tomorrow so I can start doing step responses and quantifying things.

Note that I will add some gain to the RPI output to maybe scale it to 5V so that it can cross the V_{GS} threshold by a comfortable margin.

One critical difference from the old circuit is that this one is meant to drive the MOSFET only in fully-on or fully-off mode to minimize heat dissipation through it, so we basically use PWM to regulate the heat from zero to the peak value. JC and I also set up the ethernet wiring for the Raspberry Pi 2 at the experiment as well as my desk so that I can control it from my laptop over LAN. I tested PWM using Python with an LED that can be seen in the image. Now I basically just have to plug the Pi into the circuit input and measure the RMS current to confirm that it is also controllable in a similar way and linear as we would expect, and also check out the output waveform.

  17621   Mon Jun 5 18:42:13 2023 PacoUpdateCalibrationITMY calibration with ALS and swept line

ITMY actuator calibrated with higher resolution using ALS after c1sus-DAC0 replacement

I repeated the previous measurement (with fewer points) and the result is summarized in Attachment #1 -- just as a quick confirmation that the actuation strength (POS) is restored to its nominal ~ 5 nm / ct / f^2 value.

 (plot updated Tue Jun 6 10:34:27 2023 without violin filters and higher resolution)

Attachment 1: ITMY_ALSCAL_Screenshot_2023-06-06_10-34-50.png
  17620   Mon Jun 5 15:34:27 2023 PacoUpdateCDSC1SUS DAC-0 replacement

Vertex c1sus DAC-0 card replaced yes

[Paco, Yuta, JC, Mayank]

This morning JC helped us locate a 16 bit DAC adapter card located behind the XARM vacuum tube with the cds upgrade components. Yuta and I went to the IO chassis and replaced the adapter boards. We then restarted the models and ran the same test as last time (using the Vmon channels from the acromag to monitor DAC outputs) but noticed the values were all negative and large. Using dataviewer (see Attachment #1), we saw that DAC-0 actually railed to output negative values somewhere around 07:00 UTC (midnight), even before we attempted to swap the DAC adapter card, implying that the DAC card itself was the core of the failure. Furthermore, this kind of failure prevented any other suggested workarounds (like swapping face with side coil DACs and applying negative offset to side coils). We then decided to restore the DAC card adapter back to the previous one and further look for a spare 16-bit DAC.

After more digging around, JC found a spare 18 bit DAC card which is not useful... and finally, Mayank and JC suggested using the test stand IO chassis DAC as a replacement. We replaced this (see Attachment #2) and restarted the models a few times until fcinally at around ~15:30 we managed to get the system up and running in its previous state. The awggui tests were done on all affected vertex suspensions (PRM, ITMs, BS) and the results are summarized by Attachment #3-6.

Attachment 1: DAC0_completefailure_Screenshot_2023-06-05_22-43-16.png
Attachment 2: PXL_20230605_214528130.jpg
Attachment 3: BStestpassed_DAC0_Screenshot_2023-06-05_22-43-53.png
Attachment 4: PRMtestpassed_DAC0_Screenshot_2023-06-05_22-45-34.png
Attachment 5: ITMYtestpassed_DAC0_Screenshot_2023-06-05_22-48-43.png
Attachment 6: ITMXtestpassed_DAC0_Screenshot_2023-06-05_22-47-30.png
  17619   Mon Jun 5 10:01:41 2023 YehonathanUpdateSUSETMX fast-channel-watchdog was implemented

{Mayank, Yehonathan}

We updated the c1auxex db file ETMXaux.db. Backup was saved under the same folder called ETMXauxback.db.

The following EPICs channels were added to calculate OSEM PD variances using the RTS:

        field(DESC,"ETMX UL Se")
        field(SCAN,"1 second")
        field(DTYP,"Raw Soft Channel")
        field(INPA, "C1:SUS-ETMX_ULSEN_INMON")
        field(INPB, "C1:SUS-ETMX_ULPD_MEAN_NEW")
        field("CALC", "0.5*ABS(A - B)")

    field(DESC,"ETMX UL Sensor Mean")
        field(SCAN,".2 second")
    field(EGU, "Volts")

        field(DESC,"ETMX LL Se")
        field(SCAN,"1 second")
        field(DTYP,"Raw Soft Channel")
        field(INPA, "C1:SUS-ETMX_LLSEN_INMON")
        field(INPB, "C1:SUS-ETMX_LLPD_MEAN_NEW")
        field("CALC", "0.5*ABS(A - B)")

    field(DESC,"ETMX LL Sensor Mean")
        field(SCAN,".2 second")
    field(EGU, "Volts")

        field(DESC,"ETMX SD Se")
        field(SCAN,"1 second")
        field(DTYP,"Raw Soft Channel")
        field(INPA, "C1:SUS-ETMX_SDSEN_INMON")
        field(INPB, "C1:SUS-ETMX_SDPD_MEAN_NEW")
        field("CALC", "0.5*ABS(A - B)")

    field(DESC,"ETMX SD Sensor Mean")
        field(SCAN,".2 second")
    field(EGU, "Volts")

Additionaly, we changed the watchdog logic such that it will read the variance from these new channels:

        field(DESC,"Tests whether RMS too high")
        field(SCAN,"1 second")
        field(INPA,"C1:SUS-ETMX_ULPD_VAR_NEW  NPP  NMS")
        field(INPB,"C1:SUS-ETMX_PD_MAX_VAR  NPP  NMS")
        field(INPC,"C1:SUS-ETMX_LLPD_VAR_NEW  NPP  NMS")
        field(INPD,"C1:SUS-ETMX_SDPD_VAR_NEW  NPP  NMS")

We also check that the new variance channels match more or less the old ones. Attachment shows a comparison during the transition from tripped watchdog to damped state.

The watchdog logic was checked by setting the MAX_VAR to 0 and observing the watchdog trip. ETMX damping was restored succesfuly. Now we are ready to install the new coil drivers.

Attachment 1: Screenshot_2023-06-05_11-14-34.png
  17618   Sat Jun 3 19:56:59 2023 PacoUpdateCalibrationITMY calibration with ALS and swept line

ITMY actuator calibrated with higher resolution using ALS

Today I came briefly in the lab and restarted all models because the beams were missing in the BHD camera; implying the ASS model controlling TTs has tripped into a weird state. The problem got fixed after that and I recovered the IFO alignment more or less. Thus I began another quick calibration run --

I wrote a script to put calibration line and update the LSC YARM notch filter using python-foton so as to take an ALS calibration sweep of the YARM test mass actuator responses. For a given sweep frequency array, the script loops over the frequency, updates the notchSensMat (LSC-YARM FM10), loads the coefficients, and ramps up the SENSMAT OSC gain and frequency to inject the noise. The YAUX laser is locked to the YARM and YARM is locked to PSL during this measurement. Then, the real-time demodulated BEAT_Y signals are averaged for ~ 3 seconds (just wanted a quick scan, not a very accurate or precise one) and the result is plotted in Attachment #1. Notice that I have included the phase tracker loop correction to account for the high frequency calibration line inferred response (1 + i f/2000)

I then used foton in gui mode and exported the violin filter transfer function (FM1-4 and FM6 for ITMY) magnitude and inverted its effect to get the "dc actuation strength" of ITMY.


  • The value is consistent with our recently poor actuation due to c1sus - DAC-0 failure, at ~ 3 nm /count /f^2. I look forward to another measurement after the DAC-0 has been replaced / fixed.
  • No more "high frequency" lift as seen before?
  • There is still some residual frequency dependence near the phase tracker BW; maybe not just a simple integrator?

The idea of having the response shape is so I can then use the 5 lines only to get the response to high accuracy.

Attachment 1: itmy_act_sweep_alscal.pdf
Attachment 2: itmy_act_novio_sweep_alscal.pdf
  17616   Fri Jun 2 19:03:57 2023 PacoUpdateCDSC1SUS DAC failure (Re: ITMX UL coil and BS oplev rms)

Vertex SUS DAC-0 card is kaput no (aka C1SUS DAC failure) ed: Koji

[Paco, Yuta]

Continuing our investigation of how a couple of coils seemed to be malfunctioning and the local damping was affected, we did the following:

  • We calibrated ITMX actuation strength with ALS beat at 211.11 Hz and found 5.105 nm / count / f^2 or just 5% off from the previous values. So nothing seemed strange (e.g. 25% difference from single coil failure)
  • We tried calibrating BS actuation strength and found it very hard to lock MICH. Furthermore the result was off by a factor of ~ 2 with respect to previous values!! Highly sus...
  • We tried calibrating ITMX/ITMY actuation strengths and found they were also weaker by ~ 2 with respect to previous values. Extremely sus.. Attachment #1 summarizes these results.
  • We decided to repeat our DW board transfer function estimates using single coil to Oplev transfer function measurements, but this also seemed harder in comparison with our last measurements. (couldn't even replicate using our dtt saved template results)

Finally we checked the analog electronics, breaking the BS AI to DW board connection of ULCOIL. We then used awggui to drive the single coil and the AI test mon output to read the commanded signal. We repeated this for a couple more coils, and also for other optics (PRM, SRM). We found that PRM had the same issue as BS that the DAC output couldn't drive positive voltages! In contrast, SRM worked fine. We then swapped the DAC adapter (see Attachment #2) units by swapping cables between SRM /MC3 and BS/PRM (D080303 -- not on DCC) and ruled out a failure from the buffered Test MON outputs on the AI board. So the problem was narrowed down to the DAC_0 card on c1sus chassis.

To try and fix this, we stopped the c1sus model, shutdown its frontend computer, and power cycled the IO chassis including the DC power at the front. This time, we tested the DAC outputs by driving the face coils separate from the side coils (running on DAC_2) using a 0.1 Hz sine excitation on ITMX, BS, ITMY and PRM from awggui and looking at the coil Vmon channels from the acromag on all suspensions. See Attachment #3-4 for a summary of all the tests (BS, PRM, ITMX, ITMY are bad, SRM, MC1-3 are good).

After verifying that this didn't fix the issue, we concluded that c1sus - DAC_0 fails to drive positive voltages.

Next steps

  • Replace DAC_0 with spare (does not seem to exist in our cds supplies)
  • Swap the Side coil DAC (DAC_2) with the failing DAC (DAC_0) and drive the side coils with an offset since SIDE coils are not critical.
  • Adapt the AI boards to be compatible with existing spare 18-bit DAC units.
Attachment 1: actcalibITMBS_20230602Failure.png
Attachment 2: PXL_20230603_005109646~2.jpg
Attachment 3: BS_PRM_ITMX_ITMY_DACTest.png
Attachment 4: SRM_MC1_MC2_MC3_DACTest.png
  17615   Fri Jun 2 17:01:20 2023 ReubenUpdateALSGetting comfortable with the ALS

[Reuben, Radhika]

Checked out the AUX PDH locking system at the XARM. Started by locking the AUX laser using the uPDH servo box and adjusting the test masses to maximize transmission (~0.6 achieved). There were some issues where the fundamental mode would be briefly visible and then lose lock. Higher order modes were also seen which could be removed by adjusting test masses. We also noticed the laser spot moving around a lot, as if the test masses were swaying. Finally after repeated tries we managed to lock and hold the laser to the cavity long enough to measure the open loop transfer function using the Moku:Go frequency response analyzer tool. Got an idea of the finicky and temperamental nature of the locking process.

Taking the transfer function data from the Moku:Go and using a Python script, found the UGF to be around 25.6 kHz and phase margin to be around 25.5 deg. My current goal is to keep reading up on control systems and related theory (I still feel like I lack understanding of the important principles needed), and parallelly making a small script that can take the transfer functions data and calculate some useful information (halfway done).

One issue I found with the script was that the Python control library was giving me a wrong value of Gain Margin (~0.26 where ~-5 was expected) while using the control.margin function. The other parameters phase margin and crossover frequencies agree with the data visually.

Attachment 1: test.pdf
Attachment 2: 2023-06-01_XAUX_PDH_OLTF_20230601_112313_Traces.csv
% Moku:Go Frequency Response Analyzer
% Channel 1, DC coupling, 10 Vpp range, amplitude 100 mVpp, offset 0.000 0 V, phase 0.000 deg
% Channel 2, AC coupling, 10 Vpp range, amplitude 10 mVpp, offset 0.000 0 V, phase 0.000 deg
% Logarithmic sweep from 1.000000 MHz to 10.00000 Hz with 1,024 pts, dynamic amplitude mode off, measuring fundamental, normalization off
% Averaging time 2.00 ms, 10 cycles; Settling time 100 us, 1 cycles
% Acquired 2023-06-01 T 11:23:13 -0700
% Frequency (Hz), Channel 2 Magnitude (dB), Channel 2 Phase (deg)
1.00000000e+06, -6.5842e+01, 5.9914e+01
9.88809008e+05, -6.3940e+01, 5.6437e+01
9.77743255e+05, -6.8414e+01, 6.0371e+01
... 1022 more lines ...
  17614   Fri Jun 2 16:45:46 2023 advaitUpdatePEMMass for temperature control

Thanks, I was actually looking for a scale earlier but could not find it after asking a couple of people. One of the scales reads 298 g, while the other has a limit of 200g. Looks like it is indeed aluminium.


How about measuring the actual weight with a scale? There are a couple of scales on Yuta's desk.


  17613   Fri Jun 2 11:47:33 2023 KojiUpdatePEMMass for temperature control

How about measuring the actual weight with a scale? There are a couple of scales on Yuta's desk.

  17612   Fri Jun 2 10:59:20 2023 advaitUpdatePEMMass for temperature control

I measured the dimensions of the puck we shall be using as the mass for the toy model. It has a diameter of 75 mm and a thickness of 25 mm. Assuming a density of 2.7 g/cm^3, this brings the mass to 298.2 g.

  17611   Thu Jun 1 10:03:47 2023 YehonathanUpdateSUSETMX Coil driver upgrade

Thanks. This makes the plan clear.

- Please follow the attached rack plan for 1X9

- The immediate aim is the recovery of the suspension operation without acromag. Focus on it for now, and then move on to the Acromag modification.


> Take out 2 new coil drivers and replace their output resistance with appropriate resistors (What should they be?)

We are supposed to have the coil drivers with the output Rs already replaced. But it is a great idea to check if they are really done or not.

> Test the new coil driver on the bench.

I hope this is not necessary, as the coil drivers / sat amps were already tested before...

> Change the powering of the Acromag chassis so that we can operate it with a single Sorensen.

Good idea. If we ended up having an unnecessary Sorensen, we can remove it and add it to the stock.


Attachment 1: rack_plan.pdf
  17610   Thu Jun 1 08:34:06 2023 PacoUpdateCDSITMX UL coil and BS oplev rms

ITMX / BS local damping issues  -- investigation in progress

[Paco, Yuta]


We noticed an increase in PD variance in a few optics since last Friday (05/26, circa 23:00 UTC) and decided to investigate using dataviewer. There are a few observations made by Yuta:

  • BS -- OpLev rms increase, OSEMs are nominal
    • May 26 ~22:00 UTC, oplev PIT/YAW rms increased suddenly
    • May 28 ~ 17:00 UTC, optic tripped (model crash)
    • May 29 ~21:00 UTC, optic restored (model restart), oplev PIT/YAW rms still increased
  • ITMX -- OpLev rms increase, OSEMs are not nominal (specifically UL)
    • May 26 ~ 22:00 UTC, oplev glitch but rms stays nominal
    • May 28 ~17:00 UTC, optic tripped (model crash)
    • May 29 ~21:00 UTC, optic restored (model restart), oplev PIT/YAW rms increased suddenly

BS oplev alignment

We thought it would be worth checking the BS oplev table for any alignment issues, since playing with the loop gains (OL_PIT/YAW_GAIN) didn't seem to have an effect. We quickly found two issues:

  1. Clipping on lens before QPD: which was fixed by alignment and recentering of the lens aperture.
  2. Lens AR coating was dumping almost 50% of the power: which was fixed by switching from a f=62.9mm AR.33 coated (for 1064 nm) plano convex lens to an f~ 100 mm uncoated plano convex thorlabs singlet (LA1509).

These changes are always good to implement, but the increased BS oplev rms issue remains.

Coil output test

Under the premise that local damping is not working correctly, we decided to test coil outputs at the coil driver test monitor outputs and also before (at the dewhitening monitor outputs). Looks like BS_ULCOIL is not able to drive a large enough voltage compared with the other Coils. This is consistent with the very weak optic "kicks" we get on BS when using this coil.


After this issue, we restarted all models.


Attachment 1: Screenshot_2023-05-31_16-49-26_BS.png
Attachment 2: Screenshot_2023-05-31_16-51-44_BSoplev.png
Attachment 3: Screenshot_2023-05-31_16-39-28_ITMX.png
Attachment 4: Screenshot_2023-05-31_16-56-47_ITMXoplev.png
  17609   Wed May 31 16:26:28 2023 YehonathanUpdateSUSETMX Coil driver upgrade

{Mayank, Yehonathan}

In order for the ETMX watchdog to keep working while we take the Acromag chassie out we are going to replace the PD_MONs in the variance calculation channels with fast OSEM PD channels/

We made a backup to the c1auxex db file called ETMXauxbak.db in the c1auxex folder.

Now, we are struggling with adding channels to the db file. Once we figure this out we will try to read the fast SENS_IN1 channels.

In the meanwhile this is a broadview (and maybe naive) plan for the coil driver upgrade:

-1. Take out 2 new coil drivers and replace their output resistance with appropriate resistors (What should they be?)

0. Test the new coil driver on the bench.

1. Once a temporary fast-channel-based watchdog is setup and tested, Acromag chassie is taken out to the EE bench.

2. Replace the old DB37 feedthroughs with DB9s according to the ETMY plan. Check if there are extra channels that exist in c1auxex but not in c1auxey that need to be preserved.

3. Wire the acromag units to the DB9s. Add optical isolators and wire the EnableMon and Enable fast channels through them.

4. Change the powering of the Acromag chassie so that we can operate it with a single Sorensen.

5. Add 5 EnableMon channels. We will probably need anothe BIO Acromag as there is only 1 in current chassie according to the old wiring table.

5. Bench-test the Acromag chassie channels.

6. Add 5 new EnableMon channels to the db file.

7. Install Acromag chassie, coil drivers, SatAmps and HV drivers and the connect labeled db9 cables between them.

8. Test the new coil drivers online.

Anything else?


  17608   Wed May 31 12:08:07 2023 ranaUpdateBHDSensing matrix model

it is great to see a sensing matrix without 900 digits of precision!

for choosing what sensor to use, we don't necessarily care about W/m, but more like the equivalent noise of the sensor in m/rtHz, taking into account the real noise floor. In that case, we would possibly rotate the demod phase to maximize the SNR rather than maximize the S or minimize the N.

  17607   Wed May 31 10:23:40 2023 YehonathanUpdateBHDSensing matrix model

I calculated the sensing matrix for PRMI carrier using the Finesse model (git updated) using MAXTEM=2. PRG is calculated to be 11.14, consistent with observations.

LO Phase is chosen such that it maximizes MICH signal on BHD_DIFF.

The RFPDs were assumed to have a demodulation angle that maximizes the signal they are intended to sense (using MAXTEM=2).

That is,

BH44/55 maximized for HPC

REFL11 maximized for PRCL

AS55 maximized for MICH

Values are in uW/nm

REFL11_I 1.9e-2


7.6e-2 4.0e-2 0

Some interesting numbers here. First, BHD_SUM is sensitive to MICH. It's not surprising because PRM reflects the MICH signal into POP.

Also interesting, BHD_SUM is super sensitivef to PRCL. Much more than REFL11. We can use it to enhance the PRCL lock.

Unfortunately, although BH44/55 are sensitive to HPC (LO phase), they are swamped by MICH and PRCL. This issue needs to be addressed in order to gain robust LO Phase locking in PRMI.

  17606   Mon May 29 11:04:13 2023 PacoUpdateCDSc1sus2 all FE models crashed spontaneously again

c1sus2 crashed again. Following 40m/17335, I fixed it by running

controls@c1sus2:~$ rtcds restart --all

"global diag reset" made all FE STATUS green burt restored at 2023/May/28/00:19 for c1sus2 models, and watchdogs reset for BHD optics and now all look fine.

Other optics, including MC1, MC2, and MC3 were not damped, so maybe c1sus crashed too I also ran

controls@c1sus:~$ rtcds restart --all

"global diag reset" made all FE STATUS green, burt restored at 2023/May/28/00:19 for c1sus models and watchdogs reset for all other suspensions.

TT1 and TT2 were not responding, and the DAC monitors were frozen... so I ran


Wed May 31 14:58:06 2023 UPDATE: I forgot to log that ITMX, ITMY and BS oplevs were centered after some nominal alignment was recovered.

  17605   Fri May 26 15:04:12 2023 JCUpdatePSLPSL Fans Replaced

We Changed The Fans on the PSL

To start, the part Koji ordered is 259-1818-ND from DigiKey. This is a Maglev fan from SUNON that should give us less noise. We have 3 spare replacement fans in case these go bad which are stored in the ___ Cabinet along the Y arm (This will be updated once I find a suitable storage spot for the part.)

Starting the replacement process.

Removing the PSL 

    1. Our first step to doing this was to prepare for removing PSL. We began by doing a 60s MC WFS Relief. This will allows us to turn off WFS and close the PSL Shutter next. This is to prevent a large kick once we place the PSL back in its place. 
    2. Went to the PSL and mushed the off button and turned the key. After this, begin by removing the external fan which is shown in elog 17595. After, continue by unplugging the cables from the back beginning with the power cable. Attachment #1 shows the original positions of the cables connected before removing any. Keep in mind, DO NOT TO TOUCH THE KNOBS. If the inputs are changed, this will throw off the beatnotes of the AUX lasers.
        a. There is a black plug at the bottom with a screw hat is hard to reach. Be very patient taking this off because the position of the cable blocks a screqwdriver from untightening the screw. 
        b. A second person should be on the other side of the table to push the module back into arm's reach. Also to make sure the module does not slide back and fall. 
    3. After removing the module, bring into the control room and place onnto the workbench. Make sure all of the red lights are off and the PSL table is closed properly.

Changing the Fan 
    1. We removed the top cover of the module and opened it all up. Similar to what is shown in elog 17452.
        a. Keep in mind to wear a grounding wristband when working on this.
    2. After removing the old fans and attempting to install the new ones, the holes did not line up correctly (Shown in Attachment #2). To accomodate for this, we used 6-32 screws which gave us just enough slack to fit in all 4 corners.
    3. Ones the fans were bolted down onto the aluminum plate, I soldered the cables to connecting the fan cable to the cables those of the original PSL fans.
    4. Next I used heat shrinks to cover the bare soldered areas and placed the fans into the module. 
    5. We tested the fans by plugging intp the PSL and turning the key. The fans turned on nicely and we proceeded to put it module back together.

Placing the PSL back in its place. 

    1. We place the PSL back into its original spot and began to connect the cables. Make sure the Power cables is put in LAST. 
    2. After the module was put back, we DID NOT put the external fan back into its place. This is to see if the fans which were installed are good enough to maintain the PSL.
    3. Turn the key and press the on Button.

The noise from the external fan is no longer appearing as shown in attachment #3. The PSL has been on for ~2 hrs now and has not turned off. It seems that the fans are doing their jobs well. 


Attachment 1: IMG_5650.jpeg
Attachment 2: IMG_5653.jpeg
Attachment 3: Screenshot_2023-05-26_16-25-54.png
  17604   Fri May 26 11:16:46 2023 AnchalSummaryPEMTemperature sensing circuit with AD590

I wanted to mention here that I have a printed circuit board design (LIGO-D1800304) for using AD590 as temperature sensors. I believe printed boards and all required components are stored on the wire shelf in the WB EE shop on a box labeled with this DCC number. This circuit is also meant to be read by Acromag, maybe it can come of some use to you. You can check out the use in CTN lab in WB near the south-east end of the table.


  17603   Thu May 25 14:40:03 2023 PacoUpdateCalibrationMeasured the PSL wavelength

The PSL wavelength is 1064.5068 +- 0.0015 nm

[Paco, Yehonathan]

With yehonathan's help, we borrowed a WS6-200 wavemeter and calibrated the PSL wavelength using the frequency doubled beam at the PSL table. For this we gathered a FC/APC to FC/PC fiber, cleaned both ends, and launched ~ 6 uW of power into the wavemeter (Attachment #1 shows the setup). The vacuum wavelength was measured to be 532.2534 nm, (see picture in Attachment #2) implying a PSL wavelength of 1064.5068 nm. This is not too far from my previous estimate! The wavemeter claims a "200 MHz accuracy" so we used this as a standard error to estimate the uncertainty of  2 * 0.7 pm @ 532 nm = 1.5 pm @ 1064 nm. This leaves us with 1.4 ppm of relative wavelength error in the ALS based calibration.

  • It should be noted that the Nd:YAG temperature was set to 30.615(5) degrees (?) and the injection current to 2.100 Amps for this measurement.
Attachment 1: PXL_20230525_205542591~2.jpg
Attachment 2: PXL_20230525_205332570.jpg
  17602   Thu May 25 13:38:28 2023 advaitSummaryPEMExisting temperature control hardware

Over the past few days I have been trying to understand the existing sensor and heater related hardware by manual inspection and combing elogs. From what I understand, I believe a lot of the hardware was built from scratch by Kira in 2017-18. She put in place the insulation, built the sensor and heater circuits and installed and interfaced everything with EPICS. This let her successfully do step response tests and also execute PID control of the temperature of the can. As suggested by Paco, I am trying to summarise my findings in this elog. This is the block diagram of the overall system.

In the lab I was able to locate two identical temperature sensor boards, one for monitoring ambient temps and another for the can temp, which has a sensor attached to the inner seismometer can. Attachment 1 shows the actual board.

The schematic for the temperature sensor can be found here. It was later clarified that she is using AD590 and not the AD592. I tested the ambient sensor board by hooking it up to an oscilloscope and heating the sensor up. It seems to work like she described, and the output voltage goes down with heat. I will later figure out interfacing it with an ADC and calibrating it if I cannot find Kira's old work related to this. The setup there also has +/-15V Sorensen's for power (I probed these and they work), a BNC for temp readout and a bunch of other wiring for the heater. This wiring comes from the nearby rack which should have the heater circuit, but I haven't yet been able to locate it because there is too much stuff.

Coming to the heater circuit - I found the schematic for it here. I am still unsure about what the power range it can operate over, but this plot seems to imply it saturates at around 55W. This circuit underwent many different iterations so I am unsure what load resistance was actually used finally and it is not clear from the elogs. It might be a pair of heaters combined in series or parallel. Additionally, this elog by Shruti from June 2018 implies that the original circuit that Kira made ended up breaking at several different points. She said there were attempts to fix it, but I cannot find any updates after that and I think her SURF ended. I don't know the current status of the heater circuit. I am not sure where it is stored.

I was hoping to utilise the old EPICS channels set up by Kira for heater control as well as sensor readout to verify if everything was still functional and initially just read out the temperature of the can and find out how much it fluctuates. I planned to later also try to replicate the PID results. But Paco explained how the Acromag system worked and told me that utilising the old channels will not be possible right now, as all the channels have been used up for more critical tasks and none of the old interfaces that Kira had set up can be used now, even if the hardware was fine. 

Also, the can temperature sensor board has a wobbly solder joint at one of the power connectors, and we cannot move it to the lab because the sensor is anchored to the inner can. There is no power indicator LED to signal if the connection is secure so its kind of unusable right now. Paco and JC told me that soldering near the X end is not possible because the fumes would harm the optics. We will look for solutions to this. One option would be to make an entirely new board and keep a mechanical connector for the sensor. 

  17601   Wed May 24 17:36:25 2023 PacoUpdateBHDBH44_I content and PRC alignment

BH44 is sensitive to PRC alignment noise

[Paco, Yuta]

We investigated the content of BH44 demodulated signals under PRMI configuration. We had a few ideas of what was being sensed by BH44_I but we wanted to test this. Attachment #1 shows a timeseries screenshot of the DCPDs and BH44 error signals during PRMI lock stretch. It is pretty clear how BH44_I is sensing the same as REFLDC. To understand what REFLDC is sensitive to, we locked PRY (this is like having a lossy PRC) and looked at REFLDC, and BH44 error signals again. When PRY is aligned nicely, BH44 error signals show clean LO fringes and we could lock LO_PHASE stably (Attachment #2). Dithering the PRM YAW at 0.5 Hz (amplitude of 150 counts) is sensed by the REFLDC output, so we can attribute its fluctuations to the PRC misalignment (Attachment #3). Now we saw that the zero crossing of the homodyne phase angle changes following REFLDC, and LO_PHASE could not be locked stably. These suggest that alignment of PRC is sensed by BH44, and we might need alignment control to stably lock LO_PHASE in PRMI.
To get the idea of what is causing alignment fluctuations of PRC, we checked the spectrum of SUSPIT/YAW of PRM, PR2, PR3, BS, ITMX, and ITMY. It was not clear what is causing REFLDC fluctuations. (But we found that ITMX and ITMY has huge bounce mode at 16.2 Hz; see Attachment #4).

 - Check FINESSE to see what BH44 sees. PRCL? PRG?
 - Commission REFL WFS for alignment control of PRC?
 - Commission dither loops (add option to demodulate PRCL, modulate PR2 and PR3) for alignment control of PRC?
 - Check RF spectrum of BH44 and RF LO for 44 MHz (sidebands other than 44 MHz might be contaminating the signal).
 - Check ITMY scattering. Dither ITMY in YAW and check BH44.
 - Move on to PRMI sideband BHD

Attachment 1: Screenshot_2023-05-24_17-38-22_PRMI_REFLDCvsBH44.png
Attachment 2: Screenshot_2023-05-24_17-40-58_PRY_REFLDCvsBH44.png
Attachment 3: Screenshot_2023-05-24_17-44-49_PRY_REFLDCvsBH44_PRM0.5Hz.png
Attachment 4: Screenshot_2023-05-24_17-46-13_ITMSBOUNCE.png
  17600   Wed May 24 13:19:28 2023 PacoUpdateBHDBH44 and BH55 dc transimpedance modified

We lowered the BH44 and BH55 DC transimpedances to ~ 50 V/A

[Paco, Yuta]


When locking the homodyne phase angle using BH44_Q or BH55_Q error signals, we notice the orthogonal quadrature (BH44_I, BH55_I) sometimes appears too noisy. The origin of this useless signal is not known, but we have recently attenuated these beams by placing ND filters before the two RFPDs to avoid saturation effects which become obvious when we lock PRMI. We decided to investigate further by the following tests:

  • Remove ND filters and lower the DC transimpedances to ~ 50 V/A
  • Check for scattering from suspended optics, e.g. by injecting a line at ITM PIT/YAW and look at the BH44/BH55 demodulated spectra
  • Check for PRCL sensing by BH44/BH55, e.g. by measuring the transfer function and/or running a simulation in finesse.
  • Check the RF spectra for the signals entering the IQ demod boards (including the 44 and 55 MHz LOs).

DC transimpedance modifications

The first thing we did was change the DC transimpedances of both RFPDs. After removing them from the table, we checked the schematics for 40m RFPDs on the wiki. The DC transimpedance for these gold RFPDs (D980454-v1-C) is estimated as (R22*(1+R13/R23), where these resistors are located around the follower and non-inverting amplifier stages along the DC output traces. After opening the two RFPDs and taking photos of the circuits before any changes (Attachment #1-2), we estimated the DC transimpedances from the measured values for R22, R23 and R13 and summarized them below:

Before R13 R22 R23 Est. DC transimpedance
BH44 8.2 kOhm 10.4 Ohm 99.9 Ohm ~ 864.05 V/A
BH55 99.9 kOhm 12.6 Ohm 102.7 Ohm ~ 12.26 kV/A

The changes were made on R13 (photos in Attachments #2-3) and the final values summarized below:

Before R13 R22 R23 Est. DC transimpedance
BH44 402.4 Ohm 10.4 Ohm 99.9 Ohm ~ 52.29 V/A
BH55 309.5 Ohm 12.6 Ohm 102.7 Ohm

~ 50.57 V/A

All changes have been summarized and recorded in the wiki. The ND filters were set to 0.04 (minimum attenuation) and RFPDs reinstalled.

Next steps:

Continue investigating these items:

  • Remove ND filters and lower the DC transimpedances to ~ 50 V/A
  • Check for scattering from suspended optics, e.g. by injecting a line at ITM PIT/YAW and look at the BH44/BH55 demodulated spectra
  • Check for PRCL sensing by BH44/BH55, e.g. by measuring the transfer function and/or running a simulation in finesse.
  • Check the RF spectra for the signals entering the IQ demod boards (including the 44 and 55 MHz LOs).
Attachment 1: PXL_20230524_191008053~2.jpg
Attachment 2: PXL_20230524_192525594~2.jpg
Attachment 3: PXL_20230524_193122794~2.jpg
Attachment 4: PXL_20230524_194225616~2.jpg
  17599   Wed May 24 11:50:34 2023 JCSummarySEISTACIS

[Mayank, JC]

STACIS Vibration Cancellation Isolators contain a PCB board called the Compensator board. These are boards that "allow you to control the feedback to the PZT stacks." The board is essentially held up by the 2 rear plugs and 3 screws on the front rim (Highlighted in Yellow). You don't need to disassemble the entire islotar to remove this, you just need to loosen the tension screws and pull out softly. Attachment #4 shows the seat made for the board to be placed, highlighted in Green. When placing the board back into its original position make sure in slips into this slit nicely. The extender/compensator board is part of the STACIS Isolator and each Isolator should have this. Each board seems to haver it's own serial # but not an actual part #. On this board, the S/N is 033509.

Attachment 1: IMG_5633.jpeg
Attachment 2: IMG_5634.jpeg
Attachment 3: IMG_5638.jpeg
Attachment 4: IMG_5635.jpeg
  17598   Fri May 19 15:25:00 2023 MayankUpdatePSLPSL tripped - removed internal fans

We removed the PSL controller internal (broken) fans after it tripped due to overheat.


[Mayank, Radhika]

While aligning Xarm I noticed sudden loss of beam. On Radhikas suggestion we cheked the PSL and found out that the PSL controller was in off state (No lights on front and back panel). We restored the situation by unplugging and replugging the power cord. The PSL worked fine for a few minutes (~ 30 ) and then tripped again.This time the front panel  OFF light was on . See attached image (Attachment #1).


[Paco, Mayank, Koji-remote]

We disconnected the PSL controller and took this opportunity to investigate the controller's internal cooling mechanism. After disassembling the top panel of the chassis, we saw there are two SUNON - KD1205PHB2 fans meant to run at 12 VDC (1.7 W) connected to the bottom pcb inside the controller. After disconnecting them from this board, we tested them with an externally supplied dc voltage and confirmed they no longer worked. We noted the cooling mechanism is based on a long aluminum heat sink to which most ICs are attached, and the fans are meant to provide airflow towards the rear aperture on the chassis. We followed Koji's suggestion and for now, removed the damaged components (detailed pictures of this operation have been posted in a google photos album elsewhere) to allow heat to flow out more easily.  We reassembled the controller chassis and reinstalled it with the external fan providing the necessary airflow to prevent the unit from tripping again due to overheating. Then we turned on PSL and recovered PMC and IMC locks.


We took a C1:IOO-MC_F_DQ trace after this work to confirm our earlier findings; the trace is attached in Attachment #2. The noise bumps are present as expected. This is still not a desirable configuration so next step would be replacing the external fan, or even better, find the appropriate spare of the internal units and berid the external one.

Attachment 1: 20230519_123659.jpg
Attachment 2: afterfans_PSLcontroller_Screenshot_2023-05-19_15-48-04.png
  17597   Fri May 19 13:25:03 2023 KojiUpdatePSLMCF Noise

This is super! And now is the time to replace the internal fan!


  17595   Fri May 19 09:23:58 2023 PacoUpdate MCF Noise

The fan behind the PSL controller is injecting excess band limited noise angry


While doing noise hunting to improve the BHD lock stability, we noticed peculiar noise bumps in the BH44 error point near (but not exactly at) the even line-harmonics (for example 120 Hz, 240 Hz, ...). Other channels such as C1:HPC-BHDC_SUM, C1:LSC-PRCL_IN1, or even C1:LSC-XARM_IN1 didn't show these features, so we looked at C1:IOO-MC_F_DQ (which represents the free running laser noise above 100 Hz) and to our surprise found this excess noise!

Noise hunting around PSL

Since this noise is present upstream, we decided to hunt around using C1:IOO-MC_F_DQ. We set up a diaggui measurement to do some "live demodulation" as suggested by Koji in order to understand the nature of this noise. In order to get some "video bandwidth" we set up a power spectrum measurement from 114 Hz to 140 Hz (to monitor the usual 120 Hz line noise peak) with a bandwidth of 1 Hz. A single exponential average gave us the 1 Hz narrow spectrum in "real time", from which we noticed its nonstationary character. The band limited excess noise is the result of a peak hovering in the range of 125 to 131 Hz. With this diagnostic set up, we started hunting for its source.

  1. We checked the fan behind the PSL controller (Attachment #1). 
    1. After disconnecting the molex powering it with +15 VDC the noise dissappeared!

To show the impact in the complete noise spectrum, we took a 10 fixed average measurement with and without the fan being on. The result is in Attachement #2. The spectra are shown along with their rms, which is significantly reduced when the fan is off near the 100 Hz frequency band (where these bumps appear). Anyways, we have left the fan on because the PSL controller needs it so the problem remains, but we have at least identified the source.

Attachment 1: PXL_20230519_162346524.jpg
Attachment 2: MC_Fnoisehunting_Screenshot_2023-05-19_09-27-03.png
  17594   Wed May 17 12:09:11 2023 YehonathanUpdateElectronicsPreping for new coil drivers commissioning in 1X4

It's time to start commissioning the new coil drivers. The Acromag box is already there but it needs to be modified.

The idea is to take the channel configuration from C1AUXEY that controls a single suspension - ETMY and apply it for each suspension in 1X4, that is PRM, BS, ITMX, ITMY.

For this, we need the following items

Item # per SUS # Total
DB9 Front panels 2 8
Optical isolators 4 16
DB9M feedthrough 6 24
DB9F feedthrough 5 20
DB9 Cables ? ?
EnableMON BIO channels 5 20

Currently, there are 8 spare BIO channels in the existing Acromag, we will need 12 more which requires a new BIO Acromag.

Wiring feedthrough spreadsheet coming soon.



  17593   Tue May 16 08:42:14 2023 PacoUpdateASCFPMI differential ASC - II

We aligned the AS WFS and measured some angular motion from ETMX

This work is done after IMC WFS offsets are offloaded and the WFS loops are turned off. Then, the flipper mirror M4 in the IMC WFS path is flipped up to feed the AS beam into its path. We also connected the AS WFS demod boards for both heads.

[JC, Paco]

We continued to get the AS WFS going. We added two lenses with the help of JC (f1~500 mm and f2~1000 mm) to have control over the minimum waist and its position downstream. In practice, we placed the lenses such that the beam waist lands close to the last lens before WFS1, giving a reasonable beamspot at both WFS1 WFS2 heads. These changes are reflected by the picture on Attachment #1. The beam sizes will sure need careful optimization to sense the Differential/Common ARM angular motion due to ITMs and ETMs, but for now we decided to move forward.

[Mayank, Paco]

We locked FPMI and use the WFS LOCKINs to inject a 21.173 Hz line into ETMX-PIT. Then, we look at the AS11-WFS signals using diaggui to identify any measurable signal. We see the line coming into a combination of channels C1:ASC-DHARD_PIT_IN1, C1:ASC-DHARD_YAW_IN1, C1:ASC-DSOFT_PIT_IN1, and C1:ASC-DSOFT_YAW_IN1 as shown by Attachment #2.

Attachment 1: PXL_20230515_173719320~2.jpg
Attachment 2: ASWFS_test0_Screenshot_2023-05-16_18-38-39.png
  17592   Mon May 15 18:34:05 2023 PacoSummaryLSCLocked PRMI in carrier and LO phase with BH44 and achieved handoff to BHDC_DIFF

[Yuta, Paco]

We locked PRMI-BHD (LO phase was controlled using BH44_Q) cool

Today we worked with PRMI carrier locked using AS55_Q and REFL11_I (to control MICH and PRCL respectively).

PRCL and MICH displacement calibration

We calibrated the PRCL and MICH displacements. This time we injected lines on (ITMX - ITMY) for MICH and PRM for PRCL. The optical gains were found to be

  • (ITMX - ITMY) to AS55_Q = 2.04e10 counts / m
  • PRM to REFL11_I = 1.66e12 counts / m

We added these into the C1:CAL_MICH_CINV and C1:CAL_PRCL_CINV filters on the calibration model.

PRMI-BHD handoff

After the lock was established and the alignment refined, we tried locking the homodyne phase angle using BH55_Q. We could not close the LO_PHASE loop with this sensor, so we resorted to using the BH44_Q. To do this we actually changed a few things:

  1. The BH44 whitening filter gain was lowered from +39 dB to +21 dB.
  2. Rotated the ND filter wheel to avoid saturation on the BH44 RFPD from 0.5 to 1.0. This corresponds to a change of ~33% in the incident BH44 light.

While we managed to lock BH44 by actuating on LO1, the lock was not very robust (typical lock acquistion using FM5 and FM8)... so we switched to actuating on AS4 which made the LO PHASE loop slightly more robust.

In preparation for handoff, we turned on a line at 211.11 Hz (MICH osc) and demodulated the BHDC_DIFF to estimate the sensing matrix element.

  • BHDC_DIFF to AS55_Q ~ 25

After using this number to rescale the MICH_B error point, we handed off from MICH_A (under AS55_Q control) to BHDC_DIFF. Our lock stretch covered the following gpstimes:

  • PRMI-BHD lock = 1368235235 to 1368235264

During the lock stretch above, we managed to take some noise spectra for the calibrated MICH and PRCL displacements. Attachment #1 shows the comparison between PRMI and PRMI-BHD configurations.

Discussion cool

  • Looking closely into Attachment #1 you'll find a *BH44_Q trace in green. This trace represents the uncalibrated LO phase error point. We measured the UGF to be < 20 Hz (C1:HPC-LO_PHASE_GAIN=1.2), so above 20 Hz, this trace is shown just as a guide for the noise shape. It would seem that the MICH displacement in PRMI-BHD readout is getting its shape from this noise and therefore might be limited by it.

Next steps

  • Calibrate LO phase at BH44 and see if it scales as predicted by our calculations.
  • Optimize BH44 control; why can't we lock this phase for longer?
  • Noise budget.
Attachment 1: prmibhd_Screenshot_2023-05-16_01-51-52.png
  17591   Sat May 13 11:37:41 2023 ranaUpdateGeneralStripTool -> NDscope: PSL on wall

As a test, I have replaced the PSL StripTool on the north wall of the control room with a nearly equivalent NDScope display. It is plotting the real time second trend along with min/max values. Let's try this out for awhile, and if its bad we can just close the window.

FYI, the striptool machine, zita, has a mis-configured network setup so that its not getting a useful nameserver. So for now, its running on allegra through ssh -Y. We should put the zita network thing on some sort of issue tracker. Maybe we can have tickets and issues like various companies use for tech support? This could cover all of our main lab work and help us keep track of little problems like this.

Attachment 1: Screenshot_2023-05-13_11-45-47.png
  17590   Thu May 11 12:05:24 2023 ranaUpdateBHDUpdated PRMI AS55+REFL11 noise budget

Is the A2L coming from the optical lever feedback? If so, we can make a 30 Hz ELP to cut it off by 60 Hz.

  17589   Wed May 10 17:11:34 2023 PacoUpdateASCFPMI differential ASC - I

I began commissioning the AS WFS for (PR)FPMI configurations

The main goal of this work is to close some ASC feedback loops during FPMI, or PRFPMI configurations to make locks more robust and their acquisition reliable. The running hypothesis is that angle to length coupling of the differential arms is increasing the rms and therefore straining the LSC controls... Today I began working on this, and unfortunately didn't make a lot of progress due to hardware hurdles, but the nominal plan is:

  • Stop IMC WFS and hijack the RFQPD heads for sensing -- WORK IN PROGRESS
    • We can temporarily break the IMC WFS loops to work on this upgrade, but in the future we would like to have at least one head (WFS1 or WFS2?) + transmission QPD to control IMC while the other head is our AS WFS.
    • Anchal already commissioned the AS WFS electronics and models. He also installed a couple of flipper mirrors at the Vertex table that pick the whole AS beam (otherwise going into the AS camera and ASDC, AS55, and AS110 PDs).
      • While this allows single ARM cavity ASC, we can't control MICH using our AS55 error signals.
      • I found that a beam was picked off along the AS110 path for another WFS head (currently unused), so after moving the head out of the way, I installed a mirror that sends it all the way to the IMC WFS heads area. The configuration before and after is summarized in Attachments #1-3.
      • The beam will need profiling again, but this doesn't destroy any of Anchal's ARM ASC alignment, just blocks it so we can recover it, so I think it's a good solution.
  • Lock FPMI and measure sensing matrix -- PENDING
  • Close loop, aim for gain of 10 at 10 Hz, then roll-off (e.g. IMC WFS) -- PENDING (RXA: G = 10 @ 1 Hz. G = 10 @ 10 Hz would be too spicy)


Attachment #1 before the changes were done

  • The red beam path indicates the nominal AS beam path
  • The purple beam path indicates the AS110 beam path.
  • The blue beam path indicates the unused, AS WFS (?) beam path.

Attachment #2-3 after the changes were done

  • The blue beam indicates the newly picked AS WFS beam path.
  • The yellow beam indicates the ARM AS WFS alternative path (installed by Anchal, controlled by flipper mirrors).
Attachment 1: PXL_20230510_233850237~2.jpg
Attachment 2: PXL_20230511_000946357~2.jpg
Attachment 3: PXL_20230511_000941172~2.jpg
  17588   Wed May 10 11:49:34 2023 YehonathanUpdateBHDUpdated PRMI AS55+REFL11 noise budget

I added input noises and angle to length coupling to the noise budget.

I added ADC and whitening filters noise contributions. The ADC noise is assumed to be 1uV/sqrtHz and the whitening noises were measured before in elog 17582. I use the measured whitening filter (elog   17584 ) to get the signal referred noise and calibrate.

The angle-to-length coupling is computed by taking the suppressed OpLev noise spectra of ITMX, ITMY, and BS and converting them to length noise by using the recently measured coupling coefficients in ELOG   17583 

Attachment 1: Quick_PRMI_noise_budget.pdf
  17587   Tue May 9 21:02:55 2023 RadhikaUpdateALSXEND green PDH controller

XAUX laser locked with Moku:Go controller

The analog zeros and poles used to design this filter were:

zeros = [-18849.55592154, -18849.55592154]
poles = [-125.66370614, -238.76104167, -100530.96491487]
gain = 3000

Attachment 1 shows the resulting digital SOS filter (sampling rate: 3.9 MHz) compared to the measured uPDH servo transfer function (loop closed). The filter design was loaded on the Moku:Go.

Lock acquisition

I locked the AUX laser with the uPDH servo box and maximized its transmission to ~0.8. I then fed the Moku digital filter output to the PZT and the laser was able to catch lock. However, the max green transmission I could achieve using the Moku controller was 0.5. Attachment 2 is a screenshot of the green transmission ndscope during a lock sequence.

I measured the OLTF of the loop by injecting an excitation at the error point. An SR560 was used to sum the error signal with the excitation. The Moku multi-instrument mode was configured with the Frequency Response Analyzer and Digital Filter Box; it was able to source the excitation and take a transfer function measurement of error signal / (error signal + excitation), while keeping the loop closed.

The OLTF measurement [Attachment 3] points to a loop UGF of ~4 kHz, and phase margin of ~70 deg. An optimal controller would be able to boost the gain around the UGF without changing the phase too much (lag compensator)?

Attachment 1: PDHservoTF_eyeballZerosPoles.pdf
Attachment 2: IMG_4721.JPG
Attachment 3: XEND_AUX_Moku_OLTF.pdf
  17586   Tue May 9 12:06:35 2023 RadhikaUpdateALSXEND green PDH controller

[Mayank, Radhika]

I retook a transfer function measurement of the uPDH servo closed-loop (using the SR560 to simulate a cavity pole) [Attachment 1]. While some coherence is lost at low frequencies, the servo does not appear to be saturating. Moving forward this measurement is used to design a digital filter that can replicate the uPDH servo box response. *Note: for now the chosen sampling frequency for the discrete filters is 61.04 kHz, the lowest sampling frequency setting of the Moku:Go.

We performed a low-order fit of the TF using vectfit. Vectfit always seems to return 1 more zero than pole - this results in an "improper" transfer function that causes any transformation to the z-domain to fail. Mayank took the fitted zeros and poles from vectfit and manually removed one of the zeros. After transforming the zeros and poles to the z-domain (using control.matlab.c2d), we noticed multiple resonances around 100 kHz that reached 10-20 dB. We decided to estimate poles and zeros by eye instead of using vectfit. 

2 zeros and 2 poles were selected by eye to get an estimated fit in the s-domain. Using continous-to-discrete transforms (tried scipy.signal.bilinear and control.matlab.c2d) resulted in unstable controller responses. Attachment 2 shows the original TF measurement with the designed analog filter and the resulting digital filter. The orange 'x's and 'o's mark the poles and zeros used. The digital filter contains many high-frequencies resonances, the most significant at the sampling frequency, 61.04 kHz, reaching 20 dB. Next we tried to manually load the analog ZPK coefficients into Foton. This resulted in the same digital filter as the python s-domain to z-domain functions [Attachment 3].

**UPDATE** Now looking back it's clear that the high-frequency response is limited by the sampling rate. I will redo this for the highest Moku:Go sampling rate of 3.9 MHz.

Attachment 1: PDHservoTF.pdf
Attachment 2: PDHservoTF_eyeballZerosPoles.pdf
Attachment 3: eyeball_uPDH_fit.pdf
  17585   Tue May 9 11:32:04 2023 YehonathanUpdateBHDWhitening TF measurements

We forgot to take a reference TF measurement by looping the SR785 on itself using the same BNC cables used for the actual measurement. I took this measurement today (attachment 1). As can be seen, there is a significant delay in the SR785 + cables themselves.

I also retook some measurements on the AS5_I whitening channel for various gains. Being careful with the excitation level and the channel range on the SR785 to avoid saturation I was also able to see low-frequency gains higher than 18dB so that problem is gone too. The results are shown in attachment 2 with the reference phase subtracted from the measurements.

Attachment 1: Reference_TF.pdf
Attachment 2: Whitening_TFs_AS55_I.pdf
  17584   Mon May 8 17:05:30 2023 YehonathanUpdateBHDWhitening TF measurements

{Mayank, Yehonathan}

We measured today the TFs of the whitening boards. We measured in particular REFL11 I/Q and AS55 I/Q channels using SR785.

There seems to be an issue with turning on whitening gain bigger than 18dB. In all our measurements, when the whitening filter was off the TF was flat and had the right gain. However, when we turned the whitening on, the measured TFs for gains higher than 18 dB would like exactly like as if the whitening gain was 18 dB. This happened in all channels that were measured and across two separate whitening filter boards.

Also, it was hard to measure both low and high-frequency parts of the TFs when the gain was high. The gain difference should be normally 40 dB but for higher gains it seems smaller. We verified that at higher gain level the high-frequency response was dependant on the ecxitation level meaning we had some saturation there.


Attachment 1: Whitening_TFs_REFL11_I.pdf
Attachment 2: Whitening_TFs_REFL11_Q.pdf
Attachment 3: Whitening_TFs_AS55_I.pdf
Attachment 4: Whitening_TFs_AS55_Q.pdf
  17583   Thu May 4 17:14:15 2023 PacoSummaryLSCPRMI (MICH and PRCL) calibrated displacement and BS angle to MICH couplings

[Mayank, Paco]

We calibrated PRCL displacement using MICH and estimated (?) BS angle to MICH couplings

Expt 1 - calibration of displacements for PRMI

We injected calibration lines at four different frequencies (211.11, 313.13, 575.17 and 1418.93) into (ITMY) under PRMI configuration and recorded the calibrated MICH displacement (C1:CAL-MICH_W_OUT) and uncalibrated PRCL displacement (C1:CAL-PRCL_W_OUT). The exctation amplitudes were (100,150,250 and 1000 cts) respectively.

The ratio of intensities of calibration lines peak in the two configurations are used to caliberate the PRCL displacement (C1:CAL-PRCL_W_OUT). Basically, if MICH = Lx - Ly and PRCL = Lp + 0.5(Lx + Ly), then PRCL displacement from Ly is half of MICH displacement.

The estimated optical gain (C_INV) was 6.41e-11 cts/m, which we added into FM3 of PRCL calibration filter bank. Attachment #1 shows the calibrated displacement spectra.

Expt 2 - angle to length couplings

After calibrating PRCL displacement, we tried to estimate the angle to length coupling from BS PIT/YAW to MICH under the PRMI configuartion. We started by injecting a broadband guassian noise (3000 cts amplitude in the 7-17 Hz band for PIT, and 17-27 Hz band for YAW) through an 8th order Cheby II filter with 80 dB attn to shape the noise before injecting into BS ASCPIT/ASCYAW.

We then looked at the increased displacement noise in the calibrated MICH and PRCL displacements. Assuming a naive 1 urad/count / f^2 of BS angular actuation strengths in both PIT/YAW, we estimate the couplings to be:

  • BS PIT to MICH = 0.12 nm / urad @ 13 Hz
  • BS YAW to MICH = 0.19 nm / urad @ 22 Hz
    • BS PIT to PRCL = 0.38 nm / urad @ 13 Hz
  • BS YAW to PRCL = 0.08 nm / urad @ 22 Hz

Seems a bit too large... blush bogus? Attachment #2 summarizes these measurements.

Attachment 1: calibrated_MICHPRCL_dispScreenshot_2023-05-04_18-46-05.png
Attachment 2: BSASC_noise_toMICHScreenshot_2023-05-04_18-59-32.png
  17582   Wed May 3 18:40:50 2023 YehonathanUpdateBHDWhitening noises measurements

{Mayank, Yehonathan}

We measured the noise at the WF1 (REFL11) and WF2 (AS55) boards at the LSC rack with and without whitening filter. We switch the filter on and off by switching off and on the unwhitening in the PDs filter bank.

Attachment 1 shows the measurements.

Attachment 2 shows the ratio between the noise with and without whitening filter. I also plot the inverse of the unwhitening MEDM filter (all the unWhite filters were the same). I tune the gain of that filter to match the ratio of the AS55 whitening noises.

This is because I couldn't match the ratio of the REFL11 noises.

Moreover, the overall gain doesn't make sense to me. AS55 whitening has a gain of 24db and REFL11 has a gain of 18db. I'm not entirely sure where these values should show up. Also seems like REFL11 whitening has more gain than AS55 whitening. Will have to investigate more tomorrow.

Attachment 1: Whitening_noises.pdf
Attachment 2: Whitening_noises_on_off_ratios.pdf
  17581   Wed May 3 16:24:07 2023 PacoSummaryLSCAttenuated BHD RFPD paths

[Yuta, Paco]

We attenuated RFPD BHD paths to prevent saturation

To prevent saturating RPFDs, we added ND filters along BH44 and BH55 paths. We calculated the optimal filters to be used by taking into account the previously measured DC levels at both RFPDs as well as their DC transimpedances.

BH55 (S/N 117, former POP55) DC transimpedance is reported to be 10010 V/A. Assuming a responsivity of 0.8 A/V, we expect 8008 V/W at DC. When PRMI is locked, we have measured 10 mW of light incident on this PD such that it gets saturated. Then we installed an OD ~ 1 filter to drop the power to 1 mW such that at most we get 8 VDC (< 15 VDC rail).

BH44 (S/N 115, former unknown) DC transimpedance is estimated to be 645 V/A. Assuming 0.8 A/V, we expect 516 V/W at DC. This RFPD gets 27 mW when PRMI is locked, giving a slightly saturated PD> Then we installed an OD ~ 0.5 filter to drop the power to ~ 8 mW such that we at most get 4 VDC (< 15 VDC rail).

  17580   Wed May 3 15:06:44 2023 yutaSummaryLSCPOP attenuation and PRMI PRG estimate

[Paco, Yuta]

Measured power recycling gain at POP is 10(2), consistent with our expectation.

We measured power at POP with ITMY single bounce and estimated power recycling gain in PRMI.
As POP RFPD (Thorlabs PDA10CF; used for POPDC, POP22, POP110) was saturating, we attenuated the input power by OD2.5 ND filter.
Power recycling gain was estimated to be 10(2), roughly consistent with our expectation of 13.2 (40m/17532).

What we did:
 - Realigned POP path in ITMX table after aligning the IFO. It turned out that when POP power measurements were done in 40m/17532, POP was not well aligned.
 - We measured the power with ITMY single bounce at POP right after the viewport and in front of POP RFPD.
 - We also measured counts in C1:LSC-POPDC_OUT under ITMY single bounce, PRMI carrier locked, and MICH locked with PRM misaligned, with different ND filters.


IFO configuration Where Measured power [mW] C1:LSC-POPDC_OUT [counts]
ITMY single bounce POP total 0.224(5) Expected 0.240 [a] N/A
  POP RFPD (no ND filter) 0.108(3) 437(2)
  POP RFPD (OD1) N/A 29.9(1), which is 7.4 uW [b]
  POP RFPD (OD2+OD0.5) N/A 2.4(5), which is 0.6 uW [b]
PRMI carrier POP RFPD (no ND filter) N/A 13160 (saturated)
  POP RFPD (OD1) N/A 12300(300) (saturated)
  POP RFPD (OD2+OD0.5) N/A 1600(300), which is 0.40 mW [b]
MICH POP RFPD (OD2+OD0.5) N/A 9.0(6), which is 2.2 uW [b]

 - Estimated power recycling gain is 1600(300) / (9.0(6) / 5.637%) = 10(2) .

Expected values:
 - Expected power using PSL output of 890 mW (measured in elog 40m/17390) under ITMY single bounce at POP is the following, and is consistent with the measurement.
[a] 890 mW * 0.9 (IMC transmission?) * 5.637%(PRM) * (1-2.2%)(PR2) * 50%(BS) * (1-1.384%)(ITMY) * 50%(BS) * 2.2%(PR2) = 0.240 mW

 - Calibration for C1:LSC-POPDC_OUT into power at POP RFPD is
[b] 437 counts / 0.108 mW = 4.0e3 counts/W.

 - Thorlabs PDA10CF has a transimpedance gain of 1e4 V/A and output range of 0-5 V. So, the saturation happens at 5 V / (1e4 V/A * 0.8 A/W) = 0.625 mW. We ended up attenuating POP RFPD with OD2.5 to make it not saturating (0.4 mW on the PD with PRMI carrier lock).

  17579   Wed May 3 12:11:52 2023 YehonathanUpdateBHDUpdated noise budget with measured noise and OLTF

{Paco, Yehonathan, Yuta}

Paco and Yuta locked PRMI carrier and I took the MICH OLTF measurement (attachment 1).

I downloaded 300secs of C1:LSC-MICH_IN1_DQ from when the PRMI was locked yesterday and calibrated it with the OLTF. I plot it together with the noise budget (attachment 2).

Attachment 1: PRMI_carrier_MICH_OLTF.pdf
Attachment 2: Quick_PRMI_noise_budget.pdf
  17578   Tue May 2 17:33:53 2023 MayankSummaryLSCLocked PRMI in carrier for an hour with LO phase controlled using BH55

[Mayank, Radhika, Paco]

We locked PRMI for a solid hour devil and controlled LO phase angle using BH55_Q at higher power.

After Radhika aligned the IFO for us, and recovered the PRMI flashing (using REFLDC), we attempted a PRMI lock. After a few trials we succeeded.

Control parameters: see Attachment #1, basically REFL11_I to PRCL, and AS55_Q to MICH (error points) and actuation as previous locks with PRCL to PRMand MICH to 0.5 * BS - 0.33 * PRM.

The gains are slightly different, and in particular PRCL gain was increased from -0.07 to -0.09 after an OLTF estimated the UGF could be increased to > 120 Hz (Attachment #2 shows the measured OLTF) Do note we ended up disabling the FM1 on PRCL LSC filter bank (a boost) because we thought the loop was unstable when it got triggered ON. Finally, we took a quick noise spectrum of PRMI, and we have yet to calibrate it.

We also managed to reduce the AS_DC level from 0.4 to 0.1. We first tried to add an offset to MICH error point but the trick was to align the ITMX ITMY differential yaw.

Lock start Time: 1367107965 --> 1367111565

While PRMI was locked, we quickly locked homodyne angle using BH55_Q. For this the demod angle was optimized from -60 deg to 55.374 deg. The lock was acquired using FM5 and FM8 with a gain of -0.75. Attachment #3 shows the "calibrated" noise budget of the LO phase under this configuration. The main difference with respect to the previous  budget is in the "RIN" which we now realize is not relative... therefore the increase in this budget. We will revisit this calibration later.

- Next steps

  • Re-calibrate LO phase noise with high power
  • Investigate BH44 control
  • Calibrate PRMI noise for budget
  • Estimate LO phase sensitivities at MICH vs PRMI


Attachment 1: Screenshot_2023-05-02_17-40-06.png
Attachment 2: PRCL_OLTF_Screenshot_2023-05-02_18-10-28.png
Attachment 3: PRMI_LO_phase_BH55_Q_Screenshot_2023-05-02_18-06-59.png
  17577   Tue May 2 10:39:49 2023 JCConfigurationIMCBad Alignment

It took a while, but I was finally able to align IMC. It seems like WFS has been getting really whacky lately when we arent in the lab watching it angry. The picture attached has an arrow of where the beam spot was at this morning

Attachment 1: BB26DF83-5B6A-4BC1-A2A0-6E18E1A2B91E.jpeg
  17575   Mon May 1 16:51:20 2023 PacoSummaryASCIFO alignment in bad shape

[Yuta, Mayank, JC, Paco]

We fixed the IFO nominal alignment.

  1. Yuta and Mayank had worked all morning and into the early afternoon to try and recover alignment. We noticed a few things seemed off:
    1. ASS loops still wouldn't work.
    2. ITMX oplev loops were weirdly unstable, but we suspected this had to do with the recent HeNe replacement saga.
      1. Paco revisited the setup, suspecting a lens near the QPD was wreaking havoc. This was not the case, but the setup now resembles the previous one. Furthermore, an iris was placed in the input ITMX OpLev path.
    3. Using AUX (green) beams as a reference didn't really work well.
  2. We decided to check the SUS rack electronics where some noise measurements were carried out last week.
  3. We found out that between the DW boards from ITMX and ITMY to the coil driver units for ITMX and ITMY there were two crossed wires at least (Ch4).
  4. Yuta and Paco reconnected all channels between the ITMX DW to ITMX Coil driver and ITMY DW to ITMY Coil driver units,
    1. All wires seemed to be crossed when going up the rack... suspicious...
  5. The first damping test failed, and we realized placing an offset in ITMY coils affected ITMX, so the DW board units were probably flipped because they were probably mislabeled!
  6. Yuta and JC swapped the cables again, and we ran a coil by coil test before damping. After this ITMs were successfully damped, so the labels were corrected in the AI + DW boards to prevent this confusion in the future.

  • IFO alignment was recovered by Yuta and Paco.
    • ASS now works again!
  • JC and Mayank aligned OpLevs
    • Loops were closed and remained stable in ITMs.

Attachment #1 shows the alignment state at the end of this work.

Attachment 1: alignmentScreenshot_2023-05-01_17-06-41.png
  17574   Mon May 1 14:45:48 2023 MayankSummaryLSCAttenuated BHD DC Beam

[Yuta, Mayank]

UPDATE: It turned out that the pair of 0.3 OD ND filters we used were not matched. So we replaced them with new 0.5 OD NENIR05A-C from thorlabs. Now both the photodiodes give similar count.

Counts Before OD After OD
C1:HPC-BHDC_A_OUT 114.5 counts 36.4 counts
C1:HPC-BHDC_B_OUT 111.5 counts 35.1 counts



The DC power incident on the PDs is 74 mW which may cause saturation. We attenuated the beam going to BHD_DC Photodiodes using ND filter of OD 0.3 which gives attenuation of 0.5. 

Attachment 1: 20230501_144152.jpg
  17573   Mon May 1 08:57:45 2023 JCConfigurationIMCBad Alignment

I had to realign the IMC today. When I came in, it was very bad, not much flashing at all, I had to do it from scratch. CH01 Camera on MON7 in the control room is completely white. Did the camera go out over the weekend? I will come back to poke around later, I have headed over to WB for a moment and will be back soon. sitemapsi

Attachment 1: Screenshot_2023-05-01_15-55-33.png
ELOG V3.1.3-