Displaying reports 61561-61580 of 88268.Go to page Start 3075 3076 3077 3078 3079 3080 3081 3082 3083 End
Reports until 13:34, Tuesday 31 May 2016
H1 SUS (SUS)
rana.adhikari@LIGO.ORG - posted 13:34, Tuesday 31 May 2016 - last comment - 14:20, Tuesday 31 May 2016(27455)
SRM Thermal Noise: Composite mass drawings

In the morning we were wondering what the SRM composite mass looks like, in case we want to drive it to find out the frequency and Q of the first internal mode.

https://dcc.ligo.org/LIGO-D1200886

There is a ring shaped holder which has two nubs and a set screw. This holds the 2" optic. This holder is then bolted into the larger aluminum mass. Two views from the solidworks drawings are shows with some parts made transparent. If this drawing is right, I expect that the resonant frequency is in the 500-1000 Hz range.

Images attached to this report
Comments related to this report
betsy.weaver@LIGO.ORG - 14:20, Tuesday 31 May 2016 (27456)

Here is a picture of the actual SRM surrogte optic in it's inner holder (the LLO one shown).  The 2" x 0.75" thick optic is held in the ring by what I believe are 2 black carbon peek set screws which are not shown in the assembly drawings.

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 13:14, Tuesday 31 May 2016 (27454)
summary of long weekend's problems

Saturday 28th

08:47 PSL Diode Chiller monitor signals flat-line (compuer had been running for about 24 hours since last reboot)

10:24 TCS DAC output drops to zero volts (recovered soon after)

17:04 h1nds1 kernel panics (computer rebooted)

23:46 TCS DAC output drops to zero volts (recovered Monday)

Sunday 29th

Monday 30th

11:00 PSL laser power drops to zero (recovered Tuesday)

H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 13:06, Tuesday 31 May 2016 (27453)
CDS maintenance summary

TCS Y-table FLIR camera

Kiwamu, Dave:

the TCS-Y infrared camera was not responding. Restarting the controller unit at the table appears to have resolved it.

h1nds1 restart

h1nds1 stopped running. Monit was not monitoring it, we manually instructed monit to restart daqd and it is running again.

h1oaf0 power cycle

Following three occurences of the TCS DAC being driven to zero volts, this morning we power cycled the IO Chassis for h1oaf0. Power was removed from the chassis using the front panel switch, it was down for about one minute. h1tcscs was manually burt restored to 09:10 PDT this morning.

roof camera

Richard, Jim, Dave:

We went onto the roof and verified the CDS AUX vlan was operational at the fiber media converter, it was.

H1 PSL
jason.oberling@LIGO.ORG - posted 12:17, Tuesday 31 May 2016 - last comment - 14:22, Thursday 02 June 2016(27451)
PSL Diode Chiller Work (FRS 5605)

J. Oberling, J. Bartlett, P. King (via phone)

Following yesterday's initial investigation into the PSl diode chiller issues (see alogs here), we swapped the control panel for the diode chiller with the one from the chiller we recently removed from service (this is a known working unit, just installed last year).  After installation the chiller restarted without issue and ran for several minutes, also without issue.  The serial number of the control panel we installed in the diode chiller is 44806P605; the faulty unit we removed from the diode chiller had no SN on it.

We then took the time to restart the PSL Beckhoff PC to unstick the frozen diode chiller channels.  According to Dave Barker these channels froze sometime on Saturday morning.  Fortunately the PSL interlocks are not tied to these channels, otherwise we would not have the PSL shutting down when the diode chiller shuts down (as we did yesterday).  Once restarted the channels appeared to be reading OK.  It is possible that these channels freezing for no reason can be used as an early warning sign of imminent chiller failure.  The chiller communicates with the PSL Beckhoff PC via a serial RS-232 interface and we have seen channels freeze when the cables are unplugged and plugged back in but the PC not restarted (which is expected behavior as RS-232 is not hot swappable), but this is the first time I've seen the chiller spontaneously loose communication with the PSL Beckhoff PC.  Jeff Bartlett is setting up a temporary Strip Tool on the PSL monitor in the control room that will monitor these channels.  If anyone sees that these are flatlined (there should always be some variation), please let someone on the PSL team (Peter King, Jeff Bartlett, Ed Merilh, Rick Savage, or myself) know immediately.  Thank you.

We then turned on the HPO, which came up with no problems.  We let it sit and run for a little while, then restarted the rest of the PSL.  As of now, everything is up an running.  We are going to continue to monitor over the next couple days to ensure that everything is working correctly.  The removed control panel will go back to Termotek with the chiller we are sending back and will be replaced as part of the service being done on that chiller.

