40m QIL Cryo_Lab CTN SUS_Lab CAML OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 79 of 355  Not logged in ELOG logo
ID Date Author Typeup Category Subject
  17861   Wed Sep 20 14:04:58 2023 RadhikaSummaryElectronicsVertex Electronics ~ change in the actuator calibration

MC1/MC2/MC3 damping restored

I tweaked the coil actuation gains for MC1/MC2/MC3 according to Koji's updated calculations:

1/9.6 for face coils
1/0.87 for side coils

With foton and load coefficients working as expected, these coil output filters were successfully added to MC2 and MC3.

Damping tests

Note: While burt restoring C1MCS to a pre-upgrade state, a "NOT OK" flag popped up and the coil balancing gains for MC1/MC2/MC3 were reset to +-1. Koji showed me how to access the original values in c1mcs.snap (using grep) and I restored the coil gains to their values from 9/12/2023.

- *Recall from past ELOG that MC1 OSEM input gains all switched from -1 ---> +1; and MC1 coil output gains changed signs from [-,-,-,-,-] ----> [+,-,+,-,+]. No changes were made to MC2 or MC3.*
- Turned on damping filters
- Gave an offset of 10000 cts to C1:SUS-MC1/2/3_ULCOIL_OFFSET. OSEM striptools can be found in Attachments 1,2,3.

Next steps

- Get BS/ITMX/ITMY/PRM/SRM online and apply new sensor/actuator scaling factors
- Confirm damping works as expected for above suspensions
- Bring IFO to nominal alignment
- Revisit upgraded suspensions and perform fine tuning (input matrix diagonalization, coil balancing)
  17862   Wed Sep 20 17:02:22 2023 RadhikaSummaryElectronicsVertex Electronics ~ change in the actuator calibration

[Paco, Radhika]

IMC LOCKED

We used the pre-upgrade C1:SUS-MC1/2/3_SUSPIT/YAW/POS_INMON values as a baseline to restore IMC alignment.

Procedure we followed:

1. Use MCR spot position to align MC1.
2. Move MC3 to try to hit OSEMs on MC2F. Note down these MC3 PIT/YAW offset values and navigate to their center to align MC3.
3. Now move MC2 to steer the beam back around the cavity and hit MC2 OSEMs once again. Alignment is very close! Continue to move until flashing is observed.
4. IMC autolocker kicks in; burt restore c1iooepics.snap to restore WFS.
  17863   Wed Sep 20 17:28:17 2023 RadhikaSummaryElectronicsre: Filter Coefficient Loading Issue

I noticed the same issue today with C1RMS.txt, when trying to update the coil actuation gains for SRM. The filter changes were saved to chans/C1RMS.txt, so next I checked chans/tmp/. There is no chans/tmp/C1RMS.txt, or chans/tmp/C1RMS.diff. The updated filters do not load.

Update from Chris:

C1RMS.txt is a remnant from some model that doesn't exist anymore. It can be removed.

I went ahead and deleted chans/C1RMS.txt and chans/tmp/C1RMS.txt.

  17864   Wed Sep 20 18:18:38 2023 KojiSummaryElectronicsVertex Electronics Wed Plan

[Koji, Murtaza, JC]

Regarding PRM/BS:

  • PRM2 cable and BS2 cable were wrongly connected. This was corrected.
     
  • This makes the BS face OSEM values reasonable.
    However, the side signal is still close to zero. We confirmed that the sat amp outputs (LED mon/PD mon/PD diff out) looked reasonable for all five BS OSEMs.
    The side signal issue stays downstream of the Vertex ADC adapter.

     
  • PRM2 has no issue with the sat amp.
  • PRM1: We found that all the LED mon goes down to 0.17V when the vacuum flange is connected.
    It was found that the reference voltage for the LED (TP11 of D080276) went down to low number (like 0.15V) when the in-vac OSEMs were connected.
    I found that this output was not stable. So, I replaced the U4 chip (AD8672), but this didn't help the voltage sagging issue.
  • Murtaza and I started checking the short circuits on the flange. We found that Pin 5 (OSEM PD1 Kathode) and Pin 1 (invac cable shield?) only have 5.1 Ohm. Pin 1 is connected to the vacuum chamber.
    • What does it mean? The PD has the reverse bias voltage of 10V applied on the PD Kathode. This bias voltage is shorted to ground via 5 Ohm. To keep the bias line at 10V, we need 2 A.
    • We don't have many options:
      - We can disconnect the internal wire for pin5 from the cable. (Prepare a ribbon cable). This should make the other OSEM PDs properly biased.
      We may be able to use an independent power supply to provide some amount of reverse bias (10V 2A is too much. Probably 1V 0.2A or 2.5V 0.5A?) so that the UL PD somewhat work.
  17866   Thu Sep 21 14:22:02 2023 RadhikaSummaryElectronicsVertex Electronics CDS Update

I recalculated the scale factors between OSEM sensor readings after/before the upgrade. The expected factor is 8.64, although we may want to rethink this if measurements are disagreeing.]

