40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 232 of 344  Not logged in ELOG logo
ID Date Author Typeup Category Subject
  10434   Thu Aug 28 01:41:03 2014 ericqUpdateLSCPhase Tracker UGF normalization

We want both the X and Y phase trackers to have the same UGF, so that the X and Y ALS signals are subject to the same phase characteristics and can be nicely decoupled into CARM/DARM. 

I've started implementing a simple normalization scheme that Koji suggested, namely, dividing the I output of the phase tracker by a low passed version of the Q output. (Since the I is servoed to zero, the radius of the error signal in the IQ plane is essentially equal to the Q value) I put some simulink logic into the IQLOCK library part that BEAT[XY]_FINE are instances of to switch the normalization on/off, and to protect from divide-by-zeros. I also exposed the switching and FM on the ALS screen.

UGFnorm.png

I then tried using it, to mediocre results. I put a 10mHz LP in the filter module, found a Y-Arm beat, set the phase tracker gain to give me a 2kHz UGF, and then set the gain of the UGH normalization FM to turn the current average Q to unity. 

I then moved the laser temperature around to get different beatnote locations/amplitudes, hoping that the phase tracker UGF would stay the same when the UGH normalization was on.

It did not.

It did, however, correct it in the right direction... more work will be done with this, to try and make it useful. There's also the unfortunate effect that locking/unlocking the green causes erratic phase tracker output, which messes with the input to the normalizing LP filter, so if one were to leave it switched on, wonky stuff would come out. I don't want to go overboard with triggering shenanigans before I even get it working in the first place, though.  

  10435   Thu Aug 28 08:31:16 2014 SteveUpdateGeneralone good day
Attachment 1: 1goodDay.png
1goodDay.png
Attachment 2: 1gooday.png
1gooday.png
  10436   Thu Aug 28 11:02:53 2014 SteveUpdateCalibration-RepairSR785 repair

SN 46,795 of 2003 is back.

Attachment 1: 08281401.PDF
08281401.PDF
  10437   Thu Aug 28 17:34:20 2014 ericqUpdateGreen LockinguPDH Box Checkup

I had noticed in the past, that the digital control signal monitor for the X end would saturate well before the ADC should saturate (C1:ALS-X_SLOW_SERVO_IN1, which is from the "output mon" BNC on the box). It turns out that there is some odd saturation happening inside the box itself.

In this scope trace, the servo input is being driven with a 0.02Vpp, 0.1Hz sine wave, gain knob at 1.0. This is bad. 

TEK00006.PNG

Evan and I poked around the board, and discover that for some reason currently unknown to us, the variable gain amplifier (AD8336) can't reach its negative rail, despite the +-12V arriving safely at its power supply pins. 

I also realized that the LF356 in the integrator stage in this box had been replaced with a LT1792 by Kiwamu in ELOG 4373. I've updated my schematic, and will upload both boxes' schematics to the DCC page Jenne created for them. (D1400293 and D1400294)

  10438   Fri Aug 29 17:28:07 2014 ranaUpdateGreen LockinguPDH Box Checkup

 

 I've been having trouble locking the X - green for the past few hours. Has there been some configuration change down there that anyone knows about?

I'm thinking that perhaps I need to replace the SHG crystal or perhaps remove the PZT alignment mirrors perhaps. Another possibility is that the NPRO down there is going bad. I'll start swapping the Y-end NPRO for the X-end one and see if that makes things better.

  10439   Fri Aug 29 23:53:35 2014 ericqUpdateGreen LockinguPDH Box Checkup

I had pulled out both X and Y servo boxes for inspection, put the Y box back, soldered in a missing op amp power capacitor on the X end box, and had not yet put back the X end box yet because of the saturation issue I was looking into. Otherwise nothing was changed at the ends; I didn't open the tables at all, or touch laser/SHG settings, just unplugged the servo boxes. 

  10440   Tue Sep 2 16:22:24 2014 JenneUpdateGeneralGame plan: 2 Sept

Slightly updated Game Plan.  Mostly, Q is continuing to check out the Xend PDH box saturation, and I am thinking on what our requirements are for ALS, and thus for the green PDH boxes.

40mToDoList.pdf

  10441   Tue Sep 2 20:02:06 2014 ericqUpdateGreen LockinguPDH Box Checkup

I narrowed down the saturation point in the X green PDH box to the preamp inside the AD8336, but there is still no clear answer as to why it's happening. 

As per Jenne's request, I put the X end PDH box back for tonight's work. It locks, but we have an artificially low actuation range. With SR785, I confirmed a PDH UGF around 5k. Higher than that, and I couldn't reliably measure the UGF due to SR560 saturations. The analyzer is not currently in the loop. 

Both arms lock to green, but I haven't looked at beatnotes today. 

  10443   Wed Sep 3 00:17:22 2014 ranaUpdateGreen LockinguPDH Box Checkup

What monitor point is being plotted here? Or is it a scope probe output?

If this saturation is in the uPDH-X but not in the uPDH-Y, then just replace the VGA chip. Because these things have fixed attenuation inside, they often can't go the rails even when the chip is new.

In any case, we need to make a fix to get this box on the air in a fixed state before tomorrow evening.

Quote:

I had noticed in the past, that the digital control signal monitor for the X end would saturate well before the ADC should saturate (C1:ALS-X_SLOW_SERVO_IN1, which is from the "output mon" BNC on the box). It turns out that there is some odd saturation happening inside the box itself.

In this scope trace, the servo input is being driven with a 0.02Vpp, 0.1Hz sine wave, gain knob at 1.0. This is bad. 

TEK00006.PNG

Evan and I poked around the board, and discover that for some reason currently unknown to us, the variable gain amplifier (AD8336) can't reach its negative rail, despite the +-12V arriving safely at its power supply pins. 

I also realized that the LF356 in the integrator stage in this box had been replaced with a LT1792 by Kiwamu in ELOG 4373. I've updated my schematic, and will upload both boxes' schematics to the DCC page Jenne created for them. (D1400293 and D1400294)

 

  10444   Wed Sep 3 04:17:21 2014 JenneUpdateLSCY green ALS (not PDH) needs investigation

Q put the X PDH box back, so that I could try locking, and remember which end is up after a week away.

I am unable to hold ALS comm/diff for any length of time. Only once today did I hold it through the FM3 boost turn-on.  So, I looked at the individual arms.

Xarm, even though it's the one that Q is seeing this saturation problem with, seems fine. 

