patrick.thomas@LIGO.ORG - posted 05:17, Friday 24 March 2017 - last comment - 11:32, Friday 24 March 2017(35058)
Timing error
At 11:50:12 UTC verbal alarms reported: 'Timing system error'. I worked my way through the timing medm screens, trending each error channel to see which screen to go to next. In the end I found H1:SYS-TIMING_C_FO_A_PORT_2_SLAVE_ERROR_CODE went to 40 briefly. I'm not sure how to interpret this. Trends of the sequential error codes are attached.
Non-image files attached to this report
Comments related to this report
I just found that H1:SYS-TIMING_C_FO_A_PORT_2_SLAVE_UPLINKCRCERRCOUNT increased to 1 at the same time.
The error code is 40 (0x28) which decodes to 'Firmware error' + 'DUOTONE'. The port in question feeds the IO-Chassis for h1seib2 (Beam Splitter Seismic). I trended the IOP duotone and cpu signals over this time period, no problems were found. I spoke with Daniel and he agrees this looks like a random error (the timing around 4am local time is suspicious). I trended this system over the past 100 days, only this one occurence of a glitch. Hopefully not an early symptom of aging fiber transceivers.