Jason, Jim, Dave:

I've been looking into why when we restart the PSL front end models the shutter controlled by the diode room Beckhoff OPC gets closed. Specifically it happens when the h1pslpmc model is started.

The h1pslpmc model controls the shutter through ezcawrite to the Beckhoff channel H1:PSL-EPICSALARM. A ZERO keeps the shutter open, a ONE closes the shutter. Settings within the pmc safe.snap file are zero, so the front end should not output a ONE value on startup and the shutter should not close.

The shutter can be instructed to close by the model if the FLOW monitor (a raw ADC input to the model) lies outside of upper or lower limits. The FLOW signal is passed through a standard IIR filter module. Trending the INMON and the OUT16 of this filtermodule when we started the model last Tuesday reveals for the first second the OUT16 is ZERO while the  input is the ADC value. We suspect this is normal for an IIR integrating filter module. The zero OUT16 triggers the shutter close because it lies outside of the upper and lower limits.

The filter module does not have any filters loaded, has no offsets and has unity gain. We propose (and Jason agrees) that the next time we restart this PSL model we replace FLOW's filter module with an EPICS-OUTPUT part and see if we can get the shutter to remain open during the model startup.

(see WP 6111) 
RGA data following recent bake shows improvement but needs extended baking - will extend bake of Vertex RGA (running pump) until commissioners are negatively impacted.  

1000 hrs. local -> Heating of Vertex RGA resumed -> will need periodic access to measure temps and make adjustments

TITLE: 08/23 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventitive Maintenance
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Maintenace Day recovery has been halted by the IMC not locking. Investigation is ongoing.
LOG in attached txt file
 

M. Pirello, R. McCarthy, E. Castrellon

Work Permit #6116

We removed the ISC Anti-Aliasing Chassis and investigated channel 14 which was suspected to have a failure, per ALOG 29189.  To test the channels, we attached the DB9 Breakout to the front DB9 connector and used the SR785 to test the transfer function through the filter.  We applied the test leads directly to the differential test points on the PCB.  Channel 14 looked much like all of the other channels. Unfortunately, the data was corrupted on the thumb drive, but I did get one scan of channel 9 and have attached this scan.  Every scan was nearly identical to this scan.

We returned the chassis to its original location and reattached all of the cables.

J. Kissel

Here's your weekly broken record. Time to change the ETMX and ETMY bias sign!

Several quadrants of the H1SUSETMX and H1SUSETMY's TST L3 ESD systems show an effective bias voltage of around 40 [V], which is roughly 10% of the request / applied bias voltage of 430 [V]. This means the actuation strength is 10% different from its value in late June when we had last herded the effective bias voltage to 0 [V] and we'd hoped to begin the campaign of regular bias flipping (see LHO aLOG 27890). 

