A new library part was made for the single suspension controller (it was originally made from the c1scx controller), using the following procedure:

1. Opened c1scx model (userapps/trunk/sus/c1/models/c1scx)
2. Cut ETMX subsystem block out of SUS subsystem
3. Pasted ETMX block into new empty library, and renamed it C1_SUS_SINGLE_CONTROL
4. Tweaked names of inputs, and generally cleaned up internals (cosmetically)
5. Saved library to: userapps/trunk/sus/c1/models/lib/sus_single_control.mdl

Once the new sus_single_control library part was made and the library was committed to the cds_user_apps repo, I replaced all sus controller subsystems with this new part, in:

• c1scx
• c1scy
• c1sus (x5 for each vertex mass)

All models were rebuild, installed, and tested, and everything seems to be working fine.

CDS changed the suffix for all aquired channel names from _DAQ to _DQ.  When we rebuilt the sus models, described in the previous log, the channel names were changed and consequently the channel files were completely rewritten.

To fix the issue, the latest archived channel file was copied back into the chans directory, and the suffixes were changed, as so:

cd /opt/rtcds/caltech/c1/chans
cp archive/C1SUS_110602_155403.ini  C1SUS.ini
sed -i 's/DAQ/DQ/g' C1SUS.ini

We then restarted the models and the framebuilder.

The full characterization of REFL11 is found in the PDF.

Resonance at 11.062MHz
Q of 15.5, transimpedance 4.1kOhm
shotnoise intercept current = 0.12mA (i.e. current noise of 6pA/rtHz)

Notch at 22.181MHz
Q of 28.0, transimpedance 23 Ohm

Notch at 55.589MHz
Q of 38.3, transimpedance 56 Ohm

The full characterization of POP55 is found in the PDF.

Resonance at 54.49MHz
Q of 2.5, transimpedance 241Ohm
shotnoise intercept current = 4.2mA (i.e. current noise of 37pA/rtHz)

Notch at 11.23MHz
Q of 2.4, transimpedance 6.2 Ohm

Notch at 110.80MHz
Q of 53.8, transimpedance 13.03 Ohm

AA filter box was removed and modified at 1Y7 today. The -5V power supply was current limited when I plugged it back in. It was removed for medical attention.

NO PEM channels available! because of this.

 (continuation of this)

Here are the transfer function and noise plots of the seismometer box, using the op amps that are actually indicated on the original plan (THS4131, AD826). I added them to the LISO op amp library (can be found in /cvs/cds/caltech/apps/linux64/liso/filter/opamp.lib)

Next step is to compare the noise graph below to the seismic noise curve of the interferometer to verify that the seismometer box configuration won't affect the curve...

I've finished tuning POY11 and it is now sitting on top of the analyzer waiting for Koji to test its noise.

 Notes:

1. R2 has been switched from a 50 -> 110 Ohm R and a (29 Ohm | 47 pF) in parallel to it. This makes the gain of the MAX4107 be ~20 above 100 MHz and ~5 around 11 MHz. The high gain at high frequency makes it stable (squashes the 200 MHz oscillation) and the low gain at low frequency is to prevent saturation (the raw 11 MHz transimpedance is too high).
2. There are two notches: 22.12 MHz and 55.3 MHz.
3. The TEST IN input has been disabled since it wasn't useful.
4. 107 Ohms inserted into between the U11 output and the TSENSE feedthrough. This is to prevent oscillations when driving the long Dsub cable. This needs to be done on all Gold Box RFPDs.
5. R4 -> 50 Ohms.
6. Had trouble tuning this to get the resonance at 11.06 MHz. This turned out to be the parallel inductance coming from L3 (previously 1.45 uH) whereas we needed a total inductance of ~1.6 uH. So I changed L3 to 33 uH to get it to be negligible compared to 1.7 uH at 11 MHz. This needs to be considered for all the 11 MHz diodes.

The full characterization of POY11 is found in the PDF.

Resonance at 11.03MHz
Q of 7.6, transimpedance 1.98kOhm
shotnoise intercept current = 0.17mA (i.e. current noise of 7pA/rtHz)

