Displaying reports 47441-47460 of 87653.Go to page Start 2369 2370 2371 2372 2373 2374 2375 2376 2377 End
Reports until 17:50, Tuesday 10 April 2018
H1 TCS (TCS)
daniel.vander-hyde@LIGO.ORG - posted 17:50, Tuesday 10 April 2018 (41370)
TCS verbal alarm change
Cheryl, TVO, Daniel 


The TCSX and TCSY CO2 laser verbal alarms were triggered even though they were off because the controller box was powered down causing the flowmeter readback to reach negative values. Both controller boxes were turned on and the flowrate reached nominal values but verbal alarms still persisted. To silence verbal alarms we raised the alarm condition of the CO2 laser powerhead PD from 5 watts to 10 watts. This cut out most of the alarms but the attached figure shows that the laser powerhead PD channels still glitch above the threshold. 
Images attached to this report
H1 SEI
hugh.radkins@LIGO.ORG - posted 16:40, Tuesday 10 April 2018 - last comment - 15:44, Thursday 19 April 2018(41368)
Attempt to Update ISI code for smooth Isolation loop ramp down from Watchdog Trip.
ISI code change to ramp DAC drive down when watchdog trips and not instantaneously
go to zero volts. Dave composed this and I added in red text.

Hugh and Dave. 10 April 2018
WP7462 to implement ECR E1800026 addressing II 9889 with details explained by Stocks & Lantz in T1800031.

Summary: we attempted to test the new ISO_RAMP code, but were unable to
reach that point due to filter modules outputting very large signals.
We abandoned the test and restored the code and hardware back to its original
configuration.

----------------------------------------------------------------------------

Hugh elected to test the new code on h1isietmy.

Using the latest isi/common/models/isi2stagemaster.mdl (r17117)
which uses the new isi/common/models/cushion_DOF.mdl (r17116)
and the associated C code isi/common/src/RAMP_ISO_OFF.c (r17084)
we compiled and installed h1isietmy.

Following a C code review by Jonathan, it was expected that the model
would have problems if the ramp time is zero of a divide-by-zero nature.
Our first test was to execute the if-conditional block
which would run the divide-by-zero lines.

While Hugh was manually causing watch dog trips, he noticed that the ISI DAC channels 
were negatively railing to -10.0 Volts. 
This was tracked to ST1 and ST2 OUTF filters having a railed output of 1.0e+20
with a zero input. These filter modules have two filters installed: Comp and Sym.
We found that the Sym filter (a simple gain stage) was causing the output to shoot
to rail on WD trip. It was not obvious to us why this was happening.
The rail could be removed by clearing the FM history, and could be prevented by
turning off the Sym filter. Are you sure? Hugh's not sure if we ever prevented it...

After further setup work Hugh discovered that ST[1,2] RZ T240SUBTRACT_Z filter modules
were also railing at 1.0e+20.

Due to the violent motion being caused by the ISI DAC outputs instantaneously
driving to -10.0V each time the watchdog was tripped, we needed to stop the DAC
output from driving the DAC cards. Our first attempt was to SWWD trip the output
of the h1iopseiey model. However, the ISI code and/or guardian monitors this and
this prevented our test from proceeding. Could not get the guardian to run with IOP(software WD) tripped. We eventually had to go to EY and power
off the anti-imaging (AI) chassis for the ISI DAC. We could then green up all the software
watchdogs and still be sure that no sudden motion was being driven to the seismic stack.

Hugh spent a further hour trying to get the isolation ramp code to be executed,
but was being thwarted by the misbehaving filter modules. Same drive to 1e+20 counts & -10Vs.

We decided to abandon the tests as maintenance time was running out, and to 
revert the code back to what it was.

I reverted the svn version of isi/common/models/isi2stagemaster.mdl from 
r17117(05apr2018) to r16398(31oct2017), and isi/common/models/isihammaster.mdl
from r17118(05apr2018) to r16422(06nov2017).  Thank you Dave!

I rebuilt h1isietmy and we were happy to see the DAQ INI file return to its original
content. We verified the checksum of the INI file was as it was originally.
When the model was restarted, the DAQ-ini-mismatch error was cleared, so no
DAQ restart was needed.

