Recent Log Entries

FSD Masking Tool: Successful System Masking for: BeamLossMonitor

Log Number: 4046514Logbook(s): Tags: Body: System Masking for: BeamLossMonitor
User: moser
Areas: All

BeamLossMonitor Devices:
ILM0I07
ILM0L01A
ILM0L01B
ILM0L02
ILM2D00A
ILM2D00B
ILM0L04A
ILM0L04B
ILM0L05
ILM0L06A
ILM0L08
ILM0R01
ILM4D00
ILM0R03
ILM0R04
ILM0R06
ILM0R08
ILM0R09
ILM1L01
ILM1L02
ILM6R08
ILM3S00
ILM7S00
ILM9S00
ILM5S10
ILM5E03
ILM7S01
ILM9A01
ILM3E02
ILM5A01
ILM1A04
ILM1A06
ILM1A09
ILM5A10
ILM1A16
ILM1A19
ILM3R10
ILM9R07
ILM1R09
ILM2L03
ILM5R10
ILM5R05
ILM2L01
ILM2T09
ILM8T09<

RF Expert Identified 2L22 Klystron-2 Voltage Not Regulating Well at Times

Log Number: 4046510Logbook(s): Body: 

Channels: R2MXKPSV1, R2MXKPSV2, R2MXKPSV3, R2MXKPSV4 -- signals in kV

KPSV2 powers 2L22-2 and 4. This could explain the recent 2L22 trips we've been "seeing". Quotation marks, because what we see is 8E02 BLM trips (often with 1L02). Sometimes we see FSD panel report 2L22 as the cause of the trip, but if this happens we don't actually see any 2L22 blue cav-status box leave blue and go red, or red and pink, etc... i.e. the trip and subsequent recovery is very fast.

Hall C Current Ramp RF Sensitivity

Log Number: 4046508Logbook(s): Entry Makers: bschaumlBody: 

It seems that we are having trouble ramping Hall C current from an attenuator position of 200 (~11uA) without 2L26 and sometimes 2L22 tripping. Based on historical values (we rarely set this above 180) and the trips we see, we are reducing this to 150. We may explore raising the ramp rate, though that has just been gradually decreased throughout the week as well...

2L22-2 STAT1 Seems to Correlate w/8E02 BLM Trips

Log Number: 4046506Logbook(s): Body: 

Channels: R2M1STAT1, R2M1STAT2, R2M1STAT3, R2M2STAT1, R2M2STAT2, R2M2STAT3, R2M3STAT1, R2M3STAT2, R2M3STAT3, R2M4STAT1, R2M4STAT2, R2M4STAT3, R2M5STAT1, R2M5STAT2, R2M5STAT3, R2M6STAT1, R2M6STAT2, R2M6STAT3, R2M7STAT1, R2M7STAT2, R2M7STAT3, R2M8STAT1, R2M8STAT2, R2M8STAT3, R2Q7STAT3, R2Q7STAT2, R2Q7STAT1, R2Q6STAT3, R2Q6STAT2, R2Q6STAT1, R2Q5STAT3, R2Q5STAT2, R2Q5STAT1, R2Q4STAT3, R2Q4STAT2, R2Q4STAT1, R2Q3STAT3, R2Q3STAT2, R2Q3STAT1, R2Q2STAT3, R2Q2STAT2, R2Q2STAT1, R2Q1STAT3, R2Q1STAT2, R2Q1STAT1, ILMWA2BFSDl, IBC0R08CRCUR1

Will give it a closer look.

xB - Attenuator Climbinging/Injector Charging Issue

Log Number: 4046501Logbook(s): Entry Makers: schoeneBody: 

Hall B's attenuator climbs steadily to between 3-400, culminating in a MaxJuice trip and then returning to ~200. Seems to cycle every half hour or so, and trips MaxJuice on half of them. (would expect 16 discharges, 8 trips per shift)

This is the reverse of what we had seen last week, (where the attenuator would jump up suddenly and then decline) but similar to what we'd seen earlier in the run albeit at a much higher rate than before.

Storms are Gone, 8E02 BLM Trips, however, Decided to Stay

Log Number: 4046500Logbook(s): Body: 

Channels: R041STAT1, R042STAT1, R043STAT1, R044STAT1, R045STAT1, R046STAT1, R047STAT1, R048STAT1, R151STAT1, R152STAT1, R153STAT1, R154STAT1, R155STAT1, R156STAT1, R157STAT1, R158STAT1, R171STAT1, R172STAT1, R173STAT1, R174STAT1, R175STAT1, R176STAT1, R177STAT1, R178STAT1, R1A1STAT1, R1A2STAT1, R1A3STAT1, R1A4STAT1, R1A5STAT1, R1A6STAT1, R1A7STAT1, R1A8STAT1, ((R00PGMES+R015GMES)/(R015GSET+R00PGSET)), ((R011GMES+R012GMES+R013GMES+R014GMES)/(R011GSET+R012GSET+R013GSET+R014GSET)), ((R027GMES+R028GMES+R03XGMES+R04XGMES)/(R027GSET+R028GSET+R03XGSET+R04XGSET)), R1M1STAT1, R1M2STAT1, R1M3STAT1, R1M4

Follow-up Re: South Access RM #16 loss comm

Log Number: 4046491Logbook(s): Body: 

Component on communication board failed and cause RM16 to fault. Replace card and verified with source that both neutron and gamma channels tripped both chains of the PSS. Although, the card is not directly linked to the PSS, the nature of the failure caused a hard fault that locked the CARM up with all trip indicators visible locally.

2L22-3 Phase Optimized, -5deg change

Log Number: 4046483Logbook(s): Entry Makers: moserBody: 

After repeated quenches when trying to recover in SELAP.

Dropped to SEL, phase optimized, brought back up to SELA then SELAP. Back to sending...

SL Clamps Waking Up

Log Number: 4046476Logbook(s): Body: 

Channels: R041STAT1, R042STAT1, R043STAT1, R044STAT1, R045STAT1, R046STAT1, R047STAT1, R048STAT1, R151STAT1, R152STAT1, R153STAT1, R154STAT1, R155STAT1, R156STAT1, R157STAT1, R158STAT1, R171STAT1, R172STAT1, R173STAT1, R174STAT1, R175STAT1, R176STAT1, R177STAT1, R178STAT1, R1A1STAT1, R1A2STAT1, R1A3STAT1, R1A4STAT1, R1A5STAT1, R1A6STAT1, R1A7STAT1, R1A8STAT1, ((R00PGMES+R015GMES)/(R015GSET+R00PGSET)), ((R011GMES+R012GMES+R013GMES+R014GMES)/(R011GSET+R012GSET+R013GSET+R014GSET)), ((R027GMES+R028GMES+R03XGMES+R04XGMES)/(R027GSET+R028GSET+R03XGSET+R04XGSET)), R1M1STAT1, R1M2STAT1, R1M3STAT1, R1M4

Operator SIGN IN

Log Number: 4046471Logbook(s): Body:  ACCELERATOR OPERATOR SIGN IN FORM OPERATOR:    Schaumloffel
DATE:             09/25/2022
SHIFT:               Swing

The operator has read the following:

Severe T-Storm Warning

Log Number: 4046470Logbook(s): Entry Makers: bschaumlBody: 

A warning came through on the weather radio in the MCC. Looking at lightningmaps.org we've got some strikes southeast of Richmond in the last few minutes, which is usually close enough for the machine to feel.

Pages