40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 214 of 344  Not logged in ELOG logo
ID Date Author Type Category Subjectdown
  14851   Tue Aug 20 19:05:24 2019 KojiUpdateCDSMC1 (and MC3) troubleshoot

Started the troubleshoot from the MC1 issue. Gautam showed me how to use the fake PD/LED pair to diagnose the satellite box without involving the suspension mechanics.

This revealed that the MC1 has frequent light level glitches which are common for five sensors. This feature does not exist in the test with the MC3 satellite box. I will open and check the MC1 satellite box to find the cause of this common glitches tomorrow. MC1 is currently shutdown and undamped.

BTW, at the MC3 test, i found that J2 of the satellite box (male Dsub) has all the pins too low (or too short?). I brought the box outside and found that the housing of this connector was half broken down. The connector was reassembled and the metal parts of the housing was bent again so that the housing can hold the connector body tightly.

The MC3 satellite box was restored and connected to the cables. As I touched this box, it is still under probation.

Attachment 1: Screenshot_from_2019-08-20_17-26-01.png
Screenshot_from_2019-08-20_17-26-01.png
Attachment 2: Screenshot_from_2019-08-20_17-43-03.png
Screenshot_from_2019-08-20_17-43-03.png
  4274   Fri Feb 11 16:43:09 2011 steveUpdateVIDEOMC1 & 3 video monitor

I set up video monitoring of MC1 and MC3

Attachment 1: P1070415.JPG
P1070415.JPG
  14179   Thu Aug 23 15:26:54 2018 JonUpdateIMCMC/PMC trouble

I tried unsuccessfully to relock the MC this afternoon.

I came in to find it in a trouble state with a huge amount of noise on C1:PSL-FSS_PCDRIVE visible on the projector monitor. Light was reaching the MC but it was unable to lock.

  • I checked the status of the fast machines on the CDS>FE STATUS page. All up.
  • Then I checked the slow machine status. c1iscaux and c1psl were both down. I manually reset both machines. The large noise visible on C1:PSL-FSS_PCDRIVE disappeared.
  • After the reset, light was no longer reaching the MC, which I take to mean the PMC was not locked. On the PSL>PMC page, I blanked the control signal, reenabled it, and attempted to relock by adjusting the servo gain as Gautam had showed me before. The PMC locks were unstable, with each one lasting only a second or so.
  • Next I tried restoring the burt states for c1iscaux and c1psl from a snapshot taken earlier today, before the machine reboots. That did not solve the problem either.
  14180   Thu Aug 23 16:05:24 2018 KojiUpdateIMCMC/PMC trouble

I don't know what had been wrong, but I could lock the PMC as usual.
The IMC got relocked by AutoLocker. I checked the LSC and confirmed at least Y arm could be locked just by turning on the LSC servos.

  14181   Thu Aug 23 16:10:13 2018 not KojiUpdateIMCMC/PMC trouble

Great, thanks!

Quote:

I don't know what had been wrong, but I could lock the PMC as usual.
The IMC got relocked by AutoLocker. I checked the LSC and confirmed at least Y arm could be locked just by turning on the LSC servos.

 

  178   Fri Dec 7 00:02:26 2007 ranaSummaryIOOMC/FSS Frequency Noise
The FSS frequency noise is not very bad.

I compared the MC_F spectra between Hanford and the 40m using DTT and its 'User NDS' option.
After Sam, Jenne, and DavidM installed the new MC Servo some time ago, the MC_F spectrum here
has had some whitening before it goes into the DAQ (on board; same as LLO & LHO). The tuning
coefficient of the VCO is also basically the same between all PSLs since everyone has the same
chip in the VCO driver.

Therefore, at the frequencies where the MC gain is more than ~4, the MC_F signal calibration is
the same here as anywhere. Since its the servo control signal, its basically a measure of the
frequency noise incident on the MC -- its just what comes out of the FSS with the table noise on
top. At low frequencies (< 100 Hz) its a measure of the motion of the MC mirrors.

