40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 110 of 341  Not logged in ELOG logo
ID Date Authorup Type Category Subject
  11512   Mon Aug 17 17:48:12 2015 KojiUpdatePEMWasps obliterated maybe...

We found the same wasp in the 40m. Megan found it walking behind Steve desk!

  11520   Thu Aug 20 11:31:55 2015 KojiUpdatePEMGur interface box

As reported previously, the transfer functions of the channels look fine. (i.e. All channels almost identical.)
I checked the chain from the unit input to the DAQ BNC connectors. They were all OK.

Today I have been checking the signals on the unit with the long DB37 cables connected.
I could not see anything on the Gur2 channels on the board. I looked at the DB37 for Gur2 and felt something is wrong.

I opened the housing of the cable and realized that all the pins are not fully inserted.
The wires were crimped improperly and prevents them to be fully inserted.

=> We need to redo the crimping to insert them.
=> We need to check the other side too.

Attachment 1: IMG_1958.JPG
IMG_1958.JPG
  11524   Sat Aug 22 15:48:32 2015 KojiSummaryLSCArm locking recovery

As per Ignacio's request, I restored the arm locking.

- MC WFS relief

- Slow DC restored to ~0V

- Turned off DARM/CARM

- XARM/YARM turned on

- XARM/YARM ASS& Offset offloading

  11551   Tue Sep 1 02:44:44 2015 KojiSummaryCDSc1oaf, c1mcs modified for the IMC angular FF

[Koji, Ignacio]

In order to allow us to work on the IMC angular FF, we made the signal paths from PEM to MC SUSs.
In fact, there already were the paths from c1pem to c1oaf. So, the new paths were made from c1oaf to c1mcs. (Attachment 1~3)

After some debugging those two models started running. The additional cost of the processing time is insignificant.
FB was restarted to accomodate the change.

Once the modification of the models was completed, the OAF screens were modified. It seemed that the Kissel button
for the output matrix haven't been updated for the PRM ASC implementation. This was fixed as the button was updated this time.
In addition, the button for the FM matrix was also made and pasted.

 

Attachment 1: c1oaf_screenshot1.png
c1oaf_screenshot1.png
Attachment 2: c1oaf_screenshot2.png
c1oaf_screenshot2.png
Attachment 3: c1mcs_screenshot.png
c1mcs_screenshot.png
Attachment 4: OAF_MEDM1.png
OAF_MEDM1.png
Attachment 5: OAF_MEDM2.png
OAF_MEDM2.png
  11604   Wed Sep 16 03:37:06 2015 KojiSummaryGreen LockingWorkable delay line setup prepared

[Koji Gautam]

The variable delay line has been setup for practical use. The hardware and basic software are ready.

The delay time is given by [512-1-mod(C1:LSC-BO_1_0_SET, 512)]*(1/16) ns

Giving 511 (LLLL LLLH HHHH HHHH) to C1:LSC-BO_1_0_SET makes the delayline shortest (+0ns).
Giving 0 (LLLL LLLL LLLL LLLL) to C1:LSC-BO_1_0_SET makes the delayline longest (~32ns).

The SR785 was removed from the rack for our access >> Eric


DO setup

- Three CONTEC DO-32L-PE cards are found in the Yarm digital cabinet. (I brought a card from WB, but will bring it back).
- The card was installed in the C1LSC chassis.

- The models for c1x04 and c1lsc were modified to include the card. Once they are restarted, the card was recognized without problem.
  The frame builder also needed to be restarted (Attachment 1&2). The changes were committed to the repository.

- MEDM screen "CDS_BO_STATUS.adl" has been modified to include the bit monitors for the new DO card. (Attachment 3)

Epics values "C1:LSC-BO_1_0_SET" and "C1:LSC-BO_1_1_SET" are hooked up to the DO block.

Cables

- The DO board has DB37(F). I made a I/F cable with a DB37(M) crimp connector, DB25 breakout board, and a ribbon cable.
  Pin 1 is connected to pin 14 of the DB25 (GND of the delayline circuit).
  Pin 2~10 are connected to pin 1~9 of the DB25 (Switch 1~9 of the delayline circuit)
  Pin 18 is connected to X01 (external = spare) (Attachment 4)
 

- [CONFESSION] A bench +15V power supply was prepared to power the transisters of the DO (Attachment 6). The hot side is connected to X01 (not connected to the DB25),
  and the cold side is connected to pin 14 of the DB25. Once we find this is a useful setup we need to make a dedicated interface unit to convert DB37
  into DB25 (and provide more connectivities).

- A DB25 M-F cable was installed on the cable tray above the LSC racks.

Delay line unit

- The delay line box was mounted on 34H of the LSC analog rack (Attachment 5).

- The side cross connect power supply was not available (to be described later). Therefore we decided to use the same +15V supply as the one for the DO card.

- Checked the functionarity of the local switches using a function generator @30MHz and the front panel switches. The maximum (~32ns) delay was confirmed.
  (Just not enough to have 360 deg shift).

- Now the delay line function was tested with the front panel swicth at "ext". We confirmed that the delay time changes with the number given to C1:LSC-BO_1_0_SET.


What we need further

- Implement delay time slider control (511 = 0ns, 0 = 31.94ns). The delay time is given by
  [512-1-mod(C1:LSC-BO_1_0_SET, 512)]*(1/16) ns

- Some independent RF issues I found. (Next entry)

Attachment 1: 21.png
21.png
Attachment 2: 51.png
51.png
Attachment 3: 46.png
46.png
Attachment 4: IMG_20150915_222236066.jpg
IMG_20150915_222236066.jpg
Attachment 5: IMG_20150915_234222349.jpg
IMG_20150915_234222349.jpg
Attachment 6: IMG_20150915_234323363.jpg
IMG_20150915_234323363.jpg
  11605   Wed Sep 16 03:44:18 2015 KojiUpdateLSCRF micky mouse

