40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 168 of 344  Not logged in ELOG logo
ID Date Author Type Categoryup Subject
  503   Thu May 29 15:58:44 2008 JohnSummaryIOOMC realignment
I repeatedly adjusted the yaw of the upper mirror on the input periscope and re aligned the MC. With the PRM aligned I tried to optimise MC transmission and DC refl simultaneously. I subsequently centred the beams on WFS1/2. Attached is a 30 day trend of MC alignment and transmission.
  553   Mon Jun 23 19:33:01 2008 rana, jenneUpdateIOOMC_F Noise check
We looked at the MC_F spectrum because Rob and Yoichi said that it had gone 'all crazy'. It
seemed fine as we looked at it (even with only one boost stage on) so we looked for things
that might be marginal and make it go nuts.

At the error point (Q mon on the demod board and TEST IN1) of the MC Servo board we saw the
old 3.7 MHz signal (comes from the 33 MHz RFAM getting demodulated by the 29.5 MHz MC LO)
and thought that this might cause some worries. So we installed Jenne's passive elliptic
low pass which has a 3.7 MHz zero.

This wiped out the 3.7 MHz noise but we were not able to re-create the extra frequency noise
so its unlikely to have fixed the main problem. However, we leave it in because its good. If
there is a need to revert it, we have left hanging on the side of the rack the old cable which
was a SMA->TNC making a direct, unfiltered connection between the MC Demod board and the MC
servo board.

More before and after results from Jenne tomorrow, but for now here is a calibrated MC_F spectrum
using the new MC_F-Reference.xml template file.

We also noticed that we could make some small effects on the MCF spec by adjusting the PMC gain so
there's probably more hay to be made there using a lead brick and a gain slider. More in Jenne's
entry.
  554   Mon Jun 23 19:48:28 2008 rana,albertoSummaryIOOStochMon trends (80 days)
Here's a StochMon plot showing the RFAM after the MC. Remember that in these units, 2V means no RFAM
and 0 V means lots of RFAM. Alberto says "the calibration is in Tiramisu". So there you go.
  562   Wed Jun 25 01:30:19 2008 JohnSummaryIOOFrequency noise after the MC
I made some (very) rough estimates of the contribution made to the noise after the mode cleaner by three sources.

Seismic noise - how much of the signal is due to the mode cleaner compenstaing for seismic disturbance of CARM.
Actuator noise - coil drivers and DAC noise.
MC_F - estimate of MC_F suppressed by the loop gain.
  594   Sun Jun 29 19:19:47 2008 ranaSummaryIOOTrends of the PSL/IOO Quads over 1000 days
Only IOO POS has been working for the past 2 years. I guess we should recommission the IOO ANG and REFL QPDs
  596   Sun Jun 29 20:09:40 2008 JohnSummaryIOOmcup and mcdown indicators
I edited the mcup and mcdown scripts so that C1IFO_STATE shows when these scripts are running.

I also added indicators to the LockMC screen.
  598   Mon Jun 30 01:49:06 2008 JohnUpdateIOOMC work
I'm in the process of aligning the mode cleaner/ input beam.

I turned off the WFS and cleared their histories, adjusted the input periscope and re-aligned the mode-cleaner accordingly.
I then unlocked the cavity and centred the beams on the WFS.

MC transmission is ~3.3 and the REFL beam looks a little better.

However, turning the WFS on now lowers the transmission. More thought tomorrow.

I'm leaving the MC locked with WFS off.
  600   Mon Jun 30 08:59:23 2008 steveUpdateIOOIOO-MC_DEMOD_LO is low
The alarm handler is beeping relentlessly: asking for help in high partical count and low demod signal
  601   Mon Jun 30 09:46:15 2008 JohnUpdateIOOMC WFS
MC WFS are on. They seem to do some good during the day.
  626   Wed Jul 2 18:30:01 2008 JohnUpdateIOOQPD alignment
I aligned the beams on the following QPDs

IP POS
IP ANG
MC TRANS
IOO POS
  694   Fri Jul 18 16:57:37 2008 JenneUpdateIOOCalibrated MC_F
I have calibrated MC_F. The conversion factor is 137.49 MHz/count.

The calibration data taken is attached, along with a calibrated power spectrum.

On the data plot, the x axis is volts from the C1:IOO-MC_FAST_MON channel, with the calibration between FAST_MON and MC_F = -788.18 volts/count.
The linear term of the fit line = -0.085MHz/volt. Error bars are +/- 1 in the last digit of what the spectrum analyzer gave me for frequency (+/- 0.01MHz).

