40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 258 of 339  Not logged in ELOG logo
IDup Date Author Type Category Subject
  12938   Mon Apr 10 18:42:09 2017 johannesUpdateCamerasPylon installation warning

It looks like we may not need to use this old Pylon version after all. Gautam and I looked into installing SnapPy with the makefile in scripts/GigE/SnapPy/ that he modified (removed the linkage to paths that don't exist in Pylon 5). Compiling took a while (~10 minutes) but eventually succeeded. The package was installed to /ligo/apps/linux-x86_64/camera/

GV 10pm April 10 2017: We didn't actually try executing an image capture or change some settings using the python utilities, that remains to be done..

  12939   Tue Apr 11 00:38:37 2017 gautamUpdatePSLPMC demod moved off servo board

As discussed at the Wednesday meeting last week, I tried moving the demodulation of the PMC error signal off the PMC servo board, by using some minicircuits components. This is just a quick summary elog, more details to follow tomorrow.

  • I used the Mini Circuits ZAD-6+. This is a level 7 mixer, and the LO board puts out ~16dBm, so I replaced the existing 3dB attenuator between the LO board and the input to the PMC servo board with a 9dB attenuator.
  • On the RF side, I retained the 35.5 MHz bandpass filter on the PD input.
  • On the IF output, I used an in-line 50ohm terminator in series with a minicircuits BLP1.9+ low pass filter
  • The mixer output was routed to the FP1 test input of the servo board
  • After some twiddling with the demod phase MEDM screen, I was able to lock the PMC. I've not done a thorough characterization of the loop with the current configuration, this will be done tomorrow. But the PMC and IMC have been stably locked for the last couple of hours...

During the course of this work, I noticed that there was a 35.5MHz line (at ~-55dBm) in the 4-pin LEMO DAQ outputs even when all other inputs to the servo board were terminated. So it seems like this pickup is not coming from the RFPD or demod path. The LO board has a shield enclosure similar to what we have on the LSC demod boards, but perhaps this shield does not enclose the full RF path, and there is some residual pickup between the two cards in close proximity in the Eurocrate?

On the bright side, with this demod setup, the higher harmonic peaks seem to be significantly suppressed.

In particular, the 3x35.5 MHz peak which was very prominent when I looked at these spectra with the nominal demod setup, seems to be much suppressed. 

I'm leaving the PMC servo in this configuration (off servo board demodulation using minicircuits parts) overnight.

Attachment 1: PMC_Ctrl_spec.pdf
PMC_Ctrl_spec.pdf
  12940   Wed Apr 12 00:36:53 2017 gautamUpdatePSLPMC demod moved off servo board

Here is a more detailed comparison of the spectra of the signals at the front panel DAQ LEMO output, measured with the Agilent analyzer. I've left the scale linear, it looks like when the demodulation is done on the servo board, the 1x, 3x and 5x harmonics of the 35.5MHz modulation are clearly visible. I also plut in a plot of the spectra when both the PD and LO inputs to the servo board are terminated (and so the PMC is unlocked), but with the HV In and OUT of the servo board still connected. In this case, the higher harmonics vanish, but a 35.5MHz peak of ~-50dBm remains. Since this is present with no input to the servo board, this must be direct pickup from the nearby LO board? 

In any case, it looks like many of the harmonics that are present with the nominal demod setup either vanish or are much more suppressed when the error signal demodulation is done off the servo board yes.


Further down the signal chain, I had noticed sometime last week that the ADC signals for the PMC DAQ channels I set up seemed to saturate around 4000 counts. Rana mentioned that the ADC interface box with LEMO connectors on the front is powered with +/-5V. Valera and co. had simply increased the suppy voltage sometime ago to get around this problem, so I did something similar, and increased the supply voltage to +/- 15V. I then confirmed that the ADC doesn't get saturated by driving the input with a +/-5V signal. So now the amplified AD620 signals from the PMC servo board are better matched to the ADC range. 

Here is an uncalibrated spectrum (taken with IMC locked), compared to the current ADC noise and signal levels before the AD620s were given gain.

I now need to think a little about what exactly the control scheme would be if the PMC is used as a reference for the IMC over some frequency range...

 

Attachment 1: PMC_digitalSpec.pdf
PMC_digitalSpec.pdf
Attachment 2: PMC_DAQ_spectra.pdf
PMC_DAQ_spectra.pdf
  12941   Thu Apr 13 09:48:37 2017 SteveUpdateSUSITMY-UL and ETMX sensors

Why ITMY UL can not see this earth quake? SRM and PRM are misaligned. ETMX is still not well.

We have to remember to check OSEM - magnet alignment when vented.

Attachment 1: ITMY.png
ITMY.png
Attachment 2: ITMY-UL.png
ITMY-UL.png
Attachment 3: ETMX?.png
ETMX?.png
  12942   Thu Apr 13 19:54:07 2017 ranaUpdateDAQcheckup on minute trends

Our minute trends are still not available through NDS2 from the outside world due to the bad config of the DAQ, but I can confirm that we still have the minute-raw capability. This is 111 days of Seismic BLRMS.

However, it seems we're only able to get ~1 week of lookback on our second trendssadno and that is low-down dirty shame. We used to have over a month of second trend lookback before the last decade of 'upgrades'.

Attachment 1: BRLMS-trend.png
BRLMS-trend.png
  12943   Thu Apr 13 21:01:20 2017 ranaConfigurationComputersLG UltraWide on Rossa

we installed a new curved 34" doublewide monitor on Rossa, but it seems like it has a defective dead pixel region in it. Unless it heals itself by morning, we should return it to Amazon. Please don't throw out he packing materials.

Steve 8am next morning: it is still bad The monitor is cracked. It got kicked while traveling. It's box is damaged the same place.

Shipped back 4-17-2017

Attachment 1: LG34c.jpg
LG34c.jpg
Attachment 2: crack.jpg
crack.jpg
  12944   Tue Apr 18 01:01:03 2017 gautamUpdatePSLPMC OLTF measured, DAQ channels calibrated

Quick entry, details to follow in the AM tomorrow.

  • I calibrated the PMC DAQ channels into physical units - there now exists in the filter modules  cts2m and cts2Hz filter modules, though of course only one must be used at a time
  • Finally measured the PMC OLTF, after moving the PMC PDH error signal demodulation off the servo board - I used the same procedure as Koji when he made the modifications to the PMC servo board, I will put up the algebra here tomorrow. Turns out the previously nominal servo gain of +10dB on the MEDM sliders was a little low, the new nominal gain is +20dB, and has been updated on the MEDM screen.

ToDo:

  • Put up the modified schematic on the 40m DCC tree Done April 18 10pm
  • Check calibration by comparing inferred PMC cavity displacement from error point and control point spectra, using the measured OLTF
  • Finish up looking at multicoherence with MCL and various witness channel combinations

   

Attachment 1: PMCspectra_calibrated.pdf
PMCspectra_calibrated.pdf
  12945   Tue Apr 18 16:10:00 2017 gautamUpdatePSLPMC OLTF measured, DAQ channels calibrated

Here are the details:

  1. PMC OLTF:
    • the procedure used was identical to what Koji describes in this entry.
    • I used the SR785 to take the measurement.
    • MEDM gain slider was at +20dB 
    • I used the two single pin LEMO front panel monitor points to make the measurement. 
    • Mix_out_mon was CH2A, HV_out_mon was CH1A on the SR785
    • A = CH2A/CH1A with the SR785 excitation applied to the EXT_DC single pin LEMO input on the front panel. I used an excitation amplitude of 15mV
    • B = CH2A/CH1A without any excitation
    • Couple of lines of loop algebra tells us that the OLTF is given by the ratio A/B. The plot below lines up fairly well with what Koji measured here, UGF is ~3.3kHz with a phase margin of ~60degrees, and comparable gain margin at ~28kHz. As noted by Koji, the feature at ~8kHz prevents further increase of the servo gain. I've updated the nominal gain on the PMC MEDM screen accordingly... I couldn't figure out how to easily extract Koji's modelled OLTF so I didn't overlay that here... Overlaid is the model OLTF. No great care was taken in analyzing the goodness of the agreement with the model and measurement by looking at residuals etc, except that the feature that was previously at 28.8kHz now seems to have migrated to about 33.5 kHz. I'm not sure what to make of that. 
  2. PMC DAQ calibration:
    • The calibration was done using the swept cavity, the procedure is basically the same as described by Koji in this elog.
    • The procedure was slightly complicated by the fact that I added gain to the AD620 buffers that provide the DAQ signals. So simply sweeping the cavity saturates the AD620 very quickly.
    • To workaround this, I first hooked up the un-amplified single pin LEMO front panel monitor points to the DAQ channels using some of the available BNC-LEMO patch cables.
    • I then did the swept cavity measurement, and recorded the error and control signals fron the single pin LEMO front panel monitor points. Sweep signal was applied to EXT_DC input on front panel.
    • In the nominal DAQ setup however, we have the amplification on the AD620. I measured this amplification factor by hooking up the single pin LEMO monitor point, along with its corresponding AD620 amplified counterpart, to an SR785 and measuring the transfer function. For the PMC_ERR channel, the AD620 gain is ~53.7dB (i.e. approx 484x). For the PMC_CTRL channel, the AD620 gain is ~33.6dB (i.e. approx 48x). These numbers match up well with what I would expect given the resistors I installed on the PMC board between pins 1 and 8 of the AD620. These gains are digitally undone in the corresponding filter modules, FM1.
    • To calibrate the time axis into frequency, I located the zero crossings of the sidebands and equated the interval to 2 x fmod. For the PMC servo, fmod = 35.5MHz. I used ~1Hz triangle wave, 2Vpp to do the sweep. The resulting slope was 1.7026 GHz/s.
    • The linear part of the PDH error signal for the carrier resonance was fitted with a line. It had a slope of 1.5*10^6 cts/s.
    • The round trip length of the PMC cavity was assumed to be 0.4095m as per Koji's previous entry. This allows us to calibrate the swept cavity motion from Hz to m. The number is 1.4534 * 10^-15 m/Hz. I guess we could confirm this by sweeping the cavity with the DC bias slider through the full range of 0-250V, but we only have a slow readback of the PMC reflection (and no readback of the PMC transmission).
    • Putting the last three numbers together, I get the PMC_ERR signal calibration as 1.6496 pm/ct. This is the number in the "cts2m" filter module (FM10).
    • An analogous procedure was done to calibrate the control signal slope: from the sweep, I got 4617 cts/s, which corresponds to 2.7117*10^-6 cts/Hz. Using the FSR to convert into cts/m, I get for PMC_CTRL, 535.96 pm/ct. This is the number in the "cts2m" filter module (FM10).
    • For convenience, I also added "cts2Hz" calibration filters in FM9 in the corresponding filter modules. 

The updated schematic with changes made, along with some pictures, have been uploaded to the DCC page...

Quote:

Quick entry, details to follow in the AM tomorrow.​

 

Attachment 1: PMC_OLTF_170418.pdf
PMC_OLTF_170418.pdf
  12946   Tue Apr 18 23:37:15 2017 ranaUpdatePSLPMC OLTF measured, DAQ channels calibrated

What's the reasoning behind setting the the gain to this new value? i.e. why do these 'margins' determine what the gain should be?

  12947   Wed Apr 19 15:13:30 2017 gautamUpdatePSLPMC/MCL multicoherence

I used a one hour stretch of data from last night to look at coherence between the PMC control signal and MCL, to see if the former can be used as a witness channel in some frequency band for MCL stabilization. Here is a plot of the predicted subtraction and coherence, made using EricQs pynoisesub code. I had thought about adopting the greedy channel ranking algorithm that Eric has been developing for noise subtraction in site data, but since I am just considering 3 witness channels, I figured this straight up comparison between different sets of witness channels was adequate. Looks like we get some additional coherence with MCL by adding the PMC control signal to the list of witness channels, there is about a factor of a few improvement in in the 1-2Hz band...  

Attachment 1: PMC_MCL_multicoherence.pdf
PMC_MCL_multicoherence.pdf
  12948   Wed Apr 19 15:46:24 2017 gautamUpdateGeneral1611/1811 inventory check

I looked through the lab area to do a fast photodiode inventory check, as we may need to buy some for the higher order mode spectroscopy SURF project. I looked on the following optical tables: ETMY, ITMY, BS, AS, PSL, SP, ITMX, Jenne laser table, and ETMX, as well as the photodiode cabinet, and could only find two 1611s. Here is a summary of the inventory: 

  • Power supply 0901: 2x in photodiode cabinet (E6 along the Y arm), 1x on Jenne laser table
  • Newfocus 1611 S/N 7284-WX, labelled "REF DET" on ITMY optical table, currently unused
  • Newfocus 1611 S/N 57109 on Jenne laser table

I have not yet checked if these photodiodes are in working order.

 

  12949   Fri Apr 21 13:59:47 2017 Eric GustafsonSummary 1064 nm Semiconductor Laser Fiber Distribution System and Mirror Tomography

1064 nm Semiconductor Laser Fiber Distribution System and Mirror Tomography

Below threshold these Semiconductor Fabry-Perot lasers have an axial mode structure with a spacing of about a THz. As you turn up the current to above threshold the first mode to oscillate saturates the gain down on all the modes and only it oscillates.  The laser I have here in my office (a backup for the one you have at the 40 meter) has a wavelength of 1064.9 nm at 70 Degrees C.  We should be able to temperature tune it down to 1064.3 nm although this could be a bit tedious the first time we do it. The specifications claim a "spectrum width" of 1.097 nm which I believe is the temperature tuning range.  I don’t know what the line width is but it will be single frequency and we shouldn’t have mode hoping problems.  So we should be able to use it in the “Mirror Tomography” experiment.  You might want to use some sort of polarization diversity to avoid the problems of fiber polarization drift.

There have been 2 student projects on using the fiber distributed PD frequency response at1064 nm laser.

“Automated Photodiode Frequency Response Measurement System,” Alexander Cole - T1300618

“Final Report: Automated Photodiode Frequency Response Measurement System for Caltech 40m lab,” Nichin Sreekantaswamy - P140021

I’ll look up a few more references and add include them in the next elog.

Eric

 

  12950   Tue Apr 25 19:35:41 2017 gautamUpdateGeneralIPCS -q

Dataviewer wouldn't launch on pianosa - it seemed to work fine on Donatella though. Rana suggested using the ipcs -q command. The complete fix can be found in this elog. This did the trick, dataviewer runs fine on Pianosa now...

  12951   Wed Apr 26 01:00:23 2017 gautamUpdateGeneralDRMI locking

Since we'd like to get back to DRSE locking, I tried locking the DRMI tonight. I did the following:

  • First, I aligned the arms, and ran the dither alignment scripts to maximize the arm transmission
  • Next, I misaligned the ETMs, and tried to lock the PRC resonant for the carrier (i.e. PRCL on REFL11I, MICH on AS55Q). I got brief lock stretches of a few seconds but not longer. Turns out the AS55 beam was barely hitting the photodiode. I guess this wasn't looked at since Johannes modified the AS path for the loss measurements. Anyways, it just required a minor tweak to center the beam on the AS55 photodiode.
  • Once the PRC was locked, I ran the PRC and MICH dither align scripts. The way these are set up right now, the error signals to these servos are REFLDC and ASDC respectively (demodulated at the respective dither frequencies). But looking at the spots on the ITM cameras with the PRC resonant, the spots seem shifted (in both PIT and YAW) relative to the spots when the arm cavity is resonant. Shouldn't they be the same mode? Or maybe I am missing something.
       
  • Next, I tried to lock the DRMI with the 1f error signals: i.e. PRCL on REFL11 I, SRCL on REFL55 I, and MICH on AS55 Q. After some demod phase tweaking, I was able to get some locks going. Turning on the PRC angular feedforward seemed to help the locking, but I have no idea if the installed filters are still the correct ones. I believe the POP QPD channels are the witnesses used to train this filter, I will look at the predicted vs achieved subtraction.
  • At this point, I was able to get locks lasting a few minutes - see the attachment. I ran the UGF servos and tweaked the loop gains a little, but before I could start a loop measurement, I lost the lock. I am calling it for the night.

GV 26 April 2017, 3pm: Forgot to note yesterday that I re-connected the suspect Satellite box, which has been connected to the SRM signal chain, back to the SRM suspension. I did not see any instances of glitching during my work last night. Also added pictures showing shifted spots on ITMs when PRC is locked relative to when arms are locked...

  12952   Thu Apr 27 16:41:13 2017 Eric GustafsonUpdateLSC Status of the 40 m PD Frequency Response Fiber System
There two reports in the DCC describing the state of the system as of October 2014 including: (1)  Alex Cole’s “T1300618 Automated photodiode Frequency Response Measurement System” and a Wiki  created by Alex Cole where there are some instructions on the Master Script at https://wiki.ligo.caltech.edu/ajw?AlexanderCole    

And (2)  P140021 “Final Report: Automated Photodiode Frequency Response Measurement System for 40m Lab” by Nichin Sreekantaswamy and also as part of Nichin’s report by there is an archive of data at   https://wiki-40m.ligo.caltech.edu/Electronics/PDFR%20system   

I made a visual inspection of the system and saw that the following fibers collimators are still mounted in alignment mounts and the fiber is attached and pointed at a photodetector but possibly not aligned. 

ASP Table

Photodetector Label                             Fiber Label

REFL11                                              REFL55 Fiber on mount        

REFL33                                              REFL33 Fiber on mount

REFL55                                              REFL11 Fiber on mount

REFL165                                            No Fiber

AS55                                                   AS55 Fiber on mount

MCREFPD                                         MCREFPD Fiber on mount

No PD                                                 Loose unlabeled Fiber No mount

 

ITMX Optics Table

Photodetector Label                             Fiber Label

POX11                                                POX11 on mount

Unlabeled PD                                      POP22/POP110 on mount

NO PD                                                 POP55 loose fiber No mount

 

The RF switch seems to be hooked up and there is a fiber running from the Diode Laser module to the fiber splitter module. So REFL 11 and REFL545 seem to be illuminated by the wrong fiber. I’ll try and run the software on Monday and check to see if I need to move the fibers or just relabel them.

  12953   Thu Apr 27 17:55:33 2017 SteveUpdateCameraswhich camera to use for IR scatterring pictures

Yesterday I failed to take good pictures of ETMY  resonant arm of 1064 nm with Cannon Rebel T3i in RAW 22-27Mp & JPG dual- format. UFRaw file converter worked well. The IR blocker filter seems to be too good.

Today I used Olympus SP-570UZ ( without IR blocker), in raw format of 15Mp, fl 22.4mm, 15s including 2-3s flashlight,  f/8 and auto focus  This is just too much scattered IR for the Olympus.

Overexposed raw picture' jpg is shown  at the PSL with diffraction patter of the camera.

I'll go back using  the Nikon D40 with zoom 55-200mm as this Atm2 of May 2007 : manual focus, 15s, f/4-5.6, ISO 560,  826KB

Attachment 1: P4270081RAWolym.jpg
P4270081RAWolym.jpg
Attachment 2: Img0344.jpg
Img0344.jpg
  12954   Fri Apr 28 02:04:36 2017 gautamUpdateGeneralDRMI locking

I got a couple of ~30min long DRMI lock stretches today. The settings I used are essentially the same as what I had back in November. Though we have since made some changes to the IMC RF signal chain, I guess it is not unreasonable that the LSC Demod phases that worked then work now as well. 

In the lock stretches, I did the following:

  • Took loop measurements for MICH, PRCL, SRCL
  • Turned on the sensing oscillator lines for error signal calibration
  • Tried turning on the analog whitening on AS55, REFL11 and REFL55. The latter two worked fine, but everytime I turned the REFL55 whitening on, I broke the lock. I'm also unable to acquire lock if I leave the whitening turned on all the time. The ADC overflow indicators also indicate frequent overflows when I turn the whitening on. Oddly, this seems to happen even if I turn the analog whitening gain to 0dB - the signals look well within the ADC range on dataviewer and DTT timeseries mode. Not sure what's going on here, I will investigate further tomorrow.
  • We should have some stretches where we can look at the possibility of seismic feedforward for some DRMI length DOFs.

On the side, I'm also looking at whether the PRC angular feedforward filters, last trained in October 2016, remain valid. Even post midnight, I am unable to lock the DRMI without turning on the FF, and looking at the POP QPD PIT and YAW signal spectra with the FF on vs FF off, there is definitely some improvement in the 1-4Hz band (plot to follow), question is whether we can do better and hence improve the DRMI duty cycle/ make the lock acquisition easier. To this end, I centered the beam on the POP QPD after locking and dither aligning the PRC on carrier, and have taken some data to look at.

So, much data analysis to follow - the idea is to put together a DRMI noise budget with Evan's NB code. For now, here are the uncalibrated control signal spectra.

Attachment 1: 20170428_DRMI.pdf
20170428_DRMI.pdf
  12955   Fri Apr 28 13:56:26 2017 ranaUpdateGeneralDRMI locking

one of these signals does not look like the others: explanation?

  12956   Fri Apr 28 18:01:56 2017 rebeccaUpdateCamerasAttempting to Load Camera Client

Using /ligo/apps/linux-x86-64/camera/bin/camera_client.py -c  /opt/rtcds/caltech/c1/scripts/GigE/SnapPy/L1-CAM-MC1.ini, the Python script was able to run without error but didn't show any video feed from the camera in GStreamer. Problem might be in the configuration of the camera in the .ini file.
 

  12957   Fri Apr 28 19:32:06 2017 gautamUpdateGeneralDRMI locking - PRCL angular FF

I took a closer look at the POP QPD/ PRC angular feedforward situation yesterday. I thought it would be useful to have a POP QPD MEDM screen. Looking at the PIT and YAW channel filter modules, the anti-whitening filters seemed different from what we have for other channels that are connected to the Pentek interface board (e.g. MCL). So I copied over the 150:15 (z:p) filter, and also turned on a 60Hz comb. The LSC offsets script does not set the dark offsets for this QPD, so I manually put in the dark offsets for the PIT, YAW and SUM channels as well. For the locking, I first locked the arms on IR an dither aligned them. Then I locked the PRMI on carrier, ran the PRC dither alignment, and went over to the ITMX pickoff table and centered the beam on the QPD by making the PIT and YAW channel timeseries oscillate around approximately zero. 

After these tweaks, I collected ~40mins of data with the angular FF OFF/ON. I did not DC couple the ITM Oplev servos, but Eric tells me that this did not make a difference to the achievable subtraction in the past. Here is the frequency domain multicoherence analysis - I used the BS_X and BS_Y seismometer channels as witnesses. I've also put a plot with what the raw FF filter coefficients look like (no fitting yet). 

      

Looks like we can do better for both DOFs - it even seems like we are injecting noise with the current FF filters in some bands, perhaps we can do a better job of rolling off the filters outside the band of interest. Eric and I were discussing MATLAB's "reduce" routine for this purpose, I will play around with it and see if I get a better fit.

Unfortunately, I encountered a strange error when trying to pull data with nds2 today, it kept complaining RuntimeError: Too many channels or too much data requestedeven though I have pulled longer stretches of data for more channels with 16k sampling rate as recently as last week. Shorter duration requests (<600 seconds) seemed to work fine though... So I had to use cds.getdata to pull the data, and they're much too large to attach. Has anyone else encountered a similar error?


The mystery of the spots on the ITMs when the PRC is locked on carrier remains - after talking this over with Koji, we figured that even with the carrier resonant, the spot will be much dimmer than the spots when the arms are locked, but what I see on the cameras is still a pretty beefy spot. The real cavity mode is actually visible where it should be (I marked the locations of the spots with arms well-aligned with a marker on the monitors), as given away by some twinkling that is visible only when the cavity is locked. But what ghost beam is so intense it looks almost as bright as when the arm is locked?

GV 10pm 28 April 2017: Turns out this is the spot from the single bounce off the ETM transmitting back through the ITM and hitting the suspension cage (hence the bright spot). Johannes and I confirmed by moving the ETM, the spot moved with it. I just never paid attention to this spot before.

Attachment 1: PRC_angularFF.pdf
PRC_angularFF.pdf
Attachment 2: PRC_TFs.pdf
PRC_TFs.pdf
  12958   Fri Apr 28 22:50:35 2017 johannesUpdateCamerasAttempting to Load Camera Client

You'll likely have to run camera_server.py using the same ini file first before you can use the client. Since the pylon installation is not on the shared drive but only local to optimus at the moment you would have to do it from there. You'll need to add /opt/pylon5/lib64/ to LD_LIBRARY_PATH or it won't find some required libraries. I couldn't start up the server all the way, probably because we need to define some slow EPICS channels before running the server script, as Joe points out in his document T1300202. You'll find instructions how to do that for example in this elog.

 

Quote:

Using /ligo/apps/linux-x86-64/camera/bin/camera_client.py -c  /opt/rtcds/caltech/c1/scripts/GigE/SnapPy/L1-CAM-MC1.ini, the Python script was able to run without error but didn't show any video feed from the camera in GStreamer. Problem might be in the configuration of the camera in the .ini file.
 

 

  12959   Sun Apr 30 13:24:00 2017 ranaUpdateCamerasAttempting to Load Camera Client

We ought to put the camera software on the shared disk; I don't think there's any speed reasons that it needs to be local.

Its OK to use optimus as the camera server for testing at the moment, but once we have things running, we'll install a few more cameras. With ~4-5 GigE running, we may not want to share with optimus, since we're also using it for comsol and skymap calculations.

  12960   Mon May 1 16:29:51 2017 gautamUpdateGeneralDRMI locking

For the traces I posted, I had not turned on the whitening for the SRCL sensing PD (REFL55). However, I took a spectrum on a subsequent lock, with the analog whitening + digital dewhitening turned on for all 3 PDs (AS55, REFL11 and REFL55), and the HF part of the SRCL spectrum still looked anomalous. I'm putting together the detailed NB, but here's a comparison between the signals from the 3 RFPDs with the PSL shutter closed (but whitening engaged, and with the analog gains at the same values as used during the locking).

 

To convert the y-axis into m/rtHz, I used data from a sensing matrix measurement I took yesterday night during a DRMI lock - I turned on lines between 300 Hz and 325 Hz for the 3DOFs for ~5 minutes, downloaded the RFPD error signal data and did the demodulation. I used numbers from this elog to convert the actuator drive from cts to m. The final numbers I used were:

MICH (AS55_Q):   8.706 * 10^11 cts/m

PRCL (REFL11_I): 2.757 * 10^12 cts/m

SRCL (REFL55_I): 1.995 * 10^10 cts/m

So it looks like there may be something weird going on with the REFL55 signal chain. Looking at the LSC rack (and also suggested by an elog search), it looks like the demodulation is done by a demod board labelled "POP55" - moreover, the demodulated outputs are taken not from the regular output ports on this board, but from the "MON" ports on the front panel. 

Quote:

one of these signals does not look like the others: explanation?

 

Attachment 1: LSC_sensingNoise.pdf
LSC_sensingNoise.pdf
  12961   Mon May 1 17:14:58 2017 SteveUpdateCamerasETMY & MC2 ccd cameras removed

MC2 ccd camera is replaced by Olympus 570 zoom temporarly.

So as the ETMY ccd camera is replaced by Cannon Rebel.

Both viewport are under Lexan protection and covered by Aluminum foil....still, turn all lighting off if you do not want room light in the IFO

 

Do not remove Lexan shield!

 

  12962   Mon May 1 21:45:54 2017 ericqUpdateGeneralDRMI locking
Comparing counts doesn't get you anywhere; each PD has different whitening gain which may vary from measurement to measurement. The better thing to compare is Volts coming out of the demod board, since this (hopefully) only changes when we touch the PD or analog signal chain; this is what I used for the most recent DRMI sensing measurements. (ELOG 11589) We have calibrated actuator channels in the CAL model, which will give you the control signal in m for the DRMI lengths. Perhaps you can convert your sensing matrix measurement to demod board output volts per meter to compare with the last measurement.

Also, the monitor ports are the LEMO ports to the left; the SMA ports where the signal is coming from are from a daughter board that has a better output opamp that the nominal output; we're using the same output on the REFL11 and AS55 demod boards.
  12963   Wed May 3 16:00:00 2017 gautamSummaryGeneralNetwork Topology Check

[johannes, gautam]

I forgot we had done this last year already, but we updated the control room network switch labels and double checked all the connections. Here is the status of the connections and labels as of today:

There are a few minor changes w.r.t. labeling and port numbers compared to the Dec 2015 entry. But it looks like there was no IP clash between Rossa and anything (which was one of the motivations behind embarking on this cleanup). We confirmed by detatching the cable at the PC end of Rossa, and noticed the break in the ping signals. Plugging the cable back in returned the pings. Because Rossa is currently un-bootable, I couldn't check the MAC address.

We also confirmed all of this by using the web browser interface for the switch (IP = 192.168.113.249).

Attachment 1: Network_topology_3May2017.pdf
Network_topology_3May2017.pdf
  12964   Wed May 3 16:02:36 2017 SteveUpdateGeneralPI pzt inventory check

One is broken, two are ready to steer green and 3 available in un known condition

 

Attachment 1: IMG_3678.JPG
IMG_3678.JPG
Attachment 2: PIpztETMYgreen.jpg
PIpztETMYgreen.jpg
  12965   Wed May 3 16:12:36 2017 johannesConfigurationComputerscatastrophic multiple monitor failures

It seems we lost three monitors basically overnight.

The main (landscape, left) displays of Pianosa, Rossa and Allegra are all broken with the same failure mode:

their backlights failed. Gautam and I confirmed that there is still an image displayed on all three, just incredibly faint. While Allegra hasn't been used much, we can narrow down that Pianosa's and Rossa's monitors must have failed within 5 or 6 hours of each other, last night.

One could say ... they turned to the dark side cool

Quick edit; There was a functioning Dell 24" monitor next to the iMac that we used as a replacement for Pianosa's primary display. Once the new curved display is paired with Rossa we can use its old display for Donatella or Allegra.

  12966   Wed May 3 16:46:18 2017 KojiConfigurationComputerscatastrophic multiple monitor failures

- Is there any machine that can handle 4K? I have one 4K LCD for no use.
- I also can donate one 24" Dell

  12967   Wed May 3 16:47:45 2017 KojiUpdateGeneralPI pzt inventory check

I also have a functional one on my desk, which has one of the wires repaired.

Quote:

One is broken, two are ready to steer green and 3 available in un known condition

 

 

  12968   Wed May 3 17:16:30 2017 PrafulUpdateElectronicsNew Altium Schematic Design for Microphone Amp

I made an Altium schematic for the microphone amplifier circuit for fabrication.

mic_schematicv2.pdf

Attachment 1: mic_schematicv2.pdf
mic_schematicv2.pdf
  12969   Wed May 3 18:45:45 2017 ranaUpdateGeneralDRMI locking

Quote:
Comparing counts doesn't get you anywhere; each PD has different whitening gain which may vary from measurement to measurement. The better thing to compare is Volts coming out of the demod board, since this (hopefully) only changes when we touch the PD or analog signal chain; this is what I used for the most recent DRMI sensing measurements. (ELOG 11589) We have calibrated actuator channels in the CAL model, which will give you the control signal in m for the DRMI lengths. Perhaps you can convert your sensing matrix measurement to demod board output volts per meter to compare with the last measurement.

Also, the monitor ports are the LEMO ports to the left; the SMA ports where the signal is coming from are from a daughter board that has a better output opamp that the nominal output; we're using the same output on the REFL11 and AS55 demod boards.


Wrong! RTFS.

SMA outputs are the bare, passive outputs of the mixer/lowpass.
TNC outputs are the low-noise, acti amplified outputs via the daughter board.
LEMO outputs are the high noise, G=2, LT1125 buffered outputs
  12970   Thu May 4 08:00:54 2017 SteveUpdatesafetysafety training

Freshmen Rebecca Zhang as " work study undergrad "  received 40m specific basic safety training yesterday.

  12971   Thu May 4 09:52:43 2017 ranaConfigurationComputerscatastrophic multiple monitor failures

That's a new failure mode. Probably we can't trust the power to be safe anymore.

Need Steve to order a couple of surge suppressing power strips for the monitors. The computers are already on the UPS, so they don't need it.

  12972   Thu May 4 19:03:15 2017 gautamUpdateGeneralDRMI locking - preliminary MICH NB

Summary:

I've been playing around with Evan's NB code trying to put together a noise budget for the data collected during the DRMI locks last week. Here is what I have so far.

Attachment #1: Sensing matrix measurement.

  • This is basically to show that the MICH error signal is mostly in AS55Q.
  • The whitening gain used was 0dB, and the demod phase was -82 degrees.
  • The MICH sensing response was 5.31*10^8 V/m, where V is the demod board output. The 40m wiki RFPD page for AS55 says the RF transimpedance is ~550ohms, and I measured the Demod Board puts out 5.1V of IF signal (measured at after the Preamp, which is what goes to the ADC) for 1V of RF signal at the PD input. Using these numbers, and assuming a PD responsivity of 0.8 A/W at 1064nm, the sensing response is 2.37*10^5 W/m. I don't have a feeling yet for whether this is a reasonable number, but it would be a number to compare to what my Finesse model tells me to expect, for example.
  • Actuator calibration used to arrive at these numbers was taken from this elog

Attachment #2: MICH OLTF measurement vs model

  • In order to build the MICH OLTF model, I used MATLAB to put together the following transfer functions:
    • BS pendulum
    • Digital servo filters from LSC_MICH
    • Violin mode filters 
    • Analog/Digital AA and AI filters. For the digital AA/AI filters, I took the coefficients from /opt/rtcds/rtscore/release/src/fe/controller.c
  • The loop measurement was taken with digital filter modules FM1, FM2, FM3, FM7, FM9 engaged. 
  • In order to fit the model to the measurement, I tried finding the best-fit values for an overall loop gain and delay. 
  • The agreement between model and measurement isn't stellar, but I decided to push ahead for a first attempt. This loop TF was used to convert various noises into displacement noise for plotting.

Attachment #3: Noise budget

  • It took me a while to get Evan's code going, the main changes I made were to use nds2 to grab data instead of GWPy, and also to replace reading in .txt files with importing .mat files. This is a work in progress.
  • Noises plotted:
    • Measured - I took the in loop error signal and estimated the free-running displacement noise with the model OLTF, and calibrated it into metres using the sensing response measurement. This looks consistent with what was measured back in Dec 2015.
    • Shot noise - I used the measured DC power incident on the PD, 13mW, RF transimpedance of 550 V/A, and the V/m calibration factor mentioned above, to calculate this (labelled "Quantum Noise").
    • Dark noise - measured with PSL shutter closed.
    • Seismic noise, thermal noise, gas noise - calculated with GWINC

I think I did the various conversions/calibrations/loop algebra correctly, but I may have overlooked something. Now that the framework for doing this is somewhat set up, I will try and put together analogous NBs for PRCL and SRCL. 

GV 22 August 2017: Attachment #4 is the summary of my demod board efficiency investigations, useful for converting sensing measurement numbers from cts/m to W/m.

Attachment 1: DRMI_noArms_April30.pdf
DRMI_noArms_April30.pdf
Attachment 2: MICH_OLTF.pdf
MICH_OLTF.pdf
Attachment 3: C1NB_disp_40m_MICH_NB_30_April_2017.pdf
C1NB_disp_40m_MICH_NB_30_April_2017.pdf
Attachment 4: 40m_REFL_RFPDs_efficiency.pdf
40m_REFL_RFPDs_efficiency.pdf
  12973   Fri May 5 08:41:42 2017 SteveUpdateCamerasMC2 resonant pictures

Olympus SP570 UZ - without  IR blocker, set up as Atm.3  Camera distance to MC  face ~85 cm,  IOO-MC_TRANS_SUM 16,300 counts, Lexan cover on not coated viewport.

Image mode: RAW + JPG,  M-costum,  manual focus,  Lens: Olympus 4.6 - 92 mm, f2.8 - 4.5,  Apeture: F2.8 - 8,  Image pick up device: 1/2.33" CCD (primary color filter)

Atm.1,       212k.jpg of raw 15 MB,  exp 0.025s,   apeture 2.97,  f 4.6,   iso 64,  

Atm.2,        Copied through my Cannon S100  (  3.3 MB.jpg of raw from UFraw photo shop )I will look up the original raw file for details.

 

Attachment 1: P5040028MC2c.jpg
P5040028MC2c.jpg
Attachment 2: IMG_3682.JPG
IMG_3682.JPG
Attachment 3: IMG_3688.JPG
IMG_3688.JPG
  12974   Fri May 5 10:13:02 2017 ericqUpdateGeneralMICH NB questions
Is suspension thermal noise missing? I take it "Thermal" refers just to thermal things going on in the optic, since I don't see any peaks at the bounce/roll modes as I would expect from suspension thermal noise.

What goes into the GWINC calculation of seismic noise? Does it include real 40m ground motion data and our seismic stacks?

I'm surprised to see such a sharp corner in the "Dark Noise" trace, did you apply the OLG correction to a measured dark noise ASD? (The OLG correction only needs to be applied to the in-lock error signals to recover open loop behavior, there is no closed loop when you're measuring the dark noise so nothing to correct for.)
  12975   Fri May 5 12:10:53 2017 gautamUpdateGeneralMICH NB questions

