40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 193 of 339  Not logged in ELOG logo
ID Date Author Type Category Subjectup
  2958   Thu May 20 13:12:28 2010 josephbUpdateCDSPreparations for testing lsc,lsp, scy,spy together

In /cvs/cds/caltech/target/fb modified:

master: cleaned up so only io1 (IO processor), LSC, LSP, SCY, SPY were listed, along with their associated tpchan files.

daqdrc: fixed "dcu_rate 9 = 32768" to "dcu_rate 9 = 65536" (since the IO processor is running at 64k)

Added "dcu_rate 21 = 16384" and "dcu_rate 22 = 16384"

Changed "set gds_server = "megatron" "megatron" "megatron" 9 "megatron" 10 "megatron" 11;" to

set gds_server = "megatron" "megatron" 9 9;

The above change was made after reading Rolf's Admin guide: http://lhocds.ligo-wa.caltech.edu:8000/40m/Upgrade_09/CDS?action=AttachFile&do=get&target=RCG_admin_guide.pdf
The set gds_server is simply telling which computer the gds daemons are running on, and we don't need to do it 5 times.


In /cvs/cds/caltech/gds/params modified:

testpoint.par: added C-node7 and C-node8 for SCY and SPY respectively.

  5257   Wed Aug 17 17:51:54 2011 JenneUpdateTreasurePrepared for drag wiping

While waiting for the IFO team to align things (there were already ~5 people working on a ~1 person job...), I got all of our supplies prepped for drag wiping in the morning. 

The syringes are still on the flow bench down the Xarm.  I put fresh alcohol from unopened spectrometer-grade bottles into our alcohol drag wiping bottles.

The ITMs already had rails for marking their position in place from the last time we drag wiped.  I placed marker-rails for both ETMs.

  5262   Thu Aug 18 10:59:04 2011 steveUpdateTreasurePrepared for drag wiping

Quote:

While waiting for the IFO team to align things (there were already ~5 people working on a ~1 person job...), I got all of our supplies prepped for drag wiping in the morning. 

The syringes are still on the flow bench down the Xarm.  I put fresh alcohol from unopened spectrometer-grade bottles into our alcohol drag wiping bottles.

The ITMs already had rails for marking their position in place from the last time we drag wiped.  I placed marker-rails for both ETMs.

 We should use the deionizer before drag wiping with isopropanol.

  17078   Fri Aug 12 13:40:36 2022 JCUpdateGeneralPreparing for Shutdown on Saturday, Aug 13

[Yehonathan, JC]

Our first step in preparing for the Shutdown was to center all the OpLevs. Next is to prepare the Vacuum System for the shutdown.

 

  15375   Thu Jun 4 08:45:41 2020 JordanUpdateGeneralPresence at 40m

I will be at the 40m, in the Clean and bake lab today from ~9am to ~3pm.

  15378   Fri Jun 5 08:44:50 2020 JordanUpdateGeneralPresence at 40m

I will be at the 40m, in the Clean and bake lab today from ~9am to ~3pm.

  15385   Tue Jun 9 09:35:02 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab today from 9:30am to 4pm.

  15388   Wed Jun 10 14:00:33 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab from 10am to 4pm today. I will also replace an empty N2 cylinder.

  15390   Thu Jun 11 11:14:12 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab today from 11am to 4pm.

  15395   Fri Jun 12 11:40:14 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab today from 12pm to 4pm.

  15400   Tue Jun 16 08:58:11 2020 JordanUpdateGeneralPresence at 40m

I will be at the 40m today at 10am to deliver optics to Downs and to replace the TP2 controller.

  15405   Thu Jun 18 09:46:03 2020 JordanUpdateGeneralPresence at 40m

I will be at the 40m today from 9:30am to 4pm.

  15414   Fri Jun 19 08:47:10 2020 JordanUpdateGeneralPresence at 40m

I will be at the 40m today from 9am to 3pm.

  15422   Mon Jun 22 13:16:38 2020 JordanUpdateGeneralPresence at 40m

