40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 204 of 339  Not logged in ELOG logo
ID Date Author Type Categoryup Subject
  9349   Tue Nov 5 19:39:27 2013 JenneUpdateLSCOpLev time series

[Rana, Jenne]

We looked at the time series for all the oplevs except the BS, from last Tuesday night, during a time when we were building up the power in the arms.  We conclude from a 400 second stretch of data that there is not discernible difference in the amount of motion of any optic, when the cavities are at medium power, and when they're at low power.  Note however, that we don't have such a nice stretch of data for the really high powers, so the maximum arm power in these plots is around 5.  Both the TRX and TRY signals look fairly stationary up to powers of 1 or 2, but once you get to 4 or 5, the power fluctuations are much more significant.  So, since this isn't caused by any optic moving more, perhaps it's just that we're more sensitive to optic motion when we're closer to resonance in the arms.

However, from this plot, it looks like the ETMY is moving much more than any other optic.  On the other hand, ETMY has not ever been calibrated (there's an arbitrary 300 in there for the calibration numbers on the ETMY oplev screen).  So, perhaps it's not actually moving any more than other optics.  We should calibrate the ETM oplevs nicely, so we have some real numbers in there.  ETMX also only is roughly calibrated, relative to the OSEMs.  We should either do the move-the-QPD calibration, or a Kakeru-style pitch and yaw some mirrors and look at transmitted power.

Traces on this xml file have been filtered with DTT, using zpk([0],[0.03],1,"n").

OpLevs_during_PRMI_2arms.pdf

 

  9353   Wed Nov 6 14:47:41 2013 SteveFrogsLSCDin connectors added at 1Y2

 The north side of the LSC rack is full. I installed more DIN connectors with fuses on the south side of the rack 1Y2

The access to this may be a little bit awkward. You just remove the connector, wire it and put it back in.

 

Attachment 1: 1Y2moreDinFuses.jpg
1Y2moreDinFuses.jpg
  9355   Wed Nov 6 15:57:22 2013 JenneUpdateLSCPower Supply solution

We have decided that, rather than replacing the power source for the amplifiers that are on the rack, and leaving the Thorlabs PD as POP22/110, we will remove all of the temporary elements, and put in something more permanent.

So, I have taken the broadband PDs from Zach's Gyro experiment in the ATF.  We will figure out what needs to be done to modify these to notch out unwanted frequencies, and amplify the signal nicely.  We will also create a pair of cables - one for power from the LSC rack, and one for signal back to the LSC rack.  Then we'll swap out the currently installed Thorlabs PD and replace it with a broadband PD.

  9360   Thu Nov 7 14:39:49 2013 JenneUpdateLSCLock Acquisition Game Plan

Between the 40m meeting, and chatting with Gabriele, there was lots of talking yesterday about our 40m Lock Acquisition game plan. 

From those talks, here is my current understanding of the plan, in a Ward-style cartoon:

 LockAcquisition_7Nov2013.pdf(This is a 2 page document - description of steps is on 2nd page)

If you look closely, you will notice that there are several places that I have used "?" rather than numbers, to indicate what RFPD signal we should be using.  To fill these in, I need to look at some more simulations, and think more carefully about what signals exist at what ports, and what SNR we have at each of those ports.

Also, while the overall scale of the arm power plot is correct, the power level at each step is totally arbitrary right now, and should just be taken to mean places (in time) where the CARM offset is reduced a little more.


There are several things at this point that we know we need to look into:

* POP 22/110 PD and filtering electronics should be switched to a broadband PD, rather than the Thorlabs PD + Miniciruits filters. (Hardware)

* Whitening for the transmission QPDs needs to be thought about more carefully. (Calculation, then hardware)

* Chose a good SNR REFL DC signal, which may or may not be from the PD we are currently using (I think it's the DC of REFL11, but I'll have to check). (Calculation)

* For DRMI locking, what is the size of the SRCL error signal at AS55, AS165, and the REFL ports?  Do we need to lock with AS port, and then switch over to a REFL 3f port, to make acquisition easier?  (Simulation)

* Similarly, I want to make the equivalent of Figure 3 of T1000294, with our 40m parameters. (Simulation)

* To set the phase of AS110, simulate the demod phase of AS110 in both DRMI and SRMI cases.  If no (significant) change, maybe we can set the phase in the real system by misaligning the PRM, and watching the SRMI flash.  (Simulation)

* Simulate an arm sweep, up to many orders of the sidebands, to see how close to the carrier resonance any sideband resonances might be.  If something like the 4th order sideband resonates, and then beats with a 1st order sideband, is that signal big enough to disturb our 3f locking of the PRMI / DRMI?  We want to be holding the arms off resonance with ALS closer to the carrier than any "important" sideband resonances (where the definition of "important" is still undetermined).  (Simulation)

* Check if we can hand DARM from the DC transmission signals to the final RF signal while we still have a large CARM offset. Is there a point where the CARM offset is too large, and we must be still using the DC signals? (Simulation)

* At what arm power level can we transition from ALS to IR DC transmission signals for the individual arms? (Simulation)

* Still need to finish calculating what could be causing our big arm power fluctuations (Test mass angular motion?  PRM angular motion? ALS noise?) (Calculation)


Replys, and comments are welcome, particularly to help me understand where I may have (likely did) go wrong in drawing my cartoon. 

  9361   Fri Nov 8 17:19:27 2013 JenneUpdateLSCNew Broadband PD for POP 22/110

Here is a photo of the board inside the broadband photodiode (one of them) that I took from the Gyro experiment:

IMG_1255.JPG

This PD is Serial Number S1200271.

We need to have a look at the schematic, figure out what's in here now, and then modify this to be useful (appropriate resonances / notches, as well as amplification) for POP 22/110.

  9362   Fri Nov 8 18:12:21 2013 JenneUpdateLSCPRFPMI: Not crossing any resonances

Quote:

There are several things at this point that we know we need to look into:

* Simulate an arm sweep, up to many orders of the sidebands, to see how close to the carrier resonance any sideband resonances might be.  If something like the 4th order sideband resonates, and then beats with a 1st order sideband, is that signal big enough to disturb our 3f locking of the PRMI / DRMI?  We want to be holding the arms off resonance with ALS closer to the carrier than any "important" sideband resonances (where the definition of "important" is still undetermined).  (Simulation)

 I have done a sweep of CARM, while looking at the fields inside of one arm (I've chosen the Xarm), to see where any resonances might be, that could be causing us trouble in keeping the PRMI locked as we bring the arms into resonance. 

2f_resonances_Xarm_CARMsweep.png

Since Gabriele pointed out to me that we're using the 3x55MHz signal for locking, we should be most concerned about resonances of the higher orders of 55, and not of 11.  So, on this plot, I have up to the 6th order 55 MHz sidebands, which are 332 MHz.  Although the Matlab default color chart has wrapped around, it's clear that the carrier is the carrier, and the +4f2, which is the same blue, is not the giant central peak.  So, it's kind of clear which trace is which, even though the legend colors are degenerate.  Also, the main point that I want to show here is that there is nothing going on near the carrier, with any relevant amplitude.  The nearest things are the plus and minus 55 MHz sidebands themselves, and they're more than 50 nm away from the carrier. 

Recalling from elog 9122, the PRFPMI and DRFPMI linewidths are about 40pm.  50pm away from the resonant point is ~1/10 the power, and 100pm away from the resonant point is ~1/100 the power.  So, 50 nm is a looooong ways away. 

Just for kicks, here is a plot of all the resonances of the 1f and 2f modulation frequencies, up to 30*f1, which is the same 6*f2:

AllModFreq_resonances_Xarm_CARMsweep.png

The resonances which are "close" to the carrier are the 9th order 11 MHz sidebands, and they're 280pm from the carrier, so twice as far as we need to be, to get our arm powers to ~1/100 of the maximum, and, they're a factor of ~1e4 smaller than the carrier.

  9363   Sat Nov 9 10:25:43 2013 KojiUpdateLSCNew Broadband PD for POP 22/110

General Remarks on the BBPD

- To form the LC network: Use fixed SMD inductors from Coilcraft. SMD tunable capacitors are found in the shelf right next to Steve's desk.
  If the tuning is too coarse, combine an appropriate fixed ceramic SMC C and the tunable C (in parallel, of course)

- L1/C1a/C1b pads are specifically designed for an additional notch

- Another notch at the diode stage can be formed between the middle PD pin (just left of the marking "C3b") to the large GND pad (between C1a/C1b to C3a).
  You have to scratch off the green resin with a small flat screw driver (or anything similar)

- A notch at the amplifier stage can be formed between the output of MAR-6SM ("+" marking)  and one of the GND pads (left side of the "U1" marking)

- The original design of the PD is broadband. So additional notches on the diode stage provides notches and resonances.
  Check if the resonances do not hit the signal frequencies.

- One would think the PD can have resonant feature to reduce the coupling of the undesired signals.
  In some sense it is possible but it will be different from the usual resonant tank circuit in the following two points.

  * Just adding a parallel L between the cathode and ground does not work. As this DC current should be directed to the DC path,
    L&C combo should be added. In fact this actually give a notch-resonance pair. This C should be big enough so that you can ignore it
    at the target resonant frequency. Supply complimentary small C if necessary to keep low impedance of the Cs at the target frequency.
    (i.e. Check SRF - self-resonant frequency of the big C)

  * Since the input impedance of MAR-6SM is 50Ohm, the top of the resonant curve will be cut at 50Ohm. So the resultant shape looks
    like a bandpass rather than a resonance.

- So in total, simulation of the circuit is very important to shape the transimpedance. And, consider the circuit can not be formed as simulated
  because of many practical imperfections like stray Ls and Cs.

 

  9367   Tue Nov 12 16:49:22 2013 JenneUpdateLSCXend QPD and Whitening board pulled

Quote:

* Whitening for the transmission QPDs needs to be thought about more carefully. (Calculation, then hardware)

 I have the X end transmission QPD, as well as the whitening board, out on the electronics bench.  Since the Thorlabs high-gain TRX PD also goes through this whitening board, we have no transmission signal for the Xarm at this time. The whitening board was in the left-most slot, of the top crate in the Xend rack.  The only cables that exist for it (like the Yend), are the ribbon from the QPD, the 4-pin lemo from the Thorlabs PD, and the ribbon going to the ADC.

I have taken photos, and want to make sure that I know what is going on on the circuits, before I put them back in. 

The QPD:

IMG_1262.JPG

IMG_1260.JPG

The whitening board:

IMG_1264.JPG

IMG_1276.JPG

  9371   Wed Nov 13 01:35:40 2013 JenneUpdateLSCPRM motion causing trouble?

Quote:

* Still need to finish calculating what could be causing our big arm power fluctuations (Test mass angular motion?  PRM angular motion? ALS noise?) (Calculation)

 I think that our problem of seeing significant arm power fluctuations while we bring the arms into resonance during PRMI+arms tests is coming from PRM motion. I've done 3 calculations, so I will describe below why I think the first two are not the culprit, and then why I think the PRM motion is our dominant problem.

===============================================================

ALS length fluctuations

Arm length fluctuations seem not to be a huge problem for us right now, in terms of what is causing our arm power fluctuations.

What I have done is to calculate the derivative of the power in the arm cavity, using the power buildup that optickle gives me. The interferometer configuration I'm using is PRFPMI, and I'm doing a CARM sweep. Then, I look at the power in one arm cavity. The derivative gives me Watts buildup per meter CARM motion, at various CARM offsets. Then, I multiply the derivative by 60 nm, which is my memory of the latest good rms motion of the ALS system here at the 40m. I finally divide by the carrier buildup in the arm at each offset, to give me an approximation of the RIN at any CARM offset.

I don't know exactly what the calibration is for our ALS offset counts, but since we are not seeing maximum arm cavity buildup yet, we aren't very close to zero CARM offset. 

From this plot, I conclude that we have to be quite close to zero offset for arm length fluctuations to explain the large arm power fluctuations we have been seeing.

 xarmRIN_vs_CARM.png

=======================================================================

AS port contrast defect from ETM motion

For this calculation, I considered how much AS port contrast defect we might expect to see given some ETM motion. From that, I considered what the effect would be on the power recycling buildup. 

Rather than doing the integrals out, I ended up doing a numerical analysis. I created 2 Gaussian beams, subtracted the fields, then calculated the total power left. I did this for several separations of the beams to get a plot of contrast defect vs. separation. My simulated Gaussian beams have a FWHM of 1 unit, so the x-axis of the plot below is in units of spot motion normalized by spot size. 

Unfortunately, my normalization isn't perfect, so 2 perfectly constructively interfering beams have a total power of 0.3, so my y-axis should all be divided by 0.3. 

The actual beam separation that we might expect at the AS port from some ETM motion (of order 1e-6 radians) causing some beam axis shift is of the order 1e-5 meters, while the beam spot size is of the order 1e-3 meters. So, in normalized units, that's about 1e-2. I probably should change the x-axis to log as well, but you can see that the contrast defect for that size beam separation is very small. To make a significant difference in the power recycling cavity gain, the contrast defect, which is the Michelson transmission, should be close to the transmission of the PRM. Since that's not true, I conclude that ETM angular motion leading to PRC losses is not an issue. 

I still haven't calculated the effect of ITM motion, nor have I calculated either test mass' angular effect directly on arm cavity power loss, so those are yet to be done, although I suspect that they aren't our problem either. 

ASportOverlap_moveGaussianBeams.png

========================================================================

PRM motion

 

I think that the PRM moving around, thus causing a loss in recycling gain, is our major problem. 

First, how do I conclude that, then some thoughts on why the PRM is moving at all. 

=========

theta = 12e-6 radians (ref: oplev plot from elog 9338 last week)

L = 6.781 meters

g = 0.94

a = theta * L /(1-g) = 0.0014 meters axis displacement

w0 = 3e-3 meters = spot size at ITM

a^2/w0^2 = 0.204 ==>> 20% power loss into higher order modes due to PRM motion.

That means 20% less power circulating, hitting the ITMs, so less power going into the arm cavities, so less power buildup. This isn't 50%, but it is fairly substantial, using angular fluctuation numbers that we saw during our PRMI+arms test last week. If you look at the oplev plot from that test, you will notice that when the arm power is high (as is POP), the PRM moves significantly more than when the carrier buildup in the cavities was low. The rms motion is not 12 urad, but the peak-to-peak motion can occasionally be that large. 

So, why is that? Rana and I had a look, and it is clear that there is a difference in PRM motion when the IFO is aligned and flashing, versus aligned, but PSL shutter is closed. Written the cavities flash, the PRM gets a kick. Our current theory is that some scattered light in the PRC or the BS chamber is getting into the PRM's OSEMs, causing a spike in their error signal, and this causes the damping loops to push on the optic. 

We should think a little more on why the PRM is moving so much more that any other optic while the power is building up, and if there is anything we can do about the situation without venting. If we have to, we should consider putting aluminum foil beam blocks to protect the PRM's OSEMs. 

  9373   Wed Nov 13 09:31:15 2013 GabrieleUpdateLSCPRM motion causing trouble?

Interesting results. When you compute the effect of ETM motion, you maybe should also consider that moving around the arm cavity axis changes the matching of the input beam with the cavity, and thus the coupling between PRC and arms. But I believe this effect is of the same order of the one you computed, so maybe there is only one or two factors of two to add. This do not change significantly the conclusion.

Instead, the numbers you're giving for PRM motion are interesting. Since I almost never believe computations before I see that an experiment agrees with them, I suggest that you try to prove experimentally your statement. The simplest way is to use a scatter plot as I suggested the past week: you plot the carrier arm power vs PRM optical lever signals in a scatter plot. If there is no correlation between the two motions, you should see a round fuzzy ball in the plot. Otherwise, you will se some non trivial shape. Here is an example: https://tds.ego-gw.it/itf/osl_virgo/index.php?callRep=18918

 

  9378   Wed Nov 13 19:22:58 2013 JenneUpdateLSCPRM motion correlated to intracavity power

[Gabriele, Jenne]

Nic and Evan put the ISS together (elog 9376), and we used an injection into the error point (?) to modulate the laser power before the PMC (The AOM had a bias offset, but there is no loop).  This gives us some RIN, that we can try to correlate with the PRM OSEM sensors. 

We injected several lines, around 100, 200, 500 and 800 Hz.  For 100, 200 and 800 Hz lines, we see a ratio between POPDC and the OSEM sensors of 1e-4, but at 500 Hz, the ratio was more like 1e-3. We're not sure why this ratio difference exists, but it does.  These ratios were true for the 4 face OSEMs.  The side OSEM saw a slightly smaller signal.  

For these measurements, the PRMI was sideband locked, and we were driving the AOM with an amplitude of 10,000 counts (I don't know what the calibration is between counts and actual drive, which is why we're looking at the POPDC to sensor *ratio*).  

To get a more precise number, we may want to consider locking the PRMI on carrier, so we have more power in the cavity, and so more signal in the OSEMs.  

These ratios look, by eye, similar to the ratios we see from the time back on 30 Oct when we were doing the PRMI+2arms test, and the arms were resonating about 50 units.  So, that is nice to see some consistency.

AOMmodulated_POPDC_OSEM.pdf

This time series is from 1067163395 + 27 seconds, from 30 Oct 2013 when we did the PRMI+2arms.

POPDC_sensors_30oct2013.png

 


Ideas to go forward:

We should think about chopping the OSEM LEDs, and demodulating the PD sensors. 

We should also take a look in the chamber with a camera from the viewport on the north side of the BS chamber, to see if we see any flashes in the chamber that could be going into the OSEMs, to see where we should maybe put aluminum foil shields.

  9382   Thu Nov 14 02:50:43 2013 JenneUpdateLSCPRM oplev measured and modeled TF

In the process of figuring out what we can do to fix our PRM motion problem, I am looking at the PRM oplev. 

Eventually (as in, tomorrow), I'd like to be able to simulate some optic motion as a result of an impulse, and see what the oplev loops do to that motion.  (For starters, I'll take the impulse response of the OSEM loop as my time series that the oplev loop sees).

One thing that I have done is look at the oplev model that Rana put together, which is now in the noisebudget svn: /ligo/svncommon/NbSVN/aligonoisebudget/trunk/OpLev/C1

This script plots the open loop gain of the modeled oplev:

PRM_OL_TF_model.png

This should be compared to the pitch and yaw measured transfer functions:

 PRM_OLPIT_TF.pdf

PRM_OLYAW_TF.pdf

In the YAW plot, there are 2 transfer functions.  The first time around, the UGF was ~2.5Hz, which is too low, so I increased the gain in the C1:SUS-PRM_OLYAW filter bank from -3 to -9. 

The shapes of the measured and modeled transfer functions look reasonably similar, but I haven't done a plot overlay.  I suspect that the reason I don't see the same height peak as in the model is just that I'm not taking a huge number of points.  However, if the other parts of the TF line up, I'll assume that that's okay.

I want to make sure that the modeled transfer function matches the measured ones, so that I know I can trust the model.  Then, I'll figure out how to use the time series data with the simulated loop.  Ideally, I'd like to see that the oplev loop can fully squish the motion from the OSEM kicks.  Once I get something that looks good (by hand-tweaking the filter shape), I'll give it a try in the actual system.  We should, as soon as I get the optimal stuff working, redo this in a more optimal way.  Both now, and after I get an optimal design, I'll look at the actual step and impulse responses of the loop, to make sure there aren't any hidden instabilities.

Other thoughts for the night:

Rana suggests increasing the gain in some of the oplev QPD heads (including PRM), so that we're getting more than a few hundred counts of power on each quadrant.  Since our ADCs go to 32,000 counts, a few hundred is very small, and keeping us close to our noise limits.

Also, just an observation, but when I watch the REFL camera along with POP and AS, it's clear that the PRM is getting kicked, and I don't have the ETMs aligned right now, so this is just PRMI flashes.  There is also a lot of glow in the BS chamber during flashes (as seen on the PRM face video camera).

  9401   Mon Nov 18 21:02:54 2013 JenneUpdateLSCPRM oplev measured and modeled TF

I have created a new filter for the PRM oplev damping loops.  The biggest change is an increase in the gain between 0.4 - 7 Hz.

Here is a plot of the old, and my new modelled open loop gain:

PRM_OLG_NewOld.png

When I look at my step and impulse response time series, the notches for the bounce and roll were causing some ringing, so for now they are turned off, both in the model and in the real time system.  Also, the "OLG orig" trace has a 4th order elliptic lowpass at 75 Hz, but the real system had a 4th order elliptic low pass at 35 Hz.  When we use 35 Hz in the model, we get lots of ringing.  So, we have moved both model and real system to 55 Hz 4th order elliptic low passes.  Also, also, we haven't been using the 3.3 Hz resonant gain, so I removed that from the modelled loop.

I have put the "boost" for the .4-7 Hz emphasis into FM 7 of the PRM oplev filters.  I also removed several old filters that are never used.  So, for now, the PRM oplevs should have engaged:  FM 1, 7, 9. Pitch gain is +5, yaw gain is -9.  We can consider re-implementing the bounce-roll notches, and the stack resgain if it looks like those are getting rung up, and causing trouble.

Here is a set of spectra, showing the improvement.  It's unclear why yaw is worse than pitch below 4Hz, and why pitch is so much worse than yaw between 4-15 Hz, however for each of pitch and yaw, the before (reference pink and cyan traces) is higher than the improved (dark red, dark blue traces) between a few tenths of a Hz up to 3ish Hz.  And, we're not causing more noise elsewhere.  We do want to monitor to make sure we're not ringing up the bounce and roll modes, but for now they seem fine.

PRM_oplev_improvement.pdf

  9404   Mon Nov 18 21:40:24 2013 KojiUpdateLSCPRM oplev measured and modeled TF

I forgot how we could turn on the PRM oplev servo and the PRM ASC servo at the same time without conflict.
It seems that this new oplev servo covers 0.04 to 8Hz. It's pretty broadband. Do we inject the ASC signal to the oplev error?

  9405   Tue Nov 19 00:07:16 2013 JenneUpdateLSCGreen status

After I aligned the IR interferometer (no ASS - we still need to figure out what's going on with that), I am trying to find the green beatnotes for each arm.

First, I locked the green lasers to each arm.

I then went out to the PSL table and aligned the Green Yarm path by overlapping the near-field and far-field of the yarm transmission and the PSL green pickoff.  I then turned on the power for the Beat PDs, since it was off (I confirmed that the outputs were plugged into the beatbox, so they are seeing 50 ohms).  I assume that the beat PDs were off since Manasa pulled the Beatbox last week, but there is no elog reference!!  Anyhow, after seeing a real signal, I maximized the DC power on the beat PD for the Yarm.  I then maximized the light on the DC transmission PD for the Yarm.

I looked at the Xarm, and the near-field alignment looks okay, but I haven't checked the far-field.

I started looking for the beatnotes from the control room:

I am changing the SLOW_SERVO2_OFFSETs by 30 counts, and then unlocking and relocking the arms, and checking to see if I see a peak on the RF spectrum analyser. 

The Y offset started at -10320, and I found a beatnote at -11230 (beatnote is about 26MHz).  The X offset started at 4500.  Going larger seemed to get me to a less bright TEM00 mode, so I switched and have been searching by going down in offset, but haven't yet found the beatnote.  I suspect that I actually need to align the X path on the PSL table.  The Y beatnote is very small, about -30dBm, so I also need to tweak the alignment by maximizing the peak value.

  9406   Tue Nov 19 00:18:30 2013 JenneUpdateLSCGreen ALS wishlist

EricQ said that he's going to start hanging out at the 40m a bit, and I was thinking about what I can have him help me with.  This lead to me writing up a wishlist for things that have to do with the ALS system and green lasers.  Some of these are very small tasks, while others are pretty big.  They are certainly not all high priority.  But, they're on my wishlist.

Calibrations

  • How many counts of SLOW_SERVO2_OFFSET is one green FSR (for each arm)?
  • Calibrate ALS OFFSETTER#_OFFSET counts to nm or Hz offset between the end lasers and the PSL.

Automation / script writing

  • Automate finding the beatnotes (requires freq counters)
  • Automate locking the ALS

Digital Acquisition

  • All 3 laser temperatures
  • Frequency counting of beatnotes

Hardware

  • Install flipper mirrors on the PSL table to switch between trans DCPDs and far-field views of beam overlap for each arm.
  • IR beatnote project - send pickoff of end lasers to PSL via fiber, set up beat detection for each arm, create PLLs.
  • Yarm PZT installation and autoalignment.
  9407   Tue Nov 19 01:11:19 2013 JenneUpdateLSCGreen status

I am able to lock the Yarm ALS, but not at the full gain that I should be.  I attribute this to my mediocre alignment of the path on the PSL table.  EDIT: Manasa pointed out that I forgot to set the PSL FSS slow adjust to ~zero, so the PSL temperature was off, so there wasn't really any hope for me last night.

However, I decided that I should write down the ALS locking procedure, as shown to me by Masayuki on 29Oct2013, that is written in one of the Control Room notebooks.  So, here it is.  I will write channel names and DTT template names for the Y arm, but the procedure is the same for both arms.

  1. Lock and align arms using IR.
  2. Lock green beams to arms.
  3. Align green beams to arms.
  4. Check beatnote alignment on PSL table.
  5. Find beatnote by changing end laser temperature (C1:ALS-Y_SLOW_SERVO2_OFFSET) in steps of ~30, watch spectrum analyser for peak.  Easier if arms are locked in IR, but disable LSC system before moving to step 6.  Beatnote should be less than ~50 MHz, and should have a peak height of about -20dBm or more.  When doing 2 arms, be careful that beatnotes of the different arms do not overlap in frequency.  Manasa reminds me that you must also remember to set the PSL FSS SLOW actuator adjust to near zero, to get the PSL back near its nominal temperature.
  6. Check UGF of phase tracker loop.  (DTT template in /users/Templates/ALS/YALS_PT_OLTF.xml) Want UGF to be ~2kHz.  Change C1:ALS0BEATY_FINE_PHASE_GAIN as necessary.
  7. Start the watch script from the ALS screen to watch for lockloss.
  8. Look at the PHASE_OUT spectrum (DTT template in /users/Templates/ALS/ALS.xml).
  9. Clear history of Phase Tracker Loop (clear hist button on C1:ALS-BEATY-FINE_PHASE screen).  Very important to do this before step 10, every time you get to step 10  (i.e. if you lose lock and are starting over)!
  10. Check sign of loop gain by using + or - 0.1 for the gain (C1:ALS-YARM_GAIN).  Beatnote should immediately stop moving if you have the sign right.  Otherwise, it'll zip around (if it does, repeat step 9, step 10).
  11. Turn gain of ALS up to ~15.  Watch the PHASE_OUT spectrum, look for the servo bump.  When you see it, back off the gain a little.  Gain of ~15 is usually about the right ballpark.
  12. Turn on FM 2, 3, 6, 7, 8 of C1:ALS-YARM.  (FM5 should already have been on).
  13. Wait for PHASE_OUT spectrum to come down.  Turn on FM10 of C1:ALS-YARM.
  14. Check UGF of ALS loop (DTT template in /users/Templates/ALS/YALS_OLTF.xml).  Want UGF to be about 150 or 170 Hz (at the peak of the phase bubble).  Adjust C1:ALS-YARM_GAIN as necessary.
  15. ALS is locked!  Use something like the "Scan Arm" script from the ALS screen to find IR resonance, or do whatever measurement you want.  Dataviewer template /users/Templates/Dataviewer_Templates/ALSdtv.xml may be useful.
  9409   Tue Nov 19 11:56:10 2013 manasa, jenne, ericQUpdateLSCPRM- OSEM side ccd camera is in place

Quote:

Quote:

Can't we somehow hook up this camera to the MUX with the movie mode?
I think both the MUX and the sensoray are compatible with the color video signal.
Only the old CRT is B/W.

 Watek ccd with Tamron lens is hooked up to MUX

This set up close to the viewport glass! Please be careful!

 Video captures when power recycling cavity is locked (videos 1 & 2) and flashing (video 3). Arms stayed misaligned.

1. CH1 and CH2 are loooking at PRM front and back faces. CH3 and CH4 are looking at POP and REFL

 2. CH1 and CH2 are loooking at PRM front and back faces. CH3 and CH4 are looking at the ITMs

3. CH1 and CH2 are loooking at PRM front and back faces. CH3 and CH4 are looking at POP and REFL

  9410   Tue Nov 19 14:47:44 2013 JenneUpdateLSCPRM oplev measured and modeled TF

Quote:

I forgot how we could turn on the PRM oplev servo and the PRM ASC servo at the same time without conflict.
It seems that this new oplev servo covers 0.04 to 8Hz. It's pretty broadband. Do we inject the ASC signal to the oplev error?

 Right now all 3 servos that control PRM angle (OSEM damping, Oplev, and ASC) run in parallel, and they're all AC coupled. 

  9411   Tue Nov 19 14:47:59 2013 manasaUpdateLSCGreen status

Quote:

After I aligned the IR interferometer (no ASS - we still need to figure out what's going on with that), I am trying to find the green beatnotes for each arm.

First, I locked the green lasers to each arm.

I then went out to the PSL table and aligned the Green Yarm path by overlapping the near-field and far-field of the yarm transmission and the PSL green pickoff.  I then turned on the power for the Beat PDs, since it was off (I confirmed that the outputs were plugged into the beatbox, so they are seeing 50 ohms).  I assume that the beat PDs were off since Manasa pulled the Beatbox last week, but there is no elog reference!!  Anyhow, after seeing a real signal, I maximized the DC power on the beat PD for the Yarm.  I then maximized the light on the DC transmission PD for the Yarm.

I looked at the Xarm, and the near-field alignment looks okay, but I haven't checked the far-field.

I started looking for the beatnotes from the control room:

I am changing the SLOW_SERVO2_OFFSETs by 30 counts, and then unlocking and relocking the arms, and checking to see if I see a peak on the RF spectrum analyser. 

The Y offset started at -10320, and I found a beatnote at -11230 (beatnote is about 26MHz).  The X offset started at 4500.  Going larger seemed to get me to a less bright TEM00 mode, so I switched and have been searching by going down in offset, but haven't yet found the beatnote.  I suspect that I actually need to align the X path on the PSL table.  The Y beatnote is very small, about -30dBm, so I also need to tweak the alignment by maximizing the peak value.

 I found the beatnotes for both the X and Y arm ALS this morning. The beat amplitudes measured -5dBm and -18dBm respectively and occurred at SLOW SERVO2 OFFSET 4550 and -10340. I had to only tweak the Y green PSL alignment to increase the beat amplitude.

I locked both the arms using ALS and they were stably locked until MC unlocked for a moment (nearly 16 minutes).

The only thing missing in the list of things you looked into is the status of the PSL slow actuator adjust. Check if this is near zero.

  9413   Tue Nov 19 17:47:17 2013 JenneUpdateLSCPRMI+2arms attempt

So far this afternoon, I have redone the IFO alignment, locked both arms with ALS, moved both arms off resonance, locked PRMI, and started bringing one arm back to resonance. 

The alignment was really not good, which I knew yesterday, but the ASS wasn't working yesterday.  I hand-did the alignment, and tried locking, which was easier with the slightly better alignment.

I locked both arms with ALS, found the resonances, and then moved them off resonance using Masayuki's scripts.

I then restored the PRM alignment, and locked the PRMI. 

I started bringing the Yarm back, but I kept losing lock when I got to about 0.1 transmission.


After losing lock several times, I switched over to looking at the ASS. I have figured out the problem, and fixed it.  The ASS for the arms now works again.

Looking at the StripTool plots of the lockin outputs for each arm, it was clear that the "L" traces were their usual size, but the "T" traces, which are demodulated versions of the transmission DC PDs, were tiny.  I investigated in the model, and the answer is obvious:  both the LSC and the ASS get the transmission information directly from the end sus computers.  Since we recently moved the normalization gain for the transmission diodes into the SUS models from the LSC model, this means that the ASS was seeing a differently sized signal than it had in the past. 

To fix this, I put a gain into the T_DEMOD_SIG filter banks for all 8 lockins that use info from the transmission DC PDs.  I used 1/g , where g is the gain that is in the C1:SUS-ETM#_TR#_GAIN channels.  For TRX, that number is -0.003, and for TRY that number is 0.002 .  So, in the .snap file that is used when turning on the ASS, I have given the Xarm lockins a gain of -333, and the Yarm lockins a gain of 500.  I chose this place, because the only thing that has happened to the signal until this point is a bandpass, so the rest of the servo gains can remain the same. 

I tested the ASS, and it works just like it used to.  I let it run, and align all of the optics, then I misaligned by a small amount each of the ETMs, saw that the lockin output values changed, and then were servoed back to zero.  So, it seems all good. 

  9414   Tue Nov 19 21:28:05 2013 manasaUpdateLSCPRMI carrier locking

Since we have never tried to lock PRMI on carrier after the folding mirrors were flipped, I tried to lock PRCL on carrier.

I thought this might give us some idea about the PRC stability for resonance or some clue as to what happens to the PRM suspensions and PRMI stability when we have carrier resonating in the cavity.

I changed the sign of the PRCL gain and also tried increasing the gain. But this did not work and I was not able to carrier lock PRMI. May be I am missing to change some parameter that is very trivial?

  9415   Tue Nov 19 21:59:35 2013 manasaUpdateLSCPRMI carrier locking

Quote:

Since we have never tried to lock PRMI on carrier after the folding mirrors were flipped, I tried to lock PRCL on carrier.

I thought this might give us some idea about the PRC stability for resonance or some clue as to what happens to the PRM suspensions and PRMI stability when we have carrier resonating in the cavity.

I changed the sign of the PRCL gain and also tried increasing the gain. But this did not work and I was not able to carrier lock PRMI. May be I am missing to change some parameter that is very trivial?

PRMI could not be locked on carrier using 3f. The configuration from the last time when PRMI was carrier locked (elog) were used and PRMI locked on carrier with these settings.

== PRMI carrier ==
  MICH: AS55_Q_ERR, AS55_PHASE_R = -12 deg,  MICH_GAIN = -0.2, feedback to ITMX(-1),ITMY(+1)
  PRCL: REFL55_I_ERR, REFL55_PHASE_R = 70 deg, PRCL_GAIN = 1.0, feedback to PRM

Below is the video capture showing the PRM front and back face when carrier flashes with few second locks.

EDIT by JCD:

The demod phase numbers that Manasa is quoting above were correct back in March, when the elog she's quoting from was written.  They are not true now, since we've adjusted things in the last 8 months.  Also, I'm using a gain of -1.5 for MICH, and +1.5 for PRCL.  MICH has no FMs triggered, PRCL has FM 2,3,6 triggered.  Since we won't be using this configuration for full locking, but just for some tests, I'm currently using AS55 Q for MICH, and REFL 55I for PRCL, and using the ITMs to actuate on MICH for today.

  9416   Wed Nov 20 01:10:38 2013 JenneUpdateLSCPRMI carrier locking

I have increased the gain of the MICH loop to -100, and set FMs 2,3,7 to be triggered.  I have also increased the PRCL gain to 2.  The PRCL ASC pitch and yaw gains used to be -0.004, but I have increased them both to -0.01.

Now, I'm seeing power fluctuations in POPDC of ~200 pk-pk, at an average value of 2650.  That's a RIN of 7.5% .  If I turn off all OSEM damping for the PRM (after the cavities are already locked), I get POP DC fluctuations of 100 pk-pk at the same average value, so a RIN of 4%. 

Back on October 30th (elog 9338), we had an average POPDC of 400, with fluctuations of 200 pk-pk, so a RIN of 50%. 

So, I am pleased that, with the carrier locking, I have lower power fluctuations.  And, since there is more overall power in the PRC right now than we had 3 weeks ago, I'm hopeful that a PRMI+arms test will have lower power fluctuation.

Also, a note, when my MICH gain was still low, I had lots of power fluctuation at the AS port, which was coherent with my POPDC power fluctuations (which makes sense).  At that time, my overall RIN was higher than it is now (although I neglected to write down the numbers), but more significantly, I saw occasional 'kicks', where the ASDC and POPDC powers would ring for 1 or 2 seconds, with power fluctuations of order 40%.  I have not seen any of those kicks since increasing the MICH gain.

  9417   Wed Nov 20 16:05:52 2013 JenneUpdateLSCPRMI carrier locking, OpLev Check

[Jenne, EricQ]

We locked the PRMI on carrier again today, after lunch.  Following a suggestion from the 40m meeting, we wanted to compare the PRMI carrier fluctuations with the new vs. old OpLev servo for the PRM. 

To do change between the servo shapes, I put in an elliptic lowpass at 35Hz, since I overwrote that with the 55Hz lowpass the other day.  The only other change between shapes is turning on and off my boost / emphasis filter. 

So, the scenarios were:

(1) New OpLev servo

(2) Old OpLev servo (no boost, but 3.2Hz res gain and bounce roll notches on), with 55Hz lowpass

(3) Old OpLev servo with 35Hz lowpass

For scenario (1), like last night, there were small power fluctuations.  For scenario (2), most of the time there were small power fluctuations, but occasionally there would be a kick somewhere, and the power would dip down by ~50%, and the fluctuations would continue like a ringdown for a few seconds, and then we'd be back to small fluctuations until the next kick.  For scenario (3), even with trying different LSC servo gains, we could not get the PRMI to lock on carrier for more than a few tenths of a second.  During that time, the power fluctuations were very large. 

So, the old oplev servo was kind of okay, but the lowpass at 35 Hz was bad, bad, bad.  It seems that the new OpLev servo is doing good things for us.

  9418   Wed Nov 20 17:05:15 2013 JenneUpdateLSCXend QPD and Whitening board replaced

[EricQ, Jenne]

We have put the Xend QPD back in place, and centered it.  The whitening board was replaced by me a few days ago.

We also went down to the Yend and centered the Yend QPD.

I used the offset.py script that Masayuki wrote to zero the offsets of the individual quadrants when the PSL shutter was closed, and then I averaged the output of the SUM filter banks, and made the gains 1/AvgSum, so that both the Thorlabs PD and the QPD are normalized to 1 at single-arm resonance, for each arm.

I don't know what the gain is of the QPD head off the top of my head, relative to the Thorlabs PD, but eventually we want them to be the same, so that 1=1 and 700=700 on each PD.

  9430   Wed Nov 27 18:31:26 2013 KojiSummaryLSCAdittion of the ALS error signals to the LSC input matrix

The Phase tracker outputs (= ALS X/Y error signals) are now conveyed to the LSC model.

Their entry points at the LSC model are C1:LSC-ALSX_IN1 and C1:LSC-ALSY_IN1.
They are connected to the signal matrix (28th and 29th signals) via signal conditioning filters (C1:LSC-ALSX and C1:LSC-ALSY).

The main LSC screen has not been updated. The conventional ALS servos are still remains as they were.

This renovation required the recompilation of c1als, c1rfm, and c1lsc. Two PCIe-RFM bridge paths were added resulting in
increase of the c1rfm timing budget from 38 to 44.

  9439   Wed Dec 4 14:16:42 2013 JenneUpdateLSCPRFPMI flashes on transmission QPDs

2 weeks ago I took some data, and remembered today at the 40m meeting that I hadn't posted it.  Bad grad student.

All I'm trying to show here is that we see flashes in the arms that are larger than the ~50 units that we see saturate the Thorlabs transmission PDs. For arm power values below ~50, the QPD sum and Thorlabs PDs give approximately the same values.  So, 1 unit on the Thorlabs PDs is equivalent to 1 unit on the QPD sum, and 50 units on the Thorlabs diode is equivalent to 50 units on the QPD sum.

The situation was arms held on resonance with ALS, and the PRMI was flashing.

ArmsResonatingUsingALS_PRMIflashing_TRX_TRY.pdf

Arm powers of ~140 imply a power recycling gain of ~7.

  9440   Wed Dec 4 15:43:13 2013 JenneSummaryLSCPut LSC DAQ channels back

Last week, Koji cleaned up the LSC model to make it much more readable, while he was working on piping the ALS signals to the LSC model.  However, somehow the DAQ Channels block got deleted before the model was committed to the svn.  Since there were 2 months between svn checkins for c1lsc.mdl, it's possible that someone had the model open just to look at, and the block got deleted, and that's the version that Koji started with. 

Anyhow, thankfully we have the svn, so Koji and I found that the DAQ Channels block was (as expected) in the previously checked-in version of the LSC model.  I put a copy of the old model onto my desktop, opened it up, copied the DAQ Channels block, and then pasted it into the new cleaned-up version of the model.  (Jamie - is there a way to conveniently download a previous version through the web interface?)

I have checked it in, compiled and restarted the lsc model.  The _DQ channels are back now.

  9449   Fri Dec 6 21:38:27 2013 KojiUpdateLSCCDS related activities for LSC

I worked on the CDS related stuffs for LSC yesterday and today.


1. Slow machines:

I checked the database files for c1iscaux and c1iscaux2 (slow machines). They are mainly
used for the control of LSC whitening filters. The channel names were totally random as we
reconfigured the RF PDs while the channel names had been unchanged.

- Now the database was modified so that the PD name and the channels are related.
- saverestore.req and autoBurt.req were also changed accordingly.

- PD interface channels are completely random. Don't use them.
- I found the whitening of DCPDs are not effective.

- We need to clean up /cvs/cds/caltech/target directory. The autoBurt requests in the old targets
are making unnecessary burt files.

2. LSC screens

- The channel names on the LSC OVERVIEW screen was modified. (Attachment 1)
- A new LSC Whitening screen was made. (Attachment 2)

3. LSC screen generator

To touch the main LSC screen is very tough. The screen was split in to several sub screens
and combined with a command.

/opt/rtcds/caltech/c1/medm/c1lsc/master/generateLSCscreen/generateLSCscreen.py

This command combines the multiple adl files into a single file with x&y offsets.
This way, you can work with the each section of the screen.
Also, moving the blocks are just easy.

4. LSC Code Bug?

During the screen making, I found that a couple of the whitening switches are not
working properly.
e.g. When AS165 (either I or Q) FM1 is activated throught the whitening trigger,
the MSB bit (bit15) of the binary I/O (C1:LSC-BIO_0_0) does not .

SImilarly ASDC FM1 does not toggle bit15 of C1:LSC-BIO_0_1.

The other channels seems OK.

At first, I thought this is a bug of "Bit2Word" block. But an individual test of the block showed that
the block is not guilty. So why is only Bit15 malfunctioning???

 

Attachment 1: LSC1.png
LSC1.png
Attachment 2: LSC2.png
LSC2.png
  9456   Thu Dec 12 00:47:45 2013 DenUpdateLSClocking activity

Jenne, Den

Today we worked on PRM angular servos and Y-arm ALS stabilization.

In the current PRMI angular control configuration two servos simultaneously drive PRM - oplev and POP ASC. We considered 2 ways to redesign this topology:

  • once lock is acquired, turn on POP ASC servo that corrects oplev error signal
  • turn off PRM oplev and turn on POP ASC  servo

The first option requires model rewiring so we started from the second one. We had to redesign POP ASC pitch and yaw servos for this because PRM TF has changed. Attached is servo OLTF.

This method worked out well and once PRMI is locked we turned off oplev servo with ramp of 0.5 sec and enable ASC POP servo with ramp of 1 sec.

Once PRMI was locked and ASC running we have turned off PRM angular local damping that presumably prevents us from bringing arms into resonance due to IR coupling to shadow sensors.

PRMI was stable using only ASC POP servo and we moved on to ALS. We found Y-arm beatnote and enabled control to ETMY.

Cavity was stabilized but not robust - we were loosing IR in a minute because green relocked to 01 mode with transmission equal to more than half of 00 mode. This is probably due to angle to length coupling of ETMY.

We were also loosing IMC during cavity stabilization. We made MCL servo and will tune it tomorrow looking at the arm spectrum as an OOL sensor.

Attachment 1: POP_ASC.pdf
POP_ASC.pdf
  9462   Fri Dec 13 02:19:57 2013 JenneUpdateLSClocking activity

[Jenne, Den]

Tonight we worked on tweaking up the PRCL new ASC, and then PRMI+1 arm locking.  We were unable to get the Xarm to stay locked on a TEM00 mode for very long, and after an hour or two of using the PZTs to try to align the beam to the cavity, we gave up and just used Yarm green.

NB: We haven't done anything to MCL, although it is not in use.  Den is still going to get around to elogging what servo shaping he changed on that last night.

I wrote a script that will handle the transitions between the new PRCL ASC and the PRM oplev and local damping.  The script is accessible from the PRC ASC screen, and will detect when the PRMI is locked or not.  When it is locked, it will turn down the PRM oplev gains and turn on the ASC, and then it will turn off the local shadow sensor damping for PRM pitch and yaw.  When the PRMI unlocks, the script will turn off the ASC and restore oplev and local shadow sensor damping. 

We saw that the bounce mode of the PRM was getting rung up with our new ASC, so we included a band stop in the ASC, and also turned on the triggering for the PRCL LSC FM6, which has the resonant gain for the bounce mode (as well as roll, and the stack mode).  This made the PRMI spot very stable. 

We then moved on to green arm locking.  The Yarm is behaving perfectly nicely (as nice as it has been lately - it's alignment and mode matching could also use some work), but Xarm was giving us a bit of trouble.  As always (since the PZTs were installed?), the mode matching isn't excellent for the green to the arm, so it can be hard to catch a TEM00 mode.  Also, even if we did catch a good mode, it would often not stay locked for more than a few tens of seconds.  We tried several alignment tweakings, and several different end laser temperatures (within the confines of seeing the beatnote under 100MHz), and didn't have a lot of success.  It looks like Eric had the slow servo engaged for the Xend laser, so the temperature offset was something like +300,000, which seemed totally crazy.  I turned that off, and found the beatnote somewhere around output of -10,300.  So, I haven't gone to the end to look at the temperature, but it's going to be different than when Eric was taking measurements this afternoon.  It seems like the main problem with the Xarm is poor mode matching - the maximized input pointing for TEM00, when you unlock and relock the cavity, is just as likely to give you a TEM_9_0 mode, as TEM00.

So, we gave up on the Xarm for the evening, and tried PRMI+1arm, with the new PRCL ASC.  This was successful!   The Yarm beatnote was around laser slow servo output of +4450.  Beatnote at 46.0MHz, -26dBm.  We found the IR resonance, moved off, locked the PRMI, transitioned to the new ASC, and brought the Yarm back to IR resonance.  What we see is that the power fluctuations in the PRC are much smaller than they were back around Halloween (elog 9338), however the arm power fluctuations still seem very, very large.  This is certainly partly due to the fact that we haven't done a thorough Yarm alignment since before messing with the greens, so we will have drifted somewhat.  Also, the ALS beatnote sensor isn't perfect, so won't be perfect at holding us near resonance. 

Den is thinking about whether we can use the arm transmission QPD signals to feed back to the ETM ASC servos, to try to reduce the RIN in the arms.  I feel like we should also see if this amount of power fluctuation can be explained by our ALS noise, because maybe we'll be fine once we transition to IR and turn off the ALS system.   Attached is a plot showing that the arm's RIN is coherent with the spot motion seen by the transmission QPD, so we need to check the alignment of the cavity, as well as consider using the trans QPD in an ASC feedback loop.

Here is a plot of the PRC sideband power, as well as the Yarm transmission.  The GPS time for this plot is approximately 1070963372.

PRMI_Yarm_NewPRCLasc.png

Attachment 2: try_dc.pdf
try_dc.pdf
  9463   Fri Dec 13 02:30:22 2013 KojiUpdateLSClocking activity

According to the measurement by Eric, the X-arm green PDH UGF is too low. We still have some room to increase the gain.

The out of loop stability of the ALS for each arm should be measured everyday.
Otherwise we can't tell whether the arm is prepared for advanced locking activities or not.

We expect to see the arm stablity of ~50pm_rms for the Y arm and ~150pm_rms for the X arm.

  9465   Fri Dec 13 13:28:07 2013 DenUpdateLSCarm calibration template

I have calibrated ETMX and ETMY actuators and added a template armSpectra.xml into /users/Templates directory.

Template shows control and error signals of both arms. Procedure is standard: calibrate control to meters and match error based on UGF measurement. XARM UGF: 200 Hz, YARM UGF 210 Hz.

Noise level at high frequencies (>100 Hz) for YARM is 3*10-15 and is factor of 3 better then for XARM. Servo gains are in the same ratio. I think there is less light on POX than on POY RF PD because I checked phase rotation and analog gain. I assume transimpedances are the same.

Attachment 1: armsCal.pdf
armsCal.pdf
  9471   Sat Dec 14 02:51:47 2013 DenUpdateLSClocking activity

I had a look on x,y arms stabilization using ALS. Input green beam was misaligned and I was loosing 00 every few minutes. I vent on the floor and realigned green beams.

YARM alignemt was smooth - transmission increased from 0.4 to 0.85 with PSL shutter off.

XARM was tough. Steering mirrors did not have any derivatives when transmission power was 0.5. I walked the beam with piezos but got only 0.55. It seems that the input beam is mismatched to the cavity. When the transmission was 1 last time? Does anyone have a model of the xend table to compute mode matching?

Input green alignent was improved and I could keep arms stabilized for periods of ~30min - 1 hour. Still not forever.

I noticed that ALS_XARM and ALS_YARM servos have limiters of 6000 and control signal had high frequency components that were not rolled off as shown on the plot "ETMY_DRIVE". I have added a low pass filter that reduced RMS by factor of 5 and took 7 degrees of phase at UGF=150 Hz. Now margin is 33 degrees.

Then I excited ETMY longitudinally at 100 Hz and measured first and second harmonics of the YARM RIN. I got total DC offset of 0.3 nm. This means significant length coupling to RIN. First of all, "scan arm" script does not tune the offset very precise. I guess it looks at DC power, checks when cavity passes through symmetrical points of the resonance and takes the average. It is also useful to look at POX/POY and confirm that average is 0. Plot "ALS_RIN" shows comparison of YARM power fluctuations when it is locked using IR and stabilized using ALS. By manually correcting the offset I could reduce length coupling into RIN, coherence was ~0.1.

Cavity RMS motion also couples length to RIN. Plot "ALS_IR" shows YARM error signal. I also looked at POY signal (LSC-YARM_IN1) as an OOL sensor. At low frequencies POY sees only IMC length fluctuations converted to frequency. I have engaged MCL path and ALS error and LSC error signals overlaped. Cavity RMS motion is measured to be 200 pm.

Attachment 1: ETMY_DRIVE.pdf
ETMY_DRIVE.pdf
Attachment 2: ALS_RIN.pdf
ALS_RIN.pdf
Attachment 3: ALS_IR.pdf
ALS_IR.pdf
  9472   Sat Dec 14 11:56:54 2013 ranaUpdateLSCcommon mode servo

Quote:

 

 It seems to me that current design of the common mode servo is already fine. Attached plots show common mode open and closed loop transfer function.

 These seem like pretty terrible loop shapes. Can you give us a plot with the breakdown of several of the TFs and some .m file?

We should be able to estimate the noise coming out of the MC using the single arm and then make a guess for the CM loop gain requirement. There's no reason to keep the old Boost shapes; those were used in the old MC configuration which had a RefCav. In addition to minimizing the EOM range, we should also minimize the AO signal as Koji has pointed out. In practice, I've seen that using ~300 Hz of offset makes no harm with 4 kHz MC pole.

  9474   Sat Dec 14 14:21:46 2013 DenUpdateLSCcommon mode servo

Quote:

 

 These seem like pretty terrible loop shapes. Can you give us a plot with the breakdown of several of the TFs and some .m file?

Attached is matlab code that I used

 % IMC OL
G = zpk(-2*pi*8964, 2*pi*[-10; -10; -10; -1000; -274000], db2mag(242.5)) * ...
    tf([1 0.8*1.55e+05 3.1806e+10], 1);

% CARM PATH
CARM = G/(1+G);

% Common mode boosts
BOOST = zpk(-2*pi*4000, -2*pi*40, 1);
BOOST1 = zpk(-2*pi*20000, -2*pi*1000, 1);
BOOST2 = zpk(-2*pi*20000, -2*pi*1000, 1);
BOOST3 = zpk(-2*pi*4500, -2*pi*300, 1);

% Coupled cavity pole
CCPole = zpk([], -2*pi*100, 2*pi*100);

% Servo gain
Gain = db2mag(43);

% CARM OL with boosts
H = CARM * CCPole * BOOST * Gain;
H1 = H * BOOST1;
H2 = H1 * BOOST2;
H3 = H2 * BOOST3;

% Plot
% bode(H, H1, H2, H3, 2*pi*logspace(3, 5, 10000));
% bode(1/(1+H), 1/(1+H1), 1/(1+H2), 1/(1+H3), 2*pi*logspace(3, 5, 10000));

  9475   Sun Dec 15 03:13:15 2013 DenUpdateLSCattempt to reduce carm offset

X,Y arms were stabilized using ALS and moved 5 nm from the resonance, PRMI was locked on sideband using REFL165 I&Q. POP angular servo was running; PRMI RIN was good (~2-3%)

During slow offset reduction I was sweeping MICH, PRCL and POP servos for instabilities due to possible optical gain variations, loops were fine.

I could reduce offset down to ~200 pm and then lost lock due to 60 Hz oscillations as shown on the attached plot "arm_offset"

Arms were stabilized with RMS comparable to the offset and power in arms was fluctuating from 3 to 45.

60 Hz line most probably comes from MICH. RMS is dominated by the power lines and is ~ 1 nm as seen on the plot "PRMI_CAL". I think this is too much but we need to do simulations.

Attachment 1: ARM_OFFSET.pdf
ARM_OFFSET.pdf
Attachment 2: PRMI_CAL.pdf
PRMI_CAL.pdf
  9477   Sun Dec 15 21:01:19 2013 KojiUpdateLSCCM servo module installed

Now the module is inserted at the 2nd crate from the top of 1Y2 (LSC analog rack). It is next to the DCPD whitening module.

I found the backplane cable for the Common Mode servo module.
I traced a cable form XY220 at the right most module on the crate where iscaux2 is living.
This cable was connected to the upper backplane connector.

Switching of the module is tested. All the switches and gain control are doing their job.

It was found that the offset and slow readback are not responding.
I checked the schematic of the CM servo module (D040180).
It seems that there is another cable for the offset and read back voltages.

  9478   Mon Dec 16 02:20:49 2013 DenUpdateLSCMICH rms is improved

When PRMI is locked on REFL 165 I&Q signals MICH rms is dominated by the 60 Hz line and harmonics. It comes from demodulation board.

To increase SNR ZFL-100 LN amplifier (+23.5dB) was installed in LSC analog rack. MICH 60 Hz and harmonics are improved as shown on the plot "mich_err"

I have also added a few resg at low frequencies. MICH rms is not 3*10-10. In Optickle I simulated power dependence in PRC and ARMs on MICH motion. Plot is attached.

 I think we need to stabilize MICH even more, down to ~3*10-11 . We can think about increasing RF amplifier gain, modulation index and power on BB PD.

CARM offset reduction was a little better today due to improved MICH RMS. Power in arms increases up to 15 and than starts to oscillate up to 70 and then PRMI looses lock.

Tomorrow we need to discuss where to put RF amplifier. Current design has several drawbacks:

  • DC power for the amplifier is wired from a custom (not rack based) +15V power supply that was already inside the lsc rack and used for other ZFL-100LN
  • BNC cables are used because I could not find any long SMA cables
  • we would like gain of ~40 dB instead of 23.5 dB
Attachment 1: MICH_ERR.pdf
MICH_ERR.pdf
Attachment 2: DC_power.pdf
DC_power.pdf
Attachment 3: ARM_OFFSET.pdf
ARM_OFFSET.pdf
  9479   Mon Dec 16 20:08:43 2013 KojiUpdateLSCCM servo module installed

I found another backplane cable for the CM servo module. It is plugged to the module now.

I can see that C1:LSC-CM_SLOW_MON is responding to C1:LSC-CM_REFL_OFFSET.
But C1:LSC-CM_SUM_MON and C1:LSC-CM_FAST_MON are not replated to the given offset.
I probably need to check the cross connects.

  9480   Tue Dec 17 02:10:29 2013 DenUpdateLSClocking activity

Koji, Den

Some results and conclusions from tonight:

PRC macroscopic length is detuned. We measured REFL phases in carrier and sideband configurations - they are different by ~45 degrees for both 11 and 55 MHz sidebands. Additional measurement with phase locked lasers is required.

We got stable lock of PRMI+2arms with CARM offset of ~200 pm. We think this is the point when we should transition to 1/sqrt(TR) signals. We plan to rewire LSC model and also test CM servo with 1 arm during the day.

POP ASC OL shape changes when we reduce CARM offset probably due to normalization by sum inside the PD. Servo gets almost useless when PRMI power fluctuates by a factor of few.

SMA cables were made and installed for the REFL165 RF amplifier in lsc rack.

  9481   Tue Dec 17 14:06:59 2013 ranaUpdateLSCNew Broadband PD for POP 22/110

 I looked at the BBPD design so that we could make a POP22/110. It looks like it will be easy (I hope).

 The first attachment shows the schematic with the RF notch modified to handle 55 MHz. As long as the capacitor in this notch can be kept to below 20 pF, it doesn't degrade the noise so much,

The second attachment shows the TF and input referred noise. We ought to be able to get 20 pA/rHz at the input to the first RF amplifier.

The LISO files are in the svn under liso/examples/aLIGO_BBPD/,

Later, if we have to notch more than just 55 MHz, we can add a notch between the 2 RF amplifiers as Koji has done for the REFL165.

Attachment 1: POP22110sch.pdf
POP22110sch.pdf
Attachment 2: POP22110.pdf
POP22110.pdf POP22110.pdf
  9482   Tue Dec 17 20:59:23 2013 JenneUpdateLSC1/sqrt(TR) signals added to frames

I noticed that we have not been saving the 1/sqrt(TRX) and 1/sqrt(TRY) data, so I modified the c1lsc model and added them to the DAQ channels block.  I restarted the c1lsc model, and the _DQ channels are now archived.

  9483   Tue Dec 17 21:28:36 2013 JenneUpdateLSCCM servo slow output digitized

Den just plugged an output from the common mode board into an LSC whitening board (the spare channel that used to be called "PD_XXX_I" in the LSC model).  I have modified the LSC model to reflect the new name of the new signal ("CM_SLOW"), and have added this channel to the LSC input matrix.  Koji is, I believe, adding this channel to the LSC screen in the auxiliary error signals section.  I am also adding the _OUT of the filter bank to the DAQ channels block.

  9484   Wed Dec 18 00:26:15 2013 JenneUpdateLSCXend QPD schematic investigation

I have looked at the photo of the Xend QPD from elog 9367, as well as the schematic for the board (D990272). 

Things that will need swapping out:

  • Thick film resistors in the signal path need to be changed to thin film.
  • MAX333 needs to be replaced with MAX333A.  The 333 has "ON Resistance" of 140-175 ohms, whereas the 333A has "ON Resistance" of 20-35 ohms.
  • AD797 needs to be replaced by OPA140.  The 797 is a low voltage noise op-amp, but for a diode we want low current noise.  AD797 has 2pA/rtHz at 1kHz, whereas the OP140 has 0.8fA/rtHz at 1kHz (see Zach's elog 8125 re: OPA140).

I have ordered from digikey via techmart 10 each of the MAX333A's and the OPA140's.  (4 per QPD times 2 QPDs plus 2 spares = 10).  Both of these new chips have the same footprint and pinout as the part that they are replacing, so it'll be a fairly easy task.

Next up, I need to make a LISO model for the circuit for one of the quadrants, to see what shape it'll turn out to be.  Part of this will include deciding what resistors and capacitors to put in the OPA140 gain stage. 

Right now, the AD797s say on the schematic that the gain options are different by a factor of 5, but the actual QPD has a different resistor than is on the schematic, and there is also a capacitor in parallel with each resistor, so I need to just pull those out, and pick some values that make sense to me. 

Rana and I have discussed ignoring the 2nd and 3rd gain switching options on each quadrant, as that is getting to be more fine control than we need. 

Other things on the board:

  • The 50 ohm resistors to ground for the "QPD_rtn" have all shorted.  Rana says this is good, so leave it as-is.
  • The positive input to the AD797's all have a 100 ohm resistor to ground, rather than just being connected to ground.  Why is this??

For now, I will probably just work on the QPD head, and not the whitening board.  For now, we can run with 1 stage of whitening, and if we need lower noise, we can revisit the whitening board (including replacing the thick film resistors with thin film).

When thinking about what gains I want on my gain stages, I want to have my full arm power (~700 TRX units) be ~20,000 counts from the ADC.  So, I want my single arm power (1 TRX unit) to be ~30 counts from the ADC.  This is not such a big number, so this may also require more thinking. 

  9485   Wed Dec 18 03:29:48 2013 DenUpdateLSCyarm locked on mc

As a CM slow path test I locked free swinging yarm by actuating on MC length with bandwidth of 200 Hz. Crossover with AO is not stable so far.

I used xarm as an ool frequency noise sensor. MC2 violin mode is at 645 Hz, I have added a notch filter to LSC-MC2 bank.

Attachment 1: MC_ARM.pdf
MC_ARM.pdf
  9486   Wed Dec 18 11:32:34 2013 ranaUpdateLSCXend QPD schematic investigation

 

 Since we use the TransMon QPD for triggering the high/low gain switching we need to run with the whitening OFF during lock acquisition and the turn it on after we have the arms locked with ALS. This should be put into the up/down scripts.

  9487   Wed Dec 18 11:37:12 2013 JenneUpdateLSCPOP22 and POP110 demod phases

Somehow the POP22 and POP110 demod phases weren't correct anymore.  I guess Den saw this after he changed the setup for the REFL165 PD at the LSC rack, but didn't elog it. 

I went out to the LSC rack, and found that the power supply that is supplying the amplifiers for both POP22/110 and REFL165 was set to ~16V each channel.  I put it back to 15V for each channel.  I don't know what Den intended for the 165 amplifier (more volts is more gain), but the POP22/110 amplifier usually runs with 15V. 

I also reset the POP22 and POP110 demod phases.  Since I'm not able to lock PRMI on sideband this morning (why?!?!), I locked on the carrier, and moved the phases around until POP22 and POP110 were both maximally negative.  The phases are/were:

  OLD [deg] NEW [deg]
POP22 107.2 -165.0
POP110 95.0 150.0

This is a ~60 degree change for both PDs. 

I am not sure if Den ever checked the demod phase of REFL165 after he put in the new SMA cable (there's no mention of it in the elog!), so I'm going to check that to see if it helps get PRMI locking back.  I know that Den had also been using REFL11 for PRMI locking, but the parameters he used for that aren't in the log either.

  9490   Wed Dec 18 17:28:50 2013 GabrieleSummaryLSCEstimate of the PRC length error

Measurement 

Looking back at what I did in april (see log #8411) I realized that it is possible to get an estimate of how much the PRC length is wrong looking at the splitting of the sideband resonant peak as visible in the POP_110_I signal. With the help of Jenne the PRMI was aligned and left swinging. The first plot shows a typical example of the peak splitting of 55MHz sidebands. This is much larger than what was observed in April.

When the sidebands resonate inside the PRC they get a differential dephasing given by 

dPhi = 4*pi*f_mod/c * dL

where dL is the cavity length error with respect to the one that makes the sidebands perfectly resonant when the arms are not there. This is not exactly the error we are interested in, since we should take into account the shift from anti-resonance of the SBs in the arm cavities.

Nevertheless, I can measure the splitting of the peak in units of the peaks full width at half maximum (FWHM). I did this fitting few peaks with the sum of two Airy peaks. Here is an example of the result

data_fit2.png

The average splitting is 1.8 times the FWHM. Knowing the PRC finesse, one can determine the length error:

dL = c / (4 * f_mod * Finesse) * (dPhi / FWHM)

Assuming a finesse of 60, I get a length error of 4 cm.

To get another estimate, we kicked the PRM in order to get some almost linear sweeps of the PRC length. Here is one of the best results:

data_kick.png

The distance between consecutive peaks is the free spectral range (FSR) of the PRC cavity. Again, I can measure the peak splitting in units of the FSR and determine the length error:

dL = c / (4 * f_mod) * (dPhi / FSR)

The result is again a length error of 4 cm.

Simulation

An error of 4 cm seems pretty big. Therefore I set up a quick simulation with MIST to check if this makes sense. Indeed, if I simulate a PRMI with the 40m parameters and move the PRC length from the optimal one, I get the following result for POP_110_I, which is consistent with the measurement.

pop110_vs_dL.png

 

 Therefore, we can quite confidently assume that the PRC is off by 4 cm with respect to the position that would make the 55 MHz sideband resonant without arms. Unfortunately, it is not possible with this technique to infere the direction of the error.

 

 

 

 

 

 

Attachment 3: pop110_vs_dL.png
pop110_vs_dL.png
ELOG V3.1.3-