On Tuesday 11th October we installed the ITMX and ETMX hardware watchdog chassis (HWWD) in monitor mode, which completes the install of the four HWWD chassis.
Previously we had found that the ITMY HWWD reported LED-current-monitor undervoltages which were not been seen on ETMY. In the past 24 hours we have now seen similar events on ITMX, which suggests the longer cabling to the ITM systems may be a factor.
For the past 20 hours, I plotted the ITMX HWWD LED-current-monitor status against an OSEM coil drive signal (I chose top stage F1 as a representative example). There is a clear correlation between coil drive activity and the detection of a low voltage on the LED-current-monitor as seen by the HWWD (shows up as STAT_OUT = 8). I've attached two plots, one showing the two signals separately, on the other I have scaled the coil drive signal to a compatible Y-axis scale and plotted them together.
Hmm - perhaps current-loop would have been a better design given the long cables?
State of H1: locking, some issues with PI, with Tara's fix H1 is going to Nominal Low Noise
Assistance: Tara, Jenne, (Richard, Jason, earlier today)
NOTE: If TCSY tripps off, please call Kiwamu or Nutsinee before restarting, they are hunting errors, so need to see the system before restart
Activities:
Currently:
Not much IFO up time so far, but this morning I managed to move SRM in both pitch and yaw, and see a reduction of the noise. I recall this was already know. Moving pitch by about +20 urad seems to give the best position. Also the SRC1_P error signal respond quite well to the motion, and it seems to cross zero at the right position. Also, after SRM pitch is aligned, the SRC1_Y error signal repond to yaw motion of the SRM. So it looks like we should be able to close SRC1 both P and Y, although with small bandwidth.
The attached plot shows:
For the record, SRC1's error signal is AS_A_45_I for both pitch and yaw at the times he's looking (it gets switched to this in the SRC_ASC_high_power state, since we were considering these as candidates earlier).
With new thermocouple installed inside vertical section of exhaust pipe, I overfilled CP4 today. TC registered LN2 with very little forewarning. Temp fell to -60 deg C with LN2 trickling out exhaust (bypass exhaust valve open and check valve removed).
1:30 pm local Took 20 sec to overfill CP3 with 1/2 open on bypass LLCV, but found the entire exhaust line frosted over with a pile of snow on ground. Looking back at last year's LLCV level after a Dewar fill, I decided to lower the LLCV yet again from 17% to 16%. Left bypass exhaust valve open.
I added a second class to (userapps)/sys/common/guardian/cdslib.py for the Beckhoff FEs. This will look through the autoburt.req's that are created upon build, and find the DCUID from the model name, or vise versa. Code is loaded in and committed and the diffs are being reported.
[Jenne, Cheryl, Nutsinee]
We tweaked the calibration of the PSL rotation stage, which hadn't been done since the power incident on the rotation stage was adjusted about a week ago. Now hopefully a 50W request will give us 50W, rather than some higher value. Nutsinee has her script ready for next time, so we can try doing it automatically rather than by hand.
I have written a fitting script for PSL rotation stage calibration, and put it in ...../userapps/psl/h1/scripts/RotationStage/
First, run Nutsinee's script MoveRotationStage.py, which will move the rotation stage from -90deg to +90deg, in 5 degree steps, and record the measured angle and the power at the PSL periscope to a text file.
Then with Matlab, run CalibRotStage.m. This will load the data, calibrate it, and give you a plot with the fitted calibration parameters in the legend.
Finally, move those values to the PSL rotation stage's calibration screen.
Unfortunately though, when we use the LASER_PWR guardian to request 50W, we only get about 48W. This was true earlier with my hand-tuned calibration, as well as with the fits. This is something that could be looked into.
State of H1: locking and has made it to Low Noise
Activities:
Other Site Activities:
I have created new DAQ and HWWD oveview screens. The DAQ displays the additional diagnostics information Jonathan's new code produces. The HWWD includes the ITMX and ETMX systems which were installed yesterday, and shows which systems are connected to the ISI coil drivers.
I added 250mL of water to the TCSy chiller this morning, bringing the reading on the scale from 4.5 to 9.0.
In addition, the TCSy CO2 laser tripped out this morning on a flow alarm. Peter and I reset the laser box (key off, then key on) to clear the alarm and restart the laser. Cheryl had trended the flow channel for the CO2 laser and indeed the flow dropped to zero and recovered (I don't have the trend, perhaps Cheryl will post it later). Maybe an air bubble working its way through the system?
That's a bit concerning and not something that I believe we've seen (other than on this one system recently). Certainly possible that it's an air bubble. We'll need to watch this because if the flow sensor causes it to trip out then we will start having down time on the laser. Are there any bubbles visible in any of the tubing or do you think these are getting trapped at some high point in the system? The highest point overall should be up at the chillers, but there will be other local high points such as on the table.
The trend suggests that the flow rate only went to 0 for 3 seconds then made its way back up. Bubble does sound reasonable.
There look to be some regular dips in flowrate, perhaps also bubble related. Might be easier to see in non-trended data how long and deep these dips are.
I took a 30 second full data trend from the trip, also including the interlock signal. As can be seen the flow rate is not at its usual value of ~3.0 gpm for approximately 10 seconds. Interestingly, the interlock does not trip until the flow has been below nominal for ~3 seconds. Is this the expected behavior of this interlock?
There is a low pass filter on the input, so yes that's expected behavior. I am surprised that it goes negative though - this should be linear in current from the flowmeter which makes me think it can't go negative without the flowmeter running backwards.
(Late entry for yesterday's Maintenance Day activity) Kyle, Gerardo Scheduled preventative maintenance -> Measured discharge pressure to be =/> 115 psi - OK, greased motor shaft bearings with Chevron SRI and scroll compressor orbital shaft and crank pin bearings with Anest Iwata SL-140. Belts visual and adjustment - OK.
WP6232 Upgrade frame writers
Jonathan, Jim B, Dave:
h1fw2 was running with close to the new code, it was upgraded to add the md5 filename change only. Quickly following h1fw0 and h1fw1 were upgraded to the latest code. I am updating the DAQ MEDM to show the new diagnostic md5 check sum data.
WP6217 ISI frontend code upgrade
Hugh, Jim B
All ISI models were restarted with new code
WP6227 HEPI frontend code upgrade
Hugh, Jim B
All HEPI models were restarted with new code.
WP6235 PSL-DBB jitter feed-forward to LSC
Daniel, Gabrielle, Dave:
New code on the h1psldbb exports the jitter signal as a 64kHz Dolphin channel. The h1lsc model uses this feed-forward data. Change added a 16kHz LSC DQ channel to the commissioning frame.
WP6242 Migration of virtual machines to proxmox
Carlos
Old vmware virtual hosts were migrated to the new Proxmox system.
WP6236 SUS ITMX.ETMX model changes for HWWD install
Fil, Richard, Jim B, Dave
sister wp to 6234. The ITMX and ETMX hardware watchdogs were install. The h1susitmx, h1susetmx models were modified to read the HWWD status via the binary input feed from these chassis. Since we are not controlling these units, I did not put in the binary output logic.
WP6229 h1tcscs model change for SIM parts
Kiwamu, Dave
A new h1tcscs model was installed. We verified that the TCS CO2 chillers behaved correctly on loss of temperature control voltage.
WP6231 GDS-DMT upgrade
team-GDS
Code was upgraded, no impact was seen from the control room
WP6239 PSL-ISS model change
Daniel, Dave
New h1psliss model was installed. This was done at the same time as the h1psldbb change.
WP6240 Beckhoff Slow Controls change
Daniel, Dave
Daniel installed new PLC code. I updated the DAQ INI files, the target autoBurt.req files and the Beckhoff SDF monitor files.
WP6238 CAL-CS model change
Darkhan, Jeff K, Dave
a new h1calcs model was installed.
DAQ restarts
Dave:
The DAQ was restarted several times today to support the above work.
(note we did not get to removing h1ldasgw2 WP#6237, will defer this to later in the week)
Regarding the following:
WP6217 ISI frontend code upgrade
Hugh, Jim B
All ISI models were restarted with new code
Only the HAM ISIs models were updated. I might have implied to DaveB that I was going to do something to the BSC ISIs but in the end I do no changes there.
LP_v_H4 shows the laser output power and the head 4 flow rate. At this point in time the flow rate trip
0.2 lpm. The drop in laser power seems to coincide with the increase in flow rate.
XC_v_H4 shows the output of the crystal chiller and the head 4 flow rate. The chiller clearly switches
off after the spike in the head 4 flow rate.
InletP_v_H4 shows the inlet pressure versus head 4 flow rate. The oscillations in pressure take place
after the spike in the flow rate. The same is true for the outlet pressure.
The sudden increase in the flow rate perhaps suggests that something in the flow sensor may have
been dislodged but I (PK) would expect that the flow rate would not drop to zero but to some other
non-zero value. Unless there was a following object that promptly jammed things up. But things started
up okay for the subsequent startup.
The various filters in the system are clean from a visual inspection.
Jason/Peter
The trip Peter discusses above took place at around 6:17am PDT on Sunday, 10/9/2016.
The laser did trip off on Saturday (first reported by Patrick here) at 21:06:02 PDT (04:06:02 UTC, Sunday 10/9/2016). As noted by Kiwamu the reason for the trip was due to a trip of the Laser Head 1-4 Flow interlock.
PSL_Heads_Flow_2016-10-8.png shows the 4 laser head flow sensors around the time of the trip; head 4 is once again the most likely culprit. As seen in the plots posted above by Peter for the early Sunday morning trip, head 4 sees a spike in flow rate before falling off to zero. Interestingly, when compared to the actual interlock (PSL_Head4_v_HeadIL_2016-10-8.png) the interlock trips just prior to the spike in flow rate; from the plot it can be seen that the interlock starts to trip just before the spike in head 4 flow begins. The trip threshold at this time was set to 0.2 lpm, which none of the flow sensors were below at the time the interlock tripped; I can't explain why the interlock tripped.
PSL_Head4_v_XChil_2016-10-8.png shows the crystal chiller turning off several seconds after the interlock trips (5 seconds after in this case). I've noted this before (here).
PSL_Head4_v_InletP_2016-10-8.png shows the head 4 flow rate versus the inlet pressure in the PSL water manifold. The oscillation in the pressure occurs after the interlock tripped and has been seen before (noted above by Peter and here).
Evan, Daniel
17:12:30 UTC Oct 7 2016:
17:16:30 UTC Oct 7 2016:
17:18:30 UTC Oct 7 2016:
17:24:30 UTC Oct 7 2016:
17:32:00 UTC Oct 7 2016:
17:34:30 UTC Oct 7 2016:
18:06:30 UTC Oct 7 2016:
Spectra attached.
Coherence (modulation on)
Using 2600 V/W for the demod gain and transimpedance, and 29 mW of dc PD power, this implies the following AM depths:
| I | Q | |
| 9 MHz | 0.95×10−4 | 2.4×10−4 |
| 45 MHz | 1.9×10−4 | 8.2×10−4 |
Using 0.22 rad and 0.28 rad for the 9 MHz and 45 MHz modulation depths, this implies the following AM/PM ratios:
| I | Q | |
| 9 MHz | 0.43×10−3 | 1.1×10−3 |
| 45 MHz | 0.67×10−3 | 2.9×10−3 |
The attachment contains a budget of the expected CARM residual. The in-loop error point is taken from the CM board control signal, as was done previously. Here I used 2600 V/W for the transimpedance and demod gain.
The other measured traces are taken from the REFL9I readback (not from the CM board), so in principle there could be some extra dark noise at the error point from the summing node board or CM board. However, based on the O1 level this is of the same order as the shot noise (so we are not missing a huge amount of extra noise in this estimate).
Attaching earlier RAM plot, this time with informative labels
Here is a time series of REFL LF during the modulation depth reductions that happen during lock acquistion.
During the 9 MHz depth reduction (from 0.22 rad to 0.11 rad), the dc power changes from 4.83(3) mW to 4.27(3) mW. That means that after the modulation depth reduction, 4.08(4) mW of the dc light is from the carrier and 0.19(2) mW of the dc light is from the 9 MHz sideband (this assumes the 45 MHz contribution is negligible).
Note that the dc level is still settling to its final value of ~3.7 mW, so it's possible that these power ratios are evolving during the lock.