Displaying reports 65241-65260 of 77210.Go to page Start 3259 3260 3261 3262 3263 3264 3265 3266 3267 End
Reports until 19:07, Wednesday 11 June 2014
H1 SEI
jeffrey.kissel@LIGO.ORG - posted 19:07, Wednesday 11 June 2014 (12325)
ISI ETMX Corner 1 T240 Grounding Jumper Restored
J. Kissel, R. Mittleman

While at the X-end investigating the HPI pump failure, WE remembered to put the jumper back. This is inside the Corner 1 T240 Interface chassis, S1201388 in U21. I attach a few pictures.

Pg 1 shows the internal board and the jumper in the upper left corner marked GND Shield. It's engaged in the picture.
Pg 2 shows the rack number
Pg 3 shows the serial number
Non-image files attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 18:39, Wednesday 11 June 2014 - last comment - 20:30, Wednesday 11 June 2014(12324)
power glitch at 18:08 PDT

We experienced a power glitch at Jun 12 2014 01:08:29 UTC (18:08PDT). The lights in the control room flickered for several seconds, the MSR UPS reported a switch to battery and back. Vacuum controls was not affected. Here is what I have found:

All models on h1lsc0 and h1asc0 stopped running

Both mid station PEM systems have DAQ timing errors

Right hand monitors for workstations opsws0,1,2 went blank

I'm going to restart the affected models. The workstations were power cycled.

Comments related to this report
david.barker@LIGO.ORG - 20:30, Wednesday 11 June 2014 (12326)

h1asc0 booted and came back with no problems.

I was unable to reboot h1lsc0 cleanly, I'll leave this until tomorrow, Jeff said it is not needed this evening.

both mid stations pem systems actually rebooted rather than freeze like asc/lsc. I tried restarting h1ioppemmy and could not clear the timing error. I'll leave both mid station pem systems for tomorrow.

H1 SEI
jeffrey.kissel@LIGO.ORG - posted 18:30, Wednesday 11 June 2014 (12322)
H1 HPI ETMX Pump Failure
R. Mittleman, J. Kissel

Rich found H1 ETMX HEPI unable to drive, and after a little bit of investigation, he found the "Pressure OK" indicator on the pump controller screen indicating badness. We drive to the end station and did the following:
- Confirmed that we heard the pumps not running.
- Found the "Heartbeat" LED blinking green, the "Level Alarm" LED solid red, and no light from the "Pressure OK" LED.
- Confirmed that the power supply was feeding the pump servo box +/-15 [V] (as indicated on the box itself)
- Confirmed with a DVM that power cable from the power supply at the pump servo box was outputing +/-15 [V]
- Disconnected and reconnected the power cable to the pump servo. No change, but all LEDs turned off.
- When into the pump controller box, which sounded as though it was whirring with power, and the digital readout said "OU3," which we presumed to mean "0.03"
- Rich hit the "RESET" button on the control panel, then hit "FWD," and the digital readout went to 0, but no action from the pump.
- Of the 4 The "OUT" spigots on the pump servo box, #1 was is sent to the pump controller, and all four spigots were sending out ~0.05 [V] which is ~0.
- With power on, the pump servo box's fan did spin up.
- Just to check, with everything re-powered on, we physically lowered the fluid level threshold a smidge, but this also failed to resurrect the pump.

We conclude that the pump servo box has let out its smoke in some unknown fashion. The serial number of the box is S1301037.

Once we got back to the control room, we found the pump controller screen white as well...

Pictures of the various things attached.
Pg 1 -- Fluid Level indicator. Looks like plenty of fluid.
Pg 2 -- Back of pump servo showing heartbeat, level alarm, pressure OK LEDs (off at this point)
Pg 3 -- Fluid level fluid lever threshold that was lower a smidge
Pg 4 -- display and buttons of control panel
Pg 5 -- front of pump servo box
Pg 6 -- Close up of serial number
Non-image files attached to this report
H1 SUS (CDS, ISC, SYS)
jeffrey.kissel@LIGO.ORG - posted 17:25, Wednesday 11 June 2014 (12320)
ETM ESD AI Chassis Boards at Rev 4
J. Kissel, F. Clara

