40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 93 of 339  Not logged in ELOG logo
IDup Date Author Type Category Subject
  4637   Thu May 5 13:14:15 2011 kiwamuUpdateLSCchans file for LSC

Foton doesn't correctly display the LSC filter bank file : C1LSC.txt.

Foton tells a lie that they all are empty.

 

The file itself looks fine to me i.e. I can find correct filters in text format.

Looks like someone (maybe Joe and Jenne ?) updated the file. I am not sure if this is the reason or not.

allegra:chans>ls -al | grep LSC
-rw-r--r--  1 controls controls   20659 May  5 11:46 C1LSC.txt

 

NEEDS TO BE FIXED SOON

  4638   Thu May 5 13:55:08 2011 kiwamuUpdateLSCMI locking : calibration of BS and ITMs actuators

EDIT by KI on 15/5/2011:

The calibration of MICH error signal was wrong by a factor of 2.

 

The open loop transfer functions of the Michelson locking have been measured.

The purpose of this excise is to calibrate the coil-magnet actuators on BS and ITMs.

The estimated actuation coefficients are :

 BS = 3.69e-08 [m/counts]
 ITMX = 8.89e-09 [m/counts]
 ITMY = 9.22e-09 [m/counts] 

I guess the accuracy is something like 5 % because the calibration of the MI optical gain relies on a peak-to-peak measurement.

A next step is to calibrate the PRM actuator and the PRC optical gain.


 

(measurement)

The Michelson was locked with different actuators in every measurement. I locked the Michelson to the dark fringe with BS, ITMX and ITMY in each time.

The measured peak-to-peak value in the error signal was 20.2 counts, corresponding to a sensor gain of 5.96e+07 [counts/m]. Note that I used AS55_Q for the locking.

After locking the MI I took the open loop transfer function by injecting broadband noise from DTT.

Then the data were fitted coarsely.  In the fitting I used the resonant frequencies that Leo reported recently (http://blue.ligo-wa.caltech.edu:8000/40m/Mechanical_Resonances).

The Q-values are assumed to be 5 because of the local dampings. As a result the fitting gives us the actuator coefficients.

Here is a plot showing the measured open loop transfer functions. The solid lines represent the fittings.

MICH_OL.png

 

(by the way)

- The delay time including ADC/DAC and RFM looks quite big. According to the fitting the delay is something like 600 usec.

This is about two times larger than the one reported before (see this entry). I will re-measure it with empty filters.

  4639   Thu May 5 14:40:14 2011 KojiUpdateLSCMI locking : calibration of BS and ITMs actuators

I've got confused

1) Are these the DC responses of the coils? If that is true, we need to specify the resonant frequency of each suspension to get the AC response.

2) Are these the AC responses well above the resonant freqs? In that case, The responses should be x.xxx / f^2 [m/counts]

Quote:

The open loop transfer functions of the Michelson locking have been measured.

The purpose of this excise is to calibrate the coil-magnet actuators on BS and ITMs.

The estimated actuation coefficients are :

 BS = 3.69e-08 [m/counts]
 ITMX = 8.89e-09 [m/counts]
 ITMY = 9.22e-09 [m/counts]

  4640   Thu May 5 14:50:30 2011 JenneUpdateLSCchans file for LSC

Quote:

Foton doesn't correctly display the LSC filter bank file : C1LSC.txt.

Foton tells a lie that they all are empty.

 

The file itself looks fine to me i.e. I can find correct filters in text format.

Looks like someone (maybe Joe and Jenne ?) updated the file. I am not sure if this is the reason or not.

allegra:chans>ls -al | grep LSC
-rw-r--r--  1 controls controls   20659 May  5 11:46 C1LSC.txt

 

NEEDS TO BE FIXED SOON

 See my updated elog 4636 for what Joe and I did this morning, and what a possible problem is (making the LSC model into a sub-model).

  4641   Thu May 5 15:05:06 2011 steveUpdatePSLPSL-FSS_RMTEMP is not back

Quote:

Valera and I installed the the temp sensor and the interface box that Rana fixed. This may help with diagnosing the PSL drift.

 I was wrong. Rana did not fix the interface box. I removed the interface box and turned down the HEPA flow  from 100 to 20% on the Variac.

Attachment 1: rtnfxd.jpg
rtnfxd.jpg
  4642   Thu May 5 15:26:52 2011 Leo SingerConfigurationComputers'glue' installed on some control room computers

I installed 'glue' on Rossa, Allegra, and Rosalba.  This is a Python module that includes a facility for LIGO_LW XML files.  Oddly, I couldn't find the glue package on Pianosa.

  4643   Thu May 5 15:28:23 2011 kiwamuUpdateLSCRe: MI locking : calibration of BS and ITMs actuators

They are the DC responses.

I put the resonant frequencies that Leo reported in the wiki to obtain the DC response.

The resonant frequencies I used are :

  f_BS = 0.957 Hz

  f_ITMX = 0.966 Hz

  f_ITMY = 0.988 Hz

Also I assumed that all the Q-values are 5 due to the damping.

Quote:

I've got confused

1) Are these the DC responses of the coils? If that is true, we need to specify the resonant frequency of each suspension to get the AC response.

2) Are these the AC responses well above the resonant freqs? In that case, The responses should be x.xxx / f^2 [m/counts]

Quote:

 BS = 3.69e-08 [m/counts]
 ITMX = 8.89e-09 [m/counts]
 ITMY = 9.22e-09 [m/counts]

 

  4644   Thu May 5 15:33:37 2011 steveConfigurationRF SystemLSC rack

New right angle PVC front panel with SMA bulkhead connectors are in place. The connections are still lose. It is ready for Suresh to finalise his vision on it.

Attachment 1: P1070641.JPG
P1070641.JPG
Attachment 2: P1070639.JPG
P1070639.JPG
  4645   Thu May 5 16:11:22 2011 JamieUpdateLSCchans file for LSC