Yarm however is having trouble holding lock for more than a few minutes at a time.  The green beam stays locked to the arm for ~infinity, so I'm not so worried about the PDH box right now.  If I look at the error and control points of the ALS digital servo, the Yarm is much more noisy above about 20 Hz.  Something that I might think of for this kind of mismatch at higher frequencies is poorly matched whitening / dewhitening, or none at all for the Yarm, however this doesn't look like that to me.  Based on the shape of the spectra, I don't think that we're running into ADC noise. For this plot, both arms are individually locked with ALS feeding back to the ETM, gain magnitude of 15 (Xarm gets a minus sign because of our temperature / beatnote moving direction convention), FMs 1,2,3,5,6 on.  Something that seems critical for getting the Yarm to have the FM3 boost without losing lock is having the SLOW temperature servos on for a little while so that the PZT output (as monitored on the temp servo screen) for the end lasers fluctuate around zero. Right now, both beatnotes are at about 62MHz, with an amplitude of about -31dBm.

Yarm_noisy_above_20Hz.pdf

I still need to do a somewhat more thorough investigation of what might be causing the Yarm locklosses.  Is the length-to-angle decoupling worse for ETMY than for ETMX?  Am I moving the arm length so far that the PZT can't follow within its actuation limits?  Does the Yend PDH box have a similar saturation to the Xend box, but somehow (a) worse, and (b) not as obvious so we didn't suspect it before? 

I need to put this plot into calibrated units, and also include the low frequency monitor that we have of the PDH error point (all of which are _DQ channels).

Things to do:

* Figure out Xend PDH box saturation issue.  Is Yend seeing same saturation in the variable gain amplifier?  We have 3 spares of these chips in the Plateau Tournant Bleu, if we need them. 