1. POP110 RF amps are powered from the cross connect. But that +15V block has GND connections that are not connected to the ground.
    i.e. The ground potential is given by the signal ground. (Attachment 1)

    This is caused by the misuse of the DIN connector  blocks. The hod side uses an isolated block assuming a fuse is inserted.
    However, the ground sides also have the isolated blocks

2. One of the POP110 RF cable has a suspicious shiled. The rigidity of the cable is low, suggesting the broken shield. (Attachment 2)

Attachment 1: IMG_20150915_231038191.jpg
IMG_20150915_231038191.jpg
Attachment 2: IMG_20150915_234257144.jpg
IMG_20150915_234257144.jpg
  11614   Thu Sep 17 19:42:43 2015 KojiUpdateLSCRF micky mouse - dodgy DIN connector blocks fixed

1. The delay-line box is now hooked up to the cross connect +15V supply.

2. The broken RF cable was fixed.

It is actually the POP22 cable.
Therefore, we might see significant change of the signal size for POP22.
Be aware.

RG405 + SMA connector rule

- Don't bend the cable at the connector.

- Always use a cap on the connector. It is a part of the impedance matching.

- Use transparent shrink tube for strain relieving and isolation. This allow us to check the condition of the shield without removing the cover.

Attachment 1: IMG_20150917_190635033.jpg
IMG_20150917_190635033.jpg
Attachment 2: IMG_20150917_192551919.jpg
IMG_20150917_192551919.jpg
  11672   Thu Oct 8 13:13:20 2015 KojiUpdateLSCDRFPMI Progress

Please clarify: I wonder if you were at the zero offset for CARM and DARM or not. I am 25% excited right now.

  11674   Thu Oct 8 16:48:23 2015 KojiUpdateLSCDRFPMI Progress

Awesome

  11680   Fri Oct 9 14:50:18 2015 KojiUpdateLSCALS plant shape

ALS is the comparison of the PSL laser freq vs the end laser freq that is locked to the arm cavity resonant freq

On the other hand, the AS55 PDH is the comparison of the PSL laser freq after the IMC vs the arm cavity resonant freq. Here the PDH signal involves the arm cavity pole.

In total you observe the difference by the IMC cav pole + the arm cav pole.

  11689   Wed Oct 14 16:53:22 2015 KojiUpdateGeneralNon inverting buffer for SR560

Eric needed a buffer to drive low input impedance (~130Ohm) of his pomona box, I quickly made a non-iverting buffer with G=+10. The DC power is obtained from the back of SR560. It uses 1.02K and 9.09K
to have the gain of ~10. The chip is OP27. In fact this limits the output swing to be +/-5V for the load resistance of 130Ohm. Eric thinks this is enough. If we need more, we need to swap the chip.

As SR560s tend to saturate too quickly, it would be very useful to have this kind of kit in all the labs
once it is packed in a box.

Attachment 1: IMG_20151014_145608547.jpg
IMG_20151014_145608547.jpg
Attachment 2: IMG_20151014_145548751.jpg
IMG_20151014_145548751.jpg
  11693   Thu Oct 15 10:59:12 2015 KojiUpdateLSCDRFPMI Locked for 20 sec

Great job!
Many thanks Eric, Gautam, and all the current and past colleagues
for your tremendous contributions to bring the 40m to this achievement.

  11710   Fri Oct 23 19:27:19 2015 KojiUpdateCDSFrequency counting - workable setup prepared

It is a nice scan. I'm still thinking about the equivalence of the moving average and the FIR low pass that I have mentioned in the meeting.

Anyways:

I'm confused by the plot. The bottom axis says "green beat frequency".
If you scan the IR laser frequency by df, you get 2*df shift of the green beatnote. You need to have this factor of two somewhere.
If you are looking at the IR beat freq, just the label is not correct. (I believe this is the case.)

Accepting the rather-too-low finesse of 363 (nominally 450), the total round trip loss is said to be 0.0173.
If we subtract the front transmission of 1.38% (and ignoring the transmission loss from the ETM),
the round trip loss is 3500ppm. Is this compatible with the following elog?
http://nodus.ligo.caltech.edu:8080/40m/11111
In fact, I'm afraid that the loss number in the above elog 11111 was not correct by a factor of 10.
Then, if so, can we believe this high loss number? (Nominally we expect ~100ppm loss per round trip...)

  11720   Wed Oct 28 14:07:44 2015 KojiUpdateIOOMC WFS Offsets update

MC WFS offsets were updated to have a better operating point.
 

  11725   Mon Nov 2 17:39:01 2015 KojiFrogsGeneralDRFPMI celebration

やったー!Yatta!

Attachment 1: yatta.jpg
yatta.jpg
  11747   Tue Nov 10 11:40:03 2015 KojiUpdateLSCUpdated interpretation of peaks

What is the uncertainty of your RoC estimation?

One measurement of the ETMY ROC was 57.6m, but we trust another measured value of 60.26m than the other.
The value is always dependent on the spotposition on the mirror and how the ROC is calculated from the mirror phase map (e.g. spotsize, averaging method).
So I don't think this is a huge deviation from the spec.

  11748   Tue Nov 10 11:41:56 2015 KojiUpdateLSCUpdated interpretation of peaks

FYI: I've also reported the similar mod depths of

11M: 0.194
55M: 0.234

in ELOG11036 with a different kind of measurement method.

  11753   Wed Nov 11 22:11:15 2015 KojiUpdateSUSPSL/IOO maintenance, TM SUS check up

PMC

- Before any of the following work, I went to the PSL table and aligned the PMC. In fact, it has not been misaligned.


IMC

- It was claimed in the meeting today that the IMC had not been happy thesedays. I checked out what's happening.

- I found the IMC was still well aligned. Autolocker frequently stuck on a weak higher-order mode and couldn't recover TEM00 locking without help.

- I modified /opt/rtcds/caltech/c1/scripts/MC/mcdown for easier relocking on TEM00.

The MC_REFL_GAIN and MC_VCO_GAIN for relocking was set to be 27 and -3, in stead of 0 and 10, respectively.
This means that REFL_GAIN is not changed before and after the locking. Only VCO_GAIN is lowered for lock acquisition.
The corresponding lines in mcdown are excerpted here.

