40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 123 of 341  Not logged in ELOG logo
ID Date Author Typeup Category Subject
  3858   Wed Nov 3 23:58:45 2010 ranaUpdateElectronicsCougars

I looked at this web page: http://www.teledyne-cougar.com/Index.asp for the RF company that Rich has recently started using.

There are ~15 amplifiers that they sell which have a NF < 2 dB and work in the 10-100 MHz band. We should call them to find out if they will package some amps for us or at least sell us a few with eval. boards so that we can make our own.

  3859   Thu Nov 4 03:13:46 2010 SureshUpdateLockingFibre coupling 1064nm light at the south-end table

[Kiwamu, Suresh]

We decided to use the 1064nm beam reflected from the Y1-1037-45-P mirror after the collimation lens following the doubling crystal for coupling into the optical fiber (ref 3843 and 3847 ).

We replaced a beam dump which was blocking this beam with a Y1-1037-45-P mirror and directed the beam into the fiber coupler with another Y1-1037-45-P.  The power in this beam was about 1W.  This has been stepped down to 10mW by introducing a reflective ND filter of OD=2.  The reflected power has been dumped into a blade-stack beam dump.

Steve has ordered the The Visual Fault Locator from Fluke.  It is expected to arrive within a day or two.

 

 

  3860   Thu Nov 4 15:15:43 2010 josephbUpdateCDSModified feCodeGen.pl, fmseq.pl, and suspension screens

Feature Requested:

Have the CPU_meter change change color at various alarm levels.  These alarm levels have been set at 2/3 maximum for Minor alarm (yellow) and 9/10 maximum for Major alarm (red).

Implementation:

Rather than hand code each EPICS .db file to add the alarm files each time we rebuild the front ends, I decided to modify it at the source (since it strikes me as a generally useful alarm level for all front end codes).

First, I modified the feCodeGen.pl script.

I changed

print EPICS "OUTVARIABLE FEC\_$dcuId\_CPU_METER epicsOutput.cpuMeter int ai 0 field(HOPR,\"$rate\") field(LOPR,\"0\")\n";

to

print EPICS "OUTVARIABLE FEC\_$dcuId\_CPU_METER epicsOutput.cpuMeter int ai 0 field(HOPR,\"$rate\") field(LOPR,\"0\") field(HIGH,\"$two_thirds_rate\") field(HSV,\"MINOR\") field(HIHI,\"$     nine_tenths_rate\") field(HHSV,\"MAJOR\")\n";

I added the following two lines just before it as well:

$two_thirds_rate = int($rate * 2 / 3);

$nine_tenths_rate = int($rate * 9 / 10);

However, only the first four fields were actually added to the database file.  Apparently fmseq.pl, which populated the database, was hard coded to only handle up to 4 fields.

I modified the fmseq.pl script in /opt/rtcds/caltech/c1/core/advLigoRTS/src/epics/util/ so as to be able to handle up to 6 field values when writing EPICS .db files.

This change was accomplished by simply changing the following line

($junk, $v_name, $v_var, $v_type, $ve_type, $v_init, $v_efield1, $v_efield2, $v_efield3, $v_efield4 ) = split(/\s+/, $_);

to 

($junk, $v_name, $v_var, $v_type, $ve_type, $v_init, $v_efield1, $v_efield2, $v_efield3, $v_efield4, $v_efield5, $v_efield6 ) = split(/\s+/, $_);

everywhere it occurred.  There were something like 10 instances of it. Also, I added the two lines

        $vardb .= "    $v_efield5\n";
        $vardb .= "    $v_efield6\n";

after each set of

         $vardb .= "    $v_efield1\n";
         $vardb .= "    $v_efield2\n";
         $vardb .= "    $v_efield3\n";
         $vardb .= "    $v_efield4\n";

Lastly, I modified the CPU_METER bar graph on the C1SUS_DEFAULTNAME.adl screen (located in /opt/rtcds/caltech/c1/medm/master/) to use alarm levels, and then ran generate_master_screens.py.

 

  3861   Thu Nov 4 15:27:33 2010 josephb, yutaUpdateCDSc1ioo test points not working

Problem:

We can't access any of the c1ioo computer testpoints.  Dataviewer and DTT both fail to read any data from them.

According to diag -l (when run on Rosalba in /opt/apps), the testpoints are not being set.  Also at some point during the day when debugging, we also somehow messed up all the front end connections to the framebuilder.

Errors reported by dataviewer:

Server error 13: no data found
datasrv: DataWriteRealtime failed: daq_send: Illegal seek
Server error 12: no such net-writer
Server error 13: no data found
datasrv: DataWriteRealtime failed: daq_send: Illegal seek
Server error 12: no such net-writer
read(); errno=0
Server error 6532: invalid channel name
Server error 16080: unknown error
datasrv: DataWriteRealtime failed: daq_send: Illegal seek

Error reported by daqd.log:

[Thu Nov  4 13:29:35 2010] About to request `C1:IOO-MC1_PIT_IN1' 10022
on node 34
[Thu Nov  4 13:29:35 2010] Requesting 1 testpoints; tp[0]=10022; tp[1]=32531

[Thu Nov  4 13:29:35 2010] About to request `C1:SUS-MC2_SUSPOS_IN1'
10094 on node 36
[Thu Nov  4 13:29:35 2010] Requesting 1 testpoints; tp[0]=10094; tp[1]=32531

[Thu Nov  4 13:29:38 2010] ETIMEDOUT: test point `C1:IOO-MC1_PIT_IN1'
(tp_num=10022) was not set by the test point manager; request failed
[Thu Nov  4 13:29:38 2010] About to clear `C1:IOO-MC1_PIT_IN1' 10022 on node 34

Attempted Fixes:

Remove all daq related files: /opt/rtcds/caltech/c1/target/gds/param/tpchn_c1ioo.par and /opt/rtcds/caltech/c1/chans/daq/C1IOO.ini.  Rebuilt the front end code.

Double checked ethernet connection between c1ioo and the daq router and fb. 

Confirmed open mx was running on c1ioo. Confirmed awgtpman was running (although at one point I did find duplicate awgtpman running for c1x03, the IOP associated with c1ioo).

Rebooted the c1ioo machine. Confirmed all necessary codes came back.

Restarted the daqd process several times on the fb machine.

Current Status:

Framebuilder is running, and c1sus testpoints are available.  c1ioo test points are not.  Waiting to hear back from Alex on possible ideas.

  3862   Thu Nov 4 17:24:49 2010 steveUpdateGeneralconflat flanges for MIT

