Differences

This shows you the differences between two versions of the page.

--- life:operator_explain [2025/06/26 11:05] – painter
+++ life:operator_explain [2025/08/27 16:39] (current) – ryans
@@ Line 24: / Line 24: @@
   *Don't worry! The annunciator might be constantly reminding you that there's "30 Active Alarms", but having some be active is normal and more steeped in office politics than I'd like to go into. You should not however ignore the annunciator.
   *Firstly, you may have noticed that there are two voices for the annunciator. One is a male voice that speaks much more frequently and one is a female voice that speaks infrequently, but will most likely repeat herself a few times. Theses are separate alarm systems, we'll look at the male voice first.
-  *This is the Phoebus Alarm System, named after the software it lives in. Phoebus Alarms come in three varieties, all being announced before the rest of the alarm. Those are "Minor", "Major", and "Invalid"(pronounced "In-va-lid"). To explain these, let's imagine some measurement that gives us 20 of some unit. Many devices are being monitored and measured so this could stand in for many devices,I'm just using 20 as a simple number. There are generally 4 limits associated with any measurement, the HI, the LO, the HIHI, and the LOLO. The HI and LO and numbers that are above and below the expected measurement, so for our example the HI could be 23 and the LO could be 17. These are often set as warnings that the measurement is shifting and that you should look into them before they potentially get worse. After that the HIHI and LOLO values are more extreme in both direction, so HIHI could be 25 and LOLO could be 15. These will tell us that the situation has gotten worse and things could potentially be in a bad state. HI and LO alarms will trigger a Minor alarm and HIHI and LOLO will trigger a Major alarm. Try to keep an ear out for these kinds of alarms.
+  *This is the Phoebus Alarm System, named after the software it lives in. Phoebus Alarms mainly come in three varieties, all being announced before the rest of the alarm. Those are "Minor", "Major", and "Invalid"(pronounced "In-va-lid"). You'll also see "Undefined" on rare occasion, but these often are apart of some larger bit of work going on. To explain these, let's imagine some measurement that gives us 20 of some unit. Many devices are being monitored and measured so this could stand in for many devices,I'm just using 20 as a simple number. There are generally 4 limits associated with any measurement, the HI, the LO, the HIHI, and the LOLO. The HI and LO and numbers that are above and below the expected measurement, so for our example the HI could be 23 and the LO could be 17. These are often set as warnings that the measurement is shifting and that you should look into them before they potentially get worse. After that the HIHI and LOLO values are more extreme in both direction, so HIHI could be 25 and LOLO could be 15. These will tell us that the situation has gotten worse and things could potentially be in a bad state. HI and LO alarms will trigger a Minor alarm and HIHI and LOLO will trigger a Major alarm. Try to keep an ear out for these kinds of alarms.
   *Invalid alarms notify when a measurement is "disconnected", there was some error in communication that are normally very short, but these should always be checked to make sure connection was reestablished.
   *For response advice, check [[task:phoebus_alarms|here]].
@@ Line 30: / Line 30: @@
 ====MPS====
-  * The __Machine Protection System__ is a system. It's purpose is to protect the machine. Sardonicism aside, it takes those measurements we discussed before and watches them. Some of those measurements can go into alarm without threatening the health of the machine, but many of these measurements can tell us that it is unsafe for the machine to try sending beam. NOTE: MPS only protects the beam, I'll talk about our __Personnel Protection System__ soon enough.
+  * The __Machine Protection System__ is a system. It's purpose is to protect the machine. Sardonicism aside, it takes those measurements we discussed before and watches them. Some of those measurements can go into alarm without threatening the health of the machine, but many of these measurements can tell us that it is unsafe for the machine to try sending beam. NOTE: MPS only protects the machine, I'll talk about our __Personnel Protection System__ soon enough.
   * A few things happen when MPS finds a measurement that stops us from sending beam, firstly remember that it does not watch every measurement. Some measurements correspond to devices that don't directly impact beam  and therefore aren't watched. Some measurements correspond to situations that do impact the beamline, but are localized to an area where we are not sending the beam. Some measurements do not live on the same system as the "ftc" network that controls the [[dev:chopper|Chopper]], so even if they do tell us that something is wrong and we should stop the beam ASAP, they cannot be read by MPS to stop the beam automatically.
-  * So let's say that we're sending beam and everything is working alright, suddenly "MAJOR ALARM: MPS FAULT". Now, we're not sending beam, that's stopped by the __Chopper__. If you try to tell the __Chopper__ to send beam, it won't listen. This is because the device for whichever measurement went bad is now [[info:plc_interlocks|Interlocked]]. Measurements can vary quite a bit, most have a certain "fuzz" of variation from noise or device fluctuations and to ensure that this doesn't cause the device to go in and out of alarm unceasingly, it may enter an [[info:plc_interlocks|Interlocked]] state. The device should be checked (quickly looking at it's other measurements is ok in many cases) before the [[info:plc_interlocks|Interlocked]] is reset. The __Chopper__ may not be restarted until all devices have good measurements and are not [[info:plc_interlocks|Interlocked]].
+  * So let's say that we're sending beam and everything is working alright, suddenly "MAJOR ALARM: MPS FAULT". Now, we're not sending beam, that's stopped by the __Chopper__. If you try to tell the __Chopper__ to send beam, it won't listen. This is because the device for whichever measurement went bad is now latched. Measurements can vary quite a bit, most have a certain "fuzz" of variation from noise or device fluctuations and to ensure that this doesn't cause the device to go in and out of alarm unceasingly, it may enter a latched state. The device should be checked (quickly looking at it's other measurements is ok in many cases) before the latch is reset. The __Chopper__ may not be restarted until all devices have good measurements and are not latched.
   * One final note is that MPS does not watch any measurements when the __Chopper__ is off. They are very closely linked and sometimes it's convenient to allow devices to be adjusted without causing 100 alarms, so this can be done at any time by stopping beam with the __Chopper__. Sometimes we would like to watch those measurements but not send beam, this can be done by blocking the beam with devices other than the __Chopper__, for now it's good that you know this but the details aren't urgent to know. Feel free to ask another Operator to satiate your curiosity (Hint: mention "1102" and they should know exactly what you're talking about.)
   * Read more  [[task:mps_trips|here]].