If ITMY can be restored, we can proceed to locking the YARM while PRM/ITMX/BS are worked on.
 

1. BS values seem reasonable

[UL: 7.52500126;  UR: 9.78603403;  LR: 10.80333519;  LL: 8.58031299;  SD: 4.90237845]

The SD reading is positive and nonzero, even though its still smaller than the face sensor readings by a factor of 2.
 

2. ITMX SD still negative

[UL: 12.76223943;  UR: 6.40189513;  LR: 8.52507381;  LL: 21.55229024;  SD: -7.9675249]


3. ITMY SD flipped from positive to negative ~3pm 9/21. LL is too small.

[UL: 5.21918023;  UR: 35.90315905;  LR: 19.1338805;  LL: 0.90731276;  SD: -3.68291338]


4. PRM still not reliable

[UL: -0.00064235;  UR: -0.00061758;  LR: -0.00154483;  LL: -0.00583698;  SD: -0.00283635]


5. SRM positive but scale factors widely inconsistent, order of magnitude greater than expected (~8.64).

[UL: 7.22499189;  UR: 3.36944117;  LR: 116.14296786;  LL: 114.59917629;  SD: 1.91497475]
  17867   Fri Sep 22 16:20:25 2023 RadhikaSummaryElectronicsVertex Electronics CDS Update

Today we tried to debug the unreasonable OSEM readings (see previous ELOG)

PRM process

Starting state: PRM face + side values bogus (~0)

1. Somehow through retightening connections, PRM LR+SD counts looked reasonable (and positive). Yay!

2. Toggled on and off the PRM SATAMP; removed Ch1-4 and Ch5-8 PRM inputs

    - Result: BS SD becomes negative when PRM SATAMP is on and Ch 5-8 cable is connected.

2. We disconnected the PRM SATAMP and plugged the PRM inputs into the SRM SATAMP. The SRM SATAMP output was routed to the PRM input on the SATAMP adapter.

    - Result: PRM UL/UR/LL readings still 0.

                 BS SD still negative when SRM SATAMP is turned on and Ch 5-8 from PRM are connected.

                   ---> SRM SATAMP gives same results as PRM SATAMP; PRM SATAMP likely not faulty.

3. Replaced PRM chamber connections with satellite test box for channels 1-4.

    - Result: reasonable PRM UL/UR/LL readings ---> Pin 5 shorting on chamber side is causing issues with Ch1-4.

ITMX - ITMY process

Starting state: ITMX SD counts negative, ITMY SD counts negative (depends on ITMX connection)
To test ITMX (SD negative since change), ITMY (SD negative dependent on ITMX)

 

 We first switched [ITMX, ITMY]  in the following sequence to get the following results (F = average face values, S = side value)(0 = OFF, 1 = ON)

- [0,0] -> ITMX[F,S] = [300, -5000] ITMY[F,S] = [0, -800]

- [1,0] -> ITMX[F,S] = [~, ~] ITMY[F,S] = [1000, -3000]

- [0,1] -> ITMX[F,S] = [-30, -3000] ITMY[F,S] = [~, ~]

- [1,1] -> ITMX[F,S] = [15000, -10000] ITMY[F,S] = [10000, -3000]

 

A separate test was done to test ITMX-ITMY coupling on ITMY-side

1. ITMX SAT AMP OFF -> ITMY SIDE GOOD 

2. ITMX SAT AMP ON (Ch 1-4, 5-8 DISCONNECTED) -> ITMY SIDE =/2

3. ITMX SAT AMP ON (Ch 1-4 CONNECTED) -> NO CHANGE FROM 2.

4. ITMX SAT AMP ON (Ch 1-4, 5-8 CONNECTED) -> SAME MAGNITUDE AS 2., FLIPS SIGN

 

To check if ITMX was faulty from the chamber end for the SIDE DOF, the satellite test box was used for CH 5-8

ITMY SIDE SIGN STILL NEGATIVE 

 

For the final sanity check for the effect of ITMX on ITMY side sign, we swapped the ITMX and SRM SAT AMPS ({front -> PD OUT 1, 2}, {back -> Ch 1-4, Ch 5-8})

ITMY SIDE SIGN STILL NEGATIVE 

 

Summary

PRM Ch1-4 shorting issue on chamber side (UL/UR/LL)

BS/ITMY/ITMX SD <0 all seem to be caused by SATAMP adapter or downsteam in ADC2

SUSPECTED FAULTY SAT AMP ADAPTER for ITMX-ITMY SIDE COUPLNG

  17868   Fri Sep 22 18:26:08 2023 RadhikaSummaryElectronicsVertex Electronics CDS Update

[Koji, Radhika, Murtaza]

All upgraded suspensions have reasonable OSEM readings! Ready for damping tests and alignment next week.

We fixed PRM OSEM reading by isolating pin5 of the first DB25 [17871]. This makes the PRM UL unbiased by the PD seems to be receiving some light.