#set servo and boost gains for re-acquisition
#${ewrite} C1:IOO-MC_REFL_GAIN 0 &
${ewrite} C1:IOO-MC_REFL_GAIN 27 &
#${ewrite} C1:IOO-MC_VCO_GAIN 10 &
${ewrite} C1:IOO-MC_VCO_GAIN -3 &

We still have some chance of locking on higher-order modes. If I jiggle the VCO gain slider from -31 to 0, eventually I find TEM00.
I don't know how to do it in the script yet. For now, I increased tickle amplitude from 300 to 500.

/opt/rtcds/caltech/c1/scripts/MC/MC2tickleON

amp=300
=>

amp=500

- IMC was locked and aligned with the WFS. The WFS feedback offsets were offloaded to the alignment slider (via the MEDM button as usual).


TM SUS

- I wanted to use ASS. => The OL damping and ASC inputs are enabled for ETMX. The filter bank output of the ASS servos are all turned on.
- The arms were locked and aligned with ASS. The ASS servo offsets were offloaded to the ASC offset sliders (as usual).

- I found the X arm spot positionis moving slowly in pitch. I wanted to know what is causing this.

- Turned off all the OPLEV dampings for the four test masses.
- Took the power spectra of the OSEM output (e.g. C1:SUS-ITMX_LLSEN_OUT)

See attachment 1 (The DTT XML file can be found as /users/koji/151111/TM_SUS.xml )

- It seems that something is wrong with ITMX UL OSEM
  The signal level seems to be identical with the others. However, the noise level is huge. We need to check if the cable connection is OK.

- ITMY LL shows remarkably higher bounce mode although I can't tell if this is normal or not.

- The OPLEV dampings have been restored.

Attachment 1: TM_SUS.pdf
TM_SUS.pdf
Attachment 2: TM_SUS_SD.pdf
TM_SUS_SD.pdf
  11754   Wed Nov 11 22:50:39 2015 KojiConfigurationCDSSlow machine time&date

I was gazing at the log file for Autolocker script (/opt/rtcds/caltech/c1/scripts/MC/logs/AutoLocker.log )
and found quite old time stamps. e.g.

Old : C1:IOO-MC_VCO_GAIN             1991-08-08 14:36:28.889032 -3
New : C1:IOO-MC_VCO_GAIN             1991-08-08 14:36:36.705699 18
Old : C1:PSL-FSS_FASTGAIN            1991-08-09 19:05:39.972376 14
New : C1:PSL-FSS_FASTGAIN            1991-08-09 19:05:44.939043 18

It was found that the date/time setting of some of the slow machines (at least c1psl and c1iool0) is not correct.
I could not figure out how to fix it.

Question: Is this anything critical?

Another thing: While I was in c1iool0 I frequently saw the message like

c1iool0 > 0xc461f0 (CA event): Events lost, discard count was 514

Is this anything related to EPICS Freeze?

controls@nodus|~ > telnet c1psl.martian
Trying 192.168.113.53...
Connected to c1psl.martian.
Escape character is '^]'.
c1psl > date
Aug 09, 1991 19:13:26.439024274
value = 32 = 0x20 = ' '
c1psl >
telnet> q
Connection closed.

controls@nodus|~ > telnet c1iool0.martian
Trying 192.168.113.57...
Connected to c1iool0.martian.
Escape character is '^]'.

c1iool0 > date
Aug 08, 1991 14:44:39.755679528
value = 32 = 0x20 = ' '
c1iool0 > 0xc461f0 (CA event): Events lost, discard count was 514
Change MC VCO gain to -3.
0xc461f0 (CA event): Events lost, discard count was 423
Change MC VCO gain to 18.
Change boost gain to 1.
Change boost gain to 2.

 

  11763   Fri Nov 13 22:32:54 2015 KojiSummaryPSLPMC LO degraded, usual ERA-5 replacement, LO recovered

[Yutaro, Koji]

We found that the PMC LO level was fluctuating in a strage way (it was not stable but had many clitches like an exponential decay), we suspected the infamous PMC LO level decay. In fact, in June 2014 when Rana recalibrated the LO level,  the number on the medm screen (C1:PSL-PMC_LO_CALC) was about 11dBm. However, today it was about 6dBm. So we decided to jump in to the 1X1 rack.

The LO and PC outputs of the PMC Crystal module (D980353) were measured to be 6.2dBm and 13.3dBm. Rana reported in ELOG 10160 that it was measured to be 11.5dBm. So apparently the LO level decayed. Unfortunately, there was no record of the PC output level. In any case, we decided to pull the module for the replacement of ERA-5 chips.

Once we opened the box we found that the board was covered by some greasy material. The ERA-5 chip on the LO chain seemed unreasonably brittle. It was destryed during desoldering. We also replaced the ERA-5 chip in the PC chain, just in case. The board was cleaned by the defluxing liquids.

Taking an advatage of this chance, the SMA  cables around the PMC were checked. By removing some of the heat shrinks, suspicious broken shields of the connectors were found. We provided additional solder to repair them.

After the repair, the LO and PC output levels became icreased to 17.0dBm(!) and 13.8dBm, respectively. (Victory)
This LO level is way too much compared to Rana's value. The MEDM LO power adj has little effect and the adj range was 16dBm~17dBm. Therefore we moved the slider to 10, which yields 16dBm out, and added a 5dB attenuator. The measured LO level after the attenuator was measured to be 11.2dBm.

Locking of the PMC was tried and immediately acquired the lock. However, we noticed that the nomoinal gain of 10dB cause the oscillation of the servo. As we already adjusted the LO level to recover the nominal value, we suspeced that the modulation depth could be larger than before. We left the gain at 0dB that doesn't cause the oscillation. It should be noted that the demodulation phase and the openloop gain were optimized. This should be done in the day time as soon as possible.

When the PMC LO repair was completed, the transmission of the PMC got decreased to 0.700V. The input alignment has been adjusted and the transmission level of 0.739V has been recovered.

