40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
 40m Log, Page 13 of 339 Not logged in
ID Date Author Type Category Subject
16994   Tue Jul 12 19:46:54 2022 PacoSummaryALSHow (not) to take NPRO PZT transfer function

[Paco, Deeksha, rana]

Quick elog for this evening:

• Rana disabled MC servo .
• Slow loop also got disengaged.
• AUX PSL beatnote is best taken with *free running lasers* since their relative frequency fluctuations are lowest than when locked to cavities.
• DFD may be better to get PZT transfer funcs, or get higher bandwidth phase meter.
• Multi instrument to be done with updated moku
• Deeksha will take care of updated moku
2   Thu Oct 18 14:52:35 2007 ranaRoutineASCtest
test

X-(:P;(:))
168   Wed Dec 5 18:08:36 2007 AndreyUpdateASCOptical Lever laser for ETMX is installed

A new laser with \lambda=633nm has been intalled and the mirror adjusted so that the signal hits the center of the photodetector.

Output power level of that laser is 3.45 +- 0.05 mW.

Only about 0.29mW hits the photodetector.

Cable clips have been used to firmly fix the power supply cable for the laser.

See attached photopicture of the ETMX - "oplev" - optical - table.
Attachment 1: DSC_0199.JPG
253   Tue Jan 22 13:11:03 2008 tobinUpdateASCETMY oplev recentered
The light wasn't even on the diode.
469   Thu May 8 01:50:25 2008 ranaSummaryASCArm Cavity HOM Resonances
Nothing new, but I calculated the frequencies of the first 22 higher order transverse modes and thought I might as well list them here.

To do this I took formula (23) from page 762 of Siegmans book and put it into this form:
         f_fsr
dfmn =   ----- * (m+n) * acos(sqrt(g1*g2))
pi

and then calculated them from m+n = 1..22 (22 is not a magic number).

I also used the 'mod' function of matlab to calculate the frequency mod FSR so that we would know how far away
from a cavity resonance it is. I took as parameters: Larm = 38.55 m, Ritm = 1e6 m, Retm = 57.1 m. Kirk measured
the arm length some time ago; we need to measure the arm g-factor...maybe we'll put Tobin on this when he comes
by for a visit.

1.1936 (TEM01, TEM10)
2.3871
3.5807
0.8859 (TEM22, TEM13, TEM31)
2.0795
3.2730
0.5782
1.7718
2.9654
0.2706 (TEM55, ...)
1.4641
2.6577
3.8512
1.1564
2.3500
3.5436
0.8488
2.0423
3.2359
0.5411
1.7347
2.9282
1178   Fri Dec 5 01:58:58 2008 YoichiConfigurationASCtdscntr.pl now works at 40m
Tobin gave me the perl version of tdscntr some time ago.
Pinkesh and I modified and tested it at LHO.
I further modified it today and now it runs fine on the linux machines at the 40m. I haven't tested it with the Solaris machines.
My modifications include changing channel names to 40m ones, and using tdsavg to get QPD data rather than ezcaread.
The use of tdsavg is intended to avoid aliasing problem.
tdscntr.pl is installed in /cvs/cds/caltech/apps/linux/tds/bin

Now, the alignX runs on linux up to the centering of the QPDs.
However, ezcademod seems to behave wrongly on linux. I plan to investigate on this problem tomorrow.
1210   Thu Jan 1 00:55:39 2009 YoichiUpdateASCAlignment scripts for Linux
A Happy New Year.

The dither alignment scripts did not run on linux machines because tdscntr and ezcademod do not run
on linux. Tobin wrote a perl version of tdscntr and I modified it for 40m some time ago.
Today, I wrote a perl version of ezcademod. The script is called ditherServo.pl and resides in /cvs/cds/caltech/scripts/general/.
It is not meant to be a drop-in replacement, so the command line syntax is different. Usage is explained in the comment of the script.

Using those two scripts, I wrote linux versions of the alignment scripts.
Now when you call, for example, alignX script, it calls alignX.linux or alignX.solaris depending on the OS of
In principle, ezcademod is faster than my ditherServo.pl because my script suffers from the overhead of
calling tdsdmd on each iteration of the servo. But in practice ditherServo.pl is not that bad. At least, as far as
the alignment is concerned, the performances of the both commands are comparable in terms of the final arm power and the convergence.

Now the alignXXX commands from the IFO Configure MEDM screen work for X-arm, Y-arm, PRM and DRM. I did not write a script for Michelson, since
it is optional.
I confirmed that "Align Full IFO" works correctly.
1237   Mon Jan 19 13:58:53 2009 YoichiUpdateASCBetter ditherServo.pl
Nick Smith (@LHO) tested the ditherServo.pl at Hanford.
He added options to specify exit conditions to the script. Now you can make the script exit when
a condition, such as ArmPower > 1.0, is satisfied, or let it wait until a certain condition is satisfied.

I also modified the script to use ezcastep instead of tdswrite for feedback actuation.
The script now runs ezcastep in the background while the next iteration of the tdsdmd is performed.
Instead of kicking mirrors with a big thrust each time by a single tdswrite command, ezcastep gently moves the mirrors with fine steps.
I also implemented this "background ezcastep" technique in Tobin's tdscntr.pl.

