Displaying reports 83901-83920 of 84815.Go to page Start 4192 4193 4194 4195 4196 4197 4198 4199 4200 End
Reports until 17:18, Monday 20 June 2011
LHO FMCS
kyle.ryan@LIGO.ORG - posted 17:18, Monday 20 June 2011 (950)
PT144 alarms
Operators:  Sorry for the nuisance PT144 alarms.  GV14 has been left cracked open to allow IP10 to pump the accumulating hydrogen in the X-1 beam tube module    but obviously it is not open enough as the pressure in X-1 hasn't leveled off -> I will open GV14 a little bit more tomorrow.  
LHO FMCS
kyle.ryan@LIGO.ORG - posted 17:14, Monday 20 June 2011 (949)
Added 2 quarts turbine oil to Kobelco


			
			
LHO FMCS
dani.atkinson@LIGO.ORG - posted 16:07, Monday 20 June 2011 (948)
Ops Day Shift Summary
  • The SUS crew prepared the first test stand in the LVEA to receive an ISI.
  • Gerardo and Gregorio messed with oplevs at MY.
  • SEI crew (Greg) continued HEPI assembly in the LVEA.
  • Assembly of custom clean room #2 proceeds apace.
  • The planned Y-arm peek and laser hazard in the LVEA was delayed until tomorrow morning to give Kyle some time.
H2 INS
greg.grabeel@LIGO.ORG - posted 09:22, Monday 20 June 2011 (946)
HEPI HAM 7

The HAM 7 HEPI frames and crossbeams are now in place and have been brought to nominal position. The set screws in between the HEPI frame and the foot were used to adjust the height and reduce the skew. Working with Scott and Ed the support tubes were able to be brought within 8-12 thousandth of an inch of the specified value.

 

HAM 9 work has already started with removing the old iLIGO equipment and staging the new aLIGO piers and frames.

Images attached to this report
LHO FMCS
jeffrey.kissel@LIGO.ORG - posted 20:44, Sunday 19 June 2011 (944)
MTS 01 Solid Stack Assembly
B. Bland, J. Kissel, T. Sadecki

We put up the remainder of the Solid Stack today on Mechanical Test Stand 01 (MTS01). The rest of the assembly went about as smoothly as yesterday:
- The remainder of the parts that we drilled out yesterday fit reasonably well (as opposed to not at all), but in particular we could only get 4 of 8 bolts into the middle (of 5) Table I-Beam [D050162]. We're pretty sure this is a flaw of the hole pattern in the Lower I-Beam [D050158] design, not the Table I-Beams.
- Other pieces that we didn't fit check yesterday also had holes that just didn't align at all with their mating holes, specifically the angle brackets (Upper Angle [D050165] to the Bridge Wall [D050164], and Short Left and Right Angle [D050167 and D050166] to the same Bridge Wall). We drilled out the Upper Angle bracket, but we intend to just re-make the Short Angle brackets custom, after measuring the hole mismatch.

For now, the Solid Stack is in secure enough shape that we can mount H2SUSITMY (QUAD02) to it tomorrow.

If you haven't gathered already, the Solid Stack drawing package [D0902057] needs some serious cross-checking and red-lining if we're to build any more of these things. A Solid Works model would probably help.

Non-image files attached to this report
LHO FMCS
jeffrey.kissel@LIGO.ORG - posted 21:37, Saturday 18 June 2011 (943)
Solid Stack on Mechanical Test Stand 1 Progress -- Halfway!
J. Bartlett, B. Bland, J. Kissel, A. Ramirez, T. Sadecki

Today we made a valiant attempt to install the freshly cleaned Solid Stack / Dummy ISI onto Mechanical Test Stand 01. Unfortunately, good 'ol Lady LIGO Luck got the best of us about half way through the day. We discovered two problems almost immediately after installing the first few parts.
(1) On the Table I-Beams (D050162), the weldments that merge the I-beam to the dummy optical table occulted bolt holes that secure the dummy optical table to the Lower I-Beam (D050158)
(2) Mounting holes on the mechanical test stand did not line up with bolt holts in the "Tube Mount Ends" (D050156), which are the interface brackets which connect the Lower I-Beam to the Mechanical Test Stand.
(See attached picture pointing out the problem areas)

Sadly, this required some "Class A" power drilling for a good fraction of the rest of the afternoon. Fortunately, the surfaces that must remain Class A (i.e. the downward facing surface of the dummy optical table) remained untouched by the re-working, under foil and ameristat for the whole process; all modifications were done to surfaces that will never touch Class A parts (and all resulting shavings were immediately vacuumed up and/or otherwise removed from the area).

