40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log, Page 101 of 344  Not logged in ELOG logo
ID Date Authorup Type Category Subject
  5584   Fri Sep 30 08:40:02 2011 KojiUpdateLSClength fluctuations in MICH and PRCL

Tip-Tilts has almost no isolation up to 3Hz, and isolation of about 0.5 up to 10Hz.
They have vertical resonances at around 20Hz.

See Nicole's entry

Quote:

noise.png

 

  5591   Fri Sep 30 19:12:56 2011 KojiUpdateGeneralprep for poweroutage

 

 [Koji Jenne]

The lasers were shutdown

The racks were turned off

We could not figure out how to turn off JETSTOR

The control room machines were turned off

FInally we will turn off nodus and linux1 (with this order).

Hope everything comes back with no trouble

(Finger crossing)

  5592   Sat Oct 1 17:47:21 2011 KojiSummaryGeneralRecovery from the power shutdown

[Steve Koji Kiwamu]

- The storage on linux1 and linux1 itself (with this order) were turned on at 10:30am

- Kiwamu restored the vacuum system

   => opened V4, started TP1 (maglev) and opened V1.

      The pressure went downfrom 2.5 mTorr to the normal level in about 20 minutes.

- A regular fsck of linux1 was completed at 5pm

- Nodus was turned on. Mounting /cvs/cds succeeded

- The control room computers were turned on

- The rack power for FB turned on, FB and megatron started.

- Kiwamu and Koji went through all of the rack powers and started the slow and fast machines.
As we found Solensen for -15V at ETMX was current limited. +/-15V were turned off for now.
==> Kiwamu turned on Solensen again for investigation and found it became okay.
It's now ON.
 
- c1sus and c1ioo had many red lamps on the FE status screen.
Ran killc1XXX for all of the FE codes on c1lsc and c1ioo.
Then, made software reboot (sudo shutdown -r now)
All of the FEs shows green (after some randome clicking of DIAGRESETs)

- HVs on 1X1 were turned on. The are not vacuum HV, but used only in the air

- Turned on the RF generation box and the RF distribution box

- burtrestore slow machines (c1psl, c1susaux, c1iool0, c1iscaux, c1iscaux2, c1auxex, c1auxey)

  5613   Tue Oct 4 15:43:10 2011 KojiUpdateIOOclosed the shutter before the MC

The shutter before the MC was closed at 3:30 as I started working on the RFAM.

MC REFL (INLOCK): 0.6~0.7
MC REFL (UNLOCK): 6.9
MC TRANS: 50000~52000

  5617   Tue Oct 4 19:06:46 2011 KojiUpdateIOOclosed the shutter before the MC

Finished the work at 6:30

MC REFL (INLOCK): 0.50-0.52
MC REFL (UNLOCK): 6.9
MC TRANS: 54400~547000


RFAM level

Before the work: -48.5dBm for 1.07VDC (both 50Ohm terminated)

Right after the work: -80dBm for 0.896VDC (both 50Ohm terminated)
10min after:   -70dBm
1hour after:   -65dBm
3hours after: -62dBm
1day after (Oct 5, 20:00):    -62.5dBm
2days after (Oct 6, 23:20): -72.5dBm
3 days after (Oct 7, 21:00): -57.8dBm

Quote:

The shutter before the MC was closed at 3:30 as I started working on the RFAM.

MC REFL (INLOCK): 0.6~0.7
MC REFL (UNLOCK): 6.9
MC TRANS: 50000~52000

 

  5628   Fri Oct 7 11:45:24 2011 KojiSummaryLSCPOY11 installed, 55MHz PD at POY removed

POY11 PD was installed last night. The lock of the Y arm was confirmed with the POY11I signal.

- The DC transimpedance was modified to be 1010V/A as the incident power is tiny.

- The demodulation phase of the roughly adjusted (148deg) to have PDH signal at the I-phase.
 
The comparison with AS55I signal exhibits that POY11I have ~150 times weaker signal with 45dB whitening.
 
(In total 25000 times weaker.)

On the way to make POY11 functioning, there were many fixes at the LSC rack...


Details:

- The PD interface cards (power supply for the RFPDs) were checked:
So far the two card at the right hand side were checked. 

Desipite the previous entry reported the issues on those boards, they did not show any problem yesterday.

One hypothetical possibility is the enabling switches that is controlled from the old slow epics targets.

- POY55 was removed

This 55MHz PD is supposed to be installed at POP.
The PD, an RF cable, an RF amp, the power supply of the RF amp were removed.

- POY11 was installed

The PD was placed where the 55MHz was placed.

The beam was aligned on the diode using the IR viewer and the digital multimeter.

The power supply cable and the RF cable for POY on the ITMY table were used.

There were an ND filter on the POY beam path. It was removed.


- On the LSC rack
The PD RF was connected to the patch panel at the top of the rack.

