40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
 40m Log, Page 78 of 339 Not logged in
ID Date Author Type Category Subject
12464   Thu Sep 1 19:18:14 2016 JohannesUpdateSUSITMX and ETMX preemptive table leveling

I balanced the ITMX and ETMX tables into level position today, for which I had to move quite a few of the on-table weights. I'm recording their original positions for future use here.

## ETMX

This table was only off in 'pitch', I moved the middle weight to a new location as shown in the pictures. I added secondf disk weight on top of the one I moved, this one has to come out again when we install ETMX.

## ITMX

I moved some weights around as shown in the image, but didn't have to add any. We simply have to move them back to their original location when the time comes.

While in the chambers, I also took some pictures of the ETMX window and PR2, motivated by the dirty state of SR2. We might want to consider cleaning both, specifically PR2 is relatively easily accessible and can be cleaned when we open the ITMX chamber to remove its FC and move it back into position.

12465   Thu Sep 1 19:59:22 2016 JohannesUpdateSUSIR mode flashes in Y arm

[Gautam, Lydia, Johannes]

• After placing the irises on the ETMY and ITMY cages we found that the green beam pointing was off in YAW and corrected it to hit the center of ITMY
• The green beam was well centered on ETMY to begin with, so we used it as a reference for the alignment of ITMY, sending it back through the ETMY iris
• We used the green transmission to tune the pitch and yaw of ETMY
• Using TT1 and TT2 we steered the beam IR through both irises and were hoping to see mode flashes in the IR arm transmission, which we did

The next step is the tip tilt fine alignment of the IR into the arm, using TRY, from which we removed the ND filter for the time being.

12482   Mon Sep 12 17:15:22 2016 JohannesUpdateGeneralPRM SRM alignment

[Gautam, Steve, Johannes]

We put on the remaining heavy doors on the chambers (ITMY, ITMX,ETMX, in this order) this morning. On the ITMY and ETMX tables we placed old OpLev steering mirrors that are clean and baked as witness plates such that may one day provide some insight into dust accumulation on optics.

With the heavy doors on we confirmed that we were still able to lock both IFO arms and used the dither scripts to optimize the alignment. Following that we centered all OpLevs and aligned the X and Y green beams.

12493   Wed Sep 14 19:41:23 2016 JohannesUpdateGeneralPSL back to high power

Today's summary:

• Replaced mirror in MC REFL path with R=10% BS and aligned beam on PD while still at low power
• Replaced HR mirror in Transmon path at EY table with 50/50 BS. Alignment onto QPD not yet confirmed because we need IR from the YARM for it.
• Put ND filters back on Transmon QPDs at both X and Y ends. For now I put all the filters on, for a combined OD of 1.6 at both ends (1.0 + 0.6 at YEND and 1.0 + 0.4 + 0.2 at XEND).
• Put ND filter back on Transmon CCD on EY table.
• Reverted MC autolocker to nominal, high power version.
• Raised PSL output power back to nominal level by turning the waveplate. At the PSL shutter I measured a power of 1.03W. It occured to me too late that I realigned the PMC only afterwards and increased its transmission by a few percent, so I'll have to re-measure the actual PSL power.
• MC is locked with its transmission back up to ~15,400 counts. The autolocker is not very good at obtaining the lock, as it seems to try to turn the VCO gain up too far and loses lock. The script probably needs a revision.
• The YARM was pretty badly aligned. We used the green light to visually center the beam on the test masses AND had to go exploring with the TTs to see IR flashes in the first place. We got the YARM to lock to IR and were able to run the dither alignment. The maximum transmission we saw was on the order of 0.85. However, something strange is happening with the LSC control of the armlength. When the lock is engaged it drives PIT and YAW, which manifests itself in the OpLev signal and variable transmitted power on the TRY PDs. Osamu helped us diagnose this and was able to reduce the effect by tuning the POS gains to the individual ETMY OSEMS. The problem persisted even after using the new matrix diagonalization coefficients, we'll have to investigate this further and also take a look at the filters in the feedback path.
• ITMX is still stuck and way out of alignment, so we couldn't even start with the green light in the XARM.
12524   Thu Sep 29 20:21:29 2016 JohannesUpdateGeneralYARM loss measurement

[Gautam, Johannes]

I scripted a series of YARM DC reflectivity measurements last night alternating between locked state and unlocked state (with ETMY misaligned) for measuring the after-vent armloss. The general procedure is based on elog 11810, but I'll also give a brief summary here.

• To measure the locked reflectivity the dither script is executed with a stop condition that depends on the rms values of its error signals.
• The dithering is stopped, and while the arm is locked the reflected power is recorded from both POX/POY DC and ASDC, as well as the mode cleaner transmission for normalization.
• The arm locking is switched off, and ETMY moved to is 'misaligned' position. This gets rid off unwanted mode flashes.
• In the unlocked state the same quantities are recorded.
• Rinse and repeat for a set number of times (for this run I set it to 100 and left the interferometer alone).

I did this back in June (but strangely never posted what I found, shame on me). What I found back then was a YARM loss of 237 ppm +/- 41 ppm and an XARM loss of 501 ppm +/- 105 ppm

Last night's data indicates a YARM loss of 143 ppm +/- 24 ppm after cleaning with first contact.

THIS IS STILL ASSUMING THAT THE MODE-MATCHING HASN'T CHANGED. We had however moved ETMY closer to ITMY during the vent by 19mm. Gautam and I had some trouble setting up the ALS to confirm the mode-matching, but we're in the process of recovering the XARM IR beat.

12528   Mon Oct 3 21:24:02 2016 JohannesUpdateGeneralXARM loss measurement

[gautam, johannes]

I started a script on Friday night to collect some data for a reflection armloss measurement of the XARM. Unfortunately there seemed to have been a hickup in some data transfer and some errors were produced, so we couldn't really trust the numbers.

Instead, we took a series of manual measurements today and made sure the interferometer is well behaved during the averaging process. I wrote up the math behind the measurement in the attached pdf.