8 pieces of 10" CF blanks were shipped to MIT

  3863   Thu Nov 4 17:53:29 2010 yutaUpdateCDSprimitive python script for A2L measurement

Summary:
  I wrote a python script for A2L measurement.
 Currently it is really primitive, but I tested the basic functionality of the script.

 We already have A2L script(at /cvs/cds/rtcds/caltech/c1/scripts/A2L) that uses ezlockin, but python is more stable and easy to read.

A2L measurement method:
  1. Dither a optic using software oscillator in LOCKIN and demodulate the length signal by that frequency.
  2. Change coil output gains to change the pivot of the dithering and do step 1.
  3. Coil output gain set that gives the smallest demodulated magnitude tells you where the current beam spot is.

  Say you are dithering the optic in PIT and changing the coil gains keeping UL=UR and LL=LL.
  If the coil gain set UL=UR=1.01, LL=LR=-0.99 gives you demodulated magnitude 0, that means the current beam spot is 1% upper than the center, compared to 1/2 of UL-LL length.
  You do the same thing for YAW to find horizontal position of the beam.

Description of the script:
  Currently, the script lives at /cvs/cds/caltech/users/yuta/scripts/A2L.py
  If you run;
     ./A2L.py MC1 PIT
  it gives you vertical position of the beam at MC1.

  It changes the TO_COIL matrix gain by "DELTAGAINS", turns on the oscillator, and get X_SIN, X_COS from C1IOO_LOCKIN.
  Plots DELTAGAINS vs X_SIN/X_COS and fit them by y=a+bx+cx^2.(Ideally, c=0)
  Rotates (X_SIN, X_COS) vectors to get I-phase and Q-phase.
    (I,Q)=R*(X_SIN,X_COS)
  Rotation angle is given by;
    rot=arctan(b(X_COS)/b(X_SIN))
  which gives Q 0 slope(Ideally, Q=0).
  x-intercept of DELTAGAINS vs I plot gives the beam position.

