40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 39 of 339  Not logged in ELOG logo
ID Date Author Type Category Subject
  15143   Wed Jan 22 20:12:36 2020 gautamUpdatePSLPMC demodulator electrical characterization

Summary:

The mixer + LPF combo used to demodulate the PMC PDH error signal seems to work as advertised.

Details:

Measurement setup --- Attachment #1. The IF signal was monitored using the scope in High-Z mode.

Results --- Attachment #2.

So the next step is to characterize the RF transimpedance of the PMC RFPD.

Attachment 1: demodChar.pdf
demodChar.pdf
Attachment 2: mixerChar.pdf
mixerChar.pdf
  15142   Wed Jan 22 19:17:20 2020 gautamConfigurationComputersMegatron: starts up grade

upgrade was done

cronjob testing wasn't one by one 😢 

burt snapshots were gone

i brought them back home 🏠 

Quote:

Megatron is now running Ubuntu 18.04 LTS.

  15141   Wed Jan 22 16:38:01 2020 ranaUpdateComputersrossa revival

wiped and install Debian 10 on rossa today

still to be done: config it as CDS workstation

please don't try to "fix" it in the meantime

  15140   Wed Jan 22 16:19:47 2020 JonUpdateVACTP3 controller errors

Gautam and I debugged a communications problem with TP3 that was causing its python service to fail. We traced the problem back to the querying of the pump controller for its operational parameters (speed, voltage, temp). Some small percentage of the time (~5%, indeterministically), the pump controller is returning an invalid response which causes the service to shut itself down and signal a NO COMM error.

As a temporary fix, I wrapped the failing query in an exception handler to continue past this particular error. However, we suspect the microprocessor in the TP3 controller may be beginning to fail. There is a spare controller sitting right next to it in the vacuum rack. We will ask Chub to install the replacement in the near future.

gautam: this pump is responsible for pumping the annular volume under normal operations. while this problem is being resolved, the annular volume is valved off (as it has been since July 2019 anyway which is when this problem first manifested).

  15139   Wed Jan 22 11:22:39 2020 gautamUpdatePSLPMC modulation depth measurement

Summary:

I estimate the PMC servo modulation depth to be approximately 50 mrad. This is only 15% lower than what was measured in Jan 2018, and cannot explain the ~x50 reduction of optical gain measured earlier in this thread. Later in the day, I also confirmed that the LO input to the ZAD-6 mixer is +7 dBm. So the crystal is not to blame.

Details:

  1. PSL frequency is locked to the IMC length.
  2. Arm lengths are locked to the PSL frequency using POX/POY.
  3. EX green laser locked to the X arm length using end PDH servo. GTRX was ~0.4 in this measurement, which is the nominal value.
  4. The 20dB coupled port of the beat between the EX and PSL lasers was monitored using the AG4395A in "Spectrum" units.
  5. The beat was set at ~90 MHz, and a spectrum was taken for ~100 MHz span centered at the beat frequency.
  6. The modulation depth is estimated by considering the ratio of power at the beat frequency relative to that 35.5 MHz away. See Attachment #1.

Assuming a finesse of 700 for the PMC, we expect an optical gain of 2*Pin*J0(50e-3)*J1(50e-3)/fp  ~ 1.2e-7 W/Hz (=0.089 GW/m). I can't find a measurement of the PMC RFPD transimpedance to map this onto a V/Hz value. 

Attachment 1: modDepth.pdf
modDepth.pdf
  15138   Wed Jan 22 11:00:21 2020 gautamUpdatePSLPMC REFL ghost beam

I looked into this a little more today.

  1. The steering optic used to route PMC REFL to the RFPD is in fact a window (labelled W1-PW-1025-UV-1064-45P), not a High-T beamsplitter.
  2. With the PMC unlocked, I measured ~10.70 mW in the stronger of the two beams, 5.39 mW in the weaker one. 
    • The window spec is Tp > 97%. Since we have ~1.3 W incident on the PMC, the primary reflection corresponds to T=99.2%, which is consistent with the spec.
    • There is no spec given for the coating on the back side of this window. But from the measured values, it seems to be R = 100* 5.39e-3 / (1.3*T^2) ~ 0.4%. Seems reasonable.

Currently, the iris is set up such that the stronger beam makes it to the PMC RFPD, while the weaker one is blocked by the iris. As usual, this isn't a new issue - was noted last in 2014, but who knows whether the new window was intalled...

Quote:

Today I noticed that the beam reflected from the PMC into the RFPD has a ghost (attachment) due to reflection from the back of the high transmission beam splitter that stirs the beam into the RFPD.

  15135   Mon Jan 20 20:20:36 2020 gautamUpdatePSLPMC servo checkout

Summary:

The PDH discriminant of the PMC servo was measured to be ~0.064 GV/m. This is ~50 times lower than what is reported here. Perhaps this is a signature of the infamous ERA decay, needs more investigation.

Details:

  • Calibration of the error and control points were done using 1 Hz triangle wave injection to the "EXT DC" input of the PMC servo. Two such sweeps are shown in Attachment #1 (measured data as points, fits as solid lines). For the control signal monitor, I've multiplied the signal obtained on the scope by 49.6, which is the voltage divider implemented for this monitor point.
  • The PDH discrimiannt was calibrated into physical units knowing the modulation frequency of the PMC, which is 35.5 MHz. The error in this technique due to the free-running NPRO frequency noise is expected to be small since the entire fringe is crossed in <30 ms, in which time the laser frequency is expected to change by < 5 kHz.
  • The drive to the PZT was calibrated into physical units using the same technique. This number is within a factor of 2 of the number reported here
  • Attachment #2 shows the loop OLTF measured using the usual IN1/IN2 prescription (with an SR560). In fact, the 8kHz feature makes the loop unstable. For convenience, I've overlaid the OLTF from March 2017, when things were running smoothly. It is not clear to me why even though the optical gain is now lower, a smaller servo gain results in a larger UGF.