There were loose connectors on the patch panel. Some connectors were tightened on the panel.

I found that POY11 and POX11 had I&Q signal reversely connected to the whitening board.
   ==> These were fixed but
require the orthogonality test again for those channels.



The I phase output of the AS11 demod board had a broken connector. 

The onboard SMA has got disintegrated because of too much twist on the connector.
The board was once removed from the rack and the connector was fixed using a heat gun and soldering.

The DC signals were checked. POYDC was not correctly connected. POYDC were correctly connected to the POYDC channel.

- CDS
c1lsc was found with the RFM frozen.
The c1lsc machine was soft-rebooted after stopping all of the RT processes.

Once the RT processes came back, they were all burtrestored.

- PDH locking
Restored Y-arm. Locked it with AS55Q.
Ran ASS alignment for Y-arm.
100cnt 150Hz sinusoidal signal is applied to ETMY

Measured the PSD of AS55Q, POY11I, and POY11Q.
Adjusted the demod phase so that the excitation could be minimized in POY11Q.


  5629   Fri Oct 7 11:53:47 2011 KojiUpdateLSCDRMI locked and some plans

- REFL165 PD to be fixed (shows constant high voltage at the DC out)

- Make POP22/110 PD

- Install AS11? or use it as POX11?

- Install POP55

  5634   Fri Oct 7 22:41:05 2011 KojiConfigurationGeneralScript backup fixed

Script backup regularly runs on op340m by crontab,
but the true backup were not taken since Oct 16, 2010
as the backup program was looking at the old script directory.
/cvs/cds/script/backupScripts.pl was modified to look at the new script directory.

OLD COMMAND:

$command = "cd /cvs/cds/caltech; /usr/sbin/tar cfX - $EXCLUDE_LIST scripts | bzip2 > $ARCHIVEDIR/scripts_$curdate.tar.bz2";

NEW COMMAND:

$command = "cd /opt/rtcds/caltech/c1; /usr/sbin/tar cfX - $EXCLUDE_LIST scripts | bzip2 > $ARCHIVEDIR/scripts_$curdate.tar.bz2";

  5640   Mon Oct 10 00:01:26 2011 KojiUpdateLSCFirst attempt to estimate mode matching efficiency using interferometer

"^2"s are missing in the second equation, but the calculation results seem correct.

PRX and PRY have different mode matching because of the Michelson asymmetry.
Are individually estimated mode matching indicates any sign of reasonable mode mismatch?
(The difference can be very small because the asymmetry is not so big.)

  5644   Mon Oct 10 15:41:56 2011 KojiUpdatePSLPMC aligned

[Koji Suresh]

The steering mirrors for PMC were aligned. The transmission went up from 0.779 to 0.852.

  5664   Thu Oct 13 23:58:38 2011 KojiUpdateLSCfixing REFL165

I already have reported in this entry that REFL165 shows too high DC output which does not depend on the light level on the diode.
Today I removed REFL165 from the table and inspected it.

The diode has been burnt as shown in the first picture (left).
The window is smoked, and the photo sensitive surface has been removed from its base. It moves in the can.

