Displaying reports 57541-57560 of 89315.Go to page Start 2874 2875 2876 2877 2878 2879 2880 2881 2882 End
Reports until 11:41, Saturday 17 December 2016
H1 CDS (TCS)
david.barker@LIGO.ORG - posted 11:41, Saturday 17 December 2016 - last comment - 14:34, Saturday 17 December 2016(32673)
h1ecatc1 reporting hardware errors

Alastair asked me to check if the corner station Beckhoff slow-controls system was running correctly. The system is reporting an error on the C1DEVICE0 error flag channel. I've attached the current medm screen shot.

The error started at 08:43 PST this morning, at the same time as the h1psl0 IO-Chassis glitched. I suspect a hardware error at the Beckhoff chassis, which in turn possibly glitched the PSL IO-Chassis via a shared 24VDC power supply.

 

caget H1:SYS-ETHERCAT_C1DEVICE0_ERROR_FLAG

H1:SYS-ETHERCAT_C1DEVICE0_ERROR_FLAG Error

Images attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 11:46, Saturday 17 December 2016 (32674)

Please post the device0 medm, and check the number of configured vs. actual slave modules. If the later is smaller, the following module is in error or broken.

edmond.merilh@LIGO.ORG - 11:50, Saturday 17 December 2016 (32675)

I spoke to Filiberto on the telephone. He's heading in to the site to have a look.

david.barker@LIGO.ORG - 12:53, Saturday 17 December 2016 (32677)

attached is the ecatc1 device0 medm, it show actual_slave_count = 290, config_slave_count = 345 which Daniel says indicates hardware error.

Images attached to this comment
filiberto.clara@LIGO.ORG - 14:34, Saturday 17 December 2016 (32684)

The Beckhoff slow controls chassis for PSL/TCS was found tripped off. Found the D13001631 Rotation Stage board for TCS Y was current limiting. Removed D6, D3, D7, and D4. Both TCS X and Y boards now have same configuration. Unit was reinstalled. PSL IO chassis will most likely need to be restarted. Past experience shows that power cycling the beckhoff chassis will cause errors with IO chassis.

H1 General (PSL)
edmond.merilh@LIGO.ORG - posted 10:20, Saturday 17 December 2016 - last comment - 10:24, Saturday 17 December 2016(32668)
PSL is back up

Ed, Jason

The LASER is back up. I'm waiting on a timing error in the FE computer to clear.

Comments related to this report
david.barker@LIGO.ORG - 10:23, Saturday 17 December 2016 (32669)

h1ioppsl0 IRIG-B timing has recovered. I've cleared the IPC errors and accumulated CRC counters.

edmond.merilh@LIGO.ORG - 10:24, Saturday 17 December 2016 (32670)CDS, PSL, TCS

Timing error cleared @ 18:23UTC. Going to the LVEA to check on the statues of the TCS LASERs.

H1 CDS (PSL)
edmond.merilh@LIGO.ORG - posted 09:11, Saturday 17 December 2016 - last comment - 10:13, Saturday 17 December 2016(32660)
All PSL FEs are crashed

Seems like this is the bogger issue at the moment. I noticed this after the Verbal Alarm about the TCS issue. The LASERs are still showing power. I have no QUAD FOM view. THe attached screenshot shows the current CDS FE status.

Images attached to this report
Comments related to this report
keith.thorne@LIGO.ORG - 09:45, Saturday 17 December 2016 (32663)CDS
Actually all the front-end models are on a single computer.  Either the power for the I/O chassis has tripped, or the communications was dropped for a few cycles. If you reboot the PSL front-end computer (h1psl0), that would fix the latter.  If that fails, you need to power down the PSL front-end computer, then power-cycle the I/O chassis (resetting DC power supply if needed), then booting the PSL front-end computer.
   If that fails, then we need more investigation.
edmond.merilh@LIGO.ORG - 09:46, Saturday 17 December 2016 (32664)

I have Jim Batch on the phone to troubleshoot

james.batch@LIGO.ORG - 10:05, Saturday 17 December 2016 (32665)
The IOP chassis was not visible from the computer, so I remotely removed the h1psl0 computer from the dolphin network and powered down the computer.  Ed power cycled the I/O chassis and powered the computer back on.  The cards in the I/O chassis are now visible.  Timing on the h1ioppsl0 model has gone "negative", meaning the DAQ data is bad until it works it's way back positive. But the PSL computer show be able to control the PSL OK.  

There is no known cause for this event.
david.barker@LIGO.ORG - 10:13, Saturday 17 December 2016 (32666)

