LOG-IN
Displaying reports 2241-2260 of 3128.Go to page Start 109 110 111 112 113 114 115 116 117 End
R&D (FilterCavity)
Print this report.
YuhangZhao - 09:38, Saturday 27 October 2018 (1042)Get code to link to this report
Update of Mechanical transfer function for SHG, GRMC and MZ

Since I found we used to use high voltage deriver not in a proper way. The reason is demonstrated in the e-log entry before. Since this information is crucial for the filter design, I measured these transfer functions for which the high voltage drivers we didn't use properly. The result is uploaded to our wiki page with the name as listed below. However, I don't know if this coherence level is enough for our user.

SHG SHGfrequency,SHGmagnitude,SHGphase
GRMC GRMCfrequency,GRMCmagnitude,GRMCphase
MZ MZfrequency,MZmagnitude,MZphase

For the data, please go to the following page to download. https://gwpo.nao.ac.jp/wiki/FilterCavity/Transfer%20Function

Images attached to this report
1042_20181027023638_shg.png 1042_20181027023656_grmc.png 1042_20181027023702_mz.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 21:35, Thursday 25 October 2018 (1039)Get code to link to this report
The measurement of open loop transfer function of SHG and recover remote control of second iris

Participiant: Enomoto, Eleonora and Yuhang

The week before last week we found the problem of high voltage driver, and this is also the reason why we found there is a low pass filter inside our high voltage driver. So we decided to use it in a proper way, which means switch off the sensor-in switch. However, we found the lock of SHG becomes unstable after did that. So we did the characterization of open loop transfer function again.

We found the unity gain frequency of previous set-up is 795Hz while the phase margin is 89 degree which is fine.

However, the unity gain frequency of revised set-up is 376Hz while the phase margin is 66 degree which is worse. Besides, there is also a peak going above 20k Hz and brings oscillation.

Since Pier is developing servo in APC and we also want to use high voltage driver in a proper way, so we need to measure a list of open-loop-transfer-function again with the correct set-up of high voltage driver.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Participaint: Eleonora and Yuhang

Besides, the remote control of 290m targrt is recovered based on yuefan's elog. However, its control requires the change of IP address and netmask. For the convience of remote control, we kept that computer inside our clean booth and we used another ether cable to achieve remote control.

Images attached to this report
1039_20181025143841_with.png 1039_20181025143849_without.png
R&D (FilterCavity)
Print this report.
EleonoraCapocasa - 18:42, Thursday 25 October 2018 (1037)Get code to link to this report
End mirror alignment recovered

[Takahashi, Matteo, Eleonora, Yuhang, Enomoto]

With the help of Takahashi-san, we have opened the vacuum chamber in the end room (only the top part).

[Note that even if the venting was started last Friday the vacuum level was still not low enough so we had to inject some air before opening the chamber.]

The goal was to recover the alignment of the end mirror and solve the issue with the yaw picomotor reported in the entry #954.

By visual ispection, we could confirmed that the picomotor was stuck, as it reached the end of its range, and the intermediate mass was touching the damping magnets.

We have manually put back the yaw picomotor at half range and moved the suspension with the help of a traslation stage (pic1) and also by hand, to make the reflected beam superpose on the incoiming one. The superposition was checked by letting the incoming beam pass through the hole of the second target and check the reflection from the end mirror on the rear side of the second target.

The chamber has been closed and the punping down has been restarted. The gate valve between the chamber and the pipe is still close. According to Takahashi-san, the vacuum level to be reached before opening it is 2e-7 Torr.

Even if the alignment has been recovered we were not able to see any flashes, probably beacuse the beam distortion induced by the gate valve window is too large.

Some comments:

1) The good direction for recovering the alignment was not the one in which the picomotors reach the end of the range, meaning that the suspension position and the overall alignment hadn't moved too much. In any case we prefered to move the picomotor to exactly mid range (and have an optimally centerd intermediate mass), and then move the whole suspension to recover the alignement

2) We confirm that the yaw picomotor is quite critical as by moving it it's easy to make the intermidiate mass touch the magnets. For this reason also in KAGRA during the in-air alignment procedure, the whole suspension is usually moved with the help of some pusher (see Fig. 2)

3) We checked that the beam was well centered on the end mirror and slightly adjusted the camera in the end bench in order to have the beam also centered on it.

4) Some pictures of the current position of picomotors and intemidiate mass are shown in Figs 3, 4, 5.