The burnt diode was replaced to the new one.
The new one shows ~30% better capacitance of ~50pF
and I had to increase the inductance from 14nH (i.e. 15nH//220nH) to 18nH.
After some struggles to increase/decrease the stray inductance by moving the SMD capacitors a little, the resonance is reasonably tuned to 166MHz.

The comprehensive test will be performed shortly.

  5671   Sat Oct 15 16:42:08 2011 KojiUpdateLSCTesting REFL165

Test results of new REFL165 (the first attachment)

- The resonant freq 166.2MHz, Q=57 (previous Q was ~7)

- If we believe the TF measurement, the transimpedance at the resonance is 7.8k [V/A] and the shotnoise intercept current of ~1mA.
The linearity of the peak was confirmed by changing the modulation level of the beam.

- There is a riddle: the white light test indicates 4.5k [V/A] and 2.8mA for those numbers.
There are big descrepancies from those by the TF measurements.


Further analysis of the descrepancies:

Using the noise measurements with different DC current levels, the transimpedance for each frequency can be reconstructed.

Does this indicate the satiration by the white light???

- The TF measurement shows consistent mag&phase relationship at the resonance (c.f. LISO fit).
So this steep resonance is not an artifact by a noise or glitch but the real structure of the electronics.

- The TF measurement has been done with the photocurrent of ~0.3mA, while the transimpedance measurement
with the white light illumination has the practical effect only when the DC photocurrent is larger than 1mA
because of the circuit noise. Does this higher photo current affected the resonance?

- The off-resonant transimpedance agree with the TF measurement as far as we can see with those measurements.
This may mean that the actual resonant structure has been affected in the white light measurement.
(i.e. not the saturation of the RF opamp which causes the change of the gain at any freq.)
Is the above mentioned higher DC current causing the change of the diode capacitance or other property of the diode or the inductors???

  5672   Sat Oct 15 17:06:20 2011 KojiUpdateLSCInstallation REFL165

REFL165 was installed on the AP table last night.

Meanwhile I found the DC power level at the REFL PDs were 0.8~1.2V if the PRM is aligned and the IFO is not locked.
This corresponds to 16~24mA (20~30mW). This is too big.

The HWP of the REFL path were adjusted so that we have 6~10mA (8~12mW) on each PDs.

  5678   Mon Oct 17 11:40:44 2011 KojiUpdateLSCREFL165 removed from the table

REFL165 removed from the table for the C(V) test

  5681   Mon Oct 17 22:20:42 2011 KojiUpdateLSCREFL165 removed from the table

Quote:

REFL165 removed from the table for the C(V) test

The PD was returned on the table.

The C(V) compensation path was modified and the change of the resonant freq was cancelled.
A more precise analysis comes later.

  5685   Tue Oct 18 10:04:41 2011 KojiUpdateLSCREFL165 removed from the table

The original REFL165 had ~50MHz/A dependence on the DC photocurrent.
The resistr R21, which was 2670 Ohm contrary to the original drawing, was replaced to 532 Ohm
to increase the feedforward gain by factor of 5.

The resulting dependence is reduced to ~0.5MHz/A although it has Q reduction of ~20% at 6mA.

Some concerns:

These transfer functions were measured between TEST IN and RF OUT while the diode was illuminated with the white light from a light bulb.

There looks some thermal effect on the resonant freq. If the white light illumination is suddenly removed, the bias compensation
is immediately removed but the resonance takes some time (~min) to come back to the original freq.

I am afraid that the light bulb gave too much heat on the surrounding PCB and lead unnecesarily high level dependence of the resonant freq on the DC current.

Or, if this thermal effect comes from the power consumption on the diode itself, we need to characterize it for aLIGO.

In order to check this, we need a test with the 1064nm illumination on the diode in stead of the light bulb.

  5703   Wed Oct 19 17:21:16 2011 KojiSummaryLSCModification on the RFPD interface cards

I have modified all of the three RFPD interface cards to be enabled permanently.
This prevents an accidental disabling caused by a stray voltage of the logic input (or whatever),
which was reported in multiple occasions by Anamaria and me.

The logic ICs (74LS04) for buffering of the EPICS switches were removed by 14pin sockets with additional wires soldered.
The modification shorts the inputs to the second logic chips, resulting in the permanent enabling of the PD circuit.

  5708   Thu Oct 20 01:40:33 2011 KojiSummarySUSMC2 Misaligned 2:27PM on Wednesday

There looks some activity at around MC2 on Wednesday afternoon.
It caused the misalignment of MC2. Misalignment was not found in MC1/3.

It seems that the incident beam on the MC was aligned in the evening.
This increased the MC transmission but it is vibible that the spot on MC2 is shifted from the center.

We need an action on this issue tomorrow in the daytime.

  5715   Thu Oct 20 18:42:47 2011 KojiUpdateComputer Scripts / ProgramsWhere should the "Update Snapshots" of screens live?

The following directory exists. We can apply this convention to all of the models.

/cvs/cds/rtcds/caltech/c1/medm/c1lsc/snap

Quote:

While trying to implement the regular yellow shell script button in MEDM for my new OAF screen, I noticed that the update snapshot stuff in all of the buttons that I checked (including IFO Align and LSC Overview) are pointing to folders in the old /cvs/cds/caltech/ area.  Also, I think some of the folders that it's looking for don't exist anymore, even in the old system.  So.  Has anyone thought about where the snapshots should live in the new world order?  Previously they were in ...../medm/c1/subsystem/ .  Maybe we should make a snapshots folder in each subsystem's medm folder, at the same level as the 'master' folder for the custom screens?  This is my current proposal.

Unless someone objects / has a better plan / knows why they're still pointing to the old place, I'll do this in the morning, and work on changing all the buttons to point to the new place.

 

  5745   Thu Oct 27 03:32:45 2011 KojiSummaryIOORFAM monitor progress

[Suresh, Mirko, Koji]

A cable from the stochmon box to the cross connect for the EPICS ADCs is installed.

The power supply and the signal outputs are concentrated in a single DSub 9pin connector
that is newly attached on the box.

The connection from the stochmon side of the cable and the EPICS value was confirmed.
The calibration of them looks fine.

To do:
- Once the stochmon box is completed we can immediately test it.
- The EPICS channel names are still as they were. We need to update the database file of c1iool0, the chans file for the slow channel.


The pinout is as following

-------------
| 1 2 3 4 5 |   Female / Inside View
\  6 7 8 9  /
 \---------/

1 - 11MHz Signal
2 - 30MHz Signal
3 - 55MHz Signal
4 - NC
5 - +5V supply
6 - 11MHz Return
7 - 30MHz Return
8 - 55MHz Return
9 - Supply ground

  5795   Thu Nov 3 15:14:22 2011 KojiUpdateCDSCSS/BOY installed on pianosa

How to run/use CSS/BOY

(PREPARATION)

0) Everything runs on pianosa for now.

