Page History

...

1. Understand the problem (What are they trying to do that isn't working? Is the logic for something not working as expected? Is something missing? What have the scientists already tried?)
2. Determine the general scope of the problem... Is this problem with a PV? Is this a problem with hutch python? Is this a problem with the DAQ?
   1. Is this a problem with a screen?
      1. Screens use PVs at their very foundation, if a screen is not showing a PV properly, it might be worth checking that the PV is connected
      2. Is the PV "caget-able" (check the IOC)? Does the PV show from different subnets (if not, this points to a gateway issue)?
   2. Is this a problem with hutch-python?
      1. If it is an issue with hutch-python, the root of the problem could be related to the experiment / hutch scripts. 
      2. This would likely require intervention from the POC (if they haven't already been called)
   3. Is this a problem with motion?
      1. Motion systems in the FEE are controlled (mostly) via PLC. This could be related to a number of problems, but the most easily checked would be the health of the PLC IOC. If the PLC IOC is generating PVs normally, the problem could be more fundamental to the system.
      2. If you are properly trained in PLCs, it would be okay to check on the PLC side, and see if there are fatal errors on the PLC, and other things. This would certainly point to involvement on the SME's part. Even if you can pinpoint the problem, any changes to this system should be done by an SME
   4. Is this a problem with vacuum?
      1. As with Motion, vacuum systems are also controlled via PLC in the FEE. It could be useful to look into the PLC and see if the logic of interlocks are working appropriately. Even if you can pinpoint the problem, any changes to this system should be done by an SME

...