Detector solutions

A detector problem is often seen in SPEC(exp) as:

esrf_io() server error.
Error on "id14/adsc/1" sending DevWriteImage.

or

Waiting for 1
Waiting for 1
Waiting for 1
Waiting for 1
Waiting for 1
Waiting for 1
Waiting for 1...

or

Waiting for 0
Waiting for 0
Waiting for 0
Waiting for 0
Waiting for 0...

1. Most detector problems can be fixed by restarting the device server, followed by a reconfig in SPEC (exp). For Q315R detector on ID14-4 and ID23-1 please refer to the specific page Q315R specifc issues - ID14-4 ID23-1 detector

2. Restart Detector software during a Remote Access,  type  start_detector_ra  in a terminal on the control  PC.

3. If the problems persist it is worth restarting the software on each of the individual ADSC control PCs (located in the blue control racks of each beamline). This is done by stopping the ADSC software on each of the control PCs (9 on ID14-4/ID23-1/ID29 and 4 on ID14-1/2/3). You then need to start each PC by clicking on "Start,StopXMLRPC Server", followed by a click on the "Restart Detector Software" icon on the beamline control PC desktop and a reconfig in SPEC (exp).

4. If this does not solve the problem it is worth running the "Restart Detector Software" in the foreground. To do this you need to run the 'adsc_detector_restart' on the adsc control PC. This window has more information and will inform you if there is a problem with one or more ADSC control PCs. You can then try to ping this machine to check whether its visable on the network. If not, restarting the offending PC might be the solution, followed by the procedure described in 2.

ID23-2 has a Mar225 which can be restarted on sybil in the ID23 PC control room.