1) type css to launch CSS IDE.

2) You may want to create your own project folder as generally everything happens below this folder.

=== How to make a new project ===
- Right-click on tree view of Navigator pane
- You are asked to select a wizard. Select "General -> Project". Click "Next".
- Type in an appropriate project name (like KOJI). Click "Finish"
- The actual location of the project is /home/controls/CSS-Workspaces/Default/KOJI/ in the above example

(PLAY WITH "Data Browser", THE STRIPTOOL ALTERNATIVE)

1) Select the menu "CSS -> Trends -> Data Browser". A new data browser window appears.

2) Right-click on the data browser window. Select the menu "Add PV". Type in the channel name (e.g. "C1:LSC-ASDC_OUT16")

3) Once the plot configuration is completed, it can be saved as a template. Select the menu "File -> Save" and put it in your project folder.

4) Everything else is relatively straightforward. You can add multiple channels. Log scaling is also available.
I still don't find how to split the vertical axis to make a stacked charts, but I don't surprise even if it is not available.
CSS_snapshot1.png

(HOW TO MAKE A NEW "BOY" SCREEN)

0) Simply to say BOY is the alternative of MEDM. The screen file of BOY is named as  "*.opi" similar to "*.adl" for MEDM.

1) To create a new opi file, right-click on the navigator tree and select the menu "New -> Other".

2) You are asked to select a wizard. Select "BOY -> OPI file" and click "Next".

3) Type in the name of the opi file. Also select the location of the file in the project tree. Click "Finish".

4) Now you are in OPI EDITOR. Place your widgets as you like.

5) To test the OPI screen, push the green round button at the top right. The short cut key is  "CTRL-G".
OPI_EDITOR.png

(HOW TO EDIT AN EXISTING OPI FILE)

1) Right click an OPI file in the navigator tree. Select the menu "Open WIth -> OPI Editor". That's it.

(HOW TO CONVERT AN EXISTING ADL FILE INTO OPI FILE)

1) You need to copy your ADL file into your project folder. In this example, it is /home/controls/CSS-Workspaces/Default/KOJI/

2) Once the ADL file is in the project folder, it should appear in the navigator tree. If not, right-click the navigator pane and select "Refresh".

3) Make sure "ADL Parser" button at the left top part is selected, although this has no essential function.
This button just changes the window layout and does nothing. But the ADL Tree View pane would be interesting to see.

3) If you select the ADL file by clicking it,the tree structure of the ADL file is automatically interpreted and appears in the ADL Tree View pane.
But it is just a display and does nothing.

4) Right-click the ADL file in the navigator pane. Now you can see the new menu "BOY". Select "BOY -> Convert ADL File to OPI".

5) Now you get the opi version of that file.
The conversion is not perfect as we can imagine. It works fine for the simple screens.
(e.g. matrix screens)
But the filter module screens get wierd. And the new LSC screen did not work properly (maybe too heavy?)
ADL2OPI1.png ADL2OPI2.png

(HOW TO RUN OUR SHELL/PERL/PYTHON SCRIPTS FROM BOY)

CSS has javascript/python scripting capability.
I suspect that we can make a wrapper to run external commands from python script although it is not obvious yet.

  5798   Thu Nov 3 17:04:23 2011 KojiUpdateGreen LockingSHG temperature (YARM)

Changing the crystal temperature changes the laser frequency. This will causes the beat note missing at the vertex.

In other words, you will find the beat note at the vertex when the actual temperature of the crystal is reproduced as before,
no matter how the dial setting/temp voltage input is.

  5804   Fri Nov 4 00:13:24 2011 KojiUpdateLSCXARM locked with POX11

XARM lock was achieved by POX11_I

Summary:

- The  whitening gains of POX11_I and Q are 42dB so that POX11_I have the same amplitude as AS55_I

- The demod phase of POX11 was adjusted to eliminate the PDH signal from the Q phase. The phase is  -100.5deg.

- In order to lock the XARM with POX11_I_ERR, I had to increase the trigger threshold from 0.1 to 0.2 as the arm was
kicked with the threshold of 0.1.


Method

- Lock the X arm with AS55_I at the XARM configuration.

- Adjusted POX11 demod phase so that POX11_Q is minimized.

- POX I&Q whitening gains were adjusted. When they are 42dB, POX11_I_ERR and AS55_I_ERR have almost the same signal amplitude.
(In reality, POX11_I_ERR has +1dB larger amplitude.)

- Adjusted POX11 demod phase again with better precision.

- Measured transfer function between AS55_I_ERR and POX11_I_ERR. As the sign was opposite, the demod phase was -180deg flipped.