* Check Yarm ALS stability.  (NB:  The arms have been individually locked for the last 15 min or so while I've been writing, so maybe letting the slow servo settle is the key, and this is not something that needs work).

* Get CARM on DC Trans, DARM on AS55Q (after arm powers of about 1).  Can we see good REFL DC dip?  Should we try using just the transmission PD signal as the error signal for the CM board, if we aren't close enough to resonance to use REFL DC?

  10446   Wed Sep 3 18:42:43 2014 JenneUpdateLSCGreen PDH box boosts

From EricQ's simulations reported in elog 10390, we want to transition from ALS comm to DC transmission signals around 500 pm.  However, around 100 pm, the DC transmission signals have a sign flip, so we don't want to have the ALS swing that close to the CARM resonance.  So.  We want to be at about 500 pm, and not touch 100 pm.  So, we don't want our peak ALS motion to go beyond ~400 pm.  Which means that we need to have less than about 40 pm in-loop RMS, to avoid hitting 400 pm.  This is an ALS requirement, but since the analog PDH box is what forces the end laser to follow the arm cavity, and thus give us information about the arm length fluctuations, the PDH residual noise is part of our sensor noise for the full ALS.  So, we need to have the PDH in-loop RMS be less than 40 pm, integrated from a few kHz down to at least 30 mHz. Recall that above the ALS UGF (of about 200 Hz), the sensor noise will be suppressed by 1/f, so we should take that into account when we are looking at the PDH error signal, before we calculate the RMS motion.

Q also measured the in-loop error signal with the current Yend PDH box in elog 10430, and it looks like most of the RMS is coming from a few hundred Hz.  I designed a hack to the PDH board boost that has a zero at about 2kHz, and a gain of 30 at DC, so that we will win by squishing all that RMS.  Also, it shouldn't be too aggressive, so we should be able to leave it on all the time, and still acquire lock of the green laser to the arm, without having to do triggering.

The board schematic is at DCC D1400294.  The boost is also called the "integrator stage", although it will no longer be a simple integrator.

EDIT, JCD:  This cartoon is not correct for the non-boosted state, doesn't include effect of R16.

BoostCartoon.pdf

  10447   Wed Sep 3 20:38:40 2014 ericqUpdateGreen LockinguPDH Box Checkup

The traces were from the front panel output BNCs, but the VGA preamp exhibited this asymmetric saturation at its output.  

In any case, I tried to replace the Xend box's AD8336 with a new one, and in doing so, did some irreparable damage to the traces on the board  I was not able to get a new AD8336 into the board. There are some ATF ELOGs where Zach found the AD8336 noise to be bad at low frequencies (link), and its form factor is totally unsuitable for any design that may involve hand modification, since it doesn't even have legs, just tiny little pads. I suggest we never use it for anything in the future. 

Instead, I've hacked on a little daughter board with an OP27 as an inverting op-amp with the gain resistor on the front panel as its feedback resistor, which can swing from 0 to x20 gain (the old gain setting was around 15dB=~x6). I've checked out the TF and output noise, and they look ok. The board can output both rails as well. 

I don't really like this as a long term solution, but I didn't want to leave things in a totally broken state when I left for dinner. 

  10448   Thu Sep 4 00:56:44 2014 JenneUpdateLSCGreen PDH box boosts

Okay, went back to the drawing board with Rana and Koji on PDH box stuff.

Currently (at least for the Yend), in the boost OFF state, we have an overall gain of about 50.  This is crazy big.  Also, the zero in the "transfer function stage" is around 1kHz, however our green cavity pole is (calculated) to be around 20 kHz.  Since these are supposed to cancel but they're not, we have a wide weird flat region in our loop TF.

So.  I calculated the changes to the TF stage that I'll need so that I have an increase of about 20 in DC gain, kept the pole at the same ~20Hz, but moved the zero way out to 18kHz.  I also calculated the changes needed for the integrator stage to make it effective at much higher frequency than it was designed for.  Now the pole is at 75 Hz, and the zero will be at 1.6kHz, and the high frequency gain will stay pretty close to the same with and without the boost.

Planned new TF stage:

TFstage_newDesign_3Sept2014.png

Planned boost stage (with and without boost activated):

BoostNoBoost_newDesign_3Sept2014.png

New boost stage only, so you can see the phase:

BoostOnly_newDesign_3Sept2014.png

The schematic, modified to show my planned changes (which I will put in the DCC after I make the changes):

D0901351-v1_3Sept2014.pdf

  10449   Thu Sep 4 01:28:32 2014 ericqUpdateLSCRecycling cavity lengths

 Going off some discussion we had at lunch today, here is my current knowledge of the state of cavity lengths. 

Acknowledging that Koji changed the sideband modulation frequency recently, the ideal cavity lengths are (to the nearest mm):

  • Lprc = c / ( 4 * fmod) = 6.773 m
  • Lsrc = c / ( 5 * fmod) = 5.418 m

We when last hand measured distances, after moving PR2, we found:

  • Lprc  = 6.752 m = 2.1 cm short
  • Lsrc  = 5.474 m = 5.6 cm long. 

However, when I looked at the sideband splitting interferometrically, I found:

  • Lprc = 6.759m = 1.4 cm short

This is only 5mm from the hand measured value, so we can believe that the SRC length is between 5 and 6 cm too long. I'm building a MIST model to try and see what this may entail. 

  10450   Thu Sep 4 03:12:55 2014 ericqUpdateLSCGreen PDH box boosts

Jenne made her board modifications, and the measured TF agreed with the design. Alas, the green would not lock to the arm in this state. 

I think that the reason is that the new TF does not have nearly as much low frequency gain as the old one, for a given UGF. Thus, for example, the 1Hz noise due to the pendulum resonance, has 30dB less loop gain suppressing it. 

boostedTF.pdf

 

NEED MORE gain.jpg

 

  10451   Thu Sep 4 10:10:23 2014 KojiUpdateLSCRecycling cavity lengths

Com'on. This is just a 60ppm change of the mod frequency from the nominal. How can it change the recycling cav length by more than a cm?

https://wiki-40m.ligo.caltech.edu/IFO_Modeling/RC_lengths

This describes how the desirable recycling cavity lengths are affected by the phase of the sidebands at non-resonant reflection of the arms.

If we believe these numbers, L_PRC = 6.7538 [m] and L_SRC = 5.39915 [m].

Compare them with the measured numbers

  • Lprc = 6.752 m
  • Lsrc  = 5.474 m

You should definitely run MIST to see what is the optimal length of the RCs, and what is the effect of the given length deviations.

  10452   Thu Sep 4 16:45:10 2014 JenneUpdateLSCGreen PDH box boosts

As EricQ mentioned in last night's elog, the modifications were made to the Yend (SN 17) uPDH board.

R31 became 49.9 Ohms, R30 became 45.3kOhm, R24 became 1.02k, R16 became 1k, a new flying resistor is tombstoned up against R24 and connected by purple wire to C6 and it is 20k.  C28 is 183nF and C6 is 100nF.  These numbers were used in Q's simulation last night.

 

 

IMG_1712.JPGIMG_1714.JPG

  10453   Thu Sep 4 18:16:20 2014 ericqUpdateLSCRecycling cavity lengths

Koji correctly points out that I naïvely overlooked various factors. With a similar analysis to the wiki page, I get:

  • Ideal arm length of 37.795 m
  • Ideal PRC length of 6.753 m
  • Ideal SRC length of 5.399 m

This means that:

  • The PRC, measured at 6.759m, is 6mm long. 
  • The SRC, measured at 5.474m, is 7.5 cm long

Next step is to see how this may affect our ability to sense, and thereby control, the SRC when the arms are going. 

MIST simulations and plots are in the attached zip. 

Attachment 1: 2014-09-CavityLengths.zip
  10456   Fri Sep 5 03:36:00 2014 ranaUpdateComputer Scripts / Programsmartian wireless tweak

 I changed the Martian wireless router to use channel 10 instead of something random (as it was). Using the Android app 'Wifi Analyzer' we could see that the usual channels are dominated by FlumeLab and Caltech Beaver.

The range from 9-13 looked clean so we put it up there. Also, the signal strength drops from -45 to -70 dBm as we walk from the BS down to the ends. We need to tweak the router position and orientation to give us another 10 dB so that we can reliably run the laptops at the ends.

  10457   Fri Sep 5 04:07:44 2014 ericqUpdateGreen LockingX end uPDH Box Replaced

Just a quick note, plots and data will come tomorrow:

I grabbed an unused uPDH board from the ATF (thanks Zach!), and re-stuffed almost the entire thing to match Jenne's latest schematic for the y end box. I also threw some 22uF caps on the regulators, as Koji did with the previous box, to eliminate some oscillations up in the high 10s of kHz. I replaced the tragedy of a box that I created on Wednesday with this new box. The arm locks pretty stably with the boost on, 30 degrees of phase margin with 10kHz UGF, and locks pretty darn reliably. 

Now we should now have two nicely boosted PDH loops. I'll do a noise/loop breakdown again in the upcoming days. 

  10458   Fri Sep 5 05:32:57 2014 JenneUpdateLSCGreen PDH box boosts

[Rana, Jenne, EricQ]

* Too much gain overall on Yend box, needed attenuator on output to get lock.  Rethought gain allocation.  Resoldered board, installed, Ygreen locks nicely.  Error point and control point spectra, box TF and open loop TF data collected, to be plotted.

* Q replaced the Xend box, with a matching TF.

* Locked both arms individually, Yend has lots of low freq fluctuation, Xend has some.  Can't do out of loop measurement since we're going well beyond the range of the PDH signals (Yarm RIN is between 1/2 and 1.) Plot TRX and TRY spectra with ALS lock vs. IR lock to get an idea of what frequencies we have a problem with.

* Tried comm/diff locking anyway.  Works.  Used cm_up script to get CARM to sqrtInvTrans.  Went to powers of about 0.5 (hard to say really, because of fluctuations), put sine at 611.1 Hz, 200 cts onto ETMs (-1*x, +1*y), looked at TF between ALS diff and AS55Q.  Put that amount into the static power normalization spot for AS55.  In steps of 0.1, reduced ALSdiff input matrix elements and increased AS55->DARM element.  2 (3?) times was able to get to AS55Q for DARM.  Lost lock once unknown reason, while reducing CARM offset.  Lost lock once trying to turn on FM4 LSC boost for DARM.

TRX/TRY spectra:

TRX_TRY_ALSvsIR_4Sept2014.pdf

  10459   Fri Sep 5 15:28:38 2014 SteveUpdateSUSHeNe laser test preparation

The SRM qpd was moved to accommodate the HeNe laser qualification test for LIGO Oplev use.

The qpd was saturating at 65,000 counts of 3 mW

ND1 filter lowering the power by 10 got rid of saturation. I epoxied an adapter ring to the qpd.

Atm3 was taken before saturation was realized with Koji's help.

Atm4 ND1 on SRM qpd. Now it is working and everything is moving.

 

Attachment 1: beforeRSMqpdMoved.jpg
beforeRSMqpdMoved.jpg
Attachment 2: afterSRMqpdMoved.jpg
afterSRMqpdMoved.jpg
Attachment 3: 1103Ptest.png
1103Ptest.png
Attachment 4: ND1onQPD.png
ND1onQPD.png
  10460   Fri Sep 5 16:13:00 2014 ericqUpdateGreen Lockingnew X Green PDH measurements

 I measured the noise spectra and loop TF of the green PDH with the newly stuffed board. Unfortunately, I never took the noise below 100Hz of the previous box, so we can't see what has happened to the overall RMS, or more specifically, the RMS due to the pendulum resonance. All of these plots are in the boosted state, as that is how we intend to use the box. 

Here is the loop, which does not have quite as much margin as the y-arm, but 10dB of gain peaking is probably ok, since the RMS at 10s of kHz is not so important to ALS. (OL measured, CL inferred)  We see the 1/f shape from 1k to 50k or so, and 1/f^2 under 1k, as desired. 

xGbodes.pdf

Comparing in the in loop error signals, we see the effect from the increased gain from 100Hz to 10kHz. (Here is where I regret not looking at the low frequency spectrum two weeks ago)

pdhComparison.pdf

Finally, here is the noise breakdown. 

xGspectra.pdf

The error signal RMS is now dominated by the 1Hz peak. We have talked about using digital feedback for this, since we have the PDH error signal coming into an ADC, and can sum in a DAC signal into the servo output. This also lets us intelligently trigger a sub-10Hz boost once the PDH box locks itself. With a good boost, we maybe could bring the in-loop RMS of the error signal to under 1kHz. 


Something odd that Rana brought to my attention, however, is that my measurement and calibration indicates an RMS of ~5kHz, but the cavity pole should be something like 18kHz. If this is true, how can we be seeing stable power? This maybe means that my calibration is too many Hz per Volt.

I performed the calibration by creating a MIST model of the arm, and generating the PDH error signal on a demodulated PD, I then find the slope of Hz per arbitrary error signal unit. Then, looking at a scope trace, I match up the horn-to-horn voltage to the horn-to-horn arbitrary error signal units, which lets me finally find Hz per error signal volt. 

However, there is some qualitative difference in the shape between the simulated and observed error signals, namely, that the outer horns are larger than the inner horns in the real signal. 

sigSim.pdfscopeSweep.jpg

 

Does this matter? Is there something in my simulation that I can correct that would give a more accurate calibration? 

Data, plots, code, attached. 

Attachment 6: xG_Sep5.zip
  10461   Fri Sep 5 16:25:36 2014 SteveUpdateSUScenter ITMY oplev

Quote:

The SRM qpd was moved to accommodate the HeNe laser qualification test for LIGO Oplev use.

The qpd was saturating at 65,000 counts of 3 mW

ND1 filter lowering the power by 10 got rid of saturation. I epoxied an adapter ring to the qpd.

Atm3 was taken before saturation was realized with Koji's help.

Atm4 ND1 on SRM qpd. Now it is working and everything is moving.

 

 ITMY oplev should be centered. I worked too much around it.

  10462   Fri Sep 5 21:13:57 2014 JenneUpdateLSCGreen PDH out of loop

I locked the arms with IR, and measured the beatnote spectra to get the out of loop noise for the PDH boxes. 

Unfortunately, we don't have a reference saved (that I can find), so we're going to have to compare to an elog of Koji's from a month ago.  I have created an out of loop ALS reference .xml file in the Templates/ALS folder.

ALS_XY_outOfLoop_5Sept2014.pdf

As we can see from Koji's elog 10302, the Xarm seems to have stayed the same, but the Yarm seems to have increased by about an order of magnitude below 100 Hz.  :(

  10463   Sat Sep 6 01:48:54 2014 ranaUpdateGreen Lockingnew X Green PDH measurements

Quote:

Does this matter? Is there something in my simulation that I can correct that would give a more accurate calibration? 

Data, plots, code, attached. 

 What modulation depth are you using for the simulation? I have never seen a real measurement of that in our elog for the end-PDH systems.

I also disbelieve your RMS calculations. It looks like in the 1.5-0.5 Hz band we're picking up 50 kHz of frequency noise even though the 1 Hz peak is only 80 Hz/rHz, even though math says  "80 * sqrt(1) = 80".

Take a look at:

http://www.mathwords.com/r/root_mean_square.htm

and

http://www.ligo.caltech.edu/~rana/mat/utilities/rms.m

  10464   Sat Sep 6 14:49:12 2014 ericqUpdateGreen Lockingnew X Green PDH measurements

I used a modulation depth of 0.3, which, if I recall correctly, is what we aimed for on the Y-arm when we adjusted the LO signal there. However, this is probably not the case for the X arm. 

In any case, I found the bug in my RMS calculation. (I had forgotten to flip the x array in addition to the y array for the right-to-left integration, and had uneven bin spacing, so the integration bandwidths weren't correct...)

Here are the updated plots. The properly evaluated RMS is ~600Hz, which seems to mostly come in around 10k, so we may want to turn down the gain for less gain peaking in that region. 

xGComparison.pdf xGspectra.pdf

  10465   Sun Sep 7 17:06:38 2014 ranaUpdateGreen Lockingnew X Green PDH measurements

600 Hz seems ~OK. From the measured reflectivities for 532 nm, the green Finesse = 108. So the green cavity pole should be 18.3 kHz given an arm length of 37.8 m. 

600 Hz of green frequency noise means that we would get 38 pm RMS of arm mirror motion. We should assumed a peak/RMS factor of 10, so this would allow us to get to ~0.4 nm CARM offset.

However, its better than that. What we really care about for ALS is the amount of this green frequency noise which is put onto the arm. With an ALS feedback bandwidth of 100 Hz, my eyeball estimate say that the contribution from green PDH error will be ~100 Hz RMS, since we don't care too much about the 10 kHz stuff. So this seems good enough for now; let's figure out what's up with PDH-Y and get back to locking.

  10466   Mon Sep 8 07:50:40 2014 SteveUpdateSUSPRM damping restored
  10467   Mon Sep 8 08:24:49 2014 SteveUpdateComputer Scripts / Programspreparing vac system to reboot

Q and Steve will follow elog 10028 entry to prepare the vacuum system for safe reboot

  10468   Mon Sep 8 11:10:26 2014 ericqUpdateComputer Scripts / Programspreparing vac system to reboot

Quote:

Q and Steve will follow elog 10028 entry to prepare the vacuum system for safe reboot

Here's the sequence of the morning so far:

  • I aligned the IFO (IR arms with ASS, X green with PZTs, PRM with PRMI locked on REFL33)
  • I closed the PSL shutter, and went inside to align PRM and both ITM oplevs (all others were within 10urad of zero in both directions)
  • While aligning those oplevs, I noticed the smell of burnt electronics. We tracked it down to the +15V sorensen in the rack nearest the PSL table
    • I claim the precipitating event was PSL shutter activity. If I recall correctly, the seismic rainbow traces went bonkers around the same time as the shutter was closed. There is a Guralp interface in the rack powered by the failed sorensen, so this would explain the erratic seismometer signals correlated with the power supply failure. We will look into potential shorts caused by the shutter. (Steve looked up the PMC trans and Guralp DQ channels, and confirmed the temporal coincidence of the events.)
  • We shut off all of the sorensens so that electronics were not being driven asymmetrically. 
  • Steve and I secured the vacuum system for computer reboots, as referred to in Steve's elog. Some combination of Jenne, Rana and Manasa shut down the control room computers, and turned off the watchdogs. 
  • Manasa and I moved Chiara inside, next to Mafalda, along with its backup HDs. It has been labeled. 
  • Booted up control room machines, they came up happy. 
  • FB and front-ends didn't need reboot, for some lucky reason. Watchdogs came back happily, oplev spots didn't move noticeably. 

The IFO is still down, as the PMC won't lock without the rack power, and we haven't pinned down the shorting mechanism. We don't want the replacement sorensen to immediately blow when plugged in. 

  10469   Mon Sep 8 11:34:47 2014 ranaUpdateComputer Scripts / Programspreparing vac system to reboot

FYI: in that rack, the +15V pulls ~0.5 A more than -15V usually. I think this is due to some RF amplifiers which are powered by this (e.g. the AOM that Manasa set up). The Sorensen's can source ~30A in principle, so we should make sure to set the current limit appropriately so as to not overheat them when there is a short.

Was this power supply not fused for all of its connections? I remember that this was connected to at least one un-fused connection in the past year.

  10470   Mon Sep 8 12:11:36 2014 manasaUpdateComputer Scripts / Programspreparing vac system to reboot

Quote:

FYI: in that rack, the +15V pulls ~0.5 A more than -15V usually. I think this is due to some RF amplifiers which are powered by this (e.g. the AOM that Manasa set up). The Sorensen's can source ~30A in principle, so we should make sure to set the current limit appropriately so as to not overheat them when there is a short.

Was this power supply not fused for all of its connections? I remember that this was connected to at least one un-fused connection in the past year.

 +15V supply powers the following (from what I see):

1. PMC and MC boards on the rack.

2. RF amplifiers on the rack for the beat signals from the green beat PDs.

3. Beatbox itself.

The beatbox was the one that had an un-fused connection last year. I re-did it properly to go through a fuse quite sometime ago.

I dont see any other un-fused connections now from the +15V supply right now.
 

P.S. AOM driver takes a 0 to +28V power supply and not connected to the +15V

  10471   Mon Sep 8 14:14:13 2014 JenneUpdateGreen Lockingnew Y Green PDH measurements

These are plots and notes from last week's PDH adventures. 


For the PDH servo box re-design, we wanted to think a little bit about what we actually wanted out of the box.

* We want the zero of the main transfer function to be at the same frequency as the cavity pole for green, which is about 18kHz.

* We want the boost to suppress noise at a few hundred Hz.  We don't need super-duper low-frequency boost, nor do we want it.  We'd like to leave the boost on all the time.

* Wanted to get rid of 10dB attenuator on PD input, so needed to lower the overall gain.

* We acknowledge that the gain of the raw error signal times the PZT response is very high, so no matter what, we will have to have a low-gain servo, even perhaps have the servo shape be less than unity gain.

---> We reduced the gain of the first amplification stage from a gain of 20 to a gain of 3.

---> Made the boost stage have a DC gain of 1.  Pole at 75 Hz and Zero at 1.6kHz to give suppression at a few hundred Hz.  Boost is *not* a pure integrator, so that we can leave it on.  (If we required triggering anyway, we would have made it a pure integrator).

---> In transfer function stage, put zero at 17.7kHz to match cavity pole.  Pole of servo was going to be at 20 Hz, but we wanted a little more gain, so we lowered it to 2 Hz.

Here is the final measured servo box transfer function for the Yend box (with an arbitrary gain knob setting):

PDHboxTF.png


Once installed, I set the gain knob for the Yend at 4.0, which gave an overall UGF of about 10kHz.  Then I measured the loop:

LoopGain.png

I also measured the error point and the control point, and compared them to Q's measurements in elog 10430.

ErrSpecCompare.png

ControlSpectrumCompare.png


In order to see what we might expect for a contribution to ALS noise, I looked at the error point spectra and lowpassed it with a pole at 200Hz.  I do this because the PDH error is like sensor noise for the ALS, but the ALS UGF is around 200 Hz, so noise at frequencies higher than that will be suppressed like 1/f.  So, I lowpass the error signal, then look at the RMS, and see that we should be pretty happy with our result. I include also the Xend error spectrum, as measured and reported by Q in elog 10460.

XvsY_ALScontribution.png

Attachment 6: Yend_4Sept2014.zip
  10472   Mon Sep 8 15:50:47 2014 ericqUpdateComputer Scripts / Programs+15V PSL Sorensen replaced

We replaced the +15V sorensen at 1X1, and brought the power supplies back up symmetrically, and everything seems fine. I noted that a quarter turn counter-clockwise took the current limit down by one amp, so I set the knob to just letting 2.8A (the nominal current), and then added one half turn, shooting for ~4A current limit. 

In doing so, we had to cut power to the c1psl VME box. It didn't come back happily. We had to do the chiara /etc/hosts things, like we did for c1auxexx, to get it back.

  10474   Tue Sep 9 00:34:34 2014 JenneUpdateLSCFiguring out where to do DARM->AS55

This afternoon, after Q and Manasa finished recovering from the activities of the morning, I aligned the IFO, and went to the Yend to touch up the alignment of the green to the arm.  I don't know if it was the alignment (I didn't do the PSL table), or I happened to have a good combination of laser temperatures, or what, but the Yend ALS noise was super good.  After that, the low frequency noise contribution is different lock-to-lock, and I haven't discerned a pattern yet.

One thing that we want to try is to get DARM to AS55 so that we're entirely off of ALS (assuming we've already gotten CARM to sqrtInvTrans).  However, according to Q's simulations, we have to get past arm power of a few before we are within the AS55 linewidth.  I have a DTT running showing me the phase between AS55 and ALSdiff as I reduce the CARM offset, but I haven't been able to get close enough to see the sign flip when CARM is on sqrtInvTrans.  If I just sweep through with both CARM and DARM on ALS, I see the sign flip.  I've tried a few different things, but I have not successfully gotten a transition to AS55 while the arm powers were above 1.  Empirically,  I think I want them at at least 3 or 4.