Comments related to this report
jason.oberling@LIGO.ORG - 14:22, Thursday 02 June 2016 (27512)

Completely forgot to mention that after performing the above front panel swap and restarting the laser, we adjusted the calibration of the vortex flow sensors in both chillers.  Using the chiller we just recently removed from service, we hooked it up to an external flow meter and compared the 2 readings (1 from the chiller's internal flow meter and 1 from our external flow meter) and calculated a new pulses/liter calibration for the vortex flow sensors.  According to that measurement the vortex flow sensors should be set to 494 pulses/liter (they were originally set to ~970 pulses/liter, a number we got from LZH).  The flow information from both chillers is now accurate.

LHO VE
kyle.ryan@LIGO.ORG - posted 15:04, Monday 30 May 2016 (27446)
Control room vacuum screen not completely viewable - please close or minimize offending window


			
			
LHO VE
kyle.ryan@LIGO.ORG - posted 14:44, Monday 30 May 2016 (27445)
Manually over-filled CP3
1420 - 1440 hrs. local -> To and from Y-mid 

Opened exhaust check valve bypass, opened LLCV bypass 1/2 turn ccw -> LN2 at exhaust in 40 seconds -> Closed LLCV bypass, waited a few minutes and closed exhaust check valve bypass. 

Next overfill nominally Wednesday afternoon.
H1 PSL (CDS, DetChar, ISC, PSL, TCS)
sheila.dwyer@LIGO.ORG - posted 13:53, Monday 30 May 2016 - last comment - 11:52, Tuesday 31 May 2016(27440)
laser tripped, TCS DAC problem, accoustic noise from PSL AC coupling to RF

Sheila, Terra, Craig

The PSL is off, is has been since about 17:30 UTC. The chillers don't seem to be tripped. Confusingly the laser screen indicates that the chillers are fine, (two green boxes) while the PSL_STATUS screen has a red box for the crystal chiller (screenshot attached).  Jason will come out to the site to investigate/restart the laser.  

We also noted that the temperature trends for the PSL have been usual since thursday morning's incursion. (2nd screnshot) I went to the controller box and saw that the north AS unit was on, which was probably unintentional (the south unit was off, and they are normally both off in science mode).  I turned it off at noon local time.  Terra noted that the PSL microphone has seen an elevated level of noise in the last few days, which went back to normal as soon as the AC unit was off.  (In the third attached screenshot, blue traces are from the time when the AC was on).  The montors on the RF AM stabilization also changed when we turned off the AC, and some channels on the AM stabilization box seem to have been sensitive to some kind of switching of the PSL HVAC over the last few days.  

It seems like we need some kind of a better way to monitor if the PSL environment settings are correct, maybe adding them to diag main if we can find a good set of tests to write.  It also is suprising to me that our RF system seems to be so sensitive to accoustic pick up in the PSL.  Has anyone in detchar looked at PSL PEM monitors to see if glitches there are correlated to the "RF45" glitches seen durring O1? 

The TCS chillers are also tripped, with the same DAC problem we have been having. (27435)  This happened about 36 hours ago.

Images attached to this report
Comments related to this report
terra.hardwick@LIGO.ORG - 12:23, Monday 30 May 2016 (27442)

Bottom chiller screen; flashing between 'temperature' and 'warning'

Images attached to this comment
peter.king@LIGO.ORG - 12:38, Monday 30 May 2016 (27443)
The laser was up and running this morning when I checked it around 6 am (local).
The gibberish message on the diode chiller controller I've never seen before
and is most likely a controller malfunction.

    To fix the problem, I would try (in order):
 - power cycling the chiller with the power switch located at the rear of the chiller
 - replacing the chiller controller (if Jeff Bartlett happens to have a spare handy)
 - install the spare chiller (which will take a bit of work because ... )
     * the turbine flow sensors need to be replaced with the vortex ones
     * the 3-phase power plug needs to be installed
     * some filters need to be removed
     * the coolant lines will need to have any air pockets removed

    The problem with the first solution is that it is hard to gauge how long the
"fix" might be valid for before the laser could trip out again.
terra.hardwick@LIGO.ORG - 13:25, Monday 30 May 2016 (27444)

We used Sheila's very instructive alog to kill and restart all the models on the OAF machine, reset the TCS chillers and restart the TCS laser. 

jason.oberling@LIGO.ORG - 16:14, Monday 30 May 2016 (27448)

J. Oberling, S. Dwyer

Attempted to bring the PSL back up but were ultimately unsuccessful.  Came in and found the crystal chiller running and the diode chiller off, although the Laser MEDM screen indicated the diode chiller was up and running.  EPICS channels frozen again?

The diode chiller turned on without an issue, although the weirdness on the main screen, seen in Terra's photos above, did not go away.  We let the chiller run for several minutes and then attempted to power on the HPO.  Approximately midway during the pump diode power up everything stopped and we found the diode chiller shut off.  To see if it was a coincidence we reset the interlocks and attempted to turn the HPO on again, this time monitoring the chillers.  The HPO got to its second stability range and the diode chiller immediately shut off.  We power cycled the diode chiller (which by the way cleared the funky front panel issue seen in the photos above).  This time the HPO acheived the second stability range for 10 whole seconds before the diode chiller shut off again; it almost seems as if the chiller is shutting off as soon as it sees a heat load.  During all this the crystal chiller remained up and running without issue.

At this time I'm out of ideas, although the chiller behavior copuled with the front screen weirdness makes me think we may have a control panel problem with the diode chiller (as Peter mentions above); I seem to recall that when we had the chiller flow sensor issues last year (April/May 2015) we also had some weird issues with the chiller (the one we just recently removed from service) that were solved by replacing the control panels.  I left the PSL off; the diode chiller is also off and the crystal chiller is running.  Please do not attempt to turn it on, we will investigate more fully tomorrow morning.

jason.oberling@LIGO.ORG - 11:52, Tuesday 31 May 2016 (27450)

Filed FRS #5605.

LHO VE
kyle.ryan@LIGO.ORG - posted 11:47, Monday 30 May 2016 - last comment - 09:26, Tuesday 31 May 2016(27441)
HAM4 AIP
(see attached) 
Will investigate Tues.
Non-image files attached to this report
Comments related to this report
vernon.sandberg@LIGO.ORG - 09:26, Tuesday 31 May 2016 (27449)

AIP = "annulus ion pump"

H1 ISC
sheila.dwyer@LIGO.ORG - posted 20:07, Saturday 28 May 2016 - last comment - 14:08, Friday 03 June 2016(27437)
locklosses possibly related to RF problem or SR3 glitches

Evan and I spent most of the day trying to investigate the sudden locklosses we've had over the last 3 days.  

1) We can stay locked for ~20 minutes with ALS and DRMI if we don't turn on the REFL WFS loops.  If we turn these loops on we loose lock within a minute or so.  Even with these loops off we are still not stable though, and saw last night that we can't make it through the lock acquisition sequence. 

