You are here: Home Users and Science Experimental facilities Structural biology How to use our beamlines TROUBLE SHOOTING Detector solutions ID29 - Pilatus 6M troubleshooting

ID29 - Pilatus 6M troubleshooting

last modified 24-04-2012 15:05

 

Detector software restart 

During normal operation two Servers are needed to operate the Pilatus detector - Camserver Pilatus ServerPilatus Server and Camserver - which run in two separate xterm session, as in figure. Both applications must be running to collect data. Camserver is the Dectris server the control the detector; Pilatus server is the bliss server that interface spec and mxCuBE with the Camserver.

The two servers can be restarted in case of any problem by clicking on the icon "Restart Pilatus" on the right screen (p1-id29:1) or by typing start_pilatus.sh in a terminal on p1-id29 during a remote access.

 

 

After Restart Pilatus, if Camserver restarted correctly you will get something as follow in the camserver terminal

* THread
 Channel 0: Temperature = 29.8C, Rel. Humidity = 14.5%
 Channel 1: Temperature = 25.5C, Rel. Humidity = 20.7%
 Channel 2: Temperature = 28.7C, Rel. Humidity = 0.0%
* imgmode p
* fillpix 0x9d367
* imgonly /home/det/p2_det/images/image_00429.tif
* imgmode p
* calibrate
* imgonly /home/det/p2_det/images/image_00430.tif
* imgmode x
*
Closing the socket & exiting child process
*
Connection request from 127.0.0.1
Connection has full control; pid = 14255
* Threshold has not been set
 Exposure time set to: 1.000000 sec.
 Exposure period set to: 1.005000 sec
 Image path:
  /lima_data/
 Delay time set to: 0.000000 sec.
 Exposures per frame set to: 1
*

Note that the temperature on Channel 1 must be around 25C and the Humidity on the Channel 2 is 0% (must be lower than 25%) to be able to operate the detector.

In the Pilatus server

terminal you get

This is your .profile_private talking. Put your changes in here and keep
taking newest .profile and .kshrc from /csadmin/common/install/cs-startup

Failed to import EventChannelFactory notifd/factory/pilatus29 from the Tango database

you can now start to collect data.

 

Detector temperature and Humidity

The Pilatus 6M operates between 15C and 35C. The operation temperature is set at 23 C. If the temperature is too high, or too low a warning will appear in the camserver application preventing the detector from being used.

Check if the chiller (placed between Experimental and Optic Hutch) is on and if the temperature set is correct (23C).

The green button on the right switch the chiller on and off. After turning it on, press the enter button (Enter) on the right for few seconds.

Chiller

If in the temperature is too high you will get a warning in the Camserver and you will not be able to collect data.

The same applies if the humidity is too high. Humidity is kept at reasonable values fluxing N2 gas inside the detector (blue tube in the image below).

Pilatus N2

 

Temperature/Humidity error

In case of problem with the temperature and/or humidity you will get an error like the following one

Temperature / Humidity sensing disabled on DCB 1
*** ERROR - 3 required temp / humidity sensors not found
Bad return from dcb_initialize()
Camera initialization error -- press <enter> to exit

You should check that the temperature of the cooling is the correct one and that the N2 stream valve is open. If they are OK, the error message is due to a communication problem. To overcome it, switch off the Pilatus and back on after few seconds, as explain here below.

 

Switching on/off the Pilatus

Pilatus switches

Two switches are in the back of the Pilatus. In case you need to hardly restart the detector you just need to switch them off and on again. You need to restart the detector software afterward.

After having restarted the detector the two led for Power and Temp will be red until the detector software has not been restarted and the Camserver has complete the checking and booting of the detector.

Pilatus back

 

 

 

 

 

 

 

 

 


European Synchrotron Radiation Facility