Notch at 21.99MHz
Q of 56.2, transimpedance 35.51 Ohm

Notch at 55.20MHz
Q of 48.5, transimpedance 37.5 Ohm

 D68L8EX-850Hz filter chips were removed and bypassed-shorted as Rana's entry on March 17, 2006 in old elog.

This unit is still has a short somewhere.

Today Joe and I undertook a FULL rebuild of all front end systems with the head of the 2.1 branch of the RCG.  Here is the full report of what we did:

1. checked out advLigoRTS/branches/branch-2.1, r2457 into core/branches/branch-2.1
2. linked core/release to branches/branch-2.1
3. linked in models to core/release/src/epics/simLink using Joe's new script (userapps/release/cds/c1/scripts/link_userapps)
4. remove unused/non-up-to-date models:

c1dafi.md
c1lsp.mdl
c1gpv.mdl
c1sup_vertex_plant_shmem.mdl

5. modified core/release/Makefile so that it can find models:

--- Makefile	(revision 2451)
+++ Makefile	(working copy)
@@ -346,7 +346,7 @@
 #MDL_MODELS = x1cdst1 x1isiham x1isiitmx x1iss x1lsc x1omc1 x1psl x1susetmx x1susetmy x1susitmx x1susitmy x1susquad1 x1susquad2 x1susquad3 x1susquad4 x1x12 x1x13 x1x14 x1x15 x1x16 x1x20 x1x21 x1x22 x1x23
 
 #MDL_MODELS = $(wildcard src/epics/simLink/l1*.mdl)
-MDL_MODELS = $(shell cd src/epics/simLink; ls m1*.mdl | sed 's/.mdl//')
+MDL_MODELS = $(shell cd src/epics/simLink; ls c1*.mdl | sed 's/.mdl//')
 
 World: $(MDL_MODELS)
 showWorld:

6. removed channel files for models that we know will be renumbered
   • For this rebuild, we are also building modified sus models, that are now using libraries, so the channel numbering is changing.
7. make World
   • this makes all the models
8. make installWorld
   • this installs all the models
9. Run activateDQ.py script to activate all the relevant channels
   • this script was modified to handle the new "_DQ" channels
10. make/install new awgtpman:

cd src/gds
make
cp awgtpman /opt/rtcds/caltech/c1/target/gds/bin

11. turn off all watchdogs
12. test restart one front end: c1iscex

BIG PROBLEM

The c1iscex models (c1x01 and c1scx) did not come back up.  c1x01 was running long on every cycle, until the model crashed and brought down the computer.  After many hours, and with Alex's help, we managed to track down the issue to a patch from Rolf at r2361.  The code included in that patch should have been wrapped in an "#ifndef RFM_DIRECT_READ".  This was fixed and committed to branches/branch-2.1 at r2460 and to trunk at r2461.

13. update to core/branches/branch-2.1 to r2460
14. make World && make installWorld with the new fixed code
15. restarted all computers
16. restart frame builder
17. burt restored to 8am this morning
18. turned on all watchdogs

Everything is now green, and things seem to be working.  Mode cleaner is locked.  X arm locked.

Some weeks ago, Joe, Jamie, and I reworked the ETMY controls.

Today we found that the model rebuilds and BURT restores have conspired to put the SUS damping into a bad state.

1) The FM1 files in the XXSEN modules should switch the analog shadow sensor whitening. I found today that, at least on ETMY and ETMX, they do nothing. This needs to be fixed before we can use the suspensions.

2) I found all of the 3:30 and cts2um buttons OFF AGAIN. There's something certainly wrong with the way the models are being built or BURTed. All of our suspension tuning work is being lost as a consequence. We (Joe and Jamie) need to learn to use CONLOG and check that the system is not in a nonsense state after rebuilds. Just because the monitors have lights and the MEDM values are fluctuating doesn't mean that "ITS WORKING". As a rule, when someone says "it seems to work", that basically means that they have no idea if anything is working.

