david.barker@LIGO.ORG - posted 10:11, Monday 16 June 2014 (12371)
CDS model and DAQ restart report, Saturday and Sunday 14th,15th June 2014
No restarts reported.
No restarts reported.
Today the PSL is down for maintainence so that means
Frontend is down
PMC is unlocked
FSS is disabled and ref cav unlocked
ISS at 8% diffracted power with 0 volts on PDA and PDB
- Keita working in HAM6
- Fil and Richard working on AA and AI chassis
- Peter, Patrick, and Olli working on PSL maintainence
- Jodi working on 3rd IFO in LVEA
- Robert going out to the vault
- Gerardo working on CPB
I have created new MEDM screens for the new software watchdog (SWWD) system. These are macro substituted screens, launched from H1CDS_SUS_SWWD_LAUNCHER.adl which is accessed from the SITEMAP via the SWWD option under the WD pulldown. Currently there are two new MEDM screens for EY and HAM6.
model restarts logged for Fri 13/Jun/2014
2014_06_13 11:08 h1broadcast0
2014_06_13 11:08 h1dc0
2014_06_13 11:08 h1fw0
2014_06_13 11:08 h1fw1
2014_06_13 11:08 h1nds0
2014_06_13 11:08 h1nds1
2014_06_13 11:11 h1iopiscey
2014_06_13 11:13 h1iscey
2014_06_13 11:13 h1odcy
2014_06_13 11:13 h1pemey
no unexpected restarts. DAQ restart to support SWWD work, ISCEY to clear DAC error.
The attached screen shot ZtorZCoupling.ing shows the meaured transfer function from stage 1 Z drive to the T240 rZ signal (blue line) and the measured magnetic coupling which was done in the staging building, there are only
two points in this measurement as of now. If you divide the measured magnetic coupling by 10 it exactly matches the transfer function, so I'm not sure what is going on there, but the case for the mystery coupling being magnetic is pretty strong.
The attached T240 rZ Signal shows the signal from the T240 rZ (trciky huh?) in low blend mode, with the subtraction in three different states
Blue = OFF
Orange = ON
Red = ON with the wrong sign (gain = -1)
You could convince your self that above 60mHz the subtraction is doing something good (it is mostly aimed at below 100mHz), nothing below 60mHz and something very bad at 60mHz, that you get almost
identical badness at 60mHz for either sign must (might?) mean something
The figure YAW OPLEV shows the same thing using the optical lever signal
The fact that we don't see a factor of 50 improvement isn't very surprising, but the fact that the subtraction makes things worse in the middle of the measurement band is. Right now I'm speculation on drives from other degrees of freedom coupling to the T240s although I
the mechanism isn't very clear to me
We did take a look at rZ to Z coupling, which might create an unindented loop when the subtraction gets turned on, but didn't see anything.
I've been using verious templates in /ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/ETMX/Data and ETMY/Data
The ETMX_Performance ....xml are passive Twist_Measurement ....xml are driven
I've added a few more plots to the T240rZ.... plot
MoreT240Performance
Blue = OFF
Orange = ON
Red = ON with the wrong sign (gain = -1)
Blue
Black Start blend (no T240 in loop)
Green Lower Blend Frequency, ~40mhz pervious ow blend was at ~100mHz (subtraction on)
Purple Lower Blend Frequency (no subtraction)
there are really to many lines here to make an sense of, but as far as the T240 thinks, subtracting hurts at 60Mhz, more interesting is the MoreOpLev plot which shows that above 200mHz it doesn't seem to matter what I'm doing with stage 1 (More OpLev)
if anyone really wants this is all in ETMY_Performance_testbb.xml
Thanks to the efforts of SUS I was able to get in and look at the ring heaters of ITMy today. There are no apparent problems with breakage of either the glass formers or the macor retaining pieces. However, the center macor piece (D1002545) looks to have wandered off center quite significantly. I didn't have any pictures from that angle while the quad structure was still in chamber. So, unfortunately, I am unable to determine when it wandered off, but it definitely warrants looking at ITMx closely before it leaves BSC 3 if possible. It should be noted that this is the older style of ring heater, but the macor element standoff is the same throughout all but the most recent version.
As requested a picture with a few labels, showing how the macor has wandered off the center point where it should be.
The old ring heaters on ITMy have been removed from the old quad structure. While I was packaging the upper and lower ring heater I noticed quite a bit of particulate coming out. Looks like glass, certainly warrants a closer inspection.
J. Kissel Dither paths have been added to the HSTS OVERVIEW screens, completing all development for ECR E1400105 / II 722. I attach a screen shot of the new screen. I also fixed a few bugs found in the QUAD implementation as noted yesterday, and updated the BSFM screen, in which Stuart found some bugs (see LLO aLOG 13048). These screens are also attached. As soon as Stuart gets the model changes for his HSTSs, HLTSs, and QUADs installed, and updates to the new screens, we can close out the integration issue and begin using these paths as need be. Note, that though I committed the dither path changes, I've retained the still-under-development local modifications for the prototype ESD linearization (initially installed a month ago) so the common parts for the QUAD, ${userapps}/release/sus/common/medm/quad/SUS_CUST_QUAD_OVERVIEW.adl ${userapps}/release/sus/common/models/QUAD_MASTER.mdl remain locally modified.
Swapped parts between Mid X and End X weather stations until the defective part was isolated. Left End X weather station up, but the anemometer does not work, which is a separate problem. Temperature is being reported properly for End X. Mid X weather is down until a replacement WeatherLink Isolator can be found.
Work of AA AI work at both end stations is complete. All electronics are powered on and reconnected. Will alog serial numbers of units that were either modified or verified later. When turning on SUS electronics at EX, notice that the output of a Quad Top Transmon Coil Driver(S1102670) was oscillating. Brought unit back to the lab to take closer look. Filiberto / Aaron / Vanessa
- 8:30 am Filiberto and Aaron to Y-End, to retrieve equipment for use at X-End.
- 8:34 am Corey to the CS VEA, continue work on HAM6.
- 9:25 am Filiberto, Aaron and Vanessa to X-End, continue work with AA/AI chassis.
- 9:35 am Margot to the CS VEA, West bay area work.
- 9:56 am Dale and camera crew to CS VEA, film around West bay and HAM6.
- 10:23 am Cyrus to Y-End, computer work.<--- Done by 11:00 am.
- 10:31 am Thomas to CS VEA, computer work channel fix.
- 11:06 am Dave from CS-CR, DAQ reboot.
- 11:09 am Andres to CS VEA, retrieve item for assembly.
- 11:10 am Dave from CS-CR, ISCEY code restart, succesful.
- 12:23 pm Dave and Jim to Y-End, AI chassis investigation.--->Then to X-Mid for weather station work---->Then to X-End for more Weather work.
- 2:16 pm Jim returning to X-End for more weather work.
Corey, Dan
Today we went through Keita's HAM6 Punchlist to get to a point where we could hand off HAM6 to SEI (for balancing/testing) & get HAM6 closed until final HAM6 alignment. Overall, we got through most of the items, but we did have an issue with a Tip Tilt Assy.
BOSEM check of Tip Tilt #2 & #3
Wed/Thurs, OM#2 & OM#3 were removed to cure grounding issues they had (noted in Keita's alogs: here & here). One of the first things we checked was BOSEM positioning, and each Tip Tilt (OM) had one BOSEM which was NOT Centered. BOSEM values should be around |16,000counts|.
Tried fixing #2's UL, but with moving the BOSEM to extremes in/out, later found that the entire optic looked translated (i.e. the "Flags" were all off to the side inside their BOSEMs). They were off so much they were touching the interior of the BOSEM. This is why we couldn't change the UL. See attached photo. We will need to pull this Tip Tilt out and investigate how it's hanging. It must have become messed up during handling to cure grounding.
For OM3, UR was fixed and easily taken to ~16k.
Photodiodes & WFS
After reading Keita's alog and reconnecting cables at the rack & then also seeing that a few chasis boxes were powered OFF, we were able to zip through all of these detectors (by flashing a flashlight on them.
Picomotors
The driver for these guys is not in the rack. So, I had to pull out the Driver, a Tester/power supply, and function generator to test the Picomotors. Once the set up was made we went through each picomotor and confirmed Pitch & Yaw motion. For the record, on the Tester 1 = X & 2 = Y. And when we tested picomotors we discovered 1 = X = Yaw & 2 = Y = Pitch. This was consistent for all Picomotors.
Beam Diverters
The Beam Diverters are connected in Beckhoff Land, so we were able to test these guys easily via their medm screen. I took pictures (attached) of these guys in the "closed" & "open" states.
ISI Unlocked
Before sealing the chamber up, I unlocked the ISI. On Monday, we can work on OM#2, or we can hand off to SEI (I reckon this decision is schedule-dependent). Oh, and we also had the Japanese film crew capture some video of some of our work.
This data is from the second RGA accumulation on Y2.
Following work that has been carried out at LLO this week on SUS guardians, I updated the changes here at LHO.
guardian were reloaded on SRM SR2 PRM PR2 MC1 MC2 MC3 BS ETMX ETMY ITMX ITMY TMSX TMSY
The main change is that the guardian won't be restoring alignment offsets anymore, but will only turn on/off the switches, regardless of the alignment value.
Details are explained in Jamie's alog.
TMSx and TMSy guardians had to be modified, to remove the aligned_to_pd1/aligned_to_pd4 state
Margot, Travis, Betsy
This morning, while being filmed by a foreign camera crew, we pulled the dismantled ex-ITMy lower suspension out of the storage box in the west bay cleanroom. We then used the ergo arm to remove CP09 and the ex-ITMy optic (s/n ETM02). Both were stored in optic cake tins. The lower suspension can now be reassembled with metal masses for a 3IFO QUAD assembly.
Thanks Margot for all the hardwork here at LHO!
I restarted the DAQ (DAQ with a "Q") to sync it up with the new IOP models I installed yesterday.
I restarted h1iopiscey model to clear the DAC (DAC with a "C") error is was reporting, which required restart of all user models on h1iscey. The DAC error was cleared by this restart.
The nds process on x1nds1 did not restart because of a change to the framecpp library, so I recompiled the nds program, installed it on x1nds1, and restarted the nds. Dataviewer can now get data from the past.
When OMC DCPD and OMC QPD in-air cables are both disconnected at the field rack (but connected to the in-vac components via the feed throughs), there is a continuity between DCPD signal ground (pin15, 16 and 19, 20 of the DCPD cable) and the shield of OMC QPD cable. Bad.
DCPD cable shield is not connected to the DCPD signal ground nor OMC QPD cable shield. (Good.)
This cannot happen anywhere except inside the OMC suspension cage, I think. I'm asking Rich Abbott for advice.
The case of the DCPD is at ground potential, and is attached to the incoming DCPD shield. This is OK as the DCPD box is not grounded, and represents the same situation as used in the RFPDs. I would have to assume it's a DCPD cable to QPD cable shield short developed when two cables are bundled in close proximity. A whisker must be sticking out somewhere. It should be fairly easy to track down if you still have physical access to the cabling. Otherwise, provided neither cable is directly shorted to chamber ground, the loop area for electromagnetic pickup in this scenario is far smaller than it would be in a true chamber ground loop. Small consolation if any.
Actually Koji reminded me that we had a similar situation at LLO. See LLO log number 10121. The cable bracket holding the QPD and DCPD cable Mighty Mouse Connectors bridges the shields between these two cables. In the end, measurements confirmed that this small loop pickup problem is not a show stopper. We did conclusively find that any chamber ground on the OMC shields was a big problem.
