Recent Log Entries

Log Number: 3997268Logbook(s): 

• ELOG

Entry Makers: kernsBody: 

Cavity running at 3Mv/m but tuner isn't working. No faults on tuner so it could be a disconnect downstairs that needs to be checked by SRF.

Log Number: 3997267Logbook(s): 

• ELOG

Body: 

I turned the NDX2L24&25 unit HV on at 100V. It keeps the still present leakage current in 2L24 gamma channel limited at about 15 pA currently, but allows the radiation measurements at a non-optimal efficiency (about 50-70% from nominal at 1000V). Makes the dose rates visible and relatively measurable. A rather large neutron dose rates were observed (up to about 10 rem/h in NDX2L24 at 10:30 - 11:30 am). Also decreased the integration time from 5 to 2 sec to stay within the dynamic range in 2L24&2L25.

Log Number: 3997266Logbook(s): 

• ELOG

Entry Makers: kernsBody: 

Cavity struggling at 9.5 Mv/m. High GASK (6.1v and no RATN) at 9.5 Mv/m and found KCCU at .82a and filaments changed from 5.6v to 5.2v somehow ? Cavity needs driveline , RFCM output and 2.5w amp checked or replaced. Leaving at max of 8.0 Mv/m for now.

Log Number: 3997265Logbook(s): 

• BDLOG
• ELOG

Body: 

ITV0L10- Both ends of the video cable were reterminated, image was
verified at MCC, viewer is ready for beam.

Log Number: 3997264Logbook(s): 

• ELOG
• RFLOG

Tags: 

• Autolog

Body: 

The following cavity histories have been updated:
1L02-8
Username: kerns
Date/Time: 05-27-22_12:49:20
RF Status: Good
Tuner Status: Bad
Comment: Tuner EERR
Special Instructions:

Log Number: 3997263Logbook(s): 

• ELOG
• RFLOG

Tags: 

• Autolog

Body: 

The following cavity histories have been updated:
1L02-4
Username: kerns
Date/Time: 05-27-22_12:49:20
RF Status: Good
Tuner Status: Bad
Comment: Tuner EERR
Special Instructions:

Log Number: 3997262Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 2.4 Target restore date was 2022-05-27 09:45:22 The output from the myRestore execution was as follows: iocsl26rfint Rf12Intlk_Analog@2022-05-27 09:45 55(55) restored Rf12Intlk_Slope@2022-05-27 09:45 121(121) restored Pause: 5 second(s) Execute: caput R2QXIARCinit 1 (success) Old : R2QXIARCinit 0 New : R2QXIARCinit 1 system@2022-05-27 09:45 2(2) restored Execute: /usr/csite/certified/bin/ced2Epics -ced ced -A -s -i iocsl26rfint (success) Procedure return status: Success

Log Number: 3997261Logbook(s): 

• ELOG
• RFLOG

Entry Makers: kernsBody: 

Found cavity 4 GSET 0 and noticed big change in vacuum as I tuned it in and got it to ODVH of 9.8 Mv/m. Three was running at 9.0 Mv/m already. Vacuum changed from 5.1413e-10 to settling out to 8.17867e-10 after 4 settled in. They will trip if turned on at the same time and cav. 4 will have to be ramped slowly back up until vacuum corrected. Will leave plots running to see if it gets any better.

Log Number: 3997260Logbook(s): 

• ELOG

Entry Makers: bjacobBody: 

MQD1L04 (Trim Rack NL01B02 Ch. 7) current read back was reading 0.014 A above setpoint which was enough to give mismatch alarms. Tried cycling and manually adjusting set point to get the readback to agree but no luck. Went to the rack to reseat the card but the readback was still 0.014 above the setpoint. Swapped out the card and now the readback matches the setpoint.

Log Number: 3997259Logbook(s): 

• ELOG
• POLOG

Tags: 

• Autolog

Body: 

Log Number: 3997257Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 2.4 Target restore date was 2022-05-27 11:54:47 The output from the myRestore execution was as follows: iocnl1 <NOTE> Rf6Cryo: Provided macro *CAV* is never used <NOTE> Rf6Ops: Provided macro *IOC* is never used Rf6Cryo Execute: burtwb -f /cs/opshome/burt/REBOOT/rf/snap/iocnl1heatdisvINIT.snap (success) Execute: burtwb -f /cs/opshome/burt/REBOOT/rf/snap/iocnl1heatmodemanual.snap (success) Pause: 8 second(s) Rf06Cryo_heatset@2022-05-27 11:54 6(6) restored Pause: 8 second(s) Rf06Cryo_heatmode@2022-05-27 11:54

