Also, Kiwamu has modified the layout drawing to add the green PLL stuff. This has collapsed the reference cavity's wave function placing it close to its original position.

WE (maybe Valera and Steve) can now put the reference cavity back on the table.

I put some green stuff on the layout drawing.

I continue to refine the positions of these stuff.

Notes :

 1. I flipped the reference cavity. So now the cavity is sitting on the left hand side of the layout.

  2. I removed the ISS stuf. We should think about where ISS should be.

I updated parse_mdl_to_ipc.py to correctly work with the 3 new cdsIPCx parts, namely cdsIPCx_PCIE (for dolphin connections), cdsIPCx_RFM (for our traditional reflected memory connections), and cdsIPCx_SHMEM (local shared memory on the computer).  These parts replaced cdsIPCx awhile back (see here ).

The code now correctly counts each type independantly with regards to ipcNum (I.e. you can have ipcNum = 0 for RFM and ipcNum = 0 for SHMEM for example).

I also went in and modified a few sections of the feCodeGen.pl (in /opt/rtcds/caltech/c1/core/advLigoRTS/src/epics/util/) so as to properly assign names to matrix adl files, matrix of filter bank adl files, and filter bank adl files.

I played with the particle counter this morning. Now it's running and reading the correct numbers on the old COCHECKLIST.adl medm screen.

However, it can not be seen with dataviewer.

Koji just rebooted the frame builder and the problem was solved.

 I started mode matching of the beam going to IMC. The work is still going on.

According to Rana's calculation (see here), I put the first lens (f=200mm) in between two steering mirrors after PMC.

The distance from PMC to the first lens was adjusted by using a metal ruler.  So I believe the accuracy is something like 1mm.

I aligned the beam path going through the broadband EOM and the mode matching lenses.

  I could find the optimum position for the second lens  (f=-150mm) by sliding the position of the lens and measuring the mode after it.

But the optimum position looked a bit far from the EOM. It's off by about 3-4 inch from the designed position.

Somehow I feel that the beam before the second lens goes with a smaller divergence angle than that of designed.

So tomorrow I am going to restart the work from checking the mode before the second lens.

Maybe at first I should measure the mode without going through the EOM because it changes the waist position and makes the system not straightforward.

Innolight 2W 1064nm main laser was turned off for more enclosure related work.

The electrician re rooting the power- conduit to the interlock under the floor and bring it through the new concrete tunnel.

Emergency laser power shut off switch was tested at entry door 104M.  It worked fine.

No laser glasses required. Laser will be turned back on around 11 am today.

Atm1,   AC power line to enclosure and interlock  was extended.

Atm2,   24V line to interlock rerouted

Atm3,   job is completed

SAFETY GLASSES REQUIRED !  SAFETY GLASSES REQUIRED!

 The laser is turned on. Injection current set to 0.871A.

Actually some one turned the  laser  off last night and did  not enter it into the elog ! Burned toast award is granted !

Please  come forward voluntarily.

I turned off/on the power to the accelerometers in order to re rout their connections. I found cable connector body-nut  #3 loose to Accelerometer 2X This connector should be checked for solid performance.

I measured the amplitude noise of the source outputs and the EOM outputs of the Frequency Generation box.

the setup I used is shown in this diagram:

(NB It's important that the cables from the splitter to the RF and LO inputs of the mixers are the same length).

The results of the measurements are shown in the following plot:

Considerations:

1) both Crystals (29.5MHz and 11MHz) have the same noise

2) the 55MHz source's noise is bigger than the 11 MHz (~2x): the frequency multiplication and amplification that happen before it, add extra noise

3) the noise at EOM outputs is ~2x bigger than that of the relative sources

When I have the chance, I'll plot the results of my calculations of expected noise and compare them with the measurements.

I've been working on updating the suspensions model, incorporating Koji's refinements as well as trying to simplify the model and making it less cluttered. 

This had the side benefit of making an incorrect connection obvious.  I had incorrectly wired the ASCPIT input to be summed into the yaw path, and the ASCYAW input into the pitch path.  This has been corrected.

I've finished a single optic, and now I am in the process of propagating the changes to all the optics, as well as cleaning up the overall diagram using Rolf's new tags, which make things much less cluttered.  I've attached a screenshot of the PRM optic control model, and will be updating the Matlab web export once I've updated the full model.

