TITLE: 03/21 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:
LOG: Attached

As we plan to re-open BSC10 on Monday morning, I have restarted the clean rooms at E Y. The cleaning crew will do a cleaning of these tomorrow. 

Thanks for the time to the Squeezer crew!  And to CoreyG for coming back for more everyday.

Pulled the feedthru again and just sitting in the area seemed to change the readout.  I could do some minor manipulation of the cable and send it to the rail and put some pressure and a particular bend to get it to read reasonable values.  Wasn't going to mess with fixing and end up worrying how long it would last--just pulled it and replaced it.  New sensor worked fine and repeatably.

With three working vertical sensors, we got a new locked position, unlocked and quickly balanced the table.  Relocked and only saw a slight shift.  Did a payload consolidation and refloated.  ISI damped and once things were really settled down, Isolated the platform.  Left the ISI locked on stops so SQZ crew could climb around as needed.

CAVEATS:

Unable to milk the new cable through the copper braided shield, will need to disconnect from feed-thru to do that, once I find/get a milking fid.  Need smaller kinder peek zip ties--the big ones we have are just too hard on the small CPS cable which could be contributing to shorting.

I still need to as-build the payload--it is different than last Thursday now.

We need to get an Isolated spectra for closeout.

See photo below--I'll try to get some pointers on it (it is fuzzy too) but you can see where the zip ties a couple inches from the ends have damaged the insulation exposing the inner shield.  There is also some shield visible at the BNC connector--this is where I was able to make it work and fail repeatably.

I've looked at 3 consecutive glitches in TCSX QPD B using the _DQ channels added yesterday.  The shape of all 3 glitches are the same, and have a shape that looks very much like a step function (with a second glitch about 3/4 of the way through the first).  To the best that I can measure in dtt, the interval between the first and second glitch is 900.098 seconds, and between the second and third glitch is 900.577 seconds, so 15 minutes +/-0.5 seconds.  Attached plots of the three glitches show that the ISS and RIN signals also see the glitch.  Related alog 41076.

I installed the new TEC controller for the ALS SHG. The settings are attached in Figure 1. Ugf around 100mHz. 

Figure 2: Small step response.

Figure 3: Turn-on transient. It takes about 30 second to come to equilibrium.

Added the ZMs with their sliders and made them light blue. Shots attached.

The open/close logic of the HAM6 beam diverter has been inverted to account for the new layout.

WP 7426

Daniel, Dave, Filiberto, Patrick, Richard

Yesterday Filiberto and I connected a Beckhoff EP6002-0002 serial interface module to the h1ecatc1 slow controls network (Box 300 in the attached screenshot of the h1ecatc1 system manager). The module is located behind the TCS chillers on the mezzanine in the mechanical building and connected by CAT5 to a Beckhoff CU1128 EtherCAT hub in the bier garten. It is currently powered from a 24V power supply installed in the TCS rack (also supplying power for a safety relay). Filiberto connected the first RS232 port on this terminal to the serial port of the TCSX chiller and the second RS232 port on this terminal to the serial port of the TCSY chiller. I then modified the settings on each of the chillers to enable RS232 serial communication at 9600 baud. I added the terminal to the h1ecatc1 system manager (initially in the wrong location) and updated PLC3 to run the code I wrote for serial readout/control (Chiller.lib). I have not yet made a standalone MEDM screen, but there is an auto-generated one available from the sitemap (SYS -> EtherCAT overview -> H1 C1 PLC3 -> Tcs -> Itmx or Itmy -> Chiller (see second screenshot)). Dave has added the new channels to the DAQ.

To do:

- If an error is reported from the serial code, it does not appear to propagate up to the top EtherCAT overview screen.
- Test powering on/off the chiller from the new interface. Writing 0 and then 1 to H1:TCS-ITMX_CHILLER_POWER_REQ/H1:TCS-ITMY_CHILLER_POWER_REQ should turn the respective chiller on. Writing 0 and then 2 should turn it off.
- Create a dedicated medm screen.
- Set the precision fields in the PLC code.
- Mount the EP6002-0002 module in the rack and make dedicated serial cables (current ones use screw terminals).

FAMIS6567

Added 70mL to the cyrstal chiller.

FAMIS6942

The only thing that the two scripts reported is:

ETMX ISI high freq noise is high.

TITLE: 03/21 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 2mph Gusts, 1mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.22 μm/s
QUICK SUMMARY: Peter is in the PSL, Mark and Mark are test fitting the platform on HAM6 HEPI

h1tw0 install

Jonathan, Carlos:

The new h1tw0 was connected to the DAQ 10GE switch and started.

EY weather station restart

Jeff B, Dave:

Squeezer front end code

Sheila:

New h1omc, h1sqz and h1sqzwfs models were installed.

New Guardian Nodes:

TJ:

DAQ Restart

For:

    h1sqz and h1sqzwfs code change

    h1ecatc1plc3, h1ecatc1plc4 new channels

    H1EDCU_GRD.ini 

   additional h1tcscs DQ channels

Terry, Arijit, Sheila, Daneil

