Displaying reports 75481-75500 of 85564.Go to page Start 3771 3772 3773 3774 3775 3776 3777 3778 3779 End
Reports until 16:02, Thursday 27 February 2014
LHO General
gerardo.moreno@LIGO.ORG - posted 16:02, Thursday 27 February 2014 (10392)
Operation Summary

8:50 am, Arnaud running transfer functions @ ITMY.
8:55 am, Andres to LVEA, to work on or around the test stands, West bay area.
9:04 am, Hugh to LVEA, work at HAM5.
9:10 am, Jim B and Cyrus R working at Mid-Y.
9:27 am, Rick S, Craig C, and Chirs S to the LVEA, work inside the H2 PSL enclosure.
10:22 am, Kyle R, to LVEA, crane RGA equipment over Y-arm tube, he finished craning at 10:48 am.
10:30 am, Dave B, reboots and restarts for h1seih23.
11:49 am, Hugh, to LVEA, pick up tools from around HAM5.
1:35 pm, Kyle R, to LVEA, working with the 1.5" valve at gauge pair 124.
2:19 pm, Cyrus R and Jim B picking up hardware from Mid-Y, to retrive to EE shop.

H1 SUS
betsy.weaver@LIGO.ORG - posted 15:45, Thursday 27 February 2014 (10390)
PUM glass processing continued

Gerardo, Betsy

After having one failed ear bond early in the week on PUM ITM03, Gerardo sucessfully bonded both ears.

 

We also loaded PUM ETM06 (destimed for ITMx PUM replacement soon) onto the table and glued it's flag mounts and first of 2 prisms.  We'll get to the 2nd prism tomorrow hopefully.

H1 SUS
betsy.weaver@LIGO.ORG - posted 15:42, Thursday 27 February 2014 - last comment - 10:07, Friday 28 February 2014(10389)
WBSC10 ETMy SUS cables

While in the chamber, we also connected the 5 SUS and 1 ring heater cables to the feedthru and confirmed signal throughput on the 5 sus.  We pulled the C3 covers from both of the ETMy and TMSy suspensions before installing the corner cube. 

 

Jason and Doug should have a clear shot of the corner cube (and probably the edges of the optic) through the ACB from the spool.  We await X,Y,Z measurements.

Comments related to this report
betsy.weaver@LIGO.ORG - 10:07, Friday 28 February 2014 (10391)

In-vacuum ETMy SUS cable serial numbers:

 

Floor 1 of CB  D1000225-S1104879 to D1000234-88"- 941

Floor 2 of CB  D1000225-S1l04881 to D1000234-88" - 942

Floor 3 of CB  D1000225-S1104882 to D1000234-88" - 940

FLoor 4 of CB  D1000225-S1104880 to D1002522 - 924

 

Floor 1 of CB  D1000225-S1104883 to RH cable

Floor 2 of CB  D1000225-S1104878 to D1002522 - ? (ETMy L2 stage)

 

All are plugged into feedthrus on the F3 port of the chamber as per the WBSC10 D1200111 cable routing doc.

H1 SEI (INS)
hugh.radkins@LIGO.ORG - posted 14:59, Thursday 27 February 2014 (10387)
WBSC10 ETMY SEI Activities and Status

JimW & MitchellR

We payloaded the ISI Keel with the 600 lbs per D1002266-v1 (v1 really?); each 150lb stack sitting on 8 in2 of 1/4" thick viton.  See photo.

With that completed we unlocked HEPI and floated the platform (~15000lbs) on the HEPI DSCW Springs.  Next we shot level/elevation of the Optical Table.  See attachment for log notes.

The table actually started out pretty good, I thought we had disturbed it more during float.  The level had about 0.5mm runout and the elevationi was low 1.3 mm--all within spec.  We adjusted anyway to be 0.3mm runout and 0.2mm high.

Mitchell then joined Jim in chamber and moved the ACB deep into the Spool.  I then helped Betsy put the lift table into the chamber.  Jim & Mitchell moved the Table into the Spool and set the ACB atop the table.  Betsy & Travis were working to install the retroreflector for the IAS Y shot while Jason & Doug were getting their equipment readied,

Images attached to this report
Non-image files attached to this report
H1 TCS (TCS)
thomas.vo@LIGO.ORG - posted 14:14, Thursday 27 February 2014 - last comment - 13:08, Friday 28 February 2014(10378)
ITMY Ring Heater
The readback channels for the corner station ring heaters seem to not have been working properly since last Friday.  I've attached a graph that shows that the ring heaters seem to have turned off at 02-21-2014 22:5:32 UTC.  Judging from the ALOG around that time, there were a lot of reboots going on in software, I'm not sure about hardware reboots.  However, Kiwamu says that the PRC power level is looking like the ring heaters are on just based off of the amount of loss he measured.  He also advised that since the system is working well, I should hold off on trying to power cycle the TCS chassis until a later time but at the first chance I get, we should try to resolve this issue.