The light level hasn't changed by a factor of 50, leading me to suspect the modulation depth. Recall that the demodulation of the PMC is now done off the servo board using a minicircuits mixer (hence, the "C1:PSL-PMC_LODET" channel isn't a reliable readback of the LO signal strength over time). Although there is a C1:PSL-PMC_MODET channel which looks like it comes from the crystal reference card, and so should still work - this, however, shows no degradation over 1 year.

Somebody had removed the BLP-1.9 that I installed at the I/F output of the mixer to remove the sum frequency component in the demodulated signal, I reinstalled this. I find that there are oscillations in the error signal if the PMC servo gain is increased above 14.5 on the MEDM slider.

Attachment 1: PMCsweep.pdf
PMCsweep.pdf
Attachment 2: OLTFmeas.pdf
OLTFmeas.pdf
  15134   Mon Jan 20 15:11:20 2020 gautamUpdatePSLPMCT photodiode grounding issue

For a few days, I've noticed that the PSL overview StripTool panel shows PMC transmission and FSS RMTEMP channels with variation that is too large to be believable. Looking at these signals on an oscilloscope, there was no such fuzziness in the waveform. I ruled out flaky connections, and while these are the only two channels currently being acquired by the temporary Acromag setup underneath the PSL enclosure, the Acromags themselves are not to blame, because once I connected a function generator to the Acromag instead of the PMC transmission photodiode, both channels are well behaved. So the problem seems to be with the PMC transmission photodiode, perhaps a grouding issue? Someone please fix this.

Attachment 1: PMCT_anomaly.pdf
PMCT_anomaly.pdf
  15133   Mon Jan 20 12:16:50 2020 gautamUpdatePSLPMC input reverted to AOM zeroth order beam