2)In almost every lockloss, you can see a glitch in SR3 M2 UR and LL noisemons just before the lockloss, which lines up well in time with glitches in POP18.  Since the UR noisemon has a lot of 60 Hz noise, the glitches can only be seen there in the OUT16 channel, but the UR glitches are much larger.  (We do not actuate on this stage at all).  However, there are two reasons to be skeptical that this is the real problem:

It could be that the RF problem that started in the last few days somehow makes us more senstive to loosing lock because of tiny SR3 glitches, or that the noisemons are just showing some spurious signal which is related to the lockloss/ RF problems. Some lockloss plots are attached. 

It seems like the thing to do would be trying to fix the RF problem, but we don't have many ideas for what to do. 

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 20:25, Saturday 28 May 2016 (27438)

We also tried running the Hang's automatic lockloss tool, but it is a little difficult to interpret the results from this.  There are some AS 45 WFS channels that show up in the third plot that apprears, which could be related to either a glitchy SR3 or an RF problem. 

Images attached to this comment
sheila.dwyer@LIGO.ORG - 20:27, Saturday 28 May 2016 (27439)

One more thing: Nnds1 chrashed today and Dave helped us restart it over the phone.

andrew.lundgren@LIGO.ORG - 07:41, Wednesday 01 June 2016 (27470)DetChar, ISC, Lockloss
For the three locklosses that Sheila plotted, there actually is something visible on the M3 OSEM in length. It looks like about two seconds of noise from 15 to 25 Hz; see first plot. There's also a huge ongoing burst of noise in the M2 UR NOISEMON that starts when POP18 starts to drop. The second through fourth attachments are these three channels plotted together, with causal whitening applied to the noisemon and osem.

Maybe the OSEM is just witnessing the same electrical problem as is affecting the noisemon, because it does seem a bit high in frequency to be real. But I'm not sure. It seems like whatever these two channels are seeing has to be related to the lockloss even if it's not the cause. It's possible that the other M2 coils are glitching as well. None of the other noisemons look as healthy as UR, so they might not be as sensitive to what's going on.
Images attached to this comment
keita.kawabe@LIGO.ORG - 14:08, Friday 03 June 2016 (27501)

RF "problem" is probably not a real RF problem.

Bad RFAM excess was only observed in out-of-loop RFAM sensor but not in the RFAM stabilization control signal. In the attached, top is out-of-loop, middle is the control signal, and the bottom is the error signal.

