Common Problems

Problems and Solutions

• Collimator Temperature is Rising
  • If the collimator temperature alarm goes off, call MCC and tell them to turn off the beam. Then call the RC.
  • Don't raise the temperature alarm limits on the collimator. If it's getting warm, something's wrong.
  • Things to check:
    • Is the collimator cooling? Stripchart should show 5 for the water flow at all times.
    • Is the raster size correct? Correct size is written on white board.
    • Have the Raster quads (Moller quads) been set to the correct values? See strip chart called "RasterQuadsCheck" and scale back in time to look for changes to values
    • Are the bpms working? IPM1H04A and IPM1H04E XPOS and YPOS should read out nonzero numbers on the strip chart when beam is on.
    • Is the beam in the right position? See appropriate IPM1H04A and IPM1H04E XPOS and YPOS written on the whiteboard.
    • Is the HallATGT lock enabled? Call MCC and ask if the target lock is enabled

• Runbird Aq/Parity feedback isn't working
  • We want Aq/Parity feedback running at ALL times during production data taking
  • The most reliable check to see feedback is working is to look at VPITA on runbird and make sure it is changing values every 10sec (when beam is ON).
  • If you see a red box on Runbird or if Aq doesn't update, look at VPITA. If VPITA is changing, feedback is working.
  • You can triple check by looking at the terminal where Aq/Parity feedback is being run from. Every 10sec it will output a text output showing ....HallA Aq... and ....correction... as well as a list of 8 RTP voltage values. If you see these values being updated in the terminal, feedback is still working.
  • However, if a Parity RTP voltage or IA voltage alarm goes off, feedback may be feeding back improperly. A map file may have been changed and the RC should contact the WAC.

• BPM Saturation
  • On panguin and in the alarm handler, we examine bpm11(IPM1C11) and bpm12(IPM1C12) for saturation. If they get near 50,000, they are saturated.
  • If BPMs are saturating and we are running FFB
    • The solution is to call MCC and request an FFB Gain search. OPS should switch FFB off, press a gain search button. And then turn FFB back on and the saturation should go away. It may be necessary to turn off BMW if this process takes a while. It should take OPS just 1min or so, though.
  • If BPMs are saturating and we are NOT running FFB
    • The solution is to call MCC and tell them that iocse9 is in "Feedback Mode" instead of "SEENormalOPS" mode. OPS needs to put iocse9 in "SEENormalOPS" mode for the BPMs to auto gain properly