The alignment scripts run smoother now.
1412   Fri Mar 20 12:07:19 2009 YoichiConfigurationASCETMY beam centering
I forgot to put this in the elog.
Last Sunday night, I centered the beam on the ETMY because it was too low.
To do so, I wrote scripts (beamCenterETMY-P and beamCenterETMY-Y) to continuously align the Y-arm while I'm moving the beam on the end QPD.
These scripts will continuously do the dithering servo and QPD centering in one direction (pitch for beamCenterETMY-P, yaw for the other).
So if you move the steering mirror in front of the end QPD, the servo will eventually move the beam spot on the ETM.
I centered the beam just by looking at the camera image.
No coupling measurements from Pitch/Yaw to length was done.
1595   Sun May 17 21:45:40 2009 robUpdateASCITMX oplev centered
2105   Fri Oct 16 16:08:00 2009 robConfigurationASCloop opened on PZT2 YAW at 3:40 pm

I pushed the "closed loop" button on PZT2 YAW around 3:40 pm today, then roughly recentered it using the DC Offset knob on the PiezoJena controller and the IP ANG QPD readbacks.  There was a large DC shift.    We'll watch and see how much it drifts in this state.

2107   Fri Oct 16 18:46:36 2009 ranaConfigurationASCloop opened on PZT2 YAW at 3:40 pm

 Quote: I pushed the "closed loop" button on PZT2 YAW around 3:40 pm today, then roughly recentered it using the DC Offset knob on the PiezoJena controller and the IP ANG QPD readbacks.  There was a large DC shift.    We'll watch and see how much it drifts in this state.

Here's the trend.

The transient at ~22:40 is Rob switching to 'Open Loop' on the Piezo Jena PZTs. I don't see any qualitative change in the drift after this event.

At 05:55 UTC, I removed an iris that was blocking the IP POS beam (the sum goes up from 2 to 6.5) without disturbing the mirrors who's oplev beam are on that table. Steve has conceded one sugar Napoleon after betting against my ninja-like iris skills.

We should recenter the beam on IP POS now that its unclipped - I'll let it sit this way overnight just to get more drift data.

Attachment 1: Untitled.png
2109   Sun Oct 18 16:09:34 2009 ranaConfigurationASCloop opened on PZT2 YAW at 3:40 pm

I wanted to see how long our IP POS beam has been badly clipped - turns out its since April 1, 2007.

Steve's April Fool's joke is chronicled then. The attached trend shows that the drop in IP POS is coincident with that event.

In trying to align IPPOS, I noticed that someone has placed a ND2.0 filter (factor of 100 attenuation) in front of it. This is kind of a waste - I have removed IPPOS to fix its resistors and avoid this bad optic. Also the beam coming onto the table is too big for the 1" diameter optics being used; we need to replace it with a 2" diamter optic (Y1-2037-45P).

IP ANG dropped by a factor of 2 back in early August of '08.

We need this guy on the investigation:

Attachment 1: a.png
2205   Sun Nov 8 22:50:29 2009 AlbertoUpdateASCIFO Alignment

Tonight I aligned the IFO by running the scripts one by one.

SRC was far off and I had to align SRM by hand before the script could work. SPOB is still low when DRM is aligned.

I'm restoring the full IFO now that I'm taking off.

3191   Mon Jul 12 02:21:01 2010 KojiConfigurationASCResurrection of MC WFS

I have resurrected the MC WFS on Friday night.
I have uncommented the WFS part of the MC autolocker.
The WFS total gain was empirically set to 0.1 such that the loops have no instability.

The loops somewhat worked through the weekend although they seemed to have the drift of the operating points
in accordance with the WFS spot.

4087   Wed Dec 22 15:30:47 2010 OsamuUpdateASCETMY oplev fixed

According to c1scy.mdl, OL signals should be connected to adc_0_24 to adc_0_27 but they were connected to adc_0_16 to adc_0_19 which are assigned to QPD signals.

Actually cable connections were messed up. One ribbon cable was connected from QPD driver and ADC ports assigned for OL, and another ribbon cable was connected from the board combining the signals of oplev and QPD to ADC port assigned for QPD.

Now ETMY oplev is working well and aligned to center.

4280   Sun Feb 13 16:50:17 2011 kiwamuUpdateASCIP_ANG was at wrong ADC

I found that the ADC channels for IP_ANG had been assigned to a wrong machine.

IP_ANG is supposed to be acquired at c1auxey (east end), but actually it had been at c1auxex (south end).

This is the reason why we couldn't see any signals from IP_ANG.

So I fixed it by editing the db files (i.e. ETMXaux.db and ETMYaux.db). Now it seems working fine.

This mistake obviously came from the X-Y name swapping business. Something else might be still wrong.

4287   Mon Feb 14 12:37:23 2011 kiwamuUpdateASCno signal from IP_ANG_Seg1

It turns out there are no reasonable signal from the segment 1 on the IP_ANG QPD.

For right now I can still use it as a funny QPD, but I absolutely need somebody to check and fix it in a daytime.

 Quote: IP_ANG is supposed to be acquired at c1auxey (east end), but actually it had been at c1auxex (south end). So I fixed it by editing the db files (i.e. ETMXaux.db and ETMYaux.db). Now it seems working fine.

4294   Tue Feb 15 02:13:16 2011 kiwamuSummaryASCa daytime task : small signals on ETMX OL

