The following 12 channels are still unmonitored: H1:IOP-SUS_EX_ETMX_DACKILL_PANIC H1:IOP-SUS_EX_ETMX_OSC_CLKGAIN H1:IOP-SUS_EX_ETMX_OSC_COSGAIN H1:IOP-SUS_EX_ETMX_OSC_FREQ H1:IOP-SUS_EX_ETMX_OSC_SINGAIN H1:IOP-SUS_EX_ETMX_OSC_TRAMP H1:IOP-SUS_EX_TMSX_DACKILL_PANIC H1:IOP-SUS_EX_TMSX_OSC_CLKGAIN H1:IOP-SUS_EX_TMSX_OSC_COSGAIN H1:IOP-SUS_EX_TMSX_OSC_FREQ H1:IOP-SUS_EX_TMSX_OSC_SINGAIN H1:IOP-SUS_EX_TMSX_OSC_TRAMP
Replaced the failing dust monitor in the HAM6 cleanroom. Ops will notify CC if there are additional dust problems in HAM6.
[Sheila, Kiwamu]
As a preparation for moving the IOT2L table, we have disconnected all the relevant exterior cables. The table is ready to move. The attached is a cable layout as of this morning jsut for a book-keeping purpose.
The OSEM overview screen that has been running on the top leftmost monitor in the control room has been showing the raw OSEM signals (e.g., H1:SUS-MC1_M1_OSEMINF_T1_INMON) before normalization to ±15000 counts and conversion to microns. This makes it harder to see anomalous offsets because the working positions are all over the place. Therefore I changed them to look at the OSEMINF_*_OUTPUT channels.
In userapps I edited
^/trunk/cds/h1/medm/H1CDS_SUS_OSEM_OVERVIEW.adl
and
^/trunk/cds/h1/medm/H1CDS_SUS_OSEM_LARGE_OVERVIEW.adl
with gedit to change all instances of _INMON to _OUTPUT and all instances of hoprDefault=32000 to
loprDefault=-350
hoprDefault=350
where 350 = 15000*0.0233333. With these limits the working position of each indicator should be vertical if the GAIN and OFFSET fields are set to normalize raw signals in the range 0 to ≈22-31K to exactly ±15000 (per the standard SUS procedure), and FM5 is engaged to convert to microns.
After testing the changes I committed the files.
As a follow up to Betsy's log last night, I went out to ITMX this morning to release HEPI and look at actuator gaps. Payload is almost back to full, so I would expect if everything is healthy for HEPI to be pretty much centered. This is what I found, BUT... the vertical stops were all loose, meaning the platform had moved up some. I've also looked at IPS trends and they don't look horrible, reasonable shifts considering I locked with the loops on, a lot of payload came off then back on and we are still light some payload.So, a couple thoughts on what could have happened. - Basically nothing. The error Jason found is all somehow in SUS. Seems unlikely. - Some incredibly lucky/unlucky combination of horrible shifts. SUS removed a lot of payload, then pushed up on the platform a lot when they added back. I didn't get a really hard lock on HEPI because I was trying to preserve the aligned position, and it's really hard to reach all of the stops necessary. This means the platform could have moved up, moved the actuators in their mounts (if SUS pushed REALLY hard, seems unlikely) and somehow we have come back down just the right amount for HEPI to look more or less ok. I would expect that if we had come up enough to move the actuators 6mm (presumably when we removed payload or when SUS pushed on the platform with their arm), the platform would come back down and the HEPI actuators would be bottomed out. That's not what I found, so I don't know what's happening here. Anyway, if Jason finds we are still 3 mm high, it means completely re-doing HEPI at that chamber. We should also re-check the level of the ISI at this point. Will probably also require re-doing some tests on HEPI, that we wouldn't otherwise do.
Travis helped me look at the level of the optical table yesterday, and we found the table to be level to within ~.1mm. The cross-hair of the optical level never moved out of the etched line on the ruler as Travis moved the target around, and these lines are <.1mm across. I would take this to be another point indicating that HEPI probably didn't move, it just seems too unlikely that HEPI would move purely vertically.
Jim is the Operator on shift today, but he is needed to help out with work at BSC3 for the ITMx alignment. Here's my summary from 8:15 - 10:55am:
-Troubles with ITMX HEPI position, IAS found 3-6mm height errror, will try releasing HEPI stops to see if it returns -HAM6 OFI/OMC? in chamber is done, ISI needs rebalanced, Robert has measurement to do before unlocking -HAM4 septum coming out soon, so doors need to come off, TVo working on oplev -Richard working on ESD feedthrus bsc1 -Gerardo doing viewport survey, lho drawings incomplete, so we are copying llo's layout -HAM2/HAM3 ISS work coming up -CPB is ready to balance, -Apollo moving storage containers into high bay, drilling/cleaning -NSF Review next week, mostly LVEA and control room
model restarts logged for Tue 17/Jun/2014
2014_06_17 06:22 h1fw1
2014_06_17 11:23 h1lsc
2014_06_17 11:29 h1pslfss
2014_06_17 11:37 h1broadcast0
2014_06_17 11:37 h1dc0
2014_06_17 11:37 h1fw0
2014_06_17 11:37 h1fw1
2014_06_17 11:37 h1nds0
2014_06_17 11:37 h1nds1
2014_06_17 12:13 h1susitmy
2014_06_17 13:00 h1iopsush34
2014_06_17 13:03 h1iopseih45
2014_06_17 13:42 h1iopseih23
2014_06_17 14:17 h1iopseih23
2014_06_17 14:19 h1iopsush2a
2014_06_17 14:52 h1susmc1
2014_06_17 14:54 h1susmc3
2014_06_17 14:54 h1suspr3
2014_06_17 14:54 h1susprm
2014_06_17 14:56 h1hpiham2
2014_06_17 14:56 h1susmc2
2014_06_17 14:56 h1suspr2
2014_06_17 14:56 h1sussr2
2014_06_17 14:57 h1hpiham3
2014_06_17 14:57 h1isiham2
2014_06_17 14:59 h1hpiham4
2014_06_17 14:59 h1hpiham5
2014_06_17 14:59 h1isiham3
2014_06_17 14:59 h1isiham4
2014_06_17 15:01 h1isiham5
2014_06_17 15:04 h1broadcast0
2014_06_17 15:04 h1dc0
2014_06_17 15:04 h1fw0
2014_06_17 15:04 h1fw1
2014_06_17 15:04 h1nds0
2014_06_17 15:04 h1nds1
2014_06_17 18:18 h1fw1
2014_06_17 21:14 h1fw1
2014_06_17 21:20 h1fw1
2014_06_17 21:25 h1fw1
red=unexpected restarts of fw1. light-green=psl/lsc rfpd work, dark-green=IOP-SWWD install, blue=DAQ restarts to support aforementioned work.
Following Dave's changes, I modified HSTS/HLTS/OMC medm screens to have the iop dackill state reported correctly on HAM2 (MC1 MC3 PRM PR3) HAM3 (MC2 PR2) HAM4 (SR2) HAM5 (SRM SR3) and HAM6 (OMC).
Since the upgrade, the state channel names include the suspension name eg. :
old : H1:IOP-SUS_H2A_DACKILL_STATE
new : H1:IOP-SUS_H2A_MC1_DACKILL_STATE
The following files were modified but NOT commited to the svn (they won't be until LLO get the new iop software watchdog)
/opt/rtcds/userapps/release/sus/common/medm/hxts/SUS_CUST_HLTS_OVERVIEW.adl
/opt/rtcds/userapps/release/sus/common/medm/hxts/SUS_CUST_HSTS_OVERVIEW.adl
/opt/rtcds/userapps/release/sus/common/medm/omcs/SUS_CUST_OMCS_OVERVIEW.adl
/opt/rtcds/userapps/release/sus/common/medm/SUS_CUST_IOP_DACKILL.adl
I have installed the new SWWD on the IOP models associated with HAM2,3,4,5.
The SWWD laucher MEDM was updated (see attachment). I have also attached an example of the generic macro substituted detail screen.
Models changed today are: h1iopsush2a, h1iopsush34, h1iopseih23, h1iopseih45. All were built against branches/branch-2.8.
Today, Travis and I discovered that we had incorrect blade tip heights on both the main and reaction UIM masses of the ITMx. The blades were set ~5mm too high causing Jason to sight a high test mass. Joe O'dell from RAL happens to be visiting htis week (on the QUAD design team) so we put him to work helping us lower all 4 blades. Once that was finished, Jason re-observed that we were still ~3-5mm too high. In conversation with Hugh, it dawns on him that one of the height locking stages of HEPI does not have top stops to constrain upward motion. And since we removed most of the QUAD, we think possibly stuff floated upward upstairs (HEPI). We did replace most of the QUAD, but the side constraining HEPI lockers can get jammed into position not alowwing for downward float. Additionally, the use of the install arm to reinstall the QUAD may have created more upward force on the HEPI than intended.
Jim is poised to check for gaps on the bottom HEPI lockers tomorrow morning first thing, after he gets a sub for his operator chair duty.
Made modifications to whitening chassis in racks: ISC-R1, ISC-R2, and ISC-R4. Connected all units back in R1 and R4. In the process of cleaning up cabling and reinstalling electronics in ISC-R2. Work will continue tomorrow.
Day's Activities
--Dust Monitor #6 at HAM6 continues to give faulty readings
Peter, Patrick, Kiwamu and Dave.
The DC readout of the PSL-FSS RFPD cable was connected to the 7th channel of the PSL-FSS ADC. The h1lsc model was changed to remove this channel and the h1pslfss model was changed to add this channel (channel name was not changed in the transition).
In detail,
LSC model PSL top-named part, model file is lsc/common/models/lscpsl.mdl. This had three parts:
filter-module-with-control (all inputs grounded) for RFPD which was removed (moved to h1pslfss)
filter-module-with-control (all inputs grounded) POWER_SCALE which has extensive LSC links and (via IPC) ASC links too. We left this unchanged.
epics-input part (input grounded) POWER_REQUEST which was not used by the model nor any MEDM other than tam.adl. Kiwamu gave permission to remove this.
PSL FSS model, file psl/common/models/pslfss.mdl modified to connect the 7th ADC input to a new standard IIR filter called RFPF_DC
Bottom line: tthe filter module name is still H1:PSL-FSS_RFPD_DC, but is now hosted from h1pslfss and not h1lsc and is a standard IIR filter sans controls.
(Corey, Rick)
Rick and the PSL crew have a procedure for Operators to run through for assessing the performance of the PSL via the DBB (Diagnostic BreaBoard). This is something which should be done on a weekly basis. (takes roughly about an hour). The procedure shows how one runs the measurements and it also generates plots one should post in the alog. Today, we went through the procedure and made a few notes. We were not able to run all the measurements since the FSS was down at the time.
The four DBB measurements we ran were:
We did not get to run the FRQ (Frequency Noise Measurement), since the FSS was being worked on.
Attached are the measurements we ran (they are located at: /ligo/lho/data/psl/psl_noisereports/2014-06-17)
Will post an Operator Procedure for this soon!
I and Dan replaced the bad UL BOSEM unit (SN of bobbin part of that assy is SN250, D0601106-C) with a good one (SN282) pulled out of spare "half-assembled" tip-tilt assy (base plate SN 034).
We also replaced UR one (SN258) with a spare (SN134) that was pulled out of the same half-assembled TT assy simply because we were not sure if the open voltage of SN258 (about 20000 counts) was too small. Later it turns out that 20k counts open voltage is not abnormal.
The newly installed units were of course assembled in the past but without fit check, and it turns out that the gap around the connector was non-existent and I had to loosen some screws and shift things around to make a good gap. I also used aluminum foil shim trick.
After this, we centered BOSEMs for all Tip-tilts to half the open voltage.
UL | LL | UR | LR | |
OM1 | -16k | -12k | -16k | -13k |
OM2 | -11k | -11.5k | -15.5k | -16k |
OM3 | -16k | -14k | -16k | -11.5k |
WFS DC, AS_C QPD, OMCR QPDs, OMC QPDs and OMC DCPDs all responded to flash light.
Beam diverters moved back and forth.
Picomotors moved. On cable #234, the first, the second and the third channels correspond to WFSA, WFSB and AS_C picomotors. On cable #235, the first channel is the downstream 2" mirror for the QPD sled, the second the upstream 1" steering.
Checked ground loops from outside the chamber, and all cables including SUS were good except beam diverters (we know that they ground inside the chamber) and OMC QPDs (shield grounted to the DCPD signal ground) and OMC PZTs (same as OMC QPDs).
OMC PZT cable shielding also is grounded to DCPD signal ground.
Same as OMC QPDs. It's not clear from D1300376 (OMC PZT cable document) but there seems to be continuity from the shield to the mighty mouse connector shell, which is mounted on the aluminum bracket on the OMC.
LLO alog explaining these: https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=10121
As of now, ISI is locked. OMC is free.
Beam diverter cable sheild needs to be cut at the rack or at the chamber.
With the cables disconnected from the remote rack Beckhoff motor driver module, there's continuity between the cable shell and the rack. Relevant cables are cable #316 and #317.
PZT capacitance:
From the outside of the chamber, used a short DB25 and a break out board to check that PZT pins are not short circuited to stupid things. Since I was able to, I also measured the capacitance.
Pin1-14: 474nF.
Pin2-15: 428nF.
These of course include the in-vac cables and short DB25 cable I used outside.
Sounds the correct range for the PZTs. (spec: 470nF)
Correction: Corey found that the S/N of the pulled and newly put in BOSEMs are swapped in the above entry.
Bad BOSEM that has one PD pin grounded to the coil bobbin part is SN282.
Pulled | Newly installed | |
UL | SN282, broken | SN250 |
UR | SN134, turns out that nothing was wrong. | SN258 |
Kyle valved out the Y1 Module for a few hours today. Tomorrow we will valve out the Y2 module.
Attached is the rate of rise for the two end vacuum gauges.
If I have done the math correctly this translates to a very low outgassing rate with no significant leaks : 1.3 e-6 tl/sec for the 2km module. If it is all H2 this yields ~2e-14 tl/s/cm2
Rai reminded me that the gauge factor for H2 is about twice that for N2. So the outgassing rate stated above should be ~2x higher. Rai reports a number of 4e-14 for the H2 outgassing rate when measured 15 years ago.
An accumulation on Y2 was performed today. See the attached plot.
The results are 2.4 e-7 tl/s for the module which translates to an H2 outgassing rate of ~6.6 tl/s/cm^2 (using a gauge correction of 2 for H2)
This is significantly better than Y1.
Also attached is a plot of the two accumulations plotted on the same time scale.
Correction: the number above should be 6.6 e-15 tl/s/cm^2 for the H2 outgassing.