Hugh then damped ISI-ETMY with no re-occurance of the 1.0e+20 FM outputs.  Finally, using the ISI Guardian (no SEI Manager) the stages isolated stabily.

As far as the code problem--Don't have it to look at now since Dave reverted but I suspect some  X Y Z etc DOF wires got crossed.  Don't know if that addresses the railing FMs but it would not help.

 
Comments related to this report
brian.lantz@LIGO.ORG - 17:28, Tuesday 17 April 2018 (41499)CDS

I'm trying to reproduce the issue on our test-stand but I can not.

First test shows the behavior is what I expect - I set the filter module for stage 1, X, to just be a constant (100), gain =1,  and turn the filter modules off so that the output of the filter is 100.

Then I trip the watchdog and compare the signal at the filter output to the signal at the output of the ramp stage. I do this 2 times, first with a ramp time of 0, and once with a ramp time of 0.1 sec. In the two attached plots one can see that the red filter module output drops immediately to 0, while the ramp output (blue triangles) either drops immediately to 0 or ramps to 0 in 0.1 seconds. I do not see a big glitch. I wonder what the heck is going on - will follow up with Hugh ASAP.

-Brian

 

Images attached to this comment
hugh.radkins@LIGO.ORG - 08:53, Wednesday 18 April 2018 (41515)

Hey Brian,

We never even got to try the smooth ramp as we could not get the system isolated.  We did not think to try a fake isolation state as I think you are indicating.

dane.stocks@LIGO.ORG - 15:44, Thursday 19 April 2018 (41551)
Hi Hugh,

I did a quick test just now. In the isi2stagemaster model, I went through both stage 1 and stage 2 paths to ensure that there were no "crossed-wires." That is, I went through each dof in the isolation bank and ensured that an input signal appeared as it should in the final output of each stage (a 1 count offset in ST1 X appeared as solely a 1 count output in ST1_OUTF H1, etc). (note - we set the cart2act matrix to be the identity matrix for our convenience in this test - so X goes to H1, etc) For the stage 1 path I ensured this also held true for the ST1_ST2_DRIVE_COMP. This indeed held true in the updated model, the one with the changes Brian and I made. Thus we think that the problem lies elsewhere, possibly in the way that the model was started on the H1 machines; it is my understanding that IOP model was not restarted after grabbing the updated model from the svn. However, if you have any further suggestions for us to investigate, please send them our way.
H1 General
cheryl.vorvick@LIGO.ORG - posted 16:03, Tuesday 10 April 2018 (41369)
Maintenance Day Summary:

Summary by building:

Detailed Activity List:

H1 SUS
betsy.weaver@LIGO.ORG - posted 15:57, Tuesday 10 April 2018 - last comment - 08:21, Thursday 12 April 2018(41366)
ETMX Fibers broken during installation

Today, Travis, Mark and I worked on installing the ETMX lower structure into the chamber.  After it was in, while reassembling cables, we noticed that the test mass was really jammed into it's lower stops - upon further inspection, we discovered that both fibers on the left side (viewed from back of the suspension) were gone.  We started looking for the debris and found it just outside of the chamber on the floor and on the trolley that the unit had been sitting in overnight last night and this morning.  We did not find anything like a bug nearby, but investigation ongoing.  Meanwhile, we're revising the schedule to back up a few steps and start the rebuild.  History of lower structure after it was welded:

- Welded main chain unit sat on it's trolly in weld room for ~a week before we were ready to install it.

- Yesterday, we rolled the covered main chain on it's trolly ~60ft from weld room cleanroom to the staging cleanroom.  We then uncovered it, and lifted it with the genie duct jack and placed it on the reaction chain trolley and mated the 2 units together.  The fibers were intact at this point.  We then covered it again and rolled the whole unit ~10ft from the staging cleanroom to the chamber cleanroom and parked it near the door.  We left the cover on it and the genie duct jack parked around it with the forks loose around the structure to aid in protection.

- This morning we uncovered the unit, and then lifted the unit off of the trolley with the genie lift and set it up on the install arm elevator.  We then continued with the installation of the unit into the chamber with the arm.  A few hours later we discovered the broken fibers.

