Displaying reports 76821-76840 of 84571.Go to page Start 3838 3839 3840 3841 3842 3843 3844 3845 3846 End
Reports until 17:34, Friday 04 October 2013
H1 AOS
keita.kawabe@LIGO.ORG - posted 17:34, Friday 04 October 2013 (8005)
TMS restraint: done (Cheryl, Pablo, Keita)

We've removed temporarily restraint and put the real one in.  TMSX is floating but cannot crash into ETMX.

We left two big wipes on the ISC table to protect the mirrors, which is probably like 0.2 lbs or something total. If this is a problem for you, please feel free to remove them, but take care not to touch or bump any of the mirrors/lenses/detectors on the table.

There are some minor things that should not affect the task of other people, but these should be fixed later before we pump the volume down:

  1. We need one class A 3/8 nut (either aluminum or Nickel Copper alloy) and two washers for a bolt that is necessary when pulling the TMS back away from ETM. We have the bolt but that is not in place for now due to this.
  2. We need two class A pear shaped link parts. For now we're using class B parts, but they should be replaced with class A parts. We'll ask C/B to get two from Thomas and class A them.
  3. Tuned mass damper pins are still in place.

We brought the transport restraint and some in-vac parts that I thought are ours back to the EX lab. I and Pablo didn't label these, they are just layed out on the work table there. For later labeling purpose for our own sake, these are:

  1. Transport restraint turnbuckles and chains. Chains are inside one of stainless steel tubs.
  2. ISC table covers and support rods. Rods are wrapped separately from covers but are put on the covers.
  3. Class B in-air restraint rod assembly for fake Genie. Do never ever confuse this with the class A restraint rods.
  4. Spare parts for in-vac restraint and one 3/8 bolt that are to be installed in EX are in stailess steel tubs.
  5. Some smaller stainless steel bins containing kapton tubing and screws and 1/4-20 nuts (both Nickel-Copper alloy and alluminum).
H1 CDS
david.barker@LIGO.ORG - posted 16:59, Friday 04 October 2013 (8004)
Beckhoff chassis at EX, serial hookup

Jim and Dave.

We noticed that the TCS rack layout was slightly differerent between EX and EY. The EY layout was more optimal, so we made EX the same as EY. This involved moving the PEM BNC patch below all the timing systems, and moving the End Link chassis down 1U. So from the top of the rack we have: timing fanout, comparator, space, serial concentrator, space, End Link Chassis, space, PEM patch.

Daniel provided the serial cables to hook up the fanout. The large 37pin cable was ran from the End Link to the serial concentrator. A 9pin serial was ran from the RS422 output on the back of the fanout to port 5 (lower left) on the concentrator (Daniel says this is the first RS422 port, lower numbered ports are RS232).

I dont see the timing diagnostics data on my MEDM, perhaps something on ex beckhoff needs to be restarted?

H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:28, Friday 04 October 2013 (8003)
Ops Summary
LVEA Laser Hazard
Alarms: FMCS/RO and CDS

08:00 Dave B. - DTM Broadcaster down and front-end DAQ errors, 
           Jim B reset h1broadcast0 and restarted MX-Streams on affected DAQs. 

Apollo working at End-X removing tooling back to the LVEA
Rich A. Testing cables in the HAM1/HAM/2 area

09:00 Paul F. taking MC measurements
09:55 Cheryl and Pablo in LVEA taking measurements
10:09 Gerardo M.Jr doing assembly work in LVEA mechanical test stand cleanroom
11:16 Justin B. at end-x checking laser barriers 
11:48 Stefan B. working in the HAM1/HAM2 area
16:00 several dust alarms in the DR. Justin B and Jeff B checked dust monitor in diode room.   