The net conversion factor is then (-788.18)*(-0.085)*(2) = 137.49 MHz/count. The factor of 2 is because the light passes through the AOM twice.

On the power spectrum,
REF0 and REF1 = MC unlocked, HEPAs on, MC Refl gain = 22
REF2 and REF3 = MC locked, HEPAs on, MC Refl gain = 22
REF4 and REF5 = MC locked, HEPAs on, MC Refl gain = 19
REF6 and REF7 = MC locked, HEPAs off, MC Refl gain = 19
  696   Fri Jul 18 17:12:35 2008 JenneUpdateIOOChecking out the MC Servo Board
[Jenne, Max]

One of the things that Rana thinks that might be causing my MC_F calibration to be off is that the MC Servo Board's filters don't match those on the schematics. Max and I pulled the MC servo board today to check resistor and capacitor values. Alberto needed the Mode Cleaner, so we put the board back before finishing checking values. We will probably pull the board again next week to finish checking the values.

I haven't checked to ensure that the MC still locks, because Yoichi is doing stuff on the PSL table, but I didn't change anything on the board, and hooked all the cables back where they were, so hopefully it's all okay.
  697   Fri Jul 18 19:15:15 2008 JenneUpdateIOOChecking out the MC Servo Board

Quote:
[Jenne, Max]

I haven't checked to ensure that the MC still locks, because Yoichi is doing stuff on the PSL table, but I didn't change anything on the board, and hooked all the cables back where they were, so hopefully it's all okay.


I put the PMC back and the MC now locks.
  710   Mon Jul 21 19:55:16 2008 rana,jenneConfigurationIOONoise in MC_F
Jenne put the MC board on extender today - its still that way but everything is probably connected (check AO).

We measured the TFs of the DAQ section for MC_F because of how everything looked wrong in the plots Jenne
put in the log earlier. Everything we measured today seemed to jive with the schematic. We also looked up
the original traveler for this board which Betsy filled in years ago: it also is in spec for the DAQ filtering.

So then I looked at the power spectrum of the output signal to the VCO. It had lots of HFC (high frequency crap).
I adjusted the parameters of the FSS (common gain, fast gain, RF phase Astonished) and lowered the MC common gain. This
produced a global minimum in that 4D parameter space.

I think that basically, the FSS gain is too low even with the common gain slider maxed. Having the fast gain up
at 19 dB like I had left it was bad - even though it minimizes the PC control signal, it produces a lot of HFC
up around 100 kHz in MC_F. After John (finally) gets around to measuring the FSS loop we can figure out how to
better tune this. The MC gain then has to be tuned so as to best minimize the HFC given the new FSS gain; there's
basically no coupling from the MC gain to the FSS loop shape so its always best to tune the FSS first. Pleased

The RF phase of the FSS was a mystery - I have no idea why it should do anything and I have never heard of this
and I don't know why I tried it today. But...changing it by ~0.6-0.7 slider units reduced the HFC by another factor
of ~3. Somebody should put this slider into units of degrees.8-)

Here's a table of the changes. Please make these the new nominals:
you asked for:   diff 2008/07/21,13:00 2008/07/22,2:44:16 utc '.*FSS.*|.*MC.*'
LIGO controls: differences, 2008 07/21 13:00:00 utc vs. 2008 07/22 02:44:16 utc
__Epics_Channel_Name______   __Description__________   __value1____     __value2____
C1:IOO-MC_REFL_GAIN                                    22.000000        19.000000
C1:IOO-MC_REFL_OFFSET                                  0.818380         0.818100
C1:PSL-FSS_MGAIN                                       10.000000        30.000000
C1:PSL-FSS_PHCON                                       2.073170         1.413170

The attached plot shows the "SERVO" TNC output of the board; this is supposed to be the same as the voltage going to the
VCO box. So its V/Hz transfer function is flat above 40 Hz. Tomorrow Jenne will post more data and remove the extender
board.

Since I only used an SR785, I only saw noise up to 100 kHz. Its key to use an RF spectrum analyzer when checking out
the FSS and the MC systems.
  752   Tue Jul 29 01:03:17 2008 robConfigurationIOOMC length measurement
rob, yoichi

We measured the length of the mode cleaner tonight, using a variant of the Sigg-Frolov method. We used c1omc DAC outputs to inject a signal (at 2023Hz) into the AO path of the mode cleaner and another at DC into the EXT MOD input of the 166MHz IFR2023A. We then moved an offset slider to change the 166MHz modulation frequency until we could not see the 2023Hz excitation in a single-bounce REFL166. This technique could actually be taken a step further if we were really cool--we could actually demodulate the signal at 2023Hz and look for a zero crossing rather than just a powerspec minimum. In any case, we set the frequency on the Marconi by looking at the frequency counter when the Marconi setting+EXT MOD input were correct, then changed the Marconi frequency to be within a couple of Hz of that reading after removing the EXT MOD input. We then did some arithmetic to set the other Marconis.