3) We need a way to test that the CDS system is working...

Joe discovered today that ETMY in fact has no binary output module at all, so there is actually no digital control of the whitening filters at ETMY.

We suspect that the ETMY binary output module was maybe harvested to put in the LSC rack, but we're not sure.

We found a spare binary output adapter pcb, which I will try to assemble into a module to install in ETMY.

This does not explain what's going on with ETMX, though.  ETMX has a binary output module, that appears to be properly hooked up.  I'll try to debug what's going on there as well.

In the mean time, I've removed the ETMX binary output module to use as a reference for putting together another identical module for ETMY.

Computar  75-12.5 zooms were installed for closer look at the resonant spots.  Their alignment and focus needs more loving adjustment.

Atm 1, ITMX  (  it was 10-40 mm Tamron before )

Atm 2, ITMY  ( it was 12mm wide angle showing the towers  before )

 The current status of the dither alignment system:

- Both Xarm and Yarm alignment are working. The scripts are: scripts/autoDither/alignX(Y). Each script sets up the respective arm, turns on the dither lines and servos for 66 sec, offloads the control signals to TM alignment biases and PZT sliders in case of  Yarm, and to TM and BS alignment biases in case of Xarm, and finally turns off and clears the servo filters and turns off the dither lines.

- Jammie witnessed the final tests of both scripts - both X and Y arm power went up from 0.6-0.7 to close to 1 and the AS beam became symmetric. Also Jammie wanted me to leave the ETMY oplev in its current non-nominal but more stable state i.e. the oplev signals go to the ADC from the D010033 card not the D020432 one. The scripts can now run from the CONFIGURE medm screen.

- Both arms use signals derived from modulating ITM and ETM in pitch and yaw dofs and demodulating the arm power (TRX or TRY) and the cavity length signal (AS55I). The Yarm actuation has 8 dofs - pitch and yaw of the ITM, ETM, and two input beam PZTs so all the sensed dofs are controlled. The Xarm actuation has only 6 dofs - pitch and yaw of the ITM, ETM, and BS. The Xarm servo is set up to servo the beam position on the ETMX and the relative alignment of the cavity and the input beam. The ITMX spot position is unconstrained and provides the null test. The residual displacement on the ITMX is 0.2-0.3 mm in yaw and 0.9-1.0 mm in pitch. The I phases of the beam centering lockins, which are also the error points of corresponding DOF filters, are calibrated in mm by unbalancing the TM coils by known amount. The attached snap shot of the medm screen now has both X and Y arm calibrated beam spot positions and uncalibrated input beam indicators. The input beam angle and position signals can/should be calibrated by tapping the signals digitally and applying the proper matrix transformation - this will require the model change.

- Currently there is no lock loss catching in the model. We should add a trigger on arm power (or an equivalent mechanism) to turn off the inputs to prevent the spurious inputs.

I focused these lenses so that we could get a clean image of the mirrors and the OSEMs.

Our goal is to have an image where the optic diameter almost fills the entire monitor. We want the focus to be adjusted for the YAG beam (which is almost the same as focusing for the OSEMs). This will NOT produce a nice image of the cage using visible light, but that is just fine.

When Justin Garofoli was here he found a nice lens combo that did the job, so if anyone can find his old email or elog, lets just go back to that.

For now, we do not need a camera/lens system to focus very tightly on the center of the optic.

Approximately two weeks ago I diagonalized the LSC output matrix for the DRMI locking.

Since actuation on the position of BS changes not only MICH but also PRC and SRC, we needed to diagonalize the output matrix.