Quote:
Is suspension thermal noise missing? I take it &quot;Thermal&quot; refers just to thermal things going on in the optic, since I don&#39;t see any peaks at the bounce/roll modes as I would expect from suspension thermal noise. What goes into the GWINC calculation of seismic noise? Does it include real 40m ground motion data and our seismic stacks? I&#39;m surprised to see such a sharp corner in the &quot;Dark Noise&quot; trace, did you apply the OLG correction to a measured dark noise ASD? (The OLG correction only needs to be applied to the in-lock error signals to recover open loop behavior, there is no closed loop when you&#39;re measuring the dark noise so nothing to correct for.)


I've included the suspension thermal noise in the "Thermal" trace, but I guess the GWINC file I've been using to generate this trace only computes the thermal noise for the displacement DoF. I think this paper has the formulas to account for them, I will look into including these.

For the seismic noise, I've just been using the seis40.mat file from the 40m SVN. I think it includes a model of our stacks, but I did not re-calculate anything with current seismometer spectra. In the NB I updated yesterday, however, I think I was off by a factor of sqrt(3) as I had only included the seismic noise from 1 suspended optic. I've corrected this in the attached plot.

For the dark noise, you are right, I had it grouped in the wrong dictionary in the code so it was applying the OLG inversion. I've fixed this in the attached plot.
Attachment 1: C1NB_disp_40m_MICH_NB_30_April_2017.pdf
C1NB_disp_40m_MICH_NB_30_April_2017.pdf
  12976   Sat May 6 21:52:11 2017 ranaUpdateGeneralMICH NB questions