Log Number: 3997256Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 2.4 Target restore date was 2022-05-27 11:54:47 The output from the myRestore execution was as follows: iocnl1 <NOTE> Rf6Cryo: Provided macro *CAV* is never used <NOTE> Rf6Ops: Provided macro *IOC* is never used Rf6Cryo Execute: burtwb -f /cs/opshome/burt/REBOOT/rf/snap/iocnl1heatdisvINIT.snap (success) Execute: burtwb -f /cs/opshome/burt/REBOOT/rf/snap/iocnl1heatmodemanual.snap (success) Pause: 8 second(s) Rf06Cryo_heatset@2022-05-27 11:54 6(6) restored Pause: 8 second(s) Rf06Cryo_heatmode@2022-05-27 11:54

Log Number: 3997254Logbook(s): 

• EHSLOG
• ELOG

Entry Makers: mmerzBody: 

Noted Garage Doors are open. No instruction on whether to close them.

Log Number: 3997253Logbook(s): 

• ELOG

Body: 

With Radcon help the bad power module was removed and a spare inserted. Brought rack up and cycled all cards, all appears well. Suspect a fan may have failed in the bad supply.
It looks like all the expected resistance values updated back to some default value (1 Ohm for a BT, 0.5 Ohm for a BC) causing some cards to throw resistance alarms. I remember this happened after coming up from the last down due to an old restore file I believe. I'll ask Gary to take a look at this.

Log Number: 3997252Logbook(s): 

• ELOG
• SLOG

Tags: 

• Autolog

Body: restorelib 2.4 Target restore date was 2022-05-27 11:54:47 The output from the myRestore execution was as follows: Failed to set restore status indicator iocnl1 <NOTE> Rf6Cryo: Provided macro *CAV* is never used <NOTE> Rf6Ops: Provided macro *IOC* is never used Rf6Cryo Execute: burtwb -f /cs/opshome/burt/REBOOT/rf/snap/iocnl1heatdisvINIT.snap (failure) channel >R14XHTDH.DISV< not connected, no ca_array_put() channel >R13XHTDH.DISV< not connected, no ca_array_put() channel >R12XHTDH.DISV< not connected, no ca_array_

Log Number: 3997249Logbook(s): 

• ELOG

Body: 

The terminal leads @ MDB1L24H and MQB1L24 where swap @
the terminal block. Swap the leads to their correct position and did
polarity and Inductance measurement on both magnets.

MDB1L25V was showing a Open @ the magnet, tightened the
terminal connection and moved the cable around a bit. The magnet
appears to be working now. The magnet cable itself appears to
have been repair at some point and there could be a bad
connection @ the repair portion of the cable... We will continue to
monitor this magnet.

Diggs, Kissinger

Log Number: 3997246Logbook(s): 

• ELOG

Body: The following Bypassed Interlock had it's Expected Removal Date changed in the Accelerator Bypassed-Interlocks Log (ABIL) Previous Expected Removal Date: 27 Nov 2022 New Expected Removal Date: 27 Nov 2022 Who made the change: Lee Broeker Justification for the change: Chassis air flow interlock remains jumpered, engineering fix is not yet comple

Log Number: 3997245Logbook(s): 

• ELOG

Body: The following Bypassed Interlock had it's Expected Removal Date changed in the Accelerator Bypassed-Interlocks Log (ABIL) Previous Expected Removal Date: 27 Nov 2022 New Expected Removal Date: 27 Nov 2022 Who made the change: Lee Broeker Justification for the change: Chassis air flow interlock remains jumpered, engineering fix is not yet comple

Log Number: 3997244Logbook(s): 

• ELOG

Body: The following Bypassed Interlock had it's Expected Removal Date changed in the Accelerator Bypassed-Interlocks Log (ABIL) Previous Expected Removal Date: 27 Nov 2022 New Expected Removal Date: 27 Nov 2022 Who made the change: Lee Broeker Justification for the change: Chassis air flow interlock remains jumpered, engineering fix is not yet comple

Log Number: 3997239Logbook(s): 

• ELOG

Body: The following Bypassed Interlock had it's Expected Removal Date changed in the Accelerator Bypassed-Interlocks Log (ABIL) Previous Expected Removal Date: 27 Nov 2022 New Expected Removal Date: 27 Nov 2022 Who made the change: Lee Broeker Justification for the change: Chassis air flow interlock remains jumpered, engineering fix is not yet comple