Above 200 Hz ours is the same as theirs; except for the enormous power line spikes. I think that's
either all on the light. But our acoustics are better and the noise above 1 kHz levels off at the
same flat floor (the phase noise of the VCO) as H1. The huge lump around 100 Hz is the MC2 DAC noise and
it goes down to the H1 levels when we flip on the dewhites. The giant excess from 5-50 Hz is just the fact
that our stacks don't do much until 20-30 Hz.

So we can stop blaming the FSS and move on with life as soon as Tobin gets the ISS back in shape.
Attachment 1: fly.pdf
fly.pdf
  5879   Sat Nov 12 02:00:36 2011 MirkoUpdateAdaptive FilteringMC-F and other signals

Regarding http://nodus.ligo.caltech.edu:8080/40m/5867 and http://nodus.ligo.caltech.edu:8080/40m/5869 :

MC_F signal:

The measurements on p. 5867 were done using the ADC attached to the PEM computer. There was a big difference between the MC_F signal recorded directly after the server board and the signal just before the FSS board as recorded by a PEM channel.
To understand how this happens we measured the signal at different places with a spec. analyzer:

1. WIth a locked MC measuring the signal just before the PEM ADCs (meaning after a 60ft BNC cable)
2. Same position, but unlocked and seemingly dark MC
3. Locked MC, signal just before the FSS box
4. MC_F signal that is usually going into the Pentek Generic board and is recorded in C1:IOO

Compare_signals_at_all_places.png

=> The 60ft BNC cable adds a considerable amount of noise, but doesn't fundamentally change the signal. It is weird that the signal is white from approx. 4Hz on.
Due to Jenne's measurement ( http://nodus.ligo.caltech.edu:8080/40m/5848 ) we know the TF from MCL through PD, mixer Pentek and into C1:IOO looks like this:
OAF-MCL-Delay-9Nov2011.pdf

This is with the double HP from 15Hz on that should be in the Pentek. So one might expect a less white signal going into the FSS board...

 PEM ADCs

The dark noise in the PEM ADCs is actually a factor 10 higher than in the IOO ADCs. Still ok wrt the the seismometers.
We also tried to measure essentially the dark noise of the whole seismometer readout (seismometer box, then ADC). That seemed ok, but is of limited value since the seismometer electronics behave a bit strange when there is no seismometer connected.

Channels_attached_to_the_PEM_ADC.png

Attachment 3: Compare_signals_at_all_places.fig
Attachment 5: Channels_attached_to_the_PEM_ADC.fig
  6228   Thu Jan 26 15:35:23 2012 JenneUpdateIOOMC ~1Hz badness

The mode cleaner is super unhappy.  It's rocking around at ~1Hz.

I turned off the WFS and turned them back on after the MC was locked, and it seems a little happier now.  At least it's not falling out of lock ~1/minute.

  8112   Tue Feb 19 19:55:52 2013 yutaUpdateIOOMC yaw input tuned

[Jenne, Manasa, Yuta]

