logbook/robot/script0.cds.ligo-wa.caltech.edu@LIGO.ORG - posted 15:37, Tuesday 20 December 2016 (32787)
test robo post 2
This is a test of posting from script0 using robot credentials.
This is a test of posting from script0 using robot credentials.
This is a test of posting from script0 using robot credentials. Have a very nice day.
After a little fix, moving cables to their correct block assignment (II cables were swapped at the box by the controller), the new cable was landed for ion pump IP12.
We are connected to the EI/II522A channels (all others not connected because they are not used anymore), work done per WP 6408.
Next, code will need to be updated, both in Beckhoff and MEDM world, to show upgrade to the new LPC Gamma type controller (positive polarity).
The IM alignments were adjusted many times in the commissioning ramp up to O2, so IMs have not had nominal values for some time, and DIAG_MAIN values were not consistant with the current IM values.
I adjusted IM1-3 alignments after taking some measurements during maintenance today, and in looking at the IM alignment history.
I saw the IM1 pitch had bee restored to the DIAG_MAIN value yesterday, and this was not a correct value.
The current nominal values for IM1-3 OSEM alignments, as deemed good on Dec 8th at 09:00UTC, after a discussion with Jenne, are:
| pitch | yaw | |
| IM1 | 180 | 1120 |
| IM2 | 608 | -320 |
| IM3 | 1961 | -2 |
These are also listed in the IM Nominal Alignment medm (IOO sitemap list), and are updated in the DIAG_MAIN code.
13 day trend - beginning of plots is where IM nominal alignment was set - after that, multiple ISI trips - some drift away from nominal - IM1 pitch change and recovery
Today, I performed the LVEA sweep after everyone finished their Tues maintenance work. I confirmed everything on the list, except for 2 of the 3 crane parking placements - we didn't use any cranes today and they have been parked in the same place for over a week. I also only glanced at the electronics racks, since we also had done a nice sweep to disconnect miscellaneous stuff from racks prior to the run starting. I did not see any new dangling pieces of test equipment or other interesting looking stuff.
I did unplug the West bay phone along the wall - likely on since the start of O1 since it's a somewhat unfamiliar phone to people. Here is the full list of LVEA phones I found and their status as of now (which should be added to the sweep checklist):
1) Inside H1 PSL enclosure - OFF
2) On tool box or table near H1 PSL enclosure - OFF
3) West bay along wall near crane parking sign - now OFF
4) On table near HAM7 East door - OFF
5) Along wall near HAM6 North - OFF
6) In Squeezer Bay on table - OFF
7) Back corner of electronics room, on floor - OFF
8) I suspect possibly one is inside H2 PSL enclosure - called it, didn't see it on HAM7 mic, unconclusive if it exists...
The H2 phone is definitely powered off. I checked it last week by trying to make a call from it. Dead as a door knob.
The original ETMY PUM coil driver (S1102652) was reinstalled this morning. Two hour lock shows little or no change in the glitch rate. The AI chassis controlling the PUM chassis was also power cycled.
Attaching detchar tag.
This morning, Jason, Mark and I swapped the assumed-to-be failing TCSY flow sensor which has been showing epochs of glitching and low readout (while other indicators show normal flow, alogs 32712 and 32230). The process to do this was such:
1) Key laser off at control box in rack, LVEA
2) Turn RF off at mezzanine rack, Mech room
3) Turn chiller off on mezzanine, Mech room
4) Turn power off on back of controller box in rack, LVEA (we also pulled the power cable to the sensor off the front of the controller, but it was probably overkill)
5) Close in-line valves under BSC chamber near yellow sensor to-be-swapped, LVEA
6) Quick-disconnect water tubes at manifold near table, LVEA
7) Pulled yelow top off of yellow sensor housing under BSC at the piping, LVEA
8) Pulled the blue and black wires to the Power recepticles inside the housing (see pic attached). Pulled full grey cable out of housing.
9) While carefully supporting blue piping*, unscrewed large white nut holding housing/sensor to piping (was tough, in fact so tough that we later removed all of the teflon tape which was unneeded in his join)
10) Pull* straight up on the housing (hard) and it comes out of the piping.
11) Reverse all above steps to insert new housing/sensor, wires and turn everything back on. Watch for rolled o-rings on the housing and proper alignment of the noth feature when installing the new sensor. Verify mechanical flow sensors in piping line show ~3-4 G/m readout when flow/chiller is restored to functionality.
12) Setup new flow sensor head with Settings: Go to the other in-use sensor, pull off the top and scroll through the menu items (red and white buttons on the unit (shown in pic). Set the new head to these values.
13) Verify the new settings on the head are showing a ~3 G/m readout on the medm screen. If not, possibly there is setting on the sensor that needs revisited.
14) Monitor TCS to see that laser comes back up and stabilizes.
* Blue piping can crack so be careful to always support it and avoid torque torque
Note - with the sensor removed, we could see alot of green merk in the blue piping where the paddle wheel sits. Still suffering green sludge in this system...
A few pictures to add to those already posted. The O-ring closest to the paddle wheel had a cut to it. Not near the electronics, plus there's the other O-ring so it doesn't look like water was getting into where the electronics is housed. Some kind of stuff stuck to each blade (paddle?) of the paddle wheel. Not a good sign if the cooling water for the laser is meant to be clean.
Settings were as follows:
FLO Unit (Flow Unit) = G/m (default was L/m)
FActor (K-Factor) = 135.00 (default was 20)
AVErage (Average) = 0
SEnSit (Sensitivity) = 0
4 Set (4mA Set Point) = 0 G/m
20 Set (20mA Set Point = 10 G/m (default was 160)
ContrAST (Contrast) = 3
Here's both TCS system laser power and flow for the past day. The drop out in the ITMY data is our few hour sensor replacement work. So far no glitching or low droops. Although, there weren't any for the last 24 hours on the old sensor either.
Attached is a 14 day duration minute trend of the TCSy chiller flow rate and CO2 laser power since our swap of tthe TCSy flow sensor. There have been 7 glitches below 2 GPM, with 3 of those glitches being below 1 GPM; all 7 glitches occured in the last week. Unless the spare flow sensor is also faulty (not beyond belief, but still a hard one to swallow) the root cause of our TCSy flow glitches lies elsewhere.
It might be a good idea to try swapping the laser controller chassis next. The electronics path for this flow meter is very simple - just the controller and then into the EtherCAT chassis where it's read by an ADC.
This morning I re-centered the ITMx oplev. No issues were encoutered. This completes LHO WP 6406.
Did Zero Count and Flow tests on all dust monitors. Zero Counts were all OK. Flow is down a little (2.8l/m to 2.6l/m) on the dust monitor in the Biergarten and at End-Y. If flow drops any more will adjust during next months check. Made minor adjustments to the air bypass on all three vacuum pumps to bring the flow rate back to 19 inHg. All temperature check were within normal range. Closing FAMIS #7508
Carlos, Jim The raw minute trend writing has been restarted on h1tw0. Old raw trend files were removed.
A. Urban, on behalf of the calibration group
Around GPS second 1166295017 (2016 Dec 20 10:50 AM Pacific), I restarted the primary and redundant GDS calibration pipelines at Hanford. This restart picks up a software update to gstlal-calibration-1.1.3 (see https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=30528) which is not expected to have any effect on the output of the GDS online pipeline (it primarily affects the DCS pipeline in offline mode). The filters have also not changed from their previous configuration; see https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=32389.
In preparation for the holiday break, the timing setup in the EE lab was powered down. Since the timing signal comes from the master fanout in the MSR, timing overview MEDM screen showed an error, change in configuration. Error was cleared by Jim B.
J. Kissel Grabbed this week's charge measurements. The effective bias voltage (as gauged by the angular actuation strength) is still hovering around zero thanks to the idea Sheila implemented flipping the bias signs when the IFO isn't using the respective ESD; programmed into the ISC_LOCK guardian on ETMX on 2016 Nov 03 (see LHO aLOG 31172), and for ETMY on 2016 Nov 28 (see LHO aLOG 31929). I highly recommend LLO try out a similar scheme if and when they discharge their effective bias voltage back to zero. Also, re-reminding myself and/or anyone who has time: resurrect comparison between longitudinal actuation strength and angular actuation strength, a. la. LHO aLOG 24241.
Took a couple of thermal images of the pre-modecleaner body. The images are attached.
The shot of the ceiling was to get a reference for the room temperature.
Looks like the pre-modecleaner body is around 24.6 degC, except where the two Kapton
heaters are located and the piezo.
As per yesterday morning's meeting. The alignment to the reference cavity was touched up.
Mostly vertical adjustment, consistent with moving the beam up. I feel the alignment could
be a little better but stopped in the interest of time.
For reasons unknown to me, it seems that the alignment into the pre-modecleaner changed
whilst I was in the enclosure. At least the reflected spot camera image looked like it moved
to the left.
WP6407
Jonathan, Ryan, Dave:
we are testing the robot alog-entry system.
We would like to remind the general reader that robotic entries can be filtered by using the "exclude robot entries" button in the search window.
Note that robotic entries which have non-robotic comments will not be filtered.