The ITMX ring heater is also displaying similar weirdness, which is expected since they share the same chassis and PLC.
Images attached to this report
Comments related to this report
thomas.vo@LIGO.ORG - 13:08, Friday 28 February 2014 (10415)
Kiwamu, Sheila, Thomas

This morning seemed to be a good time to investigate this issue.  At first we saw that the PLC3.pro was connected to EPICS but not to the System Manager, i.e. the ADC channels were not getting from the hardware to the TwinCAT software.  We tried re-running the install scripts but it did not fix the problem but it did help us figure out that there were some channels deleted recently.  Daniel let us know that if there are some additions or deletions, we should re-map the configuration before recompiling.  This solved the problem!
H1 ISC
jaclyn.sanders@LIGO.ORG - posted 13:07, Thursday 27 February 2014 - last comment - 10:19, Friday 28 February 2014(10382)
COMM PLL repairs

(Alexa, Jax, Stefan)

Alexa was trying to hunt down a missing gain factor for her model and instead found a busted COMM PLL board (serial number S1200564). The op-amp for the VCO compensation stage (U37) was blown. I recalled replacing the same op-amp on the DIFF PLL about a month ago, suggesting that there's something that makes this particular op-amp vulnerable. After discussing with Richard McCarthy, we opted to change resistor R96 from 0 to 2k ohms to protect the poor thing. Lab tests show that it's in good shape, and it'll be back to the ISC rack as soon as we're done with the ISC meeting.

Comments related to this report
peter.fritschel@LIGO.ORG - 13:51, Thursday 27 February 2014 (10384)

Should this resistor change be propagated to all PLL boards?

jaclyn.sanders@LIGO.ORG - 13:56, Thursday 27 February 2014 (10385)

No, we're still thinking about it. It's going in as modified and if it keeps having problems, we'll burn that bridge when we get to it.

jeffrey.kissel@LIGO.ORG - 10:19, Friday 28 February 2014 (10406)
This smells of an ISC integration issue so we don't forget...
H1 DAQ (CDS)
james.batch@LIGO.ORG - posted 12:35, Thursday 27 February 2014 (10381)
Default NDS server changed to h1nds0
Due to ongoing problems with h1fw1, the default NDS server has been changed to h1nds0.
H1 CDS
cyrus.reed@LIGO.ORG - posted 12:08, Thursday 27 February 2014 (10380)
Core Switch Configuration Change

I have changed the core switch configuration to no longer forward broadcasts on udp port 5355 to the FE network now that DTT has an environment variable to do this, and said environment variable has been configured.  This will reduce some broadcast traffic on the FE subnet, as well as correct some other side effects that probably only I care about.

H1 CDS (SEI)
david.barker@LIGO.ORG - posted 11:35, Thursday 27 February 2014 - last comment - 18:50, Thursday 27 February 2014(10379)
all models on h1seih23 restarted to clear frozen DAC outputs

Fabrice, Jamie, Jim, Dave

I restarted all the models on h1seih23 to clear the no-DAC-output problem.

Sequence was: stop user models, restart IOP model, start user models

models are h1isiham2,3 h1hpiham2,3 h1iopseih23

Fabrice then put ISI ham 2,3,4,5,6 into a safe state, and I updated the safe.snap files in SVN and committed them.

Comments related to this report
keith.thorne@LIGO.ORG - 18:50, Thursday 27 February 2014 (10395)
Has the /etc/startWorld.sh script been installed on H1 front-ends?  That is what is used at L1 for these restarts.
H1 CDS (SEI)
jameson.rollins@LIGO.ORG - posted 10:16, Thursday 27 February 2014 (10375)
h1seih23 DAC communication problems

This morning when I came in I found the HAM2/3 ISIs tripped.  I have tracked this down to what I believe to be a DAC communication problem in the front end.

While the models show output on their DACs, the IOP shows no corresponding DAC output on the same channels.  There are no error flag whatesoever to indicate that there might be a problem.  None of the watchdogs on this machine are currently tripped.

The image below show the DAC_MONITOR screens for H1IOPSEIH23, which shows zero on all outputs, and H1ISIHAM3, which shows and output of -958 counts on CH 8.

Images attached to this report
H1 CDS
james.batch@LIGO.ORG - posted 09:30, Thursday 27 February 2014 (10373)
New dataviewer installed
The dataviewer program has been updated for Linux and Mac OS X to correct issues with leap second handling and to allow short channel names to be selected from the menu.  Current version is now dv-2.8.1
H1 ISC
daniel.sigg@LIGO.ORG - posted 09:14, Thursday 27 February 2014 (10372)
Doubler for 79.2MHz moved

Filberto, Daniel