Koji suggested locking the DRMI rather than PRMI, to widen the AS55 linewidth, but I haven't tried that tonight.  Maybe tomorrow night.

I have made a ruidimentary lockloss plotting script, that I have put in ..../scripts/LSC/LockLossData, but I'm not satisfied with it yet.  Somehow it's not catching the lockloss, even though it's supposed to run when the ALS watch/down scripts run.  I'll need to look into this when I'm not so sleepy.

Q, can you please work on figuring out the phase tracker gain tracker?  It will be nice to have that functional so we don't have to fret about the phase tracker gains. 

Manasa, can you please estimate what kind of mode matching we have on the PSL table between the arm greens and the PSL green?  We *do not* want to touch any optics at this point.  Just stick in a power meter to see how much power we're getting from each beam, and then think about the peak height we see, and what that might tell us about our mode overlap.  If we determine it is total crap, we can think about measuring the beams that go either toward the camera, or the DC PDs, since neither of those paths require careful alignment, and they are already picked off from the main beatnote path.  But first, what is our current efficiency?  Yarm is first, then Xarm, since Yarm seems worse (peak height is larger for non-00 modes!)

  10475   Tue Sep 9 08:22:28 2014 SteveUpdateSUSHeNe laser test preparation

Quote:

The SRM qpd was moved to accommodate the HeNe laser qualification test for LIGO Oplev use.