The new f2 frequency is:

New              OLD
--------------------------
165983145        165977195

  753   Tue Jul 29 09:12:43 2008 KojiConfigurationIOOMC length measurement
I found that the prev modulation freq had been determined with a same kind of measurement by Osamu, which also looked accurate.
http://www.ldas-sw.ligo.caltech.edu/ilog/pub/ilog.cgi?group=40m&task=view&date_to_view=09/12/2002&anchor_to_scroll_to=2002:09:12:17:10:30-ajw

(There is also a document by Dennis to note about this measurement
http://www.ligo.caltech.edu/docs/T/T020147-00.pdf )

So, it means that the round trip length of the MC shortened by 1mm in the 6 years.
New              OLD
--------------------------
27.0924          27.0934    [m]

Quote:
rob, yoichi

We measured the length of the mode cleaner tonight, using a variant of the Sigg-Frolov method.
....
The new f2 frequency is:
New              OLD
--------------------------
165983145        165977195
  757   Tue Jul 29 18:15:36 2008 robUpdateIOOMC locked

I used the SUS DRIFT MON screen to return the MC suspensions to near their pre-quake values. This required fairly large steps in the angle biases. Once I returned to the printed values on the DRIFT screen (from 3/08), I could see HOM flashes in the MC. It was then pretty easy to get back to a good alignment and get the MC locked.
  768   Wed Jul 30 13:14:03 2008 KojiSummaryIOOHistory of the MC abs length
I was notified by Rob and Rana that there were many measurements of the MC abs length (i.e. modulation 
frequencies for the IFO.) between 2002 and now.

So, I dig the new and old e-logs and collected the measured values of the MC length, as shown below. 

I checked the presence of the vent for two big steps in the MC length. Each actually has a vent. 
The elog said that the tilt of the table was changed at the OMC installation in 2006 Oct.
It is told that the MC mirrors were moved a lot during the vent in 2007 Nov.

Note:
o The current modulation freq setting is the highest ever.
o Rob commented that the Marconi may drift in a long time.
o Apparently we need another measurement as we had the big earthquake.

My curiosity is now satified so far.

Local Time	3xFSR[MHz]	5xFSR[MHz]	MC round trip[m]	Measured by
----------------------------------------------------------------------------
2002/09/12	33.195400 	165.977000 	27.09343		Osamu
2002/10/16	33.194871 	165.974355 	27.09387		Osamu
2003/10/10	33.194929 	165.974645 	27.09382		Osamu
2004/12/14	33.194609 	165.973045 	27.09408		Osamu
2005/02/11	33.195123 	165.975615 	27.09366		Osamu
2005/02/14	33.195152 	165.975760 	27.09364		Osamu
2006/08/08	33.194700 	165.973500 	27.09401		Sam
2006/09/07	33.194490 	165.972450 	27.09418		Sam/Rana
2006/09/08	33.194550 	165.972750 	27.09413		Sam/Rana
----2006/10 VENT OMC installation	
2006/10/26	33.192985 	165.964925 	27.09541		Kirk/Sam
2006/10/27	33.192955 	165.964775 	27.09543		Kirk/Sam
2007/01/17	33.192833 	165.964165 	27.09553		Tobin/Kirk
2007/08/29	33.192120 	165.960600 	27.09611		Keita/Andrey/Rana
----2007/11 VENT Cleaning of the MC mirrors
2007/11/06	33.195439 	165.977195 	27.09340		Rob/Tobin
2008/07/29	33.196629 	165.983145 	27.09243		Rob/Yoichi
  770   Wed Jul 30 15:12:08 2008 ranaSummaryIOOHistory of the MC abs length
> I was notified by Rob and Rana that there were many measurements of the MC abs length (i.e. modulation
> frequencies for the IFO.) between 2002 and now.

I will just add that I think that the Marconi/IFR has always been off by ~150-200 Hz
in that the frequency measured by the GPS locked frequency counter is different from
what's reported by the Marconi's front panel. We should, in the future, clearly indicate
which display is being used.
  829   Tue Aug 12 19:48:24 2008 JenneUpdateIOOPRM standoff is in....mostly
Yoichi, Jenne

The missing PRM standoff is now partially installed. The standoff is in, and the wire is in the groove, but we have not finished adjusting its position to make the PRM stand up straight. It turns out to be pretty tricky to get the position of the standoff just right.

We have set up a HeNe laser as an oplev on the flow bench (which we checked was level) in the clean assembly room, and are using it to check the pitch of the mirror. We set a QPD at the height of the laser, and are looking at the single-reflected light. When the single-reflected light is at the same height as the center of the QPD, then the mirror is correctly aligned in pitch. (Actually, right now we're just trying to get the single-reflected light to hit the diode at all...one step at a time here).

We'll continue trying to align the PRM's standoff in the morning.
  837   Thu Aug 14 19:35:54 2008 JenneSummaryIOOPRM in the chamber, ready to pump!
Rob, Yoichi, Jenne, Steve

Summary: Everything is back in the chamber, we just need to put on the big doors, and start pumping in the morning.

After letting the PRM's standoff epoxy cure overnight, it was time to put the optic back in the BS Chamber. Rob put the optic cage back in the chamber, as close to the guide points that Rana had placed as possible. A handy technique was discovered for pushing the cage into place: put a long screw into the table, leaving an inch or so above the table, then use that as a push-off point so that you can push the base of the cage with your thumb. According to Rob, this is probably just about as effective as using a pusher-screw.

The guides were helpful in getting the PRM back to its original position, but one of them was placed in such a way that it could move when pushed against. The clamp that was used as a guide point was placed with one of the screws half on the edge of a hole, so that when the cage was pushed against the guide point, that screw could wiggle around, causing the clamp to rotate thus no longer being a definite guide point.

Just after putting the PRM in place, Rob found the standoff that had gone missing. (see elog #835)

Once the PRM was back in place, we put the OSEMs back, and reinstalled the satellite boxes that had been removed (PRM's, which Ben has fixed - an op-amp was blown, and BS's, which we used over in the clean room with the spare OSEMs). We found a problem with the LR PRM OSEM reading on Dataviewer. It was saturating when the OSEM was just sitting on the table, with nothing between the LED and the sensor. We measured the output from the satellite box with the octopus cables, and measured 2.3 volts, which is too much for the DAQ. It seems fine when we install it in the cage, and the magnet is blocking part of the light. We should investigate the gain of the satellite box when convenient. This is not something that needs to be done prior to pump-down. Also, when we put an allen wrench to block the light while checking which OSEM was which, we noticed that the Dataviewer reading would go down to -2V, then come back to 0V when the light was completely blocked. This may be some incorrect compensation for some whitening. Again, we should look into this, but it is not terribly time-sensitive.

Once the OSEMs were centered, we tried to turn on the damping for the PRM. This was successful, so we are confident that we have put all of the OSEMs back in their correct places.

We found that we were easily able to get the PRM's oplev back on the QPD, so we ~centered the oplev, and then centered all of the PRM's OSEMs. This assumes that the oplev was in a good place, but I think we've determined that this is the case.

We did the same thing for the SRM and the BS, to check the OSEM values before we close up for good. We found that some of the SRM OSEMs were reading low (magnet too far in), and that all of the BS OSEMs were low, perhaps as if the table were tilted a tiny bit after removing and replacing the weight of the PRM. We recentered all of the OSEMs for both of these optics.

We checked that all of the pigtails for the PRM OSEMs were anchored to the PRM cage using some copper wire as tie-downs.

We checked that all of the earthquake stops were within 1mm or so of each of the 3 optics in the BS chamber. The SRM's earthquake stops were fairly far out. One of the bottom ones was far enough that when Yoichi turned it the wrong way (accidentally), it fell out. He put it back in, and adjusted all of the earthquake stops appropriately. This 1mm distance comes from Seji, and the specs for the optics' cages.

We did a look-through of the chamber, and took out all of the tools, and other things that were not bolted down to the table.

We have left the damping of the PRM off for the night.

To do: put the doors back on, and start the pump down.
  849   Mon Aug 18 22:47:12 2008 YoichiUpdateIOOMC unlock study
As rob noted, the MC keeps unlocking in a few minutes period.
I plotted time series of several signals before unlocks.
It looks like the MC alignment goes wrong a few hundred msec before the unlock (the attached plot is only one example, but all unlocks
I've looked so far show the same behavior).
I will look for the cause of this tomorrow.

The horizontal axis of the plot is sec. The data values are scaled and offset-removed appropriately so that all curves are shown
in a single plot. Therefore, the vertical axis is in arbitrary units.
  856   Tue Aug 19 18:55:41 2008 YoichiUpdateIOOMC unlock study update
In entry 849, I reported that the MC transmitted power drops before the sudden unlocks.
However, because C1:IOO-MC_TRANS_SUM is a slow channel, we were not sure if we can believe the timing.
So I wanted to use C1:IOO-MC_RFAMPDDC, which is a fast channel, to monitor the transmitted light power.
However, this channel was broken. So I fixed it. Details of the fixing work is reported in another entry.
The attached plot shows a recent unlock event. It is clear that in the fast channel (i.e. C1:IOO-MC_RFAMPDDC),
there is no delay between the drop of the MC power and the crazy behavior of control signals.
So it was concluded that the apparent precedence of the MC power drop in the slow channels (i.e. C1:IOO-MC_TRANS_SUM)
is just an artifact of timing inaccuracy/offset of the slow epics channels.

Sometime around 5PM, the MC started to be unwilling to even lock. It turned out that the PC drive of the FSS was going
crazy continuously. So I changed the normal values of the common gain and the fast gain, which the mcup script uses.
Now with this new setting, the MC locks happily, but still keeps unlocking.
  864   Wed Aug 20 18:09:48 2008 YoichiUpdateIOOMC still unlocks
Being suspicious of FSS PC path as the culprit of the MC unlocks, I opened the FSS box and connected a probe to the TP7,
which is a test point in the PC path (before high voltage amplifier).
The signal is routed to an unused fast DAQ channel in the IOO rack. It is named C1:IOO-MC_TMP1 and recorded by the frame
builder. You can use this channel as a generic test DAQ channel later.

By looking at the attachment, the PC path (C1:IOO-MC_TMP1) goes crazy at the same time as other channels. So probably
it is not the trigger for the MC unlock.

Then I noticed the WFS signals drift away just before the unlock as shown in the attached plot. So now the WFS is the
main suspect.
Rob tweaked MC1 pitch to center the WFS QPDs while the MC is not locked. It improved the shape of the MC reflection.
However, the sudden MC unlock still happens. We then lowered the WFS gain from 0.5 to 0.3. Did not change the situation.
It looks like the MC length loop starts oscillating after the WFS signals drift away.
We will measure the WFS and MC OPLTF to see the stability of the loops tomorrow.

  867   Thu Aug 21 17:55:14 2008 ranaHowToIOOMC WFS DC Offsets
I ran the McWFS_dc_offsets script to trim out the DC offsets on the MC WFS DC signals.

Rob says "who cares?"
  868   Thu Aug 21 18:13:24 2008 ranaUpdateIOOMC WFS Control signals not responsible for lock losses
This is a 4 hour, second-trend of the MC WFS error and control signals.

There is no sign that the MC loses lock because of feedback signal saturations.
  872   Fri Aug 22 17:03:41 2008 YoichiUpdateIOOMC open loop TF
I measured the open loop TF of the overall MC loop using the sum-amp A of the MC board.
I used the Agilent 4395A network analyzer and saved the data into a floppy disk. However, the data was corrupted when
I read it with my computer. I had the same problem before. The floppy is not reliable. Anyway, I have to re-measure the TF.
From what I remember, the UGF was around 25kHz and the phase margin was less than 15deg.
Above this frequency, the open loop gain was almost flat and had a small bump around 100kHz.
This bump has a gain margin of less than 4dB (the phase is more than 180deg delayed here).
So the MC is marginally stable and either decreasing or increasing the gain will make it unstable easily.
Probably, the broken FSS is responsible for this. We have to fix it.

During the measurement, I also found that the input connectors (IN1 and IN2) of the MC board are freaky.
These are TNC connectors directory mounted on the board. Gently touching the cables hooked up to those connectors
caused a large offset change in the output.
When Rana pulled the board out and pushed it in firmly, the strange behavior went away. Probably, the board was
not correctly inserted into the backplane.
This could have been the reason for the MC unlocks.
  877   Mon Aug 25 11:43:55 2008 YoichiFrogsIOOMC REFL PD cable had been disconnected through out the weekend
Most of my morning was wasted by the MC REFL PD cable, which was disconnected on the generic LSC PD interface board.
I know who did this. *ME*. When I pulled out the MC board, which is sitting next to the PD interface, on Friday, I must have
disconnected the PD cable accidentally. The connector of the PD cable (D-Sub) does not have screws to tighten and easily comes off.
I wrote this entry to warn other people of this potential problem.
  920   Thu Sep 4 07:46:10 2008 YoichiUpdateIOOMC is now happy
The MC has been locked for more than 12 hours continuously now !
Changes I made yesterday were:
(1) Removed the 20dB attenuator before the EOM.
(2) Reduced the Fast Gain from 21dB to 16dB, which made the PC to be a little bit more loaded (~0.6Vrms).

As Rana pointed out in the meeting, setting the Fast Gain a bit lower may have put the FSS in a stabler state.
  921   Thu Sep 4 10:13:48 2008 JenneUpdateIOOWe unlocked the MC temporarily
[Joe, Eric, Jenne]

While trying to diagnose some DAQ/PD problems (look for Joe and Eric's entry later), we unlocked the PMC, which caused (of course) the MC to unlock. So if you're looking back in the data, the unlock at ~10:08am is caused by us, not whatever problems may have been going on with the FSS. It is now locked again, and looking good.
  928   Thu Sep 4 17:17:03 2008 YoichiUpdateIOOMC open loop TF
I measured open loop transfer functions of the MC servo.
The UGF was about 30kHz. Since there was some gain margin at higher frequencies, I increased
the input gain of the MC servo board from 19dB to 22dB. Now the UGF is 40kHz and we have more
phase margin (~30deg).
  935   Mon Sep 8 10:57:49 2008 steveUpdateIOOthe psl and mc are back to normal
The alarm handler is silent this morning.
This is almost unbelievably pleasant after two mount of harassment.
The MC did not lose lock for three days.

Atm1: the new fss layout
Atm2: PMC with lead brick
Atm3: 3 days plot
  952   Wed Sep 17 12:55:28 2008 robConfigurationIOOMC length
I measured the mode cleaner length last night:

SR620                Marconi
                     199178070
165981524            165981725
                     132785380
                      33196345


I did the division in Marconi-land, rather than SR620-land.
If someone wants to do this in SR620-land, feel free to do it and post the numbers.
  968   Fri Sep 19 00:06:54 2008 ranaUpdateIOOMC_F: Too much frequency noise around 100 Hz
WE noticed this excess again in MC_F. We tried recentering the WFS, but no effect.

Also no effect from changing the FSS gain, PMC gain, or ISS gain.

Actually, there IS a change when changing the PMC gain -- the ISS can be made to saturate
by lowering the PMC gain by 10 dB. Jenne and I need to finish off the PMC loop.

10 kHz UGF or bust!
  993   Thu Sep 25 15:24:05 2008 YoichiUpdateIOOMC_F VCO calibration
I calibrated the VCO driving the AOM for the AO path of the MC feedback.

I injected DC voltage to the VCO and measured the output frequency with the SR620.

The attached plot shows the relation between the input voltage to the VCO and the output frequency.
The coefficient is 1.75MHz/V. Since the AOM is double path, the actual actuation efficiency is 3.5MHz/V.
We can use this value for the calibration of the MC_F. However, the MC_F DAQ channel is sampling the VCO input voltage through a 10Hz high-pass filter.
This filter has to be taken into account to convert the MC_F counts to frequency.
I will measure the transfer function from the VCO input to the MC_F counts tomorrow.
  999   Fri Sep 26 16:13:57 2008 ranaUpdateIOOMC_L / MC_F crossover
We were trying to understand why the FAST_F signal had such large excursions (~1V ~ 5 MHz).

Some of this is due to the seismic noise and the resulting MC_F signals. Increasing the MCL
gain reduces it somewhat. But as you can see from the attached loop gain measurement, the
crossover is a healthy 90 Hz with the MCL digital gain = 1. But what's going on in the MC loop
in the 10-20 Hz band? That looks like bad news.

Then I noticed that changing the ISS gain slider puts a large step (~1V) into the FAST. My guess
is that the board has large DC offsets and also much of the switching supply noise. Not sure why
this would be worse than before though.

To prevent large noise in the FAST, I've changed the mcup script to set this gain to -5 dB. Our
intensity noise is now presumably 10-15 dB worse than the nominal good levels we had a year ago.
Needs investigation.
  1002   Fri Sep 26 19:18:39 2008 JenneUpdateIOOMC2 is having a bad day
As Steve mentioned earlier in today's elog, MC2 keeps ringing up for no clear reason. It is definitely only MC2 that is ringing up, since it's sensors will read several hundreds of counts, while all the other optics are at regular 2 counts and below on the Watchdog screen.

Preliminary investigation results: Around the time of these "kick up" events, the Ranger seismometer does not see any motion, nor does the set of accelerometers under the MC1 chamber. The set of accelerometers under the MC2 chamber do see activity that is at the same time as these events. These events are not caused just by someone walking around, since Rana went inside and clunked around near MC2 while I watched the sensor levels. MC2's watchdog did not trip.

For further investigation: Why is it that only the MC2 accelerometers are seeing the motion? Similarly, why is MC2 the only optic being kicked? Has anyone done anything lately to the MC2 stack?
  1012   Wed Oct 1 02:10:03 2008 ranaUpdateIOOMZ is going bad
Here's a 2 day trend of the MZ. You can see that there is something bad with ERR - it should really be going to zero.

Also LODET is dead. We need to rejuvinate LODET somehow.

The next plot is a 90 day hour-trend of the same signals. You can see that LODET came back to us between
September 10 and 19 ??? I looked at a 4 year trend and it seems that this signal has always been zero
(nice use of disk space) except for a few days in Nov of 06 and then whatever happend on Sep 10.
  1022   Fri Oct 3 12:15:21 2008 AlbertoConfigurationIOOC1iool0 rebooted
This morning, in order to update the threshold values of the alarm handler for the StochMon, I rebooted the C1iool0 computer following the procedure in the wiki, that is telnetting on it and typing CTRL+X. Apparently everything went well in the process.
  1032   Tue Oct 7 21:19:40 2008 YoichiUpdateIOOMC_F calibrated spectrum
I updated the plots because I did not take into account the double path AOM effect, which doubles the frequency actuation efficiency. (2008/10/8)

I determined the MC_F counts to the PSL frequency change calibration.
The attachment 1 is the calibrated MC_F spectrum, which is, above the cross over frequency, equivalent to the frequency noise seen by the MC.

The calibration method is the following:

1) I picked spare AD and DA channels (C1:IOO-MC_TMP1 and C1:OMC-SPARE_DAC_CH_16_EXC). C1:OMC-SPARE_DAC_CH_16_EXC is labeled C1:OMC-OSC_FM on the cable.

2) C1:IOO-MC_TMP1 was calibrated by injecting a sine wave of known amplitude and measuring the amplitude in counts in dataviewer.
It was 63uV/cnt.

3) C1:IOO-MC_TMP1 was connected to the feedback BNC connector of the MC board, that is the direct monitor of the feedback voltage to the VCO.

4) C1:OMC-SPARE_DAC_CH_16_EXC was connected to the channel B excitation input of the MC board, which adds the signal to the fast feedback path.

5) Using DTT a swept sine signal was injected to the MC board through C1:OMC-SPARE_DAC_CH_16_EXC, and the transfer function from C1:IOO-MC_TMP1 to the
C1:IOO-MC_F was measured.

