...

The DUT integration is controlled through setup of EUDAQ configuration files with names like ni_coins.cfg etc. residing in /home/tfuser/eudaq/conf folder (also Desktop folder) on the EUDAQ console node ar-eudaq. The data logging also goes to the data directory in the same folder. These configuration info are not only passed on to the RCE producer to configure the DUT, but also interpreted by the EUDAQ to derive online monitoring for the DUT together with the telescope. A general example of telescope + DUT configuration can be found here (not SLAC ESTB), while some explanations of the various configuration items related to the RCE producer can be found here.  

Pixel DUT YARR Readout

In addition to RCE, we also have integrated the YARR (Yet Another Rapid Readout) system into the EUDAQ system in ESA.  Here are some instructions.

    ssh -XY pixel@esadutlbnl1

    (ask Timon or Ben for the password or don't close the terminal)

    cd yarr-eudet/eudaq

    bin/yarr-fe65p2-producer -n YARR -r 172.27.100.8

In addition to starting the producer, one needs to modify the DUTMask in the .conf.  Add +4 to include YARR.  There is no need to add anything else because the configuration is currently hard-coded into the producer (and the Latency = 43 and Trig Count = 3 seem good so there should not be a need to touch this).

To fully kill this producer if it gets stuck or when terminating the run control, do a ctrl+Z to move it to the background and then kill in the usual way with ps ux | grep yarr.  Then, kill -9 <pid> where <pid> is the id of the producer from the ps ux.

After stopping a run, there will be some offline plots in ~/yarr-eudet/eudaq/data.  There is also a simple script for offline analysis:

    cd ~/yarr-eudet/eudet

    ../src/bin/read_rawData data<file>.raw #<file> is <Dutname>_<runnumber>

Infrastructure Utilities

EPICS Control Interface

...