Summary:

  1. The input beam to the PMC cavity was changed back to the zeroth order beam from the AOM. 
  2. The PMC was locked and nominal transmission levels were recovered.
  3. The AOM driver voltage was set to 0V DC. 
  4. A razor beam dump was placed to catch the first (and higher order) beams from the AOM (see Attachment #1), but allow the zeroth order beam to reach the PMC cavity.
  5. Some dangling cabling was cleared from the PSL enclosure.

Details

  • HEPA turned to 100% while work was going on in the PSL enclosure.
  • Input power to the PMC cut from ~1.3 W to ~20 mW using the first available HWP downstream of the laser head, before any realignment work was done.
  • Next, the beam dump blocking the undeflected zeroth order beam was removed.
  • Triangle wave was applied to the PZT servo board "EXT DC" input to sweep the cavity length to make the alignment easier.
  • After some patient alignment, I could see a weak transmitted beam locked to some high order mode, at which point I increased the input power to 200mW, and did the fine alignment by looking at the mode shape of the transmitted beam.
  • Once I could lock to a TEM00 mode, I bumped the power back up to the nominal 1.3W, I fine tuned the alignment further by minimizing PMC REFL's DC level. 
  • Dialled the power back down (using HWP) for installation of the beam block to catch the AOM's first (and higher order) beams.
  • Checked that the reflected beam from the PMC cavity is well centered on the PMC REFL PDH photodiode. The ghost from the AR coating of the high-T beamsplitter is blocked by the iris installed by yehonathan on Friday. 
  • The beam was a little low on the PMC REFL CCD camera - I raised the camera by ~1cm.
  • With the beam axis well matched to the PMC, I measured 1.33 mW going into the cavity, and 1.1 W transmitted, so T_{\mathrm{PMC}} \approx 83 \, \%. Whatever loss numbers we extract should be consistent with this fact.
  • HEPA turned back down to 30% shortly after noon.

Note that for all the alignment work, only the two steering mirrors immediately upstream of the PMC cavity were touched.

Attachment 1: IMG_8362.JPG
IMG_8362.JPG
  15132   Fri Jan 17 22:11:19 2020 YehonathanUpdatePSLRingdown measurements

I prepare for the ringdown measurement of the PMC according to Gautam's previous experiments.

1. I assembled the needed PDs and power supplies, lenses, beamsplitters and optomechanics needed for the measurement.

2. I surveyed the laser power with an Ophir power meter in the different parts of the experiment. All the measurements were done with the AOM driver excited with 1V DC.

For the PMC reflection, we chose to split off the beam that goes into the reflection camera. The power in that beam is ~ 0.11mW when the PMC is locked and 2.1mW otherwise.

For the PMC transmission, we chose to split the beam that is transmitted through the second steering mirror after the PMC. The power in that beam is 2mW.

For the peak off before the PMC, we chose to split the beam that goes into the fiber coupler. That path contains also the other AOM diffraction orders: 2.26mW in the 0th order beam, 6.5mW in the 1st order beam, 0.14mW in the 2nd order beam.

3. I placed a 10% beam splitter in the peak-off path such that 90% still goes into the fiber coupler (Attachment 1). I place a lens and PDA255 to measure the peak-off (Attachment 2).

It's getting late, I'll continue with the PD placements on Tuesday.

Attachment 1: 20200117_192455.jpg
20200117_192455.jpg
Attachment 2: 20200117_192448.jpg
20200117_192448.jpg
  15131   Fri Jan 17 21:56:22 2020 YehonathanUpdatePSLAOM first order beam alignment

Today I noticed that the beam reflected from the PMC into the RFPD has a ghost (attachment) due to reflection from the back of the high transmission beam splitter that stirs the beam into the RFPD.

The two beams are focused into the RFPD.

In the past, the ghost beam was probably blocked by the BS mirror mount.

I put an iris to block the ghost beam.

Attachment 1: 20200117_174841.jpg
20200117_174841.jpg
  15130   Fri Jan 17 18:02:21 2020 gautamUpdateALSGain blocks packaged and characterized

Summary:

  1. The ZHL-1010+ gain blocks acquired from MiniCircuits arrived sometime ago.
  2. I packaged them in a box prepared  (Attachment #1).
  3. Their performance was characterized by me (Attachment #2 and #3).

The measurements are consistent with the specifications, and there is no evidence of compression at any of the power levels we expect to supply to this box (<0dBm).

Details:

These "gain blocks" were acquired for the purpose of amplifying the IR ALS beat signals before transmission to the LSC rack for demodulation. The existing ZHL-3A amplifiers have a little too much gain, since our revamp to use IR light to generate the ALS beat.

Attachment #4: Setups used to measure transfer functions and noise.

For the transfer function measurement, I chose to send the output of the amplifier to a coupler, and measured the coupled port (output port of the coupler was terminated with 50 ohms). This was to avoid saturating the input of the AG4395. The "THRU" calibration feature of the AG4395 was used to remove the effect of cabling, coupler etc, so that the measurement is a true reflection of the transfer function of OUT/IN of this box. Yet, there are some periodic ripples present in the measured gain, though the size of these ripples is smaller than the spec-ed gain flatness of <0.6dB.

For the noise measurement, the plots I've presented in Attachment #3 are scaled by a factor of sqrt(2) since the noise of the ZFL-500-HLN+ and the ZHL-1010+ are nearly identical according to the specification. Note that the output noise measured was divided by the (measured) gain of the ZFL-500-HLN+ and the ZFL-1010+ to get the input referred noise. The trace labelled "Measurement noise floor" was measured with the input to the ZFL-500-HLN+ terminated with 50ohms, while for the other two traces, the inputs of the ZHL-1010+ were terminated with 50ohms.

Raw data in Attachment #5.

I will install these at the next opportunity, so that we can get rid of the many attenuators in this path (the main difficulty will be sourcing the required +12V DC for operation, we only have +15V available near the PSL table).

Attachment 1: photos.pdf
photos.pdf
Attachment 2: gain.pdf
gain.pdf
Attachment 3: noise.pdf
noise.pdf
Attachment 4: measSchem.pdf
measSchem.pdf
Attachment 5: zhl1010Data.zip
  15129   Thu Jan 16 19:32:23 2020 shrutiUpdateGeneralPLL / PM measurement of Xend NPRO PZT

With Gautam's help today the PLL managed to be be locked for a few brief moments. Turns out the signal power of the beat was an issue.

What was changed prior to/ during the experiment:

1. The PSL shutter was closed so not light goes into the input mode cleaner.

2. HEPA turned up (will be turned back down to ~30%)

3. AOM driver offset voltage decreased from 1V to ~100 mV (this will be reverted to 1V by the end of today). This increases the beat signal by deflecting the zeroth order beam to create the beat.

4. Output of servo SR 560 sent to the PZT of the X NPRO laser (the cable was disconnected from the pomona box at the X end)

5. The SR560, mixer, LPF and cables required for connections were moved into the PSL enclosure.

6. The error and control signals were hooked up to the oscilloscope where the beat outputs were visible (the setup has been reverted back to the original).

 

Elog 14687 has a detailed description of the conditions that provide a stable lock. I was told that the PI controller (LB1005) may be a better servo than the SR560, but today it was not used.

1) Parameters during the more successful attempts:

LPF: 5 MHz, Mixer: ZP-3+

Gain set at SR560: varied, but generally 200

Filter at SR560: 1 Hz low pass (single pole? at least by the label)

2) The LO had to be very close (<2 MHz) to the beat frequency in order to achieve a lock for ~30s


gautam edits:

  • the error signal for the PLL was being sourced from the 20dB coupled port on the BeatMouth.
  • additionally, most of the power in the PSL beam coupled into the fiber was being deflected into the first order beam by team ringdown.
  • The Vpp of the mixer output (when using the coupled beat and low PSL beam power) was a paltry 5-10 mVpp no.
  • I suggested using the direct NF1611 output for this measurement instead of the coupled output (alternatively, use an amp). it's probably also better to use the LB1005 for locking the PLL, long term, this can be set up to be controlled remotely, and a slow PID servo can be used to extend the duration of the lock by servoing either the marconi carrier freq or the EX temp ctrl.
Quote:

1. Some calculations

For a Unity Gain Frequency (UGF) of 1 kHz, assumed PZT response K_{VCO} of 1 MHz/V, Mixer response K_{M} of 25 mV/\pi rad, the required gain of the amplifier is

G = 2 \pi \times \text{UGF}/ (K_{VCO} K_M)

G ~ 0.8

2. Progress

- Measured the mixer response

Measuring mixer response:

- PSL laser temperature was adjusted so that beat frequency was roughly 25 MHz and the amplitude was found to be roughly -30dBm.

- At the RF port instead of the beat signal, a signal of 25 MHz + few kHz at -30 dBm was inputted. The LO was a 25 MHz signal was sent from the Marconi at 7 dBm.

- The mixer output was measured, with setup as in Attachment 1  Figure (A), on an oscilloscope. The slope near the small angle region of the sine curve would be the gain (in V/rad) and was found to be: K_M \approx 25 \text{ mV}/ \pi rad

- Since from the above calculations it seemed like an amplifer gain of 1 should work for the PLL, I rearranged the set up as in Figure (B) of Attachment 1 to actuate the X end NPRO PZT, I adjusted the PSL temperature (slow control) to try and match the frequency to 25 MHz, but couldn't lock the loop. I was monitoring the error signal after amplification (50 ohm output of the SR 560) which showed oscillations when the beat frequency was near 25 MHz and nothing significant otherwise.

- I used a 20 dB attenuator at the amplifier output and saw the beat note oscillate for longer, but maybe because it was a 50 ohm component in a high impedance channel it did not work either (?). I tried other attenuator combinations with no better luck.

- Is there a better location to add the attenuator? Should I pursue amplifying the beat signal instead?

- Also, it seemed like the beat note drift was higher than earlier. Could it be because the PMC was unlocke

  15128   Wed Jan 15 16:54:51 2020 gautamUpdateGeneralPDA10CF removed from AS table

Per Yehonathan's request, I removed one PDA10CF from a pickoff of REFL on the AS table (it was being used for the mode spectroscopy project). I placed a razor beam dump where the PD used to be, so that when the PRM is aligned, this pickoff is dumped. This is so that team ringdowns can use a fast PD.

  15127   Wed Jan 15 16:08:40 2020 not gautamUpdatePSLAssembly underway for c1psl upgrade

You're right. We had the right idea before but we got confused about this issue. I changed all the XT1121s to XT1111 and vice versa. We already know which channels are sourcing and which not. Updated the wiring spreadsheet. The chassis seems to work. It's time to pass it over to Chub.

Quote:

I don't think this is an accurate statement. XT1111 modules have sinking digital outputs, while XT1121 modules have sourcing digital outputs. Depending on the requirement, the appropriate units should be used. I believe the XT1111 is the appropriate choice for most of our circuits.

For digital outputs, one should XT1121. XT1111 should be used for digital inputs.

  15126   Wed Jan 15 15:04:31 2020 gautamUpdatePSLPMC Linewidth measurement

For the ringdowns, I suggest you replicate the setup I had - infrastructurally, this was quite robust, and the main problem I had was that I couldn't extinguish the beam completely. Now that we have the 1st order beam, it should be easy.

  15125   Wed Jan 15 14:10:28 2020 JonConfigurationPSLNew EPICS database for C1PSL + C1IOO

Summary

I have completed the new EPICS channel database for the c1psl and c1ioo channels (now combined into the new c1psl Acromag machine). I've tested a small subset of channels on the electronics bench to confirm that the addressing and analog channel calibrations are correct in a general sense. At this point, we are handing the chassis off to Chub to complete the wiring of the Acromag terminals to Dsub feedthroughs. At the 40m meeting today, we identified Feb. 17-22 as a potential window for installation in the interferometer (Gautam is out of town then). Below are some implementaton details for future reference.

Analog channel calibration for Acromag

For analog input (ai) channels, the Acromag outputs raw values ranging from +/-30,000 counts, but the EPICS IOC interprets the data type as ranging from +/-2^15 = 32,768. Similarly, for analog output (ao) channels, the Acromag expects a drive signal in the range +/-30,000 counts. To achieve proper scaling, Johannes had previously changed the EGUF and EGUL fields from +/-10 V to +/-10.923 V. However, changing the engineering fields makes it much harder for a human to read off the real physical I/O range of the channel.

A better way to achieve the correct scaling is to simply set the field  ASLO=1.09225 (65,536 / 60,001) in addition to the normal EGUF and EGUL field values (+/-10 V). Setting this field forces a rescaling of the number of raw counts that works as so (assuming a 16-bit bipolar ADC or DAC, as are the Acromags):

OVAL = (RVAL * ASLO + AOFF + 2^15) * (EGUF - EGUL) / 2^16 + EGUL

In the above mapping, OVAL is the value of the channel in engineering units (e.g., V) and RVAL is its raw value in counts. It is not the case that either the ASLO/AOFF or EGUF/EGUL fields are used, but not both. The ASLO/AOFF parameters are always applied (but their default values are ASLO=1 and AOFF=0, so have no effect unless changed). The EGUF and EGUL parameters are then additionally applied if the field LINR="LINEAR" is set.

This conversion allows the engineering fields to remain unchanged from the real physical range. The ASLO value is the same for both analog input and output channels. I have implemented this on all the new c1psl and c1ioo channels and confirmed it to work using a calibrated input voltage source.

  15124   Wed Jan 15 10:12:46 2020 gautamUpdatePSLAssembly underway for c1psl upgrade

I don't think this is an accurate statement. XT1111 modules have sinking digital outputs, while XT1121 modules have sourcing digital outputs. Depending on the requirement, the appropriate units should be used. I believe the XT1111 is the appropriate choice for most of our circuits.

For digital outputs, one should XT1121. XT1111 should be used for digital inputs.

  15123   Wed Jan 15 10:04:19 2020 gautamSummaryGeneralPOX / POY locking restored

Single arm locking using POX and POY has been restored. After running the dither alignment servos, the TRX/TRY levels are ~0.7. This is consistent with the IMC transmission being ~11000 counts with the AOM 1st order diffracted beam (c.f. 15000 counts with the undiffracted beam).

Quote:

Tomorrow, I'll check the single-arm locking and the ALS system.

Attachment 1: singleArms.png
singleArms.png
  15122   Wed Jan 15 08:55:14 2020 gautamUpdateCDSYearly DAQD fix

Summary:

Every new year (on Dec 31 or Jan 1), all of the realtime models will report a "0x4000" error. This happens due to an offset to the GPStime driver not being updated. Here is how this can be fixed (slightly modified version of what was done at LASTI).

Steps to fix the DC errors:

  1. ssh into FB machine. 
  2. Edit the file /opt/rtcds/rtscore/release/src/include/drv/spectracomGPS.c:
    • Look for the code block with a text string that reads something like
      /* 2019 had 365 days and no leap seconds */
                   pHardware->gpsOffset += 31536000;
    • Copy and paste the above string for the appropriate number of years of offset you are adding, and edit the comment string appropriately!.
  3. Navigate to /opt/rtcds/rtscore/release/src/drv/symmetricom. Run the following commands:
    sudo make
    sudo make install
  4. Stop all the daqd processes and reload symmetricom:
    sudo systemctl daqd_* stop
    sudo modprobe -r symmetricom
    sudo modprobe symmetricom
  5. Re-start the daqd processes:
    sudo service daqd_* start

Independent of this, there is a 1 second offset between the gpstimes reported by /proc/gps and gpstime. However, this doesn't seem to drift. We had effected a static offset to correct for this in the daqd config files, and it looks like these do not need to be updated on a yearly basis. All the daqd indicators are now green, see Attachment #1.

Attachment 1: DCerrors_fixed.png
DCerrors_fixed.png
  15121   Tue Jan 14 20:17:09 2020 gautamSummaryGeneralIFO recovery

Summary:

There was no light entering the IFO. I worked on a few things to bring the interferometer to a somewhat usable state. The goal is to get back to PRFPMI locking ASAP.

Details:

Problem: All fast models report a "0x4000" DC error. See Attachment #1.

Solution: I think this is a "known" issue that happened last new year too. The fix was to add a hard-coded 1 second offset to the daqd config files. However, incrementing/decreasing this offset by +/- 1 second did not fix the errors for me today. I'll reach out to JH for more troubleshooting tips.

Update 15 Jan 2020 830am: The problem is now fixed. See here.

Problem: c1susaux and c1auxey were unresponsive.

Solution: Keyed c1auxey. Rebooted c1susaux and as usual, manually started the eth0/eth1 subnets. The Acromag crate did not have to be power-cycled. ITMY got stuck in this process - I released it using the usual bias jiggling. Why did c1susaux fail? When did it fail? Was there some un-elogged cable jiggling in that part of the lab?

Problem: IMC autolocker and FSS slow processes aren't running on megatron after the upgrade.

Solution: Since no one bothered to do this, I setup systemd infrastructure for doing this on megatron. To run these, you do:

sudo systemctl start MCautolocker.service
sudo systemctl start FSSSlow.service

and to check their status, use:

sudo systemctl status MCautolocker.service
sudo systemctl status FSSSlow.service

The systemd setup is currently done in a naive way (using the bash executable to run a series of commands rather than using the systemd infrastructure itself to setup variables etc) but it works. I confirmed that the autolocker can re-acquire IMC lock, and that the FSS loop only runs when the IMC is locked. I also removed the obsolete messages printed to megatron's console (by editing /etc/motd) on ssh-login, advising the usage of initctl - the updated message reflects the above instructions.

In order to do the IMC locking, I changed the DC voltage to the AOM to +1V DC (it was +0.8 V DC). In this setting, the IMC refl level is ~3.6 V DC. When using the undiffracted AOM beam, we had more like +5.6 V DC (so now we have ~65% of the nominal level) from the IMC REFL PD when the IMC was unlocked. IIRC, the diffraction efficiency of the AOM should be somewhat better, at ~85%. Needs investigation, or better yet, let's just go back to the old configuration of using the undiffracted beam.

There was also an UN-ELOGGED angry change of the nominal value of the PMC servo gain to 12.8, and no transfer function measurement. There needs to be a proper characterization of this loop done to decide what the new nominal value should be.

I'm going to leave the PSL shutter open and let the IMC stay locked for stability investigations. Tomorrow, I'll check the single-arm locking and the ALS system.

Attachment 1: DCerrors.png
DCerrors.png
  15120   Tue Jan 14 17:16:43 2020 yehonathanUpdatePSLAssembly underway for c1psl upgrade

{Yehonathan, Jon}

I isolated a BIO Acromag completely from the chassis and powered it up. The inverted behavior persisted.

Turns out this is normal behavior for the XT1111 model.

For digital outputs, one should XT1121. XT1111 should be used for digital inputs.

Slow machines Wiki page was updated along with other pieces of information.

I replaced the XT1111 Acromags with XT1121 and did some rewiring since the XT1121 cannot get the excitation voltage from the DIN rail.

I added an XT1111 Acromag for the single digital input we have in this system.

  15119   Mon Jan 13 23:30:53 2020 YehonathanSummaryPSLChanges made since Gautam left

As per Gautam's request, I list the changes that were made since he left:

1. The AOM driver was connected to a signal generator.

2. The first order beam from the AOM was coupled into the PMC while the zero-order beam is blocked. We might want to keep this configuration if the pointing stability is adequate.

3. c1psl got Burt restored to Dec 1st.

4. Megatron got updated.

Currently, c1susaux seems unresponsive and needs to be rebooted.

  15118   Mon Jan 13 16:05:18 2020 yehonathanUpdatePSLAssembly underway for c1psl upgrade

{Yehonathan, Jon}

I configured the Acromag channels according to the Slow Controls Wiki page.

We started testing the channels. Almost at the beginning we notice that the BIO channels are inverted. High voltage when 0. 0 Voltage when 1. We checked several things:

1. We checked the configuration of the BIOs in the windows machine but nothing pointed to the problem.

2. We isolated one of the BIOs from the DIN rail but the behavior persisted.

3. We checked that the voltages that go into the Acromags are correct.

The next step is to power up an isolated Acromag directly from the power supply. This will tell us if the problem is in the chassis or the EPICs DB.

  15117   Mon Jan 13 15:47:37 2020 shrutiConfigurationComputer Scripts / Programsc1psl burt restore

[Yehonathan, Jon, Shruti]

Since the PMC would not lock, we initially burt-restored the c1psl machine to the last available shapshot (Dec 10th 2019), but it still would not lock.

Then, it was burt-restored to midnight of Dec 1st, 2019, after which it could be locked.

  15116   Fri Jan 10 19:48:46 2020 yehonathanUpdatePSLAssembly underway for c1psl upgrade

{Yehonathan, Jon}

I finished pre-wiring the PSL chassis. I mounted the Acromags on the DIN rails and labeled them. I checked that they are powered up with the right voltage +24V and that the LEDs behave as expected.

Attachment 1: 20200110_194429.jpg
20200110_194429.jpg
Attachment 2: 20200110_194516_HDR.jpg
20200110_194516_HDR.jpg
  15115   Fri Jan 10 14:21:19 2020 YehonathanUpdatePSLc1psl reboot

PSL controls on the sitemap went blank. Rebooted c1psl. PSL screens seem normal again.

  15114   Tue Jan 7 18:51:51 2020 JonUpdatePSLNew c1psl server assembled

I've assembled a new SuperMicro rackmount machine to replace c1psl. It is currently set up on the electronics bench.

  • OS: Debian 10.2
  • Hostname: c1psl1 (will become c1psl after installation)
  • IP: 192.168.113.54 (registered in the martian DNS)
  • Network drive mount point set up (/cvs/cds), which provides all the EPICS executables.
  15113   Mon Jan 6 19:05:09 2020 not gautamUpdatePSLAssembly underway for c1psl upgrade

I found them, thanks. After c1psl, there are 4 2GB DIMM cards and 1 SSD left. I moved them into the storage bins with all the other Acromag parts.

Quote:

RTFE. Where did the spares go?

Quote:

I began setting up the host server, but immediately hit a problem: We seem to have no more memory cards or solid-state drives, despite having two more SuperMicro servers. I ordered enough RAM cards and drives to finish both machines. They will hopefully arrive tomorrow.

  15112   Mon Jan 6 16:07:12 2020 gautamUpdatePSLAssembly underway for c1psl upgrade

RTFE. Where did the spares go?

Quote:

I began setting up the host server, but immediately hit a problem: We seem to have no more memory cards or solid-state drives, despite having two more SuperMicro servers. I ordered enough RAM cards and drives to finish both machines. They will hopefully arrive tomorrow.

  15111   Mon Jan 6 15:36:55 2020 JonUpdatePSLAssembly underway for c1psl upgrade

[Jon, Yehonathan]

We've begun assembling the new c1psl Acromag chassis based on Yehonathan's final pin assignments. So far, parts have been gathered and the chassis itself has been assembled.

Yehonathan is currently wiring up the chassis power and Ethernet feedthroughs, following my wiring diagram from previous assemblies. Once the Acromag units are powered, I will help configure them, assign IPs, etc. We will then turn the wiring over to Chub to complete the Acromag to breakout board wiring.

I began setting up the host server, but immediately hit a problem: We seem to have no more memory cards or solid-state drives, despite having two more SuperMicro servers. I ordered enough RAM cards and drives to finish both machines. They will hopefully arrive tomorrow.

  15110   Wed Jan 1 16:04:37 2020 YehonathanUpdatePSLMapping the PSL electronics

Done.

Quote:

For the IMC servo board, it'd be easiest to copy the wiring scheme for the BIO bits as is configured for the CM board (i.e. copy the grouping of the BIO bits on the individual Acromag units). This will enable us to use the latch code with minimal modifications (it was a pain to debug this the first time around). I don't see any major constraint in the wiring assignment that'd make this difficult.

Quote:

PSL wiring spreadsheet is ready. (But the link was stripped. Koji)

Link to a wiki page  with the link to the wiring spreadsheet (Yehonathan)

 

  15109   Wed Jan 1 14:14:00 2020 YehonathanUpdatePSLPMC Linewidth measurement

Turns out the 35MHz sidebands are way too weak to resolve from the resonance when doing a PZT scan.

I connect the IFR2023B function generator on the PSL table to the EOM instead of the FSS box and set it to generate 150MHz at 13dbm.

To observe the resulting weak sideband I place a PDA55 at the peak-off path from the transmission of the PMC where there is much more light than the transmission of the PMC head mirror. Whoever is using this path there is a PD blocking it right now.

I do a PZT scan by connecting a triangular signal to the EXT DC on the PMC servo with and without the EOM (Attachment 1). A weak sideband can clearly be spotted now.

Using the above 150MHz sideband calibration I can find the roundtrip time to be 1.55ns.

I take a high-resolution scan of a resonance peak and fit it to a Lorentzian (Attachment 2) and find a roundtrip loss of 1.3%.

Using the above results the cavity decay time is 119ns.

We should investigate what's going on with the ringdown measurements.

Attachment 1: 150MHzSideBandCreation.pdf
150MHzSideBandCreation.pdf
Attachment 2: LinewidthMeasurment.pdf
LinewidthMeasurment.pdf
  15108   Wed Jan 1 04:53:11 2020 gautamUpdatePSLMapping the PSL electronics

For the IMC servo board, it'd be easiest to copy the wiring scheme for the BIO bits as is configured for the CM board (i.e. copy the grouping of the BIO bits on the individual Acromag units). This will enable us to use the latch code with minimal modifications (it was a pain to debug this the first time around). I don't see any major constraint in the wiring assignment that'd make this difficult.

Quote:

PSL wiring spreadsheet is ready. (But the link was stripped. Koji)

Link to a wiki page  with the link to the wiring spreadsheet (Yehonathan)

  15107   Tue Dec 31 03:03:02 2019 gautamUpdatePSLPMC cavity ringdown measurement

When I was looking at this, the AOM shutdown time was measured to be ~120 ns, and while I wasn't able to do a ringdown measurement with the PMC (it'd just stay locked because at the time i was using the zeroth order beam), the PMC transmission decayed in <200 ns. 

  15106   Fri Dec 27 16:26:11 2019 YehonathanUpdatePSLPMC Linewidth measurement