I think the most important next two items to budget are the optical lever noise, and the coil driver noise. The coil driver noise is dominated at the moment by the DAC noise since we're operating with the dewhitening filters turned off.

  12977   Mon May 8 21:53:56 2017 ranaSummarySEIattempt to get seismic BLRMS minute trend

I tried to get some minute trend data today, but was unable to get it from inside or outside the control room using our matlab or python tools.

It seems the NDS2 interface will not work anywhere since it needs our minute trends to be written as frames; in the last version that Jamie left us, our minute trend frame files are not being written since they lead to periodic daqd crashes.

From inside the control room, we can get the minute trend (only with DataViewer). I've attached 30 days of BS_X just to show its real.

We can get the numerical data from the Grace plot window using the menu option Data->Export->ASCII.

You must select all of the 'Write Sets' to get all of the traces in the plot window. The resulting ascii file is not in a great format, but its not terrible.

Attachment 1: BLRMS_trend.png
BLRMS_trend.png
  12978   Tue May 9 15:23:12 2017 SteveConfigurationComputerscatastrophic multiple monitor failures

Gautam and Steve,

Surge protective power strip was install on Friday, May 5 in the Control Room

Computers not connected to the UPS are plugged into Isobar12ultra.

Quote:

That's a new failure mode. Probably we can't trust the power to be safe anymore.