6) Using the calibration of C1:IOO-MC_TMP1, the transfer function from the MC_F count to the actual voltage applied to the VCO input was obtained.
(attm2)

7) Using the DC calibration of the VCO input voltage to the VCO frequency change (1.75MHz/V elog:993) and the fact that there is a 1.6Hz pole and a 40.8Hz zero between the VCO input connector and the actual input of the VCO chip, the final calibration transfer function from the MC_F count to the frequency change of the PSL (that is twice the frequency change of the VCO within the bandwidth of the FSS) can be obtained (attm3).

8) The analytic form of the calibration TF is, poles at [1.6Hz, 11.42Hz, 11.42Hz] and zeros at [40.8Hz, 113Hz, 113Hz] with the DC gain of 110Hz/cnt.
  1081   Fri Oct 24 10:06:16 2008 YoichiConfigurationIOOMC gain and FSS gain changed
Following the measurements of MC and FSS loop gains, I modified mcup script to set the MC VCO gain to 2dB (it was -4dB before).
I also changed the normal value of the FSS common gain to 7dB. The open loop transfer functions posted in the previous two entries
were measured with those settings.
  1093   Mon Oct 27 11:16:23 2008 AlbertoConfigurationIOOStochMon Calibration
I implemented the calibration for the four channels of the StochMon in the ioo EPICS database. Now the output of those channels, as shown in the medm screen, gives the peak-to-peak amplitude in voltage of each frequency from the RFAMPD at the transmission of the MC, normalized by the DC output from the same photodiode.

