...
- Green diamond with cavity number - This indicates that the cavity is healthy and has no faults.
- Yellow triangle with TLC - Cavity has a minor fault.
- Red hexagon with TLC - Cavity has a major fault.
- Gray octagon with TLC - Indicates cavity hardware mode (maintenance, maintenance done, or ready)
- Transparent octagon with 'OFF' TLC - Cavity hardware mode has been set to Offline
- Purple circle with TLC - The fault PV associated with the cavity displayed fault code is disconnectedinvalid.
The different shapes used for these faults were chosen with the purpose of making the GUI red/green color blind accessible.
...
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 or when the low level RF system otherwise can't trust the readout.
Figure 4: Disconnected RF status bar when the RF chassis is non-communicative. This can be proven by caget-ing the PV's severity.
...
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 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).
...