We're still waiting for a robust enough interferometer / acquisition sequence to declare we're happy (and probably also for me to be in the control room for a non-Tuesday late night when we're ever happy) to flip the bias sign and debug why we had troubles with ALS DIFF and switching to ETMY (see LHO aLOGs 28362 and 28152). 

Marc P, Chris W

As per Work Permit #6104, we added a 200 kHz lowpass filter (D1600314) to the fast path of the Common Mode Servo Board (D040180), located in the LVEA ISC-R1 rack. The serial number of the servo board is S1102626.

When reconnecting the power to the Common Mode Servo Board, the 17V supply was connected first (should connect 24V first or use the sequencer), which resulted in blowing diodes D4 and D5 at the power input (see D0901846). At the time, we saw LEDs of other boards on the rack turning off. The diodes were replaced and the current drawn by the Common Mode Servo Board was confirmed to be the same as drawn by an equivalent spare board. The board was then replaced in ISC-R1 rack, this time using the sequencer switch to power cycle the whole rack.

I have created two new "Beckhoff" SDF systems: h1hpipumpctrlsdf and h1pslopcsdf. These are built in the same way as Jonathan's slow controls SDF systems, following Jonathan's wiki-page instructions. They run on h1build and take the next available DCUIDs

h1hpipumpctrlsdf (dcuid=1033). Monitors settings on the three "purple box" hepi pump controllers

h1pslopcsdf (dcuid=1034). Monitors the diode-room Beckhoff OPC system settings (Peter K provided the channel list)

The two new SDF systems were added to the SDF_OVERVIEW.adl medm screen. Also the missing h1susprocpi was added, which necessitated making the screen taller to accomodate the additional sus system. The new systems are marked on the screen capture image attached.

After Daniel's h1ecac1plc1 code changes, I have installed the new INI file and restarted the DAQ.

Ramped CP4 LLCV in 5% increments, every 5 minutes, until it reached 100% full (39% to 63% open). 

Note:  generated alarm in CDS due to overfilling

Attached is a snap of the exhaust flow and pressure as LLCV ramped.

I lowered the fill set point from 92% to 88% and and will redo experiment once CP ramps down to 88%.

I've made a script to somewhat automate the weekly oplev trends FAMIS task. It makes 3 plots like the attached image of the oplev pit, yaw and sum channels for the test-masses, BS, PR3 and SR3. It still requires a little fiddling with the plot, you have to zoom in manually on any plots that have 1e9-like spikes, but this should still be easier than running dataviewer templates. It uses h1nds for data and a pre-release version of the python nds2 client that has gap handling, so updates in the future could break this. I'll try to maintain this script, so any changes or improvements should come to me. The script lives in the userapps/sys/h1/scripts folder.

The script is run by going to the sys/h1/scripts folder:

jim.warner@opsws0:~ 0$ cd /opt/rtcds/userapps/release/sys/h1/scripts

And running the oplev_trends.py script with python:

jim.warner@opsws0:scripts 0$ python oplev_trends.py

You will then need to do the usual zooming in on useful data, saving screen shots and posting to the alog. I'll look into automating more of this, but it works well enough for now. It would also be very easy to add this to a "Weeklies" tab on the sitemap, which I believe LLO has done with some similar tasks.
 

All vacuum pumping related connections are now removed from HAM5/HAM6

Darkham, Jeff, Jim, Dave:

h1susetm[x,y] models were restarted following changes to QUAD_MASTER.mdl.

Change is to replace DAQ DQ channel H1:SUS-ETMY_LKIN_P_LO_DQ with H1:SUS-ETMY_L3_CAL2_LINE_OUT_DQ and add an oscillator (H1:SUS-ETMY_L3_CAL2_LINE).

DAQ did not restart nicely. My change to add h1sysecatxxplcysdf INI and PAR files to daq master caused h1dc0 to stop on error "channel '' has bad DCU id 1024". I have removed these from the master and the DAQ is running.

PT-210b CC was not reading pressure, so I remotely rebooted.

Jenne, Sheila

We had an unusual lockloss a few minutes ago, related to 28255

I happened around 8:11  August 23rd UTC, the DRMI gaurdian seemed to think that the lock was lost although it was not.

Overview

A synchronized oscillator was added to QUAD_MASTER model test mass stage (L3). After re-compiling the SUS-ETMY model there will be two synchronized ossilators in L3 stage that will be used for driving calibration lines: *_L3_CAL_LINE and *_L3_CAL2_LINE.

Removed channel LKIN_P_LO from the list of DQ channels and added L3_CAL2_LINE_OUT into the list.

The h1susetmy model must be recompiled in order for the changes to take effect.

Details

For one of the two calibration lines that we needed to run during ER9 we used a pitch dither oscillator, SUS-ETMY_LKIN_P (see LHO alog 28164). After analyzing the ER9 data we found two problems with this line (see LHO alog 29108):

• First, the drive amplitude that we set was not sufficient for estimation of the time-dependence in the ESD actuation strength.
• Second, the CAL-CS model that calculates the time-dependent parameters rely on an oscillator that is synchronized with the ones in the SUS-ETMY and CAL-PCALY models. Since SUS-ETMY_LKIN_P is not a fixed phase (synchronized) oscillator, the phases have to be adjusted by hand every time the oscillator gets restarted. With synchronized oscillators this is will not be necessary.

The second synchronized oscillator was added at L3_CAL2_LINE_OUT and the list of DQ channels was modified accordingly. The L3_CAL2_LINE_OUT was added with sampling rate 512 Hz. LKIN_P_LO was removed from the list of DQ channels.

The changes were commited to USERAPPS repository, rev. 14081.

HEPI BS Tripped few minutes before ITMX ISI.  This is the only HEPI that tripped in the neighborhood of the large quake.

ITMY ISI tripped--timing (H1:ISI-ITMY_ST2_WD_MON_GPS_TIME) indicates stage2 tripped on ACTuators 1 second before Stage1 on T240s but looking at the plots, the Actuators have only registered a few counts, nothing near saturation/trip level.  But the T240s hit their rail almost instantly.  It seems the Stage2 Last Trip (H1:ISI-ITMY_ST2_WD_MON_FIRSTTRIG_LATCH) should be indicating ST1WD rather than Actuator. On ETMY, the Trip Time is the same for the two stages and Stage2 notes it is an actuator trip but again, there are only a few counts on the MASTER DRIVE; seems this too should have been a ST1WD trip[ indication trip on Stage2--I'll look into the logic.

On the BS ISI, the Stage1 and Stage2 trip times are the same, and the Last Trip for Stage2 indicates ST1WD.  The Stage2 sensors are very rung up after the trip time but not before unlike the T240s which are ramping to to the rail a few seconds before trip.  ETMX shows this same logical pattern in the trip sequence indicators.

On the ITMX ISI, Stage1 Tripped 20 minutes before the last Stage2 trip. This indicates the Stage1 did not trip at the last Stage2 trip.

No HAM ISI Tripped on this EQ.

Bottom line: the logical output of the WDs are not consistent from this common model code--needs investigating. Maybe I should open an FRS...

Attachment 1) Trip plots showing Stage2 trip time 1 second before the stage1 trip where the stage2 actuators do not go anywhere near saturation levels.

Attachment 2) Dataviewer plot showing the EQ on the CS ground STS and the platform trip times indicated.