Basically the calibration takes into account the following factors:
- two in series RF preamplifiers, currently laying on the PSL table near the RFAMPD, with gains of 19 dB and 17 dB, respectively
and, inside the StochMon blue box:
- a resonant band-pass filter with the following gains h_f(f) for each of the frequencies of interest: 33MHz -39.5 dB; 133MHz -40.8 dB; 166MHz -49.0 dB; 199MHz -45.0 dB
- a power detector that provides an output voltage linearly proportional to the input power in dBm, with a factor alpha of proportionality equal to an average value of -0.0271 V/dBm for all the frequencies

The calibration that relates the output voltage from the PD to the output voltage from the StochMon is then obtained as:

V_pd(f) = sqrt(2*R*P0)/h_f(f) * 10^( (Vo-q)/(20*alpha) )

where R=50ohm, P0=1mW and q=0.772 V, the latest being the offset in the calibration of the power detector (that is its output for a 0 dBm input).
  1125   Mon Nov 10 11:06:09 2008 robHowToIOOmode cleaner locked

I found the mode cleaner unlocked, with (at least) MC1 badly mis-aligned. After checking the coil alignment biases and finding everything there looking copasetic, I checked the trends of SUS{PIT,YAW,POS} and found that both MC1 and MC3 took a step this morning. The problem turned out to be loosed/jiggled cables at the satellite amplifiers for these suspensions. Giving them a good hard push to seat them restored the alignment and the mode cleaner locked right up.
  1143   Tue Nov 18 13:28:08 2008 CarynDAQIOOnew channel for MC drum modes
