Filiberto fixed the working 36/45MHz WFS, S/N 1300511. He extracted pins from the 5-coax connector, rotated the connector shell by 180 degrees, and inserted the pins again such that the connector looks like the mirror image of its old self. Since it's the mirror of the mirror, now it's correct.
I rerouted the cables inside the ISCT1 so the connections from outside of the table are still intact.
Connected the diff-single converter out 3 and 4 to the MCL PZT driver.
ISC R1, position 2, channel (3, 4) = H1:ISC-(434, 435) cable = MCL controller (X, Y) channel on ISCT1.
DAC works.
+175 ml (accdentally). Should have been < 150 ml. Jeff B. filled 200 ml three days ago.
Started the high power oscillator this morning. The power sum came up to 144 W with the corona aperture in and the external shutter open. With the external shutter closed, the output power is ~152 W (there are some intervening optics and polarisers in the way, which accounts for the difference). With the corona aperture removed, the output power was 148 W. The pump current was decreased from 50.6 A to 50.0 A to put the operation point in the middle of the second stability range. SeededFreeRunning1.png shows the beam profile of the seeded but not injection locked high power oscillator. rpn2jpg is the measured relative power noise of the injection locked high power oscillator. This should be compared with the diagnostic breadboard measurement to be performed tomorrow by Ed. Of note is the peak at ~5 kHz that is in the dark noise spectrum of the photodiode. I am not sure what this is due to. Also there are a number of peaks in the power noise spectrum that are around 13 kHz. These peaks were not affected by changing the injection locking servo gain. All the PSL servos require tweaking at this stage. If the laser trips out for any reason, please do not attempt to resuscitate it yourself! Jason, Peter
The trend writer on h1tw0 has been started after a lengthy absence due to equipment repair.
All time in UTC
13:47 Chris S. working on beam tube enclosure sealing. Approx. be locateed 1/4 to 1/2 way toward Mid-X. Morning work.
15:19 Christina to LVEA
15:51 Jason heading to PSL
16:10 Joe to LVEA
16:15 Cheryl making measurement on IMs.
17:07 Hugh and Jim to EX.
17:21 Ed to LVEA
17:37 Ed back
17:40 Travis to LVEA to the racks near HAM2,3.
17:53 Manny to End stations looking for extension cords.
17:56 Joe out
18:13 Dave restarted LSC, ISC model
18:17 Hugh to LVEA retrieving equipment near HAM2.
18:24 Jenne and David start cutting floors in the LVEA
18:31 Hugh out
18:51 Hugh to EY making some measurement
18:57 Jason and Peter out for lunch
19:04 DAC restart (EX)
19:54 DAC restart (PEM EX)
20:23 Manny out
20:46 Manny to LVEA
21:06 Fil removing electronics box from ISCT1.
Richard and Gerado to LX and beer garden look at VAC channels. BSC7 and BSC8 high pressure alarms were their doing.
21:25 Chris to EX to unload pile of lumber.
21:47 DAC and SUS ETMY model restart
22:30 Fil out
22:40 Peter and a group of operators to LVEA for Transition training.
23:00 Peter et al out.
Keita to ISCT1 sometimes between 22:00-23:00
Added a new ISI_OFFLINE state to the sei manager guardians that has the ISIs in Ready and HEPI Isolated. This state is mainly used while the sei team is testing and not for normal operation. To get to ISI_OFFLINE I added a couple of transition states from DAMPED that will turn Off the ISI damping loops, and then turn them back on before entering DAMPED again. (HAM and BSC graphs attached)
Tested yesterday on ITMX and HAM5. Loaded the new code into all of the managers today.
Darkhan T., TJ S., Travis S., Evan G.
Yesterday, we took PCal end station measurements for both end stations. See attached pics if you are interested in the raw data and timestamps. Otherwise, see T1500129 and T1500131 for the summary reports for each end station.
A quick glance at the optical efficiency of X end seems to indicate that the known clipping issue is getting worse.
Can't see data before 4/26 on PT100. Surveyed other gauges over 15 days. PT100 seems to be the only one that gets cut off on 4/26. Dave Barker is investigating.
After Tuesday activities, noticed a step change in pirani gauge signals. Attached is plot of PT100 (on HAM 1) and PT140 (on BSC4). Note: PT100 CC gauge keeps turning on and off due to pirani set point and stepping. PT120 also shows a step in signal. Yesterday Richard & Gerardo pulled the leads on PT120 while measuring the voltage. Voltage read higher valve when lifted from rack. PT140 pirani trend over 15 days shows a major step from 4/26 (when Beckhoff was installed) to 5/3 when power was switched and system rebooted.
Sounds like the input impedance of the Beckhof ADC is lower than the original VME card ADC. These form a voltage divider with the gage head's output impedance. I/O impedances should be listed in the respective instrument datasheets. There may be a jumper/selection available.
Beyond recalibrating epics records, good to confirm that the gage heads are happy driving whatever impedance they see full-scale.
Good idea Chandra. I hadn't even considered looking at the piranis!
Daniel, Nutsinee
After Daniel made some changes to the RS configurations today (alog27008), I ran the random walk script again.
Result:
CO2X RS requested angle and measured angle agree within 0.01 deg -- Better than ever
CO2Y RS requested angle and measured angle agree within 0.02 deg -- Better than ever
And PSL RS requested angle and measured angle agree within 0.004 deg -- Awesome!
I have also recalibrated the power vs. angle calculator for CO2 RS.
Suspect Beckhoff work again.
With the ring antenna and the battery powered scope I chased down the time-domain transients that I observed on the L2 coil cable (10msec burst every 100msec). They are due to the RFID tag, and get huge close to the RFID stations (35Vpk when the antenna is held close to the RFID board).
Attached are 4 scope traces, as well as a 3MHz span spectrum. The frequency content is 124kHz plus (mostly odd) harmonics. The y-axis is arbitrary, as the gain depends on the distance from the source.
I also verified that these time-domain bursts disapear in the L2 coil cable common signal. However, most of the high frequency junk on those cables is still there - as expected only the 124kHz and harmonics disapear.
Robert and Nutsinee tested the effect of turning the RFID system off in alog 23169.
Turns out that the rotation stages are sufficiently different that the same parameters won't give optimal results. In particular, the CO2Y rotation stage seems to require significantly more current for the same velocity.
For TCS I reduced the maximum speed even further, since it is unlikely that we ever need high speed. The maximum is now about 100 times slower than originally. The speed can simply be left at 100% with 10 sec acceleration and deceleration times. I also needed to reduce the PI loop gains by 2 for X.
I noticed that the motion always falls short of the final destination. For large angles the errors tend to be somewhat larger. I added a fine adjust feature which, when engaged, will nudge the motor, after it finishes its initial motion. This feature includes an adjustment angle which is intended to compensate for the shortfall.
The busy flag gets stuck quite often, and the auto-abort is required for the fine adjust feature to work consistently.
In order to connect the duty cycle and current readbacks, the 0x1A07 and 0x1A09 regions need to be assigned in the process data configuration of the motor terminal. This will add "DCM Synchron info data channel" structures which contain the info1 and info2 channels.
Here are the CoE parameters for the TCS motor controller.
Here is a snapshot of the rotation stage settings screens, as well as updated medm screens for the rotation stage and the readbacks, respectively.
When using the adjust feature, the busy flag of the rotation stage is no longer a good indicator to see, if the laser power has reached its final value. The internal state of the laser power controller is now available in EPICS—as well as a state_busy flag which indicates that the power controller (rather than the rotation stage controller only) is busy.
WP5857 Keith, Rolf, Jim, Dave:
Tuesday 3rd May we upgraded the CDS front end systems and the DAQ to RCG3.0.2
The order of build-install was:
During the make installWorld h1fs0 developed a major NFS problem and stopped serving /opt/rtcds file system. We reboot h1fs0, but the NFS service did not start correctly and clients could not umount nor mount the file sytem. We restart kernel-nfs-server daemon and the NFS clients remounted correctly.
I need to change the SUS ITMY and ETMY now the HWWD part is synced to the hardware regarding signal levels (I removed temporary NOT inverters on binary signals).
16:00 h1iscex developed the connTrack Table Full error, new network connections were not permitted. We have to reboot this computer and disrupt the EX Dolphin fabric, requiring all EX models to be restarted (except susaux).
Vacuum controls Beckhoff gauges on BSC7,8 were moved from their temporary slow controls Beckhoff connect to the LX vacuum controls system. This required a name change (H1->H0), minute trends were changed on DAQ.
Upgrade built ISI-HAMS with latest isihammaster.mdl file, but team SEI needed to back out this latest change, so common file was reverse-merged to previous version and all isi-ham rebuilt and restarted.
CAL system was modified to remove the Blind Injection data path (h1calcs and h1calex).
Big DAQ restart at end of afternoon: new VE EDCU list, new Slow Controls EDCU LIST, new Dust monitor EDCU list, new susitmy/etmy hwwd code, new isi-ham models, new cal models
As of now CDS overview shows some IPC errors all related to h1iscex in H1HPIETMX (H1:LSC-X_TIDAL_HEPIETMX-IPC), H1ASC (a bunch of ALS ASC signals) and H1OAF (H1:SEI-EX_2_OAF_MUX_RFM).
Seems like the errors started at about 18:59 or so, went away after 3 minutes, then came back at about 19:53 or so and never went away, all UTC.
Hmm, now they're gone.
I am adjusting the CP2 LLCV PID parameters controlled by Beckhoff system. 1. Set to manual mode at 35% open and adjust PI settings while in manual mode and observe value in data viewer real time. PI still updates its values in manual mode. Note that every time a PID value is changes the LLCV % open value resets. The pneumatic actuator is physically jouncing up and down and will wear out prematurely at current Beckhoff settings. The new electronic actuator on CP1 is not jolting as much as CP2, but up/down movement is still noticeable at rapid rate - PID parameters should be addressed. Have not surveyed the other five actuators (CP3 doesn't count).
Unsuccessful in adjusting PI parameters today (P & I gains set too low from nominal 6 & 360 s. values, respectively), which significantly reduced the physical jitter in the LLCV by reducing % open signal amplitude but did not settle to the set point. But good news! At the end of the day, Patrick provided the magic button. There is a way to apply a smoothing factor on the CP liquid level (0
Good work Chandra - keep at it - this is a worthy pursuit for familiarity with the new Beckhoff controls - I will need you and Gerardo to brief me on the new environment as soon as time permits
While I was at End X (around 7pmish) I heard repeaded banging noises coming from the GN2 pipes (GN2 BURST, GN2 VENT and GN2 REGEN). Not sure whether that's a know isssue, but it was rather loud, and the support piers were shaking noticably.
This was observed between 00:46 and 0144 UTC on May 4th (17:46-18:44 PDT on May 3rd).
Also, the observation was done inside the building. I did not investigate the outside.
GN2 = "gaseous nitrogen"
LN2 = "liquid nitrogen"
for those tracking our jargon.
John and I investigated Wednesday afternoon and found everything quite -> John excited the ambient-air vaporizer (large finned aluminum ambient heat exchanger mounted on the concrete slab near the supply dewar outside of the building and piped in-line with the GN2 REGEN connection to the pump and which is easily mechanically excitable with wind) while I was in the VEA listening - Nothing -> We also created excessive LN2->GN2 boil-off in CP8 by filling in manual mode at a "high" LLCV %OPEN setting - Nothing. We did note that, nowhere in the piping between the ambient air vaporizer and CP8 was the piping clamped to anything. In fact, it was just resting on pipe stands. Also, an "ice ball" had formed on the bellows at the pump penetration - reminding us of the fact that all of the ambient air vaporizers on the X-arm have severed welds at the ASA connection flange which results in a parallel path for the GN2 exhaust to exit he pump -> We then capped the piping to eliminate this as an excitation mechanism
~21:01 UTC I turned off the camera, frame grabber, then powercycled the computer (then turned the frame grabber and the camera back on). Only HWSX code is running at the moment. Things look good for now.
May 3 16:44 UTC Stopped HWSX code and ran HWSY code alone. HWSX code had been running fine since yesterday.
May 5th 18:20 UTC I noticed HWSY code stopped running. There has been many comuter and front end restart since I left it running so it was unclear what caused it to stop. I reran it again and going to leave it again for another day.