Currently we use CCD detectors from

ADSC, MAR and Dectris.

 

 

Beamline Manufacturer Type Dimensions Max resolution on beamline Pixel size Default detector mode Image size by default Image size by default
ID23-1 ADSC Q315r 315 0.6Å 51μm hardware binned 3072 x 3072pixels 18.9Mb
ID23-2 MAR Mosaic 225 0.9Å 73μm unbinned 3072 x 3072pixels 18.9Mb
ID29 Dectris Pilatus 6M   172μm N/A 2463 x 2527pixels 6.0Mb
BM29 Dectris  Pilatus 1M  bio-SAXS  172μm unbinned 981 x 1043 pixels 4 Mb
ID30A-1  ADSC Q315 315   51μm hardware binned 3072 x 3072pixels 18.9Mb
ID30A-2 ADSC Q315 315   51μm hardware binned 3072 x 3072pixels 18.9Mb
ID30A-3 Dectris Pilatus3 2M   172μm      
ID30B                

 

General Trouble Shooting

Many problems can be resolved by clicking on the 'Restart Detector Software' on the desktop, followed by a reconfig in the Exp SPEC session. This is recommended as the first course of action with a detector problem.

 

 

 

ADSC Q315r Detectors

A link to the User Manual for the Q315s can be found in the left-hand menu.

Simple overview

Each of the 9 ADSC CCDs is controlled by a single WindowsXP computer linked via a fibre optic connection. These 9 ADSC control computers are linked via a local gigabit connection for fast data transfer to the adsc control PC running under linux. The 'Remote Operate' software has to be running on each of these 9 control PCs. The CCD 'image gather' and 'Device server' runs under linux on the adscxxxctrl. This software is started by clicking the 'Restart detector software' on the beamline control computer.

Detailed trouble shooting procedure with Q315r

If the general 'Restart detector software' does not work, the problem may well be with the software running on the ADSC computers. The first thing to do is check that the 'Remote operator' software is running on each of the 9 WindowsXP. If they are running ok, then perhaps try running the 'Restart detector software' in the foreground for more detailed and non-disappearing messages! This can be done by logging onto the adscxxxctrl PC and typing 'detector_restart' in any shell window. This then allows you to read all the output and it may become more obvious that there is a problem with one or more control PCs, see the manual for the naming scheme. The software on the offending PC can be restarted, followed by a 'Restart detector software' and reconfig in SPEC. If there is still a problem then the offending PC should be rebooted, the 'Remote operator' software restarted, followed by a 'Restart detector software' and reconfig in SPEC.

If there is still a problem then all the ADSC control PCs should be rebooted, the 'Remote operator' software restarted on each one, the 'Restart detector software' started and reconfig in SPEC. If this does not help then you will have to look in the manual for possible clues.

Data Backup on Beamlines with a Q315

The large ADSC Q315 detectors have image sizes of ~75Mb in unbinned mode and ~18Mb in binned mode.

Using the detector in unbinned mode in conjunction with the sample changer for 24 hours could mean that up to 1Tbyte of data may be collected! For data backup it is therefore recommended that you bring disks of adequate capacity, e.g. 500Gb disks. Some tests have been made at ESRF using Maxtor 500Gb disks and these work fine with the JDM software used on the beamlines. In the near future, tests will also be made with Iomega and Lacie disks.

Please make sure you bring adequate disk space for backup if you will be using one of the beamlines whee thes detectors are installed (ID14-4, ID23-1, ID29, ID30A-1 and ID30A-2). In case of problems once you are here, the MX Group has 2 spare 500Gb disks which we may lend to you.

Data Archiving on Beamlines with a Q315

There are currently ~10Tb of disk space available on ID23-1 and therefore no problems are foreseen for keeping your data on disk here for 15 days as usual. On ID14-4 and ID29 however we currently do not have adequate disk space to save your data for more than a couple of days, although CS are looking into this problem and we expect to have a solution to this early in 2006. Until a solution is found we therefore recommend that you are extremely vigilant about backing up your data while you are here, and to start the data backup as soon as possible.