LHO General
jeffrey.bartlett@LIGO.ORG - posted 14:36, Friday 04 October 2013 (8001)
Modified TS Blade flattening Procedure

   I assembled the TS cartridges for the 3IFO TMS using a modified procedure from that documented in D060370. I removed the big jacking screw that is used to pull flattening roller across the blade. Instead, I pulled the flattening roller out by hand. 

   This seemed to work better than using the screw jack because: 

      (1). It was much faster. Instead of several minutes to run the screw in and out, pulling by hand took just a couple of seconds to flatten the blade. 
      (2). There is little or no contamination generated by the hand pulling process. When using the screw jack one must continually lubricate the jacking screw with alcohol. As the jacking screw turns, it generates a large amount of aluminum shavings. These shavings mix with the alcohol to make a nasty paste, which drips on the optics table the puller is clamped to and the floor. The Teflon bearing the end of the jacking screw rides on also sheds during the pulling process. Both these contamination sources are eliminated when pulling by hand. 
      (3). The jacking screw is a source of binding. The turning of the jacking screw causes the two guide rods on the sides of the puller to twist. This twisting causes the guide rods to bind, which puts excess stress on the guide rods and the jacking screw. The hand pull greatly reduced this problem, but it did not eliminate it. 

   It did take some strength to pull the blade flat, but it was not excessive. There is a possibility the roller could snap back across the blade, without the screw jack holding it in place. However, there are notches cut into the sides of the puller, which the roller bearings drop into when the puller is fully engaged. The force of the blade pushing upwards holds the roller bearings into the notches very securely. In addition, there are holes on either side of the puller just inside the notches the roller bearings fit in. I put a pin through these two holes to act as a safety stop, should the bearings come out of the notches. 

   This process worked as well for disassembly as it did for assembly. The hardest part of the disassembly process was getting the roller bearings out of the notches.  
H1 AOS
sheila.dwyer@LIGO.ORG - posted 12:40, Friday 04 October 2013 - last comment - 16:58, Monday 07 October 2013(7998)
more beam measurements

Joe, Pablo, Cheryl, Sheila

We measured the beams coming out of the HAM2 viewport, with the nanoscan head 2 feet 6 inches from the viewport.  (in the first version of this alog I wrote the wrong distance)

For the brighter beam we measured beam diameters: 2549 um horizontal, 2632 um vertical.  after rorating the scan head 90 degrees we measured 2650um vertical, 2561 um horizontal.  

For the dim beam we measured 7160um vertical, 5972 um horizontal after rotating  by 90 degrees we got 6077um horizontal 5865um vertical. 

