[Jenne, Koji]

We removed ETMU07 from the suspension tower, after confirming that the balance was still good.  Bob put it in the oven to bake over the weekend.  The spring plungers and our spare magnets are all in there as well. 

I tried to remove the grippers from ETMU05, and when I did, both side dumbbells came off of the optic.  Unfortunately, I was working on getting channels into the DAQ, so I did not clean and reglue ETMU05 today.  However Joe told me that we don't have any ETMY controls as yet, and we're not going to do Yarm locking (probably) in the next week or so, so this doesn't really set any schedules back. 

The cleaning of ETMU05 will be tricky.  Getting the residual glue off of the optic will be fine, but for the dumbbells, we'd like to clean the glue off of the end of the dumbbells using a lint free wipe soaked in acetone, but we don't want to get any acetone in the magnet-to-dumbbell joint, and we don't want to break the magnet-to-dumbbell joint.  So we'll have to be very careful when doing this cleaning. 

The Status Table:

I have made a little bit of progress on the PEM channels.  I have begun writing up detailed instructions in the DAQ Wiki page on how to add a channel to the new DAQ system.  I have followed those instructions thus far, and can see my channels in the .ini file (and in the daqconfig gui thing), but I don't have any channels in Dataviewer or DTT. 

There are some tricky "gotchas" involved in creating new models and channels.  Some examples include:  No use of the characters "DUMMY" in any channel name.  The makefile is specifically hardcoded to fail if that string of characters is used.  Also, you must have at least 2 filter banks in every model.  Why? No one knows.  You just do.  The model won't compile unless you have 2 or more filter banks. 

My efforts today included ~3 reboots of the frame builder, and ~2 reboots of c1sus.  When Kiwamu and I rebooted c1sus, we burt restored to some time in the last 24 hrs.  Some of the SUS filters on some of the optics were not set correctly (things like the bounce roll filter), so we turned all of them on, and reset all of the input and output matricies to be the correct combination of +1 and -1's to make Pit, Pos and Yaw.  The tuning seems to happen now-a-days in the gains for each DOF, and the gains were set correctly by the burt restore for every optic except PRM.  We made some educated guesses for what the gains should be based on the other optics, and PRM is damping pretty well (these guesses included reducing the SIDE gain by ~10 from the BS SIDE value, since the analog gain of the PRM SIDE sensor is much higher than others).  We'll have to fine tune these gains using some Yuta-developed method soon.  Or find a burt snapshot that had some non-unity values in there.

 [Joe, Kiwamu]

 We tried installing C1LSC but it's not completely done yet due to the following issues.

    (1)  A PCIe optical fiber which is supposed to connect C1LSC and its IO chasis is broken at a high probability.

    (2)  Two DAC boards (blue and golden board) are missing.

 We will ask the CDS people at Downs and take some more of those stuff from there.

( works we did )

 - took the whole C1ASC crate out from the 1Y3 rack.

 - installed an IO chasis to the place where C1ASC was.

 - strung a timing optical fiber to the IO chasis.

 - checked the functionality of the PICe optical fiber and found it doesn't work.

Fig.1  c1asc taken out from the rack                                                                         Fig.2 IO chasis installed to the rack

Fig.3 PCIe extension fiber (red arrow for an obvious bended point) 

 I uploaded some pictures taken in the last and this week. They are on the Picasa web albums.

 in vac work [Nov. 18 2010]

 in vac work [Nov 23 2010]

 CDS work [Nov 24 2010]

This morning I opened the chambers and started some in-vac works.

As explained in this entry, I swapped pzt mirror (A) and (C) successfully.

The chambers are still open, so don't be surprised.

(today's missions for IOO)

 - cabling for the pzt mirrors

 - energizing the pzt mirrors and slide them to their midpoint.

 - locking and alignment of the MC

 - realignment of the pzt mirrors and other optics.

 - letting the beam go down to the arm cavity

 The elog was down so I restarted it. The instructions on the wiki do not work as the process has some complicated name (i.e. it is not just 'elogd'). I used kill and the pid number.

I will get around to updating the restart script to work with 2.8.0.

I installed the following packages on Graphviz in order to support visualization of GStreamer pipeline graphs:

graphviz

[Suresh, Jenne]

ETMU05 : Gluing Side magnets back on to the optic.

The following steps taken in this process:

1) The two magnet+dumbell units which had come loose from the optic needed to be cleaned.  A lint free wipe was placed on the table top and a few cc of acetone was poured on to it.  The free end of the dumbbell was then scrubbed on this wipe till the surface regained its shine.  The dumbell was held at its narrow part with a forceps to avoid any strain on the magnet-dumbbell joint.

