LOG-IN
Displaying reports 321-340 of 3128.Go to page Start 13 14 15 16 17 18 19 20 21 End
Birefringence mitigation (General)
Print this report.
ShalikaSingh - 22:34, Monday 12 June 2023 (3276)Get code to link to this report
Second LC retardance characterization

The retardance of the second LC (oriented along its fast axis) was observed 

1. using cross polarizer technique
2. for 20 voltage sweeps with 0.1Hz sweep frequency.
 
It was found that the maximum and minimum retardance was 988.99 nm and 15.7 nm at the temperature of 30 deg. The rms of error is 0.43 nm. See Fig 1 to understand more about the measurements. 
 
[see elog 3210 to understand more about fitting functions used]
 
foldername= "C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\LC2_calibration data\Retardance"
filename="Mon, Jun 12, 2023 9-09-19 PM.txt"
Images attached to this report
3276_20230612153506_lc2retardancefit.png
Birefringence mitigation (General)
Print this report.
ShalikaSingh - 21:07, Monday 12 June 2023 (3275)Get code to link to this report
LC fast axis measurement Finalised

We were able to align LC perfectly to its axis.

1. We were having issues with our input polarization. It was observed that it didn't remain linear over long time period even though it was tuned using HWP and QWP at the start. So we placed a GT10C Thorlabs polarizer. The ellipticity after the polarizer was 0.09deg and power was around 1mW.
 
2. We fine-tuned our input polarization using HWP and QWP after it too to obtain linear polarization which remained undeviated over several hours of measurement.
 
3. The fast axis was measured and found to be 183.63deg so we rotated by 3.63 degrees and measured again to get Fig 2.
 
4. LC 2 is aligned with its fast axis and we obtained the final alignment of 179.96+/-0.39deg as shown in Fig 2 and Fig 3.
 
The position of LC as 3.63-0.04=3.59 degree has been finalised for now.
 
Specs:
LC temperature=30 deg
measurement resolution=13 deg
folder name
Fig 1--r'C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\LC2_calibration data\fast axis 15'
Fig 2--r'C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\LC2_calibration data\fast axis 16'
Images attached to this report
3275_20230612140738_lc2fastaxis150.png 3275_20230612140744_lc2fastaxis.png 3275_20230612140751_orientation21v.png
Birefringence mitigation (General)
Print this report.
ShalikaSingh - 19:57, Thursday 08 June 2023 (3273)Get code to link to this report
The Fast and Furious (Sequel 12)

Fast axis measurement of LC2. 

 

Investigating issues mentioned in 3269, I removed the LC and found that somehow the hwp and qwp before lc were not transmitting linear polarization. The beam was displaced in the yaw before even entering the box. This was corrected. This explains the absurd measurement of elog 3262

 

Seeing Fig 3 from elog 3269 (where the initial position was 13.58) I moved the LC by 15.41 degrees in antiCW and so the initial position was 358.17 deg. The measurement was done with this and the fast axis orientation obtained is as shown in Fig 1. This was done by 9deg resolution for rotation.

 

Since the beam changed its obvious that we can't compare this present results with past one. Rotating by 12.15 degree now should align LC to the fast axis. 

 

This fast axis measurement is becoming Mission Impossible. 

 

folder_name = r'C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\LC2_calibration data\fast axis 12'

Images attached to this report
3273_20230608125707_17.png
R&D (FilterCavity)
Print this report.
MichaelPage - 16:42, Monday 05 June 2023 (3270)Get code to link to this report
PLL phase noise

Summary

I measured the phase noise of the P-Pol PLL at 50 MHz (normal operation ~200 MHz) and of the CC PLL at 20 MHz (normal operation 7 MHz). Despite the CC PLL instability, the phase noise measurement is not so bad and basically consistent with previous measurements of PLL phase noise. I am guesing that there is an issue of glitches at the normal CC operation frequency because it is much more unstable at 7 MHz than the test frequency of 20 MHz.

Details

I measured the PLL phase noise of both the CC and PPol controls using the method outlined previously. Normally, these loops operate at 7 MHz and ~ 200 MHz, respectively, but this is for the output of the PLL control loop. In the digital system, we input 3x F for CC into DDS3 DAC0, i.e. 21 MHz -> 7 MHz, and (1/5)x F for PPol into DDS3 DAC1, i.e. 35 MHz -> 175 MHz (currently). However, the DDS3 board is mis-wired so DAC3 controls the PPol LO while DAC1 controls the homodyne. For measuring the PLL phase noise, the DDS system is cleanest below 100 MHz, so instead I measured the PPol phase noise using at 50 MHz and the CC at 20 MHz.

