Due to the inability so far to damp the 18040Hz mode I have switch the PI damping to the DCPD HF path.
I changed up a few things such as:
If there is any problem with this version, please don't hesitate to go back one revision.
Attached are plots of the transfer functions measured this morning. The input modecleaner was disabled whilst these measurements were obtained. Note the frequency servo schematic is D040105 C20F22-1.tif: common gain = 20 dB, fast gain = 22 dB C20F16-1.tif: common gain = 20 dB, fast gain = 16 dB C20F22FastMon.jpg: transfer function measured at TP10 C20F22PCMon.jpg: transfer function measured at TP9 C20F22TP8.jpg: transfer function measured at TP8 (should be 10X greater than TP9 measurement) common gain = 20 dB, fast gain = 22 dB C16F22TP8.jpg: transfer function measured at TP8, common gain = 20 dB, fast gain = 22 dB C16F22TP9.jpg: transfer function measured at TP9, common gain = 20 dB, fast gain = 22 dB C20F16TP9.jpg: transfer function measured at TP9, common gain = 20 dB, fast gain = 16 dB C20F16TP8.jpg: transfer function measured at TP8, common gain = 20 dB, fast gain = 16 dB C20F16TP3Spectrum.jpg: noise measured at TP3 (the mixer monitor, or error point) common gain = 20 dB, fast gain = 16 dB C20F22TP3Spectrum.jpg: noise measured at TP3, common gain = 20 dB, fast gain = 22 dB CrossoverSpectrum.jpg: has the two noise spectra overlapped for a visual comparison.
The smoothing factor was set to 0.999 on all CPs. To confirm that the device is still active and responding and not in an "inactive state" (which happens if smoothing factor is set to its limit of 1.0), the LLCV trends over 30 days are posted for the seven CPs (CP3 excluded). The smoothing factor algorithm (from EPICS integrated into Beckhoff): if SMOO is 0 or INIT is True, VAL = val else VAL = val * (1 - SMOO) + Previous_vale * SMOO *this implements a first-order infinite impulse response (IIR) digital filter with z-plane pole at tau=-T/ln(SMOO), where T is the time between record processing
Attached are screenshots for the past 7 days of optical lever trends for PIT, YAW, and SUM.
This completes FAMIS request 4683.
Peter was in the PSL enclosure and looking at the FSS - his alog will give details.
He's done so I'm starting to lock.
DRMI locked at 16:36UTC
POP X PZT railed, but POP signal is still centered on the QPD, so this is on the "to be fixed" list, but does not prevent locking. POP X is accessable from the ASC overview screen.
in DC READOUT TRANSITION, OMC guardian was stuck in DOWN, and was unstuck by running it through INIT.
I unintentionally killed the lock by requesting the INCREASE POWER state in ISC_LOCK.
I thought this would just stop the ISC_LOCK guardian in this state, keeping the input power at 38W.
Instead it reran the code for INCREASE POWER from the beginning and lowered the input power to 10W, killing the lock.
Broken:
So I thought the power was going to increase to 50W, based on what the LASER_POWER guardian main screen was showing, however TJ explained that the guardian can only request so many states, so the power was going to stop at 40W but the guardian could not show that because 40W was not a requestable state.
Fixed:
TJ rewrote the LASER_POWER guardian to make 40W a requestable state, so when we're going to 40W it will show this.
TJ also set the ISC_LOCK to stop at 25W input power on out next lock.
Currently, we have the IMC locked and at 40W input power.
Keita is looking at the ISS Second Loop and measuring the correct offset for 40W.
18:32UTC - adjustments made for running at 25W are complete - now relocking H1
DRMI locked at 18:43UTC
19:12UTC - H1 in DC readout and heading to ENGAGE ISS 2nd loop
19:58UTC -------------
H1 made it to ENGAGE ISS 2ND LOOP which is good, because getting to the point where we could engage the 2nd loop is progress, however engaging the loop revealed an issue which broke the lock.
Jenne and Keita are looking into it.
******** my estimate of having H1 in Observer was a bit optomistic - 4PM today (23:00UTC) is more likely.
21:04UTC - locked and going to ENGAGE_ISS2ND_LOOP without engaging the loop, to do measurements
lockloss
last entry for this log:
21:52UTC - H1 is back in ENGAGE ISS 2ND LOOP with the ISS 2nd loop disabled.
Keita and Jenne are looking for a fix, so H1 can go to Observe.