PSL model changes. WP6084
Ben, Jim, Dave:
Three psl models were changed today:
h1ioppsl0: Had the new Contec 6464 binary IO card added.
h1pslpmc: Removed its grounding of the last four DAC channels, these channels will now be used by the new outerloop system
h1psliss: added the new outerloop test code for this week's chassis install and test by Ben. Current code just monitors the ADC input channels and writes them at 2kHz to the commissioning frame. I permits the four DAC channels to be driven by filter modules, it provides binary control and monitoring of the eight BIO channels.
I have created a simple MEDM and attached itto the site map (PSL -> 'ISS BEN TEST').
We anticipate more h1psliss code changes as this commissioning progresses during the week.
New GDS code
Jim:
please see Jim's alog.
Reboot h1guardian0
TJ, Dave:
h1guardian0 was rebooted after running 29 days. The loading came down a bit but starts off in the mid-20s.
New digital video camera
see today's alog for details
Wind gust meter attached to h1pemex
Jim W, Jim, Fil, Richard, Dave:
LHO's Young ultrasound 3d anemometer was attached to three spare ADC channels on h1pemex. The channels are ADC_0_12,13,14.
Frame Writer Code Testing
Jonathan:
New daqd code was tested on h1fw0. The new code has been left running.
Beckhoff C1-PLC1 code change
Daniel:
please see Daniel's alog
DAQ Restart
Daniel, Dave:
DAQ was restarted to sync to new h1psliss channels and the latest Beckhoff h1ecatc1plc1.
After running a low battery shutdown test, dust monitor #7 has been removed from the LVEA.
Isolated pump carts from HAM5/HAM6 annulus system but leaving carts running. AIPs were started earlier in the day and pump currents look low enough as to not need assistance -> Will shut down 2 of 4 running pump carts in the morning if not needed. Other pump carts will need to run until Friday morning judging from current data
TITLE: 08/16 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Aligning
INCOMING OPERATOR: Jeff
SHIFT SUMMARY: Pretty busy mintenance day. Much more than I expected at least. TCS crew is still working on diagnosing TCSY, commissioners are trying to lock without disturbing them too much.
LOG:
PEM power supplies in the CER mezzanine were swapped out for Kepco model JQE supplies. This model is a 1/4 rack version, and allows for four power supplies to be mounted on one shelf. This is to make room for the ±24V power supplies that will be used to power Beckhoff/Baffle PD Amplifier/ Spool X/Y camera ect. All PEM instrumentation microphones, magnotometers, ect. were powered down from around 10:30 am to 1:00 pm. All power is now restored.
Fil, Terra
I did a quick check of power spectra for all corner station mics and mags, before and after power supply swap. Attached spectra show pre-swap in darker colors as references, post-swap in lighter.
Found post-swap saturation in several mags, strongest in MAG_LVEA_INPUTOPTICS (first attachment at 21:03 UTC ). Fil switched this mag to battery power, which has temporarily fixed the problem (second attachment at 23:03 UTC). He took a look at the mag box in the lab but found nothing wrong. We left it battery powered for now. Will investigate more tomorrow.
Additionally, it looks like MIC_LVEA_HAM7 got disconnected around 23:03 UTC (top right of second attachment).
Channel 2 of AA Chassis S1300104 found to be bad.
MIC_LVEA_HAM7 started negatively railing yesterday ~3 hours after the power supply swap, trend attached (first drop then raise is from power supply swap). Turns out that AA channel has gone bad (bottom most AA chassis in PEM rack). Fil will pull it and have a look tomorrow morning.
AA chassis repaired, HAM7 mic back up and running. MAG_LVEA_INPUTOPTICS was also fixed. At this point, all corner station mics and mags are running well. Attached are power spectra for all.
Cabling for the readbacks for the TCS RF Amp was pulled in this morning. Readbacks are connected to the slow controls concentrator in rack ISC-C3 slot U33/32, port 3. This closes out fault report 6025.
The PSL power watchdogs tripped at 20:38:13 UTC (13:38:13 PDT). The cause appears to be the NPRO turning off. In the attached trend the NPROOK channel, which monitors if the NPRO is working or not. goes to zero (indicating the NPRO turned off) at 20:38:08 UTC, 5 seconds before the power watchdogs trip. The cause of the NPRO turning off is currently unknown. I am bringing the PSL back up.
PSL is now back up and running; came up without issue. Unknown at this time what caused the NPRO to shut down, will investigate. I reset the injection lock reset counters. Filed FRS 6060 to document the NPRO shut down.
The most recent svn software version is running now on all Beckhoff computers. Changes In detail:
All computers have been booted to make sure we are running a clean version.
Jim W. noted that a bleeding off of these accumulated saturation counts should be added to the HEPI models and this task depreciated. Only HAM1 had saturation counts to reset (it is not on the HEPI L4C WD SAT Monitor MEDM screen). Jim W. reset it and I did not see the number of counts.
Re WP 5986. Currently just running three of the four pumps at the Corner Station as I have one off for cleaning. This pump has been running from the beginning with little break and I was not always so fastidious about cleaning up the drips. It was an mess and I think there are are a couple bearing leaks at the motor and the pump. Being cleaned up now though will help evaluate if further action/worry is warranted. With just three pumps running the drive out to the pumps is about 30% higher than before--may show in a periodic famis task if it is executed during this period.
It's ready to go back together and essentially it is together but some of the fasteners are just impossible to get to without disconnecting plumbing (messy.) Going to shop for or fabricate a couple custom tools to help reassembly. WP remains open.
(M. Pirello)
Per Richard's Work Permit #6092 I reprogrammed both CPS fanouts in the LVEA, and the ones on the X and Y end stations. Programming was successful and the heartbeat LED's are now off.
S1400610 EY
S1400612 EX
S1400599 LVEA
S1400613 LVEA
WP 6087 The GDS software has been updated to branch 2.17.4 to address Bugzilla 897, 936, and 952. Release notes (T1600007) document has been updated. This affects Ubuntu 12 and Ubuntu 14 workstations.
Tues. maintenance task
(Corey, Fil, Richard M, Sheila)
Per Fil's Work Permit #6071 (Fil took care of running/connecting the camera's shielded network cable to the table's Patch Panel earlier):
Work Permit #6071 can now be CLOSED.
I have added a check to the LocklossShutterCheck guardian that will add to the guardian log a note whether the HAM6 GS13s saw a large kick or not. Note that this does not in any way change the functionality of this guardian, in that it still requires an Operator to run and look at the plot, then manually reset this guardian.
However, we should be able to look through the guardian log to ensure that each time we lose lock, the log notes that the GS13s saw a big kick. When we are satisfied that this is a good measure of the shutter having closed at the last lockloss, we can consider using it as an automation metric in lieu of Operators manually resetting the guardian.
I have set the threshold for "big kick" for the GS13 to be 30,000 nm/s (1nm/s / count, so 3e4 counts). When the shutter closes fast, the GS13 sees a signal as large as 90,000 nm/s, but when the shutter closes slowly it only kicks the GS13s to about 10,000 nm/s. The threshold of 30,000 nm/s should differentiate between a fast vs. slow closing of the shutter. Normal GS13 signal is under 100 nm/s peak.
Attached is the code, which is also checked into the svn. The idea is (once we're ready to make this automated) that if we see the GS13 kick, the CheckShutter state will automatically go to the LowArmPower state, and allow the IFO to relock. If there is any problem, including inability to fetch the data, the guardian will stay in the CheckShutter state, and will require human intervention. One could also consider adding light level checks to this, but I think that's probably overkill given the other checks that we already have in place.
At least twice today we've run into the situation where we're still locked at 2W but lose lock, and the power going to the AS port is not enough to warrant a fast close of the fast shutter. This makes things a bit more confusing, since you must know that it's okay that the shutter didn't close in this case.
So, I've added another level of checks to the LocklossShutterCheck guardian to check if the trigger PD saw more than the threshold. If not, it logs that the shutter should not have fired. If the trigger PD goes above threshold, then it looks at the GS13 data and logs whether it saw a kick or not.
Again, these changes only affect what goes into the guardian log. Manual intervention is still required at this time to reset the guardian and allow the IFO to relock.
A different option that we can also implement is to alter the thresholds for the power level that sends the guardian into the CheckShutter state. Sheila points out that maybe we only should be running these checks when there's a chance that the shutter will have closed, so at more than 2W.
After talking with Daniel this morning I made a few more changes to this guardian. The problem that Jenne was trying to address with the check on the AS power was that for 2 Watts most locklosses from 0 CARM offset will trip the shutter, but not all of them should since sometimes not as much of the power goes to the AS port. We think that the second option Jenne mentioned, only requiring a check of the shutter after high power locklosses in which we nearly always expect it to fire, will let us avoid relying on the trigger PD in this logic.
This morning I redid the arm power checking a little bit, to include the calibration into watts, and increased the threshold for requiring a shutter check to 14 kWatts of circulating power in an arm. (This is just over 4 Watts input power). I also took out the check on the triger PD, and made the logic that Jenne had logging results last night be used to reset the state of the guardian. Now the gaurdian will rest itself to LOW_ARM_POWER if it sees that the shutter went off and the GS13s see a kick. If the GS13s do not pass the test it will go to a new SHUTTER_FAIL state.
We will test this when we get to relocking this afternoon.
Sheila Evan Jenne Terra
The IMC length drive has large glitches when only the IMC is locked. The first attachment shows the MC2 M2 length drive durring a quiet time on July 31st, and a glitchy time today. There are glitches present in both traces, but they are much louder in the trace from today. If you look back at data from late July, the glitches have intermittently been present even before we started having trouble locking, so this is probably not the main reason we can't lock.
The second attachment shows 15 minutes around the time of the July 31st trace, when the glitches transition from being quiet to loud.
Daniel, Sheila
These glitches appear when green light starts flashing in the arms. The COMM PLL sometimes see a green flash, and tries to lock as you can see in the control signal in the top panel of the attached plot. This would be fed back to the mode cleaner if ALS COMM was locked, but that feedback is disabled. The PLL trying to lock moves the COMM VCO, which through some kind of RF coupling similar to the cause of the whistle glitches causes the mode cleaner glitch.
Once we are fully locked we park the VCO so this should not be a problem in full lock and should not be related to the glitches we see after changing gains on the CM board
Short version: The new shutter seems to be closing harder than before the vent. This is causing the ISI to trip. So far we have gotten around this by running the ISI in a low gain state, but this makes the table motion much worse above 1 hz.
After the shutter work, we started having problems with trips of the HAM6 ISI when the new shutter trips. This morning we put the ISI in the "Robust" isolated state, which uses low gain isolation loops with UGFs around 10hz. The normal loops have UGFs around 30-40 hz. For now this seems to have eliminated the tripping of the ISI, but the performance of the ISI is much reduced above 1 hz. First plot shows a comparison Y GS13s and ground STS for HAM6 for the two configurations. Red traces are with the high gain loops, blue traces are with the low gain loops. Below 1 hz they look roughly the same (low frequency diffs seem to be mostly in the ground for blue), but at 1 hz the high gain loop is doing ~100x better. Not surprising.
I've looked the GS13s in Z at shutter triggers before and after the vent and the shutter seems to be moving the table a lot more now. Attached plot shows a trigger from today with the 10hz loops (blue), yesterday with 30hz loops ( orange/ spiced cider) and Aug 1st with 30hz loops (red). I've looked over at least 3 events in each configuration and they look remarkably consistent, with respect to ISI configuration. Shutter triggers before the vent seem to have kicked the table less than they do now. Maybe this will reduce as the shutter breaks in?
We have some medium gain loops installed with slightly less gain that the high gain loops, tomorrow during maintenance I'll try testing those, but I doubt they'll be enough. Otherwise, we can come up with some loops with some better compromises between UGF and high frequency roll-off than the low gain loops. But the best option would be to figure out what can be done to reduce the kick from the shutter.
tagging sys
Jim, there is a little known feature on the fast shutter driver wherein a signal is available to say the shutter has triggered. You could use this signal as a form of a blanking pulse to allow you to ignore the seismic signals that follow a shutter trigger. Let me know if you want details, but the spigot is a BNC on the front of the shutter labeled "Blanking Output"
Ben has created a ISS OUTERLOOP medm. It is attached to the SITEMAP by navigating PSL -> 'ISS OUTERLOOP'