Charge measurements was done on both ETMs. It seems like ETMY change the sign of charging after changing the bias sign on ETMY (see 20387) while ETMX charging is the same (as well as the bias sign). Now (since Aug,10) both ETMX and ETMY Biases are -9.5V, Plots are in attachment.
w/conversations and email from Duncan,
Svn Up'd: userapps/release/sys/common/models/ODC_MASTER_PARTS_V2.mdl
Svn Added: userapps/release/sys/common/src/RIP_OBS_READY_FROM_MASTER.c
Modified: userapps/release/sys/h1/models/h1odcmaster.mdl from DCC E1500352 tarball.
recompiled, installed, started.
This presented two new channels: H1:ODC-AUTO_UNSET_OBS_INTENT & H1:ODC-OBS_READY_BIT_NUMBER
These were set to be monitored in SDF and set their values to 1 & 2 respectively. This means 1==> yes automatically unset the observation intent bit based on the value of bit number 2 in ODC MASTER.
The modified safe.snap has been commited to the svn.
I have updated and reloaded the guardian IFO top node such that it no longer unsets the 'ODC-OPERATOR_OBSERVATION_READY' (aka INTENT) bit after dropping from OK. This logic is now handled in the ODC MASTER.
Please see LLO alog 19981 for information about how this affects operations. Probably the most salient aspect of the change:
The INTENT (ODC-OPERATOR_OBSERVATION_READY) bit will not be allowed to be set by the operator unless the READY bit is True.
The READY bit is composed of two parts:
If the INTENT bit can not be set, look at the state of both of these things to determine if there is an issue.
I also just removed the unsetting of ODC-OPERATOR_OBSERVATION_READY from ISC_LOCK (it shouldn't have been there in the first place). ISC_LOCK was reloaded, so this change should have taken affect.
Elli, Nutsinee
The clamp turned out to be a little big so the sensor couldn't be firmly held to the mount but it is in place and won't go anywhere. The configuration is the same as how we installed it at the CO2Y.
Terminated bnc cables for the PEM-CS_RADIO_LVEA antenna. Cables are along west wall of HAM2. Installed an 18 Bit DAC AI Chassis D1101785 in OAF-C1 rack, slot U22&U21. SN S1201691 Installed an Quad I&Q RF Demodulator D0902796 in OAF-C1 rack, slot U27. SN S1000981 Pulled 2 LMR cables from the OAF-C1 rack to ISC-C4 rack for the demodulator LO signals of 9MHz and 45MHz. The LO signals are connected to the follwing RF Distribution Amplifier units in ISC-C4: 9MHz U26 Port 4 45MHz U19 Port 4
Replaced breaker on UIM chassis (S0900303) from a 1A to 3A. Nominal current draw with no load is ~0.5 amps. Will monitor to see if this resolves issue.
All times local PDT.
0728 IFO Dropped Lock
0755 Richard Starts on PRM -- Finished 1044 -- No obvious problem but Chassis changed.
0759 Hugh Installs STS2-A at HAM2 -- Finished 0825
0822 Keita to EndX for QPD checks-- Finished 1043--No obvious problem.
0833 Phil to EndX for UIM -- Upgraded breaker from 1 to 3Amps. Done 0935
0835 Hugh updates ODC MASTER for Auto Intent_Bit Reset ECR E1500352
0855 Ellie to TCS HWS Camera Power Supply, removes filter to EE Shop. No good, revert to no-filter configuration. Done 1033
0912 Nutsinee to TCSX for Temperature Sensor install--Finished 1158.
0930 Barker completes LSC/ASC/OAF/PEMEX Model updates for SciFrame changes & others (see Kawabi=LSC)
1031 Kiwamu doing ALS Diff Electronic Measurements. Done 1245
1000 SysDiag Guardian node down for rebuild finished 1723
1100 Leo starts ETM Charge Measurements. Complete 1239.
1105 Model Restarts--H1OAF fails from Epics problem. Halt model restarts.
1115 JimB fixes Epics problem. Model Restarts resume.
1124 DAQ Restart
1130 Daniel & Sheila at AS WFS Electronic response & dark noise Done 1240.
~1100 Phil Terminating PEM Cables in LVEA and CER. Installing 18bit DAC card. Done 1244.
Following up on Evan's investigation into the glitches from LL coil on the PRM M3. I tried to monitor the output with a scope attached. I was not looking for very big signals as the the noisemon indicated roughly 30mV signal and it has some gain associated with it. So I connected to scope probes to the LL coil drive signal and looked at it on a scope with a trigger set fairly low.(10s of milivolts). I also looked at UL just for comparison. I was able to get the signal to trigger on some events on LL that were not seen at as high a level on UL. This was with the DAC both connected and disconnected with small offset (20 counts) applied and a large offset (20,000 counts) applied. After a couple of hours of investigation I decided there were some glitches present and seemed to be from the coil driver not the DAC. I also looked at the DAC input to the coil driver and did not see the glitches. In the end I swapped out the coil driver. I am not 100% certain this will fix the problem as it was difficult to verify the glitches were present at all times.
Unit removed S1100045. Unit installed S1100025.
WP5452: New LSC and ASC models were made and built yesterday, and were installed today. ASC update also include one bug fix for ASC ODC (change one data type from cdsepicsout to cdsepicslong).
As for LSC, as per E1500343, 45MHz AM monitor channels was added to the science frame at 16kHz.
As for ASC, as per E1500348, input side of ASC feedback filters were added to ASC at 256Hz, and as per E1500349, ALS-C_TRX_A_LF_OUT_DQ and ALS-C_TRY_A_LF_OUT_DQ (both 2k) were removed.
After the installation, in chans/daq directory, LSC and ASC science frame channels were checked.
$ grep -B 1 "^acquire=3" H1LSC.ini|grep DQ
[H1:IMC-F_OUT_DQ]
[H1:IMC-I_OUT_DQ]
[H1:IMC-L_OUT_DQ]
[H1:IMC-REFL_DC_OUT_DQ]
[H1:IMC-TRANS_OUT_DQ]
[H1:LSC-ASAIR_B_RF90_I_ERR_DQ]
[H1:LSC-MCL_IN1_DQ]
[H1:LSC-MCL_OUT_DQ]
[H1:LSC-MICH_IN1_DQ]
[H1:LSC-MICH_OUT_DQ]
[H1:LSC-MOD_RF45_AM_AC_OUT_DQ]
[H1:LSC-ODC_CHANNEL_OUT_DQ]
[H1:LSC-POPAIR_B_RF18_I_ERR_DQ]
[H1:LSC-POPAIR_B_RF90_I_ERR_DQ]
[H1:LSC-POP_A_LF_OUT_DQ]
[H1:LSC-POP_A_RF45_I_ERR_DQ]
[H1:LSC-POP_A_RF45_Q_ERR_DQ]
[H1:LSC-POP_A_RF9_I_ERR_DQ]
[H1:LSC-POP_A_RF9_Q_ERR_DQ]
[H1:LSC-PRCL_IN1_DQ]
[H1:LSC-PRCL_OUT_DQ]
[H1:LSC-REFL_A_LF_OUT_DQ]
[H1:LSC-REFL_A_RF45_I_ERR_DQ]
[H1:LSC-REFL_A_RF45_Q_ERR_DQ]
[H1:LSC-REFL_A_RF9_I_ERR_DQ]
[H1:LSC-REFL_A_RF9_Q_ERR_DQ]
[H1:LSC-REFL_SERVO_ERR_OUT_DQ]
[H1:LSC-REFL_SERVO_SLOW_OUT_DQ]
[H1:LSC-SRCL_IN1_DQ]
[H1:LSC-SRCL_OUT_DQ]
$ grep -B 1 "^acquire=3" H1ASC.ini|grep DQ
[H1:ASC-AS_A_DC_PIT_OUT_DQ]
[H1:ASC-AS_A_DC_SUM_OUT_DQ]
[H1:ASC-AS_A_DC_YAW_OUT_DQ]
[H1:ASC-AS_A_RF36_I_PIT_OUT_DQ]
[H1:ASC-AS_A_RF36_I_YAW_OUT_DQ]
[H1:ASC-AS_A_RF36_Q_PIT_OUT_DQ]
[H1:ASC-AS_A_RF36_Q_YAW_OUT_DQ]
[H1:ASC-AS_A_RF45_I_PIT_OUT_DQ]
[H1:ASC-AS_A_RF45_I_YAW_OUT_DQ]
[H1:ASC-AS_A_RF45_Q_PIT_OUT_DQ]
[H1:ASC-AS_A_RF45_Q_YAW_OUT_DQ]
[H1:ASC-AS_B_DC_PIT_OUT_DQ]
[H1:ASC-AS_B_DC_SUM_OUT_DQ]
[H1:ASC-AS_B_DC_YAW_OUT_DQ]
[H1:ASC-AS_B_RF36_I_PIT_OUT_DQ]
[H1:ASC-AS_B_RF36_I_YAW_OUT_DQ]
[H1:ASC-AS_B_RF36_Q_PIT_OUT_DQ]
[H1:ASC-AS_B_RF36_Q_YAW_OUT_DQ]
[H1:ASC-AS_B_RF45_I_PIT_OUT_DQ]
[H1:ASC-AS_B_RF45_I_YAW_OUT_DQ]
[H1:ASC-AS_B_RF45_Q_PIT_OUT_DQ]
[H1:ASC-AS_B_RF45_Q_YAW_OUT_DQ]
[H1:ASC-AS_C_PIT_OUT_DQ]
[H1:ASC-AS_C_SUM_OUT_DQ]
[H1:ASC-AS_C_YAW_OUT_DQ]
[H1:ASC-CHARD_P_IN1_DQ]
[H1:ASC-CHARD_P_OUT_DQ]
[H1:ASC-CHARD_Y_IN1_DQ]
[H1:ASC-CHARD_Y_OUT_DQ]
[H1:ASC-CSOFT_P_IN1_DQ]
[H1:ASC-CSOFT_P_OUT_DQ]
[H1:ASC-CSOFT_Y_IN1_DQ]
[H1:ASC-CSOFT_Y_OUT_DQ]
[H1:ASC-DC1_P_IN1_DQ]
[H1:ASC-DC1_P_OUT_DQ]
[H1:ASC-DC1_Y_IN1_DQ]
[H1:ASC-DC1_Y_OUT_DQ]
[H1:ASC-DC2_P_IN1_DQ]
[H1:ASC-DC2_P_OUT_DQ]
[H1:ASC-DC2_Y_IN1_DQ]
[H1:ASC-DC2_Y_OUT_DQ]
[H1:ASC-DC3_P_IN1_DQ]
[H1:ASC-DC3_P_OUT_DQ]
[H1:ASC-DC3_Y_IN1_DQ]
[H1:ASC-DC3_Y_OUT_DQ]
[H1:ASC-DC4_P_IN1_DQ]
[H1:ASC-DC4_P_OUT_DQ]
[H1:ASC-DC4_Y_IN1_DQ]
[H1:ASC-DC4_Y_OUT_DQ]
[H1:ASC-DC5_P_IN1_DQ]
[H1:ASC-DC5_P_OUT_DQ]
[H1:ASC-DC5_Y_IN1_DQ]
[H1:ASC-DC5_Y_OUT_DQ]
[H1:ASC-DHARD_P_IN1_DQ]
[H1:ASC-DHARD_P_OUT_DQ]
[H1:ASC-DHARD_Y_IN1_DQ]
[H1:ASC-DHARD_Y_OUT_DQ]
[H1:ASC-DSOFT_P_IN1_DQ]
[H1:ASC-DSOFT_P_OUT_DQ]
[H1:ASC-DSOFT_Y_IN1_DQ]
[H1:ASC-DSOFT_Y_OUT_DQ]
[H1:ASC-INP1_P_IN1_DQ]
[H1:ASC-INP1_P_OUT_DQ]
[H1:ASC-INP1_Y_IN1_DQ]
[H1:ASC-INP1_Y_OUT_DQ]
[H1:ASC-INP2_P_IN1_DQ]
[H1:ASC-INP2_P_OUT_DQ]
[H1:ASC-INP2_Y_IN1_DQ]
[H1:ASC-INP2_Y_OUT_DQ]
[H1:ASC-MICH_P_IN1_DQ]
[H1:ASC-MICH_P_OUT_DQ]
[H1:ASC-MICH_Y_IN1_DQ]
[H1:ASC-MICH_Y_OUT_DQ]
[H1:ASC-ODC_CHANNEL_OUT_DQ]
[H1:ASC-OMC_A_PIT_OUT_DQ]
[H1:ASC-OMC_A_SUM_OUT_DQ]
[H1:ASC-OMC_A_YAW_OUT_DQ]
[H1:ASC-OMC_B_PIT_OUT_DQ]
[H1:ASC-OMC_B_SUM_OUT_DQ]
[H1:ASC-OMC_B_YAW_OUT_DQ]
[H1:ASC-POP_A_PIT_OUT_DQ]
[H1:ASC-POP_A_SUM_OUT_DQ]
[H1:ASC-POP_A_YAW_OUT_DQ]
[H1:ASC-POP_B_PIT_OUT_DQ]
[H1:ASC-POP_B_SUM_OUT_DQ]
[H1:ASC-POP_B_YAW_OUT_DQ]
[H1:ASC-POP_X_RF_I_PIT_OUT_DQ]
[H1:ASC-POP_X_RF_I_YAW_OUT_DQ]
[H1:ASC-POP_X_RF_Q_PIT_OUT_DQ]
[H1:ASC-POP_X_RF_Q_YAW_OUT_DQ]
[H1:ASC-PRC1_P_IN1_DQ]
[H1:ASC-PRC1_P_OUT_DQ]
[H1:ASC-PRC1_Y_IN1_DQ]
[H1:ASC-PRC1_Y_OUT_DQ]
[H1:ASC-PRC2_P_IN1_DQ]
[H1:ASC-PRC2_P_OUT_DQ]
[H1:ASC-PRC2_Y_IN1_DQ]
[H1:ASC-PRC2_Y_OUT_DQ]
[H1:ASC-REFL_A_DC_PIT_OUT_DQ]
[H1:ASC-REFL_A_DC_SUM_OUT_DQ]
[H1:ASC-REFL_A_DC_YAW_OUT_DQ]
[H1:ASC-REFL_A_RF45_I_PIT_OUT_DQ]
[H1:ASC-REFL_A_RF45_I_YAW_OUT_DQ]
[H1:ASC-REFL_A_RF45_Q_PIT_OUT_DQ]
[H1:ASC-REFL_A_RF45_Q_YAW_OUT_DQ]
[H1:ASC-REFL_A_RF9_I_PIT_OUT_DQ]
[H1:ASC-REFL_A_RF9_I_YAW_OUT_DQ]
[H1:ASC-REFL_A_RF9_Q_PIT_OUT_DQ]
[H1:ASC-REFL_A_RF9_Q_YAW_OUT_DQ]
[H1:ASC-REFL_B_DC_PIT_OUT_DQ]
[H1:ASC-REFL_B_DC_SUM_OUT_DQ]
[H1:ASC-REFL_B_DC_YAW_OUT_DQ]
[H1:ASC-REFL_B_RF45_I_PIT_OUT_DQ]
[H1:ASC-REFL_B_RF45_I_YAW_OUT_DQ]
[H1:ASC-REFL_B_RF45_Q_PIT_OUT_DQ]
[H1:ASC-REFL_B_RF45_Q_YAW_OUT_DQ]
[H1:ASC-REFL_B_RF9_I_PIT_OUT_DQ]
[H1:ASC-REFL_B_RF9_I_YAW_OUT_DQ]
[H1:ASC-REFL_B_RF9_Q_PIT_OUT_DQ]
[H1:ASC-REFL_B_RF9_Q_YAW_OUT_DQ]
[H1:ASC-SRC1_P_IN1_DQ]
[H1:ASC-SRC1_P_OUT_DQ]
[H1:ASC-SRC1_Y_IN1_DQ]
[H1:ASC-SRC1_Y_OUT_DQ]
[H1:ASC-SRC2_P_IN1_DQ]
[H1:ASC-SRC2_P_OUT_DQ]
[H1:ASC-SRC2_Y_IN1_DQ]
[H1:ASC-SRC2_Y_OUT_DQ]
Filiberto, Elli
The ITM HWS weren't working properly after installing the filter box last week (alog 20626). Power goes from the HWS breakout box through the filter module to the HWS cameras. The voltage drop across the filter put the voltage at the cameras below their operating range. (There is 14V at breakout box output, 10.8V after the filter. Operating voltage of the camera is 12-15V. 13.3V reaches camera with no filter installed.) We have taken the filter out and reverted to the previous HWS configuration. We will rethink the choice of filter.
The new SYS_DIAG infrastructure for the Guardian diagnostic nodes has been installed. The new infrastructure allows for multiple diagnostic nodes with different names.
The old SYS_DIAG node was re-written to use the new infrastructure, and was renamed as DIAG_MAIN:
$USERAPPS/sys/h1/guardian/DIAG_MAIN.py
The old SYS_DIAG node was destroyed, and DIAG_MAIN was created and started. DIAG_MAIN is now running and appears to be executing all tests normally.
A DAQ restart is required to pull in the new DIAG_MAIN channels.
The main infrastructure for SYS_DIAG is encoded in the SYS_DIAG module:
$USERAPPS/sys/common/guardian/SYS_DIAG.py
DO NOT MODIFY THE SYS_DIAG MODULE. This module defines common infrastructure for loading and running the tests.
To create a new diagnostic node, define a new module: $USERAPPS/sys//guardian/DIAG_. This module should import everything from SYS_DIAG, and define all diagnostic tests as follows:
from SYS_DIAG import *
@SYSDIAG.register
def TEST_SOMETHING()
"""One-line description of test.
Other info about test.
"""
if some_condition():
yield "message to be reported to operator"
Note the "@SYSDIAG.register" decorator above the TEST_SOMETHING function. That's what registers the function as a diagnostic test that gets run in the RUN_TESTS state (see below). The module can define as many functions as you like, but only those registered will be run as diagnostic tests.
Also note that the function "yields" a diagnostic message. Each test can define as many conditions as you like, and for each failing condition, yield a diagnostic message as show above. The yielded message will be displayed as a NOTIFICATION by the DIAG guardian node, tagged with the test from whence it came.
The DIAG module only needs to define tests as described above, and should not define any GuardState classes. The states are imported from SYS_DIAG: INIT that just lists the registered tests, and RUN_TESTS which runs all tests tagged with the @SYSDIAG.register decorator.
Tests can be defined in separate modules and imported as needed in the usual way.
(Keita writing) Nothing changed for green, it's hard to tell if anything happened for IR as there's no light right now. Analog signal coming out of the interface looked OK in that no high frequency oscillation was observed in green as well as IR. Ditto for Analog signal coming out of whitening. I didn't pull the QPD interface chassis out, as one of the clean room legs is blocking the front side of the ISC field rack and I couldn't move the clean room on my own.
Here is a quick script to get the svn numbers of the TwinCAT PLCs:
#!/bin/csh
ezcaread ${1}:SYS-ETHERCAT_C1PLC1_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_C1PLC2_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_C1PLC3_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_X1PLC1_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_X1PLC2_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_X1PLC3_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_Y1PLC1_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_Y1PLC2_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_Y1PLC3_SVNREVISION
and here are the results:
H1:SYS-ETHERCAT_C1PLC1_SVNREVISION = 2406
H1:SYS-ETHERCAT_C1PLC2_SVNREVISION = 2402
H1:SYS-ETHERCAT_C1PLC3_SVNREVISION = 2402
H1:SYS-ETHERCAT_X1PLC1_SVNREVISION = 2357
H1:SYS-ETHERCAT_X1PLC2_SVNREVISION = 2357
H1:SYS-ETHERCAT_X1PLC3_SVNREVISION = 2357
H1:SYS-ETHERCAT_Y1PLC1_SVNREVISION = 2357
H1:SYS-ETHERCAT_Y1PLC2_SVNREVISION = 2325
H1:SYS-ETHERCAT_Y1PLC3_SVNREVISION = 2325
These are the most recent versions for the respective PLCs.
At 0728 pdt the IFO dropped lock.
Prior to that the SDF was green except for the OMC, SUSETMY, and SUSPRM. Some CALC stuff too but I'll not worry about that.
The PRM diffs are from the LL Coil driver changes and the OMC & SUSETMY diffs are captured below. These system should not have to be restarted today.
As of 0905,
The STS2-A is installed.
Richard has been and continues to work on the PRM coils.
Keita is working the EndX QPD.
Phil is working the ETMX UIM Breaker and
Ellie is working on the TCS HWS Camera Power Supply.
ALL TIMES IN UTC
Summary:
H1 remained locked for ~6+ hours. LLO went down at 12:39UTC according to Doug Lormand’s aLog. There was ~4hrs coincidental lock with LLO. Wind and Seismic still calm. ETMY glitches at 10:12, 10:24, 11:12, 11:55, 13:19, 13:35, 14:27. Handing off to Jeff B.
LOCK LOG:
8:49 Locked @ NOMINAL_LOW_NOISE
9:03 ADD_WHITENING to OMC 66 Mpc
clearing some SDF diffs for data taking while LLO is up
Evan doing some light commissioning work before data collecting mode
9:37 OIB and OOM switched to Undisturbed/Observing
14:27 Lockloss- Possibly PRAXXAIR delivery
Sequence started again but maintenance will eventually take it down at 15:00UTC
A plot of lockloss at 14:27:29 UTC is attached.
ASC-POP glitched ~16s before and ASC-PRC2 starts to oscillating at about the same time ( and the oscillation became really huge about ~ 6s before lockloss). They were both high frequency (>128 Hz).
Besides, the ground motion did not seemed to be related to this lockloss as indicated by the second plot.
ALL TIMES IN UTC
Upon Arrival: IFO not locked. Calibration going on. Wind calm. Seismic calm
Summary:
Wind and seismic remain calm. IFO has been locked and in Undisturbed/Observing Mode since 9:37UTC @ ~66Mpc. A few ETMY glitches, nothing major. Everything looks good so far.
7:00 Kissel, Kiwamu, Evan on site doing their thing(s)
10:13 ETMY Saturation. Dropped range to 4Mpc
10:24 ETMY Saturation. Dropped range to 48Mpc
11:12 ETMY Saturation. Dropped range to 48Mpc
J. Kissel, P. Thomas Given that we've had so many examples of rocker switch death this evening (see LHO aLOG 20839), I was able to identify that my new(ish) warning message about this failure mode on the MEDM overview screen (see LHO aLOG 20281) had a bug. The MEDM logic was watching L2 for all three stages, L2, L1, and M0. I've committed the bug-fix to the SVN such that LLO can receive its benefits.
What is the MEDM Overview Screen? Is this the overall QUAD Overview? If so, where is the new(ish) warning message? Are you talking about the Guardian message window (upper right corner) on the QUAD overview?
On the top-level screen for each quad, you should see a red rectangle appear around the top, UIM, or PUM coil output filters that says "rocker switch death", as in this screenshot from Jeff's alog.
J. Kissel, S. Dwyer, E. Hall As I was about to characterizing the ETMY coil drivers (i.e. the UIM and PUM), I noticed that they were in their highest noise state. After conversations with Sheila and Evan, we (re)agreed that the PUMs should be run in their lowest noise state, which is with LP ON and ACQ OFF, or State 3 from T1100507. As such, we've switched all QUADs to this state, and confirmed that ISC_LOCK guardian will ensure this to be true in the future (again). That guardian has been reloaded. The reason they had been put back into high range (and taken out of the guardian) was that the range was needed to better damp the QUAD roll modes after they had been severely rung up in the Christmas Episode in early August. From a calibration stand point, this will affect the DARM calibration by a small amount, but I had not started characterizing the ETMY PUM drivers before I got started, and I'm now full aware of it, so it's affect will be fully understood and expected. As such, we're OK with this configuration change. Further, we'll all be happy with the little bit extra range we get from it (Evan will post an aLOG making a noise statement later)!
We can hear saturations on the quads during CARM offset reduction and when powering up, but I suppose that's the price we pay for the improved noise performance. [See attachment—blue is from yesterday (coils in high-range), red is from today (coils low range). I can't really claim that the improvements at 70+ Hz are from the coil switching, though.]
We would like to acquire with high range and then switch to low noise at some point during the lock, but the transients unlock the interferometer most of the time. Jeff suggests that we commission the digital switching delays. Perhaps that can be done parasitically with calibration activities.