[Daniel, Alberto,Bram] 17 August 2012
We found a 221 kHz resonance in the laser PZT. We modified the PZT notch filter in the TTSFF, by changing C47 from 910 pf to a 1000 pf and a 68 pf parallel to each other. With the variable capacitor C46 we managed to set the notch frequency to 219 kHz. Although we should see a -23dB depth, we only measured -10dB. In the end this seemed to be ok.
Attached are plots of dust counts > .5 microns in particles per cubic foot.
I spent several hours in the optics lab to diagnose the FSS trouble that we've been experiencing lately. I've found two failure modes though there may be more. One was fixed and the other was not.
1) EO monitor slowly creeps up due to 14.4 kHz oscillation building up.
Fixed by rebalancing the PZT-EOM crossover. (Fast gain was 592 or something like that in the morning, now it is 815).
In this mode, FSS still appears to be locked and the REFCAV transmission looks OK, but if you lock the arm your arm transmission slowly degrades, and after a while it becomes impossible to lock the arm.
When you look at the EO RMS monitor and the PZT fast monitor on the oscilloscope, EO monitor creeps up very slowly though you wouldn't notice anything in the PZT, so you would think that this is some really high frequency stuff.
However, it turns out that this is almost entirely due to 14.4kHz oscillation slowly building up. PZT signal has lower frequency crap so 14.4kHz is not that apparent on the oscillo.
Attached shows the spectrum of the common path test point in the FSS box in bad and normal state.
2) Fast glitch in PZT.
Not fixed.
This is distinctively different from the first one in that there is a big fast glitch observed in the PZT signal first. ("Fast" just means that it looks instantaneous on the oscilloscope that is set to its slowest setting, so it could be 100Hz or 100kHz.)
Sometimes the PZT can take it and the signal goes back to normal after a while. Sometimes the PZT cannot, and the refcav loses lock. It looks like the refcav can relock itself in this mode even if the lock is lost.
EOM monitor doesn't show anything until refcav loses lock.
Even though the glitch itself seems to be fast, what seems like a transient response of the servo is very slow (slower than 1Hz).
I wanted to see the glitch on the analyzer in real time, but somehow it happens only when I'm not looking at the screen. We need a good young scientist who can sit in front of the analyzer without blinking for an hour.
All awtpman processes were restarted with the latest code.
New sus models were installed for MC1, MC3, PRM and PR3 on h1sush2a.
The crash of h1susim model was tracked to a missing ipcRfm=1 flag on h1iopsush2b. In the process we imported local modified files from LLO for:
and I imported l1susim.mdl to make the h1susim.mdl but reverted the ADC channel changes made on the l1 model.
I changed H1's SITEMAP.adl to add a second SUS pull down for the IM medm screens (copied the links from LLO).
For anyone new to the IM optics naming, here is a conversion table from old to new names
SM1 | IM1 |
PMMT1 | IM2 |
PMMT2 | IM3 |
SM2 | IM4 |
ISI models for HAM2 and HAM3 were changed to read out IPC error rates into EPICS channels. We are seeing errors on watchdog IPC channels but not on OPLEV QUAD channels which is confusing. This investigation will continue tomorrow.
Following the thunderstorm, all LVEA front ends had timing errors and h2pemeyaux was frozen. I rebuillt all the cornerstation models against RCG2.5.1 and tested that the IOP watchdog still worked between h2susb478 (ITMY), h2susb78 (FMY) and h2seib8. Then Vincent made his model changes which convert EPICS comms to Dolphin IPC and verfied that RCG2.5.1 has fixed the Dolphin error he saw last week with RCG2.5.
h2pemeyaux required a power cycle to bring it back.
All H2 awgtpman processes were upgraded to the latest version.
The new ring heater code on h2tcsetmy upgrade was deferred until tomorrow to not impact on OAT work.
WHAM3 MC2 BandK in chamber LIGO-T1200403-v1
https://dcc.ligo.org/cgi-bin/private/DocDB/ShowDocument?docid=95644 Draft
This afternoon we ran the ring heater on ETMY for ~3.5 h, taking cavity scans to attempt to quantify the change in modal spacing with heating.
There's a clear change in the behavior in the 55-60 kHz region (associated with the modulation sidebands), but getting a clear signal for a higher-order cavity mode has been difficult. I also don't understand the downward slope of the phase response curve. I'm hoping to make better measurements tomorrow with a cold cavity to get consistent, clear numbers for the cavity mode frequencies, then try this measurement again.
The adoption of Phase - Phase at 30 kHz for the y-axis is purely to put the traces closer together visually for side-by-side comparisons of the sidebands. The "hot" trace starts at 166.7417, the "cold" trace starts at -162.2308.
I compared one of this afternoon's heated cavity scans with a cold cavity scan from last week. The nominal frequency of the TEM10 mode is shown (around 66kHz) [higher order frequency spacing = 28.5kHz, FSR = 37.5kHz, sum = 66kHz). There's clearly a shift in the TEM10 mode of a few hundred Hz.
Kingsoft water delivery Praxair delivery at ~10:40 Contractors on-site Jim B. to End-Y station to reboot PEM I/O chassis Michael R. to outbuildings to change signs for laser safety work just north of HAM4 by Eric A. Douglass using leak detector in OSB Optics Lab SUS work in and around HAM3
DaveB, JeffG, HugoP,
Added EPICS output channels to monitor errors on IPC receiver inputs (all from SUS) of HAM2 and HAM3 models.
We're going to take a few quick TFs of MC2 to check for mechanical interferences within the suspension since it has been installed. Next up, we'll set the B&K Hammer/Laser Vibrometer equipment up on MC2 for measurements.
We have also been cleaning up grounding and cabling issues inside the chamber. This is still ongoing and will migrate to PR2 shortly.
During iLIGO, there were 3-axis accelerometers that were mounted on the tabletops of optics tables. This was done by bolting three accelerometers to the sides of a aluminum cube that was then bolted down to a aluminum plate, which was bolted to the table. This mounting scheme, however, introduced a ~900Hz signal, associated with the resonance of the cube and the plate, into the accelerometer channels. We investigated new mounting schemes to use during aLIGO, and compared them.
For all the tests, we used as our reference an accelerometer that was attached to the table surface with a thin layer epoxy. The hole at the bottom of the accelerometer normally used for bolting it to cubes was sealed with a set screw to avoid having epoxy seep between the threads. The epoxy was Devcon 5-minute epoxy, which was applied to the bottom of the accelerometer. Excess epoxy was scraped off using the flat side of the mixing stick, to have the layer be as thin as we could make it. The accelerometer was then placed on the table, in an area where it was not over any of the holes for bolts, and the epoxy was allowed to cure for 5 minutes before the cable was attached to it. The thickness of such a layer of epoxy is no more than 0.3mm.
---------------------
SUCCESSFUL MOUNTINGS:
Items Used:
- Wilcoxon accelerometer, model 731-207
- Wilcoxon 1in. triaxial aluminum mounting cube, model TC1
- 520 ft Thermax RGS-316 cable
Z-axis mounting:
We tried adding a layer of Glad polyethylene wrap between the accelerometer and the table. A thin layer of epoxy was first applied to the accelerometer, and a piece of wrap was pulled taut against the bottom of the accelerometer. Then another thin layer of epoxy was applied to the wrap, and then the accelerometer was pressed to the table. The purpose of adding the layer of polyethylene wrap is to isolate the accelerometer from the object it's mounted to, since a thin layer of epoxy may actually allow parts of the metal exterior of the accelerometer to come into contact with the table. The combination of the epoxy and polyethylene wrap added 0.3mm to the heght of the accelerometer (the wrap itself is ~0.5 mils thick). We found that adding this layer does not make the signal deviate too much from that of the reference (see attachment 1).
Triple-axis mounting:
We tried attaching an accelerometer with a layer of polyethylene wrap on the bottom (as above) to an aluminum cube using epoxy, and attaching that cube to the table using epoxy. This also does not make the accelerometer signal deviate significantly from that of the reference (see attachment 2). For actual installation of triple-axis accelerometers, we recommend first attaching three accelerometers to a metal cube using the epoxy-polyethylene-epoxy method described above, outside the LVEA. Once the epoxy has cured and the triple-axis setup is stable, one only needs to use one batch of epoxy near the table to mount the cube. We tested a similar setup but with a (non-conductive) acrylic cube instead, but found that the aluminum cubes give better performance (see attachment 3).
Temporary mounting:
For temporary installations, we tested 1in wide double-sided clear clean room tape. Previously, in iLIGO, double-sided Scotch tape was used, but for aLIGO we wish to use particle-free adhesives such as clean room tape. We found that this mounting allowed the accelerometer to respond to vibrations in a similar way to the epoxied reference (see attachment 4). There were two kinds of clean room tape we tried, one that had a peel-away backing, and one that did not. Since the backing is a hassle to peel off, the tape without the backing is preferred.
Extra long cables:
For cases where extra long cables need to be used for an accelerometer, we verified that the length of the cable does not affect the accelerometer readings. We tested a 520 ft Thermax RGS-316 cable with an accelerometer that was epoxied to the table, next to the reference, and found no effects from using a longer cable (see attachment 5).
---------------------
SUB-OPTIMAL MOUNTINGS:
The first mounting scheme we tested was double-sided tape, used in temporary setups during iLIGO. This kind of mounting is useful in temporary installations, not specific to optics tables. The tape used was Scotch Permanent Double Sided Tape, 0.5in wide. Two parallel, non-overlapping strips were placed across the bottom of the accelerometer, which is 1in in diameter, and the accelerometer was pressed to the table surface, again away from any holes. It was placed adjacent to the reference to avoid variations due to positioning on the table. The tape was also found to be non-conductive, so it isolates the accelerometer from the object it's mounted to. We found that when taped to the table, the accelerometer behaves very similarly to one that is epoxied to the table (see attachment 6). However due to cleanliness concerns we opted to use clean room tape for future installations.
Next we compared the iLIGO setup to the epoxied reference. We again found the 900Hz resonance of the cube and plate entering the accelerometer channel (see attachment 6).
Other methods we tried were:
Accelerometer bolted to aluminum cube bolted to brown plastic plate (one of the iLIGO setups)
Accelerometer resting on the table (no mount)
Accelerometer bolted to cube taped to table
Accelerometer bolted to cube epoxied to table
Accelerometer taped to cube epoxied to table
Accelerometer epoxied to cube dog clamped to table
+ polyethylene wrap between cube and table
+ foam stuffed in dog clamp slot
+ foam between dog clamp and cube
+ different position on the table
+ cube replacement
+ tightening of the clamp
+ maximum tightening of the clamp
+ foil between clamp and cube
+ foil between cube and table
+ foil above and below cube
Accelerometer with a thin layer of epoxy + polyethylene wrap + a thick layer (0.7-1.0mm) of epoxy to the table
Accelerometer epoxied to cube bolted to plate
+ foil between cube and plate
+ foil between plate and table
+ foil above and below plate
Maggie Tse, Robert Schofield
The H1 SUS PR2 "safe" burt file was updated and committed to the "cds_user_apps" SVN repository locally in: '/opt/rtcds/userapps/release/sus/h1/burtfiles/h1suspr2_safe.snap' This is the file that is SVN version-controlled in the above directory. A soft-link pointing to this particular file was created in the directory: '/opt/rtcds/lho/h1/target/h1suspr2/h1suspr2epics/burt/' with the name "safe.snap" for use by the startup scripts when re-booting the "h1suspr2" Simulink user model.
[Jax, Elli, Alberto, Keita, Daniel, Bram]
After relocking the RefCav we started locking the Arm and setting alignments. Jax and Elli are running the mode-scans.
The ring heater at ETMY has been turned on at 19:27:25 UTC, 12:27:25 Local time. 630mA of current is requested in both segments. We will run the ring heater continuously for the next 3 hours.
HAM-ISI Unit #7 - Assembly Validation Testing was validated today. We can now proceed to storage of the unit for future insertion in HAM4 Chamber.
Reports regading the Assembly validation of previous units at LHO are available in the DCC:
HAM-ISI Unit #1 - Assembly Validation
HAM-ISI Unit #2 - Assembly Validation
HAM-ISI Unit #3 - Assembly Validation
HAM-ISI Unit #4 - Assembly Validation
HAM-ISI Unit #5 - Assembly Validation
HAM-ISI Unit #6 - Assembly Validation
Reports regading the Chamber Side testing of other units at LHO are available in the DCC:
HAM2 (HAM-ISI Unit #4) - Chamber Side Testing
HAM3 (HAM-ISI Unit #5) - Chamber Side testing
Note: Earlier this month we added an Initial In-Chamber Testing section to the HAM3-ISI Phase II - Integration Process testing report. This report has now two sections:
This report will be completed with the future tests performed on HAM3-ISI unitl the begining of Phase III - Control and Commissionning.
Kate and I are checking grounding on MC2. This will require disconnecting the exterior MC2 SUS cables from the chamber feedthru briefly.
The Simulink models for H1 MC1, MC3, PR3, and PRM were compiled, installed, and begun on the 'h1sush2a' FrontEnd this morning during the CDS Tuesday Maintenance period. The H1 DAQ was also re-booted to begin recording the channels for these models. All re-boots were clean with no apparent issues to note.
PR2 was installed in HAM3 today, and traveled well on the Genie and Arm. It's sitting against it's cookie cutter, and dogged down overnight. The crew was Kurt Buckland and Scott Shankle, as well as Deepak and I