- Tried to lock the arm with POX11_I_ERR. It did not acquire the lock. The arm looked kicked by the servo.

- Increased the trigger threshold from 0.1 to 0.2. Now the arm is locked with POX11_I_ERR.

  5821   Sat Nov 5 14:54:59 2011 KojiUpdateASCASS scripts gone

In any case, the daily backup of the scripts are found in /cvs/cds/caltech/scripts_archive

Quote:

Quote:

Did somebody delete all the scripts in /opt/rtcds/caltech/c1/scripts/ASS ?

 I have moved all the MC_ASS scripts to a directory called MC under ASS 

 

  5851   Wed Nov 9 16:29:36 2011 KojiSummaryLSCCharacterization of the Power Recycled Michelson

Difficult to understand.

The mode matching does not change the recycling gain. It changes the coupling of the incident light into the cavity.
It changes the reflected and accumulated power, but the recycling gain is not affected.

The recycling gain is determined by the optical configuration and the optical loss in the cavity.

In the actual measurement, of course, we should take both of the loss and the mode matching into account.
But this is the issue of the measurement method.

The essential questions are:
How much is the actual recycling gain? And how does it affect the signal extraction?

  5903   Wed Nov 16 02:36:35 2011 KojiUpdateelogrestarted

Basically, elog hangs up by the visit of googlebot.