The IMC lock stretch is not stable as before yet. Therefore, there would still be the issue somewhere else.

Attachment 1: PMC_LO.png
PMC_LO.png
Attachment 2: IMG_2093.JPG
IMG_2093.JPG
Attachment 3: IMG_2091.JPG
IMG_2091.JPG
Attachment 4: IMG_2095.JPG
IMG_2095.JPG
Attachment 5: IMG_2096.JPG
IMG_2096.JPG
  11764   Sat Nov 14 00:52:25 2015 KojiSummaryCDSInvestion on EPICS freeze

[Yutaro, Koji]

Recently "EPICS Freeze" is so frequent and the normal work on the MEDM screen became almost impossible.

As a part of the investigation, all 19 realtime processes were stopped in order to see any effect on the probem.

IN FACT, when the realtime processes were absent (still slow machines were running), frequency of EPICS Freeze
became much less. This might mean that the issue is related to the data collection of the slow channels. We need more investigation.

After the testing, all the processes were restored although it was not so straghtforward. Particularly, c1sus DAC had an error which was
not visible from the CDS Status screen. We noticed it as suspension damping was not effective on any of the vertex suspensions.
This has been solved by restarting c1x02 process.

  11765   Sun Nov 15 22:43:48 2015 KojiSummaryPSLPMC LO degraded, usual ERA-5 replacement, LO recovered

I think the IMC locking was somewhat improved. Still it is not solid as long time before.

Before the PMC fix (attachment 1)
After the PMC fix (attachment 2)

To do
- PMC loop inspection / phase check / spectral measurements
- PMC / IMC interaction
- IMC loop check
 

Attachment 1: C1-MULTI_E6875C_TIMESERIES-1131408017-86400.png
C1-MULTI_E6875C_TIMESERIES-1131408017-86400.png
Attachment 2: C1-MULTI_E6875C_TIMESERIES-1131580817-86400.png
C1-MULTI_E6875C_TIMESERIES-1131580817-86400.png
  11768   Mon Nov 16 19:05:59 2015 KojiSummaryPSLPMC servo circuit review, follow up measurements

PMC follow up measurements have been done. The servo circuit was reviewed.

Now the PMC, IMC, X/Y arms are locked and aligned waiting for the IFO work although I still think something is moving (ITMX?)
as the FPMI fringe is quite fast.

  11769   Mon Nov 16 21:32:49 2015 KojiSummaryPSLPMC servo circuit review, follow up measurements

The result of the precise inspection for the PMC servo board for the 40m was done.

The record, including the photo of the board, can be found at https://dcc.ligo.org/D1400221-v2

- I found some ceramic 1uF caps are used in the signal path. They have been replaced with film caps by WIMA.

- In later measurements with the openloop TF measurement, it was found that the notch frequency (14.6kHz) was off from the a sharp PZT resonance at 12.2kHz.
I replaced the combined caps of 1220pF to 1742pF. This resulted nice agreement of the notch freq with the PZT resonant freq.


Past related elogs:

SRA-3MH mixer installed in 2009: http://nodus.ligo.caltech.edu:8080/40m/1502

R20 increased for more LO Mon gain: http://nodus.ligo.caltech.edu:8080/40m/10172

  11773   Tue Nov 17 15:49:23 2015 KojiConfigurationIOOMC Autolocker modified

/opt/rtcds/caltech/c1/scripts/MC/AutoLockMC.csh  was modified last night.

1. Autolocker sometimes forget to turn off the MC2Tickle. I added the following lines to make sure to turn it off.

    echo autolockMCmain: MC locked, nothing for me to do >> ${lfnam}
    echo just in case turn off MC2 tickle >> ${lfnam}
    ${SCRIPTS}/MC/MC2tickleOFF

2. During the lock acquisition, Autolocker frequently stuck on a weak mode. So the following lines were added
so that the Autolocker toggles the servo switch while waiting for the lock.

    echo autolockMCmain: Mon=$mclockstatus, Waiting for MC to lock .. >> ${lfnam}
    # Turn off MC Servo Input button
    ezcawrite C1:IOO-MC_SW1 1
    date >> ${lfnam}
    sleep 0.5;
    # Turn on MC Servo Input button
    ezcawrite C1:IOO-MC_SW1 0
    sleep 0.5;

  11775   Tue Nov 17 16:21:10 2015 KojiSummaryPSLPMC servo circuit review, follow up measurements

I'm still analyzing the open loop TF data. Here I report some nominal settings of the PMC servo

Nominal phase setting: 5.7
Nominal gain setting: 3dB

After the tuning of the notch frequency, I thought I could increase the gain from 5dB to 9dB.
However, after several hours of the modification, the PMC servo gradually started to have oscillation.
This seemed to be mitigated by reducing the gain down to 4dB. This may mean that the notch freq got drifted away
due to themperature rise in the module. PA85 produce significant amount of heat.

(The notch frequency did not change. Just the 22kHz peak was causing the oscillation.)

  11780   Wed Nov 18 16:51:58 2015 KojiSummaryPSLPMC servo calibration

Summary

The PMC servo error (MIX OUT MON on the panel) and actuation (HV OUT MON) have been calibrated using the swept cavity.

Error signal slope in round-trip displacement: 2.93e9 +/- 0.05e9 [V/m]
HV OUT calibration (round-trip displacement): 5.36e-7 +/- 0.17e-7 [m/V]
PZT calibration (round-trip displacement): 10.8 +/- 0.3 [nm/V]
=> corresponds to ~2.5 fringes for 0~250V full range => not crazy

Measurement condition

The transmission level: 0.743V (on the PMC MEDM screen)
LO level: ~13dBm (after 3dB attenuation)
Phase setting: 5.7
PMC Servo gain: 7dB during the measurement (nominal 3dB)

Method

