Detector software restart 

During normal operation two Servers are needed to operate the Pilatus detector - Pilatus 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. In case you are experience problem with the Pilatus, such as fuzzy images, data collection doesn't start, data collection failing you can stop the Pilatus software by clicking on the icon "Stop Pilatus"

To restart the Pilatus software you need to start the new version of Camserver. To do this, click on the Icon "Start camserver". The terminal below will open

 start_camserver.png (Start camserver1)

 In this terminal type ./start.sh

and press enter

 start_camserver1.png (Start camserver2)

 Now you can click on the icon "Start Pilatus" on the right screen (id29control:1) or by typing start_pilatus.sh in a terminal on id29control during a remote access. You will have three windows, "Pilatus - do not close", "camserver" and "Pilatus server" as below

Update: Since the installation of new Pilatus3 6M you have two windows: det@pilatus29, Pilatus server and restart of MXCuBE2 after the Pilatus software is running

start_camserver3.png (Start camserver 3)

 

After Start 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 software restart - Remote Access

When logged in id29control type

- stop_pilatus.sh to stop all servers

- start_camserver.sh to start camserver and tvx

- start_pilatus.sh to start pilatus server

 

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.png (Enter)) on the right for few seconds.

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).

Photo0254.jpg (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

Photo0253.jpg (Pilatus switches)

Two switches are in the back of the Pilatus. In case you need to hard restart the detector you just need to switch them off and on again. You need to stop and start the detector software afterward (see above).

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.

Photo-0251.jpg (Pilatus back)

 

Restart adxv follow

To kill and restart ADXV Follow it should be sufficient to click on "Adxv Follow Icon" or on "Stop Adxv Follow" icon. If this is not working login on id29gate as opid29 and type ps -ef |grep adxv

id29gate:~ % ps -ef |grep adxv
opid29    9425  9424  0 09:08 ?        00:00:00 bash -c source /etc/profile; start_adxv_socket
opid29    9468  9425  0 09:08 ?        00:00:00 /bin/bash /users/blissadm/local/bin/start_adxv_socket
opid29    9469  9468  0 09:08 ?        00:00:00 /bin/bash /opt/pxsoft/bin/adxv --PXSOFT_VERSION v1.9.7 -socket -swap_beam_center
opid29    9749  9469  0 09:08 ?        00:00:00 /opt/pxsoft/adxv/v1.9.7/redhate4-i686/bin/adxv -socket -swap_beam_center
opid29    9765  9300  0 09:09 pts/0    00:00:00 grep adxv

 then kill directly the adxv process by typing kill -9 PID. In the example above type

kill -9 9425; kill -9 9468; kill -9 9469; kill -9  9749