I try to measure the linewidth of the PMC by ramping the PMC PZT. 

I do it by connecting a triangular shape signal to FP Test 1 on the PMC servo front panel (I know, it is probably better to connect it to DC EXT. next time.) and turn the servo gain to a minimum.

Attachment 1 shows the PMC transmission PD as the PZT is swept with the EOM connected and when it is disconnected. It shows the PMC over more than 1 free spectral range.

For some reason, I cannot seem to be able to find the 35MHz sidebands which I want to use to calibrate the PZT scan. I made sure that the EOM is driven by a 35MHz signal using the scope. I also made sure that the PMC cannot to lock without the EOM connected.

I am probably doing something silly.

Attachment 1: PMCTransmissionSpectra.pdf
PMCTransmissionSpectra.pdf
  15105   Fri Dec 27 15:01:02 2019 YehonathanUpdatePSLPMC cavity ringdown measurement

I measured PMC ringdowns for several input powers. I change the input power by changing the DC voltage to the AOM.

First, I raise the DC voltage to the AOM from 0V and observe the signal on the picked off PD. I see that at around 0.6V the signal stops rising. The signal on the PD is around 4V at that point so it is not saturated.

Up until now, we provided 1.5V to the AOM, which means it was saturated.

I measured ringdowns at AOM voltages of 0.05, 0.1, 0.3, 0.5, 1 volt by shutting off the DC voltage to the AOM and measuring the signal at the PMC transmission PD and the picked off PD simultaneously for reference.