The qpd was saturating at 65,000 counts of 3 mW

ND1 filter lowering the power by 10 got rid of saturation. I epoxied an adapter ring to the qpd.

Atm3 was taken before saturation was realized with Koji's help.

Atm4 ND1 on SRM qpd. Now it is working and everything is moving.

 

 SRM as set up in Atm4  26,000 count compared with ETMY oplev servo in operation 7,500 counts for 3 days

Next steps: measure beam size at qpd,

                  place qpd on translation stage for calibration,

                  change 1103P mount to single one

Attachment 1: HeNecompared.png
HeNecompared.png
  10476   Tue Sep 9 09:19:21 2014 SteveUpdatesafetyresponse to fried Sorensen

Quote:

Quote:

Q and Steve will follow elog 10028 entry to prepare the vacuum system for safe reboot

Here's the sequence of the morning so far:

  • I aligned the IFO (IR arms with ASS, X green with PZTs, PRM with PRMI locked on REFL33)
  • I closed the PSL shutter, and went inside to align PRM and both ITM oplevs (all others were within 10urad of zero in both directions)
  • While aligning those oplevs, I noticed the smell of burnt electronics. We tracked it down to the +15V sorensen in the rack nearest the PSL table
    • I claim the precipitating event was PSL shutter activity. If I recall correctly, the seismic rainbow traces went bonkers around the same time as the shutter was closed. There is a Guralp interface in the rack powered by the failed sorensen, so this would explain the erratic seismometer signals correlated with the power supply failure. We will look into potential shorts caused by the shutter. (Steve looked up the PMC trans and Guralp DQ channels, and confirmed the temporal coincidence of the events.)
  • We shut off all of the sorensens so that electronics were not being driven asymmetrically. 
  • Steve and I secured the vacuum system for computer reboots, as referred to in Steve's elog. Some combination of Jenne, Rana and Manasa shut down the control room computers, and turned off the watchdogs. 
  • Manasa and I moved Chiara inside, next to Mafalda, along with its backup HDs. It has been labeled. 
  • Booted up control room machines, they came up happy. 
  • FB and front-ends didn't need reboot, for some lucky reason. Watchdogs came back happily, oplev spots didn't move noticeably. 