The numbers we used for the calculations are the following:

While we average about 50 ppm +/-15 ppm for the XARM loss with a handful of samples, in a few instances the calculations actually yielded negative numbers, so there's a flaw in the way I'm collecting the data. There seems to be a ~3% drift in the signal level on the PO port on the order of minutes that does not show in the modecleaner transmission. The signals are somewhat small so we're closing the shutter over night to see if it could be an offset and will investigate further tomorrow. I went back and checked my data for the YARM, but that doesn't seem to be affected by it.

Attachment 1: ReflectionLoss.pdf
12531   Tue Oct 4 22:18:24 2016 JohannesUpdateGeneralX/YARM loss measurement

[gautam, johannes]

We let the PSL shutter closed overnight and observed the POXDC, POYDC and ASDC offsets. While POY has small fluctuations compared to the signal level, POX is worse off, and the drifts we observed live in the DC reading are in the same ballpark as the offset fluctuations. The POXDC level also unexpectedly increased suddenly without the PSL shutter being opened, which we can't explain. The data we took using POXDC cannot be trusted.

Even the ASDC occasionally shows some fluctuations, which is concerning because the change in value rivals the difference between locked and misaligned state. It turns out that the green shutters were left open, but that should not really affect the detectors in question.

We obtained loss numbers by measuring the arm reflections on the ASDC port instead. LSCoffsets was run before the data-taking run. For each arm we misaligned the respective other ITM to the point that moving it no longer had an impact on the ASDC reading. By taking a few quick data points we conclude the following numbers:

XARM: 247 ppm +/- 12 ppm
YARM: 285 ppm +/- 13 ppm

This is not in good agreement with the POYDC value. The script is currently running for the YARM for better statistics, which will take a couple hours.

ITMX is misaligned for the purpose of this measurement, with the original values saved.

GV edit 5Oct2016: Forgot to mention here that Johannes marked the spot positions on the ITMs and ETMs (as viewed on the QUAD in the control room) with a sharpie to reflect the current "well aligned" state.

Attachment 1: anomalousData.png
12581   Wed Oct 26 16:06:01 2016 JohannesUpdateGeneralAutolocker maintenance

[Gautam, Johannes]

The autolocker was acting up today, Gautam traced it to EPICS channels ( namely C1:IOO-MC_LOCK_ENABLE and C1:IOO-MC_AUTOLOCK_BEAT ) served by c1iool0 not being responsive and keyed the crate. This restored it nominal operation.

12604   Mon Nov 7 19:49:44 2016 JohannesUpdateCDSacromag chassis hooked up to PSL

[Lydia, Johannes]

We're waiting on the last couple electrical components to arrive that are needed to complete the acromag chassis, but it is essentially operational. Right now it is connected to the PSL Mephisto's diagnostics port, for which only a single XT1221 A/D unit is needed. We assigned the IP address 192.168.113.121 to it. For the time being I'm running a tmux session on megatron (named "acromag") that grabs and broadcasts the epics channels, with Lydia's original channel definitions. Since the chassis is 4U tall, there's not really any place in the rack for it, so we might want to move it to the X-end before we start shuffling rack components around. Once we finalize its location we can proceed with adding the channels to the frames.

For the eventual gradual replacement of the slow machines, we need to put some thought into the connectors we want in the chassis. If we want to replicate the VME crate connectors we probably need to make our own PCB boards for them, as there don't seem to be panel-mount screw terminal blocks readily available for DIN 41612 connectors. Furthermore, if we want to add whitening/AA filters, the chassis may actually be large enough to accomodate them, and arranging things on the inside is quite flexible. There are a few things to be considered when moving forward, for example how many XT units we can practically fit in the chassis (space availability, heat generation, and power requirements) and thus how many channels/connectors we can support with each.

Steve: 1X3 has plenty of room

Attachment 1: acromag_chassis_location.jpg
Attachment 2: acromag_chassis_top_view.jpg
12614   Mon Nov 14 19:15:57 2016 JohannesUpdateGeneralAchievable armloss measurement accuracy

Looking back at elog 12528, the uncertainty in the armloss number from the individual quantities in the equation for $\mathcal{L}$ can be written as:

$\delta\mathcal{L}^2=\left(\frac{T_1(1-\frac{P_L}{P_M}-2T_1)}{4\gamma}\right)^2\left(\frac{\delta T_1}{T_1}\right)^2+T_2^2\left(\frac{\delta T_2}{T_2}\right)^2+\left(\frac{T_1(1-\frac{P_L}{P_M}-T_1)}{4\gamma}\right)^2\left(\frac{\delta\gamma}{\gamma}\right )^2+\left(\frac{T_1}{4\gamma}\right )^2\left[\left(\frac{\delta P_L}{P_L}\right )^2+\left(\frac{P_L}{P_M} \right )^2\left(\frac{\delta P_M}{P_M}\right )^2\right ]$

Making some generous assumption about the individual uncertainties and filling in typical values we get in our measurements, results in the following uncertainty budget:

$\delta\mathcal{L}^2\approx\left(12\,\mathrm{ppm}\right)^2\left(\frac{\delta T_1/T_1}{5\%}\right)^2+(0.7\,\mathrm{ppm})^2\left(\frac{\delta T_2/T_2}{5\%}\right)^2+\left(2\,\mathrm{ppm}\right)^2\left(\frac{\delta\gamma/\gamma}{1\%}\right )^2+\left(140\,\mathrm{ppm}\right )^2\left(\frac{\delta P/P}{2.5\%}\right )^2$

In my recent round of measurements I had a 2.5% uncertainty in the ASDC reading, which completely dominates the armloss assessment.

The most recent numbers are 57 ppm for the YARM and 21 ppm for the XARM, but both with an uncertainty of near 150 ppm, so while these numbers fit well with Gautam's estimate of the average armloss via PRG, it's not really a confirmation.