Alberto has added a channel for the Mode Cleaner drum modes.
C1:IOO-MC_DRUM1
sample rate-2048
chnum-13648
  1144   Tue Nov 18 19:37:23 2008 YoichiUpdateIOOMC1 OSEM signals sign flipped and c1susvme1 restart problem
Around 2PM, MC1 started to swing crazily.
The damping feedback was not working and it was actually exciting the mirror wildly.
It turned out that the sign of the UR and UL OSEM signals flipped at that time.
Restarting c1sosvme fixed the problem.

While I was looking for the cause of the problem, c1susvme1 and c1susvme2 failed several times.
I don't know if it is related to this problem.
Now it is not trivial to restart c1susvme1. It fails to restart if you just power cycle it.
Alberto and I had to connect an LCD and a keyboard to it to see what was going on. After pushing the reset button on the front panel,
I had to press Ctrl+x. Otherwise, the state LED of c1susvme1 stays red and nothing happens.
After Ctrl+x, the boot screen came up but the boot sequence failed and an error message something the following was shown:
"PXE Boot failed, check the cable"
So I swapped the network cable with c1susvme2, which was already up and running.
This time, c1susvme1 started fine and surprisingly, c1susvme2 stayed alive.
Currently, both c1susvme1 and c1susvme2 are up and running with the LAN cables swapped.
We have to check the LAN cables.
  1148   Wed Nov 19 18:12:35 2008 ranaConfigurationIOOnew channel for MC drum modes