Googlebot repeatedly tries to obtain all (!) of entries by specifying  "page0" and "mode=full".
Elogd seems not to have the way to block an access from the specified IP.
We might be able to use http-proxy via apache. (c.f. http://midas.psi.ch/elog/adminguide.html#secure)

Or can we tweak the source of elod such that it does not accept "page0"?


GET /40m/page0?mode=full&new_entries=1 HTTP/1.1
Host: 131.215.115.52:8080
Connection: Keep-alive
Accept: */*
From: googlebot(at)googlebot.com
User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Accept-Encoding: gzip,deflate

 

Quote:

Elog was hanging. Restarted it with script.

 

  5911   Wed Nov 16 12:21:33 2011 KojiUpdateeloggooglebot (Re: restarted)

- elogd itself is a sort of web server which has no freedom to put our own file, we can not put robots.txt

- If we include elog using proxy in the usual web tree of Apache, we can put robots.txt at the root.

- So far, if we prevent "page0" browse by google, we will be saved for a while.

- It seems that the indexing is set to be refused by the following meta tags. But it does not prohibit googlebot to use "page0" URL, of course.

<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
  5913   Wed Nov 16 17:03:19 2011 KojiUpdateIOOMC2 Shifted in Pitch, corrected by adjusting the pitch bias

MC was not locked for more than 5 hours because of the misalignment.

Noticed that MC2 WFS feedback filters had big outputs (particularly in Pitch).
They were reset to zero.

MC2 was aligned and recovered the lock. Once the WFS is engaged, the transmission returned to the uisual value.

  5916   Wed Nov 16 18:14:09 2011 KojiUpdateIOOMC unlocked and misaligned.

Actually, do we need to reset the filter history at every lock loss of the MC?

Those DC offsets were necessary to keep the alignment good just until the MC is unlocked.
So if we keep the history, we can maintain the good alignment.

  5923   Thu Nov 17 11:35:27 2011 KojiUpdateRF SystemStochmon?

The  Stochmon channels for 11&55MHz have been reasonably working since last night.

The output is not yet calibrated as the RF power detector has a strange scaling.
I am analyzing the calibration data.

  5931   Thu Nov 17 21:12:09 2011 KojiUpdatePSLHEPA setting changed

[Koji, Suresh]

8:50PM HEPA@100% for the test

8:55PM HEPA@0%

9:20-35PM HEPA level varies from 0%-50%

9:35PM HEPA@40% and left it running at this level

Nov18 1:40 AM HEPA@80% for a work around the PSL table (by KI)

Nov18 4:35 AM HEPA@40% (by KI)

  5941   Fri Nov 18 01:51:37 2011 KojiUpdateIOOStochmon update

Update of the stochmon status

[Attachment 1: Circuit diagram]

- The new stochmon has a low noise amplifier (MAR-6SM) inside.
The RFAM signal from the PD has the power of -60~-50dBm, which is almost at the bottom of the sensitivity for the power detector.

- The band pass filters were doubled.

- I've suffered from some RF coupling from the power line as the power detector is quite sensitive to it.
The situation has been largely improved by the EMI filters in the power supply path, although the problem is still present.
The worst remaining problem is that we can not close the aluminum lid as it cause a huge sprious coupling.

 

[Attachment 2: Calibration result]

- The outputs were calibarted with Marconi. They showed the signals linear to dBm for the input powers between -70dBm and -10dBm.

- The calibration result was fitted with the empirical fit function. The function and the results are shown in the attachment.

[Attachment 3: Detection limit]

- The attached figure shows the power spectrum of the PD output. This measurement gives us the amount of the RF power given from the PD noise when there is no RF signal.

11MHz out passband noise: −72.7dBm ===> V11 = 2.0483
30MHz out passband noise: −64.6dBm ===> V30 = 1.9333
55MHz out passband noise: −71.2dBm ===> V55 = 2.0272

- Now 11MHz and 55MHz outputs seem indicating the power correctly, but the 29.5MHz output never provides useful information.
It is a constant value independent from the state of the incident beam. Strangely this problem disappears if the marconi is used
for the RF source. Thus this issue is not seen in the calibration measurement.

- So far, 11MHz, 29.5MHz, 55MHz, and DC outputs appear in the channels C1:IOO-RFAMPD_33MHZ, C1:IOO-RFAMPD_133MHZ, C1:IOO-RFAMPD_166MHZ, and C1:IOO-RFAMPD_199MHZ.
They will be renamed.

  5972   Mon Nov 21 17:48:36 2011 KojiUpdateIOORFAM monitoring test

Do we care about the AC? I thought what we care is the DC.

  5991   Wed Nov 23 18:28:09 2011 KojiUpdateIOORFAMPD channels / EOM monitor channels added to DAQ

The following channels have been registered in c1iool0 database, and are now recorded by FB

C1:IOO-RFAMPD_11MHZ
C1:IOO-RFAMPD_29_5MHZ
C1:IOO-RFAMPD_55MHZ
C1:IOO-RFAMPD_DCMON
C1:IOO-EOM_TEMPMON
C1:IOO-EOM_HEATER_DRIVEMON


PROCEDURE

1) The EPICS database file has been edited to rename/add some channels

/cvs/cds/caltech/target/c1iool0/ioo.db

REMOVED
#grecord(ao,"C1:IOO-RFAMPD_VC")
#grecord(ai,"C1:IOO-RFAMPD_TEMP")
#grecord(ai,"C1:IOO-RFAMPD_DCMON")
#grecord(bo,"C1:IOO-RFAMPD_BIAS_ENABLE")
#grecord(bi,"C1:IOO-RFAMPD_BIAS_STATUS")
#grecord(calc, "C1:IOO-RFAMPD_33MHZ_CAL")
#grecord(calc, "C1:IOO-RFAMPD_133MHZ_CAL")
#grecord(calc, "C1:IOO-RFAMPD_166MHZ_CAL")
#grecord(calc, "C1:IOO-RFAMPD_199MHZ_CAL")

ADDED/EDITED
grecord(ai,"C1:IOO-RFAMPD_11MHZ")
        field(DTYP,"VMIVME-3113")                                              
        field(INP,"#C1 S25 @")
...

grecord(ai,"C1:IOO-RFAMPD_29_5MHZ")
        field(DTYP,"VMIVME-3113")                                              
        field(INP,"#C1 S26 @")

...
grecord(ai,"C1:IOO-RFAMPD_55MHZ")
        field(DTYP,"VMIVME-3113")                                              
        field(INP,"#C1 S27 @")

...
grecord(ai,"C1:IOO-RFAMPD_DCMON")
        field(DTYP,"VMIVME-3113")                                              
        field(INP,"#C1 S28 @")

...
grecord(ai,"C1:IOO-EOM_TEMPMON")
                                                
        field(DTYP,"VMIVME-3113")                                               
        field(INP,"#C1 S29 @")

...
grecord(ai,"C1:IOO-EOM_HEATER_DRIVEMON")

        field(DTYP,"VMIVME-3113")                                              
        field(INP,"#C1 S30 @")

2) The channels have been added to the frame builder database

/cvs/cds/rtcds/caltech/c1/chans/daq/C0EDCU.ini

[C1:IOO-RFAMPD_11MHZ]
[C1:IOO-RFAMPD_29_5MHZ]
[C1:IOO-RFAMPD_55MHZ]
[C1:IOO-RFAMPD_DCMON]
[C1:IOO-EOM_TEMPMON]
[C1:IOO-EOM_HEATER_DRIVEMON]

Note that this C0EDCU.ini is the file that has been registered in

/cvs/cds/rtcds/caltech/c1/target/fb/master

3) burt restore request files were updated

RFAM related settings were removed as they don't exist anymore.

/cvs/cds/caltech/target/c1iool0/autoBurt.req
/cvs/cds/caltech/target/c1iool0/
saverestore.req

4) c1iool0 were rebooted. Framebuilder restarted. c1iool0 were burtrestored.

  5992   Wed Nov 23 22:58:33 2011 KojiUpdateGeneralc1iscaux2 is back (re: recovery from the power shutdown)

Keying again did not help to solve the issue. I turned off the power at the back of the crate, and turn it on again.
Then the key worked again.

c1iscaux2 is burtrestored and running fine now.

Quote:

 - One of the VME rack on 1X3 is not showing the +/-15V green LED lights.

   This is the one on very upper side of the rack, which contains the old c1lsc machine and c1iscaux2. If we are still using c1iscaux2, it needs to be fixed.

 

  5994   Thu Nov 24 02:23:43 2011 KojiSummaryGeneralGPIB<->WIFI

GPIB<->WIFI on Agilent Network Analyzer 4395A was broken.
The connection was fixed by replacing and configuring the LINKSYS bridge.

=======

Kiwamu and I have identified that the LINKSYS bridge was guilty.

I knew that we had another one in the bathroom, I configured it.

HOW TO CONFIGURE IT

  • You need a host with 192.168.1.*.
  • Connect the host and the LINKSYS directly
  • Open http://192.168.1.226/
  • Select 40MARS and infrastructure mode
  • Register it in the MAC filter of the 40MARS (see wiki and use your head)

The new unit works fine.

I checked the malfunctioning unit and the configuration was the same as the others.

The bad one detected the existence of 40MARS during the configuration, but it does not establish
the connection in the actual use. I am afraid that something is broken or some setting is lost
during the power supply shutdown.

  5995   Thu Nov 24 05:10:00 2011 KojiUpdateIOORFAMPD channels / EOM monitor channels added to DAQ

EOM TEMPMON and HEATER DRIVEMON have been hooked up to the following channels.

C1:IOO-EOM_TEMPMON
C1:IOO-EOM_HEATER_DRIVEMON 

What a fragile circuit...

I found some of the resistors popped up from the board because of the tension by the Pomona grabbers.
I tried to fix it based on the schematic (photo) and the board photo.

  5996   Thu Nov 24 05:47:16 2011 KojiSummaryIOOStochmon running

Now stochmon for 11MHz and 55MHz is running. The calibration / noise measurement are going to be post later...

  5999   Thu Nov 24 13:54:31 2011 KojiUpdateIOORFAMPD channels / EOM monitor channels added to DAQ

Those clips for the readouts were the ones who popped out.
When I have restored the connections, I checked the schematic and the heater drive mon is clipped on the output side of the OP27.

Quote:

Jenne: The point you indicate for the heater monitor is a virtual ground--it will be driven to zero by the circuit if it's functioning properly; the readout should be done at the input pin (2, I think) to the BUF634.

Koji: This is odd, as I made a point of not attaching any clips directly to resistors for exactly this reason. I was also careful to trim resistor/capacitor leads so that they were not towering over the breadboard and prone to bending (with the exception of the gain-setting resistor of the AD620, which was changed at the last minute). At the end of the day, it is a breadboard circuit with Pomona "readout", so it's not going to be truly resilient until I put it on a protoboard. Another thing: I think the small Pomona clips are absolutely terrible, since they slip off with piconewtons of tension; I could not find any more regular clips, so I used them against my better judgment. 

 

  6000   Thu Nov 24 14:05:10 2011 KojiUpdatePSLHEPA@50%

I left the HEPA at the 50% level @5AM, Nov 24

  6001   Thu Nov 24 14:42:57 2011 KojiUpdateelogelogd gained an immunity to googlebot

I modified elogd.c as shown below in order not to allow to display all of the entries at once by specifying page number "0".

After this modification, elog seems to have survived 66 times of attacks by googlebots.

==============================

rossa:src>pwd
/cvs/cds/caltech/elog/elog-2.8.0/src

rossa:src>diff elogd.c_orig elogd.c
19912a19913,19917
>
>    /* KA */
>    if (page_n<1)
>      page_n = 1;
>

  6009   Fri Nov 25 20:03:05 2011 KojiUpdateIOOStochmon update

 New RFAM mon calibration

  6023   Mon Nov 28 14:40:43 2011 KojiUpdateRF SystemEOM temp driver

Quote:

Here is 5 days of trend of the EOM temp sensor and the heater driver monitor.  Unfortunately, it looks like we're regularly railing the heater.  Not so awesome. 

Can you zoom the temp mon? (V= -0.1 ~ +0.1)
The crystal was too cold and I tried to heat the PSL table by the lighting. But it seemed in vain.

  6086   Thu Dec 8 00:45:13 2011 KojiUpdateRF System4ch demod is ready

I have tested the left 2ch of 4ch demod board.

The left most is for 11MHz, and the next one is for the 55MHz.

  6092   Thu Dec 8 22:44:55 2011 KojiUpdateRF System4ch demod test result

1) Linearity Test

