task:mps_trips
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
task:mps_trips [2024/11/04 20:08] – painter | task:mps_trips [2024/11/06 09:14] (current) – edited headlines pirkola | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== MPS Faults ====== | ||
+ | |||
There are a variety of MPS faults that can occur. This page will give a general solution to MPS fault that occur on a typical basis. | There are a variety of MPS faults that can occur. This page will give a general solution to MPS fault that occur on a typical basis. | ||
On the MPS Operator page, under the Failed Device section will be listed what specific device has faulted. From there, it is common practice to scroll down through the rest of the page until you find the specific device. If the device only latched, then you may click "Clear NOK" next to it, then restart the Chopper. If the fault is not simply a latch, then you must investigate further into the issue. | On the MPS Operator page, under the Failed Device section will be listed what specific device has faulted. From there, it is common practice to scroll down through the rest of the page until you find the specific device. If the device only latched, then you may click "Clear NOK" next to it, then restart the Chopper. If the fault is not simply a latch, then you must investigate further into the issue. | ||
- | **__Cavity Fault__**: | + | ==== Cavity Fault ==== |
If a device under the RFC section fully faults, you will need to go to the RF main page to solve this. Once on this page, scroll down until you find the faulted device. Then, open the details page and diagnose the issue. Depending on what faulted, you can either reset the device, wait until it ramps back to its setpoint, then restart the chopper, or you may have to call someone. The image below clarifies what specific pieces you may need to call for, which are circled in red in the image. | If a device under the RFC section fully faults, you will need to go to the RF main page to solve this. Once on this page, scroll down until you find the faulted device. Then, open the details page and diagnose the issue. Depending on what faulted, you can either reset the device, wait until it ramps back to its setpoint, then restart the chopper, or you may have to call someone. The image below clarifies what specific pieces you may need to call for, which are circled in red in the image. | ||
Line 9: | Line 11: | ||
{{: | {{: | ||
- | **__BCM Fault__**: | + | ==== BCM Fault ==== |
task/mps_trips.1730768898.txt.gz · Last modified: 2024/11/04 20:08 by painter