The principle behind the PLL phase noise measurement is described in Yuhang's thesis, pg 102. When we input a PLL beatnote and a local oscillator to a mixer at the same frequency we will be left with PLL phase noise. The power spectrum is measured in Vrms/rtHz, so to convert to rad/rtHz we must divide by a calibration factor Apk^2, where Apk is the peak to peak amplitude of the oscillating output of the mixer when the beatnote and LO are offset by some small frequency ~ 100 Hz. I use a small mixer MiniCircuits ZX05-1L-S+ which has a damage threshold of 17 dBm (50 mW at 50 Ohm). A local oscillator (either DAC0 or DAC3) goes into the LO port while the PLL [name] MON signal goes into the RF port. An SMA screw-on low pass filter is used at the output.

For the measurements I have the following inputs into the mixer:
CC 50 MHz LO 8.0 dBm, 50.000000 MHz on DDS and spectrum analyzer
PPol 50 MHz beatnote -17 dBm, 10.000000 MHz on DDS, 50.000000 MHz on spectrum analyzer
PPol 20 MHz LO 9.0 dBm, 20.000000 MHz on DDS, 19.913043 MHz on spectrum analyzer
CC 20 MHz beatnote -6 dBm, 60.000000 MHz on DDS, 20.030000 MHz on spectrum analyzer

The spectrum analyzer seems to be a bit inaccurate on peak finding. Oscillatory behaviour at the output of the mixer depends on frequency offset as set on the computer to the DDS and can be seen on the oscilloscope, rather than "as measured" on the spectrum analyzer peak finder.

For the spectral measurement I use PSD units Vrms/rtHz. I then convert to rad/rtHz using the Apk calibration factor, 0.0568 mVpk for the PPol and 0.0086 mVpk for the CC. The phase noise spectrum is shown in figure 1. They are compared with a previous measurement in September last year. It seems the CC phase noise at 20 MHz is not too bad. Both the PPol and CC loops remained locked for a long time during the test. However, the PLL lock for the CC was seen to be quite unstable at its normal operating frequency. Perhaps it is glitch noise rather than stationary noise, or maybe there is some cross coupling when operating at 7 MHz. PPol has about 50% extra noise in the range 500-2000 Hz. The difference at the lowest frequency is due to the frequency resolution of the measurement rather than the system.

Images attached to this report
3270_20230605092516_pllphaseksnip20230605162421.png
Birefringence mitigation (General)
Print this report.
ShalikaSingh - 10:51, Monday 05 June 2023 (3269)Get code to link to this report
Correction of angle for fast axis

Angle correction in analysis

The problem for angles is happening maybe because we were considering the start position of rotation as 0° (instead of the actual angle of rotator). This was removed and we consider initial angle as 0° for all measurements now to understand what's going on

1. Fig 1 from elog 3256 where measured angle is 191.43° (start point) at Temp=25°

2. Fig 2 from elog 3256 where measured angle is 193.54° (after CW rotation by 11.43°) at Temp=30°

3. Fig 3 from elog 3260 where measured angle is 195.41° (after CW rotation by 2.15°) at Temp=30°

4. Fig 4 from elog 3262 where measured angle is 183.3° (after CW rotation by 1.83°) at Temp=30°

Images attached to this report
3269_20230605035126_figure1.png 3269_20230605035129_figure2.png 3269_20230605035132_figure3.png 3269_20230605035135_figure4.png
R&D (Roberts Linkage)
Print this report.
KoheiMitsuhashi - 18:32, Sunday 04 June 2023 (3266)Get code to link to this report
Compute potential well and resonant frequency of Roberts Linkage

I computed potential well and resonant frequency of Roberts Linkage.

Both results were made by material point model.
Potential well of Roberts Linkage of which depth is 250mm was only attached. Beacuse relationship between COM position and depth are same.