Since we levelled IMC stack, we had to center beam spots on MC mirrors again.
We did this by steering PSL mirror in yaw (about same amount but opposite direction to what we did in elog #8077)
Residual beam tilt compared with a line through MC1 and 3 actuator nodes is ~ 15 mrad, mainly in yaw.
MCdecenter_19Feb2013.png

  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.
  8275   Tue Mar 12 00:45:50 2013 JenneUpdateIOOMC weird again

~20 minutes ago, maybe right around the time the fb's RAID died (elog 8274) the mode cleaner started behaving weirdly again.  The reflected value is very high, even with the WFS on.  Earlier this evening, I saw that with the WFS off, the MC reflection was high, but the WFS brought it back down to ~0.7 or 0.8.  But now it's ~1.3.  With the WFS off, the reflected value is ~1.1.  I don't really understand.

Also, the PMC has been drifting in alignment in pitch all day, but a lot more later in the day. The PMC trans is 0.800 right now, but it was as high as 0.825 today, and spent most of the day in the high 0.81xxx range today.

I would provide plots, but as mentioned in elog 8274, we can't get data right now.

  8277   Tue Mar 12 11:49:18 2013 JenneUpdateIOOMC weird again

[Manasa, Annalisa, Jenne]

The MC wasn't locking on TEM00 this morning, and the WFS kept pulling the MC out of alignment.  The MC was realigned, and the WFS spots are back to being roughly centered (all of this only touching the MC sliders), but the WFS keep doing bad things.  They're okay, and improve the alignment slightly at first, but as soon as the FM1 integrator comes on, the MC alignment immediately starts going bad, and within a second or so the MC has unlocked.

The WFS are off right now, and we'll keep investigating after LIGOX.

  5982   Tue Nov 22 23:06:13 2011 kiwamuUpdateSUSMC watchdogs

[Rana / Mirko / Kiwamu]

 The watchdogs on the MC suspensions are not working.

Switching off the watchdogs doesn't stop feeding signals to the suspensions.

For tonight, we will leave the controller of the MC suspensions switched off so that the computer won't smash the optics accidentally.

  6010   Fri Nov 25 20:41:48 2011 ranaUpdateSUSMC watchdogs

It seems as if someone was looking into this on Wednesday, but as there's no elog, I think probably not.

Tonight we noticed that, in fact, the watchdogs don't work for any of the corner optics (I confirmed that they do work for the ETMs).

Whether the switch for the coil drivers is enabled or disabled, the voltage monitor on the coil drivers responds to the digital signals.

I tried restarting the c1susaux process, hitting reset on the crate, and also keying the crate. The +5V light on the front of the crate is flickering somewhat, but I'm not sure if this is new or not since the power outage. The next step is to track the Xycom signal from the card over to the coil driver to find where the signal is failing to happen.

Since its not working for any of the corner optics, I suspect the crate and not the cards. If that's the issue this will be a painful fix. We are sort of assuming that this is due to the power outage, but in fact, I cannot tell when the last time was that someone rigorously verified the working of these switches. [

I][B]We had better get ready for upgrading our SLOW controls, Jamie.[/B][/I]

Quote:

[Rana / Mirko / Kiwamu]

 

The watchdogs on the MC suspensions are not working.

 

Switching off the watchdogs doesn't stop feeding signals to the suspensions.

For tonight, we will leave the controller of the MC suspensions switched off so that the computer won't smash the optics accidentally.

 

 

  5891   Tue Nov 15 00:00:15 2011 SureshUpdateIOOMC was realigned to remove beam clipping and to accommodate PZT1 range

[Kiwamu, Suresh]

The MC was realigned to readjust the input beam direction in pitch such that the clipping of the beam at the PSL table reduced and the railing of the PZT1 is avoided.

The current spot positions are given below on the last row:

 

 Date  #### MC1P MC2P MC3P MC1Y MC2Y MC3Y
03Nov2011   0.1354 -0.2522 -0.1383 -1.0893 0.7122 -1.5587
04Nov2011   4.0411 4.4994 3.5564 -1.4170 -0.2606 -1.7109
08Nov2011   4.7341 4.8794  4.3907 1.3542 -3.0508 -1.7167
10Nov2011    1   3.9944 3.7676 6.1001 -1.3058 -3.8087 -1.6418
11Nov2011    1  3.8542 3.6831 3.0418 -0.8383 0.1550 -2.3841
11Nov2011    2    3.6876 2.7429 2.7830 -1.6250 -0.0386 -1.6346
14Nov2011    1 5.9412 2.7658 5.4806 -4.7676 0.7778 2.2053

 

We have quite a lot of decentering in the MC which we must try to remove by parallel transporting the beam in Pitch and Yaw..

At the current settings we might be clipping on the Faraday Isolator as we had estimated that we can allow atmost a 2mm offset in spot positions due to this constraint.

 

 

 

  5615   Tue Oct 4 16:10:45 2011 SureshUpdateComputer Scripts / ProgramsMC was not damping

The MC was not damping earlier this morning around 11:45AM.  The reason was that the INMATRIX on all the three MC1, 2 and 3 were zero.   This was seen earlier when autoburt did not restore this.

This got fixed when I Burt-Restored c1mcsepics.snap

In the afternoon we had to restore c1mcs again to restore the MC_TRANS channels because its INMATRIX was also zero.

