The first pumpdown of BSC9 with the iLIGO stack.
J. Kissel, P. Fritschel Of interest to several on-going investigations, Peter and I took a look at the noise monitor channels for H2 SUS ETMY for the UIM (L1) and PUM (L2) stages. These signals pick off the output of each differential coil driver channel, and convert to a single ended, high-passed monitor signal, with a calibration of Coil Output Noise [V_out/rtHz] = Noise Monitor Signal [ct/rtHz] * ADC Gain [V/ct] * Monitor Board Gain [diff. V_out/ sing. V_mon] where, since the high pass filter is flat by 10 Hz, we've assumed the Monitor Board is only a scale factor. Those gains are ADC Gain = 40 / 2^16 [V/ct] Monitor Board Gain = 392 [Single-ended Volts Out / Differential Volts In] According to the design studies [UIM = T0900233; PUM = T0900277], the output noise of the coil driver should be around, (Equivalent Current Noise) * (Out Resistors + Coil Impedance) = (Output Voltage Noise) (across the coil [A/rtHz]) ( [V/A] ) ( [V/rtHz] (@ 10 Hz) ) UIM: 2e-12 * 7.84e3 = 1.5e-8 PUM: 2.3e-12 * 4.42e3 = 1.0e-8 in the lowest noise modes. Note that this is what Ron Cutler calls the "component noise," which we traditionally call the "coil driver noise," or "output referred noise" the self-noise of the coil-driver due to the resistors, op-amps, etc. on the board. What he calls the "input noise specification" is the DAC noise, which is claimed to be 100 [nV/rtHz]. We see from the results attached, the results are more like 100 nV/rtHz. However, this was measured in the "acquire" modes of each driver, so we expect the noise to be basically the same as the noise input to the driver, i.e. the DAC noise, which we indeed expect to be about 100 nV/rtHz.
J. Kissel, P. Fritschel We've since measured the noise in the lowest noise modes, UIM: with all low-pass (LP) filters ON (i.e. setting the UIM BIO State Request to 4.0) PUM: with acquire (Acq) bit OFF and and low-pass (LP) ON (i.e. setting the PUM BIO State Request to 3.0) (with both COIL/TEST Enable bits set to 1.0) and the results are more like what's expected from the design studies (Measured Output Referred Noise) ( Lowest Noise Mode ) ( [V_out/rtHz] @ 10 Hz ) UIM: ~1.5e-8 PUM: ~1.5e-8 Unlike the earlier measured noise, the input DAC noise is filtered down by some factors, so the "component noise," the self-noise of the resistors, op-amps, etc. is "exposed." - For the UIM, the input/DAC noise is squashed by 3 10Hz low pass filters, so the dominant noise is the coil-driver, component self noise at all frequencies (above 10 Hz). One can just barely see a little bump creeping in around 300 Hz from the DAC noise, which is from the [z:p]=[60:325] frequency response inherent to the output stage. - For the PUM, the DAC noise is only filtered out in the region around 10-20 Hz (in the "tough" region where the SUS noise is potentially dominant in the DARM spectra), but otherwise rolls back up according to the [z:p] = [13:130] frequency response inherent to the output stage (with the Acq bit OFF), so at high frequency the output noise re-asymptotes to 100 [nV/rtHz]. A couple of other things to notice when comparing the above data with this data: - In the UIM driver, whose output noise is dominated by DAC noise in Acq mode, and Component Noise in Low Noise mode, one can clearly see 60Hz lines in the Component Noise. - The spikes in the PUM output noise have shifted in frequency, and are not 60 Hz lines... not sure what that means or why.
This data can be found committed to the SusSVN repository here: /ligo/svncommon/SusSVN/sus/trunk/QUAD/H2/ETMY/Common/Data/ 2012-06-12_H2SUSETMY_L1L2_NoiseMon.pdf [first attachment] 2012-06-12_H2SUSETMY_L1L2_NoiseMon.xml [first measurement] 2012-06-12_H2SUSETMY_L1L2_NoiseMon_LowestNoiseModes.pdf [second attachment] 2012-06-12_H2SUSETMY_L1L2_NoiseMon_LowestNoiseModes.xml [second measurement] where the "*LowestNoiseModes.xml" has the first measurement as references.
J. Kissel Another measurement for these two driver to facilitate on-going electronics studies: leaving both drivers in low noise mode (UIM: LP1, LP2, LP3 all ON; PUM: Acq OFF, LP ON), but switching between the COIL In (connected to the AI/DAC) and TEST In (assumed to be an open DB9 connector). Attached are the results. You'll notice that there are is no change in the noise floor between the two states on the UIM driver, but for the PUM the four channels get totally different noise (from the COIL In state, and from each other). What did we expect? It's a long story (eventually, the story will be told in L1200193), but in short: - Each coil driver board (yes, all of them) has a equi-potential voltage reference plane to which on-board components are grounded (called "0V" on the schematic). - The given coil driver chassis forms a second equi-potential plane (which we'll call "ground" for now) - The "0V" reference plane is connected internally to pin 5 of both the "COIL In" and "TEST In" DB9 connections (called "DEMANDS" and "Front Panel Test Inputs" on the schematics), as well as to several of the output pins. - External to the chassis, the system wiring diagrams (yes, all of them) show that all of these pins are shown to be "NC" or "not connected" to cables going to and from these chassis. - It's unclear *how* they are not connected: is the pin is shorted to the chassis, to the backshell, or maybe the cable doesn't have a pin in it's female socket ... could be any number of things. - In the as-measured configuration of the electronics, the "COIL In" DB9 is connected to the full signal chain as shown in the system wiring diagram (D1002741); the "TEST In" DB9 is open to air (and not shown in D1002741). - In general, the chassis "ground" is free to swing with the surrounding environment, whose changing electric field can then interact with the reference ground "0V" on the boards, and also interact with the the components on the board. - IF and ONLY IF the differential paths are identical (which, in the real world is not possible because of component tolerances), this changing field would be common-mode to the two positive and negative paths, and cancel. - However, IF the paths are not perfectly the same, the common-mode surrounding field will couple differentially to the components and cause noise for various reasons. The HOPE was that there was no such coupling between the "0V" reference plane and the "ground" plane of the chassis going on, the switch between "COIL In" and "TEST In" would merely remove the (filtered) 100 [nV/rtHz] Input DAC noise, and we could therefore measure the component, self-noise of the board at the output. For the UIM board, the noise level remained roughly the same. We expected the noise in the "COIL In" configuration to be dominated by the component noise, so if we've "turned off" the DAC noise by switching to the TEST In configuration, we indeed expect no change. GOOD! For the PUM board, the DAC noise was not filtered as much as the UIM board in the lowest noise mode and is therefore dominant, so we expected to see the noise on all channels to simultaneously drop to the component, self-noise noise level when switching to "TEST In." Instead we see what's shown -- each channels noise is differently elevated, and its frequency response has changed. I don't want to make claims just yet of exactly what's happening (which is why I said "for various reasons), but the proposal L1200193 will suggest what to do next. Weeeeeee-ew. How do you say ... l'enquête se poursuit!
This appears to be the first pumpdown of BSC10 in 2000.
[Jeff B, Travis S, Andres R, Gerardo2 M] Today we moved the HLTS PR3 from the test stand in the Staging Building to the LVEA. This is the first of the Hanford Triple suspensions to be moved to the LVEA. We need to make some minor adjustments to our lifting gear for future HxTS moves, but in general, things went smoothly and with no serious problems encountered. Gross weight of PR3, without vibration absorbers, is 210lbs.
PSL had a need to access a particular feedthru for their In-Vacuum Cable runs. Although the LHAM2 layout managed to reflect this it did not get propagated to LHO documents. So we had to swap the feedthrus on D2 & D5. The layout is D1002873. Version v6 shows how we initially installed them. In v7 there is a text file to the effect of the change but the layout itself is not yet updated. There are two open ports now on D5 as these take 5-way Coax. These Feedthrus are in C&B now and I hope we can get these on before the next pump down.
Tomorrow Barker & Columbia will take H2 down for timing work
6 days of turbo pumping, pressure @ 2x10-6 torr, scan attached.
Work permits pulled for In-Chamber Cleaning.
First vacuum and wipe-down are complete. Second vacuum is likely to be completed by the end of the day. We expect to complete work in the dome by lunch tomorrow. We anticipate FTIR results for the permanent flooring either today or tomorrow. If all goes well, we may be out of BSC1 (including dome and door replacement) by tomorrow afternoon.
For the last several weeks we have been testing a rss feed of the alog. It is now being moved to be a publicly exposed and advertised feature. The feed is located at rss-feed.php. If you are using a RSS aware browser you should be able to find the feed in whatever method your browser exports feeds. For example in Firefox the 'Subscribe to this page...' entry of the bookmark menu becomes available. This update is scheduled to be rolled out to the LLO logbook tonight.
END Y after 6 days of pumping. No change in trend - suggests this is not an air leak.
[Stuart A, Mark B, Jeff B, Vern S] Whilst last visiting LHO I was able to quickly make some open-light and one dimensional responsivity measurements using three dirty AOSEMs and a test-jig kindly loaned from Mark. The test-jig has previously been used for characterising BOSEMs, and so had to be reconfigured to accommodate the smaller AOSEM coilformer. More importantly, rather than using the rectangular flag employed for the BOSEM, a ~1" long x ~2 mm diameter cylindrical flag was provided by Jeff B. A UK production Satellite Box (D0901284) was connected up to the AOSEM under test using a dirty in-vacuum quadrapuss harness (D1000234). The Satellite Box was provided with it's required supply lines via a Satellite Box Testing Board (courtesy of Filiberto). For electronics set-up please see image 504 below. A DVM was used to read-out the amplified voltage signal via the diagnostics port (J4) on the Satellite Box (Pins 9 and 28). Note that, the production Satellite Boxes have a input gain of 242k V/A or 0.242 µA/V (double-ended). Image 506 (below) shows the opto-mechanical set-up for the reconfigured test-jig, including the translation stages and flag assembly. For these tests, only the responsivity is sought, and therefore a one-dimensional characterisation along the sensitive axis is adequate. When connected up to the Satellite Box, each of the AOSEMs had the following open-light differential voltage measurements:- - Unit #1, open-light = 14.75 V (i.e. an open-light photo-current of ~61 µA). Corresponds to ~24k counts - Unit #2, open-light = 10.14 V (i.e. an open-light photo-current of ~42 µA). Corresponds to ~17k counts - Unit #3, open-light = 12.19 V (i.e. an open-light photo-current of ~50 µA). Corresponds to ~20k counts Over a ~0.7 mm operating range, these AOSEMs were found to have the following responsivity (see plot below):- - Unit #1, responsivity = 18784 V/m (i.e. 78 mA/m). - Unit #2, responsivity = 13028 V/m (i.e. 54 mA/m). - Unit #3, responsivity = 15721 V/m (i.e. 65 mA/m). These responsivity results can be compared with the default value we have previously assumed of ~80 mA/m (see LLO aLog entry 2715). To summarise, these measurements can be used to validate our assumption of using the AOSEM calibration factor of, 1/(80e-3 [A/m] * 240e3 [V/A] * (2^16)/40 [cts/V]) = 3.2e-8 [ct/m], is consistent for units with open-light counts above Jeff K's goal of 25k.
Please find the responsivity plot showing all three units tested below.
Mark Barton and Szymon Steplewski The responsivities of the three units test by Stuart have a scatter of about 18% (stdev//mean). However this scatter is dominated by a term proportional to the open light voltage (or counts). If you scale the responsivity to an effective OL count of 30000, as is routinely set in the OSEMINF block, the scatter is much reduced (to 0.6%). Therefore the number that it is useful to quote is the average of the scaled responsivities. See attached spreadsheet. However although this data set is useful for making the above point, it was still taken with the wrong flag (2.5 mm instead of 2 mm) and so should not be considered final.
I have reorganized and added medm snapshot screens to the CDS web page (LIGO.ORG authenticated):
https://lhocds.ligo-wa.caltech.edu/screens/
Vacuum and FMCS detailed medm screens have been moved to their own web pages, the overview screens are shown on the main page
A H1 section has been added, it contains the H1 CDS OVERVIEW MEDM
The H2 IOP SUS/SEI watchdogs screen has been added to the H2 section
Yesterday Keita and I found that the output of the ALS PLL Phase-Frequency Discriminator unit was noisy and oscillating between its voltage rails. We traced the problem back to a very noisy output signal from the frequency divider which provides the LO to the P-F Discriminator board. Going up the chain, we found that the frequency divider unit was getting 0dBm instead of the nominal 13 dBm from the VCO unit. Apparently the VCO unit is not working properly. We removed it from the rack and took it to the corner station for inspection. We are going to check it inside to find the cause of the mismatched power levels.
Paul Schwinberg checked the board in the EE shop and found that the RF levels were actually correct. It's not clear why the board was malfunctioning when Keita and I measured the levels on Friday. We took the board to the end station and reinstalled it back into the rack. This time the output level was okay: about +13 dBm.
The problem of HAM front end startup corrupting the H1PSL data was tracked down to a switch configuration and was corrected.
The following front ends and models were created by porting the LLO running models to H1.
h1seih23 | h1iopseih23 | h1hpiham2 | h1hpiham3 | h1isiham2 | h1isiham3 |
h1sush2a | h1iopsush2a | h1susmc1 | h1susmc3 | h1susprm | h1suspr3 |
h1sush2b | h1iopsush2b | h1susim | |||
h1sush34 | h1iopsush34 | h1susmc2 | h1suspr2 | h1sussr2 | |
h1susauxh34 | h1iopsusauxh34 | h1susauxh34 |
All the models started with no problems except for h1susim (which has an undefined symbol).
All systems were added to H1 DAQ using the INI files generated from the models. The H1 frame size roughly tripled in size from 1MBps to 3MBps.
Laser current set to 1.5 amps.
IR output 1.125W (after the laser head), 50.0mW (after Faraday, we're using wave plate to intentionally dump some power), 10mW after PBS (another attenuation, we can decrease this, or increase this up to 50mW)
With 10mW going to the PLL diode, we have about -3dBm beat note.
green output 22.9mW (right after the laser head), 17.5mW (after the first Faraday), 13.85 (after the second Faraday), 12mW (just before the bottom periscope mirror)
Retroreflection (measured after 10:90 splitter) 0.73mW, this means that the retroreflection is 7.3mW.
Apparent table efficiency is 7.3/12 = 61%.
Aluminum mirror reflectivity is probably not that good (95%-ish if they're good) (turns out that they're silver, not aluminum, coated, thanks Matt for pointing it out, and this means that the reflectivity of these is 98% or so rather than 95), and there are four such mirrors (TMS telescope mirrors), double path, meaning there are 8 reflections. This should amount to 0.98^8 = 85%-ish.
There is a splitter for QPD (5%? I don't remember), again double path, so if it's 5% splitter this removes 10%.
0.85*0.9 = 77%-ish.
References: D1201457, E1000870, E1000669, E1000652, E1000425, C1103229
On a closer look, there is two E1000669 "IR HR, Green HT" mirrors (M4 and M7) in the green TMS path. Transmission of these is 98.6% according to the vendor measurement.
5% transmission is really 5.0% measured (E1000870), high reflectors are measured to be really high reflective (E1000652, E1000425).
Also, though there's no reflectivity measurement for TMS telescope silver mirrors, various vendos offer "protected silver" coating reflectivity data in tiny tiny plots, and Thorlabs data looks as if the reflectivity is 97% rather than 98 for 532nm, Newport quite similar, CVI looking lower. None of these three vendors are used for TMSY, we used two Edmund optics (the reflectivity data I wasn't able to find) and two custom optics coated by a coating vendor in California, but it sounds safe to assume that the reflectivity is 0.97 or lower per silver mirror.
ETMY uses ETM04 (C1103229) which has a ITM HR with a transmission of 1% for 532nm.
Including 98.6% transmission twice, 95% reflection once and 97% reflection four times, we have:
0.986^2 * 0.95 * 0.97^4*0.99 = 0.82 single path, or
(0.986^2 * 0.95 * 0.97^4)^2 = 0.67 double path for TMS itself.
Including 99% ETM, we have 0.66 total.
Double path was measured to be 61%, so there's still 5% discrepancy but this might easily be the silver mirror reflectivity.
If we put everything into the silver mirror, its reflectivity should be 96% per mirror.
Helium spraying this afternoon has been inconclusive - intermittent response has been sufficient to keep us interested but we were not able to pinpoint any source. Maybe leakage through the annulus and orings.
We decided to try starting up the BSC10 RGA.
After finding and resurrecting the computer and controller we found that the controller would not power up. Retreived another unit from YMID, installed it, and found filament emission error on startup.
Documentation shows the last operation of this RGA was in 2008.
We will continue on Monday. I am starting to wonder if this can just be a very saturated system as we were vented for 3 months while the cartridge install was performed. For this period the iLIGO stack in BSC10 was exposed to the purge air.
Kyle,Gerardo,John