Differences

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

--- task:beamloss_tool [2024/10/01 15:39] – created pirkola
+++ task:beamloss_tool [2025/08/21 12:34] (current) – ryans
@@ Line 2: / Line 2: @@
-Tanner's notes:
+== Tanner's notes ==
-The tool configures BCM D5789 instead of D5521. Unfortunately, D5521 is specifically called out in the “Procedure to monitor primary beam current” document. Gen is going to re-write that document. In the meantime, you can still use the old threshold by going to Diag MPS Device Overview New -> Diag Expert tab -> Open Old Diag MPS Overview  and use the 1.0 sec long average threshold.
+The tool configures BCM D5789 instead of D5521. Unfortunately, D5521 is specifically called out in the “Procedure to monitor primary beam current” document. Gen is going to re-write that document. In the meantime, you can still use the old threshold by going to Diag MPS Device Overview New -> Diag Expert tab -> Open Old Diag MPS Overview, or [[pages:mps_diag|here]], and use the 1.0 sec long average threshold.
 The tool automatically sets BCM thresholds. The calculation need the information on AP config tab to be accurate. The MEBT threshold sets it to a value that includes some noise overhead, so instead of 25 W exactly is corresponds with ~32 W for example.
 When running to the niobium plate, I left the destination as FS1a and just changed the “beam energy after charge stripper” to 1.5 MeV/u. This updated the BCM 1120 threshold to avoid tripping.
+It seems that any time a TCT Parameter is changed (see ‘TCT Recent Parameter Changes’ box) threshold selections are re-established. This can be an issue if you manually stop watching a dBCM while running a lower powered beam. -ALP
+====Shane note====
+* Good info but not noob friendly
+===== Links =====
+  *{{task:beamloss_tool_reference.pdf|Reference doc/cheat sheet}}