Attachment 1 shows the reference measurement for different AOM voltages. For low AOM DC voltages, the response of the AOM+PD is slower.

Attachment 2 shows the PMC transmission PD measurements which barely change as a function of AOM voltage but shows the same trend. I believe that if the AOM+PD response was much faster there would be no observable difference between those measurements.

Attachment 3 shows PMC transmissions and references for AOM voltages 0.05V and 1V. It seems like for low AOM voltages we are barely fast enough to measure the PMC ringdown.

I fitted the 0.3V ringdown and reference to a sum of two exponentials (Attachment 4).

The fitting function is explicitly a * nm.exp(-x/b) +c* nm.exp(-x/d) +e

For the PMC transmission I get:

a = 0.21
b = 3.64 (us)
c = 0.69, 
d = 39.62 (us)
e = 2.0e-04

For the reference measurement:

a = 0.34
b = 4.97 (us)
c = 0.58
d= 31.22 (us)
e = 1.11e-03

I am still not able to do deconvolution of the ref from the measurement reliably. I think we should do a network analyzer measurement.

Shruti, the PD is again in your beam path.

Attachment 1: PDAOMResponse.pdf
PDAOMResponse.pdf
Attachment 2: PMCTransmission.pdf
PMCTransmission.pdf
Attachment 3: RingdownsAndRefs.pdf
RingdownsAndRefs.pdf
Attachment 4: TwoExponentialFitAOM0.3V.pdf
TwoExponentialFitAOM0.3V.pdf
  15104   Mon Dec 23 19:30:20 2019 YehonathanUpdatePSLMapping the PSL electronics

