travis.sadecki@LIGO.ORG - posted 21:23, Thursday 29 June 2017 - last comment - 21:49, Thursday 29 June 2017(37225)
ISS Third Loop Servo Gain channel connection error
Although it seems to have stopped on its own, and Keita had a look at the code and didn't see any issues, IMC_LOCK went into an error state and reported something like "Cannot connect to ISS_THIRD_LOOP_SERVO_GAIN". Maybe someone in CDS-land can have a look at this and tell me if it was user error or otherwise.
It happened again when we got to NLN. See screenshot.
guardlog --today IMC_LOCK |grep THIRDLOOP_SERVO_GAIN
2017-06-30_03:06:41.523790Z IMC_LOCK [POWER_UP_TR_CLOSED.main] ezca: H1:PSL-ISS_THIRDLOOP_SERVO_GAIN => 0
2017-06-30_03:06:41.890790Z IMC_LOCK [POWER_UP_TR_CLOSED.main] ezca: H1:PSL-ISS_THIRDLOOP_SERVO_GAIN => 0.5
2017-06-30_03:25:46.604890Z IMC_LOCK [POWER_UP_TR_CLOSED.main] ezca: H1:PSL-ISS_THIRDLOOP_SERVO_GAIN => 0
2017-06-30_03:25:46.994710Z IMC_LOCK [POWER_UP_TR_CLOSED.main] ezca: H1:PSL-ISS_THIRDLOOP_SERVO_GAIN => 0.5
2017-06-30_03:31:43.967770Z IMC_LOCK [ISS_DC_COUPLED.main] USERMSG 0: EZCA CONNECTION ERROR: Could not connect to channel (timeout=2s): H1:PSL_ISS_THIRDLOOP_SERVO_GAIN
2017-06-30_03:50:27.959750Z IMC_LOCK [ISS_DC_COUPLED.main] USERMSG 0: EZCA CONNECTION ERROR: Could not connect to channel (timeout=2s): H1:PSL_ISS_THIRDLOOP_SERVO_GAIN
2017-06-30_03:54:58.400950Z IMC_LOCK [ISS_DC_COUPLED.main] USERMSG 0: EZCA CONNECTION ERROR: Could not connect to channel (timeout=2s): H1:PSL_ISS_THIRDLOOP_SERVO_GAIN
2017-06-30_04:17:24.381530Z IMC_LOCK [POWER_UP_TR_CLOSED.main] ezca: H1:PSL-ISS_THIRDLOOP_SERVO_GAIN => 0
2017-06-30_04:17:24.765150Z IMC_LOCK [POWER_UP_TR_CLOSED.main] ezca: H1:PSL-ISS_THIRDLOOP_SERVO_GAIN => 0.5
2017-06-30_04:23:40.218410Z IMC_LOCK [ISS_DC_COUPLED.main] USERMSG 0: EZCA CONNECTION ERROR: Could not connect to channel (timeout=2s): H1:PSL_ISS_THIRDLOOP_SERVO_GAIN
Is this a network problem or what? I can read the number using caget almost immediately as of now, though.
This has happened the past 2 brief locks. During these locks, the DARM spectrum is ~ an order of magnitude above the reference traces from ~300Hz to several kHz. The max range reported during these locks was ~30MPc.
Called Dave at Keita's request. He noticed that the error reported contained an typo for the channel name (should be PSL-ISS rather than PSL_ISS). I found the typo in the guardian code, fixed it, and reloaded the IMC_LOCK guardian. Hopefully this fixes it. Thanks Dave!