I set the whitening gain in ASDC to 24 dB and ran LSC offsets, and now I'm getting a relative uncertainty in measured reflected power of .22%, which would be sufficient for ~25ppm accuracy according to the above formula. I'm going to start a series of measurements tonight when I leave, should be done in ~2 hours (10 pm) the latest.

If anybody wants to do some night work: I misaligned ITMY by a lot to get its reflection off ASDC. Approximate values are saved as a restore point. Also the whitening gain on ASDC will have to be rolled back (was at 0dB) and LSC offsets adjusted.

12617   Tue Nov 15 20:26:35 2016 JohannesUpdateCamerasBasler GigE-Camera on Optimus (+Mafalda dead)

I powered up the existing ace100gm GigE cam with the PoE injector and tried to interface with it as described in elog 4163. After a few initial problems with IP assignment and interfacing I connected it to one of the gigabit hubs and installed the most recent pre-compiled software suite on /opt/pylon5 on optimus, after which I was able to find it with the configuration software. I named it "c1gige_bas100-1" and gave it the static IP address 192.168.113.151.

Afterwards the image acquisition worked without problems.

It may be a good idea to leave the gigecam interfacing up to a dedicated machine. I was thinking I could use Mafalda for this, and also for developing the code for framegrabbing and imager settings, but found that it was dead, burnt at the stake so to say. I guess it wasn't running anything critical, since it wasn't even connected to the network and smelled like burnt electronics. I'll get a replacement desktop for it.

Attachment 1: gige_test.png
12618   Tue Nov 15 20:35:19 2016 JohannesUpdateGeneralAchievable armloss measurement accuracy

I had a mistake in my script that reported the wrong error after averaging several datapoints, and because I hadn't looked at the individual numbers I didn't catch it so far. Thanks to Gautam it is no more.

The updated numbers are (with fresh, more trustworthy data):

XARM: 21 +/ 35 ppm
YARM: 69 +/- 45 ppm

This looks much better. I'm planning to take more data with the AS110 PD rather than AS55 when I get the chance, increase the averaging time, and also sigma filter the datapoints. That should get us to a good spot and cut down the uncertainty even further.

12624   Thu Nov 17 21:54:11 2016 JohannesUpdateGeneralAchievable armloss measurement accuracy

I don't like AS110 or AS55. Neither of them are designed for DC and so the DC readout chain is hokey. How about use an actual transimpedance PD with a 100-1000 Ohm resistor and a 3 mm diode? This would eliminate the alignment sensitivity and the drifts due to electronics and room lights.

 This looks much better. I'm planning to take more data with the AS110 PD rather than AS55 when I get the chance, increase the averaging time, and also sigma filter the datapoints. That should get us to a good spot and cut down the uncertainty even further.

12625   Fri Nov 18 00:25:08 2016 JohannesOmnistructure40m upgradingAcromag Chassis Development

I had Rich show me his approach to a chassis for the Acromag modules. The document tree for his design can be found on the DCC. Note that he's using the high densitymodel ES series, which is available as a bare board variant with pluggable screw terminals:

He can fit up to 4 of these in a 2U chassis and has outsourced the wiring from front panel Dsubs to the board connectors to an external company. At the 40m (and in West Bridge) we currently only have the rail mounted XT series

At first glance the specs are very similar. Both A/D and D/A flavors have 16-bit precision in both cases. The high density ES series with Rich's layout can achieve 128 A/D per 2U, 64 D/A per 2U, or 384 DIO per 2U. Into a 4U chassis of the type we have currently we can fit ~32 XT modules (assuming two rows), which results in very similar numbers, except for the DAC, of which we could fit more.

XT1221-000 (8 diff. channel 16-bit ADC)                          $495.00$61.88/ch
XT1541-000 (8 channel 16-bit DAC and 4 discrete I/O )    $525.00$65.63/ch
XT1120-000 (16 channel DIO)                                         $320.00$20.00/ch

ES2162-0010 (32 diff. channel 16-bit ADC)                     $2050.00$64.06/ch
ES2172-0010 (16 channel 16-bit DAC)                           $1400.00$87.50/ch
ES2113-0010 (96 channel DIO)                                      $1100.00$11.46/ch

It's cheaper to stick with the current XT models, but they need the bulkier 4U chassis. The good news is that actually all these models have 16 bit precision, which wasn't clear to me before. Lydia and I will work out what connectors we want on the boxes, and how many modules/channels we need where. Rich also got me in touch with Keith Thorne, who handles the analog I/O Acromag at LLO, and I will ask him for advice. From his documents on the DCC it seems that he is using yet another series: EN. The 968EN-4008 for example is a rail-mounted ADC with pluggable connections, but looses quite clearly in price per channel.