- What I did :

 (1) The DRMI was locked. At this point PRC, MICH and SRC was controlled by PRM, BS and SRC actuators respectively.

 (2) I injected excitation signal on C1:LSC-MICH_EXC by awg. The excitation was at about 200 Hz, which is above the UGF of all the LSC loops.

    At this point the excitation only shakes the position of BS.

 (3) I looked at spectra of REFL11_I, AS55_Q, AS55_I, that were used to sense PRC, MICH and SRC respectively.

   At the beginning I was able to see the peak due to the excitation in those spectra. This means BS shakes the other DOFs (i.e. PRC and SRC) as well as MICH.

 (4) To minimize the coupling from MICH to PRC (or SRC), I tuned a number on an element of the output matrix, which transfers the signal from MICH to PRM (or SRM).

   This business was done by looking at the peak on REFL11_I (or AS55_I) and minimizing it. Since this technique was too naive the tuning was done only in second decimal place.

The PMC is losing power.

Nulling the slow actuation offset fixed the issue. Now PMC is back to normal.

The reflected beam on the CCD was quite symmetric (it looked very TEM00 mode !) for some reasons, I somehow suspected the mode matching to PMC.

One possibility I thought of was the laser temperature because it could change the laser spatial mode.

So I looked at the slow actuation offset on the FSS screen and found it was at -4.0 which sounds somewhat big.

Then I zeroed the offset by the slider and relocked PMC.

Then the spatial pattern of the reflected beam became usual (i.e. junk light looking) and the transmitted light wet up to 0.83 which is normal.

While answering a quick question by Kiwamu, I noticed we only had second trends going back to 99050000 GPS time, May 27th 2011. 

Trends (I thought) were intended to be kept forever, and certainly longer than full data, which currently goes back several months.

Jamie will need to look into this.

I checked the state of the whitening filters for the ETMY shadow sensors.

Result : They've been OFF  (i.e. flat response).

(measurement and setup)

 I measured the transfer functions of the whitening board (D000210) by looking at the signal before and after the whitening stage.

 The whitening board handles five signals; UL, UR, LR, LL and SD, and there are five single-pin lemo outputs for each signal on the front panel.

A good thing on those lemo monitors is that their signals are monitored before the whitening stages.

Rana suggested me to use these signals for the denominator of the transfer functions and consider the sensor signals as excitation signals.

So I plugged those signals into extra ADC channels via an AA-board and measured the transfer functions.

In the measurement the coherence above 4 Hz was quite small while the suspension was freely swinging.

Therefore I had to excite the ETMY suspension by putting random noise in a frequency band from 5 Hz to 35 Hz to obtain better coherence.

(results)

 The response is flat over frequency range from ~ 0.2 Hz to ~40 Hz, see the plot below. 

According to the spectrum of each signal the measurements above 10 Hz are just disturbed by the ADC noise.

If the whitening filters are ON, a pole and zero are expected to appear at 30 Hz and 3 Hz respectively according to the schematic, but no such features.

 Our concept is to keep second trends for 1-2 months and minute trends forever. The scheme that Alan had worked out many years ago had it such that we could look back to 1998 and that the minute trends would be backed up somehow.

If its not working, we need to get Alan's help to recover the previous configuration.

I am in the process of calibrating AS55's shot noise, and I noticed that the AS55 PD input to the demod board was only finger-tight.  I then checked all of the other SMA connections in the set of RF PD demod boards, and found several more that were loose, including all of the REFL55 connections.  This is no good!!!! RF connections need to be tightened!  I went through and tightened all of the offending connections with my personal Snap-on SMA wrench. 

[Koji Jamie]

The new c1lsc code has been installed. The LSC screens have also been updated (except for ASS screen).

The major changes are:

1. Naming of the RFPD channels. Now the PD signals were named like:

REFL11_I_IN1, REFL11_I_IN2, REFL11_I_OUT ....

instead of REFL11I_blah

2. NREFL11, etc has been removed. We now have the official error signals
named like

REFL11_I_ERR

We can't use the name "REFL11_I" for the error signal as this name is
occupied by the name of the filter module.

Last night the relative intensity noise (RIN) of the beam after MC was measured.

It looks like the RIN is dominated by the motion of the MC mirrors, possibly the angular motions because we don't have any angular stabilization servos.

Suresh will estimate the contribution from the MC mirrors' angular motion to the RIN in order to see if this plot makes sense.