Checking the script:
  1. I used the same setup when I checked LOCKIN(see elog #3857). C1:SUS-MC2_ULCOIL output goes directly to C1:IOO-LOCKIN_SIG input.

  2. Set oscillator frequency to 18.13Hz, put 18.13Hz band-pass filter to C1:IOO-LOCKIN_SIG filter module, and put 1Hz low-pass filter to C1:IOO-LOCKIN_X_SIN/X_COS filter modules.
        Drive frequency 18.13Hz is same as the previous script(/cvs/cds/rtcds/caltech/c1/scripts/A2L/A2L_MC2).

  3. Ran the script. Checked that Q~0 and rot=-35deg.

  4. Put phase shifting filter to C1:IOO-LOCKIN_SIG filter module and checked Q~0 and rotation angle.
     fitler rot(deg)
     w/o    -35
     +90deg  45
     -90deg  56
     -45deg -80

  5. Put some noise in C1:SUS-MC2_ULCOIL by adding SUSPOS feedback signal and ran the script.(Attachment #1)
      During the measurement, the damping servo was off, so SUSPOS feedback signal can be treated as noise.

Conclusion:
  The result from the test measurement seems reasonable.
  I think I can apply it to the real measurement, if MCL signal is not so noisy.[status: yellow]

Plan:
  - add calculating coherence procedure, averaging procedure to the script
  - add setting checking procedure to the script
  - apply it to real A2L measurement

Bay the way:
  Computers in the control room is being so slow (rossa, allegra, op440m, rosalba). I don't know why.

  3864   Thu Nov 4 17:57:27 2010 steveUpdateGeneralBeamScanner is working again

Koji, Suresh and Steve,

The beam scanner is back from repair.  Koji and Suresh helped to move the I/O address jumpers on the interface card from default position  300 to 320

It is working again.

  3865   Thu Nov 4 19:00:57 2010 SureshUpdateLockingFibre coupling 1064nm light at the south-end table

The Fluke Visual Fault locator (Visifault) arrived and I used it to couple 1064nm light into the single mode fibre at the south-end-table.

Procedure used:

When the output end of the fiber is plugged into the Visifault the light emerges from at the south end (input side for 1064nm).  This light is collimated with the fiber coupler at that end and serves as a reference for the optical axis along which the 1064 light must be directed.  Once the two beams (red and 1064) are overlapped with the beam steering mirrors, the Visifault was disconnected from the fiber and the  fibre output ( 1064 at the PSL table) is maximized by walking the beam at the input end and adjusting the collimation at the input.

The output of the fiber has been collimated with a fiber coupler.

7.5mW are incident on the input end and 1.3mW have been measured at the output.    This output power is adequate for the observing the beats with PSL NPRO.

 

 

 

  3866   Thu Nov 4 19:26:51 2010 SureshUpdateLockingChanges to the Video MUX reversed

All the temporary changes to the video cables and the video MUX ( 3843 ) have been reversed and the system returned to its original state.

  3867   Fri Nov 5 09:08:14 2010 steveUpdateSUSepoxy

Physical Electronics: Vac-Seal #288-6000 arriving Monday. Our last bag used last week had a p/n 1002003 with expiration date   .....2009 ? and it was stored in the

refrigerator all times. We are getting 68 small bags.

We should have precision gluing notes of epoxies/procedures used on our sus upgrade.

  3868   Fri Nov 5 14:06:19 2010 yutaUpdateIOOtried to align MC by A2L measurement

(Suresh, Kiwamu, Yuta)

Summary:
  Lastnight, we locked the MC and tried angle to length(A2L) measurement using my new python script (see elog #3863).
  Although the amount of position script shows looks too big, the response seemed somewhat reasonable.
  Using the results of A2L measurement, we managed to reduce the displacement from the center of the MC optics, but we lost TEM00 mode after changing the incident beam direction and PMC lock got off .
  We restored the alignments and now it is 00, but the displacements got worse than the best we achieved last night.

  I think I have to rethink how to align MC. Even if I could somehow get exact position of the beam, how to align the beam to the center of the optics?

What we did:
  1. At first we tried to align by changing the direction of the incident beam. We found that A2L.py shows opposite direction(lower <-> upper). It was because of my misunderstanding and we agreed that the direction is opposite.

  2. Aligned MC optics without changing the direction of the incident beam. We could understand which directions decrease the displacements from the center, and managed to decrease them.

  3. There seemed to be a limit in aligning the MC optics without changing the incident beam direction. So, we started to change the incident beam direction again by steering mirrors at PSL table.

  4. During the change, PMC lock got off. We restored it, but we lost MC's 00 mode.

  5. We restored MC 00 mode, and measured the final A2L. The result was worse than we achieved by step #2.

Result:
  The final result from last night using my script was as follows;

  MC1 MC2 MC3
vertical 36% -19% 19%
horizontal 49% 6% -37%

  % is the length compared to the half of coil to coil length. Low / right are positive.
  We can see the beam position got better by looking at the monitor from MC2, and the A2L measurement result agrees with that.

  Here's some pictures from the measurement last night. Each plots are not taken at the same time.
A2LmeasurementFigures.png
   (It was painful using slow computers to make measurement. The StripTool graph shows straight lines when computers got frozen)

Plan:
 - Plan a strategy
 - The script needs self-estimation of the measurement. Now, the script fits the plot assuming every data has the same error.
 - When the beam is near the center, the signal gets smaller and the result will be unreliable. One thing I can do is to change TO_COIL gains radically so that the axis of rotation go far from the center.

  3870   Fri Nov 5 16:40:22 2010 josephb, alexUpdateCDSc1ioo now has working awgtpman

Problem:

We couldn't set testpoints on the c1ioo machine.

Cause:

Awgtpman was getting into some strange race condition.  Alex added an additional sleep statement and shifted boot order slightly in the rc.local file.  This apparently is only a problem on c1ioo, which is a Sun X4600.  It was using up 100% of a single CPU for the awgtpman process.

Status:

We now have c1ioo test points working.

Future:

Need to examine the startc1ioo script and see if needs a similar modification, as that was tried at several points but yielded a similar state of non-functioning test points. For the moment, reboot of c1ioo is probably the best choice after making modifications to the c1ioo or c1x03 models.

Current CDS status:

MC damp dataviewer diaggui AWG c1ioo c1sus c1iscex RFM Sim.Plant Frame builder  TDS
                     
  3871   Fri Nov 5 19:33:18 2010 JenneUpdateElectronicsThe beginnings of the new phase of the RF work

Joon Ho and I took a look at the RF stuff that Alberto left, and we determined that we've got most everything that we need.  On Monday, Joon Ho will list off the stuff that we're missing, and we'll have Steve order it.

Joon Ho also replaced the temporary front panel to the RF generation box with Alberto's fancy new panel.  Pics are here (although you have to sign in as foteee to see them). 

Work on the frequency distribution box will continue on Monday.

  3874   Sat Nov 6 00:49:04 2010 KojiUpdateIOOIMC table work

[Suresh, Koji]

- Removed MCT optics in the IMC chamber

- Rotated MC1 and MC3 in clock-wise to debias the YAW bias offsets (-5V and -8V to -1.5V and -0.5V).

- Adjusted insertion of the MC1 OSEMs so as to have the outputs of about 1.0V.

- Locked to TEM00. Trying to get the beams at the center of the mirror using Yuta's A2L.

  3878   Mon Nov 8 10:37:14 2010 KojiUpdateIOOThe 10% pick-off for MCREFL was replaced to a HR mirror

As MC2 Trans mon QPD is temporary removed for fixing, we needed a reference for the MC alignment.

I replaced the 10% pick-off in the MCREFL path to the HR mirror.
Now the MCREFL DC with MC unlock is ~2.2, while it is ~0.29 in lock.
i.e. The visibility is 87%.

This means that the MCWFS were disabled for the moment.

  3879   Mon Nov 8 10:48:58 2010 kiwamuUpdateGreen Locking80MHz VCO : PLL open loop looks good

I measured the open loop transfer function of the 80MHz VCO's PLL while locking it to Marconi.

 This measurement is for a health check and a characterization of the PLL

The transfer function looks good, it agrees with the designed filter shape.

 


(measurement setup) 

vco_pll.png

 The frequency of Marconi is set to 79.5MHz which is the center frequency of the VCO.

The signal from Marconi is mixed down with the VCO signal at a mixer ZLW-3SH.

Then the demodulated signal goes to a 80MHz LPF to cut off high frequency components.

And it goes through a control filter which has 1Hz pole and 40Hz zero (see this entry).

The 80MHz LPF, the controls filter, the VCO and the RF amplifier are all built in the box.

 

 In order to measure the open loop transfer function I inserted SR560 before the 80MHz LPF.

Using T-splitters the input and the output of SR560 are connected to a spectrum analyzer SR785.

 

(results)

 VCO_PLL.png

 Exciting the system using a source channel of SR785, I measured the open loop transfer function.

The unity gain frequency was measured to about 20 kHz.

It agrees with the designed filter shape (though the gain factor is a little bit underestimated).

Apparently there is a phase delay at high frequency above 10kHz, but it is okay because the phase margin is quite acceptable up to 100kHz.

 

However I found that the control range was quite narrow.

The PLL was able to be kept in only +/- 1MHz range, this fact was confirmed by shifting the frequency of Marconi during it's locked.

I will post another elog entry about this issue.

 


 (notes)

 Marconi power = 6dBm

 VCO power after RF amp. = -0.6 dBm

 Marconi frequency = 79.5 MHz

 Phase detection coefficient = 0.4 V/rad (measured by using an oscillo scope)

 

  3880   Mon Nov 8 14:30:15 2010 josephb, yutaUpdateCDSAdded LIGONDSIP setting to cshrc.40m

We added the following line to the cshrc.40m file in the 64-bit linux and 32-bit linux sections:

setenv LIGONDSIP fb

This allows codes like tdsdmd to work properly on the linux machines (seemed to already work fine on the solaris op440m without this change).

  3881   Mon Nov 8 16:03:46 2010 kiwamuUpdateGreen Locking80MHz VCO : PLL open loop looks good

Quote:

I measured the open loop transfer function of the 80MHz VCO's PLL while locking it to Marconi.

 

Bad; there should be a passive ~1 MHz LP filter between the mixer and anything that comes after. The SR560 + mixer does not equal a demodulator.

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

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

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

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

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

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

 

 

 

  3888   Wed Nov 10 22:29:42 2010 kiwamuUpdateIOOmisaligned the wideband EOM

For Yuta's business, I intentionally misaligned the wideband EOM slightly to Yaw direction.  Good luck.

It should show a big AM component at photo detectors.

I touched only the top right knob on the EOM mount and tweaked it by exactly  2 turns in counterclockwise direction.

  3889   Thu Nov 11 01:34:27 2010 JenneUpdateSUSNew-Old ETM towers assembled

[Suresh, Jenne]

We have put together the new-old ETM towers.  These are the ones which were hanging out on the flow bench down the arm for years and years, and have recently been re-baked.  Interestingly, these are predominantly steel, whereas the newer ones are mostly aluminum.  This caused momentary drama while we scrounged for the correct screws (we needed more silver-plated screws than anticipated, since we were screwing into steel and not aluminum), however the miscellaneous clean hardware collection came to the rescue.  We did however use up all of the 1/4-20 3/4" silver plated screws, so hopefully no one else needs more later...

We only found 5 (enough for one of the two towers) spring plungers which are used to hold the OSEMs in place.  Suresh is sending an email to Steve to ask him to buy some more, so we can get them cleaned in time for use.  This is important, but not super urgent, since we have ~ 2 weeks before the ETMs will be ready for installation. 

Koji has not yet had a chance to inspect the ETM data sheets and choose for us which pair of ETMs to use (ATF sent the 4 ETMs in matched pairs).  So we will not begin the "arts and crafts" until tomorrow-ish.

  3890   Thu Nov 11 02:17:27 2010 KevinUpdateElectronicsREFL11 Photodiode Not Working

[Koji and Kevin]

I was trying to characterize the REFL11 photodiode by shining a flashlight on the photodiode and measuring the DC voltage with an oscilloscope and the RF voltage with a spectrum analyzer. At first, I had the photodiode voltage supplied incorrectly with 15V between the +15 and -15 terminals. After correcting this error, and checking that the power was supplied correctly to the board, no voltage could be seen when light was incident on the photodiode.

We looked at the REFL55 photodiode and could see ~200 mV of DC voltage when shining a light on it but could not see any signal at 55 MHz. If the value of 50 ohm DC transimpedance is correct, this should be enough to see an RF signal. Tomorrow, we will look into fixing the REFL11 photodiode.

  3893   Thu Nov 11 07:26:03 2010 AlbertoUpdateElectronicsREFL11 Photodiode Not Working

Quote:

[Koji and Kevin]

I was trying to characterize the REFL11 photodiode by shining a flashlight on the photodiode and measuring the DC voltage with an oscilloscope and the RF voltage with a spectrum analyzer. At first, I had the photodiode voltage supplied incorrectly with 15V between the +15 and -15 terminals. After correcting this error, and checking that the power was supplied correctly to the board, no voltage could be seen when light was incident on the photodiode.

We looked at the REFL55 photodiode and could see ~200 mV of DC voltage when shining a light on it but could not see any signal at 55 MHz. If the value of 50 ohm DC transimpedance is correct, this should be enough to see an RF signal. Tomorrow, we will look into fixing the REFL11 photodiode.

I just wanted to remind you that the most up to date resource about the RF system upgrade, including photodiodes, is the SVN.

https://nodus.ligo.caltech.edu:30889/svn/trunk/alberto/40mUpgrade/RFsystem/

There you can find everything: measurements, schematics, matlab scripts to plot and fit, etc. Poke around it to find what you need.
For instance, the schematic of the modified REFL11 photodiode is at:

https://nodus.ligo.caltech.edu:30889/svn/trunk/alberto/40mUpgrade/RFsystem/RFPDs/REFL11/REFL11Schematics/40mUpgradeREFL11schematic.pdf

Because I was doing new things all the time, the wiki is not up to date. But the SVN has all I've got.

  3896   Thu Nov 11 13:54:05 2010 kiwamuUpdateGreen Locking80MHz VCO : about PLL hold-in range

The hold-in range of the PLL must be greater than +/- 4MHz in order to bring the arm cavity to its resonance. 

(Hold-in range is the range of frequencies over which the PLL can track the input signal.)

However as I mentioned in the past elog (see this entry), the PLL showed a small hold-in range of about +/- 1MHz which is insufficient.

In this entry I explain what is the limitation factor for the hold-in range and how to enlarge the range.

 


(Requirement for hold-in range )

 We have to track the frequency of the green beat signal and finally bring it to a certain frequency by controlling the cavity length of the arm.

For this purpose we must be able to track the beat signal at least over the frequency range of 2*FSR ~ +/- 4MHz.

Then we will be able to have more than two resonances, in which both the end green and the PSL green are able to resonate  to the arm at the same time. 

And if we have just two resonances in the range, either one of two resonances gives a resonance for both IR and green. At this phase we just bring it to that frequency while tracking it.

 

  Theoretically this requirement can be cleared by using our VCO because the VCO can drive the frequency up to approximately +/- 5MHz (see this entry)

 The figure below is an example of resonant condition of green and IR. The VCO range should contain at least one resonance for IR.

(In the plot L=38.4m is assumed)

 

 range_green.png

 

(an issue) 

However the measured hold-in range was about +/- 1MHz or less. This is obviously not large enough.

According to a textbook[1], this fact is easily understandable.

The hold-in range is actually limited by gains of all the components such as a phase detector's, a control filter's and a VCO's gain.

Finally it is going to be expressed by,

                         [hold-in range] = G_pd * G_filter * G_vco

PLL.png

 

 At the PD (Phase Detector which is a mixer in our case) the signal does not exceed G_pd [V] because it appears as G_pd * sin(phi).

When the input signal is at the edge of the hold-in range, the PD gives its maximum voltage of G_pd to maintain the lock.

Consequently the voltage G_pd [V] goes through to G_filter [V/V] and G_vco [Hz/V].

This chain results the maximum pushable frequency, that is, hold-in range given above equation.

In our case, the estimated hold-in range was 

                      [hold-in range] ~ 0.4 [V] * 3 [V/V] * 1 [MHz/V]

                          = 1.2 [MHz]

This number reasonably explains what I saw.

In order to enlarge the hold-in range, increase the gain by more than factor of 5. That's it.

* reference [1]  "Phase-Locked Loops 6th edition" Rolan E. Best

  3898   Thu Nov 11 17:47:36 2010 kiwamuUpdateGreen Locking80MHz VCO : improve PLL hold-in range and put a boost

In order to enlarge the hold-in range I modified the control filter and increased the gain by factor of 25 in the PLL.

It successfully enlarged the range, however the lock was easily broken by a small frequency change.

So I put a low frequency boost (LFB) and it successfully engaged the PLL stiffer.

Now it can maintain the lock even when the frequency disturbance of about 1MHz/s is applied.

 


(enlargement of the hold-in range)

I modified the control filter by replacing some resistors in the circuit to increase the gain by factor of 25.

        - R18 390 [Ohm]  => 200 [Ohm]

    - R20 1000 [Ohm] => 5000 [Ohm]

    - R41 39 [Ohm] => 10 [Ohm]

 This replacement also changes the location of the pole and the zero

    - pole 1.5 [Hz] => 0.3 [Hz]

    - zero 40 [Hz] => 159 [Hz]

 Note that this replacement doesn't so much change the UGF which was about 20 kHz before.

It becomes able to track the input frequency range of +/- 5MHz if I slowly changes the frequency of the input signal. 

However the PLL is not so strong enough to track ~ 1 kHz / 0.1s frequency step.  

 

(make the PLL stiffer : a low frequency boost)

One of the solution to make the PLL stiffer is to put a boost filter in the loop.

I used another channel to more drive the VCO at low frequency. See the figure below.

 vco_pll.png

The 80MHz VCO box originally has two input channels, one of these inputs was usually disabled by MAX333A.

This time I activated both two input channels and put the input signal to each of them.

Before signals go to the box, one of the signal path is filtered by SR560. The filter has G=20000, pole=0.3Hz. So it gives a big low frequency boost.

VCO_lfb.png

Once the PLL was achieved without the boost, I increased the filter gain of SR560 to 20000 because locking with the boost is difficult as usual.

 

  3899   Thu Nov 11 18:05:55 2010 valeraUpdatePSLPMC mode matching at full laser power

 The PMC mode matching was initially done at low power ~150 mW. It was expected and found that at full power ~2 W (injection current 2.1 A) the mode matching got much worse:

the visibility degraded from 80% to 50% (1 - refl locked/refl unlocked) . The thermal lensing could be in the laser, EOM, or FI.

The first attached plot shows the scan of the beam after the EOM at low and full laser power. At full power the waist position is 10 mm after the turning mirror after the EOM and the waist size is 310 um.

The second plot shows the ABCD calculation for the mode matching solution.

I removed the MM lens PLCX-25.4-77.3-C and placed the PLCX-25.4-180.3-UV about 20 mm after the first PMC periscope mirror (the second mirror after the EOM).

The PMC visibility improved to 94% and the power through the PMC, as measured by the PMC transmission PD, went up by a factor of 2.

  3900   Thu Nov 11 21:07:49 2010 josephbUpdateCDSPlugged c1iscex into DAQ network - still causes network slowdown

I connected the c1iscex computer to the dedicated DAQ network switch (located in 1X7).

This does not seem to have helped c1iscex stop spewing out "OMX: Failed to find peer index of board 00:00:00:00:00:00 (Peer Not Found in the Table)" at the rate of ~1 Gigabyte per minute.

c1iscex is currently off until a solution can be found.

  3902   Fri Nov 12 00:13:34 2010 SureshUpdateSUSETM assembly started

[Jenne, Suresh]

Selection of ETMs

Of the four ETMs (5,6,7 and 8) that are with us Koji gave us two (nos. 5 and 7) for use in the current assembly.  This decision is based on the Radius of Curvature (RoC) measurements from the manufacturer (Advanced Thin Films).   As per their measurements the four ETMs are divided into two pairs such that each pair has nearly equal RoC. In the current case, RoCs are listed below:

   

Radii of Curvature of ETMs
ETM # RoC from Coastline Optics (m) RoC from Advanced Thin Films (m)
5 57.6 60.26
6 57.4 54.58
7 57.1 59.48
8 57.9 54.8

 

The discrepancy between the measurements from these two companies leaves us in some doubt as to the actual radius of curvature.  However we based our current decision on the measurement of Advanced Thin Films. 

 

Assembly of ETMs

We drag wiped both the ETMs (5 and 7) and placed them in the Small Optic Gluing Fixture.  The optics are positioned with the High Reflectace side facing downwards and with the arrow-mark on the Wire Standoff side (big clamp).  We then used the microscope to position the Guide Rod and the Wire Standoff in the tangential direction on the ETMs (step 4 of the procedure specified in E010171-00-D)

We will continue with the rest of the assembly tomorrow.

 

  3903   Fri Nov 12 00:42:11 2010 rana, kojiUpdateIOOMC alignment

We decided to ignore the computer script outputs for the beam positions and use instead the eyeball method to get the beam into the MC:

  1. Adjust PSL launch beam to get the beam centered on IM1.
  2. Eyeball the beam to hit the center of MC1. We can get this pretty good by using the brackets to get the vertical and using the centering of the input/refl beams to center it horizontally.
  3. Use MC3 suspension to hit the center of MC2. We did this by hitting each of the 3 EQ stop screw heads and triangulating the MC3 bias settings.
  4. Use MC2 bias to hit the center of MC1.
  5. Use MC1 to get good flashes.
  6. Use all 3 MC sus biases to maximize the transmitted light and minimize the REFL DC.

With this rough alignment in place, we leave it to Yuta to finish the coil balancing and the A2L. We will have an aligned MC in the morning and will start the BS chamber alignment.

  3904   Fri Nov 12 02:51:20 2010 KevinUpdateElectronicsPhotodiode Testing

[Jenne and Kevin]

I started testing the REFL55 photodiode. With a light bulb, I saw ~270 mV of DC voltage from the photodiode but still could not see any RF signal. I connected the RF out from the spectrum analyzer to the test input and verified that the circuit was working.

I then set up the AM laser and looked at the laser light with REFL11 and an 1811 photodiode. I was able to see an RF signal and verified that the resonant frequency is 55 MHz.

The current setup is not very reliable because the laser is not mounted rigidly. Next, I will work on making this mounting more reliable and will continue to work on finding an RF signal with a flashlight.

  3905   Fri Nov 12 06:10:24 2010 yutaUpdateIOOMC aligned (without coil balancing)

Background:
  Last night, we found that one of DAC channels are poorly connected, so we fixed the connectors.
  Rana and Koji used their incredible eyeballs to roughly align MC.
  Next thing to do is to balance the coils, but it takes some time for the setup.
  So, we decided to do A2L anyway.

What I did:
  Using the last steering mirror at PSL table and IM1, changed the incident beam direction to align MC.

Result:
MCalignCALIB.png
 
  I was amazed by their eyeballs.
  I turned the nobs of SM@PSL and IM1 in small increments, so I never lost TEM00.

Is it enough?:
  The length of the whole faraday is about 20cm and aperture diameter is about 12mm. (I couldn't measure the aperture size of the core)
  The beam is about 9mm diameter at 6w.
  So, if the beam is vertically tilted at more than ~3/200rad, it(6w) cannot go through.
  3/200 rad is about 20% difference in position at MC1 and MC3.
  So, the result meets the requirement.

  Also, assuming that coils have 5% imbalance, the beam position I measured have ~3% error.
  So, to do more precise beam centering, we need to balance the coils.

  3906   Fri Nov 12 10:49:34 2010 josephb, valeraUpdateCDSTest of ADC noise

Test:

Look at the effects of the ADC voltage range on the ADC noise floor.

ADC input was terminated with 50 ohms.  We then looked at the channel with DTT. This was at +/- 10 V range.  We used C1:SUS-PRM_SDSEN_IN1 as the test channel.

The map.c file (in /opt/rtcds/caltech/c1/core/advLigoRTS/src/fe/ ) then had two lines added at line 766.

//JCB temporary 2.5V test, remove me
  adcPtr[devNum]->BCR &= 0x84240;

This hard coded the 2.5 V range (we default to the 10 V range at the moment).

We then rebuilt the c1x02 model and reran the test.

Finally, we reverted the code change to map.c and rebuilt c1x02.

Results:
I've attached the DTT output of the two tests.

It appears the ADC is limited by 1.6 uV/rtHz.  Hence the increase in noise in counts by a factor of 4 when we drop to +/- 2.5 V from +/- 10 V.

  3909   Fri Nov 12 13:12:55 2010 kiwamuUpdatePSLincreased NPRO power

I maximized the laser power by rotating the HWP after the NPRO.

If someone works on the MC locking, one should decrease it again.

 

  3910   Fri Nov 12 19:24:56 2010 KojiUpdateCDSTest of ADC noise

[Koji Yuta]

We found one of the ADC cables were left unconnected. This left the MC suspensions uncontrollable through the whole afternoon.
Please keep the status updated and don't forget to revert the configuration...

Quote:

Test:

Look at the effects of the ADC voltage range on the ADC noise floor.

ADC input was terminated with 50 ohms.  We then looked at the channel with DTT. This was at +/- 10 V range.  We used C1:SUS-PRM_SDSEN_IN1 as the test channel.

The map.c file (in /opt/rtcds/caltech/c1/core/advLigoRTS/src/fe/ ) then had two lines added at line 766.

//JCB temporary 2.5V test, remove me
  adcPtr[devNum]->BCR &= 0x84240;

This hard coded the 2.5 V range (we default to the 10 V range at the moment).

We then rebuilt the c1x02 model and reran the test.

Finally, we reverted the code change to map.c and rebuilt c1x02.

Results:
I've attached the DTT output of the two tests.

It appears the ADC is limited by 1.6 uV/rtHz.  Hence the increase in noise in counts by a factor of 4 when we drop to +/- 2.5 V from +/- 10 V.

 

  3912   Sat Nov 13 15:53:05 2010 yutaUpdateCDSdiagonalization of MC input matrix

Motivation:
  MC is aligned from the A2L measurement, but to do the beam centering more precisely, we need coils to be balanced.
  There are several ways to balance the coils, like using oplev or WFS QPD RF channels.
  But oplev takes time to setup, especially for MC3. Also, c1ioo WFS channels were newly setup and haven't been checked yet.
  So, I decided to use OSEM sensors.
  An OSEM sensor itself is sensitive to every DOF of an optic motion, but we can diagonalize them using 4 OSEM sensors and proper input matrix.

Method:

  1. Measure transfer functions between
     ULSEN and URSEN (H_UR(f))
     ULSEN and LRSEN (H_LR(f))
     ULSEN and LLSEN (H_LL(f))

  2. Make a matrix A.

    A =  [[ 1           1           1          ]
          [ H_UR(f_pos) H_UR(f_pit) H_UR(f_yaw)]
          [ H_LR(f_pos) H_LR(f_pit) H_LR(f_yaw)]
          [ H_LL(f_pos) H_LL(f_pit) H_LL(f_yaw)]]


    where f_dof are resonant frequencies.

  3. A is

    s = Ad


   where vectors s^T=[ULSEN URSEN LRSEN LLSEN] and d^T=[POS PIT YAW].
   So,

    d = Bs = (A^TA)^(-1)A^Ts

   where A^T is transpose of A.

   B is the input matrix that diagonalizes 3 DOFs.

What I did:

  1. Measured the TFs using diaggui and exported as ASCII.

  2. Made a script that reads that TF file, calculates and sets a new input matrix B.
    /cvs/cds/caltech/users/yuta/scripts/inputmatrixoptimizer.py
   You need to set resonant frequencies to use the script.

   New input matrices for MCs are;

C1:SUS-MC1_INMATRIX
[[ 1.17649712  0.94315611  0.85065054  1.02969624]
 [ 0.55939288  1.28066594 -0.85235358 -1.3075876 ]
 [ 1.23467139 -0.74521928 -1.29394051  0.72616882]]

C1:SUS-MC2_INMATRIX
[[ 1.12630748  1.01451545  0.9013457   0.95783137]
 [ 1.03043025  0.67826036 -1.37270598 -0.91860341]
 [ 0.83546271 -1.26311029 -0.6456881   1.2557389 ]]

C1:SUS-MC3_INMATRIX
[[ 1.18212117  1.26419447  0.77744155  0.77624281]
 [ 0.79344415  0.84959646 -1.10946339 -1.247496  ]
 [ 1.00225331 -0.84807863 -1.21772132  0.93194674]]


  I ignored SIDE this time.

Result:

  Spectra of each SUSDOF_IN1_DAQ before diagonalization (INMATRIX elements all 1 or -1) were
MCspectraNov09.png

  After diagonalization, spectra are
MCspectraNov13.png

  As you can see, each SUSDOF has only single peak (and SIDE peak) after the diagonalization.
  SUSSIDE still has 4 peaks because SIDE is not included this time.

  For MC2, POS to SUSPIT and POS to SUSYAW got worse. I have to look into them.

Effect of resonant frequency drift:

  As you can compare and see from the spectra above, resonant frequencies of MC1 are somehow drifted(~0.5%) from Nov 9 to Nov 13.
  If resonant frequency you expected was wrong, calculated input matrix will be also wrong.
  The effect of 0.5% drift and wrong input matrix can be seen from this spectra. DOFs are not clearly separated.
 MC1spetra_wrongmatrix.png

Plan:

 - learn how to use diaggui from command line and fully automate this process
 - balance the coils using these diagonalized SUSPOS, SUSPIT, SUSYAW

  3915   Sun Nov 14 11:56:59 2010 valeraUpdateCDSTest of ADC noise

 

We missed a factor of 2 in the ADC calibration: the differential 16 bit ADC with +/-10 V input has 20 V per 32768 counts (1 bit is for the sign). I confirmed this calibration by directly measuring ADC counts per V.

So the ADC input voltage noise with +/-10V range around 100 Hz is 6.5e-3 cts/rtHz x 20V/32768cts =  4.0 uV/rtHz. Bummer. 

The ADC quantization noise limit is 1/sqrt(12 fs/2)=1.6e-3 cts/rtHz. Where the ADC internal sampling frequency is fs=64 kHz. If this would be the limiting digitization noise source then the equivalent ADC input voltage noise would be 1 uV/rtHz with +/-10 V range.

  3916   Sun Nov 14 16:26:31 2010 jenne, valeraUpdateElectronicsSRM side OSEM noise with no magnet

We realized that the SRM sensors are connected to the readout but just sitting on the BS in vacuum table with no magnets and therefore no shadows in them. We swapped the inputs to the SRM and PRM satellite boxes to use the higher transimpedance gain of the PRM side sensor. The attached plot shows the current spectrum in this configuration. The PD readback voltage was 9.5 V. Since this is close to the rail we put a slightly higher voltage into the AA of this channel to test that we can read out more ADC counts to make sure we are not saturating. The margin was 15800 vs 15400 counts with p-p of 5 counts on the dataviewer 1 second trend. We returned all cables to nominal configuration.

The calibration from A to m is 59 uA/1 mm.

  3917   Sun Nov 14 16:40:46 2010 JenneUpdateTreasureActivities related to OSEM measurement

[Valera, Jenne]

We pondered the idea of clamping the PRM optic to measure the OSEM noise.  So we opened up the BS tank to give this a try.  We rediscovered that Jenne is too short to reach the other side of the PRM tower, so we couldn't fully clamp the optic (when is Jaime coming again? He's kind of tall...)  If we only did the back 2 EQ stops, the optic would still be able to rock, and thus defeat the purpose of clamping anyway.  So we didn't go for it. 

While we were in there we saw that the SRM OSEMs were just hanging out on the table, and decided to go with them.  See Valera's elog for details on our measurement.  We closed up the tank without making any changes to anything.

In other news, we still need to figure out how to change up the connectors to get those OSEMs over to the ITM table.  This needs to happen pretty soonish. 

  3918   Mon Nov 15 04:57:10 2010 ranaUpdateElectronicsSRM side OSEM noise with no magnet

IF I believe this calibration and IF I believe that the noise is the same with no magnet in there, then its almost 1 nm/rHz @ 1 Hz.

I am guessing that Jenne's calculation will show that this is an unacceptably high level of OSEM sensor noise, OAF-wise.

  3919   Mon Nov 15 11:13:12 2010 josephbUpdateCDSModified rc.local to not start mx_streams automatically

Problem:

c1iscex floods the network with about 1 gigabyte of error messages in a few seconds, writing to a log file in /opt/rtcds/caltech/c1/target/fb/logs/

Temporary change:

I commented out the following line in the rc.local file on the fb machine in the /diskless/root/etc/ directory:

#nice --20 ./mx_stream -s "$SYSTEMS" -d fb:0 >& logs/$HOSTNAME.log&

This disables the automatic start up of the mx_streams code on all the front ends.  This will prevent the network being brought to its knees by c1iscex while we debug the problem.

It also means on a reboot of the front ends, the mx_stream process needs to be started by hand until this change is reverted.

To do this, log into the front end and then change directory to /opt/rtcds/caltech/c1/target/fb

For c1sus, run:

./mx_stream -s c1x02 c1sus c1mcs c1rms c1rfm  -d fb:0

For c1ioo, run:

./mx_stream -s c1x03 c1ioo -d fb:0

 

  3920   Mon Nov 15 11:52:22 2010 kiwamuUpdateGreen LockingPLL with real green signal

 PLL_with_green.png

Stabilizing the beat note frequency using Yuta's temperature servo (see this entry)

I was able to acquire the PLL of 80MHz VCO to the real green signal.

Some more details will be posted later.

  3921   Mon Nov 15 14:36:37 2010 KojiUpdatePSLC1PSL rebooted?

Has C1PSL rebooted? Has burtrestore been forgotten? Even without elog?

We found some settings are wrong and the PMC has pretty low gain.

  3922   Mon Nov 15 14:42:01 2010 AidanUpdatePSLC1PSL rebooted?

Yeah. Joe and I rebooted c1psl a couple of times this morning. I didn't realize the burtrestore wasn't automatic.

 

Quote:

Has C1PSL rebooted? Has burtrestore been forgotten? Even without elog?

We found some settings are wrong and the PMC has pretty low gain.

 

  3923   Mon Nov 15 15:01:51 2010 kiwamuUpdateIOOrealigned the wideband EOM

Since we are going to lock the MC today, I aligned it back to the default place.

Quote: #3888

For Yuta's business, I intentionally misaligned the wideband EOM slightly to Yaw direction. 

  3925   Mon Nov 15 16:09:44 2010 JenneUpdateVACETMX, ETMY, ITMY chambers opened

[Steve, Jenne, Suresh, Koji]

The remaining test mass chambers have been opened, and have light doors in place.  Now we can do all of the rest of the IFO alignment, and then (hopefully) button up before the New Year.

  3926   Mon Nov 15 16:26:46 2010 josephbUpdateCDSc1iscex is now running and the network hasn't died

Problem:

c1iscex was spamming the network with error messages.

Solution:

Updated the front end codes to current standards (they were on the order of months out of date).  After fixing them up and rebuilding the codes on c1iscex, it no longer had problems connecting to the frame builder.\

Status:

I can look at test points for ETMX.  It is not currently damping however.

To Do:

Move filters for ETMX into the correct files. 

Need to add a Binary output blue and gold box to the end rack, and plug it into the binary output card.  Confirm the binary output logic is correct for the OSEM whitening, coil dewhitening, and QPD whitening boards. 

Get ETMX damped.

Figure out what we're going to do with the aux crate which is currently running y-end code at the new x-end.  Koji suggested simply swapping auxilliary crates - this may be the easiest.  Other option would be to change the IP address, so that when it PXE boots it grabs the x-end code instead of the y-end code.

Current CDS status:

MC damp dataviewer diaggui AWG c1ioo c1sus c1iscex RFM Sim.Plant Frame builder TDS
                     
  3927   Mon Nov 15 17:10:59 2010 kiwamuUpdateGreen LockingPLL with real green signal

 I checked the slow servo and the PLL of 80MHz VCO using the real green beat note signal.

 The end laser is not locked to the cavity, so basically the beat signal represents just the frequency fluctuation of the two freely running lasers.

 The PLL was happily locked to the green beat note although I haven't fedback the VCO signal to ETMX (or the temperature of the end laser).

 It looks like we still need some more efforts for the frequency counter's slow servo because it increases the frequency fluctuation around 20-30mHz.

 


 (slow servo using frequency counter)

   As Yuta did before (see his entry), I plugged the output of the frequency counter to an ADC and fedback the signal to the end laser temperature via ezcaservo.

The peak height of the beat note is bigger than before due to the improvement of the PMC mode matching.

The peak height shown on the spectrum analyzer 8591E is now about -39dBm which is 9dB improvement. 

 

     The figure below is a spectra of the frequency counter's readout taken by the spectrum analyzer SR785.

 FCnoise.png

When the slow temperature servo is locked, the noise around 20-30 mHz increased.

I think this is true, because I was able to see the peak slowly wobbling for a timescale of ~ 1min. when it's locked.

But this servo is still useful because it drifts by ~5MHz in ~10-20min without the servo.

Next time we will work on this slow servo using Aidan's PID control (see this entry) in order to optimize the performance.

In addition to that, I will take the same spectra by using the phase locked VCO, which provides cleaner signal.

 

(acquisition of the PLL)

 In order to extract a frequency information more precisely than the frequency counter, we are going to employ 80MHz VCO box.

 While the beat note was locked at ~ 79MHz by the slow servo, I successfully acquired the PLL to the beat signal.

 However at the beginning, the PLL was easily broken by a sudden frequency step of about 5MHz/s (!!).

I turned off the low noise amplifier which currently drives the NPRO via a high-voltage amplifier, then the sudden frequency steps disappeared.

After this modification the PLL was able to keep tracking the beat signal for more than 5min.

(I was not patient enough, so I couldn't stand watching the signal more than 5min... I will hook this to an ADC)

Quote: #3920

Some more details will be posted later.

 

  3928   Mon Nov 15 22:24:28 2010 SureshUpdateSUSSelection of Magnets

I have selected a set of 16 magnets which have a B field between 900 to 950 Gauss (5% variation) when measured in the following fashion.

I took a Petri-dish, of the type which we usually use for mixing the glue, and I placed a magnet on its end.  I then brought the tip of the Hall-probe into contact with the Petri-dish from the opposite side and adjusted the location (and orientation) of the probe to maximise the reading on the Gauss meter.

The distribution of magnets observed is listed below

 

Range of B Field (Gauss) # of Magnets
800-849 2
850-899 6
900-950
16

 

 

 

 

 

The set of sixteen has been have been placed inside two test tubes and left on the optical bench (right-side)  in the clean room.

 

 

  3929   Tue Nov 16 03:33:22 2010 yutaUpdateIOOaligned Faraday, beam reached SM just before PRM

(Koji, Yuta)

We aligned the Faraday after MC and we are now ready to install PRM.

Background:
  MC was roughly aligned (beam spot ~0.7mm from the actuation center).
  So, we started aligning in-vac optics.
  First thing to align was the Faraday after MC3.

What we did:
  1. Ran A2L.py for confirmation.(Second from the last measurement point on the A2L result plot)

  2. Aligned the Faraday so that MC3 trans can go through it. We moved the Faraday itself, while we didn't touch IM2.
     We turned the pitch nob of the last steering mirror at PSL table in CCW slightly in order to lower the beam at the Faraday by ~1mm.

  3. During the alignment, we found that the polarization of the incident beam was wrong. It should have been S but it was P.
     As there is the HWP right before the EOM, Rana rotated it so as to have the correct polarization of S on the EOM and the MC.
     Note that the PMC and the main interferometer are configured to have P-pol while the MC is to have S-pol.

  4. Setup the video camera to monitor the entrance aperture of the Faraday. It required 4 steering mirrors to convey the image to the CCD.

  5. Moved all of the OSEMs for MC1 and MC3 so that the sensor output can have roughly half of their maxima.

  6. Ran A2L.py. (The last measurement point on the A2L result plot)

  7. Aligned the IO optics so that the beam goes Faraday -> MMT1 -> MMT2 -> SM3.

Result:

  1. OSEM sensor outputs for MC1 and MC3 are;

(V) MC1 MC3
max current value max current value
ULSEN 1.3 0.708 1.37 0.699
URSEN 1.4 0.845 1.71 0.796
LRSEN 1.45 0.743 1.77 0.640
LLSEN 1.56 0.762 1.56 0.650
SDSEN 1.67 0.801 1.59 0.821



  2. A2L result is;
MCalignNov16.png


     The beam position slightly got lower(~0.2mm), because we touched SM at PSL table.
     Alignment slider values changed because we moved MC1 and MC3 OSEMs.

  3. Now, MC_RFPD_DCMON is ~0.39 when MC unlocked and ~0.083 when locked.
     So, the visibility of MC is ~79% (for S-pol).

  4. Now the incident beam to the MC has S polarization, the cavity has higher finesse. This results the increased MC trans power.
     It was ~8e2 when the polarization was P, now it is ~4.2e3 when the MC is locked.

  5. The beam reached SM3 at BS table. The alignment of the SM2, MMT1, MMT2 were confirmed and adjusted.

  6. All pieces of the leftover pizza reached my stomach.

Plan:
  - Install PRM to the BS chamber.
  - Align PRM and get IFO reflection beam out to the AP table
 

  3930   Tue Nov 16 09:02:54 2010 AidanUpdateGreen LockingPID loop - calibration of SR620 output

 [Aidan, Kiwamu]

Kiwamu and I roughly calibrated the analogue output from the SR620 frequency counter yesterday. The input channel, intuitively named C1:PSL-126MOPA_126MON, now reads the measured frequency in MHz with an error of about 0.1MHz - this is, I think, due to the bit noise on the D/A conversion that Kiwamu discovered earlier. That is, the output range of the SR620 corresponds to around 100MHz and is digitized at 10-bit resolution, and ...

100MHz/(10^2) ~= 0.098MHz. [Sad Face]

Calibration:

We set the EPICS range to [-100, 100] (corresponding to [-5V, 5V]), connected a Marconi to the Freq Counter, input a variety of different frequencies and measured the counts on the EPICS channel.

The linear fit to the calibration data was F = 2.006*EPICScount - 0.2942. From this we worked out the maximum and the minimum for the range settings that give the channel in MHz: EGUF = -200.8942 and EGUL = 200.3058. The previous range was [-410, 410]

 

Calibration of SR620 analogue output
Input Frequency (MHz) Measured EPICS Value
10  5.191
20  9.98
30 15.21
40 20.00
50 25.18
60 29.99
70 35.18
71 35.565
72 35.9894
73 36.3861
74 37.17
75 37.576
76 37.9669
77 38.3575
78 39.166
79 39.5691
80 39.978
   

 

ELOG V3.1.3-