I turned off the laser last night to protect against the electricians. but failed to elog it. I accept the burnt toast completely.

- The PMC REFL PD was moved from the temporary location to the one called for by the PSL layout (picture attached). The leakage beams were dumped.

- The FSS reference cavity was aligned using temporary periscope and scanned using NPRO temperature sweep. The amplitude of the sweep (sine wave 0.03 Hz) was set such that the PMC control voltage was going about 100 V p-p with. With rough alignment the visibility was as high as 50% - it will be better when the cavity is locked and better aligned but not better than 80% expected from the mode astigmatism that Tara and I measured on Thursday. The astigmatism appear to come from the FSS AOM as it depends on the AOM drive. We reduced the drive control voltage from 5 V to 4V beyond that the diffraction efficiency went below 50%. The FSS REFL PD was set up for this measurement as shown in the attached picture. There is also a camera in transmission not shown in the picture.

Kiwamu and I found that the first lens in the PMC mode matching telescope was mislabeled. It is supposed to be PLCX-25.4-77.3-C and was labeled as such but in fact it was PLCX-25.4-103.0-C. This is why the PMC mode matching was bad. We swapped the lens for the correct one and got the PMC visibility of 82%. The attached plot shows the beam scans before and after the PMC. The data were taken with the wrong lens. The ABCD model shown in the plot uses the lens that was there at the time - PLCX-25.4-103.0-C. The model for the PMC is just the waist of 0.371 mm at the nominal location. The snap shot of the ABCD file is attached. The calculation includes the KTP for FI and LiNb for EOM with 4 cm length. The distances are as measured on the table.

The attached plot shows the beam scans of the beam leaking from the back mirror of the PMC to the BS cube that first turns the S-pol beam 90 deg to the AOM and then transmits the AOM double passed and polarization rotated P-pol beam to the reference cavity. The beam from the PMC is mode matched to the AOM using a single lens f=229 mm. The ABCD file is attached. The data were taken with VCO control voltage at 5 V. We then reduced the voltage to 4 V to reduce the astigmatism. Tara has the data for the beam scan in this configuration in his notebook.

The beam from AOM is mode matched to the reference cavity using a single lens f=286.5 mm. The ABCD file is attached.

I measured the RF power output of the VCO Driver box as a function of slider value. I measured using the Gigatronics Handheld power meter and connected to the AOM side of the cable after the white Pasternak DC block.

* at low power levels, I believe the waveform is too crappy to get an accurate reading - that's probably why it looks non-monotonic.

* the meter has a sticker label on it saying 'max +20 dBm'. I went above +20 dBm, but I wonder if maybe the thing isn't linear up there...

I've started a wiki page under the Upgrade 09/New CDS section regarding known bugs and pending feature requests for the Real Time Code Generator.   It can be found at http://lhocds.ligo-wa.caltech.edu:8000/40m/Bugs_and_Pending_Feature_requests_for_the_RCG.  If you have any ideas to improve the RCG or encounter a bug in the code generation process (say a particular part doesn't work inside subsystems for example), please note them here.

Currently there are bugs with excitation points (they don't work inside of a subsystem block) and tags (they don't respect scope and only 1 "from" tag for each "goto" tag connected to the output of a subsystem block).

I uploaded all the material about the RF frequency Generation Box into the SVN under the path:

https://nodus.ligo.caltech.edu:30889/svn/trunk/docs/upgrade08/RFsystem/frequencyGenerationBox/

I structured the directory as shown in this tree:

I'm quickly describing in a section of the Rf system upgrade document with LIGO # T1000461.

I have been working on the mode matching lenses which are sitting after the boradband EOM.

Last Friday I checked the mode profile after the first mode matching lens (f=-150mm). The measured mode was good.

According to the calculation done by ABCD software, the waist size is supposed to be 80.9 um after that lens.

The measured waists are 80.5 um for the vertical mode and 79.4 um for the horizontal mode.

The screenshot of the ABCD's result and the plot for the mode measurement are shown below.

I didn't  carefully check the mode after the last convex lens (f=200mm), but it must be already good because the beam looks having a long rayleigh range.

Now the beam is reflected back from MC1 and goes to the AP table since I coarsely aligned the beam axis to the MC.

/****  fitting result ****/

w0_v =  80.4615      +/- 0.1695 [um] 

w0_h =  79.4468      +/- 0.1889 [um]

z_v =  -0.115234        +/- 0.0005206  [m]