(RIN)

 The spectrum below 30 Hz seems to be dominated by the motion of the MC suspensions because it very resembles the spectra of those.

Above 30 Hz the spectrum becomes somehow flat, which I don't know why at the moment.

A rough estimation of the shot noise gave me a level of 10^{-9} RIN/sqrtHz, which is way below the measured spectrum.

(Setup)

 All of the suspended mirrors were intentionally misaligned except for the MC mirrors and PRM to avoid interference from the other optics.

In this setup it allows us to measure the intensity noise of the laser which is transmitted from MC.

The beam transmitted from MC is reflected by PRM and finally enters into the REFL11 RFPD.

The DC signal from the RFPD was acquired at C1:LSC-REFL_DC_DQ as the laser intensity.

As well as the RIN measurement I took a spectrum when the beam is blocked by a mechanical shutter on the PSL table.

This data contains the dark noise from REFL11 and circuit noise from the whitening, AA board and ADC. It is drawn in black in the plot.

The cut off at 15 Hz is possibly due to the digital unwhitening (two poles at 15 Hz and two zeros at 150 Hz) filter to correct the analog whitening filter.

 (continuation of this)

The noise graphs relating total noise of the Seismometer circuit (GURALP stuff) to the LIGO seismic noise curve have been completed started.

I apparently harbor hate towards Matlab (you may have notice I do everything in Mathematica)....I will try to change my ways  DX

After a couple of hickups, I was able to compile and install Koji's rework of the LSC model.

The main changes are that the model now use an RF_PD library part, and the channel names were tweaked to be more in line with what we expect.

I found a couple of small bugs in the model that were preventing it from compiling.  Those were fixed and it compiled with no further problems.

There was also some rearrangement of signal inputs to the PD_DOF matrix.  The matrix screen was updated to reflect the proper inputs.  However, this also meant that the burt restore scripts for the IFO configurations were setting the wrong elements in the matrix.  I fixed the settings for X and Y arm locking, and updated the burt snapshots using the burt/c1ifoconfigure/C1save{X,Y}arm scripts.  NOTE: burt settings will need to be updated for the MICH, PRM, DRM, and FULL IFO configurations as well.

During the build/install process, Joe and I also found a bug in the feCodeGen that was causing the filter screens to be created with the wrong names.  Joe sent out a patch that will hopefully be merged soon.  Building the model with Joe's patch fixed the screen names, so the screens are currently named correctly.

The fiber that connects the Dolphin card in the c1lsc machine (in the 1Y3 rack) to the Dolphin switch in the 1X4 rack appears to have died spontaneously this morning.  This was indicated by loss of Dolphin communication between c1lsc and c1sus.

We definitively tracked it down to the fiber by moving the c1lsc machine over to 1X4 and testing the connection with a short cable.  This worked fine.  Moving it back to using the fiber again failed.

Unfortunately, we have no replaced Dolphin fiber.  As a work around, we are stealing  a long computer->IO chassis cable from Downs and moving the c1lsc machine to 1X4.

This is will be a permanent reconfiguration.  The original plan was to have the c1lsc machine also live in 1X4.  The new setup will put the computer farther from the RF electronics, and more closely mimic the configuration at the sites, both of which are good things.

 What Larisa meant to post (I'm sure) is something more like this (sorry it's a little squished...I put too many words in the legend):

I've only included the 2 noise contributions from the LISO model that seem to dominate the sum noise.  The plot gets a little crazy if you include all of the non-important sources.

So, what's the point??

First, the new box design doesn't have any crazy-special op-amps in it, so the noise of the new box is probably comparable to the old box.  So, if that's true, the old box may not have been limiting the differential seismic noise.  This definitely needs to be checked out.  I'll make a quickie LISO model of the old Guralp breakout box, to see what its noise actually looks like, according to LISO.  If it wasn't ever the breakout box that was limiting us, what the heck was it??

Second, the current box design seems to be better than the Guralp Spec sheet noise by ~a factor of 10.  It would be nice if that number were more like a factor of 100.  Or at least 30.  So some work needs to be done to find a lower-noise op amp for the voltage buffer (the first op amp in the circuit).