For a generic multipurpose DAQ interface box the ES series is the best approach in my opinion, because it offers a more compact design. We could for example fit 1 ADC, 2 DAC, 1 DIO in a 2U chassis for 32/32/96 channels. The combined price tag for this scenario would be ~$6k. 12632 Mon Nov 21 19:54:13 2016 JohannesUpdateCDSacromag chassis hooked up to PSL [Lydia, Johannes] We connected and powered up the Acromag chassis today. It lives in 1X4 and is powered by the Sorensen +20V power supply in 1X5 via the fuse rail on the side of 1X4. For this we had to branch off the 20V path to the dewhitening and anti-image filter crate of the c1:susaux driven SOS optics. After confirming that none of the daughter modules in the crate draw from the 20V line, we added a wire leading to a new fuse we added for this unit and ran a power cable from there. The diagnostic connector of the PSL laser is now connected to the unit and a tmux session was created on megatron that interfaces with the chassis and broadcasts the EPICS channels. We need to watch out in the coming days for epics freezes/outages, as in the past these seemed to occur around the same times we were toying with the Acromags.  Quote: We set up the chassis in 1X7 today. Steve is ordering a longer 25 pin cable to reach. Until then the PSL diagnostic channels will not be usable. Attachment 1: acromag_chassis.jpg 12634 Tue Nov 22 13:55:32 2016 JohannesOmnistructure40m upgradingAcromag Chassis Current Acromag chassis status: I found out that Acromag offers DIN rail mounting kits for the open boards, so we can actually fit both XT series and ES/EN series in the same boxes, depending on the signal needs. The primary design driver will be the ES footprint, but if we find we don't need that many channels in some of the units, it's interchangable. For the wiring to the front panel - for which we will have a standard front panel express design, but may order modified ones for the custom needs of the 40m, I will contract the same company that Rich used for the wiring in his DIO box (Panel mount connectors terminating in loose wires/pre-routed plugs for Acromag units). We will either run a single DIN rail along the length of the chassis, or have two in parallel across. Lydia and I took close looks at the breakout arrangements on the rack sides, and determined that because of the many cross-connects between non-DAQ ports it is not possible to redo and debug this in a reasonable amount of time without essentially shutting down the interferometer. So instead, we will connect the chassis directly to the slots that were previously leading to the slow machines. They come in two different flavors: The ADC modules have 64 pins, while the DIO and DAC ones have 50. There are a couple things we can do: • For ADC: Put favorite 64+ pin connector on front panel. I would advocate for the 68 pin VHDIC (SCSI-5). This standard ist widely used, has a sturdy connector, and usually off-the-shelf cables have twisted pair leads. • For DAC+DIO: Either use favorite 50 pin connector (there are 50-pin DSUB connectors, and also 50-pin IDC connectors with backshell), or also send the signals through VHDIC connectors, tolerating a few unused lanes. I would prefer the second option, after all it all goes to some 64 pin VME-crate backplane connector in the end, so if we ever get rid of the rack-side breakouts the wiring will much more uniform. • For good measure, we will add a few (16 maybe) BNC connectors to the front panel. • A standardized front panel could have a variety of different connectors by default: DSUBs, BNCs, etc., to be used when needed with some initial default wiring. • Note that THEORETICALLY we could even connect all backplane EUROCARD ports to the Acromag chassis and do the cross-connect wiring entirely inside, although that would make the inside extremely messy. Based on Rich's design I will get started on a parts list and wiring diagrams to send out to the cable company. Attachment 1: acroplan.pdf 12651 Wed Nov 30 14:54:01 2016 JohannesUpdateCDSSlow machine replacement I was talking with Larry yesterday, and he suggested the rack-mounted supermicro machines SYS-5017A-EP (~$400) or SYS-5018A-FTN4 (~600) that he uses for moving data around in LIGO. They have 2 gigabit ethernet ports and can thus function as modbus gateways, conveniently placed in the rack close to the slow DAQ/DIO chassis and running some local ubuntu or other distro (I think Aidan uses CentOS in the PSL lab). These only have atom processors, which would be sufficient for the slow machine replacement, but there are many more powerful models with sometimes subtle differences. If we motion towards a more complete GigECam coverage in the lab it could be better to kill two birds with one stone and get something a little faster that can do the video capture/processing, since these machines will be distributed more or less strategically around the lab. Just a thought, as I have currently no clear idea what resources are required for this or how much we're throwing at this GigECam upgrade.  Quote: I've attached a schematic for how we will connect the Acromag mosules to the slow channel I/O curently going to c1auxex. The following changes are made: We are getting rid of the slow readbacks from the Anti-Image and Oplev boards, as Rana says they are unnnecessary. The whitening switching for the QPD is currently done by a Contec "fast" binary I/O module, but can be managed by acromag instead. This alllows CAB_1Y9_34 to be fed directly into the Acromag box since all of its connections can now be managed slow. There's no need to change the PD whitening scheme around (since the signals never get huge), so we can set those to always be on and then lose those Contec channels. This means all of the necessary pins on CAB_1Y9_10 can go to Acromag. All the other backplane cables go the the fast machines only. 12704 Thu Jan 12 02:45:53 2017 JohannesUpdateGeneralNext armloss steps As stated in elog 12618, using an oscilloscope to average the reflected powers and thus circumventing all filtering yielded much better results than before: XARM: 21 +/- 35 ppm YARM: 69 +/- 45 ppm We can probably decrease the measurement uncertainty further by using a larger photodiode that is more suited for DC measurements. It will be placed in the AS pathtemporarily. If we get below 10 ppm systematic errors will begin to matter. To get those under control I will have to re-determine the visibility in the arm cavities and the modulation indices. The numbers to match from an estimate via the power recycing gain are <= 50 ppm arm average from elog 12586. Once the measurement scheme is up and running, we can proceed to generate ETM lossmaps. ITM will still be tricky but let's see what we can do. Following Yutaro's approach, we can move the beams on the optcs in a deterministic way by several mm on the ETMs. Moving the beam is achieved by introducing offsets into the ASS auto alignment. As an example, the Yaw dither for ETMY is shown: Each of the 8 test mass rotational degrees of freedom is driven by a particular frequency, and 2 signals are digitally demodulated in the real-time system: The arm transmission ("T") and the LSC arm length feedback signal to the ETM (L). The T signal feeds back to the input pointing, aka Tip Tilts and BS. This maximizes the transmission for a given test mass orientation. The L feedback controls the beam position on the mirrors in the arms. It minimizes the coupling of the dither to the length feedback, which is achieved when the beam goes through the axis of the rotational motion. This is where we introduce the offset: The signal C1:ASS-YARM_ETM_YAW_L_DEMOD_I_OFFSET (for this example) moves the locking point of the dither-to-length coupling and thus moves the beam around on the ETM. This is true for the PIT and YAW of all test masses except ITMX. In the current configuration the TTs optimize the alignment into the YARM, and for the X we only have the BS, which is why the beam spot on ITMX cannot be independently controlled as-is. We could, however, for the sake of this measurement, temporarily temporarily give TT authority to the XARM feedback to control the ITMX beam position. I imagine something like dither-aligning with ASS the normal way, and then run a customized script in which the XARM is treated as the YARM, feecback to the BS is cut, and the YAW signals are inverted due to the reflection on BS. Knowing the angle of the offset gives us a way to calculate the beam spot displacement with the cavity geometry. For best results I want to make sure our OpLev calibration is still good (laser power decay, although last time this was done was only about a year ago), which would be analogous to elog 11831. As for ITM beam position, this scheme only works partially, because it would require the beam to steer further off its axis than in the ETM case. This is problematic because of the spacing between tip tilts and ITMs. I summarize: 1. Place larger DCPD in AS path 2. Confirm mode-matching and mod-indices 3. Assess loss in center with zero offsets 4. Uncertainty low enough? If not get better. 5. Calibrate OpLevs 6. Introduce calibrated offsets in dither alignment 7. Wander beam on test masses, recording arm losses 8. ??? 9. Profit Attachment 1: ass_illustration.pdf 12710 Fri Jan 13 08:54:32 2017 JohannesUpdateGeneralDC PD installed I installed a DC PD (Thorlabs PDA 520) in the beam path to AS55. I placed a 2" 90/10 BS on a flip mount that picks of enough light for the PD to spit out ~8V when the port is bright. Single arm continuous signal will be ~2V. While most of the light still continues towards AS55, the displacement from the BS moves the beam off AS55, so I used the flip mount in case anyone needs to use AS55. The current configuration is UP. When we're done with loss investigations the flip mount should be removed from the bench. I hooked the PD up to an ethernet-enabled scope and started scripting the loss map measurement (scope can receive commands via http so we can automate the data acquisition). The scope that was present at the bench and had been used for the MC ringdown measurements had a 'scrambled' screen that I couldn't fix so I had to retrieve another scope ("scope1"). I'll try to find out what's wrong with it but we may have to send it in for repair. 12781 Tue Jan 31 22:15:02 2017 JohannesUpdateCDSvme crate backplane adapter boards I made a crude sketch for how Lydia and I envision the connector situation on the back of the vme crates to be solved. Essentially the side panels of each crate extend about 2" (52 mm) beyond the edge of the DIN connectors. This is plenty of space for a simple PCB board. The connector of choice is D-Sub. We can split the 64 used pins into 2x 37 D-Sub OR (2x25 pin + 1x15pin). The former has fewer cables, but a few excess unused leads. A quick google search showed me that it is much cheaper to get twisted pair cables for 15 and 25 pin D-Subs. From what I remember, the used pins on the DIN connectors are concentrated on the low numbers end and the high numbers end, so might not need the 'middle' connector in many cases if we decide to break it up into three. I have to check this with Lydia though. The D-Sub connectors would be panel mounted, for which we need a narrow panel piece with dsub cutouts. We can run horizontal struts across the vme crate from side panel to side panel. This way the force upon cable (dis)connection is mostly on the panel which is attached to the struts which are attached to the crate. This will also prevent gravitational sag or cable strain from pulling on the DIN connection, and we can use twisted pair cables with backshell, screws, and strain reliefs. I was lookng into getting started with the PCB when Altium complained that the license is expired and to renew it. This is a relatively simple board layout so some free software out there is probably enough. Attachment 1: vme_backplane_conn_sketch.jpg 12810 Tue Feb 7 19:14:59 2017 JohannesUpdateCDSvme crate backplane adapter board layout After fighting with Altium for what seems like an eternity I have finished putting my vision of the vme crate backplane adapter board into an electronic format. It is dimensioned to fill the back space of the crate exactly. The connectors are panel mount and the PCB attaches to the connectors with screws, such that the whole thing will be mechanically much more stable than the current configuration. A mounting bracket will attach to horizontal struts that need to be installed in the crates, mechanical drawings to follow. Attachment 1: vme_backplane.pdf 12829 Wed Feb 15 00:26:44 2017 JohannesUpdateDAQpanels and pcbs I finished designing the PCBs for the VME crate back sides (see attached). The project files live on the DCC now at https://dcc.ligo.org/LIGO-D1700058. I ordered a prototype quantity (9) of the PCB printed and bought the corresponding connectors, all will arrive within the next two weeks. See also attached the front panels for the Acromag DAQ chassis and Lydia's RF amplifier unit (the lone +24V slot confuses me: I don't see a ground connector?). On the Acromag panel, six (3x2) of the DB37 connectors are reserved for VME hardware, two are reserve, and I filled the remaining space with general purpose BNC connectors for whatever comes up. Attachment 1: acromag_chassis_panel.pdf Attachment 2: vme_backplane_panel.pdf Attachment 3: rfAmp.pdf 14496 Tue Mar 26 04:25:13 2019 JohannesUpdateUpgradec1susaux upgrade plan Quote: ## Main TODO items • Debug issue with Acromag DC power wiring • Complete wiring from chassis feedthroughs to Acromag terminals, following this wiring diagram • Check/set the configuration of each Acromag unit using the software on the Windows laptop • Set the analog channel calibrations in the EPICS database file • Test each channel ex situ. Chub and I discussed an idea to use two DB-37F breakout boards, with the wiring between the board terminals manually set. One DAC channel would be calibrated and driven to test other ADC channels. A similar approach could be used for the digital input/output channels. Just a few remarks, since I heard from Gautam that c1susaux is next in line for upgrade. All units have already been configured with IP addresses and settings following the scheme explained on the slow controls wiki page. I did this while powering the units in the chassis, so I'm not sure where the short is coming from. Is the power supply maybe not sourcing enough current? Powering all units at the same time takes significant current, something like >1.5 Amps if I remember correctly. These are the IPs I assigned before I left:  Acromag Unit IP Address C1SUSAUX_ADC00 192.168.115.20 C1SUSAUX_ADC01 192.168.115.21 C1SUSAUX_ADC02 192.168.115.22 C1SUSAUX_ADC03 192.168.115.23 C1SUSAUX_ADC04 192.168.115.24 C1SUSAUX_ADC05 192.168.115.25 C1SUSAUX_ADC06 192.168.115.26 C1SUSAUX_ADC07 192.168.115.27 C1SUSAUX_ADC08 192.168.115.28 C1SUSAUX_ADC09 192.168.115.29 C1SUSAUX_DAC00 192.168.115.40 C1SUSAUX_DAC01 192.168.115.41 C1SUSAUX_DAC02 192.168.115.42 C1SUSAUX_DAC03 192.168.115.43 C1SUSAUX_BIO00 192.168.115.60 C1SUSAUX_BIO01 192.168.115.61 C1SUSAUX_BIO02 192.168.115.62 I used black/white twisted-pair wires for A/D, red/white for D/A, and green/white for BIO channels. I found it easiest to remove the blue terminal blocks from the Acromag units for doing the majority of the wiring, but wasn't able to finish it. I had also done the analog channel calibrations using the windows untility using multimeters and one of the precision voltage sources I had brought over from the Bridge labs, but it's probably a good idea to check it and correct if necessary. I also recommend to check that the existing wiring particularly for MC1 and MC2 is correct, as I had swapped their order in the channel assignment in the past. While looking through the database files I noticed two glaring mistakes which I fixed: 1. The definition of C1SUSAUX_BIO2 was missing in /cvs/cds/caltech/target/c1susaux2/C1SUSAUX.cmd. I added it after the assignments for C1SUSAUX_BIO1 2. Due to copy/paste the database files /cvs/cds/caltech/target/c1susaux2/C1_SUS-AUX_<OPTIC>.db files were still pointing to C1AUXEX. I overwrote all instances of this in all database files with C1SUSAUX. 97 Mon Nov 12 23:44:19 2007 JohnUpdatePSLISS  Quote: After John soldered a 3.7 MHz notch filter onto the ISS board, I took a quick TF and RIN measurement. The out-of-loop RIN is attached, including a dark noise trace, and with the gain slider at 10dB. The UGF is 35kHz with a phase margin of 30deg. John is currently doing a more thorough inspection, and will detail his findings in a subentry. No progress on the ISS tonight. I tried to implement a new filter (attached)to try and gain some phase before the notch. If anything this made things worse. More work is needed. The ISS loop is off and the power is off at the chassis. Attachment 1: ISSfilter.jpg 98 Tue Nov 13 14:33:40 2007 JohnUpdatePSLISS filter The transfer function from 'In Loop Error Point Monitor' to TP3 the filter out test point on the ISS board. -33dB at 3.715MHz. Attachment 1: PB130035.JPG Attachment 2: DSC_0165.JPG 104 Thu Nov 15 04:18:11 2007 JohnSummaryPSLPMC cavity pole measurements In connection with our work on the ISS I attempted to measure the PMC cavity pole. I swept the PMC PZT and looked at the transmission through the cavity on the ISS Monitor diode (which is now back on the table, feel free to remove it again tomorrow). To avoid thermal effects I reduced the laser power using the half wave plate at the laser ouput (rotated from 6 deg to 340deg). I swept the PZT using the triangle wave command "trianglewave C1: PSL-PMC_RAMP -3.5 3.3 20 200". I noticed that the functional form of the resonances deteriorated over the duration of the excitation. Each sweep was able to capture just over one FSR. The resonances were a little close to the 'points' of the triangle wave for my liking although I don't think PZT hysteresis was a big factor. Looking at the data the peaks are not of uniform width across a sweep or between consecutive sweeps. Hence any results from this mesurement are not particularly useful. I can't be sure if this was due to misalignments, thermal effects, higher order mode content or some other affect. Rob suggests sweeping the laser frequency using the NPRO PZT instead. Attachment 1: Peaks.jpg 107 Thu Nov 15 18:23:55 2007 JohnHowToComputersSwap CAPS and CTRL on a Windows 2000/XP machine I've swapped ctrl and caps on the four control room Windows machines. Right ctrl is unchanged. Start menu->Run "regedit" HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout Click on the KeyboardLayout entry. Edit->New Binary Value name it Scancode Map. Then select the new Scancode Map entry. Edit menu->Modify Binary Data. In the dialog box enter the following data: 0000: 00 00 00 00 00 00 00 00 0008: 03 00 00 00 3A 00 1D 00 0010: 1D 00 3A 00 00 00 00 00 Exit the Registry Editor. You need to log off and then on in XP (and restart in Windows 2000) for the changes to be made. 108 Thu Nov 15 18:36:48 2007 JohnSummary PSL table work I've rotated the lambda/2 plate to 340deg (from 6 deg) and blocked one arm of the Mach-Zender. Undo both if you need to. 116 Tue Nov 20 10:11:33 2007 JohnSummaryPSLPMC pole measurements We measured the PMC pole in the following way. 1. Reduced laser power by rotating lambda/2 plate at laser output. Thermal effects in the PZT distort resonance peaks. Reducing power too much leads to problems with digitisation error. 2. Sweep NPRO PZT (C1: PSL-FSS_INOFFSET) using trianglewave. Record ramp, PMC transmission and reference cavity transmission ('C1: PSL-FSS_FAST','C1: PSL-ISS_INMONPD_F','C1: PSL-FSS_RCTRANSPD_F). 3. Since the PZT cannot sweep a full FSR in the PMC we looked at the sideband resonances within the reference cavity to calibrate the actuator. Result: 7.35 +/- 0.22 MHz/V 4. Use #3 to calibrate the x axis of the PMC transmission. 5. Fit PMC resoances to an Airy function to get finesse. Take an average, weighted according to the resnorm. Calculate cavity pole frequency. Result: 380kHz +/- 59kHz. This corresponds to a finesse of ~936. According to this plot the nominal pole is at 488kHz and the finesse is 732. This is by no means a definitive measurement due to the misshapen resonance peaks recorded. Attachment 1: FittedPMCPeak.jpg 119 Tue Nov 20 18:02:54 2007 JohnSummaryComputersPSL_Main screen I've updated the PSL_MAIN screen. The old version may be found in cvs/cds/caltech/medm/old/medm/psl. Attachment 1: PSL_Screen.tif 120 Tue Nov 20 18:35:20 2007 JohnHowToComputersMatLab in Emacs If you can't get MatLab to run in emacs try adding the following to the .emacs file (setq matlab-shell-command-switches '("-nojvm")) This stops the gui opening. To start MatLab type M-x matlab-shell. To enter MatLab mode M-x matlab-mode. I've done this on LINUX3. To run MatLab in emacs under windows one can use MatLabShell http://www.cs.umb.edu/~ram/matlabShell/index.html 259 Thu Jan 24 12:50:50 2008 JohnSummaryTreasureSugar Napoleons Some pictures from the group meeting yesterday. Attachment 1: Sweeties.pdf 271 Sat Jan 26 02:02:43 2008 JohnSummaryGeneralNew Channels I added the following channels. # C1ASC_QPDs [C1:SUS-ETMY_QPDSUM_MON] [C1:SUS-ETMY_QPDYAW_MON] [C1:SUS-ETMY_QPDPIT_MON] [C1:SUS-ETMX_QPDSUM_MON] [C1:SUS-ETMX_QPDYAW_MON] [C1:SUS-ETMX_QPDPIT_MON] The old .ini file is /cvs/cds/caltech/chans/daq/C0EDCU_26_1_2008.ini 272 Sat Jan 26 02:08:53 2008 JohnOmnistructureLSCFibres There is now a fibre running from the SP table to the ISCT at the Y-end. In the coming days I will try to mode match the beam from this fibre into the arm through ETMY. To achieve this I will be altering the optical layout of this table. 275 Sat Jan 26 18:48:43 2008 JohnSummaryComputersRestart iscepics iscepics died this afternoon. We restarted it and restored settings from yesterday. I've written up instructions in the wiki. 276 Sat Jan 26 22:00:03 2008 JohnUpdateGeneralLSC-TRY_OUT and ETMY-QPD In the path from the ETM to the trans PD and QPD at the Y end I have replaced a BS1-1064-10-2037-45P with a polariser. The power falling on these diodes has been reduced. When the arm is locked in its nominal state the transmitted power is now less than 1. This polariser should serve as an injection point for the auxiliary arm locking. I am attempting to use crossed polarisations to separate this loop from the main arm light. 288 Thu Jan 31 12:39:14 2008 JohnConfigurationGeneralY arm test mass cameras I've adjusted the test mass cameras on the y arm to make the beam injected through ETMY more visible. 290 Fri Feb 1 10:43:05 2008 JohnUpdateEnvironmentConstruction work The boys next door have some bigger noisier toys. Attachment 1: DSC_0433.JPG 293 Fri Feb 1 17:17:05 2008 JohnSummaryPSLMach-Zender tweaking I helped Rob adjust the alignment of the Mach-Zender to try and reduce any AM on the laser light. Our goal was to reduce the large offsets in the DD signals. We reduced the MZ refl from 0.54 to 0.39. We were able to re-lock the mode cleaner without problems. We then centred the WFS heads. No change in the DD signal offsets. 294 Sat Feb 2 14:11:27 2008 JohnSummaryComputersOPTLEVmaster screen I changed the layout of the optlev master screen. The old version is /cvs/cds/caltech/medm/old/C1ASC_OPTLEVmaster080202.adl 296 Mon Feb 4 22:01:57 2008 JohnSummaryLSCFibres auxiliary locking - Fibers I managed to couple ~75% of the light transmitted from the y arm, through the fibre, back to the SP table. I hoped that this would be a good way to match the beam from the fibre into the arm. Still no flashes. It looks like the cameras just aren't sensitive enough. 304 Sat Feb 9 13:05:48 2008 JohnSummaryIOOPMC camera/ HEPA I replaced the Gig-E camera on the PMC trans beam. The PZT was close to railing and I wanted to adjust it. I just did a quick job, there is a little scattered light on the image. If Joe is finished with the Gig-E I'll take another look at it. The HEPA in the PSL table was turned off for some reason. I turned it back on. 305 Sat Feb 9 13:32:07 2008 JohnSummarySUSAll watchdogs tripped When I arrived this afternoon the watchdogs had tripped on all optics. I reset them and enabled the coil currents. I had to adjust the alignment of the mode cleaner to get it to lock. 315 Wed Feb 13 20:37:11 2008 JohnUpdateLSCFibre locking - Fiber Sam and I observed fringes in the light reflected from the Y arm. These fringes are due to the sidebands and not the carrier. To improve matters we plan to reduce the RF AM and increase our modulation index. 324 Tue Feb 19 18:28:41 2008 JohnUpdatePEMMore seismic in Baja California Steve spotted more activity from the same quake. Reset watchdog on ETMY. 328 Thu Feb 21 18:29:28 2008 JohnSummaryGeneralHP Network Analyser Analyzer The HP 4195A network analyser may be broken, measurements below 150MHz are not reliable. Above 150MHz everything looks normal. This may be caused by a problem with its output (the one you'd use as an excitation) which is varying in amplitude in a strange way. Analyzer 342 Wed Feb 27 22:05:03 2008 JohnUpdateLSCAuxiliary locking A summary of the status of the auxiliary arm locking effort. To help with lock acquisition we are attempting to independently lock the Y arm using light injected through ETMY. At present this secondary light source is an NPRO laser situated on the SP table. The laser light is transported to the ETM using a single mode optical fibre. In the future we might pick off some PSL light and apply a frequency shift. We have been able to successfully mode match the fibre beam into the cavity and have been attempting lock the cavity using standard PDH signals (phase modulation sidebands are added to the light before it enters the fibre). As yet no acceptable error signals have been produced. The demodulated RF signal is showing a time varying, bipolar dc offset. We have minimised the residual amplitude modulation of the EOM but we expect small signals due to the undercoupled nature of the system, it could be that whatever RFAM still present is varying with time and causing this behaviour. We are also able to produce similar offsets by stressing (i.e. bending, shaking) the fibre. Could it be that the fibre is somehow converting PM into AM? Are we seeing etalon effects in the fibre or elsewhere? If we cannot make any further progress with the existing setup we shall move the NPRO to the ETM table and try again. We are also looking into purchasing some other types of fibre. Other things to consider are injecting through POY or using some other wavelength - neither seems obviously better. Fiber, behavior 348 Fri Feb 29 13:51:17 2008 JohnSummaryLSCPD6 response I checked the response of PD6 using the AM laser. It looks happy enough. 16 averages -10dBm source power 77.3mV dc on the diode 359 Wed Mar 5 12:35:09 2008 JohnSummaryComputer Scripts / ProgramsPlot photodiode responses in MatLab A matlab function to plot the responses of photodiodes. There's still plenty of room for improvement but it should work for all our diodes without any changes. You may want to adjust which points are used in the fit to remove time delay. % Plot data from diode response measurements function out = diodeplot(f_Hz,mag_dB,phase_deg,f_beat_MHz) % $$clear all %$$ close all
% $$clc %$$$% $$%$$$ mag = dlmread('D:\40m\PD6\M7.txt','\t', 15, 0);
% $$phase = dlmread('D:\40m\PD6\P7.txt','\t', 15, 0); %$$$% $$% Frequency i.e. x-axis %$$$ f = mag(:,1);
% $$%$$$% Magnitude in dB % $$mag_dB = mag(:,2); %$$$
% $$% Phase in degrees %$$$phase_deg = phase(:,2); % $$%$$$ % Frequencies of interest
% $$f_beat_MHz = [33 133 166 199]*1e6; %$$$%$ diodeplot(f, mag_dB, phase_deg, f_beat_MHz)