Resonant frequency of Roberts Linkage of which depth are 108mm and 250mm wrere attached.
Some measuremet results of which depth is 108mm are far from material point model's ones.
Actually, I don't know certain reasons. I just wrote down some suspicious points I thought.

  • When I computed COM position,  there were mistakes.  I think it is most suspicious.
  • Material point model was made by some approximation.  That maked some gaps?!
  • I confused frequency for angular frequency.
  • Basically, results' resonant frequency are wrong.
  • Basically, material point model are wrong.
Images attached to this report
3266_20230604110602_potentialwellof250mmdepth.png 3266_20230604112904_resonantfrequencyvscompositiondepth108mm.png 3266_20230604112909_resonantfrequencyvscompositiondepth250mm.png
R&D (Roberts Linkage)
Print this report.
KoheiMitsuhashi - 17:34, Sunday 04 June 2023 (3265)Get code to link to this report
measure transfer function and Q factor of Roberts Linkage

I measured the transfer function and Q factor of Roberts Linkage of which depth is 250mm.

The results were as follows.

  Fig1 Fig2
COM position [mm] 80 37
Resonant Frequency [Hz] 0.33 0.20
Q factor 2240 ---

I measured the resonant frequency by fitting transfer function. The results were attached.

I measured Q factor by ring down curve.
I can't measured Q factor of which COM position is 37mm, because ring down curve is affected by the another axis' motion.
I tryed doing FFT to ring down curve of which COM position is 37mm. 
The result related to ring down curve were also attaced.

Images attached to this report
3265_20230604103410_12473124631252212540125311247112519124831248820230604172333.png 3265_20230604103418_12473124631252212540125311247112519124831248820230604172441.png 3265_20230604103426_12473124631252212540125311247112519124831248820230604172148.png 3265_20230604103435_12473124631252212540125311247112519124831248820230604172521.png 3265_20230604103441_12473124631252212540125311247112519124831248820230604172543.png
Birefringence mitigation (General)
Print this report.
ShalikaSingh - 20:55, Friday 02 June 2023 (3262)Get code to link to this report
Fast axis measurement of LC 2
For Aligining along Fast Axis
 
The LC was rotated by 1.83 degrees and so the initial position now was 15.41 degrees. See Fig 1 for reference, and Fiig 2 and 3 are to understand how the power at transmission changes with LC rotation.
 
Also, to better understand the axis orientation we fit the data obtained from Fig 1 to a linear function. See Fig 4 for reference. 
 
What I don't understand is how did it deviate by 18 degrees if it was just rotated by 1(that too in the opposite direction)
folder_name = r'C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\LC2_calibration data\fast axis 11'
Images attached to this report
3262_20230602134526_41.png 3262_20230602134534_41.png 3262_20230602134545_41.png 3262_20230602135351_41.png
Birefringence mitigation (General)
Print this report.
ShalikaSingh - 20:31, Friday 02 June 2023 (3263)Get code to link to this report
PID control for LC
PID control for temperature stability in LC
 
As reported in elog 3256 the tension in wires was sometimes causing an elevated temperature. So pid control for temperature has been implemented. The temperature was observed for both LCs with the laser on and was found to be fairly stable. This has been done for a temperature of 30 degrees. 
 
The PID parameter for both LCs are shown in the table
  LC 1 LC 2
P 0.53 0.55
I 0.34 0.32
D 0.21 0.27
 
The method to implement
 
1. P: I and D were made zero. P was made as low as 0.1. We see oscillations between two ranges of values. This was tuned so that the oscillations were faster and also the values were not over or undershooting. 
 
2. I: starting from 0 and increasing by a factor of 0.01 to reduce the height of fluctuations (this will reduce the range of values between which the temperature fluctuates)
 
3. D: this reduced the time duration between which the temperature fluctuated between the two values. Also, decide for how long the value stays in the desired value place without deviating. 
 
4. I and D were tuned till the least or no oscillations were observed. Although we had a logic to keep the temperature stable the temperature was deviating +/-0.09 deg. But now after PID control our temperature deviated +/-0.01 deg. We can see changes in temperature for every 0.01 change in PID parameters. 
 
5. After tuning the LC stays at the set temperature for more than 2 minutes at 0V. (deviates to +/-0.01 for <5s)
 
In PID control we intend to constrict our state (temperature in our case) to a desired value and tune the range of fluctuation and time between which fluctuation happens. Also, the PID control will help us change between temperatures without any overshoots and faster. This has also made cooling down faster. 
 
