Detectors: Pilatus, PCO, PerkinElmer, etc.

The detectors are integrated in Sardana as two dimesional experimental channels. In this way they can be added to the measurement group as counters and during a scan images will be taken at each point.

Up to now the detectors implemented in Sardana are: Pilatus, PCO, MarCCD, PerkinElmer, LCX camera, Lambda, EigerDectris, EigerPSI, PSCameraVHR, TangoVimba , HzgDcam and the ones controlled via Lima.

This is how a detector has to be introduced in the online.xml file for having it in Sardana:

<device>
  <name>detector_name</name> 
  <type>DETECTOR</type> 
  <module>module_name</module>
  <device>my/detector/device.01</device> 
  <control>tango</control> 
  <hostname>hasppXY:10000</hostname>
</device>

The most important tag for recognizing that the device corresponds to a detector and from which type is <module>. The possible <module> values are:

For Pilatus detector: pilatus100k, pilatus300k, pilatus1m, pilatus2m or pilatus6m. You can use the one corresponding to your type of detector, for Sardana there is no difference.
For PCO detector: pco, or any name containing pco, if we want to be more precise, for example pco200.
For MarCCD detector: marccd, or any name containing marccd.
For PerkinElmer detector: perkinelmer, or any name containing perkinelmer
For LCX camera: lcxcamera, or any name containing lcxcamera.
For Lambda: lambda, or any name containing lambda.
For EigerDectris: eigerdectris, or any name containing eigerdectris.
For EigerPSI: eigerpsi, or any name containing eigerpsi.
For PSCameraVHR: pscameravhr, or any name containing pscameravhr.
For TangoVimba: tangovimba, or any name containing tangovimba.
For HzgDcam: hzgdcam, or any name containing tangovimba.
For detectors controlled via Lima: limaccd, or any name containing limaccd.

Remarks about the other tags:

<name> is arbitrary, it will be the name of the detector inside of Sardana
<type> has to be DETECTOR (important if used in Online, not used in Sardana)
<device> has to be the name of the Tango device corresponding to the detector.
<control> is tango (only relevant for Online)
<hostname> is the Tango hostname your the detector Tango server runs in.

Certain detector attributes are not handled by the controllers because this would involve MacroServer I/O which can be too time consuming. The following sub-sections present Macros that do this job.

Section 13.2.3 explains how a pre-scan hook can be employed to configure detector attributes in a way that the images are stored in a standardized directory structure.

2019-11-13