I will be at the 40m today from 11am to 4pm.

  15426   Wed Jun 24 10:14:56 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab today from 10am to 4pm.

  15430   Thu Jun 25 11:09:01 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab from 11pm to 4pm

  15432   Fri Jun 26 11:00:52 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab today from 11am to 4pm.

  15437   Mon Jun 29 11:41:04 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab today from 11:30am to 4pm

  15441   Tue Jun 30 08:50:12 2020 JordanUpdateGeneralPresence at 40m

I will be in the clean and bake lab today from 9am to 4pm.

  15444   Wed Jul 1 08:51:52 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab from 9am to 4pm today.

  15453   Mon Jul 6 08:48:15 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab today from 8:30am to 4pm

  15459   Wed Jul 8 08:51:35 2020 JordanUpdateGeneralPresence at 40m

I will be in the clean and bake lab today from 9am to 3pm.

  15461   Thu Jul 9 09:22:44 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab today from 9am to 3pm

  15467   Fri Jul 10 10:37:30 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab today from 9am to 4pm

  15478   Tue Jul 14 09:04:53 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake Lab today from 9am to 4pm.

  15492   Fri Jul 17 09:03:58 2020 JordanUpdateGeneralPresence at 40m

I will be in the Clean and Bake lab today from 9am to 4pm.

  15616   Wed Oct 7 13:06:27 2020 KojiUpdateGeneralPresence in the lab

Tue evening from 4pm~6pm, Koji made a social distant tour for Anchal. We were present around the PSL/AS/ETMX tables.

  11159   Mon Mar 23 10:36:55 2015 ericqUpdateVACPressure watch script

Based on Jenne's chiara disk usage monitoring script, I made a script that checks the N2 pressure, which will send an email to myself, Jenne, Rana, Koji, and Steve, should the pressure fall below 60psi. I also updated the chiara disk checking script to work on the new Nodus setup. I tested the two, only emailing myself, and they appear to work as expected. 

The scripts are committed to the svn. Nodus' crontab now includes these two scripts, as well as the crontab backup script. (It occurs to me that the crontab backup script could be a little smarter, only backing it up if a change is made, but the archive is only a few MB, so it's probably not so important...)

  12774   Tue Jan 31 14:14:29 2017 ranaUpdateVACPressure watch script

I think this cron job is running on NODUS (our gateway) instead of our scripts machine:

*/1 * * * * /opt/rtcds/caltech/c1/scripts/Admin/n2Check.sh >> /opt/rtcds/caltech/c1/scripts/Admin/n2Check.log 2>&1

Quote:

Based on Jenne's chiara disk usage monitoring script, I made a script that checks the N2 pressure, which will send an email to myself, Jenne, Rana, Koji, and Steve, should the pressure fall below 60psi. I also updated the chiara disk checking script to work on the new Nodus setup. I tested the two, only emailing myself, and they appear to work as expected. 

The scripts are committed to the svn. Nodus' crontab now includes these two scripts, as well as the crontab backup script. (It occurs to me that the crontab backup script could be a little smarter, only backing it up if a change is made, but the archive is only a few MB, so it's probably not so important...)

moreover this script has a 90MB log file full of not finding its channel