The PRM/BS/ITMX/ITMY SATAMP adapter was removed and the front-end pins were checked for shorting. Indeed, a short was found in the SIDE1-4 ribbon cable inside the sat-amp adapter, from the wires being compressed to one side of the dsub-ribbon adapter at the input joint [Attachment 1]. We reclamped the ribbon and verified there was no shorting and that the pins were properly aligned [Attachment 2]. This means PRM/BS and ITMX/ITMY SIDE signals should no longer be cross coupled.

All OSEM counts looked good after these fixes. Only a few ITMY OSEMS looked low, but Koji checked both PDMON voltages for ITMY, and we confirmed with calibration that the OSEM counts were reasonable.

  17871   Fri Sep 22 19:38:06 2023 MurtazaSummaryElectronicsVertex Electronics CDS Update

PRM CHANNEL 1-4 (BS FEEDTHROUGH 1-3)

[Koji, Radhika, Murtaza]

Connector on the BS Chamber that feeds to PRM UL/LL/UR coils (PRM 1 in Attachment 1) has pin 5 shorted to pin 1 inside the chamber angry
- To resolve this, a DB25 connector was recycled from the old coil drivers
- pin 5 was isolated by cutting (green cable on the DB25 connector)
- The connector was attached between the chamber and the cable that runs through to the rack (Attachment 1)
- The connector was labelled (Attachment 2)

The PD outputs were read on the PRM SATAMP (Pins 1-4, Pin 5 (Ground))
Pin 1 ~ 5.2V
Pin 2 ~ 5.3V
Pin 3 ~ 6.7V

Pin 4 ~ 0V (Blank Pin)

No need to apply an external bias to Pin 5!

Can be fixed during the next vent!

  60   Sun Nov 4 23:22:50 2007 waldmanUpdateOMCOMC PZT and driver response functions
I wrote a big long elog and then my browser hung up, so you get a less detailed entry. I used Pinkesh's calibration of the PZT (0.9 V/nm) to calibrate the PDH error signal, then took the following data on the PZT and PZT driver response functions.:

  • FIgure 1: PZT dither path. Most of the features in this plot are understood: There is a 2kHz high pass filter in the PZT drive which is otherwise flat. The resonance features above 5 kHz are believed to be the tombstones. I don't understand the extra motion from 1-2 kHz.
  • Figure 2: PZT dither path zoom in. Since I want to dither the PZT to get an error signal, it helps to know where to dither. The ADC Anti-aliasing filter is a 3rd order butterworth at 10 kHz, so I looked for nice flat places below 10 KHz and settled on 8 kHz as relatively harmless.
  • Figure 3: PZT LSC path. This path has got a 1^2:10^2 de-whitening stage in the hardware which hasn't been digitally compensated for. You can see its effect between 10 and 40 Hz. The LSC path also has a 160 Hz low path which is visible causing a 1/f between 200 and 500 Hz. I have no idea what the 1 kHz resonant feature is, though I am inclined to point to the PDH loop since that is pretty close to the UGF and there is much gain peaking at that frequency.
  61   Sun Nov 4 23:55:24 2007 ranaUpdateIOOFriday's In-Vac work
On Friday morning when closing up we noticed that we could not get the MC to flash any modes.
We tracked this down to a misalignment of MC3. Rob went in and noticed that the stops were
still touching. Even after backing those off the beam from MC3 was hitting the east edge of
the MC tube within 12" of MC3.

This implied a misalignment of MC of ~5 mrad which is quite
large. At the end our best guess is that either I didn't put the indicator blocks in the
right place or that the MC3 tower was not slid all the way back into place. Since there
is such a strong stickiness between the table and the base of the tower its easy to
imagine the tower was misplaced.

So we looked at the beam on MC2 and twisted the MC3 tower. This got the beam back onto the
MC2 cage and required ~1/3 if the MC3 bias range to get the beam onto the center. We used
a good technique of finding that accurately: put an IR card in front of MC2 and then look
in from the south viewport of the MC2 chamber to eyeball the spot relative to the OSEMs.

Hitting MC2 in the middle instantly got us multiple round trips of the beam so we decided
to close up. First thing Monday we will put on the MC1/MC3 access connector and then
pump down.


Its possible that the MC length has changed by ~1-2 mm. So we should remeasure the length
and see if we need to reset frequencies and rephase stuff.
  62   Mon Nov 5 07:29:35 2007 ranaUpdateIOOFriday's In-Vac work
Liyuan recently did some of his pencil beam scatterometer measurements measuring not the
BRDF but instead the total integrated power radiated from each surface point
of some of the spare small optics (e.g. MMT, MC1, etc.).

The results are here on the iLIGO Wiki.

So some of our loss might just be part of the coating.
  63   Mon Nov 5 14:44:39 2007 waldmanUpdateOMCPZT response functions and De-whitening
The PZT has two control paths: a DC coupled path with gain of 20, range of 0 to 300 V, and a pair of 1:10 whitening filters, and an AC path capacitively coupled to the PZT via a 0.1 uF cap through a 2nd order, 2 kHz high pass filter. There are two monitors for the PZT, a DC monitor which sniffs the DC directly with a gain of 0.02 and one which sniffs the dither input with a gain of 10.