Upon hearing news that LLO suspects their recent discovery of excess noise in their ESD signal chain (see LLO aLOG 13017 and 13034) is due to an older revision (V4) of AI chassis not being able to drive long signal chains (where the unique), Fil and I checked what documentation exists for ours. The serial numbers and version for our ESD AI chassis are as follows:

Optic   Chassis S/N       Board(s) S/N      Version 
ETMY    S1103819          S1101716            V4
                          S1101720            V4
ETMY    S1103818          S1101884            V4
                          S1101890            V4


So we'll need to swap these out for V6 at the earlier.
H1 ISC
filiberto.clara@LIGO.ORG - posted 16:24, Wednesday 11 June 2014 (12318)
AA AI Chassis Rework - CER ISC
Per bugzilla integration issue 463, looked at AA/AI chassis to verify units have the proper insulating film used to isolate the -15V regulators to the chassis metal wall. 

All ISC AA/AI chassis in the CER have been modified or verified to have the appropriate insulating film.

S1102793 S1102790 S1102782 S1102794 S1102770 S1102786 S1102766 S1102789 S1102759 S1102760 S1102788 S1102784 S1301308 S1102761

All electronics have been reconnected and powered up. All units were placed back in appropriate rack and slot location.

Filiberto / Aaron / Vanessa
H1 General
jeffrey.bartlett@LIGO.ORG - posted 15:50, Wednesday 11 June 2014 (12317)
Ops Summary
Day Shift Summary
LVEA Laser Safe 

08:30 Corey – Going to End-X Lab
08:50 Jodi – Working on 3IFO hardware near the H2 enclosure
09:00 Filiberto & Aaron – Working on AA/AI chassis repair in H1 electronics room
09:26 Robert & John – Checking high dust counts at HAM6
09:30 Ski and Mount Lock & Key  - Checking emergency egress doors at Mid-X
09:35 Keita – At HAM6 testing for ground loops
10:05 Karen – Going to End-Y
10:15 Rick, Peter, Olli, & Patrick – Working in H1-PSL enclosure
10:38 Jim – Going to End-Y to swap WD chassis
10:44 SUS crew – Working on ITM-Y swap at BSC1
11:04 Aaron – Going to End-Y to work on AA/AI chassis repair
11:24 Filiberto – Working in BSC3 on cabling problem
13:04 Mitch – In LVEA west bay looking for parts
13:12 Gerardo – Working CPB assembly
15:00 Safety meeting in LSB auditorium  
H1 ISC (ISC)
corey.gray@LIGO.ORG - posted 15:37, Wednesday 11 June 2014 - last comment - 17:42, Wednesday 11 June 2014(12316)
HAM6 Work: Eliminating Ground Loops & Re-Running Cables

Corey, Keita

We were able to get rid of a ground loop on the "solo" QPD by simply moving/touching it's Seismically Responsible Cable.

Moved to Tip Tilts and discovered that two of the three Tip Tilts had grounding loops to the table.  After much investigation, Keita appeared to discover the issue.  It's related to the BOSEMS and how the connector is close to the aluminum mounting plate which holds them.  He was able to do some "surgery" to move the connectors in a way such that they didn't short to this plate.  One Tip Tilt (OM3) was repaired, re-installed, and tested good.  OM2 still needs to be fixed.

There were three runs of cables (the two WFS cables which run to Flange D3 & the OM2 cable) which were run "under" Stage1.  According to Hugh, this is a no-no, so these cables re-run and routed around the perimeter of Stage0.

Believe Keita still had more ground loop issues on his list, and he also wanted to look at the capacitance of the OMC PZT.

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 17:42, Wednesday 11 June 2014 (12321)

In Corey's picture, one unit is fixed, the other is not. You cannot tell which is which if you don't know where to look.