All of the above is standard install procedure, with the same equipment (trolly, cover, genie lift, install arm) used in each of the previous QUAD installations.

Since we found the fiber debris all over the trolley and on the ground outside of the chamber on the floor, it must have happened between yesterday late afternoon when we rolled it there and this mornign after we picked it up and set it into the install arm.

 

Comments related to this report
betsy.weaver@LIGO.ORG - 08:13, Thursday 12 April 2018 (41401)

We believe that the fibers broke in the morning during the lift out of the LSAT with the genie duct jack lift since we recall specifically NOT seeing debris under the trolley before that.  There is a fair amount of jostling that happens to the suspension during this, as the suspension needs to pull free from 8 supporting legs (with 8 nut bars and 8 screws) which are a tight fit around the structure, just above the upper fiber joint.  The masses were locked into position, however the test mass was locked with most of the load still on the fibers.  Since the lower EQ stops are viton tipped, they must have compressed more during the maneuver (or added up over the course of the previous maneuvers) and the load on the fibers became more than 100%.  We will go back to utilizing the rail stops under the mass D060446, a tooling piece abandoned early on due to interferences and difficulty to use (the tooling for the stops we adapted instead has proved sufficient numerous times since, but it only takes one failure).

betsy.weaver@LIGO.ORG - 08:21, Thursday 12 April 2018 (41402)

Attached are pictures of the ear and horns on the PUM and Test Mass.  The PUM horns appear to be very short now, so we will take the opportunity to replace the PUM, especially since this is the one with the crack behind the prism which may not survive around of fiber welding.

I'm prepping PUM-ITM03 in the bonding lab.  Yesterday the magnet/flag inserts and 1 prism were glued into place.  Today the second prism, followed by an overnight low temp out-gassing air-bake.

Images attached to this comment
H1 SEI (CDS)
filiberto.clara@LIGO.ORG - posted 14:53, Tuesday 10 April 2018 - last comment - 09:41, Wednesday 11 April 2018(41363)
ITMX CPS Satellite Box

WP 7464

Removed CPS satellite box for inspection of pcb DB25 connector, alog 41265. Pads on pcb board are not being stressed. Only thing to note is the connector on the pcb board is not sitting flush to the board. Unit was reinstalled.

F. Clara

Comments related to this report
hugh.radkins@LIGO.ORG - 09:41, Wednesday 11 April 2018 (41377)

And the platform isolated with no issues.

H1 CDS (CDS, PEM)
patrick.thomas@LIGO.ORG - posted 13:57, Tuesday 10 April 2018 (41362)
Weather station in MSR moved to Beckhoff, TCS chiller code updated
WP 7465

Daniel, Dave, Filiberto, Patrick, Richard

I stopped the EPICS IOC that was running on h0epics and moved the DB9 serial cable from the Comtrol to Port 1 of the serial concentrator. This port connects to channel 1 of the Corner MSR L12_13 EL6002. I added the code for the readout of the weather station to PLC1 on h1ecatc1. No channel names were changed. Channels have been added to report errors. These should be added to the medm screens. The code will automatically reconnect if communication is interrupted, for example if the weather station is powercycled. The alarm levels for the wind speed have been put in the database, so a burtrestore is no longer required to set these either.

I also took the opportunity to update the TCS chiller code. It seems to be working without issue.
LHO VE
kyle.ryan@LIGO.ORG - posted 13:16, Tuesday 10 April 2018 (41361)
FTIR sample taken of IP11 GV gate
Kyle R., Chris S. 

Today Chris S. and I took an FTIR sample from the closed gate of the 12.8" GV that isolates IP11 (VAT s/n 0002, see also https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=41353).  Additionally, we opened a new 12.8" GV (in clean room, VAT s/n 0005) and took a comparable swab from the same side of its closed gate.  In both cases, the swiped area was ~20% of the exposed gate surface area.  
H1 CDS
david.barker@LIGO.ORG - posted 12:51, Tuesday 10 April 2018 (41360)
h1iopsusey model restarted to clear DAC issue

Around 1am Thursday 5th April PDT h1iopsusey stopped driving the DACs due to a glitch. I restarted all the models on h1susey to clear this.

