40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 264 of 344  Not logged in ELOG logo
IDdown Date Author Type Category Subject
  4068   Fri Dec 17 02:22:06 2010 kiwamuUpdateCDSETMY damping: not good

  I made some efforts in order to damp ETMY, however it still doesn't happily work.

 It looks like something wrong is going on around the whitening filters and the AA filter borad.

I will briefly check those analog parts tomorrow morning.

 

- - -(symptom)

Signs of the UL and the SD readouts are flipped, which I don't know why.

At the testpoints on the analog PD interface board, all the signs are the same. This is good.

But after the signals go through the whitening filters and AA filters, UL and SD become sign-flipped.

I tried compensating the sign-flips by changing the sign by means of the software, but it didn't help the damping. 

In fact the suspension got crazy when I activated the damping. So I have no idea if we are looking at exactly right readouts or some sort of different signals.

 

- - -(fixing DAC connector)

 I fixed a connector of the DAC ribbon cable since the solderless connector was loosely locked to its cable.

Before fixing this connector I couldn't apply voltages on some of the coils  but now it is working well.

  4067   Fri Dec 17 00:55:30 2010 KojiUpdateIOOThe dark port beams reached the AP table

[Koji and Kiwamu]

We obtained two dark port beams on the AP table: OMC REFL and AS

- First, IPANG and BS were aligned so as to have the beams on the center of the ETMs.

- Then ITMX/ITMY/PRM/SRM were aligned to have fringes in a single spot anywhere.

- As we already had the dark port beam on the steering mirrors on the BS table, today the PZT mirrors were adjusted.
This work was the beam steering between the BS table to the OMC table. After some tweaking of the mirror mounts, 
the spot on the last PZT mirror was found.

As we have not touched any of the OMC optics since they were aligned well, the alignment has been adjusted by the nobs of the PZT steering mirrors.
Once the beam is on the output mode matching telescope (OMMT), the work was quite easy thanks to the beam shrinking by the OMMT.

Note that the dark port beam is slightly clipped by the green steering mirror. The steering mirror will be moved next time.

After the alignment, we indeed obtained OMC REFL and AS beams on the AP table.
The fringes were visible on the OMC REFL CCD.

We keep the dark port setup on the OMC (in-vac) and AP tables so that they can be the reference of the dark port alignment.
In principle we can align the beams onto the OMC by the two PZT mirrors.


What is left?

Our minimum success of this vent is to setup the X arm cavity which is needed for the green locking.
This setup was already realized. So we fulfilled the condition to close the tank even if the damping of
the ETMY is not achieved. (But we should try)

Tomorrow, we make a light touches to POY, Green, IPPOS, and check the table leveling, clamping, etc, in general.

JD:  We should check OSEMs for all optics *after* table leveling.  Some of them (esp. BS and ITMX) are currently close to their limits right now.

KA: Check green alignment. / Take photos of the tables. / Fix the leveling weights


Location    Optics            Action
--------------------------------------------------------------
@ITMY -     POY               mirror replacement (45deg->0deg) / alignment

@BSC -      Green steering    alignment
            IPPOS steering    alignment
            Beam dumps
            Table Leveling

@ETMX -     Al foil removal
            Table Leveling

@ETMY -     ETMY damping
            OSEM
            OPLEV
            Table Leveling

@ITM/ETM -  Mirror Wiping

  4066   Fri Dec 17 00:30:05 2010 KojiUpdateIOOITMY / SRM / BS / PRM OPLEVs aligned

[Steve and Koji]

The invac OPLEV mirrros were aligned before we get to the PMA party.

The OPLEV mirrors were adjusted in accordance with the optical layout.
Surprisingly the optical layout was enough precise such that we have the healthy red beams on the optical tables.
Steve placed the apertures at the position of the returning spots while I shook the stack to check if the range of the spot motion is sufficient.

The sole thing that has been deviated from the optical layout was that the SRM returning beam had to be reroute
as the SRM has better reflectivity on the AR surface in stead of the HR one.

  4065   Thu Dec 16 15:10:18 2010 josephb, kiwamuUpdateCDSETMY working at the expense of ETMX

I acquired a second full pair of Host interface board cards (one for the computer and one for the chassis) from Rolf (again, 2nd generation - the bad kind).

However, they exhibited the same symptoms as the first one that I was given. 

Rolf gave a few more suggestions on getting it to work.  Pull the power plugs.  If its got slow flashing green lights, just soft cycle, don't power cycle.  Alex suggested turning the IO chassis on before the computer.

None of it seemed to help in getting the computer talking to the IO chassis.

 

I finally decided to simply take the ETMX IO chassis and place it at the Y end.  So for the moment, ETMY is working, while ETMX is temporarily out of commission. 

We also made the necessary cables (2x 37 d-sub female to 40 pin female and 40 pin female to 40 pin female) .  Kiwamu also did nice work on creating a DAC adapter box, since Jay had given me a spare board, but nothing to put it in.

  4064   Thu Dec 16 10:52:42 2010 josephbUpdateCamerasNew PoE digital cameras

We have two new Basler acA640-100gm cameras.  These are power over ethernet (PoE) and very tiny.

Attachment 1: basler.jpg
basler.jpg
  4063   Thu Dec 16 01:23:43 2010 kiwamuUpdateSUSSRM OSEMs installed

  [Zach and Kiwamu]

 We worked on some more vacuum businesses.  Today we finished did the following works:

 - alignment of the POX mirrors 

 - alignment of the POP1 and POP2 mirrors

 - installation of OSEMs onto SRM

 - alignment of the SRM tower

 

 (alignment of POP mirrors)

 Since a beam on the POP path was quite too weak to see even by IR viewers, we used a He-Ne laser to imitate the real beam instead.

We injected the He-Ne beam from an optical bench to the chamber, and made it go through the PRM and PR2 by using some steering mirrors.

 

(OSEM cables)

 The pin assignment was flipped in a way of mirror image due to the extension cables which cause a mirroring.

 So we made mirroring connectors to flipp them back to the correct pin assignment, and plugged the mirroring connectors in between the feedthrough of the BS chamber and the SRM satellite box.

This is a picture showing how they are connected now.

DSC_2757_ss.jpg

  4062   Wed Dec 15 23:10:40 2010 KojiUpdateIOOSRM Oplev / Dark Steering mirrors installed

I helped the vacuum installation work in the evening.

- Three steering mirrors after the SRM (OM1-OM3) were installed on the table. OM1 and OM2 were aligned.
  OM3 is in-place but not aligned to the OM4 (PZT).

- The ITMY oplev setup was disintegrated. The SRM/ITMY oplev beams were prepared.

- The SRM oplev mirrors were placed on the table and aligned.

- The ITMY oplev mirrors were placed on the table but not in-place.

  4061   Wed Dec 15 18:29:59 2010 JenneUpdatePEMSeismometer Channels Being Recorded Again

The Seismometer channels are once more being recorded.  Alastair brought Gur1 back from the ATF the other day, and today I put it in its place below MC2 (yeah, the numbers are backwards.  But they always have been.) 

I checked the matching between BNC inputs on the breakout box to the ADC channels as labeled in the SimuLink diagram.  To do this I had all 32 channels activated, and I put a 1Hz, 1Vpp sine wave into various BNC inputs to see what channel they showed up as.  At first things were a bit backwards (BNC channels 1-16 going to ADCs 16-31, and BNCs 17-32 going to ADCs 0-15), but then Joe quickly flipped the cables on the adapter board in the back and things are in the correct order now.  Channel 1 on the BNC board corresponds to channel 0 on the ADC, etc. 

I checked that jumping near each seismometer made the signals spike, which they did. 

I then changed the channel names in the c1pem.mdl SimuLink diagram to match the old channel names for the Guralps and the accelerometers, and deleted all of the other channels that aren't being used.  There's a table in the diagram to indicate what goes with what, as of today.  If you do anything to the PEM diagram, please update the table so it's easy to look things up.

I recompiled the code, but have not yet restarted the frame builder since Zach and Kiwamu are working on some things in the chamber, and I don't want to be annoying (so the channels aren't actually being recorded quite yet). 

Edit, 7:15pm:  Just kidding.  Something didn't work, and I have to track down what.  I'm not getting any data yet.

  4060   Wed Dec 15 17:21:20 2010 josephbUpdateCDSETMY controls status

Status:

The c1iscey was converted over to be a diskless Gentoo machine like the other front ends, following the instructions found here.  Its front end model, c1scy was copied and approriately changed from the c1scx model, along with the filter banks.  A new IOP c1x05 was created and assigned to c1iscey.

The c1iscey IO chassis had the small 4 PCI slot board removed and a large 17 PCI slot board put in.  It was repopulated with an ADC/DAC/BO and RFM card.  The host interface board from Rolf was also put in. 

On start up, the IOP process did not see or recognize any of the cards in the IO chassis.

Four reboots later, the IOP code had seen the ADC/DAC/BO/RFM card once.  And on that reboot, there was a time out on the ADC which caused the IOP code to exit.

In addition to the not seeing the PCI cards most of the time, several cables still need to be put together for plugging into the the adapter boards and a box need to be made for the DAC adapter electronics.

 

  4059   Wed Dec 15 16:04:49 2010 steveConfigurationVACvacuum valves found in default condition

This condition is created when we run out of nitrogen that holds the valves in set positions. The Maglev and other turbos are still running in this configuration so one has to pay attention that the foreline valves are open.

Reset  error message on vacuum screen and opened V4 & V5 at 3pm today.

  4058   Wed Dec 15 14:23:32 2010 KojiUpdateCDSETMY IO chassis update

Great!

I wish this board works fine at least for several days...

Quote:

I gave Alex a sob story over lunch about having to go and try to resurrect dead VME crates.  He and Rolf then took pity on me and handed me their last host interface board from their test stand, although I was warned by Rolf that this one (the latest generation board from One Stop) seems to be flakier than previous versions, and may require reboots if it starts in a bad state.

Anyways, with this in hand I'm hoping to get c1iscey damping by tomorrow at the latest.

 

  4057   Wed Dec 15 13:36:44 2010 josephbUpdateCDSETMY IO chassis update

I gave Alex a sob story over lunch about having to go and try to resurrect dead VME crates.  He and Rolf then took pity on me and handed me their last host interface board from their test stand, although I was warned by Rolf that this one (the latest generation board from One Stop) seems to be flakier than previous versions, and may require reboots if it starts in a bad state.

Anyways, with this in hand I'm hoping to get c1iscey damping by tomorrow at the latest.

  4056   Wed Dec 15 12:46:18 2010 KojiSummaryIOOFinishing up the vac work

What else?

v: Edit on Dec 15 10PM
v: Edit on Dec 16 10PM

JD:  We should check OSEMs for all optics *after* table leveling.  Some of them (esp. BS and ITMX) are currently close to their limits right now.

KA: Check green alignment.

Take photos of the tables.

Fix the leveling weights



Location    Optics            Action
--------------------------------------------------------------
@ITMX -     v POX             alignment
            v POP1/POP2       alignment
            v Table Leveling

@ITMY -     POY               mirror replacement (45deg->0deg) / alignment
            v SR2-TT          alignment
            v SRM Tower       alignment / EQ-stop release
            v SRM             alignment
            v SRM OSEM
            vvSRM OPLEV (X2)  install (VIS)/ alignment
            v ITMY OPLEV (X2)   install (VIS)/ alignment
            v OM1/OM2         install (DLC 45deg)/ alignment       
            v Table Leveling

@BSC -      v OM3             install (DLC 45deg/ alignment)
            v OM4(PZT)          neutralize, adjustment
            IPPOS steering    alignment
            v BS OPLEV        alignment
           
v PRM OPLEV(x2)     alignment
            Beam dumps
            Table Leveling

@IMC -      v REFL              mirror replacement (45deg->0deg)

@ETMX -     Al foil removal
            Table Leveling

@ETMY -     ETMY damping
            OSEM
            OPLEV
            Al foil removal
            Table Leveling

@OMC -      v OM5(PZT)        neutralize, adjustment

@ITM/ETM -  Mirror Wiping

  4055   Tue Dec 14 22:42:56 2010 kiwamuUpdateSUSinstalled the last TT . And some more progresses

  [Koji, Oasmu and Kiwamu]

We made the following progresses :

   (1) installation of the last TT called SR2.

 (2) fixing an earthquake stop issue on the BS

  (3) fixing a clipping of beams at the dark port


(earthquake stops on the BS)

 - When we were aligning the BS, we found that the BS showed funny behaviors.

For example a kick on LR didn't shake LRSEN, and a big DC angular offset (~ 8 in the medm screen ) was needed to keep a horizontal beam axis in the reflection.

We checked all the earthquake stops and found two suspicious earthquake stops at right bottom side.

They looked like slightly touching the BS. So we moved them further away from the BS.

Then the problem had gone.  We doublechecked the health by kicking, applying an angular offset  and so on.

 

(beam clipping)

We found transmitted/reflected beams from the BS to the dark port was clipped at the BS tower.

We moved the BS tower by ~1cm and realigned the rotation of the BS tower.

We also found the beam spots on the two TTs, PR2 and PR3, were offcentered. Especially the beam spot on PR3 was almost on the edge of the mirror.

Probably this was because we touched PZT1 when aligning the beam to the Y end.

So it means, it is not a good idea to align the beam to the end only by steering PZT1. We should use PR2 and PR3 as well when we align the beam to the Y end.

We realigned them such that the beam hits the center of PR2, PR3 and ETMY.

  4054   Tue Dec 14 15:15:19 2010 kiwamuUpdateSUSput ETMY and aligned the beam

  [Zach and Kiwamu]

 We installed the new ETMY tower and successfully aligned the beam to the center of ETMY.

 Also we finished the final alignment of IP_ANG.

 

 

(what we did)

 - took the old ETM out  from the chamber and put it on the flow bench at the X end.

 - with a help from Joe and Osamu, we brought the new ETM and put it roughly on place.

 - did a fine positioning of ETMY.

 - covered the ETM tower with a large peace of aluminum foil in order to see the spot on a video monitor.

 - stoled a compact video monitor that was sitting on the PSL table since we don't have any monitors at the Y end.

 - made a ~1cm hole on the foil as a target for the beam.

 - steered PZT1 in order to correct the beam position on ETMY. This is done by looking at the spot on the video monitor.

 - steered IPANG_SM1 to let the beam hit a steering mirror in the ETMY chamber which Koji installed recently.

     Now we have IP_ANG coming out from the viewport of the ETMY chamber.

  4053   Tue Dec 14 11:24:35 2010 josephbUpdateCDSburt restore

I had updated the individual start scripts, but forgotten to update the rc.local file on the front ends to handle burt restores on reboot.

I went to the fb machine and into /diskless/root/etc/ and modified the rc.local file there.

Basically in the loop over systems, I added the following line:

/opt/epics-3.14.9-linux/base/bin/linux-x86/burtwb -f /opt/rtcds/caltech/c1/burt/autoburt/latest/${i}epics.snap  -l /opt/rtcds/caltech/c1/burt/autoburt/logs/${i}epics.log.restore -v

The ${i} gets replaced with the system name in the loop (c1sus, c1mcs, c1rms, etc)

  4052   Tue Dec 14 09:26:17 2010 ZachUpdateelogrestarted

 Restarted the elog with the script

  4051   Tue Dec 14 04:14:53 2010 ranaUpdateElectronicsRF Photodiode Characterizations

This is looking better, but the fit data for the TF should be plotted along with the data. The data should be made up of points and the fit a line.

For the fit, we should have the Q of the main resonance as well as the peak height of the main resonance and the values of the gain at the notch frequencies.

Also the peak as well as the notches should have the frequencies fit for and labeled. In principle, you can make the plot on the wiki have all of the data. Then in the end we can print the plot in a small size and glue it to the PD's backside.

  4050   Tue Dec 14 01:04:23 2010 kiwamuUpdateSUSalignment of ITMs and PRM done

   The alignment of the ITMs and the PRM has been done.

 As a result their reflections now come out at the REFL port successfully. 

The vacuum work is going on well as we scheduled at the last meeting.

 

(plan for tomorrow) 

 - installation of ETMY

 - installation of OSEMs on ETMY

 - alignment of the beam to the center of ETMY

 - alignment of the ETMY to the beam

 - final alignment of IP_ANG

 - setting up the oplev for ETMY

 - replace one of the steering mirrors at the RFEL path by a 0 deg mirror (see here).

 - setting up POX/POY (if there are time)

 

(today's activity) 

 - aligned the PRM tower such that the reflected beam goes back to exactly the same path as that of the incoming beam.

 - leveled the ITMY table because the OSEMs of ITMY had been completely out of range.

 - aligned the ITMY and ITMX in order to let the reflections back to REFL.

 - with a help from Osamu, we put a CCD camera, which actually had been used as OMC_T, just after the view port on the AP table.

 - looking at the CCD monitor we were able to see the reflected lights from the ITMs. (In fact sensor cards didn't help looking for the lights.)

  - playing with the alignment of the ITMs, we easily obtained Michelson fringes, which were also visible on the CCD monitor.

  4049   Mon Dec 13 22:21:41 2010 kiwamuSummarySUSfunny output matrix of ETMX: solved !

I found that a few connections in the simulink model of c1scx was incorrect, so I fixed them correctly.

It had been a mystery why we had to put a funny matrix on ETMX (see this entry).

But now we don't have to do such a voodoo magic because the problem was solved.

Now the damping of ETMX is happily running with an ordinary output matrix.


 --(details)

 I looked at the wiring diagram of the ETMX suspension (it's on Ben's web page) and confirmed that the coils are arranged in order of UL, LL, UR, LR.

But then I realized that in our simulink model they had been arranged in order of UL, UR, LL, LR.

So UR and LL had been swapped incorrectly !

So I just disconnected and plugged them into the right outputs in the simulink model.

   I rebooted c1iscex in order to reactivate c1scx front end code.

After rebooting it, I changed the output matrix to the usual one, then everything looked okay.

(actually it's been okay because of the combination of the wrong connections and the funny matrix).

  4048   Mon Dec 13 21:03:30 2010 KevinUpdateElectronicsRF Photodiode Characterizations

[Koji, Jenne, Kevin]

Jenne worked on fixing REFL11 last week (see elog 4034) and was able to measure an electrical transfer function. Today, I tried to measure an optical transfer function but REFL11 is still not responding to any optical input. I tried shining both the laser and a flashlight on the PD but could not get any DC voltage.

I also completed the characterizations of POX. I redid the optical transfer function and shot noise measurements. I also took a time series of the RF output from the PD when it was powered on with no light. This measurement shows oscillations at about 225 MHz. I also measured the spectrum with no light which also shows the oscillations at 225 MHz and smaller oscillations at ~455 MHz.

The plots can be found at http://lhocds.ligo-wa.caltech.edu:8000/40m/Electronics/POX?action=show.

  4047   Mon Dec 13 18:06:43 2010 JenneUpdateSUSETMY resuspended, ready to install. Tip Tilt realigned, ready to install.

[Koji, Jenne]

I wish I could use a bigger font for this, but, the suspension work is totally done for the upgrade!!!

Now, nobody break any suspensions, or we're not going to be friends for a while. 

Koji and I put ETMY back in its tower, and made sure that both scribe lines are at the correct height.  We also confirmed that the balance is good (as Suresh mentioned in a previous elog, since we balanced using the AR surface, the HR surface is pointing downward a little bit, but it's well within the OSEMs ability to correct.

While we were in there, we also looked at Tip Tilt number 002.  As mentioned in elog 3645, the pitch pointing was off by a little bit.  Since the TTs don't have actuators, the pointing has to be pretty good.  We tweaked the balancing, and now the reflected beam goes completely back into the laser aperture, so it's as balanced as it's going to get.  This TT is now ready for installation onto the ITMY table as part of the SRC.

Kiwamu confirmed that he's going to install these optics tomorrow, since he's doing some other alignment work today.

Just for good measure, the Table:

StatusTable.png

  4046   Mon Dec 13 17:18:47 2010 josephbUpdateCDSBurt updates

Problem:

Autoburt wouldn't restore settings for front ends on reboot

What was done:

First I moved the burt directory over to the new directory structure.

This involved moving /cvs/cds/caltech/burt/ to /opt/rtcds/caltech/c1/burt.

Then I updated the burt.cron file in the new location, /opt/rtcds/caltech/c1/burt/autoburt/.  This pointed to the new autoburt.pl script.

I created an autoburt directory in the /opt/rtcds/caltech/c1/scripts directory and placed the autoburt.pl script there.

I modified the autoburt.pl script so that it pointed to the new snapshot location.  I also modified it so it updates a directory called "latest" located in the /opt/rtcds/caltech/c1/burt/autoburt directory.  In there is a set of soft links to the latest autoburt backup.

Lastly, I edited the crontab on op340m (using crontab -e) to point to the new burt.cron file in the new location.

This was the easiest solution since the start script is just a simple bash script and I couldn't think of a quick and easy way to have it navigate the snapshots directory reliably.

I then modified the Makefile located in /opt/rtcds/caltech/c1/core/advLigoRTS/ which actually generates the start scripts, to point at the "latest" directory when doing restores.  Previously it had been pointing to /tmp/ which didn't really have anything in it.

So in the future, when building code, it should point to the correct snapshots now.  Using sed I modified all the existing start scripts to point to the latest directory when grabbing snapshots.

Future:

According to Keith directory documentation (see T1000248) , the burt restores should live in the individual target system directory i.e. /target/c1sus/burt, /target/c1lsc/burt, etc.  This is a distinctly different paradigm from what we've been using in the autoburt script, and would require a fairly extensive rewrite of that script to handle this properly.  For the moment I'm keeping the old style, everything in one directory by date.  It would probably be worth discussing if and how to move over to the new system.

  4045   Mon Dec 13 11:56:32 2010 josephb, alexUpdateCDSDolphin is working

Problem:

The dolphin RFM was not sending data between c1lsc and c1sus.

Solution:

Dig into the controller.c code located in /opt/rtcds/caltech/c1/core/advLigoRTS/src/fe/.  Find this bit of code on line 2173:

 

2173 #ifdef DOLPHIN_TEST
2174 #ifdef X1X14_CODE
2175         static const target_node = 8; //DIS_TARGET_NODE;
2176 #else
2177         static const target_node = 12; //DIS_TARGET_NODE;
2178 #endif
2179         status = init_dolphin(target_node);

Replace it with this bit of code:

2173 #ifdef DOLPHIN_TEST
2174 #ifdef C1X02_CODE
2175         static const target_node = 8; //DIS_TARGET_NODE;
2176 #else
2177         static const target_node = 4; //DIS_TARGET_NODE;
2178 #endif
2179         status = init_dolphin(target_node);

Basically this was hard coded for use at the site on their test stands.  When starting up, the dolphin adapter would look for a target node to talk to, that could not be itself.  So, all the dolphin adapters would normally try to talk to target_node 12, unless it was the X1X14 front end code, which happened to be the one with dolphin node id 12.  It would try to talk to node 8.

Unfortunately, in our setup, we only had nodes 4 and 8.  Thus, both our codes would try to talk to a nonexistent node 12.  This new code has everyone talk to node 4, except the c1x02 process which talks to node 8 (since it is node 4 and can't talk to itself).

I'm told this stuff is going away in the next revision and shouldn't have this hard coded stuff.

 
Different Dolphin Problem and Fix:

Apparently, the only models which should have pciRfm=1 are the IOP models which have a dolphin connection.  Front end models that are not IOP models (like c1lsc and c1rfm) should not have this flag set.  Otherwise they include the dolphin drivers and causes them and the IOP to refuse to unload when using rmmod.

So pciRfm=1 only in IOP models using Dolphin, everyone else should not have it or should have pciRfm=-1.

 

Current CDS status:

MC damp dataviewer diaggui AWG c1ioo c1sus c1iscex RFM Dolphin RFM Sim.Plant Frame builder TDS
                       
  4044   Sat Dec 11 00:41:55 2010 kiwamuUpdateIOOalignment of IP_ANG is done

  [Jenne, Koji and Kiwamu]

 We finished a coarse alignment of IP_ANG.

 The beam for IP_ANG successfully reached to the ETMY chamber and is ready for the final alignment.

 (Additionally we again tried looking for a resonance for TEM00 in the X arm, but we obtained only flashes of some higher order modes.)


--- what we did

 * installed the steering mirrors for IP_ANG and IP_POS.

 * checked PZT1 if it worked correctly or not. It was healthy.

 * neutralized and realigned PZT1.

 * flipped a window, which is standing before PRM, because the wedged side of the window was at wrong side.

 * realigned PZT2 and checked the spot positions on the TTs.

 * repositioned more carefully the TTs and aligned them to the correct angles.

 * aligned the beam to the center of both the BS and ITMY by rotating the last TT.

 * aligned the beam more precisely by tweaking PZT2 while looking at the spot at the Y end.

         The beam is still hitting the center of ETMY.

 * aligned the steering mirror for IP_ANG while looking at the spot at the Y end.

        In fact IP_ANG is visible with a card. 

 * aligned the BS by looking at the spot on ITMX.

 * covered ETMX with aluminum foil, and made a ~1cm hole on the foil as a target.

         The hole was placed on the center of ETMX.

 * more precisely aligned the BS by looking at the spot on the aluminum foil.

         The spot was clearly visible on CCD monitor.

 * aligned the ITMX by looking at a spot on the foil. The spot represented the beam reflected by ITMX back to ETMX.

 * saw flashes on the foil but couldn't make it TEM00 because it was difficult to see any flashes on the surface of either ETMX or ITMX.

        It means the flashes are visible only when the beam is hitting some scattering surface.

        The mirror surface of the test masses are less lossy than that of the old test masses ??

 

 

  4043   Fri Dec 10 12:55:27 2010 JenneUpdateComputersBackup should be running successfully now

[Joe, Jenne]

The nightly backup of the frames and the /cvs/cds directories is back up and running.  We are free again to do crazy stuff at will, and it will all be saved for eternity.

  4042   Fri Dec 10 11:51:20 2010 OsamuUpdateSUSITM seems bad

20101209_ITMX_drift.png

This graph shows 5 hours data in minute trend for ITMX and ETMX from 5am to 10 am today. ITM pitch drift is 3 times lager than ETM pitch if the OSEM sensitivity is assumed to be the same.

 

20101209_ITMX_2stages.png

This graph is last 1 hour data of above graph in second trend.

It is clealy seen that ITM yaw is jumping between two stages. I guess ITM is something wrong, touching magnets or earthquake stops?

Needs inspection.

 

  4041   Fri Dec 10 11:04:03 2010 OsamuUpdateSUSETM oplev mufunctioning

20101208_ETMX_oplev_sum.png

 

This plot shows ETM oplev and OSEM trend for 10 hours on day before yesterday as almost the same as plot shown this entry. I reported the 10-30minites fluctuations were seen, but I noticed it comes from not suspension but from oplev power fluctuation.

After Kiwamu fixed the ETM OSEM touch yesterday afternoon, still the same trend was seen, so we had thought what we fixed was not enough. This morning I looked at the yesterday's and day before yesterday's trend and noticed the simila trend both the pit and yaw in ETM oplev but not on the OSEM trend. Kiwamu suggested me to put the oplev sum on the same plot. It was!

So, ETMX is not bad, but in fact, still alignment fluctuation exist on the cavity. ITM?

 

  4040   Fri Dec 10 09:58:57 2010 AidanUpdateSUSbeam pointing has been done

Good news. I feel multi-chromatic-locking success is just around the corner.

By the way, there's a new presentation on the DCC from the ANU group where they've locked a short single cavity with both colors - G1000735:

https://dcc.ligo.org/cgi-bin/private/DocDB/ShowDocument?docid=14040

 

 

Quote:

[Koji, Osamu and Kiwamu]

 We aligned the beam axis pointing down to both X and Y arm.

Now the beams are hitting the centers of both ETMX and ETMY.

Amazingly Osamu made X arm flashing by aligning the cavity.


 

  4039   Thu Dec 9 23:17:47 2010 kiwamuUpdateSUSbeam pointing has been done

[Koji, Osamu and Kiwamu]

 We aligned the beam axis pointing down to both X and Y arm.

Now the beams are hitting the centers of both ETMX and ETMY.

Amazingly Osamu made X arm flashing by aligning the cavity.


(what we did)

- opened almost all the chambers except for the MC2 chamber.

- locked and aligned the MC.

   We set Marconi to the right frequency, which had been set to the default values, probably due to the power outage in the last weekend.

   Also we found a DAC cable disconnected from the IO chassis of c1sus. So we connected it in order to damp the MC suspensions.

- aligned MMT2 and PZT2 in order to let the beam go through the center of PRM.

- checked the beam centering at the two TTs (PR2, PR3).

- rotated PR3 to make the beam go through the centers of both ITMY and BS at the same time.

- tried finding the beam spot at the ETMY chamber, and successfully found it.

    To see such faint beam spot, we used an IR viewer.

    In addition to that, we put a large piece of aluminum foil as a screen in the chamber.

- aligned the beam to the center of ETMY by tweaking the PZT mirror (SM2).

- aligned the BS so that the reflected beam at the BS goes through the center of ITMX.

- tried finding the beam spot at the X end, and successfully found it hitting the wall in the chamber.

- aligned the BS in order to let the beam hit the center of ETMX.

- tried aligning ETMX and ITMX to the beam.

Eventually we made the X arm flashing.

However the flash was a bit too weak to completely align the cavity.

 

(plan for tomorrow)

- reinstall some steering mirrors into the BS chamber

- check and neutralize PZT1

- alignment of IP_ANG

 

  4038   Thu Dec 9 22:04:40 2010 kiwamuUpdateSUSRe:strange ETMX suspension

[Koji, Osamu and Kiwamu]

We checked the ETMX suspension and found the UR OSEM was close to the magnet.

So we rotated the UR OSEM so that it won't touch the magnet any more.

We will check the resonant frequencies again by taking the spectra.

--

  In fact the ETMX stacked when we applied a big angular offset to Yaw direction.

This was because that the magnet was actually touching the UR OSEM.

The earthquake stops were fine, they weren't touching the test mass.

Also we looked at the wire and the standoffs, they seemed fine.

Quote: #4036
We are going to inspect the suspension today.

  4037   Thu Dec 9 12:28:52 2010 josephb, alexUpdateCDSThe Dolphin is in (Reflected memory that is)

Setting the Configurations files:

On the fb machine in /etc/dis/ there are several configurations files that need to be set for our dolphin network.

First, we modify networkmanager.conf.

We set  "-dimensionX 2;" and leave the dimensionY and dimensionZ as 0.  If we had 3 machines on a single router, we'd set X to 3, and so forth.

We then modify dishosts.conf.

We add an entry for each machine that looks like:

#Keyword name nodeid adapter link_width
HOSTNAME: c1sus
ADAPTER:  c1sus_a0 4 0 4

The nodeids (the first number after the name)  increment by 4 each time, so c1lsc is:

HOSTNAME: c1lsc
ADAPTER:  c1lsc_a0 8 0 4

The file cluster.conf is automatically updated by the code by parsing the dishosts.conf and networkmanager.conf files.

Getting the code to automatically start:

We uncommented the following lines in the rc.local file in /diskless/root/etc on the fb machine:

# Initialize Dolphin
sleep 2
# Have to set it first to node 4 with dxconfig or dis_nodemgr fails. Unexplai   ned.
/opt/DIS/sbin/dxconfig -c 1 -a 0 -slw 4 -n 4
/opt/DIS/sbin/dis_nodemgr -basedir /opt/DIS

For the moment we left the following lines commented out:

# Wait for Dolphin to initialize on all nodes
#/etc/dolphin_wait
We were unsure of the effect of the dolphin_wait script on the front ends without Dolphin cards.  It looks like the script it calls waits until there are no dead nodes.

In /etc/conf.d/ on the fb machine we modified the local.start file by uncommenting:

/opt/DIS/sbin/dis_networkmgr&

This starts the Dolphin network manager on the fb machine.  The fb machine is not using a Dolphin connection, but controls the front end Dolphin connections via ethernet.

The Dolphin network manager can be interacted with by using the dxadmin program (located in /opt/DIS/sbin/ on the fb machine).  This is a GUI program so use ssh -X when logging into the fb before use.

Setting up the front ends models:

Each IOP model (c1x02, c1x04) that runs on a machine using the Dolphin RFM cards needs to have the flag pciRfm=1 set in the configuration box (usually located in the upper left of the model in Simulink).  Similarly, the models actually making use of the Dolphin connections should have it set as well.  Use the PCIE_SignalName parts from IO_PARTS in the CDS_PARTS.mdl file to send and receive communications via the Dolphin RFM.

  4036   Thu Dec 9 12:24:46 2010 kiwamuUpdateSUSstrange ETMX suspension

[Koji, Osamu and Kiwamu]

We found that the ETMX free swinging spectra showed a strange resonant frequencies.

We are going to inspect the suspension today.

 


(resonant frequencies)

In a ideal case the SOS (Small Optic Suspension) is supposed to have the following resonant frequecies.

(Although we didn't carefully identify which corresponds to which)

  f_POS ~ 0.98 Hz

 f_PITCH ~ 0.66 Hz

 f_YAW ~ 0.8 Hz

 f_SIDE ~ 0.99 Hz

However ETMX showed the following resonant frequencies.

  f_POS ~ 0.91 Hz

 f_PITCH ~ 0.7 Hz

 f_YAW ~ 0.93 Hz

 f_SIDE ~ 1.0 Hz

Especially f_YAW looks pretty high. Also the others are not at the right frequencies.

So we are suspicious that something wrong is happening on the ETMX suspension.

 

ETMX_spectr.png

  4035   Thu Dec 9 11:13:37 2010 OsamuUpdateSUS 

Quote:

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.

20101208_ITMX_jump2.png

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.

In this morning, the same thing happened but to opposit direction when Kiwamu activated ITMX and ETMX. Then it turned out that 1000ct offset was existing on pit of ITMX. Erasing the offset fixed ITMX to normal position.

However a big drift exists in 11hours plot on ITMX 0.1->-0.25 at OLPIT, -580->-605 at SUSPIT and 0.08->0.15 at OLYAW, no significan drift at SUSYAW. On the other hand, ETMX has no big drift but has 10-30minites order fluctuations.

After 6am both the drift and the fluctuation became, roughly saying, 10 times larger, probably due to the human activity.

 

jump_oplev_offset.png

  4034   Thu Dec 9 01:54:15 2010 JenneUpdateElectronicsSome Refl 11 fixes

The Backstory:

Kevin was working on characterizing all of our RF photodiodes for the upgrade, and he discovered that REFL11 didn't work, as described in elog 3890.  Rana was working on fixing it, but then he went off to Japan.

Today's Activities:

I visually inspected the components inside the RF cage on the REFL 11 circuit board inside the PD.  Most of them were okay, but the connection between L5 and C33 (the big tunable inductor and the next capacitor in the path) was totally flaky.  the leg of the inductor had been soldered directly to the trace on the PCB, and the inductor was a little bit tipped over, and pulling the trace off the board.  I wiggled it a little while trying to see what was going on, and the trace broke.  Since there is nothing going on between L5 and C33, just the trace, I used a piece of resistor lead to attach the two.  The connection now seems very robust.  I'm a little worried about the connection between the inductor and the board on the other side, but I can't see it since it's under the inductor itself.

Also, the soldering of L4 (a standard surface mount component type body) to the board seemed totally shoddy.  I was desoldering the first side, and the whole inductor popped off.  It was clear that the inductor was making a physical connection to the board, but not a nice solid electrical connection.  So I resoldered it on.  (On Alberto's schematics, it is listed as a 633nH inductor.  I can't find any of this value, so I just put the same one back on.  The best I could do to confirm the component was still okay was measure its resistance, and compare that to a similar inductor of a similar value.  It seemed okay.)

After that I powered up the PD, and took an electrical transfer function, just to have a look-see.  It seems kind of okay, although the resonance seems to be closer to 13MHz than 11MHz. 

Since we would like to remove the capacitor that is in parallel with the diode itself, which will then change all of the resonant conditions on other components, I didn't worry too much about the resonant peak for tonight.  We're going to have to look in on this though.

Also, I'm leaving the optical check-out for Kevin, so he will let us know if I magically fixed the PD, or if it needs some more work.

Photos of the circuit board (mostly Alberto's mods) before and after I fitzed with it are on Picasa

The Future:

More testing. Probably more fixing.

 

  4033   Thu Dec 9 01:14:42 2010 OsamuUpdateSUS 

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.

20101208_ITMX_jump2.png

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.

  4032   Thu Dec 9 00:34:53 2010 OsamuUpdateSUSITMX oplev Pitch OLTF

We measured Open loop TF for oplev pitch on ITMX.

2010128_01_ITMX_oplev_pit_oltf_fine.jpg

2010128_01_ITMX_oplev_pit_oltf_fine.pdf

 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.

 

  4031   Wed Dec 8 22:47:09 2010 kiwamuUpdateSUSwatchdogs off at ITMX and ETMX

Tonight, swing again.

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

Quote: #4024

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.

 

  4030   Wed Dec 8 22:35:50 2010 kiwamuUpdateSUSoplev installed on ITMX and ETMX

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

  4029   Wed Dec 8 17:05:39 2010 josephbUpdateCDSPut in dolphin fiber between c1sus and c1lsc

[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.

  4028   Wed Dec 8 14:51:09 2010 josephbUpdateCDSc1pem now recording data

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.

  4027   Wed Dec 8 14:46:19 2010 josephb, kiwamuUpdateCDSWhy the ETMX daq channels were not recorded last night

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.

  4026   Wed Dec 8 12:47:18 2010 kiwamuUpdateSUSdiagonalisation of ITMX input matrix

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.

  4025   Wed Dec 8 12:26:56 2010 josephbUpdateCDSmegatron set up - as a test front end

[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.

  4024   Tue Dec 7 20:38:17 2010 kiwamuUpdateSUSwatchdogs off at ITMX and ETMX

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.

  4023   Tue Dec 7 19:34:58 2010 kiwamuUpdateCDSrebooted DAQ and all the front end machines

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.

 

  4022   Tue Dec 7 18:37:15 2010 SureshUpdateSUSETMU05 ready for baking

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.

 

 

  4021   Tue Dec 7 17:19:33 2010 kiwamuUpdateComputerspyNDS available

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

Now the package is living under :

       /cvs/cds/caltech/apps/linux64/python/lib64/python2.4/site-packages

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

Quote: #3722 

3. I installed pyNDS to /cvs/cds/caltech/users/yuta/pynds

  4020   Tue Dec 7 16:09:53 2010 josephbUpdateCDSc1iscex status

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.

  4019   Tue Dec 7 12:12:40 2010 kiwamuUpdateCDSadded some more DAQ channels

[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.

 

ELOG V3.1.3-