We did managed to get to fit checking the modified parts, and that's where we've left off for the day (see attached pictures).

Non-image files attached to this report
X1 SUS
jeffrey.kissel@LIGO.ORG - posted 20:49, Saturday 18 June 2011 (942)
X1 BSFM01 OSEM Diagonalization
J. Kissel, R. Lane, T. Sadecki

After the blade tip height adjustment of BSFM01, which (sadly) requires the removal of all the BOSEM Coil/Sensor/IRLED assemblies around the M1 mass, they needed to be reattached and aligned. Attached are the results of the alignment: for both V and Y, we show the magnitude of the transfer functions and coherence between Vertical and Yaw Euler basis drive and all six OSEM basis sensors. Given all of the difficulties in adjusting the position the OSEMs with respect to their flags described below, and after several iterations on each, we had settled for "at least 30 dB of decoupling between to the sensitive and independent OSEM basis sensors." We were able to achieve this for both V and Y (though some are better, and in most it's *easy* to get worse). 

Details:
--------
The alignment process is arduous at best, as we've found from our experience with the QUAD:
(1) The flags are cylindrical, so the left-right adjustment is as sensitive to misalignment as the up-down adjustment (where the up-down, left-right plane is perpendicular to the sensitive axis of the OSEM). This is being fixed with the advent of Matt's flat flags, but we've yet to get any on a working system.
(2) The left-right, up-down range of an OSEM Coil/Sensor/IRLED with respect to a cylindrical flag is at most +/-2 mm from dead center (estimated from D1001794 and D060111), so the centering the flag in this 4 sq. mm box by eye is difficult.
(3) The nominal left-right, up-down adjustment for the OSEM Coil/Sensor/IRLED assembly is two CAM nuts (one for left-right, one for up-down), whose motion is controlled by slots surrounding the opposing CAM nut, carved into the adjustment plate (see D060322). The nuts are only mobile when their respective SHCS is loose; then they maybe rotated with fingers. Ideally, one would loosen one came nut and slide the OSEM along the opposing slot, then rinse and repeat for the other nut. However, both CAM nuts must be loose to enable any motion, and even when loose, there is a good deal of static friction to overcome, often resulting in sudden large motions (larger than the 4 sq. mm box). 
(4) There is a fixed peg and diagonal slot in the corner of the OSEM Adjustment plate, which forces the adjustment motion either along its diagonal, or in a sort of rotation about it. This motion forces one to adjust the up-down, left-right motion simultaneously, making it that much more difficult.

But we know all this.

So in order to get a more quantitative measurement of whether the BOSEMs are centered with respect to their flag, we've performed a test similar to what has been done on the QUAD: at single frequency, drive the suspension in Euler degrees of freedom which are supposed to be independent of others (vertical, yaw), and measure the response in all 6 OSEM basis sensors, moving those sensors which should not couple to the Euler basis drive around until that statement is true. Specifically, we drive in Yaw, which should only be visible in F2 and F3, and move around LF, RT, and SD, then we drive in Vertical, and move F1, F2, and F3. 

The specific frequencies used, 1.1 Hz for Vertical and 1.4 Hz for Yaw, were chosen by taking a spectra of all Euler degrees of freedom and looking for a "lonely resonance" that is seen *only* in V (1.1 Hz) or *only* in Y (1.4 Hz). 

The templates for these transfer functions can be found here:
~/SusSVN/sus/trunk/BSFM/X1/Common/dtt_templates/BSFM_OSEMDiagonalization_VtoLFRT_1p1Hz.xml
~/SusSVN/sus/trunk/BSFM/X1/Common/dtt_templates/BSFM_OSEMDiagonalization_YtoF2F3_1p4Hz.xml



Non-image files attached to this report
X1 SUS
jeffrey.kissel@LIGO.ORG - posted 18:27, Saturday 18 June 2011 - last comment - 20:59, Sunday 19 June 2011(941)
BSFM01 Blade Tip Height Readjustment
B. Bland, J. Kissel, T. Sadecki

Before we started the second round of testing, Betsy and Travis, under the advice of Joe O'Dell, wanted to make an adjustment to the blade spring tip heights of the M1 mass on BSFM01. Here was the story up to this point:
- Initial transfer functions showed several resonances much higher than expected, which implied the M1 suspension points ("d's") were off, and that therefore the M1 blade spring tips were too high. 
- The tips were then lowered a little bit (about ~mm), and no effect was observed.
- The tips were then lowered a good deal (several mm), which finally showed results where resonances were returning to the expected values. However, the tip lowering was done qualitatively so it was unclear exactly how far the tips had been lowered. Further, this caused the remainder of the chain to be significantly lower than modeled.
- BSFM01 was taken down (to be replaced by a QUAD).

However -- the story is little bit more complicated that this (see attached .pdf that demonstrates the story): The blade tip is ideally flat, from base to tip. However, because of the short geometry of these blades, (which, when unloaded, are highly curved) they are in reality a little bit curved up at the tip. Further, the procedure up to this point had been to physically measure the type height from a location that was *not exactly* at the blade tip, using gauge blocks placed physically on the blades (see E1000686). If the tip curves up *further past* the measurement point, then it is not representative of the actual tip height. Finally, though the gauge block as little mass, one still might imagine its presence on the blade spring influencing the measurement.

Now that BSFM01 was back up on the Assembly Test Stand, the plan of attack is two-fold. Re-adjust the blade tip heights back to the nominal height, but using a different reference point for measurement: a gauge block resting on the M1 base plate (with M1 locked down in its nominal position), exactly in front of the blade tip suspension point (again, see attachment). According to Joe's calculation, the distance between the the M1 base plate and M1 blade spring tip, with the suspension is under load and free, should be 26.6 mm.

The adjustment has been done; all four blade tips have been adjusted to have this height with respect to the M1 base plate. 

Now on to measurements, to see whether the results are promising!
Non-image files attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 20:59, Sunday 19 June 2011 (945)
Attached are some pictures of the BSFM, including 
- M1 Blade profile pics,
- M1 to M2 wire clearance from the M1 Baseplate, and
- Glamour shots of M2 and M3.
Non-image files attached to this comment
H2 INS
patrick.thomas@LIGO.ORG - posted 16:37, Friday 17 June 2011 (940)
dust monitor LVEA location 4
The dust monitor set for location 4 in the LVEA has been moved into the clean room over the northernmost suspension test stand in the west bay of the LVEA.
X1 SEI
michael.vargas@LIGO.ORG - posted 16:21, Friday 17 June 2011 (939)
BSC Vert. GS13 Chamber #098 Not Working
(Eric A., Jim W., Ken M., Mike V., Vincent L., Rich M.)

BSC Vertical GS-13 Chamber #098, Seismometer LV719

This unit was not working when first used at LHO.  After failing to free the mass by repeated light impacts on the chamber, the Pod was opened and the seismometer inspected.  

Results:
Given a displacement and allowed to come to rest, the mass moved to the bottom of the seismometer and remained there.  All flexures were in good repair, and the mass springs seemed to be in a correct configuration.  The damping gaskets on the mass springs were in contact.  The mass was brought back into its correct position by adjusting the spring knobs.  The seismometer was tested and seen to produce an acceptable signal.  It was re-podded, and placed back onto the BSC-ISI.  

More inspection will be done once the Pod is sent back to LLO.
X1 SEI
richard.mccarthy@LIGO.ORG - posted 12:24, Friday 17 June 2011 (938)
ISI Test Stand
Testers had DAC problems yesterday and were unable to get outputs.  As noted by the SUS team a lot of time was spent looking into this as thought SUS and ISI were related.  They were not.  The AI chassis on the ISI test stand had a blown -15V regulator thus not powering the boards and signals could not pass through.  We fixed the Inductor in question and I was able to see outputs once again.
X1 SEI
corey.gray@LIGO.ORG - posted 02:49, Friday 17 June 2011 (937)
BSC ISI Assembly Status

(Corey, Eric, Jim, Mike V.)

BSCISI #2

Much of today consisted of dealing with large plates.  Basically all the remaining plates for the #2 Assy were brought down from the VPW to the Staging Bldg  (this involved lots of shufflin' & flippin').

The top facing & bottom facing plates of the Optics Table were torqued together.  The Optics Table was then connected to Stage0 (note, the Stage0 Blade Post bolts still need to be torqued [waiting on a wrench]).

Work will now begin on assembling Walls for Stage1, and helicoiling/dowel pinning to the Stage1 Floor and Stage2 Mid-plate.

Subassemblies

(1) Stage0-1 Flexure was assembled.

LHO FMCS
john.worden@LIGO.ORG - posted 23:10, Thursday 16 June 2011 (936)
Gas burst in Y2 module
While opening a gate valve at the Y mid station we believe that an isolated ion pump volume (~1 liter at a few torr) was released into the tube. Pressure in the tube came to the 10^-6 torr range but is back on the way down. Pressure is currently 1^-7 torr at the mid station and 1^-6 at the end station as the gas sloshes about. The pumping is from the Mid station.
Note that this is not a leak.
X1 SUS
jeffrey.kissel@LIGO.ORG - posted 20:15, Thursday 16 June 2011 - last comment - 20:29, Thursday 16 June 2011(934)
X1 SUS QUAD Adventures
D. Barker, J. Batch, J. Kissel, R. Lane

After gleefully and boldly declaring victory yesterday on the upgrade to RCG 2.1.5, the CDS gods had to smite us a little bit, just be sure we still new who was boss. 

Executive summary: 
After some wild goose chases, we achieved the following results for BSFM01 and the X1 SUS Electronics Test Stand (bscteststand2): 
 - The BSFM is running on RCG 2.1.5, with associated GDS software
 - The watchdog behaves as expected
 - We are able to drive OSEM coils in all degrees of freedom using awggui, and measure the response with OSEM sensors in dataviewer and DTT.
 - We are able to retrieve frame builder data from the past.

Lessons Learned:
 - Exceeding the a reasonable amount of the test points (~6) is still bad thing, and can cause all sorts of mysterious badness.
 - Therefore when looking at real-time data, whenever possible we should use frame builder channels (_DQ channels)
 - A good, full, healthy power-cycle of the front end and I/O chassis is never a bad idea after upgrading the RCG and associated software.

Detailed breakdown of today's activities:
 - Robert "prepared" the BSFM using /ligo/svncommon/SusSVN/sus/trunk/BSFM/Common/MatlabTools/Load_BSFM_MEDM_Values.m, in order to restore matrix values, filter bank states, and offsets. (WIN!)
 - While trying to un-trip the watchdog, we discovered a few bugs in the BSFM watchdog front end code and MEDM screens, and fixed them. (WIN!)
 - Discovered some small, but strange noise in *some* of the test point channels -- not a show stopper (WIN!)
 - Once watchdog was reset-able, we attempted to drive small offsets out to the OSEM Coils, using the OSEM Sensors as our figure of merit, without success. However, it appeared that drives made out to the last possible visible point in digital land (i.e. the IOP DAC output channels)
 - Went out onto to the floor to further diagnose the problem by measuring the the voltage coming out of the Anti Imaging Chassis, and our suspicions from the OSEMs were confirmed: no voltage was coming out of the Anti-imaging Chassis. While performing this test we noticed some of the indicator lights on the GDS_TP screens were red (specifically the ones identifying that the user model acknowledges the existence of a DAC card).
 - Somehow, our CDS woes infected the SEI Electronics Test Stand as well, and they *also* found that they could not excite anything out of there DAC.
 - Assuming this was some mysterious flaw in RCG 2.1.x (SUS is at 2.1.5 and SEI is at 2.1.4), we went running to the CDS team. After trying a power cycle of the entire rack, and looking around to see if the timing crates common to botyh systems had anything to do with it (the conclusion was "maybe...?") SUS was able to finally get *some* signals out. Who knows why, our best guess is the power cycling of the rack (though this doesn't solve the same problem for SEI)
 - While attempting to get *other* signals to drive, we discovered craziness in the test points in dataviewer (some with huge digital waveforms, others with just a fixed spike, others displaying rediculously huge numbers), and when the same channels were measured in DTT, the were absent (as though the signal were a bunch of NaNs or something). Again to the CDS crew!
 - After a few minutes of noodling around, we found that our test points were *all* engaged (as read out by the GDS_TP screen), and our channel datarate had exceeded the allotted 2 MB/sec. Remembering the good 'ol "diag -l" > "tp clear *" method of clearing all test points, this magically alleviated the test point craziness. Note that this *did not* remove the small, 89Hz harmonics noise in the L and T TEST excitation channels. 
 - I then moved back to this morning's original goal, make sure that all degrees of freedom can drive, and that drive can be measured by the corresponding sensors. This was a success. The subentry below details how I performed that test, and shows the results.

Comments related to this report
jeffrey.kissel@LIGO.ORG - 20:29, Thursday 16 June 2011 (935)
J. Kissel, R. Lane

In order to assess whether we might be able to drive the new BSFM OSEM coils using the digital system with the new RCG, we developed this basic test that is a good end-to-end measure of exactly that:
Use awggui to drive a single-frequency sine wave into the TEST excitation points (in the EULER basis, e.g. X1:SUS-BSFM_M1_TEST_V_EXC), and with DTT, while watching dataviewer, measure spectra of your drive and corresponding response channels (in both the EULER basis and OSEM basis). As an additional figure of merit (and also so your don't have to drive very hard), one can capture the coherence between your drive and response as well.

The attached pdf shows the results of this test for all six EULER degrees of freedom. 
The frequency of the sine wave chosen to be 11 Hz (where the motivation for that frequency was "pick a place where there's not much going on in the spectra"). 
The drive level for each degree of freedom was:
DOF Drive Strength [cts]
L5000
T2500
V2500
R100
P1000
Y500
where the motivation was "use the minimum amount of drive in order to get a coherence of ~1 in all response channels." Templates for the measurement can be found under ~/SusSVN/sus/trunk/BSFM/X1/Common/dtt_templates/BSFM_DriveAlive_[DOF]_[Counts of Excitation].xml
Non-image files attached to this comment
H2 General
jonathan.berliner@LIGO.ORG - posted 16:46, Thursday 16 June 2011 (933)
Thursday Ops Log
- Delivery for Apollo in the morning to warehouse
- Kyle at BSC10 to prepare for unlocking of H1-ETMY
- H1-ETMY unlocked
- Electrical inspector on site
- Gregorio Tellez at MY for tests
- Richard replaced phone by FMCS workstation in the Control Room
- 4k ITMX and FMX Optical Lever lasers were turned off by Richard
- Fred leads tour to EY and LVEA
- Paul works on H1 PSL electronics
- Dust alarms ring for CS Optics Labs, (Bake Oven and Optics Lab)
X1 SUS
robert.lane@LIGO.ORG - posted 12:34, Thursday 16 June 2011 - last comment - 12:51, Thursday 16 June 2011(931)
X1 SUS Test Stand Test Channel DAQ Noise
J. Kissel, R. Lane

After the recent upgrades to the test stand, we were doing some further 'checkout' testing of the test stand. We were driving small signals and observing for a reaction of the suspension in dataviewer. When we disabled the test signal we observed some noise in a couple of the stored frame builder channels (X1:SUS-BSFM-M1-TEST-L-OUT-DQ, X1:SUS-BSFM-M1-TEST-Y-OUT-DQ), that does not appear in the test points of the same channels. These particular channels receive no input from live sensors, so with out excitation, they should read identically zero. The noise is ridiculously small (~ 1e-21 cts / rtHz), and we only noticed it because dataviewer had auto-scaled it to *look* large. However, other channels appeared to not have this noise, and we just upgraded trying to get rid of other harmonics, so we bring it CDS's attention. 

Spectra show the noise is composed of ~89 Hz harmonics. Curiously, the 7th harmonic (712.125 -- exact frequency limited by the resolution of the quick spectra) appears the loudest at ~2e-19 cts. 

Attached are a amplitude spectra (pg 1) and time series of the noise (pg 2).
Non-image files attached to this report
Comments related to this report
robert.lane@LIGO.ORG - 12:51, Thursday 16 June 2011 (932)
Other interesting notes:

 - Clearing test points does not alleviate the problem.
 - Making the same drive-then-turn-off test on the R0 model (with the watchdog tripped so we didn't run into the two-models-using-the-same-DAC problem), we so no such noise.
H2 DAQ
david.barker@LIGO.ORG - posted 11:54, Thursday 16 June 2011 (930)
CDS H2 install summary

Summary of Rolf's visit 6/6 - 6/15

Installed five front end computers in the LVEA to operate H2 ITMY/FMY cartridge install. IOP, SEI and SUS models were developed and installed, DAQ was configured for this system. SUS model templates were created (both quad and triple), ITMY, ITMX, BS, FMX and FMY were built from these templates.

RCG modified for biquad IIR filter change. Changes were applied to RCG 2.1, 2.3 and trunk.

RMS filter part limits were increased.

Test model was developed for ISI BSC8 electronics checkout.

SEI and SUS medm screens are being built from template files using macro substitution. The MEDM sitemaps and overview screens are being developed to allow efficient access to medm screens.

IRIG-B timing system was installed in the LVEA, all H2 frontends have no timing errors. H2 projector was configured in the control room.

SUS QUAD test stand was upgraded to RCG 2.1.5 (all features except long chan names).

Displaying reports 83901-83920 of 84815.Go to page Start 4192 4193 4194 4195 4196 4197 4198 4199 4200 End