40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 247 of 341  Not logged in ELOG logo
ID Date Author Type Category Subjectup
  16551   Thu Jan 6 17:16:51 2022 YehonathanUpdateBHDUsing Peek screws/nuts

There were several cases where the long EQ stops didn't perform as expected.

In one type of case, we used a counterweight at the front of the adapter but not in the back leaving a recess where the lower back EQ stop should touch.

In the other type, a recess in the thick optics adapter prevented the upper EQ stop from touching the adapter. In the first thick optic, the screw was screw barely scratched the recess' corner. In the second case, it didn't touch it at all.

In the last group meeting, we discussed using Peek screws (made out of plastic) to prevent metal on metal bumping when the EQ can touch the adapter and Peek nuts when it doesn't to increase its impact area.

Mcmaster has 1.5" long 1/4-20 screws (part number 98885A131) that will fit well in the OSEM plates. We can order 20 of those.

The biggest Peek nuts on Mcmaster however are not big enough (7/16" wide) to cover the entire bottom recess area which is 0.5" wide (they are good enough for the top recess area in the thick adapter optic design). Koji suggested that we can use a big Peek washer for that purpose that can be held between nuts. We should then order 10 Peek nuts (98886A813) and 1 package of 10 Peek washers (0.63" OD) (93785A600).

  13131   Fri Jul 21 19:44:58 2017 NaomiSummaryComputer Scripts / ProgramsUsing PyKat to run Finesse

I have been working on using PyKat to run Finesse. There appear to be several ways to run an equivalent simulation using Finesse:

1: .kat only

Run a .kat file directly from the terminal. For example, if in the directory containing the Finesse kat.ini file, run the command ‘./kat file.kat’. This method does not use PyKat.

To edit the simulation using this method, one must directly edit the .kat file. This is not ideal, as all parameters must be hard-coded, and there is no looping method for duplicate commands.


Both of the following methods use PyKat in some manner. To run Finesse using PyKat from a .py file, the command ‘from pykat import finesse’ should be included. In addition, two environment variables must be defined:

  • FINESSE_DIR': directory containing ‘kat’ executable
  • KATINI’: location and name of kat.ini file

Within a .py file running PyKat, the kat object contains all of the optical components and their states. To create a kat object, we use the command:

kat = finesse.kat()


2: .kat + .py

To load Finesse commands from a .kat file, we can use the command loadKatFile(). For example, using the kat object as defined above:

kat.loadKatFile(‘file.kat’)

The kat object now contains any components defined in the .kat file. The states of these components can be altered using PyKat. For example, if in the .kat file, we defined a mirror named ‘ITM’, with R = 0.9, T = 0.1, phi = 0, and with nodes 1 and 2 to its left and right, respectively, using the Finesse command

m ITM 0.9 0.1 0 n1 n2

we can now alter the state of the mirror using a PyKat command such as

kat.ITM.phi = 30

which changes the ‘phi’ property of the mirror to 30 degrees. Once all alterations to objects are made, we can run Finesse using the command

out = kat.run()

which stores the output of the Finesse simulation in the variable out.


3: .py only

We can also run a Finesse simulation without any .kat file. There are two ways to define Finesse objects within a .py file.

- Parse a string containing Finesse commands, as would be found in a .kat file, using the command parseCommands(). For example,

            kat.parseCommands(‘m ITM 0.9 0.1 0 n1 n2’)

defines the same mirror as above. This object can now be altered using pyKat in the same manner as above.

- Define an object using the classes defined in PyKat. For example, to define the same ITM mirror, we can use:

ITM = mirror(‘ITM’, ‘n1’, ‘n2’, 0.9, 0.1, 0)

kat.add(ITM)

The syntax for these classes can be found in the files included in the PyKat package named ‘commands.py’, ‘detectors.py’, and ‘components.py’.

We can also run Finesse commands (rather than just defining components) using their respective classes. These must also be added to the kat object. For example:

x = xaxis(‘lin’, [‘-4M’, ‘4M’], ‘f’, 1000, ‘laser’)

kat.add(x)

This runs the command ‘xaxis’, which sets the x-axis of the output data to run from freq = -4 MHz to 4 MHz, in 1000 steps. This is equivalent to the following Finesse command:

xaxis laser f lin -4M 4M 1000

In theory, we should be able to use PyKat to run any Finesse command. However, not all Finesse commands appear to be defined in PyKat; one example is the Finesse command ‘yaxis’, which I cannot locate in PyKat. In addition, I have had difficulty running some commands such as ‘cav’ and ‘pd’, despite following their class definitions in the PyKat files. However, these commands can still be easily run in PyKat using parseCommands().

  6265   Thu Feb 9 20:01:02 2012 ranaSummaryElectronicsUsing RF LP filters as dispersion units for the MFD

 WE currently use long cables to give us the dispersion that we want for the MFD. A cable gives a long delay - both the phase delay and the group delay.

But we only need the dispersion (group delay). We can get this by just using a very sharp low pass filter and having the corner be above the frequency that we have the beat signal.

For example, the MiniCircuits SLP-200+ has got a corner frequency of 200 MHz and a group delay of ~10 ns (like a 3 m vacuum delay). So we would have to use 10 of these to get the delay we now get. The passband attenuation is only 0.5 dB, so we would lose 5 dB. The cost is $35 ea. We have a few on the shelf.

OTOH, if we tune the beat frequency down to 30 MHz, we can use the SLP-30 which has a group delay of 30 ns around 30 MHz. That's like 9m at light speed. We could easily get a nice result by just using 4 or 5 SLP in series.

So why is Kiwamu using cables?? And how should we really choose the beat note frequency??

  1598   Mon May 18 02:18:17 2009 ranaSummarySEIUsing STACIS w/ a good position sensor
WE turned off STACIS a few years ago because we noticed that it was causing noise below a few Hz and making
the overall velocity between the ends higher than with them off. I'm pretty sure they were causing noise
because they use little geophones which are noisy. Below ~0.2 Hz the horizontal geophones are also probably
limited by tilt-horizontal coupling.

Another concept (based on discussion with Brian Lantz and Matt Evans) is to instead put a good position sensor
between the ground and then blue support beam. Since the the STACIS rubber acts like a Q~2 passive resonance at
20 Hz, the whole seismic system (including the blue beams, in-vac tubes, and internal stack) act like a proof
mass of a seismometer.

So, in principle, if we use a very good position sensor and feedback to the STACIS piezo actuators, we can cancel
the ground motion before it enters the stacks. The initial LIGO OSEMs have a noise of 10^-10 m/rHz above 10 Hz
and going up like 1/f below 10 Hz. The AdvLIGO BOSEMs have a noise of ~2x better. Even better, however, are the
UK's EUCLID interferometric OSEMs (developed by Stuart Aston and Clive Speake).

In the attached plot, I show what we can get if we use these EUCLIDs make a ~60 Hz BW feedback loop w/ STACIS.

BLACK   - raw ground motion measured by the Guralp
MAGENTA - motion after passive STACIS (20 Hz harmonic oscillator with a Q~2)
GREEN   - difference between ground and top of STACIS
YELLOW  - EUCLID noise in air
BLUE    - STACIS top motion with loop on (60 Hz UGF, 1/f^2 below 30 Hz)
CYAN    - same as BLUE, w/ 10x lower noise sensor

One of the SURF projects this summer is to put together a couple different sensors like EUCLID to understand the noise.
Attachment 1: stacis40.png
stacis40.png
  17031   Mon Jul 25 09:37:39 2022 DeekshaUpdateElectronicsUsing the DFD to measure PZT TF

The DFD was setup to measure the change in beatnote when excited. A long long (128in) cable goes from the SR785 near the DFD all the way to the Xend AUX which it accordingly excites and the DFD is monitored by the oscilloscope at the other end. This was completed on Friday. The wires and stand have been moved to the side but the setup is still a bit chaotic. As of writing this post, there is still atleast some minor issue with the setup as we aren't getting the expected output. 

[I will shortly update this elog with more pictures]

Edit: the SR785 was replaced by the AG 4395, and pictures added

 

Attachment 1: ag4395.jpeg
ag4395.jpeg
Attachment 2: dfd.jpeg
dfd.jpeg
  16926   Thu Jun 16 19:49:48 2022 CiciUpdateGeneralUsing the SR785

[Deeksha, Cici]

We used a python script to collect data from the SR785 remotely. The SR785 is now connected to the wifi network via Ethernet port 7.

  640   Mon Jul 7 13:58:37 2008 Eric, josephbDAQPEMUsing unused PEM channels to test camera code
Joe and I have taken control of the EPICS channels C1:PEM-Stacis_EEEX_geo and C1:PEM-Stacis_EEEY_geo since we heard that they are no longer in use.  We are currently 
using them to test the ability for the Snap camera code to read and write from EPICS channels.  Thus, the information being written to these channels is completely unrelated
to their names or previous use.  This is only temporary; we'll create our own channels for the camera code shortly (probably within the next couple of days).

- Eric
  8988   Thu Aug 8 18:47:41 2013 SujanSummaryPEMUsing weiner filters for subtracting signals MC_L and GUR2_X

I used MC_L signal from the Mode Cleaner as the desired signal with GUR2_X as witness signals. I observed good subtraction where coherence is high. But there was noise added in other frequency bands. I am not sure how to avoid that.

Please find attached documents that contains relevant plots.

Attachment 1: Results.zip
  1716   Thu Jul 2 17:37:36 2009 steveUpdateVACV1 interlock test

Joe, Alberto and Steve

We tested gate valve V1 interlock by :

1, decelerated rotation by brake from maglev controller unit.

2, turned maglev  controller off from controller unit.

3, unpluged 220VAC plug from wall socket

None of the above action triggered V1 to close. This needs to be corrected in the future.

The MEDM monitor screen of maglev indicated the correct condition changes.

 

 

  1691   Tue Jun 23 15:19:42 2009 steveConfigurationVACV1 is open

Quote:

The Maglev is running for 10 days with V1 closed.  The pressure at the RGA-region is  at 2e-9 torr on CC4 cold cathode gauge.

Valve VM2 to Rga-only was opened 6 days ago. The foreline pressure is still 2.2e-6 torr with small Varian turbo ~10 l/s on cc2

Daily scans show small improvement in large amu 32 Oxygen and large amu 16, 17 and 18 H20 water peaks.

Argon calibration valve is leaking on our Ar cylinder and it is constant.

 

The good news is that there are no fragmented hydrocarbons in the spectrum.

The Maglev is soaked with water. It was seating in the 40m for 4 years with viton o-ring seals

However I can not explan the large oxygen peak, either Rai Weiss can not.

 

The Maglev scans are indicating cleanliness and water. I'm ready to open V1 to the IFO

 V1 valve is open to IFO now. V1 interlock will be tested tomorrow.

Valve configuration: VAC NORMAL with CRYO and Maglev are both pumping on the IFO

Attachment 1: V1_opennmag.jpg
V1_opennmag.jpg
  16607   Thu Jan 20 17:34:07 2022 KojiUpdateBHDV6-704/705 Mirror now @Downs

The PR2 candidate V6-704/705 mirrors (Qty2) are now @Downs. Camille picked them up for the measurements.

To identify the mirrors, I labeled them (on the box) as M1 and M2. Also the HR side was checked to be the side pointed by an arrow mark on the barrel. e.g. Attachment 1 shows the HR side up

Attachment 1: PXL_20220120_225248265_2.jpg
PXL_20220120_225248265_2.jpg
Attachment 2: PXL_20220120_225309361_2.jpg
PXL_20220120_225309361_2.jpg
  16612   Fri Jan 21 14:51:00 2022 KojiUpdateBHDV6-704/705 Mirror now @Downs

Camille@Downs measured the surface of these M1 and M2 using Zygo.

Result of the ROC measurements:M1: ROC=2076m (convex)M2: ROC=2118m (convex)
Here are screenshots. One file shows the entire surface and the other shows the central 30mm.
Attachment 1: M1.PNG
M1.PNG
Attachment 2: M1_30mm.PNG
M1_30mm.PNG
Attachment 3: M2.PNG
M2.PNG
Attachment 4: M2_30mm.PNG
M2_30mm.PNG
  2592   Thu Feb 11 18:53:57 2010 steveConfigurationVACVAC NORMAL is back

Quote:

Joe and Alex are working on the computers. Our vacuum system is temporary "All off" condition: meaning all valves are closed, so there is no pumping. cc1 = 1.6e-6 Torr

 Designated vacuum control lap top is trouble some to use. Joe finally fixed it and I switched valve configuration back to vacuum normal. Shutter is open

  10584   Wed Oct 8 08:46:57 2014 SteveUpdateVACVAT valves actuator lubricant

Quote:

 Pump  spool valves V5, V4, V3 sweating a lot. VM3 and VC2 not so much.

They are VAT valves F28-62887-03, 11, 14 and so on ~15-16 years old.

 I'm speculating that some plastic is aging-braking down at the atmospheric-pneumatic side of valves.
The vacuum side is not effected, according to vacuum pressure readings.

May be some condensation from the small turbos? No

I'm looking for an identical valve to examine, but I can not find one.

We are using industrial grade 99.96% Nitrogen to actuate these valves.

Valves are not effected are  dry: VA6, V6, V7 and all annuloses.

 

VAT's answer:

Yes, our engineers are aware of this issue.  They say:

The pneumatic actuator needs lubricant as the O-ring (Viton) slides in the cylinder. Without grease the O-ring would be abraded and leaking after only a relatively few cycles.  The lubricant used in our pneumatic actuators is an emulsion of oil and Teflon flakes.   Vibration, many cycles and sometimes high temperature lead to the separation of the oil and Teflon.   That is apparently the issue you are seeing.

VAT is and has been testing and qualifying new lubricants, and this is one of the factors we are always looking to improve.  The formula we used 15 years ago in these valves seems to have performed reasonable  well.  Our formula today should perform even better.

We realize this explanation does not help you with these existing valves, but 15 years of service is not too bad is it? 

Steve -NOTE:bonnet seal is metal so there is no way this oil can get into our vacuum ( only if the bellow leaks )

  1524   Mon Apr 27 18:31:44 2009 steveConfigurationVACVC1 closed

CC1 5e-7 Torr,  VC1 closed at 18:25,  IFO is not pumped, RGA is in bg-mode

 

  1525   Tue Apr 28 01:48:45 2009 peteConfigurationVACVC1 open

At about 1am or so Yoichi and I opened VC1.  CC1 had fallen to about 5e-5 torr.

  1593   Sun May 17 14:35:52 2009 YoichiUpdateVACVC1 opened
I found the VC1 was closed and the pressure was 4.5e-3 torr.
I tweaked the optical sensor (cryopump temperature), and opened VC1.
  10227   Thu Jul 17 16:07:34 2014 Emily UpdateElectronicsVCO Driver

I took back he VCO driver that Reetika brought over to the 40m from the PSL lab.  

  3562   Mon Sep 13 00:19:32 2010 ranaUpdate VCO Driver Output power v. slider control voltage

I measured the RF power output of the VCO Driver box as a function of slider value. I measured using the Gigatronics Handheld power meter and connected to the AOM side of the cable after the white Pasternak DC block.

* at low power levels, I believe the waveform is too crappy to get an accurate reading - that's probably why it looks non-monotonic.

* the meter has a sticker label on it saying 'max +20 dBm'. I went above +20 dBm, but I wonder if maybe the thing isn't linear up there...

Attachment 1: vco.png
vco.png
  10221   Wed Jul 16 21:24:41 2014 ReetikaUpdateElectronicsVCO Driver inside 40m

  

I found the VCO driver, that Rana asked me to locate, inside the 40m. I already have one VCO from PSL lab. Now, I have kept both of them inside the 40m lab(one on the cart in the side of the Y-arm and the other near the X-arm electronics table).

  4281   Mon Feb 14 00:39:21 2011 rana, sureshUpdateElectronicsVCO Frequency Noise Measurement with the MFD

We hooked up the VCO Driver output to the MFD. We adjusted the levels with attenuators to match up to the Level 7 mixer that's being used.

The mixer the input to the SR560 is going in to the XARM_COARSE_OUT channel and the SR560 (AC coupled, Low Noise, G=1000, LP@1kHz) 600 Ohm output goes into XARM_FINE_OUT.

We calibrated these channels by putting in a 10 mVpp sine wave at 0.22 Hz into the Wideband Input of the VCO Driver box (which has been calibrated to have 1.75 MHz/V for f < 1.6 Hz). This should correspond to 17.5 kHz_pp.

To increase the sensitivity, we also added a 140 ft. BNC cable to the setup. We also added some extra short cable to make the overall phase shift be ~90 deg and zero out the mixer output.

I used the time series data in DTT to then calibrate the channels by changing the GAIN field in their filter modules. So now the DAQ channels are both calibrated as 1 count/Hz.

 

  4318   Thu Feb 17 23:11:40 2011 ranaUpdateElectronicsVCO Frequency Noise Measurement with the MFD

This is the 140 ft. MFD measurement of the VCO phase noise. It is open loop and so should be a good measurement. The RMS is 30 Hz integrated down to 2 mHz.

I don't know why this doesn't agree with Suresh's measurements of the same thing which uses the PLL feedback method.

In BLUE, I also plot the frequency noise measured by using a Stanford DS345 30 MHz func. generator. I think that this is actually the noise of the FD (i.e. the SR560 preamp) and not the DS345. Mainly, it just tells you that the PINK VCO noise measurement is a real measurement.

I calibrated it by putting in a 5 kHz_pp triangle wave on the sweep of the DS345 and counting the counts in DV.

Attachment 1: vco.png
vco.png
  4248   Fri Feb 4 11:10:27 2011 SureshUpdateGreen LockingVCO PLL Frequency noise

This measurement pertains to the BL2002 VCO PLL unit.

 

Our goal is to measure the frequency fluctuations introduced by the VCO. 

 

First the VCO calibration was checked.  It is -1.75 MHz per volt.  The calibration data is below:

VCO_calibration.png

 

 

 

Next we measured the Transfer function between points A and B  in the diagram below using the Stanford Research System's SR785.  This measurement was done with loop opened just after the 1.9MHz LPF and with the loop closed.

VCO_PLL_Servo.png

 

The TF[open] / TF [closed ] gave the total gain in the loop.  As shown below:

VCO_Transfer_Functions.png

Green curve is the Transfer Function with the loop open and the red with that of the loop closed.

Gain Shown below is the quotient TF[open]/TF[closed]

 

VCO_Gain.png

 

 c) As can be seen from the graph above the loop gain is >>1 over 0.1 to 300Hz.  And hence the frequency noise of the VCO is just the product of the voltage noise and the VCO calibration factor over this range,

d) the noise power at the point B was measured and multiplied by the VCO calibration  factor to yield dF(rms)/rtHz:

VCO_PLL_Freq_Noise.png

The green line with dots are the data

The blue line is the rms frequency fluctuation.

This corresponds to a arm length fluctuation of about 20pm.

 

 

  14669   Thu Jun 13 15:08:31 2019 MilindUpdateElectronicsVCO pickup by Rich

Rich dropped by at around 3:00 PM today and picked up the VCO in Attachment #1 and left the note in Attachment #2 on Gautam's desk with the promise of bringing it back soon.

Attachment 1: WhatsApp_Image_2019-06-13_at_15.06.57.jpeg
WhatsApp_Image_2019-06-13_at_15.06.57.jpeg
Attachment 2: WhatsApp_Image_2019-06-13_at_15.06.57(1).jpeg
WhatsApp_Image_2019-06-13_at_15.06.57(1).jpeg
  9568   Wed Jan 22 20:00:41 2014 JenneUpdateGeneralVENT GO!

Steve, please begin the vent!!

[EricQ, Jenne]

We have followed the pre-vent checklist, and done everything except check the jam nuts (which Steve can do in the morning).

We are ready to vent, so Steve, please begin bringing us up to atmosphere first thing in the morning.

Here is a copy of the list, from the wiki:

 

 

  • Center all oplevs/IPPOS/IPANG
  • Align the arm cavities for IR and align the green lasers to the arms. (Green powers were both ~0.8.  We only touched the Xend PZTs remotely, did not touch Yend).
  • Make a record of the MC pointing
  • Align the beam at the PSL angle and position QPDs (Did not need doing, left QPDs as-is so we keep our long-term trend.)
  • Reduce input power by touching wave plate on the PSL table BEFORE THE PMC.  (HWP was at 269degrees, now at 3 hundred something to make power just before PSL shutter 90mW)
  • Replace 10% BS before MC REFL PD with Y1 mirror and lock MC at low power.
  • Close shutter of PSL-IR and green shutters at the ends
  • Make sure the jam nuts are protecting bellows
  •  

     

    Attachment 1: IFOstatus_lowPower_preVent.png
    IFOstatus_lowPower_preVent.png
      7300   Tue Aug 28 17:59:03 2012 JenneUpdateVACVENT: GO!

    I have turned of the high voltage supplies for PZT1 and PZT2.  The OMC PZT high voltage supplies were already off, since we aren't really using them currently.

    I have closed the PSL shutter, but have not put in a manual extra beam dump yet.

    All systems go for vent!

    Steve - EricQ will be here around 8am to help with the vent.

      13702   Mon Mar 26 09:25:18 2018 SteveUpdateVACVM1 opened

    CC1 old MKS cold cathode gauge randomly turns on- off. This makes software interlock close VM1 to protect RGA  So the closed off RGA region pressure goes up and the result is distorted RGA scan.

    CC1 MKS gauge is disconnected and VM1 opened. This reminds me that we should connect our interlocks to CC1 Hornet Pressure gauge.

    Quote:

    Pumpdown 80 at 511 days and pd80b at 218 days

    Valve configuration:  special vacuum normal, annuloses are not pumped at 3 Torr, IFO pressure 7.4e-6 Torr at vac envelope temp 22 +- 1C degrres

     

     

    Attachment 1: CC4VM1.png
    CC4VM1.png
      13709   Tue Mar 27 08:58:21 2018 SteveUpdateVACVM1 opened.......scan fine

     

    Quote:

    CC1 old MKS cold cathode gauge randomly turns on- off. This makes software interlock close VM1 to protect RGA  So the closed off RGA region pressure goes up and the result is distorted RGA scan.

    CC1 MKS gauge is disconnected and VM1 opened. This reminds me that we should connect our interlocks to CC1 Hornet Pressure gauge.

    Quote:

    Pumpdown 80 at 511 days and pd80b at 218 days

    Valve configuration:  special vacuum normal, annuloses are not pumped at 3 Torr, IFO pressure 7.4e-6 Torr at vac envelope temp 22 +- 1C degrres

     

     

     

    Attachment 1: rga2018march27.png
    rga2018march27.png
      3117   Thu Jun 24 18:47:26 2010 FrankDAQIOOVME crate rebooted

    we had to reboot the IOO VME crate right before lunch as the DAQ wasn't working correct meaning showing no real signals anymore, only strange noise. The framebuilder and everything else was working fine at that time.

    • The channel used for the phase noise measurement stopped showing any useful signal right after midnight, so all the other IOO-MC signals.
    • The data taken with those channels showed something like a 140 counts or so of steady offset with something which looked like the last bit fluctuating.
    • Whatever signal we connected to the input it didn't change at all, floating/shorted input, sine wave etc.
    • the other channels for the MC which we checked showed the same strange behaviour

    As the other channels showed the same effect we decided to reboot the crate and everything was fine afterwards.

      12252   Wed Jul 6 11:02:41 2016 PrafulUpdateComputer Scripts / ProgramsVMon Tab on Summary Pages

    I've added a new tab for VMon under the SUS parent tab. I'm still working out the scale and units, but let me know if you think this is a useful addition. Here's a link to my summary page that has this tab: https://ldas-jobs.ligo.caltech.edu/~praful.vasireddy/1151193617-1151193917/sus/vmon/


    I'll have another tab with VMon BLRMS up soon.

    Also, the main summary pages should be back online soon after Max fixed a bug. I'll try to add the SUS/VMon tab to the main pages as well.

      12577   Fri Oct 21 09:28:21 2016 SteveUpdateVACVac Normal reached

    Dry pump of TP3 replaced after 9.5 months of operation.[ 45 mTorr d3 ]

    The annulosses are pumped.

    Valve configuration: vac normal, IFO pressure 4.5E-5 Torr [1.6E-5 Torr d3 ] on new ITcc gauge, RGA is not installed yet.

    Note how fast the pressure is dropping when the vent is short.

    Quote:

    IFO pressure 1.7E-4 Torr on new not logged cold cathode gauge. P1 <7E-4 Torr

    Valve configuration: vac.normal with anunulossess closed off.

    TP3 was turned off with a failing drypump. It will be replaced tomorrow.

    All time stamps are blank on the MEDM screens.

    Attachment 1: VacNormal.png
    VacNormal.png
      11292   Fri May 15 16:18:28 2015 SteveUpdateVACVac Operation Guide

    Vacuum Operation Guide is up loaded into the 40m-wiki. This is an old master copy. Not exact in terms of real action, but it is still a good guide of logic.

    Rana has promissed to watch the N2 supply and change cylinder when it is empty. I will be Hanford next week.

      11262   Tue Apr 28 09:49:26 2015 SteveUpdateVACVac Summery Channels

     

     

           Channel        

                        Function                                          Interlock action           
                

    C1:Vac-P1_pressure   

     IFO vac envelope pressure           at 3 mT close V1 and PSL shutter
    C1:Vac-P2_pressure  Maglev foreline pressure                      at 6 Torr close V1 
    C1:Vac-P3_pressure  annuloses    
    C1:Vac-CC1_pressure  IFO pressure   at 1e-5 Torr close VM1
    C1:Vac-CC4_pressure  RGA  pressure    
     C1:Vac-N2pres  valve's drive  pneumatic 60-80PSI    

     

    at 55 PSI close V1, at 45 PSI close all 
     It  does not exist yet 2 N2 cylinder sum pressure  

     

      11274   Tue May 5 16:02:57 2015 SteveUpdateVACVac Summery Channels with discription

    As it was requested by the Bos.

    It would be nice to read from the epic screen C1:Vac-state_mon.......Current State: Vacuum Normal, valve configuration

    Quote:

           Channel        

                        Function                                              Description                                             Interlock         
                 

    C1:Vac-P1_pressure   

     Main volume of 40m interferro meter        P=Pirani gauge, Pressure range: ATM-760  to 1e-4 Torr at 3 mT close V1 and PSL shutter
    C1:Vac-P2_pressure  Maglev foreline pressure

    Maglev is the main pump of our vacuum system below 500 mTorr

    It's long term pressure has to be <500 mTorr                  

     at 6 Torr close V1 
    C1:Vac-P3_pressure  annuloses

     Each chamber has it's own annulos. These small volumes are indipendent from main volume.     Their  pressure  ranges are <5 mTorr at vac. normal valve configuration.

                                              
    C1:Vac-CC1_pressure  IFO main volume

    CC1=cold cathode gauge (low emmision), Pressure range: 1e-4 to 1e-10 Torr,

    In vac- normal configuration CC1= 2e-6 Torr

    at 1e-5 Torr close VM1
    C1:Vac-CC4_pressure  RGA  pressure In vac-normal configuration CC1=CC4  
     C1:Vac-N2pres  valve's drive pneumatic    

    The N2 supply is regulated to 60-80 PSI out put at the auto cylinder changer.

     at 55 PSI close V1, at 45 PSI close all 
     It  does not exist yet 2 N2 cylinder sum pressure

    Each cylinder pressure will be measured before the regulator and summed for warning message to be send

    at 1000 PSI

     

      14384   Fri Jan 4 11:06:16 2019 JonOmnistructureUpgradeVac System Punchlist

    The base Acromag vacuum system is running and performing nicely. Here is a list of remaining questions and to-do items we still need to address.

    Safety Issues

    • Interlock for HV supplies. The vac system hosts a binary EPICS channel that is the interlock signal for the in-vacuum HV supplies. The channel value is OFF when the main volume pressure is in the arcing range, 3 mtorr - 500 torr, and ON otherwise. Is there something outside the vacuum system monitoring this channel and toggling the HV supplies?
    • Exposed 30-amp supply terminals. The 30-amp output terminals on the back of the Sorensen in the vac rack are exposed. We need a cover for those.
    • Interlock for AC power loss. The current vac system is protected only from transient power glitches, not an extended loss. The digital system should sense an outage and put the IFO into a safe state (pumps spun down and critical valves closed) before the UPS battery is fully drained. However, it presently has no way of sensing when power has been lost---the system just continues running normally on UPS power until the battery dies, at which point there is a sudden, uncontrolled shutdown. Is it possible for the digital system to communicate directly with the UPS to poll its activation state?

    Infrastructure Improvements

    • Install the new N2 tank regulator and high-pressure transducers (we have the parts; on desk across from electronics bench). Run the transducer signal wires to the Acromag chassis in the vacuum rack.
    • Replace the kludged connectors to the Hornet and SuperBee serial outputs with permanent ones (we need to order the parts).
    • Wire the position indicator readback on the manual TP1 valve to the Acromag chassis.
    • Add cable tension relief to the back of the vac rack.
    • Add the TP1 analog readback signals (rotation speed and current) to the digital system.  Digital temperature, current, voltage, and rotation speed signals have already been added for TP2 and TP3.
    • Set up a local vacuum controls terminal on the desk by the vac rack.
    • Remove gauges from the EPICS database/MEDM screens that are no longer installed or functional. Potential candidates for removal: PAN, PTP1, IG1, CC2, CC3, CC4.
    • Although it appeared on the MEDM screen, the RGA was never interfaced to the old vac system. Should it be connected to c1vac now?
      14396   Thu Jan 10 19:59:08 2019 JonUpdateVACVac System Running Normally on Turbo Pumps

    [Jon, Gautam, Chub]

    Summary

    We continued the pumpdown of the IFO today. The main volume pressure has reached 1.9e-5 torr and is continuing to fall. The system has performed without issue all day, so we'll leave the turbos continuously running from here on in the normal pumping configuration. Both TP2 and TP3 are currently backing for TP1. Once the main volume reaches operating pressure, we can transition TP3 to pump the annuli. They have already been roughed to ~0.1 torr. At that point the speed of all three turbo pumps can also be reduced. I've finished final edits/cleanup of the interlock code and MEDM screens.

    Python Code

    All the python code running on c1vac is archived to the git repo: 

    https://git.ligo.org/40m/vacpython

    This includes both the interlock code and the serial device clients for interfacing with gauges and pumps.

    MEDM Monitor/Control

    We're still using the same base MEDM monitor/control screens, but they have been much improved. Improvements:

    • Valves now light up in red when they are open. This makes it much easier to see at a glance what is valved in/out.
    • Every pump in the system (except CP1) is now digitally controlled from the MEDM control screen. No more need to physically push any buttons in the vaccum rack. 👍
    • The turbo pumps now show additional diagnostic readouts: speed (TP1/2/3), temperature (TP2/3), current draw (TP1/2/3), and voltage (TP2/3).
    • The foreline pressure gauge readouts for TP2/3 have been added to the digital system.
    • The two new main volume gauges, Hornet and SuperBee, have been added to the digital system as well.
    • New transducers have been added to read back the two N2 tank pressures.
    • The interlock code generates a log file of all its actions. A field in the MEDM screens specifies the location of the log file.
    • A tripped interlock (appearing as a message in the "Error message" field) must be manually cleared via the "Clear error message" button on the control screen before the system will accept any more manual valve input.

    Note: The apparent glitches in the pressure and TP diagnostic channels are due to the interlock system being taken down to implement some of these changes.

    Attachment 1: Screen_Shot_2019-01-10_at_7.58.24_PM.png
    Screen_Shot_2019-01-10_at_7.58.24_PM.png
    Attachment 2: CCs.png
    CCs.png
    Attachment 3: TPs.png
    TPs.png
      14509   Tue Apr 2 18:40:01 2019 gautamUpdateVACVac failure

    While glancing at my Vacuum striptool, I noticed that the IFO pressure is 2e-4 torr. There was an "AC power loss" reported by C1Vac about 4 hours (14:07 local time) ago. We are investigating. I closed the PSL shutter.


    Jon and I investigated at the vacuum rack. The UPS was reporting a normal status ("On Line"). Everything looked normal so we attempted to bring the system back to the nominal state. But TP2 drypump was making a loud rattling noise, and the TP2 foreline pressure was not coming down at a normal rate. We wonder if the TP2 drypump has somehow been damaged - we leave it for Chub to investigate and give a more professional assessment of the situation and what the appropriate course of action is.

    The PSL shutter will remain closed overning, and the main volume and annuli are valved off. We spun up TP1 and TP3 and decided to leave them on (but they have negligible load).

    Attachment 1: vacFail.png
    vacFail.png
      14511   Wed Apr 3 09:07:46 2019 gautamUpdateVACVac failure

    Overnight pressure trends don't suggest anything went awry after the initial interlock trip. Some watchdog script that monitors vacuum pressure and closes the PSL shutter in the event of pressure exceeding some threshold needs to be implemented. Another pending task is to make sure that backup disk for c1vac actually is bootable and is a plug-and-play replacement.

    Attachment 1: vacFailOvernight.png
    vacFailOvernight.png
      15391   Thu Jun 11 11:48:43 2020 gautamUpdateVACVac failure

    There appears to have been some sort of vacuum failure.

    ldas-pcdev1 was down, so the summary pages weren't being generated. I have now switched over to ldas-pcdev6. I suspect some forepump failure, will check up later today unless someone else wants to take care of this.

    There was no interlock action, and I don't check the vacuum status every half hour, so there was a period of time last night there was high circulating power in the arm cavities when the main volume pressure was higher than nominal. I have now closed the PSL shutter until the issue is resolved.

    Attachment 1: vacFailure.png
    vacFailure.png
      15392   Thu Jun 11 16:14:03 2020 gautamUpdateVACVac failure - probable cause is serial comm glitch

    Summary:

    It looks like the main vacuum interlock was tripped due to a serial communication error from the TP2 controller. With Rana/Koji's permission, I will open V1 and expose the main volume to TP1 again (#2 in last section).

    Details:

    • The vacuum interlock log file at /opt/target/vac.log on c1vac suggests that the interlock was tripped because "TP2 is too warm".
    • Looking back at the diagnostics channels, it looks like the TP2 temperature channel registered a rise in temperature of >30 C in <0.2 seconds, see Attachment #1 - seems highly unlikely, probably some kind of glitch in the serial communication? This particular pump is relatively new from Agilent (<2 years installed I think)
    • The PSL shutter was automatically closed at ~1150 am today, see Attachment #2. There is some EPICS logic on c1psl (Acromag server) that checks if C1:Vac-P1a_pressure is greater than 3 mTorr (or greater than 500 Torr for in-air locking of the IMC), in which case it closes the shutter, so this seems consistent with expectations.

    Recommended course of action:

    1. Code in some averaging in the interlock code, so that the interlock isn't triggered on some unphysical glitch like this. As shown in Attachment #3, this has been happening for the past 24 hours (though not before, because the interlock wasn't tripped). Probably need the derivative of the temperature as well, and the derivative should be less than 5 C/s or something physical (in addition to the temperature being high) for the interlock to trip.
    2. Re-open V1 to pump down the main volume to nominal pressure so that the interferometer locking activity can resume.
      • One option in the interim is to bypass the TP2 temperature interlock condition.
      • The pressure-based interlocks are probably sufficient to protect the main volume / pumps during the nominal operations - the temperature interlocks are mainly useful during the pumpdown where the TPs have a large load, and so we want to avoid over-stressing them.
    Attachment 1: TP2_tempGlitch.png
    TP2_tempGlitch.png
    Attachment 2: PSL_shutterClosed.png
    PSL_shutterClosed.png
    Attachment 3: TP2tempGlitches.pdf
    TP2tempGlitches.pdf
      15412   Thu Jun 18 22:33:57 2020 JonOmnistructureVACVac hardware purchase list

    Replacement Hardware Purchase List

    I've created a purchase list of hardware needed to restore the aging vacuum system. This wasn't planned as part of the BHD upgrade, but I've added it to the BHD procurement list since hardware replacements have become necessary.

    The list proposes replacing the aging TP3 Varian turbo pump with the newer Agilent model which has already replaced TP2. It seems I was mistaken in believing we already had a second Agilent pump on hand. A thorough search of the lab has not turned it up, and Steve himself has told me he doesn't remember ordering a second one. Fortunately Steve did leave us a detailed Agilent parts list [ELOG 14322].

    It also proposes replacing the glitching TP2 Agilent controller with a new one. The existing one can be sent back for repair and then retained as a spare. Considering that one of these controllers is already malfunctioning after < 2 years, I think it's a very good idea to have a spare on hand.

    Known Hardware Issues

    Below is our current list of vacuum hardware issues. Items that this purchase list will address (limited to only the most urgent) are highlighted in yellow.

    • Replace the UPS
      • Need a 240V socket for TP1 (currently TP1 is not protected from power loss)
      • Need RS232/485 comms with the interlock server (current UPS: serial readbacks have failed, battery is failing)
    • Remove/replace the failed pressure gauges (~5)
    • Add more cold cathode sensors to the main volume for sensor redundancy (currently the main-volume interlocks rely on only 1 working sensor)
    • Replace TP3 (controller is failing)
    • Replace TP2 controller (serial interface has failed)
    • Remove RP2
      • Dead and also not needed. We already have to throttle the pumpdown rate with only two roughing pumps
    • Remove/refurbish the cryopump
      • Contamination risk to have it sitting connectable to the main volume
      15502   Tue Jul 28 12:22:40 2020 JonUpdateVACVac interlock test today 1:30 pm

    This afternoon Jordan is going to carry out a test of the V4 and V5 hardware interlocks. To inform the interlock improvement plan [15499], we need to characterize exactly how these work (they pre-date the 2018 upgrade). I have provided him a sequence of steps for each test and will also be backing him up on Zoom.

    We will close V1 as a precaution but there should be no other impact to the IFO. The tests are expected to take <1 hour. We will advise when they are completed.

      15504   Tue Jul 28 14:11:14 2020 JonUpdateVACVac interlock test today 1:30 pm

    This test has been completed. The IFO configuration has been reverted to nominal.

    For future reference: yes, both the V4 and V5 hardware interlocks were found to still be connected and work. A TTL signal from the analog output port of each pump controller (TP2 and TP3) is connected to an auxiliary relay inside the main valve relay box. These serve the purpose of interupting the (Acromag) control signal to the primary V4/5 relay. This interrupt is triggered by each pump's R1 setpoint signal, which is programmed to go low when the rotation speed falls below 80% of the low-speed setting.

    Quote:

    This afternoon Jordan is going to carry out a test of the V4 and V5 hardware interlocks. To inform the interlock improvement plan [15499], we need to characterize exactly how these work (they pre-date the 2018 upgrade). I have provided him a sequence of steps for each test and will also be backing him up on Zoom.

    We will close V1 as a precaution but there should be no other impact to the IFO. The tests are expected to take <1 hour. We will advise when they are completed.

      14546   Tue Apr 16 22:06:51 2019 gautamUpdateVACVac interlock tripped again

    This happened again, about 30,000 seconds (~2:06pm local time according to the logfile) ago. The cited error was the same -

    2019-04-16 14:06:05,538 - C1:Vac-error_status => VA6 closed. AC power loss.

    Hard to believe there was any real power loss, nothing else in the lab seems to have been affected so I am inclined to suspect a buggy UPS communication channel. The PSL shutter was not closed - I believe the condition is for P1a to exceed 3 mtorr (it is at 1 mtorr right now), but perhaps this should be modified to close the PSL shutter in the event of any interlock tripping. Also, probably not a bad idea to send an email alert to the lab mailing list in the event of a vac interlock failure.

    For tonight, I only plan to work with the EX ALS system anyways so I'm closing the PSL shutter, I'll work with Chub to restore the vacuum if he deems it okay tomorrow.

    Attachment 1: Screenshot_from_2019-04-16_22-05-47.png
    Screenshot_from_2019-04-16_22-05-47.png
    Attachment 2: Screenshot_from_2019-04-16_22-06-02.png
    Screenshot_from_2019-04-16_22-06-02.png
      14550   Wed Apr 17 18:12:06 2019 gautamUpdateVACVac interlock tripped again

    After getting the go ahead from Chub and Jon, I restored the Vacuum state to "Vacuum normal", see Attachment #1. Steps:

    1. Interlock code modifications
      • Backed up /opt/target/python/interlocks/interlock_conditions.yaml to /opt/target/python/interlocks/interlock_conditions_UPS.yaml
      • The "power_loss" condition was removed for every valve and pump inside /opt/target/python/interlocks/interlock_conditions.yaml
      • The interlock service was restarted using sudo systemctl restart interlock.service
      • Looking at the status of the service, I saw that it was dying ~ every 1 second.
      • Traced this down to a problem in/opt/target/python/interlocks/interlock_conditions.yaml  when the "pump_managers" are initialized - the way this is coded up, doesn't play nice if there are no conditions specified in the yaml file. For now, I just commented this part out. The git diff  below:
    2. Restoring vacuum normal:
      • Spun up TP1, TP2 and TP3
      • Opened up foreline of TP1 to TP2, and then opened main volume to TP1
      • Opened up annulus foreline to TP3, and then opened the individual annular volumes to TP3.
    controls@c1vac:/opt/target/python/interlocks$ git diff interlock.py
    diff --git a/python/interlocks/interlock.py b/python/interlocks/interlock.py
    index 28d3366..46a39fc 100755
    --- a/python/interlocks/interlock.py
    +++ b/python/interlocks/interlock.py
    @@ -52,8 +52,8 @@ class Interlock(object):
             self.pumps = []
             for pump in interlocks['pumps']:
                 pm = PumpManager(pump['name'])
    -            for condition in pump['conditions']:
    -                pm.register_condition(*condition)
    +            #for condition in pump['conditions']:
    +            #    pm.register_condition(*condition)
                 self.pumps.append(pm)

    So far the pressure is coming down smoothly, see Attachment #2. I'll keep an eye on it.

    PSL shutter was opened at 645pm local time. IMC locked almost immediately.

    Update 11pm: The pressure has reached 8.5e-6 torr without hiccup. 

    Attachment 1: Screenshot_from_2019-04-17_18-11-45.png
    Screenshot_from_2019-04-17_18-11-45.png
    Attachment 2: Screenshot_from_2019-04-17_18-21-30.png
    Screenshot_from_2019-04-17_18-21-30.png
      14574   Thu Apr 25 10:32:39 2019 JonUpdateVACVac interlocks updated

    I slightly cleaned up Gautam's disabling of the UPS-predicated vac interlock and restarted the interlock service. This interlock is intended to protect the turbo pumps after a power outage, but it has proven disruptive to normal operations with too many false triggers. It will be reenabled once a new UPS has been installed. For now, as it has been since 2001, the vac pumps are unprotected against an extended power outage.

      15421   Mon Jun 22 10:43:25 2020 JonConfigurationVACVac maintenance at 11 am

    The vac system is going down at 11 am today for planned maintenance:

    • Re-install the repaired TP2 and TP3 dry pumps [ELOG 15417]
    • Incorporate an auto-mailer and flag channel into the controls code for signaling tripped interlocks [ELOG 15413]

    We will advise when the work is completed.

      15424   Mon Jun 22 20:06:06 2020 JonConfigurationVACVac maintenance complete

    This work is finally complete. The dry pump replacement was finished quickly but the controls updates required some substantial debugging.

    For one, the mailer code I had been given to install would not run against Python 3.4 on c1vac, the version run by the vac controls since about a year ago. There were some missing dependencies that proved difficult to install (related to Debian Jessie becoming unsupported). I ultimately solved the problem by migrating the whole system to Python 3.5. Getting the Python keyring working within systemd (for email account authentication) also took some time.

    Edit: The new interlock flag channel is named C1:Vac-interlock_flag.

    Along the way, I discovered why the interlocks had been failing to auto-close the PSL shutter: The interlock was pointed to the channel C1:AUX-PSL_ShutterRqst. During the recent c1psl upgrade, we renamed this channel C1:PSL-PSL_ShutterRqst. This has been fixed.

    The main volume is being pumped down, for now still in a TP3-backed configuration. As of 8:30 pm the pressure had fallen back to the upper 1E-6 range. The interlock protection is fully restored. Any time an interlock is triggered in the future, the system will send an immediate notification to 40m mailing list. 👍

    Quote:

    The vac system is going down at 11 am today for planned maintenance:

    • Re-install the repaired TP2 and TP3 dry pumps [ELOG 15417]
    • Incorporate an auto-mailer and flag channel into the controls code for signaling tripped interlocks [ELOG 15413]
    Attachment 1: Pumpdown-6-22-20.png
    Pumpdown-6-22-20.png
      15425   Tue Jun 23 17:54:56 2020 ranaConfigurationVACVac maintenance complete

    I propose we go for all CAPS for all channel names. The lower case names is just a holdover from Steve/Alan from the 90's. All other systems are all CAPS.

    It avoids us having to force them all to UPPER in the scripts and channel lists.

      15748   Wed Jan 6 15:28:04 2021 gautamUpdateVACVac rack UPS batteries replaced

    [chub, gautam]

    the replacement was done this afternoon. The red "Replace Battery" indicator is no longer on.

    ELOG V3.1.3-