LO input level was +10dBm. The LO freq was 11MHz and 55MHz for CH1 and CH2 respectively.
The IF frequency was fixed at 10kHz.

The amplitude of the RF input was swept from -50dBm to +15dBm.
Basically I and Q output of CH1 and CH2 was quite linear in this amplitude range.

2) Freqency Response

RF input was fixed at -20dBm and the IF frequency was swept from 1kHz to 1MHz.

The response was flat upto 100kHz, and have sensitivity upto 300kHz.

3) Output noise

Noise floor of the output is ~20nV/rtHz. All of the channels behave in the same way.
1/f start from 100Hz.

  6099   Fri Dec 9 17:44:45 2011 KojiUpdateRF SystemLots of current used in Rich's demod box

Those asymmetric currents are same as what I saw with the table top +/-18V supply. If you really don't like it, there could be an option to disconnect CH3/4 in the box.

In any case, this could be a good long-run test of the demod box, couldn't it?

Quote:

I checked the power regulators on the Rich demod box (according to the schematic, D1000217).  The positive one is LM2941CT, and the negative one is LM2991T.  Both accept input voltage up to +26V or -26V respectively.  So my use of +\- 24V to be regulated down to +\- 15V isn't too crazy.  It's a little crazy, but not too crazy.  They recommend having only a 3V difference between the input and output voltages.  We don't have any 18V or 20V power supplies in the regular LSC power supply rack, so Rana suggested using the 24's. 