Rana and I found that the QPD for the optical lever at X end are showing small signals.

At this moment each of the segments exhibits approximately 200 counts when the oplev beam is centered.

These small numbers may be due to the coating of ETMX, but we are not sure.

Probably we have to increase the gain of the QPD depending on situations.

So a set of the tomorrow's daytime task is:

1. check the trend data of the QPD outputs to see how much signals were there in the past.

2. check the whitening filters to make sure if it's on or off.

3. If it's necessary, increase the gain of the QPD to have reasonable readouts.

4295   Tue Feb 15 03:10:37 2011 kiwamuUpdateASCIR beam alignment for Xarm : TRX reduction

I tried aligning the IR beam axis for the X arm to have good beam centering on ITMX and ETMX.

As a first attempt, I started translating the beam upward by steering PZT1 and PZT2, since the pitch was quite off from the center on ITMX.

As a result I could decrease the pitch off-centering down to about 0.5 mm on ITMY, but on the other hand TRX decreased a lot (by a factor of 4).

I am worrying if something in the central part of IFO might be clipping the beam.

(notes)

When I was touching PZT1 and PZT2, I payed attention on IP_ANG so that I don't lose a beam spot on IP_ANG.

As long as the beam is on the IP_ANG QPD, the angle of the beam should not be so much different.

Each time after I touched the PZTs, I realigned ITMX and ETMX to maximize the transmitted light.

In this way I proceeded the alignment by changing the PZT offsets little by little while keeping the X arm locked always.

At the beginning, all the PZT offsets were zero. And at the end of this work they became:

C1:LSC-PZT1_Y = 1.880

C1:LSC-PZT2_Y = -1.699

But during this alignment work TRX gradually decreased eventually down to 0.25, which had been 1 at the beginning (TRX is calibrated by dividing it by its maximum power).

Along with this TRX reduction, I found that the optical gain also decreased by a factor of about 5.

This fact has been confirmed by intentionally increasing the filter gain such that the servo oscillates at the UGF.

 Quote: The amounts of the X arm's beam off-centering have been measured by the A2L technique.      - ETMX          PIT  = -1.61 mm          YAW =  -0.918 mm     - ITMX          PIT = -3.76 mm         YAW = -2.24 mm

4296   Tue Feb 15 06:15:07 2011 SureshUpdateASCno signal from IP_ANG_Seg1

[Valery, kiwamu, Jenne, Suresh]

I first interchanged the two QPD's on the Y end table to see if the problem QPD related.  Exchanging the units did not make any difference.  The problem therefore had to be in the cables or the circuit boards in 1X4

We traced the signals pertaining to the IP_ANG QPD ( "Initial Pointing Beam") using  Jay's wiring diagram (pages 2 and 5 of 7).  We noted that while the signals were available on all Segments till the Monitors (Lemo) on 1X4-2-2A card, two of the lines did not reach the output of the cross connect 1X4-B8.  We checked card to make sure that the signals were indeed reaching the back plane of the 1X4-2 chassis using a D990612 extension board.  The card was found to be okay.  We therefore suspected that the cable (CAB_1X4_?) going from the card to the cross connect 1X4-B8 was faulty.  Indeed visual inspection showed that the crimping of the connector was poor and weight of the cable had put further strain on the crimping.

I changed the 64-pin connector on the 1X3-2-2A side of the cable.

When I connected everything back together the problems persisted. Namely the lines P1-1A  (Segment 1 high) and P1-2C (Segment 2 Low) were floating They were not reaching points 2T and 3T respectively on the output of the cross connect.

I therefore replaced 1X4-B8 with a similar unit which I found in one of the shelves along the East (Y) arm.

I then checked with the StripTool to make sure that all the quadrants are showing similar response to a flashlight on the QPD.   All Segments are working fine now. Currently the IR Initial Pointing beam reaches the QPD but is not centered on it.

I did not attempt to center it since the beam appeared to be clipped and may anyway require repositioning.

JD: We need to meditate on where this beam could be getting clipped.  Suresh and I checked that it's not on the viewport on the beam's way out of the ETMY chamber by seeing that the beam is far away from the edges of the viewport, and also far away from the edges of the black beamtube between the viewport and the table.  Suresh mentioned that the clipping nature of the IP_ANG beam sometimes goes away.  I don't know if this is the same clipping that Kiwamu might be seeing with the main beam, or if this is separate clipping just with the IP beam, after it's been picked off.  I suspect it's the same as what Kiwamu is seeing....maybe when we move PZT1, we clip on one of the MMT mirrors or PZT2??  If this is true, it's a total pain since we might have to vent if we can't steer around it.

4306   Wed Feb 16 02:04:11 2011 kiwamuUpdateASCIR beam alignment

[Jenne and Kiwamu]

This time we aligned the vertical angle (not the translation) of the IR beam so that the transmitted light from BS shoots the center of ETMY.

The idea is to use ETMY as a beam pointing reference instead using IP_ANG, assuming the translation is not so bad.

As a result it looks like we are wining. A quick A2L test on ITMX_PITCH showed a small off-centering at sub-milimeter level.

We are concluding that the initial beam after PZT2 had been pointing downward somehow.

Before doing this whole job, we checked the spot shape on IP_POS to see if the beam is clipped or not. It was a round shape, which means no clipping around MMT.