Images attached to this report
1037_20181025122551_traslator.jpg 1037_20181025131225_7570kl02kl02lsgl.jpg 1037_20181025131229_picopitch.jpg 1037_20181025131236_picoyaw.jpg 1037_20181025131241_imm.jpg
R&D (FilterCavity)
Print this report.
EleonoraCapocasa - 17:42, Thursday 25 October 2018 (1035)Get code to link to this report
Telescope control CPU swapped

[Eleonora, Matteo, Yuhang]

On Mon 22 we found out that the supervisor PC used for Labview control system was not able to connect to the CPU (NM2 for TM: 133.40.121.78)which manages the ADC and DAC for the telescope suspended mirrors (PR and BS).

We checked this CPU (which is in the central area) and find out that it was not possible to swich it on anymore. Futher investigations suggested that the problem was in  the power supply unit.

So we removed the CPU, DAC and ADC units from it and insert them into the power box of another unused remote target, after removing its CPU (NM2 for IP: 133.40.121.73) and ADC/DAC units.
 
We could smoothly connect the supervisor PC to it and acquire and generate signals with ADC and DAC, but we observed a very strange behavior:  the frequencies at the output of the DAC are divided by two, with respect to those that we expected to send, while the frequencies read by ADC are multiplied by two. This suggest that the internal timing was two time faster than the correct one.
 
I went to the west end room and collect two other unused target computers. One of them could not be switched on (EM1 for IP: 133.40.121.71) the other one was working fine (EM1 for TM: 133.40.121.77). I have used the power box of this one to power the telescope CPU and everything worked fine and the timing problem was solved.
 
Since it is unlikely that the timing problem can come from the power box, I suspect that we might have not connected all the cables properly, the first time.
 
Summary: the power box of the telescope mirrors CPU was borken, we replaced it with another one and everything now works fine.
KAGRA MIR (Absorption)
Print this report.
ManuelMarchio - 15:48, Wednesday 24 October 2018 (1033)Get code to link to this report
HeNe probe mirror replacement and realignment. Signal maximization