We moved the doubler which drives the ALS fiber distribution box from rack ISC-R1 to ISC-R4. This hopefully reduces the electronics crosstalk between this unit and the PSL VCO. We als used a differemt RF patch panel in ISC-R2. The RF power levels have been re-measured, requiring to change the attenuator at the ALS fiber distribution chassis input from 1dB to 3dB.

H1 SEI (ISC)
stefan.ballmer@LIGO.ORG - posted 08:03, Thursday 27 February 2014 - last comment - 14:35, Thursday 27 February 2014(10370)
Question to the ISI team
I just spent another hour turning on ISI ETMX. (see previous elog for ITMX.)

This seems to me that most of the turn-on trouble comes from our attempt to turn on loops in an equilibrium position, and afterwards move to the target position. This move then leads to DC saturations in various sensors.

Question:
Why don't we put in fixed drive offsets - even after the DACkill - that allow us to make the OFF position equal to the locked position. This way the ISI never has to "move", we never have T240 saturations.

Comments related to this report
brian.lantz@LIGO.ORG - 10:22, Thursday 27 February 2014 (10376)
When the watchdog turns things off, they really need to be off. 
Last time a fiber was broken, it was because there was a bogus signal coming from the IOP process.

That said, We agree that it would be really good if turning the ISI on/off didn't mess with the alignment so much.

One clear action item is to trip the watchdog less often - all suggestions on this are welcome. 

Other Suggestions - 
1) Hold most offsets with HPI - we have in mind a way to hold HPI offsets longer during watchdog trips.

2) Stop going back to the target locations for most DOFs on the ISI. One can not see how recovering the old X, Y, Z, and roll DOF (e.g. if the beam direction is along X, the rX direction seems not-very-important at the micro-radian scale).

Clearly yaw is important for all optics, and pitch is important for tables with TMS. 

3) get the guardian for BSC-ISI up so we can turn on ISI whilst ignoring the T240s - in the mean time, this will be put into the BSCISItool scripts available in the next few days (testing is ongoing)



stefan.ballmer@LIGO.ORG - 14:35, Thursday 27 February 2014 (10386)
>When the watchdog turns things off, they really need to be off. 
>Last time a fiber was broken, it was because there was a bogus signal coming from the IOP process.

I don't understand. A constant value is just as "off" as the value 0. Not energy will be transferred to the payload.
H1 SUS
arnaud.pele@LIGO.ORG - posted 21:52, Wednesday 26 February 2014 - last comment - 10:43, Thursday 27 February 2014(10366)
ITMY TF running

ITMY TF will be running overnight on opsws8. Started at around 20:45

Comments related to this report
arnaud.pele@LIGO.ORG - 10:43, Thursday 27 February 2014 (10377)

Measurement completed and lasted ~10hours.

H1 SEI
jameson.rollins@LIGO.ORG - posted 18:36, Wednesday 26 February 2014 - last comment - 10:12, Thursday 27 February 2014(10364)
HAM2/3 ISI filter file updates in preparation for guardian deployment

In prepartation for tomorrows guardian deployment on ISI HAM2/3, I checked the configurations of the filter modules in the HAM2/3 ISIs, to make sure they are configured as needed for the guardian.  I found a couple of discrepencies that I've tried to sort out.

The BLEND configuration is not currently touched by the guardian code, so we're not working about their configuration for the moment.

The configuration of the DAMP filter modules seems to be as expected (FM1 loaded only with 'Damp').

The ISO modules were a different story.  ISI_HAMX expects the following filter banks to be populated for the vaious isolation levels:

HAM2/3 has nothing in FM3/5/6/7.  I therefore added unity gain filters into those banks, and gave them the appropriate names.

The Boost_* filters also didn't have the 5 second ramp times that we decided we needed during the HAM4 testing.  I added those ramps as well.

I have saved the filter files, but I have not yet loaded them into HAM2/3.  I will load them when I start my tests tomorrow morning.

Comments related to this report
brian.lantz@LIGO.ORG - 10:12, Thursday 27 February 2014 (10374)
There is a typo in the HIGH -
HIGH uses FM 4,5,6, possibly 7, and boosts with FM8
(using the 1-10 numbering)
H1 SEI
hugh.radkins@LIGO.ORG - posted 15:35, Wednesday 26 February 2014 - last comment - 08:41, Thursday 27 February 2014(10356)
WHAM4 ISI Tuned Mass Dampers Installed--Cables secured

Mitchell and I installed the TMDs on the HAM ISI Blade Springs similar to as Hugo and I did on WHAM3.  Mitchell has the serial numbers.  There were also a couple feedthrus that needed to have the in-vac cable attachment screws secured.  Mitchell did this.