% x axis limits
xmin = 10e6;
xmax = 500e6;

% Unwrap phase
phase_deg = (180/pi)*unwrap((pi/180)*phase_deg);

%Find values at our freqeuncies of interest
Mag_f_beat = interp1(f_Hz,mag_dB,f_beat_MHz);

% Remove the time delay from the phase data
% (May want to adjust which points are selected here)

straight = @(a, x) a(1) * x + a(2);

xdata = f_Hz;
ydata = phase_deg;

aguess = [10 0.1];
a = lsqcurvefit(straight,aguess,xdata,ydata);
fit = straight(a,xdata);

phase_deg = phase_deg-fit;

figure(1)
ha = axes('units','normalized','position',[0 0 1 1]);
uistack(ha,'bottom');
hi = imagesc(I);
colormap gray
set(ha,'handlevisibility','off', ...
'visible','off')
plot(xdata,ydata,'r')
hold on
plot(xdata,fit,'k')
plot(xdata,phase_deg,'b')
hold off
ylabel('Phase/ degrees', 'FontSize',12)
xlabel('Frequency/ Hz', 'FontSize',12)
title('Removing the time delay','FontSize',16)
legend('data','fit','data-fit',0)
set(gca,'Color','None')
box off

figure(2)
set(gcf,'Color', [1 1 1])
subplot(4,1,[1 3])