z_h =  -0.109722        +/- 0.0005753 [m]

The IR sensitive Olympus 570 camera gives us a really nice view of these IR beams. Its actually a lot better than what you can get with the analog IR viewers:

PSLAOMdogs

 I turned ON the laser at the X end station, which had been OFF for several weeks because of the crane business.

Now the green beam hits the ITMX and I got a reflection back to the end table.   

This green beam will be a nice reference when we install the green periscope in the chamber.

If it's necessary, feel free to correct the alignment of the green beam during my absence.

I completed a LIGO document describing design, construction and characterization of the RF System for the 40m upgrade.

It is available on the SVN under https://nodus.ligo.caltech.edu:30889/svn/trunk/docs/upgrade08/RFsystem/RFsystemDocument/

It can also be found on the 40m wiki (http://lhocds.ligo-wa.caltech.edu:8000/40m/Upgrade_09/RF_System#preview), and DCC under the number T1000461.

- connected the TTFSS cables (FSS fast goes directly to NPRO PZT for now)

- measured the reference cavity 21.5 MHz EOM drive to be 17.8 dBm

-  turned on the HV for the FSS phase correcting EOM (aka PC) drive

- connected and turned on the reference cavity temperature stabilization

- connected the RefCav TRANS PD

- fine tuned the RefCav REFL PD angle

The RefCav is locked and aligned. I changed the fast gain sign by changing the jumper setting on the TTFSS board. The RefCav visibility is 70%. The FSS loop ugf is about 80 kHz (plot attached. there is 10 dB gain in the test point path. this is why the ugf is at 10 dB when measured using in1 and in2 spigots on the front of the board.)  with FSS common gain max out at 30 dB. There is about 250 mW coming out of the laser and 1 mW going to RefCav out of the back of the PMC. So the ugf can be made higher at full power. I have not made any changes to account for the PMC pole (the FSS is after the PMC now). The FSS fast gain was also maxed out at 30 dB to account for the factor of 5 smaller PZT actuation coefficient - it used to be 16 dB according to the (previous) snap shot. The RefCav TRANS PD and camera are aligned. I tuned up the phase of the error signal by putting cables in the LO and PD paths. The maximum response of the mixer output to the fast actuator sweep of the fringe was with about 2 feet of extra cable in the PD leg.

I am leaving the FSS unlocked for the night in case it will start oscillating as the phase margin is not good at this ugf.

Brilliant! This is the VERY way how the things are to be conquered!

We removed the Lightwave MOPA Controller from 1X1 (south)  It was a real painfully messy job to pull out the umbilical.

Note: the umbilical is shading it plastic cover. It is functional but it has to be taken out side and cleaned. Do not remove it from it's plastic bag in a clean environment.

Now Joe has room for IOO chassy  in this rack.

We also removed the Minco temp controller and ref. cavity ion pump power supply.

We removed the Lightwave MOPA Controller, PA#102, NPRO206 power supply to make room for the IOO chassy at 1X1 (south) rack.

The umbilical cord was a real pain to take out. It is shading its plastic cover. The unused Minco was disconnected and removed.

The ref. cavity ion pump controller- power supply was temporarily taken out also.

The attached plots show the PMC cavity line width measurement with 1 mW and 160 mW into the PMC. The two curves on each plot are the PMC transmitted power and the ramp of the fast input of the NPRO. The two measurements are consistent within errors - a few %. The PMC line width  3.5 ms (FWHM) x 4 V / 20 ms (slope of the ramp) x 1.1 MHz / V (NPRO fast actuator calibration from Innolight spec sheet) = 0.77 MHz.

Here is the output of the calculation using Malik Rakhmanov code:

modematching =  8.4121e-01

transmission1 =   2.4341e-03

transmission2 =   2.4341e-03

transmission3 =   5.1280e-05

averageLosses =  6.1963e-04

visibility =  7.7439e-01

Two SOS suspensions for the ETMs were disassembled and packed for cleaning and baking by Bob.

These suspensions have been stored on the X end flow bench long years, and looked quite old.

They have some differences to the modern SOSs.

- The top suspension block is made of aluminum and had dog clamps to fix the wires.
- The side bars are not symmetric: the side OSEM can only be fixed at the right bar (left side in the picture).
- EQ stops were made of Viton.
- One of the tower bases seems to have finger prints (of Mike Zucker?).

I found that the OSEM plates had no play. We know that the arrangement of the OSEMs gets quite difficult
in this situation. Therefore the holes of the screws were drilled with the larger drill.

We decided to replace all of the screws to the new ones as all of the screws are Ag plated and got corroded
by silver sulfide (Ag₂S). I checked our stock in the clean room. We have enough screws.

Important note: Use stainless screws in aluminum / Silver-plated screws in stainless
There exists some study about galling: LIGO-G020394-00-D

The day before yesterday, I was cleaning a flow bench in the clean room.

I found that one SOS was standing there. It is the SRM suspension.

I thought of the nice idea:

- The installed PRM is actually the SRM (SRMU04). It is 2nd best SRM but not so diiferent form the best one.
==> Use this as the final SRM

- The SRM tower at the clean room
==> Use this as the final PRM tower.
==> The mirror (SRMU03) will be stored in a cabinet.

- The two SOS towers will be baked soon
==> Use them for the ETMs

This reduces the unnecessary maneuver of the suspension towers.

In doing a re-inventory prior to the IOO chassis installation, I re-discovered we had a missing interface board that goes in an IO chassis.  This board connects the chassis to the computer and lets them talk to each other.  After going to Downs we remembered Alex had taken a possibly broken interface board back to downs for testing. 

Apparently the results of that testing was it was broken.  This was about 2.5 months ago and unfortunately it hadn't been sent back for repairs or a replacement ordered.  Its my fault for not following up on that sooner.

I asked Rolf what the plan for the broken one was.  His response was  they were planning on repairing it, and that he'd have it sent back for repairs today.  My guess the turn around time for that is on the order of 3-4 weeks (based on conversations with Gary), however it could be longer.  This will affect when the last IO chassis (LSC) can be made fully functional.  I did however pickup the 100 foot fiber cable for going between the LSC chassis and the LSC computer (which will be located in 1X3).

As a general piece of information, according to Gary the latest part number for these cards is OSS-SHB-ELB-x4/x8-2.0 and they cost 936 dollars (latest quote).

I took the 5565 RFM card out of the IOVME machine to so I could put it in the new IO chassis that will be replacing it.  It is no longer on the RFM network.  This doesn't affect the slow channels associated with the auxilliary crate.

Cleaned up cables on the top and bottom. Vacuumed both areas. We still have some remaining shading from the MOPA umbilical and more unknown BNC cables hanging around.

I talked to with Alex this morning, discussing what he needed to do to have a frame builder running that was compatible with the new front ends.

1) We need a heavy duty router as a separate network dedicated to data acquisition running between the front ends and the frame builder.  Alex says they have one over at downs, although a new one may need to be ordered to replace that one.