Anyway, whatever this low frequency excess is, it should come in after the RF splitter for in- and out-of-loop board. Since this is observed both in 9 and 45MHz RFAM chassis, it should be in the difference in how in- and out-of-loop boards are configured. See D0900761. I cannot pinpoint what that is but my guess is that this is some DC stuff coming into the out-of-loop board (e.g. auto bias adjustment feedback which only exists in out-of-loop).

Note that even if it's a real RFAM, 1ppm RIN at 0.5Hz is nothing assuming that the calibration of that channel is correct.

Images attached to this comment
andrew.lundgren@LIGO.ORG - 15:22, Wednesday 01 June 2016 (27486)DetChar, ISC, Lockloss
Correction: The glitches are visible on both the M2 and M3 OSEMs in length, also weakly in pitch on M3. The central frequency looks to be 20 Hz. The height of the peaks in length looks suspiciously similar between M2 and M3.
Images attached to this comment
andrew.lundgren@LIGO.ORG - 01:42, Thursday 02 June 2016 (27496)DetChar, ISC, Lockloss
Just to be complete, I've made a PDF with several plots. Every time the noise in the noisemons comes on, POP18 drops and it looks like lock is lost. There are some times when the lock comes back with the noise still there, and the buildup of POP18 is depressed. When the noise ends, the buildup goes back up to its normal value. The burst of noise in the OSEMs seems to happen each time the noise in the noisemons pops up. The noise is in a few of the noisemons, on M2 and M3.
Non-image files attached to this comment
H1 ISC
evan.hall@LIGO.ORG - posted 17:06, Saturday 28 May 2016 (27436)
Oscillator RFAM is worse since the morning of May 26

Not clear why. It may correspond to a PSL incursion the same morning.

Also, what used to be hooked up to outputs 7 and 8 on the 9 MHz distribution amplifier in the CER? Sheila and I found some terminated attenuators on these ports, but I recall it used to be cabled up somehow.

Non-image files attached to this report
H1 CDS (CDS, TCS)
sheila.dwyer@LIGO.ORG - posted 13:05, Saturday 28 May 2016 (27435)
How to fix TCS chiller tripping problem

Evan H arrived on site this morning to find the TCS chillers tripped, reset them and found the same behavoir as described in alogs 27381 and 27374

On the OAFIOP GDS TP screen, both the DAC and ADC bits (as well as DK) were red, the ADC error cleared with a diag reset but the DAC error would not reset.  We called Dave and he asked us to check that the DAC outputs were all zero by looking at the DAC MON screens (accessed by clicking the blue buttons labeled D0). This means that it is the same DAC problem Nutsinee described.  

To fix the problem, you need to stop and start all the models on the front end, including the IOP model.  This can be done by:

1)maybe check SDF before you kill models (I frogot this step)

2) log in to h1oaf0 as controls 

3) run a script /etc/kill_models.sh, wait for all models to be shut down in the correct order, with the IOP model last

4) run a script /etc/start_models.sh

5) Dave said that for the PEM model only we restore the settings by loading the OBSERVE.snap and hitting LOAD TABLE +EDB.  Since I frogot to check SDF before killing the models I am using the automatic burts to restore the rest of the models. Confusingly, the automatic burts always appear to indicate that there are no diffs, because all channels are no mon in them, so to actually check you need to select full table, select all mon, then set the table back to setting diffs. Time machine doesn't work for the SDF screens, which would be handy in a situation like this.  

Go to the mezzanine and follow instructions here https://lhocds.ligo-wa.caltech.edu/wiki/TCS to restart the chillers, and the laser controllers near the TCS tables.

H1 General
edmond.merilh@LIGO.ORG - posted 21:30, Friday 27 May 2016 (27434)
Shift Summary - Evening
TITLE: 05/28 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Unknown
INCOMING OPERATOR: None
SHIFT SUMMARY:
  • Tour group in the Control Room.
  • Tara also gave a private tour to a couple of friends.
  • Work on TCS is done for the evening but not complete.
  • Sheila and Evan engaged in ongoing investigation of locklosses occurring around the ENGAGE_SRC_ASC stage.
  • ~ 2:15UTCGoing away party for Brynley has me at the helm, solo. I was instructed to see how long I can get things locked for (with not much hope). Otherwise, I can call it if I'm not having any luck.
  • 3:13UTC EY .3micron dust alarm
  • 3:00UTC Patrick left. I didn't realize he'd remained.
  • DRMI can get past it's ASC stage.
  • After the last DRMI lockloss I now hoave NO IR flashes in the arms.I guess it's time I called it a night 
LOG:
Displaying reports 61561-61580 of 88268.Go to page Start 3075 3076 3077 3078 3079 3080 3081 3082 3083 End