Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added blurb regarding RF status bar being purple/invalid

Learning Objective: This module is intended to teach operators how to use the Cavity Summary Display to monitor and diagnose issues with cavities.

Skills:

  • Know how to launch the GUI
  • Understand the information presented on the GUI
  • Know how to interpret faults and see the status of all potential faults associated with a cavity
  • Understand how to restart backend if the display stops updating


Introduction:

Image Added

Figure 1: Overview of Cavity Display GUI

The Cavity Summary Display is similar to the Klystron displays used in LCLS and FACET, but instead of displaying klystron information, the Cavity Summary Display shows cavity faults for all cavities in cryomodules 01 - 35. The GUI also displays whether a cavity's SSA is on and whether or not is has RF.

...

Interpreting Information on the GUI:

Cavity Shapes and Colors:

Now that we've launched the GUI, we want to use it to help us troubleshoot and keep an eye on the cavities. The GUI is broken up into the four linac regions (L0B, L1B, L2B, and L3B) each with their own cryomodules (abbreviated as CM). Each of these cryomodules has 8 cavities. If a cavity is faulted, it will display a Three Letter Code (TLC) instead of its cavity number.

...

The different shapes used for these faults were chosen with the purpose of making the GUI red/green color blind accessible.


Figure 12:  Various cavity statuses


Cavity Status Bars:

Below each cavity are two status bars. The left status bar indicates whether the SSA is On or Off, while the right status bar indicates whether the RF is On or Off.


Figure 23:  Example of a cavity with its SSA on and RF on

There is a known state where the RF status bar will appear pink/purple, but it's not disconnected in the way that we typically think about it. The RF status bar could could appear to be disconnected, but caget ACCL:L{LINAC}:{CM}{CAVITY}0:RFSTATE of the PV will yield "OFF" instead of the typical "Channel connect timed out" message. If you caget the PV again with .SEVR added to the end of it, it should yield a severity of INVALID which is what's causing the status bar to fault and indicate disconnected. This state occurs when the RF chassis is non-communicative. 

Image Added

Figure 4: Disconnected RF status bar when the RF chassis is non-communicative. This can be proven by caget-ing the PV's severity.

Understanding Cavity Faults

Three Letter Code (TLC) Decoder:

As mentioned earlier, a faulted cavity will appear on the GUI as a red hexagon with a three letter code (TLC). To figure out what fault the TLC corresponds to, we can click on the "Three Letter Codes" button in the upper right corner of the Cavity Display GUI. This will launch a Cavity Fault Three Letter Codes panel with an alphabetized list of all the potential cavity faults as well as a short description of what each fault means.

Cavity Faults Panel:

Although cavities may have multiple faults at one time, the display can only show one fault at a time and it is designed to show the highest priority fault (aka the most severe/concerning fault) first. To see what other faults may be affecting a specific cavity, we can open a cavity fault panel for the cavity by clicking directly on the cavity widget. The resulting fault panel will display all the possible faults in order of decreasing priority. To see the PV associated with each fault, we can middle click the fault status box (which will display "OK", "FAULTED", or "INVALID").

Figure 35:  Cavity fault display panel showing all faults for a given cavity

...

If you notice the watcher status indicates "NOT RUNNING", feel free to restart the watcher by launching an SRF Home via Launchpad, and then clicking "Stop Backend" followed by "Start Backend." After a minute or two, the backend should be working again. There is a known bug specifically with the cavity display GUI on the Large Monitor where the display occasionlly occasionally freezes. If the GUI works locally on an OPI but is frozen only on the Large Monitor, the Large Monitor GUI might just need to resized ever so slightly to wake it up (this is a very weird and particular bug that occurs only on the Large Monitors).

...