There are two places where the metal connector shell potentially can touch the base plate of the coil, i.e. side and bottom (see the first attachment). There's always a continuity from the coil base plate to the TT BOSEM plate to the TT body to the ISI table, so this is not cool.

The side gap can be made as large as maybe 0.3-0.4mm, or as small as zero, by how you assemble it.

My "fix" was to maximize the side gap. The bottom gap looks incredibly small when this is done, probably 0.1mm or less, but this worked consistently for four coil/connector assemblies that I have re-done.

There is zero reason that these gaps should be this small, by the way. Probably it's too late, but if I redesign it I'll make it like the second attachment.

We'll continue tomorrow.

Images attached to this comment
H1 SUS
betsy.weaver@LIGO.ORG - posted 14:54, Wednesday 11 June 2014 - last comment - 08:51, Thursday 12 June 2014(12315)
ITMy deinstalled

Travis, Betsy, Gary, Margot, Apollo

After Apollo finished mounting the arm, elevator and 5-axis lift table on the BSC 1 flange first thing this morning, the ITMy was deinstalled from the chamber.

Comments related to this report
betsy.weaver@LIGO.ORG - 08:51, Thursday 12 June 2014 (12329)

I forgot to mention that we stuffed the ACB box into BSC 8 (via BSC1) in order to stow it out of the way for ITMy SUS work.

H1 General (DetChar)
jess.mciver@LIGO.ORG - posted 14:09, Wednesday 11 June 2014 (12314)
Useful Detchar Tools
The Channel Information System (CIS) is a searchable online database of all the aLIGO channels in the frames. 
 
From the main page, cis.ligo.org, you can browse channels by the Tree, or search for particular channels in the upper right. 
 
 
The ultimate goal is to input detailed descriptions for all channels in the science frames (this is an ongoing project with a deadline goal of the start of O1, so you may still find unfilled science channels). 
 
Here's a SEI channel example (motion of the HAM2 optic table in Y): https://cis.ligo.org/channel/48527

 
The CIS also stores core channel information, including sampling rate and units, pulled directly from the DAQ configuration files (channel units are incorrect since the DAQ doesn’t know about units - a feature request has been submitted for the RCG).
 
 
Here also is a reminder pointer to the Hanford summary pageshttps://ldas-jobs.ligo-wa.caltech.edu/~detchar/summary/
 

Check out the FAQ or ping any detector characterizer (some contacts listed in the FAQ doc) if you have any questions. 

 

 

 

 

H1 SUS
betsy.weaver@LIGO.ORG - posted 12:48, Wednesday 11 June 2014 (12313)
ITMx ESD connection broke then fixed

Recall from my alog yesterday, https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=12292 that we had a broken receptacle 5 on the ESD connector connected to the CP optic which we made a repair on.  Today, Filiberto and I tested each of the 5 ESD connections from the CP solder joints on the gold traces to the air side of the feed thru at the chamber flange.  After another minor fix to a pin, we can

1) confirm continuity from the optic connector to the air feed thru on all 5 ESD channels

and

2) confirm that the test method is quite painless considering it is at the optic (likely Filiberto had the harder job juggling meters up on a ladder in cramped quarters outside the chamber).

 

Details:

Yesterday we noticed receptacle 5 broken, and we were able to pull it through and pop it into place.  During that fix, we realigned some of the other pins that looked to be buckled or too tight a little.  I think we over-open receptacle 3, which then made it fail the continuity test today.  Closing receptacle 3 down and reseating the connector made all 5 continuity tests pass.  I touched one end of a piece of cleaned copper wire to each ESD solder joint on top of the optic while holding the other end to the metal structure.  Simultaneously, FIl looked at each of the 5 pins outside to find the one with continuity.

Here's the mapping, which conforms to Kissel's G1400578 report:

LR -> Pin 1

UR -> Pin 2

DC Bias -> Pin 3

UL -> Pin 4

LL -> Pin 5

 