I wish this script was in python instead of BASH and I wish it would run on megatron instead of nodus (why can't megatron send us email too?) and I wish that this log file would get wiped out once in awhile. Currently its been spitting out errors since at least a month ago:

Tue Jan 31 14:10:02 PST 2017 : N2 Pressure:

Channel connect timed out: 'C1:Vac-N2pres' not found.

(standard_in) 1: syntax error

  11243   Fri Apr 24 17:30:32 2015 JenneUpdateVACPressure watch script broken
Quote:

I made a script that checks the N2 pressure, which will send an email to myself, Jenne, Rana, Koji, and Steve, should the pressure fall below 60psi.

The script checking the N2 pressure is not working.  I signed into the foteee account to look at some of the picasa photos, and there are thousands of emails (one every 10 minutes for the past month!) with error messages.  Q, can you please make it stop (having errors)?

The error looks like it's mad about a "caget" command.  I don't have time to investigate further though.

  11249   Sat Apr 25 18:50:47 2015 ericqUpdateVACPressure watch script broken

Ugh, this turns out to be because cron doesn't source the controls bashrc that defines where to find caget and all that jazz that many commands depend on. This is probably also why the AutoMX cron job isn't working either. 

Also, cron automatically emails everything from stderr to the email address that is configured for the user, which is why the n2 script blew up the foteee account and why the AutoMX script was blowing up my email yesterday. This can be avoided by doing something like this in the crontab:

0 8 * * * /bin/somecommand >> somefile.log 2>&1

(The >> part means that the standard output is appended to some log file, while the 2>&1 means send the standard error stream to the same place as stdout)

I made this change for the n2 script, so the foteee email account should be safe from this script. I haven't figured out the right way to set up cron to have all the right $PATH and other environment stuff, such as epics may need, so the script is still not working. 

  4079   Mon Dec 20 23:10:25 2010 JenneUpdateSUSPretty much ready for pump-down. A few final things....

[Kiwamu, Jenne, Koji, Osamu]

We have mostly prepared the IFO for pump down. 

After lunch [Steve, Bob, Koji, Kiwamu, Jenne, Joe, Joon Ho, Vladimir, Osamu] put the access connector back in place.  Hooray!  Steve still has to check the Jam Nuts before we pump down.  Kiwamu checked the leveling of the IOO table, and fixed all of the weights to the table.

For all 4 test masses, bars (upside-down dog clamps) were placed to mark the alignment of 2 sides of the suspension tower.  All test mass tables were re-leveled, and the weights fixed to the tables.  

For ETMY, PRM, BS, SRM, we confirmed that the OSEMs were close to their half-range.  ETMX was already fine.  ITMY (the screens and the optics wiki are still old-convention, so this is listed as ITMX! No good!) OSEMs are pretty much fine, but ITMX desperately needs to be adjusted.  Unfortunately, no one can find the standard screwdriver (looks like a minus), to adjust the ITM OSEMs.  All the other towers had hex-key set screws, but the ITMs need a screwdriver.  We will ask Bob to sonicate a screwdriver in the morning. 

 

 

  10995   Tue Feb 10 13:48:58 2015 manasaUpdateLSCProbable cause for headaches last night

I found the PSL enclosure open (about a feet wide) on the north side this morning. I am assuming that whoever did the X beatnote alignment last night forgot to close the door to the enclosure before locking attempts frown

Quote:

Unfortunately, we only had one good CARM offset reduction to powers of about 25, but then my QPD loop blew it. We spent the vast majority of the night dealing with headaches and annoyances. 

Things that were a pain:

  • If TRX is showing large excursions after finding resonance, there is no hope. These translate into large impulses while reducing the CARM offset, which the PRMI has no chance of handling. The first time aligning the green beat did not help this. For some reason, the second time did, though the beatnote amplitude wasn't increased noticibly. 
    • NOTICE: We should re-align the X green beatnote every night, after a solid ASS run, before any serious locking work. 
    • Afterwards, phase tracker UGFs (which depend on beatnote amplitude, and thereby frequency) should be frequently checked. 
  • We suffered some amount from ETMX wandering. Not only for realigning between lock attempts, but on one occasion, with CARM held off, GTRX wandered to half its nominal value, leading to a huge effective DARM offset, which made it impossible to lock MICH with any reasonble power in the arms. Other times, simply turning off POX/POY locking, after setting up the beatnotes, was enough to significantly change the alignment. 
  • IMC was mildly tempermental, at its worst refusing to lock for ~20min. One suspicion I have is that when the PMC PZT is nearing its rail, things go bad. The PZT voltage was above 200 when this was happening, after relocking the PMC to ~150, it seems ok. I thing I've also had this problem at PZT voltages of ~50. Something to look out for. 

Other stuff:

  • We are excited for the prospect of the FOL system, as chasing the FSS temperature around is no fun. 
  • UGF servo triggering greatly helps the PRMI reacquire if it briefly flashes out, since the multipliers don't run away. This exacerbated the ALS excursion problem. 
  • Using POPDC whitening made it very tough to hold the PRMI. Maybe because we didn't reset the dark offset...?

 

  3271   Fri Jul 23 00:13:11 2010 ranaUpdatePSLProblem NOT REALLY Solved

So...who was working around the PSL rack this morning and afternoon? Looks like there was some VCO phase noise work at the bottom of

the rack as well as some disconnecting of the Guralp cables from that rack. Who did which when and who needs to be punished?

  3270   Thu Jul 22 18:18:54 2010 AlbertoUpdatePSLProblem Solved

Quote:

Quote:

It looks like something wrong happened around the PSL front end.  One of the PSL channel, C1:PSL-PMC_LOCALC, got crazy. 

We found it by the donkey alarm 10 minutes ago.

The attached picture is a screen shot of the PMC medm screen.

The value of C1:PSL-PMC_LOCALC ( middle left on the picture ) shows wired characters. It returns "nan" when we do ezcaread.

Joe went to the rack and powered off / on the crate, but it still remains the same. It might be an analog issue (?)

The problem seems to be a software one.

In any case, Kiwamu and I looked at the at the PMC crystal board and demod board, in search of a possible bad connection. We found a weak connection of the RG cable going into the PD input of the demod board. The cable was bent and almost broken.

I replaced the SMA connector of the cable with a new one that I soldered in situ. Then I made sure that the connection was good and didn't have any short due to the soldering.

[Alberto, Koji]

By looking at the reference pictures of the rack in the wiki, it turned out that the Sorensen which provides the 10V to the 1Y1 rack was on halt (red light on). It had been like that since 1.30pm today. It might have probably got disabled by a short somewhere or inadvertently by someone working nearby it.

Turning it off and on reset it. The crazy LO calibrated amplitude on the PMC screen got fixed.

Then it was again possible to lock PMC and FSS.

We also had to burtrestore the PSL computer becasue of the several reboots done on it today.

  440   Wed Apr 23 22:39:54 2008 AndreyDAQComputer Scripts / ProgramsProblem with "get_data" and slow PEM channels

It turns out that I cannot read minute trends for the slow weather channels for more than 1000 seconds back (roughly more than 15 minutes ago) using "get_data" script.

For comparison, I tried MC1 slow channels, and similar problem did not arise there. Probably, something is wrong with the memory of slow weather channels. At the same time, I can see minute-trends in Dataviewer as long ago as I want.

In response to
>>get_data('C1: PEM-weather_outsideTemp', 'minute', gps('now') - 3690, 3600);
I get the error message:
"Warning: Missong C1: PEM-weather_outsideTemp M data at 893045156".
  261   Thu Jan 24 22:10:49 2008 AndreyConfigurationComputer Scripts / ProgramsProblem with channels - help of Rana, Robert or Steve is needed

I definitely spoiled something (changes some settings) by chaotically clicking those blue buttons (see my previous entry # 260).

Unfortunately, I cannot use standard library of functions for reading from channels from mDV directory.

Although I see the curve of a noise in the Dataviewer from the channel "Ch1:SUS_ETMX_POS", when I try to read data from the channel using the program "get_data" from MDV directory, I get the error message
"Warning: No data available for [numbers representing "gps_start_time" and "gps_end_time"].
In new_readframedata at 136
In new_fetch_shourov at 71
In get_data at 98"

I checked, both gps-times are in the past from now, so as far I understand, nothing is recorded into the channels.
Of course, I added two hours ago to the directory "mDV", that is I used addpath(pwd) in that directory.

And I also cannot run the program that I used on Tuesday evening which takes data from "C1:SUS_ITMX_POS" (no data from that channel), which worked perfectly on Tuesday.

I again apologize for clicking the wrong blue button (see my explanation in my previous message #260). I ask someone who knows how to return normal working of channels (normal interaction of computer and channel memory) to do that.

Before that I cannot take data. I do not know how to restore the initial settings which existed before I started adding the channel to Dataviewer.

Andrey.
  1040   Fri Oct 10 13:57:33 2008 AlbertoOmnistructureComputersProblems in locking the X arm
This morning for some reason that I didn't clearly understand I could not lock the Xarm. The Y arm was not a problem and the Restore and Align script worked fine.

Looking at the LSC medm screen something strange was happening on the ETMX output. Even if the Input switch for c1:LSC-ETMX_INMON was open, there still was some random output going into c1:LSC-ETMX_INMON, and it was not a residual of the restor script running. Probably something bad happened this monring when we rebooted all the FE computers for the RFM network crash that we had last night.

Restarting the LSC computer didn't solve the problem so I decided to reboot the scipe25 computer, corresponding to c1dcuepics, that controls the LSC channels.

Somehow rebooting that machine erased all the parameters on almost all medm screens. In particular the mode cleaner mirrors got a kick and took a while to stop. I then burtrestored all the medm screen parameters to yesterday Thursday October 9 at 16:00. After that everything came back to normal. I had to re-lock the PMC and the MC.

Burtrestoring c1dcuepics.snap required to edit the .snap file because of a bug in burtrestore for that computer wich adds an extra return before the final quote symbol in the file. That bug should be fixed sometime.

The rebooting apparently fixed the problem with ETMX on the LSC screen. The strange output is not present anymore and I was able to easily lock the X arm. I then run the Align and the Restore full IFO scripts.
  2491   Sat Jan 9 09:47:03 2010 AlbertoUpdateLSCProblems trying to lock the arms

This morning I've been having problems in trying to lock the X arm.

The X arm's filter FM6 in the LSC screen starts blinking as it was halfloaded. Then the transmitted power drops from 1 to ~0.5 and eventually the arm loses lock.
To me it looked like a computer related issue. So I decide to reboot C1ISCEX by powercycling it.

That doesn't seem to have solved the problem. The X arm can get locked but TRX slowly moves between 0.2 and 1.

  2492   Sat Jan 9 11:07:30 2010 AlbertoUpdateLSCProblems trying to lock the arms

Quote:

This morning I've been having problems in trying to lock the X arm.

The X arm's filter FM6 in the LSC screen starts blinking as it was halfloaded. Then the transmitted power drops from 1 to ~0.5 and eventually the arm loses lock.
To me it looked like a computer related issue. So I decide to reboot C1ISCEX by powercycling it.

That doesn't seem to have solved the problem. The X arm can get locked but TRX slowly moves between 0.2 and 1.

The X arm is now locked with TRX stable at ~1.

I think earlier on today I was having problems with running the alignment scripts from op540. Now I'm controlling the IFO from Rosalba and I can easily and stably lock all degrees of freedom.

I needed the X arm to be locked to align the auxiliary beam of the AbsL experiment to the IFO. To further stabilize TRX I increased the loop gain from 1 to 1.5.

Now the auxiliary beam is well aligned to the IFO and the beat is going through the PRC. I'm finally ready to scan the recycling cavity.

I also changed the gain of the PRC loop from -0.1 to -0.5.

  536   Tue Jun 17 22:00:53 2008 JohnHowToPSLProblems turning MZ servo on/off
We were unable to toggle the MZ servo on/off (Blank/Normal) from MEDM. Pushing on the Xycom board and cables changed the fault from constant to intermittent. At least one lock loss has been caused by a MZ glitch.
  9160   Wed Sep 25 19:34:51 2013 ranaUpdateSUSProblems with ETMY Optical Lever

I went down to investigate the issue with the extra noise that I found in the ETMY optical lever yesterday. There were several problems with the optical layout down there - I'm not sure if I remember them all now.

  1. Beam reflected from OL QPD not dumped.
  2. OL QPD set normal to the steering mirror so that the back reflection goes into the vacuum chamber.
  3. HeNe laser mount only dogged with 2 dogs. Needs 3. Looks like some said "Aw, that's not goin' nowhere. Let's just leave that there pard!"
  4. First lens downstream of the laser had 2 screws and washers, but neither was even finger tight! They were loose by more than 1 full turn.
  5. Second lens was clipping. Beam was so far off center that this lens was being used to steer the beam by a few inches on the QPD.
  6. Extra reflections from ingoing beam (I don't know which surfaces) randomly landing on green & red optics.
  7. Lenses for the HeNe mode matching are coated for 1064 nm. HeNe is 633 nm, so these lenses must be replaced to reduce the reflections.

The main noise issue, however, appears to be not a layout issue at all. Instead its that the laser intensity noise has gone through the roof. See attached spectra of the quadrants (this is the way to diagnose this issue).

I'll ask Steve to either heal this laser or swap it out tomorrow. After that's resolved we'll need another round of layout fixing. I've done a couple of hours today, but if we want a less useless and noisy servo we'll have to do better.

NOTE: by looking at the OL quadrants, I've found a noisy laser, but this still doesn't explain the excess noise in the ETMX. That was the one that has a noisier error signal, not ETMY. By the coherence in the DTT, you can see that the ETMY OL is correctly subtracting and normalizing out the intensity noise of the laser. Seems like the ETMX electronics might be the culprit down there.

Attachment 1: ETMY-BadHeNe.pdf
ETMY-BadHeNe.pdf
  9165   Thu Sep 26 11:00:51 2013 SteveUpdateSUSProblems with ETMY Optical Lever

We are out of JDSU-Uniphase 1103P heads. I'm ordering some right now. I'm planning to make some corrections on Rana's list tomorrow morning at ETMY.

  9166   Thu Sep 26 21:55:08 2013 ranaUpdateSUSProblems with ETMY Optical Lever

Not so fast! We need to plan ahead of time so that we don't have to repeat this ETMY layout another dozen times. Please don't make any changes yet to the OL layout.

Its not enough to change the optics if we don't retune the loop. Please do buy a couple of JDSU (and then we need to measure their intensity noise as you did before) and the 633 nm optics for the mode matching and then we can plan about the layout.

  12427   Sun Aug 21 17:21:22 2016 PrafulUpdateElectronicsProblems with PCB Circuit

For the past week, I've been trying to make a soldered amplifier circuit to use in a prototype box, However, I've been running into this same issue. The circuit, pictured below, works fine on a solderless breadboard.

simple_amp.png

When I amplify a sine wave, I get a clean looking result at the output on the solderless breadboard:

However, on my soldered circuit, if I turn up the negative voltage supply from the power supply past about -12.5V (the target is -15V), I get a strange signal that Gautam suggested looks like some kind of discharging.

At -12.3 V (soldered breadboard):

At -15.0 V (soldered breadboard):

The signal is much noisier. Zooming in on this second signal, this pattern appears:

This pattern is also showing up even when there is no input from the function generator and the circuit is just given a voltage supply of +/- 15V:

I have tried switching out both the positive and negative voltage regulators, the opamp, and remaking and resoldering the entire circuit but I'm still getting the same signal, which is absent from the solderless circuit. This output was produced with a function generator, so I have also ruled out the microphone as a source of this extra noise. The voltage dependence of this problem made me think it was the voltage regulator, but I've switched out the voltage regulator multiple times and it's still showing up. I'm not sure why this signal appears only as the negative voltage supply is increased- there is no problem with increasing the positive input voltage. Please let me know if you have any ideas as to what component or issue could be causing this.

Attachment 2: simple_amp.png
simple_amp.png
Attachment 4: clean.jpg
clean.jpg
Attachment 5: -12.jpg
-12.jpg
Attachment 6: -15.jpg
-15.jpg
Attachment 7: pat1.jpg
pat1.jpg
Attachment 8: pat2.jpg
pat2.jpg
Attachment 10: bad.jpg
bad.jpg
Attachment 11: pattern.jpg
pattern.jpg
Attachment 12: pattern2.jpg
pattern2.jpg
Attachment 13: pat2.jpg
pat2.jpg
Attachment 16: patternzoomed.jpg
patternzoomed.jpg
  56   Thu Nov 1 20:03:00 2007 Andrey RodionovSummaryPhotosProcedure "Drop and Drag" in pictures
Attachment 1: DSC_0072.JPG
DSC_0072.JPG
Attachment 2: DSC_0083.JPG
DSC_0083.JPG
Attachment 3: DSC_0099.JPG
DSC_0099.JPG
Attachment 4: DSC_0100.JPG
DSC_0100.JPG
  15462   Thu Jul 9 16:02:33 2020 JonHowToCDSProcedure for setting up BHD front-ends

Here is the procedure for setting up the three new BHD front-ends (c1bhd, c1sus2, c1ioo - replacement). This plan is based on technical advice from Rolf Bork and Keith Thorne.

The overall topology for each machine is shown here. As all our existing front-ends use (obsolete) Dolphin PCIe Gen1 cards for IPC, we have elected to re-use Dolphin Gen1 cards removed from the sites. Different PCIe generations of Dolphin cards cannot be mixed, so the only alternative would be to upgrade every 40m machine. However the drivers for these Gen1 Dolphin cards were last updated in 2016. Consequently, they do not support the latest Linux kernel (4.x) which forces us to install a near-obsolete OS for compatibility (Debian 8).

Hardware

Software

  • OS: Debian 8.11 (Linux kernel 3.16)
  • IPC card driver: Dolphin DX 4.4.5 [works only with Linux kernel 2.6 to 3.x]
  • I/O card driver: None required, per the manual

Install Procedure

  1. Follow Keith Thorne's procedure for setting up Debian 8 front-ends
  2. Apply the real-time kernel patches developed for Debian 9, but modified for kernel 3.16 [these are UNTESTED against Debian 8; Keith thinks they may work, but they weren't discovered until after the Debian 9 upgrade]
  3. Install the PCIe expansion cards and Dolphin DX driver (driver installation procedure)
  5464   Mon Sep 19 16:44:16 2011 KeikoHowToLSCProcedure for the demodulation board check

 Here I note the procedure for the demodulation board orthogonality check for the future reference.

1. prepare two function generators and make sure I an Q demodulation signals go to the data acquisition system.

2. sync the two generators

3. drive the function generator at the modulation frequency and connect to the LO input on the demod board

4. drive the other function generator at the modulation frequency + 50Hz  the RF in

5. run "orthogonality.py"  from a control computer scripts/demphase directory. It returns the amplitude and phase information for I and Q signals. If necessary, compensate the amplitude and phase by the command that  "orthogonality.py" returns.

 

If you want to check in the frequency domain (optional):

1. 2. 3 are the same as above.

4. drive the function generator at the LO frequency + sweep the frequency, for example from 1Hz to 1kHz, 50ms sweep time. You can do it by the function generator carrier frequency sweep option.

5. While sweeping the LO frequency, run "orthogonality.py"

6. The resulting plot from "orthogonality.py" will show the transfer function from the RF to demodulated signal. The data is saved in "dataout.txt" in the same directory.

  9573   Fri Jan 24 12:44:25 2014 GabrieleHowToLSCProcedure to measure PRC length

Here is how to measure the PRC length with a set of distance measurements in the optical setup. 

We need to take distance measurements between reference points on each mirror suspension. For the large ones (SOS) that are used for BS, PRM and ITMs, the reference points are the corners of the second rectangular base: not the one directly in contact with the optical bench (since the chamfers make difficult to define a clear corner), but the rectangular one just above it. For the small suspensions (TT) the points are directly the corners of the base plates.

From the mechanical drawings of the two kind of suspensions I got the distances between the mirror centers and the reference corners. The mirror is not centered in the base, so it is a good idea to cross check if the numbers are correct with some measurements on the dummy suspensions.

I assumed the dimensions of the mirrors, as well as the beam incidence angles are known and we don't need to measure them again. Small errors in the angles should have small impact on the results.

I wrote a MATLAB script that takes as input the measured distances and produce the optical path lengths. The script also produce a drawing of the setup as reconstructed, showing the measurement points, the mirrors, the reference base plates,  and the beam path. Here is an example output, that can be used to understand which are the five distances to be measured. I used dummy measured distances to produce it.

map.pdf

In red the beam path in vacuum and in magenta the beam path in the substrate. The mirrors are the blue rectangles inside the reference bases which are in black. The thick lines are the HR faces. The green points are the measurement points and the green lines the distances to be measured. The names on the measurement lines are those used in the MATLAB script. 

The MATLAB scripts are attached to this elog. The main file is survey_v2.m, which contains all the parameters and the measured values. Update it with the real numbers and run it to get the results, including the graphic output. The other files are auxiliary functions to create the graphics. I checked many times the code and the computations, but I can't be sure that there are no errors, since there's no way to check if the output is correct... The plot is produced in a way which is somehow independent from the computations, so if it makes sense this gives at least a self consistency test. 

Attachment 2: survey_v2.m
global sos_lx sos_ly sos_cx sos_cy tt_lx tt_ly tt_cx tt_cy

%% Survey of the PRC length

%% measured distances
d_MB2_MY  = 2000.0;
d_MB3_MX  = 2000.0;
d_MB1_M31 = 400.0;
d_M32_M21 = 3000.0;
d_M22_MP  = 2000.0;
... 210 more lines ...
Attachment 3: distance.m
function d = distance(c1, c2)
    d = sqrt(sum((c1-c2).^2));
end
Attachment 4: draw_beam.m
function draw_beam(c1, c2, color)
    plot( [c1(1), c2(1)], [c1(2), c2(2)], color, 'LineWidth', 2)
end
Attachment 5: draw_measurement.m
function draw_measurement(c1, c2, color, name)
    plot( [c1(1), c2(1)], [c1(2), c2(2)], color)
    text( (c1(1)+c2(1))/2, (c1(2)+c2(2))/2 + 20, name, ...
        'FontSize', 5, 'HorizontalAlignment', 'center', ...
         'VerticalAlignment', 'middle')
end
Attachment 6: draw_point.m
function draw_point(c)
    plot(c(1), c(2), 'go', 'LineWidth', 2, 'MarkerSize', 3);
end
Attachment 7: draw_sos.m
function draw_sos(C, angle)
    global sos_lx sos_ly sos_cx sos_cy tt_lx tt_ly tt_cx tt_cy

    c(:,1) = [-sos_lx/2, -sos_ly/2 + sos_cy-sos_ly/2]';
    c(:,2) = [-sos_lx/2, sos_ly/2 + sos_cy-sos_ly/2]';
    c(:,3) = [sos_lx/2, sos_ly/2 + sos_cy-sos_ly/2]';
    c(:,4) = [sos_lx/2, -sos_ly/2 + sos_cy-sos_ly/2]';
    c(:,5) = [-sos_lx/2, -sos_ly/2 + sos_cy-sos_ly/2]';
    
    m_lx = 25.4*2;
... 18 more lines ...
Attachment 8: draw_tt.m
function draw_tt(C, angle)
    global sos_lx sos_ly sos_cx sos_cy tt_lx tt_ly tt_cx tt_cy

    c(:,1) = [-tt_lx/2, -tt_ly/2 + tt_cy-tt_ly/2]';
    c(:,2) = [-tt_lx/2, tt_ly/2 + tt_cy-tt_ly/2]';
    c(:,3) = [tt_lx/2, tt_ly/2 + tt_cy-tt_ly/2]';
    c(:,4) = [tt_lx/2, -tt_ly/2 + tt_cy-tt_ly/2]';
    c(:,5) = [-tt_lx/2, -tt_ly/2 + tt_cy-tt_ly/2]';
    
    m_lx = 25.4;
... 18 more lines ...
  9574   Fri Jan 24 13:10:12 2014 JamieHowToLSCProcedure to measure PRC length

Quote:

I wrote a MATLAB script that takes as input the measured distances and produce the optical path lengths. The script also produce a drawing of the setup as reconstructed, showing the measurement points, the mirrors, the reference base plates,  and the beam path. Here is an example output, that can be used to understand which are the five distances to be measured. I used dummy measured distances to produce it.

map.pdf

This path does not look correct to me.  Maybe it's because this is supposed to represent "optical path lengths" as opposed to actual physical location of optics, but I think locations should be checked.  For instance, PRM looks like it's floating in mid-air between the BS and ITMX chambers, and PR2 is not located behind ITMX.  Actually, come to think of it, it might just be that ITMX (or the ITMs in general) is in the wrong place?

Here is a similar diagram I produced when building a Finesse model of the 40m, based on the CAD drawing that Manasa is maintaining:

path.pdf

ELOG V3.1.3-