Quote:

Foton doesn't correctly display the LSC filter bank file : C1LSC.txt.

 This was because of a bug in the RCG for foton filter module naming when top names is being used.  Rebuilding the LSC front-end model with top_names (which was needed to get around another bug in the RCG) broke the filter file.  I manually fixed the file, so it should work now.

  4646   Thu May 5 17:19:21 2011 Leo SingerConfigurationSUSTuning notch filters for bounce mode suspensions

I am tuning the notch filters for the bounce modes in the suspensions, starting with the ITMs and ETMs.  I'll do the MCs, the PRMs, and the SRMs next.

 

I noticed that the filter for ITMX (in the file C1SUS.txt, the module ITMX_SUSPOS, the selection BounceRoll) that the filter was composed of two bandstops (and a constant gain).  It looked like this:

 

ellip("BandStop",4,1,40,11.4,12.2)ellip("BandStop",4,1,40,16.7,17.5)gain(1.25872)

 

Valera said that one of these was for the roll mode and the other for the bounce mode.  However, looking at the spectra that Kiwamu and I made this week, I don't perceive a resonance between 11.4 and 12.2 Hz.  So, we're taking a guess that this was for a mode that has moved due to new pendulum designs.  For many of the suspensions, in the free swinging test we noticed a line around 23 Hz; we thought we might as well re-use one of these elliptical filters to avoid exciting this line.  Of course, if this line does *not* result from excitation of an uncontrolled degree of freedom, this will not help and could be detrimental.  When we talk to Valera again, we can review this decision and at that point we might decide just to take out that bandstop.

 

ITMX is done.  I'll continue tomorrow.  I've attached closed-loop spectra for before the tuning (itmx-before.pdf) and after (itmx-after.pdf).

 

(Update: the following day, I took closed loop spectra with (itmx-withbounceroll.pdf) and without (itmx-nobounceroll.pdf) the bandstops.  It looks like the bandstops made the bounce mode slightly worse, but the roll mode slightly better.)

 

 

Attachment 1: itmx-before.pdf
itmx-before.pdf
Attachment 2: itmx-before.pdf
itmx-before.pdf
Attachment 3: itmx-withbounceroll.pdf
itmx-withbounceroll.pdf
Attachment 4: timx-nobounceroll.pdf
timx-nobounceroll.pdf
  4647   Thu May 5 18:38:01 2011 ranaSummaryCDSSub-system TRAMP adjustments

I think that the gain ramping time (_TRAMP) should be set to 1 second for all filter modules by default. We don't want them to switch instantaneously except in a few special cases.

So Jamie and I wrote a script (in scripts/general/) which sets all of these fields to 1 for a given system. The name of the system is an argument to the script. e.g.

>  setTRAMP LSC 1

The idea is that we set it once and then from then on, its captured by the autoBURT. Of course, we have to run this script each time we add new filter modules to a model.

  4648   Thu May 5 20:47:41 2011 KojiUpdatePSLPMC aligned

The PMC exhibited the reduction of the transmission, so it was aligned.

The misalignment was not the angle of the beam but the translation of the beam in the vertical direction
as I had no improvement by moving the pitch of one mirror and had to move those two differentially.

This will give us the information what is moving by the temperature fluctuation or whatever.

  4649   Fri May 6 01:27:12 2011 KojiSummaryGeneralaLIGO BBPD / Green PD investigation

Minicircuits ERA-5SM was used for the RF amp of the BBPD. This amp is promising as a replacement of Teledyne Cougar AP389
as ERA-5SM gave us the best performance so far among the BBPDs I have ever tested for the aLIGO BBPD/Green.

The -3dB bandwidth of ~200MHz and the noise floor at the shotnoise level of 0.7mA DC current were obtained.


1. Introduction

The aLIGO BBPD candidate (LIGO Document D1002969-v7) employs Teledyne Cougar AP389 as an RF amplifier.
This PD design utilizes the 50Ohm termination of the RF amp as a transimpedance resistance at RF freq.

However, it turned out that the bandwidth of the transimpedance gets rather low when we use AP389, as seen in the attachment2.
The amplifier itself is broadband upto 250MHz (the transfer function was confirmed with 50Ohm source).
The reason is not understood but AP389 seems dislike current source. Rich suggested use of S-parameter measurement
to construct better model of the curcuit.

On the other hand, the RF amplifiers from Minicircuits (coaxial type like ZFL-1000LN+), in general, exhibit better compatibility with PDs.
If you open the amplifier case, you find ERA or MAR type monolithic amplifiers are used.

So the question is if we can replace AP389 by any of ERA or MAR.

2. Requirement for the RF amp

- The large gain of the RF amp is preffered as far as the output does not get saturated.

- The amplifier should be low noise so that we can detect shot noise (~1mA).

- The freq range of the useful signal is from 9MHz to 160MHz.

The advanced LIGO BBPD is supposed to be able to receive 50mW of IR or 15mW of 532nm. This approximately corresponds to
5mA of DC photocurrent if we assume FFD-100 for the photodiode. At the best (or worst) case, this 5mA has 100% intensity modulation.
If this current is converted to the votage through the 50Ohm input termination of the RF amp, we receive -2dBm of RF signal at maximum.

This gives us a dilemma. if the amp is low noise but the maximum output power is small, we can not put large amount of light
on the PD. If the amp has a high max output power (and a high gain), but the amp is not low noise, the PD has narrow power range
where we can observe the shotnoise above the electronics noise.

What we need is powerful, high gain, and low noise RF amplifier!

Teledyne Cougar AP389 was almost an ideal candidate before it shows unideal behavior with the PD.
Among Minicircuits ERA and MAR series, ERA-5 (or ERA-5SM) is the most compatible amplifier.