Note: because we don't need to change these parameters all the time this was done using the VIs with independent control for TC and has not been implemented in the integrated VI. 
Birefringence mitigation (General)
Print this report.
ShalikaSingh - 17:58, Monday 29 May 2023 (3260)Get code to link to this report
Fast axis of LC2
 
Aligining LC along its fast axis. 
 
1. The LC 2 axis was rotated by 2.15 degrees and this was specified as the initial angle(13.58 deg) in the analysis. The fast axis orientation obtained is as in Fig 1. 
 
2. The resolution of data is 13 degrees.
 
3. The LC was kept at a temperature of 30 degrees
 
Seems like I rotated by 2 degrees but LC rotated by 1 degree. We should rotate by remaining degree to align perfectly. 
 
folder_name = r'C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\LC2_calibration data\fast axis 10'
Images attached to this report
3260_20230529113910_58.png 3260_20230529113917_58.png 3260_20230529113926_58.png
Birefringence mitigation (General)
Print this report.
ShalikaSingh - 19:42, Thursday 25 May 2023 (3259)Get code to link to this report
VI to use both LC's together
VI to use both LC at the same time
 
1. We will ultimately be using both LCs together. Today the temperature control for both LC was added in a single VI. The speed of saving was at around 75Hz
 
2. Added global variable in subVIs (temperature controller, power meter, and polcam), instead of reading variable from them.
 
3. When I tried integrating Voltage control, the speed dropped to about ~39Hz. We need to think about how to be careful around this, as this is the main loop where we vary the voltage to induce retardance change. The main loop has several other logic and hence adding something makes it expensive.  
 
Comments related to this report
ShalikaSingh - 13:23, Tuesday 13 June 2023 (3277)

A parameter for a phase shifted voltage waveform between the two LCs has also been added. 

The VI is completely ready for use. The speed of VI (with all data saving) is 40Hz. 

Birefringence mitigation (General)
Print this report.
ShalikaSingh - 11:22, Wednesday 24 May 2023 (3256)Get code to link to this report
Fast axis Mystery of LC2

Measured Fast axis orientation of second LC

Issue solved:smiley

1. see elog 3242 for LC 1 fast axis. It was continuous (done in the PP(Parallel Polarizer) configuration)

 

2. see elog 3254 for LC 2 fast axis it was discontinuous.

 

3. We did LC 2 measurements and found Fig 1 and Fig 2 using the CP(Cross Polarizer) technique. But we used the cos function to fit it and other mistakes that are addressed below. We see that even if we moved our LC(by -11.62deg ) it seems that the LC didn't rotate at all. 

 

Mistakes we madeblushenlightened

 

1. When using the fit equation the bounds of phase were given from -4 to 4. I have changed it from 0 to 2*pi

 

2. We should use the sine function to fit cross-polarizer data and cos for Parallel polarizer. This arises from the fact that we use power to understand the position of the fast axis. So if you observe data from these two techniques like power vs. rotation. It will be shifted. 

 

3. Now, let's compare Fig 1 and Fig 3 where CP data was fit using right parameters.

 

4. we also need to consider the initial angle where we start measurement both when observing power vs rotation and analyzing fast axis orientation. When I incorporated this we could exactly see how much were we rotating the fast axis or if we rotated in the wrong direction

 

5. So when we first did a measurement with CP (shown in Fig 1) (we had a lot of data points because we did it with a 10-degree resolution). But because we were using the wrong function to fit no matter how many times we did the measurement our data looked strange

 

6. When we shifted to PP after 4 sets of measurements, we did measure with less resolution and so it looked strange. 

 

7. We can see from Fig 3 that we are supposed to move LC by 11.43 degree. so I moved LC and measured again to obtain Fig 4, Fig 5 and Fig 6.

 

8. Just to be sure that our new analysis is correct you can compare Fig 7 from elog 3242 for LC 1's fast axis.  

 

9. As a matter of fact, it's better to use CP for such measurements to see small changes too (because of small retardance range of LC at high voltage). See Fig 8 and Fig 9 for measurement done using PP. Although these measurements entailed the corrections during analysis, the data seemed strange enough to be considered. 

 

Miscellanous:

 

1. some angles were omitted during analysis (likely because the LC cable caused disruption in beam and hence strange data). Also, this won't matter because we won't use these omitted orientations during characterization. Preferably the LC will be fixed along the fast axis

 