I noticed that slightly touching the mount of the first mirror on the HeNe probe path makes the beam deflect a lot. So I changed it with a more rigid mirror mount.
I also wanted to clean the mirror (Thorlabs 1/2" Protected silver mirror PF05-03-P01), but I broke it, so I replaced it with a Newport 5103 General Purpose Silver Coated Mirror that I found in Tama.

Then I aligned the HeNe probe using the pinhole. The beam passes through the following positions of the pinhole:

  z y
start 15 122.373
default 38.85 120.823
end 115 115.873

I noticed that the reflection of the first lens on the IU was going up to the chopper. This is very likely to generate noise in phase, so I tilted the lens of the IU.
I also noticed another reflection from the sample that is going to the chopper. I can't tilt the sample, so I solved it putting a simple aperture near the chopper. See picture.

I used the surface reference to align the pump and maximize the AC signal.

I used the new power meter for the pump:
pump power: 74mW , chopper on: 37mW, with surf ref sample: 27mW

I moved the imaging unit to find the maximum of the signal on the surf ref.

IU pos AC DC AC/DC
60mm 0.26 4 0.065
65mm 0.32 4.2 0.076
70mm 0.36 4.4 0.082
75mm 0.51 4.75 0.107

The maximum is not in the range of the IU stage. Probably because tilting the lens to move the probe reflection from the chopper, I missed  the focus of the IU telescope.

Therefore I started again the IU alignment. I put the IU stage at 60mm. I found the sharp image of the blade. I looked for the maximum of absorption signal again:

IU pos AC DC AC/DC
60mm 0.59 6.4 0.092
65mm 0.64 6.4 0.1
70mm 0.72 6.4 0.112
75mm 0.6 6.4 0.094

So I put the IU at 70mm.

I made a scan of the surf reference.

I noticed that the DC is not linear with the power of the probe. I measured 6.4V for 1.71mW, and 6.5V for 2.58mW. Then I replaced the LDS9 power supply with the 12V battery and the 2.58mW gave 9V of DC. So I decided to keep the DC below 6V with a OD wheel, and continue using  the LDS9 power supply.

After putting the wheel, I missed the alignment pump/probe, so I used again the  pinhole to center the probe.

Then I made a scan of the surf reference again.

And a scan of the bulk reference. The transmitted power is 20mW (of 37mW incident)

Images attached to this report
1033_20181024084702_20181024foto1.jpg 1033_20181024084707_20181024foto2.jpg 1033_20181024084711_20181024foto3.jpg 1033_20181024084715_20181024foto4.jpg 1033_20181024084718_20181024foto5.jpg 1033_20181024084726_20181024foto6.jpg 1033_20181024084731_20181024foto7.jpg 1033_20181024084737_20181024foto8.jpg 1033_20181024084810_50.png 1033_20181024084815_19.png 1033_20181024084819_11.png
R&D (FilterCavity)
Print this report.
EleonoraCapocasa - 09:58, Monday 22 October 2018 (1032)Get code to link to this report
Characterization of the green produced by OPO (at the incoupling mirror side)

[Yuhang, Eleonora, Matteo]

In order to match the green beam transmitted from the green MC into the OPO we have characterized the green beam produced by OPO when it is locked with s-pol beam. Its paramenters will be the target ones for the mode matching telescope we have to design.

Since the beam is very weak (about 0.2 uW) we couldn't use the beam profile and we used a blade to do the characterization, instead.

Procedure: we attached a cutter blade to a traslation stage (See Fig.1) in order to be able to progressively cut the beam, by small and known steps.  For each step we recorded the power of the beam with a PD placed after the blade. Since the beam in gaussian the shape of this function is expected to be a error function (erf):

P (x) =  a*erf(sqrt(2)*(x-x0)/w)+o 

By fitting the data with this function we could extract the beam radius w for each position z at which the measurement was performed.

The beam size and the corresponding waist (in meter) are reported below and plotted in Fig 2.  The zero of the z-axis is taken at the incoupling mirror side of the OPO.

0.00098238 0.00115781 0.00142657 0.00143289 0.00290379 0.00266076
 0.00338225 0.00324448 0.00390693
0.00098238 0.00115781 0.00142657 0.00143289 0.00290379 0.00266076
 0.00338225 0.00324448 0.00390693

z =  [0.125, 0.15, 0.175, 0.20, 0.37, 0.395, 0.42, 0.47, 0.52];    
 
w = [0.982, 1.158, 1.426, 1.433,  2.904, 2.661, 3.382, 3.245, 3.907]*10^-3;  
 
We fitted these data with the usual function, describing the evolution of the beam size as a function of the position z  [w(z) =  w0*sqrt(1+((x-z0)/(pi*w0**2/l))**2)]
and we could extract the size and the position of the waist:   z = 1.97 +/- 2.2 cm.   w0 = 24  +/- 1.5 um
 
These parameters are in agreement with what we expected from simulation (see entry #1013) but the error on the waist position is quite large.
[Note that w0_532 = w0_1064/ sqrt(2)]
 
Conclusion: the parameters of green beam produced by OPO are how we expected and can be used to design the telescope for matching the green beam from SHG into OPO.
 
 
 0.00338225 0.00324448 0.00390693
0.00098238 0.00115781 0.00142657 0.00143289 0.00290379 0.00266076
 0.00338225 0.00324448 0.00390693

 0.00338225 0.00324448 0.00390693






			
			
Images attached to this report
1032_20181022062801_ca1e3d4152c44555a6aac9410fcfd891.jpg 1032_20181022062918_opogreen.png
Non-image files attached to this report
R&D (FilterCavity)
Print this report.
YuhangZhao - 22:49, Saturday 20 October 2018 (1031)Get code to link to this report
Telescope design for injecting output of green mode cleaner to OPO

According to the measurement result of entry about green mode cleaner output beam characterization and OPO green output beam characterization, we can design the telescope to match them. From the above entries, we know the source waist is 287um while the target waist is 24um. Based on the revised version of optical layout which I just modified today(the position of green mode cleaner and distance between bench and chamber are modified)(https://gwpo.nao.ac.jp/wiki/FilterCavity/OpticalLayout). I also attached the part of bench we care, see attached figure 1. In this picture we know the distance between waists should be 82.5cm. Besides, we should avoid putting lens around 10cm, 27.5cm, 55cm and 75cm. And putting lens between 5cm and 72cm. 

By using all the information listed above, I used JaMmt did the simulation. See attached figure 2, which shows the initial condition I gave. Besides, I upload the green lens we have in our clean booth on our wiki page(https://gwpo.nao.ac.jp/wiki/FilterCavity/Optics). See attached figure 3, it shows the lenses I used. Actually I didn't put lens with very small focal lens, although we have lots of small focal length lenses. The fitting shoes many good results. I attached three here. Some of them even tell me the mode matching is 100%.

---------------------------------------------------------------------------------------

Since we found the mirror to reflect green after dichroic (outside OPO's incoupling mirror) should be farther than last version of optical layout. I changed it and did the simulation again. The result is attached in 7th and 8th figure.

Images attached to this report
1031_20181020154909_42.png 1031_20181020155339_24.png 1031_20181020155644_30.png 1031_20181020155805_14.png 1031_20181020155810_51.png 1031_20181020155815_52.png 1031_20181029021430_10312018102015490942.png 1031_20181029021440_34.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 13:53, Friday 19 October 2018 (1027)Get code to link to this report
Problem of OPO scanning transmission fit

During the last few days, we took some data which contains more than one TEM00 and also 87.6MHz sideband. We also extrapulate some more information from the data we have already have. From the analysis we did for them, I found

1. Extrapulate more information.

For the fit of only one peak, we found the fit can give more than one result. This is reasonable, since there is couple between finesse and fsr. For example, we can have two totally different result for the same measurement we did for TEM00(as in attached figure 1, you need to zoom in to see the detail). In this picture, the finesse 75, fsr 4.54GHz can give a perfect fit while the finesse 57, fsr 3.44GHz can give as well. The difference of these two fit is only that I give two different initial range of Finesse. For the first one, I give the Finesse range around 50. However, for the second one, I give the Finesse range around 70. However, the good news is that we can have FSR we expect if we fix the finesse around 70.

For the measurement of TEM00 and sideband. I also found the fit can give more than one set of result. If I give the original Finesse around 70, means around our expected value. We can get a reasonable result of cavity length. This agrees with the fit of bandwidth. See attached figure 2. The finesse now is 72 while cavity length is 39mm. Besides, this fit result give the similar calibration factor with the former fit.

However, all the fit with a finesse value around 70 give FSR around 4GHz, while the direct measurement of FSR gives 2.8GHz. The reason can be PZT cannot response linearly with our driving HV signal.

2. Measurement with TEM00(two) and sideband together

The whole measurement and fit is attached in figure 3. You can see even visually that the distance between twoTEM00 and sidebands are totally different. That is the reason why you can see the fit cannot give a result. But anyway, I tried to fit these two peaks seperately, the result is in the attached figure 4 and 5.  This time, the calibration factor becomes ridiculously different while the fit result of FSR and cavity length becomes also quite different. You can see from the seperate fit, the time difference in the first peak is 0.000501 while 0.000340 in the second peak.

3. Measurement with TEM00(three) and sideband together

The whole measurement is shown in attached figure 6. In this figure, you can see the difference of 0.2GHz in FSR causes the displacement of the peak away from the standard position. Also this causes the fit failed. I also choosed these peaks and fit them seperately. Firstly, the calibration factor is fitted around 1200, 1300, 1100 (MHz/V) seperately.  From this point of view, we can deduce the PZT scanning velocity firstly increase and then decrease. And the fit of the finesse and FSR of the first and third peak give a similar result(first: FSR = 4.9GHz, Finesse = 75  third: FSR = 3.9GHz, Finesse = 61 ). However, the fit of the second has a very large error.

Images attached to this report
1027_20181019040604_54.png 1027_20181019043027_cali.png 1027_20181019045649_2tem.png 1027_20181019062827_tem01.png 1027_20181019062832_tem02.png 1027_20181019062841_3tem.png 1027_20181019064103_sb1.png 1027_20181019064109_sb2.png 1027_20181019064117_sb3.png
KAGRA MIR (Absorption)
Print this report.
ManuelMarchio - 18:57, Wednesday 17 October 2018 (1026)Get code to link to this report
1310nm laser noise investigation. Polarization instability

The laser current is set at 200mA.
I sent the laser output on a PBS, to check how the jumps show up in the two polarizations. 
I collected the reflection with the PM100D-S145C. This is most of the power: 58mW.
The transmission (few mW) goes on a 50mm lens and a DET10N with load resistance of 500Ohm.

I watched together the analog output of the PM100D and the DET10N signal at the oscilloscope in AC coupling.
DC of PM100D is 335mV; DC of DET10N is 900mV.
I tried a similar measurement some time ago, but ince the PM100D signal is covered by high frequency noise, I couldn't see anything.
Now I filtered the signal with a SR560 set at AC coupling and low pass first order at 3kHz, gain 5.

The result is in the attached video.
Channel1 yellow is the PM100D filtered analog output. Channel2 blue is the output of the DET10N
The signal are completely anticorrelated. Apart from high frequencies of the PM100D that are filtered out by the SR560.

This proves that the jumps are due to polarization instability.

I also attach a video of the DC of the two detectors. Channel1 is the PM100D not filtered, channel2 (blue) is the DET100D. 

Non-image files attached to this report
KAGRA MIR (Absorption)
Print this report.
ManuelMarchio - 13:42, Wednesday 17 October 2018 (1025)Get code to link to this report
Comment to 1310nm noise investigation with PM100D-S145C (Click here to view original report: 1022)

I took a video of the DC signal on the oscilloscope in 2 conditions

video7.avi
HWP at minimum of transmission
range 370uW
display 35uW

video8.avi
HWP at maximum of transmission
range 370mW
display 54mW

Non-image files attached to this comment
R&D (FilterCavity)
Print this report.
YuhangZhao - 16:06, Tuesday 16 October 2018 (1023)Get code to link to this report
Measurement of green production of OPO

[Yuhang, Eleonora]

The green production depends on incident power and on the crystal temperature. We need to find the best temperature to have the best phase matching and maximize the green production. The measurement was performed from 5.794 to 7.787kOm, which corresponds to 312.976K to 304.767K.

The method we used is to change the p-pol beam to s-pol. In this case, we can lock OPO with this beam and at the same time have green production, since only s-pol produces green beam. In transmission of OPO, we put a dichroic mirror which reflects infrared light and transmits green. The reflected beam is focuse with a lens on the  Qubig PD used for the locking,  while the transmitted beam is focused with a lens on a  InGas PD.

The attached picture shows the green production as a function of the temperature. We see two peaks: the largest is at 306.8437 K, the second largest is at 309.3391 K.

 The IR input power was 141 mW.   At the optimal temperature (309.3391 K), we measure a the green power of 0.277 uW  while the IR trasmitted power is 0.189 mW . (Tramsmissivity:  0.13%.  Lower than that measured few days ago #elog 999)

Images attached to this report
1023_20181016090654_figure1.png
KAGRA MIR (Absorption)
Print this report.
ManuelMarchio - 15:52, Tuesday 16 October 2018 (1022)Get code to link to this report
1310nm noise investigation with PM100D-S145C

I set the laser current at 200mA.
I used the PM100D power meter with the S145C power meter head to check the laser power fluctuations in several conditions.
I connected the analog output of the PM100D to the oscilloscope, and took some videos
I set the bandwidth of the PM to HI. I swithed OFF the auto range and set the range to 370mW.

PM right after the fiber output
display power: 61.3mW
analog out DC: 365mW
AC: video1 oscilloscope

PM after the first PBS
display power: 58.3mW
DC 350mW
AC: video2 

Then I rotated the half-wave plate to change the  PBS-HWP-PBS system transmitted power 

after PBS-HWP-PBS max transmission
display power: 54.3mW
DC: 327mV
AC: video3 
 

after PBS-HWP-PBS min transmission
display power: 0.0mW
DC: 10mV
AC: video4 

after PBS-HWP-PBS half transmission
display power: 25mW
DC: 150mV
AC:video5 

Changed the PM range to 370uW
after PBS-HWP-PBS min transmission
display power: 27uW
DC: 160mV
AC: video6 

Conclusion: looks like the fluctuations increase when the polarization rotates toward the minimum transmission.
I can't recognize the same jumps I saw in the DET10N

Non-image files attached to this report
Comments related to this report
ManuelMarchio - 13:42, Wednesday 17 October 2018 (1025)

I took a video of the DC signal on the oscilloscope in 2 conditions

video7.avi
HWP at minimum of transmission
range 370uW
display 35uW

video8.avi
HWP at maximum of transmission
range 370mW
display 54mW

KAGRA MIR (Absorption)
Print this report.
ManuelMarchio - 17:31, Monday 15 October 2018 (1021)Get code to link to this report
PD linearity check

I checked the linearity of the system by changing the incident power of the HeNe laser.

The PD DET10A gives a DC signal proportional to the laser power. And the AC signal obtained after the lock-in demodulation is proportional to the absorption signal and to the DC. So if there is some non-linearity (for example saturation effects) it should cause the AC/DC signal to be not constant.

I put an optical density wheel to reduce HeNe power. I rotated it a bit to change the DC level, acquired some points of AC and DC in that condition, and rotated again the wheel a bit to a different DC value and so on.

The plot shows good linearity.

Images attached to this report
1021_20181015103043_pdlinearityplot1.png 1021_20181015103046_pdlinearityplot2.png 1021_20181018084937_odwheel.jpg
R&D (FilterCavity)
Print this report.
YuhangZhao - 18:40, Sunday 14 October 2018 (1019)Get code to link to this report
The measurement of birefringence effect of OPO crystal

Temperature change causes the change of cavity length. However, PPKTP has a different refractive index for p and s polarization. So the FSR change for s and p polarization are different. If we want to make both s and p polarization resonant inside the crystal, we need to choose a good temperature or choose a good frequency difference between s and p polarization. As pointed out as the entry about the temperature we should measure, we did the measurement. Besides, we measured the calibration factor before so we can know the s-p frequency difference change according to temperature change.

The measurement was done like this, we firstly check the rotation of HWP so that the transmission of HWP keeps s-pol. At this time(almost all the light is reflected by PBS cube), the angle is 331 degrees. Then put it just in front of OPO housing, rotate HWP to have some p-pol inside OPO. In the end, we make s-pol is higher than p-pol. So we can differentiate them by hight. Then we changed temperature and made measurement.

The measurement result is listed in the last attached figure as a sheet.(detail is in the attached figure 1-17)

Most of the case, the find of frequency different is based on finding the highest and second highest peak. And then use the calibration factor and the slope of ramp signal. However, the find of frequency difference in temperature of 307.4K is performed by fitting the scanning by the addation of two airy functions.

By using these data I plot the birefringence effect in figure 18, the birefringence constant is 397.76 +/- 0.99 MHz/K.

Images attached to this report
1019_20181014112711_3029.png 1019_20181014112717_3034.png 1019_20181014112724_3039.png 1019_20181014112730_3044.png 1019_20181014112738_3049.png 1019_20181014112744_3054.png 1019_20181014112752_3059.png 1019_20181014112800_3064.png 1019_20181014112809_3069.png 1019_20181014112826_3074.png 1019_20181014112832_3079.png 1019_20181014112838_3084.png 1019_20181014112843_3089.png 1019_20181014112849_3094.png 1019_20181014112902_3099.png 1019_20181014112908_3104.png 1019_20181014112913_3109.png 1019_20181014113856_36.png 1019_20181015135354_bconstant.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 00:43, Sunday 14 October 2018 (1016)Get code to link to this report
High voltage driver issue and usage recommendation

While we were using high voltage driver, we found the monitor channel give a highly distorted signal. At the begining, we thought it is the common issue of high voltage deriver. However, I just found out on yesterday that this distortion is caused by a switch on the rear panel of high voltage driver. See attached figure 1, the function of switch is to switch the sensor signal on or off. The switch is marked with a red circle in the picture.

The phenomenon is confirmed by me and like this. When you switch it on, you will see the distortion. When you switch it off, you will see almost the same with the ramp input. This is quite easy to confirm. But the question is whether it change the real output or not?

Firstly, I did the simulation of how our high voltage driver can affect the ramp signal.

1. I generate ramp signal(80Hz) in time. I use additive synthesis to approxiamte our ramp signal. It is the summing of the odd harmonics of fundamental while every other odd harmonic multiplied by -1. Then multiply the amplitude of the harmonics by one over the square of their mode number.(more details in en.wikipedia.org/wiki/Triangle_wave#Definitions) See attached figure 4. We can see the ramp signal is quite decent. 

2. Use FFT to convert time-domain ramp into frequency-domain. See attached figure 5. It shows the spectrum of ramp signal. We can see a clear peak at 80Hz. (Actually there are some harmonic peaks of 80Hz, but they have much lower amplitude and at much higher frequency. So I didn't show them.)

3. Apply the low pass filter of our high voltage driver. The corner frequency is shown in the datasheet of high voltage driver. See attached figure 2 and 3. Since our piezo's inductor is close to the data in the sheet, so we can use the value of 600Hz as pole. See attached figure 6. It shows the lowpass filter I applied.

4. Convert frequency signal back to time domain. The result is shown in attached figure 7. You can see the distortion is not sever. And the frequency or amplitude almost remain the same. From the attached figure 8, you can see much better the frequency is exactly the same with before(80Hz). 

So the comclusion of simulation is that high voltage driver should not change the ramp. The change is very trivial.

Then I checked the situation of this ramp output by looking at the scanning of OPO cavity. Figure 9 shows the scanning while the switch is off. We can see we have three TEM00. However, after I switch it on the sensor in port. I got the result of figure 10. No matter how I change the offset of high voltage driver, I can see only two TEM00. So this means the switch really changes the output of high voltage driver.

Unfortunatly, I found the switches are on for SHG's, GRMC's and IRMC's high voltage driver. So in the future, we need to take care not switch on the 'sensor in switch'. And also, for the low frequency ramp, it doesn't change the ramp shape. So the problem of discrepancy of OPO's simulation and measurement should not come from the wrong ramp signal. The ramp signal of monitor channel reflects the truth of high voltage driver output.

Images attached to this report
1016_20181013162530_rearpanel.jpg 1016_20181013163926_33.png 1016_20181013163934_20.png 1016_20181013165621_80hzramp.png 1016_20181013170203_rampspectrum.png 1016_20181013170317_lowpass.png 1016_20181013170833_distortedramp.png 1016_20181013171624_spectrumafterlowpass.png 1016_20181013173639_switchoff.png 1016_20181013173646_switchon.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 23:41, Friday 12 October 2018 (1015)Get code to link to this report
Simulation of OPO by using Finesse after know the precise modulation depth, giving some new results

Since we have a new result of modulation depth, I did the simulation again. This time I also find a way to get the simulation result of optical length, Finesse, FSR and FWHM.

  simulation measurment CAD estimation
Finesse 73 56 +/- 0.04 -
FSR(MHz) 3943.3 2785+/- 0.19 -
FWHM(MHz) 53.79 59.93 +/- 0.21 -
optical length(mm) 38 53.855 +/- 0.013 38
error signal 60 14 -

The problem of error signal difference becomes less sever now.

Images attached to this report
1015_20181012163942_25.png 1015_20181012163948_20.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 23:12, Friday 12 October 2018 (1013)Get code to link to this report
Estimate of OPO cavity length by using OPO CAD file and Matteo's OPO installation record

The length of cavity is composed of crystal part and air part. The air part is the part between crystal and in-coupling mirror. In the first attached figure, we can see the lateral side of OPO housing. The red line stands for the cavity length. The way to estimate it is to seperate it to three parts as it is shown in the first attached figure. 

The blue line is shown in the second attached figure. It is roughly 14mm.

The green line is shown in the third attached figure. Since we can see in the attached  fourth figure, Matteo put the crystal roughly in the center of POM_bridge. So the second part should be half of bridge thickness. It is roughly 25/2 = 12.5mm.

The last purple line is half the length of crystal. We can know from the attached figure 5, crystal length is 9.3mm. So this purple line length is 9.3/2 = 4.65mm.

So the total length is 14+12.5+4.65 = 31.15mm. It concludes 9.3mm of KTP and 21.85mm of air. The real length should be 9.3*n(KTP)+21.85*n(air). The refraction index of KTP for infrared is 1.7379. So the real optical length is 9.3*1.7379+21.85 = 16.16+21.85 =38mm

Images attached to this report
1013_20181012154920_54.png 1013_20181012155253_17.png 1013_20181012155858_58.png 1013_20181012155907_21.png 1013_20181012155921_12.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 21:49, Friday 12 October 2018 (1012)Get code to link to this report
The calculation of modulation depth we are giving now for OPO's EOM

Since we measured the electrical signal we sent to OPO's EOM(see the last attached picture of elog), we can have a precise estimation for modulation depth. According to the specification(you can find it in our wiki page), the modulation depth has a linear relationship with the peak voltage. It crosses points (0, 0) and (1, 6.5), see attached figure 1 and 2. Since the curve is straight, two points is enough to know the function. Then we use the relationship between Vp and dBm, Vp = 10^((P(dBm)-10)/20). In the end, we get the function of power(dBm) and modulation depth. Since now we are sending signal of 12.6dBm, we get the modulation depth should be 0.15.

However, in the simulation of Finesse, we assume modulation depth of 0.3. So we need to do simulation again to have a more resonable error signal estimation.

Images attached to this report
1012_20181012135523_54.png 1012_20181012135630_58.png 1012_20181015140146_modulationdepth.png
R&D (FilterCavity)
Print this report.
YuhangZhao - 23:32, Thursday 11 October 2018 (1011)Get code to link to this report
Some characterization work about OPO(including Finesse, calibration factor, bandwidth and FSR measurement)

Participant: Matteo and Yuhang

Since we can do the calibration from time to frequency, I did some characterization work about OPO.

0. Fit Finesse of OPO

All the other measurement needs the value of the finesee, because there is coupling between some parameters of airy function(FSR and the finesse). So we use the measuremt which has two TEM00. It has a clear FSR, so that it can degenerate and give a better fit of the finesse.  Then we use this fit value as an initial value reference for the finesse of other fits. Besides, here we take only the data around TEM00 to avoid the influence of higher order modes to the fit.

Result is finesse = 56 +/- 0.04. Detail is shown in attached figure 1.

Note: We found the high voltage driver now behaves very well. Since all the data we took for ramp comes from the monitor chanel of high voltage driver, so we think we can trust it. The good thing is that the ramp signal is quite linear and without distortion. So we think it should be fine to just take it as the real drive we send to the piezo of OPO.

1. Find calibration factor

The method is to use airy function to fit TEM00 and sidebands. The purpose is to find the time distance between TEM00 and one of the sidebands. Then we can convert this time distance to voltage distance by using the ramp signal. This voltage distance corresponds to 87.6MHz(the resonant frequency of EOM). This new resonant frequency is because of the repair of EOM. After the repair the resonant frequency becomes from 88.1245MHz to 87.6MHz. The calibration factor of frequency/voltage is universal and can be used to all the measurement of our OPO.

See attached figure 2. The result is cal = 856.08 +/- 0.19 MHz/V.

2. Fit of bandwidth

Since we have the calibration factor. We used the only TEM00 peak did the fit of bandwidth. In the code I attached, you can find every time I calculate the slope of ramp. It is quite cumbersome, but it is not avoidable. It is crucial to have a precise result. The result is shown in attached figure 3. BW = 59.93 +/- 0.21.

3. Fit of FSR and estimate of cavity length

We use again the data with two TEM00 fit the FSR(FSR is 2785.3 +/- 0.7 MHz) and cavity length(L = 53.855 +/- 0.013 mm). The method is similar with the fit of bandwidth. According to the result of FSR, we found the estimate of cavity length is 54mm. This is quite strange since according to the assemble picture Matteo uploaded and his Phd thesis, it should be around 35mm. Our result is 20mm longer than this nominal value. I guess there maybe something wrong. I will try to figure it out.

Finally, I also upload the code I used as a pdf file.

Images attached to this report
1011_20181011161807_finesse.png 1011_20181011161815_calibration.png 1011_20181011162319_bandwidth.png 1011_20181011162332_fsr.png
Non-image files attached to this report
R&D (FilterCavity)
Print this report.
YuhangZhao - 22:58, Wednesday 10 October 2018 (1010)Get code to link to this report
The first lock of OPO and some comparison with Finesse simulation

Yesterday we first locked the OPO, and we also got the error signal. Let's first compare the transmission power and error signal in reality and simulation(for p-pol).

  measurement simulation
transmitted power(mW) 0.244 0.66
error signal pk-pk value (mV) 14 120

The simulation result is attached as figure one. The measurement result is attached as figure two.

Since the transmitted power is only roughly a factor of 2.5 lower than simulation. I guess the small error signal is because of the lower gain of PD than we expected.

After get the error signal, we used SR560 to give a low pass filter and achieved lock(can last for several tens of minutes). However, we observed some oscillation which is probably caused by the noise of SR560. I measured the noise spectrum of the error signal. It is in the attached figure 3 and 4. We can see from that the peaks are the harmonic of electrical noise. 

We also measured the opto-mechanical TF. If you are interested in that, please have a look in our wiki page.

The maximization of phase is also done. The procedure is attached in figure 2, 5, 6 and 7. The shape of error signal is quite similar with the simulation. I saved the new set-up of dds2 and the name is today's date.(name: 20181010-dds2, see attached figure 8)

We also found that the amplification factor of the board made by Pier can be increased. See attached figure 9, the magnitude now is 12dBm. However, the maximum we can give is 26dBm(according to the datasheet from Qubig). Since we don't have a large enough error signal, this is also a method we can consider to increase it.

Images attached to this report
1010_20181010155828_oposim.png 1010_20181010160008_wechatimg66.jpg 1010_20181010161010_wechatimg74.jpg 1010_20181010161017_wechatimg75.jpg 1010_20181010161705_wechatimg67.jpg 1010_20181010161716_wechatimg64.jpg 1010_20181010161726_wechatimg65.jpg 1010_20181010161738_wechatimg68.jpg 1010_20181010161756_wechatimg69.jpg