But on the other hand, the spot on IP_ANG had been clipped more than half of its bottom as Suresh reported on his elog (see here).

I found that this clipping is able to be fixed by moving the beam angle upward. I guess the clipping happened at one of the steering mirror in the ETMY chamber.

According to these information, we imagined that the beam was somehow pointing downward after PZT2.

So we started aligning the beam by touching only PZT2 for vertical direction. Then we found a beam spot on ETMY's suspension frame, and brought it to the center.

Then we aligned BS and X arm for this new beam axis. The it resulted a small off-centering on pitch.

Once the MC fully gets back, we will examine the TRX degradation with this configuration.

4355   Fri Feb 25 01:48:54 2011 valeraUpdateASCmc auto alignment status

I made several scripts to handle the mcass configuration and sensing measurements:

- The scripts and data are in the scripts/ASS directory

- The mcassUp script restores the settings for the digital lockins: oscillator gains, phases, and filters. The MC mirrors are modulated in pitch at 10, 11, 12 Hz and in yaw at 10.5, 11.5, and 12.5 Hz. The attached plot shows the comb of modulation frequencies in the MCL spectrum.

- The mcassOn and mcassOff scripts turn on and off the dither lines by ramping up and down the SUS-MC1_ASCPIT etc gains

- The senseMCdecenter script measures the response of the MCL demodulated signals to the decentering of the beam on the optics by imbalancing the coil gains by 10% which corresponds to the shift of the optic rotation point relative to the beam by 2.65 mm (75mm diameter optic) and allows calibration of the demodulated signals in mm of decentering. The order of the steps was MC1,2,3 pitch and MC1,2,3 yaw. The output of the script can be redirected to the file and analyzed in matlab. The attached plot shows the results. The plot was made using the sensemcass.m script in the same directory.

- The senseMCmirror script measures the response of the MCL demodulated signals to the mirror offsets (SUS-MC1_ASCPIT etc filter banks). The result is shown below (the sensemcass.m script makes this plot as well). There is some coupling between pitch and yaw drives so the MC coils can use some balancing - currently all gains are unity.

- The senseMCdofs scripts measures the response to the DOF excitation but I have not got to it yet.

- The next step is to invert the sensing matrix and try to center the beams on the mirrors by feeding back to optics. Note that the MC1/MC3 pitch differential and yaw common dofs are expected to have much smaller response than the other two dofs due to geometry of this tree mirror cavity. We should try to build this into the inversion.

Attachment 1: mcditherlines.pdf
Attachment 2: mcdecenter.pdf
Attachment 3: mcmirror.pdf
4673   Tue May 10 00:31:28 2011 kiwamuUpdateASCIFO alignment plan

The alignment of the interferometer goes basically step by step.

Tuesday will be an alignment day.