Comments related to this report
mitchell.robinson@LIGO.ORG - 08:41, Thursday 27 February 2014 (10371)
Serial numbers for the Blade Spring Tuned Mass Dampers (D0900703) are 025, 026, 027.
H1 ISC (ISC)
evan.hall@LIGO.ORG - posted 09:56, Wednesday 26 February 2014 - last comment - 16:43, Friday 28 February 2014(10345)
Setting up PRC length measurement with auxiliary laser

[Ed, Evan]

We are preparing to make a measurement of the length of the PRC using the phase-locked auxiliary laser technique described by Chris Mueller (T1400047). Previously, this has been used to measure the Livingston IMC length (LLO alog 9599).

We set down a 520 mW Lightwave NPRO on the IOT2R table, along with a Faraday isolator and steering mirrors. We will inject this beam into the PRM_refl side of the IOT2R periscope. The beam will hit the back of IM4, and a small fraction (2400 ppm) will be transmitted toward the PRM. This gives 1.2 mW of auxiliary power on the PRM, compared to 9 mW of 45MHz PSL single-sideband power on the PRM.

Most of the auxiliary power should reflect from the back of IM4 and return to the IOT2R table via the IO_forward side of the periscope. For mode-matching, we hope that we can simply send part of the IO_forward beam onto a New Focus 1611 and maximize the observed beat. Currently, there is 3 mW of power in the IO_forward beam.

Using this beat, or otherwise, we will phase-lock the auxiliary laser to the PSL carrier beam. Then with PRMI locked on the PSL sideband, we will sweep the offset to the auxiliary PLL and monitor the RF coming out of POPAIR_B. We should see the strength of the RF reach a maximum whenever the auxiliary beam is coresonant with the the PSL sideband. By tracing out the Lorentzian profile of the RF amplitude across successive resonances of the PRC, we can extract the FSR of the PRC. Given a design length of 57.6557 m, we expect an FSR of 2 599 850 Hz. If we can measure the FSR to within 100 Hz, we can get the PRC length to within 2 mm.

Comments related to this report
evan.hall@LIGO.ORG - 15:47, Thursday 27 February 2014 (10388)

Yesterday we got the NanoScan back from EX and Ed used it to measure the beam parameter coming out of the Faraday isolator. The waist is about 100 µm and located more or less in the middle of the isolator. The size is maybe a bit smaller than we want, but we appear to be able to get more than 90% of the power through, with a reasonably Gaussian mode.

After the FI, we placed a HWP to set the beam to be s-polarized. After this, we placed a New Focus 5104 as a first steering mirror. As a second steering mirror, we use IO_PRMR_BS1.

We removed a lens from between IO_PRMR_M3 and IO_PRMR_BS1. It was unlabeled, and anyway there is nothing after that lens except beamsplitters and dumps.

We did an ALM optimization to mode match to the PRM. Joe Gleason's IOT2R layout (D0902284) gives the distance from the bottom of the IOT2R periscope to the PRM as 3.6 m. The spot size is 2.24 mm, with a ROC of 11 m (T0900407, p 5). ALM told us to put an f = 500 mm lens about 3 inches before IO_PRMR_M3 ("before" meaning "closer to the FI").

We put down two irises in order to constrain the pointing of the PRM_Refl beam. We then blocked this beam and steered the auxiliary beam through the irises. With a little tweaking, we were able to see our beam coming out on the IO_Forward part of the periscope. We measured the power of this beam and found that it was only about 5% of what we were putting in. This initially confused us, until we realized that our path in HAM2 has to go through a 90% reflector which is intended for the ISS. Given that IO_PRMR_BS1 is a 90% reflector and ROM LH1 (in HAM2) is also a 90% reflector, we in fact only expect 90% × 90% × 10% = 8% of the power to come back onto the IOT2R table.

evan.hall@LIGO.ORG - 16:43, Friday 28 February 2014 (10432)

Yesterday, we put down the New Focus 1811, aligned the PSL and auxiliary beams from IO_forward onto the PD. We found a beat with the auxiliary laser temperature around 37.7 °C. By tweaking the auxiliary input pointing, we were able to get -4 dBm of RF beat out of the 1811 with about 1 mW of DC power from each beam in front of the PD (so 2 mW total).

We were then able to implement a PLL using an HP function generator and the LB1005 servo box. We set the function generator to ~30 MHz and +7 dBm, and used it to drive the LO of a mixer. We took the beat and put it into the mixer RF. The IF was terminated, filtered at 1.9 MHz, and then fed into the LB1005. The output of the LB1005 was then fed into the fast input of the laser. We were able to catch lock by turning the laser's temperature control knob to push the beat toward 30 MHz. The lock would hold for about 1 minute before the controller saturated. To maintain sanity, I suspect it will be necessary to implement a slow temperature loop to relieve the fast controller.

Displaying reports 75481-75500 of 85564.Go to page Start 3771 3772 3773 3774 3775 3776 3777 3778 3779 End