PSL wiring spreadsheet is ready. (But the link was stripped. Koji)

Link to a wiki page  with the link to the wiring spreadsheet (Yehonathan)

  15103   Fri Dec 20 18:33:21 2019 YehonathanUpdatePSLMapping the PSL electronics

Final (hopefully) PSL channel list is attached with allocated Acromag channels. Wiring spreadsheet coming soon.

Current Acromag count:

AI 8
AO 2
BIO 4
Number of channels 8*8+2*8+4*16=144
Number of wires 144*2=288

 

Attachment 1: PSL_Wirings_-_Channel_List.pdf
PSL_Wirings_-_Channel_List.pdf PSL_Wirings_-_Channel_List.pdf PSL_Wirings_-_Channel_List.pdf PSL_Wirings_-_Channel_List.pdf PSL_Wirings_-_Channel_List.pdf
  15102   Tue Dec 17 20:45:30 2019 ranaUpdatePSLPMC cavity ringdown measurement

idk - I'm recently worried about the 'thermal self locking' issue we discussed. I think you should try to measure the linewidth by scanning (with low input power) and also measure the TF directly by modulating the power via the AOM and taking the ratio of input/output with the PDA55s. I'm curious to see if the ringdown is different for low and high powers

Quote:

I plan to model the PD+AOM as a lowpass filter with an RC time constant of 12us and undo its filtering action on the PMC trans ringdown measurement to get the actual ringdown time.