There are two plots included below. The first measures the transfer function of the AC monitor / AC drive. It shows the expected 2 kHz 2d order filter and an AC gain of 100 dB, which seems a bit high but may be because of a filter I am forgetting. The high frequency rolloff is the AA and AI filters kicking in which are 3rd order butters at 10 kHz.

The second plot is the DC path. The two traces show the transfer function of DC monitor / DC drive with and with an Anti-dewhitening filter engaged in the DC drive. I fit the antidewhite using a least squares routine in matlab constrained to match 2 poles, 2 zeros, and a delay to the measured complex filter response. The resulting filter is (1.21, 0.72) : (12.61, 8.67) and the delay was f_pi = 912 Hz. The delay is a bit lower than expected for the f_pi = 3 kHz delay of the AA, AI, decimate combination, but not totally unreasonable. Without the delay, the filter is (1.3, 0.7) : (8.2, 13.2) - basically the same - so I use the results of the fit with delay. As you can see, the response of the combined digital AntiDW, analog DW path is flat to +/- 0.3 dB and +/- 3 degrees of phase.

Note the -44 dB of DC mon / DC drive is because the DC mon is calibrated in PZT Volts so the TF is PZT Volts / DAC cts. To calculate this value: there are (20 DAC V / 65536 DAC cts)* ( 20 PZT V / 1 DAC V) = -44.2 dB. Perfect!

I measured the high frequency response of the loop DC monitor / DC drive to be flat.
  68   Tue Nov 6 14:51:03 2007 tobin, robUpdateIOOMode cleaner length
Using the Ward-Fricke variant* of the Sigg-Frolov method, we found the length of the mode cleaner to be 27.0934020183 meters, a difference of -2.7mm from Andrey, Keita, and Rana's measurement on August 30th.

The updated RF frequencies are:
3  fsr =  33 195 439 Hz
12 fsr = 132 781 756 Hz
15 fsr = 165 977 195 Hz
18 fsr = 199 172 634 Hz
* We did the usual scheme of connecting a 20mVpp, 2 kHz sinusoid into MC AO. Instead of scanning the RF frequency by turning the dial on the 166 MHz signal generator ("marconi"), we connected a DAC channel into its external modulation port (set to 5000 Hz/volt FM deviation). We then scanned the RF frequency from the control room, minimizing the height of the 2 kHz line in LSC-PD11. In principle one could write a little dither servo to lock onto the 15fsr, but in practice simply cursoring the slider bar around while watching a dtt display worked just fine.
  69   Tue Nov 6 15:36:03 2007 robUpdateLSCXARM locked
Easily, after resetting the PSL Uniblitz shutters. There's no entry from David or Andrey about the recovery from last week's power outage, in which they could have indicated where the procedure was lacking/obscure. Tsk, tsk.
  76   Wed Nov 7 09:38:01 2007 steveUpdateVACrga scan
pd65-m-d2 at cc1 6e-6 torr
  81   Wed Nov 7 16:07:03 2007 steveUpdatePSLPSL & IOO trend
1.5 days of happy psl-ioo with litle bumps in C1:PSL-126MOPA_HTEMP
  82   Thu Nov 8 00:55:44 2007 pkpUpdateOMCSuspension tests
[Sam , Pinkesh]

We tried to measure the transfer functions of the 6 degrees of freedom in the OMS SUS. To our chagrin, we found that it was very hard to get the OSEMs to center and get a mean value of around 6000 counts. Somehow the left and top OSEMs were coupled and we tried to see if any of the OSEMs/suspension parts were touching each other. But there is still a significant coupling between the various OSEMs. In theory, the only OSEMS that are supposed to couple are [SIDE] , [LEFT, RIGHT] , [TOP1, TOP2 , TOP3] , since the motion along these 3 sets is orthogonal to the other sets. Thus an excitation along any one OSEM in a set should only couple with another OSEM in the same same set and not with the others. The graphs below were obtained by driving all the OSEMS one by one at 7 Hz and at 500 counts ( I still have to figure out how much that is in units of length). These graphs show that there is some sort of contact somewhere. I cant locate any physical contact at this point, although TOP2 is suspicious and we moved it a bit, but it seems to be hanging free now. This can also be caused by the stiff wire with the peek on it. This wire is very stiff and it can transmit motion from one degree of freedom to another quite easily. I also have a graph showing the transfer function of the longitudnal degree of freedom. I decided to do this first because it was simple and I had to only deal with SIDE, which seems to be decoupled from the other DOFs. This graph is similar to one Norna has for the longitudnal DOF transfer function, with the addition of a peak around 1.8 Hz. This I reckon could very be due to the wire, although it is hard to claim for certain. I am going to stop the measurement at this time and start a fresh high resolution spectrum and leave it running over night.

There is an extra peak in the high res spectrum that is disturbing.
  83   Thu Nov 8 11:40:21 2007 steveUpdatePEMparticle counts are up
I turned up the psl HEPA filter to 100%
This 4 days plot shows why
  87   Fri Nov 9 00:23:12 2007 pkpUpdateOMCX and Z resonances
