Gerardo, Betsy
After having one failed ear bond early in the week on PUM ITM03, Gerardo sucessfully bonded both ears.
We also loaded PUM ETM06 (destimed for ITMx PUM replacement soon) onto the table and glued it's flag mounts and first of 2 prisms. We'll get to the 2nd prism tomorrow hopefully.
While in the chamber, we also connected the 5 SUS and 1 ring heater cables to the feedthru and confirmed signal throughput on the 5 sus. We pulled the C3 covers from both of the ETMy and TMSy suspensions before installing the corner cube.
Jason and Doug should have a clear shot of the corner cube (and probably the edges of the optic) through the ACB from the spool. We await X,Y,Z measurements.
JimW & MitchellR
We payloaded the ISI Keel with the 600 lbs per D1002266-v1 (v1 really?); each 150lb stack sitting on 8 in2 of 1/4" thick viton. See photo.
With that completed we unlocked HEPI and floated the platform (~15000lbs) on the HEPI DSCW Springs. Next we shot level/elevation of the Optical Table. See attachment for log notes.
The table actually started out pretty good, I thought we had disturbed it more during float. The level had about 0.5mm runout and the elevationi was low 1.3 mm--all within spec. We adjusted anyway to be 0.3mm runout and 0.2mm high.
Mitchell then joined Jim in chamber and moved the ACB deep into the Spool. I then helped Betsy put the lift table into the chamber. Jim & Mitchell moved the Table into the Spool and set the ACB atop the table. Betsy & Travis were working to install the retroreflector for the IAS Y shot while Jason & Doug were getting their equipment readied,
The readback channels for the corner station ring heaters seem to not have been working properly since last Friday. I've attached a graph that shows that the ring heaters seem to have turned off at 02-21-2014 22:5:32 UTC. Judging from the ALOG around that time, there were a lot of reboots going on in software, I'm not sure about hardware reboots. However, Kiwamu says that the PRC power level is looking like the ring heaters are on just based off of the amount of loss he measured. He also advised that since the system is working well, I should hold off on trying to power cycle the TCS chassis until a later time but at the first chance I get, we should try to resolve this issue. The ITMX ring heater is also displaying similar weirdness, which is expected since they share the same chassis and PLC.
Kiwamu, Sheila, Thomas This morning seemed to be a good time to investigate this issue. At first we saw that the PLC3.pro was connected to EPICS but not to the System Manager, i.e. the ADC channels were not getting from the hardware to the TwinCAT software. We tried re-running the install scripts but it did not fix the problem but it did help us figure out that there were some channels deleted recently. Daniel let us know that if there are some additions or deletions, we should re-map the configuration before recompiling. This solved the problem!
(Alexa, Jax, Stefan)
Alexa was trying to hunt down a missing gain factor for her model and instead found a busted COMM PLL board (serial number S1200564). The op-amp for the VCO compensation stage (U37) was blown. I recalled replacing the same op-amp on the DIFF PLL about a month ago, suggesting that there's something that makes this particular op-amp vulnerable. After discussing with Richard McCarthy, we opted to change resistor R96 from 0 to 2k ohms to protect the poor thing. Lab tests show that it's in good shape, and it'll be back to the ISC rack as soon as we're done with the ISC meeting.
Should this resistor change be propagated to all PLL boards?
No, we're still thinking about it. It's going in as modified and if it keeps having problems, we'll burn that bridge when we get to it.
This smells of an ISC integration issue so we don't forget...
Due to ongoing problems with h1fw1, the default NDS server has been changed to h1nds0.
I have changed the core switch configuration to no longer forward broadcasts on udp port 5355 to the FE network now that DTT has an environment variable to do this, and said environment variable has been configured. This will reduce some broadcast traffic on the FE subnet, as well as correct some other side effects that probably only I care about.
Fabrice, Jamie, Jim, Dave
I restarted all the models on h1seih23 to clear the no-DAC-output problem.
Sequence was: stop user models, restart IOP model, start user models
models are h1isiham2,3 h1hpiham2,3 h1iopseih23
Fabrice then put ISI ham 2,3,4,5,6 into a safe state, and I updated the safe.snap files in SVN and committed them.
Has the /etc/startWorld.sh script been installed on H1 front-ends? That is what is used at L1 for these restarts.
This morning when I came in I found the HAM2/3 ISIs tripped. I have tracked this down to what I believe to be a DAC communication problem in the front end.
While the models show output on their DACs, the IOP shows no corresponding DAC output on the same channels. There are no error flag whatesoever to indicate that there might be a problem. None of the watchdogs on this machine are currently tripped.
The image below show the DAC_MONITOR screens for H1IOPSEIH23, which shows zero on all outputs, and H1ISIHAM3, which shows and output of -958 counts on CH 8.
The dataviewer program has been updated for Linux and Mac OS X to correct issues with leap second handling and to allow short channel names to be selected from the menu. Current version is now dv-2.8.1
Filberto, Daniel
We moved the doubler which drives the ALS fiber distribution box from rack ISC-R1 to ISC-R4. This hopefully reduces the electronics crosstalk between this unit and the PSL VCO. We als used a differemt RF patch panel in ISC-R2. The RF power levels have been re-measured, requiring to change the attenuator at the ALS fiber distribution chassis input from 1dB to 3dB.
I just spent another hour turning on ISI ETMX. (see previous elog for ITMX.) This seems to me that most of the turn-on trouble comes from our attempt to turn on loops in an equilibrium position, and afterwards move to the target position. This move then leads to DC saturations in various sensors. Question: Why don't we put in fixed drive offsets - even after the DACkill - that allow us to make the OFF position equal to the locked position. This way the ISI never has to "move", we never have T240 saturations.
When the watchdog turns things off, they really need to be off. Last time a fiber was broken, it was because there was a bogus signal coming from the IOP process. That said, We agree that it would be really good if turning the ISI on/off didn't mess with the alignment so much. One clear action item is to trip the watchdog less often - all suggestions on this are welcome. Other Suggestions - 1) Hold most offsets with HPI - we have in mind a way to hold HPI offsets longer during watchdog trips. 2) Stop going back to the target locations for most DOFs on the ISI. One can not see how recovering the old X, Y, Z, and roll DOF (e.g. if the beam direction is along X, the rX direction seems not-very-important at the micro-radian scale). Clearly yaw is important for all optics, and pitch is important for tables with TMS. 3) get the guardian for BSC-ISI up so we can turn on ISI whilst ignoring the T240s - in the mean time, this will be put into the BSCISItool scripts available in the next few days (testing is ongoing)
>When the watchdog turns things off, they really need to be off. >Last time a fiber was broken, it was because there was a bogus signal coming from the IOP process. I don't understand. A constant value is just as "off" as the value 0. Not energy will be transferred to the payload.
I've started automation work on the HAM2/3 ISIs, started at roughly 07:00 PST this morning.
While the IMC is currently locked, this work is somewhat invasive. Both ISIs are currently tripped, for instance.
I will report when the work is done.
ITMY TF will be running overnight on opsws8. Started at around 20:45
Measurement completed and lasted ~10hours.
In prepartation for tomorrows guardian deployment on ISI HAM2/3, I checked the configurations of the filter modules in the HAM2/3 ISIs, to make sure they are configured as needed for the guardian. I found a couple of discrepencies that I've tried to sort out.
The BLEND configuration is not currently touched by the guardian code, so we're not working about their configuration for the moment.
The configuration of the DAMP filter modules seems to be as expected (FM1 loaded only with 'Damp').
The ISO modules were a different story. ISI_HAMX expects the following filter banks to be populated for the vaious isolation levels:
HAM2/3 has nothing in FM3/5/6/7. I therefore added unity gain filters into those banks, and gave them the appropriate names.
The Boost_* filters also didn't have the 5 second ramp times that we decided we needed during the HAM4 testing. I added those ramps as well.
I have saved the filter files, but I have not yet loaded them into HAM2/3. I will load them when I start my tests tomorrow morning.
There is a typo in the HIGH - HIGH uses FM 4,5,6, possibly 7, and boosts with FM8 (using the 1-10 numbering)
Mitchell and I installed the TMDs on the HAM ISI Blade Springs similar to as Hugo and I did on WHAM3. Mitchell has the serial numbers. There were also a couple feedthrus that needed to have the in-vac cable attachment screws secured. Mitchell did this.
Serial numbers for the Blade Spring Tuned Mass Dampers (D0900703) are 025, 026, 027.
In-vacuum ETMy SUS cable serial numbers:
Floor 1 of CB D1000225-S1104879 to D1000234-88"- 941
Floor 2 of CB D1000225-S1l04881 to D1000234-88" - 942
Floor 3 of CB D1000225-S1104882 to D1000234-88" - 940
FLoor 4 of CB D1000225-S1104880 to D1002522 - 924
Floor 1 of CB D1000225-S1104883 to RH cable
Floor 2 of CB D1000225-S1104878 to D1002522 - ? (ETMy L2 stage)
All are plugged into feedthrus on the F3 port of the chamber as per the WBSC10 D1200111 cable routing doc.