trending h1ioppsl0's state_word shows that at 08:44 PST the FE and ADC bits faulted. It looks like a timing issue which glitched the IOP into a non-recoverable state.

IRIG-B is still in a slow recovery, DAQ data will be invalid until it completes.

H1 TCS
edmond.merilh@LIGO.ORG - posted 08:52, Saturday 17 December 2016 - last comment - 11:37, Saturday 17 December 2016(32659)
TCSX and TCSY tripped off

at 16:44UTC both TCS lasers tripped off. The Ops overview screen shows that the Flow alarm status is green. It seems to be only the Laser Power that's off. I'm currently scouring the Wiki to see what I need to do to get these back up.

Comments related to this report
alastair.heptonstall@LIGO.ORG - 09:30, Saturday 17 December 2016 (32662)

Just spoke to Ed and Jonathan.  The flow rate now looks green.  It's possible that this has been triggered by other computers going down.  I can't get remote read-only MEDM access to check the status of the system.  Ed will call me if they can't key the lasers back on at the controller.

alastair.heptonstall@LIGO.ORG - 11:37, Saturday 17 December 2016 (32672)

Ed and Dave got my remote access turned on so I could log in and take a look.  It appears both TCS lasers are in a good state but are not outputing power.  Power supply voltage is good.  Flow rate is good.  Temperature is good.  Current is around 0.7A indicating that they are getting RF and are ready to laze.  The Beckhoff screen shows red indicators on several read back channels, and it looks like this may be the cause of the lasers not coming on.

I've spoken to Dave and Ed again and they are going to take it from here since it looks like a Beckhoff issue. I'll be available by phone if needed.  The laser chassis will probably need to be re-keyed off and on once this has been fixed.

H1 General
edmond.merilh@LIGO.ORG - posted 08:18, Saturday 17 December 2016 - last comment - 10:20, Saturday 17 December 2016(32658)
Shift Summary - Day Transition
TITLE: 12/17 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Aligning
OUTGOING OPERATOR: Travis
CURRENT ENVIRONMENT:
    Wind: 1mph Gusts, 0mph 5min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.54 μm/s 
QUICK SUMMARY:
Travis left me Initial alignment. Bubba ison his way to investigat an Instrument Air alarm.
Comments related to this report
edmond.merilh@LIGO.ORG - 09:09, Saturday 17 December 2016 (32661)

16:22 Also noticed that tw0 is "white". Not certain at this time how long it has been that way

david.barker@LIGO.ORG - 10:20, Saturday 17 December 2016 (32667)

h1tw0 is currently down while we are rebuilding its raid.

H1 General
travis.sadecki@LIGO.ORG - posted 08:03, Saturday 17 December 2016 (32656)
Ops Owl Shift Summary

TITLE: 12/17 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Aligning
INCOMING OPERATOR: Ed
SHIFT SUMMARY:  Microseism is up and EQ is finally ringing down.  Having difficulty locking arms green, possibly due to a combination of ground motion factors.  Last 5 hours of shift were waiting for EQ to ring down to reasonable levels.
LOG:

See previous aLogs for details.

15:53 Starting IA.

H1 PEM (PEM)
travis.sadecki@LIGO.ORG - posted 06:05, Saturday 17 December 2016 - last comment - 11:37, Saturday 17 December 2016(32653)
Temps at EX, EY, MX, MY nonsensical

It's pretty cold on site this morning, but is it possible that the temperature sensors are past their limits?  See screenshot.

Images attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 11:37, Saturday 17 December 2016 (32671)

Actually this looks more like a conversion error between signed and unsigned words for the Fahrenheit readbacks. If you subtract 2^16/10 from these numbers, it makes sense! Filed FRS 6963.

H1 General (VE)
travis.sadecki@LIGO.ORG - posted 05:22, Saturday 17 December 2016 - last comment - 06:42, Saturday 17 December 2016(32651)
H0:VAC-EY_INSTAIR_PT499_PRESS_PSIG alarm

H0:VAC-EY_INSTAIR_PT499_PRESS_PSIG went into alarm.  See attached screenshot of the trend for the past 2 hours.  I'll continue to monitor this and make some calls to VAC folks if it persists.

Images attached to this report
Comments related to this report
travis.sadecki@LIGO.ORG - 06:42, Saturday 17 December 2016 (32654)

Updated plot for the past 2 hours.  Continuing to "trend" downward.  Looks a little suspicious how the trend smoothed out around 37.

travis.sadecki@LIGO.ORG - 06:42, Saturday 17 December 2016 (32655)

Images attached to this comment
Displaying reports 57541-57560 of 89315.Go to page Start 2874 2875 2876 2877 2878 2879 2880 2881 2882 End