Can we do something to make sure this gets done in the autoburt properly?

  8756   Wed Jun 26 13:37:13 2013 JenneUpdateIOOMC very misaligned - put back

Not sure why it was so poorly aligned, since the misalignment "event" happened while we were all away at lunch, but I steered the MC optics until their SUSYAW and SUSPIT values were about the same as they were before they got misaligned.  MC autolocker took over, and things are back to normal.

  9645   Tue Feb 18 14:28:15 2014 JenneUpdateIOOMC unstable - centering spots helped

As we've been seeing a bit lately, the MC will be locked happily for several hours, but then it will start misbehaving. 

Today, I measured the spots on the MC mirrors, and found that the MC2 spot was quite far off in yaw (about -3.5 cm).  I recentered the MC2 spot, and then (with the MCWFS on), moved MC1 and 3 until their WFS outputs were close to zero (they had gone up to 100+).  In the ~15 minutes since doing that, the MC refl signal is not oscillating like it was, the transmission is up, and the MC has not unlocked. 

To reiterate, I did not touch any settings of anything, except the alignment of the MC mirrors to center the MC2 spot, and then offload the WFS.  Next time the MC starts acting up, we should measure the spots, and roughly center them, before messing with any other settings.  Note however, that this is a ~10 minute procedure (including the fact that one spot measurement takes a little less than 5 minutes).  This need not be a several hour endeavour. 

  6291   Thu Feb 16 23:12:55 2012 kiwamuUpdateIOOMC unlocking frequently

The MC became crazy again.

It seems that there were corresponding steps in the OSEM signals. Look at the one-day trend posted below.

MCsteps.png

  16320   Mon Sep 13 09:15:15 2021 PacoUpdateLSCMC unlocked?

