OCD Guidelines.¶
This section mentions known problems and how to react to them
1. SEVERE EVENT (i.e. power cut, vacuum failure, leak of Si-oil or water)¶
In general, the detector interlock system will try to bring the detector to a state which is safe for the detector. Nevertheless there are situations (i.e. power cut), in which the interlock system is also affected and, depending on the type of failure, some of the safety actions cannot be automatically executed.
- 1st step: Assess the situation, check if the detector is in the safe condition:
- Detector is powered OFF
- Detector is warmed / is warming up to +20 deg C
- no Si-oil or water leak is observed
- 2nd step: if detector is not in a safe condition, depending on the type of failure, try to minimize the risk of the detector damage:
- Si-oil leak observed: power down detector and switch OFF the Julabo chiller in the hutch (front panel, main power switch, see user Manual for more details)
- Vacuum failure (system is accidentally vented > 1mbar ) => check if detector is warming up, it takes ~ 15 min till the temp reach +20degC, try to bring the vacuum system up as soon as possible.
- 3rd step: Call DET OCD
Warning
Do not try to cool down and start up detector before consultation with DET expert.
2. OPERATIONAL ISSUES - AGIPD¶
These issues can frequently be solved by procedures given in the manuals. OCD will only take on these problems after the prescribed troubleshooting has been performed. Therefore please follow the procedure below: * 1st step: Use trouble shooting guide to solve the problem
- Not seeing any image updates in online preview:
- check if there are no ERRORs in the run controller DAQ states
- Is the DAQ in monitoring state and are the data sources selected?
- Is the detector sending data ( use Rundeck script from ITDM)
- Detector is not sending data:
- Verify DAQ status
- follow up the trouble shooting section in manual 1
- Corrected image performance is not as expected:
- verify image performance in raw online preview, if not ok follow up performance trouble shooting section in the manual
- if raw image looks ok:
- check that the parameters in the “operating conditions’ table are correct for the current operation scenario (Calibration Manager Scene)
- follow up online preview trouble shooting 3
- No updates in online previews
- see online preview trouble shooting 3
- Online previews are slow
- see online preview trouble shooting 3
- Calibration constants in online preview cannot be loaded
- see online preview trouble shooting 3
- Karabo bridge not sending data, but online preview updating
- call Control OCD
- DAQ crashed
- call ITDM OCD
- Karabo servers are down or other control problems
- call Control OCD
- Detector interlocks were triggered:
- check vacuum system status, if not ok:
- check that the detector is warming up
- power down detector
- fix the problem of the vacuum system
- if the detector pressure was > 1mbar, call DET OCD to verify if the detector can be again cooled down and powered up.
- check if the temperatures of cooling blocks and external housing are in the usual range. If not:
- heck Julabo chiller in Rack Room, if not ok follow up Julabo manual
- Check K3 chiller hutch rooftop, if not ok follow up K3 chiller manual
- follow up trouble shooting section in the manual
- Issues with startup of the detector => follow up trouble shooting section in the manual
- Detector cannot be cooled down
- check Julabo chiller in RR, if not ok follow up Julabo manual
- Check K3 chiller on the hutch rooftop, if not ok follow up K3 chiller manual
- follow up trouble shooting section in the manual
Warning
do NOT try to cool the detector if chiller is in INTERLOCKED state.
- 2nd step: If the trouble shooting fails, call DET OCD
- If you do call DET OCD, please be prepared to answer the following questions:
- what was done before the failure occurred
- have you tried any recovery procedures
- have other OCD lines been called
- have you verified the problem is due to the detector, and not of a different cause. If so, how?