0. MC beam centering (it's done)

1. F2P to balance the coils on every optics including BS, PRM, SRM, ITMs and ETMs (Kiwamu).

2. A2L and then change the DC bias of ITMY and ETMY to get a perfect eigen axis (VF/Jamie).

3. align input PZT mirrors (PZT1 and 2) to maximize the Y arm transmission (VF/Jamie).

4. do the same things for X arm but using BS instead of the PZTs.

5. Alignment of the central part.

6. Make a script to automatically get those things done.

4684   Wed May 11 00:23:21 2011 kiwamuUpdateASCY arm and beam pointing alignment

[Jamie / Valera / Kiwamu]

The incident beam pointing was improved a lot by using C1ASS realtime code.

Some more details will be posted later. The below is the list of the highlights today.

- The Y arm cavity was aligned to have good beam centering on the mirrors.

- The input PZTs were also aligned to the aligned Y arm by hand.

- Automation of the  Y arm alignment using C1ASS_LOCKIN got partially functional with two loops closed. C1ASS correctly servos the centering on ETMY

- The amount of the off-centering on ITMY and ETMY look roughly within 1 mm.

- As a result the intracavity power got bigger by a factor of about 3.5

4769   Mon May 30 23:14:27 2011 valeraUpdateASCY arm initial alignment

I closed all 8 dither loops for the Y arm initial alignment: 2x2 centering servo (this worked before) and 2x2 input beam servo for both pitch and yaw.

So far it looks pretty good - the error points go to zero and the arm power goes up to 1.

The offloading to the alignment biases and the PZTs is not yet automated.

Today the PMC, MC, and Y arm were very cooperative and a pleasure to work with.

4883   Sat Jun 25 04:40:43 2011 SureshUpdateASCWFS1 Transimpedance measurement

### WFS1 Transimpedance

The attached plots show the location of the ~29.5 MHz pole and the 59 MHz notch for each quadrant of the WFS1 Sensor head.

 WFS1 Pole (MHz) Z(Ohms) Notch (MHz) Z(Ohms) Q1 28.89 598 60.38 0.83 Q2 29.20 513 57.70 0.57 Q3 29.63 681 59.63 0.89 Q4 28.89 609 58.13 0.78

As may be seen from the above table, these frequencies will need to be adjusted in some cases.

From the plots we can see that, when there is no attenuation set on the attenuator AT65-0263 (ref D990249-A),  the MAX4107  oscillations are seen in Q2,Q3,Q4 quadrants at around 200 MHz.

Rana suggested, from his previous encounter with this circuit, that the solution is to remove the second MAX4106 and the attenuator on the RF line to avoid this oscillation.

A look at the circuit board shows that some of the inductors have not been mounted.  That explains the presence of only one notch though the schematic shows two.

5062   Fri Jul 29 16:25:06 2011 kiwamuUpdateASCbeam axis and Y arm aligned

Last night I aligned the incident beam axis and the Yarm by touching the PZT mirrors and the suspensions.

I didn't estimate how good they were aligned, but I guess the Y arm is now ready for the Y green light.

Next : Y green alignment and the MC spots measurement / alignment.

++ Motivation ++

Prior to the coming vent we want to have the Y arm, incident beam axis and Y green light aligned so that we can align some necessary optics in the chamber.

Also alignment of the incident beam will allow us to re-position the incident beam alignment monitor (i.e. IPPOS and IPANG).

Our plan was to first align the Y arm using the ASS system and then align the Y green light to the Y arm.

++ what I failed ++

First I was trying to measure the spot positions on the MC mirrors to make me sure the beam axis has/hasn't changed.

Also I was going to align the MC suspensions to have nice spot position on each suspension using the MCASS system

because this will help us checking the beam clearance in the Faraday and perhaps re-positioning of the Faraday during the coming vent.

But essentially I failed and eventually gave up because MCASS didn't work. It seems that MCASS needs some modifications in the scripts.

Then, to make me feel better I moved on to the Y arm and beam axis alignment.

++ what I did ++

I tried using C1ASS to align the incident beam and suspensions on the Y arm, but it didn't work.

However the drive signals from ASS and its demodulated signals looked fine. Only the feedback did not work correctly.

Every time I enabled the feedback paths, the arm just lost the lock. Something is wrong in the feedback paths.

Then I started to align the cavity by my hands while looking at the demodulated signal from each LOCKIN module.

I aligned the things until each demodulated signal fluctuates around zero.

At the end the beam spots on the ETMY and ITMY camera looked well-aligned and the transmitted light became larger by a factor of 2ish.

5067   Sat Jul 30 06:24:06 2011 kiwamuUpdateASCY arm ASS fixed

The servos of C1ASS for the Y arm and the beam axis alignments were fixed.

Now we can correctly run the Y arm ASS from the C1IFO_CONFIGURE window as usual.

The sign of some control gains had been flipped for some reasons, so I changed them to the correct signs.

Next : Health-check for the X arm ASS, the loss measurements.

 Quote from #5062 I tried using C1ASS to align the incident beam and suspensions on the Y arm, but it didn't work.

5068   Sat Jul 30 07:07:28 2011 kiwamuUpdateASCMCASS status

Since we will measure (and hopefully adjust) the spot positions on the MC suspensions prior to the vent, MCASS is necessary for it.

#######################

Here is the MCASS status so far:

+ Valera worked on MCASS on the last February, and basically no progress after he left.

+ The MCASS model had been completed in C1IOO.mdl.

+ He made some useful scripts, including mcassup, mcassOn/Off, senseMCdecenter, senseMCmirrro and senseMCdofs.

Summary of those scripts can be found in his entry #4355.

+ We haven't closed the MCASS loops.

+ The control filters are still blank.

+ We haven't put any elements on the input and output matrices.

+ Some parameters for the dithering oscillators and demodulation systems were properly set.

So we can get the demodulated signals by simply running mcassUp and mcassOn. (This essentially corresponds to the A2L measurement.)

+ The PIT motions are driven at 10, 11 and 12 Hz for MC1, 2 and 3 respectively. For YAW, the frequencies were chosen to be 11.5, 12.5 and 13.5 Hz.

+ Some medm windows were prepared but not as refined as that of ASS.

+ Valera performed a measurement of the spot positions by using MCASS. The results are summarized in #4660.

+ We made an estimation about the beam clearance on the Faraday based on the measured spot positions (#4674)

#########################

So, it seems we should be able to at least measure the spot positions soon by using his scripts.

5073   Sat Jul 30 21:04:23 2011 kiwamuUpdateASCY arm ASS fixed

The X arm ASS was also fixed. So both X and Y arm ASS are now back to normal.

Now we can align the arms any time from the buttons on the C1IFO_CONFIGURE window.

(notes)

The reason why the servo didn't work was that the sign of some control gains had been flipped.

This was exactly the same situation as that in the Y arm ASS (#5067).

 Quote from #5067 The servos of C1ASS for the Y arm and the beam axis alignments were fixed.

5083   Mon Aug 1 17:47:37 2011 steveUpdateASCwhat is not working

SUS-ETMY_QPD is not responding. It is reading zero in dataviewer and 4,400 counts on QPD MEDM screen.......must be wrong cable connected

IP-POS is sick. Last time alive 7-19-2011

IP-ANG beam is clipping on pick-up mirror at ETMY chamber. This will have to be fixed at the vent. The qpd itself is responding to light.

5374   Sat Sep 10 01:36:15 2011 kiwamuUpdateASCinterferometer coarsely aligned

The interferometer was coarsely aligned.

Now spatially overwrapped DRMI and FP arm fringes are visible on the AS camera although the incident beam alignment was done only with PZT2.

All the DC biases were saved so that we can go back to this condition any time.

/***** some health checks *******/

[FINE] IPPOS : it looks okay but the spot on the QPD is a little bit too low by a few mm.

[NOT GOOD] IPANG : maybe hitting a post or something because the spot is vertically split into two. The spot is too low.

[FINE] POX/POY/POP : they all are coming out. POP is visible with an IR viewer.

[FINE] REFL :  no clipping but the beam looks a little bit too low relative to the CCD camera.

[FINE] AS : no clipping and the spot position on the AS camera looks fine.

[FINE] Green beams : both X and Y beams are successfully landing onto the PST table without no clipping.

[FINE] Suspensions : all of them are reasonably quiet without the oplevs, which is good.

5518   Thu Sep 22 13:56:56 2011 kiwamuUpdateASCC1ASS : status update

The output matrix in the C1ASS servo were coarsely readjusted and the servos seemed working.

However it is difficult to say the servo is very good or so-so,

because the ETMY suspension moves a lot and hence the cavity eigen axis moves a lot too.

(to do)

+ optimization of the ETMY oplevs and OSEM damping.
+ evaluation of the performance of the C1ASS with a good damping.

(Background)

Since we have installed the new mid-HV amplifier for the PZT1 mirror (#5450) it changed the response of the PZT1 (gains from EPICS to the actual angles).
Therefore the C1ASS output matrix needs be adapted to the new PZT1 response.

(What I have done)
What I was measuring was a coupling from each PZT mirror to both beam angle and beam position by looking at the output from the LOCKINs.
So this measurement eventually gives us a nicely diagonalized output matrix by inverting the coupling.
However the measurement turned out to be difficult because the ETMY moved too much.
In fact the cavity eigen axis also moves and the fluctuation was larger than the intentionally introduced beam angle/translation offsets, which are for the coupling measurement.

Instead of measuring the couplings, I put some numbers into the matrix based on a guess.
Since the PZT1 HV amp became weaker than that of PZT2, the elements in the output matrix should be amplified by some number.
Right now the PZT1 amp can drive the mirror in a range of -5 -30 V with EPICS range of +/-10 counts, and for PZT2 it is about 0 -150V with EPICS range of +/-5 counts.
So the difference of the responses in unit of V/counts is about 8.5.
The PZT1 elements in the matrix were multiplied by this number and I became able to close the servos.

 Quote from #5455 + Modification of C1ASS (Kiwamu)

5543   Mon Sep 26 12:41:27 2011 kiwamuUpdateASCC1ASS : status update

 Quote from #5518 (to do)  + optimization of the ETMY oplevs and OSEM damping.  + evaluation of the performance of the C1ASS with a good damping.

The servo for aligning the Y arm is working fine with the coarse gain coefficients.

However then I found the ASS_Xarm servo was not healthy.

So the next step is to refine the X arm servo in C1ASS.

(some notes)

+ With the ETMY oplev the Y arm became quieter after we recovered the oplev whitening filter (#5523)

+ The Y arm alignment scripts can be run from the usual C1IFO_CONFIGURE screen.

It will servo the spot positions on ITMY and ETMY, and align the input beam pointing. It brings the Y arm power to about 1.

+ The X arm servo is doing something funny. It doesn't bring the arm power up to 1.

I thought the X arm didn't need any modifications because the X arm servo doesn't include PZT1 and PZT2.

So it maybe a simple bug (for example, some switches are disable and so on)

5574   Thu Sep 29 03:43:20 2011 kiwamuUpdateASCwrong channel assignment on IPPOS

The channels for IPPOS had been assigned in a wrong way.

Because of this, C1:ASC-IP_POS_X_Calc corresponds to the actual vertical motion and C1:ASC-IP_POS_Y_Calc is for the horizontal motion.

We should fix the database file to get the correct vertical/horizontal corrdinate.

5578   Fri Sep 30 01:18:39 2011 kiwamuUpdateASCC1ASS : status update

Now the C1ASS servos are working fine.

However at the end of the scripts sometimes it changes the DC force (e.g. C1:SUS-ITMX_PIT_COMM and so on) by a wrong amount.

So for this bug, it misaligns the suspensions a lot. I will take a look at the script tomorrow.

 Quote from #5543 However then I found the ASS_Xarm servo was not healthy.

5605   Mon Oct 3 17:57:12 2011 kiwamuUpdateASCIPPOS fixed

The input matrix of IPPOS were fixed so that the horizaontal motion correctly shows up in X and the vertial is Y.

(what I did)

+ The data base file, QPD.db, were edited.

QPD.db is a part of the c1isxaux slow machine and it determines the input matrix for deriving the X/Y signals from each quadrant element.

+ The previous input matrix was :

X = (SEG1 + SEG4) - (SEG2 + SEG3)

Y = (SEG1 + SEG2) - (SEG3 + SEG4)

+ The new matrix which I set is :

X = (SEG1 + SEG2) - (SEG3 + SEG4)

Y = (SEG1 + SEG4) - (SEG2 + SEG3)

The new matrix is a just swap of the previous X and Y.

+ Then c1isxaux was rebooted by :

telnet  c1iscaux

reboot

+ The I did the burt restore it to this morning.

 Quote from #5574 The channels for IPPOS had been assigned in a wrong way.

5817   Sat Nov 5 00:04:23 2011 kiwamuUpdateASCASS scripts gone

Did somebody delete all the scripts in /opt/rtcds/caltech/c1/scripts/ASS ?

5818   Sat Nov 5 00:24:13 2011 SureshUpdateASCASS scripts gone

 Quote: Did somebody delete all the scripts in /opt/rtcds/caltech/c1/scripts/ASS ?

I have moved all the MC_ASS scripts to a directory called MC under ASS

5821   Sat Nov 5 14:54:59 2011 KojiUpdateASCASS scripts gone

In any case, the daily backup of the scripts are found in /cvs/cds/caltech/scripts_archive

Quote:

 Quote: Did somebody delete all the scripts in /opt/rtcds/caltech/c1/scripts/ASS ?

I have moved all the MC_ASS scripts to a directory called MC under ASS

6288   Thu Feb 16 09:59:16 2012 steveUpdateASCIP- ANG

Initial pointing or IP-ANG is a pointing monitor of the MC. This beam is launched after the second  pzt  steering mirror.

IP-ANG  is missing the pick up mirror by a few inches at ETMYchamber

1000 days plot show last appearance in Feb 2010

Attachment 1: lastIPang.png
6979   Tue Jul 17 02:17:50 2012 JenneUpdateASCASS gains wrong?
I was checking on the ASS system, and I think that the gains on some of the loops may not be correct. An old symptom was that the commands in the script were not being executed when we changed over to Ubuntu. Now it seems that each command is working fine, but the loops are pushing the optics more out of alignment than anything. I flipped the sign on some of the loops and it helped, others it didn't. I need to measure some transfer functions and meditate on what they should look like. It will be really nice to have the alignment system working again.
7389   Fri Sep 14 18:15:43 2012 ranaUpdateASCFirst In Vac Picture

Looks good. Any way that you can tell in an unambiguous way, where the beam is, is very good. Ideally we want to have1-2 mm accuracy.

7790   Wed Dec 5 03:25:32 2012 DenUpdateASCdithering

I wanted to center beams on the XARM cavity mirrors using c1ass model. I've run XARM setup script and then turned dithering on. Cavity went out of lock because calculated offsets were incorrect.

I was using TRX only and calculated rotation phases for ITM and ETM pitch and yaw. For this I've added a low pass filter into Q-quadrature bank and made DC value at the output to be zero by adjusting the phase. I've put gains (+1 or -1)  in the I quadrature such that output was positive.

Then I've set the sensing matrix to identity as I decided to deal with separate loops. Of coarse, they are mixed by the cavity, but at least in the control system they are distinguished. Old matrix summed error signals in one degree of freedom from both mirrors. This makes more sense but still not precise because coils are not ideally diagonalized.

Then I've adjusted gains for control loop for every degree of freedom. I've ended up with (0.1; 0.1; 0.1; -0.1). I did not use large gains as I wanted slow convergence because of the demodulation low-pass filter time response constant of 20 sec. Coupling (I quadrature) was reduced from (0.9, 0.3, 2.4, 1.2) to zeros (0-0.1) in ~5 minutes, TRX increased from 0.73 to 0.90.

There is one thing that I do not understand yet. I think controllers should minimize angle -> length coupling that is proportional to I-quadrature if phase is correct. But phase depends on alignment and when the feedback loops are on, phase drifts. I could see it during my measurement. But I did not find any script that smoothly tunes phase such that coupling is all in I-quadrature. I guess this is not hard to set a gradient descent algorithm that minimizes DC value of Q-quadrature. Or how this is usually done?

7979   Thu Jan 31 22:14:11 2013 ranaSummaryASCOptics lit

Gouy not Guoy:

http://www.rp-photonics.com/gouy_phase_shift.html

pronounced Goo-eee, with the emphasis on the second syllable.

7982   Fri Feb 1 12:22:27 2013 ZachSummaryASCOptics lit

It's OK; even Siegman got it wrong---48 times.

RA: NO, stil not OK.

 Quote: Gouy not Guoy: http://www.rp-photonics.com/gouy_phase_shift.html pronounced Goo-eee, with the emphasis on the second syllable.

8459   Thu Apr 18 02:24:58 2013 DenUpdateASCdither alignment of yarm

I modified our existing c1ass model to include alignment of input steering TT1 and TT2 for YARM and BS for XARM. Corresponding medm screens are also created.

## Dithering:

ETM_PIT: frequency = 6 Hz, amplitude = 100 cnts
ETM_YAW: 8 Hz, 400 cnts
ITM_PIT: 11 Hz, 800 cnts
ITM_YAW: 14 Hz, 1200 cnts


These values were chosen by looking at cavity transmission and length signals - excitation peaks should be high enough but do not shake the optics too much.

## Demodulation:

LO for each degree of freedom is mixed with cavity length and transmission signals that are first bandpassed at LO frequency. After mixing low-pass filter is applied. Phase rotation is chosen to minimize Q component

 ETM_PIT_LENGTH 0 ETM_YAW_LENGTH 20 ITM_PIT_LENGTH 0 ITM_YAW_LENGTH -25 ETM_PIT_TRANS -5 ETM_YAW_TRANS 10 ITM_PIT_TRANS 10 ITM_YAW_TRANS -30

## Sensing matrix:

8 * 8 matrix was measured by providing excitation at 0.03 Hz to optics and measuring the response in the demodulated signals. Excitation amplitude was different for each optics to create cavity transmission fluctuations of 25%

 -0.0373333 -0.010202 -0.018368 0.0042552 0 0 0 0 0.0432509 -0.209207 0.0139471 0.0780632 0 0 0 0 0.0483903 -0.0077304 0.00917147 0.000860323 0 0 0 0 -0.0751211 0.699778 -0.0115889 -0.09944 0 0 0 0 0.356164 0.121226 0.0690162 -0.0183074 -59.52 -21.9863 -30.9437 13.5582 -0.141744 1.15369 -0.0100607 -0.12914 -18.8434 -105.828 -48.213 14.8612 -0.0446516 0.00682156 -0.0204571 -0.00207764 21.3057 -1.66971 22.1538 3.93419 0.0278091 -0.205367 0.0114271 0.0648548 -4.66919 97.9043 -6.26847 -95.9963

Though coherence was > 0.95 during the measurement for each element (except for TT -> Length signals), after inverting and putting it to control servo, loops started to fight each other. So I decided to try a simple diagonal matrix:

TT1_PIT -> ETM_PIT_TRANS, TT1_YAW -> ETM_YAW_TRANS, TT2_PIT -> ITM_PIT_TRANS, TT2_YAW -> ITM_YAW_TRANS,

ITM_PIT -> ETM_PIT_LENGTH, ITM_YAW -> ETM_YAW_LENGTH, ETM_PIT -> ITM_PIT_LENGTH, ETM_YAW -> ITM_YAW_LENGTH

And this matrix worked much better.

## Control loops:

8 loops are running at the same time. UGF for input steering loops is 20 mHz, for cavity axis loops - 80 mHz. Slower loop is stronger at low frequencies so that cavity axis servo follows input steering alignment.

## Results:

When I started experiment the cavity was misaligned, transmission was ~0.4. Servo was able to align the cavity in ~30 seconds. This time depends on mirrors misalignment as well as input optics and cavity axis misalignment relative to each other.

When servo converged I disturbed ETMY, ITMY, TT1 and TT2. Servo was able to compensate for this.

Excitation lines seen by transmission and length of the cavity are suppressed as shown on the attached as pdf figures.

## Note:

Though the servo is able to align the cavity during my tests, this does not mean it will work perfectly any time. So please, if you lock, try to use the servo for alignment. If something goes wrong we'll fix it. This is better then to align IFO by hands every time.

Attachment 3: YARM_CTRL_DITHER.pdf
Attachment 4: TRY_DITHER.pdf
8465   Fri Apr 19 13:28:39 2013 DenUpdateASCdither alignment of yarm

I've put 4 scripts into ASS directory for YARM alignment. They should be called from !Scripts YARM button on c1ass main medm screen.

Scripts configure the servo to align the cavity and then save computed offsets. If everything goes right, no tuning of the servo is needed.

Call TRANS MON script to monitor YARM transmission, then "ON" script for aligning the cavity, then "SAVE OFFSETS" and "OFF" for turning the servo off.

## ON script:

• sets demodulation gains that I used during OL measuments
• sets LO oscillator frequency and amplitude for each optic
• sets demodulation phase rotation
• sets sensing matrix
• sets servo gains for each degree of freedom
• sets up limits for servo outputs
• gently increases the common gain from 0 to 1

## SAVE OFFSETS script:

• holds servo outputs
• sets servo common gain to 0 and clears outputs
• reads old optics DC offsets
• computes new DC offsets
• writes new offsets to C1:SUS-OPTIC_ANGLE_OFFSET channel
• holds off servo outputs

## OFF script:

• sets LO amplitudes to 0
• blocks servo outputs

## Notes:

SAVE OFFSET script writes DC offsets to C1:OPTIC_ANGLE_OFFSET channel, not to _COMM channel!

LIMITS are set to 500 for cavity axis degrees of freedom and to 0.5 for input steering. Usually servo outputs is ~30% if these numbers. But if something goes wrong, check this for saturation.

DC offsets of all 8 degrees of freedom are written one by one but the whole offset of put at the same time. This works fine so far, but we might change it to ezcastep in future.

8467   Fri Apr 19 16:58:59 2013 JenneUpdateASCArm A2L measurement scripts 90% working again

After Den's work with the ASS model this week, all of the channel names were changed (this wasn't pointed out in his elog....grrr), so none of the A2L scripts worked.

They are now back, however there is still some problem with the plotting that I'm not sure I understand yet.  So, the measurement works, but I don't think we're saving the results and we certainly aren't plotting them yet.

I wanted to check where the spots are on the mirrors, to make sure Den's stuff is doing what we think it's doing.  All of the numbers were within ~1.5mm of center, although Rossa keeps crashing (twice this afternoon?!?), so I can't copy and paste the numbers into the elog.

A near-term goal is to copy over Den's work on the Yarm to the Xarm, so that both arms will auto-align.  Also, I need to put the set of alignment scripts in a wrapper, and have that wrapper call-able from the IFO Configure screen.

Also, while thinking about the IFO Configure screen, the "save" scripts weren't working (on Rossa) today, even though I just made them work a week or so ago. Rossa, at least, was unhappy running csh, so I changed the "save" script over to bash.

ELOG V3.1.3-