Came in at ~ 9 PT this morning to find the IFO "down". The IMC had lost its lock ~ 6 hours before, so at about 03:00 AM. Nothing seemed like the obvious cause; there was no record of increased seismic activity, all suspensions were damped and no watchdog had tripped, and the pressure trends similar to those in recent pressure incidents show nominal behavior (Attachment #1). What happened?

Anyways I simply tried reopening the PSL shutter, and the IMC caught its lock almost immediately. I then locked the arms and everything seems fine for now cool.

Attachment 1: VAC_2021-09-13_09-32-45.png
VAC_2021-09-13_09-32-45.png
  5915   Wed Nov 16 17:40:48 2011 MirkoUpdateIOOMC unlocked and misaligned.

MC fell out of lock and was then quite badly misaligned. Mostly in pitch. I realigned it and it locked ok.

Turns out the MC falls often out of lock when the WFS servo comes on. I think the MC2_Trans history is not cleared on lockloss. I cleared it manually and realigned. Seems fine for now.

  5916   Wed Nov 16 18:14:09 2011 KojiUpdateIOOMC unlocked and misaligned.

Actually, do we need to reset the filter history at every lock loss of the MC?

Those DC offsets were necessary to keep the alignment good just until the MC is unlocked.
So if we keep the history, we can maintain the good alignment.

  5917   Wed Nov 16 20:30:27 2011 not KojiUpdateIOOMC unlocked and misaligned.

Quote:

Actually, do we need to reset the filter history at every lock loss of the MC?

Those DC offsets were necessary to keep the alignment good just until the MC is unlocked.
So if we keep the history, we can maintain the good alignment.

 I suspect the integrators get fed a huge wrong signal on lockloss. Clearing the history on the trans DOFs when the MC was badly aligned gets it nicely aligned again. I switched off the alignment transmission DOFs for now.

  5925   Thu Nov 17 13:58:12 2011 SureshUpdateIOOMC unlocked and misaligned.

Quote:

Quote:

Actually, do we need to reset the filter history at every lock loss of the MC?

Those DC offsets were necessary to keep the alignment good just until the MC is unlocked.
So if we keep the history, we can maintain the good alignment.

 I suspect the integrators get fed a huge wrong signal on lockloss. Clearing the history on the trans DOFs when the MC was badly aligned gets it nicely aligned again. I switched off the alignment transmission DOFs for now.

I have modified the 'mcwfson' and 'mcwfsoff' scripts to include the Clear History step for the MC2_TRANS_PIT and _YAW filters.  

These scripts can be run, by hand, from LOCKMC screen or from the WFS_MASTER screen.  Use the 'Turn WFS ON/OFF' button. 

The mcautolockmain script will now clear history on all ASC filter banks when the MC unlocks.

I have turned on ASC loops on the MC2_TRANS (= alignment transmission DOFs of the above elog) paths.

 

 

  1817   Mon Aug 3 01:08:20 2009 AlbertoUpdatePSLMC unlocked

Friday afternoon the mode cleaner got unlocked. Then some adjustment of the MC1 bias sliders locked it again. The driftmon showed the excursion for pitch and yaw of MC1 becasue it wasn't updated after the change.

Tonight Rana found the MC unlocked and simply touched the sliders to bring the OSEMs back to the driftmon values.

MC1 Yaw remains different from the driftmon. If brught back to htat value, the MC would get unlocked.

More investigation is needed to understand why the MC lock hasn't been stable for the last few days.

 

  1818   Mon Aug 3 12:57:09 2009 AlbertoUpdatePSLMC unlocked

Quote:

Friday afternoon the mode cleaner got unlocked. Then some adjustment of the MC1 bias sliders locked it again. The driftmon showed the excursion for pitch and yaw of MC1 becasue it wasn't updated after the change.

Tonight Rana found the MC unlocked and simply touched the sliders to bring the OSEMs back to the driftmon values.

MC1 Yaw remains different from the driftmon. If brught back to htat value, the MC would get unlocked.

More investigation is needed to understand why the MC lock hasn't been stable for the last few days.

 

 The mode cleaner is still unlocked. I played with the cable at the MC2 satellite to enusre they were all plugged in.

Then I tweaked the the mirrors alignment by the sliders and eventually I could get it locked stably with 1.3 reflection. Then I rebooted C1IOO because the WFS wouldn't engage. After that the cavity wasn't locked anymore. Trying to adjust the mirrors around their position didn't restore the lock.

More work is necessary.

I'll be back on it in a while.

  5933   Thu Nov 17 23:38:40 2011 DenUpdateIOOMC unlocked

MC is unlocked to measure the free swing of the MC mirrors with the local sensors.

Autolocker is disabled.

  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.
Attachment 1: MC-unlock.png
MC-unlock.png
  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.
Attachment 1: MC-Unlock.png
MC-Unlock.png
  9677   Wed Feb 26 02:20:35 2014 JenneUpdateIOOMC unhappy

I've asked Manasa and Q to have a look at the MC in the morning.  Rana and I have found it to be slightly uncooperative in relocking after a lockloss.

The concern is that we may be (by actuating on things during lock, or during a lockloss) ringing up some mode, maybe a violin mode in one of the suspensions, maybe a PZT mode of some sort.  If we are, and then we have to push with the PZT on the laser to lock things, that may be why the laser's PZT RMS (on the FSS screen) is so often above 1Vrms.  When we close the PSL shutter, the rms is low, like 0.6 or something, and it stays flat.  As we've all see many a' time, the red trace on the top projector plot is pretty erratic throughout the day when the MC is locked or trying to lock.

We have found that just letting the autolocker go doesn't seem to work very well, and sometimes the MC just doesn't want to re-lock.  Closing the PSL shutter or disabling the autolocker for a few minutes (5ish) doesn't do anything, but leaving it closed for a long time (30 ish minutes) helps a lot.  The MC  will relock immediately after a nice long break. 

 

  1812   Thu Jul 30 03:10:18 2009 robUpdateIOOMC tweaked further

I tilted the periscope beam and aligned the MC.  Now the spot at the Faraday entrance is near the center of the aperture in up/down space.  The arm powers are only going up to ~0.8, though.  Maybe we should try a little bit of left/right. 

I looked at the IP POS spot with a viewer card, and it looked round, so no obvious egregious clipping in the Faraday.  Someone might take a picture with one of the GigE camera and get us a beam profile there.

We no longer have an MC1 and MC3 camera view.

I can see a bright scatterer that can be seen from the east viewport of the BSC, but I can't tell what it is.  It could be a ghost beam. 

It would be nice to get an image looking into the north viewport of the IOO chamber.  I can't see in there because the BS oplev table is in the way. 

  9981   Wed May 21 11:11:01 2014 manasaUpdateIOOMC tuned

I found MC unlocked this morning. I looked at the 2 day trend of the MC suspensions and found MC2 suspensions have been misaligned.

I used Rana's ezcaservo trick to recover MC lock. This brought the MC_REFL down to 0.7 counts. I did the rest of the alignment by moving the MC2 suspension sliders only. MC_REFL is down to 0.45-0.5 counts and TRANS_SUM is at ~16300.

Also, I found the WFS servo was left turned OFF. I re-enabled them as well.

Attachment 1: MC_SUS2days.png
MC_SUS2days.png
  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.
Attachment 1: g.png
g.png
  3026   Tue Jun 1 16:29:51 2010 AlbertoUpdateIOOMC transmitted beam aligned to the Faraday; next things to do

We moved the MC-trans pick-off mirror (= the beam splitter between the input of the Faraday and the steering mirror located right after MC3). Now the beam goes through the Farady without getting clipped.

This is the list of the things that have to be done next:

  1. take pictures of the beam spot just before and after the Faraday
  2. lock down to the table the MCTrans pickoff mirror with its screws
  3. measure the beam profile after the first MC telescope mirror (MMT1)
  4. remove Jenne's extra steering mirror from the MC table
  5. re-level the MC table with the bubble level
  6. align the MC-trans beam to its photodiode on the PSL table
  7. align the REFL beam to its photodiode on the AP table
  5383   Sat Sep 10 20:30:01 2011 ranaUpdateIOOMC trans re-aligned / MC2 shifted mysteriously / MC2 re-aligned

MCdecenter.png

I re-aligned the beam onto the MC TRANS QPD since Kiwamu had centered the spots on the mirrors. However, I then inspected the MC2F camera. After coming back into the control room I noticed that the MC transmission had gone down by 50% and that the MC2 OSEMs showed a large step. My guess is that somehow the opening and closing of the can shifted the suspension. So I adjusted the MC2 alignment biases to recover the transmitted power (its now ~50000 instead of the ~33000 from Friday).

  7122   Wed Aug 8 19:54:06 2012 ManasaConfigurationIOOMC trans optics configured

Jan and I wanted to measure the ringdown at the IMC. Since the QPD at the MC trans is not fast enough for ringdown measurements, we decided to install a pickoff to include a faster PD while not disturbing much of the current MC trans configuration. The initial configuration had very little space to accommodate the pickoff. So the collimating lens along with the QPD were moved 2 inches closer to the incoming beam. A 50-50 BS was put in front of the QPD and the steering mirror was moved behind to reflect MC trans output to the new PD. The current configuration is shown below with the MC autolocker threshold mentioned in Jenne's elog

Pic1.png

The hunt for a faster PD wasn't satisfactory and we found a couple of PDs that were good for measurements actually didn't work after installing them. The one currently installed is also not satisfactorily fast enough for ringdown measurements. We'll hunt for faster PDs at Bridge tomorrow and replace PDA400. Also the IMC unlocked from time to time....may be we were noisy and didn't master the 'interferometer walk' very well.

 

 

  7126   Wed Aug 8 22:12:30 2012 ranaConfigurationIOOMC trans optics configured

  The PDA255 is a good ringdown detector - Steve can find one in the 40m if you ask him nicely.

  7127   Wed Aug 8 22:17:43 2012 ManasaConfigurationIOOMC trans optics configured

Quote:

  The PDA255 is a good ringdown detector - Steve can find one in the 40m if you ask him nicely.

 We found a PDA255 but it doesn't seem to work. I am not sure if that is one you are mentioning...but I'll ask Steve tomorrow!

  7140   Fri Aug 10 09:54:51 2012 ManasaConfigurationIOOMC trans optics configured

Quote:

Quote:

  The PDA255 is a good ringdown detector - Steve can find one in the 40m if you ask him nicely.

 We found a PDA255 but it doesn't seem to work. I am not sure if that is one you are mentioning...but I'll ask Steve tomorrow!

 I double checked the PDA255 found at the 40m and it is broken/bad. Also there was no success hunting PDs at Bridge. So the MC trans is still in the same configuration. Nothing has changed. I'll try doing ringdown measurements with PDA400 today.

  7142   Fri Aug 10 11:05:33 2012 jamieConfigurationIOOMC trans optics configured

Quote:

Quote:

Quote:

  The PDA255 is a good ringdown detector - Steve can find one in the 40m if you ask him nicely.

 We found a PDA255 but it doesn't seem to work. I am not sure if that is one you are mentioning...but I'll ask Steve tomorrow!

 I double checked the PDA255 found at the 40m and it is broken/bad. Also there was no success hunting PDs at Bridge. So the MC trans is still in the same configuration. Nothing has changed. I'll try doing ringdown measurements with PDA400 today.

Can you explain more what "broken/bad" means?  Is there no signal?  Is it noisy?  Glitch?  etc.

  7144   Fri Aug 10 15:05:52 2012 ManasaConfigurationIOOMC trans optics configured

Quote:

Quote:

Quote:

Quote:

  The PDA255 is a good ringdown detector - Steve can find one in the 40m if you ask him nicely.

 We found a PDA255 but it doesn't seem to work. I am not sure if that is one you are mentioning...but I'll ask Steve tomorrow!

 I double checked the PDA255 found at the 40m and it is broken/bad. Also there was no success hunting PDs at Bridge. So the MC trans is still in the same configuration. Nothing has changed. I'll try doing ringdown measurements with PDA400 today.

Can you explain more what "broken/bad" means?  Is there no signal?  Is it noisy?  Glitch?  etc.

 The PD saturates the oscilloscope just by switching on the power; with no real signal at all. But Steve helped locating a PD that is not being used at the AP table. So I will check it and replace the current one if it works!

  7206   Thu Aug 16 17:28:51 2012 ManasaConfigurationIOOMC trans optics configured

Quote:

Quote:

Quote:

Quote:

Quote:

  The PDA255 is a good ringdown detector - Steve can find one in the 40m if you ask him nicely.

 We found a PDA255 but it doesn't seem to work. I am not sure if that is one you are mentioning...but I'll ask Steve tomorrow!

 I double checked the PDA255 found at the 40m and it is broken/bad. Also there was no success hunting PDs at Bridge. So the MC trans is still in the same configuration. Nothing has changed. I'll try doing ringdown measurements with PDA400 today.

Can you explain more what "broken/bad" means?  Is there no signal?  Is it noisy?  Glitch?  etc.

 The PD saturates the oscilloscope just by switching on the power; with no real signal at all. But Steve helped locating a PD that is not being used at the AP table. So I will check it and replace the current one if it works!

Koji opened up the PD and found that the screw connecting the PD to the pole was doing an additional job as well; connecting the power cable to the PD output in the inside. The PD is now fixed! Yippie...we have two PDA255 s at 40m now!!

  14570   Thu Apr 25 01:03:29 2019 gautamUpdatePSLMC trans is ~1000 cts (~7%) lower than usual

When dialing up the current, I went up to 2.01 A on the front panel display, which is what I remember it being. The label on the controller is from when the laser was still putting out 2W, and says the pump current should be 2.1 A. Anyhow, the MC transmission is ~7% lower now (14500 cts compared to the usual 15000-15500 cts), even after tweaking the PMC alignment to minimize PMC REFL. Potentially there is less power coming out of the NPRO. I will measure it at the window tomorrow with a power meter.

  6096   Fri Dec 9 15:49:24 2011 JenneUpdateIOOMC trans is way down

I was looking at the trends from the RAMmon, since I did the EOM alignment yesterday, and wanted to compare them to the MC trans, just to make sure the MC was locked during the times I'm examining.  I was dismayed to discover that the MC has lost its oomph, starting around 11:30 this morning.  Den was the only person in the lab to my knowledge at that time, and he claims that he didn't touch the MC until well after lunch.  As you can see from the 8 hour trend attached, we went from normal ~26000 counts to ~15000, and we're slowly decaying from there.

MC refl looks pretty bad on the camera, particularly in YAW.  Investigations are beginning now....

Edit, ~10min later...  I enabled the WFS (I don't know why they were off...when the MC fell out of lock and relocked itself, the WFS didn't come on), and things went basically back to how they should be.  However, the sans-WFS alignment is still totally crappy, so the PSL beam probably needs to be aligned to the MC.  I don't really want to touch the alignment though without an okay from Kiwamu, so I'll wait for him to come in and confirm that he's happy with the current MC.

Attachment 1: MCtrans_9Dec2011.png
MCtrans_9Dec2011.png
  6098   Fri Dec 9 17:15:29 2011 JenneUpdateIOOMC trans is way down

Quote:

I was looking at the trends from the RAMmon, since I did the EOM alignment yesterday, and wanted to compare them to the MC trans, just to make sure the MC was locked during the times I'm examining.  I was dismayed to discover that the MC has lost its oomph, starting around 11:30 this morning.  Den was the only person in the lab to my knowledge at that time, and he claims that he didn't touch the MC until well after lunch.  As you can see from the 8 hour trend attached, we went from normal ~26000 counts to ~15000, and we're slowly decaying from there.

MC refl looks pretty bad on the camera, particularly in YAW.  Investigations are beginning now....

Edit, ~10min later...  I enabled the WFS (I don't know why they were off...when the MC fell out of lock and relocked itself, the WFS didn't come on), and things went basically back to how they should be.  However, the sans-WFS alignment is still totally crappy, so the PSL beam probably needs to be aligned to the MC.  I don't really want to touch the alignment though without an okay from Kiwamu, so I'll wait for him to come in and confirm that he's happy with the current MC.

 Kiwamu and I discussed, and looking at the AS camera with the PRM and SRM misaligned, but MCWFS engaged, things look good.  This means that it's probably the MC that has drifted, and we want to align the MC back to the PSL beam.

  6251   Fri Feb 3 19:54:21 2012 ranaConfigurationIOOMC trans awry

As usual, I noticed several bad things within 30 seconds of sitting in front of the workstation. Today its that there are OFF or missing filters on the MC TRANS.

is this the normal state? Screenshot attached.

Attachment 1: mctrans.png
mctrans.png
  8317   Wed Mar 20 14:52:09 2013 ManasaUpdateSAFETYMC trans RFPD missing

PDA255 at the MC transmission end is missing and whoever had removed it earlier has left the beam undamped.

It could be less than a mW beam...but it is still not acceptable to leave it that way.

On the other note, I have cleared up the unwanted optics from the same table.

MC.png

  1124   Fri Nov 7 18:38:19 2008 AlbertoDAQPSLMC temperature sensor hooked up
Alberto, Rana,
we found that the computer handling the signals from ICS-110B was C1IOVME so we restarted it. We changed the name of the channel to C1:PEM_TEMPS and the number to 16349. We tracked it up to the J14 connector of the DAQ.
We also observed the strange thing that both of the differential pairs on J13 are read by the channle. Also, if you connect a 50 Ohm terminator to one of the pairs, the signal even get amplified.

(The name of the channel is PEM-MC1_TEMPS)
  1114   Tue Nov 4 17:58:42 2008 AlbertoDAQPSLMC temperature sensor
I added a channel for the temperature sensor on the MC1/MC3 chamber: C1:PSL-MC_TEMP_SEN.
To do that I had to reboot the frame builder. The slow servo of the FSS had to get restarted, the reference cavity locked and so the PMC and MZ.
  1228   Wed Jan 14 15:53:32 2009 steveDAQPSLMC temperature sensor

Quote:
I added a channel for the temperature sensor on the MC1/MC3 chamber: C1:PSL-MC_TEMP_SEN.
To do that I had to reboot the frame builder. The slow servo of the FSS had to get restarted, the reference cavity locked and so the PMC and MZ.


Where is this channel?
ELOG V3.1.3-