patrick.thomas@LIGO.ORG - posted 15:35, Saturday 12 August 2017 - last comment - 17:01, Saturday 12 August 2017(38157)
Lockloss, ETMX tripped
Lost lock at 21:49 UTC. Verbal alarms reports 'ETMX RMS WD has tripped'. DIAG_MAIN reports: SUS_RMS_WD: ETMX RMS ['UL', 'LL', 'UR', 'LR'] WD has tripped SUS_WD: SUS ETMX M0 osem filter input inmon is dead OPLEV_SUMS: ETMX sum is low It seems that the hardware watchdog may also have tripped, at least according to the MEDM screen. H1:SUS-ETMX_HWWD_STAT_OUT has jumped to 15. I have not been able to reset the PUM COIL SLOW CUR WD using the WD RESET button. The wiki says a trip to the end station may be needed. I have not yet found the procedure for what to do at the end station. Screenshots attached.
Images attached to this report
Comments related to this report
Plots of H1:SUS-ETMX_L2_RMSIMON_LL_MON, H1:SUS-ETMX_L2_RMSIMON_LR_MON, H1:SUS-ETMX_L2_RMSIMON_UL_MON, H1:SUS-ETMX_L2_RMSIMON_UR_MON for last three hours.
Non-image files attached to this comment
22:53 UTC ISI ETMX stage 1 and stage 2 watchdogs just tripped.
Looking at some trends: the HWWD status went from 0 to 15 very quickly, indicating an electrical issue rather than physical since the watchdog should take 40 minutes to trip.
The IOP software watchdog OSEM RMS signal peaked to 50 and then dropped to an unusually low value, indicating it may not be functional now.
All events happened at 21:48 UTC, 14:48 PDT.
The IOP model for SUS-EX is showing a keep-alive error on all five 18bit-DACs, indicating a possible AI error. It appears the IO Chassis is still OK otherwise IOP model would have failed.
Attached is the IOP GDS-TP MEDM, and a trend of the hwwd status and the swwd osem input
Images attached to this comment