AP389 ERA-5
Freq Range 10-250MHz DC-4GHz
Gain >24.5dB 20dBtyp
Output power (1dB compression)
23dBm 18.4dBm
IP3 36dBm 33dBm
Noise Figure <3.3dB 3.5dB

Considering the difference of the gain, they are quite similar for our purpose. Both can handle upto -2dBm,
which is just the right amount for the possible maximum power we get from the 5mA of photocurrent.

3. Test circuit with ERA-5SM

A test circuit has been built (p.1 attachment #1) on a single sided prototype board. 

First, the transfer function was measured with FFD-100. With the bias 100V (max) the -3dB bandwidth of ~200MHz was observed.
This decreases down to 75MHz if the bias is 25V, which is the voltage supplied by the aLIGO BBPD circuit. The transimpedance
at the plateau was ~400Ohm.

Next, S3399 was tested with the circuit. With the bias 25V and 30V (max) the -3dB bandwidth of ~200MHz was obtained although
the responsivity of S3399 (i.e. A/W) at 1064nm is about factor of 2 smaller than that of FFD-100.

The noise levels were measured. There are many sprious peaks (possibly by unideal hand made board and insufficient power supply bypassing?).
Othewise, the floor level shows 0.7mA shotnoise level.

Attachment 1: PD_response.pdf
PD_response.pdf PD_response.pdf PD_response.pdf PD_response.pdf
Attachment 2: FFD-100_AP389_MCL.pdf
FFD-100_AP389_MCL.pdf
  4650   Fri May 6 06:36:18 2011 SureshUpdateRF SystemPD DC signals at each port connected

We now have the DC signal from three PDs available in the ADC channels 14,15 and 16.  The signals are from  REFL55, AS55 and POY photodiodes respectively.  As the DC signals on all the other PDs of the same port (REFL, AS and PO)  have the same information we do not need to monitor more than one DC PD at each port.

The LSC PD Interface Card, D990543 - Rev B, can take 4 PDs and provides the DC signals of the PDs on the connector P2 (the lower of the two) on the back plane of the chassis. An adaptor card, D010005-00, plugs into the back plane from the rear of the Eurorack and provides the four DC signals on two-pin lemo sockets.

I have connected the three DC signals from the relevant RF PDs (above) to a DC whitening filter, D990694-B-1 which is associated with the channels 9 to 16 of the ADC card.

The cables are in a bit of a mess right now as some of the PD power supply lines are too short to reach up the the Interface card in the top Eurocart. Steve and I plan to redo some of the cabling later today

 

 


 

  4651   Fri May 6 10:20:00 2011 steveSummarySAFETY2011 safety audit

The emphasis of this annual safety audit  was on  safe  electrical housekeeping on March 3, 2011

Safety audit correction list for the electric shop:

1, install breaker panel door in room 101
2, install conduit- AC out let in the east arm for USB camera table and
    south arm for maglev- external fan
3, replace AC cord to south end work bench and door alarm
4, trace breaker of 1Y4

Requested completion date: 3-28-2011 at estimated cost $1,500.
 
All recommendations  for improvement were done by April 1, 2011
 
We thank the participants for making the 40m a safer  place to work.
 
 
 
 
Attachment 1: sa2011done1.pdf
sa2011done1.pdf
Attachment 2: P1070448.JPG
P1070448.JPG
  4652   Fri May 6 14:59:36 2011 Leo SingerConfigurationSUSTuning ITMY bandstop

I tuned the ITMY bandstops -- 'before' and 'after' spectra attached.  Note that the after the tuning, the bounce mode at ~16 Hz is about twice as quiet!

 

However, notice that in the 'before' plot the roll mode at about 23.5 Hz did not show up at all, whereas it is quite prominent in the 'after' plot.  I was concerned that this line could have been a result of placing the bandstop there, so I made another plot with the BounceRoll filter turned off.  Sure enough, the 23.5 Hz line is still there.  So I'm not crazy: the roll mode did start acting up at some time between my 'before' and 'after' plot, but not as a result of the tuning.

Attachment 1: itmy-before.pdf
itmy-before.pdf
Attachment 2: itmy-after.pdf
itmy-after.pdf
Attachment 3: itmy-nobounceroll.pdf
itmy-nobounceroll.pdf
  4653   Fri May 6 15:42:55 2011 valeraMetaphysicsIOOInput mode cleaner length and 11 MHz modulation frequency

 After Kiwamu set the REFL11 phases in the PRMI configuration (maximized PRM->REFL11I reesponse) I tried to measure the MC length and the 11 MHz frequency missmatch by modulating the 11 MHz frequency and measuring the PM to AM conversion after the MC using the REFL11Q signal. The modulation appears in the REFL11Q with a good snr but the amplitude does not seem to go through a clear minimum as the 11 MHz goes through the MC resonance.

We could not relock the PRMI during the day so I resorted to a weaker method - measuring the amplitude of the 11 MHz sideband in the MC reflection (RF PD mon output on the demod board) with a RF spectrum analyzer. The minimum frequency on the IFR is 11.065650 MHz while the nominal setting was 11.065000 MHz. The sensitivity of this method is about 50 Hz.

  4654   Fri May 6 15:59:40 2011 steveUpdateVACTP3 fore pump replaced

Dry fore pump of TP3 replaced by brand new Varian SH-110  at  1.1 Torr_75,208 hrs

The annuloses were closed off for 25 minutes. We are back to VACUUM NORMAL mode.

The TP3 fore line pressure dropped to 44 mTorr at 25 minutes in operation.......9.4mTorr at day 2 with full annulos load

  4655   Fri May 6 17:11:55 2011 steveUpdateSUSSRM-oplev cable

The SRM qpd cable was removed from the BS-table. It's path was changed from 1x4 to ITMY-table following the inner cable tray.

  4656   Sat May 7 02:52:53 2011 kiwamuUpdateLSCTRY photo diode installed

[Suresh / Kiwamu]

 We installed the TRY photo diode (Thorlabs one) and the ETMYT CCD camera in place on the ETMY table.

Now we can see a signal on the TRY digital channel.

It will be quite useful for the Y arm locking, for instance we can do a triggered locking and the maximization of the intracavity power.

Someone has to install the EMTY trans QPD at some point.

  4657   Sat May 7 10:59:11 2011 SureshUpdateRF SystemRF Source filters changed

 

The SLP-50 filters which were on the 55 MHz lines have been replaced with the SBP-60.  Their respective characteristics are given below:

 

at 55MHz Insertion loss (dB) Return Loss (dB)
SLP-50 4.65 1.5
SBP-60 1.36 23

 

SBP-60 has lower insertion loss and higher return loss.  

This may however change the phase of I and Q in the demod boards and they will therefore need to be readjusted.  Currently the output power level of 55 MHz demod is at 2dBm, whereas it ought to be at 6dBm.   I have not yet corrected that.  Once that is completed Kiwamu will adjust the phases.

 I shifted the temperature sensor to a new location.  See the photograph below.  I noticed that the higher temperature is reached on the side where there are two RF Amps.  So it would be better to check the temperature of that  area and make sure that it remains well below 65 deg.  The operating maxium is 65deg C

 

Here is a picture of the new RF source layout.

RF_Source_Schematic.png

And here is a photograph of it

RF_Source.jpg

 

  4658   Sat May 7 12:57:54 2011 KojiSummaryGeneralaLIGO BBPD / Green PD investigation

The RF amplifier of the prototype BBPD has been replaced from ERA-5SM to MAR-6SM.
The bandwidth is kept (~200MHz for S3399 with 30V_bias), and the noise level got better
while the maximum handling power was reduced.

MAR-6SM is a monolithic amplifier from Minicircuits. It is similar to ERA-5SM but has lower noise
and the lower output power.


AP389 ERA-5 MAR-6
Freq Range 10-250MHz DC-4GHz DC-2GHz
Gain >24.5dB 20dBtyp 21.8dBtyp
Output power (1dB comp.)
+23dBm +18.4dBm +3.7dBm
IP3 36dBm 33dBm 18.1dBm
Noise Figure <3.3dB 3.5dB 2.3dB

The noise floor corresponds to the shotnoise of the 0.4mA DC current.
Now the mess below 50MHz and between 90-110MHz should be cleaned up.
They are consistently present no matter how I change the PD/RF amp (ERA<->MAR)/bias voltage.

I should test the circuit with a different board and enhanced power/bias supply bypassing.


Discussion on the RF power (with M. Evans)

- Assume 5mA is the maximum RF (~50mW for 1064nm, ~15mW for 532nm). This is already plenty in terms of the amount of the light.

- 100% intenisty modulation for 5mA across 50Ohm induces -2dBm RF power input for the amplifier.

- Assume if we use MAR-6 for the preamplifier. The max input power is about -18dBm.
  This corresponds to 16% intensity modulation. It may be OK, if we have too strong intensity modulation, we can limit the power
  down to 0.8mA in the worst case. The shot noise will still be above the noise level.

- In the most of the applications, the RF power is rather small. (i.e. 40m green beat note would expected to be -31dBm on the RF amp input at the higherst, -50dBm in practice)
So probably we need more gain. If we can add 10-12dB more gain, that would be useful.

- What is the requirement for the power amplifier?

  • Gain: 10~12dB
  • Output (1dBcomp): +3dBm +Gain (13dBm~15dBm)
  • Noise level / Noise Figure: 3nV/rtHz or NF=14dB
    The output of MAR-6 has the votage level of ~7nV/rtHz. If we bring the power amplifier with input noise of ~3nV/rtHz,
    we can surppress the degradation of the input equivalent noise to the level of 10%. This corresponds to N.F. of 14dB.

Search result for Freq Range 10-200MHz / Max Gain 14dB / Max NF 15dB / Min Power Out 13dBm
GVA-81 is available at the 40m. ERA-4SM, ERA-6SM, HELA-10D are available at Downs.

Model Name Frequency [MHz] DC Power Case Style Price
[$]
Low High Current [mA] Volt [V]
SORT
 
ERA-4 DC 4000 65 4.5 VV105
ERA-4SM DC 4000 65 4.5 WW107
ERA-4XSM DC 4000 65 4.5 WW107
ERA-6 DC 4000 70 5 VV105
ERA-6SM DC 4000 70 5 WW107
GALI-6 DC 4000 70 5 DF782
GVA-81+ DC 7000 112 5 DF782
HELA-10C 5 450 525 12 CM624
HELA-10D 8 300 525 12 CM624

GVA-81 ERA-4SM ERA-6SM GALI-6
Freq Range DC-6GHz DC-4GHz DC-4GHz DC-4GHz
Gain 10.5dB 13.7dB 12.6dB 12.2dB
Output power (1dB comp.)
+19dBm +17.5dBm +17.1dBm +18.2dBm
IP3 42dBm 36dBm 36.5dBm 35.5dBm
Noise Figure 7.3dB 4dB 4.4dB 4.5dB

 


Conversion between nV/rtHz and NF (in the 50Ohm system)

SN1: Connect signal source (50Ohm output) to a 50Ohm load.
Power ratio between the noise and the signal

SN1 = (4 k T (R/2)) / (S/2)^2

SN2: Connect signal source (50Ohm output) to an RF amp.
Only the voltage noise was considered.

SN2 = (4 k T (R/2) + Vn^2) / (S/2)^2

10 Log10(SN2/SN1) = 10. Log10(1 + 2.42 (Vn / 1nVrtHz)^2)

e.g.
Vn: 0 nVrtHz ==> 0dB
Vn: 0.5 nVrtHz ==> 2dB
Vn: 1 nVrtHz ==> 5dB
Vn: 2 nVrtHz ==> 10dB
Vn: 3 nVrtHz ==> 13.5dB

Attachment 1: PD_response.pdf
PD_response.pdf PD_response.pdf PD_response.pdf
  4659   Sat May 7 18:08:54 2011 valeraUpdateIOOMC beam spot centering script

I tried to run the scripts/senseMCdecentering to check the centering of the MC beam spots on the mirrors. The script (csh) produces a lot of error messages on the control room machines. They are machine dependent combination of "epicsThreadOnce0sd epicsMutexLock failed", "Segmentation fault", "FATAL: exception not rethrown". Most of ezcawrite commands fail but not all(?). After running the mcassUp script couple of times all the dither lines came on. The MCL responses to dither lines look qualitatively similar to what it was in February (plot attached). The overall MCL spectrum looks ~100 times lower, presumably due to the analog gain reallocation.

Before that I realigned the beam into the PMC, recentered the PSL QPDs, and the beam into the MC to bring the MC RFPD_DC from ~3 to ~1.5 VDC then tweaked MC2 to bring the MC RFPD_DC from ~1.5 to ~1 VDC.

The mcass dither lines are off now and the loops are disabled.

Attachment 1: mcditherlines2.pdf
mcditherlines2.pdf
  4660   Sun May 8 16:32:52 2011 valeraUpdateIOOMC beam spot centering

 Kiwamu told me that the CDS matrix notation has changed and the 40m front end code has changed since February. I changed the senseMCdecentering script to reflect that. The other problems were: the "-" sign in ezcastep on ubuntu is not recognized - I used the known workaround of using "+-" instead; the echo command in csh script on ubuntu does not make a new line - but the echo " " does. The script ran on ubuntu with one error message "FATAL: exception not rethrown" but it finished nevertheless. The data appeared ok.  On centos machine the script produced "Segmentation fault'. The matlab script sensemcass.m now calculates the position on the MC mirrors in mm. The attached table shows the MC spot positions in mm:

    feb 26 2011      may 08 2011
MC1 pit   1.6   1.9
MC2 pit   6.4   9.0
MC3 pit   1.4   2.0
MC1 yaw   -1.5   -1.7
MC2 yaw   1.0   0.2
MC3 yaw   -1.3   -1.9

I had to rephase the lockin digital phases by tens of degrees. I don't know why this should happen at ~10 Hz.

 

  4661   Sun May 8 17:29:01 2011 ranaUpdateIOOMC beam spot centering

It seems like the best option would be to make the MCASS just adjust the SUS biases and center the beams on the suspended optics. Is this not possible somehow?

  4662   Sun May 8 22:59:40 2011 ranaUpdatePSLPSL reference cavity temperature box modifications

I looked at the PSL temperature box. It started out as D980400-B-C. Then it was revised by Peter King as per the LHO mods E020247.

There are some more things to do to it to make it useful for us:

  1. R3, 4, 7, 8, 12, & 13 should be changed from 1k to 0 Ohms, I think. I cannot figure out their purpose.
  2. All resistors should be made metal-film. Right now, its kind of a mish-mash.
  3. The active filter U6B has a corner frequency of ~50 Hz. This seems not useful for keeping the 4116 DAC noise out of the temperature. We should lower this to ~30 mHz to take advantage of the stability of the LT1021 which was put in.

** Frank reminds me that we don't use the TIdal or VME external inputs anymore since we moved to the EPICS/Perl PID control. So all we have to do is make sure these inputs are hardware disabled/disconnected.

  4663   Mon May 9 09:37:51 2011 valeraUpdatePSLPSL and MC trends

The attached plot shows 7 day trends of the MC and PMC power levels, PSL QPDs, and temperature. The MC stayed locked for ~40 hours over the weekend. The temperature swings were somewhat smaller over the past couple of days but one should remember to turn the PSL HEPA down after working on the table. Steve turned the HEPA flow from 100% down to 20% on Thursday and posted the reminder signs on the PSL enclosure.

Attachment 1: pslmcdrift2.pdf
pslmcdrift2.pdf
  4664   Mon May 9 12:33:40 2011 kiwamuUpdateLSCC1:LSC-TRIG_MTRX : wrong matrix size

I found that C1:LSC-TRIG_MTRX has a wrong matrix size. It needs to be fixed.

It is designed to have a 11x8 matrix in the simlink model file, but it's been compiled as a 6x8 matrix.

I recompiled c1lsc but it didn't fix the issue. Here below is the matrix statement in the C file :c1lsc.c. Indeed it is 6x8 matrix ....

// MuxMatrix:  LSC_TRIG_MTRX
for(ii=0;ii<8;ii++)
{
  lsc_trig_mtrx[ii] =
          pLocalEpics->lsc.LSC_TRIG_MTRX[ii][0] * lsc_imux_trigger[0] +
          pLocalEpics->lsc.LSC_TRIG_MTRX[ii][1] * lsc_imux_trigger[1] +
          pLocalEpics->lsc.LSC_TRIG_MTRX[ii][2] * lsc_imux_trigger[2] +
          pLocalEpics->lsc.LSC_TRIG_MTRX[ii][3] * lsc_imux_trigger[3] +
          pLocalEpics->lsc.LSC_TRIG_MTRX[ii][4] * lsc_imux_trigger[4] +
          pLocalEpics->lsc.LSC_TRIG_MTRX[ii][5] * lsc_imux_trigger[5];
 }

  4665   Mon May 9 13:14:48 2011 josephbUpdateLSCC1:LSC-TRIG_MTRX : wrong matrix size

[Joe, Kiwamu]

There is a feature/bug of the RCG code that you can only have 1 receiving tag for every sending tag.  There were 5 tags which were being received by two tags each, for two different matrices.  Only the first tag was receiving, the second was apparently ignored.

This has been fixed temporarily by putting in direct lines in place of these 5 tags.

Quote:

I found that C1:LSC-TRIG_MTRX has a wrong matrix size. It needs to be fixed.

It is designed to have a 11x8 matrix in the simlink model file, but it's been compiled as a 6x8 matrix.

 

  4666   Mon May 9 15:21:36 2011 josephbUpdatePSLFixed channel names for PSL QPDs, fixed saturation, changed signs

[Valera, Joe]

Software Changes:

First we changed all the C1:IOO-QPD_*_* channels to C1:PSL-QPD_*_* channels in the /cvs/cds/caltech/target/c1iool0/c1ioo.db file, as well as the /opt/rtcds/caltech/c1/chans/daq/C0EDCU.ini file.  We then rebooted the frame builder via "telnet fb 8087" and then "shutdown".

This change breaks continuity for these channels prior to today.

The C1:PSL-QPD_POS_HOR and C1:PSL-QPD_POS_VERT channels were found to be backwards as well.  So we modified the /cvs/cds/caltech/target/c1iool0/c1ioo.db file to switch them.

Lastly, we changed the ASLO and AOFF values for the C1:PSL-QPD_POS_SUM and the C1:PSL-QPD_ANG_SUM so as to provide positive numbers.  This was done by flipping the sign for each entry.

ASLO went from 0.004883 to -0.004883, and AOFF when from -10 to 10 for both channels.

Hardware Changes:

The C1:PSL-QPD_ANG_SUM channel had been saturated at -10V.  Valera reduced the power on the QPD to drop it to about 4V by placing an ND attenuator in the ANG QPD path.

  4667   Mon May 9 16:12:49 2011 JamieConfigurationCDScanonicalize paths to core and userapps

I have updated the /opt/rtcds paths to reflect the new specification of the CDS aLIGO code release procedures document.


Path to RTS/opt/rtcds/caltech/c1/core/release

This is where the advLigoRTS front-end code generator is checked out.  The "release" directory is a link to the svn branch from which we are currently running ("trunk" by default).

This used to be at /opt/rtcds/caltech/c1/core/advLigoRTS


Path to userapps: /opt/rtcds/caltech/c1/userapps/release

This is where the cds_user_apps code is checked out.  cds_user_apps is where all of the front-end models, medm screen, scripts, etc. will live.  The "release" directory is a link to the svn branch from which we are currently running ("trunk" by default).

This was most recently at /opt/rtcds/cds_user_apps

 

  4668   Mon May 9 16:58:23 2011 JamieBureaucracyCDS!!!!REMEMBER TO COMMIT YOUR MODIFICATIONS!!!!

Whenever you modify any of the front-end code in /opt/rtds/caltech/c1/userapps, such as models, scripts or medm screens, REMEMBER TO COMMIT YOUR CHANGES, WITH A LOG MESSAGE!!!

cd /opt/rtcds/caltech/c1/userapps/trunk
svn commit path/to/modified/file

If you forget to commit things, they may be purged and you will loose your work.  ALWAYS COMMIT!

Things to note and watch out for:

  • When you commit, make sure you specify explicitly the path to the file that you are committing.  This repository is shared by all LIGO sites, including the sites (LHO and LLO) so you really want to make sure you're not committing anything that affects anything other than "c1" (ie. the 40m)
  • Only commit one file at a time, unless the changes to multiple files are tightly coupled.
  • Never commit without specifying the path to the file that you are committing.  Other people may be working on other files in the repository, and you don't want to commit their work with yours.
  • YOU MUST LEAVE A LOG MESSAGE.  Your log message should be specific to the file you have modified, and should be clear and verbose to explain exactly what you have done.
  • Use the "svn status" command to give you an overview of what is going on in the working directory.  This will tell you which files have been modified.  See "svn help status" for more information.

If you have questions ASK.  Don't force things.

  4669   Mon May 9 17:21:13 2011 JamieBureaucracyCDS!!!!REMEMBER TO COMMIT YOUR MODIFICATIONS!!!!

Also, remember to update the svn working copy before you begin doing any work, to make sure you're working on the most recent version:

cd /opt/rtcds/caltech/c1/userapps/trunk
svn update
  4670   Mon May 9 17:23:25 2011 SureshUpdateRF SystemRF Cables near LSC Rack

[Steve, Suresh]

We started to clean up the RF cables (heliax and PD interface cables)  at the LSC rack.

We have pulled out all the RF cables from the small hole on the side-board close to floor.  Passing the cables through this hole makes some of the cables much too short for good strain relief.  So we removed the side panel on the vacuum tube side and are going to pass the cables into the rack from there at about waist height.  We now have plenty of cable lengths to tie them off to the rack at several points.

We have traced all the available Heliax cables and have attached blank tags to them.  We have allocated some cables to REFL11, REFL55 and AS55.  These are therefore back in working order.  We have also taken stock of the available PD interface cables.  They do not have consistent names on both ends of the cable and we will identify and label the ends tomorrow.

MC is locked.  The auto-locker works fine.

Handing over the system for night time interferometer work now.  Will continue with the cabling tomorrow.

 

  4671   Mon May 9 18:54:29 2011 kiwamuUpdateLSCtriggerd locking logic : screen prepared

I made a new medm screen for the triggering logics. Have fun.

I put a button on C1LSC.adl to invoke this screen.

trigger_medm.png

Quote from #4656

It will be quite useful for the Y arm locking, for instance we can do a triggered locking and the maximization of the intracavity power.

 

  4672   Mon May 9 20:30:20 2011 ranaUpdatePSLPSL reference cavity temperature box modifications

I re-installed the box (@ ~8:15) after reflowing some of the solder joints. I will observe it over night and then remove the 1K resistors. Attached is a 8 hour minute-trend.

Attachment 1: Untitled.png
Untitled.png
  4673   Tue May 10 00:31:28 2011 kiwamuUpdateASCIFO alignment plan

The alignment of the interferometer goes basically step by step.

Tuesday will be an alignment day.

  0. MC beam centering (it's done)

  1. F2P to balance the coils on every optics including BS, PRM, SRM, ITMs and ETMs (Kiwamu).

  2. A2L and then change the DC bias of ITMY and ETMY to get a perfect eigen axis (VF/Jamie).

  3. align input PZT mirrors (PZT1 and 2) to maximize the Y arm transmission (VF/Jamie).

  4. do the same things for X arm but using BS instead of the PZTs.

  5. Alignment of the central part.

  6. Make a script to automatically get those things done. 

  4674   Tue May 10 00:44:52 2011 valeraUpdateIOOMC2 centering

Kiwamu, Koji, Valera

We centered the beam on MC2 in pitch by moving the MC1,2,3 in the following combination [-9,+3,-7]. This actuation vector mostly moves the spot on MC2 vertically. The attached plot shows the dither before and after the centering. We monitored the demodulated signals and saw the reduction of the MC2 pit response from -1.0 to -0.22 which corresponds to the beam spot position change from 9 to 2 mm. Thus all the spots on MC mirrors are within 2 mm of the center. We estimate based on the distance between the MC1-MC3 of 20 cm, the distance from the center between MC1 and MC3 to the end of the Faraday isolator of 80 cm, and the aperture of the FI of 12 mm, the maximum angle out of MC of 3/200 rad. Which implies the maximum differential spot motion of 3 mm not to be limited by the FI aperture.

Attachment 1: mc2centering.pdf
mc2centering.pdf
  4675   Tue May 10 01:39:41 2011 SureshUpdateRF SystemRF source troubles

Today after Steve and I finished the RF cabling work for the day, Kiwamu noticed that there were no RF signals to be seen.  The problem was traced to disconnected 11 and 55 MHz Demod lines from the RF source.  But reconnecting them did not restore the signals.  It turned out that one of the Heliax cables had a loose N-type connector at its end and it finally came off while we were tightening it into place.

We replaced the damaged heliax with another (we have two spare running from 1X2 IOO rack to the 1Y2 LSC rack.  The new cable is used to be the LO 33.  It seems to have a 1.5dB loss.  Have to check this again tomorrow.

In the mean time I noticed that the power output of the 55MHz Demod port of the source was less than about -12dB. So I opened the source to take a look and found that all the voltage stabilisers were supplying 15V.  Even those which were supposed to be supplying 24V.  This was traced to a mistake in wiring the external power supply.  The wires had been labeled wrongly and as a result the 18V input line was connected to 28V source and vice versa.

After fixing this problem I reassembled the source checked the power output on all the ports and found everything was functioning as expected.  However after installation once again the unit failed.  The blue light on the power supply was not lighting up when switched on.  Suspecting a power supply problem I opened the unit again and found that a weak solder joint on one of the RF amplifiers had come loose and had overloaded one of the 24V stabilisers.   We, found a spare and replaced it.  The unit has been reassembled and is functioning fine.  The output power levels are

11MHz Demod -- 6dBm

55MHz Demod -- 5.5 dBm

11MHz EOM --   24dBm

55MHz EOM -- 28dBm

The Marconi is serving as the 11MHz source.  The Wenzel 11MHz source is giving 13.3 dBm and is okay.  But it needs to be checked for its performance as it may have been exposed to higher than rated power supply levels.

The 29.5MHz source is giving 7dBm.  It is supposed to be giving 13dBm. 

The Laboratory DC power supplies currently used for both the RF source and Distribution boxes need to be replaced with rack mounted Sorensen power supplies available in the lab.

 

  4676   Tue May 10 09:05:49 2011 KojiUpdateGeneralaLIGO BBPD / Green PD investigation

BBPD update

- The BBPD circuit has been constructed on the aLIGO BBPD board

- It still keeps 200MHz BW with FDD-100 Si PD for the 100V bias.

- The noise spectrum has been cleaned up a lot more. It shows the noise level of the 0.4mA shotnoise between 9-85MHz.
The noise at 160MHz is the noise level of the 1mA shotnoise.

Some of the noise peaks at around 97MHz came from the bias voltage.

What to do next

- Confirmation of the performance with the original aLIGO BB PD configuration.

- Notch filter for 9MHz (for aLIGO).

- Implementation of a power amplifier. (issues: power supply and heat removal)

Attachment 1: PD_response.pdf
PD_response.pdf PD_response.pdf PD_response.pdf
  4677   Tue May 10 10:06:23 2011 josephbUpdatePSLFixed channel names for PSL QPDs, fixed saturation, changed signs

I added calculation entries to the /cvs/cds/caltech/target/c1iool0/c1ioo.db file which are named C1:IOO-QPD_*_*, as the channels were originally named.  These calculation channels have the identical data to the C1:PSL-QPD_*_* channels.  I then added the channels to the C0EDCU.ini file, so as to once again have continuity for the channels, in addition to having the newer, better named channels.

The c1iool0 machine ("telnet c1iool0", "reboot") and the framebuilder process ("telnet fb 8087", "shutdown") were both restarted after these changes.

These channels were brought up in dataviewer and compared.  The approriate channels were identical.

Quote:

[Valera, Joe]

Software Changes:

First we changed all the C1:IOO-QPD_*_* channels to C1:PSL-QPD_*_* channels in the /cvs/cds/caltech/target/c1iool0/c1ioo.db file, as well as the /opt/rtcds/caltech/c1/chans/daq/C0EDCU.ini file.  We then rebooted the frame builder via "telnet fb 8087" and then "shutdown".

This change breaks continuity for these channels prior to today.

 

  4678   Tue May 10 11:14:44 2011 steveUpdatePSLPSL-QPD_ANG qpd optimized

Valera and I placed F 572.7 mm lens ~15 cm away  from the ang  qpd (in the same mount with ND filter) so that two qpds see different combination of ang and pos motion - there was no lenses prior to this change. The beam diameter is reduced to ~half .

Attachment 1: qpdangl.jpg
qpdangl.jpg
  4679   Tue May 10 16:42:49 2011 josephbUpdateCDSNew upconversion model (c1uct)

[Ryan, Joe]

Ryan added the c1uct (upconversion tester) model to the c1ioo machine.   It is DCU_ID 32, CPU 6.  The relevant wiki page has been updated. It has been added to /diskless/root/etc/rtsystab on the fb machine and automatically comes up when the c1ioo computer is turned on. 

Joe still needs to add its status to the status screen.

It is soft linked from:

/opt/rtcds/caltech/c1/userapps/trunk/CDS/c1/models/c1uct.mdl

Ryan will expand upon its uses later.

  4680   Tue May 10 16:45:19 2011 josephbUpdateCDSc1ass now receiving AS55I from c1lsc

[Valera, Joe]

We added a cdsPCIx_SHMEM connection between the c1lsc and c1ass models.  This connection is called C1:LSC-ASS_AS55I, and sends the normalized AS55I data to Lockin 11 of the c1ass model.

In addition, in order to get the c1ass model to compile, we had to place all the non-IO parts inside a subsystem block, which we called ASS, and gave the top_names tag to.

The c1lsc and c1ass models were rebuilt, the frame builder restarted, and the models restarted.

  4681   Tue May 10 20:57:05 2011 ranaUpdatePSLPSL reference cavity temperature box modifications : after 24 hours still OK

Quote:

I re-installed the box (@ ~8:15) after reflowing some of the solder joints. I will observe it over night and then remove the 1K resistors. Attached is a 8 hour minute-trend.

 I compared this 24 hour trend with the one from this day exactly one year ago. Seems the same, so now I can make the resistor change.

Attachment 1: Untitled.png
Untitled.png
  4682   Tue May 10 22:56:17 2011 kiwamuUpdateSUSf2p filters installed on ETMY

New f2p filters were installed on ETMY. 

The statistical error of the coil gain settings are now about 0.8% at high frequency (i.e. above the resonant freq of the pendulum mode)

 What I did :

 -   measured and corrected the coil imbalances on ETMY using a script called F2P_LOCKIN.py

 -   made the new f2p filters based on the measurements and installed them.

  Next step :

 -  do the same adjustment for all the suspensions including PRM, SRM, BS, ITMs and ETMs

 


(Notes on F2P_LOCKIN.py)

 F2P_LOCKIN.py is a script that I've made in python. This is basically the same as the old script, f2pratio, but uses the realtime LOCKINs instead of ezcademods.

The script automatically measures the coil imbalances on an optics of interest by driving the local LOCKIN oscillators.

In the first step the script automatically balances the coil gains at high frequency (8.5Hz).

In the next step it gives some coefficients, which basically represent the coil imbalances at low frequency (0.01Hz)

Then with those coefficients one will be able to design the f2p filters.

It is not well polished yet, so I will spend some more times to make it user-friendly and readable.

Example usage : F2P_LCKIN.py -o ETMX

It currently resides in /cvs/cds/rtcds/caltech/c1/scriptss/SUS/

 

(new f2p filters)

The plot below shows the new f2p filters. Note that they are already installed.

f2p_etmy.png

Pendulum mode = 0.982 Hz (according to the wiki)
Q of the pendulum mode = 1 (to avoid ringing of IIR filters)
C1:SUS-ETMY_ULCOIL_GAIN = -0.793435
C1:SUS-ETMY_URCOIL_GAIN = 1.16877
C1:SUS-ETMY_LLCOIL_GAIN = 1.25028
C1:SUS-ETMY_LRCOIL_GAIN = -0.730704
UL_fz = 0.965125
UR_fz = 1.029517
LL_fz = 0.934231
LR_fz = 0.996562
UL_Qz = 0.982816
UR_Qz = 1.048388
LL_Qz = 0.951356
LR_Qz = 1.014829
  4683   Tue May 10 23:14:01 2011 kiwamuUpdateSUSETMX_OPLEV : He-Ne laser dead ?

I found that a He-Ne laser which has been used for ETMX_OPLEV was NOT giving the light.

Since I didn't find the switch key for it I have no idea if the laser is simply off or dead.

  4684   Wed May 11 00:23:21 2011 kiwamuUpdateASCY arm and beam pointing alignment

[Jamie / Valera / Kiwamu]

 The incident beam pointing was improved a lot by using C1ASS realtime code.

Some more details will be posted later. The below is the list of the highlights today.

 - The Y arm cavity was aligned to have good beam centering on the mirrors.

 - The input PZTs were also aligned to the aligned Y arm by hand.

 - Automation of the  Y arm alignment using C1ASS_LOCKIN got partially functional with two loops closed. C1ASS correctly servos the centering on ETMY

 - The amount of the off-centering on ITMY and ETMY look roughly within 1 mm.

 - As a result the intracavity power got bigger by a factor of about 3.5

  4685   Wed May 11 10:49:16 2011 valeraConfigurationElectronicsMC3 LL PD has no signal

Yesterday we found that MC3 OSEM LL PD did not have a sensible signal - the readback was close to zero and it was making MC move around. I disabled the PD LL so that the damping is done with just three face plus side PDs. There still no signal from MC3 LL PD today. It needs debugging.

  4686   Wed May 11 11:05:45 2011 steveUpdateSUSETMX_OPLEV : He-Ne replaced

Quote:

I found that a He-Ne laser which has been used for ETMX_OPLEV was NOT giving the light.

Since I didn't find the switch key for it I have no idea if the laser is simply off or dead.

 The dead laser was replaced by new JDSU 1103P of  2.6mW. The return beam is big ~5 mm diameter of 0.3 mW,  1400 counts

Attachment 1: P1070672.JPG
P1070672.JPG
ELOG V3.1.3-