We started by using the scanning OPO to align the transmitted red beam through the two apertures on HAM6 (we mechanically moved ZM1 in yaw but not pitch) to the temporary DC diode we have installed in homodyne path. We scanned the OPO and saw that our seed beam wasn't well aligned to the OPO.  We adjusted pitch on the 1064 collimator, and a small yaw adjustment.  We hadjusted the TEC temperature to roughly align the red and green resonances (for the current crystal position).  Daniel helped us get the OPO locking and we were able to see the amplification and deamplification of our seed beam. We didn't try to optimize the temperature or crystal position yet.  We are not scanning the seed phase but the ambient excitation is large enough that it is scanning very quickly on its own (purge air is rather high and the table is locked). 

With this fairly bright red beam generated by the squeezer we removed the septum window protector and looked for a beam returning from HAM5, but see nothing.  Daniel and Arjiti added excitations SRM, but we still didn't see anything, so we decided to leave excitations running overnight on SRM and ZM2 and look in the morning at AS QPDs to see if the beam hits them.  We have left the LVEA in laser hazard for this reason, and left the two soft covers with a small opening for the green beam to reach SQZT6.  

If we see nothing overnight we will try to taking a look through viewpoints on HAM5 tomorrow. 

The mode-matching lenses were adjusted to produce a beam diameter of approximately 280 um, 76 mm away from the
input window of the power amplifier.  The two-lens solution, using a nominal -50 mm and 80 mm focal length lenses,
is very sensitive to the position of the second lens.

    The power amplifier was turned on, without any incident beam from the front end laser, without anything
untoward noticed.  A low power beam from the front end laser was put into the amplifier and an amplified beam
was observed coming out.  There is still some alignment work to be done to see what the output power of the
amplifier will be, in addition to mode matching and alignment to take its output through the rest of the optical
train.

    The amplifier was operated without the shutter, as we do not have the parts in hand to complete fabrication
of the shutter.



Ed, Georgia, Peter

Current state: ISI is locked down on stops; the platform is NOT balanced, Corner3 CPS Feedthru is held by just a bolt or two, there appears to be a short to ground on the V3 CPS cable.

Again w/ much help from Corey, we determined that the Corner3 CPS H & Vertical connections in chamber were swapped.  Similar to the swapped Coil Driver cables which made damping impossible, the swapped CPS cables made isolating problematic.  The swapped CPS cables of course made balancing the table sort of confusing but pretty clearly explains the big 'horizontal' shift we were seeing when the platform was locked:  What we thought was balanced was anything but what we thought and locking the locker was just pulling the vertical back into a reasonable place.

The excessive noise seen on H3 led us to breaking the seal on the feedthru and during this process, the V3 signal went to the negative rail which implies a short to ground of at least the sensor shield and/or maybe, the sensor core to its shield.  We pulled the copper braided shield back as far as we could but could find not even a subtle break in the insulation exposing internal shield to the grounded copper braid.  While manipulating the cable looking for the short, there would occasionally be a reasonable signal but we were unable to isolate a definitive bad spot.  We must continue this as balancing is not possible until we have the three vertical CPS signals.

In the morning we'll move the cabling to a better place for working and looking for the short.

Summary of new features:

• Blends and sensor correction will be split into two separate nodes.
  • This cleans everything up and helps simplify how/when the SC can be changed.
  • We are currently not changing the HAM blends so they don't get a BLND node.
• Most of the states and edges are now auto-generated from a single configuration file.
  • The user can simply change the name of configurations, filter banks, filters, etc. in the file and then load the node. No editing of code necessary. This is very similar to how the rest of the SEI Guardian code is written. I tried to stay consistent at least.
• Allows for two different ways to switch sensor correction.
  • We do it slightly different compared to how LLO wants to do it, so I wrote both in.

Longer explanation of work:

All of the old SEI nodes that ended in *_CONF have been destroyed (a total of 15), and have been replaced with one or two other configuration nodes. Every HAM and BSC stage now has a sensor correction node (15 in total, name ends in *_SC), and each BSC stage also has a blend node (10 in total, name ends in *_BLND). Back in September, I tested the SC code on ITMX (alog38588) in preparation for this new setup but ran out of a time and a window to implement it. This week was looking to be perfect time to get us into our new configuration setup. The old setup was a product of JIm and I figuring out how to run the blends and sensor correction together to move the IFO into different seismic configurations based on what the environment was doing. We seem to have settled on a good way to do it after O2, but the old nodes were getting too complicated. A rewrite was necessary.

Breaking each CONF node up into separate blend and sensor correction nodes made them a bit more straightforward. I also changed it to read a large configuration file to obtain and create all of the necessary states and transitions. This is how much of the other SEI Guardian code is, and I felt that it helped the SEI team to make changes a bit easier. Plus, I've found that staying consistent with code within subsystems is generally helpful.

I tested the new nodes on ETMY first and checked with Jim before pushing it through to the rest of the chambers. I still have a bit more name changing and a few settings to change tomorrow, but all of the nodes seem to be running well.

Still left to do this week:

• Adapt the SEI_CONF manager to work with the new nodes
• Write an INIT state
• Clean up code and add more comments
• Update all of the medm screens that have the old nodes
• Possibly rework the Guardian Overview screen, if time permits

I've attached a shot of the current overview for your viewing pleasure.

Since the SEI_CONF manager is not able to communicate with these conf nodes yet, for tonight we cannot use the "LARGE EQ" button, or use it to turn off BRS corrected sensor correction. The BRS is not a big deal at the moment since those paths are all turned off.