The aim of this page is to document how we reconfigure the ASC MPOD from standard ePix configuration to be able to run the legacy CSPAD detectors (CSPAD 2M and CSPAD140).
Hardware configuration changes.
The CSPAD concentrator and PDU is located on top of the ePixPDU in the ASC MPOD. The first step in reconfiguring the hardware is to move the Weiner power cables (HV and LV) from being connected to the ePix PDU to being connected to the CSPAD PDU. See Figure 1. in addition to these connectors, the CSPAD PDU and concentrator takes a number of input connectors:
- RS232 ethernet cable (Concentrator; connects to the digi under the optical fiber, close to the tool cabinet);
- 3 fiber optical cables (RC0, RC1,EVR);
- 3 bnc cables (2M trigger; DAQ and Run trigger for small, connects to the back of daq-det-portable2 in the chase);
A number of output connectors are present going to the detectors:
- CSPAD2M: 2 sets of cables labeled Q0-Q3 are connected to the back of the detector (one Q-pair per quad);
- CSPAD140: one power cable is connected to the back of the CSPAD140; additionally, the RC1 fiber connection is taken out of the concentrator when running a 140 and connected directly to the back of the detector.
Figure 1. Connections needed to run CSPADs in the ASC lab.
Fiber optic connections
The RC0 and RC1 fibers are fiber lanes 1 and 2 that we normally use to run small ePix detectors (Marietta). The EVR fiber goes back to the chase and connects up to the third channel of the EVR module, as can be seen in Figure 2. The connections for the fibers are summarised in Table 1.
Figure 2. Fiber optical connections for running CSPAD detectors.
Table 1. Fiber connections for the CSPAD setup.
Fiber input name | Fiber to use | Fiber location endpoint |
RC0 | Fiber lane 1 (epix small fiber) | Marietta |
RC1 | Fiber lane 2 (epix small fiber) | Marietta |
EVR | Its own fiber going to the chase | Chase (evr module, see picture) |
BNC connections
The BNC connectors are connected at the cable bridge and go back to the chase. The cables connect to a BNC "braid" as seen in Figure 3, which is connected to the back of the daq-det-portable2 server. The cables at the cable bridge are labeled to match the labeling at the CSPAD PDU. The connection of the different bnc cables to which cable of the cable "braid" can be seen in Table 2.
Figure 3. Connections for the BNC connectors.
Table 2. Connections between bnc cables and bnc "braid"
Trigger | Cable number in BNC braid |
Trigger for 2M | 0 |
DAQ trigger small | 1 |
Run trigger small | 2 |
Detectors in the .cnf file
The lines to uncomment to include the cspad 2M and cspad140 can be seen in Figure 4.
Figure 4. Relevant lines in the .cnf file
GUI for controlling the CSPAD2M
To launch the control gui for CSPAD concentrator is launched by deploying cspad_display as seen on top in Figure 5. This launches the GUI seen at bottom of Figure 5. The start sequence is seen in the center of the gui, and the expected current draws can also be seen. Seeing the detector response can be done using the standard process for a detector in the LCLS1 DAQ. The channel that is controlled when running the 2M can be seen in Figure 6.
Figure 5. Launching the CSPAD control panel.
Figure 6. Channels that are used for running the CSPAD2M.
Control for the CSPAD140
Please note that when running the CSPAD140k, the RC1 fiver has to be connected directly to the detector as opposed to the CSPAD PDU. For the 140, the concentrator does not have to be on, and the detector is powered on directly in the MPOD GUI. The channels to turn on can be seen in Figure 7.
Figure 7. Channels to turn on for the CSPAD140k.