2) The frame builder is a linux machine (basically we stop using the Sun fb40m and start using the linux fb40m2 directly.).

3) He is currently working on the code today.  Depending on progress today, it might be installable tomorrow.

[Rana, Koji, Joe]

We pulled the phase shifters in the 1X2 rack out to make room for megatron.  Megatron will be converted into c1ioo, and the 8 core, 1U computer will be used as c1lsc.  A temporary ethernet cable was run from 1X2 to 1X3 to connect megatron to the same sub-network.

The c1lsc machine was worked on today, setting it up to run the real time code, along with the correct controls accounts, passwords, .cshrc files, etc.  It needs to be moved from 1X1 to 1X4 tomorrow.

I've made a first pass at a rack diagram for the 1X1 and 1X2 racks, attached as png.

Gray is old existing boards, power supplies etc.  Blue is new CDS computers and IO chassis, and gold is for the Alberto's new RF electronics.  I still need to double check on whether some of these boards will be coming out (perhaps the 2U FSS ref board?).

[Aidan, Tara, Joe]

We pulled out what used to be the LSC/ASC fiber from the 1Y3 arm rack, and then redirected it to the 1X1 rack.  This will be used as the c1ioo 1PPS timing signal.  So c1ioo is using the old c1iovme fiber for RFM communications back to the bypass switch, and the old LSC fiber for 1PPS.

The c1sus machine will be using the former sosvme fiber for communications to the RFM bypass switch.  It already had a 1 PPS timing fiber.

The c1iscex machine had a new timing fiber already put in, and will be using the c1iscey vme crate's RFM for communication.

We still need to pull up the extra blue fiber which was used to connect c1iscex directly to c1sus, and reuse it as the 1PPS signal to the new front end on the Y arm. 