The IFO is still down, as the PMC won't lock without the rack power, and we haven't pinned down the shorting mechanism. We don't want the replacement sorensen to immediately blow when plugged in. 

  Smoking Sorensen could have triggered the smoke alarm!

 Yesterday I called CIT Fire Protection Services very first to deactivate the sensors temporarily. The smoke alarm was turned back on right after the particle count dropped.

 Their phone number is posted at the entry doors 104M and 104W as shown below.

 

Attachment 1: friedSorenson.png
friedSorenson.png
Attachment 2: smokeAlarm1a.jpg
smokeAlarm1a.jpg
Attachment 3: smokeAlarm2a.jpg
smokeAlarm2a.jpg
  10477   Tue Sep 9 14:18:40 2014 SteveUpdateComputer Scripts / Programspreparing vac system to reboot

Quote:

Quote:

Q and Steve will follow elog 10028 entry to prepare the vacuum system for safe reboot

Here's the sequence of the morning so far:

  • I aligned the IFO (IR arms with ASS, X green with PZTs, PRM with PRMI locked on REFL33)
  • I closed the PSL shutter, and went inside to align PRM and both ITM oplevs (all others were within 10urad of zero in both directions)
  • While aligning those oplevs, I noticed the smell of burnt electronics. We tracked it down to the +15V sorensen in the rack nearest the PSL table
    • I claim the precipitating event was PSL shutter activity. If I recall correctly, the seismic rainbow traces went bonkers around the same time as the shutter was closed. There is a Guralp interface in the rack powered by the failed sorensen, so this would explain the erratic seismometer signals correlated with the power supply failure. We will look into potential shorts caused by the shutter. (Steve looked up the PMC trans and Guralp DQ channels, and confirmed the temporal coincidence of the events.)
  • We shut off all of the sorensens so that electronics were not being driven asymmetrically. 
  • Steve and I secured the vacuum system for computer reboots, as referred to in Steve's elog. Some combination of Jenne, Rana and Manasa shut down the control room computers, and turned off the watchdogs. 
  • Manasa and I moved Chiara inside, next to Mafalda, along with its backup HDs. It has been labeled. 
  • Booted up control room machines, they came up happy. 
  • FB and front-ends didn't need reboot, for some lucky reason. Watchdogs came back happily, oplev spots didn't move noticeably. 

The IFO is still down, as the PMC won't lock without the rack power, and we haven't pinned down the shorting mechanism. We don't want the replacement sorensen to immediately blow when plugged in. 

Vacuum safe reboot required one hour of no pumping of the vac envelope.