Is this acceptable?

This is an ole SURF report on thermal self-locking that may be of use (I haven't read it or checked it for errors, but Royal was pretty good analytically, so its worth looking at)

  15101   Tue Dec 17 20:08:09 2019 shrutiUpdateGeneralPLL / PM measurement of Xend NPRO PZT

1. Some calculations

For a Unity Gain Frequency (UGF) of 1 kHz, assumed PZT response K_{VCO} of 1 MHz/V, Mixer response K_{M} of 25 mV/\pi rad, the required gain of the amplifier is

G = 2 \pi \times \text{UGF}/ (K_{VCO} K_M)

G ~ 0.8

2. Progress

- Measured the mixer response

Measuring mixer response:

- PSL laser temperature was adjusted so that beat frequency was roughly 25 MHz and the amplitude was found to be roughly -30dBm.

- At the RF port instead of the beat signal, a signal of 25 MHz + few kHz at -30 dBm was inputted. The LO was a 25 MHz signal was sent from the Marconi at 7 dBm.

- The mixer output was measured, with setup as in Attachment 1  Figure (A), on an oscilloscope. The slope near the small angle region of the sine curve would be the gain (in V/rad) and was found to be: K_M \approx 25 \text{ mV}/ \pi rad

- Since from the above calculations it seemed like an amplifer gain of 1 should work for the PLL, I rearranged the set up as in Figure (B) of Attachment 1 to actuate the X end NPRO PZT, I adjusted the PSL temperature (slow control) to try and match the frequency to 25 MHz, but couldn't lock the loop. I was monitoring the error signal after amplification (50 ohm output of the SR 560) which showed oscillations when the beat frequency was near 25 MHz and nothing significant otherwise.

- I used a 20 dB attenuator at the amplifier output and saw the beat note oscillate for longer, but maybe because it was a 50 ohm component in a high impedance channel it did not work either (?). I tried other attenuator combinations with no better luck.

- Is there a better location to add the attenuator? Should I pursue amplifying the beat signal instead?

- Also, it seemed like the beat note drift was higher than earlier. Could it be because the PMC was unlocked?

 

Quote:
 

 

Attachment 1: 20191217.png
20191217.png
  15100   Tue Dec 17 18:05:06 2019 YehonathanUpdatePSLMapping the PSL electronics

Updated the channel list (Attached):

1. Removed the MC steering mirror PZT channels

2. Added Sourcing/Sinking column

3. Recounted the mbbos correctly

4. Allocated Acromags:

Model Purpose No. Spare channels
XT1221 ai 7 11
XT1541 ao + src bo 2 9 ao
XT1121 src bo 2 4
XT1121 sink bo 1 4

I think we can start wiring.

Attachment 1: PSL_Wirings_-_Sheet1_(3).pdf
PSL_Wirings_-_Sheet1_(3).pdf PSL_Wirings_-_Sheet1_(3).pdf
  15099   Tue Dec 17 00:23:28 2019 YehonathanUpdatePSLMapping the PSL electronics

I added to the PSL wiring list the ioo channels and the laser shutter (See attached pdf for an updated list).

The total channel numbers for now:

ai 57
ao 13
bi 1
bo 36

I counted each mbbo as 1 bo but I am not sure that's correct.

Still need to allocate Acromags.

Attachment 1: PSL_Wirings_-_Sheet1_(2).pdf
PSL_Wirings_-_Sheet1_(2).pdf PSL_Wirings_-_Sheet1_(2).pdf
  15098   Mon Dec 16 18:19:42 2019 shrutiUpdatePSLPMC cavity ringdown measurement : beat-note disruption

I have removed the PD55 + ND filter attached to it (see Attachment) and placed it next to the oscilloscope, after disconnecting its output and power supply. The post is still in place.

I did see the beat after that.

Quote:

{Yehonathan, Rana, Jon}

To check whether we laser is being shut fast enough for the ringdown measurement we put a PD55 in the path that leads to the beat note setup. The beam is picked off from the back steering mirror after AOM and before the PMC.

@Shruti the PD is now blocking the beam to your setup.

 

Attachment 1: IMG_0040.jpg
IMG_0040.jpg
  15097   Fri Dec 13 12:28:43 2019 YehonathanUpdatePSLPMC cavity ringdown measurement

I grab the data we recorded yesterday from the scope and plot it in normalized units (remove noise level and divide by maximum). See attachment.

It can be seen that the measured ringdown time is ~ 17us while the shut-off time is ~12us.

I plan to model the PD+AOM as a lowpass filter with an RC time constant of 12us and undo its filtering action on the PMC trans ringdown measurement to get the actual ringdown time.

Is this acceptable?

 

Attachment 1: Ringdown_InitialProcess.pdf
Ringdown_InitialProcess.pdf
  15096   Thu Dec 12 19:20:43 2019 YehonathanUpdatePSLPMC cavity ringdown measurement

{Yehonathan, Rana, Jon}

To check whether we laser is being shut fast enough for the ringdown measurement we put a PD55 in the path that leads to the beat note setup. The beam is picked off from the back steering mirror after AOM and before the PMC.

@Shruti the PD is now blocking the beam to your setup.

As before, we drive the AOM to deflect the beam. The deflected beam is coupled to the PMC cavity. We lock the PMC and then shut the beam by turning off the output of the function generator that provides voltage to the AOM driver.

We measure the transmitted light of the PMC together with the light that is picked off before the PMC. In Attachment 1, the purple trace is the PMC transmission, the green trace is the peaked-off beam and the yellow trace is the function generator signal.

Rana was pointing out that the PDs, the function generator and the scope were not carefully impedance matched, which could lead to erroneous measurements. He also mentioned that the backscattered beam was too bright which might indicate that the PMC is oscillating. To remedy this we lowered the gain of the PMC lock to ~8.

We repeat the measurement after setting all the components to 50ohm (attachment 2). We then realize that the BNC T junction connected on the function generator is splitting the signal between the 50ohm AOM driver and 1Mohm oscilloscope channel which causes distortions as can be seen. We remove the T junction and get a much cleaner measurement (see next elog).

 

It seems like either the shutting speed or the PDs are only slightly faster than the PMC. I also check the AOM driver RF output fall time doing the same kind of measurement (attachment 3).

We suspect the PDs' bandwidth is to blame (although they are quoted to have 10MHz bandwidth).

In any case, this is fast enough for the IMC and arm cavities whose lifetime should be much longer than the PMC.

I will post an elog with some numbers tomorrow.

Attachment 1: IMG_0105.jpeg
IMG_0105.jpeg
Attachment 2: TEK00001.PNG
TEK00001.PNG
Attachment 3: 20191212_151642.jpg
20191212_151642.jpg
  15095   Wed Dec 11 22:01:24 2019 ranaConfigurationComputersMegatron: starts up grade

Megatron is now running Ubuntu 18.04 LTS.

We should probably be able to load all the LSC software on there by adding the appropriate Debian repos.

I have re-enabled the cron jobs in the crontab.

The MC Autolocker and the PSL NPRO Slow/Temperature control are run using 'initctl', so I'll leave that up to Shruti to run/test.

  15094   Wed Dec 11 15:29:17 2019 YehonathanUpdatePSLPMC is locked

Make sure to measure the power drop of the beam downstream of the AOM but before the PMC. Need to plot both together to make sure the chop time is much shorter than the 1/e time.

  15093   Wed Dec 11 15:01:57 2019 JonSummaryPSLPMC cavity ringdown measurement

[Jon, Yehonathan]

We carried out a set of cavity ringdown measurements of the PMC. The 1/e decay time scale is found to be 35.2 +/- 2.4 (systematic) μs. The statistical error is negligible compared to the systematic error, which is taken as the maximum absolute deviation of any measurement from the average value.

To make the measurement, we injected the first order deflection beam of an 80 MHz AOM, then extinguished it quickly by cutting the voltage offset to the AOM driver provided by an RF function generator. A 100 MHz oscilloscope configured to trigger on the falling voltage offset was used to sample the cavity in transmission as sensed by a PDA55. We found the detector noise of the DC-coupled output of the 35.5 MHz REFL PD to be too high for a reflection-side measurement.

Further loss analysis is forthcoming.

Attachment 1: IMG_0101.jpg
IMG_0101.jpg
  15092   Tue Dec 10 18:27:22 2019 YehonathanUpdatePSLPMC is locked

{Yehonathan, Jon}

We are able to lock the PMC on the TEM00 mode of the deflected beam.

However when we turn off the driving voltage to the AOM and back on the lock is not restored. It get stuck on some higher order mode.

There are plethora of modes present when the PZT is scanned, which makes us believe the cavity is misaligned.

 

To lock again on the TEM00 mode again we disconnect the loop (FP Test point 1), find a TEM00 mode using the DC output adjust and close the loop again.

 

ELOG V3.1.3-