H1 PEM (PSL)
cheryl.vorvick@LIGO.ORG - posted 12:41, Tuesday 10 April 2018 (41359)
EX dust2 is stuck in Holding

Does not go to Sampling when "On" is clicked.

LHO VE
chandra.romel@LIGO.ORG - posted 12:02, Tuesday 10 April 2018 - last comment - 15:32, Tuesday 10 April 2018(41358)
Vertex turbo spun up

Spun up vertex turbo right before lunch at ~0.6 Torr. Still need to close purge/vent isolation valves (OMC and IMC) and IP3 GV and little right angle valve.

Comments related to this report
chandra.romel@LIGO.ORG - 15:32, Tuesday 10 April 2018 (41365)

Kyle closed the IMC & OMC purge valves and I closed the right angle metal valve on top of IP3 GV. Leak checker is connected to vertex turbo cart, valved out, and warming up for leak checking tomorrow or whenever He bottle is freed up from EY.

H1 DCS (CDS, DCS)
gregory.mendell@LIGO.ORG - posted 11:23, Tuesday 10 April 2018 (41357)
Patch and reboot the DMT production computers
The DMT production computers in the MSR, h1dmt0, h1dmt1, and h1dmt2, have been patched and rebooted. WP 7466 is done.
H1 SEI
hugh.radkins@LIGO.ORG - posted 08:37, Tuesday 10 April 2018 - last comment - 15:47, Tuesday 10 April 2018(41356)
Some extreme values on the ETMY CPS sensors--suspect timing

At ~2256utc on 3 April (or precisely 1206831398gps), all the CPS sensor readouts on both stages jumped to a different value. Eight of the twelve spiked to a 33kish number before going somewhere else.  A few on Stage2 are not crazy numbers but still shifted.  Most on Stage1 are extreme ~positive 8k.  See attached

Another item to be investigated is the Coil Driver Thermal trip hit at 1557utc on the fifth...

Images attached to this report
Comments related to this report
hugh.radkins@LIGO.ORG - 15:47, Tuesday 10 April 2018 (41367)

Wasted a bit of time by power cycling the CPS power and the sensors interface chassis.  Found the CPS Timing Sync fanout chassis power supply unplugged.  Guess it got swept up in the VE group's house cleaning that was found to be necessary.  While the senors don't read exactly what they did before, they are at least much more reasonable.  And, the platform will isolate.

H1 TCS (TCS)
cheryl.vorvick@LIGO.ORG - posted 08:19, Tuesday 10 April 2018 - last comment - 08:36, Tuesday 10 April 2018(41354)
TCS is in an unknown state

I confirmed with Patrick yesterday that the RS232 flow rate for both chillers shows that the chillers are on, and the flow rates are around 3gpm.

The flow rates on the medm are negative, both around -2.5gmp.

Greg's most recent alog 41314 from April 5th says the chiller is running in a small closed loop, and it appears that this is for both TCSX and TCSY chillers.

Images attached to this report
Comments related to this report
cheryl.vorvick@LIGO.ORG - 08:36, Tuesday 10 April 2018 (41355)TCS

Patrick went to look, and all 3 TCS chillers are running and all read around 3gpm flow.

LHO VE
kyle.ryan@LIGO.ORG - posted 21:05, Monday 09 April 2018 (41353)
IP11 leak found
Kyle, Gerardo, Chandra 

Today we pumped IP11 using a local turbo backed by an aux. cart.  IP11 is isolated from the Y-end via its closed GV.  As I squirted IPA around each CFF joint and vacuum welds of the Chevron Baffle nipple, Gerardo M. monitored the pressure gauge on the aux. cart to see if there was a response.  Chandra R. had already established this to be a very large leak (0.1 torr*L/sec).  We tried "listening" for the audio leak using a device intended for that purpose -> Something seems to be originating from the Chevron Baffle but difficult to eliminate background noise in the room -> We shut down the Clean Room (1417 hrs. local) and that helped a little.  Next, we modified the as-found bag such that each CFF joint was exposed but keeping the nipple's tube vacuum welds within the bagged volume.  We then purged the bag with bottled N2 while spraying helium around each CFF joint -> no significant response.  Finally, we reversed the bagging, now purging the CFF joint(s) while spraying helium around the welds of the nipple tube -> found very large leak coming from the bottom tube-to-flange vacuum weld (nipple s/n 01).  