When I plug in and turn on the Rich box, the current on the +24V power supply goes up by about 0.8A, and the -24V supply goes up by about 0.3A.  That seems like kind of a lot.  Is that too much?  Do I need to find a better plan that involves +\- 18V?  Thoughts?

For now, the Rich box is off, just in case.

 

  6115   Wed Dec 14 01:35:06 2011 KojiUpdateIOOMC alignment craziness

~11PM I came to the 40m and found the MC is repeating "LOCK->WFS ON->UNLOCK" sequence for ~2hours.

I checked the WFS spots on the QPDs and aligned them. No luck. I suspected the clipping of the beam in the chamber.

After I checked the trends of MC SUS OSEM values and IPPOS, I concluded that the input beam was aligned to somewhat misaligned MC.

The most noticable thing was that IPPOS (X, Y) indicated about (-0.5, 0) although the recent trend shows (-1, -0.5) is nominal.
In fact, the beam was about dropping from the diode. In addition, I found that the MC2 suspension showed a jump in the morning at around 8.30AM.|
This is consistent with what Jenne described.

This was a difficult situation as everything was moved.
I used the OSEM values to come back to the previous alignment of the suspensions, and started touching Zig-Zag before the MC.
After the alignment I ended up more clipping of the MC REFL. Also the spot on the IPPOS QPD was more dropping.

So, I have empirically used MC3 to misalign in Yaw to have better spot position on IPPOS. Then, the Zig Zag was aligned.
Then the spot on MC2 was adjusted while MCTRANS was kept maximized.

This helped the things back in the normal state.

Now the WFS servo is happily controlling the alignment.
MC REFL is 4.8 and 0.47 for unlocked and locked. (MCREFL_UNLOCK was 4.6 before my touch)
MCTRANS is 27000, which is close to the nominal.
IPPOS total, x, and y are 0.36, -0.97, and -0.47, respectively. They are about the nominal.

~1AM done

HOWEVER, we still don't know the position of the spot on MC1/MC3, and ITMY and ETMY.
I should consult with Kiwamu to check the spot positions tomorrow.

General lessons:
- If you find any reduction of MC transmission, check the suspensions to see if there is any slip.
- Before touching the input optics to recover the MC alignment, we should think what was moved.
- Before touching EOM alignment you must check the MC alignment WITHOUT WFS, so that you can recover the misalignment of EOM by the Zig-Zag steering.
- WFS is sensitive to clipping of the beam.
- We need a nifty indicator to tell how the MC transmitted beam is good.

  6118   Wed Dec 14 14:07:48 2011 KojiUpdateIOOMC alignment craziness

[Kiwamu Koji]

To check if the MC alignment is OK or not, we tried to lock the Y-arm.

Once the alignment of Y-arm was restored, we saw the resonant peak of ~0.2 in TRY.
After a small tweak of PZT2, TRY has got improved up to 0.7.

Kiwamu made a small tweak on the problematic PZT1, then the full (1.0) TRY was recovered.

Thus we concluded the current MC alignment is good enough.

  6128   Sat Dec 17 01:56:16 2011 KojiSummarySUSHysteresis test

[Koji Kiwamu]

We wonder if the flakiness of MC2 comes from the suspension or not.

To test it, we are shaking all of the suspension biases +/-1.0 with a script.

The script is here:
/users/koji/111216/SUS_hysteresis.sh

For this test, we closed the mechanical shutter before the MC.

Also some amount of misalignment is anticipated.
Don't be surprised if you see nothing is working when you come to the lab in the weekend.

 

 -- EDIT by KI:
I found the ITMY watchdogs tripped around 2:40 AM and then re-engaged it.
  6131   Sat Dec 17 12:41:46 2011 KojiUpdateSUSAborted Hysteresis test

The test was from: 2011-12-17 09:48 to 11:49 (UTC).
This corresponds to the period from 2011-12-17 01:48 to 3:49 (PST).

ZK: Thanks

ELOG V3.1.3-