I set up the lockin to take the MC Demod Board's Qmon signal, demodulate it at 27.5 kHz, and
put the output into a DAQ channel (I think its either MC_DRUM1 or MC1_TEMPS). However,
the MC_DRUM channel doesn't look like its getting anything in the DTT although it looked fine
on a scope. I used the 'sensitivity' setting of the lockin to make the demodulated signal
large enough but not so large that it would saturate the ADC (+/- 2V).
  1158   Sat Nov 22 10:55:51 2008 CarynConfigurationIOODrum modes Lock-In settings changed
I unhooked the MC Demod Board's Qmon signal from the Lock-In. Set the demodulation frequency to 31.11Hz with 1V amplitude, and
put the output into MC_DRUM1. DTT showed a ~30Hz peak. Dataviewer showed signal with amplitude ~20,000.
Otherwise the settings were as Rana had them: Time Constant-100us,24dB/Sensitivity-200us/Low Noise
Want to check if Lock-In frequency drifts.
  1176   Thu Dec 4 17:42:23 2008 carynUpdateIOOdrum modes observable without excitation
So, the mode cleaner was evidently aligned better and now the drum modes are observable using DTT.
The Lock-In was set to 27.8kHz and the drum mode frequencies were previously observed to be 28.039kHz(MC2), 28.222kHz(MC3) and 28.221kHz(MC1). So, we might expect peaks at ~239Hz,421Hz,422Hz.
Peaks have been observed around the expected frequencies in channel IOO-MC-DRUM1.
Note that it is possible to resolve the separate MC1 and MC3 peaks which are so close together.
(sorry these are pdf's and not png's)
  1179   Fri Dec 5 09:29:59 2008 ranaUpdateIOOdrum modes observable without excitation
Not sure what the y-scale is since there aren't any y axis labels in the plot, but it seems like we
now get an SNR of a ~few with a BW of 0.1 Hz. IN principle, the frequency noise out of the PSL ought
to be limited by the VCO phase noise at these frequencies (sort of) so the broadband MC_F level
is very roughly equal to 20-100 mHz/rHz.

Since dnu = dL*(c/lambda)/L_MC, the thermal peaks have a height of ~10^-15 m_RMS. We (Caryn) should check
that these numbers are true and then see if this is the correct amount of energy for thermally excited
mirror modes.
  1180   Fri Dec 5 14:13:41 2008 ranaSummaryIOOMC trend for the last 4 days
The MC has stayed locked for ~3 days! I just broke it to reset the MZ.
ELOG V3.1.3-