- Chose PMC actuation "BLANK" to disable servo
- Connect DS345 function generator to EXT DC input on the panel
- Monitor "MIX OUT MON" and "HV OUT MON" with an oscilloscope
- Inject a triangular wave with ~1Vpp@1 or 2Hz with appropriate offset to see the cavity resonance at about the middle of the sweep.
  The frequency of the sweep was decided considering the LPF corner freq formed by the output impedance and the capacitance of the PZT. (i.e. 11.3Hz, see next entry)

Result

- 4 sweep was taken (one 2Hz seep, three 1Hz sweep)
- The example of the sweep is shown in the attachment.
- The input triangular wave and the PDH slopes were fitted by linear lines.
- Spacing between the sideband zero crossing corresponds to twice of the modulation frequency (2x35.5MHz = 71MHz)
- The error signal slope was calibrated as V/MHz
- FSR of the PMC is given by google https://www.google.com/search?q=LIGO+pmc.m
  => Cavity round trip length is 0.4095m, FSR is 732.2MHz
- Convert frequency into round-trip displacement

- Convert HV OUT MON signal into displacement in the same way.
- The voltage applied to the PZT element is obtained considering the ratio of 49.6 between the actual HV and the HV OUT MON voltage.

Attachment 1: PMC_err_cal.pdf
PMC_err_cal.pdf
  11781   Wed Nov 18 16:53:17 2015 KojiSummaryPSLPMC PZT capacitance

The PMC PZT capacitance was measured.
- Turn off the HV supplies. Disconnect HV OUT cable.
- Make sure the cable is discharged.
- Measure the capacity at the cable end with an impedance meter.
=> The PMC PZT capacitance at the cable end was measured to be 222nF
Combined with the output impedance of 63.3kOhm, the LPF pole is at 11.3Hz

  11782   Wed Nov 18 17:09:22 2015 KojiSummaryPSLPMC Servo analysis

Summary

The PMC servo was analysed. OLTF was measured and modeled by ZPK (Attachment 1). The error and actuator signals were calibrated in m/rtHz (Attachment 2)

Measurement methods

OLTF:

- The PMC servo board does not have dedicated summing/monitor points for the OLTF measurement. Moreover the PZT HV output voltage is monitored with 1/49.6 attenuation.
  Therefore we need a bit of consideration.

- The noise injection can be done at EXT DC.
- Quantity (A): Transfer function between HV OUT MON and MIX OUT MON with the injection.
  We can measure the transfer function between the HV OUT (virtual) and the MIX OUT. (HV OUT->MIX OUT). In reality, HV OUT is attenuated by factor of 49.6.
  i.e. A = (HV_OUT->MIX_OUT)*49.6
- Quantity (B): Transfer function between HV OUT MON and MIX OUT MON without the injection.
 
This is related to the transfer function between the MIX OUT and HV OUT. In reality, HV OUT is attenuated. 
  i.e. B = 1/((MIX_OUT->HV_OUT)/49.6)

- What we want to know is HV_OUT->MIX_OUT->HV_OUT. i.e. A/B = (HV_OUT->MIX_OUT*49.6)*((MIX_OUT->HV_OUT)/49.6) = HV_OUT->MIX_OUT->HV_OUT

PSD:

- The MIX OUT and HV OUT spectra have been measured. The MIX OUT was calibrated with the calibration factor in the previous entry. This is the inloop stability estimation.
  From the calibrated MIX OUT and HV OUT, the free running stability of the cavity was estimated, by mutiplying with |1-OLTF| and |1-1/(1-OLTF)|, respectively, in order to recover
  the free running motion.

OLTF Modeling

Here is the model function for the open loop TF. The first line comes from the circuit diagram. The overall factor was determined by eye-fit.
The second and third lines are to reproduce the peak/notch feature at 12kHz. The fourth line is to reproduce 28kHz feature.
The LPF right after the mixer was analyzed by a circuit simulation (Circuit Lab). It can be approximated as 150kHz LPF as the second pole
seems to come at 1.5MHz.

The sixth line comes from the LPF formed by the output resistance and the PZT capacitance.

The seventh line is to reproduce the limit by the GBW product of OP27. As the gain is 101 in one of the stages,
it yields the pole freq of ~80kHz. But it is not enough to explain the phase delay at low frequency. Therefore this
discrepancy was compensated by empirical LPF at 30kHz.

function cmpOLTFc = PMC_OLTF_model(freqOLTFc)

cmpOLTFc = -7e5*pole1(freqOLTFc,0.162).*zero1(freqOLTFc,491)... % from the circuit diagram
    .*zero2(freqOLTFc,12.5e3,100)... % eye-fit
    .*pole2(freqOLTFc,12.2e3,6)... % eye-fit
    .*pole2(freqOLTFc,27.8e3, 12)... % eye-fit
    .*pole1(freqOLTFc,150e3)... % Mixer LPF estimated from Circuit Lab Simulation
    .*pole1(freqOLTFc,11.3)... % Output Impedance + PZT LPF
    .*pole1(freqOLTFc,8e6/101)... % GBW OP27
    .*pole1(freqOLTFc,3e4); % Unknown

end

Result

Attachment 1:

The nominal OLTF (Nov 17 data) shows the nominal UGF is ~1.7kHz and the phase margin of ~60deg.

The measured OLTF was compared with the modelled OLTF. In the end they show very sufficient agreement for further calibration.
The servo is about to be instable at 28kHz due to unknown series resonance. Later in the same day, the gain of the PMC loop had to be
reduced from 7dB to 3dB to mitigate servo oscillation. It is likely that this peak caused the oscillation. The notch frequency was measured
next day and it showed no sign of frequncy drift. That's good.

We still have some phase to reduce the high freq peaks by an LPF in order to increase the over all gain.

Attachment 2:

The red curve shows the residual floor displacement of 2~10x10-15 m/rtHz. Below 4Hz there is a big peak. I suspect that I forgot to close
the PSL shutter and the IMC was locked during the measurement. Then does this mean the measured noise corresponds to the residual laser
freq noise or the PMC cavity displacement? This is interesting to see.

The estimated free running motion from the error and actuation signals agrees very well. This ensures the precision of the caibration in the precious entries.
 

 

