40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 120 of 335  Not logged in ELOG logo
ID Date Author Type Category Subjectup
  4582   Thu Apr 28 15:31:36 2011 kiwamuUpdateIOOMC PDH lock : readjustment of demodulation phase

Since Suresh has installed the RF source box and changed the cable configuration somewhat,

the demodulation phase for the MC locking became off by about 10 degree.

I changed the length of some cables and obtained a good demodulation phase by the same technique as Suresh and Koji did before (see here for detail).

I maximized the Q signal. The lock of the MC looks healthy.

DSC_2975_ss.jpg

Quote from #4578

RF Source box has been mounted in the 1X2 rack. 

  1162   Tue Nov 25 18:38:03 2008 Alberto, RobUpdatePSLMC Periscope Alignment
This morning when I came in I found the MC cleaner unlocked and the autolocker script could not lock it. The reflected beam was quite off and showed in the bottom left corner of the IMCR camera. After turning off the WFS locking, I started slightly changing the alignment of the steering mirrors on the MC periscope, waiting for the LSC servo to lock the cavity. It didn't work. At some point I lost the beam from the IMCR camera and that is how someone might have found it when I left it for about one hour.

When I came back and tried again adjusting the steering mirrors, I noticed that the autolocker was working and was trying to lock the cavity. After just a bit of adjustment, the MC got easily locked.

After that, I spent a couple of hours trying to improve the alignment of the periscope to minimize the reflection and maximize the transmission. I started with a transmission of 0.4 V but, despite all the tweaking (I used the technique of turning both yaw knobs at the same time), I couldn't get more than 1.2 V (and 2.4 V at the reflection) if only the LSC servo was on. Looking at the camera, I moved the beam around to look for a more favorable spot but the MC wouldn't lock with the beam in other places. Maybe I could do better or maybe not because the cavity is not aligned. I'm going to try again tomorrow.
  8138   Fri Feb 22 17:33:25 2013 ManasaUpdateElectronicsMC REFL PD back from the dead

 

 [Yuta, Manasa]

We replaced the dead photodiode on MC REFL PD with a new one (GAP 2000). We measured the frequency response of the PD and tuned the resonant frequency using inductor L5 (in the circuit diagram) to be 29.575MHz - over an average of 10 measurements.

Riju is measuring the characteristics of the PD and will be posting an elog in detail.

  11237   Wed Apr 22 17:04:11 2015 ranaUpdateElectronicsMC REFL PD back from the dead

Just randomly found this old entry from 3 years ago. We should never have installed a GAP 2000 - they are an inferior type of InGaAs diode. We should add to our list replacing these with a 2 mm EG&G diode.

How many 2 mm EG&G InGaAs diodes do we have Steve? Can you please find a good clean diode case so that we can store them in the optics cabinet on the south arm?

Quote:

 [Yuta, Manasa]

We replaced the dead photodiode on MC REFL PD with a new one (GAP 2000). We measured the frequency response of the PD and tuned the resonant frequency using inductor L5 (in the circuit diagram) to be 29.575MHz - over an average of 10 measurements.

 

  877   Mon Aug 25 11:43:55 2008 YoichiFrogsIOOMC REFL PD cable had been disconnected through out the weekend
Most of my morning was wasted by the MC REFL PD cable, which was disconnected on the generic LSC PD interface board.
I know who did this. *ME*. When I pulled out the MC board, which is sitting next to the PD interface, on Friday, I must have
disconnected the PD cable accidentally. The connector of the PD cable (D-Sub) does not have screws to tighten and easily comes off.
I wrote this entry to warn other people of this potential problem.
  8137   Fri Feb 22 13:03:49 2013 ManasaUpdate MC REFL PD murder

 

[Yuta, Manasa]

We turned IFO power back to 1.25W by removing the attenuator and forgot that the Y1 mirror before the REFL PD must be replaced with BS 10% before getting to full power. The PD is dead  and now we are in the process of fixing it. Forgive us for all our sins!

On the other note, we have changed the mech shutter mode from N.O back to N.C. So the shutter now works as usual from the medm screen.

dead.jpg

  13712   Tue Mar 27 23:37:35 2018 gautamUpdateIOOMC REFL PD removed

I've removed the MC REFL PD unit from the AS table for investigation. So MC won't lock.