I got a couple of resonance plots going for now. I am still having trouble getting the Y measurement going for some reason. I will investigate that tommorow. But for tonight and tommorow morning, here is some food for thought. I have attached the X and Z transfer functions below. I compared them to Norna's plots - so just writing out what I was thinking -

Keep in mind that these arent high res scans and have been inconviniently stopped at 0.5 Hz Frown.

Z case --

I see two small resonances and two large ones - the large ones are at 5.5 Hz and 0.55 Hz and the small ones at 9 Hz and 2 Hz respectively. In Norna's resonances, these features arent present. Secondly, the two large peaks in Norna's measurement are at 4.5 Hz and just above 1 Hz. Which was kind of expected, since we shortened the wires a bit, so one of the resonances moved up and I suppose that the other one moved down for the same reason.

X case --

Only one broad peak at about 3 Hz is seen here, whereas in Norna's measurement, there were two large peaks and one dip at 0.75 Hz and 2.5 Hz. I suspect that the lower peak has shifted lower than what I scanned to here and a high res scan going upto 0.2 Hz is taking place overnight. So we will have to wait and watch.

Pitch Roll and Yaw can wait for the morning.
  88   Fri Nov 9 09:37:55 2007 steveUpdatePSLhead temp hiccup
Just an other PSL-126MOPA_HTEMP hiccup.
The water chiller is at 20.00C
  93   Mon Nov 12 10:53:58 2007 pkpUpdateOMCVertical Transfer functions
[Norna Sam Pinkesh]

These plots were created by injected white noise into the OSEMs and reading out the response of the shadow sensors ( taking the power spectrum). We suspect that some of the additional structure is due to the wires.
  96   Mon Nov 12 15:18:34 2007 robUpdatePSLISS

After John soldered a 3.7 MHz notch filter onto the ISS board, I took a quick TF and RIN measurement. The out-of-loop RIN is attached, including a dark noise trace, and with the gain slider at 10dB. The UGF is 35kHz with a phase margin of 30deg. John is currently doing a more thorough inspection, and will detail his findings in a subentry.
  97   Mon Nov 12 23:44:19 2007 JohnUpdatePSLISS

Quote:

After John soldered a 3.7 MHz notch filter onto the ISS board, I took a quick TF and RIN measurement. The out-of-loop RIN is attached, including a dark noise trace, and with the gain slider at 10dB. The UGF is 35kHz with a phase margin of 30deg. John is currently doing a more thorough inspection, and will detail his findings in a subentry.


No progress on the ISS tonight. I tried to implement a new filter (attached)to try and gain some phase before the notch. If anything this made things worse. More work is needed.

The ISS loop is off and the power is off at the chassis.
  98   Tue Nov 13 14:33:40 2007 JohnUpdatePSLISS filter
The transfer function from 'In Loop Error Point Monitor' to TP3 the filter out test point on the ISS board.

-33dB at 3.715MHz.
  101   Wed Nov 14 12:47:19 2007 tobinUpdatePSLISS
John, Tobin

With John's notch filter installed and the increased light on the ISS sensing diode, we were able to get a UGF of about 60 kHz with the gain slider set to about 20 dB. This morning we met with Stefan to learn his ISS-fu.

His recommendations for the ISS include:
  • Replace the cables from the board to the front panel connectors if this hasn't already been done.
  • Replace the input opamps with 4131's. Be sure to test both positive and negative input signals.
  • Check that all the compensation capacitors are in place and are 68 pF
  • Make sure all the feedback loops have high frequency rolloff
  • The ISS board reads the PDs differentially; make sure the PD sends differentially.
  • Add a big (ie 10uF tantalum) capacitor to the PD to suppress power supply noise
  • Add bigger power supply bypass caps to the ISS