semilogx(f_Hz,mag_dB,'k','LineWidth',2.5)
title('Response of PD6','FontSize',16)
ylabel('Magnitude/ dB', 'FontSize',12)
xlim([xmin xmax])
grid

MagLayout = get(gca, 'Position');
YLimits = get(gca, 'YLim') ;
LabelExt = [];

for ivar = 1:length(f_beat_MHz);

a = text(f_beat_MHz(ivar),1.05 * min(Mag_f_beat),...
sprintf('%2.1fdB @ %dMHz', Mag_f_beat(ivar),f_beat_MHz(ivar)/1e6),...
'FontSize',10,'FontWeight','Bold','HorizontalAlignment','right',...
'VerticalAlignment','top','BackgroundColor',[.7 .9 .7],...
'Margin',0.5, 'Rotation',90);
LabelExt = [LabelExt; get(a,'Extent')];
LabelPos = get(a,'Position');

end

% Change YLim so that it is around the bottom of the labels
% There must be a better way
set(gca, 'YLim', [min(LabelExt(:,2)) YLimits(2)])

% Remove the last tick mark so that it doesn't overlap with the
% +180 of the phase plot
YTickLabelNew = str2num(get(gca, 'YTickLabel'));
YTickNew =[[] YTickLabelNew(2:end) ];
set(gca,'XTickLabel', [], 'YTick', YTickNew)