2. Moving on, the issue of temperature rising in LC was completely unrelated to the box or laser. It was due to us using tape to fix the wire so that it doesn't move and block the beam. This tension caused an elevated temperature of 26 deg even when the laser was off, the temperature controller was off and the box was lifted. The temperature was relieved as soon as I removed the tape!

 

for PP folder_name = r'C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\LC2_calibration data\fast axis 8'

for CP folder_name = r'C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\LC2_calibration data\fast axis 9'

Images attached to this report
3256_20230524040834_lc2fastaxis2initialanalaysiswrong.png 3256_20230524040839_lc2fastaxis3initialanalaysiswrong.png 3256_20230529111652_lc2cpcorrectedlegend.png 3256_20230529111702_43.png 3256_20230529111707_43.png 3256_20230529111716_lc2fastaxis.png 3256_20230529111720_lc1.png 3256_20230529111728_4v.png 3256_20230529111735_lc2fastaxis8.png
R&D (FilterCavity)
Print this report.
MichaelPage - 00:43, Wednesday 24 May 2023 (3258)Get code to link to this report
PLL phase noise

Summary

When we were working with Yuhang in April, we noticed that the CC loop was very glitchy. I attempted to measure the CC PLL phase noise but got no signal.

 

Details

I attempted to measure PLL phase noise using the same method I did previously. To recap:

  • The PLL outputs a sine wave
  • If this is mixed with some local oscillator at the same frequency, then the output of the mixing will just be zero signal + phase noise
  • The procedure is to put [name] PLL MON into RF and a local oscillator directly from the DDS3 into LO (last time I used 7.6 dBm).
  • DDS3 outputs: Ch0 - CC LO 21 MHz, Ch1 - CC2, Ch2 - CC1, Ch3 - PPol LO 35 MHz - note that Ch1 and Ch3 are reversed compared to wiki/theses.
  • Offsetting the PLL by 100 Hz should give a signal visible on the oscilloscope at about 0.08 V

I could see that the LO was generated from the DDS board (Ch3 - 50 MHz, 9 dBm), and that the CC PLL could lock. However, no signal came out of the mixer - the spectrum analyser just showed the same as when unplugged, and putting the signal into the oscilloscope gave nothing when the RF and LO were offset by 100 Hz.

Next time I will check the mixer and cables 

Birefringence mitigation (General)
Print this report.
ShalikaSingh - 15:34, Tuesday 16 May 2023 (3255)Get code to link to this report
Comment to fast axis of second LC (Click here to view original report: 3254)

The measurement was repeated. First, I moved the LC to the new position of 337.78 degrees. Then I repeated the measurement with the angle of rotation incremented by 30 degrees. 

The issue with fast axis orientation continues. see Fig 1 and 2. It seems that there is a discontinuity at some points. This has been observed in almost all the 7 times that we did measurements. 

PS:

The data is stored in foldername= 'C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\LC2_calibration data\fast axis 7'

Images attached to this comment
3255_20230516083227_5vfastaxis7.png 3255_20230516083232_lc2fastaxischeckfastaxis7.png
Birefringence mitigation (General)
Print this report.
ShalikaSingh - 12:30, Tuesday 16 May 2023 (3254)Get code to link to this report
fast axis of second LC

[Shalika, Marc]

 

This measurement aims to find the fast axis orientation of our second LC so that we can align it correspondingly for future measurements. 

 

1. The fast axis orientation was measured using the method mentioned in elog 3242.

 

2. Our setup is inside a box and so (sometimes the laser hits the box or because of lack of air circulation) the temperature gets unstable and affects the LC. So we decide to use LC at 30 degrees. This helps us avoid any temperature fluctuations. 

 

3. The LC was rotated from 0 to 360 deg with increments of 45 degrees. 

 

4. To understand our fast axis position our data (where power is observed for the LC rotation) was fitted properly to the equations. (see Fig 1) . This fit is then used to get fast axis orientation.

 

5. The axis was found to be at -22.3 degrees (see Fig 2) and so the LC has been rotated to this position. The LC position is now 337.8 degrees

 

6. The measurement will be taken again to avoid any deviations from the best position, with 10 degree increments.

 

[we have tried taking this measurement 6 times as of now. We are a bit baffled by the mysterious nature of fast axis discontinuity. We will try to do this measurement with more points. ]

 

