Differences

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

--- life:operator_explain [2025/08/27 16:36] – ryans
+++ life:operator_explain [2025/08/27 16:39] (current) – ryans
@@ Line 32: / Line 32: @@
   * 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]].