PSL shutter was closed and location of PD was marked with sharpie (placing guides to indicate position wasn't convenient). I also kapton taped the PD to minimize dust settling on the PD while I have it out in the electronics area. Johannes has the camera, and my cellphone image probably isn't really high-res enough for diagnostics but I'm posting it here anyways for what it's worth. More importantly - the board is a D980454 revision B judging by the board, but there is no schematic for this revision on the DCC. The closest I can find is a D980454 Rev D. But I can already see several differences in the component layout (though not all of them may be important). Making a marked up schematic is going to be a pain indecision. I'm also not sure what the specific make of the PD installed is.

The lid of the RF cage wasn't on.

More to follow tomorrow, PD is on the electronics workmench for now...


gautam 28 March 2018: Schematic has been found from secret Dale stash (which exists in addition to the secret Jay stash). It has also been added to the 40m electronics tree.

Attachment 1: IMG_6955.JPG
IMG_6955.JPG
  13715   Wed Mar 28 21:31:39 2018 gautamUpdateIOOMC REFL PD removed

I re-installed the MC REFL photodiode. Centered beam on the PD by adjusting steering mirror to maximize the DC signal level (on o'scope) at the DC monitoring port. Curiously, the DC level on the scope (high-Z) was ~2.66V DC, whereas the MEDM screen reports ~twice that value, at ~5.44 "V". We may want to fix this "calibration" (or better yet, use physical units like mW). Noise-eater On/Off comparison of MC error signals to follow.

  8038   Fri Feb 8 17:15:56 2013 JenneUpdateRF SystemMC REFL Photodiode transimpedance

This measurement was done already about a week ago, in elog 7984.  Can you please describe why the numbers for the last measurement were not believable, and what was done differently this time?

  8044   Fri Feb 8 20:27:56 2013 KojiUpdateRF SystemMC REFL Photodiode transimpedance

The comment itself was added by me.
The difference between the previous and new measurements should be described by Riju.

In the entry 7984, the description has several PDs mixed up. The measurement was done with the MCREFL PD.
But the DC transimpedance of the thorlabs PD (5e3) was used, according to the text.
I first wonder if this is only a mistake not in the calculation but only in the elog due to a sloppy copy-and-paste.
But the resulting shot-noise-intercept current was 50uA, which is way too small
compared with a realistic value of 0.1~1mA. I have never seen such a good value with
C30642 at the resonant freq ~30MHz. That's why I said "hard to believe". I guessed this wrong
DC transimpedance was actually used for the calculation. 


You may wonder why this 50uA is unreasonable number.
Basically this is just my feeling and probably is same as Rana's feeling.
But "my feeling" can't be a scientific explanation. Here is some estimation.

Looking at my note in 2010:
https://wiki-40m.ligo.caltech.edu/40m_Library (Comparisons of the PD circuits by KA)

The expected shot noise intercept current (idc) is

idc = 2 kB T / (e Rres),

where Rres is the impedance of the resonant circuit at the resonant freq.

This Rres is expressed as

Rres = 1/(4 pi^2 fres^2 Cd^2 Rs),

where Cd and Rs are the capacitance and series resistance of the diode.

If we input realistic numbers,

Cd = 100pF
Rs = 10 Ohm
fres = 30MHz

We obtain, Rres ~ 300Ohm, and idc = 0.2mA

In other words, Rs needs to be 2~3Ohm in order to have idc = 50uA.
This is too small from the previous measurements.
Test Results for C30642 LSC Diode Elements by Rich Abbott

  12485   Mon Sep 12 20:19:25 2016 LydiaUpdateGeneralMC REFL beam splitter not replaced

The beam splitter that directs light into the MC REFL photodiode has not been replaced; there is still a mirror there. Gautam suggested we wait to replace it until the PSL shutter is open so the beam can be aligned. However, this must be done before going to high power.

GV addendum: What I suggested was to try and recover the arm alignment using the current low power configuration after pumpdown - since we were well aligned just before pumpdown, we should be able to recover this alignment pretty easily at low power. After locking both arms and running the dither align (also center all Oplevs), we can go ahead do the following:

  • Replace mirror in MC Refl path with 10% reflection BS (Johannes, Lydia and I confirmed that this is on the AP table earlier today). Then align the reflected beam onto the PD using the tiny mirror
  • Replace HR mirror in Transmon path at the EY table
  • Replace ND filters on Transmon QPDs at EX and EY tables
  • Repalce ND filter on Transmon CCD at EY table
  • Revert MC autolocker to the nominal version instead of the low power version we have been using during the vent
  • Turn up MC to nominal power by rotating the wave plate on the PSL table - confirm that we have nominal levels by measuring with power meter
  • Recover single arm locks, green beatnotes etc at nominal operating conditions
     
  10064   Wed Jun 18 21:37:11 2014 KojiUpdateIOOMC REFL investigation

[Jenne Koji]

We decided to check the situation of the REFL MC beam path.

- No resolution of the weird MC REFL DC increase
- The reflection from the PD was adjusted to hit the beam dump
- The MC WFS paths were aligned again


Detail:

We found that the reflected beam from the PD was hitting the mount of the beam dump.
So the entire MC REFL path was steered down such that the last steering mirror does not neet to steer the beam.
When the alignment was adjusted so that the reflection from PD hit the beam dump, the beam spot on the small mirror right before the PD
got a bit marginal but it seemed still OK after some tweak.

Then we looked at the reflection value. It is still about 6.5. No change.

As we messed up the entire MC REFL path, we aligned the MC WFS paths again.
This was done with the unlocked MC REFL beam. Once the cavity was locked,
it turned out that it was enough for the WFS too keep the MC locked.

  12806   Tue Feb 7 10:18:58 2017 gautamUpdateIMCMC REFL weirdness

A few minutes back, I glanced up at the control room StripTool and noticed that the MCREFL PD DC level had gone up from ~0 to ~0.7, even though the PSL shutter was closed. This seemed bizzare to me. Strangely, simply cycling the shutter returned the value to the expected value of 0. I wonder if this is just a CDS problem to do with c1iool0 or c1psl? (both seem to be responding to telnet though...)

Since things look to be back to normal, I am going to start with my characterization of the various TFs in the IMC FSS loop...

  16677   Thu Feb 24 14:32:57 2022 AnchalUpdateGeneralMC RFPD DCMON channel got stuck to 0

I found a peculiar issue today. The C1:IOO-MC_RFPD_DCMON remains constantly 0. I wonder if the RFPF output is being read properly. I opened the table and used an oscilloscope to confirm that the DC output from the MC REFL photodiode is coming consistently but our EPICs channel is not reading it. I tried restarting the modbusIOC service but that did not affect anything. I power cycled the acromag chassis while keeping the modbusIOC service off, and then restarted teh modbusIOC service. After this, I saw more channels got stuck and became unresponsive, including the PMC channels. So then I rebooted c1psl without doing anything to the acromaf chasis, and finally things came back online. Everything looks normal to me now but I'm not sure if one of the many channels is not in the right state. Anyways, problem is solved now.

 

  29   Tue Oct 30 00:47:29 2007 ranaOtherIOOMC Ringdowns
I did a bunch of MC ringdown measurements using the PD that Rob set up. The idea is to put a fast PD (PDA255)
looking at the transmission through MC2 after focusing by a fast lens. The input to the MC is turned off fast
by flipping the sign of the FSS (Andri Gretarsson's technique).

With the laptop sitting on the MC can, its easy to repeat many ringdowns fast:
- Turn off the MC autolocker. Relock the MC with only the acquisition settings; no boosts
  and no RGs. This makes it re-acquire fast. Turn the MC-WFS gain down to 0.001 so that
  it keeps it slowly aligned but does not drift off when you lose lock.

- Use low-ish gain on the FSS. 10 dB lower than nominal is fine.

- Setup the o'scope (100 MHz BW or greater) to do single shot trigger on the MC2 trans.

- Flip FSS sign.

- Quickly flip sign back and waggle common gain to get FSS to stop oscillating. MC
  should relock in seconds.

Clearly one can scriptify this all just by hooking up the scope to the ethernet port.


Attached are a bunch of PNG of the ringdowns as well as a tarball with the actual data. A sugar
napoleon to whomever can explain the 7 us period of the wiggle before the vent!
Attachment 1: tek00000.png
tek00000.png
Attachment 2: tek00001.png
tek00001.png
Attachment 3: tek00004.png
tek00004.png
Attachment 4: MC2ringdown.tar.gz
  30   Tue Oct 30 13:58:07 2007 ajwConfigurationIOOMC Ringdowns
Here's a quick fit-by-eye to the latter part of the data from tek00000.xls.

The prediction (blue) is eqn 41 of
http://www.ligo.caltech.edu/docs/P/P000017-A.pdf

T1 = T2 = 0.002. Loss1 = Loss2 = 150 ppm.
MC3 assumed perfectly reflecting.
Velocity = 320 um/s (assumed constant), 2 usec into the ringdown.

OK, there's one little fudge factor in the prediction:
I multiplied D by 2.
Attachment 1: CavityRingdown.png
CavityRingdown.png
Attachment 2: CavityRingdown.m
% CavityRingdown.m
% Eqn 41 of 
% "Doppler-induced dynamics of fields in Fabry–Perot
% cavities with suspended mirrors", Malik Rakhmanov (2000).
% http://www.ligo.caltech.edu/docs/P/P000017-A.pdf

clear all

% read in ringdown timeseries:
at = importdata('tek00000.csv');
... 121 more lines ...
  12904   Fri Mar 24 11:26:57 2017 gautamUpdateIMCMC SUS damping gains restored

I've restored the damping loop gains to their nominal values. Analysis of the coherence between MCL and seismometer channels under this reduced gain setting is underway, results to follow.

  12903   Thu Mar 23 23:38:58 2017 gautamUpdateIMCMC SUS damping gains stepped down

I've reduced the gains of the damping on all 3 MC SUS by a factor of 3 for overnight observation as part of the ongoing feedforward noise cancellation investigations. I will return them to the nominal values tomorrow morning.

  6244   Fri Feb 3 14:44:33 2012 JenneUpdateIOOMC SUS misalignment

The mode cleaner is a little misaligned in pitch, and is very misaligned in yaw.  The lowest order mode that is flashing is TEM11.

I had a look-see at the SUS sensors, to see if there were any big jumps.  There were moderately sized jumps on all 3 mode cleaner optics.

SUSjump_3Feb2012.png

The MC's lockloss was at ~8:22am this morning, and went along with a giganto kick to the optics.  Steve tells me that Den might have been kicking up optics while doing computer things this morning, before Steve reminded him to shut off the watchdogs.  However, Steve was also taking phots/measuring things near MC Refl, so maybe he's not totally absolved of blame.  But this really looks like the optics settled to different places after big kicks.

I'm going to try to align the MC mirrors to get back to the sensor numbers from early this morning before chaos began.

Reminder / Moral:  Everything cannot be considered to be "working fine" if the MC isn't locking.  See if you can figure out why, and especially if it's something that you screwed up, either fix it, or better yet, ask for help and learn how to fix what you broke.

  6246   Fri Feb 3 15:49:10 2012 JenneUpdateIOOMC SUS misalignment

[Jenne, Den]

We moved the MC approximately back to where the sensors for each optic used to be (mostly touching MC2, but a little bit of MC1 to help the refl get back to its max value).  MC is now locked, and with the help of the WFS it's back to nominal.  I forgot to disable the WFS, so I think we aren't perfectly aligned, but we're close enough for the WFS to get us the rest of the way.  We're heading over to JClub right now, so we're going to leave it as-is.

  6248   Fri Feb 3 17:17:47 2012 DenUpdateIOOMC SUS misalignment

Quote:

Reminder / Moral:  Everything cannot be considered to be "working fine" if the MC isn't locking.  See if you can figure out why, and especially if it's something that you screwed up, either fix it, or better yet, ask for help and learn how to fix what you broke.

When I left this morning, Steve was still working with the MC and it was unlocked anyway, I could not check it. By "fine" I meant only watchdogs. The thing is that before starting to work with c1lsc I turned off all the coils. Crazyness that Steve saw was after I turned them on back after reboot. This is a confusing thing - restarting models on c1lsc and burt restoring them is not enough. After I did it, everything at the STATUS MEDM screen was green, but the C1:SUS-???_??PD_VAR values went up after turning on coils. So sus and lsc communicated in a bad manner after the reboot. After restarting x02 model, the watchdogs were fine again.

  154   Sun Dec 2 21:02:12 2007 ranaConfigurationIOOMC SUS re-alignment
The spot on MC2 was not centered, so I put it back in the center:

  • Made sure MC trans was high with the WFS off.
  • Moved the Sliders on the MC Align screen until spot was centered (by eye)
  • Moved some more until power was maximized.
  • Unlock MC
  • Center spots on McWFS
  • Re-enable autolocker and McWFS loops.
  155   Sun Dec 2 21:07:39 2007 ranaConfigurationIOOMC SUS re-alignment
you asked for:   diff 2007/12/01,4:58:48 2007/12/03,4:58:48 utc 'MC.*COMM'
LIGO controls: differences, 2007 12/01 04:58:48 utc vs. 2007 12/03 04:58:48 utc
__Epics_Channel_Name______   __Description__________   __value1____     __value2____
C1:SUS-MC1_YAW_COMM                                    -0.273460        -0.503460
C1:SUS-MC2_PIT_COMM                                     3.624020         3.632020
C1:SUS-MC2_YAW_COMM                                    -0.936800        -1.038800
C1:SUS-MC3_YAW_COMM                                    -3.129000        -3.369000
  156   Sun Dec 2 21:13:16 2007 ranaConfigurationIOOMC SUS re-alignment
Attachment 1: e.png
e.png
  706   Mon Jul 21 11:54:00 2008 JenneUpdateGeneralMC Servo Board
I pulled the MC Servo Board again, to check the components that are on the board, and compare them with the schematics. The filters that I'm interested in on the Fast Path haven't been changed. The high pass filters on the Fast Path have been changed.
Component      Schematic      Actual
---------      ---------      ------
C140           10u            open
C144           10u            open
C149           open           a gray Cap.  value unknown
C141           10u            open
C145           10u            open
R97            1.58K          0
R99            open           1130
R103           open           1130
R100           open           0
R104           100            1130
R98            1.58K          open
R109           367            365

Board is back in, and MC locks.
  1315   Mon Feb 16 23:09:52 2009 ranaUpdateElectronicsMC Servo Board offset gone bad!

The attached plot shows that someone broke the MC_SUM_MON channel around 10:30 AM this past Wednesday the 11th. This is the EPICS monitor of the MC error point.

Come forward now with your confession and I promise that I won't let Steve hurt you.

Attachment 1: mcoff.png
mcoff.png
  4331   Sun Feb 20 21:22:33 2011 rana, kiwamu, valeraConfigurationIOOMC Servo Change

For some reason, Kiwamu forced us to change the MC servo electronics today. We are now combining it with the FSS box.

The MC Servo by itself was locking by just driving the NPRO PZT. Becuase of the ~30 kHz mechanical resonances of that system, our badnwidth is limited. To get higher bandwidth, we can either use a wideband frequency shifter like the AOM or just use the ole FSS combo of PZT/EOM. The old MC servo was able to get 100 kHz because it used the AOM.

So we decided to try going through the FSS box. The MC servo board's FAST output now goes into the IN1 port (500 Ohm input impedance) of the TTFSS box. This allows us to use the FSS as a kind of crossover network driving the PZT/EOM combo.

At first it didn't work because of the 5V offset that Jenne, Larisa, Koji, and Suresh put into there, so I cut the wire on the board that connected the power to the summing resistor and re-installed the MC Servo board.

We also removed the old Jenne-SURF 3.7 MHz LP between the MC mixer and servo. Also removed the Kevin-box (1.6:40) stuck onto the NPRO PZT.

We have yet to measure the UGF, but it seems OK. The PCDRIVE is too high (~5-6V) so there is still some high frequency oscillation. Needs some investigation.

* To get the FSS SLOW servo to work (change NPRO temperature to minimize PZT drive onto NPRO) I set the setpoint to 5V in the script so that we operate the FSS box output at 5V mean. I set the threshold channel to point to MC_TRANS_SUM instead of RC_TRANSPD. I also had to fix the crontab on op340m so that it would point to the right scripto_cron script which runs the FSSSlowServo, RCThermalPID.pl, etc. I also had to fix scripto_cron itself since it had the old path definitions and was not loading up the EpicsTools.pm library.

** Also, I was flabbergasted by the dog clamping on the last turning mirror into the MC. Barely touching the mount changes the alignment.

  7198   Wed Aug 15 18:56:46 2012 YoichiUpdateIOOMC Servo Transfer Function Measurements

 I started working on the characterization of the MC servo.

The current MC servo topology is shown in the figure attached along with a simplified schematic diagram of the MC board. 

A usual way to measure the open loop gain of this servo is to inject a signal from, say, EXCA of the MC board and measure the transfer function from TP2A to TP1A. It works OK at frequencies around the UGF. The second attachment is the OPLTF measured in this way with the Agilent 4395A. The UGF is about 100kHz with the phase margin of 40 to 50 deg. 

Now we have two issues here. First, I expected the UGF to be more than 100kHz, like 300kHz or so. The phase babble is peaked around 100kHz. According to our old measurement (http://nodus.ligo.caltech.edu:8080/40m/1431) the phase babble peak was at a much higher frequency when the FSS was using the reference cavity. One reason could be that the MC is located much farther from the laser than the reference cavity, so that there is some phase lag caused by the time delay. I will make a model of the MC servo system later to check this theory.

The second issue is that, as you can see in the plot, the OPLTF measurement becomes noisy at lower frequencies. With 4395A, which has the minimum IFBW of 2Hz, OPLTF measurement below 10kHz was impossible with the traditional method. We could use SR785 with a long averaging time to improve the SNR, but it requires a patience which I don't have.

The measurement becomes difficult at low frequencies because the loop gain is too high. When the open loop gain (G) is high, the injected signal (x) from EXCA is immediately suppressed by a factor of 1/(1+G) at TP2A. This makes the injected signal hidden in other noises at TP2A.

How do we solve this problem ? Let's consider a simple servo model shown in the third attachment. A traditional OPLTF measurement is done by injecting a signal from EXC port and measuring the TF from TP2 to TP1. The problem was that at TP2, the signal is attenuated by 1/(1+G1*G2), which is too much when G (=G1*G2) is large. However, at TP3, the attenuated signal is amplified by G1. So the injected signal x becomes x*G1/(1+G) at TP3. If G1's contribution to the overall gain G is large enough,  the signal at TP3 is not so small. Then we can easily measure G2 using TP3 and TP1. In a typical situation, G1 is the transfer function of the electric circuits, which we can know either from standalone measurements or from model calculations, and G2 is an interferometer response, which we want to measure. So, by combining the knowledge of G1 and the measurement of G2, we can obtain the overall loop gain G even at lower frequencies.

 The final attachment shows an example of the measurement of G2. In our case, this is the transfer function from MC_Out_Mon to Q-Mon (see the first attachment) . G1 is the transfer function of the MC board. Since G1 is large at low frequencies, we can measure G2 down to 100Hz with a reasonable integration time (10000 cycles per point).

Last night, I took a bunch of TFs with this method. Now I'm analyzing the data to recover the overall gain G. I will post the results later.

Attachment 1: MC-Diagram.png
MC-Diagram.png
Attachment 2: OPLG-10kHz-1MHz.png
OPLG-10kHz-1MHz.png
Attachment 3: SimpleServoDiagram.png
SimpleServoDiagram.png
Attachment 4: OPTG-100Hz-1kHz.png
OPTG-100Hz-1kHz.png
  7201   Thu Aug 16 01:52:52 2012 YoichiUpdateIOOMC Servo Transfer Function Measurements

Quote:

Last night, I took a bunch of TFs with this method. Now I'm analyzing the data to recover the overall gain G. I will post the results later.

 I calculated the MC open loop transfer function with the combination method. For that, I made a circuit model of the MC board (from the input to the output). The transfer function of this circuit is calculated by SPICE (attachment1). Then it is multiplied by the measured transfer function from the output of the MC board to the input of the MC board (attachment 2) to get the overall transfer function.

The result is shown in the attachment 3. The blue curve is the OPLTF measured with the traditional method. The red curve is the combination method described above. There are some discrepancies between the two curves. The ratio of the two curves (Traditional)/(Combination) is plotted in attachment 4. It seems there is a pole(s) missing from my model of the MC board at around 1MHz. This may come from the omitted op-amps in the MC board model (there are so many op-amps which have flat responses below 1MHz and I omitted most of those). Also the MC board includes many generic filter stages to customize the frequency response. I will open the MC board box to examine what is actually implemented on the board. 

At low frequencies, the two curves are similar but the slope is still different.

I also had to add 83dB of gain to the combined TF to match with the traditional one. I will check where does it come from.

The MC board model (Altium project) is attached as attachment 6. The schematic is attachment 5.

Attachment 1: MC_Board_TF.png
MC_Board_TF.png
Attachment 2: OPTG.png
OPTG.png
Attachment 3: OPLG.png
OPLG.png
Attachment 4: Difference.png
Difference.png
Attachment 5: MC_Board.pdf
MC_Board.pdf
Attachment 6: MC_Board.zip
  7202   Thu Aug 16 05:08:38 2012 YoichiUpdateIOOMC Servo Transfer Function Measurements

Quote:

 Also the MC board includes many generic filter stages to customize the frequency response. I will open the MC board box to examine what is actually implemented on the board. 

 I took out the MC board. Unfortunately, most of the components are surface mounted. So the values of the capacitors are not legible.

I will try my best to guess what is implemented on the board.

Attachment 1: MCBoard1.JPG
MCBoard1.JPG
Attachment 2: MCBoard2.JPG
MCBoard2.JPG
  9714   Tue Mar 11 15:01:28 2014 ericqUpdateComputer Scripts / ProgramsMC Signal Monitoring

Two weeks ago (Feb 26) I took the "Q MON" output of the demodulator that sends its Q output to the MC servo board as the error signal, and connected it to an SR785, so we can occasionally monitor the error signal noise. (Also, I did not appropriately ELOG the fact I touched things...)

I'm working on an automated script to do the monitoring, but the wireless router that the SR785 is connected is wicked slow. I should run an ethernet cable to it...

I'm just figuring I'll look at the full span (~100kHz) spectrum every ten minutes, and compare it to some nominal spectrum from a known-good time, and the last few hours.

  5866   Thu Nov 10 20:20:57 2011 SureshUpdateIOOMC Spot positions have shifted after accelerometer installation on MC2 chamber

[ Jenne, Suresh ]

We were tying the fix the WFS and noticed that the PSL --> MC alignment was poor.   The PMC output was also at about 0.5 instead of its optimal 0.86 .   So Jenne started by first realinging the PMC input and pushed the PMC ouput to about 0.8  

Then we decided to fix the PSL--> MC alignment by using the zigzag.  After Jenne finished that, we realised that it was probably not the best thing to do since the MC2 might have shifted after the accelerometer installation on the MC2 chamber.

So I measured the spot positions and find that the MC2Y has shifted by about 3.6mm and  MC2P has shifted by about a mm.  There is also a shift of 2mm in MC3P, but hopefully it will go away when we adjust the MC2

 

    MC1P MC2P MC3P MC1Y MC2Y MC3Y
03Nov2011   0.1354 -0.2522 -0.1383 -1.0893 0.7122 -1.5587
04Nov2011   4.0411 4.4994 3.5564 -1.4170 -0.2606 -1.7109
08Nov2011   4.7341 4.8794  4.3907 1.3542 -3.0508 -1.7167
10Nov2011 ........ 3.9944 3.7676 6.1001 -1.3058 -3.8087 -1.6418

 

I am going to adjust the MC2 to recover its nominal position as marked above in green

  7290   Mon Aug 27 23:52:59 2012 JenneUpdateIOOMC Spots centered

Finally!

Jamie and I have the MC spots centered.  We did the normal move the input beam, realign jazz for a while, then when we got close, used the "move MC2 spot" scripts to get the MC2 spot back to ~center.

This was way easier when the measurements were real, and not just noise.  Funny that.

The dark blue spot is the farthest from 0 in pitch, and it is 1.04mm.  The cyan and yellow we've done a pretty good job of getting them equally far from zero.  Since we aren't translating the beam, we can't get better than the point at which the cyan and yellow curves cross.

Attachment 1: MCdecenter_26Aug2012.png
MCdecenter_26Aug2012.png
  3242   Sun Jul 18 20:50:03 2010 ranaConfigurationIOOMC TRANS optics changed

To make the beam on the MC trans camera bigger, I removed the lens + ND filter that was in that path.

The camera was getting the transmission through a BS1-33 (33% reflector). The reflection went to the TRANS QPD. I changed

the R=33% into an HR mirror (Y1-45P) so now the camera has a nice beam. The QPD was now saturating so I put a ND06 into that path

so now the TRANS_SUM is ~4.5-5 V when the MC is aligned.

The MC was also misaligned and failing to lock all weekend (why??) so I aligned the MC mirrors to get it to acquire again. Since we want to

collect MC seismic data, please make sure the MC is locked and running after finishing with your various MC or PSL work (this means YOU).

  91   Sun Nov 11 21:05:55 2007 ranaHowToSUSMC Touching or not
I wrote a script: SUS/freeswing-mc.csh, which gives the MC mirrors the appropriate kicks
needed to make a measurement of the free swinging peaks in the way that Sonia did.
#!/bin/csh

set ifo = C1
set sus = ${ifo}:SUS-

foreach opt (MC1 MC2 MC3)

  set c = `ezcaread -n ${sus}${opt}_PD_MAX_VAR`
  ezcastep ${sus}${opt}_PD_MAX_VAR +300

  ezcaswitch ${sus}${opt}_ULCOIL OFFSET ON
  ezcawrite ${sus}${opt}_ULCOIL_OFFSET 30000
  sleep 1
  ezcawrite ${sus}${opt}_ULCOIL_OFFSET 0
  sleep 1
  ezcawrite ${sus}${opt}_ULCOIL_OFFSET 30000
  sleep 1
  ezcawrite ${sus}${opt}_LATCH_OFF 0

  ezcawrite ${sus}${opt}_ULCOIL_OFFSET 0
  ezcaswitch ${sus}${opt}_ULCOIL OFFSET OFF

  ezcawrite ${sus}${opt}_PD_MAX_VAR $c

end

echo
date
echo

It basically ups the watchdog threshold, wacks it around at the pendulum frequency, and then disables the
optic so that there are no electronic forces applied to it besides the bias. The date command at the end
is so that you know when to start your DTT or mDV or lalapps code or whatever.
  4106   Tue Jan 4 15:12:33 2011 SureshUpdateIOOMC Trans Mon QPD gain decreased by 10

 Decreased the gain of MC-Trans-Mon QPD ckt

The resistors R1, R2, R3, R4 are now 49.9 kOhm. The previous elog on this subject 3882 has the ckt details. 

  3882   Mon Nov 8 18:30:33 2010 SureshUpdateIOOMC Trans Mon QPD gain increased by 50x

Increased the transimpedance gain of the MC-Trans-Mon QPD ckt

The gain of this QPD was insufficient to see the light transmitted through the MC2.  The resulting voltage output was about  10 steps of the 16-bit ADC card.  As the input power, which is currently held at about 40mW may be increased to the vicinity of 2W (total output of the NPRO) we would have 500 ADC steps.  But the dynamic range of the ADC is 64k and  increasing the gain of this QPD ckt by a factor of 50 would enable us to utilise this dynamic range effectively.  However as we do not need a response faster than 10Hz from this ckt its response time has been limited by increasing the feedback capacitance value.

The ckt diagram for the QPD ckt is D980325-Rev-C1  .  The particular unit we are dealing with has the Serial No. 110.  The resistors R1, R2, R3, R4 are now 499 kOhm.  As per the guidelines in the ckt diagram, we increased the capacitance values C3,C4,C5,C6 to 2.2 nFThe current cut off frequency for the MC-Trans-Mon is 145 Hz (computed).

Initially, while reassembling the QPD unit, the IDC 16 connector to the ckt board was reversed by mistake and resulted in the OP497 chip over-heating.  Consequently one of the opamps on the chip was damaged and showed monotonously increasing ouput voltage.  Todd Etzel gave us a spare OP497 and I replaced the damaged chip with this new one. The chips are also available from  Newark Stock No. 19M8991 . The connector has been marked to indicate the correct orientation. The ckt was checked by temporarily connecting it in the place of the PRM Optical lever QPD.  It worked fine and has been put back in its place at the MC2 Transmission.  The QPD was wiped with a lens tissue+Methanol  to remove dust and finger prints from its surface.

It may need to be repositioned since the beam would have shifted under the MC realignment procedure.

 

 

 

  2256   Thu Nov 12 16:13:05 2009 AlbertoUpdatePSLMC Trans Offset

On Rana's suggestion I checked the MC transmission QPD (C1:IOO-MC_TRANS_SUM). I found that the readout is almost zero when the MC is unlocked.

I unlocked the Mode Cleaner turning off the LSC control and disabling the autolocker. The QPD reads 0.014. It seems that there is no offset.

I also checked with the IR card around the photodetector and I didn't see any stray beam.

  2258   Thu Nov 12 17:15:43 2009 KojiUpdatePSLMC Trans Offset

OK. I have been keeping my eyes on the MC transmission. In deed, the MC trans has been well kept at around 7.7 since the last PSL work.
Even it was over the 8 today!

Quote:

On Rana's suggestion I checked the MC transmission QPD (C1:IOO-MC_TRANS_SUM). I found that the readout is almost zero when the MC is unlocked.

I unlocked the Mode Cleaner turning off the LSC control and disabling the autolocker. The QPD reads 0.014. It seems that there is no offset.

I also checked with the IR card around the photodetector and I didn't see any stray beam.

 

Attachment 1: MC_TRANS.png
MC_TRANS.png
  2260   Thu Nov 12 17:42:04 2009 KojiUpdatePSLMC Trans Offset

PC_DRIVE is also improving after the last PSL work!

Quote:

OK. I have been keeping my eyes on the MC transmission. In deed, the MC trans has been well kept at around 7.7 since the last PSL work.
Even it was over the 8 today!

 

Attachment 1: PC_DRV.png
PC_DRV.png
  5009   Wed Jul 20 23:31:44 2011 SureshUpdateIOOMC Trans QPD is down

 

The mode cleaner is not locking because the MC Trans QPD signal is not present.  There is light on the QPD when the MC flashes and its position has not shifted.  The cable is plugged in well into the sensor head.  The signal cable is labled "MC2 Opt Lever"  and it arrives on the 1X4 rack along with other Optical Lever cables. Pressing the connector in did not solve the problem.

 

  5012   Thu Jul 21 12:19:29 2011 Jamie, KiwamuUpdateIOOMC Trans QPD working, now locking

It turns out that the MC_TRANS_SUM signal was being derived from the SUS-MC2_OL_SUM_INMON channel in the ioo.db file. 

However, this channel name was recently changed to SUS-MC2_OLSUM_INMON (no underscore between OL and SUM) when

I added the new OL_SUM epics channel to the sus_single_control library model (I forgot to mention it in my previous log on this change,

apologies).  This is why there appeared to be no signal.  This was also what was preventing the mode cleaner from locking, since

the MC_TRANS_SUM signal is used as a trigger in the MC autolocker script.

We modified the ioo.db file at /cvs/cds/caltech/target/c1iool0/ioo.db [0,1] to change the name of the channel that the

C1:IOO-MC_TRANS_SUM signal is derived from.  The diff on the ioo.db file is:

--- /cvs/cds/caltech/target/c1iool0/ioo.db	2011-07-21 11:43:44.000000000 -0700
+++ /cvs/cds/caltech/target/c1iool0/ioo.db.2011Jul21	2011-07-21 11:43:36.000000000 -0700
@@ -303,7 +303,7 @@
 {
         field(DESC,"MC2 Trans QPD Sum")
         field(PREC,"1")
-        field(INPA, "C1:SUS-MC2_OLSUM_INMON")
+        field(INPA, "C1:SUS-MC2_OL_SUM_INMON")
         field(SCAN, ".1 second")
         field(CALC, "A+0.001")
 }

We then rebooted the c1iool0 machine, and when it came back up the MC_TRANS_SUM channel was showing the correct values.

We then found that the MC autolocker was not running, presumably because it had crashed after the channel rename?

In any event, we logged in to op340m and restarted the autolockerMCmain40m script.

The mode cleaner is now locked.

[0] Rana's log where this was initially defined

[1] All of the slow channel stuff is still in the old /cvs/cds/caltech path.  This needs to be fixed.

 

  5612   Tue Oct 4 14:41:47 2011 JenneUpdateIOOMC Trans channels are digital 0

I relocked the PMC (why is it unlocking so much lately??), and then noticed that even though the MC is locked, MC Trans Sum, P, Y, are all seeing digital zero.  I'm putting Suresh, as IOO guy, in charge of figuring it out.

  5614   Tue Oct 4 15:57:30 2011 SureshUpdateIOOMC Trans channels are digital 0

I thought this problem might be arising because the MC2_TRANS QPD signals are not being passed from the c1mcs to c1ioo models over the rfm.   But there was no way to check if there is any data being picked up in c1mcs model.  So I copied the MCTRANS block from the c1ioo model into the c1mcs.  This block takes the four segments of the MC2_TRANS QPD and computes the pitch, yaw and sum signals from that.   It also exports these into epics channels.  I then recompiled and started the c1ioo c1mcs and c1rfm models. 

Restared fb at

Tue Oct  4 15:19:10 PDT 2011

Koji then noted that the MC2_TRANS filter banks in c1rfm and in c1ioo were showing nonzero values.   So the signals were infact reaching the c1ioo model.  They were being blocked by the INMATRIX (which the autoburt had not restored) of the MC_TRANS block, because all its elements were zero.  We burtrestored the c1iooepics to about 30hrs ago and then MC_TRANS signals were back in the LOCK_MC screen.

 

  14950   Tue Oct 8 10:29:19 2019 gautamUpdateIOOMC Transmission scan

Summary:

There is ~ 7% variation in the power seen by the MC2 trans QPD, depending on the WFS offsets applied to the MC2 PIT/YAW loops. Some more interpretation is required however, before attributing this to spot-position-dependent loss variation inside the IMC cavity.

Analysis:

Attachment #1This shows a scatter plot of the MC2 transmission and IMC REFL average values after the WFS loops have converged to the set offset positions. The size of the points are proportional to the normalized variance of the quantity. The purpose of this plot is to show that there is significant variation of the transmission, much more than the variance of an individual datapoint during the course of the averaging (again, the size of the circles is only meant to be indicative, the actual variance in counts is much smaller and wouldn't be visible on this plot scale). For a critically coupled cavity, I would have expected that the TRANS/REFL to be perfectly anti-correlated, but in fact, they are, if anything, correleated. So maybe the WFS loops aren't exactly converging to optimize the inoput pointing for a given offset? 

Attachment #2Maps of the transmission/reflection as a function of the (YAW, PIT) offset applied. The radial coordinate does not yet mean anything physical - I have to figure out the calibration from offset counts to spot position motion on the optic in mm, to get an idea for how much we scanned the surface of the optic relative to the beam size. The gray circles indicate the datapoints, while the colormaps are scipy-based interpolation. 

Attachment #3After talking with Koji, I explicitly show the correlation structure between the IMC REFL DCMON and MC2 TRANS. The shaded ellipses indicate the 1, 2 and 3-sigma bounds for the 2D dataset going radially outwards. The correlation coefficient for this dataset is 0.46, which implies moderate positive correlation. 🤔 

Scan algorithm:

The following was implemented in a python scipt:

  1. Choose 2 independent random numbers from the uniform distribution in the interval [-0.5, 0.5] (in uncalibrated counts).
  2. One of these numebrs is set as the error point offset for the QPD spot-centering PITCH WFS loop, while the other is the YAW offset.
  3. Wait for 600 seconds - this long wait is required because the step-response time for these loops is long. 
  4. If there is an MC unlock event - wait till the MC relocks, and then another 600 seconds, to give the WFS loops sufficient time to converge.
  5. Once the WFS loops have converged, average a few data channels (MC TRANS, REFL, WFS loop error points etc) for 10 seconds, and write these to a file.

I am now setting the offsets to the WFS QPD loop to the place where there was maximum transmission, to see if this is repeatable. In fact it was. Looking at the QPD segment outputs, I noticed that the MC2 transmission spot was rather off-center on the photodiode. So I went to the MC2 in-air optical table and centered the beam till the output on the 4 segments were more balanced, see Attachment #4. Then I re-set the MC2 QPD offsets and re-enabled the WFS servos. The transmission is now a little lower at ~14,500 counts (but still higher than the ~14200 counts we had before), presumably because we have more of the brightest part of the beam falling on the gap between quadrants. For a more reliable measurement, we should use a single-element photodiode for the MC2 transmission.

Quote:
  • Overnight, I'm going to run the MC2 spot position scanning code (in a tmux session on pianosa, started ~945pm) to see if we can find a place where the transmission is higher,
Attachment 1: MC2_transmission_scatter.pdf
MC2_transmission_scatter.pdf
Attachment 2: transmissionMaps.pdf
transmissionMaps.pdf
Attachment 3: correlStructure.pdf
correlStructure.pdf
  1080   Thu Oct 23 23:09:18 2008 YoichiUpdatePSLMC UGF is now 75kHz
I measured three loop transfer functions of the MC servo.
The blue curve in the first attachment is the overall open loop gain of the servo measured using
the sum-amp A of the MC board (it is the sum-amp in the common part).
The red curve is the transfer function measured by the sum-amp B of the MC board, which is in the VCO path.
Mathematically the measured transfer function is G_vco/(1+G_L), where G_L is the loop gain of the length path
and G_vco is the loop gain of the VCO path.
The green curve is G_L/(1+G_vco) which was measured from dtt by using C1:SUS-MC2_MCL_EXC.
The UGF of the MC loop is 75kHz with the phase margin of 27deg.
The cross over frequency of the two loops is 43Hz. The phase margin there seems OK.

The second attachment is the comparison of the MC open loop TF measured on Sep. 4 (old) and today (new).
The increased bandwidth of the FSS gave us a slight gain in the phase margin and the elimination of
the slight bump in the gain around 150kHz existed in the blue curve.
Attachment 1: MC_Loop.png
MC_Loop.png
Attachment 2: OldAndNew.png
OldAndNew.png
  372   Wed Mar 12 23:05:44 2008 ranaUpdateIOOMC WFS
they are bad, somewhat

please fix
  601   Mon Jun 30 09:46:15 2008 JohnUpdateIOOMC WFS
MC WFS are on. They seem to do some good during the day.
  1556   Thu May 7 17:59:23 2009 AlbertoConfiguration MC WFS
This afternoon the MC could not get locked.
I first checked the Osems values at the MC mirrors and compared them to the trend of the last few hours. That showed that the alignment of the mirrors had slightly changed. I then brought each mirror back to its old alignment state.
 
That let the LSC loop lock the MC, although the reflected power was still high (1.5V) and the WFS control wouldn't engage.
 
Since earlier during the day I was working on the AS table, it is possible that I inadvertently hit the MC REFL beam splitter misaligning the beam to the MC WFS.
To exclude that there was a problem in the suspensions, before touching the WFS, I checked that the cables at the MC's ends and those going to the ADC in the rack were well pushed in.
 
Then I proceeded in centering the beam on both the WFS, balancing the power over the QPDs.
 
In the end the MC could lock again properly.
 
  868   Thu Aug 21 18:13:24 2008 ranaUpdateIOOMC WFS Control signals not responsible for lock losses
This is a 4 hour, second-trend of the MC WFS error and control signals.

There is no sign that the MC loses lock because of feedback signal saturations.
Attachment 1: Untitled.png
Untitled.png
ELOG V3.1.3-