I am guessing that the NFS file system hangup may have caused some machines to get into an awkward state. We may be best off doing a controlled power cycle of everything...
Zach> Nodus seemed to be working fine again, and I was browsing the elog with no
Zach> problem. I tried making an entry, but when I started uploading a file it
Zach> became unresponsive. Tried SSHing, but I get no prompt after the welcome
Zach> blurb. ^C gives me some kind of tcsh prompt (">"), which only really
Zach> responds to ^D (logout). Don't know what else to do, but I assume someone
Zach> knows what's going on.
By gracefully rebooting nodus, the problem was solved.
It (">") actually was the tcsh prompt, but any commands with the shared or dynamic link libraries looked unfunctional.
I could use
to browse the directory tree. The main mounted file systems like /, /usr, /var, /cvs/cds/caltech looked fine.
I was afraid that the important library files were damaged.
in order to flush the file systems.
These should run even without the libraries as mount must properly work even before /usr is mounted.
They indeed did something to the system. Once I re-launch a new login shell, the prompt was still ">"
but now I could use most of the commands.
/, /usr, /var, /cvs/cds/caltech
I have rebooted by usual sudo-ing and now the services on nodus are back to the functional state again.
# nodus was working in the evening at around 9pm. I even made an e-log entry about that.
# So I like to assume this is not directly related to the linux1 incident. Something else could have happened.
I tested the new table top frequency stabilization system(TTFSS),
I haven’t finished it yet, and accidentally fried one amplifier in the circuit.
We received three sets of a new TTFSS system which will replace the current FSS.
It needs to be checked that the system works as specified before we can use it.
I followed the instruction written on E10000405-v1
The first test inspected how much the currents were drawn from the +/- 24 V power supply.
+24 V drew 350 mA and -24 V drew 160 mA as shown on pwr supply’s current monitor.
They exceeded the specified value which was 200 +/- 20 mA, but nothing went wrong during the test.
Nothing got overheated, all voltage outputs were correct so I proceeded.
I have gone down the list to 6, and everything works as specified.
- Correcting the document for the test procedure
I found a few errors on the instruction document. I’ll notify the author tomorrow.
- How GVA-81 amplifier on D0901894 rev A got fried
During the test, I used a mirror on a stick that looked like a dental tool to see under the board.
Unfortunately, the steel edge touched a board and caused a spark. The voltage on -24 dropped to -16.
I think this happened because the pwr supply tried to decrease the current from shorted circuit,
as I shorted it only short time ( a blink of an eye), it could not reduce the voltage to zero.
When I was checking the power supply and about to adjust the voltage back to the right value
(about 4-5 seconds after the spark,) smoke came out of the circuit.
Koji investigated the circuit and found that a GVA 81 amplifier was broken.
This was checked by applying 5V to the amp, and slightly increasing the current.
The voltage dropped to zero as the amp was broken, so its circuit was shorted.
I’ll see if I can replace this at EE lab at Downs.
If I cannot find a spare one, I’ll replace it with a resistor and resume the test procedure.
Because it amplifies LO signal, which won’t be used during the test.
Net switch mumbo-jumbo:
Although Rana is going to buy a replacement for the Netgear Switch for martian, I opened the lid of the Netgear as the fan already have stopped working.
Also the lid of the other network switch for GC (Black one) was opened as it has a broken fan and a noisy half-broken fan.
I have asked Steve to buy replacement fans. These would also be the replacement of the replacement.
During the work, it seemed that I accidentally toggled the power supply of linux1. It lead lengthy fsck of the storage.
This is why all of the machines which rely on linux1 got freezed. linux1 is back and the machines looked happy now.
If you find any machine disconnected from the network, please consult with me.
The Netgear Network Switch in the top shelf of Nodus' rack has a broken fan. It is the one interfaced to the Martian network.
The fan must have broken and it is has now started to produce a loud noise. It's like a truck was parked in the room with the engine running.
Also the other network switch, just below the Netgear, has one of its two fans broken. It is the one interfaced with the General Computer Side.
I tried to knock them to make the noise stop, but nothing happened.
We should consider trying to fix them. Although that would mean disconnecting all the computers.
[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.
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?).
John Miller has arrived from Australia with 3 bags of Wagonga Coffee. Trade bargaining has started on
250 mgs of Sumatran Mandehling, Timur and Papua New Guine.
The PSL out 2" OD beam guide tube was cut 1.5" shorter to 13.5"
The 10" OD 0.25" wall Al tube was replaced by a lighter, not anodized and thinner wall 0.094" tube of 15.5" lenght, that is 0.75" shorter.
The new position of the PSL table made these cuts necessary.
[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 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.
Larry stopped by today and had to disconnect the m25 machine (this is the 1st GC machine on the left as you walk into the control room) because its IP was conflicting with a machine over in Downs. Do not use 184.108.40.206 as the IP on this machine as this is already assigned to someone else. They couldn't figure out the root password to change it which is why it is not currently plugged into the network, and is not to be until an appropriate IP is assigned.
They've asked that whoever set the machine up to please contact them (extension 2974).
Our new 2W Mephisto has a pretty zippy "SLOW" temperature input. Tuning the perl PID servo, I found that the best response came from setting
the "P" and "D" terms to zero. This is because the internal temperature stabilization servo has a fairly high UGF. In the attached
image you can see how the open loop step response looks (loop is open then the "KI" parameter is set to zero). The internal servo
really has too little damping. There is a 30% overshoot when it gets a temperature step. For this kind of servo Innolight would have done better
to back off on the gain until they got back some phase margin.
New SLOW parameters:
timestep = 1.9 s
KP = 0
KI = 0.035
KD = 0
I installed the blue IP camera from ZoneNet onto the PSL table. It gets its power from the overhead socket and connects via Cat5 to the Netgear switch in the PSL/IO rack.
You can connect to it on the Martian network by connecting to http://192.168.113.201:3037. Your computer must have Java working in the browser to make that work.
So far, this works on rossa, but not the other machines. It will take someone with Joe/Kiwamu level linux savvy to fix the java on there. I also don't know how to fix the host tables, so someone please add this camera to the list and give it a name.
As you can see from the image, it is illuminating the PSL with IR LEDs. I've sent an email to the tech support to find out if we can disable the LEDs.
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 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.
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).
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.
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 (Ag2S). I checked our stock in the clean room. We have enough screws.
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
fw = 0.77e6; % width of resonance (FWHM) in Hz
Plas = 0.164; % power into the PMC in W
% the following number refer to the in-lock cavity state
Pref = 0.037; % reflected power in W
Ptr = 0.0712; % transmitted power in W
Pleak = 0.0015; % power leaking from back of PMC in W
- NPRO injection current 1.0 A
- PMC losses ~32%
- FSS AOM diffraction efficiency ~52%
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.
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.
Steps for RFM switch over:
1) Ensure the new frame builder code is working properly:
A) Get Alex to finish compiling the frame builder and test on Megatron.
B) Test the new frame builder code on fb40m (which is running Solaris) in a reversible way. Change directory structure away from Data1, Data2, to use actual times.
C) Confirm new frame builder code still records slow channels (c1dcuepics).
2) Ensure awg, tpman, and diagnostic codes (dtt) are working with the new front end code.
3) Physically move RFM cables from old front ends to the new front ends. Remove excess connections from the network.
4) Merge the megatron/c1sus/c1iscex/c1ioo network with the main network.
A) Update all the network settings on the machines as well as Linux1
B) Remove the network switch separating the networks.
4) Start the new frame builder code on fb40m.
Brilliant! This is the VERY way how the things are to be conquered!
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) with FSS common gain max out at 30 dB. There is about 50 mW coming out of the laser and a few 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.
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.
- 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
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.
I changed the setpoint for the HVAC control (next to Steve) from 73F to 72F. This is to handle the temperature increase in the control room with the AC unit there turned off.
We know that the control setpoint is not linear, but I hope that it settles down after several hours. Lets wait until Tuesday evening before making another change.
On Friday, Valera and I calculated the modematching for reference cavity from AOM.
We scan the beam profile where the spot should be.
The first beam waist in the AOM is 103 um, the lens (f= 183 mm, I'm not sure if I have the focal length right) is 280 mm away.
The data is attached. The first column is marking on the rail in inches,
the second column is distance from the lens, the third and fourth column are
vertical and horizontal spot radius in micron. Note that the beam is very elliptic because of the AOM.
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.
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:
Elog didn't respond, so I restarted it with the script.
Before killing the process somehow two elog daemons were running at the same time. I killed those two manually.
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]
I uploaded all the material about the RF frequency Generation Box into the SVN under the path:
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'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 restarted the seisBLRMS DMF monitor by ssh'ing into mafalda and starting up a matlab session. I also have started a StripTool session on rossa by forwarding the process from op440m.
We need to get the modern EPICS installation onto these linux machines by copying what K. Thorne has done at LLO.
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...
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.
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.
I found Sanjit's instructions for doing the Nvidia settings too complicated and so I followed these instructions from Facebook:
After installations, the monitors were autodetected and the Xinerama effect is working.
- 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.
I wiped out the old CentOS install on rossa and installed CentOS 5.5 on there. The DVDs are on a spindle in the control room; there were 2 iso's, but I only needed the first to install most things.
It still needs to get all of the usual stuff (java, flash, nvidia) installed as well as setting up the .cshrc and the NFS mount of /cvs/cds. The userID and groupID are set to 1001 as before. Whoever
sees Sanjit first should steer him towards this elog entry.
Over the last couple nights we got the beam into the FSS path and all the way to the IMC and out onto the AP table.
Tara and Valera have calculated a mode-matching solution for the reference cavity. It utilizes only a single lens between the AOM and the reference cavity. Valera and Steve will move the reference cavity into place in the morning.
We noticed that the layout was too tight on the end going into the MC and so we adjusted the angle of the final zig-zag. This will put the final mode-matching lens in between the final steering mirrors (which is generally undesirable) but the lens in this case is only f=400 mm. In addition, this lens may provide some more decoupling between the steering mirrors.
The whole layout has to be a little adjusted because of a calculation mistake I made in the mode-matching. I used only the nominal focal lengths from the CVI catalog and not the effective one. For the UV-grade fused silica lenses, the effective focal length is actually 20-30% longer. Today we measured that the "f=200 mm" lens we got is actually f = 238 mm. The BK7 lenses are much closer to the nominal.
We also replaced the Klinger mount ahead of the PMC with a Polanski style so that we could get the PMC REFL beam out without hitting the mount. Valera will continue to refine this section on the weekend.
Tomorrow, we will lock the MC using feedback only to the NPRO. The 0-150 V piezo driver is on the PSL table ready for action.
I also got a LCD video monitor from Frank and hooked it up on the PSL table. If we like this kind of thing, we can get many of them. They are pretty cheap. It would be handy to have 3-4 of them on the PSL and one on every of the ISC tables. They take the standard video for input and need +12V for power. Right now the one in there is looking at the PMC transmission.
The Omnigraffle layout as of tonight is attached.
I stored the Busby Box, the Rai's Box and the SR554 preamp in the RF cabinet down the Y arm.
I turned off the laser last night to protect against the electricians. but failed to elog it. I accept the burnt toast completely.
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 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:
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 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.
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.