PS:

The data is stored in foldername= 'C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\LC2_calibration data\fast axis 6'

Images attached to this report
3254_20230516052747_5v.png 3254_20230516053435_lc2fastaxischeck.png
Comments related to this report
ShalikaSingh - 15:34, Tuesday 16 May 2023 (3255)

The measurement was repeated. First, I moved the LC to the new position of 337.78 degrees. Then I repeated the measurement with the angle of rotation incremented by 30 degrees. 

The issue with fast axis orientation continues. see Fig 1 and 2. It seems that there is a discontinuity at some points. This has been observed in almost all the 7 times that we did measurements. 

PS:

The data is stored in foldername= 'C:\Users\atama\OneDrive\LC-Experiment\Measurement Data\LC2_calibration data\fast axis 7'

Birefringence mitigation (General)
Print this report.
MarcEisenmann - 10:12, Tuesday 16 May 2023 (3253)Get code to link to this report
Comment to LC fast axis direction as a function of applied voltage (Click here to view original report: 3242)

To measure the fast axis orientation we shuold have the 2 polarizers parallels and not crossed.

Birefringence mitigation (General)
Print this report.
ShalikaSingh - 11:19, Monday 15 May 2023 (3252)Get code to link to this report
LC 2 extinction ratio

[Shalika, Marc]

1. The extinction ratio of our second LC was measured using the method mentioned in elog 3241. The power at transmission was observed to obtain the maximum and minimum power for every voltage by correspondingly rotating the LC. 

2. The error bars are coming from the power fluctuations we measured.

3. The extinction ratio observed was at about 1.0332+/-0.0013 for all voltages. [see Fig 1]

4. Also the setup was moved to accomodate the new vertical slider and box because we have overhead table too. [see Fig 2]

 

[We also measured the fast axis orientation using the method in elog 3242 but the results were a bit confusing so its work in progress]

Images attached to this report
3252_20230515041219_lc2extinctionratio.png 3252_20230515043540_20230511191351.jpg
R&D (FilterCavity)
Print this report.
MarcEisenmann - 11:09, Monday 15 May 2023 (3251)Get code to link to this report
suspension health-check recovery

[Marc, Yuhang {remote)]

We checked the reason why healthcheck failed.

The test.sh code calls a .xml file for each coil of every suspension. All these files are located in the check_after_earthquake folder.

These .xml files are used to set up the measurement, from excitation to measurement.

However, no measurement nor excitation channels were specified aswell as reference measurements.

Looking at various folders, we found the correct files.

They were restored to the proper folder and we confirmed that the suspension health-check is recovered.

Birefringence mitigation (General)
Print this report.
MarcEisenmann - 21:06, Thursday 11 May 2023 (3250)Get code to link to this report
vertical slidder for the black box

[Hirata, Marc, Shalika]

In order to ease the installation of optics for birefringence measurement we added a vertical slidder to the box.

We use  an unused rack slider fixed to an unused part of the old scattering frame.

To stop the box at a higher position it is good to use 2 keys for safety.

R&D (FilterCavity)
Print this report.
MarcEisenmann - 21:04, Thursday 11 May 2023 (3249)Get code to link to this report
swap of AOM function generator

[Marc, Michael]

To prepare the shipping of the AOM function generator back to APC, we installed our new one (WF1968).

We used same settings as before (continuous mode, freqeuncy = 109.036035615 MHz, 1.124Vpk=5dBm).

We had quite low green power after the IRIS after the AOM.

Power budget was :

SHG reflection ~270mW

before AOM ~41.2mW

after AOM ~37.6 mW

after iris ~5.7mW

before FC ~5.26 mW.

We tuned a bit the steering mirror between the AOM and iris. Especially, there seemed to be a little clipping in the vertical direction but it did not help to recover the usual power.

We checked the function generator output on spectrum analyzer and found a -3.28 dBm amplitude. Therefore, we increased the amplitude to recover the usual 5dBM : 2.95VPk gives 5.1 dBm.

In this configuration we recovered the usual AOM transmission.

We had to realign the last steering mirror on the bench to recover the PR targets.

The beam was then really far of the BS target. We tried to move PR mirror bu it did not seem to move. The health check has some error message ('No measurement channel defined') that we need to investigate.