Attachment 1: v1closedfor1h.png
v1closedfor1h.png
  10478   Tue Sep 9 14:25:46 2014 jamieUpdateLSCFiguring out where to do DARM->AS55

Quote:

I have made a ruidimentary lockloss plotting script, that I have put in ..../scripts/LSC/LockLossData, but I'm not satisfied with it yet.  Somehow it's not catching the lockloss, even though it's supposed to run when the ALS watch/down scripts run.  I'll need to look into this when I'm not so sleepy.

We developed a fairly sophisticated lockloss script at the sites, which you could try using as well.  It's at:

USERAPPS/sys/common/scripts/lockloss

It requires a reasonably up-to-date install of cdsutils, and the tconvert utility.  It uses guardian at the sites to determine when locklosses happen, but you can use it without guardian by just feeding it a specific time to plot.  It also accepts a list of channels to plot, one per line.

  10479   Tue Sep 9 16:59:32 2014 SteveUpdateSUSHeNe laser test preparation

Quote:

 

 SRM as set up in Atm4  26,000 count compared with ETMY oplev servo in operation 7,500 counts for 3 days

Next steps: measure beam size at qpd,

                  place qpd on translation stage for calibration,

                  change 1103P mount to single one

 SRM qpd is installed on translation stage and the shims removed from laser V mounts.

The ETMY oplev servo is on.

SRM oplev servo:  100 microrad/count is an estimate, not calibrated one.

Attachment 1: 1103PqpdTranss.png
1103PqpdTranss.png
  10480   Tue Sep 9 23:05:01 2014 KojiUpdateCDSOTTAVIA lost network connection

Today the network connection of OTTAVIA was sporadic.

Then in the evening OTTAVIA lost completely it. I tried jiggle the cables to recover it, but in vain.

We wonder if the network card (on-board one) has an issue.

  10481   Wed Sep 10 02:26:20 2014 JenneUpdateLSCDARM -> AS55 optickle

 Q has pointed out that we expect a sign flip in the AS55 signal for DARM as we reduce the CARM offset in the PRFPMI case.  Koji also mentioned that the SRC will help broaden the DARM linewidth.  I wanted to check and think about these things with my Optickle simulation.  Q is working on confirming my results with Mist.

The simulation situation:  

* The demod phase for AS55 is set in the MICH-only case so that the MICH signal is maximized in the Q-phase.  I do not change the demod phase at all in these simulations.

* Cavity lengths (arms, recycling cavities) are the measured lengths.

* I look at AS55 I and Q as DARM sensors (i.e. I'm doing DARM sweeps) as a function of CARM offset, for both PRFPMI and DRFPMI cases.

Spoiler alert!  Conclusions:

* In the PRFPMI case, the DARM signal shows up with approximately equal strength in the I and Q phases, so we suffer only about a factor of 2 if we do not re-optimize the demod angle for AS55.

* In the DRFPMI case, the DARM signal is a factor of 1,000 smaller in the Q-phase than the I-phase, which means that the ideal demod phase angle has moved by about 90 degrees from the MICH-only case.  We must either use the I-phase signal or change the demod phase by 90 degrees in order to acquire lock.

* In the PRFPMI case, there is a sign flip for DARM on the AS55 PD around 100pm, so we don't want to use AS55 for DARM until we are well inside 50pm, and aren't going to fluctuate out of that range.

* In the DRFPMI case, there is no such sign flip, at least out to 1nm, so we can use AS55 for DARM as soon as we see a viable signal.  This is super awesome. The caveat is that the gain changes significantly as we reduce the CARM offset, so we either need a UGF servo (eventually) or careful watching (for now).

* The AS55 linear(-ish) range is much broader in the dual recycled case, which is yet another reason why getting DARM on AS55 will be easier for DRFPMI.

Why didn't we do it already?

* To put the SRM QPD back, we'd also have to move Steve/EricG's laser.  Since I had other things to do, I left the setup for tonight, but I think I will want it for tomorrow night.

* Monday night (and tonight) we can pretty reliably get DARM onto AS55Q for the PRFPMI case, and I don't know what the cause has been for my locklosses, so I thought I'd try to figure that out first.  

Plots!

First up, the current transition we've been trying to handle, PRFPMI DARM to AS55Q.   I also plot AS55I, and we see that the signals are roughly the same magnitude (the x axis isn't the same between these plots! sorry), so we aren't screwed if we don't change the demod phase angle.  We'll be better off once we can do a re-optimization, but this is assuming we are stuck (at first) with our MICH-only demod phase angle.

AS55Q_vs_DARM_PRFPMI_0pm300pm.pngAS55I_vs_DARM_PRFPMI_0pm300pm.png

Next up, the same plots, but for the DRFPMI case.  Note here that there is a factor of about 1000 in the y-axis scales, and also that there is no switch in the sign of the zero-crossing slope for the I-phase.

AS55Q_vs_DARM_DRFPMI_0pm300pm.pngAS55I_vs_DARM_DRFPMI_0pm300pm.png

And here is the same data (DRFPMI case), but zoomed out for the Q-phase, so you can see the craziness of this phase.  Again, this is much smaller than the signals in the I-phase, so I'm not too worried.

AS55Q_vs_DARM_DRFPMI_0pm1000pm.png

Game plan:

* Steve leaves the SRM oplev back in its nominal location (we can worry about aligning the mirror, and aligning the beam on the PD, but please put it back approximately where it came from).

* Try DRMI + 2 arm locking, which I don't think we have ever actually done before.  Hopefully there won't be any tricks, and we can get to an equivalent place and successfully get DARM to AS55.  

* .... Keep going?

  10483   Wed Sep 10 02:35:55 2014 ranaUpdateCDSOTTAVIA lost network connection

Quote:

Today the network connection of OTTAVIA was sporadic.

Then in the evening OTTAVIA lost completely it. I tried jiggle the cables to recover it, but in vain.

We wonder if the network card (on-board one) has an issue.

 I would also suspect IP conflicts; I had temporarily put the iMac on the Ottavia IP wire a few weeks ago. Hopefully its not back on there.

  10484   Wed Sep 10 02:52:05 2014 ericqUpdateCDSOTTAVIA lost network connection

