Had found stuck open previously and had valved-out -> Now all (5) compressors are valved-in
Used for fall protection whilst atop MC tube (Connecting HV cables to IP1 and IP2)
Replaced bad solenoid on Drying tower, system is now back up and running
See the attached photo showing how I've schemed Cable Stain Relief on this 12" 12 plug Feed Thru. There are holes on the perimeter of the Shroud allowing an all thread to pass between cables. The red cable conduit protects the cable from the threads. All cabling should get strain relief and there are a lot of cables on D6(SW Corner) none of which have any relief yet. There are still a lot of cables yet to be plugged into D3(PRMs.) If anyone objects to this scheme or thinks installing these should wait until... please let me know.
Added reworked one-stop card to I/O chassis for h1susauxb123. Powered up chassis, then powered up h1susauxb123 computer to verify that all cards could be seen. Note that no AA chassis are attached to this I/O chassis yet.
Added a reworked one-stop card to the h1susauxh23 I/O Chassis, then powered up the chassis. After about 15 seconds, the chassis died with what appears to be a bad power supply. This was suspected before, but it hasn't been replaced yet.
Added a reworked one-stop card to the h1seib2 chassis, ran timing fiber from the ISC fanout to the I/O chassis. Did not power up, as it appears there is a binary I/O card missing from the chassis.
The channels for the IPS (Inductive Position Sensors) were connected in the model of H1:HAM1-HEPI: h1hpiham1.mdl
Model was restarted at 11.02am. Readouts make sense. The new model is now commited to the SVN.
[Max and Kiwamu]
Max noticed that the light coming out from the ALS-PSL fiber became at a micro watts level some hours after we tuned the fiber alignment [1] in the past Tuesday. Today we stepped in the PSL room again to investigate the causes and realign the optics. However it turned out that the coupled power was back at the same level of 1.7 mW as we had before. We don't have any idea of what happened as the slow channel for the fiber power monitor is not recorded yet. We need the channel to be recoreded to investigate this issue further. All we did today was addition of two more dog clamps for the base plate of the fiber coupler to make it stiffer and realignment of the steering mirrors.
Note :
There is a BNC output, labeled as "external power", on the front panel of the fiber distribution box in ISC R4. This gave us a voltage of 0.12 V when the fiber output light was at 1.7 mW.
[1] LHO alog 5377 "Realignment of the ALS-PSL fiber launcher setup"
Installed reworked one-stop card in I/O Chassis for x1fe3, started computer, and verified that the cards in the I/O chassis were visible and models were running.
Since we are having reliability issues with h1fw0, I have moved the default nds server configuration to use h1nds1 instead of h1nds0. This will be effective with all new shells created after 10:18 AM local time.
[Cheryl, Giacomo]
Last Friday (February 1st), just before I left, Cheryl and I repeated the measurements of the IMC cavity pole using the same setup I had prepared the previous week.
We took the measurement twice, using two slight variations:
- measure the transfer function TF1 between the the ISS PD and the PD on the IOT table, in reflection of the unlocked and misaligned IMC. Then measure the transfer funtion TF2 between the ISS PD and the same PD on the IOT table, but moved in the transmitted path of the locked IMC. The ratio TF2/TF1 should give the IMC TF.
- measure the transfer function TF1 between output of the SR785 and the PD on the IOT table, in reflection of the unlocked and misaligned IMC. Then measure the transfer funtion TF2 between the SR785 and the same PD on the IOT table, but moved in the transmitted path of the locked IMC. TF2/TF1 should give the IMC TF.
The good news is that the two measurements are in very good agreement with each other (as expected and hoped); the bad one is that they are not well fitted by the expected TF.
Attachments:
1) the magnitude and phase of the IMC TF as measured using the two techniques, and compared with the expected value
2) a fit to the magnitude (in dB) of the TF, between 2.5 and 70 kHz (for comparison with LLO measurement that can be found here, and I believe was fit in this range)
It might be worth repeating the measurement with a different PD and maybe with an instrument that can go higer in frequency.
This report is the work that was preformed yesterday at End Y by the Apollo crew: The dome was removed from BSC 10, o-ring protecters installed on the BSC and dome placed on the piers in preperation for cleaning. We removed various pieces and parts from the termination slab (north side) to be used as a semi final resting place for the ISI from BSC 10 to be removed today.
[Hugo, Rodica, Paul]
Today we were finding it impossible to lock the IMC again. When we looked at the SUS-MC2-M3_LOCK_L_OUT_DQ channel, the signal appeared to be always railing (on both sides). We have seen this before at times, due to very noisy seismic states (see e.g. entry 5145). However, even with what we expected to be a quiet siesmic and ISI state, we still found this signal railing at ±40,000 counts, making it impossible to lock using the length path. In the end, Hugo realised that when the model was recently updated, the limit on the MC2 M3 lock filters had reverted to its initial old value of 40k counts. Apparently at some point this was increased to 400k counts, but not saved in a safe.snap file. Hugo increased the limit back to this value and the mode cleaner began locking again.
We should update the safe.snap file so that any further reboots revert to the 400k counts limit.
You can make a new safe back up easily, by turning off all output (damping loops off, offset off, and master switch off), then running /opt/rtcds/userapps/release/cds/common/scripts/makeSafeBackup The usage is controls@opsws2:~ 0$ cd /opt/rtcds/userapps/release/cds/common/scripts controls@opsws2:scripts 0$ controls@opsws2:scripts 0$ ./makeSafeBackup Usage: First argument is subsystem name (i.e. sus, isi, hpi, isc, etc) Second argument is model name (without .mdl) (i.e. l1suspr3) controls@opsws2:scripts 0$ ./makeSafeBackup sus h1susmc2 controls@opsws2:scripts 0$ this updates the safe backup here, /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susmc2_safe.snap which you should then commit to the SVN with appropriate comments on what has changed. Also, I believe Mark has a matlab function that sets up the suspension in the right setting for the safe capture, and does the capture, if you prefer that.
Thanks Jeff, I have now done that (I hope succesfullly). I left all the gains, limits, etc. in the useful condition for locking, but turned off all the damping filters, lock filters, alignment offsets and master switch, and then committed the new safe.snap files to the svn.
Transfer function measurements are running overnight on HAM3-ISI.
Active control will be turned back on once it is done.
Same comments apply to HAM2-ISI
Measurements are done. Level 2 Isolation loops are back ON, on both HAM2 and HAM3 ISIs.
Turns out we left cables attached to the TFIN and TFA/B inputs on the PMC field box in the racks, with the MEDM switch enabling the TF path. Removing the cables got rid of the noise, and I disabled the path. There is still some 60 Hz noise but it is nothing like it was before.
This is something we've forgotten since the science run ended...always check the cables when noise hunting!!
Checked the PSL PDA spectrum and ODC lock status again this morning and all looks fine. Thanks for following this up Michael.
Excess power diagram of the past day or so. It's very clear that the high frequency noise diminishes and disappears in the recolored channel right around the time that the problem was corrected.
I restarted and burtrestored the dust monitor and weather station IOCs on h0epics2 that lost communication after the work on the network.
