User_Manual-PILATUS-V1_2.doc 33/57
The command index number (see 'case_definitions.txt') may be generic or
specific. Most commands have the generic response 'send' (case number 15)
and, if the response is 'OK', can usually be ignored.
The exposure commands (Exposure, ExtTrigger, etc) operate a little
differently. They give an immediate acknowledgement (case number 15, the
generic response), followed by a second acknowledgement after the exposure
series is completed (case number 7), carrying the full path name of the last
completed exposure. Intermediate acknowledgements, e.g. every 100 images,
can be requested as well via the 'SetAckInt' command.
Because of the socket connection protocol, the camera hardware and server
can reside on a different machine from the high level controller.
Camserver implements a token mechanism to prevent more than one outside
process from having control over the hardware. The camserver window has
full control at all times.
There is a debug facility to help with setting up the interface. If you type
"dbglvl 5", the file 'camdbg.out' will contain many messages, including the
exact contents of socket messages. Be sure to set "dbglvl 1" (the default)
before doing real work, else 'camdbg.out' can grow without limit. If there are
difficult problems with the detector, a run with "dbglvl 6" reproducing the error
can be helpful for diagnosis. Simply capture 'camdbg.out' and send it to
DECTRIS.
The Camserver program of the PILATUS detector provides a simple to use
interface for either EPICS or SPEC. Several clients for these protocols have
been written at the Swiss Light Source (SLS) of the Paul Scherrer Institut
(PSI). by Marc Rivers of the University of Chicago:
http://cars9.uchicago.edu/software/epics/pilatusROIDoc.html
9.4.1 Steps to bring up a PILATUS detector in a new
environment:
PILATUS detectors are shipped fully configured and ready to operate as
stand-alone detectors. Some minor customization is required to integrate into
a beam-line environment.
1) If needed, change the hostname to be compatible with the local network.
This can be done conveniently in SuSE linux with YAST2, or directly with vi.
2) Set up the detector on the network, if needed. Note, that the detector does
not require an external network.
To Next Page
Loading...