2) The optic was then removed from its gluing fixture (by loosening only one of the three retaining screws) and placed in an Al ring. The glue left behind by the side magnets was scrubbed off with a optical tissue wetted with Acetone. 

3) The optic was returned to the gluing fixture.  The position of the optic was checked by inserting the brass portion of the gripper and making sure that the face magnets are centered in it [Jenne doubled checked to be sure we got everything right].

4) The side magnets were glued on and the optic in the fixture has been placed in the foil-house.

If all goes well we will be able to balance the ETMU05 and give it to Bob for baking.

ETMU07 : It is still in the oven and we need to ask Bob to take out. It will be available for installation in the 40m tomorrow.  

As a result of the vacuum work, now the IR beam is hitting ETMX.

The spot of the transmitted beam from the cavity can be found at the end table by using an IR viewer.

 I have created an updated version of the "start-elog-nodus" script and put it in .../elog/elog-2.8.0. It seems to work fine.

The elog seemed to be down at around 12:05pm.  I waited a few minutes to see if the browser would connect, but it did not.

I used the existing script in /cvs/cds/caltech/elog/ (as opposed to Zach's new on in elog/elog-2.8.0/) which also seems to have worked fine.

Problem:

We seemed to have a broken fiber link for use between the LSC and its IO chassis.  It is unclear to mean when this damage occurred.  The cable had been sitting in a box with styrofoam padding, and the kink is in the middle of the fiber, with no other obvious damage near by.  The cable however may have previously been used by the people in Downs for testing and possibly then.  Or when we were stringing it, we caused a kink to happen.

Tried Solutions:

I talked to Alex yesterday, and he suggested unplugging the power on both the computer and the IO chassis completely, then plugging in the new fiber connector, as he had to do that once with a fiber connection at Hanford.  We tried this this morning, however, still no joy.  At this point I plan to toss the fiber as I don't know of any way to rehabilitate kinked fibers.

Note this means that I rebooted c1sus and then did a burt restore from the Nov/30/07:07 directory for c1suspeics, c1rmsepics, c1mcsepics.  It looks like all the filters switched on.

Current Plan:

We do, however, have the a Dolphin fiber which originally was intended to go between the LSC and its IO chassis, before Rolf was told it doesn't work well that way.  However, we were going to connect the LSC machine to the rest of the network via Dolphin.

We can put the LSC machine next to its chassis in the LSC rack, and connect the chassis to the rest of the front ends by the Dolphin fiber.  In that case we just need the usual copper style cable going between the chassis and the computer.

 Last night I found that the response of ITMX against the angle offsets were strage.

Eventually I found a loose connection at the feedthrough connectors of ITMX chamber.

So I pushed the connector hard, and then ITMX successfully became normal.

It looked like someone had accidentally kicked the cable during some works.

This bad connection had made unacceptable offsets in the OSEM readout, but now they seem fine.

I didn't realize that the script in .../elog was configured to start 2.8.0 already. I will revert the instructions on the wiki to point to that 
one.

Issues:

1) Turns out the /opt/rtcds/caltech/c1/target/gds/param/testpoint.par file had been emptied or deleted at one point, and the only entry in it was c1pem.  This had been causing us a lack of test points for the last few days.  It is unclear when or how this happened.  The file has been fixed to include all the front end models again.  (Fixed)

2) Alex and I worked on tracking down why there's a GPS difference between the front ends and the frame builder, which is why we see a 0x4000 error on all the front end GDS screens. This involved several rebuilds of the front end codes and reboots of the machines involved. (Broken)

3) Still working on understanding why the RFM communication, which I think is related to the timing issues we're seeing.  I know the data is being transferred on the card, but it seems to being rejected after being red in, suggesting a time stamp mismatch. (Broken)