I checked chiara's tables, all seemed fine. I switched ethernet cables from the black one labelled "allegra," which seemed maybe fragile, for the teal one that may have been chiara's old ethernet cable. It's back on the network now; hopefully it lasts. 

  10485   Wed Sep 10 02:53:32 2014 JenneUpdateLSCLocking activities - nothing new :(

[Jenne, EricQ]

No major progress today.  

I fixed a bug in my lockloss script that was asking it to start gathering data just after the lockloss, rather than some seconds beforehand.  Ooops.  Anyhow, with this handy-dandy plotting, I still don't know why we are losing lock when we have PRMI on REFL33, CARM on sqrtInvTrans, and DARM on AS55.  I don't see any oscillations, just the arm power drops off, and a moment later the POP power drops.  

For example, here is one of the best states we got to tonight.  Data for this is in ..../scripts/LSC/LocklossData/1094369700 .  You can re-create the plot by going to ..../scripts/LSC/LocklossData/  and doing ./PlotLockloss.py 1094369700 .  We had set the triggers for the trans PD/QPD such that we were using the QPD transmission signals the whole time (above trans of 0.2).  We saw that the noise at high frequency during low transmission powers for sqrtInvTrans as an error signal was higher using the QPDs than with the Thorlabs PDs, but that both cases are below the noise for ALS.  The arm powers were pretty steady above 3 for the last bit of this lock stretch.  I lost lock while trying to transition DARM over to AS55Q.  CARM was on sqrtInvTrans(QPDs), PRMI on REFL33 I&Q as usual.

LocklossZoom.png

 


Other things from this evening:

* When I was starting, I saw that when I locked the PRMI, the PRM was oscillating in pitch. Oscillation only happened when PRM pitch oplev was on.  I'm not sure what could have changed to make the oplev loop unstable, but the gain was 7.0, and now I have left it at 5.0.

* I recentered the PRM and ITMY oplevs.

* Plugged in the Yend PDH error monitor and pzt output monitors, since I forgot them last week.  Hopefully this will allow the Yend SLOW servo to work, and keep us away from the limits of the PZT range.

  10486   Wed Sep 10 02:59:42 2014 ericqUpdateLSCLocking activities - nothing new :(

Some small things I did tonight which did little to nothing to help:

  • I reset the offsets in the SQRTINV FMs to try and match the DC level of the ALS CARM error signal as best as possible, to avoid moving away from the set-point too much, as I was worried we were wandering into regions of too low optical gain. 
  • I turned off the WFS, and hand tweaked the MC alignment. The WFS loops / matrices definitely have some room for improvement, and I was worried that excess angular motion of the MC was coupling into CARM. MC refl is much calmer in the last ~1.5 hrs since I turned off the WFS. 

My main concern with tonights situation was the huge low frequency fluctuations of TRY while CARM/DARM locked on ALS. We saw this being very smooth very recently, but when one arm is fluctuating by multiple line widths, it isn't surprising that locks aren't stable. I want to know why the out of loop stability is so unpredictable. 

  10487   Wed Sep 10 10:49:39 2014 ManasaUpdateLSCY arm green + PSL green mode overlap

Quote:

Manasa, can you please estimate what kind of mode matching we have on the PSL table between the arm greens and the PSL green?  We *do not* want to touch any optics at this point.  Just stick in a power meter to see how much power we're getting from each beam, and then think about the peak height we see, and what that might tell us about our mode overlap.  If we determine it is total crap, we can think about measuring the beams that go either toward the camera, or the DC PDs, since neither of those paths require careful alignment, and they are already picked off from the main beatnote path.  But first, what is our current efficiency?  Yarm is first, then Xarm, since Yarm seems worse (peak height is larger for non-00 modes!)

Estimate loss along the Y arm beat path:

1. Measured the beam powers (before the beam combiner): 
Y Arm green = 35 uW
Y PSL green = 90 uW

==> Pbeat ~ 2 * sqrt (35 uW * 90 uW) ~ 112 uW

2. Expected power of RF signal
Assuming the PD to have transimpedance ~ 2kV/A and responsivity ~ 0.3A/W, 
the expected power of the RF signal = (Pbeat * Transimpledance* Responsivity)^2 / (2 * 50ohm) ~ 45uW = -13.5 dBm

3. Measured power of Y arm beat signal

Turned OFF the beat PDs and rerouted the RF cables such that the spectrum analyzer was reading the RF signal from the Y beat PD itself (without any amplifiers or the beat box itself in the path).  
Turned ON the beat PDs and the Y arm beat signal power on the spectrum analyzer measured -58dBm
Even if we consider for losses along the length of the cables, we are still at a very bad state. 

4. Bad mode matching??
I don't think mode matching is our main problem here.
Toggling the shutter several times, even with the non-00 modes, the maximum beat power we can see is -50dBm which is still very far from the actual expected value.

  10488   Wed Sep 10 14:58:58 2014 JenneUpdateSUSOpLev test: New channels

Steve and EricG are moving their oplev test for aLIGO over to the SP table, so that we can have the SRM optical lever back.  

I have pulled out an Ontrak PSM2-10 position sensor and accompanying driver for the sensor.  This, like the POP QPD, has BNC outputs that we can take straight to the ADC.

In the c1pem model I have created 3 new filter modules:  C1:PEM-OLTEST_X, C1:PEM-OLTEST_Y, and C1:PEM-OLTEST_SUM.  I built, installed and restarted the model, and also restarted the daqd process on the frame builder.  On the AA breakout board on the 1X7 rack, these correspond to:

BNC # 29 = OLTEST_X

BNC # 30 = OLTEST_Y

BNC # 31 = OLTEST_SUM

By putting 1Vpp, 0.1Hz into each of these channels one at a time, I see on StripTool that they correspond as I expect.

Everything should be plug-and-play at this point, as soon as Steve is ready with the hardware.

  10489   Wed Sep 10 15:31:16 2014 SteveUpdateSUSHeNe laser test preparation

Quote:

Quote:

 

 SRM as set up in Atm4  26,000 count compared with ETMY oplev servo in operation 7,500 counts for 3 days

Next steps: measure beam size at qpd,

                  place qpd on translation stage for calibration,

                  change 1103P mount to single one

 SRM qpd is installed on translation stage and the shims removed from laser V mounts.

The ETMY oplev servo is on.

SRM oplev servo:  100 microrad/count is an estimate, not calibrated one.

 SRM qpd is back to its normal position. The mount base is still on delrin base. SRM and ITMY need centering.

Tomorrow I will set up the HeNe laser test at the SP table with Ontrack qpd

ETMY oplev servo on. SRM qpd with ND1 ------no component------- 1103P

Attachment 1: SRMqpdisBack0nSRMsus.png
SRMqpdisBack0nSRMsus.png
Attachment 2: slowVSfast.png
slowVSfast.png
ELOG V3.1.3-