Laser Status: SysStat is good
Front End Power is 34.78W (should be around 30 W)
Front End Watch is GREEN
HPO Watch is GREEN
PMC: It has been locked 0.0 days, 2.0 hr 12.0 minutes (should be days/weeks)
Reflected power is 34.32Watts and PowerSum = 135.1Watts.
FSS: It has been locked for 0.0 days 1.0 hr and 27.0 min (should be days/weeks)
TPD[V] = 3.682V (min 0.9V)
ISS: The diffracted power is around 4.339% (should be 5-9%)
Last saturation event was 0.0 days 1.0 hours and 27.0 minutes ago (should be days/weeks)
Possible Issues:
Dave, Kiwamu, Nutsinee
--------------------------------------------------------------------------------------------------------
Quick conclusion: It's probably related to the CO2Y rotation stage.
Lengthy details: Dave notcied TCSY chiller DAC output went crazy yesterday. After making sure that it wasn't the model update (alog30429, alog30384) that did it we investigated further. The crazy output to the chiller was due to TCS guardian trying to lock the laser when there were no laser (as the result the guadian keeps increasing and decrasing chiller temperature by about 1 deg C).

The cause of CO2 laser trips was due to RTD/IR ALARM interlock tripped, which always coincide with either power-up state and lockloss state. Although not every power-up or locklosses caused CO2Y to trip. We also looked at POP but it's not showing here.

This immediately made us think of the CO2Y rotation stage that would only move during these times. Could this be either Beckhoff or electronics issue? The fact that it actually tripped the interlock box made me think of grounding issue. But I always blame grounding.
Also Kiwamu was able to untrip the RTD/IR interlock and get the CO2 into "ready" state just by toggling LASER ON/OFF button. This is what we don't understand. How is this even possible?

The End.
Tried the new feedforward path, adding the DBB Q1Y signal to the DARM IN1 signal. It's working.
First, I measured the transfer function from Q1Y to DARM (no noise injection), and fitted it. The result is shown in the first figure (I removed from the fit the 2kHz sharp feature which is clearly a misfit artifact). The filter is implemented in the LSC-JITTERFF bank.
The second plot shows the improvement in the DARM signal and the reduction of coherence whe the feedforward is on (blue reference with FF off, red with FF on). All the peaks remaining in the DARM signal are not due to the HPO jitter.
We shall see how stable this is over time.
A temporary MEDM screen for the jitter feedforward can be found here
/opt/rtcds/userapps/release/isc/h1/medm/JITTER_DBB_FF.adl
It's been linked to the LSC menu in the sitemap.
The model modifications are described in 30412.
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.
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.