% Add lines now we know what the YLims are
for ivar = 1:length(f_beat_MHz);
line([f_beat_MHz(ivar) f_beat_MHz(ivar)], get(gca, 'YLim'))
end

subplot(4,1,4)
semilogx(f_Hz,phase_deg,'r','LineWidth',2.5)
xlim([xmin xmax])
ylabel('Phase/ degrees', 'FontSize',12)
xlabel('Frequency/ Hz', 'FontSize',16)
grid
PhaseLayout = get(gca, 'Position');
PhaseLayout(4) = MagLayout(2)-PhaseLayout(2);

% Make the top of the phase plot align to the bottom of the
% magnitude plot
set(gca, 'Color', 'None', 'Position',PhaseLayout, 'YTick',[-180:45: ...
180])
set(gcf,'units','normalized','outerposition',[0 0 1 1]);
Attachment 3: PDbw.jpg
360   Wed Mar 5 12:51:48 2008 JohnSummaryLSCInitial Ligo Arm finesse versus lambda
I've taken the coating recipes for the initial ligo arm cavity from Rana's web page (ligo.caltech/edu/~rana/mat/)
and plotted the finesse as a function of wavelength. There is some uncertainty over the indices of refraction but
the main conclusion remains unchanged - i.e. it appears that using other wavelengths will be difficult.
Stefan is looking at how to tune the layers of any new mirrors to make dichroic optics.
Attachment 1: FofLambdaLIGOI.jpg
ELOG V3.1.3-