Attachment 1: PMC_OLTF.pdf
PMC_OLTF.pdf
Attachment 2: PMC_DSP.pdf
PMC_DSP.pdf
  11791   Thu Nov 19 17:06:57 2015 KojiConfigurationCDSDisabled auto-launching RT processes upon FE booting

We want to startup the RT processes one by one on boot of FE machines.

Therefore /diskless/root/etc/rc.local on FB was modified as follows. The last sudo line was commented out.

for sys in $(/etc/rt.sh); do
    #sudo -u controls sh -c ". /opt/rtapps/rtapps-user-env.sh && /opt/rtcds/cal\
tech/c1/scripts/start${sys}"

    # NOTE: we need epics stuff AND iniChk.pl in PATH
    # we use -i here so that the .bashrc is sourced, which should also
    # source rtapps and rtcds user env (for epics and scripts paths)

    # commented out Nov 19, 2015, KA
    # see ELOG 11791 http://nodus.ligo.caltech.edu:8080/40m/11791
    # sudo -u controls -i /opt/rtcds/caltech/c1/scripts/start${sys}
done

  11793   Fri Nov 20 15:44:12 2015 KojiSummaryPSLAdded 17.5kHz LPF to the PMC servo

As a final tune of the PMC servo, I've added 1nF cap at the error signal amplification stage. The diagram has been updated and uploaded to DCC. https://dcc.ligo.org/D1400221

It should be noted that this modification yielded the error signal to have 17.5kHz roll off.


The openloop TF after the modification has been measured. (Attachment 1)

With the new nominal gain of 9dB, almost the same gain margin for the 28kHz peak has been realized.
=> We have 6dB (factor of 2) more gain at low frequency. Currently, the feature at 8kHz causes the oscillation when the gain is further increased.
 

Here is the model function for the OLTF.

function cmpOLTFc = PMC_OLTF_model(freqOLTFc)

cmpOLTFc = -9.5e5*pole1(freqOLTFc,0.162).*zero1(freqOLTFc,491)... % from the circuit diagram
    .*pole1(freqOLTFc,17.5e3)... % Newly implemented input filter => GBW pole was replaced with this
    .*zero2(freqOLTFc,12.5e3,100)... % eye-fit
    .*pole2(freqOLTFc,12.2e3,6)... % eye-fit
    .*pole2(freqOLTFc,28.8e3, 12)... % eye-fit
    .*pole1(freqOLTFc,150e3)... % Mixer LPF estimated from Circuit Lab Simulation
    .*pole1(freqOLTFc,11.3)... % Output Impedance + PZT LPF
    .*pole1(freqOLTFc,3e4); % Unknown
   
end


The free-running round-trip displacement (roundtrip) / frequency noise is shown in Attachments. There we compare the spectra with and without IMC locked.

i.e. When the IMC is not locked, we are measuring the laser frequency noise with the sensor (PMC cavity) that is noisy due to the PMC displacement.
When the IMC is locked, the laser frequency is further stabilized while the sensor (PMC) noise is not changed.

- Without IMC locked

Can we see the laser freq noise? It seems that it is visible above 100Hz.
The red curve is the measured noise level. The NPRO (although it is LWE NPRO) noise level from S. Nagano's thesis (see our wiki) is shown there.

- With IMC locked

When the IC is locked, we see the increase of the noise between 1~4Hz. It means that the IMC is not only noisier than the laser, but also noisier than the PMC cavity.
Sounds reasonable. And the PMC is capable to handle this motion.

The reduction of the frequency noise is seen from 100Hz to 30kHz.

The interesting point is that we can see the noise increase above 30kHz when the IMC is locked.
I believe that the phase correction EOM is shared with the PMC modulation. i.e. PMC sees the corrected laser frequency.

We expect that the frequency noise is reduced at this frequency. But in reality not.

In addition, there is a sharp peak at ~35kHz. I wonder If this is caused by the IMC servo. It is worse to investigate.

Attachment 1: PMC_OLTF.pdf
PMC_OLTF.pdf
Attachment 2: PMC_noise_comparison.pdf
PMC_noise_comparison.pdf
  11794   Sat Nov 21 00:45:30 2015 KojiUpdateIOOIMC fix

Based on the observation of the PMC error signal, I started measuring the IMC OLTF. Immediately, it was found that the overall IMC loop gain was too low.
The UGF was ~40kHz, which was really marginal. It had been >100kHz when I have adjusted it about a year ago. (Next entry for the detail)

The first obvious thing was that the SMA cables around the IMC servo have visible degradation (Attatched photos).
I jiggled the signal cable from the demodulator Q_out to the MC servo. The openloop gain seemed fluctuating (increased) based on the cabling.
I decided to repair these cables by adding solder on the shield.

Even after the repair, the open loop TF didn't show any improvement. I checked the LO level and found that it was -16.7dBm.

I traced the problem down to the frequency generator unit (T1000461). The front panel of the unit indicates the output power for the 29.5MHz output is 13dBm,
while measurement showed it was 6~8dBm (fluctuating). The T1000461 document describes that there is only a wenzel oscillator inside. Does this mean the oscillatorwas degraded??? We need to open the box.

I was not sure what was the LO level. I naively assumed the input is 0dBm. Reducing the attenuation of the dial on the AM Stabilizer unit from 12dB attn to 0dB.
This made the LO level -3.3dBm.


Later at home, I thought this nominal LO level of 0dBm could have been wrong.

The demodulator circuit (D990511) has the amplifier ERA-5 (G=~20dB) at the input. Between the input and the ERA-5 there is a pattern for an attenuator.
Assuming we have no attenuator, the ERA-5 has to spit out 20dBm. That is too much for this chip. I need to pull out the box to see how much is the nominal LO for this box using an active probe.

This decrease/increase of the LO level affects the WFS demod too. According to D980233-B, the input stage has the comparator chip AD96687, which can handle differential voltage of 5.5V.
Therefore the effect is minimal.