4) The c1iscex binary output card still doesn't work.  (Broken)

Plan:

Alex and I will be working on the above issues tomorrow morning.

Status:

Currently, the c1ioo, c1sus and c1iscex computers are running with their front ends. They all still have 0x4000 error.  However, you can still look at channels on dataviewer for example.  However, there's a possibility of inconsistent timing between computer (although all models on a single computer will be in sync).

All the front ends where burt restorted to 07:07 this morning.  I spot checked several optic filter banks and they look to have been turned on.

[Jenne, Kiwamu]

We put ETMX back in its tower, and confirmed its balance.  It might be pointing a teensy bit upward, but it is way less than the DC pointing offset we see when we put the OSEMs in the towers (since the PDs and LEDs have some magnetic bits to them).

Discussions are ongoing as to where the ETM should sit on its table, but we'll probably toss it into the chamber later this evening.

I took ETMY out of the magnet gluing fixture, and put it in a ring, in the foil house.  It is ready to have the wire winched and get balanced at our convenience.

The updated status table:

 Restarted the elog again, this time using .../elog/start-elog.csh, which Joe pointed out works just fine. I have amended the wiki instructions to point to this script, instead.

[Kiwamu, Jenne, Koji, Suresh]

The following steps in this process were completed.

1)  Secured the current ETMX (Old ETMY) with the earth quake stops.

2) Removed the OSEMs and noted the Sl no. of each and its position

3) Placed four clamps to mark the location of the current ETMX tower (Old ETMY's position on the table)

4) Moved the ETMX (Old ETMY) tower to the clean table flow bench.  In the process the tower had to be tilted during removal because it was too tall to pass upright through the vacuum chamber port.  It was scary but nothing went wrong.

5) Koji calculated the location of the new ETMX and told us that it should be placed on the north end of the table.

6) Moved the OSEM cables, counter balancing weights and  the 'chopper' out of the way.  Had to move some of the clamps securing the cables.

7) Moved the ETMU07 tower from the clean room to the ETMX table

8) Positioned the OSEMs as they were placed in the earlier tower and adjusted their position to the middle of the range of their shadow sensors.  The four OSEMs on the face did not give us any trouble and were positioned as required.  But the side OSEM could not be put in place.  The magnet on the left side, which we are constrained to use since the tower is not designed to hold an OSEM on the right side, seems a little too low (by about a mm) and does not interrupt the light beam in the shadow sensor.  The possible causes are

   a) the optic is rotated.  To check this we need to take the tower back to the clean room and check the location of the optic with the traveling microscope.  If indeed it is rotated, this is easy to correct.

   b) the magnet is not located at the correct place on the optic.  This can also be checked on the clean room optical bench but the solution available immediately is to hold the OSEM askew to accommodate the magnet location.  If time permits the magnet position can be corrected.

We have postponed the testing of the ETMU07 tower to 1st of Nov Dec.

Problem:

The front ends seem to have different gps timestamps on the data than the frame builder has when receiving them.

One theory is we have fairly been doing SVN checkouts of the code for the front ends once a week or every two weeks, but the frame builder has not been rebuilt for about a month. 

Current Action:

Alex is currently rebuilding the frame builder with the latest code changes.

It also suggests I should try rebuilding the frame builder on a semi-regular basis as updates come in.

Problem:

We had timing problems across the front ends.

Solution:

Noticing that the 1PPS reference was not blinking on the Master Timing Distribution box.  It was supposed to be getting a signal from the c0dcu1 VME crate computer, but this was not happening.

We disconnected the timing signal going into c0dcu1, coming from c0daqctrl, and connected the 1PPS directly from c0daqctrl to the Ref In for the Master Timing distribution box (blue box with lots of fibers coming out of it in 1X5).

We now have agreement in timing between front ends.

After several reboots we now have working RFM again, along with computers who agree on the current GPS time along with the frame builder.

Status:

RFM is back and testpoints should be happy.

We still don't have a working binary output for the X end.  I may need to get a replacement backplane with more than 4 slots if the 1st slot of this board has the same problem as the large boards.

I have burt restored the c1ioo, c1mcs, c1rms, c1sus, and c1scx processes, and optics look to be damped.

https://nodus.ligo.caltech.edu:30889/gw.swf

 [Suresh, Kiwamu]

 We finished the installation of ETMX into the chamber.

In order to clear the issue of the side OSEM, we put a spacer such that the OSEM can tilt itself and accommodate the magnet.

Though we still don't fully understand why the side magnet is off from the center. 

Anyway we are going to proceed with this ETMX and perform the REAL green locking.

 (what we did)

 - took the ETM tower out from the chamber, and brought it to the clean room again.

 - checked the rotation of the ETM by using a microscope. It was pretty good.

         The scribe lines at the both sides are at the same height within the diameter of the scribe line.

 - checked the height of the ETM by measuring the vertical distance from the table top to the scribe line. This was also quite good.

         The height is correctly 5.5 inch within the diameter of the scribe line.

 - checked the magnet positions compared with the OSEM holder holes.

     All the face magnets are a little bit off upward (approximately by 1mm or less).

     The side magnet is off toward the AR surface by ~ 1-2mm.

      (yesterday we thought it was off downward, but actually the height is good.)

 - raised the position of the OSEM holder bar in order to correct the miscentering of the face magnets.

    Now all the face magnets are well centered.

 - brought the tower back to the chamber again

 - installed the OSEMs

    We put a folded piece of aluminum foil in between the hole and the side OSEM as a spacer.

 - leveled the table and set the OSEMs to their mid positions.

 - slided the tower to place 

I succeeded in locking the end green laser to X arm with the new ETM.

Though the lock is still not so stable compared to the previous locking with the old ETM. Also the beam centering is quite bad now.

So I will keep working on the end green lock a little bit more.

Once the lock gets improved and becomes reasonably stiff, we will move onto the corner PLL experiment.

(to do)

 - beam centering on ITMX

 - check the mode matching

 - revise the control servo

This morning (~0100) I started to redo some of the wiring in the rack with the FB in it. This was in an effort to activate the new Megatron (Sun Fire 4600) which we got from Rolf.

Its sitting right above the Frame Builder (FB). The fibers in there are a rats nest. Someone needs to team up with Joe to neaten up the cabling in that rack - its a mini-disaster.

While fooling around in there I most probably disturbed something, leading to the FB troubles today.

Problem:

The front ends and fb computers were unresponsive this morning.

This was due to the fb machine having its ethernet cable plugged into the wrong input.   It should be plugged into the port labeled 0.

Since all the front end machines mount their root partition from fb, this caused them to also hang.

Solution:

The cable has been relabled to "fb" on both ends, and plugged into the correct jack.  All the front ends were rebooted.

Testing RFM for green locking:

I tested the RFM connection between c1ioo and c1scx.  Unfortunately, on the first test, it turns out the c1ioo machine had its gps time off by 1 second compared to c1sus and c1iscex.  A second reboot seems to have fixed the issue.

However, it bothers me that the code didn't come up with the correct time on the first boot.

The test was done using the c1gcv model and by modifying the c1scx model.  At the moment, the MC_L channel is being passed the MC_L input of the ETMX suspension.  In the final configuration, this will be a properly shaped error signal from the green locking.

The MC_L signal is currently not actually driving the optic, as the ETMX POS MATRIX currently has a 0 for the MC_L component.

The last time(Moonday) Jenne and I worked on the RF distribution unit's structure.

We are making RF distribution unit for RF upgrade which is designed by Alberto.

Rana, Koji, Jenne suggested a better design for RF Distribution unit.

So Jenne and I gathered information of parts and decided what parts will be used with specific numbers.

Specific circuit is shown in the attached picture.

Any suggestion would be really appreciated.

Looks like there was a power outage. The control room workstations were all off (except for op440m). Rosalba and the projector's computer came back, but rossa and allegra are not lighting up their monitors.

linux1 and nodus and fb all appear to be on and answering their pings.

I'm going to leave it like this for the morning crew. If it

The monitors for allegra and rossa's seemed to be in a weird state after the power outage.  I turned allegra and rossa on, but didn't see anything.  However, I was after awhile able to ssh in.  Power cycling the monitors did apparently got them talking with the computers again and displaying.

I had to power cycle the c1sus and c1iscex machines (they probably booted faster than linux1 and the fb machines, and thus didn't see their root and /cvs/cds directories).  All the front ends seem to be working normally and we have damped optics.

The slow crates look to be working, such as c1psl, c1iool0, c1auxex and so forth.

Kiwamu turned the main laser back on.

I checked the vacuum system and judged there is no apparent issue.

The chambers and annulus had been vented before the power failure.
So the matters are only on the TMPs.

TP1 showed the "Low Input Voltage" failure. I reset the error and the turbine was lift up and left not rotating.
TP2 and TP3 seem rotating at 50KRPM and the each lines show low pressur (~1e-7)
although I did not find the actual TP2/TP3 themselves.

Computer moved:

The c1lsc computer has been moved over to the 1Y3 rack, just above the c1lsc IO chassis. 

It will talking to the c1sus computer via a Dolphin PCIe reflected memory card.  The cards have been installed into c1lsc and c1sus this morning.

It will talk to its IO chassis via the usual short IO chassis cable.

To Do:

The Dolphin fiber still needs to be strung between c1sus and c1lsc.

The DAQ cable between c1lsc and the DAQ router (which lets the frame builder talk directly with the front ends) also needs t to be strung.

c1lsc needs to be configured to use fb as a boot server, and the fb needs to be configured to handle the c1lsc machine.

C1LSC Status:

The c1lsc computer is running Gentoo off of the fb server. It has been connected to the DAQ network and is handling mx_streams properly (so we're not flooding the network error messages like we used to with c1iscex).  It is using the old c1lsc ip address (192.168.113.62). It can ssh'd into.

However, it is not talking properly to the IO chassis.  The IO chassis turns on when the computer turns on, but the host interface board in the IO chassis only has 2 red lights on (as opposed to many green lights on the host interface boards in the c1sus, c1ioo, and c1iscex IO chassis).  The c1lsc IO processor (called c1x04) doesn't see any ADCs, DACs, or Binary cards.  The timing slave is receiving 1PPS and is locked to it, but because the chassis isn't communicating, c1x04 is running off the computer's internal clock, causing it to be several seconds off. 

Need to investigate why the computer and chassis are not talking to each other.

General Status:

The c1sus and c1ioo computers are not talking properly to the frame builder.  A reboot of c1iscex fixed the same problem earlier, however, as Kiwamu and Suresh are working in the vacuum, I'm leaving those computers alone for the moment, but a reboot and burt restore probably should be done later today for c1sus and c1ioo

Current CDS status:

 [Suresh and Kiwamu]

We aligned the green beam to the X arm cavity more carefully.

Now the green beam is hitting the centers of ETMX, ITMX and BS.

Also we confirmed that the green beam successfully comes out from the chamber to the PSL table.

(what we did)

- opened the BS, ITMX and ETMX chambers. 

- checked the positions of the beam spots on ITMX, BS and ETMX

   The spot position on ETMX was fine,

   But at BS and ITMX, the spots were off downward.

   We decided to move the beam angle by touching a steering mirror at the end green setup.

- changed the beam axis by touching the steering mirror at the end station.

- checked the spot positions again, they all became good. It looks the errors were within ~ 1mm.

- moved the position of a TT, which is sitting behind the BS, by ~10mm, because it was almost clliping the beam.

- aligned the green optics

- got the beam coming out from the chamber. 

I restarted the elog because i changed the configuration for the cryo-elog.

Used the "start-elog.csh" script in /cvs/cds/caltech/elog/

[Suresh, Jenne]

We Finished!!!

ETMU05 (ETMY) had its wire winched to the correct height, was balanced, and had the standoff glued.  Since it's kind of like final exam week at Caltech, Suresh had his suspension exam today, and did most of this work himself, with me hanging around and watching. 

As you can see in my almost entirely green table, all that is left to do with the whole suspensions project is bake the optic (hopefully Bob has time / space this week), and then stick it in the chamber!  Hooray!!! (Can you tell I'm excited to not spend too much more time in the cleanroom?)

The table:

[Joe and Kiwamu]

We added some more DAQ channels on c1sus.

We wanted to try diagonalizing the input matrices of the ITMX OSEMs because the motion of ITMX looked noisier than the others

So for this purpose we tried adding DAQ channels so that we can take spectra anytime.

After some debugging, now they are happily running.

(DAQ activation code)

There is a code which activates DAQ channels written by Yuta in this October.

       /cvs/cds/rtcds/caltech/c1/chans/daq/activateDAQ.py

If you just execute this code, it is supposed to activate the DAQ channels automatically by editing C1AAA.ini files.

However there were some small bugs in the code, so we fixed them.

Now the code seems fine.

(reboot fb DAQ process)

When new DAQ channels are added, one has to reboot the DAQ process running on fb.

To do this, log in to a certain port on fb,

          telnet fb 8088

     shutdown

Then the process will automatically recover by itself.

After doing the above reboo job, we found tpman on C1IOO got down.

We don't fully understand why only C1IOO was affected, but anyway rebooting of the c1ioo front end machine fixed the problem.

I swapped out the IO chassis which could only handle 3 PCIe cards with the another chassis which has space for 17, but which previously had timing issues.  A new cable going between the timing slave and the rear board seems to have fixed the timing issues. 

I'm hoping to get a replacement PCI extension board which can handle more than 3 cards this week from Rolf and then eventually put it in the Y-end rack.  I'm also still waiting for a repaired Host interface board to come in for that as well.

At this point, RFM is working to c1iscex, but I'm still debugging the binary outputs to the analog filters.  As of this time they are not working properly (turning the digital filters on and off seems to have no effect on the transfer function measured from an excitation in SUSPOS, all the way around to IN1 of the sensor inputs (but before measuring the digital fitlers).  Ideally I should see a difference when I switch the digital filters on and off (since the analog ones should also switch on and off), but I do not.

I moved the Pynds package from Yuta's local directory to the public place.

Now the package is living under :

Also I added the PATH on cshrc.40m, so you don't have to setenv every time.

       (This package can not run on non-64bit linux)

Typing "import nds" on python allows you to use the nds functions.

 Quote from Yuta's  past entry

The ETMU05 has been removed from the suspension and put into the little foil house. 

Before removing it I checked the position and pitch of the optic with reference to the table top. 

The height:

     Using the traveling microscope I checked the height of the scribe lines from the table top.  They are at equal heights, centered on 5.5 inches, correct to about a quarter of the width of the scribe line.

The pitch

    The retro-reflection of the He-Ne laser beam is correct to within one diameter of the beam at a distance of about 1.5m.  This is the reflection from the rear, AR coated, surface.  The reflection from the front, HR coated, surface was down by about two diameters.

Jenne has checked with Bob and agreed on a date for baking the optic.

I found that all the front end machine showed the red light indicators of DAQ on the XXX_GDS_TP.adl screens.

Also I could not get any data from both test points and DAQ channels.

First I tried fixing by telneting and rebooting fb, but it didn't help.

So I rebooted all the front end machines, and then everything became fine.

I am leaving ITMX and ETMX freely swinging, so that later I can take the spectra and diagonalize the input matrices.

Please don't restore the watchdogs until tomorrow morning.

[josephb, Osamu]

Megatron Setup:

To show Osamu how to setup a a front end as well as provide a test computer for Osamu's use, we used the new megatron (sunfire x4600 with 16 cores and 8 gigabytes of memory) as a front end without an IO chassis.

The steps we followed are in the wiki, here.

The new megatron's IP address is 192.168.113.209.  It is running the c1x99 front end code.

The input matrix of ITMX has been diagonalized.

The evaluation of this diagonalisation  will be done tonight by freely swinging ITMX again.

(Somehow I couldn't get any data for ETMX from the DAQ channels. I will try it again tonight.)

(details)

For solving the matrix, I used Yuta's python code called inmartixoptimizer.py.

I took the transfer functions of UL->UR, UL->LL and UL->LR as described in this entry.

In the measurement, the frequency bin was set to 0.001 Hz and the data were 50 times averaged on dtt.

Here is the new input matrix.

[[ 0.87059649  1.14491977  1.07992057  0.90456317]
 [ 0.64313916  0.55555661 -1.44997325 -1.35133098]
 [ 1.13979571 -1.19186285 -0.89606597  0.77227546]]

This matrix should give a better performance than before.

When adding the ETMX DAQ channels using the daqconfig gui (located in /opt/rtcds/caltech/c1/scripts/) on C1SCX.ini, we forgot to set the acquire flag to 1 from 0.

So the frame builder was receiving the data, but not recording it.

We have since then added ETMX and the C1SCX.ini file to Yuta's useful "activateDAQ.py" script in /opt/rtcds/caltech/c1/chans/daq/, so that it now sets the sensor and SUSPOS like channels to be acquired at 2k when run.  You still need to restart the frame builder (telnet fb 8087 and then shutdown) for these changes to take effect.

The script now also properly handles files which already have had channels activated, but not acquired.

Problem:

c1pem model was reporting all zeros for all the PEM channels.

Solution:

Two fold.  On the software end, I added ADCs 0, 1, and 2 to the model.  ADC 3 was already present and is the actual ADC taking in PEM information.

There was a problem noted awhile back by Alex and Rolf that there's a problem with the way the DACs and ADCs are number internally in the code.  Missing ADCs or DACs prior to the one you're actually using can cause problems.

At some point that problem should be fixed by the CDS crew, but for now, always include all ADCs and DACs up to and including the highest number ADC/DAC you need to use for that model.

On the physical end, I checked the AA filter chassis and found the power was not plugged in.  I plugged it in.

Status:

We now have PEM channels being recorded by the FB, which should make Jenne happier.

[josephb,Suresh]

We put in the fiber for use with the Dolphin reflected memory between c1sus and c1lsc (rack 1X4 to rack 1Y3).  I still need to setup the dolphin hub in the 1X4 rack, but once that is done, we should be able to test the dolphin memory tomorrow.

The oplevs have been installed on ITMX and ETMX.

Now the oplev servos are running.

The lock of the green beam became more stable after the oplevs were activated.

(what I did)

- opened the ITMX and ETMX chamber.

- rearranged the oplev mirrors in the vacuum chambers so that we can have the reflected oplev beam coming out from the viewport.

    At the ITMX table, I put the oplev mirrors approximately on the designed places.

- aligned the beam on the optical benches

- strung a ribbon cable at the 1X9 rack.

   This cable connects the oplev interface board and the ADC blue golden board.

- modified c1scx simulink model.

  Since the model didn't have proper connections to the ADC channels, I added four ADC channels and plugged them into oplev servo in the model.

- relaunched the c1scx code after building and installing it.

- activated the oplev servos. Amazingly the default gains did work (i.e. all the gain = 1)

- after aligning X arm to the green beam, I did final centering of oplev beams

(details)

 - - - - - ADC connection for ETMX oplev signals :

ADC0_24 = segment_1

ADC0_25 = segment_2

ADC0_26 = segment_3

ADC0_27 = segment_4

Tonight, swing again.

Please do not restore the watchdogs until tomorrow (Dec.9) morning.

We measured Open loop TF for oplev pitch on ITMX.

 All feed back filter of oplev  was on as same as before. Original notch filters which notches above 10Hz resonance should be modified with some measurements of present resonant frequency. Up to 10Hz, a simple f^2 filter is used, so the notch should not affect this measurement.

Measured upper UGF is about 2Hz with gain slider 1, and lower UGF is 1.3Hz. Phase margin is 40 degree, so it is not a good idea to increase the gain drastically.

I have measured the coherence also but I could not find a way to put it on this picture. Anyway coherence below 0.6Hz was not so good like ~0.95. This can be improved if larger excitation is used next time.

During this measurement around 0.2-0.3Hz, small earthquake happened but seemed OK for the control.

We will measure the other TF, yaw, ETMX or somthing, maybe tomorrow, due to free swinging ITMX and ETMX tonight.

After Kiwamu had set the free swinging mode for ITMX and ETMX, I found a big jump of ITMX pitch and yaw. This jump is shown on oplev and OSEM plots.

I talked with Kiwamu on the phone that a shutdown of suspensions does not add a big offset, and so that it should not make a big jump.

We were not sure that this jump was due to the shutdown or drift or something else. Anyway I put ITMY oplev on center again at 0;57am.