ESD LL, UR, LL, UL Quadrants are specified as viewed from the back of the CP.

ESD pins are specified as viewed from the 5 pin feedthru connector on the outside of the chamber.

H1 CDS (SUS)
james.batch@LIGO.ORG - posted 12:30, Wednesday 11 June 2014 (12312)
Swapped Hardware Watchdog Chassis between EY and DTS
As a first level of troubleshooting communication problems with the hardware watchdog chassis at EY, I replaced the EY chassis with a known good chassis from the DTS.  I then tested the (former EY) chassis in the DTS, it works properly.

Presently, hardware watchdog chassis S1301709 (formerly from DTS) is installed at EY, while hardware watchdog chassis S1301712 (formerly from EY) is installed in the DTS.

Given that the S1301712 chassis communicates well in the DTS, I don't expect that this solved the problem at EY.
H1 General
jeffrey.bartlett@LIGO.ORG - posted 10:47, Wednesday 11 June 2014 (12310)
08:15 Meeting Minutes
Apollo – Move the installation arm from BSC3 to BSC1
Apollo – Remove the spool on the X-Arm for alignment
SUS crew – Getting ready to remove ITM-Y lower structure
Keita & Corey – Working in HAM6
Gerardo – CPB assembly work
EE – Repair work on AA and AI chassis 
 
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 08:21, Wednesday 11 June 2014 (12308)
CDS model and DAQ restart report, Tuesday 10th June 2014

model restarts logged for Tue 10/Jun/2014
2014_06_10 09:21 h1susbs
2014_06_10 11:09 h1fw0
2014_06_10 11:09 h1fw1
2014_06_10 11:09 h1nds0
2014_06_10 11:09 h1nds1
2014_06_10 11:12 h1broadcast0

2014_06_10 11:26 h1iopsusey
2014_06_10 11:35 h1iopseiey
2014_06_10 11:41 h1iopseiey
2014_06_10 11:58 h1isietmy
2014_06_10 11:59 h1hpietmy
2014_06_10 12:01 h1susetmy
2014_06_10 12:01 h1sustmsy

2014_06_10 12:39 h1broadcast0
2014_06_10 12:39 h1dc0
2014_06_10 12:39 h1fw0
2014_06_10 12:39 h1fw1
2014_06_10 12:39 h1nds0
2014_06_10 12:39 h1nds1

2014_06_10 12:57 h1iopsusey
2014_06_10 12:58 h1susetmy
2014_06_10 12:58 h1sustmsy
2014_06_10 13:01 h1iopseiey
2014_06_10 14:01 h1susetmy
2014_06_10 15:23 h1sustmsy
2014_06_10 16:20 h1hpietmy
2014_06_10 16:22 h1isietmy
2014_06_10 16:29 h1susetmy
2014_06_10 16:30 h1susetmy
2014_06_10 16:30 h1sustmsy

no unexpected restarts. SUS BS work green, SUS EY watchdog yellow, supporting DAQ restarts blue.

H1 ISC
keita.kawabe@LIGO.ORG - posted 21:52, Tuesday 10 June 2014 (12289)
Many HAM6 ISC ground loops detected

Baffled to find many ground loops, then I remembered that I was baffled by this same thing in all chambers.

Tested some (not all) of the HAM6 ISC cables for ground loop according to T1200131.

Each in-air cable was disconnected from the chassis while still connected to the chamber feed through (other in-air cables were still connected to both the chassis and feed through), and the continuity between the cable shell and the chassis ground was tested using DVM beeper (any continuity=bad).

  cable # good/bad
OMC DCPDs 307 bad.
OMC QPDs 404 bad
OM1/TT1 236 good
OM2/TT2 237 bad
OM3/TT3 238 bad
QPD sled 232 good
AS_C QPD 233 bad