Attachment 1: PDRFsignal_cable.JPG
PDRFsignal_cable.JPG
Attachment 2: Qsignal_cable1.JPG
Qsignal_cable1.JPG
Attachment 3: Qsignal_cable2.JPG
Qsignal_cable2.JPG
Attachment 4: Qsignal_cable3.JPG
Qsignal_cable3.JPG
  11795   Sat Nov 21 00:46:33 2015 KojiUpdateIOOIMC OLTF

Here is the comparison before and after the fix.

Before the work, the UGF was ~40kHz. The phase margin was ~5deg. This caused huge bump of the frequency noise.

After the LO power increase, I had to reduce the MC loop gain (VCO Gain) from 18dB to 6dB. This resulted 4dB (x2.5) increase of the OLTF. This means that my fix increased the optical gain by 16dB (x6.3). The resulting UGF and phase mergin were measured to be 117kHz and 31deg, respectively.

 

Now I was curious to see if the PMC err shows reasonable improvement when the IMC is locked. Attachment 2 shows the latest comparison of the PMC err with and without the IMC locked. The PMC error has been taken up to 500kHz. The errors were divided by 17.5kHz LPF and 150kHz LPF to compensate the sensing response. The PMC cavity pole was ignored in this calculation. T990025 saids the PMC finesse is 4400 and the cavity pole is 174kHz. If this is true, this also needs to be applied.

Observations:

1. Now we can see improvement of the PMC error in the region between 10kHz to 70kHz.

2. The sharp peak at 8kHz is due to the marginally stable PMC servo. We should implement another notch there. T990025 suggests that the body resonance of the PMC spacer is somewhere around there. We might be able to damp it by placing a lossy material on it.

3. Similarly, the features at 12kHz and 28kHz is coming from the PMC. They are seen in the OLTF of the PMC loop.

4. The large peak at 36kHz does not change with the IMC state. This does mean that it is coming from the laser itself, or anything high-Q of the PMC. This signal is seen in the IMC error too.

5. 72kHz, 108kHz, 144kHz: Harmonics of 36kHz?

6. Broad feature from 40kHz to 200kHz. The IMC loop is adding the noise. This is the frequency range of the PC drive. Is something in the PC drive noisy???
 

7. The feature at 130kHz. Unknown. Seems not related to IMC. The laser noise or the PMC noise.


Remaining IMC issues:

Done (Nov 23, 2015) - 29.5MHz oscillator output degraded. Possibly unstable and noisy. Do we have any replacement? Can we take a Marconi back from one of the labs?

Done (Nov 23, 2015) - Too high LO?

- Large 36kHz peak in the IMC

- IMC loop shape optimization

- IMC locking issue. The lock streatch is not long.

- IMC PC drive issue. Could be related to the above issue.

Maybe not relevant - PC drive noise?

Attachment 1: IMC_OLTF.pdf
IMC_OLTF.pdf
Attachment 2: PMC_noise_comparison.pdf
PMC_noise_comparison.pdf
  11797   Sun Nov 22 12:07:09 2015 KojiUpdateIOOIMC fix

TO DO

Done (Nov 23, 2015) - Check if the attenuator is still there in the input chain

Done (Nov 23, 2015) - Check if the actual LO levels at the 17dBm mixers are reasonable.

- Check if the actual LO levels for the LSC demods are OK too

  11798   Sun Nov 22 12:12:17 2015 KojiUpdateIOOIMC OLTF

Well. I thought a bit more and now I think it is likely that this is just the servo bump as you can see in the closed-loop TF.

Quote:

6. Broad feature from 40kHz to 200kHz. The IMC loop is adding the noise. This is the frequency range of the PC drive. Is something in the PC drive noisy???

  11800   Mon Nov 23 20:32:43 2015 KojiUpdateLSCFrequency source fixed, IMC LO level adjusted

The frequency source was fixed. The IMC LO level was adjusted.

IMC is locked => OLTF measured UGF 144kHz PM 30deg.

  11801   Mon Nov 23 21:48:49 2015 KojiUpdateLSCFrequency source fixed, IMC LO level adjusted

The trouble we had: the 29.5 MHz source had an output of 6 dBm instead of 13 dBm.

The cause of the issue: A short cable inside had its shield cut and had no connection of the return.


- The frequency source box was dismantled.
- The power supply voltages of +28 and +18 were provided from bench supplies.
- The 29.5 MHz output of 5~6 dBm was confirmed on the work bench.
- The 11 MHz OCXO out (unused) had an output of 13 dBm.

- Once the lid was opened, it was immediately found that the output cable for the 29.5 MHz source had a sharp cut of the shield (Attachment1).
- OK. This cable was replaced. The output of 13 dBm was recovered.

- But wait. Why is the decoupling capacitor on the 29.5 MHz OCXO bulging? The polarity of the electrolytic capacitor was wrong!
- OK. This capacitor was replaced. It was 100 uF 35 V but now it is 100 uF 50 V.

- I further found some cables which had flaky shields. Some of them were twisted. When the panel cable s connected, the feedthroughs were rotated. This twists internally connected cables. Solder balls were added to the connector to reinforce the cable end.

- When the box was dismantled, it was already noticed that some of the plastic screws to mount the internal copper heat sinks for ZHL-2's were broken.
They seemed to be degraded because of the silicone grease. I didn't try to replace all as it was expected to take too much time, so only the broken screws
were replaced with steel screws with shoulder washers
at the both side of the box.

- After confirming the circuit diagram, the box was returned to the rack. The 29.5 MHz output of 13 dBm there was confirmed.

Attachment 1: IMG_2136.JPG
IMG_2136.JPG
Attachment 2: IMG_2129.JPG
IMG_2129.JPG
Attachment 3: IMG_2133.JPG
IMG_2133.JPG
  11802   Mon Nov 23 22:12:10 2015 KojiUpdateIOOLO level check for the IMC demod board

In order to check the proper LO level, the IMC demod board was checked. As a short summary, -8dBm is the proper input for the IMC demod board. This was realized when the variable attenuator of the RF AM Stabilizer was set up be -7dB.