Need Steve to order a couple of surge suppressing power strips for the monitors. The computers are already on the UPS, so they don't need it.

 

Attachment 1: Trip-Lite.jpg
Trip-Lite.jpg
  12979   Wed May 10 01:56:06 2017 gautamUpdateGeneralMICH NB - OL coupling

Last night, I tried to estimate the contribution of OL feedback signal to the MICH length error signal.

In order to do so, I took a swept sine measurement with a few points between 50 Hz and 500 Hz. The transfer function between C1:LSC-MICH_OUT_DQ and the Oplev Servo Output point (e.g. C1:SUS-BS_OL_PIT_OUT etc) was measured. I played around with the excitation amplitude till I got coherence > 0.9 for the TF measurement, while making sure I wasn't driving the Oplev error point too hard that side-lobes began to show up in the MICH control signal spectrum.

The Oplev control signal is not DQ-ed. So I locked the DRMI again and downloaded the 16k data "live" for ~5min stretch using cdsutils.getdata on the workstation. The Oplev error point is DQ-ed at 2k, but I found that the excitation amplitude needed for good SNR at the error point drove the servo to the limiter value of 2000cts - so I decided to use the control signal instead. Knowing the transfer function from the Oplev *_OUT* channel to C1:LSC-MICH_IN1_DQ, I backed out the coupling - the transfer function was only measured between 50 Hz and 500 Hz, and no extrapolation is done, so the estimation is only really valid in this range, which looks like where it is important anyways (see Attachment #2, contributions from ITMX, ITMY and BS PIT and YAW servos added in quadrature).

I was also looking at the Oplev servo shapes and noticed that they are different for the ITMs and the BS (Attachment #1). Specifically, for the ITM Oplevs, an "ELP15" is used to do the roll-off while an "ELP35" is employed in the BS servo (though an ELP35 also exists in the ITM Oplev filter banks). I got lost in an elog search for when these were tuned, but I guess the principles outlined in this elog still hold and can serve as a guideline for Oplev loop tweaking.

Coil driver noise estimation to follow

Quote:

I think the most important next two items to budget are the optical lever noise, and the coil driver noise. The coil driver noise is dominated at the moment by the DAC noise since we're operating with the dewhitening filters turned off.

GV 10 May 12:30pm: I've uploaded another copy of the NB (Attachment #3) with the contributions from the ITMs and BS separated. Looks like below 100Hz, the BS coupling dominates, while the hump/plateau around 350Hz is coming from ITMX.

Attachment 1: OL_BS_ITM_comp.pdf
OL_BS_ITM_comp.pdf
Attachment 2: C1NB_disp_40m_MICH_NB_8_May_2017.pdf
C1NB_disp_40m_MICH_NB_8_May_2017.pdf
Attachment 3: C1NB_disp_40m_MICH_NB_10_May_2017.pdf
C1NB_disp_40m_MICH_NB_10_May_2017.pdf
  12980   Wed May 10 12:37:41 2017 gautamUpdateCDSMCautolocker dead

The MCautolocker had stalled - there were no additional lines to the logfile after 12:17pm (~20mins ago). Normally, it suffices to ssh into megatron and run sudo initctl restart MCautolocker - but it seems that there was no running initctl instance of this, so I had to run sudo initctl start MCautolocker. The FSS Slow control initctl process also seemed to have been terminated, so I ran sudo initctl start FSSslowPy.

It is not clear to me why the initctl instances got killed in the first place, but MC locks fine now.

  12981   Wed May 10 16:53:38 2017 ranaUpdateGeneralMICH NB - OL coupling

That's a good find.

  1. The OL control signal can be gotten from the DQ error signal. You just need to multiply it by the digital filters and the gain. The state of the filters and the gain can be gotten using matlab tools like getFotonFilt.m. For python ChrisW wrote a tool called foton.py which is in the GDS SVN. You should ask him for it. It requires access to some ROOT libraries to run.
  2. We should have sub budgets for everything like OL and thermal, etc. They should be automatically produced each time you run the main budget and should be separate pages in the same PDF file. Jamie / Chris may have something going along these lines so check to see if they are already on it.
  12982   Wed May 10 16:57:52 2017 ranaUpdateCDSMCautolocker dead

I rebooted megatron around 12:20 today. It had dozens of stalled medm process (some of them there since February!). I couldn't kill them without them coming back like zombies, so I did sudo reboot.

  12983   Wed May 10 17:17:05 2017 gautamUpdateGeneralDAC / Coil Driver noise

Suspension Actuator noise:

There are 3 main sources of electronics noise which come in through the coil driver:

  1. Voltage noise of the coil driver.
    1. The input referred noise is ~5 nV/rHz, so not a big issue.
    2. The Johnson noise of the output resistor which is in series with the coil is sqrt(4*k*T*R) ~ 3 nV/rHz. We probably want to increase this resistor from 200 to 1000 Ohms once Gautam convinces us that we don't need that range for lock acquisition.
  2. Voltage noise of the dewhitening board.
    1. In order to reduce DAC noise, we have a "dewhitening" filter which provides some low passing. There is an "antiDW" filter in the digital part which is the inverse of this, so that when they are both turned on, the result is that the main signal path has a flat transfer function, but the DAC noise gets attenuated.
    2. In particular, ours have 2 second order filters (each with 2 poles at 15 Hz and 2 zeros at 100 Hz).
    3. We also have a passive pole:zero network at the output which has z=130, 530 Hz and p = 14, 3185 Hz.
    4. The dewhitening board has an overall gain of 3 at DC to account for our old DACs having a range of +/-5 V and our coil drivers having +/- 15 V power supplies. We should get rid of this gain of 3.
    5. The dewhitening board (and probably the coil driver) use thick film resistors and so their noise is much worse than expected at low frequencies.
  3. DAC voltage noise. 
    1. The General Standards 16-bit DACs have a noise of ~5 uV/rHz.
  4. the satellite box is passive and not a significant source of noise; its just a flaky construction and so its problematic.
Attachment 1: actuation.jpg
actuation.jpg
  12984   Wed May 10 17:46:44 2017 gautamUpdateGeneralDAC / Coil Driver noise - SRM coil driver + dewhite board removed

I've removed the SOS coil driver (D010001-B, S/N B151, labelled "SRM") + Universal Dewhitening Board (D000183 Rev C, S/N B5172, labelled "B5") combo for SRM from 1X4, for photo taking + inspection.

I first shutdown the SRM watchdog, noted cabling between these boards and also the AI board as well as output to Sat. Box. I also needed to shutdown the MC2 watchdog as I had to remove the DAC output to MC2 in order to remove the SRM Dewhitening board from the rack. This connection has been restored, MC locks fine now.

 

  12985   Thu May 11 09:45:46 2017 ranaUpdateGeneralDAC / Coil Driver noise - SRM coil driver + dewhite board removed

I believe the ETMs and ITMs are different from the others.

  12986   Thu May 11 18:59:22 2017 gautamUpdateGeneralSRM coil driver + dewhite board initial survey

I've added marked-up schematics + high-res photographs of the SRM coil driver board and dewhitening board to the 40m DCC Document tree (D1700217 and D1700218). 

In the attached marked-up schematics, I've also added the proposed changes which Rana and I discussed earlier today. For the thick-film -> thin-film resistor switching, I will try and make a quick LISO model to see if we can get away with replacing just a few rather than re-stuff the whole board.

Since I have the board out, should I implement some of these changes (like AD797 removal) before sticking it back in and pulling out one of the ITM boards? I need to look at the locking transients and current digital limit-values for the various DoFs before deciding on what is an appropriate value for the output resistance in series with the coil.

Another change I think should be made, but I forgot to include on the markups: On the dewhitening board, we should probably replace the decoupling capacitors C41 and C52 with equivalent value electrolytic caps (they are currently tantalum caps which I think are susceptible to fail by shorting input to output).

Attachment 1: D010001-B_40m.pdf
D010001-B_40m.pdf D010001-B_40m.pdf D010001-B_40m.pdf D010001-B_40m.pdf
Attachment 2: D000183-C8_40m.pdf
D000183-C8_40m.pdf D000183-C8_40m.pdf D000183-C8_40m.pdf
  12987   Fri May 12 01:36:04 2017 gautamUpdateGeneralSRM coil driver + dewhite board LISO modeling

I've made the LISO models for the dewhitening board and coil driver boards I pulled out.

Attached is a plot of the current noise in the current configuration (i.e. dewhitening board just has a gain x3 stage, and then propagated through the coil driver path), with the top 3 noise contributions: The op-amps (op3 and op5) are the LT1125s on the coil driver board in the bias path, while "R12" is the Johnson noise from the 1k input resistace to the OP27 in the signal path.

Assuming the OSEMs have an actuation gain of 0.016 N/A (so 0.064 N/A for 4 OSEMs), the current noise of ~1e-10 A/rtHz translates to a displacement noise of ~3e-15m/rtHz at ~100Hz (assuming a mirror mass of 0.25kg). 

I have NOT included the noise from the LM6321 current buffers as I couldn't find anything about their noise characteristics in the datasheet. LISO files used to generate this plot are attached.

Quote:

I've added marked-up schematics + high-res photographs of the SRM coil driver board and dewhitening board to the 40m DCC Document tree (D1700217 and D1700218). 

In the attached marked-up schematics, I've also added the proposed changes which Rana and I discussed earlier today. For the thick-film -> thin-film resistor switching, I will try and make a quick LISO model to see if we can get away with replacing just a few rather than re-stuff the whole board.

Since I have the board out, should I implement some of these changes (like AD797 removal) before sticking it back in and pulling out one of the ITM boards? I need to look at the locking transients and current digital limit-values for the various DoFs before deciding on what is an appropriate value for the output resistance in series with the coil.

Another change I think should be made, but I forgot to include on the markups: On the dewhitening board, we should probably replace the decoupling capacitors C41 and C52 with equivalent value electrolytic caps (they are currently tantalum caps which I think are susceptible to fail by shorting input to output).

 

Attachment 1: SRM_bypass_plus_CoilDriver.pdf
SRM_bypass_plus_CoilDriver.pdf
Attachment 2: liso.zip
ELOG V3.1.3-