Having found one leaking Chevron Baffle, Chandra R. examined a different one stored in the VPW.  She found suspicious looking welds.  

Also, we prepared IP11+chevron baffle nipple for tomorrow's removal by venting it with bottled UHP N2 and removing all but (3) ea. of the nipple-to-GV nuts and studs.  Note that with the local turbo spun down and disconnected from the aux. cart, I applied the N2 to the Tee at the inlet of the turbo letting it flow trough the turbo and into the room via the open-ended turbo exhaust line.  This setup would prevent the possibility of over-pressurizing IP11 as it remained open to the room.  I then opened the 1 1/2" vent/pump valve to vent IP11.  Gerardo M. noticed that room air was then entering through the exhaust.  Thus, for a short period, I had been back streaming through the local turbo and into IP11.  I then closed the 1 1/2" valve and removed the turbo. This is a "dirty" pump in that it is not a maglev.  I'll consult Chandra R. as to what, if any action is needed (FTIR?).   
LHO VE
chandra.romel@LIGO.ORG - posted 18:27, Monday 09 April 2018 (41352)
valved out vertex mechanical pump for the night

Isolated QDP80 at vertex with pressure at 1.3 Torr. Will resume tomorrow morning.

LHO VE
david.barker@LIGO.ORG - posted 16:41, Monday 09 April 2018 (41351)
increase TE202A thermocouple high alarm level

Chandra has requested that the high alarm level for H0:VAC-MY_CP3_TE202A_DISCHARGE_TEMP_DEGC be raised from 130.0 degC to 140.0 degC (this signal is currently operating at 131.1 degC). This was done and the alarm system was restarted.

H1 SUS
betsy.weaver@LIGO.ORG - posted 15:35, Monday 09 April 2018 - last comment - 15:22, Tuesday 10 April 2018(41346)
WBSC9 ETMX QUAD halves back together

Today, Travis and I finished assembling the ETMX lower reaction chain.  We assembled the PenRe mass in the structure, attaching the balance of parts to make the weight from last week including AOSEMs, cables, and cable routing brackets.  We then installed the new annular AERM07 mass below the PenRe in the lower structure and adjusted it in it's 6 DOF's by eye before suspending it.  We then reclamped everything and rolled the main lower chain up to it.  A quick lift via the Genie duct jack and we set the main lower structure and newly fiber'ed masses into the trolley with the reaction set.  We added the UIM and PUM magnets/flags (set with polarities per the QUAD controls poster), and then shoved the 2 structures together and fastened them.

We wrapped the now complete lower unit and rolled it to the chamber side.  After attaching some of the LSAT lifting blocks, we staged the Genie duct jack so that we are ready to install it on the arm and into the chamber tomorrow.

Comments related to this report
betsy.weaver@LIGO.ORG - 15:39, Monday 09 April 2018 (41347)

Note - Travis noticed a door bolt sitting in the BSC9 flange in the unused hole at 3 o'clock.  The washer from the bolt (which held nothinglooked to be rubbing funny on the o-ring so he removed it.  The vacuum crew will need to inspect this after we remove the install arm.  (Note, the install arm and stiffening flanges cover most of the right side of holes and o-ring on this chamber, except for a ~6" gap at 3 o'clock.  There are o-ring covers everywhere else.  This bolt should not have been in this hole, since it served no purpose.)

betsy.weaver@LIGO.ORG - 15:22, Tuesday 10 April 2018 (41364)

From Chandra and Kyle who inspected this o-ring portion yesterday late afternoon:

Kyle and I inspected the o-ring and deemed it ok to reuse. Kyle peeled away a
sliver of viton material that was hanging off of the o-ring. To the naked eye
the surface looks ok. We will take note of this when we install the door and
pump down the annulus volume.
Displaying reports 47441-47460 of 87653.Go to page Start 2369 2370 2371 2372 2373 2374 2375 2376 2377 End