Initially, I tried to do the measurement using the extender board. But every board had the issue of +15V not working. After several extender boards were tried, I noticed that the current draw of the demod board burned the 15V line of the extender board.

Then I moved to the work bench. The signals were checked with the 10:1 probe. It's not properly the 50Ohm system, exactly to say.

I found that the LO signals at the mixers have huge distortion as it reaches the nominal 17dBm, and I wondered if ERA-5s were gone. Just in case I replaced the ERA-5s but didn't see any significant change. Then I thought it is due to the mixer itself. The mixer was removed and replaced with a 50Ohm SMD resister. Then the output of the last ERA-5 became sinusoidal, and the level was adjusted to be ~17dBm (4.52 Vpp) when the input power was measured to be -7.7dBm with the RF power meter. Once the mixer was reinstalled, it was confirmed that the waveform becase rectangular like, with the similar amplitude (4.42Vpp).

Now the module was returned to the rack. The RF level at the LO input was adjusted to be -8dBm by setting the attenuator level to be 7dBm.

Once the IMC is locked with this setting, the open loop transfer function was measured. The optical gain seemed almost unchanged compared with the recent nominal. The UGF and PM were measured to be 144kHz and 30deg.

Attachment 1: IMG_2137.JPG
IMG_2137.JPG
Attachment 2: IMG_2138.JPG
IMG_2138.JPG
  11804   Tue Nov 24 01:14:23 2015 KojiUpdateLSCALSY recovered

Sorry, I completely forgot to turn the Marconi on...

  11808   Wed Nov 25 10:07:10 2015 KojiUpdateIOOLO level check for the IMC demod board

I didn't finish making the DCC entry for this module yet.

But the attenuators are
- AT1: 10dB. There is a sign that it was 3dB before ---  a 3dB chip was also attached on the boardnext to 10dB.
- AT2/3: Removed. They were replaced with 0Ohm resistors.

Currently the input is -8dBm. The input and output of the first ERA-5 are -17dBm and +7dBm, respectively.
Then the input and output of the second ERA-5 are -2dBm and 17dB, respectively.

In order to remove the second amplification stage, the first stage has to produce 26dBm. This is too much for either ERA-5 or any chips that fits on the foot print. If we use low gain but high output amp like GVA-81 (G=10dB, DF782 package), it is doable

Input 0dBm - [ATTN 3] - -3dBm - [ERA-5 G=20dB] - +16~+17dBm - [Circuits -9dB] - +7dBm - [Attn 0dB] - +7dBm - [GVA-81 G=10dB] - +17dBm

I think we should check the conditions of all the LSC demods.

  11811   Wed Nov 25 16:46:10 2015 KojiUpdateIOOLO level check for the IMC demod board

Awwww. I found that the demod board has the power splitter (PSCJ-2-1) with one output unterminated.
This power splitter should be removed.

https://dcc.ligo.org/D1500443

Attachment 1: D990511-40m_151123.pdf
D990511-40m_151123.pdf
  11817   Thu Nov 26 19:39:27 2015 KojiUpdateLSCCurrent state of the frequency source, and possible improvement

Uploaded on T1000461 too.

Attachment 1: RF_Frequency_Source.pdf
RF_Frequency_Source.pdf RF_Frequency_Source.pdf
  11822   Sun Nov 29 12:32:26 2015 KojiUpdateLSCCurrent state of the frequency source, and possible improvement

I'm not claiming we need to modify the frequency source immediately as we are not limited by the oscillator amplitude or phase noise.
I just wanted to note something in mind before it goes away quickly.

Alberto's T1000461 tells us that the oscillator and phase noise are degraded by factor of ~3 and ~5 due to the RF chanin.
My diagram is possible removal of up-down situation of the chain.

Maybe more direct improvement would be:

- Removal of two amplifiers out of four. The heat condition of the box is touch thought it is not critical.

- The modification will allow us to have a spare 11MHz channel at 1X2 rack that would be useful for 3f modulation.

  11826   Mon Nov 30 15:17:57 2015 KojiUpdateLSCLO level check for the LSC RF distribution box

T1000461 tells us that the nominal LO input is 2dBm although we don't know what's the LO level is at the mixers in the demod boards.

  11829   Mon Nov 30 18:27:30 2015 KojiUpdateLSCstrange behavior of ASDC

It wasn't fully mentioned in ELOG 11814.
We checked the PD first and this behavior didn't change after the realignment of the AS55PD.
Yutaro confirmed that this effect is happening in the vacuum chamber.

  11834   Tue Dec 1 17:26:14 2015 KojiUpdateGeneralMegatron maitenence

SLOWDC servo was dead. I followed EricQ's instruction.

  11835   Tue Dec 1 20:20:16 2015 KojiUpdateGeneralMegatron maitenence

MC Autolocker got stack somewhere. I had to go to megatron and kill MC Autolocker.

init relaunched the autolocker automatically, and now it started properly.

  11852   Sat Dec 5 21:28:33 2015 KojiHowToCamerasWhen image capture does not work...

Do we need "make" everytime? Do you mean just running "modprobe" didn't work?

  11867   Wed Dec 9 18:45:58 2015 KojiSummaryGeneralNetwork Topology Check

[Eric Q, Gautam, Koji]

We went through the network connections to produce the mapping of the instruments.
Gautam summarized the notes into a spread sheet. See attachments.

We didn't find any irregular connections except for the connection of NETMGR port of c1ioo to Martian Network.
This cable was removed.

Attachment 1: Network_topology_9Dec2015.xlsx
Attachment 2: Network_topology_9Dec2015.pdf
Network_topology_9Dec2015.pdf Network_topology_9Dec2015.pdf Network_topology_9Dec2015.pdf
  11873   Fri Dec 11 13:28:36 2015 KojiUpdateLSCPower recycling gain estimation from arm loss measurement

Can I ask you to make a plot of the power recycling gain as a function of the average arm loss, indicating the current loss value?

ELOG V3.1.3-