I just took sensing noise spectra (from the PD DC bnc ports) and then took the photodiodes off the table to check that they have the negative end of the differential line connected to ground. (I placed black metal beam blocks on the table in place of the ISS PD's. Also, from the ISS schematic, it looks like it sends a differential output to the PD DC bnc ports, but we have been plugging them directly into the SR785 (grounding the shield). We should make a little BNC-doodle that separates the signal+shield to go into the A and B inputs on the spectrum analyzer.) Opening up one of the photodiodes, it appears that the negative line of the differential output is not connected. Will continue later this afternoon.
  102   Wed Nov 14 16:54:54 2007 pkpUpdateOMCMuch better looking vertical transfer functions
[Norna Pinkesh]

So after Chub did his wonderful mini-surgery and removed the peek from the cables and after Norna and I aligned the whole apparatus, the following are the peaks that we see.
It almost exactly matches Norna's simulations and some of the extra peaks are possibly due to us exciting the Roll/longitudnal/yaw and pitch motions. The roll resonance is esp prominent.

We also took another plot with one of the wires removed and will wait on Chub before we remove another wire.
  103   Wed Nov 14 17:50:00 2007 tobinUpdatePSLISS
Here's the current wiring between the ISS and its PDs:

pin cable PD ISS
1 blue +5 +5
2 red +15 +15
3 white -15 -15
4 brown OUT IN PD +
5,6,7,8 no connection no connection GND
9 black GND IN PD -


The schematics for the ISS and the PDs are linked from our wiki.

We'll connect the ISS GND to the PD GND.
  105   Thu Nov 15 17:09:37 2007 pkpUpdateOMCVertical Transfer functions with no cables attached.
[Norna Pinkesh]

The cables connecting all the electronics ( DCPDs, QPDs etc) have been removed to test for the vertical transfer function. Now the cables are sitting on the OMC bench and it was realigned.
  106   Thu Nov 15 18:06:06 2007 tobinUpdateComputersalex: linux1 root file system hard disk's dying
I just noticed that Alex made an entry in the old ilog yesterday, saying: "Looks like linux1 root filesystem hard drive is about to die. The system log is full of drive seek errors. We should get a replacement IDE drive as soon as possible or else the unthinkable could happen. 40 Gb IDE hard drive will be sufficient."
  109   Thu Nov 15 18:37:06 2007 tobinUpdateComputerspossible replacement for linux1's disk
It looks like the existing disk in linux1 is a Seagate ST380013A (this can be found either via the smartctl utility or by looking at the file /proc/ide/hda/model). It appears that you can still buy this disk from amazon, though I think just about any ATA disk would work. I'll ask Steve to buy one for us.
  110   Fri Nov 16 11:27:18 2007 tobinUpdateComputersscript fix
I added a tidbit of code to "LIGOio.pm" that fixes a problem with ezcastep on Linux. Scripts such as "trianglewave" will now work on Linux.
# On Linux, "ezcastep" will interpret negative steps as command line arguments,
# because the GNU library interprets anything starting with a dash as a flag.
# There are two ways around this.  One is to set the environment variable
# POSIXLY_CORRECT and the other is to inject "--" as a command line argument
# before any dashed arguments you don't want interpreted as a flag.  The former
# is easiest to use here:

if (`uname` =~ m/Linux/) {
    # Add an environment variable for child processes
    $ENV{'POSIXLY_CORRECT'} = 1;
}
  111   Fri Nov 16 14:11:26 2007 tobinUpdateComputersop140
Alan called to say that Phil Ehrens will be coming by to take op140 off our hands.
  112   Fri Nov 16 14:31:43 2007 tobinUpdateComputersop140 disks
Phil Ehrens stopped by and took op140's disks.
  117   Tue Nov 20 11:10:07 2007 tobinUpdateComputersepics access from matlab
I installed "labca", which allows direct access to EPICS channels from within Matlab. It comes with both Linux and Solaris binaries (and source) but I've only tried it on linux.

To set it up, run these shell commands:
pushd /cvs/cds/caltech/users/tf/build/labca_2_1/bin/linux-x86
setenv PATH ${PATH}:`pwd`
cd /cvs/cds/caltech/users/tf/build/labca_2_1/lib/linux-x86
setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:`pwd`
popd
Then start matlab, and within matlab type:
addpath /cvs/cds/caltech/users/tf/build/labca_2_1/bin/linux-x86/labca
help labca
foo = lcaGet('C1:PSL-FSS_RCTRANSPD')
It seems like reasonably well-written software, and is being actively maintained right now. If we like it, I can build a more recent version, install it in a more permanent location, etc.
  121   Wed Nov 21 14:31:41 2007 robUpdatePSLFSS twiddle

I `tweaked' the FSS path today. Here's what I did:

1) Shut down the FSS autolocker

2) Turn off FSS servo

3) Assume the beam coming back from the AOM is double-first-order, and don't make any changes large enough to lose it.

4) Tweak the alignment of these components to maximize the incident power on the RC reflected diode:

a) PBS before AOM
b) AOM
c) curved mirror after the AOM

5) Translate the AOM such that the beam moves away from the PZT, then when it levels off (no more power gains with movement),
move it back just a little bit so there's a teensy drop in power. This should but the beam as close to the edge as possible,
but whether or not it's the best place is still to be determined.

6) Lock the FSS, and align the mirrors into the frequency reference cavity.

After all this, the RC transmitted power went from .57 to .73 -- probably not a big enough change to account for the missing loop
gain, but we'll know more once the loop gets measured (after Alberto stops hogging the Agilent network analyzer).

Other possible routes include a systematic check of the upstream path (e.g., the Pockels cell) and just increasing the pickoff fraction for the FSS.
  127   Tue Nov 27 20:47:00 2007 tobinUpdatePSLFSS
Rana, Tobin

We looked at the RF PD signal to the FSS (siphoning off a signal via a minicircuits directional coupler) and also took an open loop transfer function of the FSS. In the transfer function we saw the step at 100 kHz (mentioned by Rob) as well as some peculiar behavior at high frequency. The high frequency behavior (with a coupling of ~ -20 dB) turns out to be bogus, as it is still present even with the beam blocked. Rearranging the cabling had no effect; the cause is apparently inside the FSS. The step at 100 kHz turns out to be a saturation effect, as it moved as we lowered the signal amplitude, disappearing as we approached -60 dBm. (Above the step, the measurement data is valid; below, bogus.)

Transfer functions will be attached to this entry.

Some things to check tomorrow: the RF signal to the PC, RF AM generation by the PC, LO drive level into the FSS, RF reflection from the PC, efficiency of FSS optical path, quality of RF cabling.
  128   Wed Nov 28 04:21:46 2007 ranaUpdatePSLFSS

Quote:
Rana, Tobin

We looked at the RF PD signal to the FSS (siphoning off a signal via a minicircuits directional coupler) and also took an open loop transfer function of the FSS. In the transfer function we saw the step at 100 kHz (mentioned by Rob) as well as some peculiar behavior at high frequency. The high frequency behavior (with a coupling of ~ -20 dB) turns out to be bogus, as it is still present even with the beam blocked. Rearranging the cabling had no effect; the cause is apparently inside the FSS. The step at 100 kHz turns out to be a saturation effect, as it moved as we lowered the signal amplitude, disappearing as we approached -60 dBm. (Above the step, the measurement data is valid; below, bogus.)

Transfer functions will be attached to this entry.

Some things to check tomorrow: the RF signal to the PC, RF AM generation by the PC, LO drive level into the FSS, RF reflection from the PC, efficiency of FSS optical path, quality of RF cabling.


I would also add to Tobin's entry that we believe what Rob was seeing was saturation.

With the bi-directional coupler in there, the RF signal into the FSS board clearly went UP if moved the offset slider away from zero.
With a scope looking at the IN2 testpoint, we can see that there's less than 2 mV offset at zero slider offset.

One tangential thing we noticed with the coupler is that, in lock, the amount of reflected RF is around the same as that going in to the mixer.
I have always wanted to look at this but have only had uni-directional couplers in the past. I think that the double balanced mixer is inherently
not a 50 Ohm device during the times where the diodes are being switched. IF that's the case we might do better in the future by having an RF
buffer on board just before the mixer to isolate the PD head from these reflections.
  134   Wed Nov 28 17:41:34 2007 robUpdatePSLFSS again
I investigated the FSS a bit more today. I looked at the signals coming out of the FSS frequency reference, and saw that both the LO and PC drive were distorted, non-symmetric waveforms. In addition, the LO path had a 3dB attenuator, meaning the mixer was starved. I placed mini-circuits SLP-30 filters in both paths, and now both are nice sine waves. I also took out the 3dB att. With this work, and the CG slider maxed out at 30, the FSS open loop gain (for real this time) goes up to ~250kHz. Still needs more investigation.
  136   Wed Nov 28 19:44:18 2007 tobinUpdatePSLHEPA
I found the HEPA turned off completely. I turned it on.
  163   Tue Dec 4 23:16:35 2007 tobinUpdatePSLISS
I was confused to find that I could increase the ISS gain slider all the way from 15dB to 30dB without seeing much of any increase in gain in the measured open-loop transfer function. While making these swept-sine measurements, the saturation indicator almost never tripped, indicating it was seemingly happy. But then I noticed an odd thing: if I disable the test ("analog excitation") input, the saturation indicator trips immediately. I hooked up a scope to the current shunt test point (TP12). With the test input enabled, the loop closed, and the analog excitation port connected to the SR785, I see a a 5 Vpkpk, 2.55 MHz triangle wave there. It is there even if I set the SR785 excitation amplitude to zero, but it disappears if I disconnect the cable from the SR785.

I found oscillations at TP20, TP30, TP36, TP41, and TP42. Many of these are in the (unused) "outer loop" circuitry and currently lack compensation capacitors.
  165   Wed Dec 5 13:49:08 2007 albertoUpdateElectronicsRF AM PD lines monitor
In the last weeks Iíve been working on the design of an electronic board to measure directly the power of the main spectral lines on of the RF-AM photodiode from as many independent outputs. The idea is to have eventually a monitor channel in the CDS network for the power of each line.
Looking at at the spectrum from the RF-AM PD (see attached plot), there are 5 main lines:
Frequency
3 fsr = 33 195 439 Hz
4 fsr = 66 390 878 Hz
12 fsr = 132 781 756 Hz
15 fsr = 165 977 195 Hz
18 fsr = 199 172 634 Hz

Two main approaches have been proposed for the circuit depending on the way followed to isolate the lines:
1) Filters: the frequencies are separated by narrow notch filters, then a diode bridge rectifies and a low pass filter extracts the DC component.
2) Mixers: for each frequency there is a mixer driven by a copy of the correspondent modulation frequency provided by the function generators (the Marconi). The mixers automatically give the DC component of the rectified signals.
Because of the phase lags that we should compensate if we used mixers, we would prefer the first approach, if it works.
Starting with a tolerance of about 10% between the channels, the spectrum (see attachment) sets the constraint to the filterís suppression:
Filter central frequency [MHz]******Suppression within 30 Mhz [dB]
33*********************************-7-20 = -27
66**********************************7-20 = -13
133*********************************12-20 = -8
166********************************-12-20 = -32
199*********************************10-20 = 10

So far Iíve tried two kinds of designs for the filters, Butterworth (see attachment) and LC and I'm measuring transfer functions tuning the components to match the central frequency and the bandwdth of the filters with the requirements.

The frequencies weíre dealing with are rather high and several adjustments had to be done to the measurement system in order to shield the circuit from the impedance of the input and the output line (i.e., amplifier turned out to be necessary). Also, an the mixer had to be replaced to an RF one.
It seems I'm now measuring new transfer functions (which look quite different from what I've got with no amplifiers).
To be posted soon.
  167   Wed Dec 5 17:49:57 2007 tobinUpdatePSLISS
Attached is a plot of the ISS RIN with a variety of gain settings.

Unfortunately the dark noise is huge now--a result of the new cables & wiring?
  168   Wed Dec 5 18:08:36 2007 AndreyUpdateASCOptical Lever laser for ETMX is installed

A new laser with \lambda=633nm has been intalled and the mirror adjusted so that the signal hits the center of the photodetector.

Output power level of that laser is 3.45 +- 0.05 mW.

Only about 0.29mW hits the photodetector.

Cable clips have been used to firmly fix the power supply cable for the laser.

See attached photopicture of the ETMX - "oplev" - optical - table.
  169   Wed Dec 5 18:22:03 2007 tobinUpdatePSLISS dark noise
Attached is a plot of the dark noise spectrum of the ISS photodiodes (1) before fooling with them, (2) after replacing the 4151's with 4131's (improvement!), and (3) after replacing the cables and changing the wiring (disaster!).
  171   Wed Dec 5 20:32:51 2007 tobinUpdatePSLISS dark noise
The ISS dark noise is not coming from the PD heads; the spectrum is essentially unchanged when the PD is unplugged from the ISS. Did the input opamps both get semi-fried in the same way? (They worked so well when they were first installed.) What else changed? I'm baffled. Frown
  177   Thu Dec 6 19:30:43 2007 tobinUpdatePSLISS dark noise - 60 Hz!
A higher resolution spectrum [attached] shows that nearly all of the excess dark noise on the ISS is in 60 Hz harmonics (with some 256 Hz harmonics too--are these from the DAQ?).

With the loop closed and the slider at 5dB, the laser light coming out has a noise floor of 10^-7 RIN or better from 40 Hz to 8 kHz.

Now to figure out why all this 60 Hz is getting in... (I tried turning off all the lights and the HEPA, and moving the SR785 further away, none of which did anything.)
  181   Fri Dec 7 18:28:30 2007 tobinUpdateComputer Scripts / Programscompiled matlab hoses itself
Andrey pointed out to me that some matlab functions in the Signal Processing Toolbox were dying with errors. Looking into the .m file (identified using the "which" command), I was surprised to see binary garbage rather than glistening, clear Matlab prose. Then I noticed the directory in which it was finding the .m file:
>> which decimate
/cvs/cds/caltech/apps/mDV/extra/linetrack_c_mcr/toolbox/signal/signal/decimate.m
See that "linetrack_c_mcr" directory? This is what is generated when a "compiled" (grumble) Matlab program is run--it decompresses itself into a subdirectory containing weird semi-compiled binary .m files. Unfortunately this is somehow getting incorporated into the matlab path. (I assume there is something in mDV that says "put all subdirectories into the path.")

I hate the Matlab compiler.
  182   Fri Dec 7 18:31:30 2007 tobinUpdateComputer Scripts / Programscompiled matlab hoses itself
Addendnum. The reason the linemon_mcr command was in the path was because of the user issuing the command "addpath(genpath(pwd))" where genpath(D) "returns a path string starting in D, plus, recursively, all the subdirectories of D."

The Matlab compiler is still bad, however.
  183   Fri Dec 7 19:14:30 2007 tobinUpdatePSLISS dark noise - ground loop enlightenment
My alleged 60 Hz harmonics were all from a ground loop created by connecting the SR785 ground to the ISS circuit ground; they disappeared when I set the SR785 input to "floating ground." doh!

I modified the ISS PD's to have a 100 ohm resistor in series with the output (in place of 20 ohms). The diodes are again in place on the table, ready for action.
  185   Mon Dec 10 18:42:20 2007 tobinUpdatePSLISS RIN script
I wrote a script to measure the ISS RIN. The script uses the "labca" interface (described in an earlier entry) to read and twiddle EPICS settings and mDV to get DAQ data. The script measures open loop RIN, closed loop RIN at each of several gain slider settings, and dark noise. The dark noise is obtained by misaligning (unlocking) the PMC. The script also compares the whitened and unwhitened spectra for an open loop measurement and performs a fit of a simple pole to find the dewhitening filter.

This is all very exciting, but I don't quite believe the results, since the closed loop RIN seems to bottom out at 2e-7/rtHz regardless of the gain slider setting.

Sample output attached. The script may be found at scripts/PSL/ISS/rin.m.
ELOG V3.1.3-