Next steps:

Since Larisa is now starting her SURF project with Tara and Mingyuan, I'll look into improving the design of this box by a factor of 3 or 10. 

Then I'll need to make a mock-up of it, and test it out. 

If successful, then I'll draw it up in Altium and have it made.  Recall that there should be 2 outputs per seismometer channel, one with high gain, one with low gain.  Then 3 seismometer channels per seismometer (X, Y, Z), and perhaps multiple seismometer inputs per box.  So lots and lots of stuff all in the same box.  It's going to be pretty cool.

We've run into a problem with our attempts to get the LCS control back up and running.

As reported previously, the Dolphin fiber connection between c1lsc and c1sus appears to be dead.  Since we have no replacement fiber, the solution was to move the c1lsc machine in to the 1X4 rack, which would allow us to use one of the many available short Dolphin cables, and then use a long fiber PCIe extension cable to connect c1lsc to it's IO chassis.  However, the long PCIe extension cable we got from Downs does not appear to be working with our setup.  We tested the cable with c1sus, and it does not seem to work.

We've run out of options today.  Tomorrow we're going to head back to Downs to see if we can find a cable that at least works with the test-stand setup they have there.

The bad Dolphin was still bad when tested with a connection between c1sus and the Dolphin swtich.

I'm headed over to Downs to see if we can resolve the issue with the PCIe extension fiber.

After moving the c1lsc computer to 1X4, then connecting c1lsc to it's IO chassis in 1Y3 by a fiber PCIe extension cable, everything is back up and running and the status screen is all green.  c1lsc is now directly connected to c1sus via a short copper Dolphin cable.

After lunch we will do some more extensive testing of the system to make sure everything is working as expected.

The PMC trans power was a little low (0.77V or so).  I tweaked up the input pointing and now we're getting about 0.875V transmitted.

We are now locking the arms reliably, with reasonable transmitted power.  We zeroed the LSC offsets with script, since they were apparently not being reset with either the overall burt restore or the arm restore scripts.

We have lost a bit of power through the mode cleaner.  However, we have opted not to tweak it up just yet, so that we don't have to realign to the arms.

The WFS2 sensor head had a damaged Quadrant PIN diode (YAG-444-4A).  This has been replaced by a   YAG-444-4AH  which has a responsivity of 0.5 A/W. 

The responsivity of each quadrant was measured at normal incidence.  A diagram of the set up with the relevant power levels is attached.  The precision of these measurement is about 5% .  Largely because the power levels measured are sensitive to the position of the laser beam on the power meter sensor head (Ophir with ND filter mask taken off).  Putting the mask back on did not solve this problem.

The incident power was 0.491mW  of which about 0.026mW was reflected from the face of the QPD.  The beam was repositioned on the QPD to measure the response of each quadrant.  In each case the beam was positioned to obtain maximum DC output voltage from the relevant quadrant.  A small amount of spill over was seen in the other quadrants.  The measurements are given below

To measure these DC outputs of from the sensor-head a breakout board for the 25-pin D-type connector was used as in the previous measurements.  The results are given below

The measured responsivity agrees with the specification from the manufacturer.  It is to be noted that the previous QPD is reported to have a slightly smaller responsivity 0.4 A/W at 1064 nm.  The data sheet is attached. 

Since the new QPD may have a slightly different capacitance the RF transfer function of the WFS2 needs to be examined to verify the location of the resonances. 

QE = (h*c)/(lambda*e) * (I/P)

Where I = (Volts from Pin1 to GND)/2 /500ohms
P = Power from laser - power reflected from diode.
h, c, e are the natural constants, and lambda is 1064nm.

Also, I/P = Responsivity

I would like to announce my confusion with regard to the MICH noise budget, in hopes that someone else has some inspiration. 