We also measured the beam in HAM1, in the same location as wensday (we move the BS for the RF PD to 16 inches after M2, we put the nanoscan 40 inches after the BS, there we got 4025 um vertical, 4126 horizontal.  After rotating the head 90 degrees we got 4045 um vertical 4020um horizontal.  

Comments related to this report
guido.mueller@LIGO.ORG - 13:43, Friday 04 October 2013 (8000)
Hi Sheila,

Can you be a little more specific which beam you measure where? 
The 4000um diameters sound good but I don't know what you mean with the brighter beam and what with the dimer beam.
sheila.dwyer@LIGO.ORG - 21:48, Saturday 05 October 2013 (8011)

Hi Guido-

I believe the brighter beam is the reflection off of PRM, although I haven't looked at the layout to double check.  As you face the viewport, near the veiwport the dim beam is on the right while the bright beam is on the left.  If you move to about 3 feet away from the viewport they cross, and the dim one is on the left if you are facing the veiwport.  Pablo watched the spots on the wall as I moved the PRM alignment, and the bright one moved.  

sheila.dwyer@LIGO.ORG - 15:14, Sunday 06 October 2013 (8013)

I should have been more clear, the first two measurements are of beam sizes for SM2 trans, coming out of the HAM2 veiwport where IOT2R would normally be. 

paul.fulda@LIGO.ORG - 09:32, Monday 07 October 2013 (8017)

Looking at the table layout for HAM2 (D0901083), I would expect the SM1 forward trans beam (from PMMT2 a.k.a. IM3) to be the dimmer beam, since this beam is split twice before making its way to the viewport. The SM1 return trans beam is not split at all before getting to the viewport. (I think you already came to this conclusion).

From the model, using rather rough estimates for the distances after IM4 transmission (+/- 2 inches), we expect that the SM1 forward trans beam (dimmer beam) where you measured it should have diameters of 6.20mm horizontal and vertical. The SM1 return trans beam (brighter beam) where you measured it should have diameters of 2.68mm horizonal and 2.67mm vertical. Not so far away from what you measured...

I'll try to get more precise numbers for the after-IM4-trans distance from Luke and update accordingly.

paul.fulda@LIGO.ORG - 09:45, Monday 07 October 2013 (8019)

Apologies, everywhere I wrote "SM1" I meant "SM2". Or IM4, they are the same mirror.

sheila.dwyer@LIGO.ORG - 11:34, Monday 07 October 2013 (8020)

SM2TransReturn1.png is a screen shot of the nanoscan program with the bright beam, when apperature 1 veritcal. 

SM2TransForward1.png  the dimmer beam, first with Apperature 1 horizontal then SM2TransForward2.png is with the apperature 1 vertical.  

I haven't figured out how to export data from the software, and I can't uplaod .nsd files to the alog, but if anyone wants the data it is available at http://www.ligo-wa.caltech.edu/~sheila.dwyer/NanoScanData/IO/

You can use the free Nanosan software from Ophir/ Newport to open these files. 

We saw that the Forward beam looks like it could possibly be clipping, Joe tried to move the location of the nanoscan head but the beam profile didn't get any better. 

Images attached to this comment
paul.fulda@LIGO.ORG - 15:27, Monday 07 October 2013 (8028)

Just an update on the expected beam sizes with more accurate distances used in the model (good to 1/4" or so, inlcuding IM4 substrate and viewport substrate effect):

SM2trans forward 2wx=6.349mm, 2wy=6.3455mm

SM2trans return 2wx=2.6813mm, 2wy=2.6697mm

sheila.dwyer@LIGO.ORG - 16:58, Monday 07 October 2013 (8031)
H1 PSL
paul.fulda@LIGO.ORG - posted 12:29, Friday 04 October 2013 (7997)
ALS beam blocked on PSL

To make the process of inserting the pick-off BS for the Faraday isolation ratio measurement easier, we blocked the ALS beam around the same location on the PSL table with a razor dump.

At the time of writing this, that beam is still blocked.

H1 CDS
david.barker@LIGO.ORG - posted 12:28, Friday 04 October 2013 (7996)
restarted web medm snapshots for H1

I restarted the web medm snapshooter for the H1 screens to capture the new state-word overview screen with added Y-end models.

H1 SEI
hugh.radkins@LIGO.ORG - posted 12:19, Friday 04 October 2013 (7995)
WBSC8 ETMX Friday Noon Update
Thomas, Mitchell & Jason got the majority of the fixturing out of the chamber, bagged & wrapped, and out of the VEA.  They then got the retroreflector hanging on the Quad.
We then unlocked the HEPI and leveled & set the elevation of the Optical Table per D0901152.  I set the system ~.5mm low as IAS found the Optic 0.4mm high on the Test Stand.  The level is within +-0.1mm and the elevation is within 0.3mm; good enough since we still likely have much horizontal adjustment to do.
With the retroreflector in place, we then shot an X position.  IAS is still evaluating that result.
LHO General
patrick.thomas@LIGO.ORG - posted 11:25, Friday 04 October 2013 (7993)
Turning off dust monitor 8 appears to kill dust monitor 9
I noticed this morning that dust monitor 9, which had previously been dropping in and out of communication, was no longer coming back. I went out and looked at it, but didn't notice anything obvious. I also managed to smack my head on one of the light pipes between the H1 PSL enclosure and HAM1.

I connected to the IOC screen, pressed Start on the medm for the dust monitor, and got a read timeout reported by the IOC.

I then trended the mode back, which should oscillate from 'holding' to 'running' every minute, to see when communication was lost. Seeing that it stopped yesterday, I compared it to dust monitor 8, which I had turned off and removed yesterday. The two times are in close agreement (see attached plot).
Non-image files attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 10:30, Friday 04 October 2013 (7992)
DAQ restart last night caused some DAQ errors

The DAQ was restarted twice yesterday evening at 20:15 and 20:50 local time. The second restart precipitated two problems:

The front ends affected were: h1susauxex, h1susex, h1pemmx, h1lsc0, h1susauxey, h1seib2, h2seib3, h1susbstst, h1susauxh2, h1sush56, h1sush34, h1sush2b.

All data from these front ends will have been marked as bad (zero'ed) in the frames between 03:51 and 16:11 UTC today, 4th October.

Jim restart h1broadcast0 and restart MX-Streams on the affected front ends to restore the DAQ.

LHO General
patrick.thomas@LIGO.ORG - posted 10:27, Friday 04 October 2013 (7991)
plots of dust counts
Attached are plots of dust counts requested from 4 PM October 2 to 4 PM October 3.
Non-image files attached to this report
LHO General
john.worden@LIGO.ORG - posted 10:00, Friday 04 October 2013 - last comment - 12:06, Friday 04 October 2013(7990)
LVEA Purge Air Compressor Kobelco

The purge air system is up and running again. The Kobelco air compressor had shut down on an over temperature alarm which has been determined to be an open circuit RTD.

As a temporary fix a 1k resistor has been installed in place of the RTD.

 

Temps now after one hour of run time are:

 

1st air discharge - 287F

2nd air suction - 85 F

2nd air discharge - measured at 210F Front panel says 65F(1k resistor)

lube oil - 104F

Comments related to this report
john.worden@LIGO.ORG - 12:06, Friday 04 October 2013 (7994)

Temperatures remain the same at 12:00

H1 ISC
christopher.wipf@LIGO.ORG - posted 08:08, Friday 04 October 2013 (7986)
EY Beckhoff running

Yesterday Filiberto cabled the EY Beckhoff system, and we started it up.  We now have the full complement of Ethercat systems up and running for H1.

Fiber links from the corner to both end stations were verified to be working (by looking at their keepalives in Twincat).  Also, the Acromag binary I/O at both end stations was checked, by looking at the whitening readbacks in EPICS.  At EY, you could move the whitening sliders and switches around and everything worked fine.  But the EX screens showed errors.  It turned out that the Acromag chassis (S1203593) needed to have its network settings configured (following the procedure in T1100607). After this was done, the EX screens worked, and using the digital I/O test harness, I verified that the Acromag chassis outputs were actually switching.

Finally, I made a script to start Maggie's EPICS IOC on h1ecaty1 (analogous to the one found on h1ecatx1). This temporary EY script is located at: C:\SlowControls\EPICS\Utilities\Bin\start_h1y1.bat

H1 ISC
jeffrey.kissel@LIGO.ORG - posted 23:17, Thursday 03 October 2013 (7984)
Online Detector Characterization Channels implemented to the H1 IMC ASC
J. Kissel, S. Ballmer, D. Macleod, R. Fisher  

In order to further my quest to have data analysts use the IMC as their new fake gravitational wave channel, such that the *real* DetChar can begin, (and OK, because the ODC is now a blessed and essential portion of the aLIGO scope) I've installed the an Online Detector Characterization channel into the H1 ASC IMC model. This new channel is H1:IMC-ODC_CHANNEL_OUT_DQ, sampled at 2048 [Hz]. Details of the bit descriptions are outlined below. I have tested its functionality by creating a disgustingly basic MEDM screen linked off the top left corner of the IMC Overview screen (see attached) and testing that the bits all have the expected behavior -- all but one behave as expected*. The IMC runs as smoothly as it did before I got started.

Since there are a few new filter banks, a whole bunch of new epics records, some screen changes, and a front end model change, I've made sure to re-capture a new safe.snap, and have committed all of the following to the repo:
/opt/rtcds/userapps/release/asc/h1burtfiles/h1ascimc_safe.snap
/opt/rtcds/userapps/release/asc/h1models/h1ascimc.mdl
/opt/rtcds/userapps/release/asc/h1filterfiles/H1ASCIMC.txt
/opt/rtcds/userapps/release/ioo/h1/medm/IMC_CUST_OVERVIEW.adl
/opt/rtcds/userapps/release/ioo/common/medm/IMC_CUST_ODC.adl

where "safe" is a fully operational system, just with the WFS master switch off. Note that I've made several modifications to the prototype version provided to me by Ryan and Duncan, but the modifications were based on conversations with Stefan, and to otherwise increase clarity of the system.

Note that the addition of new filter banks meant I had to restart the DAQ / Data concentrator (twice, because I'd misspelled one of the new filter banks).

Also, it really seems like these WFS loops are oscillating way too much. We should look into why, or Paul's going to be very sad tomorrow when he measures the beam jitter of the IMC.

Finally, though Cheryl said she'd just aligned the Broad Band PD gathering the leakage beam at the bottom of the PSL periscope to determine the power going into vacuum, its channel (H1:IMC-PWR_IN_OUTPUT) is showing a dead -29.89 [ct].

----------------
Bit description:
----------------
There are 13 bits associated with this channel:
BIT1 : Indicator of whether the IMC ASC control system is requested to be on. This compares 
- the final product of the trigger from IMC transmission PD (just after IM1, indicating the length control is on and the cavity is locked [H1:IMC-TRIG_MON]), 
- the WFS masterswitch (H1:IMC-WFS_SWTCH), and
- the WFS master gain (H1:IMC-WFS_GAIN) 
against unity. If all are three components are one, then their product will be one, the WFS are requested to be turned on, and the bit goes high.
* I can't get this bit to turn green. I think it's because the master switch is and EPICs Binary as opposed to a standard EPICs Input. The product of these three things seems to be zero, yet the WFS are on and servo-ing just fine. We'll have to debug this tomorrow.

BIT2, BIT3, BIT4, BIT5 : Indicative of the control pitch system operating as expected, with small error signals, and therefore the IMC is well-aligned. (The equivalent of) H1:IMC-DOF_[1,2,3,4]_P_IN1 -- the error points of the WFS loops -- are low-passed in the banks H1:IMC-ODC_DOF[1,2,3,4]_PIT_ERRFILT. If the absolute value of those low-passed error points are less than a pre-defined threshold (H1:IMC-ODC_DOF[1,2,3,4]_PIT_MAX), then BITS 2, 3, 4, and 5 go high. 
As the IMC ran while commissioning the ODC channel, I found that threshold values of 10000, 10000, 10, and 10 [ct] for DOFs 1, 2, 3, and 4 PIT make these bits go green most of the time. However, we should use the H1:IMC-ODC_DOF[1,2,3,4]_PIT_ERRFILT banks to calibrate the WFS Error points into physical units, and use thresholds that make sense. 
Just for testing purposes, I've tossed in a 0.3 [Hz], 4th order Butterworth as the low pass. I'm sure more thought could be put into this. These filters are in FM1 of the ERRFILT banks, and called "0.3HzLP."

BIT6, BIT7, BIT8, BIT9 : Indicative of the control yaw system operating as expected, with small error signals, and therefore the IMC is well-aligned. (The equivalent of) H1:IMC-DOF_[1,2,3,4]_Y_IN1 -- the error points of the WFS loops -- are low-passed in the banks H1:IMC-ODC_DOF[1,2,3,4]_YAW_ERRFILT. If the absolute value of those low-passed error points are less than a pre-defined threshold (H1:IMC-ODC_DOF[1,2,3,4]_YAW_MAX), then BITS 2, 3, 4, and 5 go high. 
As the IMC ran while commissioning the ODC channel, I found that threshold values of 10000, 10000, 10, and 10 [ct] for DOFs 1, 2, 3, and 4 YAW make these bits go green most of the time. However, we should use the H1:IMC-ODC_DOF[1,2,3,4]_YAW_ERRFILT banks to calibrate the WFS Error points into physical units, and use thresholds that make sense. 
Just for testing purposes, I've tossed in a 0.3 [Hz], 4th order Butterworth as the low pass. I'm sure more thought could be put into this. These filters are in FM1 of the ERRFILT banks, and called "0.3HzLP."

BIT10 & BIT11 : Indicative of whether there is the expected amount of power input into the IMC, as measured by the MC2 TRANS QPD behind MC2 on HAM3 . The QPD's SUM (H1:IMC-MC2_TRANS_SUM_OUT_DQ) is compared against a threshold (H1:IMC-ODC_MC2_TRANS_SUM_MIN). If higher than the threshold, BIT 2 goes high. If the the SUM is greater than the input power (as measured by a Broadband PD measuring the leakage beam just behind the PSL's Periscope, H1:IMC-PWR_IN_OUT) times some multiplier (H1:IMC-ODC_MC2_TRANS_PWR_IN_MULT, the expected loss between the output of the PSL and the MC2 TRANS QPD) then BIT3 goes high.

BIT12 & BIT13 : Indicative of whether there is the expected amount of power coming out of the IMC, as measured by the IM4 TRANS QPD behind IM4 on HAM2. The QPD's SUM (H1:IMC-IM4_TRANS_SUM_OUT_DQ) is compared against a threshold (H1:IMC-ODC_IM4_TRANS_SUM_MIN). If higher than the threshold, BIT 4 goes high. If the the SUM is greater than the input power (as measured by a Broadband PD measuring the leakage beam just behind the PSL's Periscope, H1:IMC-PWR_IN_OUT) times some multiplier (H1:IMC-ODC_IM4_TRANS_PWR_IN_MLT, the expected loss between the output of the PSL and the IM4 TRANS QPD) then BIT5 goes high.
Images attached to this report
H1 ISC
sheila.dwyer@LIGO.ORG - posted 18:17, Thursday 03 October 2013 - last comment - 09:20, Friday 04 October 2013(7981)
HAM1 mode matching

If the beam entering HAM1 has the parameters that Paul calculated it should have, we could optimize the refl telescope by moving RM1 1.6 inches closer to HAM5, and M5 1 inch closer to the PSL. This would give us gouy phase seperations close to 90 for both the tip tilts and the WFS.  If we do this, and the beam entering HAM1 is in reality the value we measured yesterday, the gouy phase separations will still be above 70 degrees.  

Here are the separation caluclated in both cases:

  Paul's beam X Pauls beam Y Measured X Measured Y
WFS -89 89 74 76
TT -89 -88 84 77

I've attached the a la mode script I used.  

figure(11)
zz = 2:1e-2:5;
PaulsBeamX.plotSummary(zz)
shg
 
figure(12)
PaulsBeamY.plotSummary(zz)
shg
Non-image files attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 09:20, Friday 04 October 2013 (7988)

Even if we move both RM1 and M5 both 1 cm too far, all the gouy phases (for both the measured and calculated beams) stay above 60 degrees.  (same is true if we move them both 1 cm less than we should).  So the tolerances on these positions are fairly loose.  

Non-image files attached to this comment
H1 SUS
douglas.cook@LIGO.ORG - posted 15:27, Thursday 03 October 2013 - last comment - 09:10, Friday 04 October 2013(7976)
SI Fibers in Dry Storage Cabinet Damaged from Soot and from Pulling Process
While investigating the smoke/fire damage to the dry storage cabinet used to store the finished SI fibers I also noticed an excessive amount of soot on most of the fibers caused by overheating the fibers at the end of the pulling process. The amount of soot would likely have render the fibers unusable due the the soot coating the fibers. During the pulling process it is necessary to shut the laser down within 1 second of completing the pulling cycle or a concentrated heat load occurs that emits a white soot that covers the end of the fiber which also rains down the fiber and under cuts the fiber. We use a vacuum system to pull the fumes away during this process that also showed excessive amount of soot in the clear vacuum hose. We need to be more aware of this during the next run. I will reiterate this on the next run and possible automate a laser kill switched.

Image 2799 shows the soot from both sources, white from over heated fiber and black from dry cabinet smoke.
Image 2806 fiber coated with white soot and ring where the fiber was under cut.
Image 2810 ring groove
Image 2811 assembly with clamp block, fibers and angle stiffeners.
Image 2820 is the dry storage cabinet showing the soot from the fried power supply in the desiccant regenerating box. Cause is under investigation, possible power surge(?)

Images attached to this report
Comments related to this report
norna.robertson@LIGO.ORG - 09:10, Friday 04 October 2013 (7987)
I have sought comments on the white "soot" on the fibre ends. I quote Angus Bell's response.

"I see nothing here that would require any change in procedure. The fibre ends showing the white soot also show the clear line between "soot" and "no soot" as the polish "up" stage removes the soot that accumulates on any part of the fibre that will be used. These white bits are scribed off. The polish stage lasts about 20 mins whereas the pull is 20 seconds and the time when the laser is on after the pull is only a couple of seconds. So any vapour production at each stage will be proportional to that time. The tube that goes to the vacuum will slowly fill with soot - that's what it does."

With regard to the time between switching the laser off, Alastair Heptonstall informs me
"I would say that the laser is shut down time after the pull is less than one second.  There's an audible click when the solenoid brakes are applied to the motors, and I use that as the cue to turn off the laser."

In conclusion these fibres would have been usable. It is very unfortunate that we had a problem with the cabinet. This is under investigation.
H1 ISC
rich.abbott@LIGO.ORG - posted 19:12, Wednesday 02 October 2013 - last comment - 15:49, Friday 04 October 2013(7970)
HAM1&6 ISC Electronics Installation Work
Stefan, Alexa, Rich

HAM1:
1.  All in-air and in-vacuum cabling associated with the ASC detectors,  LSC detectors, and Pico motors have been run.  The in-air cables still require termination in TNC at the rack.
2.  All in-vacuum cabling has been run for the tip-tilts, and the cables have been mated to the tip-tilt stages.
3.  Cables for the beam diverter are attached at the flange, but not run to the diverters yet as one connector set was missing the helicoil inserts.
4.  Operational check was performed on all 4 pico motors, and all axes are correct

HAM6:
1.  All in-vacuum RF detector coaxial cabling is attached at the flange, but not yet run to the racks.

What's Next:
1.  Fix cables requiring helicoils
2.  Hook up and test beam diverters
3.  Mount all in-vacuum detectors and verify proper operation
4.  Clean up in-vacuum cable routing and ensure all is well constrained
5.  Terminate all in-air RF cables at their respective racks
6.  Install tip/tilt coil driver in the ISC R4 rack and test operation in HAM1 through installed air and vacuum cabling

Comments related to this report
alexan.staley@LIGO.ORG - 13:26, Friday 04 October 2013 (7999)

Update on status:

 

 - Helicoils fixed (Rich).

 - Beam diverters hooked up and tested. The beam diverters work, but there is a flip between REFL/POP somewhere in the chain between Beckhoff and the actual BDIVs. The easy option is just to flip the cables attached to the BDIVs; the harder route is to track where the flip happens and fix it (Alexa, Joe, Sheila).

- HAM 1 RF in-air cables have been terminated with TNC. The LSC RF cables have been connected to the proper patch panels; however, ASC RF cable are not. HAM 6 RF in-air cables remain to be terminated (Alexa, Rich).

- In the process of checking RF cable connections; about 1/3 of the cables are not properly connected (Rich, Alexa).

alexan.staley@LIGO.ORG - 15:49, Friday 04 October 2013 (8002)

(Alexa, Rich, Stefan, Kiwamu)

 

We found a swapped wire inside HAM 1; now the beam diverters are properly connected (following the wiring diagrams) and working. 

Displaying reports 76821-76840 of 84571.Go to page Start 3838 3839 3840 3841 3842 3843 3844 3845 3846 End