Added Beam Rotation Sensor usage info on the BSC ISI Overview. The signals that produce the Active indication are necessary but not sufficient. There are a number of elements that must be inplace (turned on) for implementing the BRS correction. But the correction will be inabled/disabled typically via the MATCH gain. This will eventually be controlled by the guardian.
For operators now, if someone is going to the End Stations and will be anywhere near the BRS, it should be disabled, for now by notifying SEI and otherwise zeroing the gain on the Beam-line Match bank, see 1st attached shot: If the BRS box on the ISI OVERVIEW indicates Active, open the ST1 SENSCOR medm and then the translational MATCH medm and zero the Beam-line gain: X for EndX etc.
For the Seismometer Mass Centering, the need for which is identified by a scheduled FAMIS task result, (see 26426 & 26418,) this task must be preformed with the Seismometer out of the control loop. Bring up the BIO medm accessable from the ISI OVERVIEW, see the 2nd attachment.
For the T240s, an individual BSC SEI Manager is taken to DAMPED. When in the DAMPED state, the T240 needing centering's mass is pushed by pressing the numbered (corner) button in the AutoZ area of the T240 Outputs group. The AutoZ widget should show engaged (going green,) press again to disengage after at least 1 second. The U V W mass positions can be monitored for efficacy of the process in the T240 Inputs group; these numbers should get smaller.
For the floor seismometers (STSs at the moment) doing the CPS sensor correction, the process is more involved as the seismometer is correcting all chambers. All HAM chamber's Sensor Correction MATCH filter gains are zero'd. For BSCs, the Z correction is applied to HEPI while X & Y go to the ISI, so all those must also be zero'd. There is a script for this built by TJ, alog 25936, repeated here:
thomas.shaffer@opsws10:/opt/rtcds/userapps/release/isi/h1/scripts$ ./Toggle_CS_Sensor_Correction.py -h
usage: Toggle_CS_Sensor_Correction.py [-h] ON_or_OFF
positional arguments:
ON_or_OFF 1 or 0 to turn the gain ON or OFF respectively
optional arguments:
-h, --help show this help message and exit
Once the Sensor Correction is all disengaged, the STS masses are centered by pressing the Auto Zero button in the STS-2 area of the Outputs group. This is a momentary and does not have to be pressed again to be disengaged. The masses may also be monitored in the same area.
These instructions will be repeated in a FAMIS conditional task.
According to Matt's alog 26499, the 1/f^2 mystery noise needs to have an amplitude of about 1e-20m/rtHz at 100Hz.
With the ESD actuation function ( ~6.38e-8m/N * (100Hz/f)^2 ) this corresponds to a flat force noise of about Fc = 1.5e-13N/rtHz.
We can cast this into a voltage noise at the ESD F=alpha*V~2:
Parameters:
alpha-~2e-10N/V^2,
bias voltage V0-380V.
For the linear coupling this implies V = Fc / (2*alpha*V0) = 1.0 microV/rtHz.
In principle the quadratic nature of the ESD can also down-convert higher frequencies. For a band of white-ish noise with a bandwidth BW, the resulting force noise is F_DC = alpha * V_RF^2 * sqrt(BW). To produce the mystery noise through this down-conversion, assuming a noise bandwidth of BW~1MHz, would require ~1mV/rtHz at RF frequencies.
1115 hrs. local Exhaust check valve bypass opened, LLCV bypass valve opened 1/2 turn ccw -> LN2 at exhaust after 2 mins 10 secs -> Restored valves. Next manual overfill to be Friday, May 6th.
When I started the ETMy Charge measurements today, I checked the Aligned state oplev centering. It was WAY off. So, I reset the alignment back to a more recent nominal pointing (based on trends) since yesterday's bootfest set all pointing biases to old values. Note - we should reset to a good IFO pointing across all SUSes ASAP.
However this didn't help much on the Oplev which was out at some -90 in Pitch. The long trend (attached) shows a major drift in the Oplev from ~March 20th to April 13th where it started to flatten out. (Note there is a period of poor alignment for the week after April 13th, and then the pointing is restored, and the flattening out of the Oplev resumes. Unsure of what tipped off the major drift, I checked VEA Temp - all good. A check of the alog around the March 21st date indicated that the "grout work" finished around March 21st. Wow, long grout dry time.
So, time to rezero!
For reference, our OpLev's only exhibited approx 10 urad pitch drift over a couple of week period following the pier grouting work being carried out at LLO (see LLO aLOG entry 17030).
WP5857 Keith, Rolf, Jim, Dave:
Tuesday 3rd May we upgraded the CDS front end systems and the DAQ to RCG3.0.2
The order of build-install was:
During the make installWorld h1fs0 developed a major NFS problem and stopped serving /opt/rtcds file system. We reboot h1fs0, but the NFS service did not start correctly and clients could not umount nor mount the file sytem. We restart kernel-nfs-server daemon and the NFS clients remounted correctly.
I need to change the SUS ITMY and ETMY now the HWWD part is synced to the hardware regarding signal levels (I removed temporary NOT inverters on binary signals).
16:00 h1iscex developed the connTrack Table Full error, new network connections were not permitted. We have to reboot this computer and disrupt the EX Dolphin fabric, requiring all EX models to be restarted (except susaux).
Vacuum controls Beckhoff gauges on BSC7,8 were moved from their temporary slow controls Beckhoff connect to the LX vacuum controls system. This required a name change (H1->H0), minute trends were changed on DAQ.
Upgrade built ISI-HAMS with latest isihammaster.mdl file, but team SEI needed to back out this latest change, so common file was reverse-merged to previous version and all isi-ham rebuilt and restarted.
CAL system was modified to remove the Blind Injection data path (h1calcs and h1calex).
Big DAQ restart at end of afternoon: new VE EDCU list, new Slow Controls EDCU LIST, new Dust monitor EDCU list, new susitmy/etmy hwwd code, new isi-ham models, new cal models
As of now CDS overview shows some IPC errors all related to h1iscex in H1HPIETMX (H1:LSC-X_TIDAL_HEPIETMX-IPC), H1ASC (a bunch of ALS ASC signals) and H1OAF (H1:SEI-EX_2_OAF_MUX_RFM).
Seems like the errors started at about 18:59 or so, went away after 3 minutes, then came back at about 19:53 or so and never went away, all UTC.
Hmm, now they're gone.
The web view of the vacuum medm screens has been updated again to eliminate the now obsolete original overview screen and LVEA overview screen.
I am adjusting the CP2 LLCV PID parameters controlled by Beckhoff system. 1. Set to manual mode at 35% open and adjust PI settings while in manual mode and observe value in data viewer real time. PI still updates its values in manual mode. Note that every time a PID value is changes the LLCV % open value resets. The pneumatic actuator is physically jouncing up and down and will wear out prematurely at current Beckhoff settings. The new electronic actuator on CP1 is not jolting as much as CP2, but up/down movement is still noticeable at rapid rate - PID parameters should be addressed. Have not surveyed the other five actuators (CP3 doesn't count).
Unsuccessful in adjusting PI parameters today (P & I gains set too low from nominal 6 & 360 s. values, respectively), which significantly reduced the physical jitter in the LLCV by reducing % open signal amplitude but did not settle to the set point. But good news! At the end of the day, Patrick provided the magic button. There is a way to apply a smoothing factor on the CP liquid level (0
Good work Chandra - keep at it - this is a worthy pursuit for familiarity with the new Beckhoff controls - I will need you and Gerardo to brief me on the new environment as soon as time permits
Major activities:
- PSL work to restore the laser/alignment
- beam tube baking in LVEA
Activities for today- details:
- Christina - opening roll up door, LVEA receiving
- Jim - BRS
- Stefan - coil drivers
- Patrick - rotation stage - progress
- Peter - no damage but might need a major re-alignment
- Bubba - beam tube sealing continues
- Chandra - baking RGA through Friday
--- investigating a small anomaly in a vacuum gauge, likely electrical
- Stefan - log about wind and piping
- Recovery from upgrades yesterday looks good so far, but...
- Travis - p-cal calibration
- Cheryl - IM work, may see IMs swinging
- Karen and Christina in LVEA vacuuming and mopping
While I was at End X (around 7pmish) I heard repeaded banging noises coming from the GN2 pipes (GN2 BURST, GN2 VENT and GN2 REGEN). Not sure whether that's a know isssue, but it was rather loud, and the support piers were shaking noticably.
This was observed between 00:46 and 0144 UTC on May 4th (17:46-18:44 PDT on May 3rd).
Also, the observation was done inside the building. I did not investigate the outside.
GN2 = "gaseous nitrogen"
LN2 = "liquid nitrogen"
for those tracking our jargon.
John and I investigated Wednesday afternoon and found everything quite -> John excited the ambient-air vaporizer (large finned aluminum ambient heat exchanger mounted on the concrete slab near the supply dewar outside of the building and piped in-line with the GN2 REGEN connection to the pump and which is easily mechanically excitable with wind) while I was in the VEA listening - Nothing -> We also created excessive LN2->GN2 boil-off in CP8 by filling in manual mode at a "high" LLCV %OPEN setting - Nothing. We did note that, nowhere in the piping between the ambient air vaporizer and CP8 was the piping clamped to anything. In fact, it was just resting on pipe stands. Also, an "ice ball" had formed on the bellows at the pump penetration - reminding us of the fact that all of the ambient air vaporizers on the X-arm have severed welds at the ASA connection flange which results in a parallel path for the GN2 exhaust to exit he pump -> We then capped the piping to eliminate this as an excitation mechanism
See also alog 26948. I repeated the L2 noise measurements described in alog 26948 for ETMX L2 and ETMY L2, as well as BS M2. For completeness I also added the ITM noise to this log.
The measurement conditions are the same as in alog 26948 (Acq Off, LP On, small 3kHz length drive).
Conclusion: no suspicius noise on the L2s (or the BS M2).
Plots 1-5 (in that order): ETMX, ETMY, ITMX, ITMY, BS
Plot 6: projection of the noise for the four main test masses.
Remark: ETMY features a 10Hz line, as well as a smaller 30Hz line. They seems to be real, and they have a different strenghts in the 4 coils.
For future reference and noise budget purposes I attached text files for all 5 noise measurements. Each file has 5 coilumns: frequency and coils 1-4
Daniel, Dave, Nutsinee
The first problem with some TCS Beckhoff channels returned bad vaults was probably due to bad values in safe.snap file (I didn't know Beckhoff channels were monitored on SDF!). The second problem I ran to was the channels in TCS oaf model went bogus after the front end restart this morning. Dave burtrestored the values to where they were yesterday and everything seems fine.
Below I've attached the result of today's rotation stages random walk script to test the new Beckhoff control configurations for PSL RS (which was later applied to CO2 RS).
Quick Conclusion:
PSL RS requested angle and measured angle agree within 0.02 degrees (better than before).
CO2X RS requested angle and measured angle agree within0.03 degrees (better than before)
CO2Y RS requested angle and measured angle agree within 0.1 degrees (worsen)
I also increased the CO2 RS velocity by a factor of 30 and the acceleration and deceleration by a factor of 10 as Daniel suggested (3000, 10000, 10000).
And because of worsen the CO2Y RS performance the angle vs. power calculator is a bit off right now.
I've been testing the new HWS Python code on the H1HWSEY machine. It's been a helpful identifying run-time bugs in the code. Right now, it is running smoothly on ETMY. It withstands the ETM HWS being turned off and on again.
There are still a few minor issues to sort out but hopefully it'll be ready for deployment on the vertex machines in a day or two (pending approval of an ECR).
WP 5862 and 5865 Filiberto and Richard moved the cabling for the PT170 and PT180 Inficon gauges from the second port on h1ecatc1 to h0velx. I updated the code on h0velx to read them. For some reason when the gauges were moved they stopped reading in Torr. I changed the reading back to Torr in the CoE parameters and sent the command to save the settings to non-volatile memory. The code change also added error channels and channels to set the amount of smoothing on certain channels. The amount of smoothing had been hardcoded. The smoothing on these channels is now at the default 0 until I set the values for these to what they were hardcoded to. I also changed the filter in the terminal for the CP2 LN2 level readback. On h0velx, terminal M17, CoE parameter 8000:15, I changed the filter from '50 Hz FIR' to 'IIR 7'. I removed all of the channels and terminals for the Inficon vacuum gauges from h1ecatc1, h1ecatx1 and h1ecaty1. They were temporarily on these computers until the new Beckhoff vacuum controls were installed. The channel names changes for the PT170 and PT180 gauges are: old name | new name H1:VAC-LX_X2_PT170_PRESS_OVERRANGE H0:VAC-LX_X2_PT170_MOD1_OVERRANGE H1:VAC-LX_X2_PT170_PRESS_SENSOR H0:VAC-LX_X2_PT170_MOD1_SENSOR H1:VAC-LX_X2_PT170_PRESS_TORR H0:VAC-LX_X2_PT170_MOD1_PRESS_TORR H1:VAC-LX_X2_PT170_PRESS_TRIP H0:VAC-LX_X2_PT170_MOD1_TRIP H1:VAC-LX_X2_PT170_PRESS_UNDERRANGE H0:VAC-LX_X2_PT170_MOD1_UNDERRANGE H1:VAC-LX_X2_PT170_PRESS_VALID H0:VAC-LX_X2_PT170_MOD1_VALID H1:VAC-LY_Y2_PT180_PRESS_OVERRANGE H0:VAC-LX_Y2_PT180_MOD1_OVERRANGE H1:VAC-LY_Y2_PT180_PRESS_SENSOR H0:VAC-LX_Y2_PT180_MOD1_SENSOR H1:VAC-LY_Y2_PT180_PRESS_TORR H0:VAC-LX_Y2_PT180_MOD1_PRESS_TORR H1:VAC-LY_Y2_PT180_PRESS_TRIP H0:VAC-LX_Y2_PT180_MOD1_TRIP H1:VAC-LY_Y2_PT180_PRESS_UNDERRANGE H0:VAC-LX_Y2_PT180_MOD1_UNDERRANGE H1:VAC-LY_Y2_PT180_PRESS_VALID H0:VAC-LX_Y2_PT180_MOD1_VALID Gerardo shimmed the LLCV for CP2 during this work. It is now back on PID control. The medm screens have not been updated on the Beckhoff vacuum controls computers other than h0velx. This still needs to be done.
Attached are plots of PT170 and PT180 over the last 7 days including before and after the move.
Superseeds alogs 26910 and 26924
Bad news: There is lots of MHzish pick-up on the cables to the ITM L2 coils: ~50mVpk
Good news: The ITM L2 coil noise at low freuency is very good: 1.5nV/rtHz at 25Hz, and we might not care about all that pickup.
Details:
The 10Hz harmonics reported in alog 26910 was a measurement problem, generaterd in Rai's preamplifier box (D060205). The cables pick up on the order of 50mVpk at around 1MHz, which was amplified by 100x, causing slew-rate down-conversion.
This was fixed (in the measurment setup) with a 270nF capacitor in prarallel to the 23.8Ohm cable and coil resistance, resulting in a 24.7kHz pole to cut off the cable pick-up.
Plot 1 and 2:
ITMX and ITMY coil noise.
Configuration:
- Everything (coil driver, cable, coil) was connected. The breakout box was inserted between coil driver and cable to the satellite amplifier.
- The L2 cois drivers were both is state 3: Acq Off, LP On, which is the run mode. They are never switched for the ITMs.
- The coil driver inputs were left connected to the DAC/AI. I also sent a 100ctpk, 3kHz signal into H1:SUS-ITM[XY]_L2_DRIVEALIGN_L2L_EXC, corresponing to a 2.6ctpk signal on the DAC. I did this to make sure the DAC is as least flipping bits, which raises its noise level.
- A 270nF capacitor was put in parallel to the coil using a pomona box to avoid saturating the D060205-preamp.
- The preamp has a gain of 100. After the preamp a 100Hz low pass was used (1595Ohm and 1uF) to allow the SR785 to run in the lowest noise mode.
Plot 3:
Noise projection assuming incoherent noise and assuming the ETMs behave the same.
Plot 4:
High frequency noise pick-up on the coil cable (coil driver disconnected).
The dominant noise is at ~1MHz, broadband.
Shown are two traces: one in nominal configuratiuon (green), and one with an additional choke on the cable to the coils.
Plot 5:
Scope trace of the high-frequency signal (only the x100 amplifier is used). The signal is made up of ~10msec bursts every ~100msec.
Plot 6:
All 4 coils (without amplifyer) directly connected to the scope. Note that the grounded inputs of the scope slightly change the signal.
Plot 7:
Scope trace with only an antenna connected to the scope. The signal pickup was largest between the racks - I could not trace it to a source yet.
For reference, the data and matlab code is available at ~controls/sballmer/20160429/plotIt.m
Also, since we probably have to do similar noise checks when we have the IFO back, here is the equipment I used: Top: Ring antenna Bottom, from left to right: choke, breakout card, 270nF parallel capacitor box, Rai's preamp box, 100Hz LP filter, AC coupling for looking at RF on the spectrum analyzer.
Plot 4. With the cable disconnected from the Coil drive the Shield is no longer terminated. This may contribute to the pickup.
The high frequency noise coupling in in plot 4 is mostly common, and shows up because Rai's preamp has no differential sensing.
In the attached plot the noise seen on ITMX coil 1 is plotted, once sensed with Rai's single-ended preamp, once with an SR560 in differential mode.
Conclusion: This noise does not show up on the coil current.
However: The same common HF noise pickup seems to be present on all cables. This now makes me worry about the ESD: I suspect the ESD has much less common rejection, because the +400V and -400V comes in on different cables. Moreover, a broadband noise at 1MHz on the ESD will produce noise near DC due to the quadratic nature of the ESD coupling.
I also tried to use the antenna to locate the source. The field is strongest in a circle arouind the rack, suggesting the source might not be in the electorics room, but rather just brought in by all the cables.