Starting the ADSC Q315 Detector

Unfortunately, it is occasionally necessary to restart the ADSC detector along with the associated software. This will summarize how that is done. We will assume that everything is up and running at the beginning of the process; starting when some component or other is down is essentially the same.

We’ll assume that this is only a short interruption and that we don’t have to worry about the detector vacuum.

Begin by bringing the detector to room temperature (or +10C) as described in “Detector Temperature Settings.”

Once the detector is warmed up, it can be shut down at the power switches —- it is not necessary to shut down the detector processes or other software first.

Turn the detector power switches (the green switches highlighted by the arrow) off from top to bottom. The main power switches should be turned on starting with the bottom power module, then the middle module, then the top module. The order does matter.

If you don’t have the “REMOTE Detector OP” processes running yet, this is the time to start them. Double click on the “REMOTE Detector OP” shortcut, and you should see a DOS window appear:

Even if you already had these processes running when you restarted the detector, they still must be sent a reset signal. We generally do this from a script. The script makes up part of /programs/beamline/nuke, so it can be found there, but for completeness, here is the one we’ve been using:

foreach module ( detector0 detector1 detector2 detector3 detector4 detector5 detector6 detector7 detector8 )
    # send the reset signal
    echo -n "$module restart "
    echo "restart" | sock_exchange.tcl $module 8038 1
    echo ""

Entering that script at a shell prompt at any of the BL12.3.1 Linux consoles should reset the whole group of detectors. (Since the BLU-ICE/DCSS control programs run on dataserver, that is a good place to run the script.) This reset signal will cause lots of activity on the “REMOTE Detector OP” windows: