40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 209 of 344  Not logged in ELOG logo
ID Date Author Typeup Category Subject
  9000   Mon Aug 12 21:27:03 2013 manasaUpdateCDSc1iscex needs help

I started to modify the c1asx model to reduce the RFM model from hitting its max time.
Instead of bringing in ASS, I have modified ASX to do everything and only the clock signals to ITMX pitch and yaw are now going through RFM. RFM is still hitting 62usec and I suppose that is because of the problems with c1iscex.

c1iscex not happy

Cause and symptoms

While restarting the models, c1iscex crashed a couple of times because of some errors and had to be powercycled. The models were modified and they seem to start ok.
But it looks like there is something wrong with c1iscex since the models were started. The GPS time is off and C1:DAQ-DC0_C1X01_CRC_SUM keeps building up even for c1x01 which was left untouched.

Trial treatments

1. Since c1x01 ans c1spx were not touched,c1scx and c1asx were killed and we tried to start the other models. This did not help.
2. Koji did a manual daqd restart which did not help either.

We are leaving c1iscex as is for the time being and calling Jamie for help.

P.S. While making the models, I had created IPCx_PCIE blocks in c1iscex which do not exist. I changed them to RFM and SHMEM blocks. This did not allow me to compile the model and was only spitting errors of IPCx mismatch. After some struggle and elog search I figured out from an old elog that eventhough the IPCx blocks are changed in the model, the old junk exists in the ipc file in chans directory. I deleted all junk channels related to the ASX model. The model compiled right away.

  9001   Mon Aug 12 23:13:14 2013 JenneUpdateASCPRCL ASS software in place

Quote:

Why POPDC???

 I guess I was thinking that POPDC was a proxy for any type of PRCL lock.  Even if we're sideband locked, there is still some signal in POPDC (although it is very small relative to a carrier lock - ~40cts vs. 1,000cts).  However, as soon as this question was asked of me, I realized that one of the 2f demodulated signals made more sense. 

Since I want the ability to choose between POP110 and POP22, I have put a little 1x3 input matrix before the PRCL lockins in the ASS model.  Since POPDC was already there, I included it as an option in the matrix (in case we ever want to do some PRCL ASS after we have some carrier resonating as well). 

  9002   Tue Aug 13 07:40:53 2013 SteveUpdateCDSc1iscex needs help

 

 Sorrensen ps ouput of +15V at rack 1X9 was current limited to 10.3V @ 2A

Increased threshold to 2.1A  and the voltage is up to 14.7V

Attachment 1: c1iscexSick.png
c1iscexSick.png
  9003   Tue Aug 13 11:04:44 2013 SteveUpdatePEMfluorecent lights

Our fluorecent lights became obsolete.  We'll have change fixtures over to some more energy efficient one. Do you have any recommendation regarding to less noise performer unit?

We may go this direction of LED fluorecent lamps ?

  9007   Tue Aug 13 17:20:54 2013 KojiUpdateCDS[Fixed] c1iscex needs help

c1x01 timing issue was solved. Now all of the models on c1iscex are nicely running.

Symptons

- c1x01 was synchronized to 1PPS in stead of TDS

- C1:DAQ-DC0_C1X01_STATUS (Upper right indicator) was red. The bits were 0x4000 or 0x2bad.
  C1:DAQ-DC0_C1X01_CRC_SUM kept increasing

 - c1scx, c1spx, c1asx could not get started.

Solution

- login to c1iscex "ssh c1iscex"

- Run "sudo shutdown -h now"

- Walk down to the x end rack

- Make sure the supply voltages for the electronics are correct (See Steve's entry)

- Make sure the machine is already shutdown.

- Unplug two AC power supply of the machine.

- Turn off the front panel switch of the IO chassis

- Wait for 10sec

- Turn on the IO chassis

- Plug the AC power supply cables to the machine

- Push the power switch of the realtime machine

  9008   Tue Aug 13 21:09:03 2013 manasaUpdateGreen LockingArms ready for ALS

I aligned both the X and Y end green to the arms.

The transmitted green were aligned at the PSL table green optics to the beat PDs.
Beat notes were retrieved.
 
To do:
1. Check Y arm ALS with previous performance.
2. Troubleshoot X arm ALS.
3. Edit the automation scripts for ALS.
4. Modify ALS model to talk to LSC instead of suspension models.
  9011   Wed Aug 14 08:24:20 2013 SteveUpdateVACpumpdown at day 8

 

 

Attachment 1: pd76md8.png
pd76md8.png
  9013   Thu Aug 15 09:34:12 2013 SteveUpdateGeneralWilcoxon cables rescued

Eric and Steve,

 We removed Wilcoxon Accelerometer PS and Amplifier unit under the BS optical tabel yesterday. The six cabels going to DAQ  were labeled and left in place. Gain setting were 100, except channel 3 was 10.

The ~ 40 m long 2 sets of 3 cables were very happy to get their kinks out. Especially the set going just south of ITMX optical  table.

We have to take better care of these cables! Your data will be useless this way.

Attachment 1: rescuedGraycables.jpg
rescuedGraycables.jpg
Attachment 2: wilconoxOut.jpg
wilconoxOut.jpg
Attachment 3: chanGains.jpg
chanGains.jpg
  9014   Thu Aug 15 12:30:17 2013 manasaUpdateGreen LockingLost beat notes

[Koji, Nic, Manasa]

Update from last night.

Koji and I realigned the green optics on the PSL to start working on the ALS.

We set on a beat note search. We couldn't find the beat note between any of the arm green transmission and the PSL green. All we could see was the beat between the X arm and the Y arm green leakage.

Since we had the beatnote between the 2 green transmission beams, we decided to scan the PSl temperature. We scanned the SLOW actuator adjust of PSL; but couldn't locate any beat note. The search will continue again today.

  9015   Thu Aug 15 19:05:07 2013 manasaUpdateGreen LockingALS out of loop noise

Beat notes were recovered for both the arms.

I locked the arms to IR using PDH and measured the ALS out of loop noise at the phase tracker output.

The Y arm has the same 300Hz/rtHz rms. The X arm rms noise measures nearly the same as the Y arm in the 5-500Hz region (X arm has improved nearly 10 times after the last whitening filter stage change  old elog ).

The noise in the ALSX error signals could be related to the bad alignment and conditions at the X end.

Attachment 1: ALS_OutLoop.pdf
ALS_OutLoop.pdf
  9016   Thu Aug 15 21:42:53 2013 CharlesUpdateISSISS - Schematic + PCB Layout

 After many, many moons of getting to know exactly how frustrating Altium can be, I have completed the PCB layout for my ISS board (final page of ISS_v3.pdf).

Before I get into detail about the PCB, there is one significant schematic change to note: the comparator circuit was changed (with significant help from Koji) so that the voltage reference for boost triggering is established in a more logical way. Instead of the somewhat convoluted topology I had before, now there are only two feedback resistors, R82 and R83. Because their resistances (500k and 50k respectively) are so much larger than the total resistance of the 1k potentiometer (used to establish a tunable threshold voltage), the current flowing through the feedback loop is negligible compared to the 5 mA current flowing through the potentiometer (the pot is rated for 2 W and with 5 mA -> 25 mW dissapation). This allows one to set the threshold voltage for my schmitt trigger, at pin 2 of both the pot and the comparator, entirely with the pot. This trigger also has hysteresis given by the relation deltaV ~ (R83/R82) * (Voh - Vol) where deltaV is the separation between threshold voltages, Voh is the high-level comparator ouput and Vol is the low-level comparator output. Koji simulated this using CircuitLab and I plan to verify the behavior by making a quick prototype circuit.

Now, on to the PCB. The board itself is of a 'standard' LIGO size (11" x 6") has 3 routing layers and 3 internal planes, one for +15 V, one for -15 V and one for GND. In the attached pdf, red is the top routing layer, blue is the bottom layer and brown is the middle routing layer (used for ±5 V exclusively). The grey circles are pads and vias (drilled through) and anything in black is silkscreen overlay. I placed each component and track by hand, attempting to minimize the signal path and following the general rules below,

  • Headers for power, ±5 V and ±15V, are at the back of the board
  • For sections of the board such as filter stages or buffers, resistors and capacitors were grouped around their respective op-amps.
  • As often as was possible, routing was confined to the top layer. Tracks on the bottom layer were placed mostly out of necessity (i.e. no possible connection on top routing layer).
  • The signal generally proceeds from left to right (directions with respect to the attached printout) in the same logical order as on the schematic sheets. Refer to the global sheet (page 1) of the attached "ISS_v3.pdf".
  • External ports such as the PD input, various monitoring ports and panel mounted switches/LEDs were all connected to the board via headers located along the front edge. These are also ordered following the schematic layout.
  • Occasionally, similar signal paths were grouped together although this was a rarity on my board

Sections of the board have been partitioned and labeled with silkscreen overlay to help in both signal pathway recognition as well as eventual troubleshooting.

On the board, I have also included holes so that it can be mounted inside of an enclosure. There is a DCC number printed as well as a 'barcode' (TrueType font: IDAutomationC39S), although they both contain filler asterisks as I haven't published this to the DCC and thus do not have a number.

Attachment 1: ISS_v3.pdf
ISS_v3.pdf ISS_v3.pdf ISS_v3.pdf ISS_v3.pdf ISS_v3.pdf ISS_v3.pdf
Attachment 2: ISS_v3-Power_Reg.pdf
ISS_v3-Power_Reg.pdf
  9017   Fri Aug 16 09:35:18 2013 SteveUpdateVACVacuum Normal state recognition is back

Quote:

Quote:

Quote:

Quote:

Apparently all of the ION pump valves (VIPEE, VIPEV, VIPSV, VIPSE) opened, which vented the main volume up to 62 mTorr.  All of the annulus valves (VAVSE, VAVSV, VAVBS, VAVEV, VAVEE) also appeared to be open.  One of the roughing pumps was also turned on.  Other stuff we didn't notice?  Bad. 

 Several of the suspensions were kicked pretty hard (600+ mV on some sensors) as a result of this quick vent wind.  All of the suspensions are damped now, so it doesn't look like we suffered any damage to suspensions.

CLOSE CALL on the vacuum system:

Jamie and I disabled V1, VM2 and VM3 gate valves by disconnecting their 120V solenoid actuator before the swap of the VME crate.

The vacuum controller unexpectedly lost control over the swap as Jamie described it. We were lucky not to do any damage! The ion pumps were cold and clean. We have not used them for years so their outgassing possibly  accumulated to reach ~10-50 Torr

I disconnected_ immobilized and labelled the following 6 valves:  the 4 large ion pump gate valves and VC1,  VC2  of the cryo pump. Note: the valves on the cryo pump stayed closed. It is crucial that a warm cry pump is kept closed!

This will not allow the same thing to happen again and protect the IFO from warm cryo contamination.

The down side of this that the computer can not identify vacuum states any longer.

This vacuum system badly needs an upgrade. I will make a list.

 While I was doing the oil change of the roughing pumps I accidentally touched the 24 V adjustment knob on the power supply.

All valve closed to default condition. I realized that the current indicator was red at 0.2A  and the voltage fluctuated from 3-13V

Increased current limiter to 0.4A and set voltage to 24V     I think this was the reason for the caos of valve switching during the VME swap.

 

 Based on the facts above I reconnected VC1 and VC2 valves.  State recognition is working.  Ion pumps are turned off and their gate valves are disabled. 

We learned that even with closed off gate valves while at atmosphere  ion pumps outgass hydrocarbons at 1e-6 Torr level.  We have not used them for this reason in the passed 9 rears.

 

I need help with implementing V1 interlock triggered by Maglev failure signal  and-or P2 pressure.

MEDM screen agrees with vacuum rack signs.

Attachment 1: VacuumNormal.png
VacuumNormal.png
Attachment 2: vacValvesDisabled.jpg
vacValvesDisabled.jpg
  9018   Fri Aug 16 13:25:50 2013 KojiUpdateASSASX model/screen cleaning up

[Koji Manasa]

Yesterday we cleaned up the ASX model and screens to have more straight forward structure of the screen
and the channel names, and to correct mistakes in the model/screens.

The true motivation is that I suspect the excess LF noise of the X arm ALS can be caused by misalignment
and beam jitter coupling to the intensity noise of the beat. I wanted to see how the noise is affected by the alignment.
Currently X-end green is highly misaligned in pitch.

- Any string "XEND" was replaced by "XARM", as many components in the system is not localized at the end table.

- The name like "XARM-ITMX" was changed to "XARM-ITM". This makes easier to create the corresponding model for the other arm.

- There was some inconsistency between the MEDM screens and the ASX model. This was fixed.

- A template StripTool screen was created. It is currently saved in users/koji/template as ASX.stp.
  It will be moved to the script directory once it's usefulness is confirmed.


The next step is to go to the end table and manually adjust M2 mirror while M1 is controlled by the ASX.
The test mass dithering provides the error signal for this adjustment but the range of the PZT is not enough
to make the input spot position to be controlled. In the end, we need different kind of matching optics
in order to control the spot position. (But is that what we want? That makes any PZT drift significantly moves the beam.)

  9019   Fri Aug 16 19:36:49 2013 CharlesUpdatePSLPMC_trans Channel

Rana and I connected the PMC_trans output to the BNC connector board on the west end of the PSL table (the channel is labeled). I took a few spectra off of PMC_trans and the SR785 was connected directly to the PMC_trans output for about an hour.

Data will follow.

  9020   Fri Aug 16 21:15:04 2013 ranaUpdateCDSNew/old CDS laptop for X-End

I took the "aso-laptop" and made it into Ubuntu a couple months ago. Today I added it to the Martian network and then moved it to the X End.

I followed the instructions in (https://wiki-40m.ligo.caltech.edu/Network) and added it to the files in /var/named/chroot/var/named on linux1 and did the "service named restart".

The router already had his MAC address in its list (because Yoichi was illegally using his personal laptop on the Martian). The new laptop's name is 'asia'. This is a legal name according to our computer naming conventions and this Wikipedia page (http://en.wiktionary.org/wiki/Category:Italian_female_given_names). It has been added to the Name Pool on the wiki.

The terminal on the laptop still calls itself 'aso-laptop' so I need some help in fixing that. It successfully connects to 40MARS and displays a MEDM sitemap after sshing in to pianosa.

I use 'ssh -X -C' since I find that compression actually helps when the laptops are so far from the router.

  9023   Sun Aug 18 20:07:41 2013 ranaUpdateComputer Scripts / Programsuserapps SVN up

JoeB and JamieR are working somewhat coherently on a set of python libraries to fulfill all of our command line CDS wants. This is being done mostly to satisfy The Guardian and the SkunkTools project.

I did an 'svn up' in /opt/rtcds/userapps (it might finish in ~1000 years) to get the things that they have so far (in particular, Joe's 'pyavg'). There's going to be some issues since the pylib stuff written by Yuta/Kiwamu has never been integrated with anything and is imported as 'epics' in many python scripts. As we move over to the new stuff there will be a lot of broken script functions since the new libraries are also used in that way.

  9024   Mon Aug 19 07:53:48 2013 SteveUpdateSUSETMX damping restored

ETMX sus damping restored

  9025   Mon Aug 19 09:36:32 2013 KojiUpdateGreen LockingXend green aligned

[Rana Koji]

This is an elog about the activity on Friday night.

- The X arm green beam was aligned with assist of the ASX system.

- M1 PZT alignment was swept while M2 PZT was under the control of ASX.

- Everytime M1 was touched, M2 was restored by manual alignment so that the REFL beam hits the center of the REFL PD.
  This way we could recover the lock of TEM00. Once TEM00 is recovered, ASX took care of the alignment of M2

- The error signal used by the cavity dither did not give us a good indication where the optimal alignment is.

- Thus the best alignment of M1 had to be manually scanned. The resulting maximum green transmission was ~0.88

- Once the beam was aligned, the out-of-loop stability of the Xarm was measured.
  There has been no indication of the improvement compared to Manasa's measurement taken before our beam alignment.

Attachment 1: ALS_OUTOFLOOP_130816.pdf
ALS_OUTOFLOOP_130816.pdf
  9026   Mon Aug 19 09:54:13 2013 SteveUpdatesafetyMasayuki receives safety training

Masayuki Nakano, a student of Seiji's from ICRR / U Tokyo, is visiting us here at the 40m lab for the next couple months.

He received 40m specific basic safety training this morning.

  9029   Mon Aug 19 11:12:54 2013 SteveUpdateVACRGA scan at day 13

 

 

Attachment 1: rgaScan13d.png
rgaScan13d.png
  9030   Mon Aug 19 11:30:20 2013 JenneUpdateIOOMC mirrors' ASC has non-zero inputs

[Masayuki, Jenne]

When I came in this morning, I noticed that the Mode Cleaner had not been locked for at least the past 8 hours.  We moved the MC SUS sliders until the MC SUSPIT and SUSYAW values for each mirror were back to approximately the place they were the last time the MC was nicely locked (~12 hours ago).  This got the MC flashing TEM00, so we thought we were doing well. 

However, if the servo was enabled, any time the cavity flashed a small-order mode (especially 00), the mirrors would get super kicked.  Not good

We went to investigate, and discovered that the RFPD aux laser was left on again.  We turned that off, however that didn't fix the situation. 

Manasa suggested checking that the WFS were really, really off.  When we looked at the WFS master screen, we noticed that although the WFS servos were off, the MC mirrors' ASC filter banks had non-zero inputs.  We checked, and this is not from the MCASS, nor is it from the MC WFS lockins.  At this point, I have no idea where these signals are coming from.  I have turned off the ASC outputs for all the MC mirrors (which means that we cannot turn on the WFS), and the MC locks fine

So, we need to know where the ASC signals are coming from.  There isn't anything that I can see, from any screen that I can find, that indicates some signals being sent over there.  Has anyone done anything lately?  I know Koji was working on IPC stuff the other day, but the MC was locking fine over the weekend until yesterday afternoon, so I suspect that's not the culprit. 

I have turned off the outputs of the WFS lockins, as part of my turning things off, so if whatever script needs them doesn't enable them, they should be turned back on by hand.

  9031   Mon Aug 19 14:22:36 2013 ranaUpdateGreen LockingXend green aligned

  9032   Mon Aug 19 15:23:07 2013 KojiUpdateIOOMC mirrors' ASC has non-zero inputs

[Jenne, Koji]

This disturbance in the MC ASC channels were fixed.

This craziness happened ~10pm last night. Was there any action at the time? >> Sunday-night workers? (RXA: No, Nakano-kun and I left before 9:30 PM)

We found that the signals came from c1ioo. However, restarting, recompiling c1ioo and c1mcs didn't help
to clean up this issue. Just in case we cleaned up the corresponding entries in the ipc file /opt/rtcds/caltech/c1/chans/ipc/C1.ipc
and recomplied c1ioo and c1mcs because these are the channels we touched last week to mitigate the timing out issue of c1rfm.

Incidentally, we fell into a strange mode of the RCG: IOPs could not restart. We ended up running "sudo shutdown -r now"
on each machine (except for c1lsc which was not affected by this issue). This solved the issue.

Even now c1oaf could not be running properly. This is not affecting the IFO operation right now, but we need to look into this issue again
in order to utilize OAF.

  9033   Mon Aug 19 16:18:56 2013 manasaUpdateGreen LockingXend green aligned

ASX scripts for PZT dither have been fixed appropriately. Script resides in scripts/ASX.

You can run the scripts from the ASX medm screen now.

  9034   Mon Aug 19 17:40:32 2013 SteveUpdateGreen LockingXend green layout corrections

 Shutter moved, no more clipping.

Pick-off mirror 2" replaced by 1" one. Laseroptik HR 532nm, incident angle 30-45 degrees, AR 532 nm

Green REFL PD moved to 4" close to pick-off mirror. Pd being close to pick-off does not separate multiple reflections on it. I'll replace Laseroptic mirror with Al one. It is not easy to find.

 Hole cut into side wall for doubler oven cable to exit.

 

 

Attachment 1: beforeC.jpg
beforeC.jpg
Attachment 2: nowC.jpg
nowC.jpg
Attachment 3: stillMultiple.jpg
stillMultiple.jpg
  9035   Mon Aug 19 19:08:35 2013 KojiUpdateGreen LockingXend green layout corrections

- An Aluminum mirror instead of 2" unknown mirror for the pick-off for the rejected beam from the green faraday isolator (Steve)
=> Replaced. To be reviewed

- Faraday mount replacement. Check what we have for the replacement. (Steve)

- The green REFL PD should be closer to the pick-off mirror. (Steve)
=> Moved. To be reviewed

- A beam dump should be placed for the green REFL PD

- Move the green shutter to the place where the spot is small (Steve)
=> Moved. To be reviewed.

- The pole of the PZT mounting should be replaced with a reasonable one. (Steve with Manasa's supervision)

- Tidying up doubling oven cable. Make a hole on the wall. (Steve)
=> Done. To be reviewed.

- Tidying up the PZT cabling (Steve)

- The optics are dirty. To be drag wiped. (Manasa, Masayuki)

  9036   Mon Aug 19 23:08:31 2013 JenneUpdateLSCDRMI sensing signals

Here are a bunch of sensing signals.  The configuration is always DRMI.  Except for the optic noted in the title and the x-axis of any individual plot, other optics are held in their nominal position.  DRMI condition is sidebands resonant in PRCL, 55MHz sideband resonant in SRCL.  Each plot has an error signal, as well as the 2f signals at POP and AS.

 The phases of POP22 and POP110 have been adjusted so that the I signal is maximized when everything is at the nominal positions (sideband resonant for PRMI).  The phase of AS110 has been adjusted so that the I signal is maximized when the DRMI is in the nominal position (f2 resonant in SRC).  The phases of the 1f1, 1f2, 2f1 and 2f2 REFL signals were all adjusted to have max PRCL signal in the I phase.  AS55 was adjusted to have max SRCL signal in the Q phase.

 DRMI_PRM_REFL11I.png

DRMI_PRM_REFL33I.png

DRMI_PRM_REFL55I.png

DRMI_PRM_REFL165I.png

DRMI_MICH_REFL11Q.png

DRMI_MICH_REFL33Q.png

DRMI_MICH_REFL55Q.png

DRMI_MICH_REFL165Q.png

DRMI_SRM_REFL55Q.png

DRMI_SRM_REFL165Q.png

DRMI_SRM_AS55Q.png

 

  9037   Tue Aug 20 00:19:23 2013 ranaUpdateLSCPRMI / DRMI investigations

While Jenne was plotting, I locked and aligned the MICH with AS55_Q. Then I aligned the PRM and locked PRMI using REFL55_I/Q with triggering on POP22, but no power normalization.

I used this to set the phase for REFL11 and REFL55 (driving PRM at 111.3 Hz and minimizing the Q response using the DTT Sine Response tool). I flipped the sign on REFL11 by 

The REFL11 gain is ~50x larger than REFL55; this is with the 15 dB whitening gain on REFL55 and none for REFL11. What's going on here? The attached PDF shows the two time series with the free swinging PRMI and both phases set to ~ +/- 2 deg. The REFL55 signals have been scaled up by 50x.

So then we went in and looked at the RF signals at the demod boards. To do this we disconnected the RFPD test cables and hooked the RF Mon outputs into the 50 Ohm inputs on a scope. The following PNG images show the scope traces. The REFL11 (yellow) traces are too big!! See how small the REFL55 (green) are. REFL11 is saturating - need to fix.

TEK00000.PNGTEK00001.PNG

TEK00002.PNGTEK00003.PNG

Attachment 1: REFL.pdf
REFL.pdf
Attachment 6: REFL-2.pdf
REFL-2.pdf
  9038   Tue Aug 20 01:28:47 2013 JenneUpdateLSCREFL investigations

According to the wiki, REFL 11 has a transimpedance of 4.08kV/A, and REFL 55 has a transimpedance of 615V/A.  This is a ratio of ~6.5 .  My optickle simulations from earlier this evening indicate that, at maximum, there is a ~factor of 2 more signal in REFL 11 than REFL 55.  This is a factor of order 10-15.  Then, REFL 55 has 15dB whitening gain, which is a factor of ~4.  So, this explains why we're seeing so much more digital signal on REFL11 than REFL55.

Tomorrow, I need to replace the 50/50 beam splitter that splits the beam between REFL55 and REFL11 (33 and 165 have already had their light picked off at this point).  I want to put in a 10% reflector, 90% transmission beamsplitter.  Steve, can you please find me one of these, and if we don't have one, order one? This will give us a little more light on 55, and less light on 11, so hopefully we won't be saturating things anymore.

 

  9039   Tue Aug 20 10:59:15 2013 SteveUpdateGreen LockingXend green layout corrections

Quote:

 Shutter moved, no more clipping.

Pick-off mirror 2" replaced by 1" one. Laseroptik HR 532nm, incident angle 30-45 degrees, AR 532 nm

Green REFL PD moved to 4" close to pick-off mirror. Pd being close to pick-off does not separate multiple reflections on it. I'll replace Laseroptic mirror with Al one. It is not easy to find.

 Hole cut into side wall for doubler oven cable to exit.

 

 

 Beam trap for Pd refl is in place. Cabeling is ti·died up.

 Laseroptic 1" mirror is replaced by Al 1" mirror. Problem remains the same. This diffraction patter has to be coming from the Faraday.

  Atm1, good separation when Pd is far 

  Atm2, bad separation when Pd is close 

Attachment 1: faraway.jpg
faraway.jpg
Attachment 2: closer.jpg
closer.jpg
  9040   Tue Aug 20 11:41:30 2013 KojiUpdateLSCREFL investigations

As I always tell everyone: Don't use a 10% reflector which produce ghost beams. Use a 90% reflector.

  9041   Tue Aug 20 11:52:20 2013 JenneUpdateLSCREFL investigations

Quote:

As I always tell everyone: Don't use a 10% reflector which produce ghost beams. Use a 90% reflector. 

 Hmmm, yes, I forgot (bad me).  I'll find a 90% refl BS, and swap the positions of REFL11 and REFL55.

  9043   Tue Aug 20 18:42:57 2013 JenneUpdateLSCREFL investigations

I have done the swap in the REFL path.  First, I swapped the positions of REFL11 and REFL55.  Then, I swapped out the 50/50 BS for a 90% reflection BS.  (90% goes to REFL55, 10% goes to REFL11).  I also changed the aluminum dump that was dumping the old REFL165 path into a razor dump.

Before: REFL11 had 4.0mW, REFL55 had 3.1mW.  Now, REFL11 has 0.53mW, and REFL55 has 6.9mW.  REFL165 still has around 61mW of light, and REFL33 has 3.3mW (the things that were changed were after 165 and 33 in the REFL path). 

Now, the DC value of the REFL PDs are:  REFL165 = 10.4V, REFL33 = 110mV, REFL55 = 232mV, REFL11 = 18.6mV. 

As I was finishing aligning the beams onto all of the REFL diodes, Manasa asked for the IFO so she and Masayuki could continue their work on the Xarm, so I'll check the signals acquired a little later.

  9046   Wed Aug 21 19:26:19 2013 ranaUpdateIOOFound the cause of mysterious MC motion

Quote:

Yes, this was not ELOG'd by me, unfortunately. This was the MC tickler which I described to some people in the control room when I turned it on.

As Koji points out, with the MCL path turned off this injects frequency noise and pointing fluctuations into the MC. With the MCL path back on it would have very small effect. After the pumpdown we can turn it back on and have it disabled after lock is acquired. Unfortunately, our LOCKIN modules don't have a ramp available for the excitation and so this will produce some transients (or perhaps we can ezcastep it for now). Eventually, we will modify this CDS part so that we can ramp the sine wave.

 I've written a new TICKLE script using the newly found 'cavget' and 'cavput' programs. They are in the standard epics distribution as extension binaries. They allow multichannel read/write as well as ramping, delays, incremental steps, etc. http://www.aps.anl.gov/epics/tech-talk/2012/msg01465.php.

Running from the command line, they seem to work fine, but I've left it OFF for now. I'll switch it into the MC autolocker at some point soon.

  9048   Wed Aug 21 23:50:40 2013 KojiUpdateSUSPRM SUS_LSC violin (FM5) set to correct frequency

[Jenne Koji]

It seems that the PRM violin mode freqs shifted from 625-ish to 640Hz.
The peaks rang up because of the servo.

Once the notch freq was shifted to 640Hz, the violin mode started to decay.

ellip("BandStop",4,1,90,636,644) gain(1.12202)

  9049   Thu Aug 22 02:40:12 2013 JenneUpdateLSCDRMI Locked for 1+ minute!!!!!!

[Jenne, Koji]

The DRMI has been locked!!  And at least one time, it was for more than one minute!! 

DRMI_First_Lock_1plusMinute_21Aug2013.png

We are not 100% sure yet that it's correctly sideband locked.  The test of this was to put a 50% BS in front of the AS camera (so after the beam has gone to AS55), and send the light over to a PDA10CF Thorlabs PD.  I locked the Michelson on carrier for the alignment of this diode.  Then I strung a cable to the control room, and plugged it into the RF spectrum analyzer.  (First, I had turned off the green beat PD power, so there wasn't any RF stuff on the line that I unplugged).  It's hard to watch the screen and a tv / dataviewer at the same time, so I've taken a video, so that we can see the nicely locked round DRMI beam on the AS camera, and the spectrum analyzer.  My phone is working very hard at uploading the video, but we may have to wait until tomorrow for that.  However, I think that we're locked on the 55MHz sideband. (Also, maybe I'm too tired or excited or something, but how do you make the real cameras take video??)

EDIT:  Video uploaded.  Pause the video at 10 seconds, and you'll see that we've got a strong 110MHz peak!!  Hoooray!  The TV in the upper right side of the video is AS.  You can see as we flash, the peaks go up and down.  When there's no resonance, the 110 peak goes away. (Ex., when I'm PRMI locked on the sideband, there isn't a visible peak).

 

Alignment procedure was as normal:  Lock and align the arms. Misalign ETMs. Check that MICH fringes look good (ASS does a nice enough job that I don't actually lock and align the Michelson anymore).  Restore the PRM.  Lock PRMI.  Tweak PRM alignment to maximize POP110I.  At this point, Koji and I played a little with the PRMI, but when we finished with that, we restored the SRM, and tweaked its alignment by making nice overlap on the AS camera.

Then, we tried some DRMI settings, started seeing some locks, and played a bit with trying to optmize the settings that we have. 

DETAILS:

PRMI settings: 

PRCL ASC is on (with loop triggering).  MICH gain = -0.8, PRCL gain = +0.05.  FM4, FM5 always on, FM2 triggered.  Loop and filter module triggering on POP22I.  No power normalization.  MICH and PRCL locked on REFL55 I&Q, with 1's in the LSC input matrix.  PRCL actuating on PRM with +1, MICH actuating on BS with +0.5, PRM with -0.267. 

I took transfer functions between REFL55 I&Q and REFL11 I&Q, to determine the relative gains and signs.  REFL11I's gain should be -18dB relative to REFL55I, with the opposite sign.  We tried PRMI locking with MICH = 1*REFL55Q and PRCL = -0.125*REFL11I for the input matrix.  Still no power normalization (we haven't used power norm at all today, so I'll quit writing that).

I took transfer functions between REFL55 I&Q and REFL33 I&Q.  REFL33I's gain is -8dB relative to REFL55I, but they have the same sign.  We tried locking PRMI with MICH = 1*REFL55Q and PRCL = +0.6*REFL33I.  Success.

Next up, some Optickle simulations, to help us go in the right direction for DRMI locking.  I checked the signs of the error signals REFL55I (PRM sweep), REFL11I (PRM sweep) and REFL55Q (MICH sweep) in both PRMI and DRMI configurations.  For all of these cases, the signs were the same (i.e. no sign flips needed to happen for DRMI locking, relative to PRMI locking).  I checked the sensing matrices for DRMI and PRMI for those same signals, and took the ratios of the sensing matrix elements.  This gave me the ratio of optical gains for each error signal, in the DRMI case vs. PRMI case, so any servo gain changes should be the inverse of these numbers.  These numbers are all DRMI/PRMI:  REFL55I PRCL response = 0.76, REFL11I PRCL response = 0.99, REFL55Q MICH response = 18.  So, when trying to lock the DRMI, we wanted to keep the gains for PRCL about the same, reduce the servo gain for MICH by a factor of ~20, but keep the same signs for everything.

In doing that, we started seeing some short DRMI locks, so we twiddled some parameters (mostly the elements in the LSC input matrix) a bit.  We eventually settled on:  PRCL = -0.125*REFL11I, MICH = 0.1*REFL55Q, and SRCL = 1.0 * REFL55I.  The output matrix was the same (MICH pushing on BS and PRM, PRCL on PRM), with the addition of a +1 in the SRCL -> SRM element.  For all 3 degrees of freedom (PRCL, MICH, SRCL), FMs 4 and 5 were always on.  For PRCL, FMs 2,3,6 were triggered to come on after 0.5 seconds of delay.  The PRCL FM triggers helped enormously.  I tried several other things, including changing the MICH input matrix element up and down in value, changing the SRCL input matrix element up and down in value, and engaging triggering for a few different filters in the MICH and SRCL degrees of freedom.  However, none of these made things better, and several made things worse.  Most notably, for SRCL, engaging triggering for FMs 2 and 3 kicked the cavities out of lock, which implies that perhaps our gain isn't high enough yet (and thus our UGF isn't very high yet).  I changed FM1 of SRCL to be +3dB of gain (from +10dB), and it would live through that coming on (trigger delayed by 1 sec, then ramping up over 1 second), but within a second after the filter finishing coming on, the cavity would fall out of lock (not violently kicked, just not locked anymore). 

At this point, we were trying to figure out a way to confirm what kind of lock we had.  I checked Optickle again, and we do not expect to see a significant change in POP110I between the PRMI and DRMI cases, so that isn't a useful check.  We dreamed of having our AS110 demod board, or the AS OSA set up, but neither of those was going to happen tonight.  Instead, Koji suggested hooking up the PD, and looking directly at the output. 

To-do:  Set up the AS OSA.  Also, perhaps temporarily borrow the 110 demod board from POP.  We were triggering on POP22 tonight, and that seemed to work okay.

 

 

  9050   Thu Aug 22 07:57:57 2013 LisaUpdateLSCDRMI Locked for 1+ minute!!!!!!

  Very nice!!  I was wondering, shouldn't the driving matrix be such that MICH pushes on SRM as well?

  9051   Thu Aug 22 10:20:32 2013 kiwamuUpdateLSCDRMI Locked for 1+ minute!!!!!!

Wonderful ! I like the video -- the spatial mode looks pretty clean and much cleaner than what I observed in the old days.

  9052   Thu Aug 22 13:03:40 2013 JenneUpdateLSCDRMI Locked for 1+ minute!!!!!!

Quote:

  Very nice!!  I was wondering, shouldn't the driving matrix be such that MICH pushes on SRM as well?

 Hmmm, yes, that's a very good point.  I think you're right, and I'll give that a try today.

  9053   Thu Aug 22 13:20:54 2013 KojiUpdateLSCDRMI Locked for 1+ minute!!!!!!

Don't go for a hacky solution. We want to climb a staircase step by step.
Prepare an independent 110MHz demod ports.

Quote:

To-do:  Set up the AS OSA.  Also, perhaps temporarily borrow the 110 demod board from POP.  We were triggering on POP22 tonight, and that seemed to work okay. 

 

  9055   Thu Aug 22 21:16:47 2013 ManasaUpdateGreen LockingGTRY normalized

The Y arm green transmission has been measuring in counts all along. I modified the gain in the ALS-TRY filter module to normalise the transmission.

Transmission has been normalised with GTRY = 1 corresponding to 600 counts. 

  9056   Thu Aug 22 22:05:36 2013 ranaUpdateGreen LockingGTRY normalized

Meh. 600 counts is too weak.  You should fix the electronics so that the maximized green laser transmission gives more like ~10000 counts.

  9057   Fri Aug 23 01:52:34 2013 JenneUpdateSUSViolin filters moved to LSC, from SUS

[Rana, Jenne]

We were meditating a little bit on what may be the story behind the PRM violin filter situation.  We locked the PRMI, and turned on and off the violin filters.  We noticed, very bizarrely, that when the violin filters were ON, the servos would oscillate.  Weird.  Also, probably because the oscillation was causing us to hit the limit we have in the MICH servo, we rung up a 3rd harmonic of one of the violin modes, which was at 1955 Hz. 

We took a transfer function of the PRCL servo, saw that the UGF was 300 Hz, and lowered it to ~180 Hz.  After later investigations, that high-ish UGF probably wasn't a problem.  Anyhow, we then took MICH servo transfer functions, and saw some very weird stuff. 

At frequencies where we had violin filter notches, we were seeing peaks in the transfer function, which came close to touching, or crossed the 0dB line!  We suspect that this may have something to do with the balancing of the drives to the optics, since we have PRCL driving PRM, but MICH driving BS and PRM.  What we did was move the violin filter notches into the LSC model.  There were already SUS filter banks in the LSC model (right side of the LSC screen).  In preparation for the DRMI, I have put the BS violin notches into the BS, PRM and SRM filter banks, as well as the PRM and SRM filters into all 3 banks.  Right now for PRMI, I have the BS and PRM notches (as well as the Vio3 notch) turned on in both BS and PRM.  All of the violin-related filters are turned off in the LSC filter bank inside the SUS models.  When we did this, the servo oscillations no longer are excited when we turn on the notches, and when we take a new transfer function, there are no longer weird peaks at the notch frequencies.  More meditation needs to be done.

Also, for the violin3 filter, Rana noted that at 1955 Hz, after we confirmed that the REFL 55 phase was set correctly (and we're using REFL 55 I&Q for PRMI locking), the I-phase had a response of 0.36, while the Q-phase had a response of 0.20.  I should be able to think about these numbers, and decide if the vio3 is for the BS or the PRM violin mode.

 MICHloopNotches_23Aug2013.pdf

the above series of Bode plots shows the MICH Open Loop Gain as the REFL55 phase is adjusted (PURPLE, ORANGE) with the notches in the SUS and then (RED) as the notches are moved to the LSC and made the same for all optics.

In other news, I have the parts that Jamie ordered to make a new 110 demod board, so that's one of my daytime activities now, so we can have both POP110 and AS110.

  9058   Fri Aug 23 14:19:28 2013 ranaUpdateSUSViolin filters moved to LSC, from SUS

  Just to rephrase somewhat:

  • We balance the BS & PRM actuators in the LSC Output matrix so that there is no MICH signal going into REFL_I @ 100 Hz.
  • REFL Phase is adjusted by driving PRM and minimizing Q/I to within ~1 deg (Q/I ratio of ~2%)
  • The REFL_I sensing matrix element is ~50x bigger than REFL_Q (in W/m)
  • When we turn ON the violin mode notch in the BS SUS, it changes the MICH drive into a purely PRCL drive at that frequency !!!
  • So, putting notches into the SUS screens is bad since it imbalances the drives.
  9060   Sat Aug 24 00:11:07 2013 KojiUpdateLSCDRMI Locked with improved lock streatches

Friday night locking

Much more stable DRMI lock was achieved, partly thanks to the Friday-night quiet seismic,
and partly because of the improved servo gain and LF boosts


55MHz thru-put

I wanted to confirm the enhancement of the 110MHz signal at the AS port.

As the AS110 PD is placed in the CCD path, there is nothing visible with PRMI.
The Thorlabs PD was moved to the main AS path. Now the AS110 PD is receiving 50% of the power.
 

With PRMI 110MHz peak was -30dBm (As it was fluctuating, anything more precise number did not make sense)
When the DRMI was locked, the peak was enhanced to 0dBm.

The 2f signal comes from the beat between the sidebands.
Thus the amplitude of the intensity is proportional to the power of the sidebands (assuming the +1 and -1 order sidebands have the same amplitude)
-30dBm -> 0dBm means 31.6 times amplitude of the intensity. Therefore the amplitude transmission of the sidebands is 5.6 times more. (Is this true?)

According to the wiki, the AS port thru-put (i.e. power transmission) for the 55MHz sideband is 0.0026 and 0.43 for PRMI and DRMI respectively.
This corresponds to the amplitude difference of ~13. So we still have only half of the sidebands leaking out from the IFO. This could be attributed
to both the smaller PR gain and SR gain.


Locking setup

Same as the one Jenne used the other day. Later I engaged several additional triggers.
The following is the trigger setting I used

MICH: Delay 2 sec, FM1/FM2/FM3/FM6/FM7

PRCL: Delay 0.5 sec, FM2/FM3/FM6

SRCL: Delay 5 sec, FM1/FM2/FM3/FM6

SRCL FM1 was modified from +3dB to +6dB


Lock stability

Once lock is acquired, it lasts tens of minutes. (see the attached striptool chart.)
Even the lock is lost, it reacquires quickly.

The videos to show the lock acquisition and the in-lock stability are attached below.
The AS port beam is very round. It is not so shaky, but some yaw motion is visible.
The mode at the AS port is defined by the SRM, putting a QPD at the AS port would help to
stabilize the spot.


IFO state upon leaving

I left the 40m with the arms aligned, PRM and SRM slightly misaligned, and LSC setting is for the DRMI locking.


TO DO

- AS110I/Q for triggering

- PRCL/MICH/SRCL normalization

- We should resurrect the IFO config scripts.

- Remove BS->SRCL actuation coupling

- Handing off to 3f signals (preparation for the full lock)

- Improve ALS stability

- SRM ASC: AS QPD for SRM control


Lock Acquisition Video
UL (REFL) / UR (POP)
LL (AS) / LR (PRM Face)

 
In-lock video
UL (REFL) / UR (POP)
LL (AS) / LR (PRM Face)

 

Attachment 1: Screenshot-Untitled_Window.png
Screenshot-Untitled_Window.png
  9061   Sun Aug 25 06:07:11 2013 ranaUpdateLSCDRMI Locked with improved lock streatches

 We're ready for using the auto configure.

We can put our scripts for the MICH, PRMI, and DRMI into the IFO CONFIGURE screens for now and then it should be easy to get them into the Guardian once Jamie has the bugs worked out.

This screen can also be used to setup and start the dither alignment for each configuration (once we have one working for DRMI / SRM).

Also, now that the notches/bandstop filters for the violin modes have been move from the SUS into the LSC, we should fix the triggering to engage them a few seconds after the boosts.

  9063   Mon Aug 26 18:59:08 2013 MasayukiUpdateLSCLSCoffset script updated

I made scripts/LSC/LSCoffsets2.py which is the script to zero the dark offset of all the LSC PD.  The list of PDs is same as the list in scripts/LSC/LSCoffsets. New script average all outputs of PDs parallelly, so we can zero the offsets much faster.

You can define the averaging time, and you can choose the channel for getting the dark offset from INMON or OUT16. You should know that if you use OUT16 channel, the effect of the unwhite filter is not taken into account.

Example usage (at scripts/LSC):

   ./LSCoffsets2.py -d 20 --out16

you can find the help by calling this script with option -h or --help

  9064   Mon Aug 26 19:13:38 2013 KojiUpdateLSCLSCoffset script updated

What do you mean???

What is the effect of the anti-whitening filter?

Quote:

You should know that if you use OUT16 channel, the effect of the unwhite filter is not taken into account.

 

  9065   Mon Aug 26 19:31:22 2013 manasaUpdateSUSPRM, ITMY watch dogs

PRM and ITMY were found with their watchdogs shutdown this afternoon (cause unknown). I re-engaged them.

  9066   Mon Aug 26 19:54:15 2013 manasaUpdateCDSc1als model modified

I had made changes to the c1als model a couple of weeks ago. I had removed all the beat_coarse channels that had existed from pre-phase tracker era.

Also, I forgot to elog about it then. This dawned on me only when I found that c1als isn't working the way it should right now.

mistake-cartoon.gif

ELOG V3.1.3-