If you tilt your head sideways, you will notice that in this plot (totally uncalibrated, as yet), the BLACK trace, which is my white-light measurement of the AS55 shot noise is above the AS55Q noise when the Michelson is locked (true only at low frequency).  You will also notice that the same appears to be true for the Whitening Filter + Antialiasing Filter + ADC noise (GRAY trace).  Since Black, Gray, Pink and Green should all have the same calibration factor (a constant), calibrating the plot will not change this.  Brown and Blue are the MICH_OUT (aka MICH_CTRL) for dark and bright fringes, respectively.

I measure 58mV at the DC out of the AS55 PD when the Michelson is locked on the bright fringe.  This (assuming DC transimpedance of 50ohms) gives 1.16mA of DC photo current.

So.  What is going on here?  Am I totally confused??

In other news, assuming (which I'm not 100% confident about right now) that these traces are vaguely correct, the Michelson is limited by shot noise above ~20Hz.  This is...good?  We want to be shot noise limited.  Do we want to be limited at such a low frequency?

(Also, yes I can calibrate the plot to m/rtHz, but no, I won't tonight because something is funny with my calibration for the free running noise and I'll fix it tomorrow.)

Hey, Jenne.  I think there are a couple of things.  First, you're missing a PD dark noise measurement, which would be useful to see.

But I think the main issue is that it sounds like all of your closed loop measurements are done with the in-loop PD.  This means that everything will be suppressed by the loop gain, which will make things look like they have a noise lower than the actual noise floor.

[Jenne / Kiwamu]

We spent approximately an hour for the weekly Wednesday cleaning.

This time we moved onto an area where a desk and optics shelf reside along the Y arm.

We will continue cleaning up there in the next time too.

[Jenne, Steve]

After talking with Steve, I had a look at the PEM's AA board, to see what the problem was. 

Steve said the symptom he had noticed was that the Kepco power supplies which supply the +\- 5 V to the AA board were railing at their current limits as soon as he plugged the board in.  Also, he smelled smoke. 

I started with the power supplies, and saw that the 2 individual supplies each had a dV=5V, and that the one labeled +5V had the red wire on the + output of the power supply, and the black wire on the - output.  The supply labeled -5V had the orange wire on the -output of the power suppy, and the black wire on the + output.  Normally, you would expect that the 2 black wires are also connected together, and perhaps also to ground.  But at least together, so that they share a common voltage, and you get +\- 5V.  However these 2 power supplies are not connected together at all. 

This implies that the connection must be made on the AA boards, which I found to be true.  It seems a little weird to me to have that common ground set at the board, and not at the power supplies, but whatever.  That's how it is.

The problem I found is this:  The keyed connectors were made backward, so that if you put them in "correctly" according to the key, you end up shorting the +5V to the -5V, and the 2 black wires are not connected together.  You have to put the keyed connectors in *backwards* in order to get the correct wires to the correct pins on the board.  See the attached pdf figure.

Since these are internal board connections, and they should not ever be changed now that Steve has put in the adapter thing for the SCSI cable, I'm just leaving them as-is.  Steve is going to write in huge letters in sharpie on the board how they're meant to be connected, although since this problem wasn't caught for many many years, maybe it won't ever be an issue again.  Also, we're going to move over to the new Cymac system soon-ish.  However, whomever made the power cable connector from the box to the board for this AA board was lazy and dumb.

After putting the connectors on the way they needed to be, Steve and I powered up the board, hooked up the SCSI cable in the back, and put a constant voltage (~1.3VDC battery) across various different channels, and confirmed that we could see this voltage offset in Dataviewer. (Kiwamu is hoarding both of our SRS function generators, so we couldn't put in a low freq sine wave like I normally would). Everything looked okie dokie, so I'll check the regular PEM channels tomorrow.

Steve will re-install the board in the rack in the morning.

As seen in the photo, the board has a strange bulge on the board,
and the color of the internal line around the bulge got darkened.

I don't trust this board any more. We should switch to the alternative one.

- I was investigating the SUS whitening issue.

- I could not find any suspension which can handle the input whitening switch correctly.

- I went to 1X5 rack and found that both of the two binary output boxes were turned off.
As far as I know they are pulling up the lines which are switched by the open collector outputs.

- I tried to turn on the switch. Immediately I noticed the power lamps did not work. So I need an isolated setup to investigate the situation.

- The cables are labelled. I will ask steve to remove the boxes from the rack.

 I shut down damping to the Vertex optics and removed Binary IO  Adapter chassy BO0 and BO1

About a week ago I discussed the BO0's power indicator lights with Kiwamu. They were  not on or they were blinking on-off.

I put screws into ps connectors in the back, but it did not helped.

[Jamie, Koji]

- We found the reason why some of the LEDs had no light. It was because the LEDs were blown as they were directly connected to the power supply.
The LEDs are presumably designed to be connected to a 5V supply (with internal current-limiting resistor of ~500Ohm). The too much current
with the 15V (~30mA) made the LED blown, or the life-time of them shorter.

- Jamie removed all of the BO modules and I put 800Ohm additional resister such that the resultant current is to be 12mA.
The LEDs were tested and are fine now.

- The four BO boxes for C1SUS were restored on the rack. I personally got confused what should be connected where
even though I had labeled for BO0 and BO1. I just have connected CH1-16 for BO0. The power supplies have been connected only to BO0 and BO1.

- I tested the whitening of PRM UL sensor by exciting PRM UL sensor. The transfer function told us that the pendulum response can be seen
up to 10-15Hz. When the whitening is on, I could see the change of the transfer function in that freq band. This is good.
So the main reason why I could not see theis was that the power supply for the BOs were not turned on.

- I suppose Jamie/Joe will restore all of the BO boxes on the racks tomorrow. I am going to make a test script for checking the PD whitenings.

ITMY sus damping restored.

[Suresh / Kiwamu]

 We did the following things :

   - Took the LightWave NPRO out from the MOPA box

   - Temporarily took out the laser controller which has been connected to the Y end laser.

   - Put the LightWave on AP table and plugged the laser controller and confirmed that it still emits a beam

[Things to be done]

   - measure the beam profiles and power

   - get a laser controller, which will be dedicated for this laser, from Peter King

[Background and Motivation]

 The PRC and SRC length have to be precisely measured before the vent.

In order to measure those absolute length we are going to use the Stochino technique, which requires another laser to scan the cavity profiles.

The LightWave NPRO laser in the MOPA box was chosen for the Stochino laser because it has a large PZT range of 5 MHz/V and hence allows us to measure a wider frequency range.

The laser in the MOPA box had been connected to home-made circuits, which are not handy to play with. So we decided to use the laser with the usual laser controller.

Peter King said he has a LightWave laser controller and he can hand it to us.

Until we get the controller from him we do some preparations with temporary use of the Y end laser controller.

I have installed a new binary output module in ETMY, where there was none previously.  It is installed, powered (with working LEDs), hooked up (to the binary output card and the cross connect), but it hasn't been fully tested yet.

I also re-installed the binary output module in ETMX, with newly modified power-indicator LEDs.

Both modules are fully installed, but they have not yet been fully tested to confirm that they are indeed switching the whitening and de-whitening filters.

Some updates of the LSC screen

- Signal amplitude monitor for the PD signals (--> glows red for more than 1000)

- Kissel Buttons for the main matrices

- Trigger display at the output of the DOF filters

- Signal amplitude monitor for the SUS LSC output (--> glows red for more than 10000)

ADC Over flow monitor is showing some unknown numbers (as ADCs are handled by IOPs).
I asked Joe for the investigation (and consideration for the policies)

ETMX sus damping restored

In order to install the BO module in 1X2, I need to shut down all DC power to the 1X1 and 1X2 racks.

All power has been restored to the 1X1 and 1X2 racks.  The modecleaner is locked again.

I have also hooked up the binary output module in 1X2, which was never actually powered.  This controls the whitening filters for MC WFS.  Still needs to be tested.

Here is my work plan for this week:

Current Week Plan (Week 2) (As of 6/17/11)

Setting Up for Horizontal Displacement Measurements

Begin Assembly of Sensors