FYI, for all of the above cables, there was a continuity between pin13 and shell (it's supposed to be like that).

WFS (both DC and RF), OMC PZTs, OMCS and SEI cables were not tested but I'll test at least WFS and OMC PZT.

Anyway, this is not acceptable for the chamber containing our main read out, and should be fixed in chamber.

H1 SEI (SEI)
richard.mittleman@LIGO.ORG - posted 21:38, Tuesday 10 June 2014 (12307)
ISI Trips

Many more trips today, many of which are dtt sessions ending, some come from ramping the blends from TBetter (40Mhz) to Start (750mHz, no t240) which seems to trip us every time

H1 SEI
richard.mittleman@LIGO.ORG - posted 21:36, Tuesday 10 June 2014 (12306)
Sensor Grounding Test

 

  There was some speculation that we might have a ground issue in the T240s, similar to what we had earlier with the GS13s.

To test this we lifted the shield to ground jumper in the corner #1 T240 electronics box on the ETMX-ISI. We then drove the system in the z direction (loops on, blends = start)

and looked at the individual T240 channels

 

  the first thing is that all of the Z channels look the same, so lifting the shield ground didn't effect anything here.

  the other thing is the horizontal sensors which have some coherence and a flat response which is kind of odd

 

  WE should remember to put the jumper back

 

  The second plot is the same set up except now I'm plotting the transfer functions to the modal T240 signals. We expect some cross coupling at the level of a 1-3% due to gain mismatch in the electronics, which

is kind of what you see in the vertical signals, the rX and rY are smaller then the Z by about the right factor and show the same slope. While the horizontal signals show something completely different, the 1/f^2 coupling that we have been working on

Images attached to this report
H1 SUS
betsy.weaver@LIGO.ORG - posted 16:17, Tuesday 10 June 2014 - last comment - 09:57, Wednesday 11 June 2014(12292)
H1 ITMx Monolithic installed - another ESD cable issue

This morning, we used the Genie "duct jack", the install arm, elevator, and 5-axis table to install the newly assembled ITMx Monolithic lower suspension into the chamber and mate it to it's upper structure.  All went as expected.  We then proceeded to start reconnecting wire segments and cabling.  When we mated up the lowest stage of the ESD cable, we had a small hiccup.  One of the 5 pin receptacles had fallen into the connector back shell on the end that is soldered directly to the CP.  With some care, we were able to gently fish it back out and push it into place with the wire which had been tugging on the other end of the pin receptacle.  We expanded the receptacle such that it seemed to hold itself in place better.  As well, all 5 receptacle "houses" were twisted such that they seemed to seat better in the connector.  We then connected this female connector to it's upper male cable counterpart and it "seemed" like it the connection seated properly.  We have no way of visually knowing though.  WE NEED TO CHECK THIS AT THE FEEDTHRU, OR SOMETHING.

Comments related to this report
betsy.weaver@LIGO.ORG - 16:26, Tuesday 10 June 2014 (12296)

Picture of connector with "slipped" receptacle (furthest left, shown missing in black hole):

Images attached to this comment
betsy.weaver@LIGO.ORG - 16:31, Tuesday 10 June 2014 (12297)
Forgot to mention, we also suspended the entire QUAD.
jeffrey.kissel@LIGO.ORG - 16:34, Tuesday 10 June 2014 (12298)CDS, SYS
Just trying to figure out what Betsy's talking about (before Betsy subsequently posted a picture herself), I showed Gary and Margot my picture from much earlier in the install (right after it came out of the storage container, basically, from the collection in LHO aLOG 12286). Gary said immediately "Look! You can see it's not there even that early in the day!" I attach the picture, with the missing pin circled.
Non-image files attached to this comment
rich.abbott@LIGO.ORG - 17:09, Tuesday 10 June 2014 (12300)
This is bad.  The center pin of each coaxial connector is supposed to be held fixed by a PEEK cylinder specifically designed for this purpose.  If the center pin fell through once, it is likely to do it again.  I would do two things before buttoning things up:

1.  Take the connector apart and see what's really going on.  There may (albeit unlikely) be a way to immobilize the center conductor by hook or by crook.
2.  After whatever mitigation you are able to do, I would suggest cleaning a bit of wire and literally shorting across adjacent terminals on top of the CP (if that's even physically possible) while someone outside the vacuum chamber verifies connectivity from the airside.

It may be (I just can't remember) that there's some hope that the center pin can be snapped into place with tweezers after disassembling the connector.  That would be really good if it were true.

betsy.weaver@LIGO.ORG - 09:57, Wednesday 11 June 2014 (12309)

Further detail of my first alog above:


When we discovered the problem in-chamber, we (Gary, Travis and I) already disassembled the connector very carefully, pulled the receptacle through, and attempted to "immobilize" it as Rich suggests in his alogged point 1.  We also attempted to "snap the pin into place" as he also suggested in the alog.  We plugged the 2 connectors together, so unplugging them now will likely break it again.  We need to move on to test 2. as per his alog (and as per Rich McCarthy in many verbal convos on testing all of them where we can).  We'll plan to do this today.

H1 CDS
cyrus.reed@LIGO.ORG - posted 14:58, Tuesday 10 June 2014 - last comment - 11:41, Wednesday 11 June 2014(12287)
Switch Firmware Upgrade Notes
Switch Firmware Upgrade Notes
 
These are the full details of today's switch upgrades.
 
The core switch (sw-msr-core) ROMMON was upgraded from 15.0(1r)SG7 to 15.0(1r)SG10.  This addresses an issue where the switch may drop into ROMMON if the boot process is interrupted by a powercycle if the config-register ends in 0x2.  (We use 0x2102, so it's worthwhile to upgrade).  The IOS was upgraded from XE 3.4.0SG to XE 3.4.3SG.  This includes some fixes for memory leaks, among many other things.
 
The various Cisco C2960-C switches were upgraded from IOS 15.0(2)SE2 to 15.0(2)SE6.  This includes removing support for creation of type 4 password hashes, which were demonstrated to be weaker than the type 5 password hashes they were meant to replace (Crypto is Hard(tm)).  These swtiches are: sw-gc-cdsadmin, sw-mech-aux, sw-psl-aux, sw-mx-aux, sw-my-aux.
 
All Cisco 3560-X switches were likewise upgraded from IOS 15.0(2)SE2 to 15.0(2)SE6, with same notes as above.  In addition there was an ASIC microcode update.  These switches are: sw-ex-aux, sw-ey-aux, sw-lvea-aux, sw-msr-gc, sw-msr-ops, sw-msr-server1, sw-msr-server2, sw-msr-video2.  sw-msr-gc and sw-msr-video2 show an amber SYST LED after reboot indicating some kind of POST failure.  I rebooted sw-msr-video2 and according to the console it passes all the POST tests though the LED remained amber.  These switches appear to be operating, so I will have to look into this more later.
 
The Netgear GSM72XXv2 FE network switches were upgraded from 8.0.1.27 to 8.1.0.36.  This addresses an issue with ssh management access hanging, requiring a reboot to fix, and high idle CPU usage.  These switches are: sw-ex-h1daq, sw-ex-h1fe, sw-ey-h1daq, sw-ey-h1fe, sw-msr-h1fe.  The odd one out, sw-msr-h1daq, is a different model switch and has not exhibited any issues worth fixing as yet.
 
The Fujitsu XG2600 switch that is used to broadcast data between the data concentrator and the rest of the DAQ (sw-msr-h1daqbc) was upgraded from V02.00 to V02.02.  The older version of firmware is no longer available for download, but there are no release notes for the new version to know for sure what changed.
Switch Firmware Upgrade Notes
 
These are the full details of today's switch upgrades.
 
The core switch (sw-msr-core) ROMMON was upgraded from 15.0(1r)SG7 to 15.0(1r)SG10.  This addresses an issue where the switch may drop into ROMMON if the boot process is interrupted by a powercycle if the config-register ends in 0x2.  (We use 0x2102, so it's worthwhile to upgrade).  The IOS was upgraded from XE 3.4.0SG to XE 3.4.3SG.  This includes some fixes for memory leaks, among many other things.
 
The various Cisco C2960-C switches were upgraded from IOS 15.0(2)SE2 to 15.0(2)SE6.  This includes removing support for creation of type 4 password hashes, which were demonstrated to be weaker than the type 5 password hashes they were meant to replace (Crypto is Hard(tm)).  These swtiches are: sw-gc-cdsadmin, sw-mech-aux, sw-psl-aux, sw-mx-aux, sw-my-aux.
 
All Cisco 3560-X switches were likewise upgraded from IOS 15.0(2)SE2 to 15.0(2)SE6, with same notes as above.  In addition there was an ASIC microcode update.  These switches are: sw-ex-aux, sw-ey-aux, sw-lvea-aux, sw-msr-gc, sw-msr-ops, sw-msr-server1, sw-msr-server2, sw-msr-video2.  sw-msr-gc and sw-msr-video2 show an amber SYST LED after reboot indicating some kind of POST failure.  I rebooted sw-msr-video2 and according to the console it passes all the POST tests though the LED remained amber.  These switches appear to be operating, so I will have to look into this more later.
 
The Netgear GSM72XXv2 FE network switches were upgraded from 8.0.1.27 to 8.1.0.36.  This addresses an issue with ssh management access hanging, requiring a reboot to fix, and high idle CPU usage.  These switches are: sw-ex-h1daq, sw-ex-h1fe, sw-ey-h1daq, sw-ey-h1fe, sw-msr-h1fe.  The odd one out, sw-msr-h1daq, is a different model switch and has not exhibited any issues worth fixing as yet.
 
The Fujitsu XG2600 switch that is used to broadcast data between the data concentrator and the rest of the DAQ (sw-msr-h1daqbc) was upgraded from V02.00 to V02.02.  The older version of firmware is no longer available for download, but there are no release notes for the new version to know for sure what changed.Switch Firmware Upgrade NoteThese are the full details of today's switch upgrades.
These are the full details of today's switch upgrades.
 
The core switch (sw-msr-core) ROMMON was upgraded from 15.0(1r)SG7 to 15.0(1r)SG10.  This addresses an issue where the switch may drop into ROMMON if the boot process is interrupted by a powercycle if the config-register ends in 0x2.  (We use 0x2102, so it's worthwhile to upgrade).  The IOS was upgraded from XE 3.4.0SG to XE 3.4.3SG.  This includes some fixes for memory leaks, among many other things.
 
The various Cisco C2960-C switches were upgraded from IOS 15.0(2)SE2 to 15.0(2)SE6.  This includes removing support for creation of type 4 password hashes, which were demonstrated to be weaker than the type 5 password hashes they were meant to replace (Crypto is Hard(tm)).  These swtiches are: sw-gc-cdsadmin, sw-mech-aux, sw-psl-aux, sw-mx-aux, sw-my-aux.
 
All Cisco 3560-X switches were likewise upgraded from IOS 15.0(2)SE2 to 15.0(2)SE6, with same notes as above.  In addition there was an ASIC microcode update.  These switches are: sw-ex-aux, sw-ey-aux, sw-lvea-aux, sw-msr-gc, sw-msr-ops, sw-msr-server1, sw-msr-server2, sw-msr-video2.  sw-msr-gc and sw-msr-video2 show an amber SYST LED after reboot indicating some kind of POST failure.  I rebooted sw-msr-video2 and according to the console it passes all the POST tests though the LED remained amber.  These switches appear to be operating, so I will have to look into this more later.
 
The Netgear GSM72XXv2 FE network switches were upgraded from 8.0.1.27 to 8.1.0.36.  This addresses an issue with ssh management access hanging, requiring a reboot to fix, and high idle CPU usage.  These switches are: sw-ex-h1daq, sw-ex-h1fe, sw-ey-h1daq, sw-ey-h1fe, sw-msr-h1fe.  The odd one out, sw-msr-h1daq, is a different model switch and has not exhibited any issues worth fixing as yet.
 
The Fujitsu XG2600 switch that is used to broadcast data between the data concentrator and the rest of the DAQ (sw-msr-h1daqbc) was upgraded from V02.00 to V02.02.  The older version of firmware is no longer available for download, but there are no release notes for the new version to know for sure what changed.
 
Comments related to this report
cyrus.reed@LIGO.ORG - 11:41, Wednesday 11 June 2014 (12311)

The source of the mystery SYST amber LED on sw-msr-gc and sw-msr-video2 are bad power supply fans; one each per switch, both in PS1.  The fans appear to operate, and come back OK for a while if the supply is reinserted, so they are probably just running out of spec in some fashion.  I'll either swap out the supplies, or see if just the fans can be replaced, as time allows.

H1 SUS
arnaud.pele@LIGO.ORG - posted 14:13, Friday 06 June 2014 - last comment - 17:14, Wednesday 11 June 2014(12228)
X1 QUAD08 TF

[Mark B Jeff B Arnaud P]

Yesterday we did some software debugging in the staging building in order to run transfer functions on the assembled quad 08.
When driving the top mass, we usually monitor the lower stages osems, in both osem and euler basis. For some reason the model running for the quad doesn't record those channels (particularly the ones in the euler basis "WIT_{L/P/Y}_DQ"). We decided not to spend too much time understanding what the model situation was, and instead simply not monitor the lower stages channels during the top mass TFs.

The undamped transfer function measurements for the main and the reaction chain are attached.
 

Non-image files attached to this report
Comments related to this report
arnaud.pele@LIGO.ORG - 13:12, Tuesday 10 June 2014 (12255)

[Mark Jeff Arnaud]

QUAD08 should be compared to the model called "wireloop"  (=wires from UIM to PUM looping around PUM) instead of the "wire" one (=cable segments between UIM and PUM). The first attachment from the alog above was modified since I was using the wrong model for comparison. With the wireloop model there is still a small discrepancy in the second pitch mode (modeled at 1.33Hz and measured at 1.45Hz). By playing with the d values (defined p7 of T080188) I came up with a good match, cf attachment.

Here are the modified d values for reference :
new_dm = old_dm + 0.7mm
new_dn = old_dn + 0.7 mm
new_d4 = old_d4 - 0.8 mm

Also, after an other round of matlab debugging (pb with channel sampling rates in the matlab scripts, path definitions etc...) we were able to get spectra of TOP and UIM osems, with the suspension undamped. Results are attached in the second pdf.
The only thing to notice is the noise content at high frequencies for the left osem of M0 (cyan curve, 1st page). This might be harmonics from the large 60Hz signal.

Non-image files attached to this comment
arnaud.pele@LIGO.ORG - 18:31, Tuesday 10 June 2014 (12305)

Jeff B Andres Arnaud

This afternoon we tested the noise seen in the left bosem of the main chain. We swapped left and right osem cables (at the osem output), and measured a spectra before and after. When plugging the right channel to the left osem, the noise was still present in the spectra (cf screenshot) meaning the noise comes from the left osem itself.

Second attachment is a comparison of the transfer functions between different "wireloop" quads. The 2nd pitch mode frequency is varying from quad to quad, but the largest discrepancy is on QUAD08.

Images attached to this comment
Non-image files attached to this comment
arnaud.pele@LIGO.ORG - 17:14, Wednesday 11 June 2014 (12319)

[Andres Arnaud]

Today we replaced the left osem of the main chain of QUAD08 in the staging building with an other BOSEM (stolen from one of the 3rd IFO TMS). New OLV were stored, offsets and gains were set in medm.
 Results of individual osems spectra are attached. The M0 LF channel dosen't show the elevated noise seen yesterday anymore

Non-image files attached to this comment
Displaying reports 65241-65260 of 77210.Go to page Start 3259 3260 3261 3262 3263 3264 3265 3266 3267 End