Alex has said he'll come in tomorrow morning to install the new FB code.

Alex came over this morning and we began work on the frame builder change over.  This required fb40m be brought down and disconnected from the RAID array, so the frame builder is not available.

He brought a Netgear switch which we've installed at the top of the 1X7 rack.  This will eventually be connected, via Cat 6 cable, to all the front ends.  It is connected to the new fb machine via a 10G fiber.

Alex has gone back to Downs to pickup a Symmetricon (sp?) card for getting timing information into the frame builder.  He will also be bringing back a harddrive with the necessary framebuilder software to be copied onto the new fb machine.

He said he'd like to also put a Gentoo boot server on the machine.  This boot server will not affect anything at the moment, but its apparently the style the sites are moving towards.  So you have a single boot server, and diskless front end computers, running Gentoo.  However for the moment we are sticking with our current Centos real time kernel (which is still compatible with the new frame builder code).  However this would make a switch over to the new system possible in the future.

At the moment, the RAID array is doing a file system check, and is going slowly while it checks terabytes of data.  We will continue work after lunch. 

 Punchline: things still don't work.

We found that a transistor was broken from yesterday spark too. We partially fixed TTFSS, and it should be enough for  testing purpose.

From yesterday test, we found that the RF amplifier for LO signal was broken. There was no spare at the electronic shop at Downs,

so we shorted the circuit for now.  Another part which was broken too was a transistor, Q3 PZT2222A, on D0901846.

It was removed and two connections, which are for Q3's 1 and 3 legs, are shorted. Now the voltages out from the regulators are back to normal.

We are checking a MAX333A switch, U6A on D0901894. it seems that the voltage that controls the switch disappears.

There might be a bad connection somewhere. This will be investigated next.

To startup medm screens for the new suspension front end, do the following:

1) From a control room machine, log into megatron

ssh -X megatron

2) Move to the new medm directory, and more specifically the master sub-directory

cd /opt/rtcds/caltech/c1/medm/master/

3) Run the basic sitemap in that directory

medm -x sitemap.adl

The new matrix of filters replacing the old ULPOS, URPOS, etc type filters is now on the screens.  This was previously hidden.  I also added the sensor input matrix entry for the side sensor.

Lastly, the C1SUS.txt filter bank was updated to place the old ULPOS type filters into the correct matrix filter bank.

The suspension controls still need all the correct values entered into the matrix entries (along with gains for the matrix of filter banks), as well as the filters turned on.  I hope to have some time tomorrow morning to do this, which basically involves looking at the old screens copying the values over.  The watch dogs are still controlled by the old control screens.  This will be fixed on Monday when I finish switching the front ends over from their sub-network to the main network, at which point logging into megatron will no longer be necessary.

  Q3, a PZT2222A transistor, on D0901846 is replaced by a GE-82. However, the board is still not fully function.

Since Q3, PZT2222A, was broken, I went to Wilson house and got some SP3904's for replacement. But somehow, I broke it during

installation, and did not notice it, and resumed the test. When I got to test 8 on the list, the TTFSS did not work as specified.

Koji checked and found out that -15V, Nref, Vref voltages output did not work correctly. So the SP3904 I installed was removed

and replaced with another SP3904 by Koji, and Vref is working. 

Q4 transistor is broken as well and it was replaced by GE 82.

Q1 might be broken too since -15V out is not working.

I'll go to Wilson house to get more transistors next week.

After the broken parts have been replaced, I have to make sure that I separate the power supply board from the rest of the circuit and

check if all V outputs are  working, then reconnect the board and check if the current input is reasonable before resume the test.

I hope the wrong input voltage problem today wouldn't damage anything else.

How much current do you need for each voltages?

GE-82 was the only PNP transister I could find in the lab. It's too old but we just like to confirm any other components are still functioning.

Similarly, we can confirm the functionality of the other components by skipping those current boost transisters,
if we don't need more than 30mA.

Issues I notice on first glance:

1. The OSEM Sensor Input matrix and the DOF2COIL Output matrix screens should be their own screens and linked from the overview. Right now they are not. Where is the input matrix?
2. The SIDE GAIN looks like zero on the main screen, but the side OSEM signal seems to be getting through to the SIDE filter bank. . I think the wiring of the SIDE signal through the input matrix is bogus.
3. The OUTPUT matrix seems to be the transpose of the previous OUTPUT matrix and we have lost the wires that connect the inputs and outputs to the matrix. We ought to think about how best to represent things on the OVERVIEW screen; probably only need to have a minimal representation and allow power users to open up the detailed screen.
4. The TIME string is whited out. How will this be done? Does each FE display its local time on its EPICS screens?
5. So far unable to get any channels on DV. How do we look at channels / test points?
6. As far as we can tell, there is no connection between the output of the SUSPOS, etc. filter banks and the OUTPUT MATRIX. So....nothing actually goes to the coil driver. Its hard to imagine that this new SUS could have ever worked. Is there any evidence that the damping actually worked in the past, or was it something like "well, the watchdog values came down to small numbers eventually..." ???
7. We are trying to debug the simulink file, but....the wiki entry on how to do this is out of date (yet updated as recently as August!) some path stuff just probably needs to be edited.

Basically the suspensions are not functioning yet and we can't attempt locking of the MC.

We added the Thorlabs HV Driver in between the FSS and the NPRO today. The FSS is locking with it, but we haven't taken any loop gain measurements.

This box takes 0-10 V and puts out 0-150 V. I set up the FSS SLOW loop so that it now servos the output of FAST ot be at +5V instead of 0V. This is an OK

temporary solution. In the future, we should add an offset into the output of the FSS board so that the natural output is 0-10 V.

I am suspicious that the Thorlabs box has not got enough zip to give us a nice crossover and so we should make sure to measure its frequency response with a capacitive load.

The medm screens have been updated further, with the hidden matrices added in bright colors.  An example screen shot is attached.

Megatron has been renamed c1ioo and moved to martian network.  Similarly, c1sus and c1iscex are also on the martian network.  Medm screens can be run on any of the control machines and they will work.

Currently the suspension controller is running on c1sus.

The frame builder is currently running on the fb machine *however* it is not working well.  Test points and daq channels on the new front ends tended to crash it when Alex started the mx_stream to the fb via our new DAQ network (192.168.114.XXX, accessible through the front ends or fb - has a dedicated 1 gigabit network with up to 10 gigabit for the fb).  So for the moment, we're running without front end data. Alex will be back tomorrow to work on it. 

Alex claimed to have left the frame builder in a state where it should be recording slow data, however, I can't seem to access recent trends (i.e. since we started it today).  The frame builder throws up an error "Couldn't open raw minute trend file '/frames/trend/minute_raw/C1:Vac-P1_pressure', for example.  Realtime seems to work for slow channels however.  Remember to connect to fb, not fb40m. So it seems the fb is still in a mostly non-functional state.

Alex also started a job to convert all the old trends to the correct new data format, which should finish by tomorrow.

RA: Nice screen work. The old screens had a 'slow' slider effect when ramping the bias so that we couldn't whack the optic too hard. Is the new one instantaneous?

 took two runs of the script as usual

 Looking at the sliders, I apparently still need to connect them properly.  There's a mismatch between the medm screen channel name and the model name.  At the moment there is no "slow" slider effect implemented, so they are effectively instantaneous.  Talking with Alex, he suggests writing a little c-code block and adding it to the model.  I can use the c code used in the filter module ramps as a starting point.

The vertex crane drive is overheating, it stopped functioning. Service man will be here tomorrow morning.

I crane was just turned  on for for may be  about 5 minutes. The vertical drive was fine for a while, but the horizontal did not worked at all.

The crane is tagged out again and the controller box is cooling down.

We found a small PCB defect which is an excess copper shorting circuit on the daughter board,

it was removed and the signal on mixer monitor path is working properly.

 We were checking the new TTFSS upto test 10a on the instruction, E1000405 -V1. There was no signal at MIXER mon channel.

It turned out that U3 OpAmp on the daughter board, D040424, was not working because the circuit path for leg 15 was shorted

because of the board's defect. We can see from fig1 that the contact for the OpAmp's leg (2nd from left) touches ground.

We used a knife to scrap it out, see fig 2, and now this part is working properly.

I found that several linux libraries have been moved around and disabled today. In particular, I see a bunch of new stuff in apps/linux/ and ezca tools are not working.

Who did this and why is there no ELOG ???

Also found that someone has pulled the power cable to the function generator